robclark changed the topic of #aarch64-laptops to: Linux support for AArch64 Laptops (Chrome OS Trogdor Devices - Asus NovaGo TP370QL - HP Envy x2 - Lenovo Mixx 630 - Lenovo Yoga C630 - Lenovo ThinkPad X13s - and various other snapdragon laptops) - https://oftc.irclog.whitequark.org/aarch64-laptops
sporos11[m] has joined #aarch64-laptops
EricCurtin[m] has joined #aarch64-laptops
<steev> Those of us with a modern irc client see the markdown properly
<steev> _[m]1: is it always 4 reboots?
<steev> We had something similar at one point on the c630 but I cannot for the life of me think of what the fix was
<steev> e.g. X reboots to get audio working (not crash though)
go4godvin has joined #aarch64-laptops
go4godvin is now known as Guest172
rpirea_ has joined #aarch64-laptops
rpirea has quit [Ping timeout: 480 seconds]
<Jasper[m]> <steev> "(⊙_◎): is it always 4 reboots?" <- Nah, worst I had was about 8
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
<clover[m]> <_[m]1> "I built mesa, rebooted, 4..." <- Why do you need to build Mesa? Just use the one in my repo
konradybcio1 has joined #aarch64-laptops
rpirea_ is now known as rpirea
jenneron[m] has joined #aarch64-laptops
<jhovold> robclark: as bamse mentioned there's been some people looking at addressing the need for clk_ignore_unused and pd_ignore_unused (e.g. abel, saravana) but it appears to be stalled currently
<jhovold> I haven't really had time to dig into myself yet either
<jhovold> but you definitely still need both of those
<jhovold> clover[m], _[m]1: why are both of you building mesa? alarm is carrying 23.1.7 now which has a690 support so it seems you drop the mesa-23.1.4 package you have in your repo clover[m]
<jhovold> can*
<_[m]1> <clover[m]> "Why do you need to build Mesa..." <- you don't need to do makepkg -si ?
hightower2 has quit [Ping timeout: 480 seconds]
<jhovold> _[m]1: no, you should not need to to build mesa yourself or use the one in clovers repo
<jhovold> arch has mesa-23.1.7, just make sure that one is installed if it isn't already
<_[m]1> <jhovold> "(⊙_◎): no, you should not need..." <- I built that one lol, you're saying it was available from the repo?
<jhovold> your distro already provides mesa, you do not need to build that package yourself
hightower2 has joined #aarch64-laptops
alfredo has joined #aarch64-laptops
alfredo has quit [Read error: Connection reset by peer]
hightower2 has quit [Ping timeout: 480 seconds]
hightower2 has joined #aarch64-laptops
Cyrinux9474 has quit []
Cyrinux9474 has joined #aarch64-laptops
<clover[m]> jhovold: because upstream alarm wont add the freedreno drivers: https://github.com/archlinuxarm/PKGBUILDs/pull/1996
<jhovold> clover[m]: freedreno is enabled, but, ok, apparently not the vulkan driver
<jhovold> i'm only using glmark for testing so I haven't noticed, thanks for the heads up
<jhovold> but _[m]1 shouldn't have to bother with that if he just wants to boot into xorg or sway without crashing, for whatever reason yet to be determined
<bamse> jhovold: speaking of booting, have you looked at fbcon in v6.6-rc1?
konradybcio has joined #aarch64-laptops
<konradybcio> bamse I believe lumag and narmstrong figured that out
<konradybcio> a config option is now not enabled by default
<jhovold> nope, i haven't had time to switch to rc1 yet, another fun regression?
<jhovold> ah, i think i saw the thread fixing fixing that then
<bamse> jhovold: kernel is happy, but there's nothing on the screen...launching wayland "solves" the problem though
<bamse> konradybcio: any pointer?
<konradybcio> CONFIG_FRAMEBUFFER_CONSOLE off the top of my head?
<jhovold> this is the thread that comes to mind:
<bamse> konradybcio: hehe, that would be too easy ;)
<bamse> jhovold: thanks
<bamse> jhovold: it's been too long since i screwed up those config options, that i didn't consider it to be that easy
Guest8 is now known as qzed
<strongtz[m]> camss
<_[m]1> <jhovold> "but (⊙_◎) shouldn't have to..." <- I want to play dota2, such much important
<jhovold> _[m]1: ok, got it, i thought you were just trying to get your installation to work properly
<_[m]1> I don't mind the minor discomforts hehe if anything I hope it helps to identify some edge cases and bugs
rpirea has quit [Quit: Leaving]
mar_ has joined #aarch64-laptops
mar_ has quit []
hightower2 has quit [Remote host closed the connection]
hightower2 has joined #aarch64-laptops
<clover[m]> FDE working here
<clover[m]> haven't experienced any reboots really
<clover[m]> Jasper: my grub config ended up looking slightly different than yours. maybe you can try these options:
<clover[m]> GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 efi=noruntime clk_ignore_unused pd_ignore_unused iommu.passthrough=0 iommu.strict=0"
<clover[m]> GRUB_CMDLINE_LINUX="cryptdevice=UUID=4cb8bd8d-5c9e-45a2-823f-cfec2129bae8:cryptroot root=/dev/mapper/cryptroot"
<clover[m]> i am told UUID is best to use from the tutorial i watched. this is the tutorial i used: https://www.youtube.com/watch?v=XNJ4oKla8B0&t=1233s
<clover[m]> my root fs is f2fs B:()
<clover[m]> B-)*
<steev> of course you'd use that
<steev> jk, i have no idea if f2fs is still good or not
<clover[m]> It works fine I can't notice a difference between it vs ext4. Btrfs was a bad experience since I had to run fsck a few times and the snapshot feature I didn't find useful
<Jasper[m]> <clover[m]> "haven't experienced any reboots..." <- Only happens after an unlock normally