WiFi woes

All Gurus once were Newbies
Forum rules
There are no such things as "stupid" questions. However if you think your question is a bit stupid, then this is the right place for you to post it. Please stick to easy to-the-point questions that you feel people can answer fast. For long and complicated questions prefer the other forums within the support section.
Before you post please read this

WiFi woes

Postby farrisbaharom on Thu Aug 07, 2008 11:33 am

I love the forum rules for this one - the only stupid question is the one you don't ask!

Hi, I migrated to Linux/ Ubuntu Hardy awhile back, after finding out that Vista Ultimate was anything but.
Tried a LOT of other distros in my search for a better option and until awhile back, Ubuntu Hardy was it. Recently, I was looking for a change of flavour and my earlier tryouts with Mint made it my first choice.

Also, my WiFi stopped working all of a sudden in Ubuntu/ Hardy and nothing I could do could get it back up. Mint's meant to be better at WiFi so I wiped and intalled Elyssa from scratch.

Unfortunately, my WiFi woes seem to have followed me here. It didn't work out of the box. I tried the Wiki, tried using ndiswrapper for my Intel Pro Wireless 3495ABG but none of the drivers I installed seemed to work.

I'm running a hp 520 laptop.

Wireless connections do not appear at all on Network Manager. HELP! :o
I trawled a bit bit couldn't find a solution - Network Interfaces are fine, with only the auto lo/ iface lo inet loopback lines.
farrisbaharom
Level 1
Level 1
 
Posts: 12
Joined: Thu Aug 07, 2008 11:11 am

Linux Mint is funded by ads and donations.
 

Re: WiFi woes

Postby farrisbaharom on Thu Aug 07, 2008 11:40 am

tried something from the MintWifi Wiki. Heres the output:

farris@farris-hp-520 ~ $ sudo /usr/lib/linuxmint/mintWifi/mintWifi.py
-------------------------
* I. scanning WIFI PCI devices...
-- Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)
==> PCI ID = 8086:4222 (rev 02)
-------------------------
* II. querying ndiswrapper...
-------------------------
* III. querying iwconfig...
lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:"" Nickname:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

