LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking > Linux - Wireless Networking
User Name
Password
Linux - Wireless Networking This forum is for the discussion of wireless networking in Linux.

Notices



Poll: Did this work?
Poll Options
Did this work?

You must log in and have one post to vote in this poll. If you don't have an account, you can register here.
Results will be available after the polls close.

The nominees are:

Yes
No

Reply
 
Search this Thread
Old 07-21-2007, 03:49 PM   #31
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,791
Blog Entries: 1

Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414

Quote:
sudo: gedit: command not found
That means either one of two things. Either gedit isn't installed or it isn't in a directory that is in the PATH. You don't have to use gedit, any text editor will do. You could also remove bmc43xx by hand with modprobe -r bcm43xx, but be sure to do that before you load the ndiswrapper module.
 
Old 07-28-2007, 12:30 PM   #32
Snipersnest
Member
 
Registered: Jan 2005
Location: SC
Distribution: Ubuntu 7.10 Gusty Gibbon
Posts: 269

Rep: Reputation: 30
Hi I used this guide and it didn't work for me. It removes any trace of wireless from my Ubuntu 7.04 and now I'm not sure how to install it again or how to get it to work.

I see a lot of talk about Firmware Cutter and such if this is what I need to do please link me to a tutorial or something. I've been trying to get my wireless working for a while with no luck.

Thanks!

Laptop
DV9010us HP
AMD
Broadcom 1390 Dell mini PCI rev01
 
Old 07-28-2007, 03:34 PM   #33
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,791
Blog Entries: 1

Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
Quote:
Hi I used this guide and it didn't work for me. It removes any trace of wireless from my Ubuntu 7.04 and now I'm not sure how to install it again or how to get it to work.
You'll have to provide details of what you did in order for anyone to help you undo it.
Quote:
I see a lot of talk about Firmware Cutter and such if this is what I need to do please link me to a tutorial or something.
The short answer is if you use bcm43xx, you need to install firmware, and that is done with the fwcutter program. I've got a brief tutorial on my help site (link is in my sig). If you're using ndiswrapper, you don't need to worry about installing firmware since it is in the Windows driver.
 
Old 07-28-2007, 03:41 PM   #34
Snipersnest
Member
 
Registered: Jan 2005
Location: SC
Distribution: Ubuntu 7.10 Gusty Gibbon
Posts: 269

Rep: Reputation: 30
Quote:
Originally Posted by Hangdog42
You'll have to provide details of what you did in order for anyone to help you undo it.


The short answer is if you use bcm43xx, you need to install firmware, and that is done with the fwcutter program. I've got a brief tutorial on my help site (link is in my sig). If you're using ndiswrapper, you don't need to worry about installing firmware since it is in the Windows driver.
I followed the instructions on this guide and it removes all traces of my wireless card. Every tutorial I've used does this.. and since I can neveer find help I have to reinstall everytime I want to try another one.

I don't know anything about wireless in linux. But it seems to go away after I reboot from following instructions.

