usbd0 is "No such device"

[fsjws4]

Install 3.5.1, they told me. It's better, they said...

Finally got SSH working on OZ 3.3.5, so I decided to upgrade to 3.5.1. Got all the bits and pieces and flashed it. Indeed, it's much nicer-looking. But when I plugged into the cradle, I didn't get the familiar boo-beep from XP.

ifconfig on the Z didn't show any IP address, and ipconfig on XP didn't show the connection as being up. So I went to Network on the Z, saw that DHCP was on, and manually entered the IP info I was using successfully before (the standard .201 IP address, etc). Pulled out and back in the cradle. Nothing. Tried the "Start" button: "Starting interface failed". Rebooted the Z while in the cradle. Still nothing. Tried enabling the connection from the XP side. Nope.

I searched the forums, and found some messages advising to use "ifup usbd0". Tried that, and got a few lines of "No such device":

Code: [Select]

SIOCSIFADDR: No such device
SIOCSIFNETMASK: No such device
SIOCGIFFLAGS: No such device
route: SIOC[ADD|DEL]RT: No such device
Also saw mention of just "usb0", and tried that too:

Code: [Select]

ifup: Ignoring unknown interface usb0
So I must be missing something -- what do I do to get the USB network enabled again?

[zenyatta]

A bug showed up in 3.3.6-pre1 that causes USB to only work after a reboot before the first suspend. This bug is still present in 3.5.1. Go Settings > Shutdown > Reboot and try connecting immediately after the system comes up. You should be connected and after you suspend&resume the usb should be dead.

If this is the case, there is a workaround by installing an older version of the hotplug package (google for hotplug_2002_08_26-8 or search around the forums).

z.

[fsjws4]

That doesn't seem to work, either. I left it set in Light & Power to never suspend when it's on AC power (i.e. in the cradle). Just for fun, I tried manually suspending and resuming, but of course that didn't help.

[fsjws4]

Heh.

Found the problem. I still had the winsfc app open from when I transferred the new ROM earlier today. That was somehow keeping the connection open (probably on the XP side). As soon as I quit the program, I got a beep-boop... boop-beep, and the connection activated.

I hate when it's my fault.