5.5 bsd.rd fails to boot on alix

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

5.5 bsd.rd fails to boot on alix

Dewey Hylton-5
i have 3 alix 2d13 machines, all currently running something between 5.1 and 5.3. each of these fails to boot the 5.5 bsd.rd (i386). bsd.rd checksums match. each time i attempt to boot the 5.5 bsd.rd on any of these 3 machines, i see the following two lines:

    booting tftp:bsd.rd: <snip>
    entry point at 0x200120

i've also booted the machines to their current openbsd install, downloaded the bsd.rd file locally, rebooted, and attempted to boot the new bsd.rd from the boot prompt. i get the same thing doing that, excepting for the tftp: blurb. for this reason i don't believe networking has anything to do with the failure. because i see the same thing via pxe, i don't believe the on-disk code has anything to do with the failure either.

i've run memtest, nothing bad to report. i've tried different serial speeds (9600, 38400, 115200), no changes. the 5.4 bsd.rd works just fine, while the latest snapshot yields the same problem.

i'm hoping this is a known behavior resulting from a change for which i've simply missed the clue. has something changed, and i am simply doing something wrong for the newer version of openbsd?

Reply | Threaded
Open this post in threaded view
|

Re: 5.5 bsd.rd fails to boot on alix

Gilles Cafedjian
Hello,
I have an Alix 2d13 booting fine OpenBSD 5.5.
If there is no error messages, maybe you just lost connection with
serial line.

Did you set "set tty com0" at the boot prompt?

I have this from my root tftp:

$ cat ./etc/boot.conf  
set tty com0
boot bsd.rd

The default alix work at 38400, but I set it to 9600 to be directly
compatible with OpenBSD default.
(but you can change it from boot.conf to run OpenBSD at 38400)

Try to set "set tty com0" or change the speed rate.

On 06/29/14 08:09, Dewey Hylton wrote:

> i have 3 alix 2d13 machines, all currently running something between 5.1 and 5.3. each of these fails to boot the 5.5 bsd.rd (i386). bsd.rd checksums match. each time i attempt to boot the 5.5 bsd.rd on any of these 3 machines, i see the following two lines:
>
>     booting tftp:bsd.rd: <snip>
>     entry point at 0x200120
>
> i've also booted the machines to their current openbsd install, downloaded the bsd.rd file locally, rebooted, and attempted to boot the new bsd.rd from the boot prompt. i get the same thing doing that, excepting for the tftp: blurb. for this reason i don't believe networking has anything to do with the failure. because i see the same thing via pxe, i don't believe the on-disk code has anything to do with the failure either.
>
> i've run memtest, nothing bad to report. i've tried different serial speeds (9600, 38400, 115200), no changes. the 5.4 bsd.rd works just fine, while the latest snapshot yields the same problem.
>
> i'm hoping this is a known behavior resulting from a change for which i've simply missed the clue. has something changed, and i am simply doing something wrong for the newer version of openbsd?

Reply | Threaded
Open this post in threaded view
|

Re: 5.5 bsd.rd fails to boot on alix

Christian Weisgerber
In reply to this post by Dewey Hylton-5
On 2014-06-29, Dewey Hylton <[hidden email]> wrote:

> i have 3 alix 2d13 machines, all currently running something
> between 5.1 and 5.3. each of these fails to boot the 5.5 bsd.rd
> (i386). bsd.rd checksums match. each time i attempt to boot the 5.5
> bsd.rd on any of these 3 machines, i see the following two lines:
>
>     booting tftp:bsd.rd: <snip>
>     entry point at 0x200120

Looks like the kernel doesn't switch to the serial console.
If you boot from the network, make sure that you have an etc/boot.conf
file on the TFTP server.  Also, make sure that you use the 5.5 pxeboot
and not an old one, because...

> i've also booted the machines to their current openbsd install,
> downloaded the bsd.rd file locally, rebooted, and attempted to boot
> the new bsd.rd from the boot prompt. i get the same thing doing
> that, excepting for the tftp: blurb.

I vaguely remember that at some point there was a change that
requires a new boot(8), otherwise a serial console won't be set
correctly with a new kernel.

