Hello, I have dualhead configuration - ATI Radeon 7000 with 2 attached VGA monitors. new FEDORA 11: But by booting is one of them switched off: - without kernel param. - nomodeset (added to GRUB), the monitor is switched off just before X start - with nomodeset - is switchet off by X start. In X: xrandr reports only 1 attached monitor (second port is reported as "disconnected") - the same info is in /var/log/Xorg.0.log. I have also try to use my elsewhere working predefined configuration in xorg.conf, but also without effect. The second monitor stays off :-(( On every other (older) OS I have ever tried: Ubuntu 8.04/8.10/9.04, Mandriva 2008/2009.1, Knoppix, SuSE 10.3/11.1, Windows XP, .... I had not this problem. Also - what is wrong ? Why do switch the monitor off ? Why reports, that the monitor is disconnected - when it is not true ? Thanks for help.
Please attach your xorg logs both with and without KMS.
Also, you can force the secondary monitor on using xrandr if it's not detected as a workaround.
(In reply to comment #2) > Also, you can force the secondary monitor on using xrandr if it's not detected > as a workaround. > and how ?
(In reply to comment #3) > and how ? > see this page for more info: http://wiki.debian.org/XStrikeForce/HowToRandR12 basically: xrandr --addmode <output> <mode> xrandr --output <output> --mode <mode> the name of the output and mode will depend on your card and monitors e.g., xrandr --addmode VGA-0 1024x768 xrandr --output VGA-0 --mode 1024x768
Created attachment 29157 [details] Xorg-log: without "nomodeset" kernel parm - also normal (default) start
Created attachment 29158 [details] Xorg-log: with "nomodeset" kernel parm
Created attachment 29159 [details] dmesg - normal
Created attachment 29160 [details] dmesg - with "nomodeset"
Created attachment 29161 [details] xrandr - normal
Created attachment 29163 [details] xrandr - with "nomodeset"
Created attachment 29164 [details] xrandr - failed trial to setup mode on disconnected output
Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 2048 x 1200 VGA-1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 300mm x 230mm 1280x1024 60.0* 1024x768 85.0 75.0 60.0 832x624 74.6 800x600 85.1 75.0 60.3 640x480 75.0 63.1 59.9 720x400 70.1 VGA-0 disconnected (normal left inverted right x axis y axis) S-video disconnected (normal left inverted right x axis y axis) Since VGA-0 is showing as disconnected, that is the one you have to force on: xrandr --addmode VGA-0 1280x1024 xrandr --output VGA-0 --mode 1280x1024
(In reply to comment #4) > (In reply to comment #3) > > and how ? > > > > see this page for more info: > http://wiki.debian.org/XStrikeForce/HowToRandR12 > > basically: > xrandr --addmode <output> <mode> > xrandr --output <output> --mode <mode> > > the name of the output and mode will depend on your card and monitors e.g., > xrandr --addmode VGA-0 1024x768 > xrandr --output VGA-0 --mode 1024x768 > Heloo logs added - see attachments And another interesting behavior: !!!! 1. with "nomodeset" - the monitor is switched OFF by X start - and - when I switch to text console (Ctrl+Alt+F2) - the 2. monitor goes ON, and after switching to X console back (Alt+F1) - goes OFF again. 2. After these test with Fedora 11 (at last time with nomodeset) - my up to now working dualhead on Ubuntu 9.04 was broken in the same way, like in Fedora 11 with nomodeset - also 2. monitor was switched of by X start !!! Also after hardcore reset. Also after running Windows XP (here dualhead has working normal - OK) Also after 2. reset. ... I was in PANIC ... Last chance: I turned the computer off and unplug from power line. ... ufff .... now is my dualhead in Ubuntu working again. ???? It seems, that Xorg or kernel in Fedora 11 did something "evil" with my Radeon card, something in his intern HW configuration - something what persist reset but not power off. Interesting, isn't it ?
(In reply to comment #12) > Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 2048 x 1200 > VGA-1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 300mm > x 230mm > 1280x1024 60.0* > 1024x768 85.0 75.0 60.0 > 832x624 74.6 > 800x600 85.1 75.0 60.3 > 640x480 75.0 63.1 59.9 > 720x400 70.1 > VGA-0 disconnected (normal left inverted right x axis y axis) > S-video disconnected (normal left inverted right x axis y axis) > > Since VGA-0 is showing as disconnected, that is the one you have to force on: > > xrandr --addmode VGA-0 1280x1024 > xrandr --output VGA-0 --mode 1280x1024 > With the --addmode ... I will try it and report... See also my last comment - I'm little afraid of make the test ?:-(
(In reply to comment #14) > > With the --addmode ... > > I will try it and report... > See also my last comment - I'm little afraid of make the test ?:-( > I have try it. IT REALLY WORKS. GREAT. Thank You very much ! Interesting is: 1. after reboot from (working) U9.04 in Fedora 11 with "nomodeset" - first time ever: both monitors were ON - probably from HW setting from Ubuntu ?! 2. with "nomodeset" - the 2. monitor was switched off like usual. But with Yours xrandr --addmode ... it comes up :-) The dualhead is now working. ?? Also after --admode and switching On, xrander reports this output like disconnected: <code> [liveuser@localhost ~]$ xrandr Screen 0: minimum 320 x 200, current 2048 x 768, maximum 4096 x 4096 VGA-0 connected 1024x768+1024+0 (normal left inverted right x axis y axis) 300mm x 230mm 1024x768 75.1* 60.0 832x624 74.6 800x600 75.0 60.3 640x480 75.0 60.0 720x400 70.1 0x0 0.0 VGA-1 disconnected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1024x768 75.1* [liveuser@localhost ~]$ </code> 3. After switching to "text" console and back, the monitor goes OFF again. To switch it ON is necessary to first switch it off with xrand: - xrandr --output VGA-1 --off and only then --output VGA-1 --mode 1024x768 4. The names of outputs are contrariwise ?! I hope, that this behaviour (especially switching off) will be changed. Once again - thank You. P.S. - How to set mode (resolution, ...) - and dualhead on startup ? - With kernel mode setting ?
(In reply to comment #15) > I have try it. > > IT REALLY WORKS. GREAT. Thank You very much ! > Excellent. > Interesting is: > > 1. after reboot from (working) U9.04 in Fedora 11 with "nomodeset" - first time > ever: both monitors were ON - probably from HW setting from Ubuntu ?! > 2. with "nomodeset" - the 2. monitor was switched off like usual. But with > Yours xrandr --addmode ... it comes up :-) The dualhead is now working. > > ?? Also after --admode and switching On, xrander reports this output like > disconnected: disconnected just means the driver wasn't able to detect a monitor on that port. you might try swapping the cables. Also, if the problematic monitor uses the secondary dac, you can try: Option "TVDACLoadDetect" "TRUE" for the nomodeset case. Another option is force the output on in your xorg.conf. See the page I posted in comment 4. You'll basically want to add a monitor section with the same identifier as the output name and with the sync ranges for your monitor and: Option "Enable" "TRUE" > > 3. After switching to "text" console and back, the monitor goes OFF again. To > switch it ON is necessary to first switch it off with xrand: > > - xrandr --output VGA-1 --off and only then --output VGA-1 --mode > 1024x768 > > 4. The names of outputs are contrariwise ?! > Are you saying VGA-0 and VGA-1 switch after a VT switch? That shouldn't happen. Is this with nomodeset or modeset? > > > P.S. > - How to set mode (resolution, ...) > - and dualhead on startup ? > - With kernel mode setting ? using xrandr. read the guide I posted in comment 4. once you have both outputs on: xrandr --output VGA-0 --right-of VGA-1 for example. If you are using nomodeset, you'll have to specify a virtual screen large enough for both heads. in the kms case, the driver will take care of it automatically.
(In reply to comment #16) Hello > > disconnected just means the driver wasn't able to detect a monitor on that > port. you might try swapping the cables. Also, if the problematic monitor > uses the secondary dac, you can try: > Option "TVDACLoadDetect" "TRUE" > for the nomodeset case. > Another option is force the output on in your xorg.conf. See the page I posted > in comment 4. You'll basically want to add a monitor section with the same > identifier as the output name and with the sync ranges for your monitor and: > Option "Enable" "TRUE" > Thank You - I will try it. But why Xorg in Ubuntu can detect the connected monitors and the (newer) in Fedora don't ? > > Are you saying VGA-0 and VGA-1 switch after a VT switch? That shouldn't > happen. Is this with nomodeset or modeset? > No, the output names VGA-0 VGA-1 are contrariwise in Ubuntu X Fedora. I had take note of this in F11 without nomodeset, when the (only) 1 monitor (which is known as VGA-1 in Ubuntu) was reported in Fedora like VGA-0 > > P.S. > > - How to set mode (resolution, ...) > > - and dualhead on startup ? > > - With kernel mode setting ? > > using xrandr. read the guide I posted in comment 4. once you have both outputs > on: > xrandr --output VGA-0 --right-of VGA-1 > for example. If you are using nomodeset, you'll have to specify a virtual > screen large enough for both heads. in the kms case, the driver will take care > of it automatically. > Of course - I use xrandr. I did mean something else with "startup" - when kernel boots. I have thing, that in future xrandr will be obsolete and kernel takes the mode/dualhed setting job. Also e.g. how to set the graph. mode (like with vga=791 in past) with KMS ? BTW - I have try set mode on "text" console with fbset -v 640x480-60, but the screen was damaged and after try to switch to X console, the system (or maybe just keyboard/screen) hang. Is there some another tool to ask kernel to change video mode ? Or old procedures (like vga=..., fbset, xrandr, ...) have just new "internals" - calling kernel KMS routines ?
Created attachment 29209 [details] FYI: my good old (working) xorg.con from Ubuntu 9.04
Is this still an issue with a newer driver/kernel?
Sorry - I can't test it more - I have another comp now.
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.