From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.2) Gecko/20021202
Description of problem:
loading yenta_socket on toshiba satellite 1110 noteboot freeze kernel
same on kernel 2.4.18-18.8.0 and 2.4.20-2.21 with enabled ACPI
seems that pcmcia bridge has no assigned interrupts
pcmcia is not usable on thoshiba notebooks
Unabale to install RH8.0 from CD
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Actual Results: console display
PCI: No IRQ known for interrupt pin A of device 02:04.0.
PCI: No IRQ known for interrupt pin B of device 02:04.1.
Expected Results: yenta_socket is loaded
attached dmidecode and acpidmp outputs
Created attachment 89616 [details]
output from acpidmp
Created attachment 89617 [details]
output of dmidecode
does this still happen in 2.4.20-2.27 as is available in rawhide ?
Now no kernel dont freeze but module don't load
Jan 29 20:10:12 Maus kernel: Linux Kernel Card Services 3.1.22
Jan 29 20:10:12 Maus kernel: options: [pci] [cardbus] [pm]
Jan 29 20:10:12 Maus kernel: PCI: No IRQ known for interrupt pin A of device
02:04.0. Please try using pci=biosirq.
Jan 29 20:10:12 Maus kernel: PCI: No IRQ known for interrupt pin B of device
02:04.1. Please try using pci=biosirq.
Jan 29 20:10:12 Maus kernel: unloading Kernel Card Services
pci=biosirq does no matter
BUT this kernel do not propper shut down it hangs after doing
when sending SIGTERM last message is
Sending all precesses the TERM signal ...
reboot hang is a known (and now fixed) other, unrelated bug.
It looks like your bios doesn't provide the proper $PIR table for irq routing to
your cardbus controller..... not a lot we can do about that.
adding acpi patch acpi-20021205-2.4.20.diff to 2.4.20-2.21 will solve the
IRQ routing problem.
This patch applies to the redhat kernel with only one reject in
arch/i386/kernel/io_apic.c failing insert #include <linux/acpi.h>
For toshiba laptops it is also advised to add patch
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases,
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/