Summary: | DisplayLink: Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices | ||
---|---|---|---|
Product: | xorg | Reporter: | Nathan Typanski <M8R-mnncd5> |
Component: | Driver/fbdev | Assignee: | Xorg Project Team <xorg-team> |
Status: | RESOLVED MOVED | QA Contact: | Xorg Project Team <xorg-team> |
Severity: | normal | ||
Priority: | medium | CC: | evk02, lance, leho, versalismeisteralis |
Version: | 7.7 (2012.06) | ||
Hardware: | x86-64 (AMD64) | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Nathan Typanski
2013-06-05 02:21:54 UTC
I was able to confirm with various similar configurations. A displaylink fbdev device can not co-exist in the same x session with other devices. I read that KMS might be an issue. I experimented with disabled KMS via kernel parameter which got some different but still broken results. I also experimented with attempting to pair the displaylink device with other devices using different drivers with identical results. Changing Xinerama on/off also had no effect on any result. Below "non-displaylink device" was substituted with intel,radeon, and fbdev devices. With KMS enabled and both screens enabled: X dies with "Please specify busIDs for all framebuffer devices" error With KMS disabled and both screens enabled: X starts but displays only on non-displaylink device With KMS disabled or enabled and only displaylink screen enabled: X starts and displaylink device works as expected With KMS disabled or enabled and only non-displaylink screen enabled: X starts and non-displaylink device works as expected Here is my config: ------ Section "Device" Identifier "DisplayLinkDevice" Driver "fbdev" BusID "USB" Option "fbdev" "/dev/fb0" EndSection Section "Monitor" Identifier "DisplayLinkMonitor" EndSection Section "Screen" Identifier "DisplayLinkScreen" Device "DisplayLinkDevice" Monitor "Monitor0" DefaultDepth 16 EndSection Section "Device" Identifier "InternalDevice1" Driver "radeon" BusID "PCI:1:0:0" #Driver "intel" #BusID "PCI:0:2:0" #Driver "fbdev" #Option "fbdev" "/dev/fb0" EndSection Section "Monitor" Identifier "InternalMonitor1" EndSection Section "Screen" Identifier "InternalScreen1" Device "InternalDevice1" Monitor "Monitor1" EndSection Section "ServerLayout" Identifier "Screen Layout" #Screen 0 "DisplayLinkScreen" 0 0 Screen 1 "InternalScreen1" LeftOf "DisplayLinkScreen" Option "Xinerama" "On" EndSection Sorry, Monitor1 should of been InternalMonitor1. Attempted to re-label things for clarity post-testing. I came to raise the very same bug and I found this already raised. I can confirm I experience the same bug using kernel 3.10 The same problem exists when using the modesetting driver (i.e. xf86-video-modesetting, as opposed to xf86-video-fbdev) with udldrmfb from a linux 3.15 kernel. xorg-server version is 1.12.4, xf86-video-modesetting version is 0.3.0. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video-fbdev/issues/3. |
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.