{---{{ total wireless noob...will do anything asked to resolve this..then I will print it out so I don't lose them again.

PS your sig isn't there.
 
Old 07-29-2007, 08:24 AM   #35
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,791
Blog Entries: 1

Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
Quote:
I followed the instructions on this guide and it removes all traces of my wireless card. Every tutorial I've used does this.. and since I can neveer find help I have to reinstall everytime I want to try another one.
Lets try this again.... Did you blacklist bcm43xx? If so, does undoing the blacklisting help? Did you install ndiswrapper? How? Compiled or via a package? Were there any errors during the install? What happens when you run modprobe ndiswrapper? What is the output of lsmod before and after modprobe ndiswrapper? What is the output of iwconfig? Is there anything of interest in your system logs?

Since none of us can see your computer, you have to do the heavy lifting and post the details that we can use to help you.
Quote:
I don't know anything about wireless in linux. But it seems to go away after I reboot from following instructions.
You usually need to take steps to make the driver loading and configuration run each time at boot. If you haven't done that, then it would look like it goes away after a reboot.
Quote:
PS your sig isn't there.
It is, at least on my browser. The site is here.
 
Old 07-29-2007, 08:53 AM   #36
Snipersnest
Member
 
Registered: Jan 2005
Location: SC
Distribution: Ubuntu 7.10 Gusty Gibbon
Posts: 269

Rep: Reputation: 30
Quote:
Originally Posted by Hangdog42
Lets try this again.... Did you blacklist bcm43xx? If so, does undoing the blacklisting help? Did you install ndiswrapper? How? Compiled or via a package? Were there any errors during the install? What happens when you run modprobe ndiswrapper? What is the output of lsmod before and after modprobe ndiswrapper? What is the output of iwconfig? Is there anything of interest in your system logs?
Ok let me slow down a bit as I tend to rush things. I was able to get the wireless device back after removing the blacklist. When I blacklist the device and go about installing ndiswrapper from either package or compile I get the same results. No errors during install and ndiswrapper -l shows the hardware present driver installed (14E4:4311) stuff.. But I have no sign on GDM that its there. My lspci out put shows the device present. How do I check the IRQ its on?

One quick question before I get to deep. Does ndiswrapper and the nvidia driver still have problems with each other? I read that somewhere its probably old.

Thank for being patient. (I guess sigs only show if your signed in)
 
Old 07-29-2007, 09:02 AM   #37
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,791
Blog Entries: 1

Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
Quote:
Ok let me slow down a bit as I tend to rush things. I was able to get the wireless device back after removing the blacklist.
OK, that makes sense. Your system is detecting the card and loading bcm43xx. A quick run of lsmod should confirm this.

Quote:
When I blacklist the device and go about installing ndiswrapper from either package or compile I get the same results. No errors during install and ndiswrapper -l shows the hardware present driver installed (14E4:4311) stuff.. But I have no sign on GDM that its there. My lspci out put shows the device present. How do I check the IRQ its on?
I'm hoping that you're just missing a step here. Installing ndiswrapper isn't enough, you actually have to load it every time you want to use it (don't worry, it's easy to automate). Do you ever run modprobe ndiswrapper? That is the command that loads the ndiswrapper kernel module and should give you a functional wireless card (provided bcm43xx isn't loaded).
Quote:
One quick question before I get to deep. Does ndiswrapper and the nvidia driver still have problems with each other? I read that somewhere its probably old.
I haven't seen anyone with that problem for a bit, but that doesn't mean it isn't there. Lets look at the simple stuff first and if that doesn't work, then we'll think about nvidia problems.
 
Old 07-29-2007, 09:08 AM   #38
Snipersnest
Member
 
Registered: Jan 2005
Location: SC
Distribution: Ubuntu 7.10 Gusty Gibbon
Posts: 269

Rep: Reputation: 30
Quote:
Originally Posted by Hangdog42
OK, that makes sense. Your system is detecting the card and loading bcm43xx. A quick run of lsmod should confirm this.
ok I have 2 things here..Not sure if both are supposed to be present.
ndiswrapper xx(size) 0
bcm43xx xx(size) 0

Quote:
I'm hoping that you're just missing a step here. Installing ndiswrapper isn't enough, you actually have to load it every time you want to use it (don't worry, it's easy to automate). Do you ever run modprobe ndiswrapper? That is the command that loads the ndiswrapper kernel module and should give you a functional wireless card (provided bcm43xx isn't loaded).
I've done this too still never had it come up after a reboot. The only way I've ever seen the wireless device in the network settings is to unblacklist the device.
 
Old 07-29-2007, 09:20 AM   #39
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,791
Blog Entries: 1

Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
Quote:
ok I have 2 things here..Not sure if both are supposed to be present.
ndiswrapper xx(size) 0
bcm43xx xx(size) 0
No, only one should be present in the output of lsmod. To remove one, use the modprobe -r command. So to remove ndiswrapper, it would be modprobe -r ndiswrapper and to remove bcm43xx it would be modprobe -r bcm43xx.

If you have both modules loaded at the same time, they will conflict.

Quote:
I've done this too still never had it come up after a reboot. The only way I've ever seen the wireless device in the network settings is to unblacklist the device.
That means one of two things. Either the blacklisting isn't working and the two drivers are conflicting or ndiswrapper is having problems all by itself.

OK, here is what I would do. Use modprobe and unload both ndiswrapper and bcm43xx. Then reload ndiswrapper. Check lsmod to make sure that bcm43xx isn't loaded. Then have a look at the output of iwconfig. If you see a wireless device there, you can configure it and hopefully it will work. If you don't see a wireless device, check your log files (/var/log/syslog, /var/log/messages and the output of the dmesg command) and see if ndiswrapper is leaving any clues.
 
Old 07-29-2007, 09:31 AM   #40
Snipersnest
Member
 
Registered: Jan 2005
Location: SC
Distribution: Ubuntu 7.10 Gusty Gibbon
Posts: 269

Rep: Reputation: 30
Quote:
Originally Posted by Hangdog42
OK, here is what I would do. Use modprobe and unload both ndiswrapper and bcm43xx. Then reload ndiswrapper. Check lsmod to make sure that bcm43xx isn't loaded. Then have a look at the output of iwconfig. If you see a wireless device there, you can configure it and hopefully it will work. If you don't see a wireless device, check your log files (/var/log/syslog, /var/log/messages and the output of the dmesg command) and see if ndiswrapper is leaving any clues.
Ok removed the 2 devices and redid packaged ndiswrapper (1.38). Modprobed and wireless is gone again. lsmod shows ndiswrapper and no sign of bcm43xx. iwconfig shows lo - no wireless extensions and eth0 no wireless extensions.

Code:
Jul 29 08:26:25 nate-laptop kernel: [ 1290.956000] ndiswrapper version 1.38 loaded (preempt=no,smp=yes)
Jul 29 08:26:25 nate-laptop kernel: [ 1291.116000] ndiswrapper: driver bcmwl5 (Broadcom,10/12/2006, 4.100.15.5) loaded
Jul 29 08:26:25 nate-laptop kernel: [ 1291.116000] PCI: No IRQ known for interrupt pin A of device 0000:03:00.0. Probably buggy MP table.
Jul 29 08:26:25 nate-laptop kernel: [ 1291.116000] PCI: Setting latency timer of device 0000:03:00.0 to 64
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000] IRQ handler type mismatch for IRQ 0
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000] current handler: timer
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000]  [setup_irq+302/480] setup_irq+0x12e/0x1e0
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000]  [<f8baf8d0>] ndis_isr+0x0/0xc0 [ndiswrapper]
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000]  [request_irq+163/192] request_irq+0xa3/0xc0
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000]  [<f8bae22b>] NdisMRegisterInterrupt+0x9b/0x120 [ndiswrapper]
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000]  [<f8bb28f1>] ExAllocatePoolWithTag+0x31/0x1c0 [ndiswrapper]
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000]  [<f8bbdfa4>] miniport_init+0xa4/0x170 [ndiswrapper]
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000]  [<f8bbe1c9>] NdisDispatchPnp+0xd9/0xd80 [ndiswrapper]
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000]  [__activate_task+33/64] __activate_task+0x21/0x40
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000]  [try_to_wake_up+70/1152] try_to_wake_up+0x46/0x480
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000]  [kprobe_flush_task+68/144] kprobe_flush_task+0x44/0x90
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000]  [schedule+2261/2704] __sched_text_start+0x8d5/0xa90
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000]  [kprobe_flush_task+68/144] kprobe_flush_task+0x44/0x90
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000]  [schedule+2261/2704] __sched_text_start+0x8d5/0xa90
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000]  [<f8bb7488>] IoAllocateIrp+0x68/0xa0 [ndiswrapper]
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000]  [<f8bb7f95>] IoBuildAsynchronousFsdRequest+0x35/0x170 [ndiswrapper]
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000]  [<f8bb25c1>] get_current_nt_thread+0xc1/0xf0 [ndiswrapper]
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000]  [<f8bb80eb>] IoQueueThreadIrp+0x1b/0x130 [ndiswrapper]
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000]  [<f8bb712a>] IofCallDriver+0x3a/0xa0 [ndiswrapper]
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000]  [<f8bbc8ab>] IoSendIrpTopDev+0xbb/0x120 [ndiswrapper]
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000]  [<f8bbcc03>] pnp_start_device+0x53/0xb0 [ndiswrapper]
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000]  [<f8bbce33>] wrap_pnp_start_device+0x1d3/0x280 [ndiswrapper]
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000]  [<f8bbcf25>] wrap_pnp_start_pci_device+0x45/0x50 [ndiswrapper]
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000]  [sysfs_dirent_exist+69/112] sysfs_dirent_exist+0x45/0x70
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000]  [sysfs_create_link+110/352] sysfs_create_link+0x6e/0x160
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000]  [pci_match_device+19/192] pci_match_device+0x13/0xc0
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000]  [<f8bbcee0>] wrap_pnp_start_pci_device+0x0/0x50 [ndiswrapper]
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000]  [<f8bbcee0>] wrap_pnp_start_pci_device+0x0/0x50 [ndiswrapper]
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000]  [pci_device_probe+86/128] pci_device_probe+0x56/0x80
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000]  [really_probe+102/400] really_probe+0x66/0x190
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000]  [driver_probe_device+73/192] driver_probe_device+0x49/0xc0
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000]  [__driver_attach+158/160] __driver_attach+0x9e/0xa0
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000]  [bus_for_each_dev+59/96] bus_for_each_dev+0x3b/0x60
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000]  [driver_attach+36/48] driver_attach+0x24/0x30
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000]  [__driver_attach+0/160] __driver_attach+0x0/0xa0
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000]  [bus_add_driver+123/416] bus_add_driver+0x7b/0x1a0
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000]  [__pci_register_driver+116/192] __pci_register_driver+0x74/0xc0
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000]  [<f8baae62>] loader_init+0x102/0x220 [ndiswrapper]
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000]  [<f8bb966f>] wrap_procfs_init+0x3f/0xb0 [ndiswrapper]
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000]  [<f89ee0c7>] wrapper_init+0xc7/0xd3 [ndiswrapper]
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000]  [sys_init_module+349/7072] sys_init_module+0x15d/0x1ba0
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000]  [sys_mmap2+205/208] sys_mmap2+0xcd/0xd0
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000]  [sysenter_past_esp+105/169] sysenter_past_esp+0x69/0xa9
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000]  =======================
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000] ndiswrapper: request for IRQ 0 failed
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000] ndiswrapper (miniport_init:275): couldn't initialize device: C000009A
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000] ndiswrapper (pnp_start_device:426): Windows driver couldn't initialize the device (C0000001)
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000] unregister_netdevice: device eth%%d/f58d8000 never was registered
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000] ndiswrapper (miniport_halt:339): device f58d8400 is not initialized - not halting
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000] Trying to free already-free IRQ 0
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000] ndiswrapper: device eth%%d removed
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000] ndiswrapper: probe of 0000:03:00.0 failed with error -22
Jul 29 08:26:25 nate-laptop kernel: [ 1291.208000] usbcore: registered new interface driver ndiswrapper
Jul 29 08:26:34 nate-laptop gconfd (root-7147): starting (version 2.18.0.1), pid 7147 user 'root'
Jul 29 08:26:34 nate-laptop gconfd (root-7147): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Jul 29 08:26:34 nate-laptop gconfd (root-7147): Resolved address "xml:readwrite:/root/.gconf" to a writable configuration source at position 1
Jul 29 08:26:34 nate-laptop gconfd (root-7147): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Jul 29 08:26:34 nate-laptop gconfd (root-7147): Resolved address "xml:readonly:/var/lib/gconf/debian.defaults" to a read-only configuration source at position 3
Jul 29 08:26:34 nate-laptop gconfd (root-7147): Resolved address "xml:readonly:/var/lib/gconf/defaults" to a read-only configuration source at position 4
Jul 29 08:27:05 nate-laptop gconfd (root-7147): GConf server is not in use, shutting down.
Jul 29 08:27:05 nate-laptop gconfd (root-7147): Exiting

