03:01 <altacus> I went to start up my x13s in debian today and for whatever reason, linux does not boot. After selecting a kernel, the system just reboots. Tried recopying the dtb, same reboot. I figured I must have done something wrong and so I reinstalled debian. Same, issue, system just reboots. Not sure what could be the issue.

03:02 <steev> secureboot enabled?

03:03 <steev> what are your kernel command line arguments?

03:03 <altacus> after the reinstall, it should just be quiet

03:03 <altacus> recovery mode doesn't boot either.

03:03 <altacus> let me check the secure boot

03:04 <steev> there should be more than just quiet

03:05 <steev> linux /boot/vmlinuz-6.5.1 root=UUID=<myuuid> ro pd_ignore_unused clk_ignore_unused net.ifnames=0 iommu.passthrough=0 iommu.strict=0 ipv6.disable=1 quiet splash

03:05 <steev> is what i have here

03:05 <steev> did you maybe install a debian kernel and its booting that?

03:07 <altacus> so I reformated my existing install and it still just reboots.

03:10 <altacus> Before, I tried all the different kernels that I installed (that at least booted) and they all just rebooted.

03:11 <altacus> It's really odd because the install usb, that I used to install before, successfully, now just creates a system that just reboots. I don't think there were any bios updates, etc.

03:13 <altacus> it's late where I am so I'm off to bed, but if anyone has any clue, please let me know... I will check the logs.

05:12 <jhovold> clover[m]: do you really have a different variant? what does the log say when it starts successfully?

05:13 <jhovold> it should never start unless your chip has an entry in board2.bin

09:55 <danielt> altacus: Were you using DtbLoader.efi to load the DTB? If so "just reboots" is a symptom of DtbLoader being accidentally removed from the boot chain by a grub update.

10:12 <jhovold> clover[m]: kalle forwarded your report to me:

10:12 <jhovold> https://lore.kernel.org/ath11k/ZPhCq32KlaZteCzG@hovoldconsulting.com/T/#t

10:13 <jhovold> short summary: you need to provide a lot more detail, and board-2.bin appears to have nothing to do with this

10:27 <pz[m]> Hey guys, do you know if there is a better patch for x13s Audio?

10:27 <pz[m]> I'm running Armbian for x13s, and had no sound. I applied the following patch - https://github.com/Srinivas-Kandagatla/alsa-ucm-conf

10:27 <pz[m]> Now I have audio, it's just a bit crispy and not uber loud.

10:49 <_[m]1> damn it, so I reinstalled (twice) following clover s instructions mixed with arch linux FDE instructions and twice I just boot into a black screen (as before !!) and this time /boot is outside the LUKS volume now

10:50 <_[m]1> i just put the cryptsetup UUID in grub cmd and put encrypt module in mkinitpcio

10:50 <_[m]1> Jasper what am I missing?

10:50 <_[m]1> I've read that last comment where clover thought it's some displaydriver missing but unsure

10:52 <_[m]1> > Do you think they are missing graphics module in the initrd? I think they are doing FDE

10:52 <_[m]1> I might make the list of commands into an addendum guide, the amount of times I've been doing this lol I feel ready 😉

10:57 <_[m]1> btw I forgot to close the luks volume first time, and it seemingly corrupted the install, couldn't arch-chroot into it afterwards ☹️

11:10 <Jasper[m]> <_[m]1> "i just put the cryptsetup UUID..." <- You are yes

11:11 <Jasper[m]> check the wiki on @clover 's github

11:30 <_[m]1> i am following those instructions, I meant - what am I missing to get luks volume pw on screen 😉

11:32 <Jasper[m]> _[m]1: Are you eholzbach om github?

11:33 <_[m]1> nin0-0

11:33 <Jasper[m]> Hm

11:33 <_[m]1> after dtb load, black screen

11:33 <_[m]1> I installed without luks, worked fine

11:33 <Jasper[m]> _[m]1: https://github.com/ironrobin/archiso-x13s/wiki/Feature-Support#full-disk-encryption did you add these modules to mkinitcpio?

11:34 <_[m]1> also after forgetting to close the luksvolume after install, I got some weird battery critical low boot bug

