Per Olofsson wrote:
On Sun, Jun 27, 2004 at 19:54 -0300, Robin Blondon wrote:In the installer, I found that instead of ejecting and reinserting the card I can go into the shell and kill and restart cardmgr. The intstaller then detected the card after choosing to detect network hardware from the installer menu.Hrm... strange. It could be because the installer first lacks the necessary modules and then fails to restart cardmgr properly when the modules are available. What if you choose detect network hardware a second time without killing and restarting cardmgr? And, by the way, do you have a Cardbus card or a 16-bit card?
If I choose to detect network hardware a second time without restarting cardmgr it still fails to find the card. I need to either restart cardmgr or reinsert the card. It is a 16-bit card. I believe that the laptop is not CardBus compatible.
I did find the following lines in /var/log/syslog after trying to detect the network hardware for the first time: Jun 29 18:17:09 (none) user.notice hw-detect: cardmgr[3459]: watching 1 socket
Jun 29 18:17:09 (none) daemon.info cardmgr[3459]: watching 1 socket Jun 29 18:17:09 (none) daemon.info cardmgr[3459]: starting, version is 3.2.5Jun 29 18:17:09 (none) daemon.info cardmgr[3459]: socket 0: Linksys WPC11 11Mbps 802.11b WLAN Card Jun 29 18:17:09 (none) daemon.info cardmgr[3459]: executing: 'modprobe orinoco_cs' Jun 29 18:17:09 (none) daemon.info cardmgr[3459]: + insmod: orinoco_cs.o: no module by that name found Jun 29 18:17:09 (none) daemon.info cardmgr[3459]: + modprobe: failed to load module orinoco_cs Jun 29 18:17:09 (none) daemon.info cardmgr[3459]: modprobe exited with status 1 Jun 29 18:17:09 (none) daemon.info cardmgr[3459]: module /lib/modules/2.4.25-1-386/pcmcia/orinoco_cs.o not available Jun 29 18:17:10 (none) daemon.info cardmgr[3459]: get dev info on socket 0 failed: Resource temporarily unavailable Jun 29 18:20:21 (none) user.notice hw-detect: Starting PCMCIA services: cardmgr is already running.
It looks like it found the card and tried to load the orinoco_cs module for it but it could not load the module. The "get dev info on socket 0 failed: Resource temporarily unavailable" line looks interesting.
The ESSID and the WEP key were both in /etc/network/interfaces and the auto eth0 line was in there.The first set of messages are:Configuring network interfaces...Error for wireless request "Set ESSID" (8B1A):SET failed on device eth0 ; No such device. Error for wireless request "Set Encode" (8B2A) : SET failed on device eth0 ; No such device. Error for wireless "Set Mode" (8B06) : SET failed on device eth0 ; No such device.Actually, the card should not be brought up by this init script. It should be brought up by cardmgr or hotplug. This means that the installer failed to recognise that the network interface was a PCMCIA card and thus erroneously added an "auto eth0" line to /etc/network/interfaces.
I added the i82365 module to /etc/modules and rebooted. The module loaded but it still tried to load the yenta_socket module when the PCMCIA services started.The second set of messages after starting PCMCIA services are:/lib/modules/2.4.25-1-386/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.25-1-386/kernel/drivers/pcmcia/yenta_socket.o: insmod /lib/modules/2.4.25-1-386/kernel/drivers/pcmcia/yenta_socket.o failed /lib/modules/2.4.25-1-386/kernel/drivers/pcmcia/yenta_socket.o: indmos yenta_socket failedThe problem here is probably that yenta_socket isn't the right module. Could you try loading i82365 instead? The pcmcia-cs package should have detected this but maybe something went wrong.
I then tried loading the orinoco_cs module manually via modprobe and running cardmgr and it configured the card and got an IP address from DHCP. I added orinoco_cs to /etc/modules and rebooted and it was then able to load cardmgr and configure the card. At what point is the orinoco_cs module supposed to be loaded? It is supposed to be loaded by cardmgr when it detects the card?
I've included the output of this above from the first phase of the installation.Is there anything else I should try?You could check the logs during the installation, i.e. "grep cardmgr /var/log/syslog".
- Robin