SUSE 11.0 Wireless not working - Broadcom BCM4328

English Network/Internet
#1

Hello

With SUSE 11.0 I am unable to make the wireless card function, I know that this card works because I had SUSE 10.3 on this system until I upgraded over the weekend.

Here are the instructions I used to get the wireless to work on SUSE 10.3:

-place the windows wireless drivers here - /home/tester/drivers/d631_wlan/

-enable super user

-Install the driver using ndiswrapper
ndiswrapper -i /home/tester/drivers/d631_wlan/bcmwl5.inf

-Make sure the driver installed
ndiswrapper -l

-Write the driver to modprobe
ndiswrapper -m

-Initialize the device and the driver
modprobe ndiswrapper

—After this the wireles card worked and I was able to see the device using ifconfig and iwconfig as well as connect to a network.

When I tried the same steps on SUSE 11.0, nothing happens; meaning that I am unable to see the device using ifconfig or iwconfig.

  • when I run lspci I see the device:
    0b:00.0 Network controller: Broadcom Corporation BCM4328 802.11a/b/g/n (rev 03)

Any suggestions?

Thanks
Chad

#2

Quick Update:

I tried the suggestion on, “Broadcom Card 4318… HELP!”, a few posts before mine and updating the firmware did not help.

Thanks
Chad

#3

chadbyoung wrote:
> Quick Update:
>
> I tried the suggestion on, “Broadcom Card 4318… HELP!”, a few posts
> before mine and updating the firmware did not help.

The open-source driver will not work for the 4328 as the reverse
engineering has not been completed.

You will need to use ndiswrapper as you were trying, but I cannot help
you with it.

Larry

#4

chadbyoung wrote:

>
> Hello
>
> With SUSE 11.0 I am unable to make the wireless card function, I know
> that this card works because I had SUSE 10.3 on this system until I
> upgraded over the weekend.
>
> Here are the instructions I used to get the wireless to work on SUSE
> 10.3:
>
> ---------
>
> -place the windows wireless drivers here -
> /home/tester/drivers/d631_wlan/
>
> -enable super user
>
> -Install the driver using ndiswrapper
> ndiswrapper -i /home/tester/drivers/d631_wlan/bcmwl5.inf
>
> -Make sure the driver installed
> ndiswrapper -l
>
> -Write the driver to modprobe
> ndiswrapper -m
>
> -Initialize the device and the driver
> modprobe ndiswrapper
>
> —After this the wireles card worked and I was able to see the device
> using ifconfig and iwconfig as well as connect to a network.
>
> ---------
>
> When I tried the same steps on SUSE 11.0, nothing happens; meaning that
> I am unable to see the device using ifconfig or iwconfig.
>
> * when I run lspci I see the device:
> 0b:00.0 Network controller: Broadcom Corporation BCM4328 802.11a/b/g/n
> (rev 03)
>
> Any suggestions?
>

Perhaps try the forums at the ndiswrapper site -
http://ndiswrapper.sourceforge.net/joomla/index.php

In fact, perhaps I ought to as well, since I’ve similar problems with
another Broadcom device.

–
Graham P Davis, Bracknell, Berks., UK. E-mail: newsman, not newsboy.
“What use is happiness? It can’t buy you money.” [Chic Murray, 1919-85]

#5

Has anyone had success conntecting to a wireless network with this card: Broadcom BCM4328?

Thanks
Chad

#6

chadbyoung wrote:
> Has anyone had success conntecting to a wireless network with this card:
> Broadcom BCM4328?

The BCM4328 has not yet been reverse engineered. For it, you will need
to blacklist ssb and use ndiswrapper with a Windows driver. If your
ethernet interface is a BCM44XX, you will have problems.

Larry

#7

Hi chadbyoung

Try with this:

Install Broadcom 4318 in openSUSE 11 - openSUSE Forums

Is for Broadcom 4318 + ndiswrapper, but maybe works for you

#8

