Blade 100 w/ 5.4-PRERELEASE console
David O'Brien
obrien at freebsd.org
Sun Mar 13 19:05:23 PST 2005
On Sun, Mar 13, 2005 at 10:33:50PM +0100, Marius Strobl wrote:
> On Sun, Mar 13, 2005 at 01:14:40PM -0800, David O'Brien wrote:
> > On Sat, Mar 12, 2005 at 06:19:35PM +0100, Marius Strobl wrote:
> > > On Sat, Mar 12, 2005 at 12:22:14AM -0600, Will Andrews wrote:
> > > > mess with the OBP variables. I believe this is needless pain for
> > > > users trying to install FreeBSD on their Blade 100s (and possibly
> > > > other models).
> > >
> > > No, this is a nit which easily can be worked around. A real pain is
> > > that binutils are broken on sparc64 and users have to manually apply
> > > a patch to the base src and recompile binutils in order to be able
> > > to build a number of ports.
> >
> > Applying a patch that is running work around is a nit which can be easily
> > worked around. NOT being able to boot to apply a patch isn't.
> >
>
> I don't get what you try to say with the first sentence but the
> work-around to be able to boot was to set both input-device and
> output-device to ttya. I suggested you to do just this three
> times.
You suggested it on Friday. Why do you think I just stumbled upon it on
Friday? It took up considerable amount of my FreeBSD before I figured
out the bad commit. Its lovely that a commit that breaks things is so
fought for to remain in the tree.
AND if you've been using sparc hardware for the past 15 years, this is
totally non-intuiative.
So now I'm taking your position -- I'm telling you a work around for what
you feel is a big problem -- apply Kris' patch.
--
-- David (obrien at FreeBSD.org)
More information about the freebsd-sparc64
mailing list