Hardware problems with pdaXrom..

[shula]

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)

[rgrep]

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

[rgrep]

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.

[shula]

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.

[rgrep]

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.

[sigmaX]

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

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

[jasonakay]

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.

[ScottYelich]

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

[nightfire]

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!

[nightfire]

Also, in case my patch was corrupted by the description field on bug ID 245, here's a binary.

[gene]

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!!!

[Mickeyl]

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.

[samxiao]

anyone brings Pocketop keyboard works in X11 ROM?

[Re@lity]

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!)

[AlexBeaudion]

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