Silvan,
So...I was finally successful in installing OpenMamba, here's how it went.
To start, I used dd to write the openmamba image file to an 8gb usb.
The main thing, (and I should have realized this since there was no grubx64.efi in the install files), I had to go into the BIOS settings on my computer and enable CSM mode.
Upon booting to the usb, it came up with the grub menu and I selected the "default" load line.
I did not have to use the nomodeset switch.
After installation to /dev/sdc, (I have 3 drives with sdc being an extSATA), upon initial boot, I was getting an rpm database error.
So...I rebuilt the rpm database and was able to complete the initial update.
The next thing I want to attempt is adding UEFI boot to OpenMamba.
This gentleman, Roderick Smith, writes great articles on the whole UEFI boot process...I've used his advice for many years. ( https://www.rodsbooks.com/linux-uefi/).
Douglas
Hi Douglas,
I'm glad that you could boot openmamba ISO and install it in CSM mode.
You could now try to create a USB pendrive from a ISO using the provided openmamba tool you find in the start menu by typing USB, then ideally boot in EFI mode from this pendrive and install (the calamares installer supports EFI boot).
My doubt is if it is possible (and whether other distribution do) to distribute a ISO image which you can write with dd into a pendrive and which can be booted in UEFI, but I don't think so.
For this reason there is the openmamba diskimg download, an image that you already tried which contains the EFI ESP partition and should boot. But I think that in EFI boot mode there might be, as previously noticed, KMS video driver problems that should be investigated further...
Silvan,
Well...I had luck with the install, but after rebooting, whenever I attempt to update, either through command line with dnf or through the openmamba updater, the computer hard locks.
The only option is to hold the power button to get it to turn off.
And upon rebooting, it kernel panics.
Like you mentioned, there must be an issue with kms and the kernel on my machine.
I attempted to compile a newer kernel, but downloading a newer kernel and upon running make menuconfig, it just fails as I think the openmamba file system must be different.
Douglas
Hi Douglas,
this means that the glibc-2.34-4mamba upgrade, which would make /lib[64] a symlink to /usr/lib[64], was a failure. The linux loader /lib64/ld-linux-x86-64.so.2 would disappear and no executable can be run, it is not a problem with the kernel, which will panic because it won't be able to run /sbin/init after switching to the rootfs.
The fix is to either start from the most recent ISO livecd image or do a manual recovery by booting a live system and perform a series of terminal command such as:
wget https://cdn.openmamba.org/pub/openmamba/devel/RPMS.x86_64/glibc-2.34-4mamba.x86_64.rpm
sudo su
mkdir /mnt/sda1
mount /dev/sda1 /mnt/sda1
mount -o bind /dev /mnt/sda1/dev
mount -o bind /proc /mnt/sda1/proc
mount -o bind /sys /mnt/sda1/sys
rpm -r /mnt/sda1 -u glibc-2.34-4mamba.x86_64.rpm
chroot /mnt/sda1
dnf updateThis would fix the main issue although repairing of any of the packages which were part of the upgrade may be needed as well.
Silvan,
Good day...
So, not much luck with running the update that you suggested.
First, the wget command to download glibc failed with a "certificate not trusted error" and a, "doesn't have a known user error". So I followed the link and manually downloaded the glibc file.
Also to clarify, you instructed to mount sda1...that is the efi fat32 partition, didn't you mean sda2 to mount and chroot into the rootfs?
I ran the commands mounting /dev/sda2 to /mnt/sda2 the rootfs file system.
But upon running the rpm command to upgrade glibc, I received a failed dependency error.
I chrooted into the sda2 rootfs and ran the wget command again to get the glibc update, and it also failed due to certificate not rusted error.
Something additional I tried...since I was successful at installing, I attempted to update only the glibc initially, and then thinking of rebooting and complete a full update...but alas, after a successful glibc update, the computer would only boot to black screen.
So...I can install successfully and run openmamba, I just can't update the system.
Douglas
