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)
<gabertron> oh awesome.. and just found a set of headphones and it does work.. wow a linux device with two audio outputs both working.. I feel so alive!
hightower3 has joined #aarch64-laptops
sally has quit [Remote host closed the connection]
hightower2 has quit [Ping timeout: 480 seconds]
sally has joined #aarch64-laptops
<matalama> konradybcio: Its screen turned black after grub but did not reboot or shutdown. Maybe i need a usb2ethernet to check whether linux is booted but i think there's probably something wrong with backlight's description:(
<HdkR> n/15
<matalama> i simply copied pwm-backlight from x13s's dts
sally_ has joined #aarch64-laptops
sally_ has quit []
sally has quit [Ping timeout: 480 seconds]
sally has joined #aarch64-laptops
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
<travmurav[m]> matalama: did you define a display to use that backlight?
mjeanson_ has joined #aarch64-laptops
mjeanson has quit [Remote host closed the connection]
mjeanson_ is now known as mjeanson
agl7-x13s has quit [Quit: Leaving]
jhovold has joined #aarch64-laptops
iivanov has joined #aarch64-laptops
Cyrinux94 has quit [Ping timeout: 480 seconds]
martiert has quit [Ping timeout: 480 seconds]
Cyrinux94 has joined #aarch64-laptops
martiert has joined #aarch64-laptops
apalos has joined #aarch64-laptops
apalos has quit []
apalos has joined #aarch64-laptops
mani_s- has joined #aarch64-laptops
apalos has quit [Quit: ZNC 1.7.2 - https://znc.in]
mani_s- has quit []
bryanodonoghue4 has joined #aarch64-laptops
apalos has joined #aarch64-laptops
bryanodonoghue4 has quit []
apalos has quit [Quit: ZNC 1.7.2 - https://znc.in]
<matalama> travmurav[m]: Yes I did. I found it has a mipi panel different from x13s's edp panel
<travmurav[m]> matalama: hm, what is the device you have?
<travmurav[m]> but I'd expect Linux to shut the backlight off until the display is up
<matalama> Huawei matebook e go
<travmurav[m]> and if the device has a DSI panel, do you have a driver for it? :)
<travmurav[m]> oh, a tablet, interesting
<travmurav[m]> matalama: any chance there is FCC ID on it?
<matalama> I dont think it will be available in north america :(
<travmurav[m]> ah, right, huawei...
<matalama> but its a lovely tablet and has a reasonable price here in china
<travmurav[m]> just wanted to take a peak at the teardown photos
<travmurav[m]> matalama: did you dump the dsdt table already?
<matalama> yep
<travmurav[m]> Would you mind sharing a link?
<travmurav[m]> right, cool, it has an xml with the init sequence
<travmurav[m]> matalama: so, um, did you craft/generate a panel driver?
<matalama> no
<travmurav[m]> if you have no display driver but have the backlight, Linux will see that display is not up yet, since the driver hasn't loaded and would turn the backlight off
<travmurav[m]> so I suppose "great news" backlight works :D
<matalama> well, beyond my range :(
<travmurav[m]> not sure if this has some dsc/dual-dsi/etc magic but it might be fun to finally extend lmdpdg with windows-style xml inputs...
<Jasper[m]1> travmurav[m]: From what I saw with talkman it translates fairly well
<Jasper[m]1> Otherwise it might just be panel-edp like on the x13s
<travmurav[m]> I'd say more, there is (if qcom didn't delete it as they did other stuff) even a public doc for an older version of the xml
<travmurav[m]> but no, this seems to be a honest dsi panel
<matalama> i think maybe i can found a ready driver.
<matalama> i guess xiaomi pad 5 pro use the same panel.. hope they had commit the kernel source
<Jasper[m]1> matalama: There's a panel already submitted in a downstream repo
<travmurav[m]> "Sharp Dual DSI Video Mode Panel with DSC (1600x2560 24bpp)" sounds fun, also seems like the backlight is dsc so the pwm backlight on pmic would be wrong I'd say
<travmurav[m]> ... unless it's some cabc fun and they use both :/
<Jasper[m]1> <matalama> "i guess xiaomi pad 5 pro use the..." <- Likely not if it's the sharp
<matalama> it's not the sharp
<Jasper[m]1> From what I can tell the mi pad 5 pro has either a csot or a boe panel with a nt36523 controller
<matalama> it's from csot
<Jasper[m]1> matalama: Which one then and why?
<matalama> ppc357db1
<matalama> panelname in dsdt
<Jasper[m]1> That's the driver used on the mi pad 5 pro anyways
<matalama> thx :D
<clover[m]> srinik: how can i get my hands on one of those Qualcomm ASoC drivers that were updated 3 weeks ago per https://github.com/alsa-project/alsa-ucm-conf/commit/9bda3d15cc38bb705a1aa13f58adfea74bf37fe8
<clover[m]> i think im still using the old one, not sure how though cause i am on steev's 6.5.0-rc2
Cyrinux94 has quit []
Cyrinux94 has joined #aarch64-laptops
<clover[m]> ok, thanks
<clover[m]> Jasper: you still having audio issues?
<robclark> hmm, does SC8280XP-LENOVO-X13S-tplg.bin exist anywhere? Seems I managed to overwrite thumbdrive that I copied stuff from win11 partition to
<robclark> thx
<Jasper[m]1> @clover I think you @'d me to ask if I still have audio problems. The answer is yes, but it's not that it doesn't work. It just cuts out for fractions of a second at a time and audibly tries to catch up (it feels like it's going fastforward)
<Jasper[m]1> Not sure if it's userspace or the kernel messing up though
<clover[m]> try running pacman -Syu and see if you still have issues please
<clover[m]> also can i see your /usr/share/alsa/ucm2/Qualcomm/sc8280xp/HiFi.conf?
<clover[m]> preferable before you do the pacman
<Jasper[m]1> Will fetch it
<Jasper[m]1> <clover[m]> "try running pacman -Syu and..." <- btw I haven't upgraded to the rc kernel, do I need to do that first?
<clover[m]> dont think so
<clover[m]> havent tested there though
<Jasper[m]1> <clover[m]> "also can i see your /usr/share/..." <- https://paste.centos.org/view/ec413643
<Jasper[m]1> <clover[m]> "try running pacman -Syu and..." <- same problem
<Jasper[m]1> Also volume doesn't actually scale anymore
<Jasper[m]1> Actually that might be a me problem, one sec
<Jasper[m]1> Jasper[m]1: Okay yeah that was
<Jasper[m]1> But the cutting in and out and it then trying to catch up is still a probpem
<Jasper[m]1> *problem
<Jasper[m]1> Also it seems to stab to a higher volume from time to time
<steev> robclark: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/qcom/sc8280xp/LENOVO/21BX it's also here, though it appear it's just called audioreach-tplg.bin upstream
<robclark> ahh.. so I guess that means that patches in jhovold's branch are looking for the wrong thing?
<steev> it was only somewhat recently submitted and accepted
<robclark> ahh, and doesn't appear in fedora's linux-firmware yet..
<steev> 2023-06-28
<steev> was when it got added upstream
<robclark> so probably just a matter of time..
<robclark> at least what I have now seems to work
<steev> clover[m]: also... i'm using the same drivers as you... it sounds like something else somewhere, is different
<steev> oh, i see
<HdkR> The x13s did the USB problem again!
<HdkR> `Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=r8152, 480M` That's supposed to be 5000M
<HdkR> I saw some logs this time which might explain it
<HdkR> https://gist.github.com/Sonicadvance1/9f3a4ee86bc02c316a187f24f7d73c81#file-kern-log-L679 Actually usb 1-1 claims it is fine. The hub in the other port also freaked out and is only running at 480M as well
<HdkR> There's some probe failure which I'm not sure is related
<HdkR> Maybe I still have the WWAN port set to disabled
<HdkR> Additional information in the comments of that gist
<HdkR> It seems like for some reason the USB 2.0 devices on the bus got enumerated before the USB 3.0 ones?
<HdkR> Since in the original dmesg, usb 1-1 detects the new device. usb 2-1 has zero log until unplug and plug back in.
<HdkR> Could be related to USB 3-1 throwing an absolute fit
jhovold has quit [Ping timeout: 480 seconds]
pbsds is now known as Guest6456
pbsds has joined #aarch64-laptops
Guest6456 has quit [Ping timeout: 480 seconds]
iivanov has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
<Jasper[m]1> Interesting, fwupd got an update for the fingerprint scanner
<Jasper[m]1> Is that something you can install on x13s without problems?
<clover[m]> i use my scanner all the time, yeah. its been supported in linux since 6.4
<clover[m]> maybe 6.3 i dont remember
<Jasper[m]1> clover[m]: I don't necessarily mean using the scanner, but updating the firmware
<clover[m]> oh idk
<clover[m]> i would assume its fine
<Jasper[m]1> Huh interesting, I think I found a nice graphics bug
<Jasper[m]1> Fluffychat has some weird colors
<Jasper[m]1> big and little endian I presume, green is fine
<clover[m]> pichu froze! :(
<Jasper[m]1> clover[m]: I wonder why it does that
<Jasper[m]1> I'm not running into this problem anywhere else atm
<clover[m]> flutter weirdness maybe?
<Jasper[m]1> Could be
<Jasper[m]1> Has to be endianness I think
<Jasper[m]1> kinda weird though, it's not transparent to KDE so it has to be flutter
<Bioxvirizm-x13s[m]> <clover[m]> "maybe 6.3 i dont remember" <- Is there any instructions on how to run it? The scanner?😕
<clover[m]> Bioxvirizm-x13s: https://wiki.archlinux.org/title/Fprint
<steev> Jasper[m]1: if you mean prometheus 10.01.3333223->3478575 update, yeah, i did it here without issue using fwupd
<Jasper[m]1> Yes! Okay good to know, thanks!
<steev> i actually just uploaded the report to them so they have a success note
<steev> but iirc, konrad said it worked first
hexdump01 has quit [Quit: WeeChat 1.9.1]
hexdump0815 has joined #aarch64-laptops
<hexdump0815> ungeskriptet: travmurav[m]: another little update - i have now linux-stable v6.4.3 plus the changes from travmurav[m] and ufs support working on my samsung galaxy book go
<hexdump0815> i can see the 6 ufs devices with lots of partitions and can read them - things look good, so i guess writing to them will work too - will test that over the weekend
<hexdump0815> travmurav[m]: i'll try to move to ufs over the weekend then - just to verify my plan is correct: shrink win11 partition on win11 with the disk tool there
<hexdump0815> then putting an esp and the partitions i want into the free space/gap created - esp marked as efi partition in fdisk for instance (or better not use fdisk?)
<hexdump0815> then putting my working grub from usb into the esp and copy the install over to the created ufs partitions
<hexdump0815> will the esp/efi partition then already be visible in efi config/bios? or is some other magic required for it to appear there?
<Jasper[m]1> <steev> "i actually just uploaded the..." <- Updated aswell, ended up working fine indeed
<Jasper[m]1> That's pretty cool