NW   NE
 

Corrections and Comments: Brian Tipton
 
SW   SE
NW   NE
 
Howtos

Upgrading The ROM

Connectivity
Wireless 802.11b

Linux Connectivity
Generic (USB)
Debian (USB)
Red Hat < 9 (USB)
Red Hat 9+ (USB)
Suse (USB)
Mandrake (USB)
Generic (PPP USB)
Generic (PPP Serial)

Windows Connectivity
Win2K (Serial)
Win98se (Serial)
WinMe Over (Serial)
WinNTSP6 (Serial)
WinXP Over (Serial)

Developing
DTM database
Compiler Setup
Compiling the Kernel
Special Considerations
Checklist
System Layout
Application Help Files
IPKG Howto
Buzzer Howto
Led Howto
IrDa Howto
Audio Howto
Fullscreen Howto
Resume Event
Keys
Turning off the screen

Syncing
Linux
Win2K
Wireless

Other
Wireless Comparison
The Z Boot Process
Ipv6 Setup
Servers Setup
SD And CF FAQ
Setting Up A Feed
Converting TTF fonts
Building a ROM
MPEG Encoding

Downloads
ZaurusZone Feed
Links
 
SW   SE
NW   NE
 

(c) Harold Martin 2003
Released into the public domain.

* Additional comments by Jim Weir

There are a a few things you need to get this to work:
  • make, gcc, and friends
  • The kernel sources. ie. if you're on an i386 RedHat 9 system you would want the "kernel-source-2.4.20-13.9.i386.rpm" package.
    Note1: You won't actually have to build the kernel, you just need the sources to compile against.
    Note2: Make sure your kernel and your kernel sources are the same version, otherwise this won't work!
  • The usbnet-standalone tarball.
After unzipping and untarring the usbnet-standalone tarball, cd into usbnet-standalone and type:
make && make install

If there are any errors (or anything that looks like an error) at this point email me and I'll try to help you.

There are some conflicts between usbnet and other USB modules. Make sure usbndet and CDCEther are not loaded by typing:
rmmod usbdnet
rmmod CDCEther


* To prevent conflicting modules from loading type:
echo CDCEther >> /etc/hotplug/blacklist
echo acm >> /etc/hotplug/blacklist

Now run: modprobe usbnet
It should run without any complaints.

Make sure the cradle is connected and put the Zaurus into it.
If you run tail -f /var/log/messages you should see messages about USB devices.

Now to add the Z as a network device run: (see Automation below)
ifconfig usb0 192.168.129.1 netmask 255.255.255.0 up
route add -host 192.168.129.201 usb0

You should now be able to ping 192.168.129.201 and see the Z!

From here you can treat the Z as you would any other network device and mount it's Samba share, install FTP or SSH onto it, etc.

I would have never known any of this were it not for Michael Torrie teaching me. Thanks Michael!!
Make sure the Z doesn't suspend while you're using it. The best way to avoid this is to make sure the cradle is always plugged in

* Automation scripts by Jim Weir:
in /etc/sysconfig/network-scripts/ifcfg-usb0 (make this script)

DEVICE=usb0
BOOTPROTO=static
BROADCAST=192.168.129.255
IPADDR=192.168.129.1
NETMASK=255.255.255.0
NETWORK=192.168.129.0
NOZEROCONF=yes

open the file /etc/hotplug/net.agent near the end, insert the following bold lines

.
.
.
esac
mesg $1 $ACTION event not handled
;;

unregister)
case $INTERFACE in
usb0)
debug_mesg bringing down $INTERFACE
exec /sbin/modprobe -r usbnet
esac
exit 0 ;;


*)
debug_mesg NET $ACTION event not supported
exit 1 ;;

esac
 
SW   SE

    This page was last updated: July 24 2003 18:36:49.