01:26 <freekurt[m]> can anyone confirm for me that I don't need to keep a local copy of windows for my x13s in order to update the firmware or find a mac address or get some blob in the future? i want to nuke windows completely without a backup. is that a poor decision for any reason?

02:17 <craftyguy> I nuked my windows install asap (never booted it), I haven't noticed anything worse than having windows

02:18 <FarchordSteveCossette[m]> craftyguy: I needed it to get firmware offa it

02:19 <FarchordSteveCossette[m]> But if we're talking about the Snapdragon X1 laptops, I'd say it's really not in a state right now where you can run without windows

02:19 <FarchordSteveCossette[m]> Things are way too unstable as it stands.

02:43 <craftyguy> I've been using fw from linux-firmware + extracted from lenovo dl site. It there some other fw that can only be had from windows? IIRC there are ways to get fw from windows update without running windows?

03:03 <robclark> so fw falls into two camps.. stuff loaded from kernel (ie /lib/firmware) and bios.. at least on x13s (but I think it should work on other things) there was a way to install fw updates without windows

03:03 <robclark> and for x13s lenovo pushed everything else to linux-firmware

03:04 <robclark> ofc I'm failing now to find the instructions for bios update.. iirc there where on github somewhere

04:02 <craftyguy> robclark: I've used this in the past to upgrade EFI fw on the x13s without windows https://gitlab.com/TheOneWithTheBraid/x13s-firmware-update

04:04 <craftyguy> ohh there was an EFI fw update posted this week for the x13s... anyone try it yet?

04:05 <craftyguy> 1.61

04:06 <craftyguy> change log seems kinda boring, just 1 "security update" listed

05:13 <dgilmore> robclark: https://pagure.io/arm-image-installer/blob/main/f/update-x13s-bios will make a usb disk to update the bios. it should be in arm-image-installer in fedora

05:14 <dgilmore> though looks like it is mising

07:30 <sera[m]> <FarchordSteveCossette[m]> "How can I see which modules..." <- I didn't put any modules in the initramfs, pretty much just set everything to builtin. You can see what's enabled by checking /proc/config.gz

08:03 <danielt> Yay! mutter-46 just landed in Debian Trixie. That means gnome-shell/wayland is now working out of the box for multi-monitor set ups (and as far as I can tell the visual glitch on workspace switching that made multi-monitor close to unuseable is fixed too).

09:14 <steev> si

12:27 <kalebris> what's the best way to check what is using power (like powertop) that works on arm64 (x13s)?

12:45 <TSIN[m]> hi

12:50 <konradybcio> kalebris: you can't really do much here, there's no hardware to measure the current consumption onboard

12:50 <konradybcio> only what's flowing out of the battery

12:50 <TSIN[m]> Is there any tutorial or post about installing linux on surface pro 11 or xelite laptops?

13:00 <FarchordSteveCossette[m]> <TSIN[m]> "Is there any tutorial or post..." <- I haven't seen anyone do anything on the surface pro 11 personally

13:20 <Painkiller995[m]> Farchord (Steve Cossette): Can you provide more information about the project? I have been checking GitHub, but I haven't found much activity there. I discovered these rooms through GitHub, but I'm still not sure where to find more information.

13:21 <FarchordSteveCossette[m]> Painkiller995[m]: The information is generally splattered a bit everywhere. A Decent amount of effort has been made on the Yoga laptop, but you really have to simply scrounge up in the channel history

13:21 <FarchordSteveCossette[m]> We're still in the discovery phase tbh, nothing is 100% usable. I personally think it's inadvisable to nuke your Windows install as things stand.

13:22 <FarchordSteveCossette[m]> We're very much still in the discovery phase.

13:23 <FarchordSteveCossette[m]> i.e. this is a good way to get the wifi running. I'm trying to make it work on Fedora but I think there's something about the way Fedora builds it's kernel that stops this from working