11:34 <_[m]1> Jasper[m]: waitwhaaaat there's an entry for this 😲

11:34 <_[m]1> here I am juggling 5 tabs to collect what I need lolol

11:35 <_[m]1> WHOA

11:35 <Jasper[m]> _[m]1: The problem is only generic in the sense that you need some panel and gpu driver enabled in initramfs

11:35 <_[m]1> that's probably exactly what I need thanks man 😲

11:35 <Jasper[m]> So specifically for the x13s it's those

11:35 <_[m]1> how the hell does anyone figure out which modules to put huh

11:39 <jhovold> _[m]1: i've tracked down all the dependencies and documented in johan_defconfig:

11:39 <jhovold> https://github.com/jhovold/linux/commit/669b07f9f94caf1c6235bfa74ed29f80f2b8cc36

11:40 <jhovold> The display deps are mostly needed for people like you that need a prompt for encryption

11:40 <_[m]1> does it require your level of knowledge / experience? or I could've done this?

11:40 <_[m]1> I thought at least in debian, you can fallback to text-mode prompt?

11:41 <_[m]1> weird

11:41 <jhovold> it took me a while to figure out too...

11:41 <jhovold> there's a general problem in the kernel which ends up disabling the display regulators after 30s

11:42 <jhovold> at some point we'll have generic solution to that, so that booting with just the efi framebuffer works (for more than 30 s)

11:42 <_[m]1> dude thank you so much (and damn it so my FDE with /boot included would probably have worked too)

11:42 <_[m]1> now ok attack vectors are low

11:42 <_[m]1> s/low/small/

11:42 <_[m]1> s/low/small (I think)/

11:43 <_[m]1> jhovold: it's 30sec from power on?

11:43 <Jasper[m]> _[m]1: Nah, UEFI cannot unlock LUKS

11:43 <jhovold> _[m]1: from when the kernel starts, so after grub

11:43 <_[m]1> luks1 yes

11:43 <_[m]1> I converted my luks2 to luks1 for this etc etc

11:44 <_[m]1> jhovold: I get instant black screen though

11:44 <jhovold> _[m]1: yeah, that may happen if you provide some, but not all deps so that the display driver probes and discards the content of the screen

12:18 <Jasper[m]> @[(⊙_◎)] please let me know if you run into problems with the device crashing/rebooting after typing in the LUKS pass

12:18 <Jasper[m]> I've been running into problems with that

12:32 <Dylanger> Does anyone know if the kernel for the MediaTek mt8195 has been upstream'd now?

12:32 <Dylanger> https://gitlab.collabora.com/google/chromeos-kernel/-/tree/mt8195-tracking-master-rolling

12:32 <Dylanger> Hasn't been updated for 5 months

12:33 <Dylanger> I assume because it's been upstream'd?

12:33 <Dylanger> I have an aarch64 Chromebook (Cherry)

13:19 <altacus> danielt: I think there's something off with my efi partition. I am seeing EFI stab: Booting Linux Kernel... EFI stab: Using DTB from configuration table EFI stab: Exiting boot services... and then reboot

13:21 <altacus> sorry I think there's something off with my boot partition.

13:23 <altacus> It's odd, I have a root, swap and home partition, but after reinstalling, I'm still seeing hold dtb files in the boot partition (via rescue from usb)

14:46 <_[m]1> anybody been having this weird battery issue, it won't boot with the power cable plugged in, you remove, power on, get critically low battery error then if you quickly plug it boots

14:55 <_[m]1> @clover you didn't need to put btrfs in mkinitpcio.conf?

14:56 <_[m]1> * btrfs in modules in mkinitpcio.conf?

14:56 <clover[m]> no

14:56 <clover[m]> but i didn't do FDE

14:57 <_[m]1> for that you put encrypt

14:57 <_[m]1> sigh still black screen

14:58 <_[m]1> aaaah without power cable it works I think 😲

14:58 <_[m]1> whoawhoawhoa

14:59 <_[m]1> did I fck my battery by charging with different watts one?

14:59 <_[m]1> very odd

15:02 <_[m]1> > ERROR: Failed to mount /dev/mapper/crypt on real reoot

