[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: new installation on 4400/200

Bruno Waes wrote:

> ----- Original Message -----
> From: "Ethan Benson" <erbenson@alaska.net>
> To: <debian-powerpc@lists.debian.org>
> Sent: Thursday, April 05, 2001 2:23 PM
> Subject: Re: new installation on 4400/200
> On Thu, Apr 05, 2001 at 10:00:21AM +0200, Bruno Waes wrote:
> >> so far i managed to install debian on i386, sparc and alpha, and now i
> want
> >> to give powerpc a try ;-)
> >you will find that oldworld macs are a right pain in the ass to
> >bootstrap without macos.  if you keep macos around you can use bootx.
> >preferablly use an older macos such as 8 something as 9 is more
> >problematic with bootx.
> i now have the box right beside me, it has macos 7.5.3 loaded on its single
> HD
> the bootx  .sit file is on the cdrom but it is not recognized by macos

Uh oh...  I wasn't able to get it to unpack in MockOS either (on a Motorola
StarMax- pmac 4400 clone with 7.6, the newer StuffIt don't run on <8.1), had to
unpack the tarball in Linux (link somewhere in the "Sand use hfscopy to get it
there in a form where it would run.

> >> is this machine able to boot from cdrom ?
> >>no you will need to use the hfs-boot floppy, but then that is rather
> >>broken see the list archives.  its useful if you want to purge all
> >>traces of MacOS and use quik, but you first need to figure out the
> >>right unholy witchcraft to perform on OpenFirmware to allow quik work
> >>on this particular machine.
> i need linux on this machine, no macos, but i understand i will need macos
> to boot from the first time ?
> is quik something like lilo or silo ??

Yup.  Among other things, it allows you to repartition without worrying about
corrupting your MockOS install.

> what would be the thing i have to do now ?

You might check the archives, search 1Q 2001 for quik, there are relevant
threads starting 2/6 and 3/10.  It might take a few tries with the boot floppies
to get it to work.  For your reference, here's the output of nvsetenv on my
machine (well, the bottom half anyway, the ones you care about):

auto-boot?      false
boot-device     scsi/sd@5:4
boot-file       linux
input-device    kbd
output-device   screen
boot-command    boot linux

In particular, with auto-boot? false, the input and output devices make life a
lot easier, it's a luxury to have working OF screen output (on 4400s and
clones)!  But if you want to remotely reboot, you need to set auto-boot to
true.  I boot from a kernel on the zip drive (hence the boot-device) because
Linux is on hdb, which BrokenFirmware doesn't recognize; your setting there will
be different from mine.

Oh- also, my quik.conf section which should work with the 2.2r2 kernel:

init-message = "Booting Debian GNU/Linux (Woody)\n"
timeout = 0

image = /boot/vmlinux-2.2.18pre21
 append = "video=atyfb:vmode:14,cmode:8"
 label = linux

(Those should be tabs in front of the append and label lines.)  "label=linux" is
what the boot-file and boot-command refer to in OF variables above.  This gives
1024x768, vmode:18 is 1024x870 (but is too much for my monitor).

> >> i am planning it to use as a headless, firewall/gateway box for soho use.

Why headless?  1 MB VRAM not enough for you? :-)

Seriously, I use a StarMax 3000/160 as my home workstation (and firewall/gateway
for the laptop and my wife's PIII 700 :-), and it is a fine box, even reasonably
fast with GNOME 1.4 and enlightenment.


-Adam P.

GPG fingerprint: D54D 1AEE B11C CE9B A02B  C5DD 526F 01E8 564E E4B6

                         Welcome to the best software in

Reply to: