Opened 8 years ago

Closed 11 months ago

#7626 closed bug (fixed)

USB Net Adapter not "Plug&Play"

Reported by: Pete Owned by: mmlr
Priority: normal Milestone: R1
Component: Drivers/USB Version: R1/alpha2
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

Just installed a recent build (hrev41706) on a ThinkPad, and was able to get a Pegasus USB Internet adapter working. [Finally! Earlier revisions always went wrong somehow...] However, it will only work if plugged in before boot. If I boot first and then plug the unit in, I get no connection.

Change History (8)

comment:1 by Pete, 8 years ago

I've tagged this as a USB problem, but I wonder if it's not a network server problem? On my other machines, the network is always there at boot-up.

in reply to:  1 comment:2 by mmlr, 8 years ago

Replying to Pete:

I've tagged this as a USB problem, but I wonder if it's not a network server problem? On my other machines, the network is always there at boot-up.

That's really hard to tell with that information alone. Please attach at least a syslog. Also check if the USB device itself is detected (via listusb -v) and finally check if the network interface is created (via ifconfig).

comment:3 by Pete, 8 years ago

Sorry -- guess I was a bit brief.

There's nothing much in the syslog that I can find. When I plug the adapter in, the only messages are

KERN: usb hub 2: port 0: new device connected
KERN: usb_floppy: no valid CBI interface found
KERN: bfs: bfs_open_dir:1616: Not a directory
KERN: usb_floppy: no valid CBI interface found

Only the first of which I assume is relevant.

In the boot-up time area of the log, there is always (with minor variations):

KERN: loaded driver /boot/system/add-ons/kernel/drivers/dev/net/pegasus
KERN: usb_asix:00.29.937:init_driver::ver.0.8.3
KERN: loaded driver /boot/system/add-ons/kernel/drivers/dev/net/usb_asix
KERN: loaded driver /boot/system/add-ons/kernel/drivers/dev/net/usb_ecm
KERN: register_domain(1, internet)
KERN: unregister_domain(0x8306c780, 1, internet)
KERN: register_domain(9, unix)
KERN: unregister_domain(0x8306c780, 9, unix)
KERN: register_domain(1, internet)
KERN: unregister_domain(0x8306c640, 1, internet)
KERN: register_domain(1, internet)
KERN: unregister_domain(0x8306cf00, 1, internet)
KERN: register_domain(9, unix)
KERN: unregister_domain(0x8306c600, 9, unix)
KERN: register_domain(1, internet)
KERN: unregister_domain(0x8306c440, 1, internet)
KERN: register_domain(1, internet)
KERN: unregister_domain(0x8306ca00, 1, internet)
KERN: register_domain(9, unix)
KERN: unregister_domain(0x8306c400, 9, unix)
KERN: register_domain(1, internet)
KERN: register_domain(4, link)

The only difference if the adapter is connected before boot is that the

KERN: usb hub 2: port 0: new device connected

is before the

KERN: loaded driver /boot/system/add-ons/kernel/drivers/dev/net/pegasus

The device entry /dev/net/pegasus/0 always appears at whatever point the device is connected. However ifconfig only shows it if it is plugged in at boot:

/dev/net/pegasus/0
        Hardware type: Ethernet, Address: 00:14:d1:18:72:17
        Media type: Auto-select
        inet addr: 192.168.1.5, Bcast: 192.168.1.255, Mask: 255.255.255.0
        MTU: 1500, Metric: 0, up broadcast link
        Receive: 3233 packets, 0 errors, 2041834 bytes, 0 mcasts, 0 dropped
        Transmit: 3245 packets, 1 errors, 408249 bytes, 0 mcasts, 0 dropped
        Collisions: 0

loop    Hardware type: Local Loopback, Address: none
        inet addr: 127.0.0.1, Mask: 255.0.0.0
        MTU: 16384, Metric: 0, up loopback link
        Receive: 0 packets, 0 errors, 0 bytes, 0 mcasts, 0 dropped
        Transmit: 0 packets, 0 errors, 0 bytes, 0 mcasts, 0 dropped
        Collisions: 0

If the adapter is unplugged, the /dev entry does not go away.

That's about all I know for now.

in reply to:  3 comment:4 by mmlr, 8 years ago

Replying to Pete:

There's nothing much in the syslog that I can find. When I plug the adapter in, the only messages are

KERN: usb hub 2: port 0: new device connected

That's a good thing, there don't seem to be any addressing errors or such. This means the USB side should be fine.

The device entry /dev/net/pegasus/0 always appears at whatever point the device is connected. However ifconfig only shows it if it is plugged in at boot:

So if it's not plugged in at boot then the pegasus/0 entry appears as soon as you plug the device in? Just to make sure. If so then the net_server doesn't realize there's a new interface.

What you could try now to make sure that the Pegasus driver as well as USB is working: Try manually triggering the auto configuration by running ifconfig /dev/net/pegasus/0 auto-config. If this works, then something's up with the node monitoring of the device entries.

comment:5 by Pete, 8 years ago

Addendum: I successfully posted the above from the laptop, but then unplugged the adapter to double-check my statement that the device entry remained. Instead I got a KDL! (Afraid I didn't note the details, except that it was in the pegasus driver.) So there may be a few little things wrong.

BTW, I didn't consider this an urgent matter. (:-/) It doesn't really impact my usage, as long as I remember to plug the thing in first. It was more informational, in case anyone else runs into it.

Ahh -- sorry. Didn't notice you had posted a reply in the meantime. Yes, the device entry always appears at the time the adapter is plugged in. I'll try your additional suggestion as soon as I get a chance.

Last edited 8 years ago by Pete (previous) (diff)

in reply to:  5 ; comment:6 by korli, 8 years ago

Replying to Pete:

Addendum: I successfully posted the above from the laptop, but then unplugged the adapter to double-check my statement that the device entry remained. Instead I got a KDL! (Afraid I didn't note the details, except that it was in the pegasus driver.) So there may be a few little things wrong.

Wasn't it #7252 by chance?

in reply to:  6 comment:7 by Pete, 8 years ago

Replying to korli:

Replying to Pete:

Addendum: I successfully posted the above from the laptop, but then unplugged the adapter to double-check my statement that the device entry remained. Instead I got a KDL!

Wasn't it #7252 by chance?

Sounds like it. I'm not using DHCP, but I see that it happens with other devices too. Thanks for the link. (I won't comment there until I see it again.)

comment:8 by waddlesplash, 11 months ago

Resolution: fixed
Status: newclosed

Seems this was fixed with the recent changes in net_server, if not before.

Note: See TracTickets for help on using tickets.