Ndis + Netgear WG311v3 ; Won't attach device correctly

2006-08-09 Thread Frank Staals 

Hey,

Today I got my hands on a Netgear WG311v3 and since there is no propper 
support for that card I decided to use nids, so I installed the ndis and 
if_ndis kernel modules, generated a new Kernel Module by using the 
WG311v3.INF and WG311v3XP.sys files; according to this thread:  
http://linuxcompatible.org/Netgear_WG311v3_WLAN_PCI_Card_with_Debian_Linux_Testing_t33271.html 
I should use those files. So far it worked, I loaded the module 
correctly and I had a ndis0. Allthough I had problems configuring the 
card correctly ( it wouldn't assosiate ). So I reloaded the module but 
this time it wouldn't attach my device correctly. This is what keeps 
happening:


[EMAIL PROTECTED] kldstat
Id Refs AddressSize Name
1   12 0xc040 5cfe2c   kernel
21 0xc09d 7794 snd_emu10k1.ko
32 0xc09d8000 22b88sound.ko
81 0xc0a76000 59b90acpi.ko
92 0xc2cfd000 16000linux.ko
101 0xc2ea7000 3000 daemon_saver.ko
111 0xc2ef8000 2000 rtc.ko
[EMAIL PROTECTED] kldload /boot/kernel/WG311v3XP_sys.ko

My dmesg shows this:

ndis0: NETGEAR WG311v3 802.11g Wireless PCI Adapter mem 
0xfe1e-0xfe1e,0xfe1d-0xfe1d irq 19 at device 10.0 on pci2

ndis0: NDIS API version: 5.1
ndis0: init handler failed
device_attach: ndis0 attach returned 6

these are the kernel modules loaded after loading WG311v3XP_sys :


[EMAIL PROTECTED] kldstat
Id Refs AddressSize Name
1   20 0xc040 5cfe2c   kernel
21 0xc09d 7794 snd_emu10k1.ko
32 0xc09d8000 22b88sound.ko
81 0xc0a76000 59b90acpi.ko
92 0xc2cfd000 16000linux.ko
101 0xc2ea7000 3000 daemon_saver.ko
111 0xc2ef8000 2000 rtc.ko
151 0xc310c000 47000WG311v3XP_sys.ko
161 0xc30e8000 b000 if_ndis.ko
172 0xc376a000 13000ndis.ko
181 0xc377d000 c000 pccard.ko
[EMAIL PROTECTED]


The only thing changed since the first time I loaded the module was I 
copied it to /boot/kernel and I added WG311v3XP_sys_load=YES to 
/boot/loader.conf but those changes shouldn't have effect on not 
correctly loading it I think.


I also tried to use the WG311v3.sys file, but I get the same output in 
my dmesg as above.


Can anyone tell me why it won't load my module correctly anymore ? And 
what I should do to get it working again


Regards,


--
-Frank Staals


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Ndis + Netgear WG311v3 ; Won't attach device correctly

2006-08-09 Thread John Nielsen 
On Wednesday 09 August 2006 11:40, Frank Staals wrote:
 The only thing changed since the first time I loaded the module was I
 copied it to /boot/kernel and I added WG311v3XP_sys_load=YES to
 /boot/loader.conf but those changes shouldn't have effect on not
 correctly loading it I think.

This is the key. I can't remember where I read it but this is a documented 
caveat of the ndis driver. Windows doesn't typically invoke network drivers 
until after the system is loaded, so some drivers won't work in FreeBSD 
unless they're loaded after the system is up. So take the line out 
of /boot/loader.conf, test that the driver works correctly if you reboot and 
kldload it manually, then make an rc script or something to automatically 
load the driver later in the boot process.

JN
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Ndis + Netgear WG311v3 ; Won't attach device correctly

2006-08-09 Thread Frank Staals 

John Nielsen wrote:

On Wednesday 09 August 2006 11:40, Frank Staals wrote:
  

The only thing changed since the first time I loaded the module was I
copied it to /boot/kernel and I added WG311v3XP_sys_load=YES to
/boot/loader.conf but those changes shouldn't have effect on not
correctly loading it I think.



This is the key. I can't remember where I read it but this is a documented 
caveat of the ndis driver. Windows doesn't typically invoke network drivers 
until after the system is loaded, so some drivers won't work in FreeBSD 
unless they're loaded after the system is up. So take the line out 
of /boot/loader.conf, test that the driver works correctly if you reboot and 
kldload it manually, then make an rc script or something to automatically 
load the driver later in the boot process.


JN
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


  

Ah thanks a lot, that did the trick

--
-Frank Staals


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]