Arch Linux

Stanislav

Member

Registered: 2004-10-16

Posts: 82

kernel-2.6.9-1t1 usb storage support missing! [solved]

1. Hi folks,

here is the first problem with the new kernel-2.6.9-1t1. i just did

pacman -S kernel26

and i got the new kernel from testing. i'm glad is in testing, because i can't mount my USB hard drive. i also have 2.6.8.1-mm which works pretty fine. i load my modules usb-storage & sr_mod but the kernel can't find my USB hard drive. good that i still have another kernel version.
i forgot to mention that i am using a laptop, HP pavilion zt3010us. my USB ADSL internet works fine with 2.6.9 & my USB mouse also. so i know USB works with 2.6.9 just my external hard-drive is giving me hard time.

let me sumarize:

                                    2.6.8.1        2.6.9
USB ADSL Internet                    x               x
USB Mouse                            x               x
USB Hard Drive                       x               -

2. another problem i have is, my laptop doesn't shutdown when i run halt, it only reboots. i am sure acpi works , because i can load cpufreqd & acpid. so maybe you can help with that one too.

i'll be glad to help further, if you have any questions.

take care, Stanislav

---

[URL=http://imageshack.us][img]http://img360.imageshack.us/img360/481/imbulgarian6ph.gif[/img][/URL]

Snowman

Developer/Forum Fellow

From: Montreal, Canada

Registered: 2004-08-20

Posts: 5,212

Re: kernel-2.6.9-1t1 usb storage support missing! [solved]

Your external drive needs SCSI support.  You might need to wait until  kernel26-scsi 2.6.9  is put in testing.

Xentac

Forum Fellow

From: Victoria, BC

Registered: 2003-01-17

Posts: 1,797

Website

Re: kernel-2.6.9-1t1 usb storage support missing! [solved]

I'm pretty sure the module you're actually looking for is sd_mod, but it's been builtin to the kernel to work better with SATA drives on boot.

What is the output in dmesg when you plug in that drive?

Snowman, the difference between kernel26-scsi and kernel26 is basically -scsi has a lot of the scsi controller drivers builtin, whereas kernel26 has them as modules.  Using the SCSI protocol isn't a scsi controller's job, so you don't need the -scsi kernel.

---

I have discovered that all of mans unhappiness derives from only one source, not being able to sit quietly in a room
- Blaise Pascal

Stanislav

Member

Registered: 2004-10-16

Posts: 82

Re: kernel-2.6.9-1t1 usb storage support missing! [solved]

dmesg 2.6.9

agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode
agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode
[drm] Loading R200 Microcode
Initializing USB Mass Storage driver...
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
usb 4-1: usbfs: interface 2 claimed while 'modem_run' sets config #1
usb 4-1: bulk timeout on ep5in
usb 4-1: usbfs: USBDEVFS_BULK failed ep 0x85 len 512 ret -110
usb 4-1: usbfs: interface 0 claimed while 'modem_run' sets config #1
usb 4-1: usbfs: interface 2 claimed while 'modem_run' sets config #1
HDLC line discipline: version $Revision: 4.8 $, maxframe=4096
N_HDLC line discipline registered.
usb 4-1: usbfs: interface 0 claimed while 'pppoa3' sets config #1
usb 4-1: usbfs: interface 1 claimed while 'pppoa3' sets config #1

dmesg 2.6.8.1

agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode
agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode
[drm] Loading R200 Microcode
usb 4-1: usbfs: interface 2 claimed while 'modem_run' sets config #1
usb 4-1: bulk timeout on ep5in
usb 4-1: usbfs: USBDEVFS_BULK failed ep 0x85 len 512 ret -110
usb 4-1: usbfs: interface 0 claimed while 'modem_run' sets config #1
usb 4-1: usbfs: interface 2 claimed while 'modem_run' sets config #1
HDLC line discipline: version $Revision: 4.8 $, maxframe=4096
N_HDLC line discipline registered.
usb 4-1: usbfs: interface 0 claimed while 'pppoa3' sets config #1
usb 4-1: usbfs: interface 1 claimed while 'pppoa3' sets config #1
Initializing USB Mass Storage driver...
usb-storage: USB Mass Storage device detected
usb-storage: -- associate_dev
usb-storage: Vendor: 0x0d49, Product: 0x3005, Revision: 0x0100
usb-storage: Interface Subclass: 0x06, Protocol: 0x50
usb-storage: Vendor: Maxtor,  Product: 3000LS v01.00.00
usb-storage: Transport: Bulk
usb-storage: Protocol: Transparent SCSI
usb-storage: usb_stor_control_msg: rq=fe rqtype=a1 value=0000 index=00 len=1
usb-storage: GetMaxLUN command result is -32, data is 0
usb-storage: usb_stor_control_msg: rq=01 rqtype=02 value=0000 index=88 len=0
usb-storage: usb_stor_clear_halt: result = 0
usb-storage: usb_stor_control_msg: rq=01 rqtype=02 value=0000 index=02 len=0
usb-storage: usb_stor_clear_halt: result = 0
usb-storage: *** thread sleeping.
scsi0 : SCSI emulation for USB Mass Storage devices
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Command INQUIRY (6 bytes)
usb-storage:  12 00 00 00 24 00
usb-storage: Bulk Command S 0x43425355 T 0x1 L 36 F 128 Trg 0 LUN 0 CL 6
usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
usb-storage: Status code 0; transferred 31/31
usb-storage: -- transfer complete
usb-storage: Bulk command transfer result=0
usb-storage: usb_stor_bulk_transfer_buf: xfer 36 bytes
usb-storage: Status code 0; transferred 36/36
usb-storage: -- transfer complete
usb-storage: Bulk data transfer result 0x0
usb-storage: Attempting to get CSW...
usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
usb-storage: Status code 0; transferred 13/13
usb-storage: -- transfer complete
usb-storage: Bulk status result = 0
usb-storage: Bulk Status S 0x53425355 T 0x1 R 0 Stat 0x0
usb-storage: Fixing INQUIRY data to show SCSI rev 2 - was 0
usb-storage: scsi cmd done, result=0x0
usb-storage: *** thread sleeping.
  Vendor: Maxtor 2  Model: F040L0            Rev:  0 0
  Type:   Direct-Access                      ANSI SCSI revision: 02
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Command TEST_UNIT_READY (6 bytes)
usb-storage:  00 00 00 00 00 00
usb-storage: Bulk Command S 0x43425355 T 0x2 L 0 F 0 Trg 0 LUN 0 CL 6
usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
usb-storage: Status code 0; transferred 31/31
usb-storage: -- transfer complete
usb-storage: Bulk command transfer result=0
usb-storage: Attempting to get CSW...
usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
usb-storage: Status code 0; transferred 13/13
usb-storage: -- transfer complete
usb-storage: Bulk status result = 0
usb-storage: Bulk Status S 0x53425355 T 0x2 R 0 Stat 0x0
usb-storage: scsi cmd done, result=0x0
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Command READ_CAPACITY (10 bytes)
usb-storage:  25 00 00 00 00 00 00 00 00 00
usb-storage: Bulk Command S 0x43425355 T 0x3 L 8 F 128 Trg 0 LUN 0 CL 10
usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
usb-storage: Status code 0; transferred 31/31
usb-storage: -- transfer complete
usb-storage: Bulk command transfer result=0
usb-storage: usb_stor_bulk_transfer_buf: xfer 8 bytes
usb-storage: Status code 0; transferred 8/8
usb-storage: -- transfer complete
usb-storage: Bulk data transfer result 0x0
usb-storage: Attempting to get CSW...
usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
usb-storage: Status code 0; transferred 13/13
usb-storage: -- transfer complete
usb-storage: Bulk status result = 0
usb-storage: Bulk Status S 0x53425355 T 0x3 R 0 Stat 0x0
usb-storage: scsi cmd done, result=0x0
usb-storage: *** thread sleeping.
SCSI device sda: 80293248 512-byte hdwr sectors (41110 MB)
sda: assuming drive cache: write through
 /dev/scsi/host0/bus0/target0/lun0:<7>usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Command READ_10 (10 bytes)
usb-storage:  28 00 00 00 00 00 00 00 08 00
usb-storage: Bulk Command S 0x43425355 T 0x4 L 4096 F 128 Trg 0 LUN 0 CL 10
usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
usb-storage: Status code 0; transferred 31/31
usb-storage: -- transfer complete
usb-storage: Bulk command transfer result=0
usb-storage: usb_stor_bulk_transfer_sglist: xfer 4096 bytes, 1 entries
usb-storage: Status code 0; transferred 4096/4096
usb-storage: -- transfer complete
usb-storage: Bulk data transfer result 0x0
usb-storage: Attempting to get CSW...
usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
usb-storage: Status code 0; transferred 13/13
usb-storage: -- transfer complete
usb-storage: Bulk status result = 0
usb-storage: Bulk Status S 0x53425355 T 0x4 R 0 Stat 0x0
usb-storage: scsi cmd done, result=0x0
usb-storage: *** thread sleeping.
 p1
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0,  type 0
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Bad LUN (0:1)
usb-storage: scsi cmd done, result=0x40000
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Bad target number (1:0)
usb-storage: scsi cmd done, result=0x40000
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Bad target number (2:0)
usb-storage: scsi cmd done, result=0x40000
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Bad target number (3:0)
usb-storage: scsi cmd done, result=0x40000
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Bad target number (4:0)
usb-storage: scsi cmd done, result=0x40000
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Bad target number (5:0)
usb-storage: scsi cmd done, result=0x40000
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Bad target number (6:0)
usb-storage: scsi cmd done, result=0x40000
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Bad target number (7:0)
usb-storage: scsi cmd done, result=0x40000
usb-storage: *** thread sleeping.
USB Mass Storage device found at 3
usbcore: registered new driver usb-storage
USB Mass Storage support registered.

for both kernels i run

modprobe usb-storage
modprobe sr_mod

when i try to load sd_mod, i get "FATAL:Module sd_mod not found"

i hope that helps

---

[URL=http://imageshack.us][img]http://img360.imageshack.us/img360/481/imbulgarian6ph.gif[/img][/URL]

dp

Member

From: Zürich, Switzerland

Registered: 2003-05-27

Posts: 3,378

Website

Re: kernel-2.6.9-1t1 usb storage support missing! [solved]

see here:

http://kerneltrap.org/node/view/3992

(scroll down to the comments added and you will find a message about "usb-storage" and "ub")

---

The impossible missions are the only ones which succeed.

Stanislav

Member

Registered: 2004-10-16

Posts: 82

Re: kernel-2.6.9-1t1 usb storage support missing! [solved]

Thanks dp,

i tried

modprobe ub

but that didn't change much. still the hard drive is missing! if this was a known issue, i thought it would be fixed in 2.6.9!

---

[URL=http://imageshack.us][img]http://img360.imageshack.us/img360/481/imbulgarian6ph.gif[/img][/URL]

Snowman

Developer/Forum Fellow

From: Montreal, Canada

Registered: 2004-08-20

Posts: 5,212

Re: kernel-2.6.9-1t1 usb storage support missing! [solved]

Snowman, the difference between kernel26-scsi and kernel26 is basically -scsi has a lot of the scsi controller drivers builtin, whereas kernel26 has them as modules.  Using the SCSI protocol isn't a scsi controller's job, so you don't need the -scsi kernel.

That's good to know  .  During installation, the installation guide gave me the impression that kernel26-scsi was needed for external drives.   Anywaw, I'll probably switch to kernel26 since it's smaller.

Stanislav

Member

Registered: 2004-10-16

Posts: 82

Re: kernel-2.6.9-1t1 usb storage support missing! [solved]

Hi,

i have the solution!    finally it's working. the thing was, that with kernel 2.6.9 , my external hard drive shows up at /dev/uba1 and is no longer under /dev/sda1.  hwd though, couldn't find it.

i hope this helps someone like me! :-) i am glad everything is working fine now. i'll keep testing the new kernel.

greetings, Stanislav

---

[URL=http://imageshack.us][img]http://img360.imageshack.us/img360/481/imbulgarian6ph.gif[/img][/URL]