https://qa.mandrakesoft.com/show_bug.cgi?id=2153
------- Additional Comments From [EMAIL PROTECTED] 2003-02-23 08:50 -------
On Sat, 2003-02-22 at 12:39, ruediger.ruebig wrote:
I'm having similar problems in this... I can't get my NetGear MA401RA to
work with yenta_socket (I've had it working with the i82365) If I stop
pcmcia and just try to load the i82365 module I get the following.
# modprobe i82365
/lib/modules/2.4.21pre4-9mdk/kernel/drivers/pcmcia/i82365.o.gz:
init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters,
including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
modprobe: insmod
/lib/modules/2.4.21pre4-9mdk/kernel/drivers/pcmcia/i82365.o.gz failed
modprobe: insmod i82365 failed
if I try it directly
#insmod i82365
Using /lib/modules/2.4.21pre4-9mdk/kernel/drivers/pcmcia/i82365.o.gz
/lib/modules/2.4.21pre4-9mdk/kernel/drivers/pcmcia/i82365.o.gz:
unresolved syl dead_socket_Rcf97f3bd
/lib/modules/2.4.21pre4-9mdk/kernel/drivers/pcmcia/i82365.o.gz:
unresolved syl pcmcia_get_card_services_info_R3c39c871
/lib/modules/2.4.21pre4-9mdk/kernel/drivers/pcmcia/i82365.o.gz:
unresolved syl unregister_ss_entry_R0cdfb5e5
/lib/modules/2.4.21pre4-9mdk/kernel/drivers/pcmcia/i82365.o.gz:
unresolved syl register_ss_entry_R705959cb
The errors are identical (except for module directory) with
2.4.21pre4-10mdk 8mdk 7mdk and 6mdk (don't have an earlier one to test.)
James
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: UNCONFIRMED
creation_date:
description:
I'm using an Orinoco Silver PCMCIA Card with an PCI Bridge in my Desktop PC.
The autodetection process brings an high and an low peep, and the following log
message:
Feb 22 14:34:04 localhost kernel: Linux Kernel Card Services Kernel Version
Feb 22 14:34:04 localhost kernel: options: [pci] [cardbus] [pm]
Feb 22 14:34:04 localhost kernel: PCI: Enabling device 00:0a.0 (0000 -> 0002)
Feb 22 14:34:04 localhost kernel: PCI: No IRQ known for interrupt pin A of
device 00:0a.0. Probably buggy MP table.
Feb 22 14:34:04 localhost kernel: Yenta IRQ list 0000, PCI irq0
Feb 22 14:34:04 localhost kernel: Socket status: 10000011
Feb 22 14:34:04 localhost kernel: cs: IO port probe 0x0c00-0x0cff: clean.
Feb 22 14:34:04 localhost kernel: cs: IO port probe 0x0100-0x04ff: excluding
0x290-0x297 0x378-0x37f 0x400-0x40f 0x4d0-0x4d7
Feb 22 14:34:04 localhost kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Feb 22 14:34:04 localhost kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean.
Feb 22 14:34:04 localhost kernel: orinoco_cs: RequestIRQ: Resource in use
For testing purpose I changed /etc/sysconfig/pcmcia to:
PCMCIA=yes
PCIC=i82365 (instead of PCIC=yenta_socket)
PCIC_OPTS=irq_mode=0
This configuration change had no effect, system uses yenta_socket instead of
i82365. Why???
My Specs:
AMD XP 2200+
MSI KT4 Ultra KT400/VT8235
512 MB DDR (333) RAM
