Red Hat Bugzilla – Bug 1031228
Xorg RADEON failed to set drm interface version
Last modified: 2015-02-17 14:15:58 EST
Description of problem:
I just updated my F18 Sony laptop with a ATI Radeon IGP 330M/340M/345M/350M to F19 using fedup --netwok.
It successfully boots, but when I try graphical log in, it hangs with a blank screen.
The Xorg.1.log has the following entry:
[ 354.500] (II) RADEON(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 354.500] (==) RADEON(0): Depth 24, (--) framebuffer bpp 32
[ 354.500] (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
[ 354.500] (==) RADEON(0): Default visual is TrueColor
[ 354.501] (==) RADEON(0): RGB weight 888
[ 354.501] (II) RADEON(0): Using 8 bits per RGB (8 bit DAC)
[ 354.501] (--) RADEON(0): Chipset: "ATI Radeon IGP330M/340M/350M (U2) 4337" (ChipID = 0x4337)
[ 354.501] (EE) RADEON(0): [drm] failed to set drm interface version.
[ 354.501] (EE) RADEON(0): Kernel modesetting setup failed
[ 354.501] (II) UnloadModule: "radeon"
[ 354.501] (EE) Screen(s) found, but none have a usable configuration.
[ 354.501] (EE)
Fatal server error:
[ 354.501] (EE) no screens found(EE)
[ 354.501] (EE)
Please consult the Fedora Project support
lshw for the display yields: product: RS200M [Radeon IGP 330M/340M/345M/350M]
The Xorg.1.log says fatal error, but the Xorg just appears to be hung. I SIGABRTed it to get this core dump to report the problem.
Searching for similar problems on the internet, yields clues that this may be a race condition, in that the drm Radeon driver is not finished initilizing before Xorg tries to use it.
Version-Release number of selected component:
cmdline: /usr/bin/Xorg :0 -background none -verbose -auth /run/gdm/auth-for-gdm-SXBXvI/database -seat seat0 -nolisten tcp vt1
runlevel: N 5
Thread no. 1 (4 frames)
#1 ___newselect_nocancel at ../sysdeps/unix/syscall-template.S:81
#2 WaitForSomething at WaitFor.c:221
#3 Dispatch at dispatch.c:361
Created attachment 824747 [details]
Created attachment 824748 [details]
Created attachment 824749 [details]
Created attachment 824750 [details]
Created attachment 824751 [details]
Created attachment 824752 [details]
Created attachment 824753 [details]
Created attachment 824754 [details]
Created attachment 824755 [details]
Created attachment 824756 [details]
Created attachment 824757 [details]
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
FYI for anyone else. The problem is likely still in future Fedora versions.
I switched from the default gdm to the lightdm display manager to avoid the problem, which seems to be some kind of race or timing condition with gdm. gdm does not appear to unlock the displ card before xorg tries to get it. Hence the no screens error in xorg.log
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.