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
mcbridematt has quit [Quit: Leaving]
mcbridematt has joined #aarch64-laptops
einar has quit [Remote host closed the connection]
<JensGlathe[m]>
Painkiller995: Hmm thanks for the screenshots. Maybe the pd-mapper in kernel space? We're booting without adsp on
srinik has joined #aarch64-laptops
srinik has quit [Ping timeout: 480 seconds]
xroumegue has quit [Ping timeout: 480 seconds]
xroumegue has joined #aarch64-laptops
srinik has joined #aarch64-laptops
ndi_heise[m] has joined #aarch64-laptops
xroumegue has quit [Ping timeout: 480 seconds]
<ndi_heise[m]>
hey there, i'm testing linux on the asus vivobook s15 and saw that the device trees are now in linux 6.11rc1 but i can't get it up and running (i know of the limitations). tried with fedora rawhide which should incluce the latest upstream kernel. is anybody working on the s15 as well?
<ndi_heise[m]>
i can get to grub and choose the fedora installer, then i get a black screen and windows starts up
<krzk>
ndi_heise[m]: does your fedora grub load proper DT?
xroumegue has joined #aarch64-laptops
<ndi_heise[m]>
not sure, do you know how to verify?
<Molyuu[m]>
hey guys, i'm trying to port linux to Xiaomi Book S 12.4 (8cx Gen 2), I've write a dts for it, but it cannot get into login prompt (it just boots, after systemd launched and journal service started, screen comes blank). I checked journal that systemd recorded and it seems it did not record any useful info. Is there any way to find out what cause it freezes?
craftyguy has quit [Remote host closed the connection]
craftyguy has joined #aarch64-laptops
<Painkiller995[m]>
Jens Glathe: I'm not sure if there's any firmware that needs to be added to "lib/firmware/qcom". But I do remember something about adding something to fix the pd-mapper.
<JensGlathe[m]>
the image contains the userspace components. Will look into this later
<calebccff>
ndi_heise[m]: fedora don't ship DTBs, you need to drop it in the image and specify the devicetree in grub
Integral[m] has joined #aarch64-laptops
Guest2419 has joined #aarch64-laptops
Guest2419 has quit []
<robclark>
fyi, a7xx gallium (gl/gles) support is in 24.2.0-rc4 .. so hopefully in distro repo's by the time v6.12 comes around (at which point I hope we have everything needed for x1e laptops upstream)
<JosDehaes[m]>
Oh nice, I thought you said it wasn't going to be in 24.2
<robclark>
I pinged the release mgr (eric_engestrom), since the zink automatic fallback is kinda rough (ie non existent) and he said since it only touched driver code that it would be ok to backport
<robclark>
otherwise, we'd have a window of time where kernel and distros start having x1e support but gfx would be broken without setting env variables
<HdkR>
Oh cool, I was scared of updating the FEX images because of the WSI refactoring. If it ends up in 24.2 then that is way less scary :D
<FarchordSteveCossette[m]>
They're in /boot/dtb-<kernel version>
<calebccff>
oh shoot
<calebccff>
heck yeah, didn't know this
<ndi_heise[m]>
oh, thx. sorry if thats a dumb question, but how do point grub to the correct devicetree? with "devicetree" command or in grub.cfg?
<ndi_heise[m]>
* how do i point grub
<calebccff>
devicetree command
<ndi_heise[m]>
like devicetree /boot/dtb-6.11.0-0.rc2.23.fc41.aarch64/qcom/x1e80100-asus-vivobook-s15.dtb?
enyalios has quit [Remote host closed the connection]
enyalios has joined #aarch64-laptops
<Jasper[m]>
yep! but could be that grub doesn't honor that folder scheme
<Jasper[m]>
Best is to try it in a loaded grub first and add it to the config file later. Grub itself supports tab completion.
krei-se- has joined #aarch64-laptops
krei-se has quit [Ping timeout: 480 seconds]
clee_ has joined #aarch64-laptops
srinik has joined #aarch64-laptops
clee has quit [Ping timeout: 480 seconds]
srinik has quit [Ping timeout: 480 seconds]
<steev>
bamse: one other thing i've noticed, and probably should report... ath10k snoc seems to crash on reboot/shutdown (both on the c630 and the flex5g)
<bamse>
steev: yeah, i've noticed that as well...for the last 4 years or so...would be nice to get that cleared up
<steev>
calebccff: if you happen to still have a working debug setup on your c630… could you try 6.11 and capture that? I don’t have a good way to :(
<steev>
Actually I guess any recent kernel? But I figure 6.11 since it has the ec and battery driver
srinik has joined #aarch64-laptops
<JensGlathe[m]>
Hmm 6.11rc2 doesn't boot on wdk2023. hmpf
<calebccff>
steev: i got 6.11-rc1 booting to GNOME the other day, don't have a log though
<steev>
calebccff: oh perfect :) just need a log of the shutdown because that's when ath10k_snoc crashes :)
<steev>
bamse: can confirm v3 works on the flex 5g :D
<steev>
like, what's the difference between "SILVER", "GOLD", "BIG", "LITTLE"
<HdkR>
That's just the marketing name that QCom chose, Prime, Gold, Silver
<bamse>
HdkR: you forgot gold+
<HdkR>
Is gold+ actually a thing?
<HdkR>
I thought the SoCs with two "gold" clusters were both just called gold
<bamse>
i might misremember, but i thought e.g. sm8150 has silver + gold + gold+
<HdkR>
Yea, sm8650 does as well
<HdkR>
1+3+2+2
<bamse>
as long as it goes brrr i don't pay much attention...
<steev>
ah, okay
srinik has quit [Ping timeout: 480 seconds]
<konradybcio>
juergh: is there a quick (i.e. not chase 50 A4 pages of commands like some google search results suggest) way to spin up a custom ubuntu iso?