LinuxQuestions.org
Visit Jeremy's Blog.
Home Forums Tutorials Articles Register
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


Reply
  Search this Thread
Old 10-14-2012, 08:48 AM   #1
Ace Blackwell
Member
 
Registered: Mar 2004
Location: Kentucky, USA
Distribution: SlamD 12.1 / Slack 12.0 ~ 14.2_64
Posts: 345

Rep: Reputation: 54
Wireless Networks seen but won't connect


I'm running the new Slackware 14.0 64 on an HPdv2945. I have installed the SlackBuild fwcutter and B43. I now can pull up WICD and see my network along with others in the neighborhood. I just can't connect to them.

I run iwlist scan and it shows wlan0 having a lot of network choices but won't connect. My network is WPA secured so I thought I might be typing the password incorrectly but there is also a neighbor network unsecured and it won't connect either. My network does the authorization thing but fails to get an IP.

Any ideas on what I missed during set up?

Thanks
Ace
 
Old 10-14-2012, 09:12 AM   #2
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware, Slarm64 & Android
Posts: 16,260

Rep: Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321
The best kept secret there is wpa_passphrase. You need a chunk of the output from that in /etc/wpa_supplicant.conf. Then run 'iwlist wlan0 scan |less' and copy your wireless point's ap.
Finally this command

Quote:
wpa_supplicant -c/etc/wpa_supplicant.conf -Dwext -iwlan0 && iwconfig wlan0 essid Your_essid ap your_ap (paste it)
Should do it. Then run 'dhcpcd wlan0'
 
Old 10-14-2012, 09:28 PM   #3
Ace Blackwell
Member
 
Registered: Mar 2004
Location: Kentucky, USA
Distribution: SlamD 12.1 / Slack 12.0 ~ 14.2_64
Posts: 345

Original Poster
Rep: Reputation: 54
Thanks, I had a little problem. I wasn't really sure what Your_essid ap meant. Assuming Your_essid ap meant my network name but was still unclear about where to put it in the command above. Is it...
1) wpa_supplicant -c/etc/wpa_supplicant.conf -Dwext -iwlan0 && iwconfig wlan0 essid "Ace"
or
2) wpa_supplicant -c/etc/wpa_supplicant.conf -Dwext -iwlan0 && iwconfig wlan0 essid Your_essid ap "Ace"
or
3) wpa_supplicant -c/etc/wpa_supplicant.conf -Dwext -iwlan0 && iwconfig wlan0 essid Your_essid ap your_ap "Ace"

I typed in the wpa_supplicant -c/etc/wpa_supplicant.conf -Dwext -iwlan0 && iwconfig wlan0 essid "Ace" and the command started and never finished. I had to Ctrl-C to close. Then it held the file open.

Thanks
Ace
 
Old 10-15-2012, 03:06 AM   #4
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware, Slarm64 & Android
Posts: 16,260

Rep: Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321
Here's some typical information from my neighbours returned by 'iwlist wlan0 scan |less
Quote:
Cell 01 - Address: 00:24:92:A4:EF:E4
Channel:5
Frequency:2.432 GHz (Channel 5)
Quality=56/70 Signal level=-54 dBm
Encryption keyn
ESSID:"myeircom5986"
[SNIP]
I've actually mangled a few of my neighbour's details. To get on to that fictional ap, the command would be

Code:
wpa_supplicant -c/etc/wpa_supplicant.conf -Dwext -iwlan0 && iwconfig wlan0 essid "myeircom5986" ap  00:24:92:A4:EF:E4
Got the idea? The essid argument is the network name, the ap argument is the mac address of the ap as shown in iwlist wlan0 scan |less
 
Old 10-19-2012, 07:22 PM   #5
Ace Blackwell
Member
 
Registered: Mar 2004
Location: Kentucky, USA
Distribution: SlamD 12.1 / Slack 12.0 ~ 14.2_64
Posts: 345

Original Poster
Rep: Reputation: 54
Thanks Business Kid. I didn't have any luck but I appreciate the attempt.

