Bug 40690 - PCMCIA can't start
Summary: PCMCIA can't start
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel   
(Show other bugs)
Version: 7.1
Hardware: i586
OS: Linux
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2001-05-15 14:13 UTC by Robert Dehez
Modified: 2007-04-18 16:33 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-06-06 12:39:25 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Robert Dehez 2001-05-15 14:13:28 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.7 [fr]C-CCK-MCD   (WinNT; I)

Description of problem:
I have a Toshiba 480 CDT laptop.
I've installed Red Hat 7.1 and when i boot the i have this message :
Starting PCMCIA : PCI: no IRQ known for interrupt pin A of device 00:02.0 Please try using pci=biosirq
PCI: no IRQ known for interrupt pin B of device 00:02.1 Please try using pci=biosirq.
It's impossible to do anithing after that : The PC is crashed.

How reproducible:

Steps to Reproduce:
1.Start the PC

Actual Results:  Crash

Additional info:

Comment 1 Bill Nottingham 2001-05-15 16:07:26 UTC
Assigning to kernel.

Comment 2 Arjan van de Ven 2001-05-15 16:10:23 UTC
Did you try adding "bios=biosirq" at the lilo prompt ?

Comment 3 Robert Dehez 2001-05-17 12:27:51 UTC
I've resovlded the problem by changing bios (6.90 version) values :
I changed PC card controller mode : I turned it to PCIC Compatible instead of auto selected and now it works fine.

It's strange, i did not have this problem with the suse 6.2 ...

Comment 4 Arjan van de Ven 2001-05-17 12:30:48 UTC
Suse 6.2 (and older Red Hat versions) used the cardbus controller in a different
way. The "new" way makes it, in general :), much more reliable and faster for
things like networkcards. However it seems that your laptop didn't like that in
"auto" mode...

Note You need to log in before you can comment on or make changes to this bug.