Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - g33k

Pages: [1]
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?

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:


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:


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.

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, 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]
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/ /usr/lib
Finally, symlink the file to its appropriate name:

Code: [Select]
ln -s /usr/lib/ /usr/lib/
Now vncviewer should work!

Zaurus - pdaXrom / Usb Bluetooth / Ratoc Cfu-1
« on: June 20, 2005, 01:02:09 pm »
The humorum Ratoc CFU-1 driver has associated modules that ostensibly support, among other things, USB Bluetooth adaptors. I have an Orange Micro Blue2 adaptor I'd love to get working.

When I modprobe the bluetooth module and plug in the Blue2, dmesg says:

hub.c: USB new device connect on bus1/1, assigned device number 4
bluetooth.c: found interrupt in
bluetooth.c: found bulk out
bluetooth.c: found bulk in
bluetooth.c: USB Bluetooth converter detected
bluetooth.c: Bluetooth converter now attached to ttyUB0 (or usb/ttub/0 for devfs)
bluetooth.c: usb_bluetooth_probe - improper number of endpoints. Bluetooth driver not bound.
bluetooth.c: usb_bluetooth_probe - improper number of endpoints. Bluetooth driver not bound.
bluetooth.c: usb_bluetooth_probe - improper number of endpoints. Bluetooth driver not bound.
bluetooth.c: usb_bluetooth_probe - improper number of endpoints. Bluetooth driver not bound.
bluetooth.c: usb_bluetooth_probe - improper number of endpoints. Bluetooth driver not bound.
bluetooth.c: usb_bluetooth_probe - improper number of endpoints. Bluetooth driver not bound.
bluetooth.c: usb_bluetooth_probe - improper number of endpoints. Bluetooth driver not bound.

There is a device at /dev/usb/ttub/0; if I cat /dev/usb/ttub/0 I don't get the "no such file or directory" message, so it seems as if it is to some degree working.

I cannot figure out what to do next, though. I'd sure appreciate it if someone could point me in the right direction.


Zaurus - pdaXrom / Software Request: Wavemon
« on: February 17, 2005, 01:42:38 pm »
I'm trying to get wavemon compiled for pdaXrom to aid in setting up a largish 802.11 network. I'm getting errors in the configure stage (see other thread, "C Compiler Cannot Create Executable"). Has anyone already compiled wavemon? Would anyone with a working development environment be willing to compile it?


Zaurus - pdaXrom / "c Compiler Cannot Create Executable"
« on: February 17, 2005, 10:55:33 am »
When cross-compiling (actually, when running the configure script), I sometimes get an error that says "C Compiler Cannot Create Executable". Does anyone else get this? What does it mean? How do I fix it?


Zaurus - pdaXrom / Ratoc Cfu-1 Working!
« on: February 08, 2005, 11:00:06 am »
After much fiddling around, my friend and I have gotten the Ratoc CFU-1 USB Host card working with RC8. (I assume this would work the same for RC9, but I've not tested it yet.) Here's how:

* Download and install usb-modules and cfu1-driver IPKs

Download Here

* Rebuild module dependencies

Code: [Select]
depmod -a
* Restart pcmcia subsystem

Code: [Select]
/etc/rc.d/init.d/pcmcia restart
* Add mknod entries to startup script; the way we did it is to add the lines below to the /etc/rc.d/rc.sysinit script, just before the line "# set time"

Code: [Select]
mknod /dev/sda b 8 0
mknod /dev/sda1 b 8 1
mknod /dev/sda2 b 8 2
mknod /dev/sda3 b 8 3
mknod /dev/sda4 b 8 4
mknod /dev/sdb b 8 16
mknod /dev/sdb1 b 8 17
mknod /dev/sdb2 b 8 18
mknod /dev/sdb3 b 8 19
mknod /dev/sdb4 b 8 20
mknod /dev/sdc b 8 32
mknod /dev/sdc1 b 8 33
mknod /dev/sdc2 b 8 34
mknod /dev/sdc3 b 8 35
mknod /dev/sdc4 b 8 36

* Symlink the usb script into the /etc/pcmcia directory so cardmgr can find it

Code: [Select]
ln -s /etc/rc.d/init.d/usb /etc/pcmcia/usb
At this point, you should be able to plug the CFU-1 into your Zaurus and have it recognized and all relevant drivers loaded automagically. In order to mount a USB flash drive, you'll first need to load the usb-storage module:

Code: [Select]
modprobe usb-storage
Then you can make a mount point and mount the drive; for example:

Code: [Select]
mkdir /mnt/usbflash
mount -t vfat /dev/sda1 /mnt/usbflash


Edit: I've just set this up with RC10 and it works!

Edit: Instructions altered ever-so-slightly to work with RC11.

Edit: Instructions work fine with RC12.

Zaurus - pdaXrom / Wifi Txpower
« on: January 07, 2005, 12:15:10 pm »
Using a command like

Code: [Select]
iwconfig eth0 txpower 15

Code: [Select]
iwconfig eth0 txpower 30mW
ought to allow one to adjust the power of one's wifi card.

With pdaXrom, I get

"SET failed on device eth0 : Operation not supported."

with both a Symbol LA-4137 and a D-Link DWL(something) in a C-860. In fairness, I've never used the Symbol with any other ROM... but the D-Link was used quite a bit in a 5500 with OpenZaurus and was perfectly happy to adjust it's power level.

The larger issue is that neither the Symbol or the (hellishly powerful) D-Link detect much of anything with Kismet under pdaXrom. Increasing the txpower traditionally solves this problem - or at least helps.

Zaurus - pdaXrom / Manpages? Infopages?
« on: January 07, 2005, 11:52:45 am »
Neither man nor info seems to be available in pdaXrom... is this so? If not, why not? Documentation is way important, particularly for Linux newbies like myself. Everyone tells you to RTFM, yet the FM seems not to be available...

Zaurus - pdaXrom / Trendnet Te-cf100 / Symbol La-4137
« on: December 27, 2004, 10:25:54 pm »
Neither my TRENDnet TE-CF100 wired fast ethernet adaptor nor my Symbol LA-4137 Wireless Networker 802.11 wifi card are recognized by pdaXrom by default. For the benefit of newbies like myself, here's how to get them working:

For the TE-CF100, edit the /etc/pcmcia/config file and add the following lines:

Code: [Select]
card "TRENDnet TE-CF100"
  manfid 0x0149, 0xc1ab
  bind "pcnet_cs"

For the LA-4137, edit the /etc/pcmcia/spectrum.conf file and add the following lines:

Code: [Select]
card "LA4137 Spectrum24 CF WLAN CARD"
  manfid 0x014d, 0x0001
  bind "spectrum_cs"

To make the either of the above changes effective, execute this command:

Code: [Select]
/etc/rc.d/init.d/pcmcia restart
Insert the card, and you should be good to go!

Zaurus - pdaXrom / Ratoc Usb Host
« on: December 20, 2004, 10:12:18 am »
I have the vague understanding that the virtual floating point stuff in the latest pdaXrom kernel prevents the driver from working. The hoopy frood who provides the binary driver here doesn't make the source code available. I've e-mailed him to ask if there's any possibility of his providing an updated version we can use or, failing that, of his sharing the source code so we can try and recompile it. So far, I've received no response from him.

So far, all of the references I've been able to find about using the CFU1 with Linux refer to the above website / driver. I've not found any source code at all.

The Ratoc website refers to this fellow's website, as well.

Is the binary driver really the only possible way to use the Ratoc card (short of trying to hack together a new driver ourselves)?

Is there any way we can get modern pdaXrom distros to work with the binary driver?

How many people have the Ratoc card?

Pages: [1]