- Community Home
- >
- Servers and Operating Systems
- >
- Integrity Servers
- >
- Re: USB Mouse/Keyboard not available when connecte...
Integrity Servers
1752254
Members
4280
Online
108785
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-05-2006 01:17 AM
тАО09-05-2006 01:17 AM
Hi,
I have 2 rx4640 with HP-UX B.11.23 (including HWEnable11i_B.11.23.0606.046.
When my USB Mouse/Keyboard are directly connected to the integrity server, every thing works fine and I get the following output from ioscan
Class I H/W Path Driver S/W State H/W Type Description
===============================================================================
OO 0 0/0/2/0 UsbOhci CLAIMED INTERFACE USB OHCI Interface
OO 1 0/0/2/0.0 UsbMiniBus CLAIMED INTERFACE USB Composite Device
OO 5 0/0/2/0.0.0 UsbBootKeyboard CLAIMED DEVICE USB Boot Protocol Keyboard
OO 3 0/0/2/1 UsbOhci CLAIMED INTERFACE USB OHCI Interface
OO 2 0/0/2/1.0 UsbMiniBus CLAIMED INTERFACE USB Composite Device
OO 6 0/0/2/1.0.0 UsbBootMouse CLAIMED DEVICE USB Boot Protocol Mouse
OO 4 0/0/2/2 UsbEhci CLAIMED INTERFACE USB EHCI Interface
For our customer, we have to deport Screen/Keyboard/Mouse in a control room. So we inserted extension cables.
No problem with the screen.
During the EFI boot, the keyboard is fully available : that means that the extension is OK (we also tested the extension cables with a web server without any problems).
Yet, after the boot of the server, we get the following output from the ioscan command :
Class I H/W Path Driver S/W State H/W Type Description
==============================================================================
OO 0 0/0/2/0 UsbOhci CLAIMED INTERFACE USB OHCI Interface
unknown -1 0/0/2/0.0 UNCLAIMED UNKNOWN OO Device Driver
OO 1 0/0/2/1 UsbOhci CLAIMED INTERFACE USB OHCI Interface
unknown -1 0/0/2/1.0 UNCLAIMED UNKNOWN OO Device Driver
OO 5 0/0/2/2 UsbEhci CLAIMED INTERFACE USB EHCI Interface
The Mouse/Keyboard are not available.
Last year, we had a similar architecture that was working without any trouble with the same extension cables but the result from the ioscan command was a little bit different :
usb 0 0/0/2/0 hcd CLAIMED INTERFACE NEC USB Interface
usbhub 0 0/0/2/0.1 hub CLAIMED DEVICE USB Root Hub
usbhub 2 0/0/2/0.1.2 hub CLAIMED DEVICE USB Hub
usbhid 1 0/0/2/0.1.2.3 hid CLAIMED DEVICE USB HID Kbd(0)
usb 1 0/0/2/1 hcd CLAIMED INTERFACE NEC USB Interface
usbhub 1 0/0/2/1.1 hub CLAIMED DEVICE USB Root Hub
/dev/hub
usbhub 3 0/0/2/1.1.2 hub CLAIMED DEVICE USB Hub
usbhid 0 0/0/2/1.1.2.3 hid CLAIMED DEVICE USB HID Mouse(1)
/dev/hid/firstkbd /dev/hid/hid_007 /dev/hid/kbd_000 /dev/hid/mouse_001
/dev/hid/firstmouse /dev/hid/hid_008 /dev/hid/kbd_001 /dev/hid/mouse_002
/dev/hid/hid_000 /dev/hid/hid_009 /dev/hid/kbd_002 /dev/hid/mouse_003
/dev/hid/hid_001 /dev/hid/hid_010 /dev/hid/kbd_003 /dev/hid/mouse_004
/dev/hid/hid_002 /dev/hid/hid_011 /dev/hid/kbd_004 /dev/hid/mouse_005
/dev/hid/hid_003 /dev/hid/hid_012 /dev/hid/kbd_005 /dev/hid/mouse_006
/dev/hid/hid_004 /dev/hid/hid_013 /dev/hid/kbd_006 /dev/hid/mouse_007
/dev/hid/hid_005 /dev/hid/hid_014 /dev/hid/kbd_007
/dev/hid/hid_006 /dev/hid/hid_015 /dev/hid/mouse_000
usb 2 0/0/2/2 ehci CLAIMED INTERFACE NEC USB Interface
Has anything change for USB on HPUX.
Any help is welcome.
Regards.
Bruno
I have 2 rx4640 with HP-UX B.11.23 (including HWEnable11i_B.11.23.0606.046.
When my USB Mouse/Keyboard are directly connected to the integrity server, every thing works fine and I get the following output from ioscan
Class I H/W Path Driver S/W State H/W Type Description
===============================================================================
OO 0 0/0/2/0 UsbOhci CLAIMED INTERFACE USB OHCI Interface
OO 1 0/0/2/0.0 UsbMiniBus CLAIMED INTERFACE USB Composite Device
OO 5 0/0/2/0.0.0 UsbBootKeyboard CLAIMED DEVICE USB Boot Protocol Keyboard
OO 3 0/0/2/1 UsbOhci CLAIMED INTERFACE USB OHCI Interface
OO 2 0/0/2/1.0 UsbMiniBus CLAIMED INTERFACE USB Composite Device
OO 6 0/0/2/1.0.0 UsbBootMouse CLAIMED DEVICE USB Boot Protocol Mouse
OO 4 0/0/2/2 UsbEhci CLAIMED INTERFACE USB EHCI Interface
For our customer, we have to deport Screen/Keyboard/Mouse in a control room. So we inserted extension cables.
No problem with the screen.
During the EFI boot, the keyboard is fully available : that means that the extension is OK (we also tested the extension cables with a web server without any problems).
Yet, after the boot of the server, we get the following output from the ioscan command :
Class I H/W Path Driver S/W State H/W Type Description
==============================================================================
OO 0 0/0/2/0 UsbOhci CLAIMED INTERFACE USB OHCI Interface
unknown -1 0/0/2/0.0 UNCLAIMED UNKNOWN OO Device Driver
OO 1 0/0/2/1 UsbOhci CLAIMED INTERFACE USB OHCI Interface
unknown -1 0/0/2/1.0 UNCLAIMED UNKNOWN OO Device Driver
OO 5 0/0/2/2 UsbEhci CLAIMED INTERFACE USB EHCI Interface
The Mouse/Keyboard are not available.
Last year, we had a similar architecture that was working without any trouble with the same extension cables but the result from the ioscan command was a little bit different :
usb 0 0/0/2/0 hcd CLAIMED INTERFACE NEC USB Interface
usbhub 0 0/0/2/0.1 hub CLAIMED DEVICE USB Root Hub
usbhub 2 0/0/2/0.1.2 hub CLAIMED DEVICE USB Hub
usbhid 1 0/0/2/0.1.2.3 hid CLAIMED DEVICE USB HID Kbd(0)
usb 1 0/0/2/1 hcd CLAIMED INTERFACE NEC USB Interface
usbhub 1 0/0/2/1.1 hub CLAIMED DEVICE USB Root Hub
/dev/hub
usbhub 3 0/0/2/1.1.2 hub CLAIMED DEVICE USB Hub
usbhid 0 0/0/2/1.1.2.3 hid CLAIMED DEVICE USB HID Mouse(1)
/dev/hid/firstkbd /dev/hid/hid_007 /dev/hid/kbd_000 /dev/hid/mouse_001
/dev/hid/firstmouse /dev/hid/hid_008 /dev/hid/kbd_001 /dev/hid/mouse_002
/dev/hid/hid_000 /dev/hid/hid_009 /dev/hid/kbd_002 /dev/hid/mouse_003
/dev/hid/hid_001 /dev/hid/hid_010 /dev/hid/kbd_003 /dev/hid/mouse_004
/dev/hid/hid_002 /dev/hid/hid_011 /dev/hid/kbd_004 /dev/hid/mouse_005
/dev/hid/hid_003 /dev/hid/hid_012 /dev/hid/kbd_005 /dev/hid/mouse_006
/dev/hid/hid_004 /dev/hid/hid_013 /dev/hid/kbd_006 /dev/hid/mouse_007
/dev/hid/hid_005 /dev/hid/hid_014 /dev/hid/kbd_007
/dev/hid/hid_006 /dev/hid/hid_015 /dev/hid/mouse_000
usb 2 0/0/2/2 ehci CLAIMED INTERFACE NEC USB Interface
Has anything change for USB on HPUX.
Any help is welcome.
Regards.
Bruno
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-05-2006 05:56 AM
тАО09-05-2006 05:56 AM
Solution
Yes, you are right saying about USB change on HPUX. Earlier there used to be a legacy USB driver having modules hid, hub, hcd and usbd which you see in your previous ioscan output.
There is a new USB driver as USB-00 bundle having modules like MouseMUX, UsbBootKeyboard, UsbBootMouse, UsbHub,
UsbMiniBus and UsbOhci as you see in the latest ioscan output.
Check for the patch PHKL_34588 installed on the system.
check out the outout of "ioscan -e" and try running "ioscan -f" .
Take a look at the link below and verify the devices files for USB mouse and keyboard if created.
http://docs.hp.com/en/5991-2710/ch04s07.html
It is also possible to use old legacy USB drivers by removing the new UDB driver modules and loading legacy modules in the kernel.
There is a new USB driver as USB-00 bundle having modules like MouseMUX, UsbBootKeyboard, UsbBootMouse, UsbHub,
UsbMiniBus and UsbOhci as you see in the latest ioscan output.
Check for the patch PHKL_34588 installed on the system.
check out the outout of "ioscan -e" and try running "ioscan -f" .
Take a look at the link below and verify the devices files for USB mouse and keyboard if created.
http://docs.hp.com/en/5991-2710/ch04s07.html
It is also possible to use old legacy USB drivers by removing the new UDB driver modules and loading legacy modules in the kernel.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-07-2006 04:58 AM
тАО09-07-2006 04:58 AM
Re: USB Mouse/Keyboard not available when connected through USB Active Extension Cable.
Hi Sameer,
With the information you provided me, I tried to progress on my problem.
The problem with the USB-00 bundle is that there's no USBHub module.
Sam->Kernel Configuration->Modules (All)
UsbBootKeyboard static static best
UsbBootMouse static static best
UsbBulkOnlyMS unused unused explicit
UsbEhci static static best
UsbHid static static best
UsbMiniBus static static best
UsbOhci static static best
UsbScsiAdaptor unused unused explicit
And in my previous configuration my extension cable is seen as a hub and manage by the 'hub' module from the legacy USB.
The PHKL_34588 is installed on my system and also the PHKL_32629.
ioscan -e and -f are consistant:
H/W Path Class Description
==========================================================
root
0 ioa System Bus Adapter (1229)
0/0 ba Local PCI-X Bus Adapter (122e)
0/0/1/0 tty PCI SimpleComm (103c1290)
0/0/1/1 tty PCI Serial (103c1048)
0/0/2/0 OO USB OHCI Interface
0/0/2/0.0 unknown OO Device Driver
0/0/2/1 OO USB OHCI Interface
0/0/2/1.0 unknown OO Device Driver
0/0/2/2 OO USB EHCI Interface
Class I H/W Path Driver S/W State H/W Type Description
==============================================================================
root 0 root CLAIMED BUS_NEXUS
ioa 0 0 sba CLAIMED BUS_NEXUS System Bus Adapter (1229)
ba 0 0/0 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (122e)
tty 0 0/0/1/0 asio0 CLAIMED INTERFACE PCI SimpleComm (103c1290)
tty 1 0/0/1/1 asio0 CLAIMED INTERFACE PCI Serial (103c1048)
OO 0 0/0/2/0 UsbOhci CLAIMED INTERFACE USB OHCI Interface
unknown -1 0/0/2/0.0 UNCLAIMED UNKNOWN OO Device Driver
OO 1 0/0/2/1 UsbOhci CLAIMED INTERFACE USB OHCI Interface
unknown -1 0/0/2/1.0 UNCLAIMED UNKNOWN OO Device Driver
OO 5 0/0/2/2 UsbEhci CLAIMED INTERFACE USB EHCI Interface
Finally I remove (swremove) the USB-00 bundle from my system. After reboot it works fine.
Do you know any way to ask HP if there are some evolution planned for the USB-00 in the near future to manage USBHub ?
Thanks for all your suggestions.
Best regards.
Bruno
With the information you provided me, I tried to progress on my problem.
The problem with the USB-00 bundle is that there's no USBHub module.
Sam->Kernel Configuration->Modules (All)
UsbBootKeyboard static static best
UsbBootMouse static static best
UsbBulkOnlyMS unused unused explicit
UsbEhci static static best
UsbHid static static best
UsbMiniBus static static best
UsbOhci static static best
UsbScsiAdaptor unused unused explicit
And in my previous configuration my extension cable is seen as a hub and manage by the 'hub' module from the legacy USB.
The PHKL_34588 is installed on my system and also the PHKL_32629.
ioscan -e and -f are consistant:
H/W Path Class Description
==========================================================
root
0 ioa System Bus Adapter (1229)
0/0 ba Local PCI-X Bus Adapter (122e)
0/0/1/0 tty PCI SimpleComm (103c1290)
0/0/1/1 tty PCI Serial (103c1048)
0/0/2/0 OO USB OHCI Interface
0/0/2/0.0 unknown OO Device Driver
0/0/2/1 OO USB OHCI Interface
0/0/2/1.0 unknown OO Device Driver
0/0/2/2 OO USB EHCI Interface
Class I H/W Path Driver S/W State H/W Type Description
==============================================================================
root 0 root CLAIMED BUS_NEXUS
ioa 0 0 sba CLAIMED BUS_NEXUS System Bus Adapter (1229)
ba 0 0/0 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (122e)
tty 0 0/0/1/0 asio0 CLAIMED INTERFACE PCI SimpleComm (103c1290)
tty 1 0/0/1/1 asio0 CLAIMED INTERFACE PCI Serial (103c1048)
OO 0 0/0/2/0 UsbOhci CLAIMED INTERFACE USB OHCI Interface
unknown -1 0/0/2/0.0 UNCLAIMED UNKNOWN OO Device Driver
OO 1 0/0/2/1 UsbOhci CLAIMED INTERFACE USB OHCI Interface
unknown -1 0/0/2/1.0 UNCLAIMED UNKNOWN OO Device Driver
OO 5 0/0/2/2 UsbEhci CLAIMED INTERFACE USB EHCI Interface
Finally I remove (swremove) the USB-00 bundle from my system. After reboot it works fine.
Do you know any way to ask HP if there are some evolution planned for the USB-00 in the near future to manage USBHub ?
Thanks for all your suggestions.
Best regards.
Bruno
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-07-2006 10:42 AM
тАО09-07-2006 10:42 AM
Re: USB Mouse/Keyboard not available when connected through USB Active Extension Cable.
Hi Bruno,
You nailed it correctly about UsbHub and this link of May2005 11.23 release notes confirms the same saying that "USB-00 does not support USB hubs and if USB hubs are required, you should revert to the legacy USB driver delivered as a part of the core kernel by uninstalling this product. See the product README notes for more details".
http://docs.hp.com/en/5991-1101/ch04s07.html#cihbdijh
As per the document, the support of USB hubs was taken out in USB-00 ver. C.01.00.00. I think the same applies to latest version C.01.03.01 ( which you might have ) as well.
If you have same USB-00 installed on another server, take a look at the readme using
# swlist -a readme USB-00 | more
You can log a call with HP support and seek their clarification about why USB hub was removed and future enhancements planned for USB-00.
You nailed it correctly about UsbHub and this link of May2005 11.23 release notes confirms the same saying that "USB-00 does not support USB hubs and if USB hubs are required, you should revert to the legacy USB driver delivered as a part of the core kernel by uninstalling this product. See the product README notes for more details".
http://docs.hp.com/en/5991-1101/ch04s07.html#cihbdijh
As per the document, the support of USB hubs was taken out in USB-00 ver. C.01.00.00. I think the same applies to latest version C.01.03.01 ( which you might have ) as well.
If you have same USB-00 installed on another server, take a look at the readme using
# swlist -a readme USB-00 | more
You can log a call with HP support and seek their clarification about why USB hub was removed and future enhancements planned for USB-00.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP