This is likely a duplicate of #168561 and maybe of #168562; I'm filing this separately because it is easier to close as duplicate than to separate information. The X server seems to start, but screen contents are garbage, and it doesn't react even to Ctrl+Alt+Backspace Version-Release number of selected component (if applicable): xorg-x22-6.8.2-37.FC4.48.1
Created attachment 118932 [details] Server log from ...48.1
Created attachment 118933 [details] Server log from ...45 (working)
Created attachment 118938 [details] Xorg.0.log from broken version of xorg-x11
Same problem with i830 video chipset. In dmesg I see the following carnage: mtrr: base(0xe8020000) is not aligned on a size(0x300000) boundary agpgart: pg_start == 0x00000000,intel_i830_private.gtt_entries == 0x000007df agpgart: Trying to insert into local/stolen memory
Created attachment 118940 [details] Diffs from Xorg.0.log 6.8.1 (working) to 6.8.2 (not working) I have the same problem with xorg-x11-6.8.2-1.FC3.45 on FC3 with an Intel 915 on-board video card.
I have the same card(855GM), and same problem. Temporarily sidestepped problem by using vesa driver.
Same problem on FC3 after upgrade from xorg-x11-6.8.2-1.FC3.13 to xorg-x11-6.8.2-1.FC3.45 w/ 855GME in hp dv1000 notebook. Same failure mode as reported. Corrupt screen, failure to revert to text-mode. Xorg.0.log ends with: (WW) I810(0): Extended BIOS function 0x5f05 failed. (II) I810(0): xf86BindGARTMemory: bind key 8 at 0x00000000 (pgoffset 0) (WW) I810(0): xf86BindGARTMemory: binding of gart memory with key 8 at offset 0x0 failed (Invalid argument) Fatal server error: AddScreen/ScreenInit failed for driver 0 Downgrading all xorg packages back to .13 thankfully wasn't too difficult.
Just wanted to drop in a 'same here' on i830 chipset...
Bug 168622 and bug 168623 are also probably duplicates of this.
Intel 845 using i810 driver as well
Same problem on a Thinkpad with i855 chipset, after updating FC4 from the previous Xorg packages. Using the vesa X driver instead of the default i810 driver enables X to run successfully. The error in the log is identical to comment 7.
vesa X driver does not work with Intel 845
Intel i810 on a Presario 2210US running Fedora Core 4. I did a `yum -y update` last night which consisted mainly of xorg, next reboot failed to display anything comprehendable. I tried different kernel versions, same thing.
This thing scared the hell out of me today! Inter 830M chipset on Fujitsu C7651 laptop --from Xorg.0.log.old with xorg-x11-6.8.2-37.FC4.48.1-- (II) I810(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000 (WW) I810(0): Extended BIOS function 0x5f05 failed. (II) I810(0): xf86BindGARTMemory: bind key 7 at 0x00000000 (pgoffset 0) (WW) I810(0): xf86BindGARTMemory: binding of gart memory with key 7 at offset 0x0 failed (Invalid argument) ---end---- <a href="http://konstantin.antselovich.com/downloads/bug168564/Xorg.0.log">Full working log from xorg-x11-6.8.2-31</a> <a href="http://konstantin.antselovich.com/downloads/bug168564/Xorg.0.log.old">Full X crash log from xorg-x11-6.8.2-37.FC4.48.1</a>
---- Sep 18 16:41:04 lifebook kernel: mtrr: base(0xe8020000) is not aligned on a size(0x300000) boundary Sep 18 16:41:07 lifebook kernel: agpgart: Trying to insert into local/stolen memory Sep 18 16:41:08 lifebook gdm[3992]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 ----
Take that damn xorg update down - it has blown up my Dell, HP and Compaq systems.
(In reply to comment #16) > Take that damn xorg update down - it has blown up my Dell, HP and Compaq systems. I had to boot to single user mode with Grub and change my inittab setting to 3 so it would not boot into X - X is just garbage and it locked up all three systems so like windoze I could only power off - ctl-alt-F1 would not work and ctl-alt-backspace would not work, so it was no suprise ctl-alt-delete was also dead. I will not touch my production boxes until I can get these test boxes working.
Seen here too. This blew away X on my i855 notebook. Everything apart from the display worked, so Ctrl+Alt+Del restarted the machine cleanly. Rolled back to the last updates of packages xorg-x11, xorg-x11-devel, xorg-x11-xfs and xorg-x11-libs (version 6.8.2-37.FC4.45).
*** This bug has been marked as a duplicate of 168752 ***