VanillaDPup 10.0.53 fails to load save-folder? (solved)

[mikewalsh]

@dimkr :-

Curious.

As I stated in the other thread, I'm very impressed with this. However, I've come across a situation I've not encountered before.

The save-folder was created at first shut-down, and everything is where it should be. BUT; at next boot, Vanilla DPup steadfastly refuses to load the save-folder. It doesn't even 'show' in the boot-loading text as everything else is detected and loaded. Every subsequent boot is just like a 'first-run' again.

What do you think? Just a 'dodgy' save? Would it wise to re-create the save-folder again?

(I did install the current JWM Desk manager to organise the general appearance & stuff. I never could get the hang of the 'Desktop Settings' application that Micko introduced with one of his Slacko Puppies some time back. Might this have anything to do with it?)

Mike.

[dimkr]

Can you share your boot loader configuration? Maybe you're using pfix=ram.

[mikewalsh]

Can you share your boot loader configuration? Maybe you're using pfix=ram.

Oh, for f***s sakes..... Yup; you are absolutely right, Dima. I WAS using pfix=ram, after all.....and hadn't even realised it!

Here it is (as it was till a few minutes ago!) :-

Code: Select all

title Vanilla DPup 64
  find --set-root uuid () b142cd08-ce81-413e-b963-12b393d8eaa3
  kernel /VanillaDPup64/vmlinuz  pdrv=b142cd08-ce81-413e-b963-12b393d8eaa3  psubdir=/VanillaDPup64 pmedia=satahd pfix=fsckp edd=off pfix=ram
  initrd /VanillaDPup64/initrd.gz

I'd performed my usual trick when adding a new Puppy. I copy a boot stanza - since they're all sub-directories on one main partition - and then edit/modify where necessary. I'd copied Fossapup's boot stanza, completely forgetting that I'd left it in pfix=ram mode because I'm currently testing some stuff on there...

Shows I don't always review what I've done, doesn't it?

That offending "pfix=ram" is now gone.....and as expected, everything's back to how it should be. One question? Do I actually need that "edd=off"? I know Fossapup needs it with this hardware (kernel related? No idea...) but I don't know if Vanilla DPup needs it...

Gawd, I'm a dipstick. At least you got me to look at the bootloader again.....which is where the issue was.

Cheers, mate.

Mike.

[bigpup]

Good test of the pfix=ram boot option in VanillaDpup 10.0.53.

[mikewalsh]

Good test of the pfix=ram boot option in VanillaDpup 10.0.53.

^^^ Lololol!!!

Completely unintended, of course.....but, there ya go. At least we know THAT bit works...

Mike.

[bigpup]

Do I actually need that "edd=off"?

I would remove it and see what happens.