Last edited by Snipersnest; 07-29-2007 at 09:33 AM.
 
Old 07-29-2007, 10:41 AM   #41
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,791
Blog Entries: 1

Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
Quote:
Jul 29 08:26:25 nate-laptop kernel: [ 1291.120000] ndiswrapper: probe of 0000:03:00.0 failed with error -22
OK, something is going wrong with ndiswrapper. Unfortunately their wiki doesn't seem to list their error codes, so I'm not sure what error -22 is.
Quote:
packaged ndiswrapper (1.38)
Two things here. There are significantly newer versions of ndiswrapper available on their site, and that might help. The other thing is that ndiswrapper absolutely MUST be compiled against your kernel. Usually if you're using a stock kernel for your distro, this isn't a problem. However, I've seen some of the automated software installation program install the wrong version of ndiswrapper and cause all sorts of trouble.

So I'm going to suggest that you compile it from source. As long as you have the source code for your kernel installed, it is drop-dead easy:

1) Download the newest stable source from the ndiswrapper site (avoid any rc versions)
2) Unpack the ndiswrapper tarball.
3) Remove the existing ndiswrapper package you installed
4) Drop into the directory created when you unpacked ndiswrapper and run make
5) As root, run make install
6) If you didn't get any errors for steps 4 and 5, then load the new ndiswrapper module with modprobe and check that it sees the card (ndiswrapper -l) Then check and see if you get a wireless card in iwconfig.
 
Old 07-29-2007, 11:18 AM   #42
Snipersnest
Member
 
Registered: Jan 2005
Location: SC
Distribution: Ubuntu 7.10 Gusty Gibbon
Posts: 269

Rep: Reputation: 30
Quote:
Originally Posted by Hangdog42
OK, something is going wrong with ndiswrapper. Unfortunately their wiki doesn't seem to list their error codes, so I'm not sure what error -22 is.


Two things here. There are significantly newer versions of ndiswrapper available on their site, and that might help. The other thing is that ndiswrapper absolutely MUST be compiled against your kernel. Usually if you're using a stock kernel for your distro, this isn't a problem. However, I've seen some of the automated software installation program install the wrong version of ndiswrapper and cause all sorts of trouble.

So I'm going to suggest that you compile it from source. As long as you have the source code for your kernel installed, it is drop-dead easy:

1) Download the newest stable source from the ndiswrapper site (avoid any rc versions)
2) Unpack the ndiswrapper tarball.
3) Remove the existing ndiswrapper package you installed
4) Drop into the directory created when you unpacked ndiswrapper and run make
5) As root, run make install
6) If you didn't get any errors for steps 4 and 5, then load the new ndiswrapper module with modprobe and check that it sees the card (ndiswrapper -l) Then check and see if you get a wireless card in iwconfig.
Ok I don't get any errors following your steps. However I get the same results from iwconfig that I posted earlier.

