Description of problem: Symptom of the problem is that screen of a Daewoo 1509B monitor connected to a Intel 82845 just gets blank and power led blinks with configuration generated by anaconda (xorg.conf.fc6, Xorg.0.log.fc6-fc6). The same applies for no configuration file, and also for one generated by X -configure. I've also run rPath Linux 1.0.5 (which is, I believe, derived from FC5), and there things work fine. It has XOrg 6.8.2, and there everything worked (Xorg.0.log.rpath-rpath) with anaconda-generated configuration (xorg.conf.rpath). The same configuration did not work in FC6 (Xorg.0.log.rpath-fc6). Also, the configuration generated by FC6 anaconda did not work in rPath (Xorg.0.log.fc6-rpath). Version-Release number of selected component (if applicable): Although the log files are not from latest update, the same thing happens with everything updated. Additional info: Everything here applies for "1024x768" resolution. When I add Mode "800x600" to SubSection "Display", things work also in FC6. BPP seem not to make any difference.
What is in FC6 log and not in rPath one: No idea what's this: (WW) I810(0): Extended BIOS function 0x5f05 failed. (II) I810(0): BIOS call 0x5f05 not supported, setting refresh with VBE 3 method. This is certainly incorrect: (==) I810(0): VideoRAM: 65536 kByte rPath's x11 reported correctly: (==) I810(0): VideoRAM: 32768 kByte No idea, either. (WW) EDID preferred timing clock 94.50MHz exceeds claimed max 90MHz, fixing Whis is weird. I do not have that much video memory: (II) I810(0): Allocated 52992 kB for textures at 0x620000 Versus old x11: (II) I810(0): Allocated 32 kB for the logical context at 0x73f8000. And here... Certainly not right too. IRQ 177... (II) I810(0): [drm] Initialized kernel agp heap manager, 54263808 (II) I810(0): [drm] dma control initialized, using IRQ 177 versus (II) I810(0): [drm] dma control initialized, using IRQ 5 (II) I810(0): [drm] Initialized kernel agp heap manager, 21757952
I lied. rPath is not derived from FC5. And FC5's 7.0.0 also has the bug.
Two more things: The smolt profile of the machine is here: http://smolt.fedoraproject.org/show?UUID=548e727f-f164-4e32-8e91-c194a060ddc0 When using "intel" driver instead of "i810" nothing changes, the amount ov VideoRAM detected by the X11 server is still incorrect (64M).
After I updated the machine's firmware, X11 server no longer complains about invalid V_BIOS checksum, as can be seen in the attached logs. Nothing else changed.
Created attachment 153738 [details] Differencies between the logs of old and updated i810 driver The problem doesn't appear in xorg-x11-6.8.2-31.FC4, but it does in xorg-x11-6.8.2-37.FC4.49.4. The difference that is suspect to be guilty is the patch xorg-x11-6.8.2-add-i945-support.patch. I attach the differencies between the logs of the two.
Hi, Lubomir, could we get full /var/log/Xorg.*.log and /etc/X11/xorg.conf, please?
Created attachment 154012 [details] Config files and logs from i810 on FC4 and FC6 Sure. Pardon me for not providing those before, I have even collected and packed them, but forgot to attach. In the tarball attached, "rPath" basically corresponds to FC4 without the patch.
Created attachment 155560 [details] Xorg.0.log from FC6
Created attachment 155561 [details] Xorg.0.log from FC4
Created attachment 155562 [details] Xorg.0.log.rpath-fc6
Created attachment 155563 [details] Xorg.0.log.rpath-rpath
Created attachment 155564 [details] xorg.conf.fc6
Created attachment 155565 [details] xorg.conf.rpath
Section "Device" Identifier "Videocard0" Driver "i810" Option "NoDDC" EndSection Section "Monitor" Identifier "Monitor0" VertRefresh 56 - 75 HorizSync 30 - 69 EndSection Fixed that then (NoDCC was needed). The problem was only with that particular monitor, that I'll send for a recyclation in a week or so :)
OK, so should I close this as INSUFFICIENT_DATA?
Works alright with rawhide.