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
<steev> SUBSYSTEM=="net", ACTION=="add", ATTRS{vendor}=="0x17cb", ATTRS{device}=="0x1103", PROGRAM="/bin/ip link set %k address 00:00:00:00:00:00" (obviously change it to a valid mac) - create this as a udev rule file and use the correct vendor/device and you should get a static one (i grabbed the mac address that my X13s gets in windows)
hightower4 has joined #aarch64-laptops
<clover[m]> Im curious, why do people want these static mac addresses?
hightower3 has quit [Ping timeout: 480 seconds]
<HdkR> clover[m]: It's nice to be able to assign static IP addresses
<HdkR> Without static being set on the device itself
<bamse> when i look at the list of "known devices" in my google wifi thing, i have hundreds of known copies of my laptops...that's sufficiently annoying for me to want to fix the problem
<bamse> although i guess it doesn't itch enough...because then i would have fixed it by now...
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
baozich has joined #aarch64-laptops
<steev> my router sends me a notification every time a "new" device connects to it.... guess what happens every reboot during testing? :D
<steev> or happened
<bamse> steev: sounds like a wonderful feature :)
xroumegue has quit [Ping timeout: 480 seconds]
<steev> as someone who is paranoid about their network... it is :)
<bamse> i have a family on the same network...i have to be paranoid about my things on the network instead...
xroumegue has joined #aarch64-laptops
<steev> heh
enyalios_ has joined #aarch64-laptops
enyalios has quit [Ping timeout: 480 seconds]
alfredo has joined #aarch64-laptops
alfredo has quit [Quit: alfredo]
iivanov has joined #aarch64-laptops
iivanov has quit [Remote host closed the connection]
iivanov has joined #aarch64-laptops
matthias_bgg has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
iivanov has quit [Remote host closed the connection]
iivanov has joined #aarch64-laptops
baozich has quit [Quit: baozich]
baozich has joined #aarch64-laptops
baozich has quit [Ping timeout: 480 seconds]
hightower4 has quit [Ping timeout: 480 seconds]
mcbridematt has quit [Remote host closed the connection]
Amber_Harmonia has quit [Ping timeout: 480 seconds]
matthias_bgg has quit [Ping timeout: 480 seconds]
matthias_bgg has joined #aarch64-laptops
Amber_Harmonia has joined #aarch64-laptops
<agl7> clover[m]: I decided to reinstall the EndeavourOS. Also I want to use the BTRFS. Will probably come to you when I am ready and have questions.
<_[m]1> do full disk encryption ! it's super fun !! ๐Ÿ˜„
<_[m]1> I am running btrfs, but using zstd as compression
<agl7> _[m]1: ist the zstd compression good?
<_[m]1> I'm not the expert but as I read it, it's a mix of speed and compression effectiveness
<agl7> _[m]1: Thanks!
<agl7> _[m]1: How do you enable the full disk encryption? Must I do that at installation time?
iivanov__ has joined #aarch64-laptops
iivanov has quit [Ping timeout: 480 seconds]
iivanov__ has quit [Remote host closed the connection]
iivanov has joined #aarch64-laptops
<_[m]1> <agl7> "(โŠ™_โ—Ž): How do you enable the..." <- yes, you need to, but I was half joking since me and Jasper are experiencing reboot loop on fde pw prompt entry - but clover doesn't
<_[m]1> ez mode is to not include /boot, then you can follow arch linux guide easily
<_[m]1> just make cryptsetup volume, open it and continue from there
<_[m]1> but look at the Features part in ironrobin @clover wiki
<_[m]1> and adjust mkpcio conf and grub config for using the luks volume
enyalios has joined #aarch64-laptops
enyalios_ has quit [Ping timeout: 480 seconds]
iivanov has quit [Quit: Leaving]
fvogt has quit [Quit: leaving]
matthias_bgg has quit [Ping timeout: 480 seconds]
matthias_bgg has joined #aarch64-laptops
<steev> Jasper[m]: are you connecting to a 2.4ghz network or 5ghz?
<xnox> Ubuntu Mantic candidate images are available for testing for all Ubuntu architectures. And there is Ubuntu Desktop for arm64 x13s iso build http://iso.qa.ubuntu.com/qatracker/milestones/449/builds/288408/testcases on that page there is a list of test cases and a link to download the image. If there are successful installs of X13s this image will be released tomorrow
<xnox> officially. Everything is in the ubuntu archive main; no ifs no buts no ppas, it's just Ubuntu.
<xnox> fingerprint login works, wifi works, bluetooth needs public address set correctly, installer works, dual boot works, dual boot with bitlocker works (if one resizes bitlocker from windows, and uses manual partitioning), sound works, so everything is tip top.
<steev> oh nice
hightower2 has joined #aarch64-laptops
<xnox> i also have experimental plan that should work on creating "vmlinuz" that is a valid uk with vmlinuz & dtb, to allow booting it with secureboot
<xnox> i will experiment with that.
<Jasper[m]> <steev> "Jasper: are you connecting to a..." <- Not specified, my ssid's are the same across frequencies and ap's
<Jasper[m]> <xnox> "officially. Everything is in the..." <- Amazing, hope Fedora can follow soon
<steev> Jasper[m]: `iw dev wlan0 link` (replace wlan0 with whatever your wifi device is called)
<steev> xnox: what kernel are y'all using with mantic?
<xnox> steev: it is ubuntu 6.5 generic, plus a tonne of patches from linux-next, packaged as a separate flavour.
<steev> oh nice, they're going with 6.5
<xnox> which i have sign off to crank and update with stable & security updates every 2 weeks
<steev> heck yes, always love the sign offs
<Jasper[m]> <steev> "Jasper: `iw dev wlan0 link` (..." <- I'll try it out once I get it to boot :^)
<steev> ideally it would be when it's having issues with the wifi (and are you using any sort of usb devices)
<xnox> steev: the plan for 24.04 is that i can probably integrate all the things listed in the title topic into the just generic iso
<xnox> and i will continue to experiment with secureboot too
<Jasper[m]> <steev> "ideally it would be when it's..." <- Not using usb devices, due to the dependency on docks (kinda annoying imo). Getting wifi to be on the verge of losing connection is not too hard, will let you know.
<steev> i don't use docks, i just use usb-c cables
<bamse> xnox: very nice!
agl7_ has joined #aarch64-laptops
agl7 has quit [Ping timeout: 480 seconds]
<Jasper[m]> <steev> "Jasper: `iw dev wlan0 link` (..." <- 5GHz, on the AP that's the furthest away from me
<steev> So itโ€™s more that it isnโ€™t roaming onto the nearest AP?
<Jasper[m]> Seems like it, one sec
<Jasper[m]> Yes
<Jasper[m]> Neither is it frequency hopping
<Jasper[m]> Also I booted it up in the supposed blindspot and it connected to that ap, not to the two that are nearest to me
<bamse> Jasper[m]: i have this problem too, after taking a walk through the house it can take hours before my x13s decides to switch to the AP in my office...
mcbridematt has joined #aarch64-laptops
<Jasper[m]> Is it a userspace thing or a driver thing that decides it needs to switch?
<Jasper[m]> I know for some NIC's you can set it in Windows, haven't really found any of that in Linux
<bamse> i didn't manage to get a conclusive answer when i looked at this last...
<Jasper[m]> (for the record it works fine on most of my other devices)
<bamse> it seems to work as bad in windows for me...although i have limited testing there
<Jasper[m]> Let me ask an ath11k dude
<Jasper[m]> bamse: Yeah I had unrelated issues with the touchpad freezing intermittedly
<bamse> Jasper[m]: under some specific load?
<Jasper[m]> And I also destroyed the install by installing too many, unrelated to x13s, sc8280xp drivers
<Jasper[m]> bamse: Yeah, it also only happened while charging iirc
<bamse> if you have high irq-load in the system, then the input devices can become sluggish...but it's generally working pretty ok
<Jasper[m]> It does work fine on Linux if I have it booted luckily.
<Jasper[m]> Haha it roamed now because it's probably completely out of range now
<lun[m]> On a thinkpad x13s with kernel lenovo-x13s-v6.6.0-rc4 running `bootctl status > /dev/null` often causes the machine to hang for a second and then reset. Sometimes it causes `Failed to read boot option 0xsomehex` and doesn't hang.
<lun[m]> Seems like it's related to reading UEFI nvram.
<lun[m]> * with kernel steev/linux/lenovo-x13s-v6.6.0-rc4 running
<steev> qzed or jhovold might have a better idea than i wrt uefi nvram reading
<konradybcio> lun anything in dmesg when that happens?
<lun[m]> Not when it errors and continues, and when it resets I can't tell
agl7_ is now known as agl7
<lun[m]> Got [ 3917.501729] qcom_scm firmware:scm: qseecom: scm call failed with error -22 after another slightly different error Failed to read EFI variable LoaderDevicePartUUID: Input/output error