The system isn't picking anything, it's probably defined in /etc/sysconfig/pcmcia (and may be wrong, I'm guessing.)
Mine reads as follows:
PCMCIA=yes PCIC=yenta_socket PCIC_OPTS= CORE_OPTS=
And the output of modprobe i82365?
[root@xxxxxxxxxxx sysconfig]# modprobe i82365
/lib/modules/2.4.20-8/kernel/drivers/pcmcia/i82365.o: 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
/lib/modules/2.4.20-8/kernel/drivers/pcmcia/i82365.o: insmod /lib/modules/2.4.20-8/kernel/drivers/pcmcia/i82365.o failed
/lib/modules/2.4.20-8/kernel/drivers/pcmcia/i82365.o: insmod i82365 failed
Many Toshiba systems use that module. I have an older Sattelite Pro 420 that uses it. What model Toshiba is this again? I'd give you the output
of lspci on my laptop, but it doesn't work. ;)
Toshiba 1115-S103. It's one of the low end machines that actually manufactured by someone else.
$ ssh conundrum /sbin/lspci pcilib: Cannot open /proc/bus/pci lspci: Cannot find any working access method.
Here is the /etc/sysconfig/pcmcia file from that machine: $ ssh conundrum cat /etc/sysconfig/pcmcia PCMCIA=yes PCIC=i82365 PCIC_OPTS=do_scan=0 CORE_OPTS= CARDMGR_OPTS=-f
BTW, I tried copying your settings to my /etc/sysconfig/pcmcia file and got this:
[root@xxxxxxxxxxx sysconfig]# service pcmcia start
Starting PCMCIA services:/lib/modules/2.4.20-8/kernel/drivers/pcmcia/yenta_socket.o: 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
/lib/modules/2.4.20-8/kernel/drivers/pcmcia/yenta_socket.o: insmod /lib/modules/2.4.20-8/kernel/drivers/pcmcia/yenta_socket.o failed
/lib/modules/2.4.20-8/kernel/drivers/pcmcia/yenta_socket.o: insmod yenta_socket
failed
/lib/modules/2.4.20-8/kernel/drivers/pcmcia/ds.o: init_module: Operation not permitted
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
/lib/modules/2.4.20-8/kernel/drivers/pcmcia/ds.o: insmod /lib/modules/2.4.20-8/kernel/drivers/pcmcia/ds.o failed
/lib/modules/2.4.20-8/kernel/drivers/pcmcia/ds.o: insmod ds failed
cardmgr.
- From the manpage for i82365:
This is the low-level driver for the Intel i82365sl PCMCIA host con-
troller, and many derivative controllers. It also implements the Intel
"Yenta" register specification for CardBus bridges. Common clones of the i82365sl include controllers made by Cirrus Logic, IBM, O2Micro, Omega Micro, Ricoh, SMC, Texas Instruments, Toshiba, Vadem, and VLSI.
The overwhelming majority of current PCMCIA controllers, and all Card-
Bus bridges, are register compatible with the i82365sl. This driver is
used by Card Services for configuring the host controller, and for mon-
itoring card status change events.
It looks to me like the O2 Micro controller would use i82365
-- Greg Gulik http://www.gulik.org/greg/ greg @ gulik.org
