OESF Portal | OESF Forum | OESF Wiki | LinuxPDA | #planetgemini chat on matrix.org | #gemini-pda chat on Freenode | #zaurus and #alarmz chat on Freenode | ELSI (coming soon) | Ibiblio


Welcome Guest ( Log In | Register )

> How To Bring Up Wlan0 Via Command-line?
post Aug 9 2008, 06:26 PM
Post #1

Group: Members
Posts: 7
Joined: 9-October 07
Member No.: 20,805

Hi all,

I've got a Zaurus CL-3200, using AmbiCom WL1100C-CF PCMCIA wireless card.

I'm trying to bring up wlan0 via the command-line (yeah, there's a GUI tool to do it, but I'm curious). I can connect to the wireless AP at home (sometimes).

I see the card details in dmesg after I insert it into the slot and cardctl status lists the card at socket 0. It's in suspended mode. So far so good.

I'm assuming that to get the card up I need to unsuspend it. cardctl resume prints "ioctl(): Device or resource busy", but I'm assuming that's from the built-in microdrive, which is sitting at socket 1. cardctl resume 0 doesn't print anything and seems to succeed. cardctl status shows the card in a suspended state, however. Can anyone explain why this is so?

At this stage I still can't do anything wireless-related to the card as wlan0 still doesn't exist (it isn't reported by ifconfig). Ifconfig wlan0 up prints "SIOCSIFFLAGS: No such device".

Can someone fill me in?

Go to the top of the page
+Quote Post
Start new topic
post Aug 28 2008, 08:31 PM
Post #2

Group: Members
Posts: 447
Joined: 17-November 05
Member No.: 8,551

Sorry, I am busy with other things as well. It's been so long since I wrote the request for info that I have to go back and look.

Looks to me like I have to add a request that you include the command with it's output. I get way way disoriented by loose output when I do not see exactly what command(s) generated it.

I can say I know zilch (nothing) about wireless, all I know is how to reset ttyS3, and possibly ttyS0.

I think it best if we take this to email or some other way for me to get your debugging stuff as I'm not ready to do public debugging and also your output is impossible to view clearly or decipher in lynx, unless you want to post it online at the place freenode people post code, not finding it right now.

You will need others to help you with the association issue. Also, I do not understand what your issue is with qcop. qreset is dependant on the cardctl command, so it depends on whether the tty your wirely card uses.

If you want to use qreset to just reset ttyS3, you can start your actual connection however you want. qreset only resets, it does NOT start a connection.

I also don't like your not knowing what ROM you are using. How do you know it's sharp? search here for trisoft I think they have the ROMs if you want to flash to something more know.

or google for that whole line that has yasui in it and see if that turns up what rom it is. I'm out of lines to write on, but can't tell at this point what tty you use, and will let you research ROMs. PM your email addie to me if you want. Browser is not best mode for me to do debugging....I found the URL for long output if you want to try it, http://pastebin.ca, altho short output here is cool for me. What's nice about pastebin is it doesn't add html IIRC, haven't used it in a long time.

But, the problem I see is that one thing I have qreset doing is checking the /proc/ file system for a process using ttyS3, and your device doesn't show up in the system. I don't remember how essential that is, but there has to be a way to test whether there are any processes running using the CF slot. On my Collie ROM 2.38, it's easy...check /proc file system and output of "ps ax", but that won't work with some newer kernels. I can't even get the tty to show in /proc/ when I'm online on my Tosa ROM 1.12 using a CF modem right this moment!

You really should contact Barry (PM him) from the other thread...maybe his connection script would work for you from his 3100. It won't reset, but might help with the rest of your puzzle.

Some processes just mess with the PCMCIA tty's, like Opera, some chat clients, and efax, and maybe minicom IIRC. Do you use either/any of them? You might watch for a correlation of when you use them and when you have to do that messy dance trying to clear your ability to connect.

I find it annoying that the newer kernels do not display the PCMCIA tty in the proc system...haven't figured out how to find it there yet. This runs on Tosa for me, but I don't think I've needed to reset enough to be sure it can resolve the issues as well as it does on the Collie because of that /proc/ file system issue, and because Opera on my Tosa just doesn't do the damage there that it does on the Collie to my connectivity.


This post has been edited by sdjf: Aug 29 2008, 01:05 AM
Go to the top of the page
+Quote Post

Posts in this topic

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:


RSS Lo-Fi Version Time is now: 25th June 2018 - 02:19 AM