Dell D830 Broadcom 432AGN WiFi mini PCI-Express

richardpl · Nov 26, 2010

You can use release source and merge fpu_kern API from STABLE. I use git mirror of freebsd source so this is fast and trivial.

cvs and svn is for history.

Anyway 8 STABLE is in PRERELEASE stage, so testing it and reporting bugs will make 8.2 RELEASE better.

Seeker · Nov 26, 2010

Ok, so ...

Code:

cd /usr/ports/devel/git
make install clean

Now, I would like to keep RELEASE sources and download, what-you-said-to, via git, into:

Code:

mkdir ~/ndis_stable

After that, I would mount ~/ndis_stable, via nullfs, over my existing sources

Can I get CMDs to achieve this?
Especially git fetching part.

richardpl · Nov 26, 2010

Use FreeBSD git mirror: git://gitorious.org/freebsd/freebsd.git

It keeps CURRENT, STABLE, RELEASE and even 4.11 in one go, and consume only ~350 MB.

NDISulator got README and Makefile, and wiki+issue page at https://github.com/richardpl/NDISulator

richardpl · Nov 26, 2010

Code:

#ndis_get_oid: oid=0x1010102 len (6) failed
NDIS: Get OID_802_3_CURRENT_ADDRESS failed
Failed to initialize driver interface
Failed to add interface wlan0
Cancelling scan request
Cancelling authentication timeout

Looks like this is completly another problem (it have nothing to do with fpudna).

richardpl · Nov 26, 2010

It was my fault. Fixed.

Seeker · Nov 27, 2010

Ok, so here is a report:

I've used 2 type of 64bit drivers, latest versions of:
ndis 5
ndis 4

Both worked, BUT, ndis5 driver, if loaded at boot time, causes panic!

So I stick with ndis 4 driver.

PS: Is there a way to shut up fpudna kernel's screaming?
This made me to completely avoid using console on ttyv0, so now am on ttyv1+

richardpl · Nov 27, 2010

fpudna will be gone once you use FreeBSD & NDISulator with fpu_kern API.

Even Windows does not load drivers at boot time - I will see what can be done to delay ndis initialization.
In meantime instead of loader.conf(5) use rc.local(8)

Seeker · Nov 30, 2010

If wlan0 is idle(no data transfers) for 15 min, connection acts like broken, even 'ifconfig wlan0' states associated:
From log:

Code:

wpa_supplicant[396]: WPA: EAPOL-Key Replay Counter did not increase - dropping packet

But if I do:

Code:

ifconfig wlan0 down
ifconfig wlan0 up

... and wait for a few minutes, all is back to normal.

How should I solve this?

richardpl · Nov 30, 2010

Now NDISulator have ultimate debug support. Make sure you use latest version.

Debug is compiled by default. Enable it with:
# sysctl debug.ndis=1

This will show all OID request on console.

If you set this to -1 instead you will get burst of messages on console, so be warned.

Is something else displayed on console?
Perhaps this will be fixed with fpu_kern API.

I think this is because you do not run ndis_events(8) (you really should). AP probably disconnected you due to inactivity.

Seeker · Nov 30, 2010

Ok, I will try 'ndis_events', as I haven't used it.
I've set up all, to be fully configured at boot time. (kldload, config in rc.conf)
So after boot, when I reach console, with login prompt, sys is already associated with AP.
How do I make 'ndis_events' start at boot, too?
I've searched but haven't found any directives in rc.

richardpl · Nov 30, 2010

Put it in rc.local

Seeker · Dec 2, 2010

As usual, yesterday I've downloaded latest ndisulator-ndisulator-stable_ndis5.tar.gz
Under 8.1R it compiled and run.
This time I had a lots of:

Code:

wpa_supplicant[407]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys

At some time of usage, I had a huge packet loss of approx 75% and ifconfig showed speed of 1Mbps.

Code:

ping -c10 192.168.0.1 | grep -oE '[^ ]+ packet loss'
80.0% packet loss
cruiser# ping -c10 192.168.0.1 | grep -oE '[^ ]+ packet loss'           0 /root
100.0% packet loss
cruiser# ping -c10 192.168.0.1 | grep -oE '[^ ]+ packet loss'           2 /root
50.0% packet loss
cruiser# ping -c10 192.168.0.1 | grep -oE '[^ ]+ packet loss'           0 /root
70.0% packet loss
cruiser# ping -c10 192.168.0.1 | grep -oE '[^ ]+ packet loss'           0 /root
90.0% packet loss
cruiser# ping -c10 192.168.0.1 | grep -oE '[^ ]+ packet loss'           0 /root
80.0% packet loss
cruiser# ping -c10 192.168.0.1 | grep -oE '[^ ]+ packet loss'           0 /root
70.0% packet loss
cruiser# ping -c10 192.168.0.1 | grep -oE '[^ ]+ packet loss'           0 /root
90.0% packet loss
cruiser# ping -c10 192.168.0.1 | grep -oE '[^ ]+ packet loss'           0 /root
60.0% packet loss

So I upgraded to 8.2 PRERELEASE and compiled ndisulator-ndisulator-stable_ndis5
I've received an errors during ndisgen attempt to create kernel module.
This is how, my dir, looked like:

Code:

total 3912
-rw-r--r--  1 root  wheel  -  1.1K Dec  2 16:11:39 2010 .depend
lrwxr-xr-x  1 root  wheel  -   12B Dec  2 16:11:39 2010 @ -> /usr/src/sys
-rwx------  1 root  wheel  -  754K Oct 24 19:00:30 2008 [B]bcmwl5.inf[/B]
-rwx------  1 root  wheel  -  1.4M Oct 24 19:00:30 2008 [B]bcmwl564.sys[/B]
-rw-r--r--  1 root  wheel  -   30K Dec  2 16:11:39 2010 bus_if.h
-rw-r--r--  1 root  wheel  -   11K Dec  2 16:11:39 2010 device_if.h
lrwxr-xr-x  1 root  wheel  -   26B Dec  2 16:11:39 2010 machine -> /usr/src/sys/amd64/include
-rw-r--r--  1 root  wheel  -  100K Dec  2 16:11:32 2010 windrv.h
-rw-r--r--  1 root  wheel  -  1.5M Dec  2 16:11:32 2010 windrv.o

Looks like it's broken.

richardpl · Dec 2, 2010

Read README and follow it, nothing is broken.

Please post output of dmesg(8) somewhere.

Seeker · Dec 3, 2010

During boot, now it collapses with both drivers:
Driver v4
Driver v5

Driver v5, also once crashed while working, but it also might be NFS as a cause, or something tird, who would know.

I am now with latest Driver v5.
There is an issue, where if there is no data passing through wlan0, for some time, it simply doesn't work anymore even when associated with an AP.

Log said:

Code:

WPA: EAPOL-Key Replay Counter did not increase - dropping packet

richardpl · Dec 3, 2010

Seeker said:
During boot, now it collapses with both drivers:
Driver v4
Driver v5

Just stop loading it during boot, please.

I asked for dmesg output. The info you gave me is useless.

Can you make use of textdump, because looking jpeg is daunting task.

If you use latest version on 8.2 , "fpudna" should be gone, is this true?

Is it so hard to contact me directly? Trying to debug this stuff via forum
interface is daunting task for me.

Make account on github.com, so that you can make unlimited number of tracked
issues in github.com/richardpl/ndisulator instead of spreading them on this forum.

Seeker · Dec 3, 2010

richardpl said:
Just stop loading it during boot, please.

Done.

richardpl said:
I asked for dmesg output. The info you gave me is useless.

Here it is ...

richardpl said:
Can you make use of textdump, because looking jpeg is daunting task.

No core dump has occurred.

richardpl said:
If you use latest version on 8.2 , "fpudna" should be gone, is this true?

Yes.

richardpl said:
Is it so hard to contact me directly? Trying to debug this stuff via forum interface is daunting task for me.

I don't have your personal contact.

richardpl said:
Make account on github.com, so that you can make unlimited number of tracked
issues in github.com/richardpl/ndisulator instead of spreading them on this forum.

Done.

Also, regarding idle wlan0, here is a log, when tried to use it again(down then up):

Code:

Dec  3 07:14:00 cruiser wpa_supplicant[1557]: Authentication with 00:00:00:00:00:00 timed out.
Dec  3 07:14:00 cruiser wpa_supplicant[1557]: Trying to associate with SSID 'MY_SID'
Dec  3 07:15:00 cruiser wpa_supplicant[1557]: Authentication with 00:00:00:00:00:00 timed out.
Dec  3 07:15:00 cruiser wpa_supplicant[1557]: Trying to associate with SSID 'MY_SID'
Dec  3 07:16:00 cruiser wpa_supplicant[1557]: Authentication with 00:00:00:00:00:00 timed out.
Dec  3 07:16:00 cruiser wpa_supplicant[1557]: Trying to associate with SSID 'MY_SID'
Dec  3 07:16:03 cruiser kernel: wlan0: link state changed to UP
Dec  3 07:16:03 cruiser wpa_supplicant[1557]: Associated with 00:0e:2e:e5:0b:b9
Dec  3 07:16:13 cruiser wpa_supplicant[1557]: Authentication with 00:0e:2e:e5:0b:b9 timed out.
Dec  3 07:16:13 cruiser kernel: wlan0: link state changed to DOWN
Dec  3 07:16:13 cruiser wpa_supplicant[1557]: Trying to associate with SSID 'MY_SID'
Dec  3 07:16:14 cruiser wpa_supplicant[1557]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Dec  3 07:17:13 cruiser wpa_supplicant[1557]: Authentication with 00:00:00:00:00:00 timed out.
Dec  3 07:17:13 cruiser wpa_supplicant[1557]: Trying to associate with SSID 'MY_SID'

And when frantically initiating scan, kernel said:

Code:

wlan0: ieee80211_new_state_locked: pending RUN -> SCAN transition lost

richardpl · Dec 3, 2010

My email is displayed in every commit log.

There should not be state change if roaming is manual - when using wpa_supplicant with ndis driver.

I managed to reproduce crash in workitem3 for drivers using NdisSheduleWorkItem - the same one causing panic at boot.

So use older version of driver until I fix this bug.

Seeker · Dec 4, 2010

Idle connection becomes useless, with both driver versions (roaming MANUAL) and very hard to re-associate with AP

Code:

wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
	ether 00:1f:e1:71:1a:b9
	inet 192.168.0.3 netmask 0xffffff00 broadcast 192.168.0.255
	media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11g
	status: associated
	ssid MY_SSID channel 6 (2437 MHz 11g) bssid 00:0e:2e:e5:0b:b9
	regdomain ETSI country HR authmode WPA privacy OFF txpower 30 bmiss 7
	mcastrate 6 mgmtrate 6 scanvalid 60 protmode CTS roaming MANUAL

Both driver versions cause panic at boot.

richardpl · Dec 4, 2010

Try again with last version.

Seeker · Dec 4, 2010

All compiles but, at the end:

Code:

cruiser# kldload bcmwl564
link_elf_obj: symbol kuser_shared_data undefined
linker_load_file: Unsupported file type
KLD if_ndis.ko: depends on ndisapi - not available or version mismatch
linker_load_file: Unsupported file type
KLD bcmwl564.ko: depends on ndis - not available or version mismatch
linker_load_file: Unsupported file type
kldload: can't load bcmwl564: Exec format error

Ps: I've also created issue and wrote (regarding idle wlan):

My AP hides ssid.
When I removed that AP option, problem is gone.

You should test it with AP that hides it's ssid.

richardpl · Dec 4, 2010

I fixed error in loading. On i386 AP had hiden SSID too?

Seeker · Dec 4, 2010

Seeker · Dec 5, 2010

Code:

/usr/src/sys/modules/ndis/../../compat/ndis/kern_windrv.c: In function 'patch_user_shared_data_address':
/usr/src/sys/modules/ndis/../../compat/ndis/kern_windrv.c:287: error: 'kuser_shared_data' undeclared (first use in this function)
/usr/src/sys/modules/ndis/../../compat/ndis/kern_windrv.c:287: error: (Each undeclared identifier is reported only once
/usr/src/sys/modules/ndis/../../compat/ndis/kern_windrv.c:287: error: for each function it appears in.)
*** Error code 1

Stop in /usr/src/sys/modules/ndis.
*** Error code 1

Stop in /root/ndisulator-ndisulator.

Code slower ...

richardpl · Dec 5, 2010

Try again.

Seeker · Dec 5, 2010

Regression

I've used latest v5 drivers.

This is a worst sample ever.
As soon I compiled it and created modules, crash occurred upon kldload

Not only that it crashes machine at boot time, but also during work time.
Worst part, is it's complete inability, to associate with non-hidden AP, which worked excellent before.

This is serious regression, in all 3 points.