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

Re: rt2500usb



Am Samstag, 3. Januar 2009 schrieb Ivo van Doorn:
> On Friday 02 January 2009, Rainer Dorsch wrote:
> > Am Freitag, 2. Januar 2009 schrieb Ivo van Doorn:
> > > On Wednesday 31 December 2008, Rainer Dorsch wrote:
> > > > Ivo,
> > > >
> > > > I am testing an
> > > >
> > > > blackbox:~# lsusb |grep Link
> > > > Bus 008 Device 002: ID 2001:3c00 D-Link Corp. [hex] DWL-G122 802.11g
> > > > rev. B1 [ralink]
> > > > blackbox:~#
> > > >
> > > > on a Debian Lenny system (to be released as Debian 5.0 very soon).
> > > >
> > > > Lenny comes with an 2.6.26.8 kernel.
> > > >
> > > > I get lots of timeouts in when I try to connect to the AP. I found
> > > > your commit
> > > >
> > > > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=co
> > > >mmit ;h=d06193f311102b2c990ec5f66b470ea49ecc73a4
> > > >
> > > > though I can not (I have not yet enough git expertise) tell, if that
> > > > commit went into 2.6.26.8. If not that would probably explain the
> > > > problem I see.
> > >
> > > According tohttp://kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.27
> > > the patch went into 2.6.27 so that means it probably won't be present
> > > in the 2.6.26 kernel series.
> >
> > Many thanks for the quick reply. With a 2.6.27 kernel (which is
> > unfortunately not in the upcoming Debian lenny release) the timeouts went
> > away and the stick worked flawless.
> >
> > From you commit comments, I get the impression that applying the patch to
> > a 2.6.26 kernel should be pretty save. Do you think the patch can break
> > anything when applied to a 2.6.26 kernel, is the risk of unexpected side
> > effects very low?
>
> No, the patch shoul be very save to be applied to 2.6.26.
>

Ivo,

even with the patch

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit ;h=d06193f311102b2c990ec5f66b470ea49ecc73a4

my rt2570 is still dead on a Debian 2.6.26 kernel, whereas it works flawless 
on a Debian 2.6.27 kernel on the same machine. Is there anything else you 
could imagine which should be patched?

lsusb output:

Bus 008 Device 004: ID 2001:3c00 D-Link Corp. [hex] DWL-G122 802.11g rev. B1 
[ralink]
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0x2001 D-Link Corp. [hex]
  idProduct          0x3c00 DWL-G122 802.11g rev. B1 [ralink]
  bcdDevice            0.01
  iManufacturer           1
  iProduct                2
  iSerial                 0
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           32
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x80
      (Bus Powered)
    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     0x0200  1x 512 bytes
        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     0x0200  1x 512 bytes
        bInterval               0
can't get device qualifier: Operation not permitted
can't get debug descriptor: Operation not permitted
cannot read device status, Operation not permitted (1)

syslog for 2.6.26 with patch:

Jan 18 18:07:53 blackbox kernel: [  686.402861] usb 8-2: new high speed USB 
device using ehci_hcd and address 4
Jan 18 18:07:53 blackbox kernel: [  686.811833] usb 8-2: configuration #1 
chosen from 1 choice
Jan 18 18:07:53 blackbox kernel: [  686.922369] phy2: Selected rate control 
algorithm 'pid'
Jan 18 18:07:53 blackbox kernel: [  686.922369] Registered led device: 
rt2500usb-phy2:radio
Jan 18 18:07:53 blackbox kernel: [  686.925175] usb 8-2: New USB device found, 
idVendor=2001, idProduct=3c00
Jan 18 18:07:53 blackbox kernel: [  686.925178] usb 8-2: New USB device 
strings: Mfr=1, Product=2, SerialNumber=0
Jan 18 18:07:53 blackbox kernel: [  686.925180] usb 8-2: Product: 802.11g WLAN 
Adapter
Jan 18 18:07:53 blackbox kernel: [  686.925181] usb 8-2: Manufacturer: ANI
Jan 18 18:07:53 blackbox kernel: [  687.131725] ADDRCONF(NETDEV_UP): wlan0: 
link is not ready
Jan 18 18:07:54 blackbox dhclient: Internet Systems Consortium DHCP Client 
V3.1.1
Jan 18 18:07:54 blackbox dhclient: Copyright 2004-2008 Internet Systems 
Consortium.
Jan 18 18:07:54 blackbox dhclient: All rights reserved.
Jan 18 18:07:54 blackbox dhclient: For info, please visit 
http://www.isc.org/sw/dhcp/
Jan 18 18:07:54 blackbox dhclient:
Jan 18 18:07:54 blackbox dhclient: wmaster0: unknown hardware address type 801
Jan 18 18:07:55 blackbox kernel: [  689.060811] wlan0: Initial auth_alg=0
Jan 18 18:07:55 blackbox kernel: [  689.060815] wlan0: authenticate with AP 
00:18:4d:89:3f:38
Jan 18 18:07:55 blackbox dhclient: wmaster0: unknown hardware address type 801
Jan 18 18:07:55 blackbox dhclient: Listening on LPF/wlan0/00:13:46:98:2b:fd
Jan 18 18:07:55 blackbox dhclient: Sending on   LPF/wlan0/00:13:46:98:2b:fd
Jan 18 18:07:55 blackbox dhclient: Sending on   Socket/fallback
Jan 18 18:07:55 blackbox kernel: [  689.301771] wlan0: authenticate with AP 
00:18:4d:89:3f:38
Jan 18 18:07:55 blackbox dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 
port 67
Jan 18 18:07:56 blackbox kernel: [  689.503095] wlan0: authenticate with AP 
00:18:4d:89:3f:38
Jan 18 18:07:56 blackbox kernel: [  689.703488] wlan0: authentication with AP 
00:18:4d:89:3f:38 timed out
Jan 18 18:08:00 blackbox dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 
port 67
Jan 18 18:08:05 blackbox dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 
port 67
Jan 18 18:08:06 blackbox kernel: [  700.583261] wlan0: authentication frame 
received from 00:18:4d:89:3f:38, but not in authenticate state - ignored
Jan 18 18:08:06 blackbox kernel: [  700.586759] wlan0: Initial auth_alg=0
Jan 18 18:08:06 blackbox kernel: [  700.586763] wlan0: authenticate with AP 
00:18:4d:89:3f:38
Jan 18 18:08:06 blackbox kernel: [  700.594015] wlan0: Initial auth_alg=0
Jan 18 18:08:06 blackbox kernel: [  700.594020] wlan0: authenticate with AP 
00:18:4d:89:3f:38
Jan 18 18:08:06 blackbox kernel: [  700.790672] wlan0: authenticate with AP 
00:18:4d:89:3f:38
Jan 18 18:08:06 blackbox kernel: [  700.990680] wlan0: authenticate with AP 
00:18:4d:89:3f:38
Jan 18 18:08:07 blackbox kernel: [  701.190669] wlan0: authentication with AP 
00:18:4d:89:3f:38 timed out

Thanks,
Rainer

-- 
Rainer Dorsch
Lärchenstr. 6
D-72135 Dettenhausen
07157-734133
email: rdorsch@web.de
jabber: rdorsch@jabber.org
GPG Fingerprint: 5966 C54C 2B3C 42CC 1F4F  8F59 E3A8 C538 7519 141E
Full GPG key: http://pgp.mit.edu/


Reply to: