headers
Joerg Albert | 3 Nov 2002 22:28
Picon
Picon

Re: Problems with MA101 and Redhat 9 and Ibm r40 :)

Hi R52 (strange realname anyway),

On Sun, 2 Nov 2003, R52 wrote:

> [root <at> localhost root]# dmesg
> at76c503.c: wlan0: state 6 -> 1 (SCANNING)
> at76c503.c: wlan0 BSS table (curr=00000000, new=00000000):
> at76c503.c: 0xd75acd00: bssid 00:80:c8:ad:22:0d channel 6 ssid PBHOUSE
> (5042484F555345) capa x0041 rates 82 84 8B 96 AC rssi 21 link 0 noise 0
> at76c503.c: wlan0 BSS table (curr=00000000, new=00000000):
> at76c503.c: 0xd75acd00: bssid 00:80:c8:ad:22:0d channel 6 ssid PBHOUSE
> (5042484F555345) capa x0041 rates 82 84 8B 96 AC rssi 21 link 0 noise 0
> at76c503.c: wlan0: state 1 -> 6 (JOINING)
> at76c503.c: wlan0 find_matching_bss: returned 00000000
> at76c503.c: wlan0: state 6 -> 1 (SCANNING)
> at76c503.c: wlan0 BSS table (curr=00000000, new=00000000):

> sorry about the length it all repeats anyway!
two repetitions would have been enough :-( (save bandwidth!)

You have misconfigured your adapter, please look at the iwconfig parameter
or post the syslog param lines (assuming you used debug=0x100003 for
at76c503) from the start.

/Jörg
Permalink | Reply | 0 comments |
headers
Joerg Albert | 8 Nov 2002 23:23
Picon
Picon

Re: v0.11beta5 patch

Hi Anders,

On Sat, 8 Nov 2003, Anders Karlsson wrote:

> I sat down with the CVS nightly drop (currently v0.11beta5) and tried to
> use it a few days back. I could not get the wlan0 interface working with
> that code. I posted to the mailinglist about the problems.
>
> Then I started looking at the code, and I talked to someone a bit
> quickly about it, and they gave me an idea to try. So today I tested the
> beta5 driver with my small tweak to it, and although I am getting odd
> messages in the syslog when loading the driver:
>
> Nov  8 16:15:39 tor insmod: Using
> /lib/modules/2.4.23-pre6aa3/kernel/drivers/usb/at76c503.o
> Nov  8 16:15:39 tor insmod: Symbol version prefix ''
> Nov  8 16:15:39 tor insmod: Using
> /lib/modules/2.4.23-pre6aa3/kernel/drivers/usb/at76c503-rfmd.o
> Nov  8 16:15:39 tor kernel: usbdevfs: USBDEVFS_CONTROL failed dev 4 rqt
> 128 rq 6 len 18 ret -32
> Nov  8 16:15:39 tor /etc/hotplug/usb.agent[1373]: cannot get config
> descriptor: Broken pipe
> ..
> The driver now actually works and lets me use the wlan0 interface as
> before with the beta4 driver (that I hacked in a static HZ value into).
>
> Please find my patch attached.

thanks a lot for the patch! Sure, my change initialized
module_usbdfu.reset_delay too late (after it got used in usbdfu).
(Continue reading)

Permalink | Reply | 0 comments |
headers
Joerg Albert | 8 Nov 2002 23:29
Picon
Picon

Re: No device with WLL013

Hi Dieter,

On Sat, 8 Nov 2003 E.-D.Klinkenberg <at> t-online.de wrote:

> nach ein paar Wochen und einem Suse update auf 9.0 habe ich heute noch
> einmal versucht den USB-Atmel Treiber zu aktivieren (heutige CVS-Version).
> USB-Adapter Yakumo (DLink) WLL013
>
> Ich bekomme dabei folgendes REPRODUZIERBARE Verhalten:
>
> (1) Ich stecke den USB-Stecker des Adapters ein und warte bis zum beep des
> hot-plug von SUSE, dann war es das, der Rechner HAENGT total !!!
> (2) Ich gebe bei nunmehr noch eingestecktem USB-Adapter einen
> hardware-interrupt(Knopf) und lasse das System wieder hochfahren.
> Ergebnis: Alles i.O. der Adapter laesst sich konfigurieren und arbeitet
> klaglos.

list's language is English, therefore a summary for the English readers:
- SuSE 9.0, 0.11beta5 driver version
- device gets plugged in, hotplug beeps and systems hangs
- after reset everything works fine (I assume the device remained
  plugged-in).

Dieter, please try the 0.11beta6 - just checked-in should be avail.
tomorrow. There was a bug in the last patch for the variable HZ.

HTH
Jörg.
Permalink | Reply | 0 comments |

Gmane