Re: strange umass/scsi behaviour

2003-08-07 Thread Nate Lawson
On Thu, 31 Jul 2003, John Hay wrote: > > > > > Does anyone have an idea why the umass/scsi code behave differently > > > > > between if you boot with a device already plugged in as opposed to > > > > > plugging it in later? In my case it is a Sandisk Cruiser. If I plug > > > > > it in before bootin

Re: strange umass/scsi behaviour

2003-07-31 Thread Terry Lambert
John Hay wrote: > Does anyone have an idea why the umass/scsi code behave differently > between if you boot with a device already plugged in as opposed to > plugging it in later? In my case it is a Sandisk Cruiser. If I plug > it in before booting, it works just great, but if I plug it in later, >

Re: strange umass/scsi behaviour

2003-07-30 Thread John Hay
> > > > Does anyone have an idea why the umass/scsi code behave differently > > > > between if you boot with a device already plugged in as opposed to > > > > plugging it in later? In my case it is a Sandisk Cruiser. If I plug > > > > it in before booting, it works just great, but if I plug it in l

Re: strange umass/scsi behaviour

2003-07-30 Thread Nate Lawson
On Wed, 30 Jul 2003, John Hay wrote: > On Tue, Jul 29, 2003 at 11:28:18PM -0700, Nate Lawson wrote: > > On Wed, 30 Jul 2003, John Hay wrote: > > > Does anyone have an idea why the umass/scsi code behave differently > > > between if you boot with a device already plugged in as opposed to > > > plugg

Re: strange umass/scsi behaviour

2003-07-30 Thread Yar Tikhiy
On Wed, Jul 30, 2003 at 08:44:34AM +0200, John Hay wrote: > > The last message is "Opened disk da0 -> 6". That is a little strange > because I thought we only do 10 byte commands to usb devices. The > "problem" is that only da0 pitch up in the /dev directory. There should > be a da0s1 too. Using f

Re: strange umass/scsi behaviour

2003-07-29 Thread John Hay
On Tue, Jul 29, 2003 at 11:28:18PM -0700, Nate Lawson wrote: > On Wed, 30 Jul 2003, John Hay wrote: > > Does anyone have an idea why the umass/scsi code behave differently > > between if you boot with a device already plugged in as opposed to > > plugging it in later? In my case it is a Sandisk Cru

Re: strange umass/scsi behaviour

2003-07-29 Thread Nate Lawson
On Wed, 30 Jul 2003, John Hay wrote: > Does anyone have an idea why the umass/scsi code behave differently > between if you boot with a device already plugged in as opposed to > plugging it in later? In my case it is a Sandisk Cruiser. If I plug > it in before booting, it works just great, but if I

strange umass/scsi behaviour

2003-07-29 Thread John Hay
Hi, Does anyone have an idea why the umass/scsi code behave differently between if you boot with a device already plugged in as opposed to plugging it in later? In my case it is a Sandisk Cruiser. If I plug it in before booting, it works just great, but if I plug it in later, it does not want to w