Macintosh SE - RaSCSI - no boot

[Kamelie]

Hi

Here what I have in my hands:
- Mac SE (the basic one)
. no keyboard
- no mouse
- hdd removed (assuming not working)
- floppy removed (no boot floppy avalaible)
- rasci installed and plugged instead of internal drive

I used the boot image 6.0.8 found here

Applications A - Z - Macintosh Garden

macintoshgarden.org

But cannot get it boot while the rascsi is the only thing plug ... and seems working. But as far I an see the direct log file I assume the Mac is not even trying ....



I did not see any leakage on the board itself ...


Any idea?
Thx

 

[mg.man]

Have you tried turning TERMination on?? It looks to be off...



This is usually required for a SCSI chain to work = the last device must be TERMinated...

 

[mdeverhart]

What is the Mac itself doing? Does it chime, screen turn on, show anything on the screen?

 

[Kamelie]

You are right! Now I put them both to on


It chimes .. but has always be.

Now I indeed see "happy mac" ... but blinking

At least the log file in trace is telling something interesting
Mar 13 14:10:53 raspberrypi RASCSI[531]: [2022-03-13 14:10:53.691] [trace] virtual void SCSIDEV::Send() Move to next phase msgin (9)
Mar 13 14:10:53 raspberrypi RASCSI[531]: [2022-03-13 14:10:53.691] [trace] virtual void SCSIDEV::BusFree() Bus free phase
Mar 13 14:10:53 raspberrypi RASCSI[531]: [2022-03-13 14:10:53.693] [trace] virtual void SCSIDEV::Selection() Selection Phase ID=2 (with device)
Mar 13 14:10:53 raspberrypi RASCSI[531]: [2022-03-13 14:10:53.693] [trace] virtual void SASIDEV::Command() Command Phase
Mar 13 14:10:53 raspberrypi RASCSI[531]: [2022-03-13 14:10:53.693] [trace] virtual void SASIDEV::Command() CDB[0]=$2A
Mar 13 14:10:53 raspberrypi RASCSI[531]: [2022-03-13 14:10:53.693] [trace] virtual void SASIDEV::Command() CDB[1]=$00
Mar 13 14:10:53 raspberrypi RASCSI[531]: [2022-03-13 14:10:53.693] [trace] virtual void SASIDEV::Command() CDB[2]=$00
Mar 13 14:10:53 raspberrypi RASCSI[531]: [2022-03-13 14:10:53.693] [trace] virtual void SASIDEV::Command() CDB[3]=$00
Mar 13 14:10:53 raspberrypi RASCSI[531]: [2022-03-13 14:10:53.693] [trace] virtual void SASIDEV::Command() CDB[4]=$00
Mar 13 14:10:53 raspberrypi RASCSI[531]: [2022-03-13 14:10:53.693] [trace] virtual void SASIDEV::Command() CDB[5]=$62
Mar 13 14:10:53 raspberrypi RASCSI[531]: [2022-03-13 14:10:53.693] [trace] virtual void SASIDEV::Command() CDB[6]=$00
Mar 13 14:10:53 raspberrypi RASCSI[531]: [2022-03-13 14:10:53.693] [trace] virtual void SASIDEV::Command() CDB[7]=$00
Mar 13 14:10:53 raspberrypi RASCSI[531]: [2022-03-13 14:10:53.693] [trace] virtual void SASIDEV::Command() CDB[8]=$01
Mar 13 14:10:53 raspberrypi RASCSI[531]: [2022-03-13 14:10:53.693] [trace] virtual void SASIDEV::Command() CDB[9]=$00
Mar 13 14:10:53 raspberrypi RASCSI[531]: [2022-03-13 14:10:53.693] [trace] virtual void SCSIDEV::Execute() Execution phase command $2A
Mar 13 14:10:53 raspberrypi RASCSI[531]: [2022-03-13 14:10:53.693] [debug] ++++ CMD ++++ virtual void SCSIDEV::Execute() Executing command $2A
Mar 13 14:10:53 raspberrypi RASCSI[531]: [2022-03-13 14:10:53.693] [debug] virtual bool Disk:ispatch(SCSIDEV*) Executing Write10 ($2A)
Mar 13 14:10:53 raspberrypi RASCSI[531]: [2022-03-13 14:10:53.694] [debug] virtual void Disk::Write10(SASIDEV*) WRITE(10) command record=$00000062 blocks=1
Mar 13 14:10:53 raspberrypi RASCSI[531]: [2022-03-13 14:10:53.694] [trace] bool Disk::CheckReady() Disk is ready
Mar 13 14:10:53 raspberrypi RASCSI[531]: [2022-03-13 14:10:53.694] [trace] void SASIDEV:ataOut() Data out phase
Mar 13 14:10:53 raspberrypi RASCSI[531]: [2022-03-13 14:10:53.694] [trace] virtual void SCSIDEV::Receive()
Mar 13 14:10:53 raspberrypi RASCSI[531]: [2022-03-13 14:10:53.694] [trace] virtual void SCSIDEV::Receive() length is 512
Mar 13 14:10:53 raspberrypi RASCSI[531]: [2022-03-13 14:10:53.697] [trace] virtual void SCSIDEV::Receive()
Mar 13 14:10:53 raspberrypi RASCSI[531]: [2022-03-13 14:10:53.697] [trace] virtual void SCSIDEV::Receive() ctrl.phase: 7 (dataout)
Mar 13 14:10:53 raspberrypi RASCSI[531]: [2022-03-13 14:10:53.697] [trace] virtual bool Disk::Write(const DWORD*, const BYTE*, DWORD)
Mar 13 14:10:53 raspberrypi RASCSI[531]: [2022-03-13 14:10:53.697] [trace] void SASIDEV::Status() Status phase
Mar 13 14:10:53 raspberrypi RASCSI[531]: [2022-03-13 14:10:53.697] [trace] void SASIDEV::Status() Status Phase $00
Mar 13 14:10:53 raspberrypi RASCSI[531]: [2022-03-13 14:10:53.697] [trace] virtual void SCSIDEV::Send() sending handhake with offset 0, length 1
Mar 13 14:10:53 raspberrypi RASCSI[531]: [2022-03-13 14:10:53.697] [trace] virtual void SCSIDEV::Send() Move to next phase status (8)
Mar 13 14:10:53 raspberrypi RASCSI[531]: [2022-03-13 14:10:53.697] [trace] void SASIDEV::MsgIn() Starting Message in phase
Mar 13 14:10:53 raspberrypi RASCSI[531]: [2022-03-13 14:10:53.697] [trace] void SASIDEV::MsgIn() Transitioning to Send()
Mar 13 14:10:53 raspberrypi RASCSI[531]: [2022-03-13 14:10:53.697] [trace] virtual void SCSIDEV::Send() sending handhake with offset 0, length 1
Mar 13 14:10:53 raspberrypi RASCSI[531]: [2022-03-13 14:10:53.697] [trace] void SASIDEV::MsgIn() Transitioning to Send()

 

[Kamelie]

Now I found out ... the boostrap image was causing the blinking! Now it boots nicely! Thx

 

[Kamelie]

As anyone any idea why the boostrap image was the problem?

 

[mg.man]

Now it boots nicely!

No worries, glad you got it going!

any idea why the boostrap image was the problem?

Just a wild guess... could be the SE was trying to boot from that image vs. the 6.0.8 one, and it isn't a proper / (Mac)bootable image - so it was just hanging?... I'm not that familiar with how a RaSCSI works, so just shooting in the dark atm...

 

[cheesestraws]

The Happy Mac means that the hardware is OK and it's found some boot blocks to tell it what System to load. If that System then either isn't there or doesn't want to know, you get what you see here, where the Happy Mac'll appear and then disappear, then it'll try to boot again in a loop ad nauseam.

So I'm guessing either something unfortunate has happened to the bootstrap image, or perhaps it's just wildly unsuitable for your hardware (?).

 

[timtiger]

I experienced the behavior you described previously („blinking“ happy mac) also with an SE some days ago and finished up sideloading the bootstrap image.

In my opinion the image isn‘t set up in a very special way…

 

[jcnva]

As anyone any idea why the boostrap image was the problem?

I've been trying to get my macplus booted from rascsi using these same files, but have only been successful when only one disk is mounted. It does not like when two disks are mounted - I read that the mac looks to boot up starting with scsi id 6, then 5, etc, but no matter what order I mount the disks on the rascsi, it will only boot with one mounted...

 

[mg.man]

I read that the mac looks to boot up starting with scsi id 6, then 5, etc

I believe it's the other way 'round... If no "Startup Drive" (SCSI ID really) has been set in the PRAM, then it will start with ID "0", then "1", etc... There is a Control Panel that let's you set the Startup device (ID).

There is also a keyboard combination you can hold down when powering-up to force startup from a specific SCSI ID == Command-Option-Shift-Delete-# where # is 0 through 6. Not sure this works on a Plus, but might be worth a try.

FWIW, having more than one image mounted should work, you just need to make sure the "bootable" one is the first one the Plus tries, and that both are images the Plus can mount...