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
hightower4 has joined #aarch64-laptops
hightower3 has quit [Ping timeout: 480 seconds]
checkfoc_us has quit []
checkfoc_us has joined #aarch64-laptops
rz has quit [Ping timeout: 480 seconds]
hexdump0815 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
jglathe_x13s has joined #aarch64-laptops
hightower3 has joined #aarch64-laptops
hightower4 has quit [Ping timeout: 480 seconds]
hightower3 has quit [Ping timeout: 480 seconds]
ema has quit [Quit: Changing server]
ema has joined #aarch64-laptops
jglathe__ has joined #aarch64-laptops
jglathe_ has quit [Ping timeout: 480 seconds]
<pstef> Fedora Rawhide 6.8.0-0.rc7.20240307, x13s - I was expecting audio to be quiet but there is no audio device detected at all
<ukleinek> no audio device is a special case of "audio is quiet"?!
<Jasper[m]> <pstef> "Fedora Rawhide 6.8.0-0.rc7.20240..." <- Weird, let me grab my device real quick
<Jasper[m]> It worked before
<pstef> it's very possible that I messed up
<Jasper[m]> pstef: Anything you suspect?
<pstef> not really, it's one of those unknown unknowns
<pstef> I still boot the kernel with "arm64.nopauth clk_ignore_unused pd_ignore_unused rd.driver.blacklist=msm"
<Jasper[m]> <pstef> "Fedora Rawhide 6.8.0-0.rc7.20240..." <- Turns out I branched off to fc40
<Jasper[m]> So I probably can't reproduce in general
<Jasper[m]> But I'm updating right now, we'll see
hightower2 has joined #aarch64-laptops
svarbanov has quit [Remote host closed the connection]
svarbanov has joined #aarch64-laptops
svarbanov has quit [Remote host closed the connection]
svarbanov has joined #aarch64-laptops
<pstef> jlinton: I had installed your x13s package, but the battery indicator didn't work until I installed pd-mapper, qmic, qrtr, rmtfs (can't remember which were already installed and of those not yet installed which were required) and restarted pd-mapper
<pstef> I also installed acpi for good measure
<pstef> now after a reboot I can see it doesn't start up properly, but it's easy to get it working with systemctl restart. So maybe it was the restart that fixed it then, not packages installation
<albsen[m]> <pstef> "now after a reboot I can see..." <- your missing the devices in the initramfs - once they're in it the device shows up (for me)
<albsen[m]> also, make sure u use a custom kernel - u can use the general build instructions for fedora
<pstef> I was hoping to avoid compiling kernels
ak-coram has joined #aarch64-laptops
<ak-coram> hey, did anyone manage to boot the shipped Windows 11 OS from an USB drive on the X13s? I've used the official recovery USB, mirrored whatever that did to an USB SSD, but after the initial setup I get a BSOD with the message "inaccessible boot device"
<jglathe_x13s> ak-coram that's my experience too with virtually any Windows 11 machine. I managed to set up a bootable installer from USB, but booting an actual install from USB... tried a few times, but never managed. Regardles of x86 or aarch64.
<ak-coram> jglathe_x13s: maybe they don't like that for some reason? I've read about some regedit changes that make the usb 3 drivers load sooner
louist103 has joined #aarch64-laptops
<louist103> Hi all. Got an update. Gnome is installed. However, I don't have sound, a GPU, and the network is kinda unstable. It works for a but then disconnects with error 5 or 11. Is it safe to assume these are because I may have gotten bad drivers from the gitlab repo and taking them from my actual windows install will fix it?
<steev> sound is a kinda known issue. gpu should work though (you may be missing firmware if you don't have the gpu though, it should be something like qkmsuc850.mbn)
<steev> i've not seen the network errors here, it has been quite stable
<steev> jhovold (for when you're around): 6.7.9 doesn't seem to throw the AER correctable errors on suspend, so far
<pstef> GPU is just copy the file under /lib/firmware/yadda/yadda or is that not enough?
<louist103> How do I fix sound? or is there just no sound?
<louist103> I did also notice that I can't use wayland with gnome but thats fine IMO cause I never actually use it on my other machine.
<louist103> I noticed I have something called "wpa_gui". Maybe its conflicting
jglathe_sdbox2 has joined #aarch64-laptops
vadikas[m] has joined #aarch64-laptops
jglathe_sdbox2 has quit []
<albsen[m]> <pstef> "I was hoping to avoid compiling..." <- I've tried that too, but in the end, the only way for you to get a reasonable experience on ur device is with a custom kernel at the moment. Here is the guide to do that on fedora (I recall u used fedora), by the way it's trivial on fedora and very streamlined in my opinion. https://docs.fedoraproject.org/en-US/quick-docs/kernel-build-custom/
Lucanis has quit [Ping timeout: 480 seconds]
Lucanis has joined #aarch64-laptops
<pstef> I plan to do it for some time, but I hope eventually all the good stuff will be in Linus's tree and trickle down to me from there
<albsen[m]> pstef: its trivial, trust me. just replace the part of the tutorial from the kernel.git source with which ever you want to run. I personally am on: https://github.com/jglathe/linux_ms_dev_kit.git with branch jg/blackrock-v6.7.y
<albsen[m]> and to get the config, I used: make devkit_defconfig LOCALVERSION="-jglathe-20240129"
<albsen[m]> this might be outdated now, I can see other commits are added
jglathe_sdbox2 has joined #aarch64-laptops
<pstef> thanks, I had chosen https://github.com/jhovold/linux/tree/wip/sc8280xp-v6.8-rc6 and now I'm configuring the kernel build
matthias_bgg has quit [Quit: Leaving]
matthias_bgg has joined #aarch64-laptops
<jenneron[m]> bamse_: hi. i've tried upstreaming my lenovo flex 5g patches, but there has been no activity for a month. do i have to do anything to get it further?
jglathe_ has joined #aarch64-laptops
jglathe_sdbox2 has quit [Read error: No route to host]
jglathe_sdbox2 has joined #aarch64-laptops
louist103 has quit [Remote host closed the connection]
louist103 has joined #aarch64-laptops
louist103 has quit []
louist103 has joined #aarch64-laptops
<louist103> New discovery with the wifi. It only seems to fail when doing a lot of downloading at once, IE emerging a package. normal web browsing is fine.
<louist103> When using my phone hotspot I can emerge i3 and its associated packages first try, when using my normal wifi it fails every time
matthias_bgg has quit [Quit: Leaving]
louist103 has quit [Remote host closed the connection]
jglathe_sdbox2 has quit [Remote host closed the connection]
jglathe_sdbox2 has joined #aarch64-laptops
jglathe_sdbox2 has quit [Ping timeout: 480 seconds]
jglathe_sdbox2 has joined #aarch64-laptops
louist103 has joined #aarch64-laptops
<louist103> Another interesting development. 2.4GHz works just fine. Its 5 GHz that is the problem.
jglathe_x13s has quit []
jglathe_sdbox2 has quit []
jglathe_ has quit [Remote host closed the connection]
jglathe_ has joined #aarch64-laptops
louist103 has quit [Remote host closed the connection]
louist103 has joined #aarch64-laptops
<adamcstephens> 6.8-rc7 has been quite stable for me when it comes to an external monitor. except when i wake the laptop back up and the monitor is plugged in. then i need to re-plug to get the external monitor to display
systwi has quit [Remote host closed the connection]
<_[m]123> i've had 2 crashes today, didn't find much in the logs
adamcstephens has quit [Remote host closed the connection]
adamcstephens has joined #aarch64-laptops