Comment 24 for bug 545795

Revision history for this message
James Neave (roboj1m) wrote : Re: apparmor driver blocks access to hostdev and pcidev devices

Rebooting the PC fixed that problem so I guess something hadn't been reloaded.
I've also added /dev/** rwk, to the apparmour profile. Taking it away doesn't stop it from working again, although I've not tried rebooting the host yet.

It still doesn't quite work however, as now (on the guest) I see this in lsusb:

james@myth:~$ lsusb
Bus 001 Device 002: ID 2040:9950 Hauppauge
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

but in dmesg I see:

[ 5.806567] dib0700: loaded with support for 13 different device-types
[ 5.816285] dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in warm state.
[ 5.816612] dvb-usb: This USB2.0 device cannot be run on a USB1.1 port. (it lacks a hardware PID filter)
[ 5.816682] dvb-usb: Hauppauge Nova-T 500 Dual DVB-T error while loading driver (-19)
[ 5.816787] usbcore: registered new interface driver dvb_usb_dib0700

Different problem?
Why is it on a USB 1 port? Is the virtual USB hub 1.1? Can I change that?

Regards,

James.