00:23 <thikkl> sad_plan: I got it working! (ish, I can see console output, but its a bit janky and it's having a problem mounting root). Turns out I hadn't enabled FRAMEBUFFER_CONSOLE. Thanks for all the help though!

00:26 <sad_plan> sweet!

00:40 <thikkl> Is there a way to prevent the EFI boot entry from being deleted when I remove my drive? (Yes, I installed KISS on a removable drive lol. Didn't want to mess around with dual boot)

01:26 <thikkl> Ok, I found that there's a --removable option for GRUB... but I didn't find anything for EFI Stub

01:42 <wannabekissuser> Hello everyone. I have been trying to install KISS Linux (GKISS in particular) on my machine, but have encountered several problems. I followed the instruction from KISS website, GKISS repo and kiss-xorg repo as well. I managed to finish the installation process quite successfully (that's what I thought at that moment, I didn't encounter any

01:42 <wannabekissuser> serious problem), I installed xorg and nvidia, but after trying to reboot to actual system I got stuck on motherboard logo, just without the cheatsheet like hotkeys for entering the boot menu and stuff, they're typically below it. I figured I didn't install nvidia correctly, I tried to repeat all the process again but without using kiss-xorg

01:42 <wannabekissuser> repository, which is a strange decision. That's the exact point where I am stuck now. Nvidia package doesn't build because of multiple errors, if I recall correctly they were connected with egl.h not being found. So instead of trying things blindly I figured I would try asking on reddit, then I was redirected here. So the question is, does anyone

01:42 <wannabekissuser> have advice on how to install this kind of configuration, meaning xorg + nvidia (with gkiss of course). In what order the repos should be placed? A person on reddit suggested that I also provide nvidia building log and kernel config, but I no longer have that exact "installation" on my machine (started anew), though I can replicate this error of

01:42 <wannabekissuser> course but I hoped I could avoid the hassle. Also my kernel config is mostly default, I remember checking (and enabling if disabled) settings for NVMe, ext4 and EFI support, I think that's all. If it is still necessary to provide it I would, just tell me where to upload it, not really sure.

02:29 <ehawkvu> wannabekissuser: sewn: I'm pretty sure that you need a custom nvidia package (sewn used to maintain it in kiss-xorg, but dropped it after leaving)

02:30 <ehawkvu> There are a few issues on kiss-xorg detailing how to have a nvidia setup (which maybe we ought to document on the wiki....)

02:59 <thikkl> is /etc/fstab necessary for kiss to boot properly?

03:01 <thikkl> The install guide doesn't mention anything about it, but both times I've had kiss successfully boot I had created one

03:02 <thikkl> (just out of curiosity)

04:07 <sewn> thikkl: no

04:14 <thikkl> interesting

04:16 <thikkl> I assumed it was necessary since the linux from scratch book lists it as one of the steps in "making the system bootable"

04:55 <sad_plan> wym no sewn? having a correctly set up fstab is neccessary to properly boot the system. otherwise it wont find all partitions, unless specified in init perhaps..

07:45 <sewn> sad_plan: you already set root in kernel params

07:45 <sewn> fstab is just there for remounting root ataik

07:55 <sad_plan> yes, but that wont mount /home, or /boot (if you want)

07:55 <sad_plan> no, init scripts remounts /root as ro, then rw, if setup this way ofcourse

07:55 <sad_plan> kiss does this atleast. mine didnt, but now it does, because im running fsck on boot each time

07:59 <sad_plan> fstab will also set permissions. kernel doesnt neccessarly do this the way you want.

08:00 <sad_plan> but by all means, yes you can set root= in kernel params, and manually mount everything yourself when booting. its in no way shape or form convinient though

11:17 <phoebos> wannabekissuser: it sounds like you haven't even got your bootloader running, what are you using, grub? efistub?

16:09 <wannabekissuser> phoebos: I am using efistub, but that should probably not be the case, I used it with crux previously, and had almost the same experience, think I couldn't mess it up. It's more probable that I built nvidia, but somehow didn't enable module, so the driver wasn't even loaded