[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: USB keyboard not working on a cinema display/cube

On 10 janv. 05, at 09:39, Sven Luther wrote:

On Sat, Jan 08, 2005 at 06:59:38PM +0100, Nicolas Jungers wrote:
Le 31 déc. 04, à 00:24, Sven Luther a écrit :

On Mon, Dec 27, 2004 at 07:11:34PM +0100, Nicolas Jungers wrote:
the sarge-powerpc-netinst.iso fail to activate my keyboard when
connected to the display. It's true of the RC2 version and of the
daily/powerpc/20041226/ version.

Can you look in /proc/bus/usb/devices if it shows up or something, and
post us
a lsmod output. May be tricky without keyboard though :) Maybe using
network-console and some presseding may help here ?

I dunno how to do that on a Mac. What I did was plugin two keyboards,

Yeah, that was the other solution.

one on the cube, the other on the cinema display, and both didn't

but if you plug only one into the cube, it is ok ? Can you try pluging the keyboard in the cube, go upto partman, and then add the display keyboard and
look at /proc/bus/usb/devices (or lsusb or whatever output ?)

Here are the results of 3 attempts:
- mode expert, keyboard in the cube functionnal, I plug the 2nd keyboard in the display, I do a cat /proc/bus/usb/device, it hangs (state D) - not killable. The first keyboard is still working, the second isn't.

- mode install, keyboard in the cube functionnal, I select a keymap, the installer hang, the keyboard is still functionning, there is a cat /proc/bus/usb/device stuck in the process table (state D) - not killable.

- mode expert, keyboard in the cube functionnal, I jump to the cdrom detection routine, the installer hang and there is a modprobe -v usb_storage stuck in the process table (state D) - not killable

Now, I tryed the installer because my system wasn't comming up after a
kernel upgrade. Going from 2.6.7 to 2.6.8 makes the hotplug stall.

I bet you are not using the debian kernel though, right ?

nope, I'm running a debian kernel and did the upgrade to the new one :-(

now what?


Reply to: