Hi!
I've come across a problem with drm-core.
When a drm device is opened by the X server, it opens the first drm device that does not have a busid assigned to it, since that means it is busy. It then assigns a busid to that device.
Now, if the server is exited and restarted, the server cannot find a an available device with no bus-id assigned to it and falls back to the old /proc interface:
drmOpenByBusid: busid is PCI:1:0:0
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenByBusid: drmOpenMinor returns 7
drmOpenByBusid: drmGetBusid reports PCI:1:0:0
(II) VIA(0): [drm] drmSetBusid failed (7, PCI:1:0:0), Device or resource busy
(EE) VIA(0): [dri] DRIScreenInit failed. Disabling DRI.
/Thomas
------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
