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

sylvain

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

anunakin

  • Sr. Member
  • ****
  • Posts: 340
    • View Profile
    • http://vivaphp.net
Hardware problems with pdaXrom..
« Reply #76 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?
[img]http://www.vivaphp.net/imagens/rev2.jpg\" border=\"0\" class=\"linked-sig-image\" /]
Anunakin (Marcus Fazzi)

Nokia N900 32GB + microSD 2GB
Nokia N810 w/ microSD 8GB
Nokia 5310 XpressMusic w/ microSD 1GB
HP48GX->Psion Sienna->Palm m130->Tungsten T->Zaurus SL-5500->C3000->C3100 ALL SOLD

My FEED(On Line AGAIN!!!)

TJBK_TJB

  • Newbie
  • *
  • Posts: 28
    • View Profile
Hardware problems with pdaXrom..
« Reply #77 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 and sendMap (a statically-linked x86 binary with user space qemu).
« Last Edit: April 23, 2006, 05:52:45 pm by TJBK_TJB »

sylvain

  • Newbie
  • *
  • Posts: 17
    • View Profile
Hardware problems with pdaXrom..
« Reply #78 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 !!!)

anunakin

  • Sr. Member
  • ****
  • Posts: 340
    • View Profile
    • http://vivaphp.net
Hardware problems with pdaXrom..
« Reply #79 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
[img]http://www.vivaphp.net/imagens/rev2.jpg\" border=\"0\" class=\"linked-sig-image\" /]
Anunakin (Marcus Fazzi)

Nokia N900 32GB + microSD 2GB
Nokia N810 w/ microSD 8GB
Nokia 5310 XpressMusic w/ microSD 1GB
HP48GX->Psion Sienna->Palm m130->Tungsten T->Zaurus SL-5500->C3000->C3100 ALL SOLD

My FEED(On Line AGAIN!!!)

darkage

  • Newbie
  • *
  • Posts: 23
    • View Profile
Hardware problems with pdaXrom..
« Reply #80 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
« Last Edit: May 18, 2006, 05:14:43 am by darkage »

fluffybob

  • Newbie
  • *
  • Posts: 25
    • View Profile
Hardware problems with pdaXrom..
« Reply #81 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 and sendMap (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

TJBK_TJB

  • Newbie
  • *
  • Posts: 28
    • View Profile
Hardware problems with pdaXrom..
« Reply #82 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 and sendMap (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.

louigi600

  • Sr. Member
  • ****
  • Posts: 471
    • View Profile
Hardware problems with pdaXrom..
« Reply #83 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
Regards
David

SL-c760*  pdaXrom latest
SL-c860    pdaXrom latest ;-)
SL-c1000  pdaXrom Latest
Acer Aspire One running slackware and Clash
Toshiba AC100 running ARMedslack and Clash

*with some hardware problems but good for testing

distortion

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

LukeLuke

  • Full Member
  • ***
  • Posts: 167
    • View Profile
    • http://
Hardware problems with pdaXrom..
« Reply #85 on: October 10, 2006, 04:09:41 am »
The gadget is this :
http://cgi.ebay.it/ws/eBayISAPI.dll?ViewIt...AMEWN%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

pungipungi

  • Jr. Member
  • **
  • Posts: 74
    • View Profile
    • http://members.cheese.at/woody/zaurus
Hardware problems with pdaXrom..
« Reply #86 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?
SL5500G OZ3.5.3 (GPE) , SD 1G,   D-Link air 660 wlan
C1000 pdaXrom, SD 256, D-Link air 660 wlan
Suse 9.3
My Zaurus Page

Jon_J

  • Hero Member
  • *****
  • Posts: 1853
    • View Profile
    • http://
Hardware problems with pdaXrom..
« Reply #87 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]
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

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
« Last Edit: June 10, 2007, 02:17:11 pm by Jon_J »
C3100 Multiboot-->Angstrom 2007.12-r18 | Cacko 1.23 | ArchLinuxARM
C3200 pdaxii13v2-5.5-alpha4 Akita on NAND

Ambicom WL1100C-CF Wifi - Ambicom CF modem - Ambicom CF GPS - Belkin-F5D5050 USB LAN
Socket CF Bluetooth rev K - Iogear 4 port USB micro hub - pocket CF card reader
Targus mini USB optical mouse - 2 Targus SD card readers

pwyll

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