Ok here is all I've done.
1) Installed fwcutter and B43 firmware that I used on Slackware 13.37 64. Didn't work. I could see various networks but couldn't get connected.
2) ran the command above as business kid recommended. I got a lot of "Use and Option" type replies. Like you get with you type a command without a parameter. Still no luck
3) Downloaded Broadcom_sta for Slack 14. Didn't have any luck. Couldn't even see the networks any more. (I did clean out the B43)
4) Cleaned B_sta and installed a newer Slack Build of Fwcutter and B43 firmware from a Slack 14 library site. I could see networks in wicd again but couldn't connect. I even made it past the authorization stage just wouldn't try to get an IP.
5) I ran iwconfig wlan0 essid "Ace" and then dhcpcd wlan0. no errors, it just didn't change anything.
6) Oddly enough, I also clicked around on wpa_supplicant gui. It seen my network and said it got a good IP. I was able to bring up the Google page in sea monkey and then I was dropped. The whole time wicd still didn't see me being connected nor would let me connect. After that the wpa gui wouldn't see my network.

So I've been looking around and while I'm FAR from a kernel expert it appears that B43 802.11 b/g WLAN just isn't really supported with the new Slackware 14. Is this true? If so I can quit trying to fit a square peg in a round hole and go back to 13.37 64

Meanwhile until I hear back from someone that knows more than me, I'm going to run through the process again, just to see if I've over looked something.

Thanks
Ace
 
Old 10-20-2012, 08:28 AM   #6
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware, Slarm64 & Android
Posts: 16,260

Rep: Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321
B43 is supported, or I wouldn't be getting through.

With b43-fwcutter, you need an exact varsion for your hardware and an command which should show piles of firmware being spat through to /lib/firmware. You should have stuff like this in /var/log/messages

Code:
  bash-4.2$ grep -i b43 /var/log/messages
Oct 20 13:07:00 harriet kernel: b43-pci-bridge 0000:30:00.0: PCI INT A disabled
Oct 20 13:07:00 harriet kernel: b43-pci-bridge 0000:30:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
Oct 20 13:07:00 harriet kernel: b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
Oct 20 13:59:23 harriet kernel: b43-pci-bridge 0000:30:00.0: PCI INT A disabled
Oct 20 13:59:23 harriet kernel: b43-pci-bridge 0000:30:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
Oct 20 13:59:23 harriet kernel: b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
There is actually a later version of the driver.


You find the exact version you need at
http://www.linuxwireless.org/en/users/Drivers/b43 and how to use it. This page is the gospel on b43. I think I compiled from source. Beware that the broadcom sta driver blacklists b43, so hack modprobe.d/blacklist and remove b43. If your b43 appears on usb, you also need b43-pci-bridge, a driver hidden ssb.ko (Sonics Silicon Backplane).
 
Old 10-21-2012, 07:47 AM   #7
Ace Blackwell
Member
 
Registered: Mar 2004
Location: Kentucky, USA
Distribution: SlamD 12.1 / Slack 12.0 ~ 14.2_64
Posts: 345

Original Poster
Rep: Reputation: 54
BK, Thanks,

Well I still not getting any network connections. With the latest configuration, I'm not even getting wicd to see the networks. Below is what I've done. May be you can see what I've missed.

1)grep -i b43 /var/log/messages gave me -- lsp/var/log/messages:Oct 20 11:05:28 darkstar kernel: [ 11.110808] b43-phy0: Broadcom 4312 WLAN found (core revision 15)
2) lspci -vnn -d 14e4: gave me -- Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g LP-PHY [14e4:4315] (rev 01)
3) The website you gave me shows 4315 was highly supported.
4) There wasn't a Slackware section, so I used "Other 3.2+" Fwcutter and firmware.
5) Installed fwcutter b43-fwcutter-015.tar.bz2
5) Installed b43-firmware/broadcom-wl-5.100.138.tar.bz2
6) Rebooted several times, no luck.
7) I ran iwconfig wlan0 essid "Ace" and dhcpcd wlan0. I got the light on the laptop to change to blue showing a connection of some sort but it didn't change my situation.
8) I ran iwlist scan and wlan0 sees all the local networks in the neighborhood but wpa_supplicant_gui and wicd does not.
9) Checked modprobe.d/blacklist and seen where bc43xx was blacklisted. I both left it and then commented it out. No luck. There wasn't anything for B43 or ssb etc. There actually wasn't a single blacklist file, the blacklist files seem to be for each item. IE not blacklist.conf but rather bc43xx_blacklist.conf (paraphrase name) and nivdia_XXXXXX.blacklist.conf

