savefile creates hanging on boot

[Argo Navis]

Hello!
I have been trying to make Porteus work for about a week on my system, but it seems there is one new problem after the other.

I have started from scratch a new install of v.5.01 on a usb stick and created the .dat savefile.
If I insert the path of my save.dat at the end of /porteus/porteus-v5.0-x86_64.cfg, nothing happens and I get booted in "Always Fresh" mode.
When I insert the path on the APPEND line in /boot/syslinux/porteus.cfg, it gets picked up, but then the booting process gets hanged on these lines:

Code: Select all

Triggering udev events /sbin/udevadm trigger -- action=add
Entering run level 4

After that, the behavior is less predictable, sometimes, the GUI will eventually load after around a minute, but super laggy and buggy. Sometimes it will not load up at all.

I found this thread about a similar error : Hanging on boot: Triggering udev events

I tried the 'intel_idle.max_cstate=1' cheatcode, doesn't change anything.
I went and looked in /etc/profile.d/porteus.sh, nothing seems weird or out of place.

Anybody knows what is going on?

[Ed_P]

If you posted the code you changed in the .cfg files it would help.

For my save.dat file I use the cheatcode=EXIT, it reduces the load on the Porteus drive.

Code: Select all

APPEND changes=EXIT:UUID:C23A-6012/changes/50save.dat extramod=UUID:C23A-6012/Modules "

[Blaze]

Argo Navis,
1) For bootup Porteus do you use Legacy (or Legacy+UEFI) with disabled Secure boot or UEFI in BIOS of your laptop?
2) What is file system do you use (FAT32, ext2, ext4 or)?

[Argo Navis]

Solved! I looked at Ed_P line of code and didn't understand half of what was in there, so I did a bit more of reading.
Turns out if I enter the path to my savefile like what the FAQ says, like this:

Code: Select all

APPEND changes=/mnt/sda1/porteus/save.dat

then Porteus boots in a barely functional way, but if I enter the path with the usb's UUID like this:

Code: Select all

APPEND changes=UUID:6EC6-DBA7/porteus/save.dat

then everything runs smoothly.
I don't get why two equivalent path would end up with so different results, but at least, I can finally tinker with Porteus. Yay!
Perhaps it would be a good idea to add a small note in the HOWTO guide I mainly used (http://www.porteus.org/component/conten ... d-one.html) to go take a look at the end of the CHEATCODE guide to read about EXIT and UUID.
Thanks to everyone that helped!!

[Ed_P]

Happy to hear your booting problems are under control Argo.

Something to try:

Code: Select all

APPEND changes=/porteus/save.dat

Not suggesting it's better than the UUID option, just something to see if it works with your system set up.