/var/log/syslog
Code:
Jul 29 10:04:37 nate-laptop kernel: [ 7182.888000] usbcore: deregistering interface driver ndiswrapper
Jul 29 10:04:37 nate-laptop kernel: [ 7182.892000] ndiswrapper (ntoskernel_exit:282): object f59113a0 type 2 was not freed, freeing it now
Jul 29 10:08:38 nate-laptop loadndisdriver: loadndisdriver: load_device(426): couldn't chdir to /etc/ndiswrapper: No such file or directory 
Jul 29 10:08:38 nate-laptop last message repeated 2 times
Jul 29 10:08:38 nate-laptop kernel: [ 7423.076000] ndiswrapper version 1.47 loaded (smp=yes)
Jul 29 10:08:38 nate-laptop loadndisdriver: loadndisdriver: load_device(426): couldn't chdir to /etc/ndiswrapper: No such file or directory 
Jul 29 10:08:38 nate-laptop last message repeated 17 times
Jul 29 10:08:38 nate-laptop kernel: [ 7423.184000] usbcore: registered new interface driver ndiswrapper
oh btw I had removed the previous installed driver. I think thats why the log is saying no such file or directory there. I reinstalled the driver and it comes up with ndiswrapper -l.
Code:
bcmwl5 : driver installed
        device (14E4:4311) present (alternate driver: bcm43xx)
heres another question...could these errors be because of the start options I use for grub? I was reading that with the DV9xxx laptops the ACPI and stuff screws up USB and a few other things.

noacpi acpi=off pnpbios=off pci=assign-busses so on and so on..I can't remember how to pull the menu.lst up to tell you exactly what options I have.
 
Old 07-29-2007, 06:20 PM   #43
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,791
Blog Entries: 1

Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
Something is SERIOUSLY screwed up here:
Quote:
Jul 29 10:08:38 nate-laptop loadndisdriver: loadndisdriver: load_device(426): couldn't chdir to /etc/ndiswrapper: No such file or directory
Jul 29 10:08:38 nate-laptop last message repeated 17 times
That simply shouldn't be happening if you've installed a windows driver with ndiswrapper -i. If this error is from before you installed the driver, remove and reload ndiswrapper and see if it is still there.

Quote:
heres another question...could these errors be because of the start options I use for grub? I was reading that with the DV9xxx laptops the ACPI and stuff screws up USB and a few other things.
I know acpi can cause trouble in some laptops. However, before messing around with your boot config, I would first try installing firmware and giving bcm43xx a try.

And please, please, PLEASE tell me this thing isn't a USB wireless card.

I'd google for how to pull up your boot options. I'm a LILO user, so I don't really have much experience with GRUB.
 
Old 07-29-2007, 06:28 PM   #44
Snipersnest
Member
 
Registered: Jan 2005
Location: SC
Distribution: Ubuntu 7.10 Gusty Gibbon
Posts: 269

