Disk Check Broke my Wireless?

I have a BCM4308 wireless card, and I've had it successfully (for the most part) running for a few weeks after installing (wrestling with?) ndiswrapper.

Last night, I booted up my laptop at a friends house, and it forced me to do my quot;once every 30 bootsquot; disk-check. A minor annoyance, but no problem, right?

Unfortunately, there was a problem. After booting, I could not connect to my friend's WiFi. The wireless had been working the evening before in a Hotel, and the morning before at my home. The only thing that had changed (if it's a change) is the Disk Check.

As it stands, the wireless interface is quot;stuckquot; in roaming mode. I can click on the Network Manager icon in the system tray, and the drop down menu shows the available networks (as it normally would in roaming mode). What's more, it showed my friend's network when I was at his house, and mine in my own, so, the card is detecting and showing the correct networks.

The problem is that I cannot connect to them. They show (and I know they have) decent signal strength, but when I click on them, the changes into the quot;connectingquot; icon (swirling blue) for a few minutes, then back to the quot;no connectionquot; icon.

When I open the manual network configuration, I unclick Enable Roaming Mode, and click the dropdown menu for quot;Network Name.quot; It won't detect and show the same networks that it is doing in roaming mode! So, since I can't pick a network, I can't take it out of roaming mode. I can type in my network name, but that won't connect either.

So, any suggestions? I have an ethernet connection (and a desktop without this problem) so I can connect the laptop and access the repositories if I need to.

I've tried going through the process of installing the drivers through ndiswrapper again, but each step tells me that it's already been done.

Also, and I don't kno if this is related, but the actual configuration window for my wireless module is odd. Its title in the title-bar is way offset (pic included). I don't know whether or not that's related.

Thanks in advance for any advice.

Bump?

just for fun try

   sudo ifdown -a    sudo ifup -a

see if that does any thing

Originally Posted by killdragonjust for fun try

   sudo ifdown -a    sudo ifup -a

see if that does any thing

Tried it, unfortunately no change.

Here's the output:Code:
mason@mason-laptop:~$ sudo ifdown -a
Password:
RTNETLINK answers: No such process
There is already a pid file /var/run/dhclient.eth0.pid with pid 5378
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit  from : localhost/on LPF/eth0/00:0d:56:39:8a:df
Sending on LPF/eth0/00:0d:56:39:8a:df
Sending on Socket/fallback
DHCPRELEASE on eth0 to 192.168.1.1 port 67
mason@mason-laptop:~$ sudo ifup -a
eth2: ERROR while getting interface flags: No such device
There is already a pid file /var/run/dhclient.eth2.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit  from : localhost/No such device
eth2: ERROR while getting interface flags: No such device
eth2: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up eth2.
ath0: ERROR while getting interface flags: No such device
There is already a pid file /var/run/dhclient.ath0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit  from : localhost/No such device
ath0: ERROR while getting interface flags: No such device
ath0: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up ath0.
There is already a pid file /var/run/dhclient.eth0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit  from : localhost/on LPF/eth0/00:0d:56:39:8a:df
Sending on LPF/eth0/00:0d:56:39:8a:df
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
I don't know what any of that means though.

Hi, I was looking around and saw some user's are using fwcutter along with nisdwrapper to get their cards working have you tried that?

try this -

code: ifconfig

identify your wifi card - if there are a few entries give them all ago
they will be called something like eth1

code: sudo ifconfig eth1 up
code: sudo eth1 scanning

If it says it can't scan or something try another entry

code: iwlist

Find the wireless network and note its quot;essidquot;
in my case belkin54g

code : sudo iwconfig eth1 essid belkin54g
code : sudo dhclient

Lots of stuff will scroll down but it should only take a few seconds if it works then hopefully you have wireless!

try
code: ping
or something to see if it worked

Originally Posted by killdragonHi, I was looking around and saw some user's are using fwcutter along with nisdwrapper to get their cards working have you tried that?

I had read, a little over a month ago when I first installed  and discovered this wireless card problem. I'm wary of the fcutter though because it directly effects the hardware and I need the card to be able to connect under an XP boot as well. Plus, the speeds reported weren't as good.

Plus, I had it working without the cutter for almost a month, so I know it does work, at full speed, without it. Something I did somehow changed something. Just need to figure that out.

I'll keep it in mind if nothing else works though, thank you.Originally Posted by Ultra Magnustry this -

Had a few issues. I'll break it up so you can follow what I tried.Originally Posted by Ultra Magnuscode: ifconfigCode:
mason@mason-laptop:~$ code: ifconfig
bash: code:: command not found
mason@mason-laptop:~$ ifconfig
eth0    Link encap:Ethernet  HWaddr 00:0D:56:39:8A

F 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:11

eth0:avah Link encap:Ethernet HWaddr 00:0D:56:39:8A

F inet addr:169.254.7.232 Bcast:169.254.255.255 Mask:255.255.0.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 Interrupt:11

lo Link encap

ocal Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:10 errors:0 dropped:0 overruns:0 frame:0 TX packets:10 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:710 (710.0 b) TX bytes:710 (710.0 b)

wlan0 Link encap:Ethernet HWaddr 00:90:4B:16:51:06 inet6 addr: fe80::290:4bff:fe16:5106/64 Scope

ink       UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1       RX packets:8946 errors:0 dropped:0 overruns:0 frame:0       TX packets:24 errors:0 dropped:0 overruns:0 carrier:0       collisions:0 txqueuelen:1000       RX bytes:482006 (470.7 KiB)  TX bytes:1872 (1.8 KiB)       Interrupt:5 Memory:faff6000-faff8000
This is odd, because my wireless used to be called eth1, and there was no wlan0 module. (But it worked.) I remember changing a system file entry from quot;eth1quot; to quot;wlan0,quot; in hopes to fix the problem. I don't think this is the issue because it stopped working before I changed that.

