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

Hostap troubles with a Sitecom wn-pcc-01



Hi all,

Yesterday don't come to the list, should be because I sent it with a e-mail address that not subscribe to the list.

Sorry if it cames twice.

Lobo.

-------- Mensaje Original --------
Asunto: Hostap troubles with a Sitecom wn-pcc-01
Fecha: Sat, 05 Feb 2005 22:42:48 +0100
De: Rubén Gómez Antolí <mixtolobo@jazzfree.com>
Para: debian-laptop@lists.debian.org

Hello all,

Sorry for my bad english, I will try to write as well as I do.

I'm having troubles with a pcmcia prism card knows as sitecom wn-pcc-01,
but recognized how "airbond xi-300b".

This card was working well with orinoco_cs module in a 2.6.7 kernel, but
a day, it wasn't work anymore in this system, I promise you that I don't
nothing about his configuration, and it works in knoppix v3.3 with
2.4.27 kernel version.

I tried to upgrade kernel version, but it's fails.

Read and consulting I gone to hostap modules, but card still don't work.

My system is a Dell Inspiron 8100, with a Sarge/Sid distribution. My
kernel version actually is 2.6.10:

Linux puerto-lobo 2.6.10+3.ii.2005-0 #1 Thu Feb 3 23:03:46 CET 2005 i686
GNU/Linux

compiled myself with this command:

fakeroot make-kpkg --initrd --revision puerto.lobo.0.1
--append_to_version +3.ii.2005-0 kernel-image modules_image

and hostap modules and utils version:

