[BAT] wi0: init failed -- bad or normal? (FW: Forcing IRQ assignments?)
Tony Saign
Mon, 15 Apr 2002 19:41:26 -0700
I see similar behavior under FreeBSD, changes made to pccard.conf have
no effect.
Both D-Link and WaveLAN cards take IRQ 11. (Even if removed from
available IRQ list)
Any ideas?
-Tony
-----Original Message-----
From:
[mailto:] On Behalf Of Tony Saign
Sent: Monday, April 15, 2002 5:07 PM
To:
Subject: Forcing IRQ assignments?
Is it possible to force a pccard to a specific IRQ?
Under W2K or WXP my wireless cards take IRQ7, which works fine since lpt
port doesn't need an IRQ.
However under FreeBSD I am seeing "stray IRQ 7" errors, and the cards
are using IRQ11.
Could this be why I am having lock-up issues with wi, and getting wi0:
init
failed errors???
-Tony
To Unsubscribe: send mail to
with "unsubscribe freebsd-mobile" in the body of the message
-----Original Message-----
From:
[mailto:] On Behalf Of Jerry Francus
Sent: Monday, April 15, 2002 6:42 PM
To:
Subject: [BAT] wi0: init failed -- bad or normal?
Thanks for the tips but I am a bit confused. The dmesg output shows IRQ
11
assigned to the D-Link card not IRQ 9. I tried creating /etc/pccard.conf
and
limit the available IRQs but it seems to have no effect. Upon rebooting
IRQ
11 is still used.
This laptop is a dual-boot machine with Win-2k on the other partition.
Win-2k reports the D-Link card at IRQ 10 and a bunch of devices using
IRQ 9
including the built-in sound (which does not work under FreeBSD), the
built-in modem, and the video adapter. I guess these are all PCI devices
so
they show up this way. Not sure why FreeBSD selects IRQ 11 for the
D-Link.
I am not a FreeBSD expert so I would appreciate any help you can provide
on
resolving an IRQ conflict (if in fact that is the problem here).
Thanks,
Jerry