00:01 <oicapetainbfian> Hello.

00:02 <oicapetainbfian> Bye. :-D

00:05 <farkuhar> fishe: i feel your frustration. even when it succeeds, a qtwebengine build can take many hours. it almost brings you back to the days of programming with punch cards, where you submitted a job and then came back the next day to learn whether your code was error-free.

00:09 <farkuhar> after beerman wrote on 2022-06-24 that qtwebengine (5) is a hackfest and "should be dropped as fast as possible", i haven't tried building it again.

00:51 <fishe> if firefox had a competent way to do things via keyboard i wouldn't be using qtwebengine lol

00:51 <fishe> it's slower and less secure

01:47 <farkuhar> fishe: i've been using nyxt as my primary browser for several months now, after getting annoyed at the hackfest that is qtwebengine. navigating by keyboard is just as configurable in nyxt as it was in qutebrowser.

01:48 <fishe> i haven't actually heard of nyxt, gonna check that out!

08:28 <cruxbot> [opt.git/3.6]: poppler-qt5: update to 22.08.0

08:28 <cruxbot> [opt.git/3.6]: poppler-glib: update to 22.08.0

08:28 <cruxbot> [opt.git/3.6]: poppler: update to 22.08.0

08:28 <cruxbot> [opt.git/3.6]: libunbound: update to 1.16.2

08:28 <cruxbot> [opt.git/3.6]: unbound: update to 1.16.2

14:49 <cruxbot> [contrib.git/3.6]: pam_xdg: v0.8.1 (update to XDG standard 0.8)

15:34 <mnkydeth> I had some time yesterday. So I wanted to test out the rc2 iso. I thought the install went fine per the usual stuff that I do. But upon reboot it gave me the grub prompt. So I figured it didn't install correctly. I went back in and re-ran the grub-install /boot/efi as that is my fat32 efi partition.

15:35 <mnkydeth> But after doing the grub re-install... I got the error: file '/boot/grub/x86_64-efi/terminal.mod' not found. Entering rescue mode.

15:36 <mnkydeth> I guess I'm not sure what has changed. That I'm not aware of. I went back and read some irc logs. But there is a lot there and havn't come across anything specific yet on it.

15:47 <SiFuh> mnkydeth: https://www.linuxquestions.org/questions/linux-newbie-8/grub-error-boot-grub-x86_64-efi-normal-mod-not-found-after-installing-ubuntu-4175628454/ maybe this?

15:48 <SiFuh> I am not a grub user, best to wait for a grub guy to reply though

15:56 <mnkydeth> Well, I am using UEFI not MBR. I believe it's something like this.

15:57 <mnkydeth> I know there is the new lines in the fstab file. I figured those as default would be sufficient however, just uncommented.

15:57 <SiFuh> They were added a few days back

15:59 <mnkydeth> I've never used syslinux so I have no idea how that works and what I need to do to use that. I've never read on it at all. My past grub setups have worked fine. I still use jaegers old grub.cfg as an example for myself.

15:59 <mnkydeth> http://ix.io/1f4y

15:59 <mnkydeth> obviously changing whats needed for my system. But that file to the most part has always worked for me.

16:01 <SiFuh> https://gitlab.com/SiFuh/Documentation/-/blob/master/SYSLINUX-Cheat_Sheet.pdf

16:02 <SiFuh> https://gitlab.com/SiFuh/Documentation/-/blob/master/CRUX-Syslinux.pdf

16:02 <cruxbot> [opt.git/3.6]: mpg123: update to 1.30.2

16:02 <cruxbot> [opt.git/3.6]: nano: update to 6.4

16:02 <cruxbot> [opt.git/3.6]: harfbuzz: update to 5.1.0

16:02 <SiFuh> There are lots of ways to do it with SYSLINUX, the cheat sheet is probably the better way though

16:04 <SiFuh> You could even use efibootmgr and with no configuration files at all if your UEFI system allows it.

16:09 <mnkydeth> Yeah, I'm reading up on the error I am having a bit more. And looking at the syslinux stuff as well. I think I'm just missing something with my grub. But I'm ok to learn other ways as well. I don't usually use an initrd with my kernels. I try to build as much as I can with * instead of M. So I can cut out a lot of what I'll never use. But I use the kernel automounter because of this.

16:09 <SiFuh> mnkydeth: For my system, I used the right column GPT (GUID) and the row UEFI.

16:10 <mnkydeth> Yeah, thats what I would use as well from what it looks like. I use GPT and UEFI.

