My GF has a situation in which she cannot mount a camera memory
stick. Here's the setup...

CPU<--->HUB<--->Dazzle[<--Stick

The HUB is from Radio Shack. The Dazzle is a device used to
interface the memory stick with USB. The memory stick is
a Sandisk 128 MB memory stick for a camera. Using her laptop
and XP, with the same Dazzle and memory stick, it mounts
just fine. With her desktop and Debian, it fails to mount.

Also connected to the hub are a WD USB hard disc, and an HP printer,
both of which work fine with Debian.

Currently, she mounts using XP on the laptop, then e-mails the photos
to herself over a dial-up, and then reads the mail back into Debian
using an ADSL connection. Needless to say, this is not the desirable
solution.

When we try to mount that memory card, mount responds that it is
unable to ascertain the file system type. It appears that fdisk
is unable to read anything from it at all. OTOH, lsusb shows the
Dazzle device. I have outputs from lsusb, fdisk, and dmesg, but they
are somewhat lengthy.

Any who are willing to understand what to do to get this
card to mount, I'll ship them by e-mail, or if consensus agrees
to it, I'll post them here. They are a few kilobytes altogether.

Thanks all for your time.

Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){pri ntf(p,34,p,34);}
Oppose globalization and One World Governments like the UN.
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Mon, Jul 30, 2007 at 03:37:58PM -0500, Mike McCarty wrote:
> My GF has a situation in which she cannot mount a camera memory
> stick. Here's the setup...
>
> CPU<--->HUB<--->Dazzle[<--Stick
>
> The HUB is from Radio Shack. The Dazzle is a device used to
> interface the memory stick with USB. The memory stick is
> a Sandisk 128 MB memory stick for a camera. Using her laptop
> and XP, with the same Dazzle and memory stick, it mounts
> just fine. With her desktop and Debian, it fails to mount.
>
> Also connected to the hub are a WD USB hard disc, and an HP printer,
> both of which work fine with Debian.
>
> Currently, she mounts using XP on the laptop, then e-mails the photos
> to herself over a dial-up, and then reads the mail back into Debian
> using an ADSL connection. Needless to say, this is not the desirable
> solution.
>
> When we try to mount that memory card, mount responds that it is
> unable to ascertain the file system type. It appears that fdisk
> is unable to read anything from it at all. OTOH, lsusb shows the
> Dazzle device. I have outputs from lsusb, fdisk, and dmesg, but they
> are somewhat lengthy.
>
> Any who are willing to understand what to do to get this
> card to mount, I'll ship them by e-mail, or if consensus agrees
> to it, I'll post them here. They are a few kilobytes altogether.

send them to me directly if you want, but first:

what is the output of

tail -f /var/log/syslog

when started before plugging the device in until after its plugged and
settled.

If this a regular flash memory stick/card? For example, my camera uses
bog-standard compact flash cards (about 1.25 inches square by 1/8 in
thick) and they plug into a standard card reader and mount as
/dev/sda1 as a vfat device. Is that what we're trying to do? or is it
some proprietary format device that doesn't plug into a standard
cardreader?

A

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGrk6AaIeIEqwil4YRAk11AKCGg0CQwlAD14FsMXRjtT X8m9/g6ACgqImw
iP7b8sqGt4fNRfUNc+Z9d8M=
=zPhL
-----END PGP SIGNATURE-----

Mike McCarty wrote:
> My GF has a situation in which she cannot mount a camera memory
> stick. Here's the setup...
>
> CPU<--->HUB<--->Dazzle[<--Stick
>
> The HUB is from Radio Shack. The Dazzle is a device used to
> interface the memory stick with USB. The memory stick is
> a Sandisk 128 MB memory stick for a camera. Using her laptop
> and XP, with the same Dazzle and memory stick, it mounts
> just fine. With her desktop and Debian, it fails to mount.

[snip]

I forgot to mention that she has a pendrive which mounts just
fine using the same exact port on the hub into which we plug
the Dazzle.

Here's the line in /etc/fstab

/dev/sdc1 /media/pendrive auto rw,user,noauto 0 0

Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){pri ntf(p,34,p,34);}
Oppose globalization and One World Governments like the UN.
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Mon, Jul 30, 2007 at 03:37:58PM -0500, Mike McCarty wrote:
> My GF has a situation in which she cannot mount a camera memory
> stick. Here's the setup...
>
> CPU<--->HUB<--->Dazzle[<--Stick
>
> The HUB is from Radio Shack. The Dazzle is a device used to
> interface the memory stick with USB. The memory stick is
> a Sandisk 128 MB memory stick for a camera. Using her laptop
> and XP, with the same Dazzle and memory stick, it mounts
> just fine. With her desktop and Debian, it fails to mount.

Since it does work on Windows it is probably not a hardware issue, but
did you try to connect the Dazzle directly to the USB port? Also I've
heard (on this list) about some strange formating issues, where
reformating the USB memory thingy solved the problem ...

Regards,
Andrei
--
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGrmL5qJyztHCFm9kRAowPAJ9kI8TzrbfPMJhM//NP0vdEPpIQpACgh3O/
3ZJ/jgC16FzxJrwkSxXK3Qg=
=C0MK
-----END PGP SIGNATURE-----

On Mon, Jul 30, 2007 at 03:37:58PM -0500, Mike McCarty wrote:
> My GF has a situation in which she cannot mount a camera memory
> stick. Here's the setup...
>
> CPU<--->HUB<--->Dazzle[<--Stick
>
> The HUB is from Radio Shack. The Dazzle is a device used to
> interface the memory stick with USB. The memory stick is
> a Sandisk 128 MB memory stick for a camera. Using her laptop
> and XP, with the same Dazzle and memory stick, it mounts
> just fine. With her desktop and Debian, it fails to mount.

Since it does work on Windows it is probably not a hardware issue, but
did you try to connect the Dazzle directly to the USB port? Also I've
heard (on this list) about some strange formating issues, where
reformating the USB memory thingy solved the problem ...

Regards,
Andrei
--
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGrmL5qJyztHCFm9kRAowPAJ9kI8TzrbfPMJhM//NP0vdEPpIQpACgh3O/
3ZJ/jgC16FzxJrwkSxXK3Qg=
=C0MK
-----END PGP SIGNATURE-----

Andrew Sackville-West wrote:
>
> what is the output of
>
> tail -f /var/log/syslog

See below...

> when started before plugging the device in until after its plugged and
> settled.
>
> If this a regular flash memory stick/card? For example, my camera uses
> bog-standard compact flash cards (about 1.25 inches square by 1/8 in
> thick) and they plug into a standard card reader and mount as

This is a FLASH card for a Sony camera. It is smaller than you describe,
2 inches long, 7/8 inch wide, and 1/8 inch thick (approx). It is a
Sandisk 128 MB card. You may see one here:

http://www.amazon.com/SanDisk-128-MB.../dp/B0000630TK

> /dev/sda1 as a vfat device. Is that what we're trying to do? or is it
> some proprietary format device that doesn't plug into a standard
> cardreader?

I don't own a digital camera, so I can't answer that. It mounts fine
using the Dazzle USB card reader dock, with Windows XP; the same
hardware (dock and card) does not mount with Debian.

Jul 30 14:40:51 localhost -- MARK --
Jul 30 15:00:51 localhost -- MARK --
Jul 30 15:02:01 localhost /USR/SBIN/CRON[25028]: (postgres) CMD (if !
pidof /usr/lib/postgresql/bin/pg_autovacuum > /dev/null && [ -x
/usr/lib/postgresql/bin/do.maintenance ]; then
/usr/lib/postgresql/bin/do.maintenance -a; fi)
Jul 30 15:17:01 localhost /USR/SBIN/CRON[25309]: (root) CMD (
run-parts --report /etc/cron.hourly)
Jul 30 15:40:51 localhost -- MARK --
Jul 30 16:00:51 localhost -- MARK --
Jul 30 16:17:01 localhost /USR/SBIN/CRON[26175]: (root) CMD (
run-parts --report /etc/cron.hourly)
Jul 30 16:40:51 localhost -- MARK --
Jul 30 16:55:04 localhost kernel: hub.c: new USB device 00:07.2-2.3,
assigned address 23
Jul 30 16:55:04 localhost kernel: WARNING: USB Mass Storage data
integrity not assured
Jul 30 16:55:04 localhost kernel: USB Mass Storage device found at 23
Jul 30 16:55:04 localhost hal.hotplug[27795]: could not get mountpoint
for sysfs
Jul 30 16:55:07 localhost usb.agent[27796]: usb-storage: already loaded
Jul 30 16:55:15 localhost kernel: SCSI device sdc: 502784 512-byte hdwr
sectors (257 MB)
Jul 30 16:55:15 localhost kernel: sdc: Write Protect is off
Jul 30 16:55:15 localhost kernel: /dev/scsi/host3/bus0/target0/lun0: p1
Jul 30 16:55:39 localhost kernel: usb.c: USB disconnect on device
00:07.2-2.3 address 23
Jul 30 16:55:39 localhost hal.hotplug[27849]: could not get mountpoint
for sysfs
Jul 30 16:55:58 localhost kernel: hub.c: new USB device 00:07.2-2.3,
assigned address 24
Jul 30 16:55:58 localhost kernel: WARNING: USB Mass Storage data
integrity not assured
Jul 30 16:55:58 localhost kernel: USB Mass Storage device found at 24
Jul 30 16:55:58 localhost hal.hotplug[27883]: could not get mountpoint
for sysfs
Jul 30 16:56:01 localhost usb.agent[27884]: usb-storage: already loaded
Jul 30 16:57:17 localhost kernel: sdc: Unit Not Ready, sense:
Jul 30 16:57:17 localhost kernel: Info fld=0xa00 (nonstd), Current
00:00: sense key Not Ready
Jul 30 16:57:17 localhost kernel: sdc : READ CAPACITY failed.
Jul 30 16:57:17 localhost kernel: sdc : status = 1, message = 00, host =
0, driver = 08
Jul 30 16:57:17 localhost kernel: Info fld=0xa00 (nonstd), Current
sd00:00: sense key Not Ready
Jul 30 16:57:17 localhost kernel: sdc : block size assumed to be 512
bytes, disk size 1GB.
Jul 30 16:57:17 localhost kernel: sdc: test WP failed, assume Write Enabled
Jul 30 16:57:17 localhost kernel: /dev/scsi/host3/bus0/target0/lun0:
I/O error: dev 08:20, sector 0
Jul 30 16:57:17 localhost kernel: I/O error: dev 08:20, sector 0
Jul 30 16:57:17 localhost kernel: unable to read partition table

Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){pri ntf(p,34,p,34);}
Oppose globalization and One World Governments like the UN.
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Hi Mike, McCarty,
Someone has told me before that we should install another package to
import images from Digital Camera. I remember that's the package
'gphoto2'. It will detect almost Digital Camera from different vendors.
But it's just command-line, then we should install gtkam for using
Let's try.

Thang Kieu

Mike McCarty wrote:
> My GF has a situation in which she cannot mount a camera memory
> stick. Here's the setup...
>
> CPU<--->HUB<--->Dazzle[<--Stick
>
> The HUB is from Radio Shack. The Dazzle is a device used to
> interface the memory stick with USB. The memory stick is
> a Sandisk 128 MB memory stick for a camera. Using her laptop
> and XP, with the same Dazzle and memory stick, it mounts
> just fine. With her desktop and Debian, it fails to mount.
>
> Also connected to the hub are a WD USB hard disc, and an HP printer,
> both of which work fine with Debian.
>
> Currently, she mounts using XP on the laptop, then e-mails the photos
> to herself over a dial-up, and then reads the mail back into Debian
> using an ADSL connection. Needless to say, this is not the desirable
> solution.
>
> When we try to mount that memory card, mount responds that it is
> unable to ascertain the file system type. It appears that fdisk
> is unable to read anything from it at all. OTOH, lsusb shows the
> Dazzle device. I have outputs from lsusb, fdisk, and dmesg, but they
> are somewhat lengthy.
>
> Any who are willing to understand what to do to get this
> card to mount, I'll ship them by e-mail, or if consensus agrees
> to it, I'll post them here. They are a few kilobytes altogether.
>
> Thanks all for your time.
>
> Mike


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Hi Mike, McCarty,
Someone has told me before that we should install another package to
import images from Digital Camera. I remember that's the package
'gphoto2'. It will detect almost Digital Camera from different vendors.
But it's just command-line, then we should install gtkam for using
Let's try.

Thang Kieu

Mike McCarty wrote:
> My GF has a situation in which she cannot mount a camera memory
> stick. Here's the setup...
>
> CPU<--->HUB<--->Dazzle[<--Stick
>
> The HUB is from Radio Shack. The Dazzle is a device used to
> interface the memory stick with USB. The memory stick is
> a Sandisk 128 MB memory stick for a camera. Using her laptop
> and XP, with the same Dazzle and memory stick, it mounts
> just fine. With her desktop and Debian, it fails to mount.
>
> Also connected to the hub are a WD USB hard disc, and an HP printer,
> both of which work fine with Debian.
>
> Currently, she mounts using XP on the laptop, then e-mails the photos
> to herself over a dial-up, and then reads the mail back into Debian
> using an ADSL connection. Needless to say, this is not the desirable
> solution.
>
> When we try to mount that memory card, mount responds that it is
> unable to ascertain the file system type. It appears that fdisk
> is unable to read anything from it at all. OTOH, lsusb shows the
> Dazzle device. I have outputs from lsusb, fdisk, and dmesg, but they
> are somewhat lengthy.
>
> Any who are willing to understand what to do to get this
> card to mount, I'll ship them by e-mail, or if consensus agrees
> to it, I'll post them here. They are a few kilobytes altogether.
>
> Thanks all for your time.
>
> Mike


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Mon, Jul 30, 2007 at 05:34:13PM -0500, Mike McCarty wrote:
> Andrew Sackville-West wrote:
>> what is the output of tail -f /var/log/syslog
>
> See below...
>
>> when started before plugging the device in until after its plugged and
>> settled. If this a regular flash memory stick/card? For example, my camera
>> uses
>> bog-standard compact flash cards (about 1.25 inches square by 1/8 in
>> thick) and they plug into a standard card reader and mount as
>
> This is a FLASH card for a Sony camera. It is smaller than you describe,
> 2 inches long, 7/8 inch wide, and 1/8 inch thick (approx). It is a
> Sandisk 128 MB card. You may see one here:
>
> http://www.amazon.com/SanDisk-128-MB.../dp/B0000630TK
>
>> /dev/sda1 as a vfat device. Is that what we're trying to do? or is it
>> some proprietary format device that doesn't plug into a standard
>> cardreader?
>
> I don't own a digital camera, so I can't answer that. It mounts fine
> using the Dazzle USB card reader dock, with Windows XP; the same
> hardware (dock and card) does not mount with Debian.
>
> Jul 30 14:40:51 localhost -- MARK --
> Jul 30 15:00:51 localhost -- MARK --
> Jul 30 15:02:01 localhost /USR/SBIN/CRON[25028]: (postgres) CMD (if ! pidof
> /usr/lib/postgresql/bin/pg_autovacuum > /dev/null && [ -x
> /usr/lib/postgresql/bin/do.maintenance ]; then
> /usr/lib/postgresql/bin/do.maintenance -a; fi)
> Jul 30 15:17:01 localhost /USR/SBIN/CRON[25309]: (root) CMD ( run-parts
> --report /etc/cron.hourly)
> Jul 30 15:40:51 localhost -- MARK --
> Jul 30 16:00:51 localhost -- MARK --
> Jul 30 16:17:01 localhost /USR/SBIN/CRON[26175]: (root) CMD ( run-parts
> --report /etc/cron.hourly)
> Jul 30 16:40:51 localhost -- MARK --
> Jul 30 16:55:04 localhost kernel: hub.c: new USB device 00:07.2-2.3,
> assigned address 23
> Jul 30 16:55:04 localhost kernel: WARNING: USB Mass Storage data integrity
> not assured
> Jul 30 16:55:04 localhost kernel: USB Mass Storage device found at 23
> Jul 30 16:55:04 localhost hal.hotplug[27795]: could not get mountpoint for
> sysfs
> Jul 30 16:55:07 localhost usb.agent[27796]: usb-storage: already
> loaded
> Jul 30 16:55:15 localhost kernel: SCSI device sdc: 502784 512-byte hdwr
> sectors (257 MB)
> Jul 30 16:55:15 localhost kernel: sdc: Write Protect is off
> Jul 30 16:55:15 localhost kernel: /dev/scsi/host3/bus0/target0/lun0: p1
> Jul 30 16:55:39 localhost kernel: usb.c: USB disconnect on device
> 00:07.2-2.3 address 23
> Jul 30 16:55:39 localhost hal.hotplug[27849]: could not get mountpoint for
> sysfs
> Jul 30 16:55:58 localhost kernel: hub.c: new USB device 00:07.2-2.3,
> assigned address 24
> Jul 30 16:55:58 localhost kernel: WARNING: USB Mass Storage data integrity
> not assured
> Jul 30 16:55:58 localhost kernel: USB Mass Storage device found at 24
> Jul 30 16:55:58 localhost hal.hotplug[27883]: could not get mountpoint for
> sysfs
> Jul 30 16:56:01 localhost usb.agent[27884]: usb-storage: already
> loaded
> Jul 30 16:57:17 localhost kernel: sdc: Unit Not Ready, sense:
> Jul 30 16:57:17 localhost kernel: Info fld=0xa00 (nonstd), Current 00:00:
> sense key Not Ready
> Jul 30 16:57:17 localhost kernel: sdc : READ CAPACITY failed.
> Jul 30 16:57:17 localhost kernel: sdc : status = 1, message = 00, host = 0,
> driver = 08
> Jul 30 16:57:17 localhost kernel: Info fld=0xa00 (nonstd), Current sd00:00:
> sense key Not Ready
> Jul 30 16:57:17 localhost kernel: sdc : block size assumed to be 512 bytes,
> disk size 1GB.
> Jul 30 16:57:17 localhost kernel: sdc: test WP failed, assume Write Enabled
> Jul 30 16:57:17 localhost kernel: /dev/scsi/host3/bus0/target0/lun0: I/O
> error: dev 08:20, sector 0
> Jul 30 16:57:17 localhost kernel: I/O error: dev 08:20, sector 0
> Jul 30 16:57:17 localhost kernel: unable to read partition table

based on this I would see what you can see in the partition table:

fdisk -ul /dev/sdc

and I'd say you've probably got a corrupted partition table and the
device and windows happens to be broken in the right ways to make it
still work for them. On the assumption that the camera has its own
built in format option (mine does anyway...) then there's probably no
harm, but take a bit-for-bit copy of the original partition table (dd)
so you can recreate it later if you need to.

hth

A

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGrq+yaIeIEqwil4YRAvcoAJ9ND1yh5+5EMg8/pOb7+LNsN/BbQwCgibT4
KKg2pz1NsiCKXVUNXt8dlPo=
=gEVI
-----END PGP SIGNATURE-----

Andrew Sackville-West wrote:
>
> based on this I would see what you can see in the partition table:
>
> fdisk -ul /dev/sdc

As I mentioned, it can't open it at all. It gives no report whatsoever.

> and I'd say you've probably got a corrupted partition table and the
> device and windows happens to be broken in the right ways to make it
> still work for them. On the assumption that the camera has its own
> built in format option (mine does anyway...) then there's probably no
> harm, but take a bit-for-bit copy of the original partition table (dd)
> so you can recreate it later if you need to.

No, there is no SCSI device recognized, so fdisk reports nothing.

I'm forwarding the lsusb, fdisk, etc. information under separate cover.

Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){pri ntf(p,34,p,34);}
Oppose globalization and One World Governments like the UN.
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/30/07 22:31, Kieu Minh Thang wrote:
> Hi Mike, McCarty,
> Someone has told me before that we should install another package to
> import images from Digital Camera. I remember that's the package
> 'gphoto2'. It will detect almost Digital Camera from different vendors.
> But it's just command-line, then we should install gtkam for using
> Let's try.

In GNOME, gthumb (which depends on libgphoto2) will auto-detect a
camera and auto-import the images for you.

Don't know what the KDE analog is.

- --
Ron Johnson, Jr.
Jefferson LA USA

Give a man a fish, and he eats for a day.
Hit him with a fish, and he goes away for good!

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGrrpKS9HxQb37XmcRAil9AJ9vzkl9IAGIJ6NJhTDLzN SiANdeaACdESyR
vzvm/Xh9pF2Qnmr/kwco1mY=
=PfQm
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Hi Mike, McCarty,
Someone has told me before that we should install another package to
import images from Digital Camera. I remember that's the package
'gphoto2'. It will detect almost Digital Camera from different vendors.
But it's just command-line, then we should install gtkam for using
Let's try.

Thang Kieu



Mike McCarty wrote:
> My GF has a situation in which she cannot mount a camera memory
> stick. Here's the setup...
>
> CPU<--->HUB<--->Dazzle[<--Stick
>
> The HUB is from Radio Shack. The Dazzle is a device used to
> interface the memory stick with USB. The memory stick is
> a Sandisk 128 MB memory stick for a camera. Using her laptop
> and XP, with the same Dazzle and memory stick, it mounts
> just fine. With her desktop and Debian, it fails to mount.
>
> Also connected to the hub are a WD USB hard disc, and an HP printer,
> both of which work fine with Debian.
>
> Currently, she mounts using XP on the laptop, then e-mails the photos
> to herself over a dial-up, and then reads the mail back into Debian
> using an ADSL connection. Needless to say, this is not the desirable
> solution.
>
> When we try to mount that memory card, mount responds that it is
> unable to ascertain the file system type. It appears that fdisk
> is unable to read anything from it at all. OTOH, lsusb shows the
> Dazzle device. I have outputs from lsusb, fdisk, and dmesg, but they
> are somewhat lengthy.
>
> Any who are willing to understand what to do to get this
> card to mount, I'll ship them by e-mail, or if consensus agrees
> to it, I'll post them here. They are a few kilobytes altogether.
>
> Thanks all for your time.
>
> Mike


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Mon, Jul 30, 2007 at 08:42:42PM -0700, Andrew Sackville-West wrote:
> On Mon, Jul 30, 2007 at 05:34:13PM -0500, Mike McCarty wrote:
> > Andrew Sackville-West wrote:
> >> what is the output of tail -f /var/log/syslog
> >
> > See below...
> >
> >> when started before plugging the device in until after its plugged and
> >> settled. If this a regular flash memory stick/card? For example, my camera
> >> uses
> >> bog-standard compact flash cards (about 1.25 inches square by 1/8 in
> >> thick) and they plug into a standard card reader and mount as
> >
> > This is a FLASH card for a Sony camera. It is smaller than you describe,
> > 2 inches long, 7/8 inch wide, and 1/8 inch thick (approx). It is a
> > Sandisk 128 MB card. You may see one here:
> >
> > http://www.amazon.com/SanDisk-128-MB.../dp/B0000630TK
> >
> >> /dev/sda1 as a vfat device. Is that what we're trying to do? or is it
> >> some proprietary format device that doesn't plug into a standard
> >> cardreader?
> >
> > I don't own a digital camera, so I can't answer that. It mounts fine
> > using the Dazzle USB card reader dock, with Windows XP; the same
> > hardware (dock and card) does not mount with Debian.
> >
> > Jul 30 14:40:51 localhost -- MARK --
> > Jul 30 15:00:51 localhost -- MARK --
> > Jul 30 15:02:01 localhost /USR/SBIN/CRON[25028]: (postgres) CMD (if ! pidof
> > /usr/lib/postgresql/bin/pg_autovacuum > /dev/null && [ -x
> > /usr/lib/postgresql/bin/do.maintenance ]; then
> > /usr/lib/postgresql/bin/do.maintenance -a; fi)
> > Jul 30 15:17:01 localhost /USR/SBIN/CRON[25309]: (root) CMD ( run-parts
> > --report /etc/cron.hourly)
> > Jul 30 15:40:51 localhost -- MARK --
> > Jul 30 16:00:51 localhost -- MARK --
> > Jul 30 16:17:01 localhost /USR/SBIN/CRON[26175]: (root) CMD ( run-parts
> > --report /etc/cron.hourly)
> > Jul 30 16:40:51 localhost -- MARK --
> > Jul 30 16:55:04 localhost kernel: hub.c: new USB device 00:07.2-2.3,
> > assigned address 23
> > Jul 30 16:55:04 localhost kernel: WARNING: USB Mass Storage data integrity
> > not assured
> > Jul 30 16:55:04 localhost kernel: USB Mass Storage device found at 23
> > Jul 30 16:55:04 localhost hal.hotplug[27795]: could not get mountpoint for
> > sysfs
> > Jul 30 16:55:07 localhost usb.agent[27796]: usb-storage: already
> > loaded
> > Jul 30 16:55:15 localhost kernel: SCSI device sdc: 502784 512-byte hdwr
> > sectors (257 MB)
> > Jul 30 16:55:15 localhost kernel: sdc: Write Protect is off
> > Jul 30 16:55:15 localhost kernel: /dev/scsi/host3/bus0/target0/lun0: p1
> > Jul 30 16:55:39 localhost kernel: usb.c: USB disconnect on device
> > 00:07.2-2.3 address 23
> > Jul 30 16:55:39 localhost hal.hotplug[27849]: could not get mountpoint for
> > sysfs
> > Jul 30 16:55:58 localhost kernel: hub.c: new USB device 00:07.2-2.3,
> > assigned address 24
> > Jul 30 16:55:58 localhost kernel: WARNING: USB Mass Storage data integrity
> > not assured
> > Jul 30 16:55:58 localhost kernel: USB Mass Storage device found at 24
> > Jul 30 16:55:58 localhost hal.hotplug[27883]: could not get mountpoint for
> > sysfs
> > Jul 30 16:56:01 localhost usb.agent[27884]: usb-storage: already
> > loaded
> > Jul 30 16:57:17 localhost kernel: sdc: Unit Not Ready, sense:
> > Jul 30 16:57:17 localhost kernel: Info fld=0xa00 (nonstd), Current 00:00:
> > sense key Not Ready
> > Jul 30 16:57:17 localhost kernel: sdc : READ CAPACITY failed.
> > Jul 30 16:57:17 localhost kernel: sdc : status = 1, message = 00, host = 0,
> > driver = 08
> > Jul 30 16:57:17 localhost kernel: Info fld=0xa00 (nonstd), Current sd00:00:
> > sense key Not Ready
> > Jul 30 16:57:17 localhost kernel: sdc : block size assumed to be 512 bytes,
> > disk size 1GB.
> > Jul 30 16:57:17 localhost kernel: sdc: test WP failed, assume Write Enabled
> > Jul 30 16:57:17 localhost kernel: /dev/scsi/host3/bus0/target0/lun0: I/O
> > error: dev 08:20, sector 0
> > Jul 30 16:57:17 localhost kernel: I/O error: dev 08:20, sector 0
> > Jul 30 16:57:17 localhost kernel: unable to read partition table
>
> based on this I would see what you can see in the partition table:
>
> fdisk -ul /dev/sdc
>
> and I'd say you've probably got a corrupted partition table and the
> device and windows happens to be broken in the right ways to make it
> still work for them. On the assumption that the camera has its own
> built in format option (mine does anyway...) then there's probably no
> harm, but take a bit-for-bit copy of the original partition table (dd)
> so you can recreate it later if you need to.

some of th windows thumb drives make use of the whole drive as a parition -
there is no partition table you mount the whole drive

>
> hth
>
> A



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGr6E9kZz88chpJ2MRAvk+AKCGmS+PpYTcNIhTU2DfM6 YRphrhZACg1sEn
rFeEt23ykvsVzcIqoGMXKbo=
=TNu1
-----END PGP SIGNATURE-----

Mike McCarty wrote:
> My GF has a situation in which she cannot mount a camera memory
> stick. Here's the setup...
>
> CPU<--->HUB<--->Dazzle[<--Stick
>
> The HUB is from Radio Shack. The Dazzle is a device used to
> interface the memory stick with USB. The memory stick is
> a Sandisk 128 MB memory stick for a camera. Using her laptop
> and XP, with the same Dazzle and memory stick, it mounts
> just fine. With her desktop and Debian, it fails to mount.
>
> Also connected to the hub are a WD USB hard disc, and an HP printer,
> both of which work fine with Debian.

Well, I tried plugging the Dazzle directly into another USB
port, and it mounts just fine. So, why can't the stick mount
through the hub? The "real" disc mounts fine.

The USB ports on this machine are in the back, and it's
inside an armoire so basically enclosed. Since the Dazzle
needs to move to other computers as well, it's inconvenient
to pull the CPU box out and plug it in that way. I'd just
run the cable up to the top and leave it that way, otherwise,
but it does need to move.

In syslog I see problems reading the MBR from the "disc",
and fdisk can't read it, either.

Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){pri ntf(p,34,p,34);}
Oppose globalization and One World Governments like the UN.
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Mon, Aug 06, 2007 at 02:02:09PM -0500, Mike McCarty wrote:

> Well, I tried plugging the Dazzle directly into another USB
> port, and it mounts just fine. So, why can't the stick mount
> through the hub? The "real" disc mounts fine.

Are there any options you can pass to the relevant module? Otherwise I
think it's a bug in the module (though I'm far from being an expert).

Regards,
Andrei
--
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD4DBQFGt3mfqJyztHCFm9kRAoqxAJ4sUVMrG70jqC4AepXvg2 ctF8n3IQCXQhhn
LUlWL0MRIzRUB0RknTXIIg==
=WUep
-----END PGP SIGNATURE-----

On Aug 6, 2007, at 12:02 PM, Mike McCarty wrote:

> Mike McCarty wrote:
>> My GF has a situation in which she cannot mount a camera memory
>> stick. Here's the setup...
>> CPU<--->HUB<--->Dazzle[<--Stick
>> The HUB is from Radio Shack. The Dazzle is a device used to
>> interface the memory stick with USB. The memory stick is
>> a Sandisk 128 MB memory stick for a camera. Using her laptop
>> and XP, with the same Dazzle and memory stick, it mounts
>> just fine. With her desktop and Debian, it fails to mount.
>> Also connected to the hub are a WD USB hard disc, and an HP printer,
>> both of which work fine with Debian.
>
> Well, I tried plugging the Dazzle directly into another USB
> port, and it mounts just fine. So, why can't the stick mount
> through the hub? The "real" disc mounts fine.

Is it a powered hub? I've found some USB devices don't work very
well on un-powered hubs.




--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Andrei Popescu wrote:
> On Mon, Aug 06, 2007 at 02:02:09PM -0500, Mike McCarty wrote:
>
>
>>Well, I tried plugging the Dazzle directly into another USB
>>port, and it mounts just fine. So, why can't the stick mount
>>through the hub? The "real" disc mounts fine.
>
>
> Are there any options you can pass to the relevant module? Otherwise I
> think it's a bug in the module (though I'm far from being an expert).

"The relevant module"? Sorry, I don't know how to answer your question.

Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){pri ntf(p,34,p,34);}
Oppose globalization and One World Governments like the UN.
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

David Brodbeck wrote:
>
> On Aug 6, 2007, at 12:02 PM, Mike McCarty wrote:
>
>>
>> Well, I tried plugging the Dazzle directly into another USB
>> port, and it mounts just fine. So, why can't the stick mount
>> through the hub? The "real" disc mounts fine.
>
>
> Is it a powered hub? I've found some USB devices don't work very well
> on un-powered hubs.

If by "powered hub" you mean "it has its own separate power
supply", then no. Otherwise, I don't know what you mean. It
draws power from the USB. The WD disc is powered through it.

Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){pri ntf(p,34,p,34);}
Oppose globalization and One World Governments like the UN.
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

>
>> On Mon, Aug 06, 2007 at 02:02:09PM -0500, Mike McCarty wrote:
>>> Well, I tried plugging the Dazzle directly into another USB
>>> port, and it mounts just fine. So, why can't the stick mount
>>> through the hub? The "real" disc mounts fine.
>>>
I've had issues in the past when using an unpowered USB hub, some
mouses and keyboards don't work. This might be a similar issue.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Aug 6, 2007, at 2:00 PM, Mike McCarty wrote:
> If by "powered hub" you mean "it has its own separate power
> supply", then no. Otherwise, I don't know what you mean. It
> draws power from the USB. The WD disc is powered through it.

Right, a powered hub has its own power supply. Some devices don't
work right on un-powered ones. Also, plugging too many items into an
un-powered hub can overload the USB port on the host, especially
power-hungry devices like hard disks.




--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Mon, Aug 06, 2007 at 03:58:52PM -0500, Mike McCarty wrote:
> Andrei Popescu wrote:
>> On Mon, Aug 06, 2007 at 02:02:09PM -0500, Mike McCarty wrote:
>>> Well, I tried plugging the Dazzle directly into another USB
>>> port, and it mounts just fine. So, why can't the stick mount
>>> through the hub? The "real" disc mounts fine.
>> Are there any options you can pass to the relevant module? Otherwise I
>> think it's a bug in the module (though I'm far from being an expert).
>
> "The relevant module"? Sorry, I don't know how to answer your question.

I mean some usb kernel module. The 'usbcore' module seems to have some
options for device initialization (modinfo usbcore).

Regards,
Andrei
--
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGt5dtqJyztHCFm9kRAhPHAJoCVj92/XBLaEBEM+HACiOCPRKmHwCfeTv8
RaoVW0d/GT/MlLWdjhwtoVU=
=IDzE
-----END PGP SIGNATURE-----

David Brodbeck wrote:
>
> On Aug 6, 2007, at 2:00 PM, Mike McCarty wrote:
>
>> If by "powered hub" you mean "it has its own separate power
>> supply", then no. Otherwise, I don't know what you mean. It
>> draws power from the USB. The WD disc is powered through it.
>
>
> Right, a powered hub has its own power supply. Some devices don't work
> right on un-powered ones. Also, plugging too many items into an
> un-powered hub can overload the USB port on the host, especially
> power-hungry devices like hard disks.

I tried this with no devices plugged in but the Dazzle, and it
didn't work. I'm pretty sure that just a memory stick isn't
loading the USB power too much :-)

Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){pri ntf(p,34,p,34);}
Oppose globalization and One World Governments like the UN.
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org