Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
kernel 2.6 and usb-storage problem
View unanswered posts
View posts from last 24 hours

Goto page 1, 2, 3  Next  
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
CybeRDukE
Tux's lil' helper
Tux's lil' helper


Joined: 16 Jul 2002
Posts: 92

PostPosted: Thu Nov 20, 2003 6:46 pm    Post subject: kernel 2.6 and usb-storage problem Reply with quote

Hi,

i'm using kernel-2.6.0-test9 and it works great except one thing: i can't mount my usb stick. the stick works fine with kernel 2.4 but now when i plug it in, i get the following message (from dmesg):
Code:

hub 1-0:1.0: new USB device on port 2, assigned address 3
scsi2 : SCSI emulation for USB Mass Storage devices
  Vendor: iRiver    Model: iFP Mass Driver   Rev: 1.00
  Type:   Direct-Access                      ANSI SCSI revision: 02
SCSI device sda: 256000 512-byte hdwr sectors (131 MB)
sda: Write Protect is off
sda: Mode Sense: 45 00 00 08
sda: assuming drive cache: write through
 /dev/scsi/host2/bus0/target0/lun0:<3>Buffer I/O error on device sda, logical block 0
Buffer I/O error on device sda, logical block 0
 unable to read partition table
Attached scsi removable disk sda at scsi2, channel 0, id 0, lun 0
Attached scsi generic sg2 at scsi2, channel 0, id 0, lun 0,  type 0
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 3


so it can't read the partition table, but still creates /dev/sda. with kernel 2.4 it also creates /dev/sda1 to /dev/sda4 which are missing with the new kernel.
and when i try to mount /dev/sda, i get a 'wrong superblock' error.

i don't think it's a problem with my usb-setting in general, because my scanner works fine.

here a snippet of my autoloaded modules:
Code:
usbcore
sd_mod
usb_storage
uhci-hcd
scanner



i really hope you can at least give me a hint where to look next...


thx
Back to top
View user's profile Send private message
mc_rph
n00b
n00b


Joined: 31 May 2003
Posts: 10

PostPosted: Sun Nov 23, 2003 1:43 pm    Post subject: scsi disk support needed Reply with quote

Maybe you forgot to compile "SCSI disk support" into your kernel. I once forgot it too. Same problem....

mcrph
Back to top
View user's profile Send private message
CybeRDukE
Tux's lil' helper
Tux's lil' helper


Joined: 16 Jul 2002
Posts: 92

PostPosted: Sun Nov 23, 2003 1:57 pm    Post subject: Re: scsi disk support needed Reply with quote

mc_rph wrote:
Maybe you forgot to compile "SCSI disk support" into your kernel.


i compiled it in as module. as you see. the sd_mod module is loaded as shown above. there should not be any diference if it's a module or if it's compiled in the kernel, i guess.
Back to top
View user's profile Send private message
MaGuS
Guru
Guru


Joined: 13 Jun 2002
Posts: 303
Location: Luebeck, Germany

PostPosted: Wed Nov 26, 2003 2:11 pm    Post subject: Reply with quote

Got the same problem here.
Back to top
View user's profile Send private message
alphatronics
Tux's lil' helper
Tux's lil' helper


Joined: 16 Apr 2003
Posts: 88
Location: Boston

PostPosted: Mon Dec 01, 2003 9:36 pm    Post subject: Reply with quote

I'm also having difficulty with this issue. I'm fairly sure all the necessary USB/SCSI components are compiled in.
Back to top
View user's profile Send private message
bcore
n00b
n00b


Joined: 09 Apr 2003
Posts: 59
Location: Toronto

PostPosted: Mon Dec 01, 2003 11:04 pm    Post subject: Reply with quote

I've noticed this too... Here's my workaround (just in case it works for you)

when I first plug my compactflash reader into the USB, a node /dev/sda is created, but not the /dev/sda1 node I need. If I issue the following command:

mount -t vfat /dev/sda /mnt/cflash

It fails with an error message, but for whatever reason, the /dev/sda1 node is created, and then I can issue

mount -t vfat /dev/sda1 /mnt/cflash

Hope that helps...
_________________
MR DOWNY: BISCUIT BRAAAAAAAAAAA
YUO: LOL!!!!!
Back to top
View user's profile Send private message
wdreinhart
Guru
Guru


Joined: 11 Jun 2003
Posts: 569
Location: 4QFJ12345678

