Almost have the wireless up

05-20-2009	#1 (permalink)
Seraphan Just Joined! Join Date: Mar 2009 Posts: 15	[SOLVED] Almost have the wireless up About a month ago I posted trying to get my wireless working. I gave up after a week or so when Ndiswrapper wasn't working. Turns out I didn't have the kernel headers installed so I'm back for round two. After getting Ndis up and working and the driver installed, this is what I get: Code: ndiswrapper -l bcmwl5 : driver installed device (14E4:4328) present (alternate driver: ssb) I've searched all over forums and found the same problems but the solutions haven't changed anything. When I go to network and create a new wireless connection, ndiswrapper doesn't show up in the devices. It just shows "Other Wireless Card". Thanks.

05-20-2009	#2 (permalink)
reed9 Linux Guru Join Date: Feb 2009 Location: Boston, MA Posts: 2,199	You've loaded ndiswrapper module via mopdrobe ndiswrapper? You've added it to /etc/modules to load at boot time as well? Does a wireless device show up when you type iwconfig? Please post the output of lsmod. __________________ The Arch Way How to Ask Questions the Smart Way Registered Linux User #482863

05-20-2009

#3 (permalink)

Seraphan

Just Joined!

Join Date: Mar 2009

Posts: 15

I did a modprobe after the driver was installed. Output of iwconfig:

Code:

lo        no wireless extensions.

eth0      no wireless extensions.

pan0      no wireless extensions.

and lsmod:

Code:

Module                  Size  Used by
fuse                   49436  2 
sco                    12932  2 
bridge                 43796  0 
stp                     6148  1 bridge
bnep                   14848  2 
l2cap                  21504  3 bnep
bluetooth              48608  5 sco,bnep,l2cap
sunrpc                156052  3 
ip6t_REJECT             7296  2 
nf_conntrack_ipv6      15864  2 
ip6table_filter         6400  1 
ip6_tables             14736  1 ip6table_filter
ipv6                  230516  28 ip6t_REJECT,nf_conntrack_ipv6
cpufreq_ondemand        9996  2 
acpi_cpufreq           12172  0 
dm_multipath           17164  0 
uinput                 10624  0 
snd_hda_intel         354068  3 
snd_seq_dummy           6660  0 
nvidia               7223280  52 
snd_seq_oss            30364  0 
snd_seq_midi_event      9600  1 snd_seq_oss
snd_seq                48576  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device         10124  3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_pcm_oss            42496  0 
snd_mixer_oss          16896  1 snd_pcm_oss
snd_pcm                65924  2 snd_hda_intel,snd_pcm_oss
snd_timer              22024  2 snd_seq,snd_pcm
snd_page_alloc         11016  2 snd_hda_intel,snd_pcm
b43                   131872  0 
firewire_ohci          22532  0 
rfkill                 11160  1 b43
snd_hwdep              10500  1 snd_hda_intel
mac80211              174052  1 b43
sdhci_pci              10624  0 
cfg80211               24072  1 mac80211
input_polldev           7176  1 b43
tg3                   107268  0 
libphy                 18560  1 tg3
firewire_core          35616  1 firewire_ohci
crc_itu_t               5760  1 firewire_core
ricoh_mmc               7552  0 
snd                    50616  16 snd_hda_intel,snd_seq_dummy,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer,snd_hwdep
soundcore               9416  1 snd
i2c_i801               12048  0 
ssb                    36228  1 b43
sdhci                  17796  1 sdhci_pci
mmc_core               43676  1 sdhci
iTCO_wdt               13732  0 
iTCO_vendor_support     6916  1 iTCO_wdt
i2c_core               21396  2 nvidia,i2c_i801
pcspkr                  6272  0 
video                  20500  6 
output                  6528  1 video
joydev                 12736  0 
wmi                     9768  0 
dcdbas                 10272  0 
ata_generic             8452  0 
pata_acpi               7680  0

05-20-2009	#4 (permalink)
reed9 Linux Guru Join Date: Feb 2009 Location: Boston, MA Posts: 2,199	Hmm, well, ndiswrapper is not listed as loaded, but the b43 driver is. You need to blacklist the b43 driver; it will interfere with ndiswrapper. Add to /etc/modprobe.d a line reading: blacklist b43 Note that you need to be root to write to this file. Remove it from your modules Code: su - modprobe -r b43 Load the windows driver and ndiswrapper module, and restart the network. You said in your other post you're using Fedora 8, right? Code: su - ndiswrapper -i driver-name.inf ndiswrapper -m service NetworkManager restart service NetworkManagerDispatcher restart service network restart __________________ The Arch Way How to Ask Questions the Smart Way Registered Linux User #482863

05-20-2009	#5 (permalink)
reed9 Linux Guru Join Date: Feb 2009 Location: Boston, MA Posts: 2,199	Whoops, forgot to mention after ndiswrapper -m, to do modprobe ndiswrapper __________________ The Arch Way How to Ask Questions the Smart Way Registered Linux User #482863

05-20-2009	#6 (permalink)
Seraphan Just Joined! Join Date: Mar 2009 Posts: 15	Couldn't remember if I did that so I typed it in and got Code: module configuration already contains alias directive module configuration already contains alias directive

