On Fri, Feb 08, 2008 at 02:12:28PM -0500, Alan Stern wrote:
> On Fri, 8 Feb 2008, Fabio Venturi wrote:
>
> > > Ah. I had overlooked another difference in the lsusb output. If you
> > > compare the lines for bDeviceClass, you'll see that the
> > > hotplugg
gt;
> Alan Stern
Great shot!
This patch fix the problem so now the device is properly initialized and
a file (sdb in this case) is added to the /dev directory.
Do you need the usb-debug output for any purpose?
Thank you again for the time you spent solving my problem,
best regards
Fabio
PS:
On Fri, Feb 08, 2008 at 10:24:35AM -0500, Alan Stern wrote:
> On Fri, 8 Feb 2008, Fabio Venturi wrote:
>
> > > Can you post the usb-storage debugging log? It should indicate how
> > > things are getting "stuck".
>
> > This is the relevant part of dmes
On Thu, Feb 07, 2008 at 05:14:14PM -0500, Alan Stern wrote:
> On Thu, 7 Feb 2008, Fabio Venturi wrote:
>
> > > > Redirecting stderr and stdout of 'lsusb -v' I get the following details.
> > > > Note: the device restart if it get probed with 'lsusb -v&
> > Redirecting stderr and stdout of 'lsusb -v' I get the following details.
> > Note: the device restart if it get probed with 'lsusb -v'
> >
> >
> > Bus 001 Device 011: ID 10d6:2200 Actions Semiconductor Co., Ltd
> > Device Descriptor:
> > bLength18
> > bDescriptorType
On Thu, Feb 07, 2008 at 11:52:46AM -0500, Alan Stern wrote:
> On Thu, 7 Feb 2008, Fabio Venturi wrote:
>
> > I don't see any USB quirk in dmesg,
> > the initd file is rebuilt every time I change
> > something in the kernel with mkinitcpio on ArchLinux.
>
On Tue, Feb 05, 2008 at 01:30:23PM -0500, Alan Stern wrote:
> On Tue, 5 Feb 2008, Fabio Venturi wrote:
>
> > Opppsss!!!
> > Too many outputs to deal with :(
> > I'm not sure that was right,
> > this is right one for sure:
> >
> &g
On Tue, Feb 05, 2008 at 01:30:23PM -0500, Alan Stern wrote:
> On Tue, 5 Feb 2008, Fabio Venturi wrote:
>
> > Opppsss!!!
> > Too many outputs to deal with :(
> > I'm not sure that was right,
> > this is right one for sure:
> >
> &g
On Tue, Feb 05, 2008 at 10:43:46AM -0500, Alan Stern wrote:
> On Tue, 5 Feb 2008, Fabio Venturi wrote:
>
> > I've tried to patch quirks.c with:
> > + { USB_DEVICE(0x10d6, 0x2200), .driver_info =
> > USB_QUIRK_STRING_FETCH_255},
> >
> > and also with
On Mon, Feb 04, 2008 at 05:18:15PM -0500, Alan Stern wrote:
> On Mon, 4 Feb 2008, Fabio Venturi wrote:
>
> > Here is the output of usbmon with the patched kernel:
>
> Whoops! The patch I sent you was wrong. Evidently the device is using
> a different ProductID from w
On Mon, Feb 04, 2008 at 04:45:45PM -0500, Alan Stern wrote:
> On Mon, 4 Feb 2008, Fabio Venturi wrote:
>
> > > It's probably the result of a bug in the mp3 player's firmware. The
> > > patch below might work around the bug, try it and see.
> > >
>
On Mon, Feb 04, 2008 at 10:55:24AM -0500, Alan Stern wrote:
> On Sun, 3 Feb 2008, Fabio Venturi wrote:
>
> > > > Hi to the list,
> > > > I'm trying to use a Commodore Flash Disk MP3 player "CO - C.Muse"
> > > > (I don&#
On Sun, Feb 03, 2008 at 10:25:11AM -0500, Alan Stern wrote:
> On Sun, 3 Feb 2008, Fabio Venturi wrote:
>
> > Hi to the list,
> > I'm trying to use a Commodore Flash Disk MP3 player "CO - C.Muse"
> > (I don't know the chipset)
> > but when
Hi to the list,
I'm trying to use a Commodore Flash Disk MP3 player "CO - C.Muse"
(I don't know the chipset)
but when i plug it I get this:
tail -f /var/log/messages.log
[...]
Feb 3 14:30:57 silverstar usb 1-4: new high speed USB device using
ehci_hcd and address 12
Feb 3 14:30:57 silversta
14 matches
Mail list logo
