ChanServ changed the topic of #aarch64-laptops to: Linux support for AArch64 Laptops (Asus NovaGo TP370QL - HP Envy x2 - Lenovo Mixx 630 - Lenovo Yoga C630)
e1eph4nt has quit [Ping timeout: 480 seconds]
e1eph4nt has joined #aarch64-laptops
e1eph4nt has quit [Ping timeout: 480 seconds]
e1eph4nt has joined #aarch64-laptops
e1eph4nt has quit [Ping timeout: 480 seconds]
e1eph4nt has joined #aarch64-laptops
e1eph4nt has quit [Ping timeout: 480 seconds]
e1eph4nt has joined #aarch64-laptops
<clover[m]> They release a no-jdk tarball yeah
<bamse> steev: sc8280xp uses rpmh, which has an mmio interface...platforms prior to 845 instead has the rpm (non-(h)ardened), were linux communicates with the rpm co-processor using messages sent over smd or glink - which in linux is abstracted using the rpmsg framework
<steev> ahh
<bamse> steev: we do however use glink (exposed through rpmsg) to communicate with the adsp and cdsp
<bamse> steev: so for battery manager, altmode driver and audio support you rely on rpmsg et al
<steev> got it, okay cool
e1eph4nt has quit [Ping timeout: 480 seconds]
e1eph4nt has joined #aarch64-laptops
e1eph4nt has quit [Ping timeout: 480 seconds]
e1eph4nt has joined #aarch64-laptops
hexdump0815 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
klardotsh has joined #aarch64-laptops
jhovold has joined #aarch64-laptops
e1eph4nt has quit [Ping timeout: 480 seconds]
e1eph4nt has joined #aarch64-laptops
e1eph4nt has quit [Ping timeout: 480 seconds]
e1eph4nt has joined #aarch64-laptops
e1eph4nt has quit [Ping timeout: 480 seconds]
e1eph4nt has joined #aarch64-laptops
e1eph4nt has quit [Ping timeout: 480 seconds]
e1eph4nt has joined #aarch64-laptops
e1eph4nt has quit [Ping timeout: 480 seconds]
owlman has joined #aarch64-laptops
e1eph4nt has joined #aarch64-laptops
e1eph4nt has quit [Ping timeout: 480 seconds]
matthias_bgg has joined #aarch64-laptops
e1eph4nt has joined #aarch64-laptops
Penguinpee_ has joined #aarch64-laptops
Penguinpee has quit [Ping timeout: 480 seconds]
srinik has quit [Killed (NickServ (Too many failed password attempts.))]
srinik has joined #aarch64-laptops
e1eph4nt has quit [Ping timeout: 480 seconds]
e1eph4nt has joined #aarch64-laptops
e1eph4nt has quit [Ping timeout: 480 seconds]
e1eph4nt has joined #aarch64-laptops
e1eph4nt has quit [Ping timeout: 480 seconds]
e1eph4nt has joined #aarch64-laptops
e1eph4nt has quit [Ping timeout: 480 seconds]
e1eph4nt has joined #aarch64-laptops
e1eph4nt has quit [Ping timeout: 480 seconds]
e1eph4nt has joined #aarch64-laptops
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
MobileSuitMajicStarGundamPower has joined #aarch64-laptops
e1eph4nt has quit [Ping timeout: 480 seconds]
e1eph4nt has joined #aarch64-laptops
e1eph4nt has quit [Ping timeout: 480 seconds]
e1eph4nt has joined #aarch64-laptops
e1eph4nt has quit [Ping timeout: 480 seconds]
e1eph4nt has joined #aarch64-laptops
<clover[m]> cool, my M720 logitech mouse + receiver working great with x13s and the solaar app. sometimes i have to manually restart it after suspend for my rule to work (thumb button->gnome activities overview)
<clover[m]> this little pinephone dock works well so far
<bamse> clover[m]: is that bt or some proprietary dongle?
<clover[m]> its a logitech usb reciever
<clover[m]> i don't think we have kernel support for bluetooth on the x13s yet
<bamse> no, not yet...i'm relying on a usb/bt dongle for that
<bamse> that works fine though
<clover[m]> oh really, let me try
<clover[m]> yes, my bt dongle but the signal isnt as strong as the usb dongle
<clover[m]> bt dongle works*
<bamse> well, that's not the x13s' fault
<clover[m]> thanks for the tip ;) this is really huge for me. im going to try my bt speakers now
<clover[m]> my buds seemed to be too much for it, caused a crash
<bamse> odd, that should just be generic/non-x13s code involved
<bamse> anything useful in the logs?
<clover[m]> in meeting will check later
e1eph4nt has quit [Ping timeout: 480 seconds]
falk689_ has joined #aarch64-laptops
falk689 has quit [Ping timeout: 480 seconds]
<steev> bamse: silly question, but would it really be this simple to add 0x81 notifications to the battery? https://paste.debian.net/1252963/ it *seems* to work here, but i dunno if i'm missing something (and the battery info reported does seem to be correct?)
e1eph4nt has joined #aarch64-laptops
<bamse> steev: yes, but i suspect that the NOTIFC_BAT_INFO: should be moved down to NOTIF_BAT_PROPRETY
<bamse> steev: but the only issue is that we might currently read the battery info more often than necessary
<travmurav[m]> Is qca bluetooth (the one in the 7c wcn) supposed to support two connections at the same time?
<travmurav[m]> Noticed that I can't connect both bt sound and a mouse at the same time
<bamse> travmurav[m]: yes, i've been using it on sc8180x to connect to both keyboard and mouse at least
<travmurav[m]> Hm, will need to see if there are some logs I suppose
<travmurav[m]> Or sweep this all under the rug by figuring out how to connect the realtek codec and the adsp-based sound
<travmurav[m]> as I've recently figured out that 7c can re-use sm8250 sound almost as-is
<travmurav[m]> (for the times when one forced to use the adsp that is)
<clover[m]> bamse: when i plug in my adapter with a usb-c->usb-a dongle: https://pastebin.com/tGt0hCnt
<steev> that looks like missing firmware itself
<clover[m]> package x13s-firmware-20220815-0 is up to date
<steev> bamse: i'll try that
<steev> clover[m]: the brcm firmware isn't thinkpad specific
<bamse> clover[m]: but that firmware should be completely unrelated to the x13s, as it's a generic dongle
<steev> that would likely be firmware-brcm or maybe bluez-firmware
<bamse> what steev said :)
<steev> bamse: i'll try moving it here and see what happens :)
<travmurav[m]> Hm, interesting, seems like for me it can actually connect 2 or even 3 devices at once, just not reliably and with some fiddling...
<bamse> steev: worst case you won't notice in time that the charge counter went up
<bamse> steev: until you get that 0x81 instead - which hopefully will come when that happens
<bamse> steev: it's not going to matter, it only affects the almost static data points, such as voltage at full charge and charge counter
<clover[m]> thanks guys, everythings working perfect once i found the right firmware
<bamse> steev: so perhaps if you have a long uptime you might miss the fact that your battery has degrated slightly
<clover[m]> galaxy buds work too!
<bamse> steev: the outcome would be that it reports full charge below 100%
<clover[m]> get this if you want bt on x13s
<steev> bamse: hm, so maybe leave it where it was then
<bamse> steev: no
<bamse> steev: i was just guessing, but this is a better guess
<steev> i'll let em run for a bit (testing on both flex and x13s) - but the x13s is at full, and the flex is at 54%
matthias_bgg has quit [Quit: Leaving]
<steev> seems to be fine so far though
<steev> bamse: would you like an email with my test bits? so it's somewhere public and doesn't get lost (main thing being the splat when trying to modprobe -r the battery)
<clover[m]> steev can you re-link your mutter patch?
<steev> sure, one moment
<steev> https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2577/diffs?commit_id=642791673c345bd1432f97d6b7c5e4632e01f2fd - but, if you're using wayland, you'll want to keep https://gitlab.gnome.org/GNOME/mutter/-/issues/2398 in mind (i've not tested Robert's thought, to blacklist msm from atomic)
<clover[m]> nice, added BT and mutter stuff to [arch feature support](https://github.com/ironrobin/archiso-x13s/wiki/Feature-Support)
<clover[m]> hey Leo Shen if i make a pkgbuild with a patched mutter would you add it to your repo?
<szclsya[m]> is it a drop in replacement & how would it handle dependency with gnome?
<steev> szclsya[m]: should be a drop-in replacement, it's just a patch to mutter, realistically, it should be applied at some point (it's in main, backported to 42 and 3.38)
jhovold has quit [Ping timeout: 480 seconds]
<steev> oh spiffy, a machine driver
<steev> well, v2 of it
e1eph4nt has quit [Remote host closed the connection]
e1eph4nt has joined #aarch64-laptops
e1eph4nt has quit [Ping timeout: 480 seconds]
e1eph4nt has joined #aarch64-laptops
klardotsh has quit [Ping timeout: 480 seconds]
pierro78 has joined #aarch64-laptops
e1eph4nt has quit [Ping timeout: 480 seconds]
Penguinpee_ has quit [Remote host closed the connection]
e1eph4nt has joined #aarch64-laptops
Penguinpee_ has joined #aarch64-laptops
jelly has quit [Ping timeout: 480 seconds]
Manis[m] has joined #aarch64-laptops
e1eph4nt has quit [Ping timeout: 480 seconds]
e1eph4nt has joined #aarch64-laptops
klardotsh has joined #aarch64-laptops
jelly has joined #aarch64-laptops
jelly has quit [Read error: Connection reset by peer]
jelly-hme has joined #aarch64-laptops
pierro78 has quit [Remote host closed the connection]
<clover[m]> Is this the mutter suspend bug lol
<steev> i haven't seen that one on the x13s, can you ssh in to it?
<steev> i've seen that on the c630, occasionally
<steev> typically the mutter bug is that if you're in GNOME+wayland, mutter will crash, and kick you back to gdm, and gdm will only offer to let you use Xorg
<steev> but that happens pretty quickly after plugging in the adapter
<derzahl> do we have a solid fix for c630 booting up without keyboard input? Seems to be plaguing me quite a bit lately
<steev> do not know what causes that at all derzahl, because typically when that happens, keyboard isn't even available at grub
<derzahl> dang, was hoping someone figured out how to end it once and for all
<derzahl> steev: is c630-6.0.0-rc4 from your github seeming reasonably stable now?
<steev> uhhhh
<steev> aside from audio, yeah
<derzahl> i havent been having much luck building any recent kernel, failing right away on devicetree stuff so still on 5.17
<derzahl> wanted to try again and see if anyone can help
<steev> what is wrong with your compiler
<steev> even the kernel ci uses clang to test iirc
<derzahl> ill stick with your 5.19 if that is a better choice. mostly want the efivars fixes
<derzahl> well...let me try again. maybe i did something stupid
<derzahl> but i dont think i changed anything recently
<steev> my 5.19 has broken gpu for some reason
<steev> i'm trying to come up with a 6.0 that includes x13s, c630 and flex5g in it
<derzahl> oh dang, and suggestions on version to use then?
<steev> i'm uing the 6.0.0-rc4 and dealing with no audio
<steev> i really have no idea why it doesn't work because message output wise... it should
<derzahl> ok, ill try
<derzahl> been getting these devicetree errors ever since i tried to build 5.19 vanilla after getting compiler errors using clang on your 5.19
<derzahl> lets see what happens this time
<steev> give me the command you're running to build it?
<clover[m]> Works on xorg as long as I don't suspend
<clover[m]> If I suspend everything turns blue
<clover[m]> It doesn't like booting while connected. Once I get to gdm it seems safe to connect
Penguinpee_ is now known as Penguinpee
<clover[m]> I seem to be blocked from loading the evdi module for DisplayLink support with the x13s kernel:... (full message at https://matrix.org/_matrix/media/r0/download/matrix.org/cKGGOGEPTvyiHTXaOPDPCNyL)
<clover[m]> I have linux-x13s-headers installed
<steev> it might need changes for 6.0
<steev> yep
<steev> you can try that patch in there, although i'd probably change up the ifs instead of just straight adding the patch in there as it
e1eph4nt has quit [Ping timeout: 480 seconds]
e1eph4nt has joined #aarch64-laptops
e1eph4nt has quit [Ping timeout: 480 seconds]
e1eph4nt has joined #aarch64-laptops
MajicStarHaloAssasins has joined #aarch64-laptops
MobileSuitMajicStarGundamPower has quit [Ping timeout: 480 seconds]
<derzahl> ok, i seemed to fix my compile problem but not sure how
<derzahl> so if i enable the qcom scmi stuff will I be able to just use efibootmgr as normal?
<derzahl> or is there more to it?
<clover[m]> <steev> "you can try that patch in there,..." <- that did work
MajicStarHaloAssasins has quit [Remote host closed the connection]