On 29/01/12 09:42 AM, H.S. wrote: >> This leads me to believe the device name being assigned to the device >> is "usb0". Try this in /etc/network/interfaces: >> >> iface usb0 inet manual >> >> That line should tell ifupdown that the configuration is manual. And >> since it is a configuration for ifupdown that tells NetworkManager to >> leave it alone. I am pretty sure that will work. > > That did help a little. Inserted that line in 'interfaces' file, > restarted networking and network-manager and now Tomtom is not tried as > a network device. > > However, it is still grayed out in virtualbox and the VM doesn't see it > as attached at all. Same behavior whether I have a filter for it in VB's > USB devices filters section. > > BTW, I have, since yesterday, virtualization enabled on my machine (amd > machine, it is called AMD-V in it?). Is this necessary?
Well, a little success. Based on the thread here: https://forums.virtualbox.org/viewtopic.php?t=4932 , I created a rules file in /etc/udev.d with the following contents: KERNEL=="vboxdrv", NAME="vboxdrv", OWNER="root", GROUP="root", MODE="0600" #these two lines give access permission to vboxusers to properly work with usb nodes, this could be security risk (bnc#664520) !! SUBSYSTEM=="usb_device", ATTR{devnum}=="?*", ATTR{busnum}=="?*",SYMLINK+="vboxusb/$attr{busnum}/$attr{devnum}", GROUP="vboxusers" SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTR{devnum}=="?*", ATTR{busnum}=="?*",SYMLINK="vboxusb/$attr{busnum}/$attr{devnum}", GROUP="vboxusers" Now the Tomtom device is visible to the guest OS and I can check or uncheck it. However, Tomtom's application in Windows 7(guest OS) still is unable to see that the device is connected. Coming back to the first point, I see that this is a permissions issue. Is there a better way than the brute force method in the rules files above? -- Please reply to this list only. I read this list on its corresponding newsgroup on gmane.org. Replies sent to my email address are just filtered to a folder in my mailbox and get periodically deleted without ever having been read. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jg4tj6$evb$1...@dough.gmane.org
