ts-7000
[Top] [All Lists]

[ts-7000] Re: wlan0 not coming up/iwconfig not working

To:
Subject: [ts-7000] Re: wlan0 not coming up/iwconfig not working
From: "Naubert" <>
Date: Fri, 23 Mar 2007 02:40:51 -0000

Hello.

I tried the zd.o driver from:

> ftp://oz.embeddedarm.com/wireless/zd1211/r83/zd.o

in my shipping kernel 2.4.26-ts11 in a 7200 and the IOGEAR USB WiFi is
not detected:

hub.c: new USB device not_pci-3, assigned address 8
usb.c: USB device 8 (vend/prod 0xace/0x1215) is not claimed by any
active driver

So I think that the problem still exists.  The driver is reported as:

zd1211 - http://zd1211.ath.cx/ - r83
Based on www.zydas.com.tw driver version 2.5.0.0
usb.c: registered new driver zd1211

and obviously no wlan0 device appear:

# ifconfig -a
:/# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:D0:69:40:82:83
          inet addr:192.168.1.138  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:39

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:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:560 (560.0 b)  TX bytes:560 (560.0 b)


Please advise,

Nas


--- In  Eddie Dawydiuk <> wrote:
>
> Hello,
>
> > I'm having the exactly the same problem as you and Patty with 2 brand
> > new TS7260 cards and IOGEAR USB wireles devices (purchased Feb
7,2007).
>
> The revision r83 driver that was on our FTP site was originally compiled
> for a TS-WIFIBOX/TS-7400. The current shipping TS-7400 kernel has a
> newer version of the wireless extensions in the kernel than the other
> TS-7xxx products. I've moved the previously compiled rev 83 driver to
> the r83/ts7400 folder
> (ftp://oz.embeddedarm.com/wireless/zd1211/r83/ts7400/zd.o) and
recompiled
> the rev 83 driver against the kernel that is currently shipping on all
> other TS-7xxx products. I've verified the reported problems as well as
> the driver currently on the FTP site is properly working on a TS-7xxx
> boards with the current shipping kernel.
>
> ftp://oz.embeddedarm.com/wireless/zd1211/r83/zd.o
>
> Let me know if you see any problems with the new driver.
>
> //Eddie
>
> > --- In  "Gonzalo A. de la Vega"
<gadelavega@> wrote:
> >>
> >> I had the same problem with my new TS-7260s. I just changed the
kernel
> >> to ts9, and everything works fine (you have to get zd.o from the
> >> ftp.embeddedarm.com/wireless/zd1211/r53/ directory, which has been
> >> built for ts9)
> >>
> >> Gonzalo
> >>
> >> --- In  "pattykirsch" <kirsch@> wrote:
> >>>
> >>> Did this get resolved?  I seem to be having the same problem on a
> >>> TS-7200 but this isn't doing it for me.
> >>>
> >>> Patty
> >>>
> >>> --- In  "Don W. Carr" <doncarr@> wrote:
> >>>>
> >>>> It worked for me on a 7260. Here is what I had that I think
> >> someone else
> >>>> posted before.  On the newer 7260, they might install more of the
> >>> modules by
> >>>> default.
> >>>>
> >>>> insmod usbcore
> >>>> insmod pcipool
> >>>> insmod usb-ohci
> >>>> insmod usb-ohci-ep93xx
> >>>> insmod scsi_mod
> >>>> insmod sd_mod
> >>>> insmod /path/to/zd.o
> >>>>
> >>>> ifconfig wlan0 up
> >>>> iwconfig wlan0 essid wappy
> >>>> ifconfig wlan0 192.168.0.99
> >>>> ping 192.168.0.5
> >>>>
> >>>>
> >>>>
> >>>> On 12/29/06, Tom <tl@> wrote:
> >>>>>
> >>>>>   Hmm, I am still stuck. Anyone have any suggestions? I
neglected to
> >>>>> mention that I'm using the included WIFI-G-USB option from
> >>>>> embeddedarm.com, an IOGear GWU-523. Has anyone else gotten this to
> >>> work
> >>>>> with a TS-7260?
> >>>>>
> >>>>> Tom
> >>>>>
> >>>>>
> >>>>> Tom McCarty wrote:
> >>>>>
> >>>>>> Hi all, I just bought a TS-7260 a couple of days ago, and I
> >>> can't get
> >>>>>> the wireless interface to work. The USB drivers seem to be
> >>> working, but
> >>>>>> the iwconfig command doesn't seem to do anything, and I can't
find
> >>>>>> anything in the archives with this particular problem.
> >>>>>>
> >>>>>> A full log of my interaction from bootup is included below, but
> >>> I think
> >>>>>> the salient part is this, where iwconfig doesn't seem to do
> >>> anything,
> >>>>>> and looks like it's reading from a corrupted data structure.
> >>>>>>
> >>>>>> $ iwconfig wlan0 essid pleasework
> >>>>>> $ iwconfig wlan0 mode ad-hoc
> >>>>>> $ ifconfig wlan0 192.168.0.2
> >>>>>> $ iwconfig
> >>>>>> lo no wireless extensions.
> >>>>>>
> >>>>>> eth0 no wireless extensions.
> >>>>>>
> >>>>>> wlan0 \· �x¼*îâ ESSID:off/any Nickname:""
> >>>>>> NWID:off/any Mode:Managed Frequency:2.412 GHz
> >>>>>> Access Point: FF:7F:B4:5C:AD:2A Bit Rate:1 Mb/s Tx-Power=off
> >>>>>> Sensitivity=2147482204/3
> >>>>>> Retry:off RTS thr=2432 B Fragment thr:off
> >>>>>> Encryption key:<too big>
> >>>>>> 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:0 Missed beacon:0
> >>>>>>
> >>>>>> I've tried "$iwconfig wlan0 nick test", too, but no iwconfig
> >>> line seems
> >>>>>> to change the output of just "$iwconfig" except to specify the
> >>>>>> interface, in which case the output is slightly different:
> >>>>>> $ iwconfig wlan0
> >>>>>> wlan0 � â?? ESSID:off/any Nickname:""
> >>>>>> NWID:off/any Mode:Managed Frequency:2.412 GHz
> >>>>>> Access Point: Not-Associated Bit Rate:1 Mb/s Tx-Power=off
> >>>>>> Sensitivity:0/3
> >>>>>> Retry:off RTS thr=2432 B Fragment thr:off
> >>>>>> Encryption key:<too big>
> >>>>>> 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:0 Missed beacon:0
> >>>>>>
> >>>>>>> From my as-shipped system, here's what I have done to it:
> >>>>>>
> >>>>>> uploaded zd.o to /root from
> >>> ftp://ftp.embeddedarm.com/wireless/zd1211
> >>>>>> <ftp://ftp.embeddedarm.com/wireless/zd1211>
> >>>>>> uploaded iwconfig,iwlist, iwspy to /usr/bin from
> >>>>>> ftp://ftp.embeddedarm.com/wireless/wireless_tools
> >>>>>> <ftp://ftp.embeddedarm.com/wireless/wireless_tools>
> >>>>>> uploaded libiw.so.28 to /lib from
> >>>>>> ftp://ftp.embeddedarm.com/wireless/wireless_tools
> >>>>>> <ftp://ftp.embeddedarm.com/wireless/wireless_tools>
> >>>>>>
> >>>>>> I'm following the instructions in the Linux Arm guide v2.2,
> >>> however, the
> >>>>>> zd.o at
> >>>>>>
ftp://ftp.embeddedarm.com/ts-arm-linux-cd/binaries/ts-modules/zd.o
> >>>>>>
> >> <ftp://ftp.embeddedarm.com/ts-arm-linux-cd/binaries/ts-modules/zd.o>
> >>>>>> is for ts10, and wouldn't work with my ts11 system, so I got a
> >> more
> >>>>>> recent version from another location on the web site.
According to
> >>>>>> iwconfig --version, it should work, but obviously isn't.
> >> Anyone have
> >>>>>> suggestions?
> >>>>>>
> >>>>>> TIA,
> >>>>>>
> >>>>>> Tom
> >>>>>> -----
> >>>>>>
> >>>>>> Technologic Systems TS-LINUX/arm 7.0
> >>>>>> ts7200 login: root
> >>>>>> login[81]: root login on `ttyAM0'
> >>>>>>
> >>>>>> BusyBox v1.00-rc2 (2004.08.05-21:44+0000) Built-in shell (ash)
> >>>>>> Enter 'help' for a list of built-in commands.
> >>>>>>
> >>>>>> $ insmod usbcore
> >>>>>> Using /lib/modules/2.4.26-ts11/kernel/drivers/usb/usbcore.o
> >>>>>> usb.c: registered new driver usbdevfs
> >>>>>> usb.c: registered new driver hub
> >>>>>> $ insmod pcipool
> >>>>>> Using /lib/modules/2.4.26-ts11/kernel/arch/arm/common/pcipool.o
> >>>>>> $ insmod usb-ohca
> >>>>>> insmod: usb-ohca.o: no module by that name found
> >>>>>> $ insmod usb-ohci
> >>>>>> Using /lib/modules/2.4.26-ts11/kernel/drivers/usb/host/usb-ohci.o
> >>>>>> $ insmod usb-ohci-ep93xx
> >>>>>> Using
> >>> /lib/modules/2.4.26-ts11/kernel/drivers/usb/host/usb-ohci-ep93xx.o
> >>>>>> usb-ohci.c: USB OHCI at membase 0xe0020000, IRQ 56
> >>>>>> usb.c: new USB bus registered, assigned bus number 1
> >>>>>> hub.c: USB hub found
> >>>>>> hub.c: 3 ports detected
> >>>>>> $ hub.c: new USB device not_pci-3, assigned address 2
> >>>>>> usb.c: USB device 2 (vend/prod 0xace/0x1211) is not claimed
by any
> >>>>>> active driver
> >>>>>> .
> >>>>>> insmod scsi_mod
> >>>>>> Using /lib/modules/2.4.26-ts11/kernel/drivers/scsi/scsi_mod.o
> >>>>>> SCSI subsystem driver Revision: 1.00
> >>>>>> $ insmod sd_mod
> >>>>>> Using /lib/modules/2.4.26-ts11/kernel/drivers/scsi/sd_mod.o
> >>>>>> $ insmod zd.o
> >>>>>> Using zd.o
> >>>>>> zd1211 - http://zd1211.ath.cx/ <http://zd1211.ath.cx/> - r83
> >>>>>> Based on www.zydas.com.tw driver version 2.5.0.0
> >>>>>> usb.c: registered new driver zd1211
> >>>>>> Release Ver = 4802
> >>>>>> EEPORM Ver = 4330
> >>>>>> PA type: 0
> >>>>>> AiroHa AL2230RF
> >>>>>> AllowedChannel = 000107ff
> >>>>>> Region:16
> >>>>>> $ ifconfig wlan0 up
> >>>>>> $ iwconfig wlan0 essid pleasework
> >>>>>> $ ifconfig wlan0 192.168.0.2
> >>>>>> $ iwconfig wlan0 mode ad-hoc
> >>>>>> $ iwconfig
> >>>>>> lo no wireless extensions.
> >>>>>>
> >>>>>> eth0 no wireless extensions.
> >>>>>>
> >>>>>> wlan0 \· �x¼*îâ ESSID:off/any Nickname:""
> >>>>>> NWID:off/any Mode:Managed Frequency:2.412 GHz
> >>>>>> Access Point: FF:7F:B4:5C:AD:2A Bit Rate:1 Mb/s Tx-Power=off
> >>>>>> Sensitivity=2147482204/3
> >>>>>> Retry:off RTS thr=2432 B Fragment thr:off
> >>>>>> Encryption key:<too big>
> >>>>>> 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:0 Missed beacon:0
> >>>>>> $ iwconfig --version
> >>>>>> iwconfig Wireless-Tools version 28
> >>>>>> Compatible with Wireless Extension v11 to v20.
> >>>>>>
> >>>>>> Kernel Currently compiled with Wireless Extension v16.
> >>>>>>
> >>>>>> wlan0 Recommend Wireless Extension v13 or later,
> >>>>>> Currently compiled with Wireless Extension v18.
> >>>>>>
> >>>>>> $ iwconfig wlan0
> >>>>>> wlan0 � â?? ESSID:off/any Nickname:""
> >>>>>> NWID:off/any Mode:Managed Frequency:2.412 GHz
> >>>>>> Access Point: Not-Associated Bit Rate:1 Mb/s Tx-Power=off
> >>>>>> Sensitivity:0/3
> >>>>>> Retry:off RTS thr=2432 B Fragment thr:off
> >>>>>> Encryption key:<too big>
> >>>>>> 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:0 Missed beacon:0
> >>>>>>
> >>>>>> $
> >>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Dr. Don W. Carr
> >>>> J. G. Montenegro 2258
> >>>> Guadalajara, Mexico
> >>>> +52-333-630-0704
> >>>> +52-333-836-4500 ext 2930
> >>>>
> >>>
> >>
> >
> >
> >
> >
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
> >
>





Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/ts-7000/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/ts-7000/join
    (Yahoo! ID required)

<*> To change settings via email:
    
    

<*> To unsubscribe from this group, send an email to:
    

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/


<Prev in Thread] Current Thread [Next in Thread>
Admin

Disclaimer: Neither Andrew Taylor nor the University of NSW School of Computer and Engineering take any responsibility for the contents of this archive. It is purely a compilation of material sent by many people to the birding-aus mailing list. It has not been checked for accuracy nor its content verified in any way. If you wish to get material removed from the archive or have other queries about the archive e-mail Andrew Taylor at this address: andrewt@cse.unsw.EDU.AU