Red Hat Bugzilla – Bug 148923
Pegasus USB driver S-L-O-W
Last modified: 2015-01-04 17:17:01 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5)
Description of problem:
Connecting a usb ethernet device successfully loads the pegasus
driver. Dhclient successfully sets the interface up but bandwidth
in and out is terrible. No amount of resetting seems to help.
Email me if you need more info.
Version-Release number of selected component (if applicable):
default kernel from install ISO
Steps to Reproduce:
1. Boot computer, login, (with or without the USB device connected
during boot doesn't change the behavior)
2. Connect usb ethernet device.
3. Attempt to use the Internet/yum/etc.
Actual Results: Attempt to do anything involving the network (dsl)
connection is pitifully slow to non-existant. Something as simple as
"yum update" is just waiting for data.
Expected Results: Fast connection to Internet. (factoring in congestion)
Which kernel are you running ("rpm -q kernel" shows which are installed and
uname "uname -a" prints the currently running one)? If it's less than the latest
release (kernel-2.6.10-1.766_FC3) you will probably be asked to upgrade and retest.
It is the very latest kernel. I ran yum update before I reported the bug.
I had a similar problem with my pegasus USB-Ethernet adaptor. It was a case
where most packets were being dropped (when it's slow, try pinging something on
your local network). I found that the problem would go away if I plugged the
adaptor into a newer auto-sensing type hub/switch instead of an older one. Even
just doing this once (turn on computer, let it boot, plug ethernet into 'new'
hub, unplug ethernet, plug it into original connection where it would be slow)
would fix it for the duration of the powerup. If this is the case, it might
have something to do with bug 130382.
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which
may contain a fix for your problem. Please update to this new kernel, and
report whether or not it fixes your problem.
If you have updated to Fedora Core 4 since this bug was opened, and the problem
still occurs with the latest updates for that release, please change the version
field of this bug to 'fc4'.
This bug has been automatically closed as part of a mass update.
It had been in NEEDINFO state since July 2005.
If this bug still exists in current errata kernels, please reopen this bug.
There are a large number of inactive bugs in the database, and this is the only
way to purge them.