Red Hat Bugzilla – Bug 116493
Fedora core 2 test 1 installer exits with signal 11
Last modified: 2015-01-04 17:04:42 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)
Description of problem:
Tried to install fedora core 2 test 1 on a toshiba tecra 8200 with
128meg, first install hangs on /sbin/loader. Tried again with the
nousb option, it then enters starts the installer. Tried the media
test, which completed succesfully. If I try to install, however, the
installer exits with a signal 11
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.installed with nousb option
2.installed in text mode
3.installed with mem=128 option
Actual Results: nothing, install exits with signal 11
Expected Results: The installer should have started
Do you have a pcmcia card in? If so, does removing it help?
No, there is no pcmcia card, however, the laptop does have an
internal wifi card (orinoco type, at least it works with that driver)
which uses pcmcia (it needs cardmgr), shutting it down does not solve
the problem unfortunately.
the wifi card is onboard, so can not be removed
Does booting with 'linux nopcmcia' work then?
Well, it works, as in, I tried it and was able to install fedora.
However, after the first reboot, it immediately hangs when it tries
to configure pcmcia. Trying to boot it without pcmcia doesn't help,
because it then hangs trying to configure an unidentified device,
which I guess is my wifi card. It says (right after enabling the swap
PCI: Enabling device 0000:02:0c.0 (0000 -> 0002)
ACPI: No IRQ known for interrupt pin A of device 0000:02:0c.0 - using
PCI: Enabling device 0000:02:0d.0 (0000 -> 0002)
ACPI: No IRQ known for interrupt pin A of device 0000:02:0d.0 - using
I have the same problem with a Dell Inspiron 4000 with 128mb.
Please report if acpi=off or later test kernels fixed this
Fedora Core 2 has now reached end of life, and no further updates will be
provided by Red Hat. The Fedora legacy project will be producing further kernel
updates for security problems only.
If this bug has not been fixed in the latest Fedora Core 2 update kernel, please
try to reproduce it under Fedora Core 3, and reopen if necessary, changing the
product version accordingly.