Re: Fw: Re: Elitegroup K7S5A + usb_storage problem

2005-08-07 Thread Martin Maurer
On Sunday, 7. August 2005 20:08, Alan Stern wrote:
> On Sun, 7 Aug 2005 [EMAIL PROTECTED] wrote:
> > Hi Alan,
> >
> > no. the stick doesn't have a write protection switch.
> > Once when i tried to copy a file to the mp3 player i got a new file there
> > on remount, but it consisted of incorrect data. (so writing seemed to be
> > possible and just went wrong) (in that case the fat seemed to be damaged
> > after i had tried this, so that windows wasn't able to read it correctly
> > any more.
> > (formatting from the mp3 players menu helped)
>
> Well, perhaps the device isn't consistently writing data to the
> correct locations.
>
> > greetings
> > Martin
> >
> > PS: just as an info - i sent a usbmon trace to Pete Zaitcev today, should
> > I send it to you too?
>
> Pete is quite as competent at solving this kind of problem as I am.  And
> he knows the ub driver much better, so I'm happy to bow out and let him
> worry about it!  :-)
>
> Just out of curiosity, if you plug the player into a Windows system
> without installing any special drivers first, will Windows be able to read
> and write files okay?  If it can, a USB packet trace may give Pete a clue
> as to where to look.
as far as i recall i didnt install any special drivers for my win 2k and win 
xp systems. (i got this mp3 player quite a while now...)
How would I do such an packet trace ?


>
> Alan Stern
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [EMAIL PROTECTED]
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


pgpEicsCRSKbU.pgp
Description: PGP signature


Re: Fw: Re: Elitegroup K7S5A + usb_storage problem

2005-08-07 Thread martin . maurer

Hi Alan,

