From: Joshua Juran <jjuran@gmail.com>
To: Finn Thain <fthain@telegraphics.com.au>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Laurent Vivier <laurent@lvivier.info>,
Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: I'm back on linux-m68k
Date: Sat, 8 Nov 2008 08:14:01 -0800 [thread overview]
Message-ID: <E6F5E51C-FCEC-4DCD-85EC-6BD1FFE1088F@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0811090006020.13889@loopy.telegraphics.com.au>
On Nov 8, 2008, at 5:12 AM, Finn Thain wrote:
> On Sat, 8 Nov 2008, Joshua Juran wrote:
>
>> So far, I haven't been able to boot my 950 while a drive connected to
>> the external bus was powered on. The external drive's access
>> light goes
>> on immediately after the screen lights up grey, and startup gets
>> as far
>> as drawing the Mac OS splash screen and maybe 12 pixels of progress
>> before halting, resuming normally if I power off the external drive.
>>
>> Any ideas?
>
> I see the same issue sometimes. I don't think it is a termination
> problem
> but it is hard to say. You could try installing drivers from HD SC
> Setup,
> Drive Setup, Silverlinig or HDT etc.
I had no such problems using a removable storage drive, although I
had to tighten the cable before it was recognized, so it may have
been a cabling issue originally.
Anyway, with regards to startup devices, there's no distinction
between the buses. If you select the device at SCSI ID 5 on bus 1,
the XPRam value is set to 0xFFFFFFDA, just as it would be for bus 0.
And if a SCSI ID is shared by devices on each bus, selecting the
external one in Startup Disk beeps and sets the XPRam value to
0x00000000.
Solution: Pretend it's all one bus and give everything a unique SCSI
ID. Or, just don't 'upstage' the boot disks (with a device of the
same ID on a lower-numbered bus).
(Bad news if you were hoping to have eight or more different startup
disks...)
Josh
next prev parent reply other threads:[~2008-11-08 16:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 9:38 I'm back on linux-m68k Joshua Juran
2008-10-15 14:20 ` Finn Thain
2008-10-15 19:24 ` Tony Mantler
2008-10-15 23:05 ` Laurent Vivier
2008-10-16 0:44 ` Finn Thain
2008-10-16 6:05 ` Laurent Vivier
2008-10-16 6:42 ` Finn Thain
2008-10-16 9:44 ` Joshua Juran
2008-11-03 11:40 ` Joshua Juran
2008-11-03 12:01 ` Geert Uytterhoeven
2008-11-03 19:47 ` Brad Boyer
2008-11-03 21:15 ` Michael Schmitz
2008-11-03 22:37 ` Brad Boyer
2008-11-04 7:25 ` Michael Schmitz
2008-11-04 17:59 ` Brad Boyer
2008-11-04 8:05 ` Joshua Juran
2008-11-04 18:37 ` Riccardo
2008-11-08 9:00 ` Joshua Juran
2008-11-08 13:12 ` Finn Thain
2008-11-08 16:14 ` Joshua Juran [this message]
2008-11-09 2:05 ` Brad Boyer
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=E6F5E51C-FCEC-4DCD-85EC-6BD1FFE1088F@gmail.com \
--to=jjuran@gmail.com \
--cc=fthain@telegraphics.com.au \
--cc=geert@linux-m68k.org \
--cc=laurent@lvivier.info \
--cc=linux-m68k@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