Emmet. I just realised you seem to be suggest it worked with the patch
(for KVM on Hardy wasn't it?) but the patch simply replaces
/proc/bus/usb/ with /dev/bus/usb/ but there is no 'devices' file link
there *unless* the uncommented magic in /etc/init.d/mountdevsubfs.sh (or
equivalent) has created a usbfs and linked /dev/bus/usb/devices into it.
I've tested the KVM Gutsy patch here. Without mounting the usbfs (using
my new mountdevusbfs.sh script) I get:
$ ls -a /dev/bus/usb
. .. 001 002 003 004 005
info usbhost
Could not open /dev/bus/usb/devices
But once the usbfs is mounted and the 'devices' link created, it works:
$ sudo /etc/init.d/mountdevusbfs.sh start
$ ls -a /dev/bus/usb
. .. 001 002 003 004 005 devices .usbfs
info usbhost
Device 5.4, speed 480 Mb/s
Class 00: USB device 0781:5151, Cruzer Micro
Device 5.3, speed 480 Mb/s
Class ef: USB device 05ca:1836
Device 3.3, speed 12 Mb/s
Class e0: USB device 044e:300d, UGX
Is it possible the Hardy init is creating the usbfs and linking devices,
or is there some confusion here?
** Attachment added: "Proposed /etc/init.d/mountdevusbfs.sh"
http://launchpadlibrarian.net/10380330/mountdevusbfs.sh
--
Could not open /proc/bus/usb/devices
https://bugs.launchpad.net/bugs/156085
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