So thats where I'm at. All of this was done on top of a brand new installation of Slackware 14 64. You stated you were getting on with Slackware 14_64 did you use the same fwcutter / firmware file as I? Did you use the section under "Other" or did you go with a different distro? Lastly, instead of using 3.2+ kernal section or should i have went with 2.X+?

Thanks for all your patience.
Ace
 
Old 10-21-2012, 01:01 PM   #8
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware, Slarm64 & Android
Posts: 16,260

Rep: Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321
Up here,
https://skydrive.live.com/?cid=99361...4096FF2C07!208

I have put

1. The firmware, in a b43/ directory from /lib/firmware
2. rc.wireless.conf which is untouched. My much hacked one was swapped out during the install
3. rc.inet1.conf which has a few tweaks in the [4] section. You may want to comment out

DHCP_KEEPRESOLV=yes

Grab those in the next day or two, and try them. The rc. files go in /etc/rc.d. I have the 4312 and it works on those. You did doctor up wpa_supplicant.conf with the output of wpa_passphrase??
 
Old 10-22-2012, 08:47 AM   #9
Ace Blackwell
Member
 
Registered: Mar 2004
Location: Kentucky, USA
Distribution: SlamD 12.1 / Slack 12.0 ~ 14.2_64
Posts: 345

Original Poster
Rep: Reputation: 54
Hey Business Kid, I appreciate all the effort. I wasn't able to get a connection. The boot up hangs at a certain point and tries to get a carrier. It gets an 8 sec time out and continues with the boot up. Also Wicd doesn't see any networks once I'm in KDE.

I think this week I'll go back to 13.37 64. The setup was alot easier as I remember and I've been without my computer for over a week. Plus I'm worried that if 14.0 takes dating various files and running numerous commands from the prompt just to get on my network, then when I take the laptop anywhere away from the house, I'm going to have to go through updating various files for the new network. I didn't have that with the 13.37 64. Once I set up the card, I could log on to about any network by just clicking connect.

Again I do appreicate all the trouble you went through. I'll just wait until I have more time and knowledge to try 14.0 again. Right now I'm updating files because different web-sites are telling me exactly what to type and where. As a result, I don't fully understand what is going on so I don't know what is missing or correct order to do various commands.

Thanks
Ace
 
Old 10-22-2012, 11:23 AM   #10
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware, Slarm64 & Android
Posts: 16,260

Rep: Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321
I never used wicd. I set up the psk with wpa_passphrase, and then the rc scripts did it and wicd or nothing else is needed. The wifi for 13.37 is the same as the wifi for 14.0. The program versions may have been bumped up but the scripts are the same.

Get specific, Ace, or you'll never get connected. Do it by hand. Get stuck. Tell us exactly where you are stuck. No need to upgrade, downgrade, or change distros. Then when we ask you to try something, try it and be precise as to the error messages. All we can go on is your description of the problem and error behaviour.
You're not telling us error behaviour.

With that 8 sec delay, you're not associating. Post the last few lines of
grep b43-phy0 /var/log/messages
 
Old 10-22-2012, 01:19 PM   #11
Ace Blackwell
Member
 
Registered: Mar 2004
Location: Kentucky, USA
Distribution: SlamD 12.1 / Slack 12.0 ~ 14.2_64
Posts: 345

Original Poster
Rep: Reputation: 54
Ok. You convinced me. I'm going put in a fresh copy of 14.0. Then I will run lspci then lsmod and drop it in here so you can see what we get right out of the gate. Then I'll read up on wpa passphase and psk then go where it leads.. I'll keep you posted .

Thanks
Ace
 
Old 10-22-2012, 03:19 PM   #12
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware, Slarm64 & Android
Posts: 16,260

Rep: Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321
man wpa_passphrase
 