PostPosted: Mon Dec 01, 2003 11:14 pm    Post subject: Reply with quote

My USB memory stick and digital camera both work using love-sources (2.6.0-test11-love1), so this must be a version-specific bug or configuration problem, rather than a general kernel 2.6 bug.
Back to top
View user's profile Send private message
alphatronics
Tux's lil' helper
Tux's lil' helper


Joined: 16 Apr 2003
Posts: 88
Location: Boston

PostPosted: Mon Dec 01, 2003 11:48 pm    Post subject: Reply with quote

I'm not even getting an sda to show up, I'll try out these new-fangled love sources and see what happens.

Here's what I'm using for kernel options at the moment (gentoo-dev, 2.6_test11):

USB Mass storage is on, USB works fine, otherwise my mouse probably wouldn't be working right now.
SCSI disk and cdrom support are on, the cdrom works fine, so I'm fairly sure that SCSI is okay too.

Here's what comes up in dmesg:

hub 5-0:1.0: new USB device on port 2, assigned address 4
scsi2 : SCSI emulation for USB Mass Storage devices
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 4
Back to top
View user's profile Send private message
alphatronics
Tux's lil' helper
Tux's lil' helper


Joined: 16 Apr 2003
Posts: 88
Location: Boston

PostPosted: Tue Dec 02, 2003 1:27 am    Post subject: Reply with quote

Installed love-sources_test11-r1, getting the same BS.

Turned on verbose logging in the kernel, so it's giving some more useless info. Maybe someone else can make sense of this:

Connect:

Quote:
hub 5-0:1.0: new USB device on port 2, assigned address 5
usb-storage: USB Mass Storage device detected
usb-storage: act_altsetting is 0, id_index is 71
usb-storage: -- associate_dev
usb-storage: Transport: Control/Bulk/Interrupt
usb-storage: Protocol: 8070i
usb-storage: Endpoints: In: 0xd9e413a8 Out: 0xd9e41394 Int: 0xd9e41380 (Period 1)
usb-storage: *** thread sleeping.
scsi3 : 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: usb_stor_ctrl_transfer: rq=00 rqtype=21 value=0000 index=00 len=12
usb-storage: Status code 0; transferred 12/12
usb-storage: -- transfer complete
usb-storage: Call to usb_stor_ctrl_transfer() returned 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: CBI data stage result is 0x0
usb-storage: usb_stor_intr_transfer: xfer 2 bytes
usb-storage: Status code 0; transferred 2/2
usb-storage: -- transfer complete
usb-storage: Got interrupt data (0x28, 0x0)
usb-storage: CBI IRQ data showed reserved bType 40
usb-storage: -- transport indicates error, resetting
usb-storage: usb_stor_CB_reset called
usb-storage: usb_stor_control_msg: rq=00 rqtype=21 value=0000 index=00 len=12
usb-storage: Soft reset failed: -32
usb-storage: scsi cmd done, result=0x70000
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Command INQUIRY (6 bytes)
usb-storage: 12 00 00 00 24 00
usb-storage: usb_stor_ctrl_transfer: rq=00 rqtype=21 value=0000 index=00 len=12
usb-storage: Status code 0; transferred 12/12
usb-storage: -- transfer complete
usb-storage: Call to usb_stor_ctrl_transfer() returned 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: CBI data stage result is 0x0
usb-storage: usb_stor_intr_transfer: xfer 2 bytes
usb-storage: Status code 0; transferred 2/2
usb-storage: -- transfer complete
usb-storage: Got interrupt data (0x28, 0x0)
usb-storage: CBI IRQ data showed reserved bType 40
usb-storage: -- transport indicates error, resetting
usb-storage: usb_stor_CB_reset called
usb-storage: usb_stor_control_msg: rq=00 rqtype=21 value=0000 index=00 len=12
usb-storage: Soft reset failed: -32
usb-storage: scsi cmd done, result=0x70000
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Command INQUIRY (6 bytes)
usb-storage: 12 00 00 00 24 00
usb-storage: usb_stor_ctrl_transfer: rq=00 rqtype=21 value=0000 index=00 len=12
usb-storage: Status code 0; transferred 12/12
usb-storage: -- transfer complete
usb-storage: Call to usb_stor_ctrl_transfer() returned 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: CBI data stage result is 0x0
usb-storage: usb_stor_intr_transfer: xfer 2 bytes
usb-storage: Status code 0; transferred 2/2
usb-storage: -- transfer complete
usb-storage: Got interrupt data (0x28, 0x0)
usb-storage: CBI IRQ data showed reserved bType 40
usb-storage: -- transport indicates error, resetting
usb-storage: usb_stor_CB_reset called
usb-storage: usb_stor_control_msg: rq=00 rqtype=21 value=0000 index=00 len=12
usb-storage: Soft reset failed: -32
usb-storage: scsi cmd done, result=0x70000
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.
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 5


Disconnect:

Quote:
usb 5-2: USB disconnect, address 5
usb-storage: storage_disconnect() called
usb-storage: usb_stor_stop_transport called
usb-storage: -- dissociate_dev
usb-storage: -- sending exit command to thread
usb-storage: *** thread awakened.
usb-storage: -- exit command received
usb-storage: -- usb_stor_release_resources finished


Here are the relevant contents of /dev:

Quote:
$ ls -l s*0
lr-xr-xr-x 1 root root 36 Dec 1 15:20 sg0 -> scsi/host0/bus0/target0/lun0/generic
lr-xr-xr-x 1 root root 31 Dec 1 15:20 sr0 -> scsi/host0/bus0/target0/lun0/cd


I'll try activating verbose logging in the gentoo-dev kernel and see if it gives the same thing.
Back to top
View user's profile Send private message
alphatronics
Tux's lil' helper
Tux's lil' helper


Joined: 16 Apr 2003
Posts: 88
Location: Boston

PostPosted: Tue Dec 02, 2003 4:32 am    Post subject: Reply with quote

Getting the same errors with gentoo-dev-sources-2.6.0_beta11

Just in case it was something wierd with the memory stick, I switched sticks and got the same errors.

This all works fine in 2.4.x.
Back to top
View user's profile Send private message
sbporter
n00b
n00b


Joined: 01 May 2003
Posts: 7
Location: Huntsville, AL

PostPosted: Tue Dec 02, 2003 5:10 am    Post subject: Reply with quote

I'm getting the same thing; I had though it was an x86_64 problem, but it seems not...

Kernel 2.6.0-test11, athlon 64 3200+, latest gentoo besides....

Simon ;)
Back to top
View user's profile Send private message
DocGonzo
Tux's lil' helper
Tux's lil' helper


Joined: 14 Nov 2002
Posts: 133
Location: Wuerzburg/Germany

PostPosted: Tue Dec 02, 2003 4:18 pm    Post subject: Reply with quote

Quote:
/dev/scsi/host2/bus0/target0/lun0:<3>Buffer I/O error on device sda, logical block 0
Buffer I/O error on device sda, logical block 0
unable to read partition table


I got the same error with my hd when I first switched to kernel 2.6. I had to enable the "DOS or Windows partitiontable support" or what ever it is named. If you have a preformated USB-stick I bet you have a windows partition table on it.

Give it a try, maybe it helps.
Back to top
View user's profile Send private message
alphatronics
Tux's lil' helper
Tux's lil' helper


Joined: 16 Apr 2003
Posts: 88
Location: Boston

PostPosted: Tue Dec 02, 2003 4:56 pm    Post subject: Reply with quote

I have NTFS/FAT filesystems included in the kernel, if that's what you mean. (hda5 on this computer is a FAT partition)

/me looks around kernel config for partition table support

Didn't see anything about partition types, though I checked to make sure FAT as well as the VFAT and MSDOS extensions were enabled (they were).


Last edited by alphatronics on Tue Dec 02, 2003 5:11 pm; edited 1 time in total
Back to top
View user's profile Send private message
DocGonzo
Tux's lil' helper
Tux's lil' helper


Joined: 14 Nov 2002
Posts: 133
Location: Wuerzburg/Germany

PostPosted: Tue Dec 02, 2003 5:10 pm    Post subject: Reply with quote

No thats not what i mean. Look for "Partition Table Support". Its not the Filesystem what i mean. When I get on my linux box, I can tell you the right checkbox in the Kernelconfig.
Back to top
View user's profile Send private message
alphatronics
Tux's lil' helper
Tux's lil' helper


Joined: 16 Apr 2003
Posts: 88
Location: Boston

PostPosted: Tue Dec 02, 2003 5:12 pm    Post subject: Reply with quote

Okay. Thanks!
Back to top
View user's profile Send private message
sbporter
n00b
n00b


Joined: 01 May 2003
Posts: 7
Location: Huntsville, AL

PostPosted: Tue Dec 02, 2003 11:33 pm    Post subject: Reply with quote

I checked, and my kernel has the DOS/Win patitioning enabled...

I suppose this is why we have test kernels....

Simon ;)
Back to top
View user's profile Send private message
alphatronics
Tux's lil' helper
Tux's lil' helper


Joined: 16 Apr 2003
Posts: 88
Location: Boston

PostPosted: Wed Dec 03, 2003 3:31 am    Post subject: Reply with quote

Under what section is this thing located, just out of curiosity? I'm having no luck finding it.
Back to top
View user's profile Send private message
Beekster
Apprentice
Apprentice


Joined: 26 Nov 2002
Posts: 268
Location: Sydney

PostPosted: Wed Dec 03, 2003 3:48 am    Post subject: Reply with quote

File Systems -> Partition types -> Advanced partition selection -> PC BIOS (MSDOS Partition Tables) Support.

I've tried it, and it didn't help me...

I got a:
Code:
Dec  3 13:06:03 [kernel] hub 1-0:1.0: new USB device on port 2, assigned address 3
Dec  3 13:06:03 [kernel] scsi0 : SCSI emulation for USB Mass Storage devices
Dec  3 13:06:03 [usb.agent] ... no modules for USB product 54c/10/210
Dec  3 13:06:03 [kernel] SCSI device sda: 253696 512-byte hdwr sectors (130 MB)
Dec  3 13:06:03 [scsi.agent] how to add device type= at /devices/pci0000:00/0000:00:1f.2/usb1/1-2/1-2:1.0/host0/0:0:0:0 ??
Dec  3 13:06:03 [kernel] sda: Write Protect is off
Dec  3 13:06:03 [kernel] sda: assuming drive cache: write through
Dec  3 13:06:03 [kernel] SCSI device (ioctl) reports ILLEGAL REQUEST.
Dec  3 13:06:03 [kernel] SCSI device sda: 253696 512-byte hdwr sectors (130 MB)
Dec  3 13:06:03 [kernel] sda: Write Protect is off
Dec  3 13:06:03 [kernel] SCSI device sda: 253696 512-byte hdwr sectors (130 MB)
Dec  3 13:06:03 [kernel] sda: Write Protect is off
Dec  3 13:07:26 [kernel] SCSI device (ioctl) reports ILLEGAL REQUEST.
Dec  3 13:07:26 [kernel] SCSI device sda: 253696 512-byte hdwr sectors (130 MB)
Dec  3 13:07:26 [kernel] sda: Write Protect is off
Dec  3 13:07:26 [kernel] SCSI device sda: 253696 512-byte hdwr sectors (130 MB)
Dec  3 13:07:26 [kernel] sda: Write Protect is off
Dec  3 13:07:26 [kernel] Buffer I/O error on device sda, logical block 0
Dec  3 13:07:26 [kernel] ldm_validate_partition_table(): Disk read failed.
Dec  3 13:07:26 [kernel]  unable to read partition table
Dec  3 13:07:26 [kernel] FAT: unable to read boot sector
Dec  3 13:08:10 [kernel] SCSI device (ioctl) reports ILLEGAL REQUEST.
Dec  3 13:08:10 [kernel] SCSI device sda: 253696 512-byte hdwr sectors (130 MB)
Dec  3 13:08:10 [kernel] sda: Write Protect is off
Dec  3 13:08:10 [kernel] SCSI device sda: 253696 512-byte hdwr sectors (130 MB)
Dec  3 13:08:10 [kernel] sda: Write Protect is off
Dec  3 13:08:10 [kernel] Buffer I/O error on device sda, logical block 0
Dec  3 13:08:10 [kernel] ldm_validate_partition_table(): Disk read failed.
Dec  3 13:08:10 [kernel]  unable to read partition table
Dec  3 13:08:10 [kernel] SCSI device (ioctl) reports ILLEGAL REQUEST.
Dec  3 13:08:10 [kernel] SCSI device sda: 253696 512-byte hdwr sectors (130 MB)
Dec  3 13:08:10 [kernel] sda: Write Protect is off
Dec  3 13:08:10 [kernel] SCSI device sda: 253696 512-byte hdwr sectors (130 MB)
Dec  3 13:08:10 [kernel] sda: Write Protect is off
Dec  3 13:08:10 [kernel] Buffer I/O error on device sda, logical block 0
Dec  3 13:08:10 [kernel] ldm_validate_partition_table(): Disk read failed.
Dec  3 13:08:10 [kernel]  unable to read partition table
Dec  3 13:08:10 [kernel] Buffer I/O error on device sda, logical block 0
Dec  3 13:08:49 [kernel] usb 1-2: USB disconnect, address 3
Back to top
View user's profile Send private message
DocGonzo
Tux's lil' helper
Tux's lil' helper


Joined: 14 Nov 2002
Posts: 133
Location: Wuerzburg/Germany

PostPosted: Wed Dec 03, 2003 2:33 pm    Post subject: Reply with quote

Sorry I'm late. :oops:

Under File Systems -> Partitiontypes

I checked:

[x] Advanced partition selection
...
[x] PC BIOS (MSDOS) partition
[x] Windows Logical Disk Manager

Maybe the last one is the one you need.
I didn't had the time to install 2.6.0test11 yet, but with test9 all crap that i pluged onto my USB port worked flawlessly.
Back to top
View user's profile Send private message
Beekster
Apprentice
Apprentice


Joined: 26 Nov 2002
Posts: 268
Location: Sydney

PostPosted: Thu Dec 04, 2003 12:26 am    Post subject: Reply with quote

I needed a patch that I found here to get my Sony camera working with 2.6.0-test10. I have my /dev/sda1 back!
Back to top
View user's profile Send private message
alphatronics
Tux's lil' helper
Tux's lil' helper


Joined: 16 Apr 2003
Posts: 88
Location: Boston

PostPosted: Thu Dec 04, 2003 9:11 pm    Post subject: Reply with quote

After modifying the kernel, here's what I get in dmesg:

Connect:

Quote:
hub 5-0:1.0: new USB device on port 2, assigned address 4
usb-storage: USB Mass Storage device detected
usb-storage: act_altsetting is 0, id_index is 71
usb-storage: -- associate_dev
usb-storage: Transport: Control/Bulk/Interrupt
usb-storage: Protocol: 8070i
usb-storage: Endpoints: In: 0xd5948768 Out: 0xd5948754 Int: 0xd5948740 (Period 1)
usb-storage: *** thread sleeping.
scsi2 : 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: usb_stor_ctrl_transfer: rq=00 rqtype=21 value=0000 index=00 len=12
usb-storage: Status code 0; transferred 12/12
usb-storage: -- transfer complete
usb-storage: Call to usb_stor_ctrl_transfer() returned 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: CBI data stage result is 0x0
usb-storage: usb_stor_intr_transfer: xfer 2 bytes
usb-storage: Status code 0; transferred 2/2
usb-storage: -- transfer complete
usb-storage: Got interrupt data (0x28, 0x0)
usb-storage: CBI IRQ data showed reserved bType 40
usb-storage: -- transport indicates error, resetting
usb-storage: usb_stor_CB_reset called
usb-storage: usb_stor_control_msg: rq=00 rqtype=21 value=0000 index=00 len=12
usb-storage: Soft reset failed: -32
usb-storage: scsi cmd done, result=0x70000
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Command INQUIRY (6 bytes)
usb-storage: 12 00 00 00 24 00
usb-storage: usb_stor_ctrl_transfer: rq=00 rqtype=21 value=0000 index=00 len=12
usb-storage: Status code 0; transferred 12/12
usb-storage: -- transfer complete
usb-storage: Call to usb_stor_ctrl_transfer() returned 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: CBI data stage result is 0x0
usb-storage: usb_stor_intr_transfer: xfer 2 bytes
usb-storage: Status code 0; transferred 2/2
usb-storage: -- transfer complete
usb-storage: Got interrupt data (0x28, 0x0)
usb-storage: CBI IRQ data showed reserved bType 40
usb-storage: -- transport indicates error, resetting
usb-storage: usb_stor_CB_reset called
usb-storage: usb_stor_control_msg: rq=00 rqtype=21 value=0000 index=00 len=12
usb-storage: Soft reset failed: -32
usb-storage: scsi cmd done, result=0x70000
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Command INQUIRY (6 bytes)
usb-storage: 12 00 00 00 24 00
usb-storage: usb_stor_ctrl_transfer: rq=00 rqtype=21 value=0000 index=00 len=12
usb-storage: Status code 0; transferred 12/12
usb-storage: -- transfer complete
usb-storage: Call to usb_stor_ctrl_transfer() returned 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: CBI data stage result is 0x0
usb-storage: usb_stor_intr_transfer: xfer 2 bytes
usb-storage: Status code 0; transferred 2/2
usb-storage: -- transfer complete
usb-storage: Got interrupt data (0x28, 0x0)
usb-storage: CBI IRQ data showed reserved bType 40
usb-storage: -- transport indicates error, resetting
usb-storage: usb_stor_CB_reset called
usb-storage: usb_stor_control_msg: rq=00 rqtype=21 value=0000 index=00 len=12
usb-storage: Soft reset failed: -32
usb-storage: scsi cmd done, result=0x70000
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.
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 4


