Tiny Core Linux
Tiny Core Base => TCB Talk => Topic started by: lmart on July 16, 2012, 07:06:31 PM
-
Downloaded CorePlus 4.5.6. Installed USB-HDD from LiveCD for use on my laptop.
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
What can I do to help you help me resolve this issue?
-
PS USB setup with (1) WiFi support, (2) ndiswrapper and, (3) Wireless Firmware.
-
If you are going to use the ndiswrapper, you'll also need the WinXP driver follow the instructions in the Wrapper info file. You'll not need the firmware extension either.
If the wifi app is scanning then you must already have the correct firmware and driver. Or Ndiswrapper + WinXP Driver, But in this case why the firmware.? It's either one or the other.
Also it's hard to help without a list of equipment, at least the wifi device in this case
-
thanks for your reply
just downloaded everything, have no idea what hdiswrapper is or how to use it
how do i know if i have the correct firmware and driver?
what command(s) would you like me to run to provide you with the list of equipment?
is there a tutorial on this stuff?
What can I do to help you help me resolve this issue?
-
have no idea what hdiswrapper is or how to use it
As said above, follow the instructions in the info file - you can also use google to navigate to the ndiswrapper wiki.
If you use lspci or lsusb to give details of your hardware and paste the output here, it would the forum to help you.
-
IMHO ndiswrapper is not ideal, and a last resort or temporay fix only when no linux driver would work at some given moment.
-
Juanito; thanks for your reply. Output of the 2 commands you requested follow. "As said above, follow the instructions in the info file" - I'm lost, what instructions?
tinypoodle; thanks for your reply.
output-lspci
00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller (rev 03)
00:01.0 PCI bridge: Intel Corporation Mobile 915GM/PM Express PCI Express Root Port (rev 03)
00:1b.0 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 03)
00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev d3)
00:1f.0 ISA bridge: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) IDE Controller (rev 03)
00:1f.2 IDE interface: Intel Corporation 82801FBM (ICH6M) SATA Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller (rev 03)
01:00.0 VGA compatible controller: nVidia Corporation NV44 [GeForce Go 6200] (rev a1)
06:05.0 CardBus bridge: Texas Instruments PCI7420 CardBus Controller
06:05.2 FireWire (IEEE 1394): Texas Instruments PCI7x20 1394a-2000 OHCI Two-Port PHY/Link-Layer Controller
06:05.3 Mass storage controller: Texas Instruments PCI7420/7620 Combo CardBus, 1394a-2000 OHCI and SD/MS-Pro Controller
06:08.0 Ethernet controller: Intel Corporation 82562ET/EZ/GT/GZ - PRO/100 VE (LOM) Ethernet Controller Mobile (rev 03)
06:0b.0 Network controller: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection (rev 05)
output-lsusb
not found
-
Output of the 2 commands you requested follow. "As said above, follow the instructions in the info file" - I'm lost, what instructions?
From the ndiswrapper info file (info tab in the apps gui):
example howto:
enter bootcodes blacklist=ssb blacklist=b43 blacklist=bcma
$ sudo ndiswrapper -i /mnt/sda1/drivers/ndiswrapper/bcmwl5.inf
$ sudo ndiswrapper -l
$ sudo ndiswrapper -m
$ sudo modprobe ndiswrapper
----------
Note: you can now make an extension out of everything in
.. /etc/ndiswrapper and use it with the ndiswrapper extension
..to avoid having to use the perl5 extension
----------
Of course you would need to substitute the windows driver for your hardware for bcmwl5.inf/bcmwl5.sys
06:0b.0 Network controller: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection (rev 05)
This is your wifi hardware - I seem to recall some posts in the forum about how to get this working with linux drivers rather than ndiswrapper.
Edit: It might even work right out of the box with the wifi extension
-
For an Intel Corporation PRO/Wireless 2200BG device, the Linux " ipw2200 " firmware and driver is recommended.
Honestly, I'd start over by removing any and all wifi associated extensions including the ndiswrapper which is not required.
Then using the APPS Utility download and install with "OnBoot" selected only the following, which will install the required applications and dependencies.
firmware-ipw2200.tcz
wireless-3.0.21-tinycore.tcz
wifi.tcz
Note that wireless-3.0.21-tinycore.tcz is a dependency of wifi.tcz so will be installed automatically when installing wifi.tcz, installing it separately is ok too.
-
coreplayer2
thanks, start over makes sense; want to make sure we're on the same page
#1 - will reinstall tc+ from LiveCD to usb
#2 - do not check any of the following boxes when installing; (1) WiFi support, (2) ndiswrapper and, (3) Wireless Firmware
#3 - then follow your instructions;
"Then using the APPS Utility download and install with "OnBoot" selected only the following, which will install the required applications and dependencies.
firmware-ipw2200.tcz
wireless-3.0.21-tinycore.tcz
wifi.tcz"
Are the 3 steps correct - Yes|No?
-
This is the classic chicken before the egg syndrome.
I see now your method. so in this case NO
select only Wifi support and firmware
No need to use Apps in this scenario as all the required extensions are included in the live cd
First, can you connect using the wifi icon whilst booted to the CorePlus live cd ?
-
coreplayer2
#1 - Bootled to LiveCD on desktop and launched TC_Install
#2 - Created tc+ usb-hdd accepting only defaults, no boot options
#3 - On Core+ extensions, selected (a) WiFi support and, (b) Wireless Firmware
#4 - Booted tc+ usb on laptop and launched WiFi
#5 - Same Results - No connection to access point
scan networks
send credential to access point
udhcpc
failed to connect
-
What do the last few lines of dmesg say after you fail to connect:
$ dmesg | tail -20
-
Juanito
dmesg | tail -20, as requested
intel_rng: FWH not detected
intel_rng: FWH not detected
intel_rng: FWH not detected
ipw2200: Detected geography ZZM (11 802.11bg channels, 0 802.11a channels)
lib80211_crypt: registered algorithm 'WEP'
usb 1-1: new high speed USB device number 3 using ehci_hcd
scsi7 : usb-storage 1-1:1.0
scsi 7:0:0:0: Direct-Access USB 2.0 Flash Disk 8.07 PQ: 0 ANSI: 2
sd 7:0:0:0: Attached scsi generic sg3 type 0
sd 7:0:0:0: [sdc] 511998 512-byte logical blocks: (262 MB/249 MiB)
sd 7:0:0:0: [sdc] Write Protect is off
sd 7:0:0:0: [sdc] Mode Sense: 03 00 00 00
sd 7:0:0:0: [sdc] No Caching mode page present
sd 7:0:0:0: [sdc] Assuming drive cache: write through
sd 7:0:0:0: [sdc] No Caching mode page present
sd 7:0:0:0: [sdc] Assuming drive cache: write through
sdc: sdc1
sd 7:0:0:0: [sdc] No Caching mode page present
sd 7:0:0:0: [sdc] Assuming drive cache: write through
sd 7:0:0:0: [sdc] Attached SCSI removable disk
-
That looks like what you'd see if the drivers were loaded "onboot" and you have not run the wifi extension script (double-click on wifi icon or "wifi.sh").
I'd expect you would see something like: $ dmesg
...
Broadcom 43xx driver loaded [ Features: PLR, Firmware-ID: FW13 ]
firmware: requesting b43/ucode5.fw
firmware: requesting b43/pcm5.fw
firmware: requesting b43/b0g0initvals5.fw
firmware: requesting b43/b0g0bsinitvals5.fw
b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)..with Intel in place of Broadcom
and: $ dmesg
...
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'
wl 0000:02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
wl 0000:02:00.0: setting latency timer to 64
lib80211_crypt: registered algorithm 'TKIP'
eth1: Broadcom BCM4359 802.11 Hybrid Wireless Controller 5.100.82.112
lib80211_crypt: registered algorithm 'WEP'
lib80211_crypt: registered algorithm 'CCMP'
..with possibly wlan0 or eth0 in place of eth1
-
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
-
Eh?
From this: 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"
-
Juanito
I did run dmesg | tail -20, as requested, and provided the output
tried wifi again, attached is the full output from dmesg
-
Ah - OK
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.
-
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?
-
OK, so the following extensions appear to be loaded:
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 : $ sudo /usr/local/bin/wifi.sh auto 2>&1 > /tmp/wifi.log
-
juanito
see attached
-
using WEP
-
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"?
-
What does the following command produce?
sudo iwlist eth1 scanning
-
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
-
Need to be root for those commands.
$ sudo -s
#
-
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
-
how would I add 'script' to the bash commands so it can capture my terminal session?
$ script filename
...
<ctrl-d>
-
error for wireless request "commit changes" (8B00): operation not supported suggestions?
"commit" appears not to work with all drivers.
option -h NAME is deprecated, use -x hostname:NAME suggestions?
The "-i interface" option alone should be sufficient.
-
tinypoodle
thanks, the commands used are from http://wiki.tinycorelinux.net/wiki:setting_up_wifi
will try your recommendations shortly, to confirm
iwconfig ${wlan} commit remove this line
pkill udhcpc
udhcpc -i ${wlan}
Yes | No?
another question, you seem to be in the know on thing 'core', I wanted to download leafpad, there are 2 files a .tcz and a locale file. what is the locale file and should I download it?
-
Looks ok, though there is no necessity to remove "commit", just that error output could be disregarded.
For a new unrelated question please open a new thread in adequate subforum ;)
-
roberts,Juanito and, tinypoodle
success, me thinks ... will download a browser and know for sure
thank you for your help!
here's the sequence of events
#1) wrote a small script an incorporated the changed tinypoodle suggested. Script follows.
#2) modified Juanito's code to capture the script output ($ sudo /usr/local/bin/wifi.sh auto 2>&1 > /tmp/wifi.log) The following message appeared on the screen but not in the log file: route: SIOCDELRT: No such process.
#3) This 'success' gives rise to many questions. Why didn't the original wifi script work on my system. What is unique about my system? Where should I place my script to run on boot? etc ...
my script
#!/bin/sh
# chmod +x filename.sh
# Example usage:
# sudo sh filename.sh
# sudo ./filename.sh
# source: http://wiki.tinycorelinux.net/wiki:setting_up_wifi
#sh-4.1# chmod +x /mnt/sdb1/mywifi.sh
#sh-4.1# ls -al /mnt/sdb1/mywifi.sh
#-rwxr-xr-x 1 root root 401 2012-07-18 19:36 /mnt/sdb1/mywifi.sh
wlan=eth1
essid=398VC
wepkey=
iwconfig ${wlan}
iwconfig ${wlan} essid ${essid}
iwconfig ${wlan} enc ${wepkey}
iwconfig ${wlan} key ${wepkey}
#iwconfig ${wlan} commit ; changed per tinypoodle
pkill udhcpc
#udhcpc -H box -b -i ${wlan} ; changed per tinypoodle
udhcpc -i ${wlan}
#
iwconfig ${wlan}
-
udhcpc -H box -b -i ${wlan}
option -h NAME is deprecated, use -x hostname:NAME
You can use: udhcpc -b -i ${wlan} -x hostname:box -p /var/run/udhcpc.{wlan}.pid
route: SIOCDELRT: No such process.
I think you can ignore this.
Where should I place my script to run on boot? etc ...
place the script in /opt and then call it from /opt/bootlocal.sh
-
Juanito
thanks for your help
will try your suggestions and let you know
learned a couple of things along the way, thanks for staying with me on this challenge
-
well ...
yesterday the script worked, today it doesn't
it appears to make it to udhcpc -i ${wlan} and it just keeps sending discovery notices until I control-c out of the script
recommendations?
-
udhcoc cannot get an IP address if you are not associated with an access point.
Use iwconfig to troubleshoot the connection.
Make sure the transmitter is on.
-
gerald_clark
thanks for your reply
from the script above, which command(s) associate with my access point?
the transmitter is on
having a hard time understanding why the original wifi script doesn't work and, the above script works then doesn't work
not quite sure how to troubleshoot to provide help to you folks
download another linux 2 days ago, wifi works flawlessly, is there anything I can cull from that distro to help me with tc+?
-
Boot with code "syslog".
In an aterm do "tail -f /var/log/messages"
Then configure wireless step by step while always having an eye on output from syslog to get feedback ;)
IMHO it is futile to use a script until connecting manually step by step works reliably.
-
tinypoodle
IMHO it is futile to use a script until connecting manually step by step works reliably.
agree! worked through wifi setup manually, then used the script
will try your recommendations, then let you know
? will the script command capture all output to the terminal so I can post ?
-
will the script command capture all output to the terminal so I can post
Yes
-
Boot with code "syslog".
In an aterm do "tail -f /var/log/messages"
Then configure wireless step by step while always having an eye on output from syslog to get feedback ;)
IMHO it is futile to use a script until connecting manually step by step works reliably.
how do i get the usb to boot with code "syslog"?
-
Hi hitsware
When you get to the boot prompt (the screen with the F2, F3, or F4 message) enter:
tc syslog
-
On usb, Syslinux message, then it launches boot sequences immediately. No boot prompt.
Is there a boot sh where I can insert the option?
-
There should be a file named boot/syslinux/syslinux.conf or syslinux.cfg or something like that, which should look something like this:
display boot.msg
default core
label core
kernel /boot/vmlinuz
append initrd=/boot/core.gz quiet noswap tce=UUID=aaab6273-4a6c-4118-8eb2-e31a9b31edb3 waitusb=10:UUID=aaab6273-4a6c-4118-8eb2-e31a9b31edb3 host=boxdell text
implicit 0
prompt 1
timeout 300
F1 boot.msg
F2 f2
F3 f3
F4 f4
add "syslog" somewhere on the line analogous to "append initrd=/boot/core.gz" or you can type something like "core syslog" delending on what label your conf file uses.
-
Juanito
Thanks. FYI, TC on usb uses extlinux. Appended syslog to file /boot/extlinux/extlinux.conf.
DEFAULT core
LABEL core
KERNEL /boot/vmlinuz
APPEND initrd=/boot/core.gz quiet waitusb=5:UUID="2ae0196d-ad7f-43fd-bae2-e303759a07da" tce=UUID="2ae0196d-ad7f-43fd-bae2-e303759a07da" syslog
-
I guess (without checking) that the "prompt 1" is what causes it to pause - this would allow you to add boot codes by entering:
core syslog
core base norestore (useful to check things and run e2fsck)
core etc, etc
-
well ... unusual things seem to be happening
attached is the messages file (copied immediately after boot) and, output from my script attempting to walk through a manual wifi setup
as you will see, didn't get far
thoughts?
-
Use a root terminal for wifi/net commands.
-
indeed, forgot the sudo in front of each command, thus the "Newbie" under my username
-
Manual WiFi Setup
sudo iwconfig eth1
sudo iwconfig eth1 essid 398VC
sudo iwconfig eth1 enc wepkey
sudo iwconfig eth1 key wepkey
sudo iwconfig eth1 commit (error for wireless request "commit changes" (8B00): operation not supported)
sudo pkill udhcpc
sudo udhcpc -i eth1 would sometimes give an error, but then connect
entered these commands manually, several times throughout the day. entered ping google.com and received an acknowledgement from the site
?Next Steps? If these commands work, why do you suppose the tcp wifi script did not work
FYI, roberts suggested using sudo -s with the above commands. However, sudo -s either did not work or I used it incorrectly
-
Either I'm confused or your pc is confused..
eth1 ?? this means there is an eth0 hiding somewhere trying to confuse the whole deal, right? besides, I thought all wifi was automatically declared as wlan0 etc etc
-
However, sudo -s either did not work or I used it incorrectly
If you enter "sudo su" <cr> the terminal will switch from user to root to save you having to enter "sudo" before every command.
eth1 ?? this means there is an eth0 hiding somewhere trying to confuse the whole deal, right? besides, I thought all wifi was automatically declared as wlan0 etc etc
In fact many wifi cards use eth1 - it's worth entering "ps aux | grep udhcpc" to check if udhcpc is trying to connect a wired ethernet adapter eth0, I've found this sometime seems to prevent wifi from connecting
-
interesting, is that (eth1) a result of the wifi card firmware or udev rules?
-
The name is compiled into the driver.
-
Either I'm confused or your pc is confused..
eth1 ?? this means there is an eth0 hiding somewhere trying to confuse the whole deal, right? besides, I thought all wifi was automatically declared as wlan0 etc etc
Not really hiding, most likely presence of an ethernet card.
I happened to remove my ethernet card recently, and since then my radio instead of eth1 has eth0 assigned.
-
If you enter "sudo su" <cr> the terminal will switch from user to root to save you having to enter "sudo" before every command.
Thanks Juanito
In fact many wifi cards use eth1 - it's worth entering "ps aux | grep udhcpc" to check if udhcpc is trying to connect a wired ethernet adapter eth0, I've found this sometime seems to prevent wifi from connecting
iwconfig lists my ethernet card as eth0
will try ps aux | grep udhcpc and report back
Thanks everyone for sticking with me.
-
"ps aux | grep udhcpc"
see attachment
udhcpc appears to be the most fragile part in the process
it either connects, now with the constant error message, see attached
or, it keeps sending discoveries and, I have to CTRL-C to exit, then start all over again
?What are my Next Steps?
-
# ps aux | grep udhcpc
2668 root grep udhcpc
That means there's no other instance of udhcpc running, which is a good thing.
I guess the next step could be to try something slightly different - for example: sudo iwconfig eth1 essid "ssid"
sudo iwconfig eth1 key restricted 7D:3A:7C:72:F7:9A:6F:91:DF:CF:C9:AD:CE [replace with your wep key]
sudo udhcpc -b -i eth1 -x hostname:box -p /var/run/udhcpc.eth1.pid
-
In fact many wifi cards use eth1 - it's worth entering "ps aux | grep udhcpc" to check if udhcpc is trying to connect a wired ethernet adapter eth0, I've found this sometime seems to prevent wifi from connecting
Might be a good idea to use boot code "nodhcp" when planning to use wireless net.
-
udhcpc appears to be the most fragile part in the process
it either connects, now with the constant error message, see attached
Not sure about error msg, looks perfect to me...
-
I guess the next step could be to try something slightly different - for example: sudo iwconfig eth1 essid "ssid"
sudo iwconfig eth1 key restricted 7D:3A:7C:72:F7:9A:6F:91:DF:CF:C9:AD:CE [replace with your wep key]
sudo udhcpc -b -i eth1 -x hostname:box -p /var/run/udhcpc.eth1.pid
results: no lease, forking to background
In fact many wifi cards use eth1 - it's worth entering "ps aux | grep udhcpc" to check if udhcpc is trying to connect a wired ethernet adapter eth0, I've found this sometime seems to prevent wifi from connecting
Might be a good idea to use boot code "nodhcp" when planning to use wireless net.
will add it to extlinux.conf and give it a try
at this point, getting confused, it is (1) my laptop, (2) tcp or (3) something else?