Re: Intel 5100AGN ndis driver problem

From: Ganbold <ganbold_at_micom.mng.net>
Date: Fri, 20 Mar 2009 15:29:43 +0800
Paul B. Mahol wrote:
> On 3/19/09, Ganbold <ganbold_at_micom.mng.net> wrote:
>   
>> Hi,
>>
>> I'm trying to use ndis driver for Intel 5100AGN and got
>> following error:
>>
>> beastie# grep ndis /var/log/messages
>> Mar 19 23:41:21 beastie kernel: ndis0: <Intel(R) WiFi Link 5100 AGN> mem
>> 0xf4300000-0xf4301fff irq 17 at device 0.0 on pci3
>> Mar 19 23:41:21 beastie kernel: ndis0: [ITHREAD]
>> Mar 19 23:41:21 beastie kernel: ndis0: NDIS API version: 5.1
>> Mar 19 23:41:21 beastie kernel: ndis0: NDIS ERROR: 40001b7c (unknown error)
>>
>> Mar 19 23:41:21 beastie kernel: ndis0: NDIS ERROR: 40001b7c (unknown error)
>> Mar 19 23:41:21 beastie root: Unknown USB device: vendor 0x08ff product
>> 0x2810 bus uhub1
>> Mar 19 23:41:21 beastie root: Unknown USB device: vendor 0x0a5c product
>> 0x2145 bus uhub1
>> Mar 19 23:41:21 beastie root: Unknown USB device: vendor 0x17ef product
>> 0x1004 bus uhub3
>> Mar 19 23:41:53 beastie kernel: ugen1.3: <Lenovo Computer Corp> at
>> usbus1 (disconnected)
>> Mar 19 23:41:57 beastie kernel: ugen1.3: <Lenovo Computer Corp> at usbus1
>> Mar 19 23:41:57 beastie root: Unknown USB device: vendor 0x0a5c product
>> 0x2145 bus uhub1
>> Mar 19 23:45:36 beastie kernel: wlan0: Ethernet address: 00:21:6b:9a:23:8e
>> Mar 19 23:52:02 beastie kernel: pid 9861 (initial thread) is using
>> legacy pty devices
>> Mar 20 00:08:06 beastie kernel: ndis0: NDIS ERROR: 40001b7c (unknown error)
>> ...
>> ndis0_at_pci0:3:0:0:    class=0x028000 card=0x12118086 chip=0x42378086
>> rev=0x00 hdr=0x00
>>     vendor     = 'Intel Corporation'
>>     class      = network
>>
>> I'm running:
>> beastie# uname -an
>> FreeBSD beastie.micom.mng.net 8.0-CURRENT FreeBSD 8.0-CURRENT #5
>> r190040M: Thu Mar 19 21:45:37 ULAT 2009
>> tsgan_at_beastie.micom.mng.net:/usr/obj/usr/src/sys/DEVIL_WITNESS  i386
>>
>>
>> Any idea how to fix this issue?
>> Please let me know if you need more info.
>>     
>
> How you generate ndis module?
> Post whole output _after_ is module loaded
> _not_ just lines containing ndis.
>
> also enable debug.ndis sysctl.
>   

I tried to generate ndis module with ndisgen.
I will try again with debug.ndis and let you know.

thanks,

Ganbold




-- 
Satire is what closes Saturday night. -- George Kaufman
Received on Fri Mar 20 2009 - 06:29:49 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:44 UTC