ChanServ 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
chrisl has quit [Ping timeout: 480 seconds]
Melody91 has joined #aarch64-laptops
tobhe has joined #aarch64-laptops
hexdump01 has joined #aarch64-laptops
hexdump03 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
tobhe_ has quit [Ping timeout: 480 seconds]
hexdump02 has quit [Ping timeout: 480 seconds]
<steev>
bryanodonoghue: have you tried showtime on a gnome desktop on x13s? i can't seem to seek forward in videos, and i'm not sure if its venus or not; i suppose booting a kernel without venus would tell me that, so let me try that
<steev>
yeah, i'm able to jump around in videos without venus
<steev>
i used yt-dlp to download https://www.youtube.com/watch?v=Wjrdr0NU4Sk and it's a vp9(video)/opus(audio) video and can bounce around in it, as soon as i try to seek with venus, showtime just locks up and i have to force quit it, but there's nothing in the kernel logs
hexdump0815 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
eluks has quit [Remote host closed the connection]
eluks has joined #aarch64-laptops
kalebris_ has joined #aarch64-laptops
kalebris has quit [Ping timeout: 480 seconds]
kalebris_ is now known as kalebris
jhovold has joined #aarch64-laptops
ungeskriptet_ has joined #aarch64-laptops
ungeskriptet has quit [Ping timeout: 480 seconds]
kalebris_ has joined #aarch64-laptops
davidinux has quit [Quit: WeeChat 4.3.1]
masked has quit [Quit: leaving]
kalebris has quit [Ping timeout: 480 seconds]
kalebris_ is now known as kalebris
martiert has quit [Quit: WeeChat 4.5.1]
martiert has joined #aarch64-laptops
<sgerhold>
HdkR: DP/HDMI audio is/was already working somewhat at least on X1E CRD half a year ago or so. If you add the right stuff to audio topology, alsa UCM and DT you can probably make it work. I think it was close to being merged, or even partially merged already, but then it got reverted again due to some unresolved userspace integration issues.
ungeskriptet_ has quit [Ping timeout: 480 seconds]
ungeskriptet has joined #aarch64-laptops
srinik has joined #aarch64-laptops
JosDehaes[m] has joined #aarch64-laptops
<JosDehaes[m]>
anyone else have instant reboots all the time on yoga 7x?
davidinux has joined #aarch64-laptops
<Grabunhold>
no instant reboots on my x13s so far, not very helpful but at least you don't feel like you're talking to the void I guess?
<JosDehaes[m]>
thx anyway 🙂. I didn't have this some months ago, but now, it reboots just out of the blue (with fs corruption every time of course). Had it on 6.11, 6.13 and 6.14 kernels.
<JensGlathe[m]>
WCN7850?
<JensGlathe[m]>
This is a source of a lot of grief in 6.14
<JosDehaes[m]>
well, I built a 6.13.0 to test, and same. Also booted an old 6.11 kernel (that worked before I think), but still same. I used to have these issues when using lazygit in the past, but now it reboots at any random point
<JosDehaes[m]>
oh and have it on Arch and also on stock ubuntu concept kernel
<JosDehaes[m]>
* on Arch (self built kernel) and also
<JensGlathe[m]>
hmm. I remember a lot of complaints when changing AP
<JensGlathe[m]>
On my box WiFi is disabled bc of it
<JosDehaes[m]>
I can try that to narrow down the issue
<JosDehaes[m]>
but if it happens on all of these kernels, wouldn't it rather point to firmware issue?
<JensGlathe[m]>
You could try my 6.14.0-31-jg-2 from googledrive
<JensGlathe[m]>
Yes, or some hardware fluke
<JosDehaes[m]>
don't have the windows ssd with me today
<JosDehaes[m]>
of course there's nothing in the logs as the reboot is so sudden
<JosDehaes[m]>
now tried to disable wifi, and had a kernel oops
<JosDehaes[m]>
and now reproduced on 6.11 with wifi disabled
<Grabunhold>
huh, FS corruption on almost every random reboot? and you're talking the bad "data lost" kind, not the "fs logs replayed or whatever, everything dandy in the grand scheme of things" kind of corruption?
<JensGlathe[m]>
Then its def something else
<JensGlathe[m]>
do you see something in journalctl -b -1
<JosDehaes[m]>
no actual fs corruption, like files corrupt, fish history, or even installed packages (crash during upgrade)
<JosDehaes[m]>
JensGlathe[m]: nope
<JensGlathe[m]>
Argh
<JensGlathe[m]>
How hard do you usually push it
<JosDehaes[m]>
s/no//
<JosDehaes[m]>
this can happen at any time, like editing a file or something
<JosDehaes[m]>
and at other times, it's fine to compile a kernel
<JensGlathe[m]>
do you have some special stuff in your dt, tried to enable something others don't have?
<JosDehaes[m]>
I have bluetooth, ec, and rtc enabled
<JosDehaes[m]>
can try without that
<JensGlathe[m]>
ec
<JosDehaes[m]>
this was an old patch from macc24, maybe it is now giving issues
<JosDehaes[m]>
oh but on ubuntu, I'm using just the stock kernel, pretty sure they don't have that
<JensGlathe[m]>
not sure def
<JensGlathe[m]>
they have loads of odd stuff, and iirc the EC is part of it
<JosDehaes[m]>
oh
<JosDehaes[m]>
well, rebooted now without the EC
<JosDehaes[m]>
and hop crash
<JosDehaes[m]>
was just resizing a window
<JosDehaes[m]>
now rebooted without the RTC patch
<JosDehaes[m]>
and now different behaviour: lockup but no reboot
<JosDehaes[m]>
ah reboot after a while 😅
<JensGlathe[m]>
This awfully sounds like hardware issue
<JosDehaes[m]>
yeah
<JosDehaes[m]>
will test tonight with the windows SSD
davidinux has quit [Ping timeout: 480 seconds]
<macc24>
Jos Dehaes: any logs?
<macc24>
i don't think my ec driver is even able to force a reboot
<jhovold>
JosDehaes[m]: try with my wip branch first, which is known to be mostly stable (e.g. modulo some known mainline issues)
<jhovold>
there are too many patches floating around
number0ne_ has joined #aarch64-laptops
number0ne_ has quit [Quit: Konversation terminated!]
ravikant_ has joined #aarch64-laptops
<kuruczgy[m]>
I am using both the old EC driver and the nvmem rtc patch and I don't have any issues
<bryanodonoghue>
steev have you confirmed /proc/interrupts venus is bumping ?
<bryanodonoghue>
ATM Firefox dma buf API for example doesn't work with venus
<bryanodonoghue>
you can see the IRQ count increment as the API interrogates the hw
<bryanodonoghue>
but then decode is done in sw as the API bugs out on the dma buf handle
<bryanodonoghue>
so I wonder if you can confirm showtime is actually in-use with venus on gnome
<JosDehaes[m]>
<jhovold> "Jos Dehaes: try with my wip..." <- latest test was with your wip test + bluetooth patch
<JosDehaes[m]>
* latest test was with your wip 6.14 branch + bluetooth patch
<JosDehaes[m]>
<macc24> "Jos Dehaes: any logs?" <- nope
sudeepholla has quit [Quit: Ex-Chat]
<jhovold>
JosDehaes[m]: ok, good, but if you're the only one seeing this with the yoga I guess it could indicate a hw issue too
<jhovold>
kuruczgy[m]: that's an out-of-tree patch you use for dp on the yoga, just skimmed it, but you have at least one bug in there for the retimer that sometimes fails to probe
<jhovold>
the retimer regulator pinconfig should be using function "normal" not "func1" for the enable signals
<jhovold>
looks like it was copied from one of the early revisions adding support to the crd/t14s
<jhovold>
as I remember pointing it out during review
<jhovold>
maybe not the cause of the probe failures, but it should be fixed up
<kuruczgy[m]>
jhovold: thanks for looking at it. Is the t14s dp altmode support merged already? I guess I should re-adapt the newer version for the yoga
<jhovold>
it was merged for 6.15, but the dt changes didn't make it in this cycle so should show up in 6.16
davidinux has joined #aarch64-laptops
<anthony25>
JosDehaes[m]: I have the bluetooth patch + EC on jhovold's 6.14, and I don't have these crashes
<anthony25>
on which bios is the laptop?
<robclark>
fwiw only problem I've been seeing on my 7x (6.14-rc6 still) is wifi sometimes locking things up when I switch networks (which I believe is a known issue)
fantom has joined #aarch64-laptops
<HdkR>
sgerhold: Tying all the loose ends together for audio over DP/HDMI is hard for me. :)
<sgerhold>
HdkR: I think I managed to get it working at some point, but the integration into the sound settings on e.g. Gnome was really weird
<travmurav[m]>
was the problem different from the one I had on older platforms where the dp port driver would -einval (iirc) the audio device "as to not touch unclocked IP" when the cable is not plugged, or the problem is different on newer things?
<travmurav[m]>
as in, PA would disregard the ucm profile with a failing device when it boots with the cable unplugged, but would work fine if PA booted when the cable was in, and then jack detection would work fine
djakov has quit [Remote host closed the connection]
djakov has joined #aarch64-laptops
srinik has quit [Ping timeout: 480 seconds]
<HdkR>
sgerhold: I see. I still didn't have external display working anyway, so if audio over it is still having problems then eh
ravikant_ has quit [Remote host closed the connection]
ravikant_ has joined #aarch64-laptops
ravikant_ has quit [Ping timeout: 480 seconds]
<steev>
bryanodonoghue: yes it bumps; before playing video `249: 7 0 0 0 0 0 0 0 GICv3 206 Level venus` and after trying to seek `249: 583 0 0 0 0 0 0 0 GICv3 206 Level venus`
<steev>
it isn't just showtime either though, totem had the same thing, so potentially it's gstreamer that has issues? i can move back and forth in videos in both mpv and in vlc
todi1 has joined #aarch64-laptops
todi has quit [Ping timeout: 480 seconds]
checkfoc_us9 has quit []
checkfoc_us9 has joined #aarch64-laptops
checkfoc_us9 has quit []
checkfoc_us9 has joined #aarch64-laptops
<steev>
bryanodonoghue: additionally, booting without venus, as mentioned, playback is as expected, can seek forward and back without issue since its all being done in software
hexdump03 has quit []
hexdump0815 has joined #aarch64-laptops
jhovold has quit [Ping timeout: 480 seconds]
EdLin has joined #aarch64-laptops
<EdLin>
what is the most compatible Snapdragon X laptop or should I avoid those altogether at present?
<EdLin>
best supported I mean
<EdLin>
I currently have a MS Surface Pro SD X Plus model and it's not supported very well yet, also have an old Lenovo Flex that is very slow and too old.
<gwolf>
Many among us are more than happy with our snapdragons
<gwolf>
... But many among us also like tinkering with our computers🙃
<EdLin>
gwolf: I can't really write my own GPU drivers, which is what's necessary for the SP11 X Plus model
<EdLin>
I don't mind some tinkering but writing GPU drivers is a bit above my expertise level. I'm an IT guy, not a systems programmer yet. :)
<EdLin>
Maybe I could get the X Elite one, but I didn't like its screen with the pen support messing up its OLED for some reason.
<EdLin>
(no pen support in Linux, just is the screen gets a bit grainy)
<robclark>
hamoa (the 10 core x1p or 12 core x1e) is in better shape for gpu.. purwa (8 core x1/x1p) will come but it might be a few months
<EdLin>
I see, and my XP one is 8 core?
<EdLin>
if it's just coming rather than never that'd be OK
<EdLin>
I should have looked at the github issues tab before purchasing this model
<robclark>
it won't be never... but I can't say exactly when.. It shouldn't be massive change, but will need a small bit of information from qc
<EdLin>
I'd assumed that since Arch (modified) was almost working perfectly it'd be OK for me.
<EdLin>
ok
<EdLin>
I'll wait some, possibly though tarrifs will make my decision for me. lol
<EdLin>
thanks
EdLin has quit [Quit: WeeChat 4.1.1]
pbrobinson has quit [Ping timeout: 480 seconds]
ravikant_ has joined #aarch64-laptops
ravikant_ has quit [Remote host closed the connection]
<bryanodonoghue>
steev are you playing just a regular h264 file ?
ravikant_ has joined #aarch64-laptops
<steev>
bryanodonoghue: that one in particular was vp9, but it happens with any, although looking, i only seem to have avc, vp9 and webm available locally, i can try to grab a h264 or convert to h264
ravikant_ has quit [Ping timeout: 480 seconds]
<bryanodonoghue>
steev yep pause/resume works but sliding the bar breaks
<steev>
yeah, that's what i see here :(
<bryanodonoghue>
i'll log a bug in our linaro db to track
<steev>
thank you!
<bryanodonoghue>
just accept the cadence of the space/time continuum - don't mess with the temporal mechanics of the timeline with the slidebar
<bryanodonoghue>
teachable moment
<bryanodonoghue>
actually I may as well report the bug to linux-media
<steev>
i use mpv and vlc as workaround, just usually forget on the first launch (since showtime is the default app for media in gnome)