13:23 <FarchordSteveCossette[m]> https://pastebin.com/vJEGy5RD

13:25 <FarchordSteveCossette[m]> Joske has written a good little walkthrough for arch here: https://gist.github.com/joske/52be3f1e5d0239706cd5a4252606644b

13:26 <FarchordSteveCossette[m]> I honestly just think we should just setup 1 repo where we dump all the information required to make our respective laptops working

13:26 <FarchordSteveCossette[m]> But as things stands, there's bits and pieces of infos peppered a bit everywhere

13:35 <Painkiller995[m]> Farchord (Steve Cossette): This is the issue new members here are facing, or maybe it's just me. Thanks for the info, by the way. I saw a screenshot of your Vivobook running Linux. Is there a guide or something on how you did that? Which kernel build and configuration did you use?

13:37 <FarchordSteveCossette[m]> Painkiller995[m]: Right now I don't have anything solid. .sera gave me an image he built of archlinuxarm which makes it boot perfectly (without sound mind you), and wifi works. I don't have a definite guide as I'm still investigating myself. I'm personally working hard right now on transferring the stuff I learn from that image over to Fedora

13:37 <FarchordSteveCossette[m]> But as it stands, my Fedora image has no keyboard and mousepad support, so I gotta use an external mouse/kb

13:38 <FarchordSteveCossette[m]> Sound as I understand it is currently a no-go

13:38 <FarchordSteveCossette[m]> on my laptop, USB-A ports also don't work (If I remember right, Asus used a chipset that other vendors didn't for their USB-A ports, hence why they dont work)

14:48 <freekurt[m]> <craftyguy> "I nuked my windows install asap..." <- thx for the feedback! going to nuke today. thx for all the pmOS work you are doing. were you able to get the camera working in a browser yet? i tried building Libcamera with softIPA but i kept running into build errors. is that needed?

14:49 <KieranBingham[m]> freekurt: For camera in a browser, then yes you need libcamera for x13s

15:01 <freekurt[m]> Kieran Bingham: thanks! do I have to build it myself or are there any releases somewhere? i couldn't find them. i've never used alpine before and they don't really provide good build instructions on the libcamera website.

15:03 <KieranBingham[m]> freekurt: Well - if the libcamera build instructions aren't suitable - that's my fault.

15:03 <KieranBingham[m]> What do you need to be fixed?

15:03 <KieranBingham[m]> But yes - you should be able to use a libcamera release from your package manager as long as it's version 0.3.0 or 0.3.1

15:04 <KieranBingham[m]> https://libcamera.org/getting-started.html git clone https://git.libcamera.org/libcamera/libcamera.git cd libcamera meson setup build ninja -C build install

15:05 <KieranBingham[m]> the tricky part of building yourself is installing to the right place, and having all the right dependencies.

15:05 <freekurt[m]> Kieran Bingham: i don't think it is an issue of being unsuitable, it is just that i am not used to converting all the names of debian packages into alpine packages so that i have all the correct dependencies before building. this is my first time using alpine.

15:05 <KieranBingham[m]> I see you're on pmos ... I'm sure there's a pmos libcamera package.

15:05 <KieranBingham[m]> You'll also need to have pipewire ... and run firefox-nightly.

15:05 <travmurav[m]> https://pkgs.alpinelinux.org/package/edge/community/aarch64/libcamera

15:06 <travmurav[m]> freekurt: you can probably just pick up the makedepends from APKBUILD for alpine

15:06 <travmurav[m]> ("git repository" link in above one)

15:08 <travmurav[m]> but I believe the packaged one should work and I thiiink it was tested in pmOS on few qcom devices

15:10 <freekurt[m]> KieranBingham[m]: i was unaware that all i needed was to make sure the libcamera package was 3.0 or above. i thought building it locally was a requirement due to this being a fork or something.

15:11 <freekurt[m]> travmurav[m]: thanks!

