Bug 374901
Description
James Antill
2007-11-10 18:04:08 UTC
Created attachment 254011 [details]
Xorg config.
Can we get /var/log/Xorg.0.log as well, please? It's gone now, so it'll take a while before I can regenerate the problem (this is my main desktop). However off hand I remember it complained about the PCI ids. From the current Fed-7 Xorg log: (--) PCI:*(1:0:0) ATI Technologies Inc RV370 [Sapphire X550 Silent] rev 0, Mem @ 0xd0000000/28, 0xe0210000/16, I/O @ 0x2000/8, BIOS @ 0xfffe0000/17 (--) PCI: (1:0:1) ATI Technologies Inc RV370 secondary [Sapphire X550 Silent] rev 0, Mem @ 0xe0200000/16 ...in the Fed-8 one, IIRC, the first line was still there but the second one failed with "cannot use PCI 1:0:1, already in use" or something like that. OK, waiting on that log file. If I won't get any message from you in a month, I will close down this bug. OK? Created attachment 257311 [details]
/etc/X11/xorg.conf - nonfunctional dual-head configuration
Created attachment 257321 [details]
/var/log/Xorg.0.log - output with errors from nonfunctional dual-head config
Oops - sorry, first time logging a bugzilla. I accidentally added the xorg.conf and Xorg.0.log files first. This problem sounds very similar to one that I am experiencing - system-config-display does not produce a functional xorg.conf for a dual-monitor configuration. I'm running F8 with a Radeon RV100 on a 32-bit x86 machine. Here is the output of lspci from my system: 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE] (prog-if 00 [VGA]) Subsystem: ATI Technologies Inc Unknown device 1b8a Flags: stepping, 66MHz, medium devsel, IRQ 17 Memory at f0000000 (32-bit, prefetchable) [size=128M] I/O ports at ec00 [size=256] Memory at ff8f0000 (32-bit, non-prefetchable) [size=64K] Expansion ROM at ff800000 [disabled] [size=128K] Capabilities: [58] AGP version 2.0 Capabilities: [50] Power Management version 2 I will attach the non-working dual-head /etc/X11/xorg.conf file as well as /var/log/Xorg.0.log. Thanks in advance for your help! That looks like the same issue, as I tried without a BusID or Screen option too (output of system-config-display) and it still didn't work. Currently I'm specifying both Screen (0) and BusID (identical to the other device section) ... with the Fed-7 driver, which gave the slightly different error message. I have the same problem with xorg-x11-drv-ati-6.7.195-3.fc8 and RV280 [Radeon 9200] on i386 machine. File Xorg.0.log ends with "Requested Entity already in use!" too. Older xorg-x11-drv-ati-6.6.3-4.fc7 works fine. I'm using the same xorg.conf as in F7. Created attachment 261071 [details]
my one and only xorg.conf with polished device options
Created attachment 261081 [details]
Xorg.0.log with xorg-x11-drv-ati-6.7.195-3.fc8 (error)
Created attachment 261091 [details]
Xorg.0.log with xorg-x11-drv-ati-6.6.3-4.fc7 (ok)
Created attachment 272351 [details]
Xorg.0.log with xorg-x11-drv-ati-6.7.196-1.fc8 (error)
the error remains with latest update
I just tried the latest in updates-testing: xorg-x11-drv-ati.x86_64 6.7.196-5.fc8 ...this one booted up with dual head, and seemed like it might work ... but as soon as I logged in Xorg crashed after starting some of the session. Also, when I did C-A-F1 to reinstall the older rpm again, it locked the Video card up. So getting closer :). Could we get /var/log/Xorg.0.log again, please? Agree with #14. It started, but init 3 or reboot freezes system. On my dual head 1600x1200 and 1280x1024 it looks like there is memory sharing issue. On second (smaller) head mouse pointer shows as bigger white-blue stripped box while on first head appears a few black horizontal lines with white dots (probably arrow) near bottom of the screen. Still unusable. Created attachment 290820 [details]
Xorg.0.log with xorg-x11-drv-ati-6.7.196-5.fc8 (memory issue?)
James? I assume you want the non-working Xorg.0.log? I haven't updated/rebooted into xorg-x11-drv-ati-6.7.196-5.fc8.x86_64 yet. I should get to it tomorrow, or the weekend. If you just want an older working one, I can do that today. Hi, I can confirm this bug for i386, too. Was using Fedora 7 since yesterday in working dualhead configuration, updated to 8 and had a cloned display after that. Fiddling around in config brought me no success. Seems the new drivers does not support Xinerama any more - a notice says one should use RandR for this - but the RandR extension is not loaded by default and can not be configured in xorg.conf afaik. I turned by xorg-x11-drv-ati package back to the fc7 version (from updates), which worked fine. Regards, Ingo Ok, moving to Fed-9 as this has basically gotten much worse now as the old f7 drv-ati isn't compatible with the new X server in Fed-9. Now it _mostly_ seems to work, I get two screens however something seems to think the screens are bigger than they are. From my working Fed-8 (using xorg-x11-drv-ati.x86_64) xdpyinfo says: screen #0: dimensions: 2560x1024 pixels (748x302 millimeters) resolution: 87x86 dots per inch depths (7): 24, 1, 4, 8, 15, 16, 32 ...on the Fed-9 machine I get: screen #0: dimensions: 2800x1200 pixels (764x302 millimeters) resolution: 93x101 dots per inch depths (7): 24, 1, 4, 8, 15, 16, 32 ...which predictably gives me one of those an annoying HW virtual desktop. Hopefully the last tweak needed to completely fix this is easy now. In case it matters: Installed Packages xorg-x11-apps.x86_64 7.3-3.fc9 installed xorg-x11-drivers.x86_64 7.3-4.fc9 installed [...] xorg-x11-drv-ati.x86_64 6.8.0-14.fc9 installed [...] xorg-x11-filesystem.noarch 7.3-1.fc9 installed xorg-x11-font-utils.x86_64 1:7.2-4.fc9 installed [...] xorg-x11-server-Xorg.x86_64 1.4.99.905-1.20080701. installed xorg-x11-server-common.x86_64 1.4.99.905-1.20080701. installed xorg-x11-server-utils.x86_64 7.4-1.fc9 installed [...] xorg-x11-utils.x86_64 7.4-1.fc9 installed [...] Created attachment 311455 [details]
current xorg.conf with dual head - manually edited
I've attached my xorg.conf which I edited after generating it with system-config-display in Fedora 9. Now I don't get this annoying too big virtual desktop anymore. But the fedora tools should definately create a usable dual head configuration! Confirmed that manually putting the "Virtual" line in to match your highest mode makes it all happy. I guess we can close this now, as unusably hard to configure is kind of a known bug, I guess :). Please reopen the bug and assign it to system-config-display. Reason: The tools to configure the display resolution should generate configuration files that match this configuration. And not adding the "Virtual"-lines for the current mode means not to generate the configuration the user requested. As a side-note: system-config-display is not able to parse this configuration. gnome-display-properties crashes. It might be worth opening a new BZ, but it doesn't seem right to overload this one for that purpose ... this one was about the fact X would crash in dual head mode, and that is now fixed in Fed-9. It's also worth nothing that, for me in Fed-9, system-config-display refuses to output anything at all for dual head mode. Clicking the OK button didn't do anything unless you de-selected dual head mode ... also when I first used dual head mode, system-config-display was similarly non-functional. So this isn't a new/recent problem. |