Red Hat Bugzilla – Bug 13478
signal 11 during installation.
Last modified: 2007-04-18 12:27:27 EDT
I get "install exited abnormally--received signal 11" during the installation of RedHat 6.1. It then goes right to shut-down. It does not matter which GUI is chosen to be installed; but I tried GNU multiple times. It occurs right after the partitionin step, BEFORE THE VIDEO DRIVER TEST AND ISNTALL. I set the Severity to high because the OS cannot be installed at all. I tried several different automatic platforms, and a manual install. The following is the PC configuration: RedHat Version: 6.1, but 6.2 has also been attempted with the same results. Motherboard: FIC SD11 (Slot A) Memory: two 8ns, 128 MB DIMMs video adapter: ATI Rage Fury MAXX 64 MB sound: Creative Soundblaster PCI128 NEC: FE100R II/III HDD: primary ide master--Maxtor 5 1024U2 (10 gig) primary ide slave--Maxtor 9 1303D6 ((13 gig) secondary ide master--ATAPI CDR 32X secondary ide slave--Mitsumi CDRW 8X4X4 Alternate OS: Win 98SE Thanks for your attention to this issue.
If you try the text based installer does it work?
Hi, I tried the text mode, the GUI mode--neither work. I tried gnu and Kde. I never had trouble installing in until I upgraded to the AMD Athlon 700 on the FIC SD11. I could not get the gui to install, because there is no default driver for the video card (ATI Rage FURY MAXX), but the command line came up. on my new PC, I cant get to the video driver detection screen at all. All the components are the same; the only difference is the Athlon and the SD11. Thanks again, Carl
Update: I installed a Creative Labs Voodoo Banshee card, and because there exists a driver for the Banshee in Linux, it came up with the GUI install screens; but it still goes to shutdown right after the partition setup screen. At this point, I believe this is a motherboard incompatability issue. The CMOS version is the latest (I checked on the FIC website). The motherboard rev. is 1.8. This motherboard has several limitations (i.e.: non-ACPI compliant), but I do not know which would apply to or cause this issue. C Anthony
This certainly sounds like a hardware compatibility issue unfortunelately.
This has been duplicated on an ABIT KA7 Athlon MB. If this is a hardware issue (duh!), is it with all ne athlons? Athlons are X86 architecture, aren't they? Is it a timing issue? I believe closure of this as a NOTABUG is incorrect, but I guess as far as RedHat is concerned, it doesn't matter.