> Why not faster on the 25-pin connector? Well, every SCSI signal should
> have a seperate ground return pin (which means twisted-pair transmission
> lines end-to-end). That's not possible on the 25-pin designs, so signal
> quality is rather poor. Hence the speed limit...
>
> Now we only need to fi
Just to add a bit more confusion ;-)
On 20 Jun, this message from Michael Schmitz echoed through cyberspace:
>> > Seems in this case it can't. My external disk only runs at 5 MB (of
>> > course).
>>
>> External is different. Since Apple wisely decided on a 25-pin scsi
>> cable scheme for externa
On 29 Sivan 5761, Andrew Sharp wrote:
>> that is understandable since all of Apple's oldworld builtin scsi
>> was 5MB/s only.
>
> You mean the drives were only 5MB/sec? I can believe that, but the
> MESH controller will do 10MB/sec sync. I say that with a crack in
> my voice, because my experie
> > Seems in this case it can't. My external disk only runs at 5 MB (of
> > course).
> >
> > How to set MESH to 5 MB/s? I'd not object to providing a patch that makes
> > it a driver option, if someone can point me to the correct combinattion of
> > period and offset to limit the rate.
>
> Eternal
Michael Schmitz wrote:
> > my voice, because my experience with this controller is that it
> > doesn't work too dang well. With some drives it just plain can't
> > handle the higher speed. But with some drives it can. So it's hit
>
> Seems in this case it can't. My external disk only runs at
On Wed, 20 Jun 2001, Michael Schmitz wrote:
> > > > > Well, at least the drive info and partition table can be read :-)
> > > >
> > > > Just my 2 cents, I had the same problems with a 7300 when I setup MESH
> > > > to run at 10MB/s.
> > > > This problem only ocurred with heavy disk-I/O and it damag
> > > > Well, at least the drive info and partition table can be read :-)
> > >
> > > Just my 2 cents, I had the same problems with a 7300 when I setup MESH
> > > to run at 10MB/s.
> > > This problem only ocurred with heavy disk-I/O and it damaged my
> > > file-system.
> > > With MESH set to 5MB/s
Ethan Benson wrote:
>
> On Wed, Jun 20, 2001 at 12:41:07PM +0200, Christoph Ewering wrote:
> > Hello!
> >
> > Michael Schmitz schrieb:
> > ...
> > > > mesh: target 1 synchronous at 10.0 MB/s
> > ...
> > > Well, at least the drive info and partition table can be read :-)
> >
> > Just my 2 cents, I
On Wed, Jun 20, 2001 at 12:41:07PM +0200, Christoph Ewering wrote:
> Hello!
>
> Michael Schmitz schrieb:
> ...
> > > mesh: target 1 synchronous at 10.0 MB/s
> ...
> > Well, at least the drive info and partition table can be read :-)
>
> Just my 2 cents, I had the same problems with a 7300 when I
Hello!
Michael Schmitz schrieb:
...
> > mesh: target 1 synchronous at 10.0 MB/s
...
> Well, at least the drive info and partition table can be read :-)
Just my 2 cents, I had the same problems with a 7300 when I setup MESH
to run at 10MB/s.
This problem only ocurred with heavy disk-I/O and it dam
> Several people responded to my previous note with good suggestions for
> providing more complete information on my problem. Here's a recap of my
> situation, with what I hope will be more helpful info from dmesg and
> /var/log/messages.
Thanks, this should help narrowing down your problem.
> her
On Wed, Jun 20, 2001 at 01:21:00AM -0500, Jamie Hutt wrote:
>
> I've installed Potato on a Mac 7500, a two-scsi-bus, OldWorld machine. When
> I'm doing a large file copy from one Mac to the Debian box via SAMBA (and
> FTP too!) the collision lights on my hubs go nuts and the Debian machine's
larg
12 matches
Mail list logo
