Tiny Core Linux
Tiny Core Extensions => TCE Q&A Forum => Topic started by: lmart on May 05, 2011, 06:22:20 PM
-
Working my way down the wiki, step by step, for setting up wifi.
#1 - installed wicd package (and its dependencies) from the package repository
#2 - sudo wicd-start
#3 - iwconfig; no wireless
?what are the next steps to get wireless (ipw2200) working?
-
ipw2200 requires firmware, which I have and use and have been meaning to make an extension out of it. I will aim for that soon.
http://ipw2200.sourceforge.net/firmware.php
-
If your WiFi device requires a firmware file there is no "shortcut" around it. But if you don't want to wait you could try to find out the exact file name (e.g. from the 'dmesg' output) and then attempt to download it from one of the files available from sf.net. You'll have to put the file into an appropriate directory (e.g. '/usr/local/lib/firmware' which needs to be created first) before installing the kernel driver extension (i.e. 'wireless-KERNEL.tcz' or 'compat-wireless-KERNEL.tcz') or activation of the device.
-
Can I get wifi up and working manually, or do you suggest that I wait until you make an extension out of it?
perhaps, use ndiswrapper as long the firmware dont exist.
See what I had done in http://forum.tinycorelinux.net/index.php?topic=8001.msg43118#msg43118
(today, I am working with Ethernet Adapters which are using the electricity network of the house and combining it with a LAN network)
Or/Then later, for the honor of linux and when available, take the firmware way.
-
I finally got around to uploading ipw2200.tcz, so it is now in the repo.
-
On the ipw2200 end, just make sure the ipw2200.tcz extension is loaded before the wireless-KERNEL.tcz. Though I am not familiar with using passwords and only vaguely familiar with Wicd.
-
To connect manually via cli, we need to know whether the ap you're trying to connect to uses no encryption, wep, wpa, wpa2 or whatever?
-
Best to use a root shell for network related commands ;)
-
Listing all wireless cards in that part would just clutter it, IMHO. Many need firmware, and many of those firmwares aren't even redistributable as extensions.
That aside, anyone can contribute to the wiki.
-
lmart: Do I understand from your reply #12 correctly that you've got a script that when running it in Puppy connects to your WLAN whilst it fails with certain errors in TC? Furthermore looking at some of the errors you reported I wonder whether the script was run as 'root' in TC (as already suggested in reply #13).
Clearly as Puppy runs everything under super-user privileges this might be a reason for a different outcome. I personally wholeheartedly disagree with the approach taken by Puppy and it's one of the reasons why I'm "hanging out" over here and not over there. In my own customized WiFi startup script (to be run by user 'tc') I only need 'sudo' for a very few commands (e.g. 'ifconfig $IF up', 'sudo wpa_supplicant -B -i $IF -c $CONF', and 'sudo udhcpc -b -i $IF').
If you need more help you'll have to improve on your reporting of the steps and outcomes of each step (as it is IMHO unfortunately rather inconsistent). I believe it would help if you would describe not just some details but rather try to structure things more useful for us out here trying to help:
(1) describe the step (e.g. plugging in a USB device, or quote the exact command used).
(2) describe the outcome (e.g. quote the full command result incl. command, warning and error messages)
(3) provide (optional) additional supporting information (e.g. 'dmesg' output).
Please note that the "usual" 'dmesg | tail -N' is a bit a "hit-and-miss" affair. I'd recommend to rather create what I would call the "dmesg delta": (a) take a "snapshot" before whatever action you undertake (e.g. dmesg > before-step1), (b) execute the step, and (c) identify what has changed (e.g. via dmesg > after-step1 ; diff -U 0 before-step1 after-step1).
Running a whole script (without attaching it here) and only quoting some output makes it too much of a guessing game for us to provide specific help. I'd therefore suggest to execute each (critical) step (e.g. a 'sudo COMMAND') on it's own providing supporting information along the lines of the above for each step. Only if we are really able to fully understand of what is happening on your system will we be able to provide you with more specific suggestions.
-
lmart-
I may have missed it, but what are the command sequence that works with other distros that does not work here? Also, post the output of:
cat `cat /opt/.tce_dir`/onboot.lst
If you are issuing terminal commands, or Wicd, in other distros to get wireless working there, then it should work here if the extensions are loaded in the correct order.
-
How about trying this:
$ tce-load -i ipw2200.tcz
$ tce-load -i wireless_tools.tcz
$ sudo modprobe lib80211_crypt_tkip
$ sudo modprobe lib80211_crypt_wep
$ sudo modprobe lib80211_crypt_ccmp
$ sudo iwconfig wlan0 essid "substitute_your_ssid_here"
$ sudo iwconfig wlan0 key restricted 12:34:56:78:90:AB:CD:EF:12:34:56:78:90)
$ sudo udhcpc -b -i wlan0
-
Adding
ifconfig eth1 upsomewhere could not harm. ;)
-
?next steps?
Start from a clean boot without ipw2000 and wireless_tools installed.
What did dmesg say?
-
I would suggest not to run the commands as a script but to enter them line by line in a terminal window to have the best chance of troubleshooting.
I use similar commands every day without "ifconfig eth1 up" and it works every time, but that's not to say it might not be needed in your case ;)
-
I use similar commands every day without "ifconfig eth1 up" and it works every time, but that's not to say it might not be needed in your case ;)
I suspect that might be driver specific, and for the same reason I refrained to mention a specific order and was also cautious in my choice of words [could not harm != needed]. ;)
-
a dmesg before the 8 commands and after the 8 commands are executed should be OK.
-
I remembered I had an old toshiba with intel wifi, here's what I get, albeit for wpa2 instead of wep:
$ lspci
01:0a.0 Network controller: Intel Corporation PRO/Wireless LAN 2100 3B Mini PCI Adapter (rev 04)
$ sudo cp /mnt/hda2/conf/wpa_jnet_configure.conf /etc/wpa_configure.conf
$ tce-load -i /mnt/hda2/tce_3x/optional/ipw2100_firmware.tcz
$ tce-load -i /mnt/hda2/tce_3x/optional/wireless_tools.tcz
$ tce-load -i /mnt/hda2/tce_3x/optional/wpa_supplicant.tcz
$ sudo modprobe lib80211_crypt_tkip
$ sudo modprobe lib80211_crypt_wep
$ sudo modprobe lib80211_crypt_ccmp
$ sudo iwconfig eth1 essid "jnet"
$ sudo wpa_supplicant -B -Dwext -i eth1 -c/etc/wpa_configure.conf
$ sudo udhcpc -b -i eth1
udhcpc (v1.18.3) started
Sending discover...
Sending select for 192.168.1.112...
Lease of 192.168.1.112 obtained, lease time 86400
deleting routers
route: SIOCDELRT: No such process
adding dns 195.229.241.222
adding dns 213.42.20.20
$ dmesg | tail -20
...
cfg80211: Using static regulatory domain info
cfg80211: Regulatory domain: 00
(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
(2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
(2457000 KHz - 2482000 KHz @ 20000 KHz), (600 mBi, 2000 mBm)
(2474000 KHz - 2494000 KHz @ 20000 KHz), (600 mBi, 2000 mBm)
(5170000 KHz - 5250000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
(5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
cfg80211: Calling CRDA to update world regulatory domain
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'
ieee80211: 802.11 data/management/control stack, git-1.1.13
ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
ipw2100: Intel(R) PRO/Wireless 2100 Network Driver, git-1.2.2
ipw2100: Copyright(c) 2003-2006 Intel Corporation
ACPI: PCI Interrupt Link [LNKG] enabled at IRQ 11
ipw2100 0000:01:0a.0: PCI INT A -> Link[LNKG] -> GSI 11 (level, low) -> IRQ 11
ipw2100: Detected Intel PRO/Wireless 2100 Network Connection
ipw2100 0000:01:0a.0: firmware: requesting ipw2100-1.3.fw
lib80211_crypt: registered algorithm 'TKIP'
lib80211_crypt: registered algorithm 'WEP'
lib80211_crypt: registered algorithm 'CCMP
perhaps you don't have the correct firmware?
-
The output from "lspci" - just the line concerning your wireless hardware - would be useful.
Are you sure the firmware was loaded before wireless-2.6.33.3-tinycore.tcz? The dmesg you uploaded seemed to indicate that might not have been the case?
-
when you ask if the firmware was loaded, are you referring to JasonW's ipw2200.tcz extension? if so, that includes wicd?
By firmware, I mean the ipw2200 extension, not wicd.
Could you post the output of "lspci" for your wireless hardware.
-
small problem, no lspci ...
Install pci-utils ;)
-
OK, so your hardware and driver version are:
06:0b.0 Network controller: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection (rev 05)
ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq
So, according to http://ipw2200.sourceforge.net/firmware.php, your firmware choices are: driver versions v1.1.1 and newer firmware v3.0 , firmware v3.1
Jason provided firmware v3.1 in his ipw2200.tcz extension, so things should work if you have your ssid and wep code entered correctly.
Sorry, but I'm not sure what you could try next..
-
Post the output of
sudo iwconfig&
ifconfigright before the udhcpc step
Alter the key of first before posting
-
my commands (captured via 'script') follow; if this does not help you and you want me to start from a completely fresh frugal install of tinycore, will do; pls advise
after reading the whole efforts of a huge number of hardworkers.. a question: are you communicating here with your box with wired lan?
if this is the case, I would kill the wired lan process before starting the wireless process ( or use the onboot code "nodhcp", or perhaps blacklist the wired ethernet module?.. who knows.. both are from Intel..).
-
When all works fine in puppy, does iwconfig also show "Security mode:restricted" ?
With
sudo iwlist eth1 scan you see your AP?
-
The iwconfig command should look like this:
sudo iwconfig wlan0 key restricted 54:B0:DB:75:B1:54:0C:A5:D1:89:C3:6B:ED
..i.e. the code should not be enclosed in quotes
also, did you issue the command: sudo modprobe lib80211_crypt_wep..I don't see the results in the dmesg you post above.
-
Maybe this is tempting fate, but you could try using the iw extension instead of wireless_tools - I don't think it would be a problem to have both of them loaded at the same time, the commands would then be something like:
$ sudo iw eth1 connect ssid keys 1:00112233445566778899AABBCC
$ iw list [to list available devices]
$ iw dev eth1 scan [to look for access points]
$ iw dev eth1 link [to check the link status]
-
FWIW, I have had both extensions loaded many times and never observed any particular issue about.
-
Generally speaking: If there are difficulties with setting up wireless and one has the opportunity it is preferable to turn off encryption entirely until connecting to an open AP works, and only then to look into the encryption part.
-
Hi lmart
Tell your wife "It's the thrill of making the trip, getting there is just a bonus.".
-
my recommendation:
- again: kill the dhcp process or bootcode NODHCP; the cable disconnected is not enough
- go for ndiswrapper (perhaps you achieve something very quick)
- when your wife sleep, make nightshifts for moving to a linux driver (as per current try)
I know the pressure for making running a PC in a family..
Honestly, if your wife is benchmarking the laptop of her girlfriends, which are apple or weandooze, then forget linux: any few issue coming up with linux later (with openoffice.. text or format lost by exchanging files with weandooze..), will be massiv because the benchmark will come up immediatly "it runs at my girlfriend laptop". Girls dont have in my opinion such patience as boys for technical things running differently or a bit unstable. Sorry girls.. (but my wife has much more patience for learning a video-recorder command than me.. here I dont have any second of patience for a stupid engineer wanted me to learn how to use a complicated video setup).
-
adopt a puppy
I made it with Puppy on my old box, too !
But I achieved TCL, later (it tooks me.. >1 month..)
So, mister, I achieved a bit more than you..;-) ... (just to see if you are a sportsman)
Now: I use a LAN adapter for electricity network. So, I am hardwired via my electricity network which is 200% better than WLAN. Weandooze? oh no.. this is like you are hungry and you go to MacDonalds instead of having a "Steack Frites" at a nice french restaurant in Brittany (where you get a glas of house wine with it). terrible decision..
-
Thanks a bunch guys. I've got that stupid tune stuck in my brain now. And when It comes to whistling, I've been told I couldn't carry a tune in a bucket! :)
-
#?unsure what following 3 commands accomplish
sudo modprobe lib80211_crypt_tkip
sudo modprobe lib80211_crypt_wep
sudo modprobe lib80211_crypt_ccmp
These kernel modules deal with wifi encryption - strictly speaking you only need lib80211_crypt_wep, but you might as well load them all.
-
Without looking into details at this moment, do not use (Security mode) "restricted", as it works with Security mode:open.
(That was my suspicion since 14 posts ago...)
-
juanito & tinypoodle, thanks for sticking with me
ok, spent the weekend culling through wifi stuff
here's what's on my plate for this evening, would appreciate your review/questions/comments
in shell script format, however, will run all commands manually from the cli
#variables - network specific
#essid (text), wepkey (hex 00:00:00:00:00:00:00:00:00:00)
wlan=eth1
essid=
wepkey=
#detect wifi device, load the applicable driver, will load manually as tce-load did not work
#tce-load -i pci-utils.tcz
#tce-load -i ip...
first "pkill udhcpc"
then the whole stuff
-
why not using wpa_supplicant, with WEP, too?
Anyhow, WPA is much better than WEP, so perhaps it would run with WPA?
-
why not using wpa_supplicant, with WEP, too?
Anyhow, WPA is much better than WEP, so perhaps it would run with WPA?
Why not? ::)
Because complicating things before the basics work somehow - i.e. achieving a connection with simple means - does not help at all!
And no, if taking the approach of changing router settings, WPA would not help with troubleshooting when it does not work with WEP - turning off encryption entirely could make sense.
If you do not understand, please read all posts of the thread in order.
-
Next thing to achieve would be "seeing" your AP with
iwlist eth1 sunder TC, the same way as you can see it under puppy.
-
???at this point, is there any reason to keep typing the commands manually as opposed to a script???
Yes of course, scripting doesn't make sense before you have managed to get a functional connection manually.
-
perhaps you need the wpa_supplicant?
wpa_supplicant -B -Dwext -ieth1 -c/etc/wpa_supplicant.conf
with wpa_supplicant.conf (from ubuntu page http://wiki.ubuntuusers.de/wlan/wpa_supplicant ; see in the forum here too)
==============
network={
ssid="Netzwerkname"
scan_ssid=1
key_mgmt=NONE
wep_tx_keyidx=0
wep_key0="Netzwerkschlüssel"
}
==============
-
It is possible your router does not like the busybox udhcpc. You can try one of the other dhcp clients in the repo (isc-dhcp).
-
Hi lmart
while trying to reduce the variables, changing dhcp would add one to the mix ...
Actually you would be replacing one variable with another to try to either confirm or eliminate it as
a possible source of your problems. If nothing changes you can always go back to the original dhcp.
-
floppy; appreciate your help, you are staying the course on wpa and, you may be correct, i know nothing about wpa, w/ Puppy all i do in enter my wep and it works so if wpa is at play, it must be in the background ... as promised, will try your recommendation after i exhaust the current course,
the name is wpa_supplicant.
the parameters inside were for wep.
But you can use wpa2.. (tinypoodle would like it, too.. ;-).
You will get it.. it took me 1 month..
wpa_supplicant: here http://wiki.tinycorelinux.net/wiki:setting_up_wifi or here http://hostap.epitest.fi/wpa_supplicant/
-
perhaps you need the wpa_supplicant?
wpa_supplicant -B -Dwext -ieth1 -c/etc/wpa_supplicant.conf
with wpa_supplicant.conf (from ubuntu page http://wiki.ubuntuusers.de/wlan/wpa_supplicant ; see in the forum here too)
==============
network={
ssid="Netzwerkname"
scan_ssid=1
key_mgmt=NONE
wep_tx_keyidx=0
wep_key0="Netzwerkschlüssel"
}
==============
Have you even read Reply #62??
Have you read all the 67(!!) preceeding posts of this thread in correct order?
::)
-
lmart,
see Replies #13, #41, #50.
The thread is now at Reply #75 and you still haven't followed any of those... ::)
Also, please change the topic of the thread, as it is not representative of content at all.
-
This is my last post on Tinycore Linux Forum.