Old 10-23-2012, 09:43 AM   #13
Ace Blackwell
Member
 
Registered: Mar 2004
Location: Kentucky, USA
Distribution: SlamD 12.1 / Slack 12.0 ~ 14.2_64
Posts: 345

Original Poster
Rep: Reputation: 54
Ok, here is what I had last night. I started with a new installation of 14.0 the lsmod and lspci were as such
Quote:
bash-4.2# lspci
00:00.0 RAM memory: nVidia Corporation MCP67 Memory Controller (rev a2)
00:01.0 ISA bridge: nVidia Corporation MCP67 ISA Bridge (rev a2)
00:01.1 SMBus: nVidia Corporation MCP67 SMBus (rev a2)
00:01.2 RAM memory: nVidia Corporation MCP67 Memory Controller (rev a2)
00:01.3 Co-processor: nVidia Corporation MCP67 Co-processor (rev a2)
00:02.0 USB controller: nVidia Corporation MCP67 OHCI USB 1.1 Controller (rev a2)
00:02.1 USB controller: nVidia Corporation MCP67 EHCI USB 2.0 Controller (rev a2)
00:04.0 USB controller: nVidia Corporation MCP67 OHCI USB 1.1 Controller (rev a2)
00:04.1 USB controller: nVidia Corporation MCP67 EHCI USB 2.0 Controller (rev a2)
00:06.0 IDE interface: nVidia Corporation MCP67 IDE Controller (rev a1)
00:07.0 Audio device: nVidia Corporation MCP67 High Definition Audio (rev a1)
00:08.0 PCI bridge: nVidia Corporation MCP67 PCI Bridge (rev a2)
00:09.0 IDE interface: nVidia Corporation MCP67 AHCI Controller (rev a2)
00:0a.0 Ethernet controller: nVidia Corporation MCP67 Ethernet (rev a2)
00:0c.0 PCI bridge: nVidia Corporation MCP67 PCI Express Bridge (rev a2)
00:0d.0 PCI bridge: nVidia Corporation MCP67 PCI Express Bridge (rev a2)
00:12.0 VGA compatible controller: nVidia Corporation C67 [GeForce 7150M / nForce 630M] (rev a2)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:09.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 05)
01:09.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 22)
01:09.2 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 12)
01:09.3 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 12)
08:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01)

