Theory Waste your time effectively with linux

[svgmn1]

odd should pick it up, though i'm pretty lazy with my linux systems I always just install grub and all its efi files directly into /boot/, makes /boot/ a bit messy but its never bothered me, did the same when I used to daily drive arch for half a decade before moving to gentoo, if you need any other help or can't get it working just hmu, i'll typically respond decently fast

Thanks brocel
reinstalling grub with that line then mkconfig did make the vmm bios detect grub

however for some reason boot process still gets stuck at run /init as init process, even after reinstall of initramfs.

Selinux is excluded from being the culprit, I made sure that all semodules/options are chosen using --menuconfig so the kernel have them, as well as installing userland selinux utils.

I double and triple checked that everything points at the right location/path of everything.

maybe genkernel is the culprit and can't make an initramfs for this specific profile, idk, I will try dracut or something to install initramfs seperately.

 

[zd60]

Thanks brocel
reinstalling grub with that line then mkconfig did make the vmm bios detect grub

however for some reason boot process still gets stuck at run /init as init process, even after reinstall of initramfs.

Selinux is excluded from being the culprit, I made sure that all semodules/options are chosen using --menuconfig so the kernel have them, as well as installing userland selinux utils.

I double and triple checked that everything points at the right location/path of everything.

maybe genkernel is the culprit and can't make an initramfs for this specific profile, idk, I will try dracut or something to install initramfs seperately.

you can try generating just a initramfs directly with genkernel to see if that changes anything

 

[svgmn1]

you can try generating just a initramfs directly with genkernel to see if that changes anything

yes, I did try it in the optimal way forcing a clean install with all ramdisk modules like this

genkernel --install --no-clean --no-mrproper --loglevel=5 --log=/var/log/genkernel.log --all-ramdisk-modules initramfs

no error or anything suspecious happens, however I am getting a clue why this happnes

when I generated initramfs by genkernel, returned an xz archive for the image using file /boot/initramfs.img

HOWEVER now after installing with dracut then ran file /boot/initramfs.img it returned an ascII cpio archive, hmmmm


so right now I'm experimenting with dracut and staying away from genkernel to see if this difference does anything

 

[zd60]

yes, I did try it in the optimal way forcing a clean install with all ramdisk modules like this

genkernel --install --no-clean --no-mrproper --loglevel=5 --log=/var/log/genkernel.log --all-ramdisk-modules initramfs

no error or anything suspecious happens, however I am getting a clue why this happnes

when I generated initramfs with dracut and copied the initramfs then ran file /initramfs it returned an ascII cpio archive, while the initramfs generated by genkernel, returned an xz archive for the image. so right now I'm experimenting with dracut and staying away from genkernel to see if this difference does anything

yes, I did try it in the optimal way forcing a clean install with all ramdisk modules like this

genkernel --install --no-clean --no-mrproper --loglevel=5 --log=/var/log/genkernel.log --all-ramdisk-modules initramfs

no error or anything suspecious happens, however I am getting a clue why this happnes

when I generated initramfs with dracut and copied the initramfs then ran file /initramfs it returned an ascII cpio archive, while the initramfs generated by genkernel, returned an xz archive for the image. so right now I'm experimenting with dracut and staying away from genkernel to see if this difference does anything

hmm, that's one of the quirks about gentoo is that it can be installed so many different ways, I don't ever typically do much with genkernel besides making my initramfs, you might benefit from specifically pointing to your kernel config in the /usr/src/linux/.config in you genkernel command, is your fstab setup to point to drives via their UUID or their drive name like /dev/sdX ? its probably worth setting up your fstab to use drives by UUID since they don't change and typically cause less booting issues too long-term

 

[svgmn1]

hmm, that's one of the quirks about gentoo is that it can be installed so many different ways, I don't ever typically do much with genkernel besides making my initramfs, you might benefit from specifically pointing to your kernel config in the /usr/src/linux/.config in you genkernel command, is your fstab setup to point to drives via their UUID or their drive name like /dev/sdX ?

I pointed towards both root and efi in fstab using UUIDs of the partitions which I grabbed from lsblk -f instead of using regular paths, you can find full fstab info in the config.txt file I sent earlier

I didn't use a config or messed anything with menuconfig, I used genkernel all which should in theory automatically cover up everything (right?)

 

[zd60]

I pointed towards both root and efi in fstab using UUIDs of the partitions which I grabbed from lsblk -f instead of using regular paths, you can find full fstab info in the config.txt file I sent earlier

I didn't use a config or messed anything with menuconfig, I used genkernel all which should in theory automatically cover up everything (right?)

I've tried parsing through a bit of the files it seems like your fstab is a little weird for the /boot/ you seem to have noatime on the /boot/ which isn't something typical at least not for me my fstab is setup for /boot/ like this


/boot/ vfat defaults 0 2

you can modifiy it to be /boot/efi, i'd then probably regenerate your grub.cfg

 

[zd60]

@svgmn1 also maybe I missed it but is there a specific reason for you to use the --no-nvram flag in yoru grub-install you don't typically need it for a desktop install or in a vm

 

[svgmn1]

I've tried parsing through a bit of the files it seems like your fstab is a little weird for the /boot/ you seem to have noatime on the /boot/ which isn't something typical at least not for me my fstab is setup for /boot/ like this


/boot/ vfat defaults 0 2

you can modifiy it to be /boot/efi, i'd then probably regenerate your grub.cfg

yes cando and will, noatime was just put there because I read it improves fs performance

will change efi path as well then regenerate grub.cfg

@svgmn1 also maybe I missed it but is there a specific reason for you to use the --no-nvram flag in yoru grub-install you don't typically need it for a desktop install or in a vm

I reintalled and reconfigured grub at this point without this flag already, I think back then it was just to test or something idk so I wrote it and forgot

 

[nazianime]

I use Linux as my personal desktop and it’s good, a few headaches but I don’t run windows games so ehh. I’ll just pirate games on older consoles and run those instead. Microsoft has become such hot garbage that the pain of using Linux > using windows.

I still use windows 11 for work because professional applications I have to use but that’s it though. Just right now I tried to use quick assist to help a colleague and that shit won’t open, on the most vanilla install with all the updates, literally broke itself. That’s how much trash microshit has become. But seriously fuck pajeetsoft, adobe pajeet, and google jeet, all ran by Indian ceos to the ground.

 

[svgmn1]

/boot/ vfat defaults 0 2

you can modifiy it to be /boot/efi, i'd then probably regenerate your grub.cfg

this is weird as hell
after installing with dracut then doing these, now the system boot stuck at "cdrom: uniform cd-rom driver revision: 3.28" for like minutes then it shows these warnings "dracut warning: /dev/disk/by-uuid/4a57c1a8-388b-42e7-a689-e859ea4c7dea does not exist dracut warning: /dev/disk/by-uuid/F0E6-FDD2 does not exist "
I double-checked the uuids saved from lsblk -f, they are THE EXACT SAME UUIDS, down to each character

idk what to try anymore tbh since uuid pointing should be exact and bullet proof in theory

 

[svgmn1]

this is weird as hell
after installing with dracut then doing these, now the system boot stuck at "cdrom: uniform cd-rom driver revision: 3.28" for like minutes then it shows these warnings "dracut warning: /dev/disk/by-uuid/4a57c1a8-388b-42e7-a689-e859ea4c7dea does not exist dracut warning: /dev/disk/by-uuid/F0E6-FDD2 does not exist "
I double-checked the uuids saved from lsblk -f, they are THE EXACT SAME UUIDS, down to each character

idk what to try anymore tbh since uuid pointing should be exact and bullet proof in theory

I'll take a rest today already spent too much time on checking stuff

 

[zd60]

I'll take a rest today already spent too much time on checking stuff

I might've overlooked it in your files that you sent but did you install the sys-kernel/linux-firmware package and I didn't see this in your make.conf but if yoru on efi you typically need to add this to your make.conf
GRUB_PLATFORMS="efi-64"

 

[svgmn1]

I might've overlooked it in your files that you sent but did you install the sys-kernel/linux-firmware package and I didn't see this in your make.conf but if yoru on efi you typically need to add this to your make.conf
GRUB_PLATFORMS="efi-64"

will check and do if necessary, tomorrow
thanks for the help so far bud

 

[zd60]

will check and do if necessary, tomorrow
thanks for the help so far bud

sounds good just hmu whenever

 

[svgmn1]

sounds good just hmu whenever

Fuck yeah brother it did boot

turns out the only thing that was missing is running touch /.autorelabel
rookie mistake for such a manual distro, but Idk if that was the only thing missing for dracut kernel to detect and load my disk? because I reinstalled with dracut, then force installed intramfs with dracut then installed the linux-firmware as you reminded me.

I got another problem right now after boot since I want a DE, turns out it's a hassle even for a small DE like lxqt/lxd
and setting selinux labels is failing when I try to install anything.
turns out file_contexts is missing in etc/selinux/mcs/file, tried to install sec-policy/selinux-base to fix that but it fails. so right now it can't install anything because "unable to set selinux security labels!" keeps appearing when emerging anything.

seems like another rabbit hole for me to dig in

 

[zd60]

Fuck yeah brother it did boot

turns out the only thing that was missing is running touch /.autorelabel
rookie mistake for such a manual distro, but Idk if that was the only thing missing for dracut kernel to detect and load my disk? because I reinstalled with dracut, then force installed intramfs with dracut then installed the linux-firmware as you reminded me.

I got another problem right now after boot since I want a DE, turns out it's a hassle even for a small DE like lxqt/lxd
and setting selinux labels is failing when I try to install anything.
turns out file_contexts is missing in etc/selinux/mcs/file, tried to install sec-policy/selinux-base to fix that but it fails. so right now it can't install anything because "unable to set selinux security labels!" keeps appearing when emerging anything.

seems like another rabbit hole for me to dig in

The setting labels issue sounds like I've something I've read about on the wiki for selinux on gentoo

might want to read over here again just to make sure you got everything configured correctly
https://wiki.gentoo.org/wiki/SELinux/Installation,

if its your first install of sec-policy/selinux-base I think it requires to be emerge with -selinux feature disabled at first I could be wrong been a little bit since I've set it up

 

[svgmn1]

The setting labels issue sounds like I've something I've read about on the wiki for selinux on gentoo

might want to read over here again just to make sure you got everything configured correctly
https://wiki.gentoo.org/wiki/SELinux/Installation,

if its your first install of sec-policy/selinux-base I think it requires to be emerge with -selinux feature disabled at first I could be wrong been a little bit since I've set it up

Yes, which is exactly what I did
FEATURE ="-selinux" + emerge, however it gave me some sort of error with a log, mostly about lines in python scripts which seems ambiguous at best.
gotta boot my laptop, test again and do some searching first.

 

[zd60]

Yes, which is exactly what I did
FEATURE ="-selinux" + emerge, however it gave me some sort of error with a log, mostly about lines in python scripts which seems ambiguous at best.
gotta boot my laptop, test again and do some searching first.

did the package fully compile or did it fail, do you have that log file?

 

[svgmn1]

did the package fully compile or did it fail, do you have that log file?

No it failed, here's the log file: (skip to L 1164 for the failures)

it is strange because in the wiki guide it just mentions installing the kernel first then using this line to install the sec-policy/selinux-base and optional use flags
so I don't even know what I'm missing tbh

 

[zd60]

No it failed, here's the log file: (skip to L 1164 for the failures)

it is strange because in the wiki guide it just mentions installing the kernel first then using this line to install the sec-policy/selinux-base and optional use flags
so I don't even know what I'm missing tbh

Oh wow there's a lot of file collisions in there, honestly if you're comfortable with it might be worth just restarting the whole install from the start instead jumping from one problem to another might be faster, seems like something might've went wrong during the install possibly

 

[svgmn1]

No it failed, here's the log file: (skip to L 1164 for the failures)

it is strange because in the wiki guide it just mentions installing the kernel first then using this line to install the sec-policy/selinux-base and optional use flags
so I don't even know what I'm missing tbh

I think im getting close to solve this
even though sestatus is set 0 right now I may need to disable selinux temporarily using grub menuentry
but then this would render my fs read only for some reason
what I dislike about gentoo is the philosophy but I have to admit it's a super resilient os
all the issues and the bugs you throw at it and your progress won't get fucked over or ever have to start from 0 (so far atleast, which I hope it doesn't change)

 

[svgmn1]

Oh wow there's a lot of file collisions in there, honestly if you're comfortable with it might be worth just restarting the whole install from the start instead jumping from one problem to another might be faster, seems like something might've went wrong during the install possibly

why lol I feel like I can fix anything wrong with it at this point

 

[zd60]

why lol I feel like I can fix anything wrong with it at this point

lol okay, the file collisions are usually easily fixed, if you have the feature collision-protect setup in your make.conf typically just disabling it and re-emerging the package fixes it, also you def can fix pretty much everything from this point on yeah just adds more time before you're up to a fully work system idk how much time someone is willing to dedicate to installing a linux distro most people would've gave up already lol

 

[svgmn1]

lol okay, the file collisions are usually easily fixed, if you have the feature collision-protect setup in your make.conf typically just disabling it and re-emerging the package fixes it

It's ok brocel I'll figure it out
just need more time and search tbh thanks for the help so far

 

[zd60]

It's ok brocel I'll figure it out
just need more time and search tbh thanks for the help so far

oh I got nothing but time, I don't mind helping still, I just know you might run into something I've not delt with before