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
<steev>
JensGlathe[m]: ah, i tracked down the panic :) it was a patch i was pulling in that was supposed to do something with shutdown (i missed the discussion on the patch though :( )
nashpa has joined #aarch64-laptops
dliviu has quit [Ping timeout: 480 seconds]
mani_s has joined #aarch64-laptops
tobhe has joined #aarch64-laptops
<genius1237[m]>
Is suspend supposed to work? After enabling the gpu driver on my x1p42100, I'm getting lines like this in dmesg on wake from suspend and a blank screen.
<genius1237[m]>
[drm:msm_dp_ctrl_on_stream [msm]] ERROR Failed to start pixel clocks. ret=-16
<genius1237[m]>
[drm:dpu_kms_wait_for_commit_done:524] [dpu error]wait for commit done returned -110
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
tobhe_ has quit [Ping timeout: 480 seconds]
mani_s has quit [Remote host closed the connection]
mbuhl has quit [Remote host closed the connection]
mbuhl has joined #aarch64-laptops
mbuhl has quit [Remote host closed the connection]
mbuhl has joined #aarch64-laptops
<JensGlathe[m]>
genius1237: it is, sort of. But things get interesting if there are not-supported devices in the mix, which is likely on the Ideapad 5 2-in-1.
<JensGlathe[m]>
Seems to work with GPU enabled. The error messages from your log suggest that it's something with the external display link.
jglathe_volterra has quit [Remote host closed the connection]
<genius1237[m]>
I tried again after a reboot and suspends seems to work, so idk, will observe and see
<JensGlathe[m]>
Just tried with external display on (4k@60) - works, but mouse artifacts after wakeup until the first refresh https://pastebin.com/XWHQqGgz
<agl>
steev: I patched bluez-5.83 .. the patch works
djakov has quit [Remote host closed the connection]
djakov has joined #aarch64-laptops
pbrobinson has joined #aarch64-laptops
SpieringsAE has joined #aarch64-laptops
<SpieringsAE>
deathmist: all good again, I think it was mainly some funkyness with the archlinuxarm repos
<SpieringsAE>
they've been a bit wacky the last week, some library updates that are breaking dependencies. but plasma 6.4 is running great now!
jglathe_volterra has joined #aarch64-laptops
SpieringsAE has quit []
flokli has quit [Quit: WeeChat 4.6.2]
flokli has joined #aarch64-laptops
<kuruczgy[m]>
I am getting errors like this on 6.16-rc2 when I have an external display connected and I suspend/resume:
<kuruczgy[m]>
After this starts happening the screen periodically starts freezing, the only solution seems to be a reboot.
<kuruczgy[m]>
Anyone seen this? Could this be a 6.16-rc* regression? I would think that I already tried suspend/resume + DP altomde on older kernels and I don't remember any issues.
<alexVinarskis[m]>
Yes i have it as well, but only on one of the two devices, XPS freezes, Zenbook doesn't. Happens after suspend even without the external display. Indeed older 6.15 rc were fine.
<agl>
steev: I have tried your 6.15.3 Kernel which you post bevor some hours. I can't access my ACASIS-Box over USB-C where my ethernet connection over LAN is and a two SSDs are connected. Bluetooth, WLAN works.
<agl>
steev: I must use 6.14.11 !!!
<steev>
i have no idea what an acasis-box is, so you're gonna have to help me out and dig into the commits, or use 6.14.11 or jens kernel, but i don't have whatever that is and have no idea
<agl>
It's a Box whith USB-C-Interfaces and Ethernet interface and one SSD.
<agl>
a second SSD is connected over USB-C at the ACais-Box.
<steev>
what i mean is, go through the commits, find the usb-ish ones, and revert them til you find the problem commit(s)
<agl>
ok
<steev>
i don't have a ton of usb devices here and the ones i have work, so i can't say what is causing it :(
<agl>
The ACASIS-Box is a Dok
<agl>
USB-C-Dok
<steev>
and i don't have one here :) i'd probably remove the usb:dwc3 related commits
<erebion>
Yesterday set up Secure Boot with my boyfriend on his X13s. We wiped all keys, rebooted, enrolled using sbctl, rebooted, no longer booted up. Nothing about a Security Violation, selecting a Boot Entry just does nothing. We then disabled Secure Boot and even reset all the BIOS settings. Anyone got an idea what's going on? BIOS works fine, but we cannot get anything to boot. Latest BIOS version from
<erebion>
Lenovo.
<erebion>
I had no such issue when enrolling keys on my own X13s, btw. But the BIOS version I used was one from ~ October.
<erebion>
I'd be glad if anyone has a tip that will make it boot again :)
<erebion>
Now trying to flash the an/the older BIOS version that I probably used in October, hopefully then it will work again
Lenni_ has joined #aarch64-laptops
<erebion>
Downgraded the BIOS, still does not boot
Lenni_ has quit [Remote host closed the connection]
<anthony25>
Did you try to reset the EC by pressing on the recovery pin under the laptop?
<anthony25>
You can try to set the EFI in setup mode again, and enroll the keys with the Microsoft ones
ravikant_ has joined #aarch64-laptops
<anthony25>
With sbctl, did you you the -m option when enrolling the keys (to also include Microsoft keys) or you just enrolled your keys?
ravikant__ has joined #aarch64-laptops
ravikant__ has quit []
<erebion>
Without the Microsoft keys
<erebion>
Which worked fine on my X13s, but not his
<erebion>
Reset button has no effect
<erebion>
Nothing will boot... Except the BIOS flash utility
<JensGlathe[m]>
and recovery image?
<Lenni>
Which recovery image?
<JensGlathe[m]>
for the X13s
<Lenni>
Do you mean the Windows image?
<JensGlathe[m]>
There is a recovery image from Lenovo, kills all data on ssd though
<erebion>
We could take that one out
hwpplayer1 has joined #aarch64-laptops
<erebion>
Could you link to it pls? Can't find it on their website
<hwpplayer1>
do we have a benchmark report how much does it take to create a pgp key generation takes ?
<hwpplayer1>
4096 RSA
<erebion>
So weird that the BIOS Flash Utility boots and I can update/downgrade, but nothing else will boot
<JensGlathe[m]>
idk, tbh
<anthony25>
My slim 7x was taking ages to boot, even to access to the bios, and just trigerring a hardware diagnostic from the recovery (that you can trigger with the pin under then laptop) fixed it
<anthony25>
It doesn't reset anything, I guess it just resets the EC, maybe you can try
<erebion>
I cannot trigger recovery using the button in the pin hole
<anthony25>
Oh…
<anthony25>
Sorry I missed your answer before
<anthony25>
Otherwise, opening the laptop, unplug the battery, and wait 15min?
<JensGlathe[m]>
erebion: its compressing now, hopefully to something manageable
<JensGlathe[m]>
Mine is not activated, but I would set it to permanently disabled
<erebion>
After enabling and disabling, Windows booted into a repair mode
<JensGlathe[m]>
good one
<erebion>
in what way?
<erebion>
Bc MS is a joke or because it could actually help?
<JensGlathe[m]>
They changed something that broke the "secure" chain for Windows, so maybe that's a symptom
<JensGlathe[m]>
Windows was not happy with what the UEFI reported now, and wanted to repair itself
<JensGlathe[m]>
what's not to like
<JensGlathe[m]>
so something reported off but was actually on
<erebion>
Or Windows just crashed in that moment
<JensGlathe[m]>
not tooo likely
<erebion>
though I still cannot boot anything
<JensGlathe[m]>
but Windows does?
<erebion>
yes
<erebion>
Let me try again: Enabling Bitlocker, disabling
<erebion>
New encryption or compatible?
<erebion>
You said they changed something?
<JensGlathe[m]>
now, please install hwinfo64 (it automatically installs the arm variant) and look at the dashboard. There are security options how they are detected by windows and enabled or not
<erebion>
Maybe I'd better choose the old one?
<erebion>
WIll do
<JensGlathe[m]>
they changed it so that it is always encrypted ex factory despite you not having a recovery key. To get rid of it, it must be explicitly disabled and decrypted in the process.
<erebion>
ooooof
<erebion>
hwinfo says Secure Boot is on -.-
<erebion>
But then I cannot turn it off again if the BIOS is unaware, right?
<JensGlathe[m]>
see, and again you explicitly enable bitlocker, do the recovery key dance, reboot, explicitly disable bitlocker, decrypt the drive, reboot to BIOS and disable secure boot.
<JensGlathe[m]>
No, I didn't design that
<erebion>
But does it matter whether I choose "new encryption method" or "compatible modus"?
<JensGlathe[m]>
how do I know
<erebion>
seemed like you do ;-)
<JensGlathe[m]>
no idea what this is
<JensGlathe[m]>
My newest laptop is 6 months old, and it wasn't there then
<JensGlathe[m]>
but I had to forcefully disable Bitlocker on that one, too
<erebion>
Yeah, boy friend booted it up to Windows, it automatically installed updates... Just so he could take a photo of the license agreement for the seller to get the Windows license refund
<erebion>
After enabling, disabling, turning secure boot off AND even then having to put it into SETUP MODE AGAIN... AAAAAAAHHHH.... hwinfo now reports Secure Boot as off.
<erebion>
Now, let's try booting again...
<JensGlathe[m]>
See, that wasn't too hard. Now let's boot some real system from USB
<erebion>
YES
<erebion>
Works
<erebion>
Finally
<erebion>
Thanks sooo much
<erebion>
^_^
hwpplayer1 has joined #aarch64-laptops
<erebion>
"that wasn't too hard"
<erebion>
literally been fiddling for 11 hours
<mani_s>
abelvesa Are the SMBIOS CHID/HWIDs different for all SKUs? I'm just asking if we could provide a 1-1 mapping between HWID and DTB
<mani_s>
I know that we use HWIDs for identifying a product, but not sure it is different for all combinations (OLED, PMIC etc...) or not
hwpplayer1 has quit [Remote host closed the connection]