Re: smart media card reader problem

2004-01-13 Thread Steven Yap
On Mon, 2004-01-12 at 03:25, Richard Lyons wrote:
 
 [ Removable storage tale of woe elided ]
 
 Any insights, please.

The removable storage devices plug in to the SCSI subsystem. The dev
entries they get mapped to is determined by the order in which they are
found and/or plugged into the computer.  

You need to rescan the SCSI bus, either manually:

   echo scsi add-single-device C B T U /proc/scsi/scsi

  where
   C = Controller  (host)  no.
   B = Bus (Channel)
   T = Target (SCSI ID)
   U = Unit (SCSI LUN)

or run the shell script rescan-scsi-bus.sh 
(see http://sethbuckley.com/wiki/moin.cgi/rescan_2dscsi_2dbus_2esh)

No reboots required.
-- 
Steven Yap [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: smart media card reader problem

2004-01-13 Thread Richard Lyons
On Tuesday 13 January 2004 07:25, Steven Yap wrote:
 On Mon, 2004-01-12 at 03:25, Richard Lyons wrote:
  [ Removable storage tale of woe elided ]
 
  Any insights, please.

 The removable storage devices plug in to the SCSI subsystem. The dev
 entries they get mapped to is determined by the order in which they
 are found and/or plugged into the computer.

 You need to rescan the SCSI bus, either manually:

echo scsi add-single-device C B T U /proc/scsi/scsi

   where
C = Controller  (host)  no.
B = Bus (Channel)
T = Target (SCSI ID)
U = Unit (SCSI LUN)

 or run the shell script rescan-scsi-bus.sh
 (see http://sethbuckley.com/wiki/moin.cgi/rescan_2dscsi_2dbus_2esh)

 No reboots required.

I'm so glad to hear that.  Nostalgia for Doze98 is all very well, but I 
don't expect to reboot from one month to another.  Thanks, Steven, I'll 
try these methods.
-- 
richard


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: smart media card reader problem

2004-01-13 Thread Richard Lyons
On Tuesday 13 January 2004 06:10, Tim Timmerman wrote:
  Richard == Richard Lyons [EMAIL PROTECTED] writes:
 
  No, you're right: it must be the kernel drivers. I've now
  discovered it is worse than you described.  I have no complicated
  filesystems on any of the media, but after mounting any one of them
  it is necessary to reboot before you can mount any other type. 
  This applies also to smart media and to SD cards - not just to the
  disgo.  Now that is tedious...

   Worse.. don't know. What happens is that when you unplug a usb
   storage device and plug in a different one, it gets assigned a
   different drive letter. What used to be /dev/sda is now
   /dev/sdb. The reboot resets the counter.

   In your case then, after plugging in the second device, try
   /dev/sdbsomething in your mount command.

I thought I'd tried all the likely ones, but must have missed the 
correct one then.  I'll investigate next time.  Thanks.

-- 
richard


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: smart media card reader problem

2004-01-13 Thread Andrew Perrin
On Tue, 13 Jan 2004, Richard Lyons wrote:

 On Tuesday 13 January 2004 06:10, Tim Timmerman wrote:
   Richard == Richard Lyons [EMAIL PROTECTED] writes:
  
Worse.. don't know. What happens is that when you unplug a usb
storage device and plug in a different one, it gets assigned a
different drive letter. What used to be /dev/sda is now
/dev/sdb. The reboot resets the counter.

Try using eject /dev/sda to reset the counter. No need to reboot.

Andy Perrin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: smart media card reader problem

2004-01-13 Thread Richard Lyons
On Tuesday 13 January 2004 19:19, Andrew Perrin wrote:
 On Tue, 13 Jan 2004, Richard Lyons wrote:
  On Tuesday 13 January 2004 06:10, Tim Timmerman wrote:
Richard == Richard Lyons [EMAIL PROTECTED] writes:
  
 Worse.. don't know. What happens is that when you unplug a usb
 storage device and plug in a different one, it gets assigned a
 different drive letter. What used to be /dev/sda is now
 /dev/sdb. The reboot resets the counter.

 Try using eject /dev/sda to reset the counter. No need to reboot.

 Andy Perrin

Thanks Andy.  Far and away the simplest method anyone has suggested.

(Churlish of me to complain after such a useful tip, but when replying 
to list it's better to 'reply to list' not to 'reply to all'.  I get 
two copies the way you do it.)

-- 
richard


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



smart media card reader problem

2004-01-12 Thread Richard Lyons
This is puzzling me.  I have used smart media cards from my olympus 
camera not only to read in photos, but also to transfer data.  THe card 
reader is a cheap and simple PCline blue thing plugged into the USB.  
All well and good.  Then I tried a disgo - but got   
   mount: /dev/sda1 is not a valid block device
Meanwhile a different camera has SD cards.  So I got the equivalent 
reader for SD cards.  They also work fine.  Still no problem.

Now I plug in the smart media card reader again, and suddenly all the 
cards that I have used only two weeks ago are unreadable. They all give
   mount: /dev/sda1 is not a valid block device

Seems to me that one of four things can have caused this.

 1 The smart card reader has coincidentally gone wrong just when it 
   was not used for two weeks.

 2 The disgo somehow caused a change of setup or hardware somewhere.

 3 The SD card reader somehow caused a change. (It still works, so
   the hardware and cable would seemm to be ok)

 4 The latest update I did to sid during this period has altered the 
   modules so that they can only read SD and not smart media.  

Or what?...

Any insights, please.

-- 
richard




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: smart media card reader problem

2004-01-12 Thread Colin Watson
On Mon, Jan 12, 2004 at 11:25:44AM +, Richard Lyons wrote:
 This is puzzling me.  I have used smart media cards from my olympus 
 camera not only to read in photos, but also to transfer data.  THe card 
 reader is a cheap and simple PCline blue thing plugged into the USB.  
 All well and good.  Then I tried a disgo - but got   
mount: /dev/sda1 is not a valid block device

I don't know about your other devices, but Disgos show up as /dev/sda,
unpartitioned; you don't have /dev/sda1 etc.

 Now I plug in the smart media card reader again, and suddenly all the 
 cards that I have used only two weeks ago are unreadable. They all give
mount: /dev/sda1 is not a valid block device

I've found sometimes that something in the USB/SCSI layer gets confused
after using my Disgo and I have to reboot to clear it up. This is a bit
crap, but I've never got round to investigating properly ...

Cheers,

-- 
Colin Watson  [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: smart media card reader problem

2004-01-12 Thread Richard Lyons
On Monday 12 January 2004 11:37, Colin Watson wrote:
 On Mon, Jan 12, 2004 at 11:25:44AM +, Richard Lyons wrote:
[...]
   Then I tried a disgo - but got
 mount: /dev/sda1 is not a valid block device

 I don't know about your other devices, but Disgos show up as
 /dev/sda, unpartitioned; you don't have /dev/sda1 etc.

Okay, I might look at that, but maybe in light of you later comments, I 
might just give the disgo to a windoze user...

[...]
 I've found sometimes that something in the USB/SCSI layer gets
 confused after using my Disgo and I have to reboot to clear it up.
 This is a bit crap, but I've never got round to investigating
 properly ...

Aah!  That did it.  Takes me back to my days on the dark side...

Thanks Colin.

-- 
richard


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: smart media card reader problem

2004-01-12 Thread Colin Watson
On Mon, Jan 12, 2004 at 11:53:45AM +, Richard Lyons wrote:
 On Monday 12 January 2004 11:37, Colin Watson wrote:
  On Mon, Jan 12, 2004 at 11:25:44AM +, Richard Lyons wrote:
 [...]
Then I tried a disgo - but got
  mount: /dev/sda1 is not a valid block device
 
  I don't know about your other devices, but Disgos show up as
  /dev/sda, unpartitioned; you don't have /dev/sda1 etc.
 
 Okay, I might look at that, but maybe in light of you later comments, I 
 might just give the disgo to a windoze user...

Heh. I don't think they're *that* bad, actually; I'm almost certain that
the bug must be in the kernel drivers rather than in hardware. I haven't
got round to trying it with 2.6 to see if that clears it up.

My Disgo setup is a little complicated since it has a VFAT filesystem
containing a loop-mounted ext2 filesystem containing a cfs filesystem,
which tends to confuse issues like this somewhat.

Cheers,

-- 
Colin Watson  [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: smart media card reader problem

2004-01-12 Thread Richard Lyons
On Monday 12 January 2004 12:03, Colin Watson wrote:
 On Mon, Jan 12, 2004 at 11:53:45AM +, Richard Lyons wrote:
  On Monday 12 January 2004 11:37, Colin Watson wrote:
   On Mon, Jan 12, 2004 at 11:25:44AM +, Richard Lyons wrote:
 
  [...]
 
 Then I tried a disgo - but got
   mount: /dev/sda1 is not a valid block device
  
   I don't know about your other devices, but Disgos show up as
   /dev/sda, unpartitioned; you don't have /dev/sda1 etc.
 
  Okay, I might look at that, but maybe in light of you later
  comments, I might just give the disgo to a windoze user...

 Heh. I don't think they're *that* bad, actually; I'm almost certain
 that the bug must be in the kernel drivers rather than in hardware. I
 haven't got round to trying it with 2.6 to see if that clears it up.

 My Disgo setup is a little complicated since it has a VFAT filesystem
 containing a loop-mounted ext2 filesystem containing a cfs
 filesystem, which tends to confuse issues like this somewhat.

No, you're right: it must be the kernel drivers. I've now discovered it 
is worse than you described.  I have no complicated filesystems on any 
of the media, but after mounting any one of them it is necessary to 
reboot before you can mount any other type.  This applies also to smart 
media and to SD cards - not just to the disgo.  Now that is tedious...

Hey ho.

-- 
richard


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: smart media card reader problem

2004-01-12 Thread Tim Timmerman
 Richard == Richard Lyons [EMAIL PROTECTED] writes:

 No, you're right: it must be the kernel drivers. I've now discovered it 
 is worse than you described.  I have no complicated filesystems on any 
 of the media, but after mounting any one of them it is necessary to 
 reboot before you can mount any other type.  This applies also to smart 
 media and to SD cards - not just to the disgo.  Now that is tedious...
  Worse.. don't know. What happens is that when you unplug a usb
  storage device and plug in a different one, it gets assigned a
  different drive letter. What used to be /dev/sda is now
  /dev/sdb. The reboot resets the counter. 

  In your case then, after plugging in the second device, try
  /dev/sdbsomething in your mount command. 

  Funnily enough, I think there is a reasonable explanation for
  this.. just can't remember it at the moment. 
 Hey ho.
  Indeed. 

  TimT
 -- 
 richard


 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]


-- 
[EMAIL PROTECTED]  040-2683613
[EMAIL PROTECTED]   Voodoo Programmer/Keeper of the Rubber Chicken
There are very few things better than being owned by a cat!  



-- 
The information contained in this communication and any attachments is confidential 
and may be privileged, and is for the sole use of the intended recipient(s). Any 
unauthorized review, use, disclosure or distribution is prohibited. If you are not the 
intended recipient, please notify the sender immediately by replying to this message 
and destroy all copies of this message and any attachments. ASML is neither liable for 
the proper and complete transmission of the information contained in this 
communication, nor for any delay in its receipt.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]