public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Sam Creasey <sammy@sammy.net>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	linux-m68k <linux-m68k@lists.linux-m68k.org>
Subject: Re: Booting Linux on Sun3 machines
Date: Fri, 15 Jan 2021 20:05:03 -0500	[thread overview]
Message-ID: <20210116010503.GI1344617@anhedonia> (raw)
In-Reply-To: <CAMuHMdW5Of5dJwVjBytZyuTw3fxv1vPXrTcB6EzLUVW6T3Jsbw@mail.gmail.com>

Honestly, it probably doesn't boot.  The last kernel I knew to boot
successfully was 2.6.16, and that required patches.

My last round of notes is still here: https://sammy.net/sun3/

It does include links to a compiled bootloader to netboot a sun3, and
a very ancient debian userland (though if you get to trying to load
init, I'd call that a victory).

I don't believe I ever wrote up full boot instructions, but the
bootloader is a fork of the NetBSD one, so if you can get
rarp/tftp/nfs/etc working well enough to netboot that, you're in the
right place to try to netboot a Linux kernel.  I don't currently have
a boot server configured, but I might be able to find some time to
set something up and help you debug if you get that far.  I've
certainly still got hardware to test with.

-- Sam

On Fri, Jan 15, 2021 at 07:52:05PM +0100, Geert Uytterhoeven wrote:
> CC sammy
>
> On Fri, Jan 15, 2021 at 7:32 PM John Paul Adrian Glaubitz
> <glaubitz@physik.fu-berlin.de> wrote:
> > Since Arnd has waved with the axe at the Sun3 port this week, I would like to start
> > testing the port to make sure it still boots and if not, we can fix the problems.
> >
> > I have three Sun3 machines in my basement that I can test the kernel on. However,
> > I have zero experience booting these machines, so I was wondering whether anyone
> > has booted Linux on these machines in the past and can tell me how that works.
> >
> > Thanks,
> > Adrian
> >
> > --
> >  .''`.  John Paul Adrian Glaubitz
> > : :' :  Debian Developer - glaubitz@debian.org
> > `. `'   Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
> >   `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

  reply	other threads:[~2021-01-16  2:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-15 18:31 Booting Linux on Sun3 machines John Paul Adrian Glaubitz
2021-01-15 18:52 ` Geert Uytterhoeven
2021-01-16  1:05   ` Sam Creasey [this message]
2021-01-16  5:09     ` Finn Thain
2021-01-16  9:04     ` John Paul Adrian Glaubitz
2021-01-18 20:01     ` Thomas Bogendoerfer
2021-01-18 21:03       ` John Paul Adrian Glaubitz

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=20210116010503.GI1344617@anhedonia \
    --to=sammy@sammy.net \
    --cc=geert@linux-m68k.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=linux-m68k@lists.linux-m68k.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