I'm still having issues with this. Today I rebooted from a remote location and the Sabrent USB-G1000 didn't come back up. So I had to drive on-site to investigate.
The Sabrent USB-G1000 did not have any networking-lights lit up on it where the cat-5 cable plugs into it. It seemed like it was dead. I rebooted again, on-site, and the lights didn't come on. Then, I unplugged it from the USB 2.0 port and then plugged it back in. After this the networking lights came on again. I rebooted once more, and this time the Sabrent USB-G1000 began functioning as normal. So something has changed. Ever since upgrading to the 3.5.0-49-generic kernel, rebooting isn't a sure thing anymore. I certainly can't risk rebooting off-site anymore. I'm not sure if the issue is caused by a kernel update for the Sabrent USB-G1000 or is it the USB port's behavior that has been modified with the new kernel. Either the port is"forgetting" to turn on the Sabrent USB-G1000 or the Sabrent USB-G1000's driver is not consistently turning it on after a reboot. That's my best try, perhaps someone else can advise where the cause is truly coming from? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1312853 Title: 3.5.0-49-generic made Sabrent USB-G1000 network card nonfunctional To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-quantal/+bug/1312853/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
