What's wrong if wlan0 device is not reacting?

What's wrong if wlan0 device is not reacting?

[lynx.abraxas]

Hello!


I'm  desperately  trying  to get a micronet SP907GK V5 (USB 1.1 WLAN-Stick) to
run under openSuSE 10.3.

lsusb tells me the manufacturer is Realtek rtl8187 so  I  compiled,  installed
and modprobed rtl8187 for the 2.6.22.5 kernel.

The module loads and iwconfig lists wlan0 as wireless device. wmaster0 is also
created. I could not find any info on what wmaster0 is for. Some say it  is  a
hint  for  malfunction of the driver. I did configure the device with Yast and
also by hand (setting essid and key with iwconfig and using dhcpcd or ifconfig
with static local ip) but had no success when pinging the router.

Micronet does not list my device as linux compatible but the support says they
don't have any devices that run under linux although the FAQ  list  a  few.  A
similar  one SP907BB is said to work under linux but it seems not to be on the
market.

Well any help or hint on how to get my device working are very appreciated.

Thanks
Lynx


PS: I'm not a list member.


part of dmesg:


rtl8187: no version for "eeprom_93cx6_multiread" found: kernel tainted.
wmaster0: Selected rate control algorithm 'simple'
phy0: hwaddr 00:11:3b:0a:fc:ac, rtl8187 V1 + rtl8225z2
usbcore: registered new interface driver rtl8187
.
.
.
usb 1-2: USB disconnect, address 5
usb 1-2: new full speed USB device using uhci_hcd and address 6
usb 1-2: new device found, idVendor=0bda, idProduct=8187
usb 1-2: new device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-2: Product: RTL8187_Wireless_LAN_Adapter
usb 1-2: Manufacturer: Manufacturer_Realtek_RTL8187_
usb 1-2: SerialNumber: 00113B0AFCAC
usb 1-2: configuration #1 chosen from 1 choice
wmaster0: Selected rate control algorithm 'simple'
phy2: hwaddr 00:11:3b:0a:fc:ac, rtl8187 V1 + rtl8225z2
ADDRCONF(NETDEV_UP): wlan0: link is not ready


___________________________________________


iwconfig
lo        no wireless extensions.

wmaster0  no wireless extensions.

wlan0     IEEE 802.11g  ESSID:"WLAN"
          Mode:Managed  Frequency:2.412 GHz  Access Point: Not-Associated
          Retry min limit:7   RTS thr:off   Fragment thr=2346 B
          Encryption key:foo_key
          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

____________________________________________

lsusb -v -d 0bda:8187


Bus 001 Device 006: ID 0bda:8187 Realtek Semiconductor Corp.
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0x0bda Realtek Semiconductor Corp.
  idProduct          0x8187
  bcdDevice            1.00
  iManufacturer           1 Manufacturer_Realtek_RTL8187_
  iProduct                2 RTL8187_Wireless_LAN_Adapter
  iSerial                 3 00113B0AFCAC
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           39
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          4 Wireless Network Card
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass         0 (Defined at Interface level)
      bInterfaceSubClass      0
      bInterfaceProtocol      0
      iInterface              5 Bulk-IN,Bulk-OUT,Bulk-OUT
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x03  EP 3 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
Device Status:     0x0000
  (Bus Powered)

Re: What's wrong if wlan0 device is not reacting?

[Will Dyson]

On Dec 6, 2007 12:08 PM,  <lynx.abraxas@freenet.de> wrote:

> I'm  desperately  trying  to get a micronet SP907GK V5 (USB 1.1 WLAN-Stick) to
> run under openSuSE 10.3.
>
> lsusb tells me the manufacturer is Realtek rtl8187 so  I  compiled,  installed
> and modprobed rtl8187 for the 2.6.22.5 kernel.

You might want to mention where you got the source for the rtl8187
module that you compiled. Git checkout? Tarball from a website?

This driver is included in the 2.6.23 kernel, so you may want to try that.

> The module loads and iwconfig lists wlan0 as wireless device. wmaster0 is also
> created. I could not find any info on what wmaster0 is for. Some say it  is  a
> hint  for  malfunction of the driver. I did configure the device with Yast and
> also by hand (setting essid and key with iwconfig and using dhcpcd or ifconfig
> with static local ip) but had no success when pinging the router.

Fortunately, those who say the presence of the wmaster0 is a problem
are wrong. It is completely normal.

Your iwconfig output reveals that the device is not associated, so
naturally you will not be able to ping the router.

Also, you seem to imply that your network uses a WEP key (as opposed
to WPA), but please make sure.

Other thoughts:

Can you scan with the device? You will need to set the interface up
(ifconfig wlan0 up) before scanning.

When configuring the device manually with a WEP key, you will need to
make sure that setting the essid is the last step. Setting the essid
and then the key will not work.

-- 
Will Dyson

Re: What's wrong if wlan0 device is not reacting?

[lynx.abraxas]

On 06/12/07 13:52:25, Will Dyson wrote:


Thank You very much Will for Your quick answer.


> On Dec 6, 2007 12:08 PM,  <lynx.abraxas@freenet.de> wrote:
>
>  >  I'm   desperately   trying   to get a micronet SP907GK V5 (USB 1.1 WLAN-
Stick) to
> > run under openSuSE 10.3.
> >
> > lsusb tells me the  manufacturer  is  Realtek  rtl8187  so   I   compiled,
installed
> > and modprobed rtl8187 for the 2.6.22.5 kernel.
>
> You might want to mention where you got the source for the rtl8187
> module that you compiled. Git checkout? Tarball from a website?

I    mixed    things   a   bit   up.   I   compiled   rtl8187   from   realtek
(http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=16&PFid=14&Level=5&Conn=4)
on SuSE 10.2.
But I found no source that compiles under SuSE 10.3 which has a kernel > 2.6.19 where there is no config.h any more. So I used rtl8187-kmp-default-20070806_2.6.22.5_31-2.i586.rpm from ftp://ftp5.gwdg.de/pub/opensuse/distribution/10.3/repo/oss/suse/i586/ which was recommended in a thread concerning micronet USB-WLAN as well (which SP907 was'n mentioned). I also installed rt2x00... from the SuSE DVD. compat-wireless-2.6.tar.bz2 did not compile, which I thought would be the best choise. 


>
> This driver is included in the 2.6.23 kernel, so you may want to try that.

I'm  not sure if it is possible at all to switch to a different kernel version
in SuSE but I'll give it a test on my LFS-laptop.

>
> > The module loads and iwconfig lists wlan0 as wireless device. wmaster0  is
also
>  >  created.  I could not find any info on what wmaster0 is for. Some say it
is  a
> > hint  for  malfunction of the driver. I did configure the device with Yast
and
>  >  also  by  hand  (setting essid and key with iwconfig and using dhcpcd or
ifconfig
> > with static local ip) but had no success when pinging the router.
>
> Fortunately, those who say the presence of the wmaster0 is a problem
> are wrong. It is completely normal.

What's it for the wmaster0? Do I have to configure it as well?

>
> Your iwconfig output reveals that the device is not associated, so
> naturally you will not be able to ping the router.

This seems to be the problem. It does not catch the channel  of  my  WLAN  nor
does it help to set the frequency directly.


>
> Also, you seem to imply that your network uses a WEP key (as opposed
> to WPA), but please make sure.

Yes WEP for the time I'm here at my parents house because (though less secure)
my good old flashed orinoco card seems not to be able to handel WPA. The Stick
is supposed to be abled to do both WEP and WPA.

>
> Other thoughts:
>
> Can you scan with the device? You will need to set the interface up
> (ifconfig wlan0 up) before scanning.

No,  scanning  doesn't work either. Also "ifconfig wlan0 up" takes a long time
to finish  compared to other devices I have worked with. It yields the "wlan0:
link is not ready" message.
iwlist wlan0 scan gives: wlan0 No scan results

>
> When configuring the device manually with a WEP key, you will need to
> make sure that setting the essid is the last step. Setting the essid
> and then the key will not work.

I tried both an none worked.
Is  it  possible,  though  the  driver  catches the device and I don't get any
error-messages, that the Stick cannot be used under linux?


Thanks for any further help or hints
Lynx

Re: What's wrong if wlan0 device is not reacting?

[Luis R. Rodriguez]

On Dec 6, 2007 4:48 PM,  <lynx.abraxas@freenet.de> wrote:

> > lsusb tells me the  manufacturer  is  Realtek  rtl8187  so   I   compiled, installed
> > and modprobed rtl8187 for the 2.6.22.5 kernel.

CC'ing those who worked on that driver.

> compat-wireless-2.6.tar.bz2 did not compile, which I thought would be the best choise.

Please try today's release, last night's release was broken due to
zd1211rw-mac80211 --> zd1211rw move, among other things. Let me know
how it goes and what kernel you are using.

> What's it for the wmaster0?

wmaster0 is an internal master device used only by mac80211. It serves
as a holder for all interfaces we have, and represent the underlying
hardware. For example, when TXing your wlan0 STA interface will
actually add IEEE-802.11 header data to a frame with just Ethernet
headers, and then pass it down to the master device for actual
transmission using the low level drivers. Anyway, your wlan0 is an
interface, in your case a STA interface, this is the real guy you
would be configuring. The idea with is to be able to support multiple
interfaces at the same time using the same wireless card (say an AP
and a STA).

> Do I have to configure it as well?

No, if we could we would hide that from users, I believe there may be
patch coming for that soon.

(Dan:)

Using compat-wireless-2.6 I get my wmaster0 as 'eth3' actually and I
think that's making network manager angry (my wlan0 is actually
wlan0_rename too).

> > Your iwconfig output reveals that the device is not associated, so
> > naturally you will not be able to ping the router.
>
> This seems to be the problem. It does not catch the channel  of  my  WLAN  nor
> does it help to set the frequency directly.

I believe what Will was trying to tell you is that:

ADDRCONF(NETDEV_UP): wlan0: link is not ready

indicates to us that your wireless interface was not yet associated.

> No,  scanning  doesn't work either. Also "ifconfig wlan0 up" takes a long time
> to finish  compared to other devices I have worked with. It yields the "wlan0:
> link is not ready" message.
> iwlist wlan0 scan gives: wlan0 No scan results

Best thing to do is to try to get you to use the latest driver, we'll
be able to help a lot better that way. You can try wireless-2.6.git
tree yourself or we can try to get the compat-wireless-2.6 package
working for you.

> I tried both an none worked.
> Is  it  possible,  though  the  driver  catches the device and I don't get any
> error-messages, that the Stick cannot be used under linux?

Well lets find out, I believe it should be supported and working with
the current drivers.

  Luis

Re: What's wrong if wlan0 device is not reacting?

[Andrea Merello]

> > > lsusb tells me the  manufacturer  is  Realtek  rtl8187  so   I   compiled, installed
> > > and modprobed rtl8187 for the 2.6.22.5 kernel.

Can you please tell us which version of RF frontend and MAC processor
do you have?
You can see it in the dmesg output. I need the line where it talks about rtl8225

> > Also "ifconfig wlan0 up" takes a long time
> > to finish  compared to other devices I have worked with.

This is OK. Especially earlier version of the rtl8187 MAC need a quite
long procedure to turn on. It is not symptom of any problem.

> > iwlist wlan0 scan gives: wlan0 No scan results

Should the scan find a lot of APs or just one ? Are you close to any
AP? If you have other working cards can you please provide us a
indicative measure of AP signal strength? Is it possible that the
sensitivity of the card is not enough to find the AP? on which channel
is the AP?

> > Is  it  possible,  though  the  driver  catches the device and I don't get any
> > error-messages, that the Stick cannot be used under linux?

If the device is a rtl818L, and it is likely to be, since the driver
catches it, then it should work. If it doesn't not then it is probably
a bug. rtl8187B is not supported, but it should not be catched by the
driver (should have different USB id).

Oh, do you have an USB port 1.x or 2.0 ?

Thanks
Andrea

Re: What's wrong if wlan0 device is not reacting?

[Will Dyson]

On Dec 6, 2007 8:14 PM, Luis R. Rodriguez <mcgrof@gmail.com> wrote:

> Using compat-wireless-2.6 I get my wmaster0 as 'eth3' actually and I
> think that's making network manager angry (my wlan0 is actually
> wlan0_rename too).

