iDRAC 7/PowerEdge R720 console issues with Fedora 17

Stuart_Hayes at Dell.com Stuart_Hayes at Dell.com
Mon Jul 2 15:50:49 CDT 2012


Try kernel parameter “usbcore.autosuspend=-1” to work around this issue.
Stuart


From: linux-poweredge-bounces-Lists On Behalf Of Kevin White
Sent: Friday, June 22, 2012 10:10 AM
To: Stroller
Cc: linux-poweredge-Lists
Subject: Re: iDRAC 7/PowerEdge R720 console issues with Fedora 17

On 6/22/2012 10:10 AM, Stroller wrote:



I'm using IE 9 on Windows 7 to access the iDRAC 7.  It works: I can

watch the unit boot.  I can hit keys and go into the system setup

program.  I can even interact with Grub when Fedora starts to boot...but

as soon as it finishes booting and drops to a login: prompt, I can't

type anything.  (This is a very basic install of F17, no GUI, booting to

a text console.)



I plugged a keyboard in directly to the unit, and it works.  I can

actually see what I'm typing at the keyboard in the iDRAC remote session.



You appear to be missing a driver module that allows the PC to recognise the iDRAC as an input device.



$ zcat /proc/config.gz | grep -i keyb



Boot with a bunch of LiveCDs, see which ones work. On each - working and non-working - run `lsmod` and redirect the output to a text file. Compare the results.



I would try the installer CD first - if this does work then it should be relatively easy to find which module you're missing. Kernel versions should match up, too.



Also might be worth grabbing a copy of /proc/config.gz for your installed system and each liveCD.




Well, what is weird is that, twice (on Fedora 17, freshly booting), I've actually seen the DRAC console work, for a few seconds.  One, it was long enough to log in and type a command, and the second, it was enough to press "enter" a few times.  Then, it stops registering keyboard input.

(To make clear: on CentOS 6.2, none of this was a problem.)

This shows up in the dmesg:

[    2.881570] usb 1-1.6.1: new high-speed USB device number 5 using ehci_hcd
[    2.973520] usb 1-1.6.1: New USB device found, idVendor=0624, idProduct=0249
[    2.978932] usb 1-1.6.1: New USB device strings: Mfr=4, Product=5, SerialNumber=6
[    2.984341] usb 1-1.6.1: Product: Keyboard/Mouse Function
[    2.984344] usb 1-1.6.1: Manufacturer: Avocent
[    2.984346] usb 1-1.6.1: SerialNumber: 20110426
[    2.990493] input: Avocent Keyboard/Mouse Function as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6.1/1-1.6.1:1.0/input/input3
[    2.990775] generic-usb 0003:0624:0249.0003: input,hidraw2: USB HID v1.00 Keyboard [Avocent Keyboard/Mouse Function] on usb-0000:00:1a.0-1.6.1/input0
[    2.991812] input: Avocent Keyboard/Mouse Function as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6.1/1-1.6.1:1.1/input/input4
[    2.991864] dracut: Scanning devices sda1  for LVM logical volumes vg_vmhost1/lv_root vg_vmhost1/lv_swap
[    2.992003] generic-usb 0003:0624:0249.0004: input,hidraw3: USB HID v1.00 Mouse [Avocent Keyboard/Mouse Function] on usb-0000:00:1a.0-1.6.1/input1
[    2.993035] input: Avocent Keyboard/Mouse Function as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6.1/1-1.6.1:1.2/input/input5
[    2.993163] generic-usb 0003:0624:0249.0005: input,hidraw4: USB HID v1.00 Mouse [Avocent Keyboard/Mouse Function] on usb-0000:00:1a.0-1.6.1/input2

which tells me that the Avocent KVM stuff is detected.  I looked later to see if there were any errors on the device, something to make it stop working.  There weren't.

There's no /proc/config.gz in Fedora 17.  However, I think the same thing is in /boot/config-$(uname -r).  Although, since the driver for the device is loading (and has been seen to work, momentarily), I'm not sure what I'd be looking for here.  I'm pretty sure the KVM keyboard/mouse show up to the system as a USB HID, just like any other keyboard/mouse.

And, since a USB keyboard plugged in to the unit is still working, I know that it isn't the entire USB subsystem that has crashed, or the USB_HID driver or something.

Looking more at dmesg:

[    1.730237] usb 1-1: new high-speed USB device number 2 using ehci_hcd
[    1.848447] usb 1-1: New USB device found, idVendor=8087, idProduct=0024
[    1.853025] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    1.857950] hub 1-1:1.0: USB hub found
[    1.862523] hub 1-1:1.0: 6 ports detected


Oh, and there's a hub attached to that hub:

[    2.456116] usb 1-1.6: New USB device found, idVendor=0624, idProduct=0248
[    2.460196] usb 1-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    2.557859] usb 1-1.6: Product: Gadget USB HUB
[    2.562405] usb 1-1.6: Manufacturer: no manufacturer
[    2.566798] usb 1-1.6: SerialNumber: 0123456789
[    2.571479] hub 1-1.6:1.0: USB hub found
[    2.576019] hub 1-1.6:1.0: 6 ports detected

That tells me that when:

[    2.881570] usb 1-1.6.1: new high-speed USB device number 5 using ehci_hcd

is detected a second later, it is connected through two hubs, the hub that's on 1-1.6 and the one on 1-1.

I'm not really sure what could be going wrong...

Kevin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.us.dell.com/pipermail/linux-poweredge/attachments/20120702/1d4bc49d/attachment.html 


More information about the Linux-PowerEdge mailing list