Blank screen with mouse pointer when using cheat codes EXIT:

[mostar]

Hi,

I'm using last version KDE.
Only when booting using cheat codes EXIT: I got blank screen with mouse pointer.
need crtl+alt+f1 for console (no gui) login.

I what to use the EXIT option how to solve it.

[Ed_P]

Hi mostar, welcome to the forum.

Can you post your boot parms?
Where did you hear about the changes=EXIT cheatcode?
Check the Porteus's /boot/docs/cheatcodes.txt file for examples of the changes=EXIT: use. Lines 459-462.

I've always used the changes=EXIT: option when I boot to save changes. The best part is when I screw up my system when I reboot I can skip saving my changes.

[mostar]

Hi Ed,

here is my boot params:

Code: Select all

/boot/syslinux/vmlinuxuz changes=EXIT:/dev/sda2/some-dir-name inited=/boot/syslinux/initrd.xz

Where did you hear about the changes=EXIT cheatcode?

from the docs, I use to this functionality from puppy linux

The best part is when I screw up my system when I reboot I can skip saving my changes.

How you do it? because its automatically will be save at shutdown?

[Ed_P]

changes=EXIT:/dev/sda2/some-dir-name

It's possible /dev/ needs to be /mnt/ and unless the drive is ext4 format the changes need to reference a save.dat file.

If root is set to the drive you don't need the /dev/sda2 path to the changes folder. I use grub2 and this is my boot code for booting with changes=:

Code: Select all

menuentry " Porteus 5.0 ISO - changes="  --class slackware   --class icon-porteus  {

     set bootparms="volume=10 reboot=cold extramod=$linux_folder/Modules  \
       changes=EXIT:$linux_folder/changes/50save.dat  \
       noload=kde;jinn;lxqt;xfce;lxde;mate;open;dat.xzm;mychanges;autonet" # ;mychanges"

     search -f $iso --set=root
     loopback loop $iso
     linux (loop)/boot/syslinux/vmlinuz      from=$iso $bootparms
#     linux $linux_folder/BootModules/vmlinuz from=$iso $bootparms
     initrd (loop)/boot/syslinux/initrd.xz
#     initrd $linux_folder/initrd/initrd.xz
     } 

Earlier in the cfg I have:

Code: Select all

     set linux_folder=/porteus5.0

#     set iso="/ISOs/Porteus-CINNAMON-v5.0-x86_64-220723.iso"
#     set iso="/ISOs/Porteus-CINNAMON-v5.0-x86_64-220924.iso"
#     set iso="/ISOs/Porteus-CINNAMON-v5.0-x86_64-221210.iso"
#     set iso="/ISOs/Porteus-CINNAMON-v5.0-x86_64-230217.iso"
     set iso="/ISOs/Porteus-CINNAMON-v5.0-x86_64-230406.iso"

And yes I boot ISOs but the codes work for installs also.

How you do it? because its automatically will be save at shutdown?

There is a 3 second pause when shutting down that allows you to abort saving the changes. Just press a key other than Enter or the space bar.

[mostar]

It's possible /dev/ needs to be /mnt/ and unless the drive is ext4 format the changes need to reference a save.dat file.

its ext4.
Please note that when I change form:

Code: Select all

/boot/syslinux/vmlinuxuz changes=EXIT:/dev/sda2/some-dir-name inited=/boot/syslinux/initrd.xz

to:

Code: Select all

/boot/syslinux/vmlinuxuz changes=/dev/sda2/some-dir-name inited=/boot/syslinux/initrd.xz

It work fine.

How to check the log of the xserver.

allso when I'm getting the blank screen with mouse pointer (only when using cheat codes EXIT:)
I'm loging as root via the console ( crtl+alt+f1) and then type startx and work as root.

Still puzzle how can I have GUI as user guest.

[mostar]

Maybe some thing current with user guest, how can I create new user?

[Ed_P]

Please note that when I change form:

Code: Select all

/boot/syslinux/vmlinuxuz changes=EXIT:/dev/sda2/some-dir-name inited=/boot/syslinux/initrd.xz

to:

Code: Select all

/boot/syslinux/vmlinuxuz changes=/dev/sda2/some-dir-name inited=/boot/syslinux/initrd.xz

It work fine.

Interesting.

Have you tried using the Porteus /boot/syslinux/vmlinuz file? From what I've read if you don't specify "some-dir-name" Porteus will create a /changes folder on the drive, so you could try just changes=EXIT:/dev/sda2/ and see what happens.

Maybe some thing current with user guest, how can I create new user?

To not use user guest when booting you could try adding the cheatcode login=root.