From Bugzilla Helper: User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.4.12-ac3 i686) Description of problem: I wantend to install a fresh 7.2 on a system with S3 Virge graphic card. It freezed at various points within a few seconds after X server started. The furthest i came was the mouse selection ;) Version-Release number of selected component (if applicable): 7.2 How reproducible: Always Steps to Reproduce: 1. Have a S3 virge card in your system 2. Try default install, graphical 3. Observer the X server freeze Actual Results: Within seconds of X server starting, machine freezes completely, mouse does not move, keyboard unresponsive. It happens at various stages, once i came as far as the mouse selection, once it froze before the redhat logo was displayed. Expected Results: It should work, no? I ended up inserting an ancient 256k isa vga card into the system and installig with vga16 X server ... Additional info: It is known that various S3 graphic boards are a reason for unstable systems with XFree86 4.x. So why exactly is XFree86 4.x used in the installer? Or, at least run something like vga16 if an S3 chip is detected ;)
Does text mode work?
Yes, text mode works ok. Only X freezes.
We don't use XFree86 4.0 for the installer. We use the XF86_FBDev server, which is the XFree86 3.3.6 framebuffer device server. I have an "S3 ViRGE /DX /GX" (that's what ddcprobe returns) that works fine in the installer. There were some problems with S3 ViRGEs in some of the betas for Enigma, but they were fixed for the final release (at least for the ViRGEs that we have here). I don't know why you are having problems with it, but the best workaround I can suggest would be to use text mode install. There's not anything else I can do to fix this.
My card is recognized as S3 ViRGE generic and the card reports itself as 86C325 on screen. If you want, i can check the markings on the chip itself.
Try switching to VC2 during the install by pressing <Ctrl><Alt><F2> and running ddcprobe. Having that information would be more useful, since that's what the video card is reporting itself as.
ddc out reports: VESA 1.2 detected. OEM Name: S3 Incorporated. 86C325 Memory installed = 32 * 64k blocks = 2048kb Supported standard modes: 640x400x256 640x480x256 800x600x16 800x600x256 1024x768x16 1024x768x256 1280x1024x16 1280x1024x256 132x25 (text) 132x43 (text) 320x200x32k 320x200x64k 320x200x16m 640x480x32k 640x480x64k 640x480x16m 800x600x32k 800x600x64k 800x600x16m 1024x768x32k 1024x768x64k 1024x768x16m 1280x1024x32k 1280x1024x64k 1600x1200x256 EDID read failed, returned empty data
Ok, can you post the output of 'lspci -n' and 'lspci -v'? That will tell us the pci ID of the card. The pci ID should be 5333:5631. That is what kudzu says the pci ID should be for a "Card:S3 ViRGE (generic)" "S3 Inc.|86c325 [ViRGE]".
lspci -v shows the card as: 00:0d.0 VGA compatible controller: S3 Inc. 86c325 [ViRGE] (rev 06) (prog-if 00 [VGA]) Flags: bus master, medium devsel, latency 40, IRQ 11 Memory at f8000000 (32-bit, non-prefetchable) [size=64M] Expansion ROM at <unassigned> [disabled] [size=64K] and lspci -n for 0d.0 is: 00:0d.0 Class 0300: 5333:5631 (rev 06) so yes, it gets detected properly. it just locks up for unknown reason :) if i'll find some free time i'll try it under normal X session to see if it behaves properly.