Disconnect:

Quote:
usb 5-2: USB disconnect, address 4
usb-storage: storage_disconnect() called
usb-storage: usb_stor_stop_transport called
usb-storage: -- dissociate_dev
usb-storage: -- sending exit command to thread
usb-storage: *** thread awakened.
usb-storage: -- exit command received
usb-storage: -- usb_stor_release_resources finished


I have no idea what any of that means, but here's a summary: "2.6 < 2.4"
Back to top
View user's profile Send private message
CybeRDukE
Tux's lil' helper
Tux's lil' helper


Joined: 16 Jul 2002
Posts: 92

PostPosted: Wed Dec 10, 2003 11:18 am    Post subject: Reply with quote

i just tried again getting my iriver to work and i realized some strange things that might help us.

i first tried adding my device to
Code:
/usr/src/linux/drivers/usb/storage/unusual_devs.h

and tried several combinations of flags, transfer type etc (a good overview can be found here: http://lumumba.luc.ac.be/~cheezy/misc/unusual_devs.html)
dmesg output changed but the stick still did not work.

next thing was a look at the partition table since /dev/sda is created, but the 4 partitions are not recognized. now the very interesting fact:
after a
Code:
fdisk -l /dev/sda
the 4 missing entries were created, but disappeared when i tried to access them. and i realized that the table on the usb-stick is really messed up. fdisk complains about different physical and logical start/end sectors.

i also had a look at the kernel source and partition detection really changed a lot from 2.4 to 2.6 (as far as i could see with a quick look at check.c)

now my conclusion is: kernel 2.4 did not care about "unclean" partition talbles but 2.6 does. it would be interesting if your partition table has the same warnings (both, if your usb-storage device does or does not work).

btw, when looking at kernel-sources i realized that the "unable to read partition table" is not caused by a missing partition table type in the kernel (as discussed above).
Back to top
View user's profile Send private message
alphatronics
Tux's lil' helper
Tux's lil' helper


Joined: 16 Apr 2003
Posts: 88
Location: Boston

PostPosted: Sat Dec 13, 2003 4:42 am    Post subject: Reply with quote

I performed the edit/patch that I found here. After recompiling the kernel, the problem was solved, though it seemed to take a few seconds for /dev/sda1 to show up, even though /dev/sda showed up immediately.

Perhaps this could be a patch for a future gentoo-dev-sources build?
Back to top
View user's profile Send private message
CybeRDukE
Tux's lil' helper
Tux's lil' helper


Joined: 16 Jul 2002
Posts: 92

PostPosted: Sat Dec 13, 2003 2:37 pm    Post subject: Reply with quote

i just tried the patch alphatronics mentioned but for me it hasn't changed anything. neither the dmesg-output nor the devices at /dev
Back to top
View user's profile Send private message
alphatronics
Tux's lil' helper
Tux's lil' helper


Joined: 16 Apr 2003
Posts: 88
Location: Boston

PostPosted: Sat Dec 13, 2003 7:54 pm    Post subject: Reply with quote

Hm, after doing it a couple times:

Correction: While sda shows up, sda1 might or might not, depending on which direction the wind is blowing. If it doesn't show up, this fixes it:

bcore wrote:
I've noticed this too... Here's my workaround (just in case it works for you)

when I first plug my compactflash reader into the USB, a node /dev/sda is created, but not the /dev/sda1 node I need. If I issue the following command:

mount -t vfat /dev/sda /mnt/cflash

It fails with an error message, but for whatever reason, the /dev/sda1 node is created, and then I can issue

mount -t vfat /dev/sda1 /mnt/cflash

Hope that helps...


Under that thread, there's also this patch, but it looks like it's specific to the SJ33 that I'm trying to use. Haven't tried it yet.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Goto page 1, 2, 3  Next
Page 1 of 3

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum