Ok, found the real reason:
Kernels => 2.6.16 have a feature that checks whether devices can be
given as much power as they claim to need. If there's not enough juice
(like in my case), the device is not activated. So a feature, not a bug.
The Debian bug I linked to is about notifying the user abo
My problem was solved by adding irqpoll to the grub bootup options -- an
easy fix that I should have found much sooner. But it's still a failure
to work out-of-the-box... I haven't determined whether the same issue
exists in the newly-released official version of 6.10.
http://ubuntuforums.org/show
I'm assuming that two people suffering from apparently the same problem
is sufficient basis to call a bug confirmed...
** Changed in: linux-source-2.6.17 (Ubuntu)
Status: Unconfirmed => Confirmed
--
pegasus usb-ethernet driver does not work in Edgy
https://launchpad.net/bugs/67848
--
ub
Jussi drew my attention to this bug report when I posted about a similar
network problem, also with a Pegasus driven adapter, to
http://www.ubuntuforums.org/showthread.php?t=283634
So to the best of my knowledge, I have encountered the same bug that
Jussi did. Additional details are at the linked