You've got an old set of udev network device rename rules. The master
interface has the same MAC address as the real interface, and it is
created first. So the old udev rule (which only keys on the MAC
address) renames it to eth3. Then the real interface is created, udev
sees that it has already renamed an interface with that MAC and gives
it the wlan0_rename name.

If you delete the generated rename rules, it should create the correct
ones on the next boot. Alternately, you could add a ATTRS{type}="1"
selector to your current rule. Debian puts these autogenerated udev
rules in /etc/udev/rules.d/z25_persistent-net.rules. Other
distributions may vary slightly.

-- 
Will Dyson

Re: What's wrong if wlan0 device is not reacting?

[lynx.abraxas]

On 06/12/07 20:14:11, Luis R. Rodriguez wrote:
> On Dec 6, 2007 4:48 PM,  <lynx.abraxas@freenet.de> wrote:
>
>  >  >  lsusb  tells  me  the   manufacturer   is   Realtek   rtl8187  so   I
compiled, installed
> > > and modprobed rtl8187 for the 2.6.22.5 kernel.
>
> CC'ing those who worked on that driver.
>
> > compat-wireless-2.6.tar.bz2 did not compile, which I thought would be  the
best choise.
>
> Please try today's release, last night's release was broken due to
> zd1211rw-mac80211 --> zd1211rw move, among other things. Let me know
> how it goes and what kernel you are using.

