Has any one managed to sync their Zaurus with 9.0 and Qtopia desktop, or anything else for that matter. I gave up on 8.2 after following the SuSE knowlagebase instructions. When the zaurus is first attached by USB 9.0 trys to configure it as a modem. I am sure there is a way. Some step by step instructions would be very helpful. Nick
Am Son, 2003-11-02 um 10.43 schrieb nick murphy:
Has any one managed to sync their Zaurus with 9.0 and Qtopia desktop, or anything else for that matter. I gave up on 8.2 after following the SuSE knowlagebase instructions. When the zaurus is first attached by USB 9.0 trys to configure it as a modem. I am sure there is a way. Some step by step instructions would be very helpful.
Nick
hi nick,
i send you a detailed answer via PM
regards
--
Peter Thill
Peter Thill wrote:
Am Son, 2003-11-02 um 10.43 schrieb nick murphy:
Has any one managed to sync their Zaurus with 9.0 and Qtopia desktop, or anything else for that matter. I gave up on 8.2 after following the SuSE knowlagebase instructions. When the zaurus is first attached by USB 9.0 trys to configure it as a modem. I am sure there is a way. Some step by step instructions would be very helpful.
Nick
hi nick,
i send you a detailed answer via PM
regards
Thanks Peter. But as I don't read German it is not much use. It also suggests recomplieing the kernel at the begining. I know it is possible without this now. Any other suggestions out there? Nick
On Sunday 02 November 2003 5:24 am, Peter Thill wrote:
Am Son, 2003-11-02 um 10.43 schrieb nick murphy:
Has any one managed to sync their Zaurus with 9.0 and Qtopia desktop, or anything else for that matter. I gave up on 8.2 after following the SuSE knowlagebase instructions. When the zaurus is first attached by USB 9.0 trys to configure it as a modem. I am sure there is a way. Some step by step instructions would be very helpful.
Nick
hi nick,
i send you a detailed answer via PM
regards -- Peter Thill
NO!!! PLEASE send it to the list! What's the big secret? Don't feel like sharing today? Thanks you very much, Stan
Am Son, 2003-11-02 um 17.18 schrieb Stan Glasoe:
On Sunday 02 November 2003 5:24 am, Peter Thill wrote:
Am Son, 2003-11-02 um 10.43 schrieb nick murphy:
Has any one managed to sync their Zaurus with 9.0 and Qtopia desktop, or anything else for that matter. I gave up on 8.2 after following the SuSE knowlagebase instructions. When the zaurus is first attached by USB 9.0 trys to configure it as a modem. I am sure there is a way. Some step by step instructions would be very helpful.
Nick
hi nick,
i send you a detailed answer via PM
regards -- Peter Thill
NO!!! PLEASE send it to the list! What's the big secret? Don't feel like sharing today?
hi stan,no thats no secret. the thing is taht i save the whole page from the net and this isn't possible to send it to the list. Also i didn't know the URL anymore :-( If you're intreasted i'll send the page to you but remember that the page is in german and i don't have the possibilito for translating :-( Sorry for that
Thanks you very much, Stan
--
Peter Thill
Am Son, 2003-11-02 um 10.43 schrieb nick murphy:
Has any one managed to sync their Zaurus with 9.0 and Qtopia desktop, or anything else for that matter. I gave up on 8.2 after following the SuSE knowlagebase instructions. When the zaurus is first attached by USB 9.0 trys to configure it as a modem. I am sure there is a way. Some step by step instructions would be very helpful.
Nick
Hi, to everyone
heres the URL:
http://www.teamlinux.de/twiki/bin/view/Main/ZaurusLinuxUSB
As i told the page is in german. And i don't have the possibility to
translate :-(
The only thing you need is the topic 'SuSE 8.1' this is also valid for
the 8.2 and the 9.0 :-)
regards
--
Peter Thill
On Sun, 2003-11-02 at 03:43, nick murphy wrote:
Has any one managed to sync their Zaurus with 9.0 and Qtopia desktop, or anything else for that matter. I gave up on 8.2 after following the SuSE knowlagebase instructions. When the zaurus is first attached by USB 9.0 trys to configure it as a modem. I am sure there is a way. Some step by step instructions would be very helpful.
Nick
Hi Nick and others!
It's been a while since I've had to set mine up, but here goes...
First, you have to have the Zaurus plugged in and turned on and the
right module loaded...
usbdnet
This is the one that actually works, and I think you may have to d/l it
from somewhere... I can't actually remember if I had to or not w/8.2??!
:(
Also, there's a problem with other modules that think they should be the
ones loaded... you'll have to list them in the "/etc/hotplug/blacklist"
file. I listed mine after the "de4x5" entry (already there) because the
rest in my list are "network" related, so I stuck them here with the
other one. (made sense to me...) These are the three that kept giving me
fits...
# tulip ... de4x5, xircom_tulip_cb, dmfe (...) handle same devices
de4x5
CDCEther
acm
usbnet
Anyway, once you get it loaded, you should be able to run a simple
script as root
(I have mine called "zaurus.sh" in my /root directory so I "su -" and
"./zaurus" and presto it's up)
-------------------------------------------------
#!/bin/bash
ifconfig usb0 192.168.129.1 broadcast 192.168.129.255 netmask 255.255.255.0 up
route add -host 192.168.192.201/32 gw 192.168.129.1 usb0
-------------------------------------------------
This will configure your "usbdnet" with the right interface settings for
the Zaurus.
I never could get the regular "hot-plug" solutions to work for me.
Plugging mine it gets me the two beeps, but it never brought up my
interface settings correctly. :( So, I cheat and use this little
script.
If you get your "hot-plug" solution to work, please share it with me!
I plug in my Zaurus, hit the sync button, "su -" and run the zaurus.sh
script, and then fire up Qtopia Desktop. Also works for Multisync.
HTH,
--
Travis Owens
On Wednesday 05 November 2003 02:25, Travis Owens wrote:
It's been a while since I've had to set mine up, but here goes...
First, you have to have the Zaurus plugged in and turned on and the right module loaded...
usbdnet
This is the one that actually works, and I think you may have to d/l it from somewhere... I can't actually remember if I had to or not w/8.2??!
:(
Also, there's a problem with other modules that think they should be the ones loaded... you'll have to list them in the "/etc/hotplug/blacklist" file. I listed mine after the "de4x5" entry (already there) because the rest in my list are "network" related, so I stuck them here with the other one. (made sense to me...) These are the three that kept giving me fits...
# tulip ... de4x5, xircom_tulip_cb, dmfe (...) handle same devices de4x5 CDCEther acm usbnet
Anyway, once you get it loaded, you should be able to run a simple script as root
(I have mine called "zaurus.sh" in my /root directory so I "su -" and "./zaurus" and presto it's up) ------------------------------------------------- #!/bin/bash
ifconfig usb0 192.168.129.1 broadcast 192.168.129.255 netmask 255.255.255.0 up
route add -host 192.168.192.201/32 gw 192.168.129.1 usb0 -------------------------------------------------
This will configure your "usbdnet" with the right interface settings for the Zaurus.
I never could get the regular "hot-plug" solutions to work for me. Plugging mine it gets me the two beeps, but it never brought up my interface settings correctly. :( So, I cheat and use this little script.
If you get your "hot-plug" solution to work, please share it with me!
I plug in my Zaurus, hit the sync button, "su -" and run the zaurus.sh script, and then fire up Qtopia Desktop. Also works for Multisync.
HTH, -- Travis Owens
Okay, I'm having some difficulty here - could be that I'm not that clever. We'll see. Likewise, when I plug my Z5500 into SuSE9.0(sans USB hub,) suseplugger thinks it's a modem. Okay, cancel out of that. Anyway, I make the additions to /etc/hotplug/blacklist, make sure that usbnet is loaded, plug it in, get a beep (happy,) then I run Travis' script. Okay here's what usb0 looks like: usb0 Link encap:Ethernet HWaddr 40:00:00:00:FF:08 inet addr:192.168.129.1 Bcast:192.168.129.255 Mask:255.255.255.0 inet6 addr: fe80::4200:ff:fe00:ff08/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:5 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 b) TX bytes:304 (304.0 b) If I try to telnet, ftp or ssh to the Z, I'm connected to the system into which the Z is plugged. As Henry Plantagenet once said, "Surely that's not what I intended." Does anyone have this working between the Z5500 and SuSE9.0? Can someone tell me where I've gone wrong? Remember that I told you I'm not that clever. -- JAY VOLLMER JVOLLMER@CONSOLIDATEDLINT.COM TEXT REFS DOUBLEPLUSUNGOOD SELFTHINK VERGING CRIMETHINK IGNORE FULLWISE
On Fri, 2003-11-07 at 11:53, Jay Vollmer wrote:
Likewise, when I plug my Z5500 into SuSE9.0(sans USB hub,) suseplugger thinks it's a modem. Okay, cancel out of that.
Yeah, I know it thinks this... I'm not sure why, but by default, SUSE detects the ACM before detecting the CDCEther or the usbdnet modules??! It's not relevant anyway, since you're disabling all the bad mods.
Anyway, I make the additions to /etc/hotplug/blacklist, make sure that usbnet is loaded, plug it in, get a beep (happy,) then I run Travis' script.
Excellent!
Okay here's what usb0 looks like: usb0 Link encap:Ethernet HWaddr 40:00:00:00:FF:08 inet addr:192.168.129.1 Bcast:192.168.129.255 Mask:255.255.255.0 inet6 addr: fe80::4200:ff:fe00:ff08/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:5 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 b) TX bytes:304 (304.0 b)
Goodo again!! Ok, can you run "route -n" and give us an example of your route. Should resemble something like this: (relevant to the USB0 device) 192.168.129.201 192.168.129.1 255.255.255.255 UGH 0 0 0 usb0 192.168.129.0 0.0.0.0 255.255.255.0 U 0 0 0 usb0 See, when you connect to the ".201" (the original IP of the Zaurus) the Linux machine automatically knows that you're routing through the ".1" IP of your USB0 device, since the only IP it can connect to, is ".201" NOTE: You're problem may lie in the IP addresses you're using. I'm not saying that you can't use your own addresses, but I *know* for a fact that using the originals work. This is why I still use the originals--they worked when I hooked it up and I still don't have a reason to change. All I need them for currently is to sync.
If I try to telnet, ftp or ssh to the Z, I'm connected to the system into which the Z is plugged.
First, what ports were you trying when accessing these services (telnet: 23 [default] NA [Zaurus], ftp 21 [default] 4242 [Zaurus], ssh 22 [default] 22 [Zaurus], sftp 22 [default] 4243 [Zaurus]) The Zaurus is not setup as a standard Linux machine. It's been highly customized, so we have to conform to those standards.
Remember that I told you I'm not that clever.
It doesn't take a clever person to run anything, just someone that's
been instructed! You can do it!
Contact me again if you need more help!
--
Travis Owens
participants (6)
-
Jay Vollmer -
nick murphy -
Peter Thill -
Stan Glasoe -
Terence McCarthy -
Travis Owens