bash-4.2# lsmod
Module Size Used by
nvidia 12290147 42
snd_seq_dummy 1455 0
snd_seq_oss 29048 0
snd_seq_midi_event 5620 1 snd_seq_oss
snd_seq 51265 5 snd_seq_midi_event,snd_seq_oss,snd_seq_dummy
snd_seq_device 5228 3 snd_seq,snd_seq_oss,snd_seq_dummy
snd_pcm_oss 39183 0
snd_mixer_oss 15404 1 snd_pcm_oss
appletalk 26625 0
ipv6 279979 20
cpufreq_ondemand 6252 1
powernow_k8 12747 1
mperf 1171 1 powernow_k8
freq_table 2475 2 powernow_k8,cpufreq_ondemand
agpgart 27372 1 nvidia
lp 9787 0
ppdev 5958 0
parport_pc 19423 0
parport 31427 3 parport_pc,ppdev,lp
fuse 66626 7
r852 10660 0
sm_common 7474 1 r852
nand 45285 2 sm_common,r852
uvcvideo 62784 0
joydev 9972 0
nand_ecc 3532 1 nand
nand_bch 2450 1 nand
videodev 76679 1 uvcvideo
v4l2_compat_ioctl32 8660 1 videodev
b43 340351 0
mac80211 227731 1 b43
sdhci_pci 10812 0
sdhci 23109 1 sdhci_pci
processor 25592 1 powernow_k8
bch 9681 1 nand_bch
nand_ids 6505 1 nand
hp_wmi 7802 0
sparse_keymap 3016 1 hp_wmi
cfg80211 169025 2 mac80211,b43
snd_hda_codec_conexant 46868 1
rfkill 15428 3 cfg80211,hp_wmi
ssb 47856 1 b43
k8temp 3363 0
firewire_ohci 31953 0
mmc_core 77850 4 ssb,sdhci,sdhci_pci,b43
thermal 7983 0
psmouse 61704 0
video 11378 0
thermal_sys 14578 3 video,thermal,processor
forcedeth 52696 0
hwmon 1329 2 thermal_sys,k8temp
pcmcia 35720 2 ssb,b43
pcmcia_core 12061 1 pcmcia
serio_raw 4389 0
snd_hda_intel 23267 2
snd_hda_codec 81925 2 snd_hda_intel,snd_hda_codec_conexant
i2c_nforce2 5056 0
snd_hwdep 6324 1 snd_hda_codec
wmi 8403 1 hp_wmi
i2c_core 19978 3 i2c_nforce2,videodev,nvidia
snd_pcm 72864 3 snd_hda_codec,snd_hda_intel,snd_pcm_oss
snd_page_alloc 7081 2 snd_pcm,snd_hda_intel
battery 11171 0
ac 3331 0
button 4529 0
firewire_core 50552 1 firewire_ohci
r592 11907 0
mtd 26221 2 nand,sm_common
memstick 6856 1 r592
evdev 9574 11
snd_timer 18798 2 snd_pcm,snd_seq
snd 57796 15 snd_timer,snd_pcm,snd_hwdep,snd_hda_codec,snd_hda_intel,snd_hda_codec_conexant,snd_mixer_oss,snd_pcm _oss,snd_seq_device,snd_seq,snd_seq_oss
soundcore 5474 1 snd
loop 18192 0
Then I installed Fwcutter and rebooted. Then installed B43firmware and rebooted. Below is what I had afterwards
Quote:
AFTER FWCUTTER ADN B43 FIRMWARE
ash-4.2# lspci
00:00.0 RAM memory: nVidia Corporation MCP67 Memory Controller (rev a2)
00:01.0 ISA bridge: nVidia Corporation MCP67 ISA Bridge (rev a2)
00:01.1 SMBus: nVidia Corporation MCP67 SMBus (rev a2)
00:01.2 RAM memory: nVidia Corporation MCP67 Memory Controller (rev a2)
00:01.3 Co-processor: nVidia Corporation MCP67 Co-processor (rev a2)
00:02.0 USB controller: nVidia Corporation MCP67 OHCI USB 1.1 Controller (rev a2)
00:02.1 USB controller: nVidia Corporation MCP67 EHCI USB 2.0 Controller (rev a2)
00:04.0 USB controller: nVidia Corporation MCP67 OHCI USB 1.1 Controller (rev a2)
00:04.1 USB controller: nVidia Corporation MCP67 EHCI USB 2.0 Controller (rev a2)
00:06.0 IDE interface: nVidia Corporation MCP67 IDE Controller (rev a1)
00:07.0 Audio device: nVidia Corporation MCP67 High Definition Audio (rev a1)
00:08.0 PCI bridge: nVidia Corporation MCP67 PCI Bridge (rev a2)
00:09.0 IDE interface: nVidia Corporation MCP67 AHCI Controller (rev a2)
00:0a.0 Ethernet controller: nVidia Corporation MCP67 Ethernet (rev a2)
00:0c.0 PCI bridge: nVidia Corporation MCP67 PCI Express Bridge (rev a2)
00:0d.0 PCI bridge: nVidia Corporation MCP67 PCI Express Bridge (rev a2)
00:12.0 VGA compatible controller: nVidia Corporation C67 [GeForce 7150M / nForce 630M] (rev a2)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:09.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 05)
01:09.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 22)
01:09.2 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 12)
01:09.3 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 12)
08:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01)

