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.


Messages - zahnoliv

Pages: [1]
1
6000 - Tosa / mounting the SL-6000
« on: November 26, 2004, 06:20:56 pm »
Concerning establishing the connection with dhcpcd (standard in Suse): Arcmeanvil, thanks, the script you submitted works great.

Concerning the alternative client dhclient (used by other distributions): MeaninglessNick, if I comment out the line in dhclient.conf, it also works. Thanks you especially for your patience!

I can now use the network to transfer files with samba or connect with ssh.

2
6000 - Tosa / mounting the SL-6000
« on: November 25, 2004, 02:43:29 pm »
Arcmeanvil, thanks for the suggestion, I'll try it out as soon as I get back to my pc.

MeaninglessNick, you mentioned that the package length is not a problem, but seem to think I could establish a connection. How can I use it though? I tried to use samba or ping or ssh to 192.168.129.201, but without success.

Thanks

3
6000 - Tosa / mounting the SL-6000
« 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...
 

4
6000 - Tosa / mounting the SL-6000
« 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?

5
6000 - Tosa / mounting the SL-6000
« 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"?

6
6000 - Tosa / mounting the SL-6000
« 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.

7
6000 - Tosa / mounting the SL-6000
« 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.

8
6000 - Tosa / Communicating Between The 6000 And A Linux Pc
« on: November 22, 2004, 04:17:15 pm »
Hello Nick,

thanks for pointing this out. Unfortunately in this case I'm support.using Suse 8.0.
modprobe usbnet gave no result. I don't know how I can rebuilt my kernel to include usbnet support.

Can you imagine alternatives to using Debian?

9
6000 - Tosa / Communicating Between The 6000 And A Linux Pc
« on: November 22, 2004, 02:49:51 pm »
This is a follow-up to an earlier post I made, titled "mounting the SL-6000".

I'm interested in communicating between my laptop and the Zaurus via USB. The former is running Suse Linux 8.0.  I understand now (thanks to lumi) that the Zaurus is not treated as USB storage, so I can not simply mount it.

Following the advice I tried to establish a network with Samba. When I calll smb://192.168.129.201/home/ from Konqueror, it gives me the message "Protocol not supported".

How can I transfer files between the Zaurus and other Linux computers, maybe without using Samba?

Thanks for any experience sharing

10
6000 - Tosa / mounting the SL-6000
« 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

11
6000 - Tosa / mounting the SL-6000
« 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

12
6000 - Tosa / USB Adaptor & Cables
« on: November 19, 2004, 06:20:12 pm »
Where on the iriver site do you find the host adapter?

13
6000 - Tosa / mounting the SL-6000
« 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!

Pages: [1]