00:33 <chrcav> Not personally a wayland user but I was pretty sure xwayland should be enabled by default on sway. Did you explicitly disable xwayland in your sway config?

00:48 <mnkydeth> I didn't disable it. I did make sure to put xwayland enable in the .config/sway/config

00:49 <mnkydeth> I just tried greetd and tuigreet. But no luck there either.

00:51 <mnkydeth> I may try modifying my start script a bit. I found TimB87 crux-wayland startup script. He has a little different config then what I used.

00:52 <mnkydeth> I mostly used the oper.io example as my base for crux. switching from x11 to native-wayland.

00:54 <mnkydeth> Not much time left for me tonight to play. So, I'll try a few things over the next couple days. Just figured I would put out a line to see what people typically do here that run wayland. config files or logins etc.

00:57 <farkuhar> mnkydeth: if you compiled sway while xorg-xwayland was not present, then sway would have been configured with no xwayland support. Try rebuilding sway now that you have xorg-xwayland installed.

01:01 <farkuhar> it sounds from your description "finally decided to try steam" that maybe you added the xorg ports after setting up a pure wayland desktop. If that's the case, rebuild sway and see if the pkgmk log shows that xwayland was detected.

03:27 <chrcav> SiFuh: turns out I was missing CONFIG_EFI_STUB=y in my kernel config. Once I added that syslinux started working.

04:29 <jaeger> interesting, I didn't think stub was required for syslinux

04:30 <jaeger> Usually stub support means the kernel itself is the UEFI bootloader

04:49 <jaeger> mnkydeth: sway needs to be recompiled after xwayland is installed, if you haven't done that already

05:48 <SiFuh> jaeger: in the pdf I wrote for syslinux I had CONFIG_EFI_STUB=y as well

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

06:22 <jaeger> Hrmm, very interesting... something to test more for me later

06:41 <ppetrov^> hey guys, in openjdk17-jdk, this is not reachable: https://crux.ster.zone/downloads/java/

11:30 <cruxbot> [opt.git/3.7]: php: update to 8.1.13

11:30 <cruxbot> [core.git/3.7]: tzdata: update to 2022g

11:44 <cruxbot> [core.git/3.7]: vim: update to 9.0.0979

11:44 <cruxbot> [core.git/3.7]: xz: update to 5.2.9

11:44 <cruxbot> [core.git/3.7]: cmake: update to 3.25.1

12:04 <cruxbot> [opt.git/3.7]: gvim: update to 9.0.0979

12:12 <farkuhar> stenur: for me it's the opposite, the libera irclogs page looks total bozo in a webkitgtk browser (nyxt with zoom-ratio 1.25), but fine in firefox-bin.

12:29 <SiFuh> Thanks chrcav_. jaeger I will query and verify in #syslinux about this.

12:29 <SiFuh> I am finding a lot of references to it, but none explaining why or if it is needed

12:30 <SiFuh> farkuhar: I will keep you posted on this as well, if it is as chrcav_ says it might need to be specified in the documentation.

13:07 <farkuhar> SiFuh: thanks. I'm now seeing in the Slackware syslinux docs a few comments that I don't remember being there earlier. Especially the four bullet points after "Frankly, there are no compelling reasons not to use CSM ... On the contrary, there are reasons to avoid UEFI booting, because ..."

13:07 <farkuhar> https://docs.slackware.com/howtos:slackware_admin:set_up_syslinux_as_boot_loader_on_uefi_based_hardware

13:13 <farkuhar> which makes me wonder whether chrcav_'s original kernel might have booted just fine, if CSM or Legacy mode were enabled.

13:42 <SiFuh> farkuhar: I saw the slackware documents but as I mentioned above, I am not finding any actual real information regarding it

13:43 <SiFuh> I can guarantee that it would boot in Legacy.

13:44 <SiFuh> Yeah, I read that URL today probably 10 minutes before I mentioned not being able to find real info

13:46 <SiFuh> farkuhar: No reply from #syslinux yet, but the one I did find curious is this https://www.bkhome.org/news/201411/booting-qu-on-uefi-machine.html Paragraph 2

13:48 <SiFuh> http://www.rodsbooks.com/efi-bootloaders/efistub.html <-- farkuhar jaeger

13:48 <SiFuh> "In practice, the EFI stub loader is generally used with a separate boot manager program—most commonly rEFInd or gummiboot/systemd-boot, but GRUB 2 can be used this way, too."

13:57 <SiFuh> Maybe SYSLINUX is booting the kernel directly through UEFI stub?

13:58 <SiFuh> UEFI and stub* like a man in the middle

14:00 <chrcav_> That might be what's happenning. I ended up switch from GRUB2 to SYSLINUX on two systems and enabling EFI stub was the only change I needed to get running.

14:01 <SiFuh> chrcav_: Yeah, that is cool. I reckon you found the issue

14:06 <SiFuh> chrcav_: All my systems have had EFI STUB enabled and I even wrote that it is to be enabled in my original documentation a couple of years ago. I never really looked into what STUB was until later. I had the same idea as jaeger that it was only used from UEFI to Kernel.

14:07 <chrcav> I mean that's what the kernel doc says about it.

14:07 <SiFuh> Yeah, so hopefully the SYLINUX guys can clear that up. Either way, whether they confirm or not, we may need to make a note of this for future installations in the CRUX handbook

14:08 <SiFuh> I'd prefer actual confirmation though.

14:09 <SiFuh> I may end up examing the source instead to find the answer.

14:57 <cruxbot> [opt.git/3.7]: glib: update to 2.74.3

15:46 <jaeger> I generally don't have stub support in my kernels except for when I tested booting a kernel directly with it for the documentation ages ago

15:50 <SiFuh> I am pretty sure I picked up the addition of the kernel option from Arch Linux's SYSLINUX documentation.

15:51 <SiFuh> To be honest. SYSLINUX was such a pain in the arse to get around because there was so much trash documentation out there and limited explanations as well.

15:51 <SiFuh> This is the reason I decided to write the cheat sheet and the basic documentation for myself. Mostly in layman's terms

18:33 <stenur> For EFI_STUB to make sense the kernel must be on the EFI partition, right. Otherwise you need something to chain-load. I use a static kernel on EFI to chain load another one via kexec-tools on an encrypted partition.

18:34 <SiFuh> Yes, but this isn't what we are talking about.

18:35 <SiFuh> Basically, we are told that EFI_STUB is to load the kernel directly without a bootloader. However, it appears that in UEFI boot with SYSLINUX we may actually need EFI_STUB enabled in the kernel or it will not boot.

18:36 <stenur> hard to believe actually.

18:37 <SiFuh> Yeah, and the SYSLINUX guys haven't replied either.

18:40 <SiFuh> All the howtos and documentation I have read that mention kernel configuration options are all saying to enable it, but none explain why.