jnigro wrote:
> Hi chadbyoung
>
> Try with this:
>
> ‘Install Broadcom 4318 in openSUSE 11 - openSUSE Forums’
> (http://tinyurl.com/5nkv3a)
>
> Is for Broadcom 4318 + ndiswrapper, but maybe works for you

For a BCM4318, ndiswrapper is the last thing you should use. If you do
you are just asking for the same kind of crashes that Windows has.
Remember that the memory layout is different in Linux and that some of
the Windows drivers have bugs that do not cause any difficulty in
Windows, but will lead to spontaneous reboots in Linux.

To use the open-source driver b43, which has been extensively tested,
you need to install the firmware and configure the interface.

Larry

#9

I have the same problem. The card is working! Here is the output of:

iwlist scan wlan0

wlan0 Scan completed :
Cell 01 - Address: 00:18:4D:93:7A:E2
ESSID:“WLAN836”
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:15/100 Signal level:-86 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0

So …

The question is how to use the card with KDE4

KNetworkManager is no longer a part of KDE4 is what it looks like to me. I could really use some help on this subject.

#10

It’s the little grey globe on the bottom right corner of the screen. Click on it and select :: New Connection>wlan01
Then follow the steps right through for checking your settings.

#11

this worked for me just copy paste the steps…

its for opensuse 10.3 but i used it for opensuse 11 and it worked

http://www.suseblog.com/?p=279

:slight_smile:

#12

you forgot to blacklist bcm43xx

#13

I also have a Broadcom BCM4328 and have trouble in SuSE 11. I am trying to use ndiswrapper as I did before in 10.3 but there seems to be a problem with the ssb driver. For some reason ssb always loads even if you blacklist it. I can get the card sort of working by manually unloading ssb.

rmmod ssb

modprobe ndiswrapper

modprobe ssb

iwlist wlan0 scan will return results but if I try to connect through network manager in kde, it freezes weather I try to connect to a locked or unlocked access point.

If you have this problem, you can find out by running ndiswrapper -l. You should see that the driver bcmwl5 has been loaded but it also says alternate driver: ssb.

If I go into Yast to configure my card, I can select options for ssb but nothing for ndiswrapper?

I also tried running this with module ssb unloaded with the same result. Ssb got loaded at boot and took control of the usb bus I think. There may be other modules that should be unloaded along with ssb for this to work but I don’t know which ones. Maybe by unloading all conflicting modules this could work. If it does, loading back the modules after ndiswrapper may still work. In that case you could have a script do that for you automatically.

Any help is appreciated!

#14

I get a GPF when it freezes. Here is the output from /var/log/messages. Hopefully this will have some Novell Guru’s attention!

Jul 3 00:40:43 fijii kernel: general protection fault: 0000 [1] SMP
Jul 3 00:40:43 fijii kernel: last sysfs file: /sys/devices/system/cpu/cpu1/cache/index2/shared_cpu_map
Jul 3 00:40:43 fijii kernel: CPU 1
Jul 3 00:40:43 fijii kernel: Modules linked in: ssb ndiswrapper xt_tcpudp xt_pkttype xt_physdev ipt_LOG xt_limit af_packet bridge bnep snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device ipt_REJECT xt_state iptable_mangle iptable_nat nf_nat iptable_filter nf_conntrack_netbios_ns nf_conntrack_ipv4 nf_conntrack ip_tables cpufreq_conservative cpufreq_userspace cpufreq_powersave powernow_k8 ip6_tables x_tables binfmt_misc fuse loop dm_mod rfcomm l2cap usbtouchscreen uvcvideo compat_ioctl32 videodev v4l1_compat hci_usb btusb bluetooth snd_hda_intel snd_pcm snd_timer rtc_cmos sr_mod snd_page_alloc rtc_core snd_hwdep joydev cdrom rtc_lib k8temp sg snd forcedeth soundcore i2c_nforce2 i2c_core video output usbhid pcmcia hid wmi pcmcia_core firmware_class battery button ff_memless ac ehci_hcd ohci_hcd sd_mod usbcore edd ext3 mbcache jbd fan pata_amd sata_nv libata scsi_mod dock thermal processor [last unloaded: ssb]
Jul 3 00:40:43 fijii kernel: Pid: 5045, comm: ntos_wq Tainted: P N 2.6.25.5-1.1-default #1
Jul 3 00:40:43 fijii kernel: RIP: 0010:<ffffc200022551fb>] <ffffc200022551fb>]
Jul 3 00:40:43 fijii kernel: RSP: 0018:ffff81011b991a48 EFLAGS: 00010286
Jul 3 00:40:43 fijii kernel: RAX: ffff81011b991b50 RBX: ffffc20001e06000 RCX: ffffc20001e06000
Jul 3 00:40:43 fijii kernel: RDX: 0000000000000001 RSI: 0000000000000001 RDI: ffff81013b452b00
Jul 3 00:40:43 fijii kernel: RBP: ffff81013b4522c0 R08: 0000000000000003 R09: 000000000000000c
Jul 3 00:40:43 fijii kernel: R10: ffffc20002303840 R11: ffffc20001e01af0 R12: ffffc20001e01af0
Jul 3 00:40:43 fijii kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 00000000000000ff
Jul 3 00:40:43 fijii kernel: FS: 00007f4ddb831700(0000) GS:ffff81013fa6da40(0000) knlGS:00000000f7d37af0
Jul 3 00:40:43 fijii kernel: CS: 0010 DS: 0018 ES: 0018 CR0: 0000000080050033
Jul 3 00:40:43 fijii kernel: CR2: 00000000008b8000 CR3: 000000011b952000 CR4: 00000000000006e0
Jul 3 00:40:43 fijii kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Jul 3 00:40:43 fijii kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Jul 3 00:40:43 fijii kernel: Process ntos_wq (pid: 5045, threadinfo ffff81011b990000, task ffff81013e0d0500)
Jul 3 00:40:43 fijii kernel: Stack: ffff8101064d2c3e ffff81011b991a60 ffffffff8851c369 00000000ffffffff
Jul 3 00:40:43 fijii kernel: ffffffff00000008 ffffc20001e061e3 ffff8101064d2c3e ffffc200022470b5
Jul 3 00:40:43 fijii kernel: ffffc20001e06101 000000000000c23b 000000000000002d ffffc20001e06000
Jul 3 00:40:43 fijii kernel: Call Trace:
Jul 3 00:40:43 fijii kernel: Inexact backtrace:
Jul 3 00:40:43 fijii kernel:
Jul 3 00:40:43 fijii kernel: <ffffffff8851c369>] ? :ndiswrapper:KeStallExecutionProcessor+0xb/0xe
Jul 3 00:40:43 fijii kernel: <ffffffff803268e2>] ? __udelay+0x50/0x62
Jul 3 00:40:43 fijii kernel: <ffffffff88527672>] ? :ndiswrapper:ExFreePoolWithTag+0x26/0x2f
Jul 3 00:40:43 fijii kernel: <ffffffff88527686>] ? :ndiswrapper:ExFreePool+0xb/0xd
Jul 3 00:40:43 fijii kernel: <ffffffff885210f1>] ? :ndiswrapper:NdisFreeMemory+0x9/0xb
Jul 3 00:40:43 fijii kernel: <ffffffff8853326b>] ? :ndiswrapper:win2lin3+0x11/0x14
Jul 3 00:40:43 fijii kernel: <ffffffff88525e02>] ? :ndiswrapper:KeRaiseIrql+0x7/0xb7
Jul 3 00:40:43 fijii kernel: <ffffffff88525eb2>] ? :ndiswrapper:kdpc_worker+0x0/0x163
Jul 3 00:40:43 fijii kernel: <ffffffff8044774c>] ? thread_return+0x6a/0xae
Jul 3 00:40:43 fijii kernel: <ffffffff88525fba>] ? :ndiswrapper:kdpc_worker+0x108/0x163
Jul 3 00:40:43 fijii kernel: <ffffffff88525f9c>] ? :ndiswrapper:kdpc_worker+0xea/0x163
Jul 3 00:40:43 fijii kernel: <ffffffff80246e5c>] ? run_workqueue+0x8b/0x11a
Jul 3 00:40:43 fijii kernel: <ffffffff80246fc8>] ? worker_thread+0xdd/0xee
Jul 3 00:40:43 fijii kernel: <ffffffff8024a583>] ? autoremove_wake_function+0x0/0x38
Jul 3 00:40:43 fijii kernel: <ffffffff80246eeb>] ? worker_thread+0x0/0xee
Jul 3 00:40:43 fijii kernel: <ffffffff8024a22d>] ? kthread+0x49/0x76
Jul 3 00:40:43 fijii kernel: <ffffffff8020d058>] ? child_rip+0xa/0x12
Jul 3 00:40:43 fijii kernel: <ffffffff8024a1e4>] ? kthread+0x0/0x76
Jul 3 00:40:43 fijii kernel: <ffffffff8020d04e>] ? child_rip+0x0/0x12
Jul 3 00:40:43 fijii kernel:
Jul 3 00:40:43 fijii kernel:
Jul 3 00:40:43 fijii kernel: Code: 20 5b c3 cc cc cc cc cc cc cc cc cc 48 8b c4 48 89 58 10 48 89 68 18 48 89 70 20 57 41 54 41 55 41 56 41 57 48 81 ec e0 00 00 00 <0f> 29 70 c8 48 8b 05 fa ae 0f 00 48 33 c4 48 89 84 24 c0 00 00
Jul 3 00:40:43 fijii kernel: RIP <ffffc200022551fb>]
Jul 3 00:40:43 fijii kernel: RSP <ffff81011b991a48>
Jul 3 00:40:43 fijii kernel: — end trace 64eea59528dddfab ]—

I have a HP Pavillion tx1218ca and I am using the Windows XP driver provided by HP for this computer.

# lspci -v
03:00.0 Network controller: Broadcom Corporation BCM4328 802.11a/b/g/n (rev 03)
Subsystem: Hewlett-Packard Company Device 1366
Flags: bus master, fast devsel, latency 0, IRQ 19
Memory at c8000000 (64-bit, non-prefetchable) [size=16]
Memory at c9200000 (64-bit, prefetchable) [size=1]
Capabilities: [40] Power Management version 2
Capabilities: [58] Vendor Specific Information <?>
Capabilities: [e8] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Capabilities: [d0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting <?>
Capabilities: [13c] Virtual Channel <?>
Capabilities: [160] Device Serial Number 1a-00-71-ff-ff-73-df-b8
Capabilities: [16c] Power Budgeting <?>
Kernel driver in use: ndiswrapper
Kernel modules: ssb

# ndiswrapper -l[/size]
bcmwl5 : driver installed
device (14E4:4328) present (alternate driver: ssb)

# lsmod
Module Size Used by
ssb 56324 0
ndiswrapper 270016 0
xt_tcpudp 20480 7
xt_pkttype 18944 3
xt_physdev 19728 1
ipt_LOG 23428 11
xt_limit 20356 11
af_packet 42624 4
bridge 81192 1
bnep 35200 2
snd_pcm_oss 68992 0
ipt_REJECT 21120 3
snd_mixer_oss 35584 1 snd_pcm_oss
snd_seq 83600 0
snd_seq_device 26516 1 snd_seq
xt_state 19712 4
iptable_mangle 20608 0
iptable_nat 24976 0
nf_nat 39576 1 iptable_nat
iptable_filter 20736 1
nf_conntrack_netbios_ns 19968 0
nf_conntrack_ipv4 29576 7 iptable_nat,nf_nat
nf_conntrack 91536 5 xt_state,iptable_nat,nf_nat,nf_conntrack_netbios_ns,nf_conntrack_ipv4
ip_tables 39056 3 iptable_mangle,iptable_nat,iptable_filter
cpufreq_conservative 26248 0
cpufreq_userspace 23556 0
cpufreq_powersave 18816 0
ip6_tables 40720 0
x_tables 43144 10 xt_tcpudp,xt_pkttype,xt_physdev,ipt_LOG,xt_limit,ipt_REJECT,xt_state,iptable_nat,ip_tables,ip6_tables
powernow_k8 32772 1
binfmt_misc 30220 1
fuse 72256 1
loop 37508 0
dm_mod 88600 0
rfcomm 63392 4
l2cap 44160 12 bnep,rfcomm
snd_hda_intel 497452 1
snd_pcm 115208 2 snd_pcm_oss,snd_hda_intel
rtc_cmos 28728 0
snd_timer 45072 2 snd_seq,snd_pcm
rtc_core 41012 1 rtc_cmos
rtc_lib 20224 1 rtc_core
snd_page_alloc 28688 2 snd_hda_intel,snd_pcm
snd_hwdep 28424 1 snd_hda_intel
snd 96248 10 snd_pcm_oss,snd_mixer_oss,snd_seq,snd_seq_device,snd_hda_intel,snd_pcm,snd_timer,snd_hwdep
forcedeth 72588 0
k8temp 23040 0
soundcore 26000 1 snd
sg 56912 0
sr_mod 35636 0
cdrom 53416 1 sr_mod
uvcvideo 75912 0
compat_ioctl32 25984 1 uvcvideo
hci_usb 34716 0
video 43156 0
videodev 52096 2 uvcvideo,compat_ioctl32
output 21248 1 video
joydev 30848 0
wmi 26048 0
btusb 25496 2
v4l1_compat 29444 2 uvcvideo,videodev
battery 33672 0
i2c_nforce2 24192 0
pcmcia 61336 1 ssb
pcmcia_core 61604 1 pcmcia
ac 24328 0
button 27040 0
firmware_class 27776 1 pcmcia
i2c_core 45344 1 i2c_nforce2
bluetooth 82340 9 bnep,rfcomm,l2cap,hci_usb,btusb
usbhid 65488 0
hid 59296 1 usbhid
ff_memless 23176 1 usbhid
ehci_hcd 56204 0
ohci_hcd 42500 0
sd_mod 47280 4
usbcore 188248 8 ndiswrapper,uvcvideo,hci_usb,btusb,usbhid,ehci_hcd,ohci_hcd
edd 28176 0
ext3 170768 2
mbcache 27396 1 ext3
jbd 82240 1 ext3
fan 23944 0
pata_amd 33284 0
sata_nv 46860 3
libata 194976 2 pata_amd,sata_nv
scsi_mod 194904 4 sg,sr_mod,sd_mod,libata
dock 29344 1 libata
thermal 43040 0
processor 72668 2 powernow_k8,thermal[/size]

#15

Text was too long, here’s more :

# ifconfig -a
wlan0     Link encap:Ethernet  HWaddr 00:1A:73:71:B8:DF
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:19 Memory:c8000000-c8004000

# iwlist wlan0 scan
wlan0     Scan completed :
          Cell 01 - Address: 00:18:F8:70:BE:79
                    ESSID:"ctviwap"
                    Protocol:IEEE 802.11g
                    Mode:Managed
                    Frequency:2.412 GHz (Channel 1)
                    Quality:71/100  Signal level:-50 dBm  Noise level:-96 dBm
                    Encryption key:on
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
                              24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
                              12 Mb/s; 48 Mb/s
                    Extra:bcn_int=100
                    Extra:atim=0
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (2) : CCMP TKIP
                        Authentication Suites (1) : PSK
                    IE: WPA Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (2) : CCMP TKIP
                        Authentication Suites (1) : PSK
          Cell 02 - Address: 00:13:46:A5:AA:70
                    ESSID:"salman"
                    Protocol:IEEE 802.11g
                    Mode:Managed
                    Frequency:2.437 GHz (Channel 6)
                    Quality:14/100  Signal level:-87 dBm  Noise level:-96 dBm
                    Encryption key:off
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
                              12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
                              48 Mb/s; 54 Mb/s
                    Extra:bcn_int=100
                    Extra:atim=0
          Cell 03 - Address: 00:13:46:A3:34:2A
                    ESSID:"stef"
                    Protocol:IEEE 802.11g
                    Mode:Managed
                    Frequency:2.437 GHz (Channel 6)
                    Quality:20/100  Signal level:-83 dBm  Noise level:-96 dBm
                    Encryption key:on
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
                              12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
                              48 Mb/s; 54 Mb/s
                    Extra:bcn_int=100
                    Extra:atim=0
          Cell 04 - Address: 00:1C:10:19:C2:B7
                    ESSID:"Rivendell"
                    Protocol:IEEE 802.11g
                    Mode:Managed
                    Frequency:2.457 GHz (Channel 10)
                    Quality:43/100  Signal level:-68 dBm  Noise level:-96 dBm
                    Encryption key:on
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
                              24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
                              12 Mb/s; 48 Mb/s
                    Extra:bcn_int=100
                    Extra:atim=0
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : CCMP
                        Pairwise Ciphers (1) : CCMP
                        Authentication Suites (1) : PSK
          Cell 05 - Address: 00:0F:66:94:E0:C9
                    ESSID:"Rivendell"
                    Protocol:IEEE 802.11g
                    Mode:Managed
                    Frequency:2.462 GHz (Channel 11)
                    Quality:23/100  Signal level:-81 dBm  Noise level:-96 dBm
                    Encryption key:on
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
                              24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
                              12 Mb/s; 48 Mb/s
                    Extra:bcn_int=100
                    Extra:atim=0
                    IE: WPA Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (1) : TKIP
                        Authentication Suites (1) : PSK
#16

avinette wrote:
> I get a GPF when it freezes. Here is the output from
> /var/log/messages. Hopefully this will have some Novell Guru’s
> attention!
>
> Jul 3 00:40:43 fijii kernel: general protection fault: 0000 [1] SMP
> Jul 3 00:40:43 fijii kernel: last sysfs file:
> /sys/devices/system/cpu/cpu1/cache/index2/shared_cpu_map
> Jul 3 00:40:43 fijii kernel: CPU 1
> Jul 3 00:40:43 fijii kernel: Modules linked in: ssb ndiswrapper
> xt_tcpudp xt_pkttype xt_physdev ipt_LOG xt_limit af_packet bridge bnep
> snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device ipt_REJECT xt_state
> iptable_mangle iptable_nat nf_nat iptable_filter
> nf_conntrack_netbios_ns nf_conntrack_ipv4 nf_conntrack ip_tables
> cpufreq_conservative cpufreq_userspace cpufreq_powersave powernow_k8
> ip6_tables x_tables binfmt_misc fuse loop dm_mod rfcomm l2cap
> usbtouchscreen uvcvideo compat_ioctl32 videodev v4l1_compat hci_usb
> btusb bluetooth snd_hda_intel snd_pcm snd_timer rtc_cmos sr_mod
> snd_page_alloc rtc_core snd_hwdep joydev cdrom rtc_lib k8temp sg snd
> forcedeth soundcore i2c_nforce2 i2c_core video output usbhid pcmcia hid
> wmi pcmcia_core firmware_class battery button ff_memless ac ehci_hcd
> ohci_hcd sd_mod usbcore edd ext3 mbcache jbd fan pata_amd sata_nv
> libata scsi_mod dock thermal processor [last unloaded: ssb]
> Jul 3 00:40:43 fijii kernel: Pid: 5045, comm: ntos_wq Tainted: P
> N 2.6.25.5-1.1-default #1
> Jul 3 00:40:43 fijii kernel: RIP: 0010:<ffffc200022551fb>]
> <ffffc200022551fb>]
> Jul 3 00:40:43 fijii kernel: RSP: 0018:ffff81011b991a48 EFLAGS:
> 00010286
> Jul 3 00:40:43 fijii kernel: RAX: ffff81011b991b50 RBX:
> ffffc20001e06000 RCX: ffffc20001e06000
> Jul 3 00:40:43 fijii kernel: RDX: 0000000000000001 RSI:
> 0000000000000001 RDI: ffff81013b452b00
> Jul 3 00:40:43 fijii kernel: RBP: ffff81013b4522c0 R08:
> 0000000000000003 R09: 000000000000000c
> Jul 3 00:40:43 fijii kernel: R10: ffffc20002303840 R11:
> ffffc20001e01af0 R12: ffffc20001e01af0
> Jul 3 00:40:43 fijii kernel: R13: 0000000000000000 R14:
> 0000000000000000 R15: 00000000000000ff
> Jul 3 00:40:43 fijii kernel: FS: 00007f4ddb831700(0000)
> GS:ffff81013fa6da40(0000) knlGS:00000000f7d37af0
> Jul 3 00:40:43 fijii kernel: CS: 0010 DS: 0018 ES: 0018 CR0:
> 0000000080050033
> Jul 3 00:40:43 fijii kernel: CR2: 00000000008b8000 CR3:
> 000000011b952000 CR4: 00000000000006e0
> Jul 3 00:40:43 fijii kernel: DR0: 0000000000000000 DR1:
> 0000000000000000 DR2: 0000000000000000
> Jul 3 00:40:43 fijii kernel: DR3: 0000000000000000 DR6:
> 00000000ffff0ff0 DR7: 0000000000000400
> Jul 3 00:40:43 fijii kernel: Process ntos_wq (pid: 5045, threadinfo
> ffff81011b990000, task ffff81013e0d0500)
> Jul 3 00:40:43 fijii kernel: Stack: ffff8101064d2c3e ffff81011b991a60
> ffffffff8851c369 00000000ffffffff
> Jul 3 00:40:43 fijii kernel: ffffffff00000008 ffffc20001e061e3
> ffff8101064d2c3e ffffc200022470b5
> Jul 3 00:40:43 fijii kernel: ffffc20001e06101 000000000000c23b
> 000000000000002d ffffc20001e06000
> Jul 3 00:40:43 fijii kernel: Call Trace:
> Jul 3 00:40:43 fijii kernel: Inexact backtrace:
> Jul 3 00:40:43 fijii kernel:
> Jul 3 00:40:43 fijii kernel: <ffffffff8851c369>] ?
> :ndiswrapper:KeStallExecutionProcessor+0xb/0xe
> Jul 3 00:40:43 fijii kernel: <ffffffff803268e2>] ?
> __udelay+0x50/0x62
> Jul 3 00:40:43 fijii kernel: <ffffffff88527672>] ?
> :ndiswrapper:ExFreePoolWithTag+0x26/0x2f
> Jul 3 00:40:43 fijii kernel: <ffffffff88527686>] ?
> :ndiswrapper:ExFreePool+0xb/0xd
> Jul 3 00:40:43 fijii kernel: <ffffffff885210f1>] ?

