LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Weird message when connecting USB mass storage device (https://www.linuxquestions.org/questions/slackware-14/weird-message-when-connecting-usb-mass-storage-device-164940/)

destin 04-01-2004 08:25 AM

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.

Is that a bug or any hotplug stupidity ??

Using 2.6.4 kernel+slack9.1

mrpdaemon 04-01-2004 08:33 AM

getting the same messages in boot since I compiled 2.6.4 too. It happens during bringing up USB mouse & keyboard.

My guess is, from that pathname, that the USB driver assumes sysfs is there, but I don't think I have that compiled.

destin 04-01-2004 09:24 AM

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.

tobyl 04-01-2004 10:06 AM

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.

tobyl

destin 04-01-2004 05:11 PM

Quote:

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.

tobyl

that works too :)

mrpdaemon 04-04-2004 08:34 AM

2.6.5 removes the error messages when a sysfs mountpoint does not exist.


All times are GMT -5. The time now is 08:36 AM.