Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with 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.
I have a Universal Buslink Corporation external hard drive (USB), model number L30 (30GB). It works fine with windows, for which they gave drivers. However, in linux, on bootup, it gives messages like:
usb.c: assigning device number 2
usb.c device rejected device number 2 (error=-100)
It goes on like this until it reaches device number 5, then it stops giving messages and finishes booting up.
I have the usb-ohci, usb-storage, and usbcore modules installed. Are there more modules that I need? I'm running slackware 9.0, and I checked through the USB drivers they have and added as many as looked relevent to /etc/rc.d/rc.modules.
Thanks.
You probably have all the modules for USB installed, but you also need to check on scsi devices. Linux treats almost all writable USB devices as scsi, so you will need to see 'scsi_mod', 'sr_mod' and 'sd_mod' at least. Post the output of 'lsmod' and 'cat /proc/scsi/scsi'. These are commands issued at a console while you're logged in as root.
So I've got the ide-scsi module in there anyway. And here's the "cat" you wanted:
cat /proc/scsi/scsi
Attached devices: none
I'll look for more scsi modules as well. But the problem is that the same error occurs if I try a USB mouse, which makes me think it is probably a USB error.
Well, your scsi arrangement doesn't look normal to me. If you have ide-scsi to handle a CD burner, then something should show up in /proc/scsi/scsi. The output of my /proc/scsi/scsi is:
Now, Mandrake 9.1 uses devfs, so that might account for some differences, since you use Slackware. For example, if Slack doesn't have devfs, then you might not have 'sr_mod' or 'sd_mod', but I would think you would still need 'scsi_mod' regardless. My 'lsmod' says that 'scsi_mod' is used by 'ide-scsi' (as well as by 'sr_mod' and 'sd_mod'). This needs help from a Slackware person, I'm afraid.
Have you removed plug& play from the bios you are using???
I'm having sort of the same issue with my usb intellimouse... when I removed the plug&play option from it at least I got it to work once... after I rebooted it fail again but at this it did something.
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,700
Rep:
Is your computer's USB ports 2.0 or 1.0,1.1 . I never could get a 2.0 device to work on a 1.1 USB port. I might be able now. If your USB ports are 2.0 you need to load one or the other of the following modules usb-uhci or usb-ehci.
My computer has the 1.1 USB. However, the hard drive is about 6 months older than the computer, so I really doubt that its a 2.0 USB hard drive. The mouse, being a mouse, might be.
I tried the following commands:
root@Mad2Physicist:~# modprobe usb-uhci
/lib/modules/2.4.20/kernel/drivers/usb/usb-uhci.o.gz: init_module: No such device
/lib/modules/2.4.20/kernel/drivers/usb/usb-uhci.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.20/kernel/drivers/usb/usb-uhci.o.gz: insmod /lib/modules/2.4.20/kernel/drivers/usb/usb-uhci.o.gz failed
/lib/modules/2.4.20/kernel/drivers/usb/usb-uhci.o.gz: insmod usb-uhci failed
root@Mad2Physicist:~# modprobe ehci-hcd
/lib/modules/2.4.20/kernel/drivers/usb/hcd/ehci-hcd.o.gz: init_module: No such device
/lib/modules/2.4.20/kernel/drivers/usb/hcd/ehci-hcd.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.20/kernel/drivers/usb/hcd/ehci-hcd.o.gz: insmod /lib/modules/2.4.20/kernel/drivers/usb/hcd/ehci-hcd.o.gz failed
/lib/modules/2.4.20/kernel/drivers/usb/hcd/ehci-hcd.o.gz: insmod ehci-hcd failed
root@Mad2Physicist:~#
So I'm not really sure what was up with that. I'm wondering if it would work if I had a PC card USB port.
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,700
Rep:
I did the experiment and ehci-hcd does not load with 1.1 USB controllers. I have another thought.
Try this:
In a terminal screen enter the following:
' echo "scsi add-single-device 0 0 0 0" > /proc/scsi/scsi '
Then do a ' cat /proc/scsi/scsi ' See if it shows a device now. If it does, try mounting it.
btw, when I attatched the hard drive while the computer was running to test this, i tried running a dmesg and it gave the following (exactly what it was giving before, but at least it knows I plugged something in...):
hub.c: new USB device 00:02.0-2, assigned address 2
usb_control/bulk_msg: timeout
usb-ohci.c: unlink URB timeout
usb.c: USB device not accepting new address=2 (error=-110)
hub.c: new USB device 00:02.0-2, assigned address 3
usb_control/bulk_msg: timeout
usb-ohci.c: unlink URB timeout
usb.c: USB device not accepting new address=3 (error=-110)
I am wondering if the problem is with not having the right scsi drivers. I'm going to start checking those.
Thanks for your help.
root@Mad2Physicist:/lib/modules/2.4.20/kernel/drivers/scsi# mount /dev/sda /exthd
mount: you must specify the filesystem type
However, at least it thinks something is there.
Unfortunately, unplugging the drive doesn't change what the SCSI things say, and when I plugged it in again, it only brought up the same "usb not accepting address=x" that i was getting before.
Your mount command should have been something like:
mount -t vfat /dev/sda1 /exthd
'/dev/sda' refers to the whole drive, whereas '/dev/sda1' refers to the first partition on that drive. You need to specify a partition in a mount command, because it is the partition that holds the filesystem. '-t vfat' is specifying the filesystem type, so you don't get that 'mount: you must specify the filesystem type' error.
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,700
Rep:
It seems to see the device on scsi 1 and not scsi 0. You can try this command ' ' echo "scsi add-single-device 1 0 0 0" > /proc/scsi/scsi '. and see what happens. Then mount like the above post mentions
' mount -t vfat /dev/sda1 /exthd ' . Just make sure you have created a subdirectory /exthd ' mkdir exthd '.
Also what is the format on the drive vfat or ntfs? You need to have ntfs configured in the kernel for it work.
Another option is boot with a knoppix disc and see if you can mount your USB drive.
mad, i have a similar problem with a Buslink L20 (20 gig version of what you have) on slack 9.0. did you manage to fix these issues? if so, what did you do?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.