Hardware problems with pdaXrom..

[Hrw]

yossie: with hostap maybe? Atleast this is what I will try for prism2 cards.

[sleepy]

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?

[MONVMENTVM]

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

[sleepy]

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?

[MONVMENTVM]

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

[desertrat]

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]

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

[agraef]

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"

[Hrw]

agraef: use hostap-modules instead of orinoco for that card.

most of Prism2 cards works better with hostap_cs then with orinoco_cs driver.

[agraef]

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.

[Hrw]

oops. I was thinking that pdaX provide hostap-modules.

[agraef]

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 for a tarball with the binaries.

[Cagilaba]

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

[ajnk]

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.

[Hrw]

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)

[cjb]

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.

HTH