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
mrkajetanp has quit [Ping timeout: 480 seconds]
<steev> rc7 is out
<craftyguy> last RC? 🤞 😛
<steev> usually...
<steev> i'm still trying to get my c630 to boot again to see if rc7 fixes things
mrkajetanp has joined #aarch64-laptops
mrkajetanp has quit [Ping timeout: 480 seconds]
<steev> bamse: https://dpaste.org/Gnm9A - there's just nothing about why the wifi isn't there, the remoteprocs are up and running, and the only devices deferred is aux_bridge.aux_bridge.0aux_bridge.aux_bridge: failed to acquire drm_bridge
<steev> i notice with 6.10.3 (6.10.6 doesn't seem to want to exit efi for some reason), i do get an error about msadp being missing, but no idea what that firmware is even supposed to be. it's not like the c630's firmware has changed any since 2019
<steev> though, it looks like it's some sorta dp firmware
mrkajetanp has joined #aarch64-laptops
mrkajetanp has quit [Ping timeout: 480 seconds]
mcbridematt has quit [Quit: Leaving]
mcbridematt has joined #aarch64-laptops
Caterpillar has joined #aarch64-laptops
mrkajetanp has joined #aarch64-laptops
ellyq_ has joined #aarch64-laptops
ellyq has quit [Ping timeout: 480 seconds]
mrkajetanp has quit [Ping timeout: 480 seconds]
mrkajetanp has joined #aarch64-laptops
mrkajetanp has quit [Ping timeout: 480 seconds]
tobhe has joined #aarch64-laptops
mrkajetanp has joined #aarch64-laptops
tobhe_ has quit [Ping timeout: 480 seconds]
mrkajetanp has quit [Ping timeout: 480 seconds]
mrkajetanp has joined #aarch64-laptops
mrkajetanp has quit [Ping timeout: 480 seconds]
mrkajetanp has joined #aarch64-laptops
mrkajetanp has quit [Ping timeout: 480 seconds]
mrkajetanp has joined #aarch64-laptops
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
mrkajetanp has quit [Ping timeout: 480 seconds]
mrkajetanp has joined #aarch64-laptops
mrkajetanp has quit [Ping timeout: 480 seconds]
mrkajetanp has joined #aarch64-laptops
mrkajetanp has quit [Ping timeout: 480 seconds]
mrkajetanp has joined #aarch64-laptops
mrkajetanp has quit [Ping timeout: 480 seconds]
vk6[m] has joined #aarch64-laptops
<vk6[m]> so i updated my kernel and device tree for my asus vivobook s15, and while the keyboard and trackpad work now, the gpu is suddenly missing?
<vk6[m]> [ 1.677256] [drm:dpu_kms_hw_init:1108] dpu hardware revision:0x90020000
<vk6[m]> [ 1.678477] msm_dpu ae01000.display-controller: no GPU device was found
<vk6[m]> [ 1.678471] [drm] Initialized msm 1.12.0 for ae01000.display-controller on minor 0
<vk6[m]> this is with linux 6.11.0-rc7
<vk6[m]> at least xorg still starts
<vk6[m]> i had the gpu working for a single boot in 6.11.0-rc1 and the original device tree
mrkajetanp has joined #aarch64-laptops
alfredo has joined #aarch64-laptops
<vk6[m]> oh maybe i need to revert the commit that disabled the gpu in the device tree
mrkajetanp has quit [Ping timeout: 480 seconds]
alfredo1 has joined #aarch64-laptops
<vk6[m]> yep reverting 1f7574a1f9a892dd79e0dfc03f38573e9c399ec2 fixes it
alfredo has quit [Ping timeout: 480 seconds]
alfredo1 is now known as alfredo
mrkajetanp has joined #aarch64-laptops
mrkajetanp has quit [Ping timeout: 480 seconds]
<vk6[m]> now the only problem is the lack of a battery status
<vk6[m]> is there any workaround for it?
alfredo has quit [Quit: alfredo]
jhovold has joined #aarch64-laptops
<JensGlathe[m]> do the USB-A connectors work?
mrkajetanp has joined #aarch64-laptops
<JosDehaes[m]> vk6: do you have the in-kernel pd-mapper or the userspace pd-mapper?
mrkajetanp has quit [Ping timeout: 480 seconds]
mrkajetanp has joined #aarch64-laptops
mrkajetanp has quit [Ping timeout: 480 seconds]
mrkajetanp has joined #aarch64-laptops
mrkajetanp has quit [Ping timeout: 480 seconds]
mrkajetanp has joined #aarch64-laptops
mrkajetanp has quit [Ping timeout: 480 seconds]
mrkajetanp has joined #aarch64-laptops
mrkajetanp has quit [Ping timeout: 480 seconds]
<jhovold> Here's an updated wip branch for the X13s:
<jhovold> Changes include:
<jhovold> - fix serial console corruption
<jhovold> - fix camera interrupt type in dt
<jhovold> Here's an updated wip branch for x1e80100:
<jhovold> Changes include:
<jhovold> - fix usb-c orientation detection (crd, t14s)
<jhovold> - fix serial console corruption
<jhovold> - fix edac driver probe
<jhovold> - enable usb-c dp altmode (crd, t14s)
<jhovold> - johan_defconfig: enable ps8830 retimer
mrkajetanp has joined #aarch64-laptops
mrkajetanp has quit [Ping timeout: 480 seconds]
mrkajetanp has joined #aarch64-laptops
mrkajetanp has quit [Ping timeout: 480 seconds]
mrkajetanp has joined #aarch64-laptops
mrkajetanp has quit [Remote host closed the connection]
mrkajetanp has joined #aarch64-laptops
todi_away has joined #aarch64-laptops
todi has quit [Ping timeout: 480 seconds]
mrkajetanp has quit [Ping timeout: 480 seconds]
mrkajetanp has joined #aarch64-laptops
<vk6[m]> Jens Glathe: no, i didn't think it was a big deal so i didnt mention it
MrCatfood[m] has joined #aarch64-laptops
iivanov has joined #aarch64-laptops
<MrCatfood[m]> can anyone try running zed on linux with the vivobook?
mrkajetanp has quit [Ping timeout: 480 seconds]
mrkajetanp has joined #aarch64-laptops
SpieringsAE has joined #aarch64-laptops
<SpieringsAE> MrCatfood[m]: seems to at least open on mine
<SpieringsAE> I've never used zed so I don't know if there is anything weird going on
<SpieringsAE> vk6[m]: dont know yet how to fix the battery, I fixed qseecom to change the bootorder and gpu node on mine so far
iivanov has quit [Remote host closed the connection]
iivanov has joined #aarch64-laptops
alfredo has joined #aarch64-laptops
whiskey9 has quit [Remote host closed the connection]
SpieringsAE has quit [Remote host closed the connection]
SpieringsAE has joined #aarch64-laptops
maud has joined #aarch64-laptops
alfredo has quit [Ping timeout: 480 seconds]
SpieringsAE has quit [Read error: Connection reset by peer]
<\[m]> it's time to buy t14s, or am I reading it wrong that dp altmode usb c enabled means external screen is working?
<jhovold> it's supposed to be working, yes, but there may still be some issues iiuc (e.g. requiring a monitor power cycle)
<konradybcio> jhovold doesn't it crash the device on dp unplug for you?
iivanov has quit [Remote host closed the connection]
<jhovold> konradybcio: I didn't get around to buy a longer usb-c dp cable last week so I haven't tested this myself yet (on the crd)
<jhovold> there are a ton of issues with the dp code in the drm msm driver, so I wouldn't be surprised
<jhovold> but I would have expected abel to not submit these patches without at least pointing that out if that was the case
<jhovold> are you seeing the crash on the t14s, crd or both?
iivanov has joined #aarch64-laptops
<anonymix007[m]> Can I test USB-C video output with a USB-C to HDMI adapter?
maud has quit [Remote host closed the connection]
alfredo has joined #aarch64-laptops
<konradybcio> jhovold i don't have either.. but i do get crashes on my surface laptop
<konradybcio> anonymix007: probably
<jhovold> ok, thanks, I'll see if I can reproduce this myself
* \[m] opens bank app
<anonymix007[m]> How can I debug "EFI stub" issue? It fails to exit boot services with "normal" boot (Image) using systemd-boot when booting from NVMe. Basically, it only works if I use UKI and if I interrupt selection of the default boot option
<travmurav[m]> anonymix007: do you have the error code that it spits out?
flokli has quit [Ping timeout: 480 seconds]
<travmurav[m]> inb4 also funny 64gb ram device
<anonymix007[m]> travmurav: my T14s only has 32 gigs. Can I just print this status code with efi_debug or something?
<travmurav[m]> anonymix007: just add it to the print that complains, yes
<travmurav[m]> it's printf-like thing so should be easy
<travmurav[m]> (may want to dump it with %x tho)
flokli has joined #aarch64-laptops
mrkajetanp has quit [Remote host closed the connection]
alfredo has quit [Ping timeout: 480 seconds]
mrkajetanp has joined #aarch64-laptops
<robclark> vk6[m]: you shouldn't revert 1f7574a1f9a892dd79e0dfc03f38573e9c399ec2 but instead re-enable the gpu (with correct firmware path for zap shader) in the per-laptop toplevel dts (see x1e80100-lenovo-yoga-slim7x.dts, for an example)
matthias_bgg has joined #aarch64-laptops
<anonymix007[m]> travmurav: it's 0x2
<travmurav[m]> ugh
<travmurav[m]> ah hm
<anonymix007[m]> Should've used %lx, so probably EFI_INVALID_PARAMETER
winne42[m] has joined #aarch64-laptops
<travmurav[m]> but well ebs is defined to leave this error only if mapkey is incorrect, aka something changed the memory map between get memory map and ebs
<travmurav[m]> so hmmm
<travmurav[m]> I guess it fails here twice
<travmurav[m]> could put a loop there for funny, note that you can't use any efi services between get mmap and ebs since even print changes the memory map
<travmurav[m]> but this really shouldn't be a problem...
<travmurav[m]> weird stuff
<anonymix007[m]> The funny part is that it only fails if I let sd-boot automatically select the default entry or the "normal" vmlinux/Image entry. UKI only works if selected manually, otherwise it has the same error
<travmurav[m]> this still feels like some oem firmware mess to me since it's likely firmware that has some other thread that kills the memory map
<anonymix007[m]> Well, that's likely, but that would be very unfortunate as it would be up to Lenovo to fix this in such case
<robclark> nirik: hmm, downloaded and installed the 2.2.12-4.fc41 grub from rawhide, but still kb isn't working in grub menu.. my 7x seems to be somehow "special" :-/
<travmurav[m]> well, making it retry ebs a few more times might be interesting still
<travmurav[m]> might be some fun timing issue
<anonymix007[m]> abelvesa: do you have the same issue on your T14s?
<konradybcio> robclark can you try updating the bios manually?
<konradybcio> even if you're on latest
<travmurav[m]> i.e. if the funny mess only has time to stop messing with memory if you delay it by going through the menus
<robclark> konradybcio: maybe.. I checked ~1mo ago and there were no bios updates avail to download but maybe that has changed in the mean time
<travmurav[m]> iow "it's broken because linux is booting too fast"
<travmurav[m]> would be funny
<anonymix007[m]> Another thing is that this basically never happens with grub, so it's probably just sd-boot that is too fast
<travmurav[m]> what if you literally put a bs stall before ebs? xD
* travmurav[m] puts a salesman hat on
<travmurav[m]> or my dtbloader has all the facilities to stall for a second for you upon detecting t14s :^)
<travmurav[m]> (as well as locking out most of the memory on 64gb machines :^) )
<anonymix007[m]> That would probably fix UKI, but vmlinux/Image just doesn't boot at all, so timing issue won't explain it
<travmurav[m]> hm and its same ebs issue?
SpieringsAE has joined #aarch64-laptops
<anonymix007[m]> Yes, same status
<travmurav[m]> well I guess trying to repeatedly ebs multiple times would be interesting
<SpieringsAE> anonymix007[m]: mind if I send in a pull request to enable the uinput module to your x1e-alarm repo? keyd doesn't work without it, built my own kernel with it and it fixed it.
<anonymix007[m]> konradybcio: well, USB-C to HDMI adapter didn't work
<travmurav[m]> inb4 need to flip it twice
<robclark> konradybcio: checked again.. possibly I just don't know how to find things on lenovo support site, but I'm not seeing any bios update for the 7x yet
* travmurav[m] sees second training failure and gets reminded that he has never figured out how to convince rift-s to run while only having two DP lanes
<konradybcio> robclark: actually.. looks like there's no support page for the yoga even!?
<anonymix007[m]> SpieringsAE: well, config is autogenerated from johan_defconfig and then I enable a few options manually, so not sure how that'd work.
<nirik> robclark: is yours a 16GB or 32GB one? mine is 32 if that matters
<SpieringsAE> anonymix007[m]: ah okay jeah that makes things more tricky guess i'll live without keyd for now
<nirik> indeed dmidecode has mine with:
<nirik> Version: NHCN44WW
<nirik> Release Date: 06/22/2024
<anonymix007[m]> SpieringsAE: Would adding CONFIG_INPUT_UINPUT=m be enough? I'll try to not forget adding it in the future if so
<SpieringsAE> jep thats enough
<travmurav[m]> anonymix007: maybe you can just maintain a config fragment?
<travmurav[m]> and then make johan_defconfig extras.config
<travmurav[m]> to combine
<anonymix007[m]> travmurav: Thanks for the suggestion, now I did just that
<abelvesa> anonymix007[m]: let me guess, compressed kernel image ?
<anonymix007[m]> abelvesa: It shouldn't be, you can check the packages here: https://github.com/anonymix007/x1e-alarm/releases/tag/packages
<anonymix007[m]> sd-boot entry has vmlinux, so that's not it
<travmurav[m]> it could be zboot (efi self decompressing) but don't think that would explain failing ebs
<abelvesa> sd-boot, unlike grub, doesn't know how to decompress the kernel image, AFAIU
<travmurav[m]> yes, if it's just raw gzip but then it would've not gotten to the efistub code either
<travmurav[m]> (zboot is plain efistub + compressed kernel proper which efistub will decompress however)
<abelvesa> anonymix007[m]: for systemd-boot you definitely need this: https://lore.kernel.org/all/20240819-uncompressed-distro-packages-v1-1-c8accc8bc9ea@quicinc.com/
<anonymix007[m]> abelvesa: That would only be needed for in-kernel PKGBUILD, I have a separate one (basically copied from clover's x13s repo)
<abelvesa> oh, right, endeavouros, my bad
<robclark> nirik: ^^^
<robclark> it is 32GB, fwiw
<anonymix007[m]> abelvesa: BTW, have you seen https://katb.in/ezehofelige with USB-C DP?
<abelvesa> anonymix007[m]: it's expected to get 4-5 link training before it actually succeed
<abelvesa> anonymix007[m]: and yes, it's a known issue
<nirik> wonder why they aren't shipping the bios version I have as an update... ;(
<robclark> what is the bios version you have?
<robclark> it's possible they are and I just don't know how to find things on lenovo's site
<anonymix007[m]> abelvesa: Does it mean that DP doesn't work yet? I also randomly got "[ 2146.498502] [drm:dp_panel_read_sink_caps [msm]] *ERROR* read dpcd failed -110"
SpieringsAE has quit [Remote host closed the connection]
<robclark> anonymix007[m]: dp works but is not very stable/reliable yet.. doesn't work on every boot, sometimes doesn't come back from dpms-off, etc
<vk6[m]> this is how i ended up modifying the device tree. i didn't blindly git revert it because i had the kernel source downloaded from the tarball so i couldn't do that anyways.
<anonymix007[m]> robclark: so far it's pretty reliably not working. 0/7 reboots
<vk6[m]> btw i've uploaded deb packages for the working 6.11-rc7 kernel for the vivobook to my website: https://local.ading.dev/array/linux-snapdragon-vivobook/
<vk6[m]> note that you will also have to edit `/etc/grub/10_linux` to add the device tree to every boot entry... (full message at <https://matrix.org/oftc/media/v1/media/download/AYmfGK6sXwLU0T8RSegBvSE-d2ApMzJrvWOZyN0J5m6y0wML7AloZtFMOkSp2YOku9Y1FcI1g9_FZVM9gNLNjftCeR2UXjSAAG1hdHJpeC5vcmcvcG5HaWh5eEFKaWdqSFZHdXNqVklvdklN>)
<vk6[m]> i haven't actually tested these deb packages since i used make install after compiling the kernel, but they're using the same .config so it should still work
kuruczgy[m] has joined #aarch64-laptops
<kuruczgy[m]> vk6: FYI in-kernel pd-mapper is still buggy, for now it's recommended to use the userspace one
<vk6[m]> <kuruczgy[m]> "vk6: FYI in-kernel pd-mapper..." <- you're talking about this package right? https://packages.debian.org/sid/protection-domain-mapper
<kuruczgy[m]> Looks like it
<vk6[m]> i tried it and it doesn't work, it just fails with a no pd maps available message
<JensGlathe[m]> the maps are these json files, right? need to be in the same place as the adsp firmware afair
iivanov has quit [Remote host closed the connection]
<steev> correct
iivanov has joined #aarch64-laptops
ellyq has joined #aarch64-laptops
ellyq__ has joined #aarch64-laptops
ellyq_ has quit [Ping timeout: 480 seconds]
ellyq_ has joined #aarch64-laptops
ellyq___ has joined #aarch64-laptops
ellyq has quit [Ping timeout: 480 seconds]
ellyq has joined #aarch64-laptops
ellyq__ has quit [Ping timeout: 480 seconds]
ellyq_ has quit [Ping timeout: 480 seconds]
ellyq_ has joined #aarch64-laptops
ellyq___ has quit [Ping timeout: 480 seconds]
ellyq has quit [Ping timeout: 480 seconds]
ellyq has joined #aarch64-laptops
ellyq_ has quit [Ping timeout: 480 seconds]
iivanov has quit [Remote host closed the connection]
iivanov has joined #aarch64-laptops
<nirik> robclark: I have 1.44... https://paste.centos.org/view/13dc6846
<robclark> hmm, ok.. I guess that means there should be some sort of bios update out there _somewhere_
<nirik> yeah, you would think, but I can't see one anywhere...this the version mine shipped with
<robclark> interestingly enough, there is a "Lenovo Linux Diagnostics - Bootable CD"
<robclark> but looks like it is an x86 image.. I guess that won't work all that well :-P
<nirik> I managed to find some kind of menu with diag on boot a while back, but I don't know what I hit to get it... :(
iivanov has quit [Remote host closed the connection]
agl_ has quit [Ping timeout: 480 seconds]
agl has joined #aarch64-laptops
<nirik> robclark: the pdf manual mentions a 'novo button hole' that can bring up a firmware util? https://download.lenovo.com/consumer/mobiles_pub/yoga_slim_7_14q8x9_ug_en.pdf
<robclark> ahh, yeah, I did see that
<robclark> I'm not specifically looking for diags, just something that might contain a bios update
<robclark> (there is a windows driver update package, but that didn't seem to include any bios update)
<JensGlathe[m]> what kind of design / solution is that
<robclark> probably a rma tool, ie. meant for tech if user takes laptop in for service
<nirik> yeah, if I can find a paperclip I can try it later.
<JensGlathe[m]> HP has complete testing tool as an EFI application
jhovold has quit [Ping timeout: 480 seconds]
<robclark> that is _probably_ what the novo button thing is too
iivanov has joined #aarch64-laptops
iivanov has quit [Remote host closed the connection]
iivanov has joined #aarch64-laptops
iivanov_ has joined #aarch64-laptops
iivanov_ has quit [Remote host closed the connection]
iivanov has quit [Read error: No route to host]
iivanov has joined #aarch64-laptops
<steev> assuming your CN36WW means you have 1.36, and CN44WW means 1.44?
anarsoul has quit [Quit: ZNC 1.8.2 - https://znc.in]
<steev> or i'm looking at the wrong device :D
<robclark> that is a different device
<steev> yeah... they really don't seem to have a downloads section for that one, weird
<nirik> lenovo's naming is horrible. There's a ton of different 'slim 7' devices that are wildly different. ;(
<steev> yep
<steev> look at their lenovo yoga c630... and lenovo chromebook c630
<nirik> https://pcsupport.lenovo.com/us/en/products/laptops-and-netbooks/yoga-series/yoga-slim-7-14q8x9/83ed/83edcto1ww/pf55103x/downloads/driver-list/component?name=Diagnostic was the place I was seeing the diag stuff, but those don't really have anything to do with firmware, only testing hardware bits it seems like.
<JensGlathe[m]> They're learning from Microsoft
<abby> and the lenovo yoga vs lenovo thinkpad yoga lines
<nirik> and the marketing has 'yoga slim 7x' but the model is just 'slim 7'... the 'x' is just marketing, not used for any of the internal product stuff it seems like.
<JensGlathe[m]> X is x1e I assumed (in this case)
<robclark> iirc there was a 'yoga slim 7i' with intel
<nirik> I guess it's 'Yoga Slim 7 14Q8X9 - Type 83ED' just rolls off the tounge. :)
<JosDehaes[m]> there is a 'Lenovo Linux Diagnostics - Bootable CD', anyone try this?
<JosDehaes[m]> and 'Lenovo Linux Diagnostics - Bootable USB'
<JosDehaes[m]> this seems to be x86_64 though
iivanov has quit [Remote host closed the connection]
mrkajetanp has quit [Quit: WeeChat 4.4.2]
flokli has quit [Ping timeout: 480 seconds]
flokli has joined #aarch64-laptops
iivanov has joined #aarch64-laptops
<freekurt[m]> <freekurt[m]> "In Ubuntu's official installer..." <- After using this official Ubuntu installer ISO to install onto my x13s SSD, I enabled oracular-proposed and upgraded to Ubuntu's 6.11.0-6-generic kernel using ‘sudo apt install linux-image-generic/oracular-proposed’.
<freekurt[m]> Someone had made some x13s specific tweaks to it a few days ago: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2078929
<freekurt[m]> I couldn't get it to boot at first, but I got a little help from someone who told me there was a race condition of some sort. https://discourse.ubuntu.com/t/status-of-ubuntu-support-for-lenovo-thinkpad-x13s/44652/79?u=libredood
<freekurt[m]> I was able to confirm using mesa-tools that hw acceleration is working. The camera still doesn't work, though.
<freekurt[m]> 'cam -l' does see the internal front camera, but it doesn't show up in Cheese or Gnome Camera.
iivanov has quit [Ping timeout: 480 seconds]
indy_ has joined #aarch64-laptops
indy has quit [Ping timeout: 480 seconds]
<freekurt[m]> Also I still can't get my usb-c to DP cable to work, even though the cable works on my gf's work computer. What should I look for when purchasing another cable so I can be somewhat assured the next one I buy will work with my x13s?
matthias_bgg has quit [Quit: Leaving]
eac has quit [Quit: bye]
<gabertron> and also requires some strange process which is:
<gabertron> t14s + 64GB update: with a 6.10-rc6 kernel with some patches that konrad and I were using to get the t14s working back in july I can get the frame buffer mode of the display to work if I disable mdss and use either mem=16G or mem=8G on the kernel commandline
<gabertron> 1. reboot into efi shell
<gabertron> 2. hit escape to prevent it from booting
<gabertron> 3. type "reset" to get it to do a soft reboot
<gabertron> 4. now let it reboot and boot up fully this time
<gabertron> 5. the same procedure is required for both efi shell as well as the grub version that I sent out over the weekend that was limited to using 4GB
<gabertron> I've tried a couple of the newer johan kernels and those don't work -- looks like even with those changes above I get a kernel panic of some variant
<gabertron> if I enable mdss in the dts then the screen goes black but it doesn't kernel panic and I can ssh in and read the edid from the display
<gabertron> not sure how much more time I can burn on this but for people who have these laptops if you want to try including in your test process the warm reboot trick and using say mem=16G on the kernel command line, I'm curious if anybody can get one of the newer kernels working
<robclark> gabertron: can you pastebin edid-decode? That should give us make/model for the panel.. and from that we can attempt to cobble together dts for t14s-oled
eac has joined #aarch64-laptops
<gabertron> that has the edid bin itself and the parsed version of that
<kuruczgy[m]> vk6: You have to copy the json files from windows. (Or if you don't want that I have them here: https://github.com/kuruczgy/x1e-nixos-config/tree/main/firmware )
<kuruczgy[m]> Put them in the `.../qcom/x1e80100/LENOVO/83ED/` firmware path. Make sure that they are not compressed.
<kuruczgy[m]> (Ah actually I am not sure which device you have, this is for the yoga slim 7x, on a different device you have to use a different path, and I am not sure if the json files are the same...)
<robclark> gabertron: ok, ATNA40YK20 .. compared to ATNA45DC02 on the yoga..
<gabertron> so a bit different
<robclark> it's probably the same panel driver.. but maybe it is wired up differently?
jkm_ is now known as jkm
<gabertron> yea I wonder -- probably need an acpi dump?
<HdkR> acpi dump is on the github
<gabertron> oh from 64GB + OLED 2880x1800 display model?
<HdkR> yea, I uploaded mine
<gabertron> nice
<robclark> travmurav[m]: jfwiw, the t14s with oled has a different ProductVersion (and probably some other different strings) from the IPS t14s.. so DtbLoader should have no trouble to pick the right dtb for each
phire_ has joined #aarch64-laptops
phire is now known as Guest3014
phire_ is now known as phire
Guest3014 has quit [Ping timeout: 480 seconds]
rfs613 has quit [Remote host closed the connection]
flokli has quit [Ping timeout: 480 seconds]
rfs613 has joined #aarch64-laptops
rfs613 has quit [Remote host closed the connection]
rfs613 has joined #aarch64-laptops
flokli has joined #aarch64-laptops
anarsoul has joined #aarch64-laptops
indy_ has quit [Ping timeout: 480 seconds]
indy has joined #aarch64-laptops
snoonet has joined #aarch64-laptops
<steev> freekurt[m]: keep in mind if you/ubuntu have the venus patchset, you *need* to have the venus firmware in there
<steev> it's not provided in linux-firmware, and has to be gotten from the windows partition, unless ubuntu are shipping it
<steev> also, fwiw, juergh is the one that seems to have pulled in those patches :)
<freekurt[m]> steev: Is juergh cool? I don't know their reputation or the significance of them pulling the patches you reference.
<freekurt[m]> Or were you just pointing out that I was telling someone who pulled the patches in Ubuntu that patches were pulled in Ubuntu? lol
<steev> i think all devs are cool. i can't say i've had a ton of interactions with him, i'm just saying he's here in the channel, and is the someone who pulled in the patches. i just wanna make sure y'all have the venus firmware, if you have the venus patches because otherwise things don't work quite right (but it's slipping my mind on how it manifests... something about interconnects)