Forum › Forums › Official Releases › antiX-21/22 “Grup Yorum” › [solved] only default option after reboot from customize menu setup on 21 core
- This topic has 12 replies, 3 voices, and was last updated Feb 18-1:27 pm by robertklsz.
-
AuthorPosts
-
February 13, 2022 at 11:17 pm #77360Member
robertklsz
After a reboot from going through the Customize Boot setup only “antiX-21-runit x64-core (31 October 2021)” option is available.
No other option is displayed. None. Not even the original options such as: Customize Boot menu; Advanced Options; Language – keyboard – Timezone; …
I have done this many times with AntiX 19.5. Does not seem to work with AntiX 21.
- This topic was modified 1 year, 2 months ago by christophe.
- This topic was modified 1 year, 2 months ago by christophe. Reason: Solved
February 14, 2022 at 12:09 am #77361Moderator
christophe
February 14, 2022 at 12:43 am #77362Memberrobertklsz
February 14, 2022 at 2:03 am #77365Moderator
christophe
::I’m sorry, I meant the boot menu. There should be a place toward the middle of the boot sequence, when you make your last choice, to save the changes regarding the boot choices you made on a live system — I assumed this is what we are discussing.
Or are you speaking of peristence settings? (“Semi-auto” & “auto” are persistence save options, which are totally different.)confirmed antiX frugaler, since 2019
February 14, 2022 at 2:48 am #77366Moderator
christophe
::Thanks for pointing this out, robertklsz.
I made a live-usb in virtualbox, and I see the same thing.
During my first boot (using grub menu), and saving at the end of the choices, I end up with only that ONE “choice” on the grub menu on the next boot. Nothing is saved. I’ll check to see if this is just runit of both of the core ISOs.- This reply was modified 1 year, 2 months ago by christophe.
Attachments:
confirmed antiX frugaler, since 2019
February 14, 2022 at 2:55 am #77368Memberrobertklsz
February 14, 2022 at 3:13 am #77369Moderator
christophe
::I made a “real” live-usb & ran the test on the sysvinit x64 core ISO. I got the same result. No options are present on the subsequent boots, not even the chance to use the text menus. (Also the option of which wm should be default is among the “first-run” menu choices, which isn’t applicable on the core edition.)
It definitely appears to be broken on the core ISOs, at the moment.
- This reply was modified 1 year, 2 months ago by christophe.
confirmed antiX frugaler, since 2019
February 14, 2022 at 7:09 pm #77427Forum Admin
anticapitalista
::Can you confirm that this only happens with antiX-21-core or antiX-21-net and not antiX-21-base/full?
Also, can you confirm that it only happens when choosing the second entry in the UEFI/grub drop down menu ie Customize boot (text menus).
Thanks
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
February 14, 2022 at 7:51 pm #77433Forum Admin
anticapitalista
::Here’s a fix.
Customize boot (text menus) under grub should not appear on core/net isos.
If you never use that option, all should be fine.If you are stuck like the first poster, try this.
1. Boot to ‘desktop’ using that one option.
2. Navigate to /live/boot-dev/boot/grub and open as root or sudo the file grub.cfg
3. Remove the Customize (text) entries
Something like this should be removedmenuentry " Customize Boot (text menus)" { linux /antiX/vmlinuz quiet splasht disable=lxF menus initrd /antiX/initrd.gz }4. Save changes and reboot.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
February 17, 2022 at 1:55 am #77576Memberrobertklsz
::The above solution does not fix anything. There is no change in the menus. The one option is the same before and after the change in /live/boot-dev/boot/grub/grub.cfg.
I don’t understand the statement “Customize boot (text menus) under grub should not appear on core/net isos.” as this worked in AntiX-Core-19; Antix-Core-17 and if memory serves it also worked in Antix-Core-15.
February 17, 2022 at 9:43 am #77599Forum Admin
anticapitalista
::Because we have changed how grub operates on live antiX-21 since antiX-21 ships with 2 kernels and because we replaced the old text menu with a newer/better method.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
February 17, 2022 at 1:54 pm #77602Moderator
christophe
::FWIW, robertklsz, perhaps change the contents of your live-usb’s /live/boot-dev/boot/grub/grub.cfg.
(Note: It’s something like /media/demo/antiX-live-usb/boot/grub/grub.cfg if accessed from another antiX system.)Here’s an example:
#------------------------------------------------------------------ # file: /boot/grub/grub.cfg for the Live version of antiX # # This file can get updated automatically on a LiveUSB via the save # feature in the text menus. It is possible to break these updates # by editing this file. #------------------------------------------------------------------ # load defaults # if [ -s $prefix/config/defaults.cfg ]; then source $prefix/config/defaults.cfg fi # search --no-floppy --set=root --fs-uuid %UUID% set timeout=30 set gfxmode=1024x768 set gfxpayload="2048x2048;2048x1280;2048x1080;1920x1080;1680x1050;1600x900;1600x1200;1600x1050;1500x1000;1440x960;1440x900;1368x912;1366x768;1280x800;1280x720;1280x1024;1200x800;1024x768;auto" set default=0 menuentry " antiX-21 x64-core (31 October 2021)" { linux /antiX/vmlinuz quiet splash=v disable=lx initrd /antiX/initrd.gz } menuentry " antiX-21 x64-core toram" { linux /antiX/vmlinuz quiet splash=v disable=lx hostname=a21core tz=America/Chicago toram initrd /antiX/initrd.gz } menuentry " antiX-21 x64-core dynamic persistence" { linux /antiX/vmlinuz quiet splash=v disable=lx hostname=a21core tz=America/Chicago persist_all initrd /antiX/initrd.gz } menuentry " antiX-21 x64-core static persistence" { linux /antiX/vmlinuz quiet splash=v disable=lx hostname=a21core tz=America/Chicago persist_static initrd /antiX/initrd.gz } #menu_color_normal=white/black #menu_color_highlight=yellow/light-gray #menuentry " antiX-21 x64-core Failsafe" { #linux /antiX/vmlinuz quiet splash=v disable=lx failsafe #initrd /antiX/initrd.gz #} #menuentry "antiX-21 x64-core Create Bootchart" { #linux /antiX/vmlinuz quiet splash=v disable=lx bootchart initcall_debug printk.time=y #initrd /antiX/initrd.gz #} #menuentry " antiX-21 x64-core (1024x768)" { #linux /antiX/vmlinuz quiet splash=v disable=lx #initrd /antiX/initrd.gz #} menuentry " Power Off" --hotkey=P { halt } menuentry " Reboot" --hotkey=R { reboot } #if [ -f /boot/grub/theme/help.txt ]; then #menuentry " Help" --hotkey=H { #cat /boot/grub/theme/help.txt #echo -n "Press <Enter> to continue " #read xxx_help #} #fi #} # load boot menus # #if [ -f $prefix/config/bootmenu.cfg ]; then #source $prefix/config/bootmenu.cfg #fiIt is simply grub from the core live-usb, that has pre-set boot options that I like. Obviously, you substitute what YOU like.
This is just an idea, for those who like to use core as a live-usb, and like to customize.
I figure that if one is using core, they should be comfortable setting boot parameters manually. 🙂
- This reply was modified 1 year, 2 months ago by christophe.
confirmed antiX frugaler, since 2019
February 18, 2022 at 1:27 pm #77650Memberrobertklsz
::Thanks Christophe! Your suggestion solved what I was trying to do by tweaking the Custom grub entry.
You see the last thing that you do in the custom menus is setup root and home persistence. Having done that my main question (that i guess i did not articulate very well) was how does one get back to that? How does one login to the new home and root?
If you take away that then one of the main reason to use the core iso’s seems lost.
-
AuthorPosts
- You must be logged in to reply to this topic.