Welcome to the space between a “rock and a hard place”.

Your crash is either happening in ndiswrapper or in the Windows driver. I doubt
that any Novell engineer will be able to do much, nor will any kernel developer
even look at the problem due to the tainted kernel. Unfortunately, there is no
open-source driver for the BCM4328 (yet). We are doing the reverse engineering now.

You should report this problem to the ndiswrapper people. They should be able to
tell if it is their bug or that of the Windows driver.

Larry

#17

Before using ndiswrapper I would try the following:

  1. Install the firmware as described above. Mine installed fine and I did not need bmcutter. However, try that if the firmware does not install.

  2. [ONLY APPLIES IF YOU ARE DUAL BOOTING] Boot into Windows and go to devices. Right click on your NIC (wired and wireless) and disable the power save mode. Then go into the power settings (advanced) and make sure nothing there is causing your NIC to go to sleep under Windows.

  3. Boot back to Suse and see if your card is detecting the presence of any ESSIDs. Do this by right clicking on the applet. If the wireless connection is grayed out or doesn’t show any connections do the following:

Make sure you have a wired connection working. (ethernet)

Open Networking using Yast. Create a new connection (delete any wireless connections you may already have) and enter all the information. Use the correct encryption method (WEP, WPA Personal or none) and make sure DHCP is clicked.

At the bottom click “Next” at each stage. After entering all the information click finish. It should take you to the configuration page. It will go thru about 10 steps and check them off. Then it will try to connect to a repository. It may fail the first time. However it should give you the option to “Retry.” At that point it will use the wired connection and download some configuration files.

When it is finished click “Finish” and the Yast window should close. If wireless is working you should see bars on the applet instead of the round circle.

Wireless should now be working. This procedure should be the same once you have the correct firmware installed for your NIC. Also, right clicking on the applet should now show a list of all nodes nearby. Click on yours and make sure there is an “x” beside it.