next up previous Link to 'computer' page
Next: Synchronisation and file transfer Up: Zaurus pocket-computer Previous: Zaurus pocket-computer

Linux operating system issues

I connect my Zaurus to my Linux computer with the USB connection. Instructions on how to do this are in the Ethernet over USB Howto, and can also be found at the Sharp Developer website. More information can be found if you run `susehelp' or access the on-line SuSE database at the SuSE website. Using susehelp, type 'zaurus' as a query. When re-compiling the kernel, some options need to be set. To quote the Howto...

in "Code maturity level options",

select "Prompt for development and/or incomplete code/drivers"

in "USB support", section "USB Network adaptors",

select (as a module) "USBD Network (Encapsulated) Host-to-Host Link (EXPERIMENTAL)"

Then enter 04dd in USBD Network idVendor and 8004 in USBD Network idProduct

The last option needs to be set when compiling the kernel modules, since the default value is 0000. The 'susehelp' claims that these values do not need to be set.

Note, I have become aware that if you are using SuSE 9.0 or later, which apparantly uses kernel version 2.4.21 or later, the preference is to use USBnet, rather than USBDnet. For futher details see Linux Connectivity FAQ at ZaurusUserGroup.

The 'Ethernet over USB Howto' instructs that the configuration files /etc/sysconfig/hotplug and /etc/sysconfig/network/ifcfg-usb0 need to be modified or created. In my situation, these files were already created or modified before I updated SuSE from 8.0 to 8.2.

Susehelp also suggests disabling CDCEther (which provides an old version of the Zaurus-Linux connection), and some other options. I do not know what the susehelp is talking about when it suggests using 'yast2 lan'.

I also modified /etc/hotplug/usb.handmap. The purpose of this file is described in Chapter 8 of the SuSE8.2 administration guide (p. 223 Hotplugging Services - USB). If you look at the Ethernet over USB howto you will find mention, under the Mandrake section, about changing /lib/modules/2.4.20-w4l/modules.usbmap (2.4.20-w4l is my kernel name, your kernel name might be '2.4.20-4GB'). I needed to do this change as well, to have my Zaurus auto-detected. However, manual changes to the 'modules.usbmap' file are not permanent, as the howto notes. The solution is to add the lines to /etc/hotplug/usb.handmap. In my case, I added four lines...

# Zaurus SL5500

usbdnet 0x0003 0x04dd 0x8004 0x0000 0x0000 0x02 0x00 0x00 0x02 0x06 0x00 0x00000000

usbdnet 0x0003 0x04dd 0x8004 0x0000 0x0000 0x02 0x00 0x00 0xff 0x01 0x00 0x00000000

usbdnet 0x0003 0x04dd 0x8004 0x0000 0x0000 0x02 0x00 0x00 0x00 0x00 0x00 0x00000000

Note that I added several lines to /etc/hotplug/usb.handmap, but perhaps only one line starting with

usbdnet 0x0003 0x04dd ...
may be necessary. Also note the warning at the beginning of the /etc/hotplug/usb.handmap. Include NO punctuation in any comment lines that you add to /etc/hotplug/usb.handmap.

On my ASUS A7V333 motherboard, the Zaurus appears to be recognised more easily if its USB cable is attached to the USB 1.1 ports, rather than the USB 2.0 ports.


next up previous Link to 'computer' page
Next: Synchronisation and file transfer Up: Zaurus pocket-computer Previous: Zaurus pocket-computer
David Pat Shui Fong 2007-05-31