Asus Wl-167g On Pdaxrom?

[kkazakov13]

I recently bought this wifi usb card. When plugged in, I can see the following messages:

Code: [Select]

May 11 09:03:54 /etc/hotplug/usbh.agent: arguments () env (OLDPWD=/etc/hotplug PATH=/bin:/sbin:/usr/sbin:/usr/bin ACTION=load PWD=/etc/hotplug SHLVL=1 HOME=/ INTERFACE=monitor _=/usr/bin/env)
May 11 09:03:54 /etc/hotplug/usbh.agent: LOAD ...
May 11 09:03:54 /etc/hotplug/usbh.agent: LOAD done.
May 11 09:03:54 /sbin/hotplug: arguments (usb) env (ACTION=add DEBUG=kernel OLDPWD=/ HOME=/ DEVFS=/proc/bus/usb PATH=/bin:/sbin:/usr/sbin:/usr/bin TYPE=9/0/0 PRODUCT=0/0/0 PWD=/etc/hotplug DEVICE=/proc/bus/usb/001/001)
May 11 09:03:54 /sbin/hotplug: invoke /etc/hotplug/usb.agent ()
May 11 09:03:55 /etc/hotplug/usb.agent: Setup usbcore for USB product 0/0/0
May 11 09:03:55 /etc/hotplug/usb.agent: Setup usbcore for USB product 0/0/0
May 11 09:03:56 /sbin/hotplug: arguments (usb) env (ACTION=add DEBUG=kernel OLDPWD=/ HOME=/ DEVFS=/proc/bus/usb PATH=/bin:/sbin:/usr/sbin:/usr/bin TYPE=0/0/0 INTERFACE=255/255/255 PRODUCT=b05/1723/1 PWD=/etc/hotplug DEVICE=/proc/bus/usb/001/003)
May 11 09:03:56 /sbin/hotplug: invoke /etc/hotplug/usb.agent ()
May 11 09:03:56 /etc/hotplug/usb.agent: ... no modules for USB product b05/1723/1
lsusb produces:

Code: [Select]

Bus 001 Device 001: ID 0000:0000
Bus 001 Device 003: ID 0b05:1723 ASUSTek Computer, Inc.
I'm with 2.4.20 (default beta3 kernel). Anyone with ideas which kernel modules I need, and if it's not compiled, what's the best way to do it?

[Meanie]

I recently bought this wifi usb card. When plugged in, I can see the following messages:

Code: [Select]

May 11 09:03:54 /etc/hotplug/usbh.agent: arguments () env (OLDPWD=/etc/hotplug PATH=/bin:/sbin:/usr/sbin:/usr/bin ACTION=load PWD=/etc/hotplug SHLVL=1 HOME=/ INTERFACE=monitor _=/usr/bin/env)
May 11 09:03:54 /etc/hotplug/usbh.agent: LOAD ...
May 11 09:03:54 /etc/hotplug/usbh.agent: LOAD done.
May 11 09:03:54 /sbin/hotplug: arguments (usb) env (ACTION=add DEBUG=kernel OLDPWD=/ HOME=/ DEVFS=/proc/bus/usb PATH=/bin:/sbin:/usr/sbin:/usr/bin TYPE=9/0/0 PRODUCT=0/0/0 PWD=/etc/hotplug DEVICE=/proc/bus/usb/001/001)
May 11 09:03:54 /sbin/hotplug: invoke /etc/hotplug/usb.agent ()
May 11 09:03:55 /etc/hotplug/usb.agent: Setup usbcore for USB product 0/0/0
May 11 09:03:55 /etc/hotplug/usb.agent: Setup usbcore for USB product 0/0/0
May 11 09:03:56 /sbin/hotplug: arguments (usb) env (ACTION=add DEBUG=kernel OLDPWD=/ HOME=/ DEVFS=/proc/bus/usb PATH=/bin:/sbin:/usr/sbin:/usr/bin TYPE=0/0/0 INTERFACE=255/255/255 PRODUCT=b05/1723/1 PWD=/etc/hotplug DEVICE=/proc/bus/usb/001/003)
May 11 09:03:56 /sbin/hotplug: invoke /etc/hotplug/usb.agent ()
May 11 09:03:56 /etc/hotplug/usb.agent: ... no modules for USB product b05/1723/1
lsusb produces:

Code: [Select]

Bus 001 Device 001: ID 0000:0000
Bus 001 Device 003: ID 0b05:1723 ASUSTek Computer, Inc.
I'm with 2.4.20 (default beta3 kernel). Anyone with ideas which kernel modules I need, and if it's not compiled, what's the best way to do it?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=161023\"][{POST_SNAPBACK}][/a][/div]

you need to setup a gcc 2.95.3 cross compiler with 2.4.20 kernel headers and then compile rt2570 module


or try this one
 [ Invalid Attachment ]

[kkazakov13]

The driver loaded OK, lsmod says it's unused, the log shows the same messages. No other changes. I've put rt73.bin and rt73sta.dat in /etc/pcmcia/firmware/ but since there it's nothing to load them ... I don't see anything changes at all

It's not even half-part detected ...

lsusb -v produces this:

Code: [Select]

Bus 001 Device 005: ID 0b05:1723 ASUSTek Computer, Inc.
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0x0b05 ASUSTek Computer, Inc.
  idProduct          0x1723
  bcdDevice            0.01
  iManufacturer           1 Ralink
  iProduct                2 802.11 bg WLAN
  iSerial                 0
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           32
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x80
    MaxPower              300mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               none
          Usage Type               Data
        wMaxPacketSize     0x0040  bytes 64 once
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               none
          Usage Type               Data
        wMaxPacketSize     0x0040  bytes 64 once
        bInterval               0
  Language IDs: (length=4)
     0409 English(US)

[Meanie]

i guess this means you will need to get yourself cross compiler build....

[kkazakov13]

What this will help ... if i build the same module, what's the difference?

[Meanie]

What this will help ... if i build the same module, what's the difference?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=161043\"][{POST_SNAPBACK}][/a][/div]

well, it all depends on how good your cross compiler is, ie buggy or stable cross compiler. there is differences between 2.95.3 and 2.95.2, so try any of those variations. plus it may also depend on certain kernel headers and applied patches for those as well as the version of the module code....

[kkazakov13]

Crap  I tested it also on my Slackware box with 2.6.21 kernel, and didn't worked out-of-the-box. The problem is that everyone suggests differently named kernel module and i tried few and non of them worked