OESF Portables Forum
Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Angstrom & OpenZaurus => Topic started by: grog on May 18, 2006, 03:58:49 pm
-
Hi all. I just loaded OZ/GPE 3.5.4 on my boxer (C860) & I can't seem to get my windows 2000 box to recognize that a usb device is attached.
This was formerly working just fine when the Z was running pdaxrom, so I know the windows side should still be ok. I don't see any usb modules when I run lsmod, so I think this might be the problem, but then again, this is with a 2.6 kernel so it might be different than what I'm used to on my old 5600 with the 2.4 kernel.
I _have_ gone into the network settings app & check the usbd0 settings & saved; they look ok to me.
thks in advance.
-
g_ether on Z will give usb0
windows need linux.inf from Linux 2.6 source
-
g_ether on Z will give usb0
I managed to insmod that ok, now windows reconizes a 'RNDIS Ethernet gadget'. the module will stay loaded through reboots now, correct?
windows need linux.inf from Linux 2.6 source[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=127650\")
This is where I'm stumped. I found losts of references through [a href=\"http://www.google.ca/search?hl=en&q=linux.inf+2.6+kernel+source&meta=]google[/url] (here (http://www.handhelds.org/moin/moin.cgi/WindowsXpUsbNetworkHowTo) & here (http://www.mjmwired.net/kernel/Documentation/usb/linux.inf), for example), but none worked; they all asked me to specify the 'usb8023k.sys', which I don't have. Where would you recommend I get the proper linux.inf?
-
I posted it on the forum:
https://www.oesf.org/forums/index.php?showt...169&#entry73169 (https://www.oesf.org/forums/index.php?showtopic=11320&st=30&p=73169&#entry73169)
Si
-
I posted it on the forum:
https://www.oesf.org/forums/index.php?showt...169&#entry73169 (https://www.oesf.org/forums/index.php?showtopic=11320&st=30&p=73169&#entry73169)[div align=\"right\"][a href=\"index.php?act=findpost&pid=127712\"][{POST_SNAPBACK}][/a][/div]
nope, even that one doesn't work. Windows still can't find the usb8023k.sys driver file. I know it's supposed to be in system32/drivers, but nada. These must be XP specific; any idea how to get this to work under 2000?
-
Try something like this: http://www.microsoft.com/whdc/device/network/NDIS/rndis.mspx (http://www.microsoft.com/whdc/device/network/NDIS/rndis.mspx)
I'm guessing that this will have these drivers in it.
Si
-
Try something like this: http://www.microsoft.com/whdc/device/network/NDIS/rndis.mspx (http://www.microsoft.com/whdc/device/network/NDIS/rndis.mspx)[div align=\"right\"][a href=\"index.php?act=findpost&pid=127778\"][{POST_SNAPBACK}][/a][/div]
Close, but no cigar. This package contains usb8023y.sys & rndismpy.sys, but the linux.inf specifies usb8023k.sys & rndismpk.sys. I tried editing the inf & specifying the 'y' files, it loaded ok & the usb device shows up on the taskbar, but there's no connection to be had.
-
Try something like this: http://www.microsoft.com/whdc/device/network/NDIS/rndis.mspx (http://www.microsoft.com/whdc/device/network/NDIS/rndis.mspx)[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=127778\")
Close, but no cigar. This package contains usb8023y.sys & rndismpy.sys, but the linux.inf specifies usb8023k.sys & rndismpk.sys. I tried editing the inf & specifying the 'y' files, it loaded ok & the usb device shows up on the taskbar, but there's no connection to be had.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=127782\"][{POST_SNAPBACK}][/a][/div]
I figured I hadn't had enough frustration, so I'd take another stab at this. I downloaded & extracted what I hoped to be the two proper files from [a href=\"http://www.multimedia.pl/object.php/act/sho/oid/db377597c1def1bf1b788811bf2531c3]this motorola driver package[/url]. Wouldn't you know it, now windows won't forget the 'y' files that it almost 'properly' installed, now I can't get the installer to even look at these ones!!
AAARRGGHH!! I love windows.
I tried uninstalling them, deleting them from the drivers folder, deleting all references to them from the registry. Windows has it in for me, I know it.
The more I work on computers, the more I love my dog.
-
Try something like this: http://www.microsoft.com/whdc/device/network/NDIS/rndis.mspx (http://www.microsoft.com/whdc/device/network/NDIS/rndis.mspx)[div align=\"right\"][a href=\"index.php?act=findpost&pid=127778\"][{POST_SNAPBACK}][/a][/div]
Close, but no cigar. This package contains usb8023y.sys & rndismpy.sys, but the linux.inf specifies usb8023k.sys & rndismpk.sys. I tried editing the inf & specifying the 'y' files, it loaded ok & the usb device shows up on the taskbar, but there's no connection to be had.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=127782\"][{POST_SNAPBACK}][/a][/div]
I had a similar problem; for some reason my Z doesn't like to be connected to the front panel usb connectors, it agrees to work only with the connectors on the back side (those connected directly to the mother board). If you're connected to the front panel that might do the trick.
Good luck,
YoG.
-
I figured I hadn't had enough frustration, so I'd take another stab at this. I downloaded & extracted what I hoped to be the two proper files from this motorola driver package (http://www.multimedia.pl/object.php/act/sho/oid/db377597c1def1bf1b788811bf2531c3). Wouldn't you know it, now windows won't forget the 'y' files that it almost 'properly' installed, now I can't get the installer to even look at these ones!!
I tried uninstalling them, deleting them from the drivers folder, deleting all references to them from the registry. Windows has it in for me, I know it.[div align=\"right\"][a href=\"index.php?act=findpost&pid=128247\"][{POST_SNAPBACK}][/a][/div]
IT'S ACTUALLY WORKING
Well, almost . I managed to find the reference to the 'y' files in the WINNT/inf/oem17.inf & changed them to the proper 'k's. The next time I plugged the Z in it asked for the 'k's so I pointed the installer to the ones from the motorola package & PING! The pc now has not only the proper usb connection indication, but also a network icon. kewl.
But no cheering yet . I change the network settings to the standard static ip (192.168.129.201), 'doze has to reboot (as always. Now I can ping the address but can't login via putty. So this must be the Z's fault. ifconfig shows no usbd0 as I'm used to in OZ (this is with 3.5.4.1.rc4, both e-image-core & gpe-image). So I try a 'ifup usbd0' & I get several 'no such device' errors. I try usb0 (no 'd'), & while the interface comes up fine, it's with a different address. So I change the /etc/network/interfaces ip's for usb0 to match that of usbd0 & while it comes up with the proper address (& I can still ping it), it doesn't allow a ssh connection. Still must be an OZ thing (the root password is set), so can anyone make any suggestions on what I should do?
thks
-
I figured I hadn't had enough frustration, so I'd take another stab at this. I downloaded & extracted what I hoped to be the two proper files from this motorola driver package (http://www.multimedia.pl/object.php/act/sho/oid/db377597c1def1bf1b788811bf2531c3). Wouldn't you know it, now windows won't forget the 'y' files that it almost 'properly' installed, now I can't get the installer to even look at these ones!!
I tried uninstalling them, deleting them from the drivers folder, deleting all references to them from the registry. Windows has it in for me, I know it.[div align=\"right\"][a href=\"index.php?act=findpost&pid=128247\"][{POST_SNAPBACK}][/a][/div]
IT'S ACTUALLY WORKING
Well, almost . I managed to find the reference to the 'y' files in the WINNT/inf & changed them to the proper 'k's. The next time I plugged the Z in it asked for the 'k's so I pointed the installer to the ones from the motorola package & PING! The pc now has not only the proper usb connection indication, but also a network icon. kewl.
But no cheering yet . I change the network settings to the standard static ip (192.168.129.201), 'doze has to reboot (as always. Now I can ping the address but can't login via putty. So this must be the Z's fault. ifconfig shows no usbd0 as I'm used to in OZ (this is with 3.5.4.1.rc4, both e-image-core & gpe-image). So I try a 'ifup usbd0' & I get several 'no such device' errors. I try usb0 (no 'd'), & while the interface comes up fine, it's with a different address. So I change the /etc/network/interfaces ip's for usb0 to match that of usbd0 & while it comes up with the proper address (& I can still ping it), it doesn't allow a ssh connection. Still must be an OZ thing (the root password is set), so can anyone make any suggestions on what I should do?
thks
[div align=\"right\"][a href=\"index.php?act=findpost&pid=128318\"][{POST_SNAPBACK}][/a][/div]
usbd0 is the kernel 2.4 interface, usb0 the 2.6 one.
-
This happy end needs definetely to be put in the wiki...
-
This happy end needs definetely to be put in the wiki...[div align=\"right\"][a href=\"index.php?act=findpost&pid=128329\"][{POST_SNAPBACK}][/a][/div]
I'll be more than willing to do that once there _is_ a final solution .
To recap, I now have my gadget module loaded on the Z & 'ifup usb0' gives me an address of 192.168.0.202. The pc seems to have the driver loaded properly & gives me a network icon, in which I've set the static ip info. This all allows me to ping the Z's address successfully, but not to ssh in. The root password on the Z is set, which up 'til now was the only other thing needed to allow a ssh connection.
So, under 3.5.4.1.rc4, anybody have any ideas as to what have I missed to make this work? thks
-
UPDATE: so I tried on my XP box. Pointing it to the linux.inf worked right away, I got a network connection icon, set it to the same ip, and I can actually get putty to get to a login prompt.
BUT that's where it stops. I try to login as either root or the local user (as set up when I flashed gpe), but all I get is access denied. This is after I connected the Z to my lan via my cf nic & was able to login just fine. SO I can only conclude that this definitely has to be a software issue on the Z's side. As far as this thread is concerned I guess I have been successful in installing the driver onto both XP & 2000.
Now all I have to do is to get the new OZ images working. I'll post this on the wiki as soon as I can. Thanks for the help.
-
Interestingly I did ipkg update / ipkg upgrade and this upgraded only one file: i think it was "libusb".
Did you upgrade too?
Ant
-
grog: I've seen issues with some ssh clients, not sure why, but dropbear just appears to not like some of them. You might try a different one.
Si
-
quote=ant,May 25 2006, 01:28 AM]Interestingly I did ipkg update / ipkg upgrade and this upgraded only one file: i think it was "libusb".[div align=\"right\"][a href=\"index.php?act=findpost&pid=128367\"][{POST_SNAPBACK}][/a][/div][/quote]
I didn't try an upgrade before, but I did & noticed the same thing, libusb. Even after a reboot didn't change anything, however.
grog: I've seen issues with some ssh clients, not sure why, but dropbear just appears to not like some of them. You might try a different one.[div align=\"right\"][a href=\"index.php?act=findpost&pid=128379\"][{POST_SNAPBACK}][/a][/div]
I uninstalled dropbear & installed openssh. No diff.
This worked with the sharp drivers with 2.4 kernel roms. So since two things have changed in my setup, it's hard to tell which is the culprit. Is there noone that has usb connectivity working with a 2.6 image?
-
Give me another day or so and my gpe-image should be built and I'll tell you.
It always used to work for me.
Si
-
Give me another day or so and my gpe-image should be built and I'll tell you.
It always used to work for me.[div align=\"right\"][a href=\"index.php?act=findpost&pid=128403\"][{POST_SNAPBACK}][/a][/div]
Waiting anxiously ...
Thanks lardman
-
Is there noone that has usb connectivity working with a 2.6 image?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=128389\"][{POST_SNAPBACK}][/a][/div]
Me.
SSH works through usb0 interface on my akita with 3.5.4.1-RC4 (gpe image), so in 2.6, but coming from my GNU/Linux box... didn't try with a SSH client on windows, and am not willing to
Did you try with the openssh client from Cygwin on your windows box ?
Are you using SSH v1 or v2 ?
Anyway, problem seems to be with SSH rather than networking stack ?
-
Is there noone that has usb connectivity working with a 2.6 image?[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=128389\")
Me.
SSH works through usb0 interface on my akita with 3.5.4.1-RC4 (gpe image), so in 2.6, but coming from my GNU/Linux box... didn't try with a SSH client on windows, and am not willing to
Did you try with the openssh client from Cygwin on your windows box ?
Are you using SSH v1 or v2 ?
Anyway, problem seems to be with SSH rather than networking stack ?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=128501\"][{POST_SNAPBACK}][/a][/div]
As I've said previously, I *can* ssh into my Z if it's connected directly to the network (via my wifi or nic card), so I would I think that it's not just ssh itself. I'm using putty on the 'doze box, I've tried setting both ssh1 & ssh2 without a difference.
I just tried [a href=\"ftp://sunsite.unc.edu/pub/packages/security/ssh/SSHSecureShellClient-3.2.9.exe]ssh com's client[/url] which reported that the address is unreachable. So maybe it *is* a setup problem. But then in my experience, if putty is pointed to an unreachable/invalid address, the terminal window doesn't appear. In this case it does, but then fails with a 'conection refused'. Confusing
-
Works for me using the ssh you linked above (with e-image from 3.5.4-rc2).
Note that I had to use ifconfig to change the IP address of the usb0 device (it was defaulting to 192.168.0.202 iirc.)
Si
-
Works for me using the ssh you linked above (with e-image from 3.5.4-rc2).
Note that I had to use ifconfig to change the IP address of the usb0 device (it was defaulting to 192.168.0.202 iirc.)[div align=\"right\"][a href=\"index.php?act=findpost&pid=128779\"][{POST_SNAPBACK}][/a][/div]
It still doesn't work for me. I wonder if it's a problem with rc4 then, 'cause that's all I have access to. I assume you changed the interface ip to this:
ifconfig usb0 192.168.129.201 upI did the same & ifconfig reports the correct specified address & I made sure that the network connection in windows had that same specification. You did the same? Anything different?
thks
-
Oops, mis-type on my part, I hafve the latest version which is rc4.
I did:
'ifup usb0'
Found it had the wrong IP address,
'ifdown usb0'
'ifconfig usb0 192.168.129.201'
'ifup usb0'
and it worked.
Si
-
Oops, mis-type on my part, I hafve the latest version which is rc4.
I did:
'ifup usb0'
Found it had the wrong IP address,
'ifdown usb0'
'ifconfig usb0 192.168.129.201'
'ifup usb0'
and it worked.[div align=\"right\"][a href=\"index.php?act=findpost&pid=128925\"][{POST_SNAPBACK}][/a][/div]
Still not working. On mine, I tried the exact steps as you (except you didn't specify a 'modprobe g_ether' to start off, which I assume you had to) except:
# modprobe g_ether
# ifup usb0
# ifconfig usb0
(reports 192.168.0.202)
# ifdown usb0
# ifconfig usb0 192.168.129.201
# ifup usb0
# ifconfig usb0
(still reports 192.168.0.202)
# ifdown usb0
# ifconfig usb0 192.168.129.201 up
# ifconfig usb0
(now reports 192.168.129.201)But after all that I still get a 'connection refused' from putty & a 'host unreachable' from the ssh client.
I've attached a screen shot of my 'doze ip config. See anything wrong? thks
-
Yeah, forgot about the g_ether modprobe, sorry.
You need to set the WinXP connection to something other than 192.168.129.201 (as this is the Zaurus-end-of-the-connection IP address).
Try 192.168.129.200
Si
-
Yeah, forgot about the g_ether modprobe, sorry.
You need to set the WinXP connection to something other than 192.168.129.201 (as this is the Zaurus-end-of-the-connection IP address).
Try 192.168.129.200[div align=\"right\"][a href=\"index.php?act=findpost&pid=128974\"][{POST_SNAPBACK}][/a][/div]
I double-checked, but that is what I have already. One thing you mention though is that you're running XP. I'm doing this on my 2000 box right now which I had to install the drivers I mentioned earlier, which I assume you did not. That would be the only other point of contention between our settings.
I'll double check the settings on my XP box when I get home later. thks
-
I only said that as the screenshot you've provided says you've set the XP end of the adaptor to the same IP address as the Zaurus end.
Si
-
I only said that as the screenshot you've provided says you've set the XP end of the adaptor to the same IP address as the Zaurus end.[div align=\"right\"][a href=\"index.php?act=findpost&pid=128990\"][{POST_SNAPBACK}][/a][/div]
Actually it doesn't (take another peek), but no matter. Then to confirm, what version of windows are you using on your end to test this? And did you have to install any additional drivers (beyond pointing the install at the linux.inf)? Do you still have (or have you ever had) the Sharp drivers (for 2.4 devices) installed?
-
Actually it doesn't (take another peek), but no matter.
Yes it does.
You say you set the Zaurus IP address to 192.168.129.201, which is standard.
the screenshot shows the top line of the WinXP dialog also indicating an IP address of 192.168.129.201, this therefore, won't work.
I have had the old drivers installed, but they make no difference as the ID numbers have changed with the gadget ethernet driver (and in any case it appears that your gadget driver is working as the device is recognised).
Si
-
Actually it doesn't (take another peek), but no matter.
Yes it does.
You say you set the Zaurus IP address to 192.168.129.201, which is standard.
the screenshot shows the top line of the WinXP dialog also indicating an IP address of 192.168.129.201, this therefore, won't work.
I have had the old drivers installed, but they make no difference as the ID numbers have changed with the gadget ethernet driver (and in any case it appears that your gadget driver is working as the device is recognised).
[div align=\"right\"][a href=\"index.php?act=findpost&pid=129111\"][{POST_SNAPBACK}][/a][/div]
I think we need to clear this up, as this might be the cause of my problem. I'm looking at my windows network settings for my zaurus connection (which was called 'Local Area Connection 2' & which I've renamed to Zaurus). This is the same setting I've had that always worked with previous 2.4 kernel connections. I have 192.168.129.201 in the 'IP address' field, 255.255.255.0 in the 'Subnet mask' field and '192.168.129.200 in the 'Default gateway' field. What values do you have for each of these?
-
On the Windows machine:
IP: 192.168.129.200
Subnet: 255.255.255.0
gateway: my modem's IP address
(so this connection can talk to the outside world, hopefully )
On the Zaurus:
IP: 192.168.129.201
subnet: 255.255.255.0
gateway: 192.168.129.200
(so that my Zaurus routes stuff to the PC, probably also needs some 'route' magic)
Si
-
On the Windows machine:
IP: 192.168.129.200
Subnet: 255.255.255.0
gateway: my modem's IP address
(so this connection can talk to the outside world, hopefully )
On the Zaurus:
IP: 192.168.129.201
subnet: 255.255.255.0
gateway: 192.168.129.200
(so that my Zaurus routes stuff to the PC, probably also needs some 'route' magic)[div align=\"right\"][a href=\"index.php?act=findpost&pid=129151\"][{POST_SNAPBACK}][/a][/div]
I'm not trying to argue the fact that this works for you, but for me, it locks up my network connection (presumably with an ip address conflict). How come under a 2.4 kernel rom my Z's net connection ip had to match that of the Z, and it worked? I always understood that it was the way of letting both the Z & the pc know the common address. If I understand correctly, it seems you have it set up with two.
I'm going to lay this out again just to make sure we're not talking about two different things. First I have my pc's connection to the net set up as dhcp. Let's say it gets an address of 10.10.0.4 (I have no control over the subnet used, i.e. I can't change it). Formerly I've had the Z's connection on the pc side set up like this:
ip: 192.168.129.201
subnet: 255.255.255.0
gateway: (blank)
and my Z set up like this:
ip: 192.168.129.201
subnet: 255.255.255.0
gateway: (blank)
Which allowed me to ssh in to my Z from the pc, but the Z was never able to get to the net. I always wanted to fix that but never could. But you're saying I should have the Z's connection on the pc side set up like this:
ip: 192.168.129.200
subnet: 255.255.255.0
gateway: 10.10.0.4
and my Z set up like this:
ip: 192.168.129.201
subnet: 255.255.255.0
gateway: 192.168.129.200
Correct? thks
-
>>presumably with an ip address conflict
*************
Sure, you were contradicting the basics of TCP-IP...
Ant
-
>>presumably with an ip address conflict
*************
Sure, you were contradicting the basics of TCP-IP...[div align=\"right\"][a href=\"index.php?act=findpost&pid=129819\"][{POST_SNAPBACK}][/a][/div]
So you're saying I was right in the first place?
-
>>presumably with an ip address conflict
*************
Sure, you were contradicting the basics of TCP-IP...[div align=\"right\"][a href=\"index.php?act=findpost&pid=129819\"][{POST_SNAPBACK}][/a][/div]
So you're saying I was right in the first place?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=129845\"][{POST_SNAPBACK}][/a][/div]
NO!
grog,
on a given subnet, each NIC is supposed to own a distinct ip address.
So, you'd need TWO different IP's on the same subnet: one for the Z and one for the PC.
Ant
EDIT
This is a "normal" case: what's unique is the MAC address and not the IP address.
But to be precise, a NIC can have several ip *aliases*.
-
So you're saying I was right in the first place?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=129845\"][{POST_SNAPBACK}][/a][/div]NO!
grog,
on a given subnet, each NIC is supposed to own a distinct ip address.
So, you'd need TWO different IP's on the same subnet: one for the Z and one for the PC.[div align=\"right\"][a href=\"index.php?act=findpost&pid=129876\"][{POST_SNAPBACK}][/a][/div]
errggghh. I think we're all getting confused here (or at least I am). I know that different boxen on the same subnet require different ip's. But I thought that the Z's usb settings on the pc side needed to match, i.e. the settings represented how the Z as a sudo-network (usb) device could be addressed by the pc. How else could the pc be able to contact the Z unless the address was hard-coded into the usb settings. And by putting a different address in there, it seems to me to fuddle up the mix. Like I said, this always worked fine before I stumbled blindly into 2.6 kernel land.
I doubt that I'm explaining myself properly. I'll conitnue to hack at it, if I stumble on a solution I'll post it. thks
-
errggghh. I think we're all getting confused here (or at least I am). I know that different boxen on the same subnet require different ip's. But I thought that the Z's usb settings on the pc side needed to match, i.e. the settings represented how the Z as a sudo-network (usb) device could be addressed by the pc. How else could the pc be able to contact the Z unless the address was hard-coded into the usb settings. And by putting a different address in there, it seems to me to fuddle up the mix.
The gadget or CDC/RNDIS ethernet driver makes the usb connection appear to be an ethernet device on the PC end, the same goes for the driver on the Zaurus end. Therefore you handle it exactly the same as if you were connecting a cross-over ethernet cable between two computers with real ethernet cards.
Like I said, this always worked fine before I stumbled blindly into 2.6 kernel land.
Hmm...
Anyway, the two need different IP addresses. what happens when you change them to be different & both on the same subnet?
Simon
P.S. I'm sure you already appreciate this, but if you setup with an IP of .201 on the Zaurus and .200 on the PC, make sure you try to ping/ssh to .201 from the PC, and to .200 from the Zaurus.
-
Anyway, the two need different IP addresses. what happens when you change them to be different & both on the same subnet?
I have that right now, 192.168.129.200 on the pc side, 192.168.129.201 on the Z. The network settings on the pc takes a llllooonnnggg time to come up when I try to access it's properties & it won't initialize at all. I tried removing the gateway address (my pc's network address), but makes no difference.
P.S. I'm sure you already appreciate this, but if you setup with an IP of .201 on the Zaurus and .200 on the PC, make sure you try to ping/ssh to .201 from the PC, and to .200 from the Zaurus.[div align=\"right\"][a href=\"index.php?act=findpost&pid=129901\"][{POST_SNAPBACK}][/a][/div]
Still makes no sense to me, but I'll play along . Right now I can't ping either address. Until I get the interface back up again, it's really snafu'd.
-
ok, so I decided to try something really wild & wacky . I installed OZ/OPIE 3.5.4.1.rc4. Set root's password, set the usb0 ip to 192.168.129.201 & left the pc's settings as per lardmans' instructions and ...
IT WORKS!! IT WORKS!! IT WORKS!!
So I kept on my wacky road & did a fresh install of gpe. Set up usb0 in the exact same way and IT DOES NOT WORK!!!
So why can't I get the gpe image to work!!!!????? What is the diff between the gpe & opie images at this level. Nothing, or so I formerly believed.
-
Run 'lsmod' on the GPE image and see whether the g_ether module is loaded.
If not, you need to 'modprobe g_ether' (probably need to cd to its location under /lib/modules/...)
Si
-
Run 'lsmod' on the GPE image and see whether the g_ether module is loaded.
If not, you need to 'modprobe g_ether' (probably need to cd to its location under /lib/modules/...)[div align=\"right\"][a href=\"index.php?act=findpost&pid=130031\"][{POST_SNAPBACK}][/a][/div]
Done. Here's specifically the steps I had to take with both images:
- edit /etc/network/interfaces to change usb0 to 192.168.129.201 & gateway to 192.168.129.200
- modprobe g_ether
- ifup usb0
-
Run 'lsmod' on the GPE image and see whether the g_ether module is loaded.
If not, you need to 'modprobe g_ether' (probably need to cd to its location under /lib/modules/...)[div align=\"right\"][a href=\"index.php?act=findpost&pid=130031\"][{POST_SNAPBACK}][/a][/div]
Done. Here's specifically the steps I had to take with both images:
- edit /etc/network/interfaces to change usb0 to 192.168.129.201 & gateway to 192.168.129.200
- modprobe g_ether
- ifup usb0[div align=\"right\"][a href=\"index.php?act=findpost&pid=130038\"][{POST_SNAPBACK}][/a][/div]
Just wanted to make myself clear in case there's any confusion. These are the steps that I previously took that enabled only opie to work. I haven't made any headway since that point. thks
-
Grog, the same instructions should work for you with GPE (the base systems are the same). Are you saying that they don't work?
If so, at what point do they fail?
Si
-
Grog, the same instructions should work for you with GPE (the base systems are the same). Are you saying that they don't work?
If so, at what point do they fail?[div align=\"right\"][a href=\"index.php?act=findpost&pid=137800\"][{POST_SNAPBACK}][/a][/div]
I'd pretty much given up on this, but I'll take another stab. i installed 3.5.4.1.release first with OPIE & setup my windows 2000 pc & Z exactly as you previously suggested:
On the Windows machine:
IP: 192.168.129.200
Subnet: 255.255.255.0
gateway: my modem's IP address
(so this connection can talk to the outside world, hopefully )
On the Zaurus:
IP: 192.168.129.201
subnet: 255.255.255.0
gateway: 192.168.129.200
(so that my Zaurus routes stuff to the PC, probably also needs some 'route' magic)
[div align=\"right\"][a href=\"index.php?act=findpost&pid=129151\"][{POST_SNAPBACK}][/a][/div]
And I 'modprobe g_ether' & 'ifup usb0', but while the pc shows the network device loaded, I can't ping nor contact the Z as '192.168.129.201'.
I think the pc is now confused. I recognized the Z as a new device, even though I had previously tried this with rc4. I had to point it at the usb8023k.sys driver again & the new network icon now says it's "Linux USB Ethernet/RNDIS Gadget #2". When I set the ip address, it complained that it had the same address as the "Linux USB Ethernet/RNDIS Gadget", but that isn't shown anywhere so I can delete or change it's settings. So I think this may be an address conflict problem between the two devices, but I can't see any way of removing the first one.
I'll try it on my XP box when I can make time @ home.
(sigh) I love windows
-
I think the pc is now confused. I recognized the Z as a new device, even though I had previously tried this with rc4. I had to point it at the usb8023k.sys driver again & the new network icon now says it's "Linux USB Ethernet/RNDIS Gadget #2". When I set the ip address, it complained that it had the same address as the "Linux USB Ethernet/RNDIS Gadget", but that isn't shown anywhere so I can delete or change it's settings. So I think this may be an address conflict problem between the two devices, but I can't see any way of removing the first one.[div align=\"right\"][a href=\"index.php?act=findpost&pid=137848\"][{POST_SNAPBACK}][/a][/div]
No headway yet. Haven't had time to test on XP, the 2000 box isn't able to ping 192.168.129.201, even though it shows the device attached & the network icon shows connected.
-
I think the pc is now confused. I recognized the Z as a new device, even though I had previously tried this with rc4. I had to point it at the usb8023k.sys driver again & the new network icon now says it's "Linux USB Ethernet/RNDIS Gadget #2". When I set the ip address, it complained that it had the same address as the "Linux USB Ethernet/RNDIS Gadget", but that isn't shown anywhere so I can delete or change it's settings. So I think this may be an address conflict problem between the two devices, but I can't see any way of removing the first one.
This is standard, I get this warning whenever I create a new connection with the same IP address.
After your ping has failed, I'd be interested to see the output of:
on the Windows machine: 'ipconfig' and 'route print'
and on the Zaurus: 'ifconfig' and 'route'
Si
-
I think the pc is now confused. I recognized the Z as a new device, even though I had previously tried this with rc4. I had to point it at the usb8023k.sys driver again & the new network icon now says it's "Linux USB Ethernet/RNDIS Gadget #2". When I set the ip address, it complained that it had the same address as the "Linux USB Ethernet/RNDIS Gadget", but that isn't shown anywhere so I can delete or change it's settings. So I think this may be an address conflict problem between the two devices, but I can't see any way of removing the first one.
This is standard, I get this warning whenever I create a new connection with the same IP address.
After your ping has failed, I'd be interested to see the output of:
on the Windows machine: 'ipconfig' and 'route print'
and on the Zaurus: 'ifconfig' and 'route'[div align=\"right\"][a href=\"index.php?act=findpost&pid=138259\"][{POST_SNAPBACK}][/a][/div]
Windows:
C:\>ping 192.168.129.201
Pinging 192.168.129.201 with 32 bytes of data:
Request timed out.
Request timed out.
Ping statistics for 192.168.129.201:
Packets: Sent = 2, Received = 0, Lost = 2 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Control-C
^C
C:\>ipconfig
Windows 2000 IP Configuration
Ethernet adapter zaurus:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.129.200
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : federated.ca
IP Address. . . . . . . . . . . . : 172.28.14.63
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 172.28.10.3
C:\>route print
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x1000004 ...00 0f 1f 88 76 df ...... Broadcom NetXtreme Gigabit Ethernet Driver
0x3000002 ...e6 6d e4 94 22 ad ...... Linux 2.6.16/pxa2xx_udc
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 172.28.10.3 172.28.14.63 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
172.28.0.0 255.255.0.0 172.28.14.63 172.28.14.63 1
172.28.14.63 255.255.255.255 127.0.0.1 127.0.0.1 1
172.28.255.255 255.255.255.255 172.28.14.63 172.28.14.63 1
192.168.129.0 255.255.255.0 192.168.129.200 192.168.129.200 1
192.168.129.200 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.129.255 255.255.255.255 192.168.129.200 192.168.129.200 1
224.0.0.0 224.0.0.0 172.28.14.63 172.28.14.63 1
224.0.0.0 224.0.0.0 192.168.129.200 192.168.129.200 1
255.255.255.255 255.255.255.255 172.28.14.63 172.28.14.63 1
Default Gateway: 172.28.10.3
===========================================================================
Persistent Routes:
None
Z
+ ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:13 errors:0 dropped:0 overruns:0 frame:0
TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1192 (1.1 KiB) TX bytes:1192 (1.1 KiB)
usb0 Link encap:Ethernet HWaddr 46:9E:7A:D5:9C:1D
inet addr:192.168.129.201 Bcast:192.168.129.255 Mask:255.255.255.0
inet6 addr: fe80::449e:7aff:fed5:9c1d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3 errors:1 dropped:0 overruns:0 frame:1
TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:84 (84.0 B) TX bytes:2196 (2.1 KiB)
+ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.129.0 * 255.255.255.0 U 0 0 0 usb0
default 192.168.129.200 0.0.0.0 UG 0 0 0 usb0
-
192.168.129.200 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.129.255 255.255.255.255 192.168.129.200 192.168.129.200 1
looks to me as if the interface is set up incorectly on the windows PC, the broadcast address below it seems to be fine but the other just points back to itself