1
Angstrom & OpenZaurus / Sitecom Wifi Card
« on: July 18, 2005, 11:46:06 am »
I sent you an email Steven.
Select language:
News:
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1] 2
2
Angstrom & OpenZaurus / What About The New R21 Kernel Upgrade ?
« on: July 15, 2005, 11:20:35 am »
I have the US 5500, and on the R21 with both GPE and Opie, it got stuck on boot. Hentages seemed to work, as does the non-R21 version of 3.5.3 with Opie. I have some odd problems when I reboot with the 3.5.3, but it otherwise seems stable.
3
Angstrom & OpenZaurus / Sitecom Wifi Card
« on: July 14, 2005, 07:33:04 pm »
Haha, I just spent several irritating days trying to get my old D-Link DCF-650W card to work. It turns out that it wasn't supported. The file I pointed you to is the file that seems to let auto-detection scripts figure out what it is that's been plugged into the CF slot. It has WiFi cards, wired cards, memory cards, and random other things in that list. If it's not in that list, you're probably going to have a hard time getting it to work.
My recommendation is don't get a card unless you can find out what model number it is beforehand. That way you can make sure that it works before shelling out money for it. Not all cards from a particular manufacturer are supported, so if you just assume that a Linksys will work, you may find that you got one that really didn't.
You can do a search for a manufacturer's card in that config file by typing in "cat /etc/pcmcia/config | grep -i <search string>" on your Zaurus. That command basically reads the text of that file into grep who searches for that search string in the file and prints out every line where that string appears. The -i makes the search case insensitive so you don't have to worry about capitalization. When I searched for Sitecom I got no results, so that's probably a good sign to stear clear for the moment. It doesn't mean that it can't work, just that it will be hard to make it work. Good things to try in your search string are vendor names (though some vendors are typed differently like both "D Link" and "D-Link" are used) and exact model numbers like "DCF-650W" or "WCF12".
Here's a sample of what that command prints out for cat /etc/pcmcia/config | grep -i "linksys":
By doing that, you can search for and try to find out what models of cards are most easily supported.
I am no expert in Linux nor the Zaurus, but I feel like I have some idea what I'm talking about with the wireless cards. Of course, I could be completely off my rocker and I have no idea what I'm talking about, but that's up to you to decide.
My recommendation is don't get a card unless you can find out what model number it is beforehand. That way you can make sure that it works before shelling out money for it. Not all cards from a particular manufacturer are supported, so if you just assume that a Linksys will work, you may find that you got one that really didn't.
You can do a search for a manufacturer's card in that config file by typing in "cat /etc/pcmcia/config | grep -i <search string>" on your Zaurus. That command basically reads the text of that file into grep who searches for that search string in the file and prints out every line where that string appears. The -i makes the search case insensitive so you don't have to worry about capitalization. When I searched for Sitecom I got no results, so that's probably a good sign to stear clear for the moment. It doesn't mean that it can't work, just that it will be hard to make it work. Good things to try in your search string are vendor names (though some vendors are typed differently like both "D Link" and "D-Link" are used) and exact model numbers like "DCF-650W" or "WCF12".
Here's a sample of what that command prints out for cat /etc/pcmcia/config | grep -i "linksys":
Code: [Select]
card "Linksys WPC11 11Mbps 802.11b WLAN Card"
card "Linksys WPC11 11Mbps 802.11b WLAN Card"
card "Linksys WCF12 Wireless CompactFlash Card"
card "Linksys LANmodem 28.8"
version "LINKSYS", "PCMLM28"
card "Linksys LANmodem 33.6"
version "LINKSYS", "PCMLM336"As you can see by that third line, my WCF12 Linksys card is in the file, so I know it's nice and supported by the auto-detection. By doing that, you can search for and try to find out what models of cards are most easily supported.
I am no expert in Linux nor the Zaurus, but I feel like I have some idea what I'm talking about with the wireless cards. Of course, I could be completely off my rocker and I have no idea what I'm talking about, but that's up to you to decide.
4
Angstrom & OpenZaurus / Setting Up Wifi Problem/questions
« on: July 14, 2005, 07:17:32 pm »
Just ignore me, I'm rambling now, and I think I have enough tools in my little mini Linux toolbox now to be able to track down my wireless problem...
Okay, I tried using a totally different and newer wireless card I canabalized off a different device... (Mwahahahahaa... *rubs hands maniacally*) Unfortunately, it uses the default settings as well (for wlan0). Obviously whatever script that goes through and reads /etc/network/interfaces just doesn't like the syntax.
I dug around some more and I found this little Debian script over in /etc/network/if-pre-up.d/wireless-tools:
Well, that probably doesn't help.... It could be that the script is just detecting that I'm trying to use wlan_ng and it just exits as soon as it sees that, and no other script takes over. Frankly, there are no other scripts in if-pre-up.d and no other pre-up stuff, so I think that there is nothing there to handle wlan-ng that I can see easily. Kay, I don't need to use wlan_ng, I just want it to work and get set properly.
The driver that my current test card uses appears to be hostap_cs, so that means it's a more advanced version of the prism2_cs driver. That means that I don't have to use wlan_ng to get it set up.
* * * * *
Update: I have WiFi working with this Linksys card. My conclusion is that:
1) The D-Link DCF-650W, though supported previously (or was just lucky to get set right previously), is not currently supported.
2) You have to manually set the /etc/network/interfaces file to get things right.
3) DON'T use wlan_ng. If the driver uses hostap_cs, then don't. Most cards use hostap over prism2 now, and prism2 is the one that used wlan_ng.
4) The syntax for the wireless is moderately simple. It's pretty much "wireless_<function> <value>" where the function is one of the parameters for iwconfig like essid or key. For a list of iwconfig parameters and valid values, see the iwconfig man page.
5) You can tell what cards are and aren't supported by looking through the files in /etc/pcmcia. An easy way to check is find the manufacturer of your card like Linksys or D-Link. You can look to see if it's generally supported by typing cat /etc/pcmcia/config | grep "Linksys", where Linksys is the name of your card's manufaturer (and it's case sensitive.) To see if it's supported by hostap, type cat /etc/pcmcia/hostap_cs.conf | grep "Linksys". If your exact card shows up on the list, then your card is supported. For example, I have a Linksys card with a model number of WCF12, and I see a line in the output of both commands that says card "Linksys WCF12 Wireless CompactFlash Card", so it's supported by both the general recognition as well as the hostap driver.
I fixed it! To bad I just didn't know it was because it wasn't supported and the script was broken, then the second script wasn't correct for this enviroment.
Okay, I tried using a totally different and newer wireless card I canabalized off a different device... (Mwahahahahaa... *rubs hands maniacally*) Unfortunately, it uses the default settings as well (for wlan0). Obviously whatever script that goes through and reads /etc/network/interfaces just doesn't like the syntax.
I dug around some more and I found this little Debian script over in /etc/network/if-pre-up.d/wireless-tools:
Code: [Select]
# Detect and do nothing for linux-wlan-ng interfaces;
# which are configured by thier own if-pre-up script.
if [ -n "$IF_WIRELESS_TYPE" -a "$IF_WIRELESS_TYPE" = "wlan-ng" ]; then
exit 0
fiWell, that probably doesn't help.... It could be that the script is just detecting that I'm trying to use wlan_ng and it just exits as soon as it sees that, and no other script takes over. Frankly, there are no other scripts in if-pre-up.d and no other pre-up stuff, so I think that there is nothing there to handle wlan-ng that I can see easily. Kay, I don't need to use wlan_ng, I just want it to work and get set properly.
The driver that my current test card uses appears to be hostap_cs, so that means it's a more advanced version of the prism2_cs driver. That means that I don't have to use wlan_ng to get it set up.
* * * * *
Update: I have WiFi working with this Linksys card. My conclusion is that:
1) The D-Link DCF-650W, though supported previously (or was just lucky to get set right previously), is not currently supported.
2) You have to manually set the /etc/network/interfaces file to get things right.
3) DON'T use wlan_ng. If the driver uses hostap_cs, then don't. Most cards use hostap over prism2 now, and prism2 is the one that used wlan_ng.
4) The syntax for the wireless is moderately simple. It's pretty much "wireless_<function> <value>" where the function is one of the parameters for iwconfig like essid or key. For a list of iwconfig parameters and valid values, see the iwconfig man page.
5) You can tell what cards are and aren't supported by looking through the files in /etc/pcmcia. An easy way to check is find the manufacturer of your card like Linksys or D-Link. You can look to see if it's generally supported by typing cat /etc/pcmcia/config | grep "Linksys", where Linksys is the name of your card's manufaturer (and it's case sensitive.) To see if it's supported by hostap, type cat /etc/pcmcia/hostap_cs.conf | grep "Linksys". If your exact card shows up on the list, then your card is supported. For example, I have a Linksys card with a model number of WCF12, and I see a line in the output of both commands that says card "Linksys WCF12 Wireless CompactFlash Card", so it's supported by both the general recognition as well as the hostap driver.
I fixed it! To bad I just didn't know it was because it wasn't supported and the script was broken, then the second script wasn't correct for this enviroment.
5
Angstrom & OpenZaurus / Setting Up Wifi Problem/questions
« on: July 14, 2005, 12:03:52 pm »
For hostap_cs there is a .o file for it in /lib/modules/2.4.18-rmk7-pxa3-embedix/pcmcia/ but, there is no entry for the driver in the /etc/pcmcia/config file, which would explain why I can't use that driver. It's simply not defined. This is getting WAY too complicated.
6
OpenZaurus/Opie/Qtopia / Making It Simpler
« on: July 14, 2005, 11:47:45 am »
Thanks, I'll drop you an email.
7
Angstrom & OpenZaurus / Sitecom Wifi Card
« on: July 14, 2005, 11:44:17 am »Quote
Hi,You have a specific model in mind? Also, I think that a simple Google search would reveal a lot of info about your card... that, or you could look in /etc/pcmcia/config to see if it's in the list (assuming that I know what I'm talking about). On the 5500 config file, there is no mention of "sitecom" at all.
Has anyone had experiance with any sitecom wireless cars, and know weather they are any good, of weather to saty clear of them?
Thanks
Jedeye
[div align=\"right\"][a href=\"index.php?act=findpost&pid=88244\"][{POST_SNAPBACK}][/a][/div]
8
Angstrom & OpenZaurus / Setting Up Wifi Problem/questions
« on: July 14, 2005, 11:39:58 am »
I unbent the pin (using this handy dandy plastic knife) and plugged in the card. Despite it being recognized and using the orinoco_cs drivers, it's still not pulling the wireless configuration info from /etc/network/interfaces. I really think that either the syntax is just plain wrong or it needs to go in a different file.
9
Angstrom & OpenZaurus / Setting Up Wifi Problem/questions
« on: July 14, 2005, 11:35:46 am »
Yay!!! I bent a pin inside the CF slot!!!
I don't think I was meant to succeed...
I don't think I was meant to succeed...
10
Angstrom & OpenZaurus / Setting Up Wifi Problem/questions
« on: July 13, 2005, 07:23:34 pm »
Bah.. BAH! I SAY!
Okay, I added an entry to config.opts.
I'm having odd problems, though, which highlight that I have no real idea of what I'm doing. When I first added the entry, I didn't have the host_ap line, and the orinoco_cs line was uncommented. I popped in the card after it started up and it recognized it fine. The output of dmesg, ifconfig, and iwconfig basically said that it was bound to eth0. I thought that was funky, so I edited config.opts to what you see above. At that point it started recognizing it as the XI-300 again. I got frustrated, and uncommented out the XI-300 lines in /etc/pcmcia/config and it still recognized it as the XI-300, so I rebooted the Z. More or less, I did a bunch of commenting and uncommenting, and it feels like it randomly detects the right card only about 25% of the time, and only when it's bound to orinoco. (Of course, there is the irritating problem that the Z only restarts properly about 25% of the time as well, and that seems to be completely random. I have to keep using the restart button in the battery compartment. )
Okay... I am absolutely sure that it misidentifies the card as the XI-300 when I try to bind the DCF-650W to host_ap instead of orinoco. Fine. Tomorrow I will edit /etc/network/interfaces to define the eth0 adapter have the same info as the wlan0 adapter and hope it works that way. Sheesh.
I know if it's misidentifying my card as a card that I have COMPLETELY commented out, then there's some other file in the mix that I don't know about that's messing things up.
Okay, I added an entry to config.opts.
Code: [Select]
#Attempt to get the D-Link DCF-650W working
card "D-Link DCF-650W"
version "D-Link", "DCF-650W"
manfid 0xd601, 0x0002
#bind "orinoco_cs"
bind "host_ap"I'm having odd problems, though, which highlight that I have no real idea of what I'm doing. When I first added the entry, I didn't have the host_ap line, and the orinoco_cs line was uncommented. I popped in the card after it started up and it recognized it fine. The output of dmesg, ifconfig, and iwconfig basically said that it was bound to eth0. I thought that was funky, so I edited config.opts to what you see above. At that point it started recognizing it as the XI-300 again. I got frustrated, and uncommented out the XI-300 lines in /etc/pcmcia/config and it still recognized it as the XI-300, so I rebooted the Z. More or less, I did a bunch of commenting and uncommenting, and it feels like it randomly detects the right card only about 25% of the time, and only when it's bound to orinoco. (Of course, there is the irritating problem that the Z only restarts properly about 25% of the time as well, and that seems to be completely random. I have to keep using the restart button in the battery compartment. )
Okay... I am absolutely sure that it misidentifies the card as the XI-300 when I try to bind the DCF-650W to host_ap instead of orinoco. Fine. Tomorrow I will edit /etc/network/interfaces to define the eth0 adapter have the same info as the wlan0 adapter and hope it works that way. Sheesh.
I know if it's misidentifying my card as a card that I have COMPLETELY commented out, then there's some other file in the mix that I don't know about that's messing things up.
11
Angstrom & OpenZaurus / Setting Up Wifi Problem/questions
« on: July 13, 2005, 06:01:44 pm »
Oh! I found something!!! I looked through /etc/pcmcia/config and I found out that it doesn't have an entry for my card at all!!! That's probably a good thing to discover and something that doesn't help much. Assuming that /etc/pcmcia/config is the file used to identify devices, that would probably explain why it's not finding the right card. The XI-300 is in there.
Since no one seems to use the prism2 stuff and all the prism2 cards are using orinoco_cs, that's probably what I should use. I can edit config.opts to add my card to the list, and hopefully, things would work better? I run cardctl ident and I get
It looks like it's misidentifying my card because the manfid is the same as the XI-300. I feel like adding this in, though, is just gonna change the text string identifier and not really make things any different in the actual operation.
I also noticed that I do not have a /etc/pcmcia/wlan-ng.conf file... Is that right? Is there a way for me to easily figure out if I have wlan-ng?
Code: [Select]
card "ZCOMAX AirRunner/XI-300"
#version "ZCOMAX", "AirRunner/XI-300"
manfid 0xd601, 0x0002
bind "orinoco_cs"Since no one seems to use the prism2 stuff and all the prism2 cards are using orinoco_cs, that's probably what I should use. I can edit config.opts to add my card to the list, and hopefully, things would work better? I run cardctl ident and I get
Code: [Select]
Socket 0:
product info: "D-Link", "DCF-650W", ""
manfid: 0xd601, 0x0002
function: 6 (network)
Socket 1:
no product info availableIt looks like it's misidentifying my card because the manfid is the same as the XI-300. I feel like adding this in, though, is just gonna change the text string identifier and not really make things any different in the actual operation.
I also noticed that I do not have a /etc/pcmcia/wlan-ng.conf file... Is that right? Is there a way for me to easily figure out if I have wlan-ng?
12
Angstrom & OpenZaurus / Setting Up Wifi Problem/questions
« on: July 13, 2005, 05:35:52 pm »Quote
<snip>I do have two of these cards... I also have access to a few more if it's just the card. For the heck of it, I switched to the other card for this test. Since they should be identical, either it will work, or it'll still be stupid. (It appears that the latter is the case.)
My suspicion at this point is faulty card or wrong drivers.
Okay... I just noticed that the card icon at the bottom detects it as a "ZCOMAX AirRunner/XI-300". That's definately not the right card. I'm confused because on the older version of OZ/Opie, it worked just fine. (A year or two old version.)
The dmesg difference is:
Code: [Select]
hostap_crypt: registered algorithm 'NULL'
hostap_cs: 0.3.7 - 2005-02-12 (Jouni Malinen )
hostap_cs: setting Vcc=33 (constant)
hostap_cs: CS_EVENT_CARD_INSERTION
hostap_cs: ignoring Vcc=33 (from config)
Checking CFTABLE_ENTRY 0x01 (default 0x01)
IO window settings: cfg->io.nwin=1 dflt.io.nwin=1
io->flags = 0x0046, io.base=0x0000, len=64
hostap_cs: Registered netdevice wifi0
hostap_cs: index 0x01: Vcc 3.3, irq 35, io 0xc4860000-0xc486003f
prism2_hw_init: initialized in 110 ms
wifi0: NIC: id=0x8002 v1.0.0
wifi0: PRI: id=0x15 v0.3.0
wifi0: STA: id=0x1f v0.8.3
wifi0: defaulting to bogus WDS frame as a workaround for firmware bug in Host AP mode WDS
wifi0: registered netdevice wlan0
wifi0: TXEXC - status=0x0004 ([Discon]) tx_control=000c
retry_count=0 tx_rate=0 fc=0x0108 (Data::0 ToDS)
A1=00:00:00:00:00:00 A2=00:05:5d:f9:92:21 A3=33:33:ff:f9:92:21 A4=00:00:00:00:00:00
wifi0: TXEXC - status=0x0004 ([Discon]) tx_control=000c
retry_count=0 tx_rate=0 fc=0x0108 (Data::0 ToDS)
A1=00:00:00:00:00:00 A2=00:05:5d:f9:92:21 A3=33:33:00:00:00:02 A4=00:00:00:00:00:00
wifi0: TXEXC - status=0x0004 ([Discon]) tx_control=000c
retry_count=0 tx_rate=0 fc=0x0108 (Data::0 ToDS)
A1=00:00:00:00:00:00 A2=00:05:5d:f9:92:21 A3=33:33:00:00:00:02 A4=00:00:00:00:00:00
wifi0: TXEXC - status=0x0004 ([Discon]) tx_control=000c
retry_count=0 tx_rate=0 fc=0x0108 (Data::0 ToDS)
A1=00:00:00:00:00:00 A2=00:05:5d:f9:92:21 A3=33:33:00:00:00:02 A4=00:00:00:00:00:00
wlan0: no IPv6 routers present It correctly identifies my card as a Prism/2 card. I went and looked up info on my card...Kismet reports this:
Card: D-Link DCF-650W
Chipset: Prism/2
Description: D-Link Compact Flash
Driver: wlan-ng/hostap
Confirmed Working: Yes
The Zaurus user's group says:
Vendor Model: DLink DCF-650W
Chipset: Prism 2
Supported: Yes
Blocks Ports: Yes
Standby/rx/tx ma: 170/280/380
My card is a fairly common card, but having the system seem to misidentify it doesn't make me feel very good. In theory the XI-300 it misidentified as has the same chipset and drivers, so it shouldn't be so... irritable, but I don't rememeber seeing the misidentification before on the Hentages ROM. Whether it's because I just missed it, or if it's a new issue, I don't know.
13
Angstrom & OpenZaurus / Hentges Install Guide
« on: July 13, 2005, 05:08:29 pm »
It's also possible to kill the initial kernel warning message if it bothers you. You can completely remove the file called /etc/init.d/checkversion, or just rename it to temporarily disable it.
Also, you can just hit your "ok" button to do the default boot of 1 when you get to that part of the bootup.
Also, you can just hit your "ok" button to do the default boot of 1 when you get to that part of the bootup.
14
Angstrom & OpenZaurus / Xcas Installation On Sl-5500
« on: July 13, 2005, 03:30:57 pm »
Assuming I ever get my build system up and working, I'd be happy to compile it for you. Right now, I need to get my build system up, and hopefully the nice people in the other forum will help me. Heh...
Until then... you can either try it yourself or look for another volunteer to get it working for you. (Stupid differences in processors!!)
Until then... you can either try it yourself or look for another volunteer to get it working for you. (Stupid differences in processors!!)
15
OpenZaurus/Opie/Qtopia / Making It Simpler
« on: July 13, 2005, 03:28:16 pm »
Thank you, I suspected as much. I'm not sure how complicated my program may or may not get, but it's always irritating when it's the compiler's fault that my program is buggy.
Okay. So my other system's toolchain is up and built, but it was prebuilt, so I didn't have to figure out how to do a cross compile. I think I got something together and working with Crosstool for the 5500, but I have no idea if I used the right settings or not. (I'm guessing not.) Can anyone spare a moment to give me an idea of what I should compile and/or how to get a working cross compile going or where to find that info? I don't care if I use Crosstool or not as long as something works.
Ideally, I'll get Opie's SDK up and running with it, but one thing at a time!
Okay, so I need an old version of gcc, I need to compile for the ARM4 arch. Should I use the same kernel that my Z is running? What about things like glibc or linuxthreads or whatever?
Of course, if someone can explain to me why OE is so complicated to install, and why it makes things so easy once it's there, I may take another whack at that.
Okay. So my other system's toolchain is up and built, but it was prebuilt, so I didn't have to figure out how to do a cross compile. I think I got something together and working with Crosstool for the 5500, but I have no idea if I used the right settings or not. (I'm guessing not.) Can anyone spare a moment to give me an idea of what I should compile and/or how to get a working cross compile going or where to find that info? I don't care if I use Crosstool or not as long as something works.
Ideally, I'll get Opie's SDK up and running with it, but one thing at a time!
Okay, so I need an old version of gcc, I need to compile for the ARM4 arch. Should I use the same kernel that my Z is running? What about things like glibc or linuxthreads or whatever?
Of course, if someone can explain to me why OE is so complicated to install, and why it makes things so easy once it's there, I may take another whack at that.
Pages: [1] 2