 Howto Load Usb Driver(s) To Get Usbd0?, OZ/GPE 3.5.4 + on C860 (boxer) |
OESF Forums > Distros, Development, and Model Specific Forums > Distro Support and Discussion > Angstrom & OpenZaurus  |
 May 18 2006, 11:58 AM
Post
#1
|
|
 Group: Members Posts: 692 Joined: 27-January 04 From: Canada Member No.: 1,564  |
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. |
 |
 
|
|
May 18 2006, 12:37 PM
Post
#2
|
|
 Group: Members Posts: 1,376 Joined: 11-January 04 From: Poznań, Poland Member No.: 1,413 |
g_ether on Z will give usb0
windows need linux.inf from Linux 2.6 source |
|
|
|
|
May 18 2006, 01:39 PM
Post
#3
|
|
|
Group: Members Posts: 692 Joined: 27-January 04 From: Canada Member No.: 1,564 |
QUOTE(Hrw @ May 18 2006, 02:37 PM) 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? QUOTE windows need linux.inf from Linux 2.6 source  This is where I'm stumped. I found losts of references through google (here & here, 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? |
|
|
|
|
May 19 2006, 01:37 AM
Post
#4
|
|
|
Group: Members Posts: 4,515 Joined: 25-October 03 From: Bath, UK Member No.: 464 |
|
|
|
|
|
May 19 2006, 07:00 AM
Post
#5
|
|
|
Group: Members Posts: 692 Joined: 27-January 04 From: Canada Member No.: 1,564 |
QUOTE(lardman @ May 19 2006, 03:37 AM) 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? |
|
|
|
|
May 19 2006, 08:37 AM
Post
#6
|
|
|
Group: Members Posts: 4,515 Joined: 25-October 03 From: Bath, UK Member No.: 464 |
Try something like this: http://www.microsoft.com/whdc/device/network/NDIS/rndis.mspx
I'm guessing that this will have these drivers in it. Si |
|
|
|
|
May 19 2006, 09:03 AM
Post
#7
|
|
|
Group: Members Posts: 692 Joined: 27-January 04 From: Canada Member No.: 1,564 |
QUOTE(lardman @ May 19 2006, 10:37 AM) Try something like this: http://www.microsoft.com/whdc/device/network/NDIS/rndis.mspx 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. |
|
|
|
|
May 23 2006, 02:40 PM
Post
#8
|
|
|
Group: Members Posts: 692 Joined: 27-January 04 From: Canada Member No.: 1,564 |
QUOTE(grog @ May 19 2006, 11:03 AM) QUOTE(lardman @ May 19 2006, 10:37 AM) Try something like this: http://www.microsoft.com/whdc/device/network/NDIS/rndis.mspx 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. 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. 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. |
|
|
|
|
May 23 2006, 09:18 PM
Post
#9
|
|
 Group: Members Posts: 54 Joined: 12-November 05 From: Israel Member No.: 8,524 |
QUOTE(grog @ May 19 2006, 07:03 PM) QUOTE(lardman @ May 19 2006, 10:37 AM) Try something like this: http://www.microsoft.com/whdc/device/network/NDIS/rndis.mspx 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. 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. |
|
|
|
|
May 24 2006, 09:34 AM
Post
#10
|
|
|
Group: Members Posts: 692 Joined: 27-January 04 From: Canada Member No.: 1,564 |
QUOTE(grog @ May 23 2006, 04:40 PM) 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. 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. 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 |
|
|
|
|
May 24 2006, 10:42 AM
Post
#11
|
|
 Group: Members Posts: 1,014 Joined: 4-January 05 From: Enschede, The Netherlands Member No.: 6,107 |
QUOTE(grog @ May 24 2006, 05:34 PM) QUOTE(grog @ May 23 2006, 04:40 PM) 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. 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. 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 usbd0 is the kernel 2.4 interface, usb0 the 2.6 one. |
|
|
|
|
May 24 2006, 11:22 AM
Post
#12
|
|
 Group: Members Posts: 163 Joined: 11-March 04 From: IT Member No.: 2,270 |
This happy end needs definetely to be put in the wiki...
|
|
|
|
|
May 24 2006, 12:05 PM
Post
#13
|
|
|
Group: Members Posts: 692 Joined: 27-January 04 From: Canada Member No.: 1,564 |
QUOTE(ant @ May 24 2006, 01:22 PM) This happy end needs definetely to be put in the wiki... 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 |
|
|
|
|
May 24 2006, 06:41 PM
Post
#14
|
|
|
Group: Members Posts: 692 Joined: 27-January 04 From: Canada Member No.: 1,564 |
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. |
|
|
|
|
May 24 2006, 11:28 PM
Post
#15
|
|
|
Group: Members Posts: 163 Joined: 11-March 04 From: IT Member No.: 2,270 |
Interestingly I did ipkg update / ipkg upgrade and this upgraded only one file: i think it was "libusb".
Did you upgrade too? Ant |
|
|
|
|
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:
|
Lo-Fi Version | Time is now: 21st May 2013 - 09:56 PM |