-------------------------
* IV. querying ifconfig...
eth0 Link encap:Ethernet HWaddr 00:1b:38:31:9a:1c
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1394281 errors:0 dropped:0 overruns:0 frame:0
TX packets:1204890 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1423156156 (1.3 GB) TX bytes:101533923 (96.8 MB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:226 errors:0 dropped:0 overruns:0 frame:0
TX packets:226 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:11300 (11.0 KB) TX bytes:11300 (11.0 KB)

-------------------------
* V. querying DHCP...
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
SIOCSIFFLAGS: Input/output error
SIOCSIFFLAGS: Input/output error
wmaster0: unknown hardware address type 801
Listening on LPF/wlan0/00:1b:77:7c:2a:7d
Sending on LPF/wlan0/00:1b:77:7c:2a:7d
Listening on LPF/wmaster0/
Sending on LPF/wmaster0/
Listening on LPF/eth0/00:1b:38:31:9a:1c
Sending on LPF/eth0/00:1b:38:31:9a:1c
Sending on Socket/fallback
receive_packet failed on wlan0: Network is down
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
send_packet: Network is down
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
DHCPOFFER of 192.168.1.2 from 192.168.1.1
DHCPREQUEST of 192.168.1.2 on eth0 to 255.255.255.255 port 67
DHCPACK of 192.168.1.2 from 192.168.1.1
bound to 192.168.1.2 -- renewal in 1644 seconds.
-------------------------
* VI. querying nslookup google.com...
Server: 192.168.1.1
Address: 192.168.1.1#53

Non-authoritative answer:
Name: google.com
Address: 64.233.167.99
Name: google.com
Address: 64.233.187.99
Name: google.com
Address: 72.14.207.99

Hope this helps. Being cable bound in this day and age is too cruel to bear! :P
farrisbaharom
Level 1
Level 1
 
Posts: 12
Joined: Thu Aug 07, 2008 11:11 am

Re: WiFi woes

Postby AK Dave on Thu Aug 07, 2008 12:12 pm

I see that iwconfig says you have a wireless adapter, so I don't think this is a driver issue.

Looks like you're having a DHCP problem. Is your router correctly configured?

I'm confused at ifconfig. It looks like you have a wired connection active. I find that neither Mint nor Ubuntu can support having both wired and wireless active at once. This may be no more difficult than unplugging a network cable and L-clicking the network icon on your toolbar.

I do recommend, if you have a home router that allows this, disabling DHCP on your laptop and using a static IP.
User avatar
AK Dave
Level 6
Level 6
 
Posts: 1042
Joined: Wed May 14, 2008 3:39 pm
Location: Anchorage, AK USA

Re: WiFi woes

Postby farrisbaharom on Thu Aug 07, 2008 1:04 pm

thanks dave.

I'll try and dig up what I can on your comments - you don't think it's a driver issue?
so far I've tried everything here http://www.linuxmint.com/wiki/index.php/MintWifi but still no joy on iwconfig
farrisbaharom
Level 1
Level 1
 
Posts: 12
Joined: Thu Aug 07, 2008 11:11 am

Re: WiFi woes

Postby farrisbaharom on Thu Aug 07, 2008 1:17 pm

Hey! you were right! I unwired and the Wireless Connection was right where it was meant to be.

Although the network connection is visible in Network Manager, but I can't seem to type in the bssid. I think I'm close! Will try a restart and a looksie at the MintWifi wiki again to make sure I'm doing it right.

Will post on if it works. Cheers again for pointing that out. I've now sunk to new levels of noob-ness :lol:
farrisbaharom
Level 1
Level 1
 
Posts: 12
Joined: Thu Aug 07, 2008 11:11 am

Re: WiFi woes

Postby farrisbaharom on Thu Aug 07, 2008 1:41 pm

Okay, tried the restart/ unplugged - but my Wireless Connection in Net. Manager have disappeared again.
Also, when I checked the Network Interface
Code: Select all
 $ sudo gedit /etc/network/interfaces
I get this output:

auto lo
iface lo inet loopback


iface wlan0 inet dhcp
address 192.168.1.1
netmask 255.255.255.0
wireless-key aabbccddee
wireless-essid aztech

auto wlan0


which should indicate that things are working, but still no joy. Tried to restart NM
Code: Select all
$ sudo /etc/init.d/networking restart
and got this:

* Reconfiguring network interfaces... wlan0: ERROR while getting interface flags: No such device
Error for wireless request "Set Encode" (8B2A) :
SET failed on device wlan0 ; No such device.
Error for wireless request "Set ESSID" (8B1A) :
SET failed on device wlan0 ; No such device.
There is already a pid file /var/run/dhclient.wlan0.pid with pid 134519072
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

SIOCSIFADDR: No such device
wlan0: ERROR while getting interface flags: No such device
wlan0: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up wlan0.


What's up with this?! :evil:
farrisbaharom
Level 1
Level 1
 
Posts: 12
Joined: Thu Aug 07, 2008 11:11 am

Re: WiFi woes

Postby farrisbaharom on Thu Aug 07, 2008 1:55 pm

One more thing to add. Output of
Code: Select all
$ sudo /usr/lib/linuxmint/mintWifi/mintWifi.py
is now (unwired):

* I. scanning WIFI PCI devices...
-- Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)
==> PCI ID = 8086:4222 (rev 02)
-------------------------
* II. querying ndiswrapper...
netw5v32 : driver installed
device (8086:4222) present (alternate driver: iwl3945)
netw5x32 : driver installed
device (8086:4222) present (alternate driver: iwl3945)
w29n51 : driver installed
-------------------------
* III. querying iwconfig...
lo no wireless extensions.

eth0 no wireless extensions.

-------------------------
* IV. querying ifconfig...
eth0 Link encap:Ethernet HWaddr 00:1b:38:31:9a:1c
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:1060 errors:0 dropped:0 overruns:0 frame:0
TX packets:1017 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1345337 (1.2 MB) TX bytes:121028 (118.1 KB)

eth0:avahi Link encap:Ethernet HWaddr 00:1b:38:31:9a:1c
inet addr:169.254.4.19 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:193 errors:0 dropped:0 overruns:0 frame:0
TX packets:193 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:9860 (9.6 KB) TX bytes:9860 (9.6 KB)

-------------------------
* V. querying DHCP...
There is already a pid file /var/run/dhclient.pid with pid 7539
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:1b:38:31:9a:1c
Sending on LPF/eth0/00:1b:38:31:9a:1c
Sending on Socket/fallback
DHCPREQUEST of 192.168.1.2 on eth0 to 255.255.255.255 port 67
DHCPREQUEST of 192.168.1.2 on eth0 to 255.255.255.255 port 67
DHCPREQUEST of 192.168.1.2 on eth0 to 255.255.255.255 port 67
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
No DHCPOFFERS received.
Trying recorded lease 192.168.1.2
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.

--- 192.168.1.1 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms

No working leases in persistent database - sleeping.
-------------------------
* VI. querying nslookup google.com...
;; connection timed out; no servers could be reached

I'm stumped :?: it's late here in Malaysia so I'm gonna give it another go trow.
Should I edit Network Interfaces again, and revert to the 1st 2 lines:

auto lo
iface lo inet loopback

and delete the rest? Am lost.
farrisbaharom
Level 1
Level 1
 
Posts: 12
Joined: Thu Aug 07, 2008 11:11 am

Re: WiFi woes

Postby AK Dave on Thu Aug 07, 2008 2:03 pm

damnedest thing. Now iwconfig isn't seeing your wlan0.

It detects your 3945, ndiswrapper loads drivers, but iwconfig doesn't see a wlan0.

If you go to Control Panel -> Network you should get the interface to manually configure your networking specs. Usually "roaming" works great. Sometimes you have to hand-code and coddle it. But that shouldn't be your problem, because right now it all hinges on iwconfig not seeing a wlan0.
User avatar
AK Dave
Level 6
Level 6
 
Posts: 1042
Joined: Wed May 14, 2008 3:39 pm
Location: Anchorage, AK USA

Re: WiFi woes

Postby farrisbaharom on Thu Aug 07, 2008 11:24 pm

Hmm, perhaps me having 2 drivers for the same card is causing a problem?
farrisbaharom
Level 1
Level 1
 
Posts: 12
Joined: Thu Aug 07, 2008 11:11 am

Re: WiFi woes

Postby farrisbaharom on Fri Aug 08, 2008 2:04 pm

FYI

I tried installing the driver through other means - uninstalling the Windows drivers in ndiswrapper, then tried to reinstall using both the mac80211 and ieee80211 patches to the kernel (2.6.24-16-386).

Had to uninstall some older modules (?) which I did, but when I tried to make the file in both cases I got Error 2 - Shell not bash.
I'm sure I messed up the command when I tried to do this so I'm stuck.

I'm guessing that I have messed up my kernel now, so am going to try a fresh install once my current downloads are done and starting again with a fresh install.

Before I do so, does anyone have any advice about any updates I should avoid after a fresh install? I receive a few notifications about newer packages already shipped in the installation. I've always kept the originals/ newer files but now I'm paranoid.

Why would MintUpdate ask me to install older packages? Could this be the cause of my grief? Will post updates - this time I'm accepting all the updates/ not keeping the newer exisiting packages shipped in the latest Elyssa.

Fingers crossed...
farrisbaharom
Level 1
Level 1
 
Posts: 12
Joined: Thu Aug 07, 2008 11:11 am

Re: WiFi woes

Postby AK Dave on Fri Aug 08, 2008 7:59 pm

I would have just had you manually blacklist the drivers one at a time.

Set your MintUpdate to only update level 1&2 updates.
User avatar
AK Dave
Level 6
Level 6
 
Posts: 1042
Joined: Wed May 14, 2008 3:39 pm
Location: Anchorage, AK USA

Re: WiFi woes

Postby farrisbaharom on Sat Aug 09, 2008 4:02 am

Okay, my problem is solved.

Here's what I did:

1. Fresh install of Mint Elyssa
2. MintUpdate - opted for the older packages i.e. did not 'keep' the newer packages shipped in the LiveCD
3.
Code: Select all
iwconfig
to check that wmaster0 was up and that the card was detected
4. Installed the Intel driver for the Intel Pro Wireless 3945 chip (for vista) driver: NETw5v32.inf
5.
Code: Select all
sudo /usr/lib/linuxmint/mintWifi/mintWifi.py
to check that everything is in order, hardware detected, driver installed