05-20-2009	#7 (permalink)
waterhead Trusted Penguin Join Date: Jul 2004 Location: Franklin, Wisconsin Posts: 3,957	Since it is automatically loading the b43 driver, I would recommend just using that driver. It makes things a lot easier, too. You would need to install the proprietary firmware. How this is done is dependent on the Linux version that you are using. If you are interested in going this route, I would first like to know the exact wireless card that you have. Please post the output of this command. Code: lsmod __________________ Paul Please do not PM me with requests for help. I will not reply.

05-20-2009

#8 (permalink)

Seraphan

Just Joined!

Join Date: Mar 2009

Posts: 15

Edit: I missed your post about the blacklisting, reed. After going through all that, I got a connection and now using my wireless. Thanks a bunch for the quick replies guys.

Edit again: I restarted the computer and lost the wireless connection. When I restart the network I get this:

Code:

Shutting down interface eth0:                              [  OK  ]
Shutting down loopback interface:                          [  OK  ]
Bringing up loopback interface:                            [  OK  ]
Bringing up interface eth0:  
Determining IP information for eth0... done.
                                                           [  OK  ]
Bringing up interface wlan0:  ndiswrapper device wlan0 does not seem to be present, delaying initialization.
                                                           [FAILED]

So back where I was, here is the lsmod:

Code:

Module                  Size  Used by
sit                    12804  0 
tunnel4                 6792  1 sit
ndiswrapper           155284  0 
fuse                   49436  2 
sco                    12932  2 
bridge                 43796  0 
stp                     6148  1 bridge
bnep                   14848  2 
l2cap                  21504  3 bnep
bluetooth              48608  5 sco,bnep,l2cap
sunrpc                156052  3 
ip6t_REJECT             7296  2 
nf_conntrack_ipv6      15864  2 
ip6table_filter         6400  1 
ip6_tables             14736  1 ip6table_filter
ipv6                  230516  29 sit,ip6t_REJECT,nf_conntrack_ipv6
cpufreq_ondemand        9996  2 
acpi_cpufreq           12172  0 
dm_multipath           17164  0 
uinput                 10624  0 
snd_hda_intel         354068  3 
snd_seq_dummy           6660  0 
snd_seq_oss            30364  0 
nvidia               7223280  28 
snd_seq_midi_event      9600  1 snd_seq_oss
snd_seq                48576  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
sdhci_pci              10624  0 
firewire_ohci          22532  0 
snd_seq_device         10124  3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_pcm_oss            42496  0 
snd_mixer_oss          16896  1 snd_pcm_oss
snd_pcm                65924  2 snd_hda_intel,snd_pcm_oss
firewire_core          35616  1 firewire_ohci
crc_itu_t               5760  1 firewire_core
tg3                   107268  0 
libphy                 18560  1 tg3
i2c_i801               12048  0 
pcspkr                  6272  0 
sdhci                  17796  1 sdhci_pci
mmc_core               43676  1 sdhci
i2c_core               21396  2 nvidia,i2c_i801
snd_timer              22024  2 snd_seq,snd_pcm
snd_page_alloc         11016  2 snd_hda_intel,snd_pcm
snd_hwdep              10500  1 snd_hda_intel
snd                    50616  16 snd_hda_intel,snd_seq_dummy,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer,snd_hwdep
joydev                 12736  0 
soundcore               9416  1 snd
iTCO_wdt               13732  0 
iTCO_vendor_support     6916  1 iTCO_wdt
dcdbas                 10272  0 
video                  20500  6 
output                  6528  1 video
wmi                     9768  0 
ata_generic             8452  0 
pata_acpi               7680  0

If it makes a difference, I'm using Fedora 10 with the 2.6.27.21-170 kernel.

05-21-2009	#9 (permalink)
waterhead Trusted Penguin Join Date: Jul 2004 Location: Franklin, Wisconsin Posts: 3,957	I got my "ls" commands mixed up. What I really wanted was the output of this command. Code: lspci Using the b43 driver would mean undoing everything that you just did to enable the NDISwrapper driver. If it matters to you, b43 is a true Linux driver, that is in the Linux kernel. NDISwrapper is a "hack" that uses the WindowsXP driver to get the wireless to work. The b43 driver is actually a better driver, but in the end what matters is if the wireless works. Since you seem to have it working, stick with what works. __________________ Paul Please do not PM me with requests for help. I will not reply.

05-21-2009

#10 (permalink)

Seraphan

Just Joined!

Join Date: Mar 2009

Posts: 15

It worked before I rebooted now its back at step one. Here's the lspci:

Code:

00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03)
00:01.0 PCI bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express PCI Express Root Port (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 01)
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 01)
00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 01)
00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 01)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 01)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 01)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 01)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 01)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e1)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 01)
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Controller (rev 01)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 01)
01:00.0 VGA compatible controller: nVidia Corporation GeForce Go 7900 GTX (rev a1)
03:01.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller
03:01.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 19)
03:01.2 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 0a)
03:01.3 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 05)
09:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5752 Gigabit Ethernet PCI Express (rev 02)
0c:00.0 Network controller: Broadcom Corporation BCM4328 802.11a/b/g/n (rev 01)

My wifi light is on so its getting power unlike before but I can't find the card (other than ndis) in the system-network and its not being found.

Are you a Linux Guru who is willing to share your in-depth Linux knowledge? Try our new Article submission system.