Regardless, these are the four entries I got.Originally Posted by Ultra Magnusidentify your wifi card - if there are a few entries give them all ago
they will be called something like eth1

code: sudo ifconfig eth1 up
code: sudo eth1 scanning

If it says it can't scan or something try another entryCode:
mason@mason-laptop:~$ sudo ifconfig wlan0 up
Password:
mason@mason-laptop:~$ sudo wlan0 scanning
sudo: wlan0: command not found
mason@mason-laptop:~$ sudo ifconfig eth0 up
mason@mason-laptop:~$ sudo eth0 scanning
sudo: eth0: command not found
mason@mason-laptop:~$ sodu ifconfig eth0:avah up
bash: sodu: command not found
mason@mason-laptop:~$ sudo ifconfig eth0:avah up
SIOCSIFFLAGS: Cannot assign requested address
mason@mason-laptop:~$ sudo ifconfig lo up
mason@mason-laptop:~$ sudo lo scanning
sudo: lo: command not found
I tried the wireless card first, obviously a no-go. I went down the list, and none of them worked. Did I just do something wrong?

Also 'eth1,' what the card used to be, didn't work either.Originally Posted by Ultra Magnuscode: iwlist

Find the wireless network and note its quot;essidquot;
in my case belkin54gCode:
mason@mason-laptop:~$ iwlist
Usage: iwlist [interface] scanning  [interface] frequency  [interface] channel  [interface] bitrate  [interface] rate  [interface] encryption  [interface] key  [interface] power  [interface] txpower  [interface] retry  [interface] ap  [interface] accesspoints  [interface] peers  [interface] event
mason@mason-laptop:~$
I tried to press on, but this doesn't look like a list of available networks. Is this what the iwlist is supposed to look like?Originally Posted by Ultra Magnuscode : sudo iwconfig eth1 essid belkin54g
code : sudo dhclient

Lots of stuff will scroll down but it should only take a few seconds if it works then hopefully you have wireless!

try
code: ping
or something to see if it worked

Thanks for the help so far. I didn't try the rest because it seemed that something was amiss.

Ultra Magnus meant to say was to use:
iwlist scan

This will run through and list all the wireless sites that it sees.

By the way, the last steps of using eth1--use wlan0 instead.  The last two steps work if the network you are connecting is not secured.

Originally Posted by AyuthiaUltra Magnus meant to say was to use:
iwlist scan

This will run through and list all the wireless sites that it sees.

By the way, the last steps of using eth1--use wlan0 instead.  The last two steps work if the network you are connecting is not secured.

Ah, well that gave me what I expected to be the output from that command. Still not working though:Code:
mason@mason-laptop:~$ ifconfig
eth0    Link encap:Ethernet  HWaddr 00:0D:56:39:8A

F inet addr:169.254.7.232 Bcast:169.254.255.255 Mask:255.255.0.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 Interrupt:11

lo Link encap

ink       UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1       RX packets:15357 errors:0 dropped:0 overruns:0 frame:0       TX packets:24 errors:0 dropped:0 overruns:0 carrier:0       collisions:0 txqueuelen:1000       RX bytes:810826 (791.8 KiB)  TX bytes:1872 (1.8 KiB)       Interrupt:5 Memory:faff6000-faff8000

mason@mason-laptop:~$ sudo ifconfig wlan0 up
Password:
mason@mason-laptop:~$ sudo wlan0 scanning
sudo: wlan0: command not found
mason@mason-laptop:~$ wlan0 scanning
bash: wlan0: command not found
mason@mason-laptop:~$ iwlist scan
lo       Interface doesn't support scanning.

eth0    Interface doesn't support scanning.

wlan0    Scan completed :       Cell 01 - Address: 00:12:17:38:C6:26       ESSID:quot;linksysquot;       Protocol:IEEE 802.11b       Mode:Managed       Frequency:2.462 GHz (Channel 11)       Quality:81/100  Signal level:-44 dBm  Noise level:-96 dBm       Encryption key

ff       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

mason@mason-laptop:~$ sudo iwconfig wlan0 essid linksys
mason@mason-laptop:~$ sudo dhclient
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit  from : localhost/on LPF/wlan0/00:90:4b:16:51:06
Sending on LPF/wlan0/00:90:4b:16:51:06
Listening on LPF/eth0/00:0d:56:39:8a:df
Sending on LPF/eth0/00:0d:56:39:8a:df
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPOFFER from 192.168.1.1
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
DHCPACK from 192.168.1.1
bound to 192.168.1.106 -- renewal in 35517 seconds.
mason@mason-laptop:~$ ping unknown host that have anything to do with sudo wlan0 scanning code bringing up an error? It still wouldn't connect to the network or show the network in manual configuration.

The 'sudo wlan0 scanning' does not hurt anything because you are telling it to execute wlan0 and it does not exist as a file.

As for where you are at right now, it is beyond my knowledge.  Sorry about that.  I am sure that someone here would know the answer though.  It does seem that you are getting closer though.

From what I recall, the wlan0 comes from /etc/modprobe.d/ndiswrapper.  You could go and update that file (gksudo gedit /etc/modprobe.d/ndiswrapper) and change wlan0 to eth1.  You would have to restart and you should be back to eth1.  wlan0 should work for you though.  Why the name change occurred is something I am still trying to understand.  I had this happen to and I just updated my /etc/modprobe.d/ndiswrapper on my 32-bit side and it seems to be working fine under eth1 again.  I left my 64-bit side alone and it just had it's file check and it still kept it at eth1.

Sorry I can't help you further.