Why "lsusb" return nothing?

Discussion:

Peter Teoh

2012-09-29 01:42:12 UTC

I entered "lsusb" at the command line (as root) and nothing is return,
not even any error message.

Doing a strace the last few lines are:

open("/dev/bus/usb", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = -1
ENOENT (No such file or directory)
open("/proc/bus/usb", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = -1
ENOENT (No such file or directory)

What happened?

This is Ubuntu 10.04 (it used NOT to be like that, not sure I what did
wrong last time). But running a VirtualBox INSIDE this same OS, I
was able to get result from "lsusb" (after enabling the USB devices in
VirtualBox interface) and strace gives result:

open("/dev/bus/usb/001/002", O_RDWR) = 3
ioctl(3, USBDEVFS_IOCTL, 0xbff6f75c) = -1 ENOTTY (Inappropriate
ioctl for device)
close(3) = 0
open("/dev/bus/usb/001/001", O_RDWR) = 3

Why the difference?

--
Regards,
Peter Teoh

Mark Bishop

2012-09-29 02:21:55 UTC

Permalink

You don't have the USB module loaded or it isn't compiled into your kernel.

Post by Peter Teoh
I entered "lsusb" at the command line (as root) and nothing is return,
not even any error message.
open("/dev/bus/usb", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = -1
ENOENT (No such file or directory)
open("/proc/bus/usb", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = -1
ENOENT (No such file or directory)
What happened?
This is Ubuntu 10.04 (it used NOT to be like that, not sure I what did
wrong last time). But running a VirtualBox INSIDE this same OS, I
was able to get result from "lsusb" (after enabling the USB devices in
open("/dev/bus/usb/001/002", O_RDWR) = 3
ioctl(3, USBDEVFS_IOCTL, 0xbff6f75c) = -1 ENOTTY (Inappropriate
ioctl for device)
close(3) = 0
open("/dev/bus/usb/001/001", O_RDWR) = 3
Why the difference?
--
Regards,
Peter Teoh
_______________________________________________
Kernelnewbies mailing list
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.

Peter Teoh

2012-09-29 05:07:59 UTC

Permalink

what are the implication (or symptoms) of that statement? how do i know that?

ps -ef |grep usb

root 232 2 0 07:44 ? 00:00:18 [usb-storage]
root 266 2 0 07:44 ? 00:00:14 [usb-storage]
root 6757 2 0 13:05 ? 00:00:00 [usb-storage]
root 6831 5920 0 13:05 pts/0 00:00:00 grep --color=auto usb

lsmod |grep usb

usbhid 39214 0
hid 89444 1 usbhid
usb_storage 49986 4

right now, i have no problem in accessing any USB devices. when i
mirror the internal partition into an external USB storage disk, the
external USB storage partition successfully the exact identical OS -
with exactly the same sympton: "lsusb" returning nothing.

it used to be working, and there is completely no change in the kernel
or module, as far as i am aware. and "working" means "lsusb" used to
return everything.

You don't have the USB module loaded or it isn't compiled into your kernel.

Post by Peter Teoh
I entered "lsusb" at the command line (as root) and nothing is return,
not even any error message.
open("/dev/bus/usb", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = -1
ENOENT (No such file or directory)
open("/proc/bus/usb", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = -1
ENOENT (No such file or directory)
What happened?
This is Ubuntu 10.04 (it used NOT to be like that, not sure I what did
wrong last time). But running a VirtualBox INSIDE this same OS, I
was able to get result from "lsusb" (after enabling the USB devices in
open("/dev/bus/usb/001/002", O_RDWR) = 3
ioctl(3, USBDEVFS_IOCTL, 0xbff6f75c) = -1 ENOTTY (Inappropriate
ioctl for device)
close(3) = 0
open("/dev/bus/usb/001/001", O_RDWR) = 3
Why the difference?
--
Regards,
Peter Teoh
________________________________
Kernelnewbies mailing list
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.

--
Regards,
Peter Teoh

Mark Bishop

2012-09-29 05:12:16 UTC

Permalink

What does 'find /dev/ | grep dev' show

Post by Peter Teoh
what are the implication (or symptoms) of that statement? how do i know that?

ps -ef |grep usb

root 232 2 0 07:44 ? 00:00:18 [usb-storage]
root 266 2 0 07:44 ? 00:00:14 [usb-storage]
root 6757 2 0 13:05 ? 00:00:00 [usb-storage]
root 6831 5920 0 13:05 pts/0 00:00:00 grep --color=auto usb

lsmod |grep usb

usbhid 39214 0
hid 89444 1 usbhid
usb_storage 49986 4
right now, i have no problem in accessing any USB devices. when i
mirror the internal partition into an external USB storage disk, the
external USB storage partition successfully the exact identical OS -
with exactly the same sympton: "lsusb" returning nothing.
it used to be working, and there is completely no change in the kernel
or module, as far as i am aware. and "working" means "lsusb" used to
return everything.

You don't have the USB module loaded or it isn't compiled into your

kernel.

Post by Peter Teoh
I entered "lsusb" at the command line (as root) and nothing is

return,

-1

Post by Peter Teoh
ENOENT (No such file or directory)
What happened?
This is Ubuntu 10.04 (it used NOT to be like that, not sure I what

did

Post by Peter Teoh
wrong last time). But running a VirtualBox INSIDE this same OS, I
was able to get result from "lsusb" (after enabling the USB devices

Post by Peter Teoh
open("/dev/bus/usb/001/002", O_RDWR) = 3
ioctl(3, USBDEVFS_IOCTL, 0xbff6f75c) = -1 ENOTTY (Inappropriate
ioctl for device)
close(3) = 0
open("/dev/bus/usb/001/001", O_RDWR) = 3
Why the difference?
--
Regards,
Peter Teoh
________________________________
Kernelnewbies mailing list
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.

--
Regards,
Peter Teoh

--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.

Peter Teoh

2012-09-29 05:17:46 UTC

Permalink

Post by Mark Bishop
What does 'find /dev/ | grep dev' show

http://pastebin.com/tuh7fv3v

any idea?

Post by Mark Bishop

Post by Peter Teoh
what are the implication (or symptoms) of that statement? how do i know that?

ps -ef |grep usb

root 232 2 0 07:44 ? 00:00:18 [usb-storage]
root 266 2 0 07:44 ? 00:00:14 [usb-storage]
root 6757 2 0 13:05 ? 00:00:00 [usb-storage]
root 6831 5920 0 13:05 pts/0 00:00:00 grep --color=auto usb

lsmod |grep usb

usbhid 39214 0
hid 89444 1 usbhid
usb_storage 49986 4
right now, i have no problem in accessing any USB devices. when i
mirror the internal partition into an external USB storage disk, the
external USB storage partition successfully the exact identical OS -
with exactly the same sympton: "lsusb" returning nothing.
it used to be working, and there is completely no change in the kernel
or module, as far as i am aware. and "working" means "lsusb" used to
return everything.

You don't have the USB module loaded or it isn't compiled into your kernel.

Post by Peter Teoh
I entered "lsusb" at the command line (as root) and nothing is return,
not even any error message.
open("/dev/bus/usb", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = -1
ENOENT (No such file or directory)
open("/proc/bus/usb", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = -1
ENOENT (No such file or directory)
What happened?
This is Ubuntu 10.04 (it used NOT to be like that, not sure I what did
wrong last time). But running a VirtualBox INSIDE this same OS, I
was able to get result from "lsusb" (after enabling the USB devices in
open("/dev/bus/usb/001/002", O_RDWR) = 3
ioctl(3, USBDEVFS_IOCTL, 0xbff6f75c) = -1 ENOTTY (Inappropriate
ioctl for device)
close(3) = 0
open("/dev/bus/usb/001/001", O_RDWR) = 3
Why the difference?
--
Regards,
Peter Teoh
________________________________
Kernelnewbies mailing list
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.

--
Regards,
Peter Teoh

2012-09-30 22:49:13 UTC

Permalink

I entered "lsusb" at the command line (as root) and nothing is return, not even any error message.
open("/dev/bus/usb", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/proc/bus/usb", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = -1 ENOENT (No such file
or directory)
What happened?
This is Ubuntu 10.04 (it used NOT to be like that, not sure I what did wrong last time).

Ubuntu 10.04 Lucid uses kernel version 2.6.32. This was the first kernel version used in Ubuntu
that uses devtmpfs for /dev/.

$ grep DEVTMPFS /boot/config-2.6.32-37-generic
CONFIG_DEVTMPFS=y
CONFIG_DEVTMPFS_MOUNT=y

Your system appears to be missing the /dev/ structures created by the kernel in devtmpfs. Check that the kernel version is 2.6.32 or later.

$ uname -a

See: http://lwn.net/Articles/345480/

Peter Teoh

2012-09-29 07:19:32 UTC

Permalink

Furthermore, if u look at the /sys/bus/usb interface:

.
./uevent
./devices
./devices/usb1
./devices/1-0:1.0
./devices/usb2
./devices/2-0:1.0
./devices/1-1
./devices/1-1:1.0
./devices/2-1
./devices/2-1:1.0
./devices/1-1.1
./devices/1-1.1:1.0
./devices/1-1.2
./devices/1-1.2:1.0
./devices/1-1.3
./devices/1-1.3:1.0
./devices/1-1.4
./devices/1-1.4:1.0
./devices/1-1.5
./devices/1-1.5:1.0
./devices/1-1.5:1.1
./devices/2-1.2
./devices/2-1.2:1.0
./devices/2-1.3
./devices/2-1.3:1.0
./devices/2-1.6
./devices/2-1.6:1.0
./drivers
./drivers/usbfs
./drivers/usbfs/module
./drivers/usbfs/uevent
./drivers/usbfs/unbind
./drivers/usbfs/bind
./drivers/usbfs/new_id
./drivers/usbfs/remove_id
./drivers/usbfs/1-1.3:1.0
./drivers/hub
./drivers/hub/module
./drivers/hub/uevent
./drivers/hub/unbind
./drivers/hub/bind
./drivers/hub/new_id
./drivers/hub/remove_id
./drivers/hub/1-0:1.0
./drivers/hub/2-0:1.0
./drivers/hub/1-1:1.0
./drivers/hub/2-1:1.0
./drivers/usb
./drivers/usb/uevent
./drivers/usb/unbind
./drivers/usb/bind
./drivers/usb/usb1
./drivers/usb/usb2
./drivers/usb/1-1
./drivers/usb/2-1
./drivers/usb/1-1.1
./drivers/usb/1-1.2
./drivers/usb/1-1.3
./drivers/usb/1-1.4
./drivers/usb/1-1.5
./drivers/usb/2-1.2
./drivers/usb/2-1.3
./drivers/usb/2-1.6
./drivers/usb-storage
./drivers/usb-storage/1-1.1:1.0
./drivers/usb-storage/module
./drivers/usb-storage/uevent
./drivers/usb-storage/unbind
./drivers/usb-storage/bind
./drivers/usb-storage/remove_id
./drivers/usb-storage/2-1.2:1.0
./drivers/usbhid
./drivers/usbhid/1-1.2:1.0
./drivers/usbhid/module
./drivers/usbhid/uevent
./drivers/usbhid/unbind
./drivers/usbhid/bind
./drivers/usbhid/new_id
./drivers/usbhid/remove_id
./drivers/uvcvideo
./drivers/uvcvideo/1-1.5:1.0
./drivers/uvcvideo/1-1.5:1.1
./drivers/uvcvideo/module
./drivers/uvcvideo/uevent
./drivers/uvcvideo/unbind
./drivers/uvcvideo/bind
./drivers/uvcvideo/new_id
./drivers/uvcvideo/remove_id
./drivers_probe
./drivers_autoprobe

this I guessed account for some of the hardware (like USB mass storage
device) still working, whereas those that depend on the /dev/bus/usb
interface is not working (eg, Android's adb)

another symptom is that when i "mkdir -p /dev/bus/usb" directory, by
inserting a new USB harddisk, the directory is immediately deleted.
and now i can access the newly inserted harddisk, and dmesg returns:

[26949.222877] sd 12:0:0:0: [sdc] Mode Sense: 38 00 00 00
[26949.225095] sd 12:0:0:0: [sdc] No Caching mode page present
[26949.225099] sd 12:0:0:0: [sdc] Assuming drive cache: write through
[26949.230715] sd 12:0:0:0: [sdc] No Caching mode page present
[26949.230719] sd 12:0:0:0: [sdc] Assuming drive cache: write through
[26949.282965] sdc: sdc1 sdc2 sdc4
[26949.288972] sd 12:0:0:0: [sdc] No Caching mode page present
[26949.288977] sd 12:0:0:0: [sdc] Assuming drive cache: write through
[26949.288980] sd 12:0:0:0: [sdc] Attached SCSI disk

seemingly noproblem - but "lsusb" returned NOTHING.

In fact I had also mirror the entire system into another different
hardware - before the /dev/bus/usb non-availability happened, and this
same system is still working fine.

So I am quite sure it is a udev thing, just trying my luck if anyone
know the answer?

--
Regards,
Peter Teoh

A***@Dell.com

2012-10-01 04:51:37 UTC

Permalink

This steps helped me when I had same problem in SUSE9.

The Reason is "/proc/bus/usb/ doesn't has any entry where actually lsusb searches to show USB BUS devices.To make that happen you have to manually .
Mount the Bus devices using below command.

mount -t usbdevfs none /proc/bus/usb/

And you are done.
Now lsusb should show all USB BUS devies.

Thanks
Ashish Bunkar

-----Original Message-----
From: kernelnewbies-***@kernelnewbies.org [mailto:kernelnewbies-***@kernelnewbies.org] On Behalf Of Peter Teoh
Sent: Saturday, September 29, 2012 7:12 AM
To: ***@kernelnewbies.org
Subject: Why "lsusb" return nothing?

I entered "lsusb" at the command line (as root) and nothing is return, not even any error message.

Doing a strace the last few lines are:

open("/dev/bus/usb", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = -1 ENOENT (No such file or directory) open("/proc/bus/usb", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

What happened?

This is Ubuntu 10.04 (it used NOT to be like that, not sure I what did
wrong last time). But running a VirtualBox INSIDE this same OS, I
was able to get result from "lsusb" (after enabling the USB devices in VirtualBox interface) and strace gives result:

open("/dev/bus/usb/001/002", O_RDWR) = 3
ioctl(3, USBDEVFS_IOCTL, 0xbff6f75c) = -1 ENOTTY (Inappropriate
ioctl for device)
close(3) = 0
open("/dev/bus/usb/001/001", O_RDWR) = 3

Why the difference?

--
Regards,
Peter Teoh

Peter Teoh

2012-10-03 23:33:48 UTC

Permalink

THank you for your help. This is the result:

mount -t usbdevfs none /proc/bus/usb
mount: mount point /proc/bus/usb does not exist

mkdir /proc/bus/usb
mkdir: cannot create directory `/proc/bus/usb': No such file or directory

And supposed I tried a directory that exist:

mount -t usbdevfs none /proc/bus
mount: unknown filesystem type 'usbdevfs'

The exact mirror (before the problem start I mirrored the system) is still
working today, and I have not find any difference between the two version
so far.

Post by A***@Dell.com
This steps helped me when I had same problem in SUSE9.
The Reason is "/proc/bus/usb/ doesn't has any entry where actually lsusb
searches to show USB BUS devices.To make that happen you have to manually .
Mount the Bus devices using below command.
mount -t usbdevfs none /proc/bus/usb/
And you are done.
Now lsusb should show all USB BUS devies.
Thanks
Ashish Bunkar
-----Original Message-----
Sent: Saturday, September 29, 2012 7:12 AM
Subject: Why "lsusb" return nothing?
I entered "lsusb" at the command line (as root) and nothing is return, not
even any error message.
open("/dev/bus/usb", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = -1
ENOENT (No such file or directory) open("/proc/bus/usb",
O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = -1 ENOENT (No such file or
directory)
What happened?
This is Ubuntu 10.04 (it used NOT to be like that, not sure I what did
wrong last time). But running a VirtualBox INSIDE this same OS, I
was able to get result from "lsusb" (after enabling the USB devices in
open("/dev/bus/usb/001/002", O_RDWR) = 3
ioctl(3, USBDEVFS_IOCTL, 0xbff6f75c) = -1 ENOTTY (Inappropriate
ioctl for device)
close(3) = 0
open("/dev/bus/usb/001/001", O_RDWR) = 3
Why the difference?
--
Regards,
Peter Teoh
_______________________________________________
Kernelnewbies mailing list
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

--
Regards,
Peter Teoh

Continue reading on narkive:

Search results for 'Why "lsusb" return nothing?' (Questions and Answers)

replies

Webcam problems with Ubuntu?

started 2011-12-19 13:27:11 UTC

add-ons

replies

Linux- wireless does not work in linux but works in windows?

started 2012-06-29 16:07:14 UTC

computer networking