pegasus2-linux Mailing List for Linux Pegasus USB-Ethernet drv
Brought to you by:
petkan
Menu
▾
▴
pegasus2-linux — Linux pegasus, rtl8150 and any other usb-ethernet driver
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2004 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Hollis B. <ho...@pe...> - 2007-05-03 15:52:53
|
Hi, I've found that the pegasus driver in Ubuntu 6.10, 7.04, and Fedora 6 incorrectly tries to manage my Belkin USB Bluetooth adapter (and in the older distros, it fails poorly). Given the report at http://www.qbik.ch/usb/devices/showdev.php?id=791 , I'm wondering if these devices report the exact same product ID, and need some sort of quirk in the USB layer to distinguish them? The bluetooth device vendor/product ID is 050d:0121 . One I added "blacklist pegasus" to /etc/modprobe.d/blacklist, the hci_usb driver picked up my device and seems to be working fine. -Hollis |
|
From: Andrew S <ste...@ua...> - 2006-05-22 21:18:21
|
Pegasus.h labels the ADMTEK 0x8515 driver as supported, however, I have had little success in trying to get it to work. My dmesg is populated by the following error (over and over and over again, until I "rmmod pegasus") ehci_hcd 0000:00:1d.7: devpath 2.5 ep0in 3strikes pegasus 1-2.5:1.0: ctrl_callback, status -71 A little research tells me that -71 coresponds to a EPROTO error. Unfortunately, I know very little about the USB drivers, and have had limited success diagnosing the problem further. Ndiswrapper was also unsuccessful. I've attached a usbsnoop log of what occurs under windows when I plug the device in, I've also attached a usbmon log of what happens under linux. Unfortunately, they seem very different. If theres anyone out there that can help me with this, it would be greatly appreciated. -- Andrew S. |
|
From: Jay C. <jay...@ya...> - 2005-12-08 09:18:07
|
Hello, from what i could see there is only one perason subscribed to this list :( i just hope its not an automated bot. i am currently getting an error -71 when i plug in a multifunction device (keyboard/mouse ethernet and serial as well as 4 port hub) does anyone know what this may be and posbile ways i can fix it as at the moment its flooding my dmesg logs if its somthing i have to program then i will give it a try if its somthing in the source just say so and i will take a look when i get a bit of free time thanks to anyone on this mailing list __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
|
From: Karsten H. <khe...@ec...> - 2004-01-13 20:50:06
|
Hello list, I'm new to this list, and as I didn't find an archive I couldn't check wether it is an already known problem. I've recently bought a usb 8150based network adaptor for the thinkpad of my girlfriend and am getting the following error with Kernel 2.4.24: If I plug in the device, it is recognized and the 8150 module is loaded, but I don't get a link. The 'connect' led on the adaptor is on, also the light on the hub I connect to, but 'mii-tool eth' reports 'no link'. The same device works flawlessly on my Asus notebook (2.4.24 too) as well as with windows98se on the thinkpad with the drivers shipped. I tried to compile the driver from pegasus2.sf.net as well as the linux driver shipped on floppy, but (certainly due to lack of knowledge on my side) wasn't successfull (I simply replaced the rtl8150.c file in the kernel sources tree and tried 'make modules'). Maybe you have an idea how I can go on. Do you need further information and how do I get it? Are there known incompatibilities? Oh, my network adaptor is from 'Sitecom', it's named 'USB to fast Ethernet'. Yours, Karsten |
|
From: Petko M. <pe...@us...> - 2003-06-07 20:54:25
|
OK, thanks. Will add the new vendor and device IDs soon. Petko On Sat, 7 Jun 2003, Jay Carlson wrote: > The Microsoft MN-110 10/100 USB Ethernet Adapter is a PEGASUS_II. > Worked in 2.4.18 after adding the obvious thing to pegasus.h. I'm going > to be really lazy here and not prepare a patch....gotta get on a plane > shortly. > > T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 3 Spd=12 MxCh= 0 > D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 > P: Vendor=045e ProdID=007a Rev= 1.01 > S: Manufacturer=Microsoft > S: Product=Ethernet USB Adapter MN-110 > S: SerialNumber=0050F274C6A3 > C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=160mA > I: If#= 0 Alt= 0 #EPs= 3 Cls=00(>ifc ) Sub=00 Prot=00 Driver=pegasus > E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl= 0ms > E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl= 0ms > E: Ad=83(I) Atr=03(Int.) MxPS= 8 Ivl=128ms > > eth1 Link encap:Ethernet HWaddr 00:50:F2:74:C6:A3 > inet addr:129.83.x.x Bcast:129.83.255.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:503296 errors:0 dropped:0 overruns:0 frame:0 > TX packets:289907 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:100 > RX bytes:760638253 (725.4 MiB) TX bytes:19619775 (18.7 MiB) > > -- > Jay Carlson <no...@mi...> > > |
|
From: Jay C. <no...@mi...> - 2003-06-07 20:47:03
|
The Microsoft MN-110 10/100 USB Ethernet Adapter is a PEGASUS_II.
Worked in 2.4.18 after adding the obvious thing to pegasus.h. I'm going
to be really lazy here and not prepare a patch....gotta get on a plane
shortly.
T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 3 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=045e ProdID=007a Rev= 1.01
S: Manufacturer=Microsoft
S: Product=Ethernet USB Adapter MN-110
S: SerialNumber=0050F274C6A3
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=160mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=00(>ifc ) Sub=00 Prot=00 Driver=pegasus
E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl= 0ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl= 0ms
E: Ad=83(I) Atr=03(Int.) MxPS= 8 Ivl=128ms
eth1 Link encap:Ethernet HWaddr 00:50:F2:74:C6:A3
inet addr:129.83.x.x Bcast:129.83.255.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:503296 errors:0 dropped:0 overruns:0 frame:0
TX packets:289907 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:760638253 (725.4 MiB) TX bytes:19619775 (18.7 MiB)
--
Jay Carlson <no...@mi...>
|
|
From: Hanno <ha...@gm...> - 2002-12-17 21:41:05
|
There is a bug in the CVS-Version of pegasus.h for kernel 2.4. The Vendor-ID for the Netgear FA101 must be VENDOR_NETGEAR, not VENDOR_MELCO. The bug is not in the 2.5-version of the driver. Patch see below. I also wanted to know when it is planned to merge the current pegasus driver into the main kernel tree. --- pegasus-vanilla/pegasus.h 2002-11-19 14:30:53.000000000 +0100 +++ pegasus/pegasus.h 2002-12-17 22:35:28.000000000 +0100 @@ -247,7 +247,7 @@ DEFAULT_GPIO_RESET ) PEGASUS_DEV( "MELCO/BUFFALO LUA2-TX", VENDOR_MELCO, 0x0009, DEFAULT_GPIO_RESET | PEGASUS_II ) -PEGASUS_DEV( "NETGEAR FA101", VENDOR_MELCO, 0x1020, +PEGASUS_DEV( "NETGEAR FA101", VENDOR_NETGEAR, 0x1020, DEFAULT_GPIO_RESET | PEGASUS_II ) PEGASUS_DEV( "smartNIC 2 PnP Adapter", VENDOR_SMARTBRIDGES, 0x0003, DEFAULT_GPIO_RESET | PEGASUS_II ) |
|
From: Petko M. <pma...@Ln...> - 2002-03-27 19:12:44
|
this is just a test - ignore |