15:11 <KieranBingham[m]> I've used x13s for several video calls now. But please bear in mind this is still fairly early development ;-) - the support for firefox only gets into firefox 129 - and firefox 128 was only just released.

15:11 <KieranBingham[m]> (hence nightly builds required)

15:12 <freekurt[m]> are the colors expected to improve at some point on the x13s camera?

15:12 <KieranBingham[m]> freekurt: 'improve' yes ;-) But how much depeneds on what you're starting from and what you've tried so far

15:13 <KieranBingham[m]> But otherwise - it's being actively developed (the softisp) and I'll probably handle some tuning phase when the softisp matures to handle parameterised CCM's

15:13 <KieranBingham[m]> you said 'improve' so what have you used so far to see a picture on x13s ?

15:14 <KieranBingham[m]> At the moment it's quite usable for video calls - but it's like having a webcam from 2000

15:20 <freekurt[m]> i haven't tried video calls yet. just gnome camera.

16:21 <lollaritits[m]> im trying to run GUI apps through FEX Emu but it fails at the mesa driver

16:21 <lollaritits[m]> does anyone know how to get it working

16:32 <lollaritits[m]> i always end up on this error 'MESA-LOADER: failed to open msm: libLLVM-17.so: cannot open shared object file: No such file or directory (search paths /usr/lib/dri, suffix _dri)'

16:33 <travmurav[m]> lollar (it/its): are you trying to run fex on alpine host?

16:33 <lollaritits[m]> nope archlinux

16:34 <travmurav[m]> mhm

16:34 <lollaritits[m]> host and rootfs

16:34 <lollaritits[m]> i can open stuff like wine explorer

16:34 <lollaritits[m]> or this steam update window

16:34 <lollaritits[m]> but thats about it

16:35 <lollaritits[m]> rootfs is update

16:54 <\[m]> did anyone maybe contact lenovo to ask where the higher end SKUs are? I might just do it now myself

16:58 <robclark> lollaritits[m]: normally you'll need an x86 build of mesa in the fex chroot/container thing.. but HdkR is the resident expert

17:12 <lollaritits[m]> <robclark> "lollar (it/its): normally you'll..." <- how would i get that?

17:14 <robclark> I think fexemu has chroots to download for different distro's which should include mesa

17:28 <ektor5> lollaritits[m]: you probably are using the Archlinux rootfs

17:29 <ektor5> use Ubuntu24.04 instead

17:43 <JensGlathe[m]> Has anybody got an idea where to look? I get this constantly since 6.10, but only on the box running EL2

17:43 <lollaritits[m]> <ektor5> "use Ubuntu24.04 instead" <- doesnt work at all :/

17:55 <ektor5> lollaritits[m]: ? I'm using it, the llvm problem is caused from an update in Arch, Ubuntu24.04 works fine for me because version is fixed

17:56 <ektor5> you may need to use `export MESA_LOADER_DRIVER_OVERRIDE=zink`

17:58 <lollaritits[m]> i got a 2001 game to run

17:58 <lollaritits[m]> but without sound

17:58 <lollaritits[m]> weirdly sound works in winecfg

18:04 <FarchordSteveCossette[m]> <JensGlathe[m]> "Screenshot from 2024-07-26 19-41..." <- That's not a bug, that's a feature. (Don't worry that's "normal", you can ignore it)

18:17 <lollaritits[m]> <lollaritits[m]> "i got a 2001 game to run" <- i think the random generator is broken on linux

18:18 <lollaritits[m]> the output is very weird

18:18 <lollaritits[m]> i get the same all the time

18:24 <colemickens> Do I need to do anything special to get x1e mesa going? I think I need to use zink, but I think it's going to do that by default since the new mesa pr isn't merged yet.

18:26 <robclark> you'll want the MESA_LOADER_DRIVER_OVERRIDE=zink env var... just don't forget to remove it after the branch is merged

