OESF Portables Forum

Model Specific Forums => Sharp Zaurus => Zaurus - pdaXrom => Topic started by: Laze on December 28, 2004, 09:43:25 am

Title: Hardware problems with pdaXrom..
Post by: Laze on December 28, 2004, 09:43:25 am
Do you have a piece of hardware thats not working under pdaXrom like a CF network card, USB controller etc?

Please post your cardctl ident and cardctl status and all other info you can find about the card (links to drivers etc.) - then we will try and fix them one at a time and try and make sure that pdaXrom supports as many accessories as possible.

We will probally be holding an IRC meeting with all user who are having problems with hardware but this is meant to be a warm up to see how many problems there are and how much time it will take to fix them.
Title: Hardware problems with pdaXrom..
Post by: w14 on December 28, 2004, 10:21:51 am
Laze,

There are a few people on these boards that use cheap and nasty Zonet ZCF1100 wireless cards, including me.

I added the following to /etc/pcmcia/hermes.conf to make it work:

card "Zonet ZCF1100"
  manfid 0x000b, 0x7100
  bind "orinoco_cs"

Cheers,

Mike.
Title: Hardware problems with pdaXrom..
Post by: ScottYelich on December 28, 2004, 10:23:18 am
Laze --

did you fix the cell modem that my friend has -- I think we sent you the info
before.  we/he said that we/he were willing to donate/pay $100 for this
card to work.  

Scott
Title: Hardware problems with pdaXrom..
Post by: sigmaX on December 28, 2004, 11:08:05 am
I already talked in irc to sashz and sent him an email with cardctl ident and info ... but anyway, in order to get also the info in here, I post:

CARD: Ambicom CF Bluetooth model BT2000CF

cardctl ident:

Socket 0:
  product info: "AmbiCom BT2000C", "Bluetooth PC/CF Card", "", ""
  manfid: 0x022d, 0x2000
  function: 2 (serial)
Socket 1:
  no product info available

cardctl info:

PRODID_1="AmbiCom BT2000C"
PRODID_2="Bluetooth PC/CF Card"
PRODID_3=""
PRODID_4=""
MANFID=022d,2000
FUNCID=2
PRODID_1=""
PRODID_2=""
PRODID_3=""
PRODID_4=""
MANFID=0000,0000
FUNCID=255
Title: Hardware problems with pdaXrom..
Post by: deniscallies on December 28, 2004, 04:44:03 pm
Hey
has somebody any experiences with the audiovox RTM 8000 and RC8?

Just  want it to call friends and surf over GPRS

Thanks

Denis
Title: Hardware problems with pdaXrom..
Post by: cnorwood19 on December 28, 2004, 06:08:20 pm
Quote
Hey
has somebody any experiences with the audiovox RTM 8000 and RC8?

Just  want it to call friends and surf over GPRS

Thanks

Denis
I just tried the instrutions here:

https://www.oesf.org/forums/inde...ic=1382&hl=gprs (https://www.oesf.org/forums/index.php?showtopic=1382&hl=gprs)

I had the bad vcc error at first, just like he/she did.

Then I downloaded the sample scripts and edited it for my provider, using vi

tried to connect, but had output of:

defining PDP context...
Connect script failed


So, since i really dont know anything but how to follow instructions, I am at a loss.



I think Laze said there would be a how-to with this card sometime after RC8 release. I guess we wait!
Title: Hardware problems with pdaXrom..
Post by: g33k on December 28, 2004, 06:44:05 pm
Since you've started a thread specifically for this purpose, I'll repost this stuff...

To enable the Symbol LA-4137 "Wireless Networker" wifi card, add the following lines to /etc/pcmcia/spectrum.conf:

Code: [Select]
card "LA4137 Spectrum24 CF WLAN CARD"
 manfid 0x014d, 0x0001
 bind "spectrum_cs"

For the TRENDnet TE-CF100 wired fast ethernet card, add the following lines to /etc/pcmcia/config:

Code: [Select]
card "TRENDnet TE-CF100"
 manfid 0x0149, 0xc1ab
 bind "pcnet_cs"

When I insert my RATOC CFU-1, "cardctl ident" returns

Code: [Select]
Socket 0:
  product info: "RACTOC",  "USB HOST CF+ Card"
  manfid: 0xc015, 0x0001
  function: 11  (ident)

"cardctl status" returns

Code: [Select]
Socket 0:
  3.3V 16-bit PC Card
  function 0: [ready]

Driver source code for the CFU-1 is here:
http://www.paipai.org/~humorum/zaurus/cfu1..._0.0.2-3.tar.gz (http://www.paipai.org/~humorum/zaurus/cfu1-driver_0.0.2-3.tar.gz)

C7x0/C860 patch for USB keyboard mappings:
http://www.paipai.org/~humorum/zaurus/usbk...lc-0.2.patch.gz (http://www.paipai.org/~humorum/zaurus/usbkbd-slc-0.2.patch.gz)
Title: Hardware problems with pdaXrom..
Post by: cs_jacky on December 28, 2004, 07:12:56 pm
Quote
Quote
Hey
has somebody any experiences with the audiovox RTM 8000 and RC8?

Just  want it to call friends and surf over GPRS

Thanks

Denis
I just tried the instrutions here:

https://www.oesf.org/forums/inde...ic=1382&hl=gprs (https://www.oesf.org/forums/index.php?showtopic=1382&hl=gprs)

I had the bad vcc error at first, just like he/she did.

Then I downloaded the sample scripts and edited it for my provider, using vi

tried to connect, but had output of:

defining PDP context...
Connect script failed


So, since i really dont know anything but how to follow instructions, I am at a loss.



I think Laze said there would be a how-to with this card sometime after RC8 release. I guess we wait!
The card works. After follow the instruction in the thread, run the following commands:Connect to GPRS. It works.

Jacky
Title: Hardware problems with pdaXrom..
Post by: cnorwood19 on December 28, 2004, 07:31:57 pm
My card is ready, and the cardctl suspend then resume doesnt work.

When dialing I get, /usr/sbin/ppd: unrecongnized option"

and cardctl config gives me Vcc and a large string of #s

Ill just redo the whole process to make sure everythink is right.

Good to know it is working for others!
Title: Hardware problems with pdaXrom..
Post by: Vanguard on December 29, 2004, 07:45:33 am
How about the pocketop IR keyboard?

What can I do to help someone get some working drivers going?
Title: Hardware problems with pdaXrom..
Post by: mike151 on December 29, 2004, 01:33:30 pm
Hi,

I have an 'Eagletec' CF wireless card that is partially working
# cardctl info
PRODID_1="Wireless"
PRODID_2="LAN Adapter"
PRODID_3="Version 01.02"
PRODID_4=""
MANFID=0156,0002
FUNCTID=6
PRODID_1=""
PRODID_2=""
PRODID_3=""
PRODID_4=""
MANFID=0000,0000
FUNCIF=255

# iwconfig eth0
shows proper ESSID, Mode, Frequency and Encryption Key.

# ifconfig eth0
shows proper static ip and dns data

# route -vn
shows my liksys AP ip address as the gateway

ping my C860 by its fixed IP address is ok

Everything seems perfect, BUT...

ping my AP or other PCs in my home network losses all packages.

What could be wrong here?

Thanks!

Mike
Title: Hardware problems with pdaXrom..
Post by: Martin on December 29, 2004, 06:19:00 pm
Problem with Netgear MA701 Wireless 802.11b CF card

thx to pdaXrom team for great work on RC8

Martin

===================================================================

OUTPUT: cardctl ident
---------------------

Socket 0:
  product info: "NETGEAR", "MA701 Wireless CF Card", ""
  manfid: 0xd601, 0x0002
  function: 6 (network)
Socket 1:
  no product info available
===================================================================

OUTPUT: cardctl status
----------------------

Socket 0:
  3.3V 16-bit PC Card [suspended]
Socket 1:
  no card

===================================================================

NETGEAR MA701 Wireless CF Card 802.11b

MANID / PRODID : d601 / 0002

===================================================================

Recognized by CF/SD Card applet as

Ambicom WL1100C 11Mbs Card 802.11b
...

===================================================================

OUTPUT: cardctl info
--------------------

PRODID_1="NETGEAR"
PRODID_2="MA701 Wireless CF Card"
PRODID_3=""
PRODID_4=""
MANFID=d601,0002
FUNCID=6
PRODID_1=""
PRODID_2=""
PRODID_3=""
PRODID_4=""
MANFID=0000,0000
FUNCID=255

===================================================================
Title: Hardware problems with pdaXrom..
Post by: Laze on December 30, 2004, 05:19:02 am
Martin what is the problem - tried updating as described in the Kathrin RC8 is out and please try setting the wireless options in wireless config tool. It should work with your card,
Title: Hardware problems with pdaXrom..
Post by: webslngr on December 30, 2004, 02:02:31 pm
another CF Lan card to add to the list:
Hawking 10/100 CF Fast Ethernet
I got it working by adding the following to the /etc/pcmcia/config
Code: [Select]
card "Fast Ethernet"
 manfid 0x0149, 0xc1ab
 bind "pcnet_cs"
Thanks for all the hard work on the rom!
--webslngr
Title: Hardware problems with pdaXrom..
Post by: jasonakay on December 31, 2004, 06:31:43 pm
My Billionton CFLA-100N 10/100 FastEthernet Compact Flash LAN Adapter doesn't work 'out of the box'.

I add the following to /etc/pcmcia/config:

Code: [Select]
card "Billionton CFLA-100N 10/100 FastEthernet"
 version "CF", "100Base-Ethernet", "V", "1.0"
 manfid 0x021b, 0x0202
 bind "pcnet_cs"

Thanks!  You guys are doing a FANTASTIC job of pdaXrom!!    

