on my laptop I installed via network image leap 16.0, everything seems to went well (apart the agama tha is a very bad sofware) but after the boot appear
"you are in emergency mode…
insert root password to login
how can I access to my new leap 16.0??
if it can help I succeed to post the
journalctl -xb https://paste.opensuse.org/pastes/09bbafbe6b99
(suggested after emergency mode)
What is the name of the install image you used, did you verify the checksum etc?
How was the boot media created?
Is this a single boot system?
Did you review the install documentation before proceeding?
https://agama-project.github.io/docs/overview
I downloaded from here
selecting Intel or AMD 64-bit desktops, laptops, and servers (x86_64)
Network Image (712.0 MiB)
but the cheksum wasn’t available and today too isn’t available
I used
SUSE Studio Imagewriter
to make the bootable USB stick, is this ok?
if I insert the USB stick
/media/Install-Leap-16.0-x86_64/
is the name
not, it is (will be) a multi boot system
no I didn’t review install documentation
I learn now that I can make an USB stick with agama
I will try with agama installer
I downloadede checked and tryed but agama installer allow to install only opensuse micro os, tumbleweed and slowroll, no leap 16.0
https://forums.opensuse.org/t/leap-16-0-iso-verification-issue-404-expired-signature/194640/2
Sorry, seems still to be work in progress.
ok, I installed slowroll, it worked but
how “stable” is slowroll?
does slowroll uses yast?
can I install software from tumbleweed repos?
the boot screen is very different from 16.0 (is it possible to have the more beautyful 16.0 boot screen?),
does it support multiboot?
Basically Slowroll copies Tumbleweed once a month and provides security bugfixes in between, so it depends on your definition of “stable”; it is less likely to break than Tumbleweed, if that is the question.
Yes, at the moment, but be aware that YaST is on its way out anyway; better to check Myrlyn and Cockpit when you have time.
Slowroll has its own repos that are synced to Tumbleweed once a month, so basically you get Tumbleweed packages with some delay. Tumbleweed packages should work, but installing from Tumbleweed repos is very likely to cause dependency problems and breakages sooner or later.
Possibly you installed a different bootloader? With Grub2-efi the boot screens are the same, so maybe you are seeing the systemd-boot boot screen that is much more “basic”.
Yes.
Maybe, maybe you could do some searching and reading yourself? All these questions have been addressed over and over again.
I didn’t it volountarly, if I do
sudo update-bootloader --show
it gives me
systemd-boot
so I’ll open a new thread to solve this
Please no. Keep this here. There is no new issue. You already mixed in Slowroll in this Leap-16 tagged thread, it will just add another confusing thread.
The answer is simple: SR uses systemd-boot by default, Leap 16 uses grub2-efi, and both look different. So what? All this info is in our wiki and should not require another dozen of threads here.
sorry I alreay opened another thread (as always suggested by the forum)
I don’t like systemd-boot becouse is small and difficult to read so I would like to have grub2 also in slowroll if it is possible
Yeah, and I flagged it. Again you tagged it with Leap 16, where it is Slowroll and again you don’t tell that you use AI first, do what it says and then come here. That is confusing and wasting time and effort from those who are trying to help.
manythanks here I am
I don’t know if I used AI, I only searched with google to solve.
I found that I have systemd-boot.
I would like to switch to grub2-efi, I googled and found this:
Install GRUB2
Update Bootloader Configuration
Change the loader type variable in /etc/sysconfig/bootloader
LOADER_TYPE=“systemd-boot” and change it to
LOADER_TYPE=“grub2-efi”
Reinitialize and Install GRUB
install GRUB to your EFI partition
sudo update-bootloader --install --config
I installed grub via myrlyn,
in /etc/sysconfig/bootloader I changed:
LOADER_TYPE=“systemd-boot”
LOADER_TYPE=“grub2-efi”
but with sudo update-bootloader --install I had this error:
pla@localhost:~> sudo update-bootloader --install
[sudo] password for pla:
target = x86_64-efi, update default location = 0
+ /usr/sbin/shim-install --config-file=/boot/grub2/grub.cfg
No valid EFI partition
efi_distro_dir=opensuse
efi_order=0000,0003,0005,0004,0002,0001,2001,2002,2003
efi_entry.num=0003
efi_entry.file=EFI/opensuse/shim.efi
efi_entry.name=opensuse-secureboot
pla@localhost:~>
how can I proceed to have grub2-efi bootloader?
You don’t. Stop trying to change perfectly fine working stuff, just because you want to see something different for 8 seconds.
FYI: When I installed TW on my current laptop 3 years ago, grub2-efi was the default. I’ve looked at moving to systemd-boot, even have a 2 GB free space, but nothing and no one could tell me what the win would be in doing so, so I did not proceed.
I cannot guarantee that the following will work since you might have broken your system in unexpected ways already, anyway try:
update-bootloader --loader grub2-efi
update-bootloader --install --config
Since you have several (too many?) boot options installed, maybe you have to search for the good one in the grub screen after reboot.
Alse bear in mind that grub2-efi may disappear at some point… stick with the defaults and move on…
it start to become omplicate, and also maybe grub will disappear??!! he also retired so young?? manythanks, I will try to bear system-boot for some months and see whether he improves or I improve in terms of endurance 