I've installed all of the ehci patches from mm. My audio works from
the USB 2.0 hub now. But I am having trouble with the card numbering
of my ALSA devices not being stable on each boot.
I'm getting this in my log dozens of times, not sure what it means.
ehci_hcd :00:1d.7: Should not have seen
On 12/19/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> On 12/19/06, Jon Smirl <[EMAIL PROTECTED]> wrote:
>
> > I was giving the hub more credit than it deserved. I thought it was
> > doing store and forward so that it was talking 480Mb to the PC and
> > then 1Mb, 12Mb or 480Mb to the periphera
On 12/19/06, Jon Smirl <[EMAIL PROTECTED]> wrote:
> I was giving the hub more credit than it deserved. I thought it was
> doing store and forward so that it was talking 480Mb to the PC and
> then 1Mb, 12Mb or 480Mb to the peripherals.
It is, but it makes none of the timing decisions itself. This
On 12/19/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> On 12/19/06, Jon Smirl <[EMAIL PROTECTED]> wrote:
>
> > That's a pretty bad scheduler if it can't schedule a single 12Mb
> > device on a 480Mb hub.
> > It's only sharing the hub with a USB keyboard. The audio being sent to
> > it is less t
On 12/19/06, Jon Smirl <[EMAIL PROTECTED]> wrote:
> That's a pretty bad scheduler if it can't schedule a single 12Mb
> device on a 480Mb hub.
> It's only sharing the hub with a USB keyboard. The audio being sent to
> it is less than 1Mb.
That's not the problem; it has trouble scheduling the bandw
On 12/19/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Well known issue; the 'stock' ehci scheduler is not efficient enough
> using hub TT bandwidth to allow many audio devices to work through a
> 2.0 hub.
That's a pretty bad scheduler if it can't schedule a single 12Mb
device on a 480Mb hub.
Well known issue; the 'stock' ehci scheduler is not efficient enough
using hub TT bandwidth to allow many audio devices to work through a
2.0 hub.
The -mm kernel series has a new, experimental scheduler in testing for
eventual mainline deployment that should allow all full-speed (USB
1.1) devices
On Thu, 9 Dec 2004, Douglas Pastorello wrote:
> I visited sourceforge.net, but it was not clear to me what I needed to
> download to fix this problem. Could you give me the name of the
> program/package that I need to fix the problem?
> Thanks
You need to look at www.kernel.org. The 2.6.10
On Wed, 8 Dec 2004, Douglas Pastorello wrote:
> eth0: no IPv6 routers present
> ohci_hcd :00:0c.1: wakeup
> usb 2-1: new full speed USB device using address 6
> usb-storage: This device (0686,4006,0001 S 06 P 50) has an unneeded
> SubClass entry in unusual_devs.h
>Please send a copy of thi
Correct me if I'm wrong ... this isn't really a usbdevfs problem,
it's that problem with host controller drivers that don't queue
control requests (uhci, usb-uhci). Yes? Userspace workarounds
shouldn't be needed any more for 2.5 kernels.
If it's really a usbdevfs problem, what is it, and why h
On Sat, Nov 30, David Brownell wrote:
> Olaf Hering wrote:
> >On Mon, Sep 23, Greg KH wrote:
> >
> >
> >>On Mon, Sep 23, 2002 at 05:34:31PM +0200, Olaf Hering wrote:
> >>
> >>>ftp.suse.com/pub/people/olh/hotplug_for_usb/hotplug.rpm
> >>>
> >>>Try that one, known and unfixed bug in usbdevfs...
> >
Olaf Hering wrote:
On Mon, Sep 23, Greg KH wrote:
On Mon, Sep 23, 2002 at 05:34:31PM +0200, Olaf Hering wrote:
ftp.suse.com/pub/people/olh/hotplug_for_usb/hotplug.rpm
Try that one, known and unfixed bug in usbdevfs...
Hm, which patch fixes this problem?
the fix is: /sbin/hotplug must do
begin On Mon, Sep 23, Greg KH wrote:
> On Mon, Sep 23, 2002 at 05:34:31PM +0200, Olaf Hering wrote:
> >
> > ftp.suse.com/pub/people/olh/hotplug_for_usb/hotplug.rpm
> >
> > Try that one, known and unfixed bug in usbdevfs...
>
> Hm, which patch fixes this problem?
the fix is: /sbin/hotplug mus
On Mon, Sep 23, 2002 at 05:34:31PM +0200, Olaf Hering wrote:
>
> ftp.suse.com/pub/people/olh/hotplug_for_usb/hotplug.rpm
>
> Try that one, known and unfixed bug in usbdevfs...
Hm, which patch fixes this problem?
thanks,
greg k-h
---
This s
begin On Sun, Sep 22, Manish Sharma wrote:
> usb.c: USB device not accepting new address=38 (error=-110)
> hub.c: USB new device connect on bus1/1, assigned device number 39
> usb_control/bulk_msg: timeout
> usb.c: USB device not accepting new address=39 (error=-110)
> hub.c: USB new device conn
Yes I did try that aswell.. still no luck..
On Sunday 22 September 2002 09:10 pm, Stephen J. Gowdy wrote:
> Did you try the ideas in;
>
> http://www.linux-usb.org/FAQ.html#ts6
>
> On Sun, 22 Sep 2002, Manish Sharma wrote:
> > I have the following setup.
> >
> > computer-1
> > Abit KT7 raid Moth
Did you try the ideas in;
http://www.linux-usb.org/FAQ.html#ts6
On Sun, 22 Sep 2002, Manish Sharma wrote:
> I have the following setup.
>
> computer-1
> Abit KT7 raid Motherboard, Suse 8.0
>
> computer-2
> MSI-6501 Motherboard, RH-7.3
>
> and a
> KVM Switch...with USB connectors to share
17 matches
Mail list logo
