Your message dated Thu, 8 May 2008 23:40:44 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#455899: damned ADMtek junk
has caused the Debian Bug report #455899,
regarding USB IDs for buggy Pegasus chips
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
455899: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=455899
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: linux-2.6
Severity: wishlist
Tags: patch
It seems that ADMtek ADM8515 chips report broken USB IDs under certain
conditions. When I plug my usb-ethernet adaptor before the computer is
powered on, it often reports a broken ID; at which point unplugging/replugging
would solve it.
I reproduced this on two different computers, although a third test on my
laptop didn't reveal the same problem.
In all my tests, it reported either ID fe4c:4784 or fe4c:4704; adding these
IDs to the list is working for me.
Attached patch was sent upstream already. The maintainer of the pegasus
driver seems to be ok with it (I expect it'll be merged with 2.6.25).
-- System Information:
Debian Release: lenny/sid
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-5-amd64
Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8)
diff -ur linux-2.6-2.6.23.old/drivers/net/usb/pegasus.h
linux-2.6-2.6.23/drivers/net/usb/pegasus.h
--- linux-2.6-2.6.23.old/drivers/net/usb/pegasus.h 2007-10-09
22:31:38.000000000 +0200
+++ linux-2.6-2.6.23/drivers/net/usb/pegasus.h 2007-12-06 22:57:14.000000000
+0100
@@ -122,6 +122,7 @@
#define VENDOR_ABOCOM 0x07b8
#define VENDOR_ACCTON 0x083a
#define VENDOR_ADMTEK 0x07a6
+#define VENDOR_ADMTEK_BUGGY 0xfe4c
#define VENDOR_AEILAB 0x3334
#define VENDOR_ALLIEDTEL 0x07c9
#define VENDOR_ATEN 0x0557
@@ -193,6 +194,12 @@
PEGASUS_DEV( "ADMtek ADM8515 \"Pegasus II\" USB-2.0 Ethernet",
VENDOR_ADMTEK, 0x8515,
DEFAULT_GPIO_RESET | PEGASUS_II )
+PEGASUS_DEV( "ADMtek ADM8515 \"Pegasus II\" USB-2.0 Ethernet (broken USB
ID!!)",
+ VENDOR_ADMTEK_BUGGY, 0x4704,
+ DEFAULT_GPIO_RESET | PEGASUS_II )
+PEGASUS_DEV( "ADMtek ADM8515 \"Pegasus II\" USB-2.0 Ethernet (broken USB
ID!!)",
+ VENDOR_ADMTEK_BUGGY, 0x4784,
+ DEFAULT_GPIO_RESET | PEGASUS_II )
PEGASUS_DEV( "ADMtek AN986 \"Pegasus\" USB Ethernet (evaluation board)",
VENDOR_ADMTEK, 0x0986,
DEFAULT_GPIO_RESET | HAS_HOME_PNA )
--- End Message ---
--- Begin Message ---
On Thu, May 08, 2008 at 11:21:51PM +0200, Robert Millan wrote:
>
> Sorry, I got rid of that device a while ago. Anyway, my impression is that
> this is a bug in the firmware, not in Linux. Maybe it would be possible to
> work around it in Linux, but it'd be extremely difficult without at least
> knowing what's causing the firmware to hang.
thanks for quick feedback.
if you happen to get it back and it still stinks, don't forget to holler
upstream on bugzilla.kernel.org too :)
best regards
--
maks
--- End Message ---
