From: Eyal Lebedinsky <eyal@eyal.emu.id.au>
To: "Mr. James W. Laferriere" <babydr@baby-dragons.com>
Cc: list linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.19: sym53c8xx problems
Date: Sun, 06 Oct 2002 09:36:25 +1000 [thread overview]
Message-ID: <3D9F7779.579746C6@eyal.emu.id.au> (raw)
In-Reply-To: <Pine.LNX.4.44.0210051116120.20304-100000@filesrv1.baby-dragons.com>
"Mr. James W. Laferriere" wrote:
>
> Hello Eyal , I have a CP6000 unit (PPRO's tho) & am having no
> such difficulties . Now that said I rebuilt the WHOLE scsi
> layout in the system in order to get rid of those older hotswap
> cages (imo, they stink electrically) . Btw , Stable as heck .
> Wheres that forest I need to knock on ;-)
Sounds good
> Is your scsi setup easy enough to make an ascii art description
> of ? If so would you post it please ? From the messages below
> it appears (to me) that their is some difficulty in the chain that
> attaches to the python . I have never seen those messages when I
> have attached (albeit differant) tape drives , ie: DLT,dat2,dat3 .
As I mentioned the ONLY scsi device is the externally connected DDS-1
tape drive. It is a SCSI-2 narrow (50-pin) device. It uses a
HD-centronics->50pin\x12-centronics cable.
I believe the BIOS on this machine really does not like and IDE disks
connected. It does have an IDE controller but will only allow the CD
drive on it, so we have a PCI/IDE controller installed to handle the
single IDE disk. The machine refuses to boot off the IDE but LILO is
happy to do so off a floppy.
BTW, I only have this machine in order to test out software on a 4-way
SMP machine, which is why we passed on installing more expensive scsi
disks.
Now, when I connect the cable to my tape, lilo fails to boot off the
floppy. It seems that the first BIOS disk (80h) which is detected
properly by the IDE controller is trashed by the scsi controller
(which initialises later than the IDE). So we now boot off the floppy
directly (i.e. the kernel boots off the floppy, not just lilo).
Finally, now that we are booting just fine, and the scsi tape drive
is clearly detected at bootup by the kernel, I see that the scsi
driver does not stay loaded (maybe the boot process loads it, and
if there are no disks it unloads it?). So I try to load it myself
modprobe sym53c8xx
and this kills the machine.
By "kills" I mean the machine stutters for a few seconds, and then
locks up, not even vt switching. No message is ever displayed.
--
Eyal Lebedinsky (eyal@eyal.emu.id.au) <http://samba.org/eyal/>
next prev parent reply other threads:[~2002-10-05 23:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-05 12:34 Eyal Lebedinsky
2002-10-05 15:24 ` Mr. James W. Laferriere
2002-10-05 23:36 ` Eyal Lebedinsky [this message]
2002-10-07 4:22 ` Mr. James W. Laferriere
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3D9F7779.579746C6@eyal.emu.id.au \
--to=eyal@eyal.emu.id.au \
--cc=babydr@baby-dragons.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®