Rep: Reputation: 30
Quote:
Originally Posted by Hangdog42
I know acpi can cause trouble in some laptops. However, before messing around with your boot config, I would first try installing firmware and giving bcm43xx a try.

And please, please, PLEASE tell me this thing isn't a USB wireless card.

I'd google for how to pull up your boot options. I'm a LILO user, so I don't really have much experience with GRUB.
Ok thats not what I wanted to hear :P Ok do you have a good starter for doing fwcutter and howto use/install it? I really wanted to showcase this laptop so people can see Ubuntu. Oh and no its NOT USB...its the built in PCI-E type.

I will google up some boot options for Grub. I may just try the noacpi setting and see if that fixes anything directly. Thank you for trying to help me fix this issue.

Last edited by Snipersnest; 07-29-2007 at 06:30 PM.
 
Old 07-30-2007, 04:35 AM   #45
pappy_mcfae
Member
 
Registered: Feb 2007
Location: Dallas
Distribution: Gentoo x86 & x86_64
Posts: 190

Rep: Reputation: 30
Post Forgive me for interrupting...

...but it seems there is more to your problem than meets the eye. These things should be checked...

1) check your kernel version. Is it 2.4.x or 2.6.x? Enter uname-r. If it's not a 2.6 kernel, my experience indicates that ndiswrapper won't work properly when you need it most. It will install, load itself as a module, and so on. However, when it comes to boot time, it's a no dice scenario.
2) If you compiled your kernel, did you include wireless extensions? If you didn't, or if you didn't enable all of them, once again, ndiswrapper loads incorrectly.
3) ndiswrapper initializes the adapter. If your wireless router is set for anything but a COMPLETELY open network, you will also need wpa_supplicant.
4) Once ndiswrapper brings up the adapter, and wpa_supplicant gains access to your wireless router, you also need to set an IP address for the wireless adapter.

Might I suggest you take a look at my step-by-step instructions for getting bcm43xx wireless adapters going? While it's specifically written for Slackware, much will cross over to other distributions; such as the idea that you should compile ndiswrapper directly from source code. Don't count on the version that comes on your install disk (if applicable) to be functional. Ndiswrapper is compiled to work with your specific kernel. The only way to insure that happens as it should is to compile ndiswrapper from source.

While getting a wireless network operating properly under Linux is no cakewalk like it is under Windoze, it is a very doable kind of thing. I have done it five times already. Once on this machine, and four different times on my other laptop. Now, not only does the wireless network work under Linux, with the addition of my wireless restore script, the wireless network is actually much more stable, and more likely to come back gracefully from a hiccup under Linux than XP.

As strange as that statement might seem, it is very true. Sometimes the wireless adapter gets squirrelly under XP. When that happens, the wireless network will sit there, sometimes for fifteen minutes or more trying to re-establish an IP address. Sometimes, when things get really weird, the "repair" button gets pushed, too. Even when that step is taken, sometimes the wireless network remains down. Under Linux, if the wireless adapter gets squirrelly, invoking my script gets the wireless network back up in less than fifteen seconds. Once up, it stays up, especially if I am jamming on internet radio.

I agree with Hangdog42; you need to be mellow about the situation. Getting upset at Linux makes it that much harder to fix bugs and tweak the system. The fact that you can get online means you aren't tied to your wireless adapter. If you look it as more of an experiment than a mandatory thing, you might get a little bit ahead of where you are.

I hope the situation works out for you. Getting a wireless network functional under Linux can be a real pain in the posterior. However, once you get it working, it works as reliably (or better) under Linux as it does under Windoze XP.

Blessed be!
Pappy
 
  


Reply

Tags
adapter, airforce, bcm43xx, broadcom, ndiswrapper, ubuntu, wireless


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Broadcom BCM4401 Drivers Veratien Linux - Hardware 8 08-12-2007 02:04 AM
Native Broadcom wireless driver and Devicescape stack HowTo Hangdog42 Linux - Wireless Networking 12 01-17-2007 07:55 AM
Does new Linux bcm43xx driver for Broadcom wireless cards work on a HP ze4805us? svarmido Linux - Hardware 4 10-10-2006 04:02 AM
bcm43xx and Broadcom 4319 josemari37 Linux - Hardware 3 10-04-2006 05:29 PM
plain english install of softmac/bcm43xx wireless drivers please.... wasted38 Linux - Wireless Networking 7 03-04-2006 12:41 PM


All times are GMT -5. The time now is 12:41 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration