Playing with radeonhd under F11, which includes updated kernel/drm and X/xrandr. With latest git radeonhd (see logfile for commit string), X and KDE start up, but crash with a backtrace when compiz tries to start. FireGL v5200 on a Thinkpad T60p, so a supposedly supported r5xx chipset (although compositing and GL always have crashed things badly when used together, see for example Bug #18097). Using the radeon instead of radeonhd driver does not crash, so while the crash seems to be coming from DRM, it's certainly being instigated by something we're doing differently than radeon. Attachments: crash.log is stderr/stdout of the startx chain, contains the backtrace. Other spew in that file looks similar if compiz is not started, so scroll down to the trace. Xorg.0.log is with logverbose 7
Created attachment 26848 [details] stdout/stderr from the startx command stdout/stderr from the startx command
Created attachment 26849 [details] X logfile with logverbose 7 X logfile with logverbose 7
I assume F11 already has the new radeon DRI module that supports the new command submission ioctl. In that case it could be a compatibility issue, though the new ioctl should be implemented backwards compatible. Alex, other ideas?
Make sure the radeon drm is not loaded in kms mode when starting radeonhd.
Disabled at the kernel with boot-time parameter nomodeset (from memory, not on that system at the moment). Without it, Fedora's "plymouth" graphical eyecandy boot would lock the machine hard when trying to modeset. Is there an additional radeonhd parameter to try to be double sure?
(In reply to comment #5) > Disabled at the kernel with boot-time parameter nomodeset (from memory, not on > that system at the moment). Without it, Fedora's "plymouth" graphical eyecandy > boot would lock the machine hard when trying to modeset. > > Is there an additional radeonhd parameter to try to be double sure? > Looks like a problem in the 3D driver. Maybe a dupe of bug 21582. Can you try a newer 3D driver?
Does this issue occur with the preferred ati driver (xf86-vide-ati)? If so, please move this to the Driver/Radeon component. Development of radeonhd has pretty much halted and development focus is on the ati driver. Please see http://www.x.org/wiki/radeonhd If the issue does not exist in the ati driver (or if there is no response to this message), this bug will be closed as WONTFIX unless someone contributes a patch.
Closing due to lack of response. Please reopen and move to the Driver/Radeon component if this issue persists with xf86-video-ati
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.