bash-4.2# lsmod
Module Size Used by
snd_seq_dummy 1455 0
snd_seq_oss 29048 0
snd_seq_midi_event 5620 1 snd_seq_oss
snd_seq 51265 5 snd_seq_midi_event,snd_seq_oss,snd_seq_dummy
snd_seq_device 5228 3 snd_seq,snd_seq_oss,snd_seq_dummy
snd_pcm_oss 39183 0
snd_mixer_oss 15404 1 snd_pcm_oss
appletalk 26625 0
ipv6 279979 20
cpufreq_ondemand 6252 1
powernow_k8 12747 1
mperf 1171 1 powernow_k8
freq_table 2475 2 powernow_k8,cpufreq_ondemand
lp 9787 0
ppdev 5958 0
parport_pc 19423 0
parport 31427 3 parport_pc,ppdev,lp
fuse 66626 7
nvidia 12290147 42
snd_hda_codec_conexant 46868 1
snd_hda_intel 23267 2
snd_hda_codec 81925 2 snd_hda_intel,snd_hda_codec_conexant
snd_hwdep 6324 1 snd_hda_codec
snd_pcm 72864 3 snd_hda_codec,snd_hda_intel,snd_pcm_oss
sdhci_pci 10812 0
uvcvideo 62784 0
joydev 9972 0
b43 340351 0
videodev 76679 1 uvcvideo
v4l2_compat_ioctl32 8660 1 videodev
sdhci 23109 1 sdhci_pci
mac80211 227731 1 b43
cfg80211 169025 2 mac80211,b43
r852 10660 0
firewire_ohci 31953 0
r592 11907 0
video 11378 0
thermal 7983 0
ssb 47856 1 b43
processor 25592 1 powernow_k8
mmc_core 77850 4 ssb,sdhci,b43,sdhci_pci
forcedeth 52696 0
hp_wmi 7802 0
evdev 9574 11
psmouse 61704 0
serio_raw 4389 0
sparse_keymap 3016 1 hp_wmi
rfkill 15428 3 hp_wmi,cfg80211
memstick 6856 1 r592
thermal_sys 14578 3 processor,thermal,video
wmi 8403 1 hp_wmi
sm_common 7474 1 r852
nand 45285 2 sm_common,r852
nand_ecc 3532 1 nand
nand_bch 2450 1 nand
button 4529 0
bch 9681 1 nand_bch
nand_ids 6505 1 nand
mtd 26221 2 nand,sm_common
firewire_core 50552 1 firewire_ohci
k8temp 3363 0
hwmon 1329 2 k8temp,thermal_sys
ac 3331 0
battery 11171 0
pcmcia 35720 2 ssb,b43
snd_page_alloc 7081 2 snd_pcm,snd_hda_intel
pcmcia_core 12061 1 pcmcia
agpgart 27372 1 nvidia
i2c_nforce2 5056 0
i2c_core 19978 3 i2c_nforce2,videodev,nvidia
snd_timer 18798 2 snd_pcm,snd_seq
snd 57796 15 snd_timer,snd_pcm,snd_hwdep,snd_hda_codec,snd_hda_intel,snd_hda_codec_conexant,snd_mixer_oss,snd_pcm _oss,snd_seq_device,snd_seq,snd_seq_oss
soundcore 5474 1 snd
loop 18192 0
Next I ran iwlist scan and iwconfig
Quote:
bash-4.2# iwlist scan
lo Interface doesn't support scanning.

wlan0 Interface doesn't support scanning : Network is down

eth0 Interface doesn't support scanning.

bash-4.2# iwconfig
lo no wireless extensions.

wlan0 IEEE 802.11bg ESSIDff/any
Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm
Retry long limit:7 RTS thrff Fragment thrff
Encryption keyff
Power Managementn

eth0 no wireless extensions.
Then I read up on and ran wpa_passphase
Quote:
bash-4.2# wpa_passphrase "Ace" linux2012
network={
ssid="Ace"
#psk="linux2012"
psk=3cc7e7501db87035aee137abc4451ac377d7a05d82582543b98664a50c612f70
}
Lastly I ran iwconfig and dhcpcd.
Quote:
iwconfig wlan0 essid "Ace"
bash-4.2# dhcpcd wlan0
dhcpcd[2662]: version 5.5.6 starting
dhcpcd[2662]: wlan0: carrier acquired
dhcpcd[2662]: wlan0: carrier lost
dhcpcd[2662]: wlan0: waiting for carrier
dhcpcd[2662]: timed out
dhcpcd[2662]: allowing 8 seconds for IPv4LL timeout
dhcpcd[2662]: timed out
So here is where I'm at. The wifi light on the computer activates but none of the gui's see any networks.

Any suggestions or do you see where I've missed something.