18:27 <robclark> or if you are building mesa, just build it from the PR. I'm down to just a handful of remaining fails, so probably it will be ready to merge later today or over the weekend

18:27 <colemickens> nice, thanks.

18:48 <lollaritits[m]> <ektor5> "you may need to use `export MESA..." <- failed to load driver: zink

18:48 <lollaritits[m]> that just gives me this

19:17 <FarchordSteveCossette[m]> Urgh.... everytime I update dracut to add files to the initramfs, the root drive no longer mounts

19:17 <FarchordSteveCossette[m]> I have no idea why

19:18 <FarchordSteveCossette[m]> and keyboard and mouse still aren't loading

20:33 <HdkR> lollaritits[m]: Sounds like the archlinux rootfs borked somehow since llvm-17 wasn't able to be found. If you're running on an X1E device then you'll need to use zink until the Freedreno stuff lands

20:34 <lollaritits[m]> im running on X13S

20:34 <lollaritits[m]> just as a fun side note

20:34 <lollaritits[m]> zuma deluxe (random childhood game) does run

21:19 <vk6[m]> so i bought the asus vivobook s15 with the x elite recently, and i was wondering how i could compile a working kernel for it. so far, everything i've tried has resulted in a black screen right after the early kernel startup. i noticed that the device tree for it seems to rely on some firmware binaries i can't seem to find anywhere (qcom/x1e80100/ASUSTeK/vivobook-s15/qcadsp8380.mbn and some others). does anyone know where i could get

21:19 <vk6[m]> these files? my end goal is to get debian sid working on this device

21:24 <robclark> some of the fw you'll need to copy from windows

21:26 <vk6[m]> where is the firmware located in windows?

21:26 <vk6[m]> also, i just found this github repository that seems to have the right files, so i think i'll just download them from there https://github.com/Seraphin-/linux-firmware-x1e80100-vivobook

21:27 <robclark> I don't remember the windows path offhand.. I just disabled bitlocker and mounted from linux and used find

21:29 <vk6[m]> i did a quick search in file explorer and that seems to have worked

21:30 <robclark> fwiw, someone posted this earlier: https://gist.github.com/joske/52be3f1e5d0239706cd5a4252606644b

21:30 <robclark> looks like the closest thing to instructions that anyone has had a chance to write up yet

22:26 <amstan> Thanks!

22:27 <amstan> ... One of these days

22:27 <amstan> Most of those steps look familiar, I actually have another way, but it's good to get the corner cases documented

23:50 <colemickens> lmao I just disabled SB on a Copilot+ laptop and windows just happily booted right up

23:50 <colemickens> wait these arent FDE'd? I thought MS was doing bitlocker on all win11 devices now

23:50 <colemickens> wtaf

23:51 <HdkR> The Yoga 7x that I got had Bitlocker enabled at least

23:51 <colemickens> weird just grabbed one in vancouver and it seemingly doesn't. sure enough, no usual bitlocker icon or anything

23:53 <colemickens> bummer, saw systemd-boot menu and then black screen :(

23:53 <vk6[m]> my asus vivobook s15 also had bitlocker on by default

23:53 <colemickens> I actually think it powered off even

23:54 <vk6[m]> i believe you have to compile your own kernel (with the right drivers built in), add the right firmware to the initramfs, and specify the correct device tree through grub

23:55 <vk6[m]> though i havent gotten it working lol

23:55 <colemickens> i'm using abelvesa's kernel, have a custom devicetree line in my systemd boot config entries

23:55 <colemickens> should be good to go

23:57 <colemickens> interesting, definitely some sort of screen flash

23:57 <colemickens> any other kernel params I need to consider

23:57 <colemickens> ?

23:57 <vk6[m]> i'm not sure about what custom kernel parameters to use

23:58 <vk6[m]> but you can try boot_delay=500 to see if you can figure out where it's crashing

23:59 <colemickens> Exiting boot services, then sometimes a "screen flash" then nothing