no. the stick doesn't have a write protection switch.
Once when i tried to copy a file to the mp3 player i got a new file there on 
remount,
but it consisted of incorrect data. (so writing seemed to be possible and just 
went wrong)
(in that case the fat seemed to be damaged after i had tried this, so that 
windows wasn't 
able to read it correctly any more.
(formatting from the mp3 players menu helped)

greetings
Martin

PS: just as an info - i sent a usbmon trace to Pete Zaitcev today, should I 
send it to you too? 

Alan Stern <[EMAIL PROTECTED]> schrieb am 07.08.05 17:14:52:
On Sun, 7 Aug 2005, Martin Maurer wrote:

> Hi Pete,
> 
> when using ub with your patch i get a lot further:
> the device is detected and uba+uba1 entries appear.
> I can mount the device correctly.
> Copying the files down and comparing them with the originals gives correct 
> results.
> 
> but:
> when i delete the files which are on the stick and do an umount/mount cycle, 
> the files are there again. 
> Copying files to the stick gives wrong results too.
> Once the created file vanished after the remount,
> and once it was there with a different name/size/date and garbage as content.

It sounds as though the device isn't actually carrying out the write 
operations.  Is it write-protected?

Alan Stern



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: Fw: Re: Elitegroup K7S5A + usb_storage problem

2005-08-06 Thread Martin Maurer
Hi Pete,

when using ub with your patch i get a lot further:
the device is detected and uba+uba1 entries appear.
I can mount the device correctly.
Copying the files down and comparing them with the originals gives correct 
results.

but:
when i delete the files which are on the stick and do an umount/mount cycle, 
the files are there again. 
Copying files to the stick gives wrong results too.
Once the created file vanished after the remount,
and once it was there with a different name/size/date and garbage as content.

I didnt try ub without your patch (CONFIG_BLK_DEV_UB was disabled in my kernel 
configuration). Shall I try this too?

greetings
Martin


On Saturday, 6. August 2005 22:02, Pete Zaitcev wrote:
> On Sat, 6 Aug 2005 11:49:05 -0400 (EDT), Alan Stern 
<[EMAIL PROTECTED]> wrote:
> > When asked what went wrong, the device says it didn't understand the
> > INQUIRY command.  This is a fatal error; if a device can't identify
> > itself there's no way for Linux to use it.
> >
> > In short, your mp3stick is worthless.  Trade it in for one that works.
>
> This is only true if usb-storage is used. The stick may work with ub.
>
> Martin, please apply the attached patch and enable CONFIG_BLK_DEV_UB.
> If you do not run a userland with udev, do this:
>
> mknod /dev/uba b 180 0
> mknod /dev/uba1 b 180 1
>
> Let me know how it went.
>
> -- Pete
>
> diff -urp -X dontdiff linux-2.6.12/drivers/usb/storage/usb.c
> linux-2.6.12-lem/drivers/usb/storage/usb.c ---
> linux-2.6.12/drivers/usb/storage/usb.c2005-06-17 12:48:29.0 
> -0700
> +++ linux-2.6.12-lem/drivers/usb/storage/usb.c2005-07-25
> 22:12:53.0 -0700 @@ -150,7 +150,9 @@ static struct usb_device_id
> storage_usb_
>   { USB_INTERFACE_INFO(USB_CLASS_MASS_STORAGE, US_SC_QIC, US_PR_BULK) },
>   { USB_INTERFACE_INFO(USB_CLASS_MASS_STORAGE, US_SC_UFI, US_PR_BULK) },
>   { USB_INTERFACE_INFO(USB_CLASS_MASS_STORAGE, US_SC_8070, US_PR_BULK) },
> +#if !defined(CONFIG_BLK_DEV_UB) && !defined(CONFIG_BLK_DEV_UB_MODULE)
>   { USB_INTERFACE_INFO(USB_CLASS_MASS_STORAGE, US_SC_SCSI, US_PR_BULK) },
> +#endif
>
>   /* Terminating entry */
>   { }
> @@ -224,8 +226,10 @@ static struct us_unusual_dev us_unusual_
> .useTransport = US_PR_BULK},
>   { .useProtocol = US_SC_8070,
> .useTransport = US_PR_BULK},
> +#if !defined(CONFIG_BLK_DEV_UB) && !defined(CONFIG_BLK_DEV_UB_MODULE)
>   { .useProtocol = US_SC_SCSI,
> .useTransport = US_PR_BULK},
> +#endif
>
>   /* Terminating entry */
>   { NULL }
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [EMAIL PROTECTED]
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
hub 1-1:1.0: state 5 ports 4 chg  evt 0010
hub 1-1:1.0: port 4, status 0101, change 0001, 12 Mb/s
hub 1-1:1.0: debounce: port 4: total 100ms stable 100ms status 0x101
usb 1-1.4: new full speed USB device using ohci_hcd and address 7
usb 1-1.4: ep0 maxpacket = 32
usb 1-1.4: new device strings: Mfr=0, Product=0, SerialNumber=0
usb 1-1.4: hotplug
usb 1-1.4: adding 1-1.4:1.0 (config #1, interface 0)
usb 1-1.4:1.0: hotplug
ub 1-1.4:1.0: usb_probe_interface
ub 1-1.4:1.0: usb_probe_interface - got id
ub(1.7): GetMaxLUN returned 0 bytes
ub(1.7): GetMaxLUN returned 0 bytes
ub(1.7): GetMaxLUN returned 0 bytes
 uba: uba1
hub 1-1:1.0: state 5 ports 4 chg  evt 0010


pgpgacNr6NzKX.pgp
Description: PGP signature


Re: Elitegroup K7S5A + usb_storage problem

2005-08-05 Thread Martin Maurer
An update on this issue:

I realized a problem with my kernel configuration - i was missing sd_mod. This 
fixed the problem with the harddrive, but the usb stick still doesn't work.
attached a new dmesg output of the mp3stick problem (only very little changes)

greetings
Martin Maurer

On Friday, 5. August 2005 17:51, Martin Maurer wrote:
> Hi everybody,
>
> For quite some time now I have got a problem mounting my usb-stick (MP3
> FUN256 from DNT) with linux. This stick worked back in the 2.4.x days,
> though it needed one of the later versions (I switched to 2.6.x as soon
> about when it was released, so I didnt test the newest versions.)
>
> Recently I bought an usb harddisk encasing and tried this one, but it
> doesnt work either. Taking a look at dmesg I think the devices are not
> correctly found by the kernel. (I attached the two dmesg outputs).
>
> As I dont know which part of the kernel causes this problem I did not so
> far report a bug using bugzilla. (And as it may be my fault too).
>
> I currently use 2.6.13-rc5 + software-suspoend 2 patch 2.1.9.12
> (I tried 2.6.12-rc5, and some earlier versions too)
>
> Processor: AMD Athlon XP 1700+
> Distribution: Debian unstable (though not updated for about a month).
>
> Anyone knows help for this issues ?
> (patches to try and verify happily accepted)
>
> greetings
> Martin Maurer
hub 1-1:1.0: state 5 ports 4 chg  evt 0010
hub 1-1:1.0: port 4, status 0101, change 0001, 12 Mb/s
hub 1-1:1.0: debounce: port 4: total 100ms stable 100ms status 0x101
usb 1-1.4: new full speed USB device using ohci_hcd and address 18
usb 1-1.4: ep0 maxpacket = 32
usb 1-1.4: new device strings: Mfr=0, Product=0, SerialNumber=0
usb 1-1.4: hotplug
usb 1-1.4: adding 1-1.4:1.0 (config #1, interface 0)
usb 1-1.4:1.0: hotplug
usb-storage 1-1.4:1.0: usb_probe_interface
usb-storage 1-1.4:1.0: usb_probe_interface - got id
usb-storage: USB Mass Storage device detected
usb-storage: -- associate_dev
usb-storage: Vendor: 0x0f19, Product: 0x0103, Revision: 0x0100
usb-storage: Interface Subclass: 0x06, Protocol: 0x50
usb-storage: Transport: Bulk
usb-storage: Protocol: Transparent SCSI
usb-storage: usb_stor_control_msg: rq=fe rqtype=a1 value= index=00 len=1
usb-storage: GetMaxLUN command result is -32, data is 85
usb-storage: usb_stor_control_msg: rq=01 rqtype=02 value= index=82 len=0
usb-storage: usb_stor_clear_halt: result = 0
usb-storage: usb_stor_control_msg: rq=01 rqtype=02 value= index=01 len=0
usb-storage: usb_stor_clear_halt: result = 0
scsi10 : SCSI emulation for USB Mass Storage devices
usb-storage: *** thread sleeping.
hub 1-1:1.0: state 5 ports 4 chg  evt 0010
usb-storage: device found at 18
usb-storage: waiting for device to settle before scanning
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 13/36
usb-storage: -- short transfer
usb-storage: Bulk data transfer result 0x1
usb-storage: Attempting to get CSW...
usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
ohci_hcd :00:02.2: urb cf61ca60 path 1.4 ep2in 8216 cc 8 --> status -75
usb-storage: Status code -75; transferred 13/13
usb-storage: -- babble
usb-storage: Bulk status result = 3
usb-storage: -- transport indicates error, resetting
hub 1-1:1.0: state 5 ports 4 chg  evt 0010
usb 1-1.4: reset full speed USB device using ohci_hcd and address 18
hub 1-1:1.0: state 5 ports 4 chg  evt 0010
usb 1-1.4: ep0 maxpacket = 32
usb-storage: usb_reset_device returns 0
usb-storage: scsi cmd done, result=0x7
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: Bulk Command S 0x43425355 T 0x2 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 0x2 R 0 Stat 0x1
usb-storage: -- transport indicates command failure
usb-storage: Issuing auto-REQUEST_SENSE
usb-storage: Bulk Command S 0x434253

Elitegroup K7S5A + usb_storage problem

2005-08-05 Thread Martin Maurer
Hi everybody,

For quite some time now I have got a problem mounting my usb-stick (MP3 FUN256 
from DNT) with linux. This stick worked back in the 2.4.x days, though it 
needed one of the later versions (I switched to 2.6.x as soon about when it 
was released, so I didnt test the newest versions.)

Recently I bought an usb harddisk encasing and tried this one, but it doesnt 
work either. Taking a look at dmesg I think the devices are not correctly 
found by the kernel. (I attached the two dmesg outputs).

As I dont know which part of the kernel causes this problem I did not so far 
report a bug using bugzilla. (And as it may be my fault too).

I currently use 2.6.13-rc5 + software-suspoend 2 patch 2.1.9.12
(I tried 2.6.12-rc5, and some earlier versions too)

Processor: AMD Athlon XP 1700+
Distribution: Debian unstable (though not updated for about a month).

Anyone knows help for this issues ?
(patches to try and verify happily accepted)

greetings
Martin Maurer
Module  Size  Used by
usb_storage   115792  0 
scsi_mod  145832  1 usb_storage
bnep   16640  2 
rfcomm 41564  0 
l2cap  27972  9 bnep,rfcomm
lp 11652  0 
ipv6  267264  19 
ip_queue   11744  0 
ipt_ULOG8388  5 
ipt_state   1920  8 
ipt_MASQUERADE  3648  1 
iptable_nat24212  2 ipt_MASQUERADE
ip_conntrack   45240  3 ipt_state,ipt_MASQUERADE,iptable_nat
iptable_filter  3008  1 
ip_tables  23104  5 
ipt_ULOG,ipt_state,ipt_MASQUERADE,iptable_nat,iptable_filter
af_packet  22920  2 
ide_cd 43396  0 
cdrom  41184  1 ide_cd
parport_pc 36548  1 
parport38344  2 lp,parport_pc
floppy 59476  0 
pcspkr  3864  0 
rtc14072  0 
snd_bt87x  15304  0 
tuner  38056  0 
tvaudio22812  0 
bttv  162448  0 
video_buf  22212  1 bttv
i2c_algo_bit9864  1 bttv
v4l2_common 5824  1 bttv
btcx_risc   4936  1 bttv
tveeprom   11920  1 bttv
videodev9984  1 bttv
8139cp 21440  0 
usbhid 35040  0 
hci_usb16008  0 
bluetooth  52804  6 bnep,rfcomm,l2cap,hci_usb
snd_intel8x0   34112  0 
ohci_hcd   36740  0 
i2c_sis96x  5508  0 
i2c_sis630  7820  0 
i2c_core   4  7 
tuner,tvaudio,bttv,i2c_algo_bit,tveeprom,i2c_sis96x,i2c_sis630
sis_agp 8708  1 
agpgart36296  1 sis_agp
nls_iso8859_1   4032  2 
nls_cp437   5696  2 
vfat   14080  2 
fat53212  1 vfat
8139too28480  0 
mii 5568  2 8139cp,8139too
ne2k_pci   10912  0 
8390   10240  1 ne2k_pci
crc32   4224  4 bnep,8139cp,8139too,8390
snd_via82xx28320  0 
snd_mpu401_uart 8192  1 snd_via82xx
snd_usb_audio  78016  0 
snd_usb_lib15872  1 snd_usb_audio
snd_emu10k1_synth   8192  0 
snd_emux_synth 38976  1 snd_emu10k1_synth
snd_seq_virmidi 8064  1 snd_emux_synth
snd_seq_midi_emul   7488  1 snd_emux_synth
snd_emu10k1   124644  1 snd_emu10k1_synth
snd_ac97_codec 85308  3 snd_intel8x0,snd_via82xx,snd_emu10k1
snd_pcm_oss53216  0 
snd_mixer_oss  19776  1 snd_pcm_oss
snd_pcm94280  7 
snd_bt87x,snd_intel8x0,snd_via82xx,snd_usb_audio,snd_emu10k1,snd_ac97_codec,snd_pcm_oss
snd_page_alloc 10760  5 
snd_bt87x,snd_intel8x0,snd_via82xx,snd_emu10k1,snd_pcm
snd_seq_dummy   3716  0 
tsdev   7488  0 
snd_seq_oss35776  0 
evdev   9280  0 
snd_seq_midi9056  0 
snd_rawmidi26656  5 
snd_mpu401_uart,snd_usb_lib,snd_seq_virmidi,snd_emu10k1,snd_seq_midi
snd_seq_midi_event  7552  3 snd_seq_virmidi,snd_seq_oss,snd_seq_midi
snd_seq55504  9 
snd_emux_synth,snd_seq_virmidi,snd_seq_midi_emul,snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
snd_timer  26308  3 snd_emu10k1,snd_pcm,snd_seq
snd_seq_device  8780  8 
snd_emu10k1_synth,snd_emux_synth,snd_emu10k1,snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
snd_hwdep   9760  3 snd_usb_audio,snd_emux_synth,snd_emu10k1
snd56484  18 
snd_bt87x,snd_intel8x0,snd_via82xx,snd_mpu401_uart,snd_usb_audio,snd_emux_synth,snd_seq_virmidi,snd_emu10k1,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device,snd_hwdep
soundcore  10400  1 snd
snd_util_mem4544  2 snd_emux_synth,snd_emu10k1
psmouse35396  0 
mousedev   11936  2