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)
baozich1 has joined #aarch64-laptops
baozich has quit [Read error: Connection reset by peer]
<travmurav[m]>
-517 should be EPROBE_DEFER aka "should try again later" so maybe it just loads later?
<juergh>
ah yes. guess so. but what is the correct order I wonder?
<travmurav[m]>
it would be something like "initfs has msm but not display panel driver so it tries and fails until rootfs is mounted" kind of problem I'd guess
<juergh>
the panel driver is in the initrd but something it depends on must be missing.
<juergh>
the dependencies are really obscure. at least to me :-)
<travmurav[m]>
qcom_pmic_glink pmic-glink: Failed to create device link sounds fun, maybe you lack some rpmhpd stuff? I'm not so familiar with the modern platforms
<travmurav[m]>
at least quick look at the place that errors out makes me think it fails creating the connector, and the connector attached to those failing displayport-controllers are pmic_glink_con(0|1)_ss aka type-c ones under pmic-glink
<jhovold>
juergh: i've listed the display deps in the commit message for johan_defconfig
<travmurav[m]>
so might be as simple as some driver not in the initfs or even "msm" loads before "glink" causing a short glitch
<juergh>
jhovold: yes. those I have included and try to load in that order
<jhovold>
you still need to load the panel driver manually before the drm driver if you want to avoid the probe deferral due to the msm drm driver being broken
<jhovold>
the problem is that the drm driver does not look up the panel during probe as it should, but rather during component bind, which is much too late
<juergh>
jhovold I try to but it looks like it goes the other way around
<jhovold>
I use:
<jhovold>
cat /etc/modules-load.d/drm-msm.conf
<jhovold>
# This is enough to avoid the bind "probe" deferral
<jhovold>
panel-edp
<jhovold>
msm
<jhovold>
juergh: the following error suggests that you have a bad backport:
godvino has quit [Read error: Connection reset by peer]
godvino has joined #aarch64-laptops
godvino has quit [Quit: WeeChat 3.6]
baozich has quit [Quit: baozich]
baozich has joined #aarch64-laptops
baozich has quit [Quit: baozich]
baozich has joined #aarch64-laptops
baozich1 has joined #aarch64-laptops
baozich has quit [Remote host closed the connection]
baozich1 is now known as baozich
matthias_bgg has quit [Ping timeout: 480 seconds]
baozich has quit [Quit: baozich]
matthias_bgg has joined #aarch64-laptops
baozich has joined #aarch64-laptops
baozich has quit []
baozich has joined #aarch64-laptops
baozich has quit [Ping timeout: 480 seconds]
init_x13s has joined #aarch64-laptops
hightower4 has quit [Ping timeout: 480 seconds]
baozich has joined #aarch64-laptops
baozich has quit [Ping timeout: 480 seconds]
baozich has joined #aarch64-laptops
<init_x13s>
I had this weird problem where the x13s would drain it's battery while fully shutdown. I did a factory reset of the bios, it wiped the boot table and I had to reinstall grub, but the problem seems to have cleared. Hard to explain why, but for som reason it did the job.
<HdkR>
It'll still happen
<init_x13s>
least explainable fix I've applied recently
<init_x13s>
My understanding is that it's related to some MS sleep state under shutdown..
<HdkR>
Wouldn't really matter if you just hard turn it off.
<init_x13s>
how do you "hard" turn it off
<HdkR>
Hold the power button for ten seconds
<init_x13s>
that's a better solution than hotwiring a switch on the battery wires. I'l try that.
<HdkR>
Still slowly drains in this case. So it doesn't really solve anything
<init_x13s>
someone also seemd to suggest to hold shift while powering down, any opinion on that?
<HdkR>
Never heard of anything like that
baozich has quit [Ping timeout: 480 seconds]
<jhovold>
init_x13s, HdkR: is this when shutting down from windows or linux?
<init_x13s>
linux
<jhovold>
i think someone reported this when shutting down windows as well (e.g. before having even installed linux)
baozich has joined #aarch64-laptops
<HdkR>
jhovold: Well a power button hold down isn't really a shutdown. Would be hard for the hardware to care at that point
<jhovold>
right, and it happens after such a hard power-off as well, you say?
<HdkR>
Indeed
<init_x13s>
If it makes any sense for any of you. Whatever I did (Except a hard shutdown as described by hdkr) , the laptop would drain it's battery under 3 days while shut down. no exception, and it has been like that for months. Someone suggested I just reset the bios to factory default, which I thought was a bit silly, but in the end, was cheap to try. And since then, I rarely notice the battery drop over a few days.
<init_x13s>
when it's shut down.
<init_x13s>
I might not need an explanation, until the problem comes back
<init_x13s>
ehe
<jhovold>
ok, thanks for the summary. Have not noticed anything myself, but then I tend to keep mine connected to the charger
<jhovold>
init_x13s: are you running the latest bios btw?
<init_x13s>
I tend to move a lot during a day, power management is part of my daily struggle.
<init_x13s>
yes, the laptop was sent to lenovo to fix the keyboard issue and came back last week with "new keyboard installed, new bios installed"
<jhovold>
ok, good to know
<init_x13s>
they did re-image it with windows also.
<init_x13s>
just DD'ed my backup on top of the drive.
<jhovold>
that's just rude...
<init_x13s>
to be fair, I wiped the HD before sending it in.
<init_x13s>
they had to test it in some ways
<jhovold>
ah, so you've dropped windows completely?
<jhovold>
kept a small partition around for fw updates. too small to update windows it turned out though...
<init_x13s>
yes I dropped win. I use a live bootable windows usb key for updates.
<init_x13s>
a bit hackish but it works reasonably well
baozich1 has joined #aarch64-laptops
baozich has quit [Ping timeout: 480 seconds]
baozich1 is now known as baozich
baozich has quit [Ping timeout: 480 seconds]
init_x13s has quit [Remote host closed the connection]
hightower2 has joined #aarch64-laptops
agl7 has joined #aarch64-laptops
hightower2 has quit [Ping timeout: 480 seconds]
<agl7>
xnox: Do you produce a final release of Ubuntu 23.04 for the ThinkPad X13s Gen1?
<steev>
travmurav[m]: the device link thing is... new-ish, and whatever it is was backported to 6.2 too
<steev>
it's probably a valid issue but i have no idea
<agl7>
Hello steev :-)
<steev>
hi
<clover[m]>
hello steev
<steev>
hello ironrobi
<steev>
n
bluerise has joined #aarch64-laptops
bluerise_ has quit [Ping timeout: 480 seconds]
<clover[m]>
dont give up my alter ego
<steev>
hi clover[m]
<clover[m]>
it's been pretty quiet on x13s front lately hmm?
<clover[m]>
i guess things are slowing down
<steev>
there is always a lul late in the rc's
<_`[m]1>
anyone has bluetooth stuttering?
<_`[m]1>
just waiting for new rcs? ;D
<steev>
occasionally i do, don't know what causes it, and i only really see it with the h2go speaker
<_`[m]1>
it stabilises after a while?
<_`[m]1>
but sound quality is lower?
<_`[m]1>
s/lower/low/
<gwolf>
sound quality over BT is never too great
<gwolf>
I have some ocassional little hiccups (i.e. no sound for a tenth of second or so) in my C630
<gwolf>
but at least it... works better than the inbuilt sound (which doesn't 😉)
<HdkR>
If your headphones support LDAC, AptX HD, or AAC the quality usually isn't too bad
<HdkR>
anything below that is hot garbage
<HdkR>
hiccups not withstanding of course :P
<_`[m]1>
<gwolf> "sound quality over BT is never..." <- I don't notice the difference on my macbook though
<gwolf>
_`[m]1: The Bluetooth protocol is not very well suited for audio. It ugh works, and has got quite popular as it indeed solves a common use case
<gwolf>
...I notice cuts mostly when I'm sitting >5m away from my speaker, and it might be due to interference. I notice it both from my Linux laptop and from others.
bluerise_ has joined #aarch64-laptops
hightower2 has joined #aarch64-laptops
bluerise has quit [Ping timeout: 480 seconds]
<_`[m]1>
depends on the receiver
<_`[m]1>
you can get good ones for cheap though
<gwolf>
Not as cheap as the bad ones 😉
<gwolf>
(yes, I'm cheap on my hardware... and I sometimes pay the price for it)
<_`[m]1>
I'm talking 2 euro in aliexpress
bluerise_ has quit [Ping timeout: 480 seconds]
bluerise has joined #aarch64-laptops
Lucanis0 has joined #aarch64-laptops
Lucanis has quit [Ping timeout: 480 seconds]
bluerise_ has joined #aarch64-laptops
bluerise has quit [Ping timeout: 480 seconds]
iivanov has quit [Ping timeout: 480 seconds]
bluerise has joined #aarch64-laptops
bluerise_ has quit [Ping timeout: 480 seconds]
bluerise_ has joined #aarch64-laptops
bluerise has quit [Ping timeout: 480 seconds]
<steev>
ajhalaney[m]: :D sorry about that, i really don't have any idea how it keeps dropping
bluerise has joined #aarch64-laptops
bluerise_ has quit [Ping timeout: 480 seconds]
<ajhalaney[m]>
Lol no worries steev I check a few things now every time I finally decide to start looking at upgrading the kernel for my x13s and that's one of em