..and voila! everything worked! Didn't even have to unplug/ unwired to switch/ configure my Wireless Connection.

God help me i was THIS CLOSE to installing Mandriva!

Problem Solved. Cause inconclusive.
farrisbaharom
Level 1
Level 1
 
Posts: 12
Joined: Thu Aug 07, 2008 11:11 am

Re: WiFi woes

Postby farrisbaharom on Sat Aug 09, 2008 4:15 am

Okay now THIS is frustrating.
I restarted my system and now my Wireless Connection has disappeared.

Output of
Code: Select all
sudo /usr/lib/linuxmint/mintWifi/mintWifi.py
:
* I. scanning WIFI PCI devices...
-- Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)
==> PCI ID = 8086:4222 (rev 02)
-------------------------
* II. querying ndiswrapper...
netw5v32 : driver installed
device (8086:4222) present (alternate driver: iwl3945)
-------------------------
* III. querying iwconfig...
lo no wireless extensions.

eth0 no wireless extensions.

-------------------------
* IV. querying ifconfig...
eth0 Link encap:Ethernet HWaddr 00:1b:38:31:9a:1c
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1249 errors:0 dropped:0 overruns:0 frame:0
TX packets:1110 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1652164 (1.5 MB) TX bytes:119409 (116.6 KB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:134 errors:0 dropped:0 overruns:0 frame:0
TX packets:134 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6700 (6.5 KB) TX bytes:6700 (6.5 KB)

-------------------------
* V. querying DHCP...
There is already a pid file /var/run/dhclient.pid with pid 6565
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:1b:38:31:9a:1c
Sending on LPF/eth0/00:1b:38:31:9a:1c
Sending on Socket/fallback
DHCPREQUEST of 192.168.1.2 on eth0 to 255.255.255.255 port 67
DHCPACK of 192.168.1.2 from 192.168.1.1
bound to 192.168.1.2 -- renewal in 1534 seconds.
-------------------------
* VI. querying nslookup google.com...
Server: 192.168.1.1
Address: 192.168.1.1#53

Non-authoritative answer:
Name: google.com
Address: 64.233.187.99

Ouput of
Code: Select all
iwconfig
:

lo no wireless extensions.

eth0 no wireless extensions.

So I'm guessing that yes, I do need to blacklist some default drivers - any help? Pleeeeaaasssee... :D
farrisbaharom
Level 1
Level 1
 
Posts: 12
Joined: Thu Aug 07, 2008 11:11 am

Re: WiFi woes

Postby farrisbaharom on Sat Aug 09, 2008 7:37 am

Okay, I seem to have gotten everything up and working:

1. Fresh install of Elyssa
2. Level 2 MintUpdates only

Seems to have sorted out my problem. Holding out for a week to make sure it's stable.
farrisbaharom
Level 1
Level 1
 
Posts: 12
Joined: Thu Aug 07, 2008 11:11 am

Re: WiFi woes

Postby farrisbaharom on Mon Aug 25, 2008 4:41 pm

Okay, it's stable so I guess everything worked out fine.
farrisbaharom
Level 1
Level 1
 
Posts: 12
Joined: Thu Aug 07, 2008 11:11 am

Re: WiFi woes

Postby MagnusB on Tue Aug 26, 2008 5:22 am

That card is supported with open source drivers from Intel, and is reported to be a bit buggy with ndiswrapper. I think the first issues was that you have to many drivers installed in ndiswrapper, which caused a conflict, and it still can be a conflict if you have iwl, mac80211 and one more module loaded.

Did you first try to install drivers through ndiswrapper, or did you check if you had a working wireless before starting with windows drivers? Also, take a look at http://intellinuxwireless.org to see the official (Intel) instructions for that chipset.
Image
You're not drunk if you can lie on the floor without holding on.
--Dean Martin
MagnusB
Level 6
Level 6
 
Posts: 1255
Joined: Sun Nov 18, 2007 12:39 pm
Location: Norway

Linux Mint is funded by ads and donations.
 

Return to Newbie Questions

Who is online

Users browsing this forum: Google Adsense [Bot], tbrownarcher2, wyrdoak, Yahoo [Bot] and 34 guests