Thanks Again
Ace

Last edited by Ace Blackwell; 10-23-2012 at 09:44 AM.
 
Old 10-24-2012, 04:52 AM   #14
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware, Slarm64 & Android
Posts: 16,260

Rep: Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321
Make sure you haven't got 'fast ethernet switching' or anything like it enabled in the kernel. What that does is switch off the wifi if you configure the lan, or vice-versa.

The connect sequence is
Code:
ifconfig wlan0 up
iwlist wlan0 scan |less #copy your AP mac address
iwconfig essid "Ace" ap <paste your AP mac address> #This associates you, and wpa_supplicant should be automatic
iwconfig wlan0  # Check you are associated
dhcpcd wlan0
Each stage has to succeed before the next will work

In the cloistered days of old, an English monarch and his virgin wife got married without sufficient knowledge of each other to do what comes naturally, and people only gathered that when there was no offspring for some years :-/. You're in a similar position - you have it perfect, you just need to set it up. Stop fixing it, and try the above sequence. Losing the carrier can be a signal strength problem. What's the quality for your ap in iwlist?

If you can't associate, try

Code:
wpa_supplicant -c/etc/wpa_supplicant.conf -Dwext -iwlan0 && iwconfig essid "Ace" ap <paste your AP mac address>
That may grab a terminal, and run 'dhcpcd wlan0' from another if it does.
 
Old 10-25-2012, 10:22 AM   #15
Ace Blackwell
Member
 
Registered: Mar 2004
Location: Kentucky, USA
Distribution: SlamD 12.1 / Slack 12.0 ~ 14.2_64
Posts: 345

Original Poster
Rep: Reputation: 54
B_K,

Well here are the results from last attempt.

ifconfig wlan0 up
Ran fine, no errors and back to the prompt.
iwlist wlan0 scan |less #copy your AP mac address
Ran fine, copied MAC address
iwconfig essid "Ace" ap <paste your AP mac address> #This associates you, and wpa_supplicant should be automatic
Gave me “Ace unknown command” error. I had to type iwconfig wlan0 essid "Ace" ap 00:00:00:00:00 then it ran fine and dropped to prompt again.
iwconfig wlan0 # Check you are associated
Ran Fine No errors, though it just dropped to the prompt. It didn't say anything about being associated or not
dhcpcd wlan0
Ran Fine no errors
Over all went well but no connection. I did get the blue activation light on the computer however.


wpa_supplicant -c/etc/wpa_supplicant.conf -Dwext -iwlan0 && iwconfig essid "Ace" ap 00:00:00:00:00
This didn’t give an error but it doesn’t go back to the prompt. It drops to a blank line and sits. I left it for 15 mins. Finally I had to Ctrl-Z to stop the process. I reran but I get and open file error. Went to var/wpa_supplicant (I believe) and had to delete wlan0 file . I reran again, and got the same result as the first attempt. A hang up.

I don’t have wicd installed so I don’t not if the networks are seen or not. I do know that iwlist sees all the networks close to my house including mine.

Any suggestions? I’m not trying to throw in your lap. I just don’t know where to go from here. You’ve covered what I knew to do a long while back.

Also, I’ve never worked with the kernel. I can’t say if I have fast switching activated or not. I’ll research it when I get home.

Thanks
Ace

Last edited by Ace Blackwell; 10-25-2012 at 10:23 AM.
 
  


Reply



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
wireless won't connect to password-protected networks qianian Linux - Wireless Networking 6 09-23-2009 06:26 PM
Slackware 12.2 will not connect to Wireless Networks picketfence Linux - Laptop and Netbook 9 03-28-2009 10:00 AM
how i connect in wireless networks ? hatebreeder666 Linux - Newbie 2 01-03-2009 03:11 PM
Can't Connect to any Encrypted Wireless Networks markackerman8@gmail. Linux - Newbie 3 07-13-2008 12:52 PM
NetworkManager can't connect to wireless networks debeus Linux - Laptop and Netbook 3 12-26-2007 07:39 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking > Linux - Wireless Networking

All times are GMT -5. The time now is 05:51 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
Open Source Consulting | Domain Registration