Does anyone know the device and vendor ID for memorex mini travel
drive? It's the 1 GB device and the USB 2.0 is uncircled.
Bill
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version
On Thu, 16 Feb 2006, Jean-Philippe Mengual wrote:
> Hi,
> Well it's very strange, but it seems the problem is physical. I was
> said tha]s very rare, and the person who made my computer doesn't
> understand. I'll do a new check with Windows, to see if USB is known.
That's a good idea.
> If it is
Hi,
Well it's very strange, but it seems the problem is physical. I was
said tha]s very rare, and the person who made my computer doesn't
understand. I'll do a new check with Windows, to see if USB is known.
If it is, problem isn't physical. Anyway if it is it's happent for a
short time, since 2 ye
On Tue, 14 Feb 2006, Jean-Philippe Mengual wrote:
> Hi,
> As you said, now in /proc/bus/usb, I have 001 002 devices. But devices
> stays empty, even when I connect my hd. I changed the source code as
> you said but I still have
> uhci_hcd :00:11.3: HCRESET not completed yet!
>
> I don't under
Hi,
As you said, now in /proc/bus/usb, I have 001 002 devices. But devices
stays empty, even when I connect my hd. I changed the source code as
you said but I still have
uhci_hcd :00:11.3: HCRESET not completed yet!
I don't understand. So, now, if I understand, if my hd doesn't work,
it's a ph
On Tue, 14 Feb 2006, Jean-Philippe Mengual wrote:
> Hi,
> I'm using a 2.6.11.12 kernel. And I'd like to know where I can find
> information or if you can help me yourself to make work my USB
> ports on a motherboard which has a VIA chipset, KT266/A/333.
> Normally, when I connect an extern
Hi,
I'm using a 2.6.11.12 kernel. And I'd like to know where I can find
information or if you can help me yourself to make work my USB
ports on a motherboard which has a VIA chipset, KT266/A/333.
Normally, when I connect an external hd via USB, in /dev, sdaX
should be created, since I i
David:
Here's a few ideas.
You mentioned before the need for documenting how devices get disconnected
some time after their state is set not NOTATTACHED. Below is a patch to
take care of this. I made some slight changes to your logic in a couple
of spots, mainly because the new hub_port_logical
