X5000 bootup questions

I powered the X5000,
entered the boot menu,
pressed something accidentally.

Now, when I boot the X5000 from cold I get a white screen that says:
"Could not load bootloader" (or something like that).

I now have to enter the boot menu and specifically choose Boot AmigaOS.

It seems to be trying to boot MorphOS now by default.

1 - Why?

2. Also, why is it that from cold boot I can enter the boot menu and select AmigaOS and boot into AmigaOS much quicker vs just leaving it to boot on its own?

___
EDIT
See also: https://www.amigans.net/modules/newbb/viewtopic.php?post_id=136360 (as of comment #7)

countdown or delay ?

type nvgetvar in your shell to get your U-Boot parameters.

here is what I have :

amigaboot_quiet=N
amigabootmenu_animate=0
baudrate=115200
bdev=sda3
bootargs=root=/dev/sda2 mem=3500M console=ttyS0,115200 console=tty0
bootargs_live=root=/dev/ramdisk boot=casper mem=3500M ro --
bootargs_live_debug=root=/dev/ramdisk boot=casper mem=3500M ro break debug
bootcmd=setenv bootargs root=/dev/$bdev rw console=$consoledev,$baudrate $othbootargs;tftp $loadaddr $bootfile;tftp $fdtaddr $fdtfile;bootm $loadaddr - $fdtaddr
bootdelay=10
bootdvd=scsi reset ; load scsi 0 2000000 boot_dvd ; bootm 2000000
bootfile=uImage
consoledev=ttyS0
eth1addr=00:50:C2:20:DA:CC
ethact=FM1@DTSEC4
ethaddr=00:50:C2:20:DA:CB
ethernetboot=echo Running Ethernet Boot
ethprime=FM1@DTSEC4
fdtaddr=c00000
fman_ucode=7fe73380
harddiskboot=echo Running Hard Disk Boot
hwconfig=fsl_ddr:ctlr_intlv=cacheline,bank_intlv=cs0_cs1;usb1:dr_mode=host,phy_type=utmi;usb2:dr_mode=host,phy_type=utmi
linuxboot=echo Running Linux
liveusb=usb start ; setenv bootargs_live_debug ; ext2load usb 1:1 2000000 boot_dvd ; bootm 2000000
loadaddr=1000000
loadbmps=mmc read 0x10005000 0x500 0x200; mmc read 0x20000000 0x10000 0x20000
massboot=echo Running Mass Storage Boot
mos=bootmorphos
netdev=eth0
nfsboot=setenv bootargs root=/dev/nfs rw nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname:$netdev:off console=$consoledev,$baudrate $othbootargs;tftp $loadaddr $bootfile;tftp $fdtaddr $fdtfile;bootm $loadaddr - $fdtaddr
opticalboot=echo Running Optical Boot
preboot=run loadbmps;bmp d 0x20000000;ami
ramboot=setenv bootargs root=/dev/ram rw console=$consoledev,$baudrate $othbootargs;tftp $ramdiskaddr $ramdiskfile;tftp $loadaddr $bootfile;tftp $fdtaddr $fdtfile;bootm $loadaddr $ramdiskaddr $fdtaddr
ramdiskaddr=2000000
ramdiskfile=ramdisk.uboot
rootpath=/opt/nfsroot
scsidevs=1
stdin=usbkbd,serial
stdout=serial,vga
uboot=u-boot.bin
ubootaddr=0xFFF80000

I just cannot seem to get a grasp on the inconsistent behaviour of this machine.

Just now, I rebooted, changed amigaboot_quiet to N. It booted. Then, I turned the machine off proper, waited for 15 seconds, turned it on. Now I do not get the white screen with "could not load bootloader" and it just works.

Everytime I press the power switch on this thing, I literally do not know what it is going to throw at me next. All I know is that once the RANDOMNESS has stopped and it boots into Workbench, it generally is very stable. But, not having permissions to even post on the Hyperion forums is poor since I can get no support.

Anyway, it is time to shut this thing down and wait until tomorrow and probably be surprised by more sheer randomness from power on!

Here is my nvgetvar:

@rjd324Quote:

Check the cables, especially those connected to the boot devices (HDD, DVD, etc).

I have had a similar problem, and reconnecting the sata cables sorted it.

Tomorrow I will check the battery voltage and check the cables.

I have heard of cables being an issue in these machines, which I find confusing. I mean, why is it that these NG machines are so susceptible to loose cables? Think of our PCs. Never once have I needed to really reseat a cable due to inconsistent behaviour.

Still, I will do this tomorrow.

Good point about the battery, I also changed mine at the same time although I quietly suspect it wasn't a problem and caused issues of its own.

I built my own X5000, so I only have myself to blame (have now switched to cables with latches!), I can't speak for AmigaKit's builds.

Woah,

you can actually just set this variable in uboot:

setenv amigabootmenu_animate 0
saveenv

power on, and see how fast you can boot into workbench.