Command to see CFE / UBOOT variables (SOLVED)

Once more I have forgotten how to display the CFE variables in shell. There is a simple command that shows them when inside a shell/booted up AmigaOS4 session.

Is it also the same command to see UBOOT variables?

@nbache told me what command this was, but I can no longer remember!

@rjd324

https://wiki.amigaos.net/wiki/UserDoc:BIOS

Quote:

I dont have a X1000 so cant check if this is correct.

`nvgetvar'

Thanks.

been a damn long time since I set up my CFE on my X1K. Long story short few months back my system boots up only to a prompt...then I type in menu and everything boots up fine. Have no idea how that happened but would like to know which file I need to edit and where the heck do I have to enter 'menu' so it boots up automatically?

Can you output the contents of your `nvgetvar'?

@rjd324

here it is:
New Shell process 9
9.AmigaOS:> NVGetVar
name=options
little-endian?=
ETH0_HWADDR=00:50:c2:20:d9:ca
MENU_1_COMMAND=setenv amigaboot_quiet Y;set pmu -astate=a4;boot -fatfs cf0:amigaboot.of
MENU_2_COMMAND=
MENU_4_LABEL=Linux-Debian
MENU_TIMEOUT=20
bootargs=root=/dev/sda5
MENU_4_COMMAND=boot -elf -noints -fatfs cf0:vmlinux
os4_bootdevice=auto
MENU_0_LABEL=Boot Options/Beta/CD
MENU_2_LABEL=---
MENU_3_LABEL=---
MENU_1_LABEL=AmigaOS4.x- End User
MENU_x_COMMAND=setenv os4_commandline "DEBUGLEVEL=5 SERIAL";setenv os4_bootdevice "auto";boot-fs=amigafs ide0.1:amigaboot.of
MENU_3_COMMAND=setenv os4_commandline "DEBUGLEVEL=5 SERIAL";setenv os4_bootdevice "auto";boot-fatfs cf0:amigaboot.of
MENU_0_COMMAND=boot -fs=amigafs cf0:amigaboot.of
STARTUP=MENU
framebuffer=800/600/8/0x90000000/832
BOOT_CONSOLE=pcconsole0
CFE_VERSION=PAS-2.0.30
CFE_BOARDNAME=NEMO
CFE_MEMORYSIZE=4096
9.AmigaOS:>

Right, you are missing


Presumably you want to boot into AmgiaOS4 by default, hence why I chose 1.

You should set that variable and remember to save it.

===

If that does not work for you I will actually consult my X1000 documentation and find out what exactly you need.

It may be the MENU_TIMEOUT setting that needs changing. Cannot remember right now.

well I do still want to boot up to the menu first although nowadays my Beta partition is just a backup of my main one.

@rjd324

how to edit NVGetVar file?

`NVGetVar' just fetches the settings from NVRAM.

In order to change the settings you would have to boot into CFE and actually change and then save (do not forget to save) the settings.

I do not believe you can do this from within AmigaOS4 - but would be happy to be told otherwise!

@rjd324

No, that's right, except on the Sams (440 and 460), where ACube have provided a custom NVSetVar command which can set them from AmigaOS.

Would be great to have such a command for X1000 and X5000 (etc.) as well.

Best regards,

Niels

@nbache

Sorry, just revisiting this old thread.

I was certain that there was an NVSetVar for non-SAMs. I may even have used it on my A1XE.

I even have documentation for it in the Documentation/C drawer of my X5000, and no documentation for NVGetVar (yes, I know, it's pretty easy to use, just pointing out we have documentation for non-existent NVSetVar, and no documentation for NVGetvar, which does exist).

Don't know how it would've got there, either from my A1XE or for the brief period I was loaned a SAM. It's also my my emergency USB boot drive, so I think somehow it was released.

@daveyw

No, I believe you're right, there was also an NVSetVar command for the original A1 machines.

I forgot about those, I haven't had a working A1 for a decade or something. Only working OS4 systems here are Sam440ep, Sam460ex, X1000 and X5000/40 - and an A1200 with BPPC/BVision. Oh, and an emulated A4000 in Amiga Forever on my wife's laptop.

Best regards,

Niels

@nbache

Quote:

I distinctly remember this. The A1 had it but the feature was missing on the X1000 for some reason. At times I would have used it to restore firmware variables which was possible as they could be backed up.

Right now my A1 is in a state of flux. I don't know what I've done to it but the main test volume won't boot up and stalls after Kickstart. The beta volume is wrecked after I added RadeonHD drivers in testing and messed up a module name. I need to boot my OS4 CD but even booting off USB which I had working fails in UBoot now.