ChanServ 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
mbuhl has joined #aarch64-laptops
bibikski has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
bibikski has quit [Read error: Connection reset by peer]
bibikski has joined #aarch64-laptops
hexdump02 has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
bibikski has quit [Read error: Connection reset by peer]
hexdump0815 has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
weirdtreething has quit [Ping timeout: 480 seconds]
weirdtreething has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
lucanis has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
<steev>
jhovold: running all day, with various suspends, and definitely not seeing issues with your patch (and no splats either)
hexdump0815 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
tobhe has joined #aarch64-laptops
tobhe_ has quit [Ping timeout: 480 seconds]
pabs has quit [Read error: No route to host]
pabs has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
davidinux has joined #aarch64-laptops
jhovold has joined #aarch64-laptops
<jhovold>
steev: that's good, thanks
<jhovold>
but we'd also need to know if you start hitting the corruption again if you revert the fix
<jhovold>
that is, same kernel, only the fix reverted
krei-se has quit [Read error: Connection reset by peer]
chrisl has quit [Ping timeout: 480 seconds]
krei-se has joined #aarch64-laptops
SpieringsAE has quit [Quit: SpieringsAE]
krei-se- has joined #aarch64-laptops
krei-se has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
krei-se- has quit [Ping timeout: 480 seconds]
krei-se has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<tobhe>
jhovold: I did some more testing with and without your efi hack yesterday. The installation on my T14s seems to be in a state where it fails 100% of the time without but boots fine with the patch. Forgot how bad this was since I've been running with your patch for quite a while...
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<jhovold>
tobhe: yeah, it makes all the difference, I wouldn't be able to use my t14s without it either
krei-se has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
davidinux is now known as Guest11327
davidinux has joined #aarch64-laptops
Guest11327 has quit [Ping timeout: 480 seconds]
krei-se has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
bibikski has joined #aarch64-laptops
<bibikski>
bamse: Apologies for the delay, first pass didn't work. I spent some of the night reviewing the mkosi documentation to wrap my head around the concepts
<bibikski>
I tried to boot the drive but it took me right back to the boot selection. @tobhe and @jhovold is this the efi issue you two are referring to? If so, could you point me in the direction of the patch please?
bibikski has quit [Read error: Connection reset by peer]
chrisl has quit [Ping timeout: 480 seconds]
<jhovold>
sounds like you're hitting the t14s uefi fw bug, here's the workaround:
<bibikski>
Did you perform the pipx command to install qcom's version of mkosi
<bibikski>
Yeah sorry I close my laptop and check in on the logs
<bamse>
bibikski: the pipx command from the readme will install the latest verion of mkosi directly from the systemd-git...
<bamse>
bibikski: and you need that, because the latest released version (and in particular whatever you'll find in your distro) is lacking some patch(es)
<jhovold>
dgilmore: looks like the same null-deref, but good if you could amend the report since that guy is running with a tainted kernel it seems
<bamse>
bibikski: make johan_defconfig && make pacman-pkg
<bamse>
although, it might be that jhovold doesn't set CONFIG_EFI_ZBOOT=y you need that as well
<dgilmore>
I'll update it. There was a linux-firmware update in the last day or so and I've now had the system crash 3 times in the last hour
<jhovold>
(probably the nvidia driver, but still)
<dgilmore>
Right.
<jhovold>
ouch
<dgilmore>
Seemingly in my case it's changing access points
<dgilmore>
My main networks have 3 APs all with 2.4ghz, 5ghz, and 6ghz support. 2 are WiFi 7 and the other is WiFi 6
chrisl has joined #aarch64-laptops
srinik has quit [Remote host closed the connection]
srinik has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<bibikski>
basme: Just so I have my check list in order. 1) Clone jhovold's repository. 2) Make config 3) make johan_defconfig && make pacman-pkg 4) mkosi --devicetree=<path to thinkpad dts> build --force 5) mkosi --devicetree burn /dev/sdb <usb>
<bibikski>
Apologies I realize now that johan_defconfig does the config for step 2
chrisl has joined #aarch64-laptops
<bamse>
bibikski: between make johan_defconfig and make pacman-pkg you should "make menuconfig" search for CONFIG_EFI_ZBOOT and select 'y', then exit and save
<bamse>
but other than that, it looks reasonable
<bibikski>
Tried running with config_efi_zboot to y and got "drivers/firemware/efi/libstub/zboot.c: In function 'efi_zboot_entry' zboot.c:130:15 error implicit declaration of function '___decompress'
chrisl has quit [Ping timeout: 480 seconds]
<bibikski>
I'm still monitoring, but ill brb. Trying the usb drive I just burnt
<bamse>
not sure why, CONFIG_EFI_ZBOOT should select HAVE_KERNEL_GZIP and HAVE_KERNEL_ZSTD...so it should just work
bibikski_0x0 has joined #aarch64-laptops
<bibikski_0x0>
How can I ensure that the package is being copied from mkosi.packges
bibikski has quit [Ping timeout: 480 seconds]
bibikski_0x0 has quit [Ping timeout: 480 seconds]
bibikski has joined #aarch64-laptops
<bibikski>
Okay, so I tried running the mkosi config from qcom and I am receiving "error: keyring is not writable(\n)error: required key missing from keyring(\n)error: failed to commit transaction (unexpected errors). It only happens when I build the arm64 architecture.
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
srinik has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
<dgilmore>
jhovold: added my traces to the bug report
chrisl has quit [Ping timeout: 480 seconds]
<craftyguy>
jhovold: Every so often I am seeing these messages: [ +27.547696] ath11k_pci 0006:01:00.0: rxed invalid length (nbytes 0, max 2048)
chrisl has joined #aarch64-laptops
<craftyguy>
but it doesn't seem to cause major dropout/disconnects/driver lockups like I was seeing before
chrisl has quit [Ping timeout: 480 seconds]
bibikski has quit [Read error: Connection reset by peer]
<jhovold>
dgilmore: thanks
<jhovold>
craftyguy: sounds like you're testing the fix from qcom, rather than mine
<jhovold>
you should not see that warning otherwise
<jhovold>
but still good to know that their fix works, even if I think it can be handled better
<craftyguy>
ugh, ok I'll check which patch I applied. can you send the link again to where your patch is?
chrisl has joined #aarch64-laptops
<craftyguy>
(I can also dig through the chat backlog later)
<jhovold>
but you may not be able to apply it with b4 as I sent it as a reply to qcom's fix
<jhovold>
it's just two lines, if you want to add them manually
<jhovold>
(i'm sure there's some switch to make b4 pick up the right patch)
<steev>
and back those 2 patches out
<jhovold>
yes, that too
<steev>
i have not yet seen it since reverting your patch, here at my sisters which is odd
<steev>
but i know i will
chrisl has quit [Ping timeout: 480 seconds]
<dgilmore>
I did go from linux-firmware-20250211-1.fc42.noarch to linux-firmware-20250311-1.fc42.noarch today
bibikski has joined #aarch64-laptops
<bamse>
bibikski: what host OS do you run mkosi in?
<bibikski>
Arch on x86_64. I started wondering if it is a build machine issue, so I'm setting up an arch vm
<bamse>
checking...
<bamse>
bibikski: hmm, i see the same thing on my x86_64/arch machine... works fine on my arm64 machine...
jhovold has quit [Quit: WeeChat 4.4.3]
<bibikski>
Then I may be in a pickle for how to continue. I may have to see about getting that ubuntu iso to boot to bastardize a arch build machine
<bamse>
bibikski: you should be able to boot the ubuntu image, chroot into the generic arch iso and install from there - that's more or less how i used to do it before i got mkosi going
chrisl has joined #aarch64-laptops
<bamse>
trying to figure out what changed, and where...becuase this worked last week or so
<bamse>
i think...
<bibikski>
That is true. The last time I tried to install ubuntu, it wouldn't read the nvme drive. Thinking it was due to secure boot + bitlocker
<bamse>
don't you need to shrink the partitions from windows first?
<bibikski>
But i've since reconfigured the laptop. I'll give it a go. But at this point I feel invested in making a bootable image
<bibikski>
Yeah, and I'm trying to dual boot the laptop. I already had split a 2tb drive into two partitions
jglathe_volterra has joined #aarch64-laptops
jhovold has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
bibikski_0x0 has joined #aarch64-laptops
bibikski_0x0 has quit [Ping timeout: 480 seconds]
<bibikski>
39**************************
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<bibikski>
Apologies for the last message, left the client up and the cats got on the keyboard. Anyways I found my mistake. The reason why the ubuntu installer always failed to recognize the nvme drive was due to this adapter I was using (https://www.amazon.com/dp/B0BLJNGGVD). I went cheap and bought a 2tb corsair 2230 nvme and thought I required an extender (2230 to 2242) for it to attach it. Anyways, something about the installer
<bibikski>
is unable to see the drive. The windows recovery image was able to use the drive just fine.
<HdkR>
Oh interesting, I've never seen an adapter on the connector side like that. I usually try to not mess with the connection and extend the other direction :D
<jhovold>
steev: good, how long did it take to trigger?
<jhovold>
:)
<steev>
now reverting the revert and going back to working stuff :D
<jhovold>
and how long did you run with my fix without hitting it (in the same network?)
<jhovold>
perfect, thanks again
<steev>
24 hours or so?
<steev>
its my daily driver machine so
<steev>
i do use it pretty heavily
<jhovold>
sounds like it's working as intended then
<jhovold>
I'll switch to my fix in the next wip branch, so we can get some wider coverage, but this will be good feedback in the discussion with qcom
jhovold has quit [Quit: WeeChat 4.4.3]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
weirdtreething_ has joined #aarch64-laptops
weirdtreething has quit [Ping timeout: 480 seconds]
weirdtreething_ is now known as weirdtreething
xroumegue has quit [Ping timeout: 480 seconds]
todi has quit [Remote host closed the connection]
weirdtreething_ has joined #aarch64-laptops
weirdtreething has quit [Ping timeout: 480 seconds]
weirdtreething_ is now known as weirdtreething
xroumegue has joined #aarch64-laptops
hfg477[m] has joined #aarch64-laptops
lCarlio[m] has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
amstan has joined #aarch64-laptops
<amstan>
so i hear qcom is now bullish on freedreno?
<bamse>
bibikski: on your x86_64 host, "git clone https://github.com/archlinuxarm/PKGBUILDs.git", then in core/archlinuxarm-keyring run "makepkg -i"... this will create and install the archlinuxarm keyring on your arch linux host... when you then try to run mkosi it will be able to find the keys you're looking for