On Fri, 23 Dec 2005, Brown, Len wrote:
> >2.6.13 failed
>
> >2.6.13-15 from SL10 works out of the box with kbd interrupts
> > over ehci-hcd with ohci-hcd also loaded.
>
> So I built 2.6.13 built with SL10's .config and it worked!
> Then I built 2.6.15-rc6 with SL10's .config and it also work
On Fri, 23 Dec 2005, Brown, Len wrote:
> >2.6.13 failed
>
> >2.6.13-15 from SL10 works out of the box with kbd interrupts
> > over ehci-hcd with ohci-hcd also loaded.
>
> So I built 2.6.13 built with SL10's .config and it worked!
> Then I built 2.6.15-rc6 with SL10's .config and it also work
On Thu, 22 Dec 2005 17:24:25 -0500 (EST), Alan Stern <[EMAIL PROTECTED]> wrote:
> > > 2.6.12 worked, but neither ehci-hcd, nor ohci-hcd loaded and
> > > instead the keyboard interrupts came in over IRQ1 i8042
> > > so I guess there is some sort of emulation at play there?
> > > Unclear why i
On Thu, Dec 22, 2005 at 03:51:51PM -0800, Steve Calfee wrote:
> On Thu, 2005-12-22 at 15:31 -0800, Greg KH wrote:
> > On Thu, Dec 22, 2005 at 08:12:02PM +, James Courtier-Dutton wrote:
> > > Randy.Dunlap wrote:
> > > >>
> > > >>Load ehci-hcd OR ohci-hcd, but not both at the same time.
> > > >
>
On Thu, 2005-12-22 at 15:31 -0800, Greg KH wrote:
> On Thu, Dec 22, 2005 at 08:12:02PM +, James Courtier-Dutton wrote:
> > Randy.Dunlap wrote:
> > >>
> > >>Load ehci-hcd OR ohci-hcd, but not both at the same time.
> > >
> > >
> > >What's the reasoning for that?
> > >
> > >EHCI needs a "companio
On Thu, 22 Dec 2005, Pete Zaitcev wrote:
> On Thu, 22 Dec 2005 14:33:11 -0500, "Brown, Len" <[EMAIL PROTECTED]> wrote:
>
> > 2.6.12 worked, but neither ehci-hcd, nor ohci-hcd loaded and
> > instead the keyboard interrupts came in over IRQ1 i8042
> > so I guess there is some sort of emulat
On Thu, Dec 22, 2005 at 08:32:07PM +, James Courtier-Dutton wrote:
> That explains why my ehci-hcd works for my mouse. It is behind a USB 2.0
> hub.
> If I load the uhci-hcd module, it causes havoc with both drivers then
> trying to control the same USB device.
No, the uhci-hcd driver should
On Thu, 22 Dec 2005, Greg KH wrote:
> On Thu, Dec 22, 2005 at 08:12:02PM +, James Courtier-Dutton wrote:
> > Randy.Dunlap wrote:
> > >>
> > >>Load ehci-hcd OR ohci-hcd, but not both at the same time.
> > >
> > >
> > >What's the reasoning for that?
> > >
> > >EHCI needs a "companion" controller
Greg KH wrote:
On Thu, Dec 22, 2005 at 08:12:02PM +, James Courtier-Dutton wrote:
Randy.Dunlap wrote:
Load ehci-hcd OR ohci-hcd, but not both at the same time.
What's the reasoning for that?
EHCI needs a "companion" controller and driver (like
UHCI or OHCI) for non-high-speed devices.
>On Thu, 22 Dec 2005 14:33:11 -0500, "Brown, Len"
><[EMAIL PROTECTED]> wrote:
>
>> 2.6.12 worked, but neither ehci-hcd, nor ohci-hcd loaded and
>> instead the keyboard interrupts came in over IRQ1 i8042
>> so I guess there is some sort of emulation at play there?
>> Unclear why it
that is what I did as of XXX below:
>-Original Message-
>From: James Courtier-Dutton [mailto:[EMAIL PROTECTED]
>Sent: Thursday, December 22, 2005 3:03 PM
>To: Brown, Len
>Cc: Alan Stern; Greg KH; USB development list
>Subject: Re: [linux-usb-devel] Re: ehci-hcd re
On Thu, Dec 22, 2005 at 08:12:02PM +, James Courtier-Dutton wrote:
> Randy.Dunlap wrote:
> >>
> >>Load ehci-hcd OR ohci-hcd, but not both at the same time.
> >
> >
> >What's the reasoning for that?
> >
> >EHCI needs a "companion" controller and driver (like
> >UHCI or OHCI) for non-high-speed d
On Thu, Dec 22, 2005 at 08:12:02PM +, James Courtier-Dutton wrote:
> Randy.Dunlap wrote:
> >>
> >>Load ehci-hcd OR ohci-hcd, but not both at the same time.
> >
> >
> >What's the reasoning for that?
> >
> >EHCI needs a "companion" controller and driver (like
> >UHCI or OHCI) for non-high-speed d
Randy.Dunlap wrote:
Load ehci-hcd OR ohci-hcd, but not both at the same time.
What's the reasoning for that?
EHCI needs a "companion" controller and driver (like
UHCI or OHCI) for non-high-speed devices.
Since when?
---
This SF.net ema
On Thu, 22 Dec 2005, James Courtier-Dutton wrote:
> Brown, Len wrote:
> >
> >
> >>As an alternate experiment,
> >>first manually insmod ohci-hcd.ko and then insmod ehci-hcd.ko.
> >
> >
> > keyboard started working when ohci-hcd was loaded,
> > loading ehci-hcd broke it
> > unloading ehci-hcd fixe
Brown, Len wrote:
As an alternate experiment,
first manually insmod ohci-hcd.ko and then insmod ehci-hcd.ko.
keyboard started working when ohci-hcd was loaded,
loading ehci-hcd broke it
unloading ehci-hcd fixed it
loaded ehci-hcd and this time keyboard continued to work,
but kbd interrupts
On Thu, 22 Dec 2005 14:33:11 -0500, "Brown, Len" <[EMAIL PROTECTED]> wrote:
> 2.6.12 worked, but neither ehci-hcd, nor ohci-hcd loaded and
> instead the keyboard interrupts came in over IRQ1 i8042
> so I guess there is some sort of emulation at play there?
> Unclear why it isn't
>> I guess the question then are what changed such that it worked
>> on SL10 and it fails now,
>
>Exactly. I have no idea. Can you identify the most recent
>kernel version where it worked okay?
2.6.13 failed
2.6.12 worked, but neither ehci-hcd, nor ohci-hcd loaded and
instead the keybo
On Wed, 21 Dec 2005, Brown, Len wrote:
> Here you go.
> Note that this is the configuration with the devices
> plugged directly into the laptop, and the laptop also
> plugged into the docking station. Seems that the USB
> keyboard takes about 20 sec to come to life.
Actually that's the time it t
>I still don't have a clue about why the docking station's hub
>refuses to cooperate. The log shows only that it is not sending back
>data when it should be. If it worked correctly then none of those timeouts
>and retries would have occurred.
I guess the question then are what changed such
There aren't any timestamps in the log
Here you go.
Note that this is the configuration with the devices
plugged directly into the laptop, and the laptop also
plugged into the docking station. Seems that the USB
keyboard takes about 20 sec to come to life.
yes, the wireless receiver is the key
On Wed, 21 Dec 2005, Brown, Len wrote:
> >> >Can you send the dmesg log for the situation where you boot with the
> >> >keyboard and mouse plugged into the computer and the computer
> >> >attached to the docking station?
> >>
> >> Attached as dmesg.init3
> >> corresponding devices.init3 attached
>> >Can you send the dmesg log for the situation where you boot with the
>> >keyboard and mouse plugged into the computer and the computer
>> >attached to the docking station?
>>
>> Attached as dmesg.init3
>> corresponding devices.init3 attached as well.
>>
>> However, while gathering the dmesg
On Wed, 21 Dec 2005, Brown, Len wrote:
> The keyboard doesn't work when I boot,
> but is working when a very long delayed 1st cat
> of /proc/bus/usb/devices returns. Curiously
> the 2nd cat of devices still takes a huge 7 seconds,
> and only upon the 3rd is is quick:
Clearly something is waiting
On Wed, 21 Dec 2005, Brown, Len wrote:
> >Can you send the dmesg log for the situation where you boot with the
> >keyboard and mouse plugged into the computer and the computer
> >attached to the docking station?
>
> Attached as dmesg.init3
> corresponding devices.init3 attached as well.
>
> How
>The dmesg log was very informative. You've got one of those strange
>situations where things don't work at boot time but they do
>work later.
>In particular, the docking station's internal hub refused to
>initialize at boot time. When you removed ehci-hcd,
>it did initialize at full speed.
>However, while gathering the dmesg I realized that the
>keyboard started working some time after I logged in
>(via network and serial console, not using console kbd)
>
>After I realized the keyboard was working I looked in that
>file again and the keyboard had appeard (devices.init3.diff)
The k
>> When I boot with the USB keyboard and mouse connected directly
>> to the laptop, then they still don't work after a boot with
>> ehci-hcd present.
>
>This sounds like a different problem. Or at least, if it is the same
>problem it's affecting a different device. I don't see why
>failure of
>> > # nothing in /proc/bus/usb/devices/
>>
>> Did you try doing "cat /proc/bus/usb/devices" ?
>
>Oops, forgot that SuSE doesn't mount usbfs. Len, there's a
>line in your
>fstab you can uncomment to get usbfs back. Uncomment it, and do:
> mount /proc/bus/usb
>to get it back.
Actually th
>Odds are, that docking station is a usb 2.0 hub. Can you provide the
>output of /proc/bus/usb/devices with the docking station and device
>pluged in and ehci-hcd loaded?
gah, must have thought this was supposed to be a directory --
here's the file. System state is with ehci-hcd loaded
and the d
On Wed, Dec 21, 2005 at 11:26:13AM -0500, Alan Stern wrote:
> It's possible that you're seeing more than one problem.
>
> On Tue, 20 Dec 2005, Brown, Len wrote:
>
> > # nothing in /proc/bus/usb/devices/
>
> Did you try doing "cat /proc/bus/usb/devices" ?
Oops, forgot that SuSE doesn't mount usb
It's possible that you're seeing more than one problem.
On Tue, 20 Dec 2005, Brown, Len wrote:
> # nothing in /proc/bus/usb/devices/
Did you try doing "cat /proc/bus/usb/devices" ?
> The devices are plugged into the HP docking station.
> It has 3 ports, so I guess there is a hub inside it?
> dm
On Tue, Dec 20, 2005 at 11:04:37AM -0800, Pete Zaitcev wrote:
> On Tue, 20 Dec 2005 08:54:49 -0800, Greg KH <[EMAIL PROTECTED]> wrote:
> > On Mon, Dec 19, 2005 at 11:21:19PM -0500, Len Brown wrote:
>
> > > If i remove ehci-hcd.ko from Linux-2..15-rc5 and then boot,
> > > the USB keyboard and mouse
On Tue, Dec 20, 2005 at 02:49:20PM -0500, Brown, Len wrote:
>
> so it seems to be the presence, rather than the use of, the
> docking station that is making ehci-hcd into a trouble-maker.
Odds are, that docking station is a usb 2.0 hub. Can you provide the
output of /proc/bus/usb/devices with th
On Tue, 20 Dec 2005 08:54:49 -0800, Greg KH <[EMAIL PROTECTED]> wrote:
> On Mon, Dec 19, 2005 at 11:21:19PM -0500, Len Brown wrote:
> > If i remove ehci-hcd.ko from Linux-2..15-rc5 and then boot,
> > the USB keyboard and mouse work fine. I wiggle the mouse
> > and get interrupts in IRQ209:
>
>
On Mon, Dec 19, 2005 at 11:21:19PM -0500, Len Brown wrote:
> If i remove ehci-hcd.ko from Linux-2..15-rc5 and then boot,
> the USB keyboard and mouse work fine. I wiggle the mouse
> and get interrupts in IRQ209:
Wait, do you have these devices plugged into a usb 2.0 hub? If so, can
you just pl
On Mon, 19 Dec 2005, Len Brown wrote:
> If i remove ehci-hcd.ko from Linux-2..15-rc5 and then boot,
You mean, if you boot and then rmmod ehci-hcd?
> the USB keyboard and mouse work fine. I wiggle the mouse
> and get interrupts in IRQ209:
>
> r3000:~ # cat /proc/interrupts
>CPU0
>
If i remove ehci-hcd.ko from Linux-2..15-rc5 and then boot,
the USB keyboard and mouse work fine. I wiggle the mouse
and get interrupts in IRQ209:
r3000:~ # cat /proc/interrupts
CPU0
0: 34121IO-APIC-edge timer
1: 12IO-APIC-edge i8042
4: 1255IO-API
38 matches
Mail list logo
