/dev/dri devices are absent after recent update (intel card)

Bug #430876 reported by ilna
46
This bug affects 9 people
Affects Status Importance Assigned to Milestone
libdrm (Ubuntu)
Confirmed
Undecided
Unassigned
Nominated for Karmic by FriedChicken

Bug Description

Up to date Kubuntu Karmic is in use. After recent night ad day updates (with that big noise around upstart) /dev/dri devices are no longer found at X boot. X11 log fragment:

...
(II) Module "ramdac" already built-in
drmOpenDevice: node name is /dev/dri/card0
drmOpenByBusid: Searching for BusID pci:0000:00:02.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card1
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card2
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card3
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card4
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card5
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card6
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card7
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card8
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card9
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card10
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card11
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card12
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card13
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card14
drmOpenByBusid: drmOpenMinor returns -1
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: node name is /dev/dri/card1
drmOpenDevice: node name is /dev/dri/card2
drmOpenDevice: node name is /dev/dri/card3
drmOpenDevice: node name is /dev/dri/card4
drmOpenDevice: node name is /dev/dri/card5
drmOpenDevice: node name is /dev/dri/card6
drmOpenDevice: node name is /dev/dri/card7
drmOpenDevice: node name is /dev/dri/card8
drmOpenDevice: node name is /dev/dri/card9
drmOpenDevice: node name is /dev/dri/card10
drmOpenDevice: node name is /dev/dri/card11
drmOpenDevice: node name is /dev/dri/card12
drmOpenDevice: node name is /dev/dri/card13
drmOpenDevice: node name is /dev/dri/card14
(EE) intel(0): [drm] Failed to open DRM device for : No such file or directory
(EE) intel(0): Failed to become DRM master.
(**) intel(0): Depth 24, (--) framebuffer bpp 32
(==) intel(0): RGB weight 888
(==) intel(0): Default visual is TrueColor
(II) intel(0): Integrated Graphics Chipset: Intel(R) 965G
(--) intel(0): Chipset: "965G"
(--) intel(0): Linear framebuffer at 0xD0000000
(--) intel(0): IO registers at addr 0xFFA00000 size 1048576
...

Revision history for this message
ilna (a-gaydenko) wrote :

It seems like a workaround is to reinstall drm-related packages. The same reinstallation has (shortly, at some moment) helped during long fight with that massive upstart-and-around updates. Have no an idea which concrete package update is a cause of the issue.

Revision history for this message
FriedChicken (domlyons) wrote :

Reinstalling libdrm-intel1 and libdrm2 solved/worked-around this for me, too.

Revision history for this message
arky (arky) wrote :

Assigning to libdrm. Looks like a transitional problem, seems to be fixed.

affects: ubuntu → libdrm (Ubuntu)
Revision history for this message
ilna (a-gaydenko) wrote :

After today upgrade I was forced reinstall drm again - there was the only (I think) reason responsible for the issue, and it is initsrcipts/sysv package group.

Revision history for this message
Bryce Harrington (bryce) wrote :

Hi a-gaydenko,

Please attach the output of `lspci -vvnn` and `dmesg`, and attach your /var/log/Xorg.0.log (and maybe Xorg.0.log.old) file from after reproducing this issue. If you're using a custom /etc/X11/xorg.conf please attach that as well.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-xorglog
tags: added: needs-lspci-vvnn
Changed in libdrm (Ubuntu):
status: New → Incomplete
Revision history for this message
ilna (a-gaydenko) wrote :
Revision history for this message
ilna (a-gaydenko) wrote :
Revision history for this message
ilna (a-gaydenko) wrote :

Have attached lspci and dmesg outs. Unfortunately I have not "bad: X11 log at the moment (old one is also "good"). But I guess it isn't needed at all: the problem takes place just at those state when 'ls /dev/dri/' finds nothing - it isn't needed to start X at all, and, in fact, I boot in console (kdm is removed from rc.X's) and check the situation this way.

Revision history for this message
Jared Klingenberger (itsjareds) wrote :

I have this problem as well, and I believe the main problem is that my /dev/dri/card0 is placed in /dev.

Revision history for this message
Jared Klingenberger (itsjareds) wrote :

Note: I tried reinstalling libdrm-intel1 and libdrm2, as ilna said, through Synaptic, then rebooted, but did not fix the issue for me.

Revision history for this message
Daniel Swarbrick (pressureman) wrote :

This is still occurring periodically on my system. I also tried re-installing libdrm-intel1 and libdrm2.

Revision history for this message
Jared Klingenberger (itsjareds) wrote :

If anyone's got a /dev/card0 but no /dev/dri/card0, you can use this workaround until the developers truly fix it:

http://ubuntuforums.org/showpost.php?p=8018573&postcount=2

Revision history for this message
Arnaud (arnaud-oss) wrote :

Today I hit this problem for the 3rd time (kubuntu karmic, fresh install using kubuntu alternate CD of alpha 6, intel 915 gfx card).

Reinstalling everything libdrm related did not fix the problem.

First an observation, then my workaround.

Observation:
The first symptom of this problem is not the content of the X log file, it is the boot splash which is displayed in a much lower resolution.

So this made me think that the problem was happening very early during the boot process. This lead me to the following workaround:
sudo update-initramfs -k all -u
sudo update-grub2
"sudo reboot"

which always fixed the problem.

It would be great to know what information I should gather the next time this happens, so that the problem could be tracked down...

Changed in libdrm (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Anton¡o Sch¡fano (skiantoz) wrote :

I have the same problem on my EEEPC 1000HD.
I experienced the following boot sequence:
- Good boot
- Bad boot (after no install, no config changes)
- Bad boot (after a power-off)
- Good boot (after boot to Windows XP + reboot)
I think this points to some hardware initialization issue (BIOS or kernel?)

Revision history for this message
Anton¡o Sch¡fano (skiantoz) wrote :

When the problem shows up, in my dmesg there is an error in the initialization of the agpgart module, in function drm_fill_in_dev.
In this case the console does not switch to color framebuffer mode and the dri entries in /dev are not created.

Revision history for this message
Anton¡o Sch¡fano (skiantoz) wrote :

Here is the dmesg when everything works.
The two dmesgs have been taken after two consecutive boots, with no actions in-between.

Maybe this is a duplicate of bug 430694? Too sleepy now to check :)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.