16:10 <SiFuh> Side note. If you do go with SYSLINUX and you do not have any INITRD then that line cannot be empty. Just end your config with the APPEND line

16:16 <SiFuh> mnkydeth: Oh you use intel-ucode so that would be on the intrid line

16:20 <mnkydeth> I don't usually set any ucode either. Sorry, that grub.cfg was just an example jaeger showed me a long while ago.

16:24 <mnkydeth> Prolly won't help, but I recently did a rebuild on my system. And I can't seem to get the higher resolution on the installation media. Kind of a pain but it's still workable.

16:26 <SiFuh> https://dpaste.com/DZSBVKAEV.txt <-- I converted that grub to syslinux.cfg I didn't add the Windows stuff because I don't know anything about that. I think chain loading is not supported.

16:27 <SiFuh> If not using the intel-ucode then you must remove the entire entry 'INITRD intel-ucode.img' do not leave INITRD with nothing after it.

16:28 <SiFuh> And I forgot to add the word single at the end of the second APPEND line

16:31 <SiFuh> If you doit the way I do it. You won't even need to touch the UEFI menu entry. You won't to write anything to mbr. Just make sure you use the /boot/efi/boot location, and edit only the config. After you change the config you don't have to do anything.

16:32 <SiFuh> If you install a new kernel. Copy it to /boot/efi/boot add a new entry or edit an old entry in the syslinux.cfg file and your done.

16:34 <SiFuh> What I like is that I don't have to run any special command like lilo or grub-installer (Or whatever it is called). If you never touch your /boot directory your system will still boot, might be missing some modules though if you formated root though

16:38 <mnkydeth> interesting, I'll be giving the rc2 iso an install here in a bit again. Just had to get the kids settled before I do another attempt.

16:39 <SiFuh> This resolution you are tlaking about. Is it that the words are too small?

16:40 <SiFuh> Like you are using a 4K screen or something

16:42 <mnkydeth> To big... My old motherboard was a MSI x570 Prestige Creation. If I hit F9 during the bios load screen, like when you hit the del key to enter the bios I could select UEFI boot on the crux media. And it would be a nice high resolution, small text. I use a 1440p 32" screen. This new board is the Asus x570 Crosshair 8 Extreme. And I can only boot from usb devices if my drive is wiped or I select the boot

16:42 <mnkydeth> device from within the bios itself. And it doesn't give me the smaller text.

16:43 <mnkydeth> Once an OS is installed it's fine however.

16:45 <mnkydeth> switching clients

16:48 <SiFuh> I was wondering mnkydeth if you partitioned the disk as GPT or accidentally partitioned it as MBR.

16:50 <mnkydeth> I use cfdisk as my partition tool of choice. Always set to GPT.

16:54 <mnkydeth> Just going through the bios now. Gonna disable fast boot. Seems there are a few options in here that may effect how the media is booted.

16:54 <mnkydeth> That I wasn't aware of.

16:55 <SiFuh> My BIOS has secure boot enabled, and it doesn't do anything ;-)

16:55 <SiFuh> The one on the laptops secure boot works fine.

16:57 <mnkydeth> I have secure boot disabled, CSM compatibility was disabled, I am going to enable that and force everything to UEFI manually. Fast Boot was enabled, it's now disabled. The AMD fTPM is now disabled.

16:57 <SiFuh> Enabling secureboot will require you to hash the loader

16:58 <mnkydeth> I wiped all keys that were there. And secure boot is disabled.

16:59 <SiFuh> There are two files PreLoader.efi and HashTool.efi that are used for creating hashes but that is another topic for another time

17:00 <SiFuh> It is not part of CRUX that I know of

17:00 <mnkydeth> Yeah, I'm not really concerned about the boot. I'm just trying this to see if I can get the higher resolutions from the boot media.

17:00 <mnkydeth> It's prolly something with the bios I'm thinking as well.

18:47 <mnkydeth> well, I'm not exactly for sure what changed. But, to give an idea. I first ran grub-mkconfig to generate a grub.cfg file. It didn't work in it's default state. So I modified it. Got the system to boot however without graphics mode in the terminal so all I had was a blank screen. I tried several things and nothing worked. So...

18:49 <mnkydeth> I went back, wiped the grub.cfg loaded up my normal grub.cfg and it worked this time for some reason. However, I get one error on boot that says .... /sys/firmware/efi/efivars mount point does not exist. So, I will go back in and double check to see if the directory is there. If not I'll remove it from fstab to see if I get all the way to the command line.

18:51 <mnkydeth> hmm... the directory is there....

18:53 <mnkydeth> yep, just commenting out the efivars line in the fstab worked. Finally made it to the command line.

