Post your question in this forum. Peter Teoh htmldeveloper at gmail.com Wed Oct 3 19:33:48 EDT 2012 Previous message: Why "lsusb" return nothing? Join our community today! Registration is quick, simple and absolutely free. http://ecoflashapps.com/cannot-open/cannot-open-proc-bus-usb-no-such-file-or-directory.html
A: You need to have a version of cdrecord of at least 1.10a4. This is only needed on some models. Re: usbview error And what will be the outcome Code: cat /proc/bus/usb/devices Adv Reply July 5th, 2008 #5 rixtr66 View Profile View Forum Posts Private Message Cookies and cream Join VirtualBox with USB virtualisation, since that no longer depends on /proc/bus/usb :) ). http://www.linuxquestions.org/questions/linux-software-2/cannot-open-proc-bus-usb-devices-no-such-file-or-directory-378916/
If you're setting it up for the first time, you may want to reboot to make sure everything acts as you expect ... It's easiest to use the dmesg command to see the kernel debug messages. You probably need to load those drivers as modules, in which case lsmod will tell you whether it's already there or not. The versioning of SRUs are a bit different to normal development versioning.
You can tell which kind you have by output of lspci -v|grep HCI: 00:02.2 USB Controller: Silicon Integrated Systems [SiS] 7001 (rev 07) (prog-if 10 [OHCI]) 00:02.3 USB Controller: Silicon Integrated My usb sticks all work fine. However, you could put your kernel and initrd on a floppy and then use a USB root file system to get around this. Switch to a different USB connector on your computer.
If you're using any kernel that old, you should probably have some sort of vendor support agreement to handle issues that come up. Please get the fixes uploaded and tested in hardy, and attach tested debdiffs for the packages you think should be fixed in gutsy. Q: How do I get my printer working? browse this site And while there's only one OHCI driver (usb-ohci), you probably have a choice of two UHCI drivers, usb-uhci and the "alternate (JE)" driver uhci.
Changed in qemu: assignee: nobody → intuitivenipple importance: Undecided → Low status: New → In Progress Changed in kvm: assignee: nobody → intuitivenipple importance: Undecided → Low status: New → In In 2.2 and 2.4 kernels this directory should be created when you load usbcore, however there will be no content till you mount usbfs (the new name for usbdevfs). Recent 2.4.x kernels (such as 2.4.5) have AMD's workaround; upgrade your kernel. That type of controller doesn't do very much in hardware, which makes the software do more work (and need more memory).
My Athlon system, with AMD-756, doesn't like low speed devices. http://www.linuxforums.org/forum/hardware-peripherals/67429-cant-open-proc-bus-usb-devices.html The second solution should also work for USBView by the way. By the way, I see that vmware-server is mentioned here. Q: My Athlon system, with AMD-756, doesn't like low speed devices.
That's a common way for driver bugs to panic kernels, and there are at least three different scenarios to test: driver unused, driver in use but inactive, and driver active. http://ecoflashapps.com/cannot-open/cygisl-10-dll-cannot-open-shared-object-file-no-such-file-or-directory.html TJ (tj) wrote on 2007-10-27: #4 Your initial comment made me smile - it was the first thing I tried. Any help would be sincerely appreciated... Got any testing tips for Linux USB Device Drivers?
It also keeps on showing the message "Could not open /proc/bus/usb/devices". A: HotPlugging is a facility that can load and configure drivers as you plug in your devices. Re: USBView error from the Following List Posting https://lists.ubuntu.com/archives/ub...ne/148307.html Make sure you have usbfs mounted, which can be found in /etc/fstab, by adding the following line: Code: #
The Linux Kernel HOWTO will tell you how to build and install your new kernel. Ubuntu Ubuntu Insights Planet Ubuntu Activity Page Please read before SSO login Advanced Search Forum The Ubuntu Forum Community Ubuntu Official Flavours Support New to Ubuntu [ubuntu] [SOLVED] usbview error Having If there's any question, just include lspci -v output.) If you are having problems with your host controller being recognised, include output of lspci -v (at least for PCI based host
Changed in kvm: status: In Progress → Fix Committed Changed in qemu: status: In Progress → Fix Committed TJ (tj) on 2007-10-29 Changed in kvm: status: Fix Committed → In Progress Samson aspartat View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by aspartat Thread Tools Show Printable Version Email this Page Search this Q: Why doesn't /proc/bus/usb exist? Q: How do I make sure the correct modules are loaded?
First the backward-compatible way: all high speed (480 Mbit/sec) devices can be used at full speed (12 Mbit/sec) in all current Linux kernels. First, you need to know what kind of USB "Host Controller" hardware you have. It does not appear to be really frown to permission issues, because it links to the udev controlled interface. http://ecoflashapps.com/cannot-open/cannot-open-proc-bus-usb.html USB 2.0 (rev 51) (prog-if 20 [EHCI]) 00:11.0 USB Controller: OPTi Inc. 82C861 (rev 10) (prog-if 10 [OHCI]) Second, you need to know what Host Controller Driver (HCD) to use.
Home Forum Today's Posts | FAQ | Calendar | Community Groups | Forum Actions Mark Forums Read | Quick Links View Site Leaders | Unanswered Posts | Forum Rules Articles Marketplace I'm an end-user that wants the fix. A:In the 2.6.10 kernel the method of enumerating devices was changed to follow a similar algorithm as Windows (while the standard allows both many devices require the Windows method). The alternative is to add a complete new set of scripts and links, either: /etc/rc.S/S12mountdevusbfs -> /etc/init.d/mountdevusbfs.sh or /etc/rc2.d/S20mountdevusbfs -> /etc/init.d/mountdevusbfs.sh That, coupled with the alteration to KVM/QEMU would solve the
It affects handling of low speed devices (such as some mice and keyboards) when they're connected to the root hub. Scott -- Scott James Remnant
Then comes the sequence of port numbers for each of the intermediate hubs along the path to the device. Use a different cable. That's all there is to it. This prevents usb-storage from automatically detecting all the devices in your removable storage device.
I've tried to mount usbfs manually using mount -t usbfs none /proc/bus/usb I've tried modifying /etc/fstab by adding the following code at the bottom: usbfs /proc/bus/usb usbfs auto 0 0 The Re-opening the sysvinit task: I'm not affected by it myself, but I wonder why we cannot just enable the magic to make it work by default, from /etc/init.d/mountdevsubfs.sh (code commented out