Author Topic: mounting the SL-6000 (Read 5476 times)

zahnoliv · « **on:** November 19, 2004, 05:28:48 pm »

Instead of synchronizing and copying new files to my Zaurus from the Windows part of my laptop, I've been trying to mount the SL-6000 from my Linux partition. Different from other usb devices I can mount (digital camera, storage), the pc doesn't seem to recognize the connected Zaurus. There appears no new entry in /etc/fstab or /etc/mtab.

Help from somebody who has suceeded mounting the Zaurus on Linux would be greatly appreciated!

guylhem · « **Reply #1 on:** November 19, 2004, 08:42:31 pm »

Done that. but it cause the graphical interface on the zaurus to restart.
still interested?

lumi · « **Reply #2 on:** November 20, 2004, 02:30:28 am »

Quote

I've been trying to mount the SL-6000 from my Linux partition.

Which Linux distribution / version are you using?

It sounds like you think it should be treated like USB storage on your Linux but I don't know why you think so. Nothing is automatic.

Dave

zahnoliv · « **Reply #3 on:** November 21, 2004, 12:11:57 am »

Guylhem, yes, I'd be still interested. Is it a problem if the graphical interface restarts?

Lumi, I'm using Suse Linux 8.1. Do you think there's a way to mount the device? I took for granted that new usb devices are detected if they are attached.

Thanks for replying you both,

Oliver

lumi · « **Reply #4 on:** November 21, 2004, 01:18:47 am »

It may help if you understand that the Zaurus (SL-6000L) is _not_ a usb-storage device like a flash drive. It is like a laptop itself which you can connect over a USB network (or wireless if you prefer). The Zaurus has built-in Samba (Windows network disk-sharing) capability.

If you setup the PC Link in the Settings tab to "USB-TCP/IP (advanced)". When you hook up the Z and turn it on (well, resume it), then it should make a network with your laptop over the USB cable. The Z's IP address is 192.168.129.201. I was able to mount the Z onto my PC or access the Z from Konqueror. From Konqueror: smb://192.168.129.201/home/. My current experience is based on Mandrake 9.2/10.0/10.1.

If you have a problem setting up USB networking on your laptop check out the "Linux" forum on this board. There is previous discussion there.

I have seen some modules to allow your Z to look like a usb-storage device but I haven't been successful getting it working -- but I have Samba....

Dave

zahnoliv · « **Reply #5 on:** November 21, 2004, 05:07:02 pm »

Hello Dave,

I don't seem to be successful in setting up a network.
I set the connection type to "USB - TCP/IP (advanced)", then I launched "Sync
Start", but am not able to communicate (ping, ssh) to 192.168.129.201.
Later the Zaurus gives me the error message "Communication was aborted".

I tried to do it with konqueror, as you recommended, calling
smb://192.168.129.201/home/
Konqueror gives me the message "Protocol not supported".

Also I didn't find information addressing my problem on the Linux section of
this portal. Do you remember where exactly you saw this?

Oliver

zahnoliv · « **Reply #6 on:** November 23, 2004, 05:43:40 pm »

I installed Suse 9.1, in the hope that would work better. I'm still not successful establishing a Samba network. PC Link at the Zaurus is at TCP/IP, and when I dial
smb://192.168.129.201/home/
in Konqueror
the wheel keeps turning for 10 minutes before the browser gives an error message "Network is unreachable".

I'm not sure whether the samba network is automatically established.

MeaninglessNick · « **Reply #7 on:** November 24, 2004, 07:39:39 am »

Can you give us the output of the following commands (as root) on the desktop

modprobe usbnet

ifconfig usb0 up

dhclient usb0

One thing is that you apparently have to use dhcp to set the IP address on the desktop or
the Zaurus won't talk to it.

zahnoliv · « **Reply #8 on:** November 24, 2004, 12:04:59 pm »

The outputs of modprobe, ifconfig, and dhclient are

---
# modprobe usbnet
# ifconfig usb0 up
usb0: unknown interface: No such device
# dhclient usb0
sit0: unknown hardware address type 776
sit0: unknown hardware address type 776
Bind socket to interface: No such device
exiting.
---

> One thing is that you apparently have to use dhcp to set the IP address on the desktop or
> the Zaurus won't talk to it.

How do I have do this?

Thanks in advance.

MeaninglessNick · « **Reply #9 on:** November 24, 2004, 12:53:14 pm »

Is the zaurus in the cradle and on? My cradle is at the office, so I can't test, but from memory the second step should work.

An interface (i.e. usb0) is sortof like a magical file that should appear (although not in a directory) when the kernel and the hardware are communicating.

If you look at the kernel log (using dmesg) you should see a line like

Quote

usb0: register usbnet at usb-0000:00:1d.1-2, Sharp Zaurus, PXA-2xx based

when the Z is plugged into the cradle

The dhclient command should get an IP address from the Z, but it won't work unless the second step does.

zahnoliv · « **Reply #10 on:** November 24, 2004, 02:22:08 pm »