Jason.
Title: Hardware problems with pdaXrom..
Post by: shula on January 01, 2005, 07:48:38 am
it's *not exactly* a hardware problem, but IMHO it kind of fits here:

SYNC on SD card issue:

after writing files to my SD card, i plugged it in the desktop, and NADA: file is not there.  returned the SD to the zaurus, and the file IS there.

it's probably a "sync/cache" issue.
the workaround is to run "sync" before i take out the card from the Z.
 
this behaviour didnt exist on my previous rom (cacko 1.21b)
Title: Hardware problems with pdaXrom..
Post by: rgrep on January 01, 2005, 10:11:16 pm
You are unmounting the card before you remove it, right?   You could test whether it's a problem with the eject applet by typing 'mount' in a terminal after telling the applet to eject it.  If you see it still listed as mounted then some process may still be using the card.   You can eject it manually by typing '/etc/sdcontrol eject' but you will still get the "device is busy" error if a process has a file open on your card.  To find out which processes are using your card just type:
Code: [Select]
fuser -vm /mnt/cardor to see more of each process's command line:
Code: [Select]
ps | grep $(fuser -m /mnt/card | tr -s " " | sed 's/ / -e /g' | cut -d" " -f2-)Matt
Title: Hardware problems with pdaXrom..
Post by: rgrep on January 01, 2005, 10:20:31 pm
If you mount filesystems from your SD card through the loopback device (e.g. cramfs filesystems like the SDK) then even after unmounting them you still won't be able to eject your card ("umount /mnt/card: device is busy"), and "fuser -m /mnt/card" won't list any processes.  If you type "ps | grep loop" you'll see a line like this:
Code: [Select]
15368 root            SW< [loop0]To unlink the loop device just type:
Code: [Select]
losetup -d /dev/loop0Do that for each loop device listed in the ps output.  The umount command is actually supposed to do this for you when you unmount a loopbacked filesystem but for some reason the pdaXrom version doesn't.
Title: Hardware problems with pdaXrom..
Post by: shula on January 02, 2005, 10:27:36 am
no, i'm too lazy to umount it.
usually i just wait 3-5 seconds after file op is finished, and i eject the card.
as i noted before, it wokred in cacko without the need to umount (which is what i call "real hot-swap" ;-))

thanks for your advices.
Title: Hardware problems with pdaXrom..
Post by: rgrep on January 02, 2005, 01:16:59 pm
I wouldn't call it a bug if you're doing something no one would ever recommend.   pdaXrom has synchronous I/O disabled in the kernel (CONFIG_FS_SYNC), do you know if Cacko 1.21b does as well?  If not then that would explain why you're able to remove the card after such a short time without doing a manual sync.
Title: Hardware problems with pdaXrom..
Post by: sigmaX on January 02, 2005, 09:56:48 pm
I installed SAMBA server (2.2.9) and now when rebooting, I am getting the following error repeated on the output screen:

eth0: Error -110 writing Tx descriptor to BAP

I disconnect the Orinocco based wifi card and it stops...

I get login and log in uneventfully. I can Plug again the card, and I got internet access...

but NO SAMBA SHARES...

I found this link:

http://www.uwsg.iu.edu/hypermail/linux/ker...412.1/0329.html (http://www.uwsg.iu.edu/hypermail/linux/kernel/0412.1/0329.html)

Which talks about same error ... is this MY problem or is it some kind of incompatibility / inconsistency between Kernel and compiled samba version AND orinocco cards ?

Regards
Title: Hardware problems with pdaXrom..
Post by: jasonakay on January 03, 2005, 02:48:07 pm
I have a GlobalSat BC-307 Compact Flash GPS receiver that doesn't work 'out of the box'.

I add the following to /etc/pcmcia/config:

Code: [Select]
card "GlobalSat BC-307 GPS"
  manfid 0x0279, 0x950b
  bind "serial_cs"

Thanks!!

Jason.
Title: Hardware problems with pdaXrom..
Post by: ScottYelich on January 03, 2005, 10:57:34 pm
Quote
no, i'm too lazy to umount it.
usually i just wait 3-5 seconds after file op is finished, and i eject the card.
as i noted before, it wokred in cacko without the need to umount (which is what i call "real hot-swap" ;-))

thanks for your advices.

hehe... my battery on my laptop gives me 0 seconds... so my shutdown
for freebsd was "sync;sync" and pull the power.  I never had any
corruption :->

Scott
Title: Hardware problems with pdaXrom..
Post by: nightfire on January 05, 2005, 01:47:38 am
I think the socketcom firmware in the spectrum24 driver is old.. my locally compiled driver works ok (under my own kernel), but the one with 1.1.0-rc8 seems to overdrive the antenna or something.  Oddly, cupping my hand over the antenna seems to improve the signal quality.   Quite strange.

Anyway, I attached my spectrum_fw.h generated from the latest firmware on Socket's web site.  Can you check if it differs, and if so, recompile the driver against rc8's kernel?  Alternatively, could you post your kernel source?

Thanks!
Title: Hardware problems with pdaXrom..
Post by: nightfire on January 05, 2005, 01:53:46 am
Also, in case my patch was corrupted by the description field on bug ID 245, here's a binary.
Title: Hardware problems with pdaXrom..
Post by: gene on January 27, 2005, 09:56:13 pm
Guys,

I know it listed as fixed for RC8, but it isn't working for me. That is revision B of Socket 6004 card.

I added the following entry in /etc/pcmcia/spectrum.com:

Code: [Select]
card "Socket Communications CF+ LP WLAN Card Rev B"
  manfid 0x0156, 0x0003
  bind "spectrum_cs"

Now it appears like its tyring to work and dmesg spits out the following:

Code: [Select]
spectrum_cs.c 0.4.2 (Pavel Roskin and others)
orinoco_lock() called with hw_unavailable (dev=c346c000)
orinoco_lock() called with hw_unavailable (dev=c346c000)
spectrum_cs: primary firmware download failed
spectrum_cs: firmware download failed
eth0: Station identity 0015:0002:0001:000a
eth0: Looks like an Intersil firmware version 1.10.2
eth0: Ad-hoc demo mode supported
eth0: IEEE standard IBSS ad-hoc mode supported
eth0: WEP supported, 104-bit key
eth0: failed to read MAC address!
spectrum_cs: register_netdev() failed


Any and all help would be more than welcome and very much appreciated!!!
Title: Hardware problems with pdaXrom..
Post by: Mickeyl on January 28, 2005, 06:32:39 am
6004 B is not a prism2.5 card, there's no way you will get spectrum_cs work with it.
It's based on Agere HERMES II design. Someone added their drivers to OE, so you could try to build and run these.
Title: Hardware problems with pdaXrom..
Post by: samxiao on January 29, 2005, 08:48:17 am
anyone brings Pocketop keyboard works in X11 ROM?
Title: Hardware problems with pdaXrom..
Post by: Re@lity on February 08, 2005, 11:01:34 am
Senao NL-2511 CF Mercury (prism3 card afaik)

Cardctl:

Socket 0:

product info: "wlan", "11Mbps_PC_Card_3.0", "ISL37100P", "Eval-RevA"

manfid: 0x000b, 0x7100

function: 6 (network)


It would be great to get this card running with the HostAP drivers, preferably!
I'm new here, so please forgive if this has been covered already! (a link would be nice though, in that case!)
Title: Hardware problems with pdaXrom..
Post by: AlexBeaudion on February 24, 2005, 12:24:05 pm
My linksys PKW-WCF12 has a problem, I have no issues connecting to a 802.11b base station, but as soon as I try to connect to a 802.11g station the card refuses to connect (even at .b speeds), other cards in laptops and the like have no problems at all.

Am I using the correct drivers? does anyone else have this problem?? Any quick fixes??

Thx,
  Alex

The error that I get is:
cardmgr[130]: socket 0: Linksys CompatfFlash Wireless Card
cardmgr[130]: executing: './hermes start eth0 2>&1'
cardmgr[130]: + Error for wireless request "Set Frequency" (8B04) :
cardmgr[130]: +    SET failed on device eth0 ; Operation not supported.
or
cardmgr[130]: socket 0: Linksys CompatfFlash Wireless Card
cardmgr[130]: executing: './hermes start eth0 2>&1'
cardmgr[130]: + Error for wireless request "Set Frequency" (8B04) :
cardmgr[130]: +    SET failed on device eth0 ; Invalid argument.
(depending on mood it seems)

cardctl ident:
Socket 0:
product info: "Linksys", "Wireless CompactFlash Card", "", ""
manfid: 0x028a, 0x0673
function: 6 (network)
Socket 1:
no product info available

cardctl info:
PRODID_1="Linksys"
PRODID_2="Wireless CompactFlash Card"
PRODID_3=""
PRODID_4=""
MANFID=028a,0673
FUNCID=2
PRODID_1=""
PRODID_2=""
PRODID_3=""
PRODID_4=""
MANFID=0000,0000
FUNCID=255

lsmod:
orinco_cs
orinco
hermes
pxa_bi
storage_fd
usbdcore
usbdmonitor
sharp_mmcsd_m
Title: Hardware problems with pdaXrom..
Post by: rgrep on February 24, 2005, 10:54:54 pm
Quote
My linksys PKW-WCF12 has a problem, I have no issues connecting to a 802.11b base station, but as soon as I try to connect to a 802.11g station the card refuses to connect (even at .b speeds), other cards in laptops and the like have no problems at all.

Am I using the correct drivers? does anyone else have this problem?? Any quick fixes??

Hi Alex,

You could try changing drivers from orinoco to hostap.  I also have a Linksys WCF12 and have noticed my card behaves much better under hostap.  See this post (https://www.oesf.org/forums/index.php?showtopic=7151&view=findpost&p=44759) for instructions on changing drivers.

Hope this helps.

Matt
Title: Hardware problems with pdaXrom..
Post by: wowo123 on March 03, 2005, 07:41:26 am
I would like to use my Belkin-BT-Card F8T020, which works great with cacko-ROM.
With pdaxrom it is't recognized.
It says:

product info: "CF CARD", "GENERIC", "", ""
manfid:  0x0279, 0x950b
function: 2 (serial)

Would be nice to have it with pdaxrom too.
Title: Hardware problems with pdaXrom..
Post by: Wolfie_Fox on March 11, 2005, 06:16:57 pm
I found that after re flashing from RC8 to RC9 that my Bluetooth card stopped working, I don't remember the exact problem as I am back on RC8 now, also every time I try to put my Zaurus into standby with the Bluetooth card in the PDA just crashes and I end up having to take the battery out to restart it

(Had to edit this as I forgot to mention my Bluetooth card make...)
It is a Armadillo Bluetooth CF Card V1.1. Model no: LSE039/4 R1D Type: LSE039

Thaks all I know about my BT card  

That's one problem I'm having...

The other is with the USB data cable, when I set the USB settings so it will let my comp access the SD slot I keep getting my comp telling me that even when I have a card in the SD slot it says "There is no disk in the drive" The Zaurus shows up in My Computer as a new removable drive but it just will not work. It has never worked since the feature was added. Do I need to install some special driver for my Zaurus on to my comp which runs XP Pro SP 2 instead of it using the generic driver that XP installs the second you connect the Z for the first time?

Apart from that I'm really happy with RC8, don't know about RC9 as I used it for only 10 mins before going back to 8, waiting for RC10 now

One more thing that probably isn't related to the OS but... then I install the WiFi scanner from the IPK feed it doesn't give me an icon anywhere to let me use the program and I have no idea where it is installed, I have that prob with a few of the programs that I install.

One last thing... The PPP thing for accessing the internet only lets me dial a phone number, it there not a way I can get my Z to connect to my phone and connect to the internet via GPRS so that I don't have to pay for the duration that I am online, just pay for the amount of data transferred.

Thanks in advance
Title: Hardware problems with pdaXrom..
Post by: omega on June 03, 2005, 04:02:11 am
Wolfie_FOX, regarding gprs... It is the same settings for ppp to use gprs over ir to phone you just put in a different dialing number... it's like #99 or something...
Title: Hardware problems with pdaXrom..
Post by: azalin on June 13, 2005, 08:01:53 am
I hope this is the right thread to post in, but I think this is some nice info on getting support for the only 802.11g network card currently on the market (this is nice so hotspots won't get slower because a 802.11b card connects or on hotspots which are 802.11g (+WPA or WEP) exclusively).

Card name: Linksys WCF54G Wireless Compact Flash
Chipset: likely the Hermes II.5 chip (WL60040) (or possibly Hermes II chip (WL60010)?)
Drivers source: http://www.agere.com/mobility/wireless_lan_drivers.html (http://www.agere.com/mobility/wireless_lan_drivers.html)
(Pick the 7.22 version drivers, does not support older chips anymore but it reportedly supports this chip).
Review of the card: http://www.tomsnetworking.com/Reviews-177-ProdID-WCF54G.php (http://www.tomsnetworking.com/Reviews-177-ProdID-WCF54G.php)
Possible problems: Driver is kernel 2.4 only, driver reportedly (http://www.linuxdevices.com/cgi-bin/board/UltraBoard.pl?Action=ShowPost&Board=linuxpda&Post=327&Idle=0&Sort=0&Order=Descend&Page=0&Session=)
works on x86, so far only a report of crashes on Xscale (Zaurus Cacko).
Driver download extras: HCF directory contains firmware images to allow the card to operate in either station (STA) or Access Point (AP) mode.

Check also the following threads (I tried to make a summary of the info in this post).
https://www.oesf.org/forums/index.php?showtopic=11082&st=15 (https://www.oesf.org/forums/index.php?showtopic=11082&st=15)
https://www.oesf.org/forums/index.php?showtopic=8469 (https://www.oesf.org/forums/index.php?showtopic=8469)
Title: Hardware problems with pdaXrom..
Post by: Quino on August 08, 2005, 04:17:07 pm
There is a popular wireless CF card which isn't supported by pdaXrom, at least, I thought it was very popular and therefore I bought it.

SMC2642 EZ Connect 2642W

This card is recognized either as "anonymus memory" or as Sandisk connect SDWCFB-000".

#cardctl info
PRODID_1 = "  "          (yes one space)
PRODID_2 = "SMC2642W 11Mbps Wireless CF Card"
PRODID_3 = ""
PRODID_4 = ""
MANFID=d601, 0005
FUNCID=6

#cardctl ident 0
Product info: " ", "SMC2642W 11Mbps Wireless CF Card", ""
manfid: 0x601, 0x0005
function: 6(network)

Other ROMS support this card according what I read in these forums. Would you add support to this card?. I tried all kind of configurations in the /etc/pcmcia files, but now I'm clueless.
Title: Hardware problems with pdaXrom..
Post by: sandmansandine on August 23, 2005, 12:01:02 am
I'm having a really hard time with my Planex GW-CF11X, can't find anything that'll do the trick

SL-C1000
PDAxRoom 10.4
Planex GW-CF11X
Title: Hardware problems with pdaXrom..
Post by: miskinis on September 04, 2005, 12:44:29 pm
SL-6000 - builtin MIC does not work, bundled oss mixer won't even start
Title: Hardware problems with pdaXrom..
Post by: adf on September 04, 2005, 02:49:29 pm
6000 (probably other too for some of this)

USB keyboard map incomplete--no punctuation, that sort of thing

IR Keyboard Belkin f8u1500 Doesn't work

Sharp CF camera

Maybe publish a list of usb Bluetooth dongles? I have one that doesn't work, but it might be easier just to find ones that do.

USB GPS?? I don't have one atm, but I haven't seen reports of their use (could be me).

USB cameras via V4L support in the kernel?

On the 6k
Power button doesn't suspend
ctrl/alt does nothing
"special keys" Mail home menu, etc do nothing
Record button does nothing.
Suspend/resume while wireless is on brings back a "dead" connection (light is on , no data will transfer)

And.. something that doesn't work on any rom that I have seen, but seems wanted: 2gig sd... or at least 2 gig mmc (which I think hasn't been tested)
Title: Hardware problems with pdaXrom..
Post by: dominate on September 27, 2005, 07:23:48 pm
hi all.... just running pdaxrom after playing around with the sharp rom and openzaurus opie and gpe distros for a while.... i can't believe how sweet pdaXrom is!  exactly what i want!

anyway, back on topic... i have the ambicom wl1100c-cf wireless card... it works very sporadically in pdaXrom, although always worked perfectly in the others... what am i missing?  it has worked for me a couple times, but even then droped and reconnected quite a bit.  Other times, i can't even get it to connect to my network.

I've read a bunch of the discussion on using hostap drivers, but i'm confused... i don't have ANY wireless drivers in lsmod (at least when it's not working), and only a couple even installed in the modules directory, so i'm assuming most are built in.  also, my card shows up as eth0 not wlan0.  

What am i missing?

thanks!
ken
Title: Hardware problems with pdaXrom..
Post by: Hrw on September 28, 2005, 08:17:45 am
Quote
There are a few people on these boards that use cheap and nasty Zonet ZCF1100 wireless cards, including me.

I added the following to /etc/pcmcia/hermes.conf to make it work:

card "Zonet ZCF1100"
  manfid 0x000b, 0x7100
  bind "orinoco_cs"
[div align=\"right\"][a href=\"index.php?act=findpost&pid=59346\"][{POST_SNAPBACK}][/a][/div]

That card has few other names (atleast manfid says so). In OpenZaurus they are handled by hostap_cs:
Code: [Select]
card "SonicWALL Long Range Wireless Card"
   version "SonicWALL", "Long Range Wireless Card", "ISL37100P", "1.0"
   manfid 0x000b, 0x7100
   bind "hostap_cs"

card "Senao NL-2011CD PLUS Ext2 Mercury"
   version "WLAN", "11Mbps_PC-Card_3.0", "ISL37100P", "Eval-RevA"
   manfid 0x000b, 0x7100
   bind "hostap_cs"

card "Senao/Origo 80211b WLAN Card"
   manfid 0x000b,0x7100
   bind "hostap_cs"
Title: Hardware problems with pdaXrom..
Post by: Hrw on September 28, 2005, 08:26:11 am
Quote
I have an 'Eagletec' CF wireless card that is partially working
# cardctl info
PRODID_1="Wireless"
PRODID_2="LAN Adapter"
PRODID_3="Version 01.02"
PRODID_4=""
MANFID=0156,0002

[div align=\"right\"][a href=\"index.php?act=findpost&pid=59567\"][{POST_SNAPBACK}][/a][/div]

It's prism2 based card - use hostap_cs or orinoco_cs for it. It was released by many manufacturers and IIRC it is based on Intersil reference card.
Title: Hardware problems with pdaXrom..
Post by: Hrw on September 28, 2005, 02:10:34 pm
Quote
Socket 0:
  product info: "AmbiCom BT2000C", "Bluetooth PC/CF Card", "", ""
  manfid: 0x022d, 0x2000
  function: 2 (serial)

[div align=\"right\"][a href=\"index.php?act=findpost&pid=59355\"][{POST_SNAPBACK}][/a][/div]

Add that into /etc/pcmcia/config:
Code: [Select]
card "AmbiCom BT2000C Bluetooth PC/CF Card"
  version "AmbiCom BT2000C", "Bluetooth PC/CF Card"
  bind "serial_cs" class "bluetooth"

thats how it is setup in OZ - I dont know does it works or not.
Title: Hardware problems with pdaXrom..
Post by: trichmon on September 28, 2005, 03:10:42 pm
apmsleep does not seem to work correctly on the 6000.  It suspends but does not resume.  Cant seem to right click (even after reading other threads).  Windows still open like they are on a clamshell (have not looked for a fix).  

Wireless works like rc10, it *seems* faster to me, even firefox seems to open faster.  All in all a fairly large step in stability and speed.  If apmsleep worked and I could script up alarms, pdaxrom would be 100% usable for me.

Great Job!!
Title: Hardware problems with pdaXrom..
Post by: YOSSIE on October 04, 2005, 10:36:14 am
wlan-ng ipk in feed of rc11 (http://212.10.30.205/rc11/Zaurus-C1000-C3100/feed/wlan-ng_0.2.1-pre26-1_armv5tel.ipk) does not seem to contain prism2_cs.o.

I am going to use PLANEX GW-CF11X on C1000 and rc11. How can I use this card on rc11?
Title: Hardware problems with pdaXrom..
Post by: Hrw on October 04, 2005, 10:58:41 am
yossie: with hostap maybe? Atleast this is what I will try for prism2 cards.
Title: Hardware problems with pdaXrom..
Post by: sleepy on October 11, 2005, 01:59:22 am
I apologize for the somewhat redundant post in the "rc 12" topic but this topic seemed more suitable...

Anyhow, I'm using rc12 with a C1000 and while a USB mouse works fine trying to use a USB keyboard is a no-go. Switching USB function to "serial" causes the built-in keyboard to stop working (touch screen works fine) and no keypresses from the USB keyboard are registered. Unplugging the keyboard and switching the USB function back to "storage" freezes up the system.

I've tried both a Fellowes "stowaway keyboard" as well as a standard mac usb keyboard.

Any ideas?
Title: Hardware problems with pdaXrom..
Post by: MONVMENTVM on October 13, 2005, 09:57:03 am
how do you use the usb mouse? i just plugged it in but nothing happens... dmesg says something about usb device not activated.

using rc12 on c3100
Title: Hardware problems with pdaXrom..
Post by: sleepy on October 13, 2005, 06:24:38 pm
Quote
how do you use the usb mouse? i just plugged it in but nothing happens... dmesg says something about usb device not activated.

using rc12 on c3100
[div align=\"right\"][a href=\"index.php?act=findpost&pid=99183\"][{POST_SNAPBACK}][/a][/div]

I just plugged it in and dmesg picks it up properly. After that I open up the "USB Function" app and switch to "serial" mode and it just works. I don't know if it matters but this is with a Kensington Orbit two button trackball.

I'm also using a C1000 so perhaps this is C3100 specific. Did you upgrade from rc11 or was this a freshly flashed rc12?
Title: Hardware problems with pdaXrom..
Post by: MONVMENTVM on October 14, 2005, 01:26:52 am
was a fresh rc12. there shouldnt be any difference between the c3100 and the c1000... if you look rc12 is the same rom for both devices.

do you have /proc/bus/usb ? i saw that some usb functions need it (lsusb needs it... and also usbh!). but i dont have it.

i also tested with the DM-menu. under "test mouse" it said to connect the mouse (which i did); then the lights of the mouse appeared and it said that the mouse is ok and working... so the hardware should be ok. i think that i dont have some files...

i also plugged in a card reader... but nothing happens.

dmesg says the following (just the things wich sound interesting for me):
pxa_sd_wait_id_response: responce time out (cmd=01 MMC_STAT=0x2142)
//this line is written very often... about 20 to 30 times
SD Driver Initialized.
sharp_mmcsd 0.30 13 Oct 2004
pxa_sd_wait_id_response: responce time out (cmd=52 MMC_STAT=0x2142)
pxa_sd_wait_id_response: responce time out (cmd=05 MMC_STAT=0x2142)
pxa_sd_wait_id_response: responce time out (cmd=55 MMC_STAT=0x2142)
pxa_sd_wait_id_response: responce time out (cmd=41 MMC_STAT=0x2142)
[SD]-clustersize = 800
.....
...
Trying to free nonexistent resource <f7000000-f700000f>
...
...
usbh: udc_connected: ACTIVE_LOW: 0<7>usbh: monitor_conected: 0
usbh: monitor_unload: 0
usbh: monitor_hotplug: agend: usbh interface: monitor action: unload
usbh: monitor_request_irq: 41 71
usbh: monitor_modinit: finished
usbdm: usbd_monitor 0.3 035 2002-06-12 20:00
monitor_connected: 1
monitor_load:
monitor_hotplug: agent: usbd interface: monitor action: load
usbh: udc_connected: ACTIVE_LOW: 0<7>usbh: monitor_connected: 0
usbh: monitor_unload: 4
usbdcore: usbdcore 0.1 blablablabla (dbg=" ")
bi_modinit: call udc_startup_events
bi_device_event: call udc_enable
bi_device_event: call udc_all_interrupts
udc_connect: usb-device is not active.
monitor_modinit: finished
...
...
start check battery !
mice: PS/2 mouse device common for all mice
Title: Hardware problems with pdaXrom..
Post by: desertrat on October 16, 2005, 04:17:12 am
Quote
anyway, back on topic... i have the ambicom wl1100c-cf wireless card... it works very sporadically in pdaXrom, although always worked perfectly in the others... what am i missing?  it has worked for me a couple times, but even then droped and reconnected quite a bit.  Other times, i can't even get it to connect to my network.
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=97311\")

I'm using the same card on a C3100. It seems to die after a certain amount of activity. IE if I have it connected but leave the connection idle all is well -- but not very useful

When I start downloading files or browsing the web etc, then after a random number of bytes (or number of seconds?) the connection dies and I start getting these errors on dmesg:

Code: [Select]
eth0: Error -110 writing Tx descriptor to BAP
When this happens the following usually brings the card back up:

Code: [Select]
cardctl eject 0
cardctl insert 0

And I have to keep doing this everytime the connection dies

I have also tried using the hostap driver as per this post:

[a href=\"https://www.oesf.org/forums/index.php?showtopic=7151&st=0&p=44759&#entry44759]https://www.oesf.org/forums/index.php?showt...759&#entry44759[/url]

But evidently the hostap drive isn't available because I get this error:

Code: [Select]
module /lib/modules/2.4.20/pcmcia/hostap_cs.o not available

This is the major stumbling block which prevents me from using pdaXrom. Any help appreciated


cheers
-- desert rat
Title: Hardware problems with pdaXrom..
Post by: agraef on October 18, 2005, 05:46:50 am
Quote
Quote
anyway, back on topic... i have the ambicom wl1100c-cf wireless card... it works very sporadically in pdaXrom, although always worked perfectly in the others... what am i missing?  it has worked for me a couple times, but even then droped and reconnected quite a bit.  Other times, i can't even get it to connect to my network.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=97311\"][{POST_SNAPBACK}][/a][/div]

I'm using the same card on a C3100. It seems to die after a certain amount of activity. IE if I have it connected but leave the connection idle all is well -- but not very useful

Yup, same over here, running RC12 on an Akita with a D-Link DCF-660W. Transfer from network to Zaurus works ok, but the uplink is totally broken, locks up whenever transferring a larger file from the Z to the network. Sometimes the driver locks up so badly that the card can't be reinitialized with the cardctl eject/insert trick, and even reboot won't work so that I have to reset the device.

Have others fallen victim to the same bug? Maybe it's an RC12 issue? The D-Link DCF-660W is a fairly common card, supported by almost any Zaurus OS including the venerable Sharp ROM.

BTW, the hermes.conf file also lacks an entry for the DCF-660W, so it's recognized as a "Sandisk Connect SDWCFB-000" instead. Here's the entry that I use now, can someone please confirm that I'm using the correct module?

Code: [Select]
card "D-Link DCF-660W"
  version "D-Link", "DCF-660W"
  manfid 0xd601,0x0005
  bind "orinoco_cs"
Title: Hardware problems with pdaXrom..
Post by: Hrw on October 18, 2005, 05:56:13 am
agraef: use hostap-modules instead of orinoco for that card.

most of Prism2 cards works better with hostap_cs then with orinoco_cs driver.
Title: Hardware problems with pdaXrom..
Post by: agraef on October 18, 2005, 07:53:23 am
Quote
agraef: use hostap-modules instead of orinoco for that card.

Yes but how? Correct me if I'm wrong but the hostap modules don't seem to be supported on pdaXrom?

Just to make sure, I just tried the card on Oz and it works perfectly (using hostap-modules, of course), so it's not a hardware issue. And it's not RC12-specific either, RC11 exhibits the same symptoms.
Title: Hardware problems with pdaXrom..
Post by: Hrw on October 18, 2005, 09:05:56 am
oops. I was thinking that pdaX provide hostap-modules.
Title: Hardware problems with pdaXrom..
Post by: agraef on October 18, 2005, 09:29:35 am
Quote
oops. I was thinking that pdaX provide hostap-modules.
Well, at least not out of the box and not in the regular feeds. But I'll try to see whether I can get one of the older hostap packages someone posted in another thread to work.

EDIT: Bad luck, RC12 comes with kernel 2.4.20, but all those older packages are for RC10 and the 2.4.18 kernel.

EDIT#2: I found that this apparently only affects the C1K/C3100 release (based on kernel 2.4.20). At least with RC11+12 for the C1000/C3100, most of the wlan drivers (hermes, orinoco etc.) are not built as separate modules, but are compiled into the kernel, and the hostap modules are just missing. So I had to build my own, see here (https://www.oesf.org/forums/index.php?showtopic=15608&view=findpost&p=101297) for a tarball with the binaries.
Title: Hardware problems with pdaXrom..
Post by: Cagilaba on November 05, 2005, 06:15:30 am
Quote
Anyhow, I'm using rc12 with a C1000 and while a USB mouse works fine trying to use a USB keyboard is a no-go.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=98913\"][{POST_SNAPBACK}][/a][/div]
Anyone got the Fellowes Stowaway keyboard working yet? USB mouse worked automatically for me too, but when I plug in the keyboard the keymapping is completely random.  

If the external keyboard could work properly with pdaXrom, it would be a killer combination -- did it work previously in pdaX? or do we need to wait for the next rc to have this feature?

thanks
Title: Hardware problems with pdaXrom..
Post by: ajnk on November 23, 2005, 05:19:58 am
I have just bought a Belkin F8T020 Bluetooth card, I saw reports of it working on OZ, so presumed it would work on pdaxrom.  I did see an earlier post about this card, but no solution.

# cardctl ident
Socket 0:
  product info: "CF CARD", "GENERIC", "", ""
  manfid: 0x0279, 0x950b
  function: 2 (serial)
Socket 1:
  no product info available

# cardctl info
PRODID_1="CF CARD"
PRODID_2="GENERIC"
PRODID_3=""
PRODID_4=""
MANFID=0279,950b
FUNCID=2
PRODID_1=""
PRODID_2=""
PRODID_3=""
PRODID_4=""
MANFID=0000,0000
FUNCID=255

I added an entry to to /etc/pcmcia/config


card "Belkin F8T020 Bluetooth Adapter"
  manfid 0x0279, 0x950b
  bind "serial_cs"

but the card is still seen as GENERIC, I also added the same entry to /etc/pcmcia/bluetooth.conf

and finally :-

# cat /var/lib/pcmcia/stab
Socket 0: Belkin F8T020 Bluetooth Adapter
0       serial  serial_cs       0       ttyS3   4       67
Socket 1: empty

Can anyone out there help ?

I have a C860 running RC12 BTW.
Title: Hardware problems with pdaXrom..
Post by: Hrw on November 23, 2005, 06:28:22 am
ajnk: if it wont work with serial_cs then you can try bt950_cs driver (but I dont know how pdaX devels resolved bt950 cards support)
Title: Hardware problems with pdaXrom..
Post by: cjb on November 25, 2005, 09:42:14 am
Hi,

I had problems with my Socket Low Power WLAN card using rc10 and rc12 on my SL-C1000. It would work fine as a normal WiFi, but would not go into monitor mode for some Kismet action. I ended up recompiling the tetsu kernel, taking out the compiled in hermes chipset driver and compiling some modules from the latest source of the drivers.

I just had to do it again when upgrading from rc10 to rc12, so I put down a bit more detail on what I did here (http://www.neonbox.org/zaurus/index.html).

HTH
Title: Hardware problems with pdaXrom..
Post by: Dima202 on December 03, 2005, 10:54:25 pm
Quote
I have just bought a Belkin F8T020 Bluetooth card, I saw reports of it working on OZ, so presumed it would work on pdaxrom.  I did see an earlier post about this card, but no solution.

# cardctl ident
Socket 0:
  product info: "CF CARD", "GENERIC", "", ""
  manfid: 0x0279, 0x950b
  function: 2 (serial)
Socket 1:
  no product info available

# cardctl info
PRODID_1="CF CARD"
PRODID_2="GENERIC"
PRODID_3=""
PRODID_4=""
MANFID=0279,950b
FUNCID=2
PRODID_1=""
PRODID_2=""
PRODID_3=""
PRODID_4=""
MANFID=0000,0000
FUNCID=255

I added an entry to to /etc/pcmcia/config


card "Belkin F8T020 Bluetooth Adapter"
  manfid 0x0279, 0x950b
  bind "serial_cs"

but the card is still seen as GENERIC, I also added the same entry to /etc/pcmcia/bluetooth.conf

and finally :-

# cat /var/lib/pcmcia/stab
Socket 0: Belkin F8T020 Bluetooth Adapter
0       serial  serial_cs       0       ttyS3   4       67
Socket 1: empty

Can anyone out there help ?

I have a C860 running RC12 BTW.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=104657\"][{POST_SNAPBACK}][/a][/div]
Hey I have the same card and the same Z.
Did you by any chance get it to work?
If so please post how. So everyone with this or similiar problem could fix it too.

Thanks
Title: Hardware problems with pdaXrom..
Post by: Alfinfrance on December 30, 2005, 05:14:41 pm
Hi,

I tried my Holux GPS GM-270 CF card on my SL C3100 running pdaxrom v1.1.0beta1 and... strange thing : it isn't recognized as a GPS card but as "Compaq iPAQ Bluetooth Sleeve"

#cardctl ident
Socket 0:
  product info: "CF CARD", "GENERIC", "", ""
  manfid: 0x0279, 0x950b
  function: 2 (serial)

But it works perfect on my 5500 running Sharp Rom v3.13 ( and also with 3.10 )

Any idea?

Thanks
Title: Hardware problems with pdaXrom..
Post by: cmpayc13 on January 03, 2006, 06:05:41 am
Hi,

is there any way to get Linksys WCF54G working with PDAXROM?

any idea?

best regards

cmpayc
Title: Hardware problems with pdaXrom..
Post by: anunakin on January 12, 2006, 08:21:12 am
I need some help to put to work my CFVGA adapter, a voyager this has a cirrus logic chipset....
Title: Hardware problems with pdaXrom..
Post by: john4 on January 12, 2006, 10:56:10 pm
A problem confuse me form R10~Beta 1.My Z is SL-7500C.
My Z cannt be charged by AC/DC adapter,but the orange light is always lighte.
And the machine will use the power from the plugin power,instead of the battery.It means the AC/DC adapter work for the Z.

I wanna know what happen,If there any solution about this.
Or is it something about the hardware inside?
Title: Hardware problems with pdaXrom..
Post by: Tom'caT on February 07, 2006, 11:55:09 am
Quote
CARD: Ambicom CF Bluetooth model BT2000CF

cardctl ident:

Socket 0:
  product info: "AmbiCom BT2000C", "Bluetooth PC/CF Card", "", ""
  manfid: 0x0279, 0x950b
  function: 2 (serial)
Socket 1:
  no product info available

cardctl info:

PRODID_1="AmbiCom BT2000C"
PRODID_2="Bluetooth PC/CF Card"
PRODID_3=""
PRODID_4...=""
MANFID=022d,2000
FUNCID=2
PRODID_1=""
PRODID_2=""
PRODID_3=""
PRODID_4=""
MANFID=0000,0000
FUNCID=255
[div align=\"right\"][a href=\"index.php?act=findpost&pid=59355\"][{POST_SNAPBACK}][/a][/div]
Ok, I have a different problem with that card.
Zaurus SL-C700, PdaXrom 1.1.0beta1. When booting kernel I get this message:"cs: socket c0386800 timed out during reset.  Try increasing setup_delay."
and few lines later corgi_bl : change limit contrast 3
corgi_bl : unlimit contrast

'cardctl info 0' gives following output:
PRODID_1="CF CARD"
PRODID_2="GENERIC"
PRODID_3=""
PRODID_4...=""
MANFID=0279,950b
FUNCID=2

'cardctl ident 0' gives this:

Socket 0:
  product info: "CF CARD", "GENERIC", "", ""
  manfid: 0x0279, 0x950b
  function: 2 (serial)

'cardctl status 0' gives
3.3V 16-bit PC Card
function 0: [ready], [bat dead], [bat low].

'hciconfig' doesn't give any output.

I don't know what to do. Is it possible that CF card has a hardware malfunction or is this just a kernel error. Should I recompile the kernel or what?
I really tried everything I could think of.
Oh yes it's a 'yellow-black' revision (the newer one).
Title: Hardware problems with pdaXrom..
Post by: cycle_55 on February 17, 2006, 10:11:23 am
Quote
Do you have a piece of hardware thats not working under pdaXrom like a CF network card, USB controller etc?

Please post your cardctl ident and cardctl status and all other info you can find about the card (links to drivers etc.) - then we will try and fix them one at a time and try and make sure that pdaXrom supports as many accessories as possible.

We will probally be holding an IRC meeting with all user who are having problems with hardware but this is meant to be a warm up to see how many problems there are and how much time it will take to fix them.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=59334\"][{POST_SNAPBACK}][/a][/div]

I have a wireless cf card that's not recognized. It is a Planex GW-CF11X. I will have to figure out what other information to send you. I was originally going to just buy another recognized card but have not found a list of supported hardware. I like you site and will use it alot and will be donating to your cause soon. Thanks.
Title: Hardware problems with pdaXrom..
Post by: cycle_55 on February 24, 2006, 06:04:07 pm
Quote
Quote
Do you have a piece of hardware thats not working under pdaXrom like a CF network card, USB controller etc?

Please post your cardctl ident and cardctl status and all other info you can find about the card (links to drivers etc.) - then we will try and fix them one at a time and try and make sure that pdaXrom supports as many accessories as possible.

We will probally be holding an IRC meeting with all user who are having problems with hardware but this is meant to be a warm up to see how many problems there are and how much time it will take to fix them.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=59334\"][{POST_SNAPBACK}][/a][/div]

I have a wireless cf card that's not recognized. It is a Planex GW-CF11X. I will have to figure out what other information to send you. I was originally going to just buy another recognized card but have not found a list of supported hardware. I like you site and will use it alot and will be donating to your cause soon. Thanks.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=115163\"][{POST_SNAPBACK}][/a][/div]

The following is what I get:

cardctl ident

product info: "PLANEX COMMUNICXATIONS INC.", PLANEX GW_CF!!X Wireless CF
Card", "", ""
manfid: 0xd601, 0x0010
function: 6 (network)

cardctl status

Socket 0:
   3.3V 16-bit PC Card
   function 0: [ready]
Socket 1:
   3.3V 16-bit PC Card
   function 0: [ready], [bat dead], [bat low]

Socket 0 doesnt show up if the planex card is not in its slot. Thanks
Title: Hardware problems with pdaXrom..
Post by: dun4n on February 27, 2006, 04:30:42 am
First, you have to add your card definition to /etc/pcmcia/hostap_cs.conf

Edit this file and add :

Code: [Select]
card "PLANEX COMMUNICXATIONS INC."
   manfid 0xd601, 0x0010
   bind "hostap_cs"

It's time to flash your card (credits to gryning).
Download the latest firmware from :
http://www.red-bean.com/~proski/firmware/1.8.4.tar.bz2 (http://www.red-bean.com/~proski/firmware/1.8.4.tar.bz2) (extract rf010804.hex)
http://www.red-bean.com/~proski/firmware/primary.tar.bz2 (http://www.red-bean.com/~proski/firmware/primary.tar.bz2) (extract pm010102.hex)

Then use this script :
Code: [Select]
#!/bin/sh
cardctl scheme default
prism2_srec -gs wlan0 /pm010102.hex
prism2_srec -gp wlan0 /pm010102.hex
iwpriv wlan0 reset 1
prism2_srec -rp wlan0 path/rf010804.hex
iwconfig wlan0 mode 2
cardctl scheme planex
Where <path> is the path to the firmware.

Use ifconfig -a and you will see your card interface, now put it up using ifconfig <interface> up and it will works.

If it's doesn't work properly, verify that you have hostap and hostap_cs module loaded (lsmod | grep hostap) and try to plug the card one more time.
Title: Hardware problems with pdaXrom..
Post by: cycle_55 on March 02, 2006, 12:10:37 am
Quote
Quote
Quote
First, you have to add your card definition to /etc/pcmcia/hostap_cs.conf

Edit this file and add :

Code: [Select]
card "PLANEX COMMUNICXATIONS INC."
   manfid 0xd601, 0x0010
   bind "hostap_cs"

It's time to flash your card (credits to gryning).
Download the latest firmware from :
http://www.red-bean.com/~proski/firmware/1.8.4.tar.bz2 (http://www.red-bean.com/~proski/firmware/1.8.4.tar.bz2) (extract rf010804.hex)
http://www.red-bean.com/~proski/firmware/primary.tar.bz2 (http://www.red-bean.com/~proski/firmware/primary.tar.bz2) (extract pm010102.hex)

Then use this script :
Code: [Select]
#!/bin/sh
cardctl scheme default
prism2_srec -gs wlan0 /pm010102.hex
prism2_srec -gp wlan0 /pm010102.hex
iwpriv wlan0 reset 1
prism2_srec -rp wlan0 path/rf010804.hex
iwconfig wlan0 mode 2
cardctl scheme planex
Where <path> is the path to the firmware.

Use ifconfig -a and you will see your card interface, now put it up using ifconfig <interface> up and it will works.

If it's doesn't work properly, verify that you have hostap and hostap_cs module loaded (lsmod | grep hostap) and try to plug the card one more time.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=116219\"][{POST_SNAPBACK}][/a][/div]
[div align=\"right\"][a href=\"index.php?act=findpost&pid=116386\"][{POST_SNAPBACK}][/a][/div]

Thanx, I will try that and let you know how things go. It may take a bit for me to get there as I'm not all that fluent in linux but I eventually always manage to. Thanks again
[div align=\"right\"][a href=\"index.php?act=findpost&pid=116388\"][{POST_SNAPBACK}][/a][/div]
Please bear with me, I need to ask if the above script is put into a certain file such as /etc/pcmcia/wireless or network or?. Thanks.

I just realized I haven't said what hardware I have: C3100 with 1.1.0beta1
Title: Hardware problems with pdaXrom..
Post by: dun4n on March 08, 2006, 09:40:32 am
Quote
Please bear with me, I need to ask if the above script is put into a certain file such as /etc/pcmcia/wireless or network or?. Thanks.

Actually this script has to be run manually. But you can modify it to act as an init.d script and / or create an hotplug / hostap config to made it run when you plug your wifi card.
Title: Hardware problems with pdaXrom..
Post by: cycle_55 on March 08, 2006, 11:05:03 am
Quote
Quote
Please bear with me, I need to ask if the above script is put into a certain file such as /etc/pcmcia/wireless or network or?. Thanks.

Actually this script has to be run manually. But you can modify it to act as an init.d script and / or create an hotplug / hostap config to made it run when you plug your wifi card.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=117563\"][{POST_SNAPBACK}][/a][/div]

That is what I have been doing and even though Wlan0 is detected when I plug the card in I can not seem to be able to get it to go on line. After I run the script the light goes on but it will not send just receive. When I go to the lan/wifi icon and try to input my info the light goes out and I can't get it to go on again without rerunning the script and the same things happen all over again. It may be time to buy another card. Maybe I could donate this one to the cause. The problem with buying another one is that they're not that easy to find and which one would be better than what I've got. I have read some other posts and think I have some ideas. Thanks for all your help.

Well I thought I would give it one more try and I finally managed to get it to work. What I was doing wrong was that I had not saved a scheme in the lan/wifi setup, once I did that it worked as soon as the script is run. Thanks again for all your help.
Title: Hardware problems with pdaXrom..
Post by: Reaper on March 12, 2006, 10:45:52 am
Quote
I need some help to put to work my CFVGA adapter, a voyager this has a cirrus logic chipset....
[div align=\"right\"][a href=\"index.php?act=findpost&pid=110628\"][{POST_SNAPBACK}][/a][/div]

I also have CF VGA adapter, but mine is Pretec PocketPresenter with Epson S1D13806F00A1 chipset. I would like very much to get it working with pdaX, because it works with Cacko (not without a trick - I had to run "cfxgamirror 1" instead of "cfxgamirror 0" by default).
Title: Hardware problems with pdaXrom..
Post by: erbrmn on April 06, 2006, 02:45:41 am
Quote
First, you have to add your card definition to /etc/pcmcia/hostap_cs.conf
Edit this file and add :
Code: [Select]
card "PLANEX COMMUNICXATIONS INC."
   manfid 0xd601, 0x0010
   bind "hostap_cs"

It's time to flash your card (credits to gryning).
Download the latest firmware from :
http://www.red-bean.com/~proski/firmware/1.8.4.tar.bz2 (http://www.red-bean.com/~proski/firmware/1.8.4.tar.bz2) (extract rf010804.hex)
http://www.red-bean.com/~proski/firmware/primary.tar.bz2 (http://www.red-bean.com/~proski/firmware/primary.tar.bz2) (extract pm010102.hex)

Then use this script :
Code: [Select]
#!/bin/sh
cardctl scheme default
prism2_srec -gs wlan0 /pm010102.hex
prism2_srec -gp wlan0 /pm010102.hex
iwpriv wlan0 reset 1
prism2_srec -rp wlan0 path/rf010804.hex
iwconfig wlan0 mode 2
cardctl scheme planex
Where <path> is the path to the firmware.

Use ifconfig -a and you will see your card interface, now put it up using ifconfig <interface> up and it will works.

If it's doesn't work properly, verify that you have hostap and hostap_cs module loaded (lsmod | grep hostap) and try to plug the card one more time.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=116219\"][{POST_SNAPBACK}][/a][/div]

I have Planex wireless card and i have problem that it could not detect on RHEL4.
I tried this tip, and  It worked, it was brilliant
But, after restart system or reinsert card, I could not find wireless card.
Now , how can I download new firmware into flash of card. I want to use "-f" parametr.
But, I tried several time, there was some error .
I only changed "g" to "f" on script.





Please advice me, to download firmware into flash of card.
Title: Hardware problems with pdaXrom..
Post by: cycle_55 on April 06, 2006, 10:32:45 am
Quote
Quote
First, you have to add your card definition to /etc/pcmcia/hostap_cs.conf
Edit this file and add :
Code: [Select]
card "PLANEX COMMUNICXATIONS INC."
   manfid 0xd601, 0x0010
   bind "hostap_cs"

It's time to flash your card (credits to gryning).
Download the latest firmware from :
http://www.red-bean.com/~proski/firmware/1.8.4.tar.bz2 (http://www.red-bean.com/~proski/firmware/1.8.4.tar.bz2) (extract rf010804.hex)
http://www.red-bean.com/~proski/firmware/primary.tar.bz2 (http://www.red-bean.com/~proski/firmware/primary.tar.bz2) (extract pm010102.hex)

Then use this script :
Code: [Select]
#!/bin/sh
cardctl scheme default
prism2_srec -gs wlan0 /pm010102.hex
prism2_srec -gp wlan0 /pm010102.hex
iwpriv wlan0 reset 1
prism2_srec -rp wlan0 path/rf010804.hex
iwconfig wlan0 mode 2
cardctl scheme planex
Where <path> is the path to the firmware.

Use ifconfig -a and you will see your card interface, now put it up using ifconfig <interface> up and it will works.

If it's doesn't work properly, verify that you have hostap and hostap_cs module loaded (lsmod | grep hostap) and try to plug the card one more time.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=116219\"][{POST_SNAPBACK}][/a][/div]

I have Planex wireless card and i have problem that it could not detect on RHEL4.
I tried this tip, and  It worked, it was brilliant
But, after restart system or reinsert card, I could not find wireless card.
Now , how can I download new firmware into flash of card. I want to use "-f" parametr.
But, I tried several time, there was some error .
I only changed "g" to "f" on script.





Please advice me, to download firmware into flash of card.

[div align=\"right\"][a href=\"index.php?act=findpost&pid=121995\"][{POST_SNAPBACK}][/a][/div]

i can only tell you that i highlight and paste this script and run it every time i want to use this card. Beyond that i have no idea how to make this automatic.
Title: Hardware problems with pdaXrom..
Post by: sylvain on April 13, 2006, 01:23:49 pm
Hello.

I tried to use the Netgear WG111 USB wifi dongle on my C3100 (pdaxrom 1.1.0-beta1).
When I plug it (with USB setting "serial"), it does find any driver. I am not quite familiar with USB support with Linux, so I wonder if it either unsupported, or if I have something to do before inserting it (modprobe some module ?).

With USB storage, it works without any problem.
Title: Hardware problems with pdaXrom..
Post by: anunakin on April 19, 2006, 06:17:43 pm
Quote
Hello.

I tried to use the Netgear WG111 USB wifi dongle on my C3100 (pdaxrom 1.1.0-beta1).
When I plug it (with USB setting "serial"), it does find any driver. I am not quite familiar with USB support with Linux, so I wonder if it either unsupported, or if I have something to do before inserting it (modprobe some module ?).

With USB storage, it works without any problem.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=123065\"][{POST_SNAPBACK}][/a][/div]

1- Have you a USB OTG adapter cable?

2- If yes on (1), Have you tested with a powered USB HUB?
Title: Hardware problems with pdaXrom..
Post by: TJBK_TJB on April 23, 2006, 05:52:23 pm
I've been having trouble with USB to serial adapters. The first one I tried was a Belkin F5U109 USB Serial Adapter. The driver reported by dmesg is the Magic Control Technology USB-RS232 converter driver v1.1 (mct_u232.c). It appeared to work at first, but then I realized that sending data did not work. So, I purchased an IOGear GUC232AWM USB to Serial Adapter. When I connected it, dmesg reported that it was a PL-2303 converter. It seems to function well, but it refused to function with the two programs that didn't work with earlier, though it seems to do more. The two programs are GPSBabel (http://www.gpsbabel.org/) and sendMap (http://cgpsmapper.com/) (a statically-linked x86 binary with user space qemu).
Title: Hardware problems with pdaXrom..
Post by: sylvain on April 28, 2006, 01:39:20 am
Quote
1- Have you a USB OTG adapter cable?

2- If yes on (1), Have you tested with a powered USB HUB?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=123827\"][{POST_SNAPBACK}][/a][/div]
I use the cable adapter "mini USB host", but i do not use a hub. Should I ?

(I also noticed that i can use my Ipod as an external drive !!!)
Title: Hardware problems with pdaXrom..
Post by: anunakin on May 09, 2006, 09:14:09 pm
OK! I think WG111 must works with wlan-ng ...
try install and loads driver from wlan-ng
Title: Hardware problems with pdaXrom..
Post by: darkage on May 18, 2006, 12:34:52 am
ThinkOutside Stowaway BlueTooth Keyboard.  

Can discover device, but cant connect/use keyboard.   Default sharp rom, & OZ works fine.   Pdaxrom beta 3+4 & cracko it doesn't work.

Any hints on comparing whats different between pdaxrom & sharp/oz roms to make this device work?

I will love you forever if you can help   *crossing fingers for help* lol
Title: Hardware problems with pdaXrom..
Post by: fluffybob on June 02, 2006, 07:27:51 am
Quote
I've been having trouble with USB to serial adapters. The first one I tried was a Belkin F5U109 USB Serial Adapter. The driver reported by dmesg is the Magic Control Technology USB-RS232 converter driver v1.1 (mct_u232.c). It appeared to work at first, but then I realized that sending data did not work. So, I purchased an IOGear GUC232AWM USB to Serial Adapter. When I connected it, dmesg reported that it was a PL-2303 converter. It seems to function well, but it refused to function with the two programs that didn't work with earlier, though it seems to do more. The two programs are GPSBabel (http://www.gpsbabel.org/) and sendMap (http://cgpsmapper.com/) (a statically-linked x86 binary with user space qemu).
[div align=\"right\"][a href=\"index.php?act=findpost&pid=124302\"][{POST_SNAPBACK}][/a][/div]

I've been trying for awhile to get a deleo usb gps device working on a C1000. When i attach the gps the output from dmesg shows the pl-2303 converter attached and says it has attached it to ttyUSB0. Im using beta4 now and cant find ttyUSB anything in /dev (i have seen it in previous versions though). I was interested to hear you say "It  seems to function well". I'm a bit new at Zaurus (or even linus) devopment and was planning on trying cat /dev/ttyUSB0 to see the raw output from the gps to check if that was working before i then go on the get gpsd running. But since i now can't find ttyUSB0 and don't know what else to try I am stuck. Is there something i'm overlooking or some other package i need to install?

Thanks guys.

SL-C1000
pdaxrom beta4
deleo usb gps
Title: Hardware problems with pdaXrom..
Post by: TJBK_TJB on June 04, 2006, 08:47:06 pm
Quote
Quote
I've been having trouble with USB to serial adapters. The first one I tried was a Belkin F5U109 USB Serial Adapter. The driver reported by dmesg is the Magic Control Technology USB-RS232 converter driver v1.1 (mct_u232.c). It appeared to work at first, but then I realized that sending data did not work. So, I purchased an IOGear GUC232AWM USB to Serial Adapter. When I connected it, dmesg reported that it was a PL-2303 converter. It seems to function well, but it refused to function with the two programs that didn't work with earlier, though it seems to do more. The two programs are GPSBabel (http://www.gpsbabel.org/) and sendMap (http://cgpsmapper.com/) (a statically-linked x86 binary with user space qemu).
[div align=\"right\"][a href=\"index.php?act=findpost&pid=124302\"][{POST_SNAPBACK}][/a][/div]

I've been trying for awhile to get a deleo usb gps device working on a C1000. When i attach the gps the output from dmesg shows the pl-2303 converter attached and says it has attached it to ttyUSB0. Im using beta4 now and cant find ttyUSB anything in /dev (i have seen it in previous versions though). I was interested to hear you say "It  seems to function well". I'm a bit new at Zaurus (or even linus) devopment and was planning on trying cat /dev/ttyUSB0 to see the raw output from the gps to check if that was working before i then go on the get gpsd running. But since i now can't find ttyUSB0 and don't know what else to try I am stuck. Is there something i'm overlooking or some other package i need to install?

Thanks guys.

SL-C1000
pdaxrom beta4
deleo usb gps
[div align=\"right\"][a href=\"index.php?act=findpost&pid=129448\"][{POST_SNAPBACK}][/a][/div]

I've been using beta2 as neither beta4 nor beta3 was not quite working out for me. I did not get to testing my USB serial device, so I never tried it myself. So I don't know.
Title: Hardware problems with pdaXrom..
Post by: louigi600 on July 07, 2006, 09:24:48 am
Hi I'm a new user to pdaxrom 1.1.0beta1 "Kathrin"
running on a c860 (I'm also doing some testing with a c760 on the beta4 release)

Previously I was a fairly satisfied cacko rom user but I wanted something
that gave me more the feel on a minature computer rather than a handheld,
something for which it would be easier to port normal linux applications to
so here I am.

Right after the install I started testing if all the hardware I frequently
use on my zaurus (wireless lan card, GPS receiver and bluetooth card) worked correctly.
Unfortunately one I need most while on standby is the bluetooth card that
system reports to be unsupported. On the cacko rom I managed to get it
working, altough I forgot if I hadto fiddle a little or if it worked
straight away.

Hope you can get me going with this card soon ;-)

Here are the essential card details:
PRODID_2="CF + PersonalNetwork Card"
MANFID=0104,009f
FUNCTID=254

Regards
David Rao
Title: Hardware problems with pdaXrom..
Post by: distortion on August 07, 2006, 06:56:43 am
I've been trying for awhile to get a deleo usb gps device working on a C1000.

probably talking out of my hat but almost sure beta4 uses udev so there will be nothing in dev for ttyUSB untill something is conected. for that to happen a udev rule is needed for the device (had to read up on this to get a usb network working between debian and a 5000d). would sugest reading up on udev and how to write rules fot it. if someone has already made a rule for your gps device (for a laptop/desktop/toaster) then that should work for your zaurus to.
Title: Hardware problems with pdaXrom..
Post by: LukeLuke on October 10, 2006, 04:09:41 am
The gadget is this :
http://cgi.ebay.it/ws/eBayISAPI.dll?ViewIt...AMEWN%3AIT&rd=1 (http://cgi.ebay.it/ws/eBayISAPI.dll?ViewItem&ih=019&item=290023507220&rd=1&sspagename=STRK%3AMEWN%3AIT&rd=1)
is an ST268 USB NIC, when i use it on pdaXrom it's not work!

What can i do ?

Code: [Select]
root@zaurus ~# lsusb -v

Bus 001 Device 014: ID 0a46:0268 Davicom Semiconductor, Inc.
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0         8
  idVendor           0x0a46 Davicom Semiconductor, Inc.
  idProduct          0x0268
  bcdDevice            1.01
  iManufacturer           1 ShanTou
  iProduct                2 ST268 USB NIC
  iSerial                 3 0268
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           39
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0xa0
      Remote Wakeup
    MaxPower              144mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass         0 (Defined at Interface level)
      bInterfaceSubClass      0
      bInterfaceProtocol      0
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               none
          Usage Type               Data
        wMaxPacketSize     0x0040  bytes 64 once
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               none
          Usage Type               Data
        wMaxPacketSize     0x0040  bytes 64 once
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               none
          Usage Type               Data
        wMaxPacketSize     0x0008  bytes 8 once
        bInterval               1
  Language IDs: (length=4)
     0409 English(US)

this is my dmesg :

Code: [Select]
usb 1-2.2: new full speed USB device using pxa27x-ohci and address 20
usb 1-2.2: configuration #1 chosen from 1 choice

THANKS              

Bye
Title: Hardware problems with pdaXrom..
Post by: pungipungi on December 30, 2006, 05:49:37 pm
Currently I got stucked with a Samsung Magiclan  SWL-2610C card.

# cardctl status
Socket 0:
  3.3V 16-bit PC Card
  function 0: [ready]
# cardctl ident
Socket 0:
  product info: "SAMSUNG", "WLAN CF Card(SWL-2600)"
  manfid: 0x0250, 0xb001
  function: 6 (network)
# dmesg
hostap_cs: 0.4.7 - 2005-11-20 (Jouni Malinen <jkmaline@cc.hut.fi>)
hostap_cs: setting Vcc=33 (constant)
hostap_cs: CS_EVENT_CARD_INSERTION
hostap_cs: setting Vcc=33 (from config)
Checking CFTABLE_ENTRY 0x01 (default 0x01)
IO window settings: cfg->io.nwin=0 dflt.io.nwin=0
hostap_cs: Registered netdevice wifi0
hostap_cs: index 0x01: Vcc 3.3, irq 135
hostap_cs: assuming no Primary image in flash - card initialization not completed
wifi0: test Genesis mode with HCR 0x1f
prism2_pccard_cor_sreset: original COR 41
prism2_pccard_genesis_sreset: original COR 00
Readback test failed, HCR 0x1f write 00 e1 a1 ff read 00 00 00 00
wifi0: test Genesis mode with HCR 0x0f
prism2_pccard_cor_sreset: original COR 00
prism2_pccard_genesis_sreset: original COR 00
Readback test failed, HCR 0x0f write 00 e1 a1 ff read 00 00 00 00
prism2_pccard_genesis_sreset: original COR 00
wifi0: registered netdevice wlan0
corgi_bl : change limit contrast 3
prism2: wlan0: operating mode changed 3 -> 2
wlan0: cannot set RID fc00 (len=2) - no PRI f/w
wlan0: cannot set RID fc0e (len=34) - no PRI f/w
hostap_crypt: registered algorithm 'WEP'
wifi0: cannot get RID fc28 (len=2) - no PRI f/w
Could not read current WEP flags.
wifi0: encryption setup failed
wlan0: set_encryption failed
wlan0: cannot set RID fc02 (len=34) - no PRI f/w
wlan0: could not set interface UP - no PRI f/w
wlan0: could not set interface UP - no PRI f/w
prism2_download: dl_cmd=4 start_addr=0x003f0000 num_areas=3
wifi0: test Genesis mode with HCR 0x1f
prism2_pccard_cor_sreset: original COR 00
prism2_pccard_genesis_sreset: original COR 00
Readback test failed, HCR 0x1f write 00 e1 a1 ff read 00 00 00 00
wifi0: test Genesis mode with HCR 0x0f
prism2_pccard_cor_sreset: original COR 00
prism2_pccard_genesis_sreset: original COR 00
Readback test failed, HCR 0x0f write 00 e1 a1 ff read 00 00 00 00
wifi0: Could not initiate genesis mode
wifi0: cannot get RID fd0b (len=1008) - no PRI f/w
wifi0: cannot get RID fd0b (len=1008) - no PRI f/w
prism2_download: dl_cmd=4 start_addr=0x003f0000 num_areas=3
wifi0: test Genesis mode with HCR 0x1f
prism2_pccard_cor_sreset: original COR 00
prism2_pccard_genesis_sreset: original COR 00
Readback test failed, HCR 0x1f write 00 e1 a1 ff read 00 00 00 00
wifi0: test Genesis mode with HCR 0x0f
prism2_pccard_cor_sreset: original COR 00
prism2_pccard_genesis_sreset: original COR 00
Readback test failed, HCR 0x0f write 00 e1 a1 ff read 00 00 00 00
wifi0: Could not initiate genesis mode
wifi0: cannot get RID fd0b (len=1008) - no PRI f/w
wifi0: cannot get RID fd0b (len=1008) - no PRI f/w
wifi0: cannot get RID fd0b (len=1008) - no PRI f/w
#

Seems that there's no primary firmware available. I hope I'm correct that this card uses a PRISM based chip ...

Anybody an idea how to proceed?
Title: Hardware problems with pdaXrom..
Post by: Jon_J on June 09, 2007, 12:36:08 pm
Quote
Do you have a piece of hardware thats not working under pdaXrom like a CF network card, USB controller etc?

Please post your cardctl ident and cardctl status and all other info you can find about the card (links to drivers etc.) - then we will try and fix them one at a time and try and make sure that pdaXrom supports as many accessories as possible.

We will probally be holding an IRC meeting with all user who are having problems with hardware but this is meant to be a warm up to see how many problems there are and how much time it will take to fix them.
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=59334\")
I have this CF ethernet card, which I haven't gotten to connect.
Socket Rugged CF 10/100™ card
Model number: EA2917 - 722, Rugged CF 10/100 Ethernet
[a href=\"http://www.socketmobile.com/products/network-connectivity/10-100-ethernet/]http://www.socketmobile.com/products/netwo...0-100-ethernet/[/url]
----------
cardctl ident
Socket 0:
 product info: "Socket", "CF 10/100 Ethernet Card", "Revision B", "05/11/06"
 manfid: 0x0104, 0x02d2
 function: 6 (network)
----------
cardctl info
PRODID_1="Socket"
PRODID_2="CF 10/100 Ethernet Card"
PRODID_3="Revision B"
PRODID_4="05/11/06"
MANFID=0104,02d2
FUNCID=6
----------
dmesg
eth0: NE2000 Compatible: io 0xf6000300, irq 135, auto xcvr, hw_addr 00:C0:1B:07:D5:3A
pxa_pcmcia_suspend(0)
----------
/etc/pcmcia/config (I added this myself)
card "Socket 10/100 Ethernet CF Card"
  manfid 0x0104, 0x02d2
  bind "pcnet_cs"
----------
Setting up network with DHCP and auto DNS results in no connection and no lights on my router.
Setting up network with IP address, subnet mask, gateway, two DNS addresses, and default domain, lights up my router, but I cannot ping the internet or open any webpages.
It shows as connected, and takes at least 25-30 seconds to connect. (My wifi card only takes about 5 secs)
----------
ifconfig
eth0      
Link encap:Ethernet  HWaddr 00:C0:1B:07:D5:3A
inet addr:66.249.50.162  Bcast:66.249.51.255  Mask:255.255.252.0
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
RX packets:13 errors:0 dropped:0 overruns:0 frame:0
TX packets:111 errors:18 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0   TX bytes:2160 (2.1 Kb)
Interrupt:135 Base address:0x300
----------
EDIT:
I'm not giving up easily on this card since I paid a lot of money for it, it is brand new, and I cannot return it.
Additional info - this card uses this chip:
The Rugged CF 10/100 card utilizes the Asix AX88790 L 10/100BASE 3-in-1 PCMCIA Fast Ethernet Controller.

Here is a post about someone getting this working for 2.6 kernel
http://www.mail-archive.com/linux-pcmcia@l...g/msg00051.html (http://www.mail-archive.com/linux-pcmcia@lists.infradead.org/msg00051.html)

Socket indicates that this chip has a Phy bug and they provide a workaround.
ftp://ftp.socketcom.com/ea/Rugged_10-100_...ges_07-2006.zip (http://ftp://ftp.socketcom.com/ea/Rugged_10-100_Driver_Changes_07-2006.zip)
Title: Hardware problems with pdaXrom..
Post by: pwyll on December 25, 2007, 07:05:00 am
I realize I am quoting a three year old post in a thread that hasn't seen a message in six months, but this is the most appropriate thread and it *is* pinned...

I am running a pdaXii13 full install from a SanDisk Ultra II 2gb SD card on an Akita, so far without issue.  I am trying desperately to achieve some sort of network connectivity and have, to that end, just acquired a Trendnet TE-CF10 (yes, ten),  This thread seemed the best bet to get it working, beginning with this (reposted at the time) info.

Quote
Code: [Select]
card "TRENDnet TE-CF100"
 manfid 0x0149, 0xc1ab
 bind "pcnet_cs"

I have tried it with the "100" and with a "10".  I have tried it with the actual information reported by cardctl ident ("Ethernet", "CF Size PC Card", "1.0", " ") and I have tried it with the (later suggested) "Unknown NE2000 Compatible Ethernet".  I have tried it with and without  "function: 6 (network)" and even added the commented out "function: network_adapter" mentioned in one post.  Nothing worked--in fact it never mattered what I entered in /etc/pcmcia/config, the card eject panel in icewm always reported it as "TRENDnet TE-CF100" (yes, one hundred).

I suppose it was due to my own tunnel-vision that it took me several hours to finally check lsmod to find out the module wasn't even being loaded and subsequently try modprobe pcnet_cs to discover that the module bound by 11,000 entries in /etc/pcmcia/config couldn't even be found...  

I've looked in every beta1, beta3 and ii13 feed I can find (which is probably relatively few) to no avail.  But then I realized that this is a fresh install of 5.4.9, my entire set of customizations consisting of adding some wallpapers, editing ipkg.conf so that /mnt/card2 will show up as a possible destination, and now one edit (several times) to /etc/pcmcia/config--which means that 5.4.9 doesn't include that module.

Is there some way I can get it, or would I need to reflash to some indeterminately older version of pdaxrom, get the card working and then attempt to upgrade back to 5.4.9 from there?  Or am I stuck with an unconnected Zaurus until I can score a wireless card, since all the ethernet cards require this (seemingly) now non-existent module?

Thanks for any help you may be able to provide  :>


Scott