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
erebion has quit [Remote host closed the connection]
enyalios has joined #aarch64-laptops
enyalios_ has quit [Ping timeout: 480 seconds]
baozich has joined #aarch64-laptops
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
<travmurav[m]> jhovold: Nice! Confirmed that it fixes the qca used with sc7180 too and left t-b on the list
<travmurav[m]> jhovold: if you were looking into local-bd-address dt prop, does this mean someone figured out where macs are stored on x13s? :)
<steev> jenneron[m]: sorry, i JUST got home, so i'll give it a spin later when i wake up
<konradybcio> travmurav: on the sticker on the bottom of the laptop ;)
<travmurav[m]> xD
<travmurav[m]> but is it?
<travmurav[m]> aspire1 only has it on the box lol
<steev> if my thinkpad had it on there... it's definitely gone by now, it wiped off long ago
<jenneron[m]> steev: unfortunately 6.6.x has problems with UFS and bluetooth..
<jenneron[m]> i backported my changes to 6.1.69 lts kernel, you can find the branch in my fork
<steev> i'll give that a try tomorrow^W later instead
<steev> now i'm off to bed for reals
baozich has quit [Ping timeout: 480 seconds]
jhovold has joined #aarch64-laptops
<jhovold> travmurav[m]: thanks for testing
<jhovold> unfortunately still waiting on details on how to retreive the MAC addresses
baozich has joined #aarch64-laptops
baozich has quit [Ping timeout: 480 seconds]
jglathe has joined #aarch64-laptops
jglathe has quit [Ping timeout: 480 seconds]
jglathe has joined #aarch64-laptops
systwi has quit [Ping timeout: 480 seconds]
jglathe has quit [Ping timeout: 480 seconds]
systwi has joined #aarch64-laptops
systwi has quit [Ping timeout: 480 seconds]
systwi has joined #aarch64-laptops
<craftyguy> I've noticed that the BT range on the x13s is really short, like about 1-2 meters with a headset that is normally usable from much farther away on other devices. is this a known issue?
systwi has quit [Ping timeout: 480 seconds]
<steev> kind of known? as in, i see it here, and i don't know what causes it
<exeat> I had a similar problem [1] and found that either replacing firmware hpnv21.bin with hpnv21.b8c (from e.g. [2]), or having both plus that (dropped?) kernel patch [3] that probes the board id, gives much improved BT range.
<steev> the kernel patch was dropped because the version that made it into the kernel... doesn't work properly for me
<steev> i work on it here and there
<steev> but my only bluetooth headset are the airpods and they are a huge pita to get working
systwi has joined #aarch64-laptops
<exeat> As far as I could see that patch selected which firmware to load... so I ended up dpkg-diverting firmware-atheros's .bin and replacing it with a symlink to the .b8c that would have been loaded (with the patch applied)
<steev> for the record, i'm the steev that wrote that patch
<steev> that file comes from windows, and lenovo/qualcomm never submitted it upstream either, unfortunately (that's why you have to find it in clover[m]'s repo); but oddly with the new patch, i'm just always getting a boardid of 0, which defaults to the .bin
<steev> exeat: can you give me your dmesg | grep Bluetooth
<exeat> Yup, I'm glad you wrote that patch. It definitely loaded the "other" hpnv21 on my x13s.
<craftyguy> exeat: hmm I see, so I should try using that other bt firmware
<exeat> If you try it and it works better, I will begin to hope that maybe I can get rid of my fw diversion kludge at some point :)
systwi has quit [Remote host closed the connection]
jhovold has quit [Ping timeout: 480 seconds]
<steev> since it's reporting a boardid of 0 now, instead of the previous 8c... i'm not sure how to force it, yet
<Dantheman825[m]> I guess GPU hangs still like rear their head every now and then on this thing
<HdkR> That's the new hang that is all the rage now that the other GPU registers are programmed correctly
<Dantheman825[m]> Ah
<Dantheman825[m]> That hang triggered when I was testing Splatoon 2 on Ryujinx
<Dantheman825[m]> It happens on a few others
<robclark> "cx gdsc didn't collapse" == "gpu reset didn't work".. I more or less know what is going on but haven't figured out how to convince runpm to actually cut the power when I need it to
<craftyguy> exeat: is that kernel patch necessary or could I just use a symlink to load the fw?