Created attachment 17500 [details] xorg.conf I have an old pci s3virge[1] card in my system as a secondary card. If I try to start xorg-server-1.4.99.905 with this card (in a xinerama or stand alone) xorg-server hangs[2] before kdm start and can't go back to a terminal. If I do a crt+alt+sup the system reboot. I am using gentoo ~x86 (vanilla-kernel 2.6.26, gcc 4.3.1, glibc 2.8_p20080602) I test it with gentoo-sources 2.6.25 and fail too. With xorg-server-1.4.2 works perfectly (even in a xinerama setup) [1]02:07.0 VGA compatible controller: S3 Inc. ViRGE/DX or /GX (rev 01) [2]Last line in Xorg.0.log (II) Loading /usr/lib/xorg/modules//libvbe.so (II) Module vbe: vendor="X.Org Foundation" compiled for 1.4.99.905, module version = 1.1.0 ABI class: X.Org Video Driver, version 4.1 (II) Loading sub module "int10" (II) LoadModule: "int10" (II) Loading /usr/lib/xorg/modules//libint10.so (II) Module int10: vendor="X.Org Foundation" compiled for 1.4.99.905, module version = 1.0.0 ABI class: X.Org Video Driver, version 4.1 (II) S3VIRGE(0): initializing int10 (II) S3VIRGE(0): VESA BIOS detected (II) S3VIRGE(0): VESA VBE Version 1.2 (II) S3VIRGE(0): VESA VBE Total Mem: 2048 kB (II) S3VIRGE(0): VESA VBE OEM: S3 Incorporated. 86C375/86C385 (--) S3VIRGE(0): Chipset: "virge dx" (==) S3VIRGE(0): XVideo supported. (II) S3VIRGE(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000 (II) S3VIRGE(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000 (II) Loading sub module "ddc" (II) LoadModule: "ddc" (II) Module "ddc" already built-in
Is this still happening? Were the driver versions the same when you tried 1.4.99.905 and 1.4.2? Can you please run the server under strace or some other introspection tool to see where it's blocking?
Mass closure: This bug has been untouched for more than six years, and is not obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.