Messages

1

Zaurus - pdaXrom / 1.1.0r121 Is Out!

« on: October 20, 2006, 02:48:09 pm »

I still can't get my Symbol Spectrum24 working!

I downloaded the firmware using the previously supplied link and copied it to my (newly created) /usr/lib/hotplug/firmware directory.

pdaXrom responds to my Spectrum24 just it did without the firmware.

To wit - when I plug the card in, I can see it in the (little card manager app on the taskbar, whatever it's called) - it shows up as "Symbol Tech?ologies LA4111 Spectrum24 Wireless LAN PC Card 1.00" The little LED on the card never lights up, even for a moment, though, and no eth0 is created. dmesg says -

pccard: PCMCIA card inserted into slot 0
pcmcia: registering new device pcmcia0.0

When I remove the card, dmesg says -

pccard: card ejected from slot 0

With the older versions of the ROM, I was accustomed to calling "/etc/rc.d/init.d/pcmcia restart" - with this version, there is no pcmcia script I could find, so I restarted the whole system. The behavior is unchanged.

Can someone please help me figure this out?

2

Zaurus - pdaXrom / Gui Bails Almost Immediately - C860 / R121

« on: October 20, 2006, 01:39:04 pm »

Did you check your MD5 checksum before burning that image to NAND?

No, I didn't - but I have now done so and they check out.

I've just tried reflashing the kernel and root filesystem image, and - with horror - I think I see the problem.

Once the emergency system started "writing data to block," I got an I/O error. It rebooted before I could read the whole thing, but it said something about how the file didn't fit due to bad blocks!

So - I restarted the whole process, and it went without incident the second time around.

And it booted into the GUI just fine!

Is my NAND dying? Is this simply a bug or a glitch?

3

Zaurus - pdaXrom / Gui Bails Almost Immediately - C860 / R121

« on: October 20, 2006, 11:14:52 am »

I've just done a fresh install of 1.1.0r121 - both uboot and the system itself - on my C860. Everything seemed to go well - very smooth. Eventually, the system starts and I login as root. I run startx and get the touchscreen calibration screen as expected.

Then x starts. The screen is initially rotated as if my clamshell was in portrait mode, which it isn't. As the display gets almost fully drawn - the toolbar is complete but the wallpaper and icons aren't loaded yet - the screen flashes and switches to landscape mode. The screen is drawn to the same point - toolbar but no icons or wallpaper - then I'm dumped back out to the command prompt.

I see:

Code: [Select]

# startx
Jan 1 00:02:42 sudo: root : TTY=vc/1; PWD=/home/root; =/sbin/modprobe mousedev
Jan 1 00:02:43 input.agent[1082]: ... no modules for INPUT
Removing empty element from the valid list of fontpaths
Shutting down switchevd: Jan 1 00:02:46 switchev: switchevd
Starting switchevd: Jan 1 00:02:47 switchev: Starting swit
pdaXrom [Husky]
Removing empty element from the valid list of fontpaths
This output is truncated - I guess by the switch from one screen mode to another - and I don't know how to see the full output. The above is just as it appears on my screen.

If I startx again at this point, everything goes exactly the same, except the "... no modules for INPUT" line is omitted. I see that line only once per boot.

The behavior is the same whether my clamshel is in portrait or landscape mode.

Can anyone give me any suggestions?

4

Zaurus - pdaXrom / Quivering Mouse Pointer/stylus

« on: October 20, 2006, 09:57:23 am »

if you have a 7x0 -860 you can try

cat 75 > /proc/driver/w100/fastsysclk
[div align=\"right\"][a href=\"index.php?act=findpost&pid=143178\"][{POST_SNAPBACK}][/a][/div]

I have an 860 running r121. My /proc/driver directory contains only rtc and snd-page-alloc - there is no w100.

Any ideas? My jittery cursor makes using the stylus an exercise in frustration and restraint.

5

Zaurus - pdaXrom / Ratoc Cfu-1 And Usb Mouse

« on: March 20, 2006, 03:30:00 pm »

So, four and a half months later, having just installed v1.1beta2, things seem to be unchanged. It's swell that the Ratoc CFU-1 is supported by the ROM now, but I still can't figure out how to use a mouse.

Can anyone point me in the right direction?

6

Accessories / Any New Non-sticky-outy Wifi Cards Out There?

« on: November 04, 2005, 10:54:14 am »

Symbol LA-4137 Wireless Networker

Overall: 55mm
Sticky-outy: 18mm

7

Zaurus - pdaXrom / Ratoc Cfu-1 And Usb Mouse

« on: November 03, 2005, 01:16:46 pm »

I installed RC12 on my C860 last night and set up my CFU-1 USB host card. I was able to mount a USB flash drive and access it properly.

I decided to have another go at getting my USB mouse working. I created the following device nodes:

/dev/input
/dev/input/mice
/dev/input/mouse0

I modprobed mousedev and hid.

I plugged in my USB mouse and saw in dmesg that the mouse was detected.

I then tried cat /dev/input/mice. No error was returned but no data was dumped to the console when I manipulated the mouse.

I tried cating /dev/input/mouse0 with the same result.

I created more device nodes:

/dev/input/mouse1
/dev/input/mouse2
/dev/input/mouse3

and tried cating them.

For each of those, I got an error that said that the device didn't exist.

When I removed the USB mouse, I got the same error for /dev/input/mouse0.

This suggested to me that /dev/input/mouse0 was properly mapping the USB mouse, and it seemed that everything *almost* worked - but not.

I tried using usbmouse instead of mousedev with the same results.

I looked around on the net for some clue as to what I could try next. Everything I read seemed to say that after modprobing the modules and creating the device nodes, I should be able to see mouse data when I cat the device. No one provided any further troubleshooting information; it seemed to be something that should "just work."

The really frustrating thing is that last time I fooled around with this, I *was* able to see mouse data on the console, and I feel that I did the exact same thing to accomplish this. Yet, this time, I was less successful.

The mouse I'm using is the same as I used last time, and one that I've been using successfully with my laptop. When I connect it to the CFU-1, the mouse lights up (it's optical). I don't think there's any chance this is a hardware issue.

I'm by no means confident that the corgi xserver has mouse support, but it seems like I should be able to get mouse data on the console in any case.

Has something changed in the ROM to make this less possible?

Does anyone have any suggestions as to what else I might try?

I would really, really like to get this to work.

8

Zaurus - pdaXrom / Just got back from DefCon, idea for pdaXrom

« on: October 31, 2005, 10:40:24 am »

I'd like to advocate FreeOTFE over BestCrypt. FOTFE is cross-platform, yet free and open.

http://www.freeotfe.org/

9

Zaurus - pdaXrom / Daphne Laserdisc Arcade

« on: October 21, 2005, 06:22:39 pm »

Please do post it; it sounds neat!

10

Zaurus - pdaXrom / Ir Keyboard Drivers - Alpha Release

« on: October 20, 2005, 10:06:59 pm »

It turned out that the boolean value being assigned to key_down in your scancode interpreting routine was inverted - the driver saw the keypress as a keyup, and vice versa. Seeing a keyup, then a keydown for each keypress was causing autorepeat to kick in after a moment, as the keys never seemed to be released. I was very pleased to have been able to fix that!

There were also some codes in the wrong spots in the normal_map. I fixed some easy ones; most of the keys work now. There seem to be some issues with the modifier keys; I'll look at them next.

The updated driver file is attached. (Just remove the .tar from the filename; it's not really a tar.)

11

Zaurus - pdaXrom / Ir Keyboard Drivers - Alpha Release

« on: October 20, 2005, 05:19:40 pm »

I'm sorry to say that this isn't working very well for me. I'm using the palm_3169ww driver (of course).

Some keys don't seem to do anything:

2
w
a
s
z

Some do the wrong thing:

1 registers as 2
TAB registers as q
q registers as w
<, registers /
SPACE registers ^@ (which I assume is a non-printable character, rather than those literal characters)
RSHIFT registers as "
LSHIFT registers as z
CTRL registers as a
ALTGR registers as *

Since I provided the codes for this keyboard, I fear this is my fault. I'm going to see if I can figure out how the keycodes are stored and double-check them.

The primary problem, though, is that once a keypress is registered, unless I press another (working) key almost immediately, the keypress is duplicated endlessly. It's as if I'm holding down the key and key repeat is set very fast. I assume this is because the key release event isn't getting to the OS for whatever reason. I ran the driver in debug mode and it was displaying both keydown and keyup events, so the driver is clearly receiving and processing them.

12

Zaurus - pdaXrom / How To Use Vncviewer With Rc11

« on: October 19, 2005, 04:46:05 pm »

vncviewer in the unstable feed doesn't work with RC11 on my 860. This is because its looking for libstdc++.so.5, which is sadly absent. After some fiddling, my man scogan figured out how to get it working.

Make a temp folder to goof around in:

Code: [Select]

mkdir tmp
cd tmp
Get the RC9.1 version of libstdcxx:

Code: [Select]

wget http://mirror1.pdaxrom.org/rc9.1/feed/libstdcxx_5.0.5_armv5tel.ipk
It may be that you could simply use the package manager to install this ipk. We weren't sure that the package would install cleanly and not break stuff, so we extract the needed file manually.

Unpackage the IPK:

Code: [Select]

tar zxvpf libstdcxx_5.0.5_armv5tel.ipk
Now unpackage the data package contained therein:

Code: [Select]

tar zxvpf data.tar.gz
Now copy the relevant file into /usr/lib:

Code: [Select]

cp ./usr/lib/libstdc++.so.5.0.5 /usr/lib
Finally, symlink the file to its appropriate name:

Code: [Select]

ln -s /usr/lib/libstdc++.so.5.0.5 /usr/lib/libstdc++.so.5
Now vncviewer should work!

13

Zaurus - pdaXrom / Pdaxrom Rc11 For Pxa Devices

« on: October 19, 2005, 04:00:29 pm »

Regarding VNCviewer - when I attempt to execute it, I get

"error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory"

FINDing from root confirms that this file is not present in my filesystem.

I'm running RC11 on a C860.

14

Zaurus - pdaXrom / Ratoc Cfu-1 Working!

« on: October 19, 2005, 10:14:04 am »

I found with RC11 I had to rebuild module dependencies before the drivers would load properly. The instructions at the beginning of this thread have been updated to include this step.

15

Zaurus - pdaXrom / Ir Keyboard Drivers - Alpha Release

« on: October 19, 2005, 09:21:11 am »

I've PMed you some key codes for the Palm Universal Wireless Keyboard.

Thanks for your swell work on this!