Subject: Re: ural device timeout on -current
To: dixie <dixieml@imap.cc>
From: dixie <dixieml@imap.cc>
List: current-users
Date: 10/24/2005 17:42:07
dixie wrote:

> Kouichirou Hiratsuka wrote:
>
>> Hello,
>>
>> At Fri, 14 Oct 2005 13:15:56 +0900,
>> FUKAUMI Naoki wrote:
>>  
>>
>>> At Wed, 17 Aug 2005 16:20:41 +0200,
>>> dixie wrote:
>>>   
>>>
>>>> Hi there, I got a BUFFALO WLI-U2-KG54-AI, rev 2.00/1.15 succesfully 
>>>> attached but when I try to assign an address, either manually or 
>>>> via dhclient it goes on timeout.
>>>> Here's the full dmesg output:
>>>>     
>>>
>>> <...snip...>
>>>   
>>>
>>>> ral0: timeout waiting for BBP/RF to wakeup
>>>>
>>>> # ifconfig ral0 inet 192.168.1.15
>>>> ifconfig: SIOCAIFADDR: Input/output error
>>>>
>>>> I'm on a 3.99.7 macppc machine.
>>>> Please to/cc me because I'm not subscribed to this list.
>>>> Thank you.
>>>>     
>>>
>>> I don't have WLI-U2-KG54-AI. Some devices listed in if_ural.c are not
>>> tested. Some devices may not be supported by (u)ral(4).
>>>
>>> I'll buy WLI-U2-KG54-AI soon and check it on my machine.
>>>   
>>
>> I bought this today.  It has a flash drive in order to install a
>> Windows device driver.  The flash drive can be disabled by the
>> switch on it.  If the flash drive is off, its device ID is changed
>> to 0x0067.  In this state, I can use it with the following patch.
>>
>> best regards.
>> -- 
>> Kouichirou Hiratsuka
>>   hira@po6.nsk.ne.jp
>>
>> --- usbdevs.orig    2005-10-20 00:42:35.000000000 +0900
>> +++ usbdevs    2005-10-20 00:42:50.000000000 +0900
>> @@ -1270,7 +1270,7 @@
>> product MELCO KB11        0x0044    WLI-USB-KB11 WLAN
>> product MELCO KG54YB        0x005e    WLI-U2-KG54-YB WLAN
>> product MELCO KG54        0x0066    WLI-U2-KG54 WLAN
>> -product MELCO KG54AI        0x006d    WLI-U2-KG54-AI WLAN
>> +product MELCO KG54AI        0x0067    WLI-U2-KG54-AI WLAN
>>
>> /* Metricom products */
>> product METRICOM RICOCHET_GS    0x0001    Ricochet GS
>>  
>>
> The device did not attach with the flash drive disabled so I kept it 
> enabled.
> Thank you, I'll try your patch as soon as possible :)
> Best regards
> -- 
> dixie
>
Thank you very much for the hint!
It works, now the device is attached and I can bring it up and configure 
all the parameters via ifconfig.
Anyway, it cannot associate, scanning trough wiconfig does not show any 
AP even if it's present.
Dhclient cannot find any lease even if dhcpd is running.
What procedure do you follow in order to associate?
Maybe I'm missing something so basilar that I cannot recall it :(
I'll post the full output if it would be of any use.
Thank you again :)