Open SuSE 12.2 (amd64), USB scanner does not work when plugged on usb hub

English Hardware
#1

As of today, there is a problem with USB devices when they are plugged on a usb hub (Alcor Micro Corp. USB hub).
They simply do not work. However, if the devices are plugged on usb sockets on the computer they work fine.
This problem does not affect block devices, as usb disks and memory sticks do work on the hub.

I found out that the usb scanner (on the hub) works, if I run the scanning application as root.
The mouse and the keyboard do not.

Thanasis

#2

See if that solves the problem.

#3

What is this line supposed to do, why is it there in the first place?

My generic USB-Hub built-into my laptop did not work after upgrading to 12.2 from 12.1. I found this post, commented that line out, and now my USB-Hub is working fine again. Thanks!

#4

This is supposed to configure new seat (i.e. workplace) for external display+touchscreen device. But rule seems to be too generic. Could you please paste output of “lsusb” and “lsusb -t” in tags code so I can verify which hardware you have? Thank you.

#5

What does “new seat” mean? Could this be useful for me? I am using a laptop with 4 different docking stations during a typical week, all having different external displays & input devices. Manually switching is a bit of a pain, and I would welcome any automation steps (different keyboard layouts - switched via systray, different firewall settings - switched via systray, different sound devices (phonon should take care, but does not work), switching default printer, switching twin view resolutions (after docking and switching resolutions, I often only see window frames, not no content - pretty weird), etc.

Anyway, I will post the requested output next week (I won’t have access to this USB-hub until next week. EDIT-PS: it is not built into my laptop, it is built-into a laptop tray that I use as a quasi docking station at once place).

#6

This is abstraction of workplace, consisting usually of display and associated devices (keyboard, mouse, …). It is assumed that for each seat separate instance of X server is started and this X server will see only devices assigned to this seat. So you get multi-terminal system where each terminal runs own independent session and does not conflict with each other.

Could this be useful for me?

Probably, but as far I as I understand, implementation is incomplete currently.

firewall … sound devices … default printer …

Sound - possibly. Each seat gets own devices that it manages. The practical problem is per-seat persistent configuration. Printers - unlikely. It may be possible to assign specific printer device to specific seat, but again, your desktop environment needs support for per-seat configuration. Firewall - no. This is system-wide.

#7

[quote="“arvidjaar,post:6,topic:82983”]

This is abstraction of workplace, consisting usually of display and associated devices (keyboard, mouse, …). It is assumed that for each seat separate instance of X server is started and this X server will see only devices assigned to this seat. So you get multi-terminal system where each terminal runs own independent session and does not conflict with each other.

Probably, but as far I as I understand, implementation is incomplete currently.[/QUOTE]Just as an expansion upon arvidjaar’s post:

  • it refers to multiseat (see Multiseat configuration - Wikipedia, the free encyclopedia for a generic description).
  • static multiseat configurations have been available to Linux users for years
  • an automatic/hotplug multiseat implementation is under active development. If you are interested in those capabilities, then Fedora is the distro you’d want to go with right now. (openSUSE will not work currently in these regards because of some technical issues that will have to be addressed in future releases: see http://forums.opensuse.org/english/get-technical-help-here/install-boot-login/479385-multiseat-systemd.html)
  • you can do a static multiseat configuration under openSUSE 12.2, though (as I described in the last link) it is now a little bit more difficult to do than in the past because of the presence of systemd … actually, its more of a case that your configuration/setup options are currently a little more constrained than in the past … this too should resolve itself in time
#8

Likely not needed. You could test updated systemd package from https://bugzilla.novell.com/show_bug.cgi?id=782271 and add you comments there if something does not work.

#9

Here is my system witht he USB-Hub in my laptop tray connected (the one that did not work without uncommenting that line in /lib/udev/rules.d/71-seat.rules):


> lsusb
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
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 001 Device 003: ID 05ca:1814 Ricoh Co., Ltd HD Webcam
Bus 002 Device 008: ID 058f:6254 Alcor Micro Corp. USB Hub
Bus 002 Device 004: ID 413c:8187 Dell Computer Corp. DW375 Bluetooth Module
Bus 002 Device 005: ID 0a5c:5801 Broadcom Corp. BCM5880 Secure Applications Processor with fingerprint swipe sensor
Bus 002 Device 009: ID 046d:c52b Logitech, Inc. Unifying Receiver

and here is my system without that USB-Hub being connected:

> lsusb
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
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 001 Device 003: ID 05ca:1814 Ricoh Co., Ltd HD Webcam
Bus 002 Device 004: ID 413c:8187 Dell Computer Corp. DW375 Bluetooth Module
Bus 002 Device 005: ID 0a5c:5801 Broadcom Corp. BCM5880 Secure Applications Processor with fingerprint swipe sensor