[lug] Wireless networking
Terry Branaman
t-branaman at comcast.net
Wed Jul 16 09:39:16 MDT 2003
Here is the output from /var/messages:
Jul 16 09:34:31 laptop kernel: cs: cb_alloc(bus 4): vendor 0x1317,
device 0x8201
Jul 16 09:34:31 laptop kernel: PCI: Enabling device 04:00.0 (0000 ->
0003)
Jul 16 09:34:31 laptop kernel: PCI: No IRQ known for interrupt pin A of
device 04:00.0. Please try using pci=biosirq.
Jul 16 09:34:31 laptop /etc/hotplug/pci.agent: pcimodules is scanning
more than ...
Jul 16 09:34:31 laptop /etc/hotplug/pci.agent: Setup yenta_socket
eepro100 e100 ohci1394 ehci-hcd usb-ohci snd-intel8x0 i810_audio
i810-tco i810_rng for PCI slot 04:00.0
Jul 16 09:34:31 laptop kernel: eepro100.c:v1.09j-t 9/29/99 Donald Becker
http://www.scyld.com/network/eepro100.html
Jul 16 09:34:31 laptop kernel: eepro100.c: $Revision: 1.36 $ 2000/11/17
Modified by Andrey V. Savochkin <saw at saw.sw.com.sg> and others
Jul 16 09:34:31 laptop insmod:
/lib/modules/2.4.21-0.13mdk/kernel/drivers/net/eepro100.o.gz:
init_module: No such device
Jul 16 09:34:31 laptop insmod: 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
Jul 16 09:34:31 laptop modprobe: modprobe: insmod
/lib/modules/2.4.21-0.13mdk/kernel/drivers/net/eepro100.o.gz failed
Jul 16 09:34:31 laptop modprobe: modprobe: insmod eepro100 failed
Jul 16 09:34:31 laptop /etc/hotplug/pci.agent: ... can't load module
eepro100
Jul 16 09:34:31 laptop /etc/hotplug/pci.agent: missing kernel or user
mode driver eepro100
Jul 16 09:34:32 laptop kernel: ohci1394: $Rev: 693 $ Ben Collins
<bcollins at debian.org>
Jul 16 09:34:32 laptop kernel: PCI: Enabling device 02:07.0 (0000 ->
0002)
Jul 16 09:34:32 laptop kernel: PCI: No IRQ known for interrupt pin A of
device 02:07.0. Please try using pci=biosirq.
Jul 16 09:34:32 laptop kernel: ohci1394_0: No IR DMA context available
Jul 16 09:34:32 laptop kernel: ohci1394_0: Runaway loop while stopping
context...
Jul 16 09:34:32 laptop kernel: ohci1394: Failed to allocate IR context
Jul 16 09:34:32 laptop kernel: ohci1394_0: Runaway loop while stopping
context...
Jul 16 09:34:32 laptop last message repeated 3 times
Jul 16 09:34:32 laptop insmod:
/lib/modules/2.4.21-0.13mdk/kernel/drivers/ieee1394/ohci1394.o.gz:
init_module: No such device
Jul 16 09:34:32 laptop insmod: 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
Jul 16 09:34:32 laptop modprobe: modprobe: insmod
/lib/modules/2.4.21-0.13mdk/kernel/drivers/ieee1394/ohci1394.o.gz failed
Jul 16 09:34:32 laptop modprobe: modprobe: insmod ohci1394 failed
Jul 16 09:34:32 laptop /etc/hotplug/pci.agent: ... can't load module
ohci1394
Jul 16 09:34:32 laptop /etc/hotplug/pci.agent: missing kernel or user
mode driver ohci1394
Jul 16 09:34:32 laptop kernel: PCI: Enabling device 02:06.2 (0000 ->
0002)
Jul 16 09:34:32 laptop kernel: PCI: No IRQ known for interrupt pin C of
device 02:06.2. Please try using pci=biosirq.
Jul 16 09:34:32 laptop kernel: hcd.c: Found HC with no IRQ. Check
BIOS/PCI 02:06.2 setup!
Jul 16 09:34:32 laptop insmod:
/lib/modules/2.4.21-0.13mdk/kernel/drivers/usb/hcd/ehci-hcd.o.gz:
init_module: No such device
Jul 16 09:34:32 laptop insmod: 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
Jul 16 09:34:32 laptop modprobe: modprobe: insmod
/lib/modules/2.4.21-0.13mdk/kernel/drivers/usb/hcd/ehci-hcd.o.gz failed
Jul 16 09:34:32 laptop modprobe: modprobe: insmod ehci-hcd failed
Jul 16 09:34:32 laptop /etc/hotplug/pci.agent: ... can't load module
ehci-hcd
Jul 16 09:34:32 laptop /etc/hotplug/pci.agent: missing kernel or user
mode driver ehci-hcd
Jul 16 09:34:32 laptop kernel: PCI: No IRQ known for interrupt pin B of
device 00:1f.5. Please try using pci=biosirq.
Jul 16 09:34:32 laptop kernel: unable to grab IRQ 0
Jul 16 09:34:32 laptop kernel: Intel ICH soundcard not found or device
busy
Jul 16 09:34:32 laptop insmod:
/lib/modules/2.4.21-0.13mdk/kernel/sound/pci/snd-intel8x0.o.gz:
init_module: No such device
Jul 16 09:34:32 laptop insmod: 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
Jul 16 09:34:32 laptop modprobe: modprobe: insmod
/lib/modules/2.4.21-0.13mdk/kernel/sound/pci/snd-intel8x0.o.gz failed
Jul 16 09:34:32 laptop modprobe: modprobe: insmod snd-intel8x0 failed
Jul 16 09:34:32 laptop /etc/hotplug/pci.agent: ... can't load module
snd-intel8x0
Jul 16 09:34:32 laptop /etc/hotplug/pci.agent: missing kernel or user
mode driver snd-intel8x0
Jul 16 09:34:32 laptop kernel: Intel 810 + AC97 Audio, version 0.24,
15:29:58 Mar 14 2003
Jul 16 09:34:32 laptop kernel: PCI: No IRQ known for interrupt pin B of
device 00:1f.5. Please try using pci=biosirq.
Jul 16 09:34:32 laptop kernel: i810: Intel ICH3 found at IO 0x1400 and
0x1000, MEM 0x0000 and 0x0000, IRQ 0
Jul 16 09:34:32 laptop kernel: i810_audio: unable to allocate irq 0
Jul 16 09:34:32 laptop insmod:
/lib/modules/2.4.21-0.13mdk/kernel/drivers/sound/i810_audio.o.gz:
init_module: No such device
Jul 16 09:34:32 laptop insmod: 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
Jul 16 09:34:32 laptop modprobe: modprobe: insmod
/lib/modules/2.4.21-0.13mdk/kernel/drivers/sound/i810_audio.o.gz failed
Jul 16 09:34:32 laptop modprobe: modprobe: insmod i810_audio failed
Jul 16 09:34:32 laptop /etc/hotplug/pci.agent: ... can't load module
i810_audio
Jul 16 09:34:32 laptop /etc/hotplug/pci.agent: missing kernel or user
mode driver i810_audio
Jul 16 09:34:32 laptop kernel: i810 TCO timer, v0.05: timer margin: 30
sec (0xee60) (nowayout=0)
Jul 16 09:34:32 laptop kernel: i810_rng: RNG not detected
Jul 16 09:34:32 laptop insmod:
/lib/modules/2.4.21-0.13mdk/kernel/drivers/char/i810_rng.o.gz:
init_module: No such device
Jul 16 09:34:32 laptop insmod: 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
Jul 16 09:34:32 laptop modprobe: modprobe: insmod
/lib/modules/2.4.21-0.13mdk/kernel/drivers/char/i810_rng.o.gz failed
Jul 16 09:34:32 laptop modprobe: modprobe: insmod i810_rng failed
Jul 16 09:34:32 laptop /etc/hotplug/pci.agent: ... can't load module
i810_rng
Jul 16 09:34:32 laptop /etc/hotplug/pci.agent: missing kernel or user
mode driver i810_rng
On Wed, 2003-07-16 at 06:45, Ed Hill wrote:
> On Wed, 2003-07-16 at 00:12, Terry Branaman wrote:
> > I'm trying to get wireless networking on my laptop, with no success. The
> > laptop is a Toshiba Satellite 5205 running Mandrake 9.1. The wireless
> > nic is a SMC2635W. I followed the instructions on the SMC web site:
> >
> > 1. Add the following lines to your /etc/pcmcia/config file:
> > card "SMC2632W"
> > manfid 0x0156, 0x0002
> > bind "wvlan_cs"
> >
> > 2. Add or uncomment the following lines to your /etc/pcmcia/config.opts
> > file:
> > # Options for WaveLAN/IEEE driver (AccessPoint mode)...
> > #module "wvlan_cs" opts "station_name=MY_PC"
> > # Options for WaveLAN/IEEE driver (ad-hoc mode)...
> > module "wvlan_cs" opts "port_type=1 channel=6 station_name=Linux"
> >
> > 3. Add or uncomment these lines to your /etc/pcmcia/wireless.opts file:
> > # Note : wvlan_cs driver only, and version 1.0.4+ for encryption support
> > *,*,*,00:e0:29:*) # Here you should enter the MAC address of your
> > INFO="SMC test network adapter" #wireless adapter
> > ESSID="any"
> > MODE="Infrastructure"
> > RATE="auto"
> > CHANNEL="6"
> > Lastly, run the Linuxconf Utility and configure your first network
> > interface (assuming you only have one network adapter in your system) to
> > use the "Net Device" = "wvlan0" and set it to DHCP or static depending
> > on your network infrastructure.
> >
> > I then restarted the pcmcia and network services, but the system is not
> > seeing the wireless nic; it is seeing the built-in 10/100 nic (eth0)
> > just fine. "ifup eht1" gives the message "wvlan0 device eth1 does not
> > seem to be present, delaying initialization."
> >
> > I've looked on google, without success, for aditional information that
> > might help. Any pointers would be greatly appreciated.
>
>
> Hi Terry,
>
> Could you send us the output produced in /var/log/messages when you
> insert the card? That will be a BIG help for anyone trying to diagnose
> the problem(s)!
>
> Ed
--
Terry Branaman <t-branaman at comcast.net>
More information about the LUG
mailing list