Usbat2 February 2005

usbat2@lists.lysator.liu.se

3 participants
3 discussions

Re: USBAT 0.5.4 for Linux 2.6
by jdpinnj＠optonline.net 19 Apr '05

19 Apr '05

Hi Daniel - The device is the ZIO that came with a Canon G2. No other CF readers to toy with. My observations using the dd to the device: The problem is on the writing: On an old 2.4.25 kernel, I can write a 1M file to the card that will be identical to one read off of the device directly. This is consistent with the behavior that I have with a filesystem on the card. On the 2.6.10 kernel, I can consistently write and read up to 64k. Anything over that amount gave inconsistent results. Looking over the driver code shows that it is a magic number on the write size to the device. I made a minor mod to line 1008 of shuttle_usbat.c, and changed alloclen to 32k (65536u to 32768u). After a recompile and reload of the modules, I could not successfully write and re-read file greater than 32k. (the logs did show the write size at 32768). Any files that exceed a single write seems to cause the problem. I went back over the maillists and tried some of the various drivers. I was able to get 2.6-04.25 to work against a 2.6.8 kernel. I was not able to get 2.6-04.27 to work. I can send logs, but they didn't show anything unusual. Let me know if there is anything else to try. Jim ----- Original Message ----- From: Daniel Drake <dsd(a)gentoo.org> Date: Saturday, February 5, 2005 8:39 am Subject: Re: USBAT 0.5.4 for Linux 2.6 > Hi Jim, > > Hm, this is odd. There are no errors in your log anywhere- it seems > to have > transferred everything perfectly - but the uservisible results > don't tie in > with this. > > Which device is it? Which kernel are you running? > Have you got any other CF readers you can test on the same > configuration? > We can also test it without getting filesystems involved. Be warned > that this > will destroy any data (including the partition table) on your card. > > Use this command to create a 1mb file: > # dd if=/dev/urandom of=fileA bs=1M count=1 > > Record its md5sum: > # md5sum fileA > > Now copy it *directly* onto the device. Make sure it isn't mounted, > just do > the exact command below, where sda is the root device node: (notice > that i use > sda, not sda1...) > # cat fileA > /dev/sda > > Now copy that back over into another file: > # dd if=/dev/sda of=fileB bs=1M count=1 > > And check its md5sum: > # md5sum fileB > > Both md5sums should match. Do they? You might wish to experiment > with > different file sizes. > > Thanks, > Daniel > _______________________________________________ > Usbat2 mailing list > Usbat2(a)lists.lysator.liu.se > http://lists.lysator.liu.se/mailman/listinfo/usbat2 >

2 1

Any news?
by Jon Lapham 24 Feb '05

24 Feb '05

Daniel- Any news on getting your USBAT driver into the mainline kernel? PS: did the patch you sent for submission to the kernel include the following adjustment? /usr/src/linux/drivers/usb/storage/shuttle_usbat.c and edit line 943 - if (!(status & 0x08)) { + if (!(status & 0x40)) { -Jon -- -**-*-*---*-*---*-*---*-----*-*-----*---*-*---*-----*-----*-*-----*--- Jon Lapham <lapham(a)jandr.org> Rio de Janeiro, Brasil Personal: http://www.jandr.org/ ***-*--*----*-------*------------*--------------------*---------------

2 2

Re: USBAT 0.5.4 for Linux 2.6
by jdpinnj＠optonline.net 05 Feb '05

05 Feb '05

Hi Daniel - I am a late comer to the 2.6 kernel. This is my first go at trying to get the device to work here. I did get the device working with the 2.4.25 kernel using the old usbat-02.20031116.tar.gz file. Logging should now be complete. I have made the edit to shuttle_usbat.c and recompiled/reinstalled the modules. The activity is: 01:10:35 plug in 01:11:06 mount /cf (as type vfat) 1:12:01 mkdir /cf/test 01:12:31 ls -lat /cf - this is the proper output. total 21 drwxr--r-- 2 root root 2048 Jan 28 01:12 test drwxr--r-- 4 root root 16384 Jan 28 01:12 . drwxr--r-- 3 root root 2048 Jan 28 01:03 dcim drwxr-xr-x 20 root root 512 Jan 26 20:35 .. 01:13:29 umount /cf 01:13:49 mount /cf 01:14 ls -lat /cf total 33 drwxr-xr-x 20 root root 512 Jan 26 20:35 .. drwxr-xr-x 20 root root 512 Jan 26 20:35 .. drwxr--r-- 4 root root 16384 Dec 31 1969 . drwxr--r-- 4 root root 16384 Dec 31 1969 . 01:14:53 umount /cf 01:15:08 touch /dev/sda1 01:15:24 mount /cf 01:15:52 cp /tmp/x /cf (md5 sum shows files are the same) 01:16 ls -lat /cf total 1929 -rwxr--r-- 1 root root 1940818 Jan 28 01:15 x drwxr--r-- 4 root root 16384 Jan 28 01:15 . drwxr--r-- 4 root root 16384 Jan 28 01:15 . drwxr-xr-x 20 root root 512 Jan 26 20:35 .. drwxr-xr-x 20 root root 512 Jan 26 20:35 .. 01:16:46 umount /cf 01:17:03 mount /cf 01:17 ls -lat /cf total 33 drwxr-xr-x 20 root root 512 Jan 26 20:35 .. drwxr-xr-x 20 root root 512 Jan 26 20:35 .. drwxr--r-- 4 root root 16384 Dec 31 1969 . drwxr--r-- 4 root root 16384 Dec 31 1969 . 01:29:04 umount /cf 01:29:40 mkfs -t ext2 /dev/sda1 01:30:23 mount /dev/sda1 (mistake - tries to mount a vfat filesystem amd fails) 01:30:47 mount /dev/sda1 /cf 01:31:18 ls -lat /cf - fails ls: reading directory /cf: Input/output error total 0 I have made ext2 and ext3 filesystems on /dev/sda1, but these will not mount. This is repeatable on two CF cards that work against my old 2.4.25 kernel. Thanks. Jim ----- Original Message ----- From: Daniel Drake <dsd(a)gentoo.org> Date: Thursday, January 27, 2005 6:24 am Subject: Re: USBAT 0.5.4 for Linux 2.6 > Hi, > > jdpinnj(a)optonline.net wrote: > > Sorry to throw a wrench into the works. Copying files from the > device works like a charm. However, writing to the device has > problems. Attached are logs. > > Have you tried any other media, or different filesystems? > > Could you please make the change to the source code that I asked > Jon to do > (line 943, 0x08 --> 0x40) > > Your logs aren't complete either :( > dmesg is complete but has no timestamps. > "everything" doesn't contain kernel debug messages, "kernel" only > contains > some of them, plus starts halfway through your session at 21:26... > Please make sure both usb storage verbose debug and usb debug are > enabled, and > configure your logger to log all messages. > > Which is the last version that worked for you? > > Daniel >

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

Usbat2 February 2005