Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 16 Sep 2020 14:45:56 +0000
From:      bugzilla-noreply@freebsd.org
To:        x11@FreeBSD.org
Subject:   [Bug 249357] graphics/drm-fbsd12.0-kmod: Doesn't work on AMD E-300 (Radeon HD 6310/PALM) laptop
Message-ID:  <bug-249357-7141-78ewyCKX3Z@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-249357-7141@https.bugs.freebsd.org/bugzilla/>
References:  <bug-249357-7141@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D249357

--- Comment #11 from Joshua Kinard <kumba@gentoo.org> ---
(In reply to Niclas Zeising from comment #10)

Laptop is from ~2011, so it doesn't have UEFI, just BIOS.  And it's a dual-=
core
system that's rather slow, so I really plan to stick to binary packaging wh=
ere
possible.  Last I checked, I don't think -CURRENT is doable by basic binary
updates through freebsd-update(8).  buildworld/installworld would be an all=
-day
affair on this machine.

And even if drm-v5.0-fbsd12.1 is broken, the issue I am encountering still
happens, so whatever the cause is, is probably independent of the branch's
current brokenness.  I'd be content at this point to get a more recent
radeonkms.ko to initialize and drop me off at a shell prompt at the laptop's
native resolution (like current drm-legacy-kmod will do).  That would then =
move
the ball back to figuring out why eglInitialize() fails against current
xorg-server.

Are there any debugging switches to radeomkms?  I have some familiarity with
poking around Linux's kernel, but haven't dived deep into FreeBSD's as much=
, so
not as familiar w/ debugging things.  It looks like 'cat /dev/klog' can get=
 me
some kind of usable raw output when loading the driver, up until the screen
does the icing-up effect.

And given I'm on 12.2-BETA1, which branch of kms-drm would be best to
test/debug with?

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-249357-7141-78ewyCKX3Z>