vdev icon indicating copy to clipboard operation
vdev copied to clipboard

Re-scan /sys until no new devices are found

Open jcnelson opened this issue 10 years ago • 5 comments

Vdevd needs to re-walk /sys/devices until no new devices are found. This is because handling a sysfs device tree can have the side-effect of creating more device trees in directories vdevd already handled.

jcnelson avatar Nov 01 '15 23:11 jcnelson

On boot, my X tries to start before /dev/dri exists...is this the same issue, or should I start a new one?

Jamessall avatar Nov 29 '15 01:11 Jamessall

Does /dev/dri come into existence after X starts, or does it never show up? If /dev/dri isn't showing up, it could be because the module never gets loaded (which this issue is tracking). If you ensure that your video drivers are loaded before vdevd starts, does /dev/dri show up?

jcnelson avatar Nov 30 '15 04:11 jcnelson

The Xorg log says that /dev/dri/card0 does not exist. But when I look, /dev/dri/card0 does exist. I then have to start X manually on every boot, which works. This happens on two different laptops, both with integrated intel gpu's and both running devuan-jessie.

If you ensure that your video drivers are loaded before vdevd starts, does /dev/dri show up?

Not sure how to do that.../etc/modules?

Jamessall avatar Nov 30 '15 13:11 Jamessall

@jimyyz It looks like vdevd is creating /dev/dri, if it shows up in ls. Can you verify that the X server has read/write access to /dev/dri/card0, and the parent directories?

jcnelson avatar Dec 01 '15 07:12 jcnelson

By the time I can look, the device exists with read/write access, so manually starting X works with no fixing of permissions.

Jamessall avatar Dec 02 '15 15:12 Jamessall