I put the Zaurus again in the cradle and executed

# modprobe usbnet
# ifconfig usb0 up

After that the last lines of the kernel log look like this:

---
usb 1-2: new full speed USB device using address 5
usb 1-2: Product: SL-6000
usb 1-2: Manufacturer: Sharp
usb0: register usbnet at usb-0000:00:1d.0-2, Sharp Zaurus, PXA-2xx based
---

But then dhclient usb0 leads to:

---
sit0: unknown hardware address type 776
sit0: unknown hardware address type 776
Listening on LPF/usb0/16:fe:56:f8:67:64
Sending on LPF/usb0/16:fe:56:f8:67:64
Can't bind to dhcp address: Address already in use
Please make sure there is no other dhcp server
running and that there's no entry for dhcp or
bootp in /etc/inetd.conf. Also make sure you
are not running HP JetAdmin software, which
includes a bootp server.
---

and I can not establish a connection with samba.
I don't understand the hints given by the dhclient. What could be meant by "Address already in use"?

MeaninglessNick · « **Reply #11 on:** November 24, 2004, 04:02:02 pm »

Quote

and I can not establish a connection with samba.
I don't understand the hints given by the dhclient. What could be meant by "Address already in use"?

Every server (in the sense of running program) on the internet has a host address and one or more port numbers (i.e. 80, http servers).
It seems to be claiming that some other server is running on your host with port 67 or 68.

If you run

netstat -l | grep bootp

It should come up blank. Otherwise you need to find the server; the rest of the hints give you
candidates.

zahnoliv · « **Reply #12 on:** November 24, 2004, 04:16:29 pm »

Netstat gives the following

# netstat -l | grep bootp
udp 0 0 *:bootpc *:*

so should calling

smb://192.168.129.201/home/

work?

MeaninglessNick · « **Reply #13 on:** November 24, 2004, 04:36:24 pm »

No, nothing will work until you get dhclient working.

thie output from netstat means there is most likely another instance of dhclient running. You can confirm this by running

Code: [Select]

netstat -l -p | grep bootp
The last column gives you the pid and command name of whatever is using that port.

You could just kill that process, but chances are you may need to reboot (well, really just restart the daemon)
after your experiments.

If you do kill it, then you can try running dhclient.

At this point I think you probably need how Suse sets up their networking.

zahnoliv · « **Reply #14 on:** November 24, 2004, 05:39:09 pm »

Suse 9.1 has a different dhcp client running, called dhcpcd. In my configuration eth0 is configured with that. I can't find out how to add usb0.

So I took the other route and killed dhcpcd. Then I used dhclient. The result is this:

Code: [Select]

# dhclient usb0
Internet Software Consortium DHCP Client V3.0.1rc13
Copyright 1995-2002 Internet Software Consortium.
All rights reserved.
For info, please visit [URL=http://www.isc.org/products/DHCP]http://www.isc.org/products/DHCP[/URL]

sit0: unknown hardware address type 776
sit0: unknown hardware address type 776
Listening on LPF/usb0/be:01:1c:1c:3c:70
Sending on   LPF/usb0/be:01:1c:1c:3c:70
Sending on   Socket/fallback
DHCPDISCOVER on usb0 to 255.255.255.255 port 67 interval 5
ip length 328 disagrees with bytes received 332.
accepting packet with data after udp payload.
DHCPOFFER from 192.168.129.201: no domain-name-servers option.
DHCPDISCOVER on usb0 to 255.255.255.255 port 67 interval 7
ip length 328 disagrees with bytes received 332.
accepting packet with data after udp payload.
DHCPOFFER from 192.168.129.201: no domain-name-servers option.
DHCPDISCOVER on usb0 to 255.255.255.255 port 67 interval 14
ip length 328 disagrees with bytes received 332.
accepting packet with data after udp payload.
DHCPOFFER from 192.168.129.201: no domain-name-servers option.
DHCPDISCOVER on usb0 to 255.255.255.255 port 67 interval 9
ip length 328 disagrees with bytes received 332.
accepting packet with data after udp payload.
DHCPOFFER from 192.168.129.201: no domain-name-servers option.
DHCPDISCOVER on usb0 to 255.255.255.255 port 67 interval 7
ip length 328 disagrees with bytes received 332.
accepting packet with data after udp payload.
DHCPOFFER from 192.168.129.201: no domain-name-servers option.
DHCPDISCOVER on usb0 to 255.255.255.255 port 67 interval 13
ip length 328 disagrees with bytes received 332.
accepting packet with data after udp payload.
DHCPOFFER from 192.168.129.201: no domain-name-servers option.
DHCPDISCOVER on usb0 to 255.255.255.255 port 67 interval 6
ip length 328 disagrees with bytes received 332.
accepting packet with data after udp payload.
DHCPOFFER from 192.168.129.201: no domain-name-servers option.
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

I'm not sure what it means...

News:

Author Topic: mounting the SL-6000 (Read 5476 times)