Hyperion Entertainment Message Boards

mechanic wrote:When I switch on X1000 it takes about 12 sec. before the initial screen appears.

Diffs in my CFE;

1. CFE_MEMORYSIZE 2048
2. STARTUP set pmu -astate=A4;menu (no separate 'speed')
3. NO os4commandline

Not sure about this, but 'speed' sets the variable to whatever, and 'STARTUP'
should then use that variable. So try....STARTUP speed;menu (with saparate speed setting)

I don't think it makes any difference, but
If your not using debug, why have it there(?)

Oh, and Welcome Aboard.

Thank you for your answer. The most settings are from Amigakit except Debian settings.

Perhaps they used debugging for testing and forgot to take it out?
Here is mine. The order is different with Ranger.


name=options
little-endian?=
ETH0_HWADDR=00:50:C2:20:DA:24
MENU_0_LABEL=AmigaOS
MENU_1_LABEL=AmigaOS CD Boot
MENU_0_COMMAND=setenv amigaboot_quiet Y ;boot -fs=amigafs ide0.0:amigaboot.of
MENU_1_COMMAND=setenv amigaboot_quiet Y ;boot -fs=iso atapi0.1:amigaboot.of
MENU_DEFAULT=0
MENU_TIMEOUT=3
STARTUP=set pmu -astate=A4 ; menu
MENU_3_LABEL=Debian /dev/sdc2
MENU_3_COMMAND=setenv bootargs "root=/dev/sdc2" ; boot -elf -noints -fatfs ide1.0:vmlinux-3.5.7
MENU_2_LABEL=MINT /dev/sdb2
MENU_2_COMMAND=setenv bootargs "root=/dev/sdb2" ; boot -elf -fatfs -noints ide1.0:vmlinux-3.5.7
framebuffer=800/600/8/0x90000000/832
BOOT_CONSOLE=pcconsole0
CFE_VERSION=PAS-2.0.30
CFE_BOARDNAME=NEMO
CFE_MEMORYSIZE=2048
amigaboot_quiet=Y

Severin wrote:No such problems here, I've only ever connected to the internal ethernet port once via linux.

A little tip... Try the c:nvgetvar command. it lists your CFE settings so you can just cut'n'paste the text instead of messing about grabbing screens and uploading them.

Does NVGETVAR: still work on the X1000 then, it has stopped doing so here ?

I just get the following message:

"NVGETVAR: Could not open nonvolatile.library V51."

I have 'nonvolatile.library 53.5' for the nonvolatile.library.kmod in Kickstart.

@BillEaves

Always worked for me, even right now.

I also have 53.3 of nonvolatile.library and c:nvgetvar is working fine.

Make sure that you haven't got another version of nvgetvar lying around which is picked first.
Try explicitely "C:nvgetvar"

Try also
nvgetvar > ram:nv.txt

No ':' after nvgetvar.

Raziel wrote:@BillEaves


Make sure that you haven't got another version of nvgetvar lying around which is picked first.
Try explicitely "C:nvgetvar"

I only have one file which is in c:, it is:
NVGetVar 52.1 (09/12/2006)

This looks a bit old - is there a newer version that I may have overwritten at some time ?

BillEaves wrote: I only have one file which is in c:, it is:
NVGetVar 52.1 (09/12/2006)

Same one I have. Works here.

@BillEaves

Let snoopy run and see where the culprit lies...maybe you miss something nonvolatile.library is looking for?

BillEaves wrote:I have 'nonvolatile.library 53.5' for the nonvolatile.library.kmod in Kickstart.

Same one I have here.
Check kicklayout and make sure there is not a semicolon in front of nonvolatile.library.kmod,
if there is then it's not being loaded.

mechanic wrote: Check kicklayout and make sure there is not a semicolon in front of nonvolatile.library.kmod,
if there is then it's not being loaded.

Aha. There was no entry at all for the novolatile.library.kmod !


Edit: Adding the entry back has done the trick