razer@puerto-lobo:~$ COLUMNS=100 dpkg -l |grep -i hostap
ii  hostap-modules-2.6. 0.2.6-1+puerto.lobo Host AP driver for Intersil
Prism2/2.5/3 (kernel 2.6.1
ii  hostap-modules-2.6. 0.2.6-1+puerto.lobo Host AP driver for Intersil
Prism2/2.5/3 (kernel 2.6.1
ii  hostap-source       0.2.6-1             Host AP driver for Intersil
Prism2/2.5/3
ii  hostap-utils        0.2.6-1             Utility programs for Host AP
driver for Intersil Prism

I tried to upgrade firmware's card with prism2_srec:

prism2_srec -v -f wlan0 s1010701.hex

with this result:

puerto-lobo:~# hostap_diag wlan0
Host AP driver diagnostics information for 'wlan0'

NICID: id=0x8002 v1.0.0 (HWB3163-01,02,03,04 Rev A)
PRIID: id=0x0015 v0.3.0
STAID: id=0x001f v1.7.1 (station firmware)

But card doesn't works.

I tried with several kernel, including debian kernel-image with no results.

Actually I try to connect with network with dhclient and pump. Pump
doesn't returns any error:

Feb  5 21:46:53 localhost pumpd[4485]: PUMP: sending discover
Feb  5 21:47:23 localhost kernel: wifi0: Deauthenticate all stations

But, if I try with dhclient:

Feb  5 21:47:33 localhost kernel: wifi0: invalid skb->cb magic
(0x00000000, expected 0xf08a36a2)
Feb  5 21:47:34 localhost dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 7
Feb  5 21:47:34 localhost dhclient: DHCPDISCOVER on lo to
255.255.255.255 port 67 interval 7
Feb  5 21:47:34 localhost dhclient: receive_packet failed on eth0:
Network is down
Feb  5 21:47:34 localhost dhclient: DHCPDISCOVER on wifi0 to
255.255.255.255 port 67 interval 6
Feb  5 21:47:34 localhost kernel: wifi0: invalid skb->cb magic
(0x00000000, expected 0xf08a36a2)


Dmesg output is "more" clear:

wifi0: invalid skb->cb magic (0x00000000, expected 0xf08a36a2)
wifi0: invalid skb->cb magic (0x00000000, expected 0xf08a36a2)
wifi0: invalid skb->cb magic (0x00000000, expected 0xf08a36a2)
wifi0: invalid skb->cb magic (0x00000000, expected 0xf08a36a2)
wifi0: invalid skb->cb magic (0x00000000, expected 0xf08a36a2)
wifi0: invalid skb->cb magic (0x00000000, expected 0xf08a36a2)


These errors messages is received if I configured wlan0 with this command:

iwconfig nickname "puerto-lobo" key "my_wep_key"

And iwconfig outputs after execute dhclient:

puerto-lobo:~# iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

wifi0     IEEE 802.11b  ESSID:"test"  Nickname:"puerto-lobo"
~          Mode:Master  Frequency:2.422 GHz  Access Point: 00:60:B3:68:F6:E0
~          Bit Rate:11 Mb/s   Sensitivity=1/3
~          Retry min limit:8   RTS thr:off   Fragment thr:off
~          Encryption key:xxxxxxxxxxxxxxxx   Security mode:restricted
~          Power Management:off
~          Link Quality:0  Signal level:0  Noise level:0
~          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
~          Tx excessive retries:0  Invalid misc:333   Missed beacon:0

wlan0     IEEE 802.11b  ESSID:"test"  Nickname:"puerto-lobo"
~          Mode:Master  Frequency:2.422 GHz  Access Point: 00:60:B3:68:F6:E0
~          Bit Rate:11 Mb/s   Sensitivity=1/3
~          Retry min limit:8   RTS thr:off   Fragment thr:off
~          Encryption key:xxxxxxxxxxxxxxxxxxxx   Security mode:restricted
~          Power Management:off
~          Link Quality:0  Signal level:0  Noise level:0
~          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
~          Tx excessive retries:0  Invalid misc:333   Missed beacon:0

If you see, dhclient can see an access point, but, surprisingly this is
the mac address of the card.

If I try with:

"iwconfig nickname "puerto-lobo" key "my_wep_key" mode managed", I obtain:

Feb  5 21:49:04 localhost kernel: prism2: wlan0: operating mode changed
3 -> 2
Feb  5 21:49:04 localhost kernel: wifi0: LinkStatus=2 (Disconnected)
Feb  5 21:49:04 localhost kernel: wifi0: LinkStatus: BSSID=00:60:b3:68:f6:e0
Feb  5 21:49:18 localhost pumpd[4485]: PUMP: sending discover
Feb  5 21:49:18 localhost kernel: wifi0: TXEXC - status=0x0004
([Discon]) tx_control=000c
Feb  5 21:49:18 localhost kernel:    retry_count=0 tx_rate=0 fc=0x4108
(Data::0 ToDS)
Feb  5 21:49:18 localhost kernel:    A1=00:60:b3:68:f6:e0
A2=00:60:b3:68:f6:e0 A3=ff:ff:ff:ff:ff:ff A4=00:00:00:00:00:00
Feb  5 21:49:22 localhost kernel: wifi0: TXEXC - status=0x0004
([Discon]) tx_control=000c
Feb  5 21:49:22 localhost kernel:    retry_count=0 tx_rate=0 fc=0x4108
(Data::0 ToDS)
Feb  5 21:49:22 localhost kernel:    A1=00:60:b3:68:f6:e0
A2=00:60:b3:68:f6:e0 A3=ff:ff:ff:ff:ff:ff A4=00:00:00:00:00:00

I read, and try with no results, things how that:

----------- cut ----------------

http://64.233.167.104/search?q=cache:vag8tiieAqAJ:ibot.rikers.org/oe/20040531.html.gz+%22invalid+skb-%3Ecb+magic+(0x00000000,+expected+0xf08a36a2)%22&hl=es&client=firefox

12:53.43        Twiun   error is "wifi0: invalid skb->cb magic
(0x00000000, expected 0xf08a36a2)" whenever I try pinging
12:53.54        mithro  hostap is ALOT better then ornioco
12:54.03        mithro  anyway i'm off to bed
12:54.10        mithro  Twiun: good luck
12:54.21        Twiun   mithro: thanks :)
12:55.07        krypto  you're buidling from scratch? --- what kernel
version are you using?
12:55.47        Twiun   2.6.6 and hostap-driver v26
13:00.45        krypto  hmm, never worked on 2.6 though... but, most
likely skb->cb is not initialized properly to point to a priv data
13:02.17        krypto  or something is touching it in the network
stack, that it gets corrupted on the driver layer
13:03.04        krypto  montypython: you still there? what's your nsgmls
version?
13:03.33        krypto  i wanted to try gpe-image but i don't know why
its stuck with nsgmls
13:11.50        Twiun   Got it working!
13:12.07        Twiun   found a post about not configuring wifi0 as
that's the raw iface

------------ end of cut -----------------

I was look for "raw iface" and when I encounter it I try change this in
/etc/pcmcia/network:

---------- pcmcia network file --------

### http://lists.shmoo.com/pipermail/hostap/2003-November/004813.html
#
#if [ "$DEVICE" = "wifi0" ]; then
#  DEVICE="wlan0"
#fi

------- end of cut -----------

(Actually comment because it doesn't work)

I think that kernel tries to connect to wifi0 are incorrect but I don't
know to say kernel that correct interface is wlan0.

Last intent was with linux-wlan-ng and returning to orinoco_cs but
orinoco now send me that error:

Error for wireless request "Set Encode" (8B2A) :
SET failed on device eth1 ; Invalid argument.

when I make:

iwconfig nickname "puerto-lobo" key "my_wep_key"

Result is that I don't have wireless network here.

Any helpful ideas for me?

Thanks in advance and sorry for the large mail.

Salud y Revolución.

Lobo.


--
Libertad es poder elegir en cualquier momento. Ahora yo elijo GNU/Linux,
para no atar mis manos con las cadenas del soft propietario.
---------
Desde El Ejido, en Almería, usuario registrado linux #294013
http://www.counter.li.org



Reply to: