Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 02 Mar 2011 12:01:19 -0500
From:      Etienne Robillard <erob@gthcfoundation.org>
To:        John Baldwin <jhb@freebsd.org>
Cc:        freebsd-current@freebsd.org, bschmidt@freebsd.org
Subject:   Re: urtw0: could not allocate USB transfers
Message-ID:  <4D6E77DF.1030605@gthcfoundation.org>
In-Reply-To: <201103021147.50506.jhb@freebsd.org>
References:  <4D66C4CB.1060207@2egos.de> <201102251331.37589.bschmidt@freebsd.org> <4D6E699A.2020405@gthcfoundation.org> <201103021147.50506.jhb@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 02/03/11 11:47 AM, John Baldwin wrote:
> On Wednesday, March 02, 2011 11:00:26 am Etienne Robillard wrote:
>   
>> On 02/25/2011 07:31, Bernhard Schmidt wrote:
>>     
>>> On Friday, February 25, 2011 12:47:12 Etienne Robillard wrote:
>>>    
>>>       
>>>> On 25/02/11 06:18 AM, Bernhard Schmidt wrote:
>>>>      
>>>>         
>>>>> On Friday, February 25, 2011 11:03:04 Etienne Robillard wrote:
>>>>>
>>>>>        
>>>>>           
>>>>>> On 25/02/11 04:11 AM, Bernhard Schmidt wrote:
>>>>>>
>>>>>>          
>>>>>>             
>>>>>>> On Thursday, February 24, 2011 21:51:23 joseph wrote:
>>>>>>>
>>>>>>>
>>>>>>>            
>>>>>>>               
>>>>>>>> Hello,
>>>>>>>>
>>>>>>>> i decided to get my laptop wlan via usb because my internal device 
>>>>>>>>                 
> isn't
>   
>>>>>>>> supported yet.
>>>>>>>> The usb device is a logilink WL0006 unit its vendorid is 0x0bda and 
>>>>>>>>                 
> the
>   
>>>>>>>> productid says 0x8187.
>>>>>>>> My search results say that this device depends on a RTL8187 chipset.
>>>>>>>> I tried both, load the kernel module at boot time and compile kernel
>>>>>>>> withe urtw, but i get the same output at dmesg
>>>>>>>>
>>>>>>>> device_attach: urtw0 attach returned 6
>>>>>>>> urtw0:<vendor 0x0bda product 0x8187, class 0/0, rev 2.00/2.00, addr 
>>>>>>>>                 
> 2>
>   
>>>>>>>> on usbus3
>>>>>>>> urtw0: could not allocate USB transfers, err=USB_ERR_NO_PIPE
>>>>>>>> device_attach: urtw0 attach returned 6
>>>>>>>>
>>>>>>>> im running FreeBSD 8.1-RELEASE-p2 amd64.
>>>>>>>>
>>>>>>>> What might be the reason for this error?
>>>>>>>> Thanks for all hints.
>>>>>>>>
>>>>>>>>
>>>>>>>>              
>>>>>>>>                 
>>>>>>> Well, I have no clue about USB.. but this smells like one of the
>>>>>>> endpoints is 'not there'. At least I can't find any reference to
>>>>>>> it in the Linux driver. Wanna give attached patch a shot?
>>>>>>>
>>>>>>>
>>>>>>>            
>>>>>>>               
>>>>>> Hi Bernard,
>>>>>>
>>>>>> For rt287x based cards, you can try using rt28700 chipset instead of
>>>>>> urtw0 on
>>>>>> FreeBSD 8.
>>>>>>
>>>>>> The former is not in the stable src tree, but could be retrieved from 
>>>>>>             
> here:
>   
>>>>>> https://gthc.org/distfiles/freebsd/rt2870_fbsd8.tar.gz
>>>>>>
>>>>>> Any takers to make module rt28700 (if_rt2870) officially part of the
>>>>>> FreeBSD src tree?
>>>>>>
>>>>>>          
>>>>>>             
>>>>> I'm a bit confused now, shouldn't the rt2870 be supported by run(4)? On
>>>>> a site-note, this is Ralink chipset not a Realtek one.
>>>>>
>>>>>
>>>>>        
>>>>>           
>>>> I believe this is a different implementation for RT8187 usb network
>>>> adapters than
>>>> run(4). However in my view I found urtw0 buggy, but would certainly take
>>>> a look at run(4) to
>>>> compare the results with wireless networking agaisnt the other driver
>>>> (rt28700).
>>>>      
>>>>         
>>> Yeah, urtw(4) has a few flaws..
>>>
>>> - urtw(4): Realtek RTL8187B/RTL8187L
>>> - rum(4): Ralink RT2501/RT2601
>>> - run(4): Ralink RT2700/RT2800/RT3000
>>>
>>> So it seems the driver you've posted conflicts with run(4). From a
>>> quick glance at it, it seems to support 11n? If so, can I talk you
>>> into working on getting those bits merged?
>>> Thanks!
>>>
>>> --
>>> Bernhard
>>> X-UID: 10549
>>> Status:
>>> X-Keywords:
>>> Content-Length: 0
>>>
>>>    
>>>       
>> I forwarded this thread on -current.
>>
>> Please also find below a stack trace produced with option KDB_UNATTENDED
>> for the rt28700 driver (if_rt28700).
>>
>> On another side note, I have not being able to load
>> the runfw firmware module anymore after having updated
>> the src tree for 8.2-STABLE ?
>>
>> $ sudo kldload /boot/kernel/runfw.ko
>> kldload: can't load /boot/kernel/runfw.ko: Exec format error
>>     
> Here is your real error in dmesg:
>
>   
>> KLD runfw.ko: depends on firmware - not available or version mismatch
>> linker_load_file: Unsupported file type
>>     
> You need to kldload firmware.ko or make sure 'device firmware' is in your
> kernel config.
>
>   

Hi,

Many thanks. This explains the change of behavior attempting to kldload
runfw.ko
without the firmware assist module. :)

However I find strange that run(4) requires such a firmware to be preloaded
when the rt2870 driver doesn't require it!

Cheers,



-- 
Etienne Robillard

Company: Green Tea Hackers Club
Occupation: Software Developer (and CEO)
E-mail:     erob@gthcfoundation.org
Work phone: 450-936-2123
Website (Company):  https://gthc.org/
Website (Blog):     https://gthc.org/blog/
PGP public key fingerprint:    F2A9 32EA 8E7C 460F 1728  A1A7 649C 7F17 A086 DDEC

During times of universal deceit, telling the truth becomes a revolutionary act. -- George Orwell 

If a free society cannot help the many who are poor, it cannot save the few who are rich. -- John F. Kennedy




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D6E77DF.1030605>