Bug#455899: USB IDs for buggy Pegasus chips - Debian

This is a discussion on Bug#455899: USB IDs for buggy Pegasus chips - Debian ; 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 ...

+ Reply to Thread
Results 1 to 4 of 4

Thread: Bug#455899: USB IDs for buggy Pegasus chips

  1. Bug#455899: USB IDs for buggy Pegasus chips

    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)


  2. Bug#455899: USB IDs for buggy Pegasus chips

    On Wed, Dec 12, 2007 at 02:45:11PM +0100, Robert Millan wrote:
    > 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).


    Damn, now the device came up with a new ID. It doesn't look stable to me..

    Please, put this on hold. If you don't mind, I'd like to keep the bug open,
    just in case a solution is found.

    --
    Robert Millan

    I know my rights; I want my phone call!
    What use is a phone call, if you are unable to speak?
    (as seen on /.)



    --
    To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  3. Bug#455899: USB IDs for buggy Pegasus chips

    On Wed, Dec 12, 2007 at 08:21:53PM +0100, Robert Millan wrote:
    >
    > Damn, now the device came up with a new ID. It doesn't look stable to me..
    >
    > Please, put this on hold. If you don't mind, I'd like to keep the bug open,
    > just in case a solution is found.


    yep keep us posted.

    --
    maks



    --
    To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  4. Bug#455899: marked as done (USB IDs for buggy Pegasus chips)


    Your message dated Thu, 8 May 2008 23:40:44 +0200
    with message-id <20080508214043.GG27599@baikonur.stro.at>
    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 owner@bugs.debian.org
    immediately.)


    --
    455899: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=455899
    Debian Bug Tracking System
    Contact owner@bugs.debian.org with problems


+ Reply to Thread