WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: WiFi - Not connecting to access point  (Read 23433 times)

Offline lmart

  • Jr. Member
  • **
  • Posts: 65
Re: WiFi - Not connecting to access point
« Reply #15 on: July 18, 2012, 07:17:14 AM »
Juanito

thanks for your reply
at a loss as what to do
does TC_Install load the drivers as "onboot"?
know nothing about wifi.sh, will try to find it

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 14801
Re: WiFi - Not connecting to access point
« Reply #16 on: July 18, 2012, 07:22:33 AM »
Eh?

From this:
Quote
WiFi does not connect to my router. Here's what happened after clicking the WiFi icon.
  scan networks
  send credential to access point
  udhcpc
  failed to connect
..it looks like you were doing the right thing, you just need to run "dmesg" after "failed to connect"

Offline lmart

  • Jr. Member
  • **
  • Posts: 65
Re: WiFi - Not connecting to access point
« Reply #17 on: July 18, 2012, 07:31:00 AM »
Juanito
I did run dmesg | tail -20, as requested, and provided the output

tried wifi again, attached is the full output from dmesg


Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 14801
Re: WiFi - Not connecting to access point
« Reply #18 on: July 18, 2012, 07:47:38 AM »
Ah - OK
Code: [Select]
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'
cfg80211: Calling CRDA to update world regulatory domain
libipw: 802.11 data/management/control stack, git-1.1.13
libipw: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq
ipw2200: Copyright(c) 2003-2006 Intel Corporation
ipw2200 0000:06:0b.0: power state changed by ACPI to D0
ipw2200 0000:06:0b.0: power state changed by ACPI to D0
ipw2200 0000:06:0b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
ipw2200: Detected geography ZZM (11 802.11bg channels, 0 802.11a channels)
lib80211_crypt: registered algorithm 'WEP'

There's no mention of the firmware being loaded - not that this means it wasn't - is the firmware-ipw2200 extension loaded (look for /tmp/tcloop/firmware-ipw2200)?

There's also no mention of a network connection - eth0, eth1, wlan0, wlan1 - being assigned, so for sure nothing will work until one is assigned, but that will depend on the firmware being loaded.

Offline lmart

  • Jr. Member
  • **
  • Posts: 65
Re: WiFi - Not connecting to access point
« Reply #19 on: July 18, 2012, 08:16:34 AM »
Juanito

contents of /mnt/tcloop attached

when I launch wifi by clicking the icon, the program finds eth1 and requests a password
I supply the password, credentials to access point, udhcpc, sends discovery 3 times, messages "no lease, failing", then failed to connect

with that said, how can I tell if the firmware is loaded?

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 14801
Re: WiFi - Not connecting to access point
« Reply #20 on: July 18, 2012, 08:40:49 AM »
OK, so the following extensions appear to be loaded:
Code: [Select]
firmware
firmware-ipw2100
firmware-ipw2200
firmware-iwlwifi
..which should cover things.

I'm surprised that eth1 does not show up in dmesg if wifi is using eth1 and I'd also expect to see various wifi connection attempt messages in dmesg that are not present, which is a bit of a puzzle.

What encryption is your wireless ap using - wep, wpa, wpa2? Is the ssid broadcast?

Maybe you could try this and see what /tmp/wifi.log says :
Code: [Select]
$ sudo /usr/local/bin/wifi.sh auto 2>&1 > /tmp/wifi.log

Offline lmart

  • Jr. Member
  • **
  • Posts: 65
Re: WiFi - Not connecting to access point
« Reply #21 on: July 18, 2012, 09:05:42 AM »
juanito

see attached

Offline lmart

  • Jr. Member
  • **
  • Posts: 65
Re: WiFi - Not connecting to access point
« Reply #22 on: July 18, 2012, 09:08:37 AM »
using WEP

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 14801
Re: WiFi - Not connecting to access point
« Reply #23 on: July 18, 2012, 10:37:30 AM »
Code: [Select]
Found wifi device eth1
Standby for scan of available networks...
Attempting auto connection with
udhcpc (v1.20.1) started
Sending discover...
Sending discover...
Sending discover...
No lease, failing

Is the ssid broadcast - I would expect it to say "Attempting auto connection with ssid"?

Offline roberts

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: WiFi - Not connecting to access point
« Reply #24 on: July 18, 2012, 10:46:39 AM »
What does the following command produce?

sudo iwlist eth1 scanning
10+ Years Contributing to Linux Open Source Projects.

Offline lmart

  • Jr. Member
  • **
  • Posts: 65
Re: WiFi - Not connecting to access point
« Reply #25 on: July 18, 2012, 10:55:39 AM »
Juanto
thanks for stick with it
"Is the ssid broadcast" - Yes, I can connect my wireless on my desktop using the LiveCD.

tried to connect from the command line; ref to http://wiki.tinycorelinux.net/wiki:setting_up_wifi
manually entered the following command, replacing values in {}

iwconfig ${wlan}
iwconfig ${wlan} essid ${essid}
iwconfig ${wlan} enc ${wepkey}
iwconfig ${wlan} key ${wepkey}
iwconfig ${wlan} commit
  error for wireless request "commit changes" (8B00): operation not supported  suggestions?
pkill udhcpc
udhcpc -H box -b -i ${wlan}
  option -h NAME is deprecated, use -x hostname:NAME  suggestions?

just received your last post, wait one and I will try

Offline roberts

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: WiFi - Not connecting to access point
« Reply #26 on: July 18, 2012, 10:58:34 AM »
Need to be root for those commands.
$ sudo -s
#
10+ Years Contributing to Linux Open Source Projects.

Offline lmart

  • Jr. Member
  • **
  • Posts: 65
Re: WiFi - Not connecting to access point
« Reply #27 on: July 18, 2012, 11:06:06 AM »
roberts

thanks for your help

yes, entered sudo before each command - ? how would I add 'script' to the bash commands so it can capture my terminal session?

here's the output from sudo iwlist eth1 scanning with other access points removed

eth1      Scan completed :
          Cell 02 - Address: E8:39:DF:AA:C3:E5
                    ESSID:"398VC"
                    Protocol:IEEE 802.11bg
                    Mode:Master
                    Frequency:2.412 GHz (Channel 1)
                    Encryption key:on
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
                              11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
                              48 Mb/s; 54 Mb/s
                    Quality=65/100  Signal level=-30 dBm 
                    Extra: Last beacon: 133ms ago



Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 14801
Re: WiFi - Not connecting to access point
« Reply #28 on: July 18, 2012, 11:42:09 AM »
how would I add 'script' to the bash commands so it can capture my terminal session?

Code: [Select]
$ script filename
...
<ctrl-d>

Offline tinypoodle

  • Hero Member
  • *****
  • Posts: 3857
Re: WiFi - Not connecting to access point
« Reply #29 on: July 18, 2012, 05:24:50 PM »

  error for wireless request "commit changes" (8B00): operation not supported  suggestions?

"commit" appears not to work with all drivers.

Quote
  option -h NAME is deprecated, use -x hostname:NAME  suggestions?

The "-i interface" option alone should be sufficient.
« Last Edit: July 18, 2012, 06:14:44 PM by tinypoodle »
"Software gets slower faster than hardware gets faster." Niklaus Wirth - A Plea for Lean Software (1995)