Dell D830 Broadcom 432AGN WiFi mini PCI-Express

This file is what you are looking for: /tmp/ascii_inf.LzpbUk

You need to read DriverVer from bcmwl5.inf:
Code: 
DriverVer=09/20/2007, 4.170.25.12
 
I can not reproduce it, but I don't have your card ...
Does scanning works with code from gitorious (try again with latest changes)?

Does other drivers panic if you kldload them _after_ boot?
 
Ok, now I used latest and newest drivers, that cause panic.
Code: 
DriverVer=08/25/2009, 5.60.18.9
Unfortunately there is no vmcore.n to debug, as crash happens in a stage of loading modules.

There is no panic when I kldload module at already booted system.
But there is one line that differ from previous version(in red):
Code: 
[color="Red"]no match for ExFreePoolWithTag[/color]
ndis0: <Dell Wireless 1500 Draft 802.11n WLAN Mini-Card> mem 0xf1ffc000-0xf1ffffff,0xf0000000-0xf00fffff irq 17 at device 0.0 on pci12
ndis0: [ITHREAD]
ndis0: NDIS API version: 5.1
 
If you did used code from gitorious, including rebuilding bcmwl5_sys.ko that line would not be displayed.

Also copy ndiscvt and other stuff from usr.sbin (usually done via `make world') like windrv_stub.c in /usr/share/misc/



When panic happens something is displayed on console.
You have dumpdev and other stuff defined in rc.conf?

Without bt I'm blind.
 
Excellent!

And a..., I don't understand this part:
Also copy ndiscvt and other stuff from usr.sbin (usually done via `make world') like windrv_stub.c in /usr/share/misc/
Click to expand...

I will do this:
1) Upload source tree as I run 8.0 STBALE
2) :
Code: 
git clone git://gitorious.org/ndisulator/ndisulator.git
Then, from downloaded folder, I will move src folder to /usr/src
3) I will rebuild world and kernel regulary...

Tomorrow I guess...
 
# mount_nullfs /path/to/NDISulator/src/sys/dev/if_ndis /usr/src/sys/dev/if_ndis
# mount_nullfs /path/to/NDISulator/src/sys/compat/ndis /usr/src/sys/compat/ndis
# mount_nullfs /path/to/NDISulator/src/usr.sbin/ndiscvt /usr/src/usr.sbin/ndiscvt

You don't need to rebuild world, just code in ndiscvt directory.
 
richardpl said:
# mount_nullfs /path/to/NDISulator/src/sys/dev/if_ndis /usr/src/sys/dev/if_ndis
# mount_nullfs /path/to/NDISulator/src/sys/compat/ndis /usr/src/sys/compat/ndis
# mount_nullfs /path/to/NDISulator/src/usr.sbin/ndiscvt /usr/src/usr.sbin/ndiscvt
Click to expand...

I see..., so after this mounting, access to /usr/src/sys/dev/if_ndis, will actually provide latest gitted version of ndis.

This saves me a step of moving files to /usr/src, after download.

But what did you meant by:
You don't need to rebuild world, just code in ndiscvt folder
Click to expand...
To what do you refer by code in
 
# cd /usr/src/usr.sbin/ndiscvt && make install clean

And if you use GENERIC kernel (ndis and ndisapi are modules):
# cd /usr/src/sys/modules/ndis && make install clean
# cd /usr/src/sys/modules/if_ndis && make install clean

So you dont need to rebuild world and kernel.
 
richardpl said:
...
And if you use GENERIC kernel (ndis and ndisapi are modules):
# cd /usr/src/sys/modules/ndis && make install clean
# cd /usr/src/sys/modules/if_ndis && make install clean

So you dont need to rebuild world and kernel.
Click to expand...
This is exactly a way I went last time.
 
Ok, hell, then I'll do it again.
And a..., you said you've reproduced an error.
Does this means, I'll have to wait until problem is solved in ndis code?
 
You picked master branch and not CURRENT?

I first need to find source of the problem ...
BTW new driver appears to freeze system now and then and I still need to find can this be traced via kdb ...

But older drivers and new one should have working scan, does it?
 
No. :p
With wpa_supplicant, scanning doesn't work.

I merely establish connection, to AP, which does broadcast it's SSID, only when I set in wpa_supplicant.conf:
Code: 
scan_ssid=1
And that option is intended to successfully connect to APs that don't broadcast theirs SSID
And connection breaks soon and is never established again.

In any of this steps scanning never works / show any results.
 
richardpl said:
try master again (sync source first to last commit)
Click to expand...
Works.
Kind of..

With my newest drivers, there is a crash during a boot.
With my oldest drivers, there is a crash during a boot, only if I set it to connect via wpa_supplicant in rc.conf.

So now it works, with my oldest drivers at 1/10th of speed, when connected to AP manually using wpa_supplicant, after boot.

PS: Used ndis master branch from 7 days ago.

Will test more... :stud
 
There is something wrong with list manipulation during boot (actually just after boot) I have no idea what is source of the problem.

Speaking about speed issue, is that regression? Is # top -HS showing something strange (too much use of CPU from ndis threads ...)

Speaking about scan results, maybe OID_802_11_BSSID_LIST(_SCAN) needs some tricks? So last master have some more debug, so just enable debug.ndis=1 while scanning: # ifconfig wlan0 scan (BTW: You must be root)
 
Ok I've just csup-ed src tree and downloaded latest master branch
Regarding booting, here is a latest crash http://www.starforce.biz/C.JPG

Forget speed, as it is now ok.
I simply didn't do any real speed test, till now.

It works when I kldload it after boot and scan works too.
Scan now works super fast!
Code: 
ifconfig wlan0 scan
Best of all ndis versions! ;)
And
Code: 
ifconfig wlan0 list scan
..., even faster

There is an issue with APs, that hide theirs ssid.
I can't connect, even when I use in wpa_supplicant.conf:
Code: 
scan_ssid=1

But I solved that anyway by using this wpa_supplicant.conf:
Code: 
eapol_version=2

ap_scan=2

network={
  ssid="xxx"
  scan_ssid=1
  proto=WPA
  key_mgmt=WPA-PSK
  pairwise=CCMP
  psk="xxxxxxxxxxxxx"
}

Now, your last issue, is a boot time crash. ;)
 
For hidden APs encryption must be changed to what AP is using, I dunno is this driver issue or just NDIS limitation.
 
Look a post above, as I've just edited it,... few sec before your post.

Now, your last issue, is a boot time crash.
;)
 
Seeker said:
Look a post above, as I've just edited it,... few sec before your post.

Now, your last issue, is a boot time crash.
;)
Click to expand...

Does wpa_supplicant -Dbsd works instead of -Dndis for you?

There are many other issues to be resolved .... the worst one is that amd64 is broken with my card.
 
You must log in or register to reply here.
Back
Top