Ask Your Question
0

[Solved] Problem with Fedora 17 and devices connected to USB HUB

asked 2012-06-06 10:38:57 -0600

Nelson Caballero gravatar image

updated 2012-06-06 11:02:05 -0600

Hi!

I come with a new challenge for you :p

The problem: After install and update Fedora 17 on my laptop, my USB mouse and keyboard doesn't works. Both of them are connected to a USB HUB, and they works fine on Fedora 16 and Windows 7. If I connect it directly to a USB Port, then works nice.

Any solution?

Output for lsusb with devices connected to USB HUB:

$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 010: ID 058f:6254 Alcor Micro Corp. USB Hub
Bus 002 Device 011: ID 1241:1503 Belkin Keyboard
Bus 002 Device 004: ID 05a9:2640 OmniVision Technologies, Inc. OV2640 Webcam
Bus 003 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 002 Device 012: ID 0458:00ec KYE Systems Corp. (Mouse Systems) 
Bus 003 Device 003: ID 413c:8126 Dell Computer Corp. Wireless 355 Bluetooth
Bus 003 Device 004: ID 0a5c:4502 Broadcom Corp. Keyboard (Boot Interface Subclass)
Bus 003 Device 005: ID 0a5c:4503 Broadcom Corp. Mouse (Boot Interface Subclass)

Output for lsusb with mouse directly connected:

$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 003: ID 0458:00ec KYE Systems Corp. (Mouse Systems) 
Bus 002 Device 004: ID 05a9:2640 OmniVision Technologies, Inc. OV2640 Webcam
Bus 003 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 003 Device 003: ID 413c:8126 Dell Computer Corp. Wireless 355 Bluetooth
Bus 003 Device 004: ID 0a5c:4502 Broadcom Corp. Keyboard (Boot Interface Subclass)
Bus 003 Device 005: ID 0a5c:4503 Broadcom Corp. Mouse (Boot Interface Subclass)

If you need another info, please tell me :)

Thanks!

edit retag flag offensive close merge delete

Comments

This worked like a charm for me. Tested in Fedora 18 i686 (32 bit PC)

Sourav gravatar imageSourav ( 2013-08-25 02:34:47 -0600 )edit

@Sourav: if it works for you, please upvote the answer. Please post only solutions as answers. I've converted your answer to a comment.

FranciscoD_ gravatar imageFranciscoD_ ( 2013-08-25 06:18:06 -0600 )edit

1 Answer

Sort by ยป oldest newest most voted
1

answered 2012-06-06 11:01:37 -0600

Nelson Caballero gravatar image

I find a solution for my problem. If anyone have this problem, here is solution:

https://bugzilla.redhat.com/show_bug.cgi?id=823815#c7

I commented out this line in /lib/udev/rules.d/71-seat.rules:

# Mimo 720, with integrated USB hub, displaylink graphics, and e2i touchscreen
#SUBSYSTEM=="usb", ATTR{idVendor}=="058f", ATTR{idProduct}=="6254", ENV{ID_AUTOSEAT}="1"

and now everything is working nicely.

Enjoy!

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2012-06-06 10:38:57 -0600

Seen: 11,120 times

Last updated: Aug 25 '13