18:59 <SiFuh_> Cool, yeah that efivars is something else someone else requested

18:59 <SiFuh_> Actually I think jaeger added that

19:00 <SiFuh_> The /boot is what was requested for EFI

19:02 <mnkydeth> Yeah, I'm looking over what I did. Because I thought I did this the first time around and it failed. So I moved on trying other stuff. But in the end I did a last ditch effort with my original grub file. And put the fstab to my normal default stuff and everything worked.

19:03 <SiFuh_> I haven't seen the new entries or your modified entries so I am not sure

19:04 <mnkydeth> Honestly, if it didn't work I was going to start the syslinux stuff. Honestly, I should prolly try using that as well so I have two options for booting if I ever run into a scenario I can't get to work with grub.

19:07 <mnkydeth> Yeah, it's a lot like that link I posted earlier. Not exact but really close. I can't get the files pasted online at the moment.

19:11 <jaeger> So you got grub figured out now?

19:11 <jaeger> There was a typo introduced by me (oops) on the efivars line in fstab, correcting it should help that part

19:14 <mnkydeth> I commented out the efivars line in fstab. And I was able to get to command line.

19:14 <jaeger> That's unrelated to grub, but also a problem, yeah

19:15 <jaeger> The corrected line looks like this:

19:15 <jaeger> efivars /sys/firmware/efi/efivars efivarfs defaults 0 0

19:15 <mnkydeth> I do have efivars in my directories. But I don't put them on their own partition or anything. I have them part of /

19:15 <jaeger> It's a special filesystem created by the kernel, not something user-managed

19:16 <jaeger> The fstab line is just mounting it so tools like efibootmgr work properly

19:16 <mnkydeth> Ahh I see

19:22 <SiFuh_> The efivarfs filesystem was created to address the shortcomings of using entries in sysfs to maintain EFI variables. The old sysfs EFI variables code only supported variables of up to 1024 bytes.

19:23 <SiFuh_> Since variables can now be larger than a single page, sysfs isn’t the best interface for this.

19:50 <farkuhar> mnkydeth, the bios can definitely interfere with what looks like perfectly reasonable settings reported by efibootmgr. My laptop bios absolutely refuses to honor the custom settings I make with efibootmgr, and I have to rename the desired bootloader (even a Linux kernel with EFI stub enabled) as BOOTX64.EFI in order for it to be recognized.

19:50 <jaeger> farkuhar: out of curiosity, what laptop model is that?

19:51 <farkuhar> it's an HP

19:51 <jaeger> how old?

19:51 <farkuhar> 2017, i believe

19:52 <jaeger> OK. Just curious. I think most manufacturers were doing sane-ish things with EFI by 2017 but HP always does their own thing, heh

19:52 <jaeger> I had a bunch of elitebook laptops at my last job that were a pain with EFI vars too

19:55 <jaeger> 8530p, 8540p, and 720 G1/G2 models if I remember right

19:56 <jaeger> I wonder if their latest Dev One or whatever it is does it right

20:00 <jaeger> Anyone in here buy a framework laptop yet? Also very curious about those but my cheap xiaomi laptop still works great, haven't felt the need to replace it :)

20:07 <farkuhar> grub is more idiot-proof than syslinux with eccentric motherboards, thanks to the --removable flag in grub-install. That flag tells grub to use a generic name when saving the bootloader in the EFI system partition, so that the bios will find it even if no changes were made with efibootmgr.

20:40 <mnkydeth> Well, that's good to know. I do know this Asus board has a few more options then my msi board did. And as I was flipping those settings on and off I may have left it in a better config for grub then what I had. I'd have to go back and test each individual one to see if I had a failed boot on a specific setting.

20:40 <mnkydeth> The reason my normal grub.cfg I typically use didn't seem to work in the first place.

22:39 <fishe> nyxt build wanted harfbuzz recompiled with icu installed

22:39 <fishe> did it an when i recompile harfbuzz i now get this footprint mismatch

22:40 <fishe> https://www.irccloud.com/pastebin/XohzQmtw

22:41 <fishe> as well as a few new files from icu which im too lazy to type out (xorg crashed because now harfbuzz is missing)

23:16 <cruxbot> [contrib.git/3.6]: go: updated to version 1.19

23:36 <farkuhar> fishe, you might try first rebuilding freetype with "-D harfbuzz=disabled", and then rebuilding harfbuzz. See here for an earlier report of this phenomenon: https://lists.crux.nu/pipermail/crux/2022-June/007203.html

23:54 <fishe> that worked, many thanks!