[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: wifi, knoppix, WEP



On Sun, 2004-08-29 at 02:19, Robert Citek wrote:
> Revisiting this with Knoppix 3.6 on a WAP that does not use WEP.
> 
> On Tuesday, Aug 24, 2004, at 00:55 US/Central, Robert G. (Doc) Savage 
> wrote:
> > At this point I would suspect the wavelan.o driver. After you insert 
> > the
> > card, what do the last few lines of dmesg say? Does they indicate your
> > card is being recognized? If so, what happens when you manually install
> > the driver (I'll assume that would be wavelan.o).
> 
> Below are the messages from dmesg, /var/log/syslog, and 'ifconfig -a'.  
> As far as I can tell the card is being recognized as a wifi card, but 
> does not work.  In contrast, I've been able to get a netgear PCMCIA 
> wifi card to work just fine.  But then the Netgear card uses the 
> orinoco driver.
> 
> Any thoughts?
> 
> Regards,
> - Robert
> 
> -----
> ### tail of dmesg before inserting card
>   ...
[snip]
> cs: memory probe 0xa0000000-0xa0ffffff: clean.
> hostap_crypt: registered algorithm 'NULL'
> hostap_cs: 0.0.4 - 2003-07-27 (Jouni Malinen <jkmaline@cc.hut.fi>)
> hostap_cs: setting Vcc=33 (constant)
> hostap_cs: CS_EVENT_CARD_INSERTION
> prism2_config()
> hostap_cs: setting Vcc=33 (from config)
> Checking CFTABLE_ENTRY 0x01 (default 0x01)
> IO window settings: cfg->io.nwin=1 dflt.io.nwin=1
> io->flags = 0x0046, io.base=0x0000, len=64
> hostap_cs: index 0x01: Vcc 3.3, irq 3, io 0x0100-0x013f
> hostap_cs: Registered netdevice wlan0
> prism2_hw_init()
> prism2_hw_init: initialized in 110 ms
> wlan0: trying to read PDA from 0x007f0000: failed
> wlan0: trying to read PDA from 0x003f0000: failed
> wlan0: trying to read PDA from 0x00390000: OK
> wlan0: NIC: id=0x8002 v1.0.0
> wlan0: PRI: id=0x15 v0.3.0
> wlan0: STA: id=0x1f v1.7.1
> wlan0: prism2_open
> wlan0: prism2_close
> wlan0: Deauthenticate all stations

Robert,

I'm not familiar with the Wavelan card, but these insertion and
registration messages appear fairly nominal.

> #### /var/log/syslog after inserting card
> Aug 29 01:49:42 Knoppix syslogd 1.4.1#15: restart.
> Aug 29 01:50:23 Knoppix usb.agent[818]:      usbcore: already loaded
> Aug 29 01:50:23 Knoppix usb.agent[818]:      usbcore: already loaded
> Aug 29 01:50:24 Knoppix usb.agent[835]:      usb-storage: loaded 
> successfully
> Aug 29 01:51:05 Knoppix cardmgr[86]: socket 0: Proxim RangeLAN
> Aug 29 01:51:05 Knoppix cardmgr[86]: executing: 'modprobe hostap'
> Aug 29 01:51:06 Knoppix cardmgr[86]: executing: 'modprobe hostap_cs'
> Aug 29 01:51:07 Knoppix cardmgr[86]: executing: './network start wlan0'
> Aug 29 01:51:07 Knoppix cardmgr[86]: + Sample private network setup
> Aug 29 01:51:07 Knoppix cardmgr[86]: + /sbin/ifconfig wlan0 up
> Aug 29 01:51:07 Knoppix cardmgr[86]: + /sbin/pump  -i wlan0 > /dev/null
> Aug 29 01:51:07 Knoppix pumpd[276]: PUMP: sending discover
> Aug 29 01:51:27 Knoppix cardmgr[86]: + Operation failed.
> Aug 29 01:51:27 Knoppix cardmgr[86]: start cmd exited with status 1

PUMP has a problem here. I don't use it, but I believe it's a DHCP
client manager and should have gotten your card an IP address. Status 1
usually means failure. And this is with Knoppix?

> #### lsmod after inserting card
> Module                  Size  Used by    Not tainted
> nls_iso8859-1           2844   1  (autoclean)
> nls_cp437               4348   1  (autoclean)
> hostap_cs              47708   0
> hostap                 86244   0  [hostap_cs]
> hostap_crypt            1424   0  [hostap]
> autofs4                 8756   1  (autoclean)
> af_packet              13544   0  (autoclean)
> agpgart                42724   0  (unused)
> cs4281                 46760   0
> soundcore               3428   3  [cs4281]
> e100                   51064   0
> serial                 52100   0  (autoclean)
> ds                      6536   2  [hostap_cs]
> yenta_socket            9508   2
> pcmcia_core            39840   0  [hostap_cs ds yenta_socket]
> thermal                 6724   0  (unused)
> processor               9008   0  [thermal]
> fan                     1600   0  (unused)
> button                  2700   0  (unused)
> battery                 5952   0  (unused)
> ac                      1824   0  (unused)
> rtc                     7036   0  (autoclean)
> cloop                   8740   2
> ieee1394              183076   0
> usb-storage            61760   1
> usb-uhci               21644   0  (unused)
> usbcore                57600   1  [usb-storage usb-uhci]
> ataraid                 6180   0
> ide-scsi                8816   1

The above confirms that your driver isn't loading correctly. You should
see a wlan0 listing in the first column and also in the column 4 listing
for pcmcia_core.

> #### ifconfig -a after inserting card
> eth0      Link encap:Ethernet  HWaddr 00:03:47:0F:90:A8
>            BROADCAST MULTICAST  MTU:1500  Metric:1
>            RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:0 errors:1 dropped:0 overruns:0 carrier:1
>            collisions:0 txqueuelen:1000
>            RX bytes:0 (0.0 b)  TX bytes:342 (342.0 b)
>            Interrupt:11 Base address:0x1840 Memory:f4010000-f4010038
> 
> lo        Link encap:Local Loopback
>            inet addr:127.0.0.1  Mask:255.0.0.0
>            UP LOOPBACK RUNNING  MTU:16436  Metric:1
>            RX packets:2 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:0
>            RX bytes:100 (100.0 b)  TX bytes:100 (100.0 b)
> 
> wlan0     Link encap:Ethernet  HWaddr 00:60:B3:6F:5B:6D
>            BROADCAST MULTICAST  MTU:1500  Metric:1
>            RX packets:18 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:1000
>            RX bytes:0 (0.0 b)  TX bytes:1488 (1.4 KiB)
>            Interrupt:3 Base address:0x100

You didn't list your modules.conf or ifcfg-eth1, so I can't tell what's
aliased to what. Your wlan0 device appears to have been discovered
correctly and has been configured correctly up to frame Layer 2 (raw
Ethernet). wlan0 has no IP address assigned, so network Layer 3 isn't
properly configured.

Did you try running iwconfig to see if it could talk to the card? 

At this point I still suspect a problem with the wavelan driver. Have
you tried searching Bugzilla for similar problems? If none, file your
own.

-- Doc
Robert G. (Doc) Savage, BSE(EE), CISSP, RHCE | Fairview Heights, IL
Fedora Core 1 kernel 2.4.22-1.2199.nptl on P-III/M IBM Thinkpad A22p
"Perfection is the enemy of good enough."
                         -- Admiral of the Fleet Sergei G. Gorshkov


-
To unsubscribe, send email to majordomo@silug.org with
"unsubscribe silug-discuss" in the body.