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
todi has joined #aarch64-laptops
todi1 has joined #aarch64-laptops
todi has quit [Ping timeout: 480 seconds]
hightower3 has joined #aarch64-laptops
<dgilmore>
robclark: the delay is blocking loading in the initramfs
hightower2 has quit [Ping timeout: 480 seconds]
<robclark>
dgilmore: I kinda suspect there are 1000 paths to fail when it comes to probe-defer, given the # of various dependencies... in x86 world it is all just acpi and you can take that for granted
<robclark>
(well, maybe not 1000 but a lot)
<dgilmore>
robclark: it's certainly not as straight forward as it should be
<robclark>
the arm approach of having a bunch of small drivers for a particular part of the SoC.. while cleaner, it does make things more complicated
<robclark>
it would have been easier if MS forced the ACPI route on windows laptops instead of the PEP thing.. maybe not better in the long run, but easier in the short term
<dgilmore>
It would be
hexdump0815 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
alfredo has joined #aarch64-laptops
alfredo has quit [Quit: alfredo]
<owc[m]>
<push> "owc: i've been trying to get a..." <- Yes, same for me. No luck w/ catching anything in the logs.
<owc[m]>
<push> "owc: Im confident is saying..." <- Interesting. I'm still on GNOME. So maybe the hw rendering then…
<owc[m]>
<push> "owc: i've been trying to get a..." <- Kinda same: 1.57, though I totally wiped windows, installed concept and upgraded to mantic.
iivanov has joined #aarch64-laptops
matalama_ has joined #aarch64-laptops
iivanov has quit [Remote host closed the connection]
iivanov has joined #aarch64-laptops
<danielt>
Can't believe I've had one for so long and am only asking this now... but is there a commonly used trick to get the MAC address of the X13s WiFi stable?
matalama_ has quit [Quit: Connection closed for inactivity]
<Bioxvirizm-x13s[m]>
<danielt> "Can't believe I've had one for..." <- +1
svarbanov_ has quit [Ping timeout: 480 seconds]
svarbanov has joined #aarch64-laptops
svarbanov has quit [Ping timeout: 480 seconds]
martiert_ has quit [Remote host closed the connection]
martiert has joined #aarch64-laptops
svarbanov has joined #aarch64-laptops
svarbanov has quit [Read error: Connection reset by peer]
svarbanov has joined #aarch64-laptops
svarbanov_ has joined #aarch64-laptops
alfredo has joined #aarch64-laptops
svarbanov has quit [Ping timeout: 480 seconds]
<mkrawczuk>
Hi!
<mkrawczuk>
I'm trying to launch the mainline kernel on a Samsung Galaxy Book S SM-W767. I noticed that many of the features are marked as working on postmarketOS. I built and launched the kernel from https://gitlab.com/jenneron/linux/-/tree/galaxy-book-s-6.1.2 on Armbian, but many components like wifi are not working. Is there any kernel or distro image that has better support for my device?
<clover[m]>
systemd override is what most are doing these days
<push>
owc[m]: try installing cinnamon and lightdm, then remove geoclue and all the gnome crap that depends on it, and make sure your linux-firmware is up-to-date
<push>
owc[m]: thats what ive done in the last few couple days and it hasn't reset once, unfortunately I don't know what I actually did that fixed it
<clover[m]>
oh oops you are talking about WiFi
<clover[m]>
idk about that one
<push>
probably just use nmcli to set the hwaddr right?
<danielt>
clover: No worries at all... I'm not currently using such an elegant approach for the BT MAC either so I shall probably switch over.
<Jasper[m]>
<robclark> "tbf, s/a never had much love for..." <- Hearing some noise that it's mostly bs anyways. I'm not going to bother taking it seriously.
jhovold has joined #aarch64-laptops
<jhovold>
danielt: i use a udev rule to set the mac address using ip
<jhovold>
ACTION=="add", SUBSYSTEM=="net", KERNELS=="0006:01:00.0", RUN+="/usr/bin/ip link set dev $name address xx:xx:xx:xx:xx:xx
<jhovold>
Bioxvirizm-x13s[m]: ^
<danielt>
jhovold: Sounds good. Thanks!
<jhovold>
dgilmore: i've posted a fix for the touchpad regression in 6.6-rc1 here:
<jhovold>
...until i have a fix or workaround i mean
<ukleinek>
the right place to set the macaddress is the dtb, but that has its own problems.
<travmurav[m]>
cooperative firmware should be fine with patching the dtb with board specific details like wifi/bt mac upon boot
<jhovold>
ukleinek: sure, but we don't control the fw
<jhovold>
we'll probably be able to read out the addresses at some point and set it from the drivers
<jhovold>
just need qualcomm to tell us how... or spend time figuring it out ourselves
<travmurav[m]>
pretty sure lenovo ships some kind of dtb loader nowdays in their efi? given they seem cooperative and as a board vendor they are the ones assigning the macs, it sounds sad if they can't make firmware pass it...
<travmurav[m]>
or did qcom invent something new to hide the macs now?
<jhovold>
the fw can load a dtb, but that's it currently
<jhovold>
still waiting on details so we can determine how to move forward wth this
<travmurav[m]>
well I still think it should be trivial to add a couple of libfdt calls on the loaded dt to insert macs from the firmware so if lenovo wants they should be able to implement it, though I have no idea what's really behind the x13s effort and what bureaucracy/qcom firmware mess may intervene...
<jhovold>
should be, but as you know this is a woa device and we're retrofitting linux support
<jhovold>
so things aren't always as easy they may seem
<jhovold>
as*
<steev>
truth
matalama_ has joined #aarch64-laptops
<travmurav[m]>
Well I get it, while considering something like aspire1 I'm working on, if anyone is ever to implement efi driver with sku detection/mac provisioning it would probably be me...
<travmurav[m]>
but not sure if I got wrong impression from lenovo adding that "linux mode" switch
jhovold has quit [Quit: WeeChat 4.0.4]
<konradybcio>
travmurav the issue with that approach is that only lenovo machines will be fixed
<konradybcio>
setting mac address from userspace is "normal" and that's why it's passed in android cmdline
<konradybcio>
userspace.. uh i meant HLOS
<travmurav[m]>
on the other hand every vendor has their own way of storing the macs I'd imagine
<travmurav[m]>
so if you are going to implement it in the kernel, it will be a total mess
<konradybcio>
my educated guesstimate is that it's in SMBIOS
<konradybcio>
saying that without checking though
<travmurav[m]>
konradybcio on aspire1 it's in EC and you need to tickle it properly to get the bytes out
<travmurav[m]>
so I really expect it to be a total mess across vendors
<travmurav[m]>
so IMO if it's possible for the bootloader to provision the mac via DT, it's reasonable to target that for a vendor that cooperates
matalama has quit [Remote host closed the connection]
hexdump0815 has quit [Quit: WeeChat 1.9.1]
hexdump0815 has joined #aarch64-laptops
alfredo has quit [Quit: alfredo]
matalama_ has quit [Quit: Connection closed for inactivity]
iivanov has quit [Remote host closed the connection]
pbsds has quit [Ping timeout: 480 seconds]
alfredo has joined #aarch64-laptops
alfredo has quit [Quit: alfredo]
erebion[m] has left #aarch64-laptops [#aarch64-laptops]