I'm  now  trying to get the device working on my LFS with 2.6.23.9 which seems
to be a bit to new. My other kernel 2.6.21.5 a bit too old:(
Well the current compat-wireless-2.6.tar.bz2 does not compile through  either.
Even with make -k rtl8187.ko is not created. make stops with:


make
make -C /lib/modules/2.6.23.9/build M=/home/lynx/compat-wireless-2.6 modules
make[1]: Entering directory `/usr/src/linux-2.6.23.9'
  CC [M]  /home/lynx/compat-wireless-2.6/drivers/net/wireless/b43/main.o
In file included from /home/lynx/compat-wireless-2.6/drivers/net/wireless/b43/main.c:44:
/home/lynx/compat-wireless-2.6/drivers/net/wireless/b43/b43.h:783:3: error: #error "Using neither DMA nor PIO? Confused..."
/home/lynx/compat-wireless-2.6/drivers/net/wireless/b43/main.c: In function 'b43_interrupt_tasklet':
/home/lynx/compat-wireless-2.6/drivers/net/wireless/b43/main.c:1451: error: implicit declaration of function 'b43_using_pio'
/home/lynx/compat-wireless-2.6/drivers/net/wireless/b43/main.c: In function 'b43_one_core_attach':
/home/lynx/compat-wireless-2.6/drivers/net/wireless/b43/main.c:3857: error: 'modparam_pio' undeclared (first use in this function)
/home/lynx/compat-wireless-2.6/drivers/net/wireless/b43/main.c:3857: error: (Each undeclared identifier is reported only once
/home/lynx/compat-wireless-2.6/drivers/net/wireless/b43/main.c:3857: error: for each function it appears in.)
make[4]: *** [/home/lynx/compat-wireless-2.6/drivers/net/wireless/b43/main.o] Error 1
make[3]: *** [/home/lynx/compat-wireless-2.6/drivers/net/wireless/b43] Error 2
make[2]: *** [/home/lynx/compat-wireless-2.6/drivers/net/wireless] Error 2
make[1]: *** [_module_/home/lynx/compat-wireless-2.6] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.23.9'
make: *** [modules] Error 2

> > No,  scanning  doesn't work either. Also "ifconfig wlan0 up" takes a long time
> > to finish  compared to other devices I have worked with. It yields the "wlan0:
> > link is not ready" message.
> > iwlist wlan0 scan gives: wlan0 No scan results
> 
> Best thing to do is to try to get you to use the latest driver, we'll
> be able to help a lot better that way. You can try wireless-2.6.git
> tree yourself or we can try to get the compat-wireless-2.6 package
> working for you.

Is git different from compat-wireless-2.6 package? It seems like it is a daily
snapshot.

>
> > I tried both an none worked.
> > Is  it  possible,  though  the  driver  catches the device and I don't get
any
> > error-messages, that the Stick cannot be used under linux?
>
> Well lets find out, I believe it should be supported and working with
> the current drivers.
>

That  would be great. I got a lot of things running with my LFS but this WLAN-
Stick is a hard one again...

Lynx

Re: What's wrong if wlan0 device is not reacting?

[Luis R. Rodriguez]

On Dec 7, 2007 3:17 PM,  <lynx.abraxas@freenet.de> wrote:
> On 06/12/07 20:14:11, Luis R. Rodriguez wrote:
> > On Dec 6, 2007 4:48 PM,  <lynx.abraxas@freenet.de> wrote:
> >
> >  >  >  lsusb  tells  me  the   manufacturer   is   Realtek   rtl8187  so   I
> compiled, installed
> > > > and modprobed rtl8187 for the 2.6.22.5 kernel.
> >
> > CC'ing those who worked on that driver.
> >
> > > compat-wireless-2.6.tar.bz2 did not compile, which I thought would be  the
> best choise.
> >
> > Please try today's release, last night's release was broken due to
> > zd1211rw-mac80211 --> zd1211rw move, among other things. Let me know
> > how it goes and what kernel you are using.
>
> I'm  now  trying to get the device working on my LFS with 2.6.23.9 which seems
> to be a bit to new. My other kernel 2.6.21.5 a bit too old:(
> Well the current compat-wireless-2.6.tar.bz2 does not compile through  either.
> Even with make -k rtl8187.ko is not created. make stops with:
>
>
> make
> make -C /lib/modules/2.6.23.9/build M=/home/lynx/compat-wireless-2.6 modules
> make[1]: Entering directory `/usr/src/linux-2.6.23.9'
>   CC [M]  /home/lynx/compat-wireless-2.6/drivers/net/wireless/b43/main.o
> In file included from /home/lynx/compat-wireless-2.6/drivers/net/wireless/b43/main.c:44:
> /home/lynx/compat-wireless-2.6/drivers/net/wireless/b43/b43.h:783:3: error: #error "Using neither DMA nor PIO? Confused..."
> /home/lynx/compat-wireless-2.6/drivers/net/wireless/b43/main.c: In function 'b43_interrupt_tasklet':
> /home/lynx/compat-wireless-2.6/drivers/net/wireless/b43/main.c:1451: error: implicit declaration of function 'b43_using_pio'
> /home/lynx/compat-wireless-2.6/drivers/net/wireless/b43/main.c: In function 'b43_one_core_attach':
> /home/lynx/compat-wireless-2.6/drivers/net/wireless/b43/main.c:3857: error: 'modparam_pio' undeclared (first use in this function)
> /home/lynx/compat-wireless-2.6/drivers/net/wireless/b43/main.c:3857: error: (Each undeclared identifier is reported only once
> /home/lynx/compat-wireless-2.6/drivers/net/wireless/b43/main.c:3857: error: for each function it appears in.)
> make[4]: *** [/home/lynx/compat-wireless-2.6/drivers/net/wireless/b43/main.o] Error 1
> make[3]: *** [/home/lynx/compat-wireless-2.6/drivers/net/wireless/b43] Error 2
> make[2]: *** [/home/lynx/compat-wireless-2.6/drivers/net/wireless] Error 2
> make[1]: *** [_module_/home/lynx/compat-wireless-2.6] Error 2
> make[1]: Leaving directory `/usr/src/linux-2.6.23.9'
> make: *** [modules] Error 2

I just fixed this. I'll e-mail once I propagate the tarball.

> > > No,  scanning  doesn't work either. Also "ifconfig wlan0 up" takes a long time
> > > to finish  compared to other devices I have worked with. It yields the "wlan0:
> > > link is not ready" message.
> > > iwlist wlan0 scan gives: wlan0 No scan results
> >
> > Best thing to do is to try to get you to use the latest driver, we'll
> > be able to help a lot better that way. You can try wireless-2.6.git
> > tree yourself or we can try to get the compat-wireless-2.6 package
> > working for you.
>
> Is git different from compat-wireless-2.6 package? It seems like it is a daily
> snapshot.

Its a daily snapshot. Cron'd for at 06:10am CET.

  Luis

Re: What's wrong if wlan0 device is not reacting?

[lynx.abraxas]

On 07/12/07 11:21:53, Andrea Merello wrote:
> > > > lsusb tells me the  manufacturer  is  Realtek  rtl8187  so   I   compiled, installed
> > > > and modprobed rtl8187 for the 2.6.22.5 kernel.
> 
> Can you please tell us which version of RF frontend and MAC processor
> do you have?
> You can see it in the dmesg output. I need the line where it talks about rtl8225

Dec  7 21:05:53 drago kernel: wmaster0: Selected rate control algorithm 'simple'
Dec  7 21:05:54 drago kernel: phy0: hwaddr 00:11:3b:0a:fc:ac, rtl8187 V1 + rtl8225z2
Dec  7 21:05:54 drago kernel: usbcore: registered new interface driver rtl8187


> > > iwlist wlan0 scan gives: wlan0 No scan results
>
> Should the scan find a lot of APs or just one ? Are you close to any
> AP? If you have other working cards can you please provide us a
> indicative measure of AP signal strength? Is it possible that the
> sensitivity of the card is not enough to find the AP? on which channel
> is the AP?

Scan could find more than one but here is what my orinoco card yields:

iwlist eth1 scan
eth1      Scan completed :
          Cell 01 - Address: 00:04:0E:8F:19:0D
                    ESSID:"home-WLAN"
                    Mode:Master
                    Frequency:2.462 GHz (Channel 11)
                    Signal level:-56 dBm  Noise level:-104 dBm
                    Encryption key:on


The  AP  is  just  5 meters away and the signal is close to best. I'm not sure
though if I have to set the sensitivity of  the  device  with  iwconfig  wlan0
txpower ???
What configuration should I do anyway? I do:

modprobe rtl8187
iwconfig wlan0 key foo_key
iwconfig wlan0 essid home-WLAN
ifconfig wlan0 192.168.2.23 or dhcpcd -d wlan0

lsmod|sort
Module                  Size  Used by
ac97_bus                2432  1 snd_ac97_codec
arc4                    2176  2
blkcipher               6660  1 ecb
cfg80211                7176  1 mac80211
crypto_algapi          14720  3 arc4,ecb,cryptomgr
cryptomgr               3712  0
ecb                     3712  2
eeprom_93cx6            2432  1 rtl8187
ehci_hcd               34572  0
evdev                  10368  1
fat                    50588  1 vfat
floppy                 56100  0
hermes                  7424  2 orinoco_cs,orinoco
mac80211              123012  2 rtl8187,rc80211_simple
mousedev               12808  1
nls_base                7680  2 vfat,fat
orinoco                41620  1 orinoco_cs
orinoco_cs             15876  1
pcmcia                 38676  5 orinoco_cs
pcmcia_core            38800  4 orinoco_cs,pcmcia,yenta_socket,rsrc_nonstatic
rc80211_simple          4480  1
rsrc_nonstatic         11136  1 yenta_socket
rtc                    13336  0
rtl8187                34304  0
scsi_mod              100360  2 sd_mod,usb_storage
sd_mod                 24720  0
sis900                 22656  0
snd                    50532  5 snd_intel8x0m,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer
snd_ac97_codec         94112  2 snd_intel8x0m,snd_intel8x0
snd_intel8x0           32924  0
snd_intel8x0m          17548  0
snd_page_alloc         10376  3 snd_intel8x0m,snd_intel8x0,snd_pcm
snd_pcm                76552  3 snd_intel8x0m,snd_intel8x0,snd_ac97_codec
snd_timer              22788  1 snd_pcm
soundcore               8160  1 snd
usb_storage            37248  0
usbcore               135832  5 rtl8187,usb_storage,ehci_hcd,usbhid
usbhid                 21540  0
vfat                   13440  0
yenta_socket           25868  6


>
>  >  > Is  it  possible,  though  the  driver  catches the device and I don't
get any
> > > error-messages, that the Stick cannot be used under linux?
>
> If the device is a rtl818L, and it is likely to be, since the driver
> catches it, then it should work. If it doesn't not then it is probably
> a bug. rtl8187B is not supported, but it should not be catched by the
> driver (should have different USB id).
>
> Oh, do you have an USB port 1.x or 2.0 ?

On my LFS I have 2.0 but on the old PC where it is supposed to do its job  has
only  USB1.1. It's the reason why I bought this device. It is supposed to work
with USB1.1.

Thanks
Lynx

PS: I'm in the list now.

Re: What's wrong if wlan0 device is not reacting?

[Luis R. Rodriguez]

On Dec 7, 2007 3:25 PM, Luis R. Rodriguez <mcgrof@gmail.com> wrote:

> > make
> > make -C /lib/modules/2.6.23.9/build M=/home/lynx/compat-wireless-2.6 modules
> > make[1]: Entering directory `/usr/src/linux-2.6.23.9'
> >   CC [M]  /home/lynx/compat-wireless-2.6/drivers/net/wireless/b43/main.o
> > In file included from /home/lynx/compat-wireless-2.6/drivers/net/wireless/b43/main.c:44:
> > /home/lynx/compat-wireless-2.6/drivers/net/wireless/b43/b43.h:783:3: error: #error "Using neither DMA nor PIO? Confused..."
> > /home/lynx/compat-wireless-2.6/drivers/net/wireless/b43/main.c: In function 'b43_interrupt_tasklet':
> > /home/lynx/compat-wireless-2.6/drivers/net/wireless/b43/main.c:1451: error: implicit declaration of function 'b43_using_pio'
> > /home/lynx/compat-wireless-2.6/drivers/net/wireless/b43/main.c: In function 'b43_one_core_attach':
> > /home/lynx/compat-wireless-2.6/drivers/net/wireless/b43/main.c:3857: error: 'modparam_pio' undeclared (first use in this function)
> > /home/lynx/compat-wireless-2.6/drivers/net/wireless/b43/main.c:3857: error: (Each undeclared identifier is reported only once
> > /home/lynx/compat-wireless-2.6/drivers/net/wireless/b43/main.c:3857: error: for each function it appears in.)
> > make[4]: *** [/home/lynx/compat-wireless-2.6/drivers/net/wireless/b43/main.o] Error 1
> > make[3]: *** [/home/lynx/compat-wireless-2.6/drivers/net/wireless/b43] Error 2
> > make[2]: *** [/home/lynx/compat-wireless-2.6/drivers/net/wireless] Error 2
> > make[1]: *** [_module_/home/lynx/compat-wireless-2.6] Error 2
> > make[1]: Leaving directory `/usr/src/linux-2.6.23.9'
> > make: *** [modules] Error 2
>
> I just fixed this. I'll e-mail once I propagate the tarball.

OK give it a shot again, I just regenerated it.

http://linuxwireless.org/download/compat-wireless-2.6/compat-wireless-2.6.tar.bz2

  Luis

Re: What's wrong if wlan0 device is not reacting?

[Luis R. Rodriguez]

On Dec 7, 2007 2:21 PM, Will Dyson <will.dyson@gmail.com> wrote:
> On Dec 6, 2007 8:14 PM, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
>
> > Using compat-wireless-2.6 I get my wmaster0 as 'eth3' actually and I
> > think that's making network manager angry (my wlan0 is actually
> > wlan0_rename too).
>
> You've got an old set of udev network device rename rules. The master
> interface has the same MAC address as the real interface, and it is
> created first. So the old udev rule (which only keys on the MAC
> address) renames it to eth3. Then the real interface is created, udev
> sees that it has already renamed an interface with that MAC and gives
> it the wlan0_rename name.
>
> If you delete the generated rename rules, it should create the correct
> ones on the next boot. Alternately, you could add a ATTRS{type}="1"
> selector to your current rule. Debian puts these autogenerated udev
> rules in /etc/udev/rules.d/z25_persistent-net.rules. Other
> distributions may vary slightly.

Thanks I've added this here:

http://linuxwireless.org/en/users/Download#Knownissues

Also, clarified the master interface here:

http://linuxwireless.org/en/developers/Documentation/mac80211#Themasterdevicewmaster0

Please feel free to expand.

  Luis

Re: What's wrong if wlan0 device is not reacting?

[lynx.abraxas]

Checked  this  morning  but I'm still getting errors there. Could I be missing
some configuration of the build?


  CC [M]  /home/lynx/compat-wireless-2.6/drivers/net/wireless/b43/main.o
In file included from /home/lynx/compat-wireless-2.6/drivers/net/wireless/b43/main.c:44:
/home/lynx/compat-wireless-2.6/drivers/net/wireless/b43/b43.h:783:3: error: #error "Using neither DMA nor PIO? Confused..."
/home/lynx/compat-wireless-2.6/drivers/net/wireless/b43/main.c: In function 'b43_interrupt_tasklet':
/home/lynx/compat-wireless-2.6/drivers/net/wireless/b43/main.c:1451: error: implicit declaration of function 'b43_using_pio'
/home/lynx/compat-wireless-2.6/drivers/net/wireless/b43/main.c: In function 'b43_one_core_attach':
/home/lynx/compat-wireless-2.6/drivers/net/wireless/b43/main.c:3857: error: 'modparam_pio' undeclared (first use in this function)
/home/lynx/compat-wireless-2.6/drivers/net/wireless/b43/main.c:3857: error: (Each undeclared identifier is reported only once
/home/lynx/compat-wireless-2.6/drivers/net/wireless/b43/main.c:3857: error: for each function it appears in.)
make[4]: *** [/home/lynx/compat-wireless-2.6/drivers/net/wireless/b43/main.o] Error 1
make[3]: *** [/home/lynx/compat-wireless-2.6/drivers/net/wireless/b43] Error 2
make[2]: *** [/home/lynx/compat-wireless-2.6/drivers/net/wireless] Error 2
make[1]: *** [_module_/home/lynx/compat-wireless-2.6] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.23.9'
make: *** [modules] Error 2


I'll  be  off  my  parents  house till the next year. I'll be able to test the
compilation but not the function with the device  till  January.  I'll  reprot
back then.


Thanks  very much for the help so far. Would be great to get the thing running
some time.

Lynx

Re: What's wrong if wlan0 device is not reacting?

[lynx.abraxas]

On 08/12/07 08:44:02, lynx.abraxas@freenet.de wrote:
> Checked  this  morning  but I'm still getting errors there. Could I be missing
> some configuration of the build?
> 

Found  the problem: I seem to have gotten a cached tarball which didn't differ
at all. Downloading it with wget got the new one  and  that  compiles  without
problems under 2.6.23.9. I'm sorry for the fuzz.
Well testing the device with the new drivers will have to wait untill January.


Till then, mary Christmas and a happy New Year.
Lynx

Re: What's wrong if wlan0 device is not reacting?

[Luis R. Rodriguez]

On Dec 10, 2007 12:15 PM,  <lynx.abraxas@freenet.de> wrote:
> On 08/12/07 08:44:02, lynx.abraxas@freenet.de wrote:
> > Checked  this  morning  but I'm still getting errors there. Could I be missing
> > some configuration of the build?
> >
>
> Found  the problem: I seem to have gotten a cached tarball which didn't differ
> at all. Downloading it with wget got the new one  and  that  compiles  without
> problems under 2.6.23.9. I'm sorry for the fuzz.
> Well testing the device with the new drivers will have to wait untill January.
>
>
> Till then, mary Christmas and a happy New Year.

Heh, thanks, I was about to reply that I tested the build with the
same exact kernel. Please do get back with test results :)

  Luis

Re: What's wrong if wlan0 device is not reacting?

[lynx.abraxas]

On 10/12/07 14:26:24, Luis R. Rodriguez wrote:
> On Dec 10, 2007 12:15 PM,  <lynx.abraxas@freenet.de> wrote:
> > On 08/12/07 08:44:02, lynx.abraxas@freenet.de wrote:
> > > Checked  this  morning  but I'm still getting errors there. Could I be missing
> > > some configuration of the build?
> > >
> >
> > Found  the problem: I seem to have gotten a cached tarball which didn't differ
> > at all. Downloading it with wget got the new one  and  that  compiles  without
> > problems under 2.6.23.9. I'm sorry for the fuzz.
> > Well testing the device with the new drivers will have to wait untill January.


I tried the tar-ball from 25-1-2008 and the device still didn't work.
So    I    got    the   USB-Hama-Stick   which   has   a   ralink   chip   and
http://www.ralinktech.com offers a driver for linux (rt73.ko) with which I got
everything to work nicely.

Thanks for the help, support and for the wirless drivers.
Lynx