Fedora Account System
Red Hat Associate
Red Hat Customer
Created attachment 646005 [details] xorg.conf used to try to start MIMO screen Description of problem: When I try to start a second X session on a MIMO UM-720F DisplayLink USB touchpad monitor, it repeatedly (and immediately) panics the kernel. Version-Release number of selected component (if applicable): Reproduced on: kernel-3.6.6-3.fc18.x86_64 kernel-3.7.0-0.rc5.git1.3.fc19.x86_64 How reproducible: Always Steps to Reproduce: 1. Connect MIMO monitor to USB port, confirm that udl loads and /dev/fd1 is assigned. 2. Run: sudo xinit xclock -- :3 -config /home/spot/xorg.conf.DL -configdir -sharevts 3. Panic. Actual results: Panic. No change on the MIMO display. Expected results: xclock running on the MIMO display Additional info: xorg.conf.DL attached. kernel panic on 3.6.6-3.fc18 hand-transcribed and attached.
Created attachment 646006 [details] kernel panic (hand transcribed from pictures)
(In reply to comment #1) > Created attachment 646006 [details] > kernel panic (hand transcribed from pictures) I get the same results with a SIIG displaylink adapter that I had working well in F16. 3.7.1-2.fc18 produces kernel panic when trying to launch 2nd X using the fbdev driver. Adapter is useless in F18.
don't use fbdev use the modesetting driver.
Using the modesetting driver starts X, but the screen keeps getting deleted, thus nothing is displayed on the displaylink monitor. I will attach log and config.
Created attachment 674236 [details] xorg log using modesetting driver
Created attachment 674237 [details] xorg.conf using modesetting driver
anything in dmesg when this happens? it sounds like USB is removing the device maybe.
no additional information in dmesg.
I should also note that using krandr to attempt to extend to the primary X session to the displaylink adapter seems to work (as in no crashes and the monitor will show power), but only a black screen is present.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 18 kernel bugs. Fedora 18 has now been rebased to 3.11.4-101.fc18. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 19, and are still experiencing this issue, please change the version to Fedora 19. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. It has been over a month since we asked you to test the 3.11 kernel updates and let us know if your issue has been resolved or is still a problem. When this happened, the bug was set to needinfo. Because the needinfo is still set, we assume either this is no longer a problem, or you cannot provide additional information to help us resolve the issue. As a result we are closing with insufficient data. If this is still a problem, we apologize, feel free to reopen the bug and provide more information so that we can work towards a resolution If you experience different issues, please open a new bug report for those.