On Tue, Oct 20, 2015 at 12:10:39PM +0200, Sebastien Marie wrote:
> On Tue, Oct 20, 2015 at 11:09:58AM +0200, Kim Zeitler wrote:
> > Hello
> >
> > On 10/19/15 19:58, Sebastien Marie wrote:
> > >
> > >RELEASE 5.8 returns ENOSYS ("Function not implemented") on tame(2) call
> > >(which is the old name for pledge, so with the same syscall number).
> > I pulled the kernel down from the same URL path as the tgz I used.
> > Before reinstalling the system I noticed, the Kernel login string having an
> > older date than the snapshot.
> >
> > >I would be great if you can grab the kernel version echoed at boot time.
> > >You could use `boot -c' in the boot loader, in order to enter in config
> > >mode, and have the time to read the OpenBSD version.
> > >
> > Sadly EdgeRouterLite have no 'real bootloader' but use U-Boot. Which I guess
> > is part of the problem.
> >
> > My steps where as followed:
> >
> > mv bsd obsd
> > mv /tmp/bsd /bsd
> > mv /tmp/bsd.rd /bsd.rd
> > reboot
> >
> > Can i be, that U-boot does not cleanly reload the new kernel on reboot?
>
> As I don't know U-boot, I couldn't say anything...
>
> As you told previously that you have problem when running command, I
> think you have a valid shell ? If it is the case, could you run:
> # sysctl kern.version
>
> sysctl(8) isn't pledged, so it should be runnable (if you have a shell).
>
> after, if the running bsd is a too old version (without pledge(2)
> support), you will need to change the booted kernel to something else.
>
> Reading the INSTALL.octeon file, it seems it should be possible to
> choose at boottime the image you want to boot. The more simple should be
> to try booting bsd.rd: it is self-contained so inside the RAMDISK the
> userland will be compatible with the kernel.
>
> And after you will have to download another bsd file, and try to boot it.
>
> For checking the version of an arbitrary bsd file, you could use
> what(1):
>
> # what /bsd
> /bsd
> OpenBSD 5.8-current (GENERIC.MP) #27: Tue Oct 20 09:23:20 CEST 2015
>
> I will try to get more information about U-boot.
There is no OpenBSD bootloader for armv7 or octeon, in part because
u-boot by default provides no interface for enumerating disks, reading blocks
or putc/getc equivalents unlike firmware shipped with almost every
other system.
As a result the kernel has to live on filesystems u-boot understands,
fat32 or ext2 not ffs. So /bsd will not be the kernel that is loaded.
kernel arguments like -c to get into ukc can be set via
setenv bootargs
though it seems the octeon code may not use that while armv7 does.