--
Christian "naddy" Weisgerber                          [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: 5.5 bsd.rd fails to boot on alix

Nick Holland
In reply to this post by Dewey Hylton-5
On 06/29/14 02:08, Dewey Hylton wrote:

> i have 3 alix 2d13 machines, all currently running something between
> 5.1 and 5.3. each of these fails to boot the 5.5 bsd.rd (i386).
> bsd.rd checksums match. each time i attempt to boot the 5.5 bsd.rd on
> any of these 3 machines, i see the following two lines:
>
> booting tftp:bsd.rd: <snip> entry point at 0x200120
>
> i've also booted the machines to their current openbsd install,
> downloaded the bsd.rd file locally, rebooted, and attempted to boot
> the new bsd.rd from the boot prompt. i get the same thing doing that,
> excepting for the tftp: blurb. for this reason i don't believe
> networking has anything to do with the failure. because i see the
> same thing via pxe, i don't believe the on-disk code has anything to
> do with the failure either.

I think you are wrong on that.

> i've run memtest, nothing bad to report. i've tried different serial
> speeds (9600, 38400, 115200), no changes. the 5.4 bsd.rd works just
> fine, while the latest snapshot yields the same problem.
>
> i'm hoping this is a known behavior resulting from a change for which
> i've simply missed the clue. has something changed, and i am simply
> doing something wrong for the newer version of openbsd?

I think you missed the "Install new boot blocks" step of upgrade55.html.
This causes your serial console config to be ignored, and gives you the
results you are seeing.

Note: you need to respect the "one-release-at-a-time" thing here --
installing the 5.3 boot blocks probably won't help you -- upgrade from
5.3 to 5.4 to get the 5.4 boot blocks in place, then again to 5.5.

Nick.

Reply | Threaded
Open this post in threaded view
|

Re: 5.5 bsd.rd fails to boot on alix

Dewey Hylton-5
In reply to this post by Christian Weisgerber
> From: "Christian Weisgerber" <[hidden email]>
> To: "dewey hylton" <[hidden email]>
> Sent: Sunday, June 29, 2014 10:10:35 AM
> Subject: Re: 5.5 bsd.rd fails to boot on alix
>
> [This message has also been posted to list.openbsd.misc.]
> On 2014-06-29, Dewey Hylton <[hidden email]> wrote:
>
> > i have 3 alix 2d13 machines, all currently running something
> > between 5.1 and 5.3. each of these fails to boot the 5.5 bsd.rd
> > (i386). bsd.rd checksums match. each time i attempt to boot the 5.5
> > bsd.rd on any of these 3 machines, i see the following two lines:
> >
> >     booting tftp:bsd.rd: <snip>
> >     entry point at 0x200120
>
> Looks like the kernel doesn't switch to the serial console.
> If you boot from the network, make sure that you have an
> etc/boot.conf

agreed; yes, i have boot.conf in place, which is how the other 5.x versions of bsd.rd are working.

> file on the TFTP server.  Also, make sure that you use the 5.5
> pxeboot
> and not an old one, because...
>
> > i've also booted the machines to their current openbsd install,
> > downloaded the bsd.rd file locally, rebooted, and attempted to boot
> > the new bsd.rd from the boot prompt. i get the same thing doing
> > that, excepting for the tftp: blurb.
>
> I vaguely remember that at some point there was a change that
> requires a new boot(8), otherwise a serial console won't be set
> correctly with a new kernel.

hmmm ... would this affect both pxe and locally booting bsd.rd? if so, this is probably my issue. i'm betting that the current pxeboot version is from 4.7 or 4.8, and the on-disk version of boot on all 3 boxes is 5.1 ... i can test this tomorow morning.

thanks for this pointer! where is this documented?

>
> --
> Christian "naddy" Weisgerber
>                          [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: 5.5 bsd.rd fails to boot on alix

Christian Weisgerber
Dewey Hylton:

> > I vaguely remember that at some point there was a change that
> > requires a new boot(8), otherwise a serial console won't be set
> > correctly with a new kernel.
>
> hmmm ... would this affect both pxe and locally booting bsd.rd?

It affects both pxeboot(8) and boot(8) on disk.

> where is this documented?

I don't think it is explicitly documented anywhere, but this may
be pertinent:

"Upgrades are only supported from one release to the release immediately
 following it. Do not skip releases. If you got lucky skipping releases
 in the past, you may not this time."

--
Christian "naddy" Weisgerber                          [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: 5.5 bsd.rd fails to boot on alix

Nick Holland
In reply to this post by Dewey Hylton-5
On 06/29/14 15:27, Dewey Hylton wrote:
>> From: "Christian Weisgerber" <[hidden email]> To: "dewey
...
> hmmm ... would this affect both pxe and locally booting bsd.rd? if
> so, this is probably my issue. i'm betting that the current pxeboot
> version is from 4.7 or 4.8, and the on-disk version of boot on all 3
> boxes is 5.1 ... i can test this tomorow morning.
>
> thanks for this pointer! where is this documented?

http://www.openbsd.org/faq/upgrade55.html

See "Install new boot blocks" -- the first one.

However, read the whole thing.

Nick.

Reply | Threaded
Open this post in threaded view
|

Re: 5.5 bsd.rd fails to boot on alix

Stuart Henderson
In reply to this post by Christian Weisgerber
On 2014-06-29, Christian Weisgerber <[hidden email]> wrote:

> Dewey Hylton:
>
>> > I vaguely remember that at some point there was a change that
>> > requires a new boot(8), otherwise a serial console won't be set
>> > correctly with a new kernel.
>>
>> hmmm ... would this affect both pxe and locally booting bsd.rd?
>
> It affects both pxeboot(8) and boot(8) on disk.
>
>> where is this documented?
>
> I don't think it is explicitly documented anywhere, but this may
> be pertinent:
>
> "Upgrades are only supported from one release to the release immediately
>  following it. Do not skip releases. If you got lucky skipping releases
>  in the past, you may not this time."
>

I documented this carefully in current.html (after having been bitten
by it on a couple of machines) but unfortunately this didn't make it
through to the release notes.

+<a name="20140214"></a>
+<h3>2014/02/14 - amd64/i386 serial consoles need current bootloader</h3>
+This is a reminder of a change which
+<a href="http://permalink.gmane.org/gmane.os.openbsd.cvs/124092">took place
+earlier</a>: backward compatibility for learning about a serial console device
+from old boot loaders was removed.
+This only affects those who will be doing a <b>remote</b> upgrade <b>via serial
+console</b> on <b>amd64/i386</b> who do not already have "BOOT 3.20" (amd64)
+or "BOOT 3.18" (i386).<p>
+The boot loader is updated as part of the normal upgrade procedure
+via the install media, but users who have previously upgraded from
+OpenBSD 5.2 or earlier using the "without install kernel" method on a
+running system may have missed this step.
+If this is the case, you can either do a ramdisk-based update to
+OpenBSD 5.4 first (even if you are already running 5.4), or manually
+use
+<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=installboot&manpath=OpenBSD+5%2e4&arch=i386">installboot(8)</a>
+<!-- XXX do not update 5.4 link above to 5.5, this needs to show the old
+installboot syntax which has now changed -->
+to update to boot blocks from OpenBSD 5.3 or 5.4, before attempting to
+boot a 5.5 kernel or installer.

Reply | Threaded
Open this post in threaded view
|

Re: 5.5 bsd.rd fails to boot on alix

Dewey Hylton-5
In reply to this post by Christian Weisgerber
Christian Weisgerber:

> > > I vaguely remember that at some point there was a change that
> > > requires a new boot(8), otherwise a serial console won't be set
> > > correctly with a new kernel.
> >
> > hmmm ... would this affect both pxe and locally booting bsd.rd?
>
> It affects both pxeboot(8) and boot(8) on disk.
>
> > where is this documented?
>
> I don't think it is explicitly documented anywhere, but this may
> be pertinent:
>
> "Upgrades are only supported from one release to the release
> immediately
>  following it. Do not skip releases. If you got lucky skipping
>  releases
>  in the past, you may not this time."

excellent, copying the updated pxeboot(8) into place was the ticket.

as this was not an upgrade, but instead a wipe-and-reload it never occurred to me that the boot(8) blurb in the upgrading documentation would have been relevant. i now understand that pxeboot(8) is just a modified version of boot(8), but still may not have found it myself because i didn't make that connection.

thanks for pointing this out.