Dell D830 Broadcom 432AGN WiFi mini PCI-Express

I already said not to use last driver because it easily exposes bugs in NDISulator and panics. The last change just expose bug more directly.

Use older driver until I rewrite big pile of awful code in WorkItem implementation.
 
Oh, I see.
I've thought you've meant not to use v5 if I intend to boot with it.

Will try v4 then.
 
It only doesn't crash, but AP association is obliterated!
Can I have a code(how to get), from point in time, just before I've told you about hidden ssid issue.
Obviously you've did a major regression, on that part, in your attempt to fix it.
 
Seeker said:
Can I have a code(how to get), from point in time, just before I've told you about hidden ssid issue.
Click to expand...

Clone git, checkout stable_ndis5 branch, look at git log and checkout second to last commit.

You can also download tar.gz state of tree before last commit.
 
I can see, you now have 2 branches, as merging occurred.
I've fetched latest FreeBSD's src and recompiled world+kern, about 14 hrs ago.

I've downloaded ndis 'stable' 1 hrs ago.

It compiled and I've created module.
Upon kldload:
Code: 
link_elf_obj: symbol x86_64_call2 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
 
stable is for FreeBSD STABLE as mentioned in README

modules loads fine for me on amd64 and i386.

You can not mix modules/kernel with different __FreeBSD__version.
 
???
But I have been using stable_ndis5 up to now!
Isn't this now a stable branch after merge?

I still run 8.2 PRERELEASE
That is whats gets compiled when I download RELENG_8 (aka STABLE)
 
Using ndis v4 drivers ...

If AP hiddes ssid, association isn't posible:
Code: 
Dec 12 02:29:24 cruiser wpa_supplicant[399]: CTRL-EVENT-SCAN-RESULTS
Dec 12 02:30:00 cruiser last message repeated 3 times
Dec 12 02:32:01 cruiser last message repeated 10 times
Unhiding solves an issue.

For some reason, ndis now sets txpower to 0, which results in disastrous speeds. (20 Kbps)
Setting it to txpower 30, fixes it.

However(when encryption used), speed varies on it's own, so I get 20% of max speed, which seems now to be 50~80%, with just downloaded ndis sources.
Lastly I've saw this:
Code: 
media DS/5.5Mbps
And it was supposed to be OFDM/54
It varies on it's own, sometimes giving speeds of funny 1Kb/s ?!
;)

I did ifconfig up and down and even achieved max speed.

If wlan0 is idle, I can't use it anymore:
Code: 
Dec 12 05:03:03 cruiser wpa_supplicant[399]: WPA: EAPOL-Key Replay Counter did not increase - dropping packet
Dec 12 05:03:29 cruiser last message repeated 5 times
Dec 12 05:09:04 cruiser wpa_supplicant[399]: WPA: EAPOL-Key Replay Counter did not increase - dropping packet
 
I remember having max speeds even on amd64. At that time there was 3 branches, before you did a merge.
It also seems I don't have this problem, if I use ndis v5 drivers, that is, I can get max speeds, but am not using it, as you said not to + I can't boot with it, while with v4 I can.
After more testing in current situation, I am getting on average max ~100 Kb/s

Via rc.conf
Code: 
/usr/sbin/wpa_supplicant -dd -s -B -i wlan0 -c /etc/wpa_supplicant.conf -D ndis -P /var/run/wpa_supplicant/wlan0.pid
 
I can use latest broadcom driver: version 5.100.9.142 just fine except I never load miniport drivers via loader.conf.

So just use last driver but do not touch loader.conf until I announce it is safe.

Did you ever tried to load driver via rc.local ?

Repeating over and over again boot issue will not make it get fixed sooner - ever heard about negative feedback?
 
ROFLMAO!
I was refering to cron's @reboot, which I would use, to kldload v5 driver, at boot time.
And even configure if ...
 
Using v5, I get higher average speed ~300 Kb/s
However, I can reach max of ~650 Kb/s(which I can't with v4), if I do $IF up and down, around 4 times.
But, in that process, I can also hit a "null point", which means I can't scan nor connected to AP:
Code: 
Dec 12 19:23:42 cruiser [B]kernel: ifa_add_loopback_route: insertion failed[/B]
Dec 12 19:23:46 cruiser wpa_supplicant[1620]: CTRL-EVENT-SCAN-RESULTS
Dec 12 19:24:22 cruiser last message repeated 3 times
Dec 12 19:24:46 cruiser last message repeated 2 times
Dec 12 19:24:49 cruiser [B]kernel: ifa_add_loopback_route: insertion failed[/B]
Dec 12 19:24:58 cruiser wpa_supplicant[1620]: CTRL-EVENT-SCAN-RESULTS
Dec 12 19:25:34 cruiser last message repeated 3 times
I've also noticed that at 2 time, txpower is dropped to 0 instead to 30 (same as with v4), which gives ~ 12 Kb/s
 
Regarding txpower issue: ifconfig txpower output is incorrect. If you do not like such output look at ifconfig manual page for country/regdomain and similar commands.
 
I am already using county HR .. ETSI ...
Anyway, when you improve bandwith logic and other issues, throw a post, so I could jump for new drivers.
;)
 
I've tried yours latest sources:
Speed is now improved, up to 80% of max speed.

After done few $IF up and downs (wpa also restarted) I can't scan(nor assocciate with AP), sometimes, with error:
Code: 
ifconfig wlan0 scan
wlan0: ieee80211_new_state_locked: pending INIT -> RUN transition lost

Dec 16 16:18:40 cruiser kernel: ifa_add_loopback_route: insertion failed
Dec 16 16:19:31 cruiser kernel: ifa_add_loopback_route: insertion failed
Dec 16 16:19:39 cruiser wpa_supplicant[1843]: CTRL-EVENT-SCAN-RESULTS
Dec 16 16:20:15 cruiser last message repeated 3 times
Dec 16 16:21:03 cruiser last message repeated 4 times
 
There are other problems with ndis driver for wpa_supplicant, if wlan device is gone, wpa_supplicant will start to consume all cpu cycles.

Sometimes ieee80211 state will got corrupted in such way that only wlan recreation will fix it.
I'm looking for solution.
So if wlan destroy/create doesn't fix this it is another problem.
 
I must admit, that I've never reached for wlan0 destroy/create as a solution.
Will try it here and there ...
 
With your latest ndisulator -> stable ...
v4 drivers -> I can reach 40-50% of max speed and there is no panic
v5 drivers -> I can reach 95-100% of max speed and there is panic upon scan, sometimes

Part of code, from v5, that enables max speed, should be transferred into v4 part of code.
 
Seeker said:
Part of code, from v5, that enables max speed, should be transferred into v4 part of code.
Click to expand...
There is no such code. There is nothing that can be transferred.

If speed of v4 on i386 is higher than on amd64 than that is something else....
 
No, no, I am talking about amd64 in both cases, with your latest ndisulator -> stable ...
i386 is completely out of context here, as I don't use it, for about few months already.
 
You must log in or register to reply here.
Back
Top