Author Topic: Hardware problems with pdaXrom..  (Read 129792 times)

shula

  • Jr. Member
  • **
  • Posts: 95
    • View Profile
Hardware problems with pdaXrom..
« Reply #15 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)
C860, pdaxrom rc8,
with Gnumeric as the perfect PIM :-)

rgrep

  • Full Member
  • ***
  • Posts: 149
    • View Profile
Hardware problems with pdaXrom..
« Reply #16 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
« Last Edit: January 01, 2005, 10:14:10 pm by rgrep »
[img]https://www.oesf.org/forums/style_emoticons/default/smile.gif\" border=\"0\" class=\"linked-sig-image\" /] Has: Dynamism C760 / Linksys WCF12 WiFi / Kingston 512MB SD
[img]https://www.oesf.org/forums/style_emoticons/default/biggrin.gif\" border=\"0\" class=\"linked-sig-image\" /] Loves: pdaXrom / Warwalking
[img]https://www.oesf.org/forums/style_emoticons/default/sad.gif\" border=\"0\" class=\"linked-sig-image\" /] Hates: NetGear MA701 WiFi / SanDisk 256MB SD / C760 Charging Faults

rgrep

  • Full Member
  • ***
  • Posts: 149
    • View Profile
Hardware problems with pdaXrom..
« Reply #17 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.
[img]https://www.oesf.org/forums/style_emoticons/default/smile.gif\" border=\"0\" class=\"linked-sig-image\" /] Has: Dynamism C760 / Linksys WCF12 WiFi / Kingston 512MB SD
[img]https://www.oesf.org/forums/style_emoticons/default/biggrin.gif\" border=\"0\" class=\"linked-sig-image\" /] Loves: pdaXrom / Warwalking
[img]https://www.oesf.org/forums/style_emoticons/default/sad.gif\" border=\"0\" class=\"linked-sig-image\" /] Hates: NetGear MA701 WiFi / SanDisk 256MB SD / C760 Charging Faults

shula

  • Jr. Member
  • **
  • Posts: 95
    • View Profile
Hardware problems with pdaXrom..
« Reply #18 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.
C860, pdaxrom rc8,
with Gnumeric as the perfect PIM :-)

rgrep

  • Full Member
  • ***
  • Posts: 149
    • View Profile
Hardware problems with pdaXrom..
« Reply #19 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.
[img]https://www.oesf.org/forums/style_emoticons/default/smile.gif\" border=\"0\" class=\"linked-sig-image\" /] Has: Dynamism C760 / Linksys WCF12 WiFi / Kingston 512MB SD
[img]https://www.oesf.org/forums/style_emoticons/default/biggrin.gif\" border=\"0\" class=\"linked-sig-image\" /] Loves: pdaXrom / Warwalking
[img]https://www.oesf.org/forums/style_emoticons/default/sad.gif\" border=\"0\" class=\"linked-sig-image\" /] Hates: NetGear MA701 WiFi / SanDisk 256MB SD / C760 Charging Faults

sigmaX

  • Full Member
  • ***
  • Posts: 110
    • View Profile
Hardware problems with pdaXrom..
« Reply #20 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

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
Enrique

sl-c860 / 1gigCF 40X / 256mbSD / Ambicom WIFI / TRENDnet 10/100 ethernet / SL-5500 CF 40X 32MB

jasonakay

  • Newbie
  • *
  • Posts: 23
    • View Profile
Hardware problems with pdaXrom..
« Reply #21 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.

ScottYelich

  • Hero Member
  • *****
  • Posts: 992
    • View Profile
    • http://www.zaurususergroup.com/modules.php?opmodload&namephpWiki&filei
Hardware problems with pdaXrom..
« Reply #22 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

nightfire

  • Newbie
  • *
  • Posts: 14
    • View Profile
Hardware problems with pdaXrom..
« Reply #23 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!
« Last Edit: January 05, 2005, 01:50:57 am by nightfire »

nightfire

  • Newbie
  • *
  • Posts: 14
    • View Profile
Hardware problems with pdaXrom..
« Reply #24 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.

gene

  • Newbie
  • *
  • Posts: 45
    • View Profile
    • http://www.fastcube.com
Hardware problems with pdaXrom..
« Reply #25 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!!!
« Last Edit: January 27, 2005, 10:07:50 pm by gene »

Mickeyl

  • Hero Member
  • *****
  • Posts: 1495
    • View Profile
    • http://www.Vanille.de
Hardware problems with pdaXrom..
« Reply #26 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.
« Last Edit: January 28, 2005, 06:33:06 am by Mickeyl »
Cheers,

Michael 'Mickey' Lauer | Embedded Linux Freelancer | www.Vanille-Media.de
Consider donating, if you like the software I contribute to.

samxiao

  • Sr. Member
  • ****
  • Posts: 260
    • View Profile
    • http://
Hardware problems with pdaXrom..
« Reply #27 on: January 29, 2005, 08:48:17 am »
anyone brings Pocketop keyboard works in X11 ROM?
Zaurus C1000 (formerly SL5500 and C700)
Cacko developer ROM 1.23 beta + Debian Sarge + X/Qt
1GB Transcend 80x SD (ext2) / 512MB Lexar SD (ext2) / 256MB SanDisk CF(vfat)
Netgear MA701 WiFi CF
Ambicom GPS-CF
Pocketop IR keyboard (has positioning problem with C1000)
Brando LCD screen protector

Apple PowerBook 12" G4 Rev. C + Mac OS X 10.4.x (Tiger)

Re@lity

  • Newbie
  • *
  • Posts: 10
    • View Profile
Hardware problems with pdaXrom..
« Reply #28 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!)
.................I started out with nothing..............................and I've still got most of it left........................

AlexBeaudion

  • Newbie
  • *
  • Posts: 3
    • View Profile
Hardware problems with pdaXrom..
« Reply #29 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