x.org problem with savage driver (T23 Thinkpad)

Adam Williamson awilliam at redhat.com
Fri Mar 27 17:26:15 UTC 2009


On Thu, 2009-03-26 at 20:44 -0700, Kenny Simpson wrote:
> I installed F10 on a T23 Thinkpad and from there upgraded to rawhide.
> X worked reasonably well in F10, but dies in rawhide with the error:
> ...
> (II) Module int10: vendor="X.Org Foundation"
>         compiled for 1.6.0, module version = 1.0.0
>         ABI class: X.Org Video Driver, version 5.0
> (II) SAVAGE(0): initializing int10
> (II) SAVAGE(0): Primary V_BIOS segment is: 0xc000
> (II) SAVAGE(0): VESA BIOS detected
> (II) SAVAGE(0): VESA VBE Version 2.0
> (II) SAVAGE(0): VESA VBE Total Mem: 15168 kB
> (II) SAVAGE(0): VESA VBE OEM: S3 Incorporated. Paramont BIOS
> (II) SAVAGE(0): VESA VBE OEM Software Rev: 1.0
> (II) SAVAGE(0): VESA VBE OEM Vendor: S3 Incorporated.
> (II) SAVAGE(0): VESA VBE OEM Product: VBE 2.0
> (II) SAVAGE(0): VESA VBE OEM Product Rev: Rev 1.0
> (--) SAVAGE(0): Chip: id 8c2e, "SuperSavage/IXC 64"
> (--) SAVAGE(0): Engine: "SuperSavage"
> (--) SAVAGE(0): AGP card detected
> (==) SAVAGE(0): Using AGP DMA
> (II) SAVAGE(0): DMA is not supported on SuperSavages.
> (==) SAVAGE(0): DMA disabled
> (==) SAVAGE(0): Using AGP 1x mode
> (==) SAVAGE(0): Using 16 MB AGP aperture
> (EE) SAVAGE(0): Internal error: cound not map aperture range (7, Argument list too long).
> 
> Backtrace:
> 0: /usr/bin/Xorg(xorg_backtrace+0x3b) [0x812e12b]
> 1: /usr/bin/Xorg(xf86SigHandler+0x9e) [0x80c0dbe]
> 2: [0x6a4400]
> 3: /usr/lib/xorg/modules/drivers//savage_drv.so [0x1d8ac1]
> 4: /usr/lib/xorg/modules/drivers//savage_drv.so [0x1da245]
> 5: /usr/lib/xorg/modules/drivers//savage_drv.so [0x1da38d]
> 6: /usr/lib/xorg/modules/drivers//savage_drv.so [0x1dde37]
> 7: /usr/bin/Xorg(InitOutput+0x4e9) [0x80a92c9]
> 8: /usr/bin/Xorg(main+0x1d3) [0x806b903]
> 9: /lib/libc.so.6(__libc_start_main+0xe6) [0x720736]
> 10: /usr/bin/Xorg [0x806af71]
> 
> Fatal server error:
> Caught signal 11.  Server aborting
> 
> 
> 
> This is with all the current updates as of today.

Please file a bug on this issue. It may even be best to file it
upstream, as I doubt the Fedora package is diverged from the upstream
code.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net




More information about the fedora-test-list mailing list