Re: D-link dub e100

[david aubril <david.aubril%ac-nantes.fr@localhost>]

Hum.
1°) 0x2001 and 0x3c05 id's are already in sys/dev/usb/usbdevs and
describe the product I have. ( answer to Adam Hamsik )
2°) '#strings /netbsd | grep _CFG | grep axe' gives : '_CFG_axe*\011at
uhub? port ?\011\011# ASIX AX88172 based adapters'
Si I'm rebuilding the kernel.
But I don't see why NetBSD 5 GENERIC wouldn't have axe* built in ? (
in****| usr/src/sys/arch/i386/conf, the axe line isn't commented out, it
seems to be active by default )|****
Best regards,
David

Wouter Klouwen a écrit :
> david aubril(david.aubril%ac-nantes.fr@localhost) said 2008.12.03 17:34:23 
> +0000:
>   
>> Here we go.
>> It's really weard. It works fine, smoothly with the linux box. But
>> nothing with the netbsd box. Not even a light, or a line in dmesg.
>>     
>
> There are some clues in the dmesg.
>
>   
>> ugen0 at uhub3 port 1
>> ugen0: vendor 0x2001 product 0x3c05, rev 2.00/0.01, addr 2
>>     
>
> I believe this is your e100 device. ugen is attaching. This means that there
> probably isn't a better driver. Either your kernel doesn't have the axe
> driver built in, or you've been bitten by something that manufacturers of
> cheap hardware often do, they switch to a different chipset without telling
> anybody. 
> The first is probably more likely. To check, do:
>       #  strings /netbsd | grep _CFG  | grep axe
> If it shows something like:
>       _CFG_#axe* bla bla bla
> then it wasn't included in the kernel config.
>
>   
>> Best regards,
>> David
>>     
>       --Wouter
>
>