Tiny Core Extensions > TCE Bugs

(fixed for the tce* version) segfault: wpa_supplicant tcz*

<< < (3/3)

jpeters:
For whatever it's worth, I've never used wpa_supplicant, and had no problem getting ath0 up and running with tc on my laptops with a simple script. I have two access points I connect to, one on 80211B with WEP, and one on 80211A without.  My approach was to get a buy a card that I knew would work (inexpensively, of course   :) .   

tobiaus:

--- Quote from: roberts on March 13, 2009, 08:25:38 PM ---Have you tried copying your wpa_supplicant.conf from xubuntu into TC and try it.

--- End quote ---

there isn't one, i've looked in scripts and setups and they link to files that simply aren't there. i've used sudo find / and grep to look for anything containing "wpa" and "conf" but there isn't one.


--- Quote from: jpeters on March 14, 2009, 12:03:31 AM ---For whatever it's worth, I've never used wpa_supplicant, and had no problem getting ath0 up and running with tc on my laptops with a simple script. I have two access points I connect to, one on 80211B with WEP...

--- End quote ---

with a key i assume. i know it's wep (that's the setting you use in the xubuntu setup,) so your way probably suffices. it's all very confusing.


--- Quote from: jpeters on March 14, 2009, 12:03:31 AM ---My approach was to get a buy a card that I knew would work (inexpensively, of course   :) .   

--- End quote ---

mine too, i bought mine for dsl. it seems to be just fine with dsl, but i wasn't able to connect it either. actually there was just once when i got both lights blinking in dsl, just the way it does when it's connected in xubuntu. but the browser wouldn't go to any site, not even ip addresses (so i don't think it's a dns issue.) i've used the dsl book to try to set it up, but i've only gotten close.

there's a lot more to making something friendly than sticking a gui on top. i have no problem with the command line, it's everything else that is confusing. i hope someday connecting to things on linux is a little less complicated, but this is an iwconfig / all the other tools issue, not a tc issue. probably. i have to say the first time i did this in windows it was really very simple. in xubuntu almost as much. once you have the three commands right, naturally, it's very easy from there.

i'd certainly rather use the net in tc than anything else though. i mean if it wasn't for that preference, this wouldn't be an issue let alone a hassle.

softwaregurl:
Hi tobiaus,
Wireless has given me fits on linux as well, once I got it its a gazillion times better then before linux.  I finally got wpa working on DSL just a month ago.  the problem was prism54 was wrongly detecting my card.  I had tryed unloading it but didn't realize all the dependencies that had to go to (e.g. firmware).  Then went ndiswrapper.  A headache in its self because the driver that works with windows doesn't with ndiswrapper.  I had to install a disposable copy of windows to extract each one (5 or 6 I think) then try each one.  I still don't know how I got wpa_supplicant.conf to work right but it does if I do everything right and pray lots.
heres a couple things I found:

Don't try to iwlist wlan0 scan ever.  It will never connect or stop transferring data even if the lights are on.

give wpa_supplicant lots of time to connect...Lots...before starting the DHCP client.  I find its best to just start it manually after booting finishes. and the lights look right.

Double and triple check dmesg to see whats loading on boot.  Remove the card or maybe disable in bios and compare the two boots.  Check all the bios settings.  My pc card slots have more then one mode in bios.  Makes no difference which in windows but does in Linux.  And different Linuxs can be very different.  TCL works on stuff I never can get going on debian and vs. versa.

wpa_supplicant can connect to most anything.  It can connect to the first open network it finds if configured that way.  I will be needing to connect to open access points and wpa at least.

I know this is just some general stuff because I havn't tryed beyond that i need to recompile to get rid of the kernel panic on boot with tiny core.  Once I can boot then on a computer with wireless I'll post details on what I find.  Hope something in this helps until I can give an educated answer.
I still say it's worth the effort.  Once I do get connected its so much more stable then windows.  Everything I read says the newer kernels do way better at wireless.  And if it doesn't work right you "free" to redo it so it does.
--- Quote ---i got wireless working in jwm without .xsession by examining the output of ps -FA and replicating this and that, so i have a script that lets me get online even though i'm not using xfce anymore.
--- End quote ---
Before TCL i had never successfully compiled anything for Linux much less even considered attempting the custom kernel I need.  Hope that gives some encouragement.

jpeters:
I'm using a Netgear WAG511 dual band card, and have wireless-2.6.26, wireless_tools, and madwifi-hal loaded.  Then  I can modprobe ath_pci, and use iwconfig ath0 channel XX essid XXX key XXX.
The difference from DSL is using udhcpc -i ath0 instead of pump  to get the lights blinking.   

Navigation

[0] Message Index

[*] Previous page