Yesterday I bought the SL-C3000 here in Japan and took it home. I've been trying ever since to connect to it (by USB) from my desktop Suse 9.2 to copy files to it. Also being able to synchronize would be nice. Can anybody point me in the right direction? Have to use USB for the moment as wireless lan cards for the C3000 are "sold out" at this moment here (have tried all stores in my neighborhood, am bidding on a card on an auction right now, but this will take another 4 days).
All help is appreciated!
Robert
[div align=\"right\"][a href=\"index.php?act=findpost&pid=59314\"][{POST_SNAPBACK}][/a][/div]
Hi I am glad that people are using SuSE 9.2. It is very well put together in my opinion. Anyways, the first thing you need to do is make sure that your firewall is disabled via YaST. This is required because the YaST Firewall configuration GUI is not robust enough to handle what you would need to do to configure your connection with the Zaurus, and it just eliminates another variable during testing your connection.
Second, you need to create a file in in /etc/sysconfig/network/ called ifcfg-usb0. This file should contain the following:
BOOTPROTO='static'
BROADCAST='192.168.129.255'
IPADDR='192.168.129.1'
MTU=''
NETMASK='255.255.255.0'
NETWORK='192.168.129.0'
REMOTE_IP=''
STARTMODE='hotplug'
UNIQUE=''
The ifcfg-usb0 file is what allows the hotplug component to bring up your virtual ethernet device using the usbnet kernel module (the module that is used to do TCP/IP over USB, which is how the Zaurus works).
Third, you need to go to the "PC Link" application on your Zaurus. It is usually under the "Settings" tab. Once in "PC Link", you want to make sure the the Zaurus hostname is set to "zaurus" (without the quotes) and that the USB IP address of the Zaurus is set to "192.168.129.201" (without the quotes). You also want to make sure that the proper connection type is selected. The "USB - TCP/IP (advanced)" option, should be the connection option that is selected in the drop down list for connection type. If it is NOT then SELECT it.
Fourth, exit the "PC Link" application by tapping the "OK" button. At this point both your Zaurus and your SuSE 9.2 box are ready to meet, .
Open a terminal and as super user run the following:
# tail -f /var/log/messages
The above command will show you the content of the log file as it changes, the messages file gets the output from the kernel, modules and such. Hence, it will allow us to see the hotplug system detecting the Zaurus.
Plug your EMPTY Zaurus cradle into a working USB port on your SuSE 9.2 box. Note: You will not see anything happen in the /var/log/messages tail yet because the cradle isn't the device, the cradle is basically just a spiffy wire that holds and connects to the Zaurus rather than just connecting to it.
Take your Zaurus (in powered OFF state) and place it fully into the cradle. Note: You still won't see anything in the /var/log/messages tail yet because your Zaurus is off.
Turn on your Zaurus (leaving it in the cradle). You sould see in the /var/log/messages tail something similar to the following:
Jan 24 09:42:57 waddler kernel: usb 2-1: new full speed USB device using address 2
Jan 24 09:42:57 waddler kernel: usb 2-1: Product: SL-5600
Jan 24 09:42:57 waddler kernel: usb 2-1: Manufacturer: Sharp
Jan 24 09:43:04 waddler kernel: usb0: register usbnet at usb-0000:00:11.3-1, Sharp Zaurus, PXA-2xx based
Jan 24 09:43:04 waddler kernel: usbcore: registered new driver usbnet
Jan 24 09:43:25 waddler kernel: usb0: no IPv6 routers present
The first line is the usb kernel portion recognizing the Zaurus as a full speed USB device and identifying what address it is using. In your case this should happen but the address will most likely be different.
The second and third line is the usb kernel portion outputing its Product and Manufacturer information. I assume that in your case it will match SL-C3000 (or the variant that it is under the plastic, lol) with Sharp as the manufacturer.
The fourth line and fifth are very important, They are showing that the usb0 device is being registered to the usbnet kernel module. This is basically showing that the hotplug system detected your Zaurus and then loaded the usbnet driver for it. The fifth line is showing that the usbcore kernel module recognized and registered the usbnet driver.
The sixth line is just some output complaining because I don't have IPv6 setup, and I assume that neither do you if you are using a stock install of SUSE 9.2.
At this point you should now run the following as super user to check if the driver was loaded properly and the device configured properly:
# /sbin/ifconfig usb0
You should see the following:
usb0 Link encap:Ethernet HWaddr 4E:40:D8:21:ED:EB
inet addr:192.168.129.1 Bcast:192.168.129.255 Mask:255.255.255.0
inet6 addr: fe80::4c40:d8ff:fe21:edeb/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:44 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6075 (5.9 Kb) TX bytes:484 (484.0
This shows that the hotplug system used the /etc/sysconfig/network/ifcfg-usb0 file to configure the device for you automatically when the device was found.
Now, EXIT super user mode and run the following:
$ netstat -rn
You should see a line in the output that looks as follows:
192.168.129.0 0.0.0.0 255.255.255.0 U 0 0 0 usb0
This shows that the hotplug system used the /etc/sysconfig/network/ifcfg-usb0 file to configure your routing tables so that the IP packets are routed to the proper devices for the proper address. In this case it shows that the 192.168.129 class C address family is routed out the usb0 device which is correct.
K, now that we see that everything that we wanted to happen automatically has we can do our first real test. Now that everything seems to be set up correctly we want to see if we can ping the Zaurus and get in echo response back, proving that our network connection over USB is working as it should.
Run the following (as a normal user):
$ ping 192.168.129.201
You should see output similar to the following:
PING 192.168.129.201 (192.168.129.201) 56(84) bytes of data.
64 bytes from 192.168.129.201: icmp_seq=1 ttl=255 time=75.3 ms
64 bytes from 192.168.129.201: icmp_seq=2 ttl=255 time=16.9 ms
64 bytes from 192.168.129.201: icmp_seq=3 ttl=255 time=6.01 ms
64 bytes from 192.168.129.201: icmp_seq=4 ttl=255 time=7.93 ms
64 bytes from 192.168.129.201: icmp_seq=5 ttl=255 time=24.0 ms
64 bytes from 192.168.129.201: icmp_seq=6 ttl=255 time=11.8 ms
As you can see I sent 6 pings and got back 7 echos. You should see similar. To stop the ping press Ctrl-C in the terminal window you are running the ping in. The time just shows the unit of time which it took to get an echo back for each ping packet.
If you got output that looked similar to the above then you are good and you are ready to use this connection to do what ever you want.
If you are interested in a method to move files to the Zaurus may I suggest using Samba. The Zaurus comes running Samba already so all you have to do is open up Konqueror and type the following in the URL entry area:
smb://192.168.129.201/
That should provide you with a nice method of transfering files to and from the Zaurus. At least it did in SUSE 9.1 I have yet to try it with SUSE 9.2 but I would assume that it work the same.
If you are interested in a method to synchronize your PIM (Personal Information Management) data from your Zaurus to your SUSE 9.2 box may I suggest you use "zync" and "zync-gui". They are tools provided by the Zaurus Synchronization Repository (
http://zsrep.sourceforge.net). Note: They are in testing phase still so don't expect a totally solid product, however the applications need testers for them to become solid products, so why not you, .
Anyways, I hope that pushed you in the proper direction. I am sick of typing, hence am going to stop now .
