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
iivanov has joined #aarch64-laptops
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
iivanov has quit [Remote host closed the connection]
iivanov has joined #aarch64-laptops
<travmurav[m]>
jlinton: interesting... AFAICT after a quick look, btmgmt public-addr should read BE ("normal order") and converts it into LE bdaddr_t internally. Then it's passed on unchanged until it's sent to qca with qca_set_bdaddr_rome(). Notably on OLD qca based bt controller, mac address is set correctly. (mostly the same code path is used afaict)
ungeskriptet is now known as Guest11400
ungeskriptet has joined #aarch64-laptops
<travmurav[m]>
which means we can't just flip it in the kernel before sending - this will break other things
Guest11400 has quit [Ping timeout: 480 seconds]
jhovold has joined #aarch64-laptops
iivanov has quit [Remote host closed the connection]
iivanov has joined #aarch64-laptops
<Jasper[m]>
I think I've asked this before, but does anyone else have issues with roaming and connecting to other ap's with the x13s?
<Jasper[m]>
My range is terrible while I'm fine on my phone
<Jasper[m]>
dmesg is also full of authenticate associate deauthenticate lines
iivanov has quit [Remote host closed the connection]
iivanov has joined #aarch64-laptops
iivanov has quit [Remote host closed the connection]
iivanov has quit [Remote host closed the connection]
iivanov has joined #aarch64-laptops
iivanov has quit [Remote host closed the connection]
<neobrain>
Looks like my x13s can't charge from a usb-c dock. Is that expected?
<exeat>
My x13s is usually plugged into an "Anker 543 USB-C Hub (6-in-1, Slim)" and charging seems to work as expected
<exeat>
IIRC there were a couple of early (1.2x) bios versions with weird usb issues but it's been plain sailing ever since (though no >1G ethernet or external displays here)
<HdkR>
My X13s is also connected to a dock and charges correctly
<Jasper[m]>
Mine too, a cable matters dock
<HdkR>
When you plug in the power does the power LED blink three times without dock and with dock?
<Jasper[m]>
Afaik yes, will test it again in a sec
<javierm>
jhovold, ajhalaney[m]: most mutters devs are already on PTO for the holiday season, but I'll ping them again in early Jan
<javierm>
another option is to ask your distros to backport Jonas' patches to the stable released packages
<Jasper[m]>
@dgilmore I have another addition suggestion for the x13s package. Make wifi mac static aswell. It switches around too apprently
<neobrain>
hmm guess it must be this weird dell dock then
<neobrain>
actually no, my anker 6-in-1 hub doesn't charge it either, weird
<HdkR>
pd-mapper running?
<HdkR>
If it charges when shutdown which you can see if the power LED blinks three times when plugging it then it's a userspace or kernel problem
Caterpillar has quit [Quit: Konversation terminated!]
<Jasper[m]>
<Jasper[m]> "@dgilmore I have another..." <- I had to delete like 12 DHCP ip reservations from my router with its hostname hahahaha
<Jasper[m]>
Solved it with a udev rule: `ACTION=="add", SUBSYSTEM=="net|pci", KERNELS=="0006:01:00.0", RUN+="/usr/sbin/ip link set dev $name address AA:BB:CC:DD:EE:FF`
<Jasper[m]>
* address AA:BB:CC:DD:EE:FF"`
<neobrain>
HdkR: yeah, charging directly with a usb-c cable works fine
<neobrain>
will look at shutdown behavior later, maybe it's actually charging but just not telling userspace about it
<Jasper[m]>
<Jasper[m]> "My range is terrible while I'm..." <- Okay I checked, it keeps connecting to the 5GHz network of the sole wifi 6 capable AP on the other side of the house. Is there a way to prefer range instead or is it like that for everyone?
<jhovold>
javierm: thanks, it'd be best if upstream could do the backport, but asking the distros may be an option if for some reason that doesn't happen
<jhovold>
Jasper[m]: a semi random MAC is better than a static non-unique MAC in a distro
<Jasper[m]>
jhovold: These change on reboot right?
<jhovold>
yeah
<jhovold>
I think so anyway
<Jasper[m]>
Ah okay that's not too bad then
<Jasper[m]>
I stuck it to something so I don't have weird issues, but yeah
<jhovold>
makes perfect sense, but the user needs to provide a unique MAC (preferrably the one assigned to the device)
<jhovold>
until we've figured out how to do that from Linux
<jhovold>
s/do that/read out the assigned MAC/
<jhovold>
neobrain: I've head of at least one dock that fails to charge (an Apple one), but many seems to work
<jhovold>
the exact reason is yet to be determined, but an hypothesis is that it's related to role-switching not yet being supported
<Jasper[m]>
Biggest problem I currently have with wifi is that it refuses to connect to the ap with the best signal
<Jasper[m]>
Which is quite annoying since it fails to connect to the one it tries to connect to aswell
<Jasper[m]>
A different (Mediatek) nic works fine, don't think it's a configuration issue
<danielt>
Interestingly the Fedora folks are talking about defaulting to stable-but-randomly-assigned MACs everywhere (e.g. each SSID will see your machine with a different MAC): https://fedoraproject.org/wiki/Changes/WifiMACRandomization
<danielt>
It's not intended to workaround unassigned hardware MACs but will solve unstable DHCP addresses anyway·
<Jasper[m]>
Would at least solve my problem
<jhovold>
interesting indeed
<konradybcio>
that's the default on android nowadays, i think
<konradybcio>
and ios
<Jasper[m]>
Yes
<neobrain>
jhovold: ah, interesting
<neobrain>
of course, I can't actually reproduce it anymore now. reboot magically fixed it, though I'd definitely seen this other times before as well
<jhovold>
heh, ok, good to hear still I guess :)
<neobrain>
What I still see is that Plasma's systray only reacts to plug-in/out events like half of the time, hence not updating the "charging" indicator. But if you open the associated menu, it clearly does know whether it's charging or not. So it's a bit messy apparently, but at least not outright broken :D
<Jasper[m]>
@HdkR am I correct in assuming that installing packages in the respective fex-emu rootfs is impossible? You should be able to install it directly from rpmfusion in a fedora install
<Jasper[m]>
unbreak_chroot does not seem to work with the fexrootfsfetcher install of fedora 38
<HdkR>
Jasper[m]: Yea, unbreak_chroot.sh only works with the ubuntu rootfs on an ubuntu/debian system due to multi-arch shenanigans. I haven't solved that for Fedora or Arch rootfs images
<HdkR>
Would need to chroot in with an x86 host and copy the changes over
<Jasper[m]>
rip
<Jasper[m]>
Well, I'll download steam by hand then from rpmfusion instead of tencent hahaha
<Jasper[m]>
<HdkR> "Would need to chroot in with..." <- Any tips on getting a game running? There's the list obviously, but I'd love to test some stuff
<HdkR>
Jasper[m]: I usually just launch games through Steam
<Jasper[m]>
HdkR: Well I tried that and I either got greeted by nothing or a black screen
<Jasper[m]>
Assuming it crashed along the way
<Jasper[m]>
It's ULTRAKILL (awesome game btw)
<HdkR>
Huh, Steam black screening or the game?
<Jasper[m]>
The game
<Jasper[m]>
It did crash on its own now instead of hanging, terminal is full of stuff now
<HdkR>
I can't remember, do you have TSO emulation enabled in the config?
<Jasper[m]>
HdkR: `TSO Enabled` is checked
<Jasper[m]>
It's on x13s so I'm assuming it's emulation then?
<HdkR>
Yea, it's emulation
<HdkR>
Could be that Unity game is abusing something that we aren't expecting
<Jasper[m]>
Want some logs from somewhere?
<HdkR>
I'm guessing the logs would be a backtrace in the terminal?
<Jasper[m]>
HdkR: Well it's a bunch of ld.so related errors, but that's about the overlay
<HdkR>
Oh, that one is benign
<Jasper[m]>
I'll throw it up somewhere, do you want me to open an issue or just dm you here?
<HdkR>
That's just glibc complaining about stuff that doesn't matter
<HdkR>
You can throw me a gist or create an issue
<HdkR>
Unity games are fairly spicy, the garbage collector can make the JIT upset right now
<HdkR>
There are some plans to make that more stable but I haven't had a chance to get back to it. Deferring signals from the kernel is a bit spicy
<Jasper[m]>
HdkR: Oh yeah that's fair. It seemed like something that would probably run on this hw so it's not really that urgent
<Jasper[m]>
What did wonder if streaming could work in some way
<Jasper[m]>
Without ripping the pi steam link package lmfao
<HdkR>
Last I tested the Steam Link app worked fine, although it relies on CPU decoding of course
<HdkR>
Obviously wouldn't be wired up to use v4l2
<Jasper[m]>
<HdkR> "Could be that Unity game is..." <- Got a tip for downloading based on an appid, Steam doesn't allow downloading demo's from the interface if you bought it.
<Jasper[m]>
s/,/?/
<HdkR>
No idea on that one. I'm just a normal Steam user like anyone else :P
<travmurav[m]>
perhaps can download the depot via steam console?
<Jasper[m]>
HdkR: Yet? :p
<Jasper[m]>
travmurav[m]: A workaround would be to use "open" and use it as a link but that's not working I think
<Jasper[m]>
I am somehow having trouble shutting it down to restart with console enabled
<Jasper[m]>
@HdkR guessing you need host mesa version for the video driver?
<HdkR>
Without messing with thunk configs then it will be using the mesa version shipped in the rootfs. Which will be 23.3.0