Lenovo Ideapad Slim 5(x) 14Q8X9 (83HL) #36
Replies: 15 comments 142 replies
-
As I've added to the launchpad, I wrote with rufus the img file (extracted from the xz file) and tried to boot. I did this twice once for each type A port in this laptop. I've added a screen grab of the boot process at the point that it stops after a period of time it automatically reboots, much like the 25.04 image does, it just gets further than a blinking cursor. |
Beta Was this translation helpful? Give feedback.
-
Hmm. Could you just try the reportedly "working" image for the ThinkBook 16? They have almost the same mainboard, only real difference is the type/address for the touchscreen (which wouldn't work). Writing the stick several times should confirm its working. Since its stalling so early... interesting. |
Beta Was this translation helpful? Give feedback.
-
Update from the other tester colleague: He brought it up, with keyboard, touchpad, touchscreen 😁 One hurdle is the not-really enabled bitlocker on windows, which needs to be once enabled (ugh) and then explicitly disabled. I vaguely remember this with my tb16, though. Bitlocker needs to be explicitly off. |
Beta Was this translation helpful? Give feedback.
-
Hmm I thought you provided the ACPI tables and hwinfo64 log, but you... didn't? Could you please, since they are different models apparently |
Beta Was this translation helpful? Give feedback.
-
Ok I created and test-booted (with pcie3 enabled) on the tb16, worth a try. At the usual place, Ubuntu_Desktop_24.10_Lenovo_Ideapad_Slim_5x.img.xz. |
Beta Was this translation helpful? Give feedback.
-
Alright new image is uploading to Google Drive now. It says ~20mins until up, still Ubuntu_Desktop_24.10_Lenovo_Ideapad_Slim_5x.img.xz (the old one was a dud, so...) |
Beta Was this translation helpful? Give feedback.
-
Hmm sorry to hear that. debating with my self if I want to spend €1000 to get that sob of a laptop up 😼 |
Beta Was this translation helpful? Give feedback.
-
Hi, |
Beta Was this translation helpful? Give feedback.
-
The reboot should be caused by copy _firmware.service. There maybe something wrong with the firmware, so It comes to black screen again. We rewrite a new Image and remove the copy_firmware.service, then it works.
… From: "Richard ***@***.***>
Date: 2025年6月30日 (周一) 19:45
Subject: Re: [jglathe/linux_ms_dev_kit] Lenovo Ideapad Slim 5(x) 14Q8X9 (83HL) (Discussion #36)
To: ***@***.***>
Cc: ***@***.***>, ***@***.***>
Okay, I got a loading to black screen, followed by a reboot, then loading to a black screen again. So we have progress, however, there's no point where the screen comes back yet 😬
I'll check out external monitors shortly.
—
Reply to this email directly, view it on GitHub<#36 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BLTBRN6T2A4S5JPBKF3I6PD3GEPM7AVCNFSM6AAAAAB6Z7K57WVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGNRRGY4TQOA>.
You are receiving this because you were mentioned.[image]Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
This sounds a lot like the Windows partition still being encrypted with Bitlocker, an unholy issue (because its saying its not, probably). But curious, after disabling the copy_firmware.service, did it boot to display? With todays image?
After that, you can either boot to Windows (should have secure boot disabled and no Bitlocker - can be checked with HWInfo64) or boot the Image after it was newly written to a stick/SSD. |
Beta Was this translation helpful? Give feedback.
-
Yes, It did boot to desktop after we manually installed firmware. And it displayed on EDP.
… From: "Jens ***@***.***>
Date: 2025年6月30日 (周一) 20:17
Subject: Re: [jglathe/linux_ms_dev_kit] Lenovo Ideapad Slim 5(x) 14Q8X9 (83HL) (Discussion #36)
To: ***@***.***>
Cc: ***@***.***>, ***@***.***>
This sounds a lot like the Windows partition still being encrypted with Bitlocker, an unholy issue (because its saying its not, probably). But curious, after disabling the copy_firmware.service, did it boot to display? With todays image?
To actually disable Bitlocker:
• re-enable secure boot in UEFI
• boot to Windows, enable Bitlocker
• reboot to Windows, disable Bitlocker, explicitly let it decrypt the disk
• disable secure boot in UEFI
After that, you can either boot to Windows (should have secure boot disabled and no Bitlocker - can be checked with HWInfo64) or boot the Image after it was newly written to a stick/SSD.
—
Reply to this email directly, view it on GitHub<#36 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BLTBRN6PFU2AIWWWKXSYPE33GETD3AVCNFSM6AAAAAB6Z7K57WVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGNRRG4ZTMNA>.
You are receiving this because you were mentioned.[image]Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Please note: we use the Image of 28 June with the newest dtb we built from GitHub source. It should be same with today’s Image.
From: "Jens ***@***.***>
Date: 2025年6月30日 (周一) 20:17
Subject: Re: [jglathe/linux_ms_dev_kit] Lenovo Ideapad Slim 5(x) 14Q8X9 (83HL) (Discussion #36)
To: ***@***.***>
Cc: ***@***.***>, ***@***.***>
This sounds a lot like the Windows partition still being encrypted with Bitlocker, an unholy issue (because its saying its not, probably). But curious, after disabling the copy_firmware.service, did it boot to display? With todays image?
To actually disable Bitlocker:
… • re-enable secure boot in UEFI
• boot to Windows, enable Bitlocker
• reboot to Windows, disable Bitlocker, explicitly let it decrypt the disk
• disable secure boot in UEFI
After that, you can either boot to Windows (should have secure boot disabled and no Bitlocker - can be checked with HWInfo64) or boot the Image after it was newly written to a stick/SSD.
—
Reply to this email directly, view it on GitHub<#36 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BLTBRN6PFU2AIWWWKXSYPE33GETD3AVCNFSM6AAAAAB6Z7K57WVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGNRRG4ZTMNA>.
You are receiving this because you were mentioned.[image]Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
We can only provide it tomorrow, At least After 12-13 hours.
… From: "Jens ***@***.***>
Date: 2025年6月30日 (周一) 20:52
Subject: Re: [jglathe/linux_ms_dev_kit] Lenovo Ideapad Slim 5(x) 14Q8X9 (83HL) (Discussion #36)
To: ***@***.***>
Cc: ***@***.***>, ***@***.***>
Hmm okay. This should be the same. The HWInfo log would be nice, though. And a list of what doesn't work :)
—
Reply to this email directly, view it on GitHub<#36 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BLTBRNZSRED2EOKV4T75T6L3GEXH5AVCNFSM6AAAAAB6Z7K57WVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGNRRG43TOMY>.
You are receiving this because you were mentioned.[image]Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
@richardnpaul @sandiecao-dc thank you for the logs. Two different display panels, nice :) Also a deviating device name. Anyway, Both logs show a kernel WARN, though, that needs to be investigated. This will also affect things like suspend/resume since the clock tree is not in the desired state, leading to the strangest errors. Screen backlight brightness: This will be some experimenting to find out. If the system is stable enough we should consider installing on internal nvme with dual boot. That's how I drive my devices, works well enough. And upstreaming of the trees ofc. |
Beta Was this translation helpful? Give feedback.
-
New version of dtb to copy over: What's changed:
If it comes up, please send the dmesg and function reports. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Start of discussion, brought over from launchpad
Beta Was this translation helpful? Give feedback.
All reactions