USB Pen Drive, /dev/sda1 is not a valid block device

Aeiri · 07-17-2004, 04:36 PM

I'm trying to get a PNY USB Pen Drive working on kernel 2.6.7. I had some issues with ehci_hcd, but I got that resolved by using the kernel option "pci=noacpi". When I try to mount it, it says:

Quote:

root@holly:/home/aeiri# mount -t vfat /dev/sda1 /mnt/usb
mount: /dev/sda1 is not a valid block device

This is the output of dmesg regarding the USB stuff:

Quote:

SCSI subsystem initialized
Initializing USB Mass Storage driver...
usbcore: registered new driver usb-storage
USB Mass Storage support registered.

The modules I have loaded are:

vfat
fat
usb_storage
sd_mod
sg
scsi_mod

I can't figure out what's wrong, any help would be appreciated.

EDIT: I just found a new error in dmesg:

Quote:

usb 1-3: new high speed USB device using address 2
usb 1-3: control timeout on ep0out
ehci_hcd 0000:00:02.2: Unlink after no-IRQ? Different ACPI or APIC settings may help.

I'm going to try to disable acpi altogether to see if that works.

Aeiri · 07-17-2004, 05:08 PM

Alright, disabling ACPI completely did nothing. I completely got rid of ACPI in kernel and still nothing....

This is the full error in dmesg after plugging it in, and trying to mount it:

Quote:

usb 1-3: new high speed USB device using address 2
usb 1-3: control timeout on ep0out
ehci_hcd 0000:00:02.2: Unlink after no-IRQ? Different ACPI or APIC settings may help.
usb 1-3: control timeout on ep0out
usb 1-3: device not accepting address 2, error -110
usb 1-3: new high speed USB device using address 3
usb 1-3: control timeout on ep0out
usb 1-3: control timeout on ep0out
usb 1-3: device not accepting address 3, error -11

Anyone?

Pete M · 07-17-2004, 05:28 PM

Aeiri

Try loading one or both of these modules

sbin/modprobe ehci-hcd
sbin/modprobe usb-uhci

Pete

tore64 · 08-13-2004, 10:32 AM

I had the same symtoms, and eventually solved the problem by removing the ehci_hcd module: "rmmod ehci_hcd". Afterwards the USB stick and USB drive worked fine.

It seems ehci_hcd is automatically activated although the related hardware is not present. The best thing would be if the module did not install itself with the wrong hardware, however as secondary solutions it would have been nice to disable ehci_hcd either by giving kernel boot parameters or a setting in modprobe.conf. Anyone know how to do this?

As a brute force solution I have moved ehci_hcd.ko away from /lib/modules/2.6.7-1.494.2.2/kernel/drivers/usb/host/ so that it is hidden from the kernel, however I would prefer a more elegant solution...

--
Tore