all PCI values below are taken from http://yourvote.com/pci database.
> /var/log/XFree86.0.log: > > XFree86 Version 4.3.0 > (II) PCI: PCI scan (all values are in hex) > (II) PCI: 00:00:0: chip 1002,cab2 card 0000,0000 rev 02 class 06,00,00 > hdr 00 ATI IGP 340M host bridge > (II) PCI: 00:01:0: chip 1002,7010 card 0000,0000 rev 00 class 06,04,00 > hdr 01 ATI RS200 PCI to AGP bridge > (II) PCI: 01:05:0: chip 1002,4337 card 0e11,0056 rev 00 class 03,00,00 > hdr 00 ATI RS200M Mobility M6 (U2) laptop typcial chipset > (II) Primary Device is: PCI 01:05:0 > (**) ChipID override: 0x514C > (**) Chipset ATI Radeon 8500 QL (AGP) found Boy, you are using overrides - telling the driver that it should see something it knows which is not present at all in your system. You will better take one of the latest snapshots from XF86 or the DRI people and retry than trying things that will surely crash. > (WW) RADEON(0): Failed to set up write-combining range > (0x8000000,0x2000000) I think your CPU is our of MTRR resources our your Linux kernel does have some coding flaw for MTRR. > (EE) RADEON(0): Idle timed out, resetting engine... The engine got some bogus data, possibly from AGP range. Alternatively the programmed and/or checked bits do not at all match what the driver wants them to be. Use latest drivers. the RS200 was not supported in the last XF86 release since those chipset is newer or at least Linux coding for that was not there at this time. > /etc/X11/XF86CONFIG: its XF86Config or rather XF86Config-4. > Section "Device" > Identifier "VESA Framebuffer" > Driver "radeon" > ChipID 0x514c > VideoRam 32768 > #Option "AGPMode" "4" > MemBase 0x8000000 # physical address of the linear framebuffer > #IOBase 0xf0300000 # physical address of the MMIO registers > BusID "PCI:1:05:0" > EndSection Forget about all those overrides, those were merely for ISA boards which did not expose full autoconfiguration and autodetection. PCI/AGP boards do nicely autodetect if they are supported. The sole purpose of the ChipID override for PCI boards is the fact that some newer chipset IDs are mostly compatible with former designs. You already failed that with the stock drivers. Use beta drivers. -Alex. _______________________________________________ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