15:03 <_[m]1> * > unknown filesystem type efivarfs

15:03 <_[m]1> > ERROR: Failed to mount /dev/mapper/crypt on real reoot

15:03 <_[m]1> * > unknown filesystem type efivarfs

15:03 <_[m]1> > ERROR: Failed to mount /dev/mapper/crypt on real root

15:03 <_[m]1> it's doing legacy boot ??

15:07 <_[m]1> lol you can't even enable that in bios

15:08 <_[m]1> on reboot now it says just that i can't find my luks volume in /dev/mapper hmm

15:09 <_[m]1> will check later for typos in my uuid but I was pretty vigilant

15:09 <_[m]1> wtf it's just trying to do fsck - I didn't enable that though mm

15:11 <_[m]1> ah right that was in initramsfs fallback

15:26 <_[m]1> jhovold so still where did you find these modules? similar soc instructions or so?

16:59 <jhovold> _[m]1: basically from analysing the devicetree and corresponding drivers

17:00 <jhovold> having worked full-time on adding support for the machine also helps

17:00 <jhovold> the qcom display implementation is still a bit of maze

17:08 <clover[m]> jhovold: should I try that patch Jeff mentioned?

17:10 <jhovold> clover[m]: no, no need to as it has no effect on this platform

19:13 <clover[m]> jhovold:... (full message at <https://matrix.org/_matrix/media/v3/download/matrix.org/edAKIEhdWnSPnMZmPRzovHMQ>)

20:06 <_[m]1> <jhovold> "the qcom display implementation..." <- undocumented I guess?

20:32 <_[m]1> oh my I gave the UUID of the luks volume and not the partition #oops

20:41 <_[m]1> thanks so much to everyone working on this, I'm super happy!! btw I'm running arch hahaha

20:45 <hexdump0815> Dylanger: leezu seems to have v6.5 mainline running more or less on his mt8192 asurada spherion - so might be worth a try

21:16 <_[m]1> am getting Cannot open display now on cinnamon-session mm

21:25 <clover[m]> Oh I always was curious about cinnamon, but I don't think it supports Wayland so I never tried it

21:25 <_[m]1> I thought I took cinnamon last time around, but now I start doubting hmpf maybe I went plasma

21:38 <_[m]1> yep nope it's not the DE

21:40 <clover[m]> More fde shenanagins?

21:55 <_[m]1> unsure really, it just boots to tty

21:56 <_[m]1> installed plasma now, same shit, crashes on sddm start 🤷

21:57 <_[m]1> * start 🤷 and nothign in the logs 😢

22:03 <_[m]1> haaa what a joke, I reinstalled endeavouros and took SWAY and bim wayland plasma works WHAT

22:04 <_[m]1> at least the gui login screen lol now mouse and black screen, funfun

22:06 <_[m]1> ah yeah maybe now running into jaspers bug, rebooting after you decrypt root luks volume

22:07 <_[m]1> 2 times reboot lol

22:12 <_[m]1> oh btw I was lying I used pbkdf luks2 instead of argon2, you can't convert luks2 to luks1 but inverse you can

22:15 <_[m]1> * you can (for /boot inside the luks container)

22:16 <_[m]1> * oh btw I was lying I used pbkdf2 luks2 instead of argon2, you can't convert luks2 to luks1 but inverse you can (for /boot inside the luks container)

23:04 <_[m]1> seems we'll be running gnome 🙂

23:25 <steev> aka the good stuff

23:25 <steev> odd that sway didn't run though... are you sure it wasn't running and you just had no config?

23:25 <Jasper[m]> <_[m]1> "2 times reboot lol" <- :|

23:29 <_[m]1> nah wasn't available in the dropdown, I'll investigate more later

23:30 <steev> i dunno what the dropdown is, but that makes me think X was installed and wayland wasn't?

23:30 <_[m]1> <Jasper[m]> ":|" <- I even had a loop when I ran fallback initramfs whoa scary, also ctrl alt f2 wasn't working aaaah but when I added windows key it did? super key weird

23:31 <_[m]1> steev: I installeled wayland session before I even retried endeavouros reinstall with sway

23:32 <_[m]1> à lot of funky stuff I don't understand hmm