8th June 2019
|
Arp Constable
|
|
Join Date: May 2008
Location: Dry and Dusty
Posts: 1,507
|
|
Theo de Raadt wrote
Quote:
I am hoping to get one also... and as a rule whatever I get my hands on tends to work \
out well.
danieljboyd@icloud.com wrote:
> I just ordered some E495s (not 'T', but pretty similar). I think
> they're supposed to arrive today. I'll do a test boot and send in a
> dmesg.
>
> On Tue, May 28, 2019 at 10:44:44AM -0400, David Anthony wrote:
> > All,
> >
> > The Lenovo release of T*95 series laptops with AMD Ryzen CPU appears imminent.
> >
> > Would these be poor choices for OpenBSD? Are there any anticipated ???gotchas??? \
> > that I should be aware of? Any thoughts would be greatly appreciated.
> > Respectfully,
> > David Anthony
> >
>
|
My understanding is that the kernel driver code is in -current but not currently in the default build. Early testers have to build a custom kernel
Quote:
I've tried the new amdgpu driver on my RX460 (4G VRAM), and it seems to work
reasonably. KMS picks up the appropriate console resolution, and X appears to
work. There is some strange behavior with xrandr when setting rotation on one of
my displays (1920x1200->1200x1920) that I don't quite understand; its idea of
the mouse pointer's position seems to be confused. Changing virtual desktop size
by disabling displays outright doesn't seem to cause any problems. I can play
with it more and report further if that information would be helpful. OpenGL
seems to work, but not entirely correctly. I only had time today to test
glxgears (fine) and 0ad (some obvious artifacts, and doesn't quite reach 60fps
at 1920x1200 as it should be able to, presumably has something to do with the
powerplay error visible in dmesg; images available on request. I also see
display corruption in my xterms after exiting, which is resolved by restarting
X). dmesg quickly fills up with stub messages upon starting X, but I assume
that's known. If there's anything I can test on this hardware to assist
development, I'm happy to do so. dmesg without X, post fw_update:
|
|