OESF Portables Forum
Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Angstrom & OpenZaurus => Topic started by: dare333 on June 27, 2005, 10:18:52 pm
-
I have reflashed several times the latest 3.5.3 OZ kernel on my SL-C3000. I can get the Symbol Wireless Networker I have to operate easily enough, but I can't get monitor or scanning to work at all. I have searched for a long time trying to find info on it, but most seems to be outdated. I have read elsewhere that people can get it to work, but they usually are using SL-C1000. Is there a trick to it? Any help would be great.
-
It would help if you gave some more information than "can't get monitor or scanning to work at all". Any error message? Any steps to reproduce the problem?
-
It would help if you gave some more information than "can't get monitor or scanning to work at all". Any error message? Any steps to reproduce the problem?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=86177\"][{POST_SNAPBACK}][/a][/div]
I load Wellenreiter. "Can't set interface 'eth0' into monitor mode: Invalid argument Continue with limited functionality?"
The "Rescan Neighbourhood" function in Wireless Configuration does not do anything.
ifconfig:
eth0 Link encap:Ethernet HWaddr 00:A0:F8:A0:5C:46
inet addr:192.168.2.206 Bcast:192.168.2.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:37 errors:0 dropped:0 overruns:0 frame:0
TX packets:37 errors:1 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:4835 (4.7 KiB) TX bytes:7611 (7.4 KiB)
Interrupt:135
iwconfig:
eth0 IEEE 802.11-DS ESSID:"werd" Nickname:"Prism I"
Mode:Managed Frequency:2.437 GHz Access Point: 0B:16:13:B1:31:38
Bit Rate:11 Mb/s Tx-Power=15 dBm
Retry limit:16 RTS thr:off Fragment thr=0 B
Encryption key:92B4-G324-F1AB-1170-B355-2319-62 Security mode:open
Power Management:off
Link Quality=28/92 Signal level=135/153 Noise level=107/153
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Also, if I take the CF card out and put it back in, it creates an eth0 and then puts the network card at eth1. If I do it again it will up the number again. I hope this is helpful.
-
Uh oh, that sounds odd. Please reboot without the card, then insert the card, and send us the complete 'logread' output.
-
ut (cmd=01 MMC_STAT=0x2142)
Jun 29 09:29:41 spitz user.warn kernel: pxa_sd_wait_id_response: responce time out (cmd=01 MMC_STAT=0x2142)
Jun 29 09:29:41 spitz user.warn kernel: pxa_sd_wait_id_response: responce time out (cmd=01 MMC_STAT=0x2142)
Jun 29 09:29:41 spitz user.warn kernel: pxa_sd_wait_id_response: responce time out (cmd=01 MMC_STAT=0x2142)
Jun 29 09:29:41 spitz user.warn kernel: pxa_sd_wait_id_response: responce time out (cmd=01 MMC_STAT=0x2142)
Jun 29 09:29:41 spitz user.warn kernel: pxa_sd_wait_id_response: responce time out (cmd=01 MMC_STAT=0x2142)
Jun 29 09:29:41 spitz user.warn kernel: pxa_sd_wait_id_response: responce time out (cmd=01 MMC_STAT=0x2142)
Jun 29 09:29:41 spitz user.warn kernel: pxa_sd_wait_id_response: responce time out (cmd=01 MMC_STAT=0x2142)
Jun 29 09:29:41 spitz user.warn kernel: pxa_sd_wait_id_response: responce time out (cmd=01 MMC_STAT=0x2142)
Jun 29 09:29:41 spitz user.warn kernel: pxa_sd_wait_id_response: responce time out (cmd=01 MMC_STAT=0x2142)
Jun 29 09:29:41 spitz user.warn kernel: pxa_sd_wait_id_response: responce time out (cmd=01 MMC_STAT=0x2142)
Jun 29 09:29:41 spitz user.warn kernel: x2142)
Jun 29 09:29:41 spitz user.warn kernel: pxa_sd_wait_id_response: responce time out (cmd=01 MMC_STAT=0x2142)
Jun 29 09:29:41 spitz user.warn kernel: pxa_sd_wait_id_response: responce time out (cmd=01 MMC_STAT=0x2142)
Jun 29 09:29:41 spitz user.warn kernel: pxa_sd_wait_id_response: responce time out (cmd=01 MMC_STAT=0x2142)
Jun 29 09:29:41 spitz user.warn kernel: pxa_sd_wait_id_response: responce time out (cmd=01 MMC_STAT=0x2142)
Jun 29 09:29:41 spitz user.warn kernel: pxa_sd_wait_id_response: responce time out (cmd=01 MMC_STAT=0x2142)
Jun 29 09:29:41 spitz user.warn kernel: pxa_sd_wait_id_response: responce time out (cmd=01 MMC_STAT=0x2142)
Jun 29 09:29:41 spitz user.warn kernel: pxa_sd_wait_id_response: responce time out (cmd=01 MMC_STAT=0x2142)
Jun 29 09:29:41 spitz user.warn kernel: pxa_sd_wait_id_response: responce time out (cmd=01 MMC_STAT=0x2142)
Jun 29 09:29:41 spitz user.warn kernel: pxa_sd_wait_id_response: responce time out (cmd=01 MMC_STAT=0x2142)
Jun 29 09:29:41 spitz user.warn kernel: pxa_sd_wait_id_response: responce time out (cmd=01 MMC_STAT=0x2142)
Jun 29 09:29:41 spitz user.warn kernel: pxa_sd_wait_id_response: responce time out (cmd=01 MMC_STAT=0x2142)
Jun 29 09:29:41 spitz user.warn kernel: pxa_sd_wait_id_response: responce time out (cmd=01 MMC_STAT=0x2142)
Jun 29 09:29:41 spitz user.warn kernel: pxa_sd_wait_id_response: responce time out (cmd=01 MMC_STAT=0x2142)
Jun 29 09:29:41 spitz user.warn kernel: pxa_sd_wait_id_response: responce time out (cmd=01 MMC_STAT=0x2142)
Jun 29 09:29:41 spitz user.warn kernel: pxa_sd_wait_id_response: responce time out (cmd=01 MMC_STAT=0x2142)
Jun 29 09:29:41 spitz user.warn kernel: pxa_sd_wait_id_response: responce time out (cmd=01 MMC_STAT=0x2142)
Jun 29 09:29:41 spitz user.warn kernel: pxa_sd_wait_id_response: responce time out (cmd=01 MMC_STAT=0x2142)
Jun 29 09:29:41 spitz user.warn kernel: pxa_sd_wait_id_response: responce time out (cmd=01 MMC_STAT=0x2142)
Jun 29 09:29:41 spitz user.warn kernel: pxa_sd_wait_id_response: responce time out (cmd=01 MMC_STAT=0x2142)
Jun 29 09:29:41 spitz user.warn kernel: pxa_sd_wait_id_response: responce time out (cmd=01 MMC_STAT=0x2142)
Jun 29 09:29:41 spitz user.warn kernel: pxa_sd_wait_id_response: responce time out (cmd=01 MMC_STAT=0x2142)
Jun 29 09:29:41 spitz user.warn kernel: pxa_sd_wait_id_response: responce time out (cmd=01 MMC_STAT=0x2142)
Jun 29 09:29:41 spitz user.warn kernel: pxa_sd_wait_id_response: responce time out (cmd=01 MMC_STAT=0x2142)
Jun 29 09:29:41 spitz user.warn kernel: pxa_sd_wait_id_response: responce time out (cmd=01 MMC_STAT=0x2142)
Jun 29 09:29:41 spitz user.warn kernel: SD Driver Initialized.
Jun 29 09:29:41 spitz user.warn kernel: sharp_mmcsd 0.30 13 Oct 2004
Jun 29 09:29:41 spitz user.warn kernel: pxa_sd_wait_response: responce time out (cmd=52 MMC_STAT=0x2142)
Jun 29 09:29:41 spitz user.warn kernel: pxa_sd_wait_response: responce time out (cmd=05 MMC_STAT=0x2142)
Jun 29 09:29:41 spitz user.warn kernel: [SD]-clustsize = 4000
Jun 29 09:29:41 spitz user.info kernel: mmcda: mmcda1
Jun 29 09:29:41 spitz user.info kernel: mmcda: mmcda1
Jun 29 09:29:41 spitz user.info kernel: usb.c: registered new driver usbdevfs
Jun 29 09:29:41 spitz user.info kernel: usb.c: registered new driver hub
Jun 29 09:29:41 spitz user.warn kernel: VFS: Can't find a Minix or Minix V2 filesystem on device 3c:01.
Jun 29 09:29:41 spitz user.info kernel: mmcda: mmcda1
Jun 29 09:29:41 spitz user.info kernel: mmcda: mmcda1
Jun 29 09:29:41 spitz user.info kernel: mmcda: mmcda1
Jun 29 09:29:41 spitz user.warn kernel: MINIX-fs: unable to read superblock
Jun 29 09:29:41 spitz user.info kernel: mmcda: mmcda1
Jun 29 09:29:41 spitz user.warn kernel: FAT: unable to read boot sector
Jun 29 09:29:41 spitz user.info kernel: mmcda: mmcda1
Jun 29 09:29:41 spitz user.warn kernel: EXT2-fs: unable to read superblock
Jun 29 09:29:41 spitz user.info kernel: mmcda: mmcda1
Jun 29 09:29:41 spitz user.err kernel: EXT3-fs: unable to read superblock
Jun 29 09:29:41 spitz user.info kernel: mmcda: mmcda1
Jun 29 09:29:41 spitz user.err kernel: EXT3-fs: unable to read superblock
Jun 29 09:29:41 spitz user.info kernel: mmcda: mmcda1
Jun 29 09:29:41 spitz user.warn kernel: EXT2-fs: unable to read superblock
Jun 29 09:29:41 spitz user.info kernel: mmcda: mmcda1
Jun 29 09:29:41 spitz user.err kernel: cramfs: wrong magic
Jun 29 09:29:41 spitz user.info kernel: mmcda: mmcda1
Jun 29 09:29:41 spitz user.warn kernel: MINIX-fs: unable to read superblock
Jun 29 09:29:41 spitz user.info kernel: mmcda: mmcda1
Jun 29 09:29:41 spitz user.warn kernel: FAT: unable to read boot sector
Jun 29 09:29:41 spitz user.info kernel: mmcda: mmcda1
Jun 29 09:29:41 spitz user.warn kernel: isofs_read_super: bread failed, dev=3c:02, iso_blknum=16, block=32
Jun 29 09:29:41 spitz user.info kernel: mmcda: mmcda1
Jun 29 09:29:41 spitz user.debug kernel: jffs2: attempt to mount non-MTD device 3c:02
Jun 29 09:29:41 spitz user.info kernel: mmcda: mmcda1
Jun 29 09:29:41 spitz user.warn kernel: MINIX-fs: unable to read superblock
Jun 29 09:29:41 spitz user.info kernel: mmcda: mmcda1
Jun 29 09:29:41 spitz user.warn kernel: FAT: unable to read boot sector
Jun 29 09:29:41 spitz user.info kernel: mmcda: mmcda1
Jun 29 09:29:41 spitz user.warn kernel: EXT2-fs: unable to read superblock
Jun 29 09:29:41 spitz user.info kernel: mmcda: mmcda1
Jun 29 09:29:41 spitz user.err kernel: EXT3-fs: unable to read superblock
Jun 29 09:29:41 spitz user.info kernel: mmcda: mmcda1
Jun 29 09:29:41 spitz user.err kernel: EXT3-fs: unable to read superblock
Jun 29 09:29:41 spitz user.info kernel: mmcda: mmcda1
Jun 29 09:29:41 spitz user.warn kernel: EXT2-fs: unable to read superblock
Jun 29 09:29:41 spitz user.info kernel: mmcda: mmcda1
Jun 29 09:29:41 spitz user.err kernel: cramfs: wrong magic
Jun 29 09:29:41 spitz user.info kernel: mmcda: mmcda1
Jun 29 09:29:41 spitz user.warn kernel: MINIX-fs: unable to read superblock
Jun 29 09:29:41 spitz user.info kernel: mmcda: mmcda1
Jun 29 09:29:41 spitz user.warn kernel: FAT: unable to read boot sector
Jun 29 09:29:41 spitz user.info kernel: mmcda: mmcda1
Jun 29 09:29:41 spitz user.warn kernel: isofs_read_super: bread failed, dev=3c:03, iso_blknum=16, block=32
Jun 29 09:29:41 spitz user.info kernel: mmcda: mmcda1
Jun 29 09:29:41 spitz user.debug kernel: jffs2: attempt to mount non-MTD device 3c:03
Jun 29 09:29:41 spitz user.info kernel: mmcda: mmcda1
Jun 29 09:29:41 spitz user.warn kernel: MINIX-fs: unable to read superblock
Jun 29 09:29:41 spitz user.info kernel: mmcda: mmcda1
Jun 29 09:29:41 spitz user.warn kernel: FAT: unable to read boot sector
Jun 29 09:29:41 spitz user.info kernel: mmcda: mmcda1
Jun 29 09:29:41 spitz user.warn kernel: EXT2-fs: unable to read superblock
Jun 29 09:29:41 spitz user.info kernel: mmcda: mmcda1
Jun 29 09:29:41 spitz user.err kernel: EXT3-fs: unable to read superblock
Jun 29 09:29:41 spitz user.info kernel: mmcda: mmcda1
Jun 29 09:29:41 spitz user.err kernel: EXT3-fs: unable to read superblock
Jun 29 09:29:41 spitz user.info kernel: mmcda: mmcda1
Jun 29 09:29:41 spitz user.warn kernel: EXT2-fs: unable to read superblock
Jun 29 09:29:41 spitz user.info kernel: mmcda: mmcda1
Jun 29 09:29:41 spitz user.err kernel: cramfs: wrong magic
Jun 29 09:29:41 spitz user.info kernel: mmcda: mmcda1
Jun 29 09:29:41 spitz user.warn kernel: MINIX-fs: unable to read superblock
Jun 29 09:29:41 spitz user.info kernel: mmcda: mmcda1
Jun 29 09:29:41 spitz user.warn kernel: FAT: unable to read boot sector
Jun 29 09:29:41 spitz user.info kernel: mmcda: mmcda1
Jun 29 09:29:41 spitz user.warn kernel: isofs_read_super: bread failed, dev=3c:04, iso_blknum=16, block=32
Jun 29 09:29:41 spitz user.info kernel: mmcda: mmcda1
Jun 29 09:29:41 spitz user.debug kernel: jffs2: attempt to mount non-MTD device 3c:04
Jun 29 09:29:41 spitz user.info kernel: IrDA: Registered device irda0
Jun 29 09:29:41 spitz user.notice root: SHARED [] [/dev/hda1]
Jun 29 09:29:41 spitz daemon.info hcid[892]: Bluetooth HCI daemon
Jun 29 09:29:41 spitz user.info kernel: BlueZ Core ver 2.4 Copyright © 2000,2001 Qualcomm Inc
Jun 29 09:29:41 spitz user.info kernel: Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>
Jun 29 09:29:42 spitz user.info kernel: BlueZ L2CAP ver 2.3 Copyright © 2000,2001 Qualcomm Inc
Jun 29 09:29:42 spitz user.info kernel: Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>
Jun 29 09:29:42 spitz daemon.info sdpd[899]: Bluetooth SDP daemon
Jun 29 09:29:42 spitz user.info kernel: BlueZ RFCOMM ver 1.1
Jun 29 09:29:42 spitz user.info kernel: Copyright © 2002 Maxim Krasnyansky <maxk@qualcomm.com>
Jun 29 09:29:42 spitz user.info kernel: Copyright © 2002 Marcel Holtmann <marcel@holtmann.org>
Jun 29 02:29:55 spitz user.warn qpe: qt_init() [949] - successfully entered daemon mode
Jun 29 09:31:27 spitz daemon.info cardmgr[835]: socket 0: LA4100 Spectrum24 CF WLAN Card
Jun 29 09:31:28 spitz daemon.info cardmgr[835]: executing: 'modprobe hermes 2>&1'
Jun 29 09:31:28 spitz daemon.info cardmgr[835]: + Using /lib/modules/2.4.20/net/hermes.o
Jun 29 09:31:28 spitz user.debug kernel: orinoco.c 0.13e (David Gibson <hermes@gibson.dropbear.id.au> and others)
Jun 29 09:31:28 spitz daemon.info cardmgr[835]: executing: 'modprobe orinoco 2>&1'
Jun 29 09:31:28 spitz daemon.info cardmgr[835]: + Using /lib/modules/2.4.20/net/orinoco.o
Jun 29 09:31:28 spitz user.debug kernel: eth0: Station identity 0021:0002:0002:0001
Jun 29 09:31:28 spitz user.debug kernel: eth0: Looks like a Symbol firmware version [F3.10-06] (parsing to 31006)
Jun 29 09:31:28 spitz user.debug kernel: eth0: Ad-hoc demo mode supported
Jun 29 09:31:28 spitz user.debug kernel: eth0: IEEE standard IBSS ad-hoc mode supported
Jun 29 09:31:28 spitz user.debug kernel: eth0: WEP supported, 104-bit key
Jun 29 09:31:28 spitz user.debug kernel: eth0: MAC address 0C:A3:C8:A0:3C:46
Jun 29 09:31:28 spitz user.debug kernel: eth0: Station name "Prism I"
Jun 29 09:31:28 spitz user.debug kernel: eth0: ready
Jun 29 09:31:28 spitz user.debug kernel: eth0: index 0x01: Vcc 3.3, irq 135, io 0xf6000000-0xf6000047
Jun 29 09:31:30 spitz daemon.info cardmgr[835]: executing: './network start eth0 2>&1'
Jun 29 09:31:30 spitz daemon.info cardmgr[835]: + Error for wireless request "Set Mode" (8B06) :
Jun 29 09:31:30 spitz daemon.info cardmgr[835]: + SET failed on device eth0 ; Invalid argument.
Jun 29 09:31:30 spitz local0.info udhcpc[1092]: udhcpc (v0.9.9-pre) started
Jun 29 09:31:30 spitz user.err udhcpc: pidfile_check: process 1092 exists (/var/run/udhcpc.eth0.pid)
Jun 29 09:31:30 spitz daemon.info cardmgr[835]: + pidfile_check: process 1092 exists (/var/run/udhcpc.eth0.pid)
Jun 29 09:31:30 spitz daemon.info cardmgr[835]: +
Jun 29 09:31:30 spitz local0.debug udhcpc[1092]: Sending discover...
Jun 29 09:31:32 spitz local0.debug udhcpc[1092]: Sending discover...
Jun 29 09:31:33 spitz local0.debug udhcpc[1092]: Sending select for 192.168.2.206...
Jun 29 09:31:33 spitz local0.info udhcpc[1092]: Lease of 192.168.2.206 obtained, lease time 86400
Jun 29 09:31:46 spitz authpriv.info dropbear[1123]: Child connection from 192.168.2.207:1639
Jun 29 09:32:17 spitz user.warn kernel: eth0: Undersized frame received (0 bytes)
-
Look good so far. What is 'iwpriv eth0' telling you? Does 'iwconfig eth0 mode monitor' work?
-
Look good so far. What is 'iwpriv eth0' telling you? Does 'iwconfig eth0 mode monitor' work?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=86294\"][{POST_SNAPBACK}][/a][/div]
There is this in the above which does not look right to me, and is delivering the same error as Wellenreiter.
Jun 29 09:31:30 spitz daemon.info cardmgr[835]: + Error for wireless request "Set Mode" (8B06) :
Jun 29 09:31:30 spitz daemon.info cardmgr[835]: + SET failed on device eth0 ; Invalid argument.
:
root@spitz:~# iwpriv eth0
eth0 Available private ioctl :
force_reset (8BE0) : set 0 & get 0
card_reset (8BE1) : set 0 & get 0
set_port3 (8BE2) : set 1 int & get 0
get_port3 (8BE3) : set 0 & get 1 int
set_preamble (8BE4) : set 1 int & get 0
get_preamble (8BE5) : set 0 & get 1 int
set_ibssport (8BE6) : set 1 int & get 0
get_ibssport (8BE7) : set 0 & get 1 int
root@spitz:~# iwconfig eth0 mode monitor
Error for wireless request "Set Mode" (8B06) :
SET failed on device eth0 ; Invalid argument.
-
Hmm... that looks like you're using a non-patched orinoco instead of the one we ship by default with OZ 3.5.3....
Oh Uh... I got it. Grrr, it's a bug in our kernel configuration. We enabled the in-kernel orinoco
I'll try to cook you an updated kernel when I have a chance.
-
Hmm... that looks like you're using a non-patched orinoco instead of the one we ship by default with OZ 3.5.3....
Oh Uh... I got it. Grrr, it's a bug in our kernel configuration. We enabled the in-kernel orinoco
I'll try to cook you an updated kernel when I have a chance.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=86350\"][{POST_SNAPBACK}][/a][/div]
That would be great! Thank you
-
Hmm... that looks like you're using a non-patched orinoco instead of the one we ship by default with OZ 3.5.3....
Oh Uh... I got it. Grrr, it's a bug in our kernel configuration. We enabled the in-kernel orinoco
I'll try to cook you an updated kernel when I have a chance.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=86350\"][{POST_SNAPBACK}][/a][/div]
Any news on this? If I just run the "Update" command from package manager, loading the WiFi driver causes the zaurus to lock up.
Thanks!