Weird message when connecting USB mass storage device
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Weird message when connecting USB mass storage device
When i plug a USB box with an IDE hd inside to my laptop I get this weird message on my console:
root@*****:~# cat: /sys//devices//pci0000:00/0000:00:11.2/usb1/1-1/bNumConfigurations:No such file or directory
/etc/hotplug/usb.agent: line 144: [: too many arguments
then i press Contol^C to get back in console.I have no problem mounting the drive.I searched a bit when i compiled 2.6.4 for usb+pci hotplug but i did not add those options.I do not use hotpluging.
I read that a lot of people have that problem.I updated to hotplug-2004_03_29.tar.bz2 but the problem persisted.
But "# chmod -x /etc/hotplug/scsi.agent" solved the problem.I believe that at 2.6.5 stable they will have fixed it.
sysfs is built in to the 2.6 series kernel.
What is missing is the directory /sys which will not exist unless you create it yourself.
(at least until distro's based on the new kernel series are released).
You also need an entry in /etc/fstab.
1. Give sysfs a mount point
mkdir /sys
2. Put an entry in /etc/fstab
sysfs /sys sysfs defaults 0 0
The reason that everything still works despite the error messages, is that sysfs works to a large extent in parallel with proc at the moment, while the new kernel evolves.
Documentation about this is scarce, but you may wish to read /Documentation/filesystems/sysfs.txt in your kernel sources, but it really doesn't help much.
Still you can get rid of the error messages by following the points 1 & 2 above.
Originally posted by tobyl sysfs is built in to the 2.6 series kernel.
What is missing is the directory /sys which will not exist unless you create it yourself.
(at least until distro's based on the new kernel series are released).
You also need an entry in /etc/fstab.
1. Give sysfs a mount point
mkdir /sys
2. Put an entry in /etc/fstab
sysfs /sys sysfs defaults 0 0
The reason that everything still works despite the error messages, is that sysfs works to a large extent in parallel with proc at the moment, while the new kernel evolves.
Documentation about this is scarce, but you may wish to read /Documentation/filesystems/sysfs.txt in your kernel sources, but it really doesn't help much.
Still you can get rid of the error messages by following the points 1 & 2 above.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.