QUOTE(Jon_J @ May 23 2007, 03:25 PM)
It's cardctl1 listed in the script.
I have always booted with my CF card in pdaxrom, this must be why my microdrive is getting ejected when using my wifi card.
I'll refrain from booting with my CF card inserted from now on.
Doesn't anyone use WPA in pdaxrom??
Why not just copy the files from Cacko and use the configuration that cacko uses to enable WPA?
Or is this a kernel thing?
Jon, I don't know if this thread has died or not, but here's my two cents' worth.
I did get WPA working in pdaXii13 on a c3200 - once! I essentially did what you have described above, plus entering the card info in /etc/pcmcia/hostap_cs.cofig and /etc/pcmcia/hermes.config.
My use of the 3200 depends on having a good wi-fi scanner, to audit my networks. A program like Wellenreiter or kismet coupled with ethereal. I could not get either Wellenreiter or kismet to work properly on pdaXii13. There is something about the way they use the card that is incompatible with WPA, I guess. I believe they need to use "promiscuous mode" on the card so that they can listen to packets NOT addressed to the card doing the monitoring. Kismet even warns you upon exit that you may have to remove and re-insert you wifi card to use it again. I can live with that but I do need to return to WPA authentication when I'm done, without having to reboot!
In any event, I finally gave up and went back to Cacko. While I was experimenting with Cacko, I discovered pdaXQtrom
. This is an implementation of X that runs under a Sharp ROM (Including Cacko).By the Way! THANKS! to Meanie (menaie?) for providing all of those wonderfully illustrated and clearly explained pages on the ROMs for the clamshell series!
Back from my tangent, this seemed to be the answer for me. The programs run slower, which is to be expected given the extra layers of code, but the one almost fatal flaw for me is that a lot of the ethereal configuration screens are too long. Since they are pop-ups with no scrollbars, I can't get to the bottom third of the screen, and rotating the physical screen back and forth is not acceptable. Besides, being a junkie for fast computers, I decided to have another run at native pdaXii13.
Things have never been the same since. There must be some section of nonvolitale memory that gets changed by some of the flashing routines but not by others. Right now I am where you are - with pdaXii13 loaded but unusable without networking. I tried going back again to Cacko, but it won't boot. I restored the Sharp (Trisoft) NAND restore and HDD configuration and that works, but for some reason Cacko flashes OK but won't boot - it gets stuck in a loop trying to grep a file and won't get out of it.
I'm not sure what I am going to do next. I don't mind editing config files or even writing short scripts but I do need guidance.
During bootup, some (unknown to me) program checks the CF card, and somehow uses /etc/pcmcia/config. The manfid for our card is 0xd601, 0x0002. In my config file, there is a card called WF701 with the same manfid, but bound to the orinoco drivers. If I boot with the file "as-is", my card gets identified as the WF701, and nothing I do with editing config files, or using wifi-radar seems to help. I tried adding the hostap drivers following the pattern for the orinoco drivers at the top of the file, and commenting out the card name, replacing it with the string for the WL1100C:
card "AmbiCom", "WL1100C 802.11b CF-Card", "2.2"
manfid 0xd601, 0x0002
This yields a message about an unsupported card in socket 0 on boot! NOTHING works after that.
There is information about the card in several config files, but I'm not sure what role each plays. You can read more about my one successful attempt In this thread
- a feat I have been unable to duplicate
(I have since learned that I don't need to upload the card's RAM - the current version supports WPA)
So, Jon, if you or anyone else has any information to share abotu how to get this stuff working, I would be very grateful. I'd especially like to see some sort of description of what programs and files are used in the process of getting the wi-fi card up and running.