Re: 12-r326622 install won't boot

From: O. Hartmann <ohartmann_at_walstatt.org>
Date: Thu, 14 Dec 2017 13:46:25 +0100
Am Tue, 12 Dec 2017 15:24:34 -0800
"Chris H" <bsd-lists_at_BSDforge.com> schrieb:

> On Tue, 12 Dec 2017 13:56:56 -0800 <bsd-lists_at_BSDforge.com> said
> 
> > On Tue, 12 Dec 2017 14:33:10 -0700 "Warner Losh" <imp_at_bsdimp.com> said
> >   
> > > On Tue, Dec 12, 2017 at 2:28 PM, Chris H <bsd-lists_at_bsdforge.com> wrote:
> > >   
> > > > On Tue, 12 Dec 2017 11:37:33 -0800 <bsd-lists_at_BSDforge.com> said
> > > >
> > > > Hello all,  
> > > >> I just blew away a old RELENG_11, to start working with current. I
> > > >> must admit I had several disappointments regarding the installer.
> > > >> But that's for another topic, and another time.
> > > >> To the point;
> > > >> I completed the install. The only event(s) that might be notable
> > > >> during the install. Was early on during (boot?) I saw a "dumped core"
> > > >> race past on the screen. I also experienced at least 1 LOR. But the
> > > >> install continued, seemingly un(interrupted|affected). That said, I
> > > >> chose the reboot option after completion. Ejected the DVD during POST,
> > > >> and I'm stuck at:
> > > >>
> > > >> BTX loader 1.00 BTX version is 1.02
> > > >> 


> > > >>
> > > >> followed by 2 gibberish characters; 1 appears as a right pointing arrow,
> > > >> the other, kind of like a battlestar galactca spaceship.
> > > >> NOTE: those 2 characters did not show up on the initial reboot from
> > > >> the install (just the 2 lines above). But after I attempted a hard
> > > >> reset after the first fail.
> > > >>  
> > > > OK tried the installation again, and nothings changed.
> > > > Still left with the 2 lines listed above.
> > > >
> > > > Guess I'll have to wait until 12-CURRENT becomes a usable version.
> > > > Sigh...
> > > > I was really hoping to run 12, so I could better develop 11.
> > > > Oh well. Guess I'll grab a copy of 11 off one of the ftp servers, and spin
> > > > it
> > > > up.
> > > >
> > > > Thanks anyway! :-)  
> > > 
> > > 
> > > 
> > > I think a two-week old snapshot would work a lot better if you wanted to
> > > make the jump to -current. I've botched something in my boot loader cleanup
> > > and it's taking a little time to get sorted out...  
> > OH, thank you *very* much, Warner!
> > Whew! Just in time, too. I had almost slipped the 11 DVD into the box.
> > 
> > Thanks again, Warner. Hope the things go well for you.
> > 
> > --Chris  
> Spot on, Warner! r326056 gave me a working 12-CURRENT. Including all
> the LORs. :-)
> 
> Thank you!
> 
[ ... deleted line ...]

I have the same here. I just tried on a APU2C4 r326846 and, as I reported in another
thread earlier, it gives me on a serial console the same:

Consoles: internal video/keyboard
Nothing more.

The last known-good version is r326583. r326584 won't build, the same with r326586 (bails
out with some errors in geli related stuff, I believe) and then the subsequent versions
start to fail. I realised the issues on the serial console driven APU with r326734 and I
tried to "bi-sect", unsuccessfully due to lack of time and resources down to r326583.

Obviously I'm not alone having issues with loader/boot loader and it would be wise to put
out a warning for all the other brave CURRENT testers out ...

Regards,
Oliver

-- 
O. Hartmann

Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).

Received on Thu Dec 14 2017 - 11:47:17 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:14 UTC