[linuxcat]

Silvan,
I was happy that I could help out, if there is anything I can assist you with in the future, don’t hesitate to let me know.

Douglas

[linuxcat]

Silvan,

I’m keeping my finger crossed, but I think I may finally have a working system, thanks to your hard work.
So…I created a new boot stick with the openmamba-diskimage-livecd-en-snapshot-20210912 image and completed the install and update.
It looks like it is running good; I will try things out and let you know.
Thanks again.

Douglas

[linuxcat]

Silvan,

Just to inform you of other things I have done…
My boot stick works just fine and I can complete an install. Upon reboot, I can log in, but just get the spinning wheel.
So I switched to tty2 and ran systemctl stop sddm and then systemctl disable SDDM.
I then, (without rebooting), installed lxdm and ran systemctl start lxdm. The lxdm login came right up and I could log in normally, without rebooting.
I then ran a selective update, I deselected sddm and sddm-kcm and the newer 5-10.47 kernel. Update completed, but upon reboot, (with quiet turned off), the boot process would just stop and never go to login.

So…I’ll try your suggestion above for the new kernel and let you know how it goes.

Douglas

[linuxcat]

Silvan,

I used the openmamba-diskimg-livecd-en-snapshot-20210630.x86_64.img
And I used gnome-disks to restore the image to an 8gb usb stick. It would then boot up efi.
As the attachment shows, boot stops with the line at the bottom, when I removed quiet and splash from the linux load line.
If I remove quiet and add nomodeset, then it boots to a prompt.
(If you remember, I disabled SDDM with the systemctl disable SDDM command).
I have configured and compiled new kernels on other distros…is that an option with openmamba, or is it hardcoded by you?

Douglas

Attachments:

You must be logged in to view attached files.

[linuxcat]

Silvan,
Good day…So I was able to boot normally from my initial install and I ran update, (sudo dnf update), from command line and it completed and installed appropriately.
Upon reboot though, and I had to add nomodeset to the linux loader line, the boot up process would not complete. I would never see the black desktop and mouse pointer, like you mentioned.
Thinking the issue was with SDDM like you mentioned, I switched to tty2 and ran, “systemctl stop SDDM” and then, “systemctl disable SDDM”.
Upon reboot, the boot process completed by going to a login prompt. So it seemed SDDM was failing and stopping the boot process.
I tried running startx from command line and just received the following:
“[KMS} drm report modesetting isn’t supported”
“xinit: unable to connect to X server: Connection refused”.

I assume the modesetting error is from my adding nomodeset to the kernel load line.
Is it possible to use lightdm instead of SDDM?

Douglas

[linuxcat]

Silvan,
Thank you for your continued attention and patience, I will try and implement your suggestions today.

Douglas

[linuxcat]

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

[linuxcat]

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

[linuxcat]

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

[linuxcat]

Silvan,
Thank you for your insight…I will check a few more things in regards to booting the usb and also the image boot.

Douglas

[linuxcat]

Silvan,
Thank you for quick response…
When the usb stick I created booted and I switched to tty2, I could start mc and see that in fact the sym link was created for systemd that you mentioned. I updated using dnf but couldn’t get the desktop to start using startx.

Just to confirm, so that you are aware…I am seeing these issues when booting the usb stick I created. It never does boot to a desktop.
I created my boot stick using dd…I may also try Belana-etcher to see if that makes a difference.

I even downloaded the openmambo image and using gnome-disks, restored the openmamba image to a second drive. Interestingly enough, it created 3 partitions.
Partition #1 19mb hfs+ (EFI_MAC), Partition #2 20mb Fat (EFI), Partition #3 3.7gb Ext4 (openmamba)
Both partition #1 & #2 have the same folders and files; EFI/Boot/bootx64.efi
Partition #3 has a boot folder (grub/initrd.gz/vmlinuz) and a LiveOS folder with the squashfs.img
But my system, (and rEFInd) can’t find either bootx64.efi or grub in either partition #1 or #2
I hope that I haven’t overloaded you with too much info.
Any pointers will be greatly appreciated.

Douglas

[Author]

Posts