Lenovo Ideapad Slim 5(x) 14Q8X9 (83HL)

[richardnpaul]

Start of discussion, brought over from launchpad

[richardnpaul]

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.

[jglathe]

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.
For me this looks as if it behaves like without the patches for the Purwa (x1p42100) SoC. But they are definitely there. Have you updated the device firmware from Windows?

[richardnpaul]

Okay, that gets much further. Now I get to a segfault.

[richardnpaul]

This is fully patched firmware wise via Windows

[jglathe]

Well thats something, confirmation its not the ideapad image per se. That display panel is a Samsung ATNA40, could be that it needs a different driver. Let's see what the other tester says, maybe we get a better picture (he also has the Samsung panel).
It could very well be that they have some different chips on this for the USB repeaters, which may sound odd, but without schematics you can't know.

[jglathe]

I looked again at the boot try you did with the ThinkBook 16 image, that's odd. It really went way further than the Ideapad images. Trying to think up a reason for this.

[richardnpaul]

I looked again at the boot try you did with the ThinkBook 16 image, that's odd. It really went way further than the Ideapad images. Trying to think up a reason for this.

That was my impression too, that the Thinkbook image was loading for quite some time before failing. Sorry if I didn't mention it previously.

[jglathe]

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.
He was using a type-A USB stick, so maybe its somewhere in the writing method...

[jglathe]

I'm a bit out of ideas, this sounds odd. Especially since Windows seems to run on it fine. You tried 2 images, both fail fairly hard. It could be something with uefi , but that doesn't help either. Thanks for the data, though. Thinking about this.

[richardnpaul]

Final updates as I'm out of ideas too. I've written the ideapad 5 image from a Windows Intel x86_64 machine using 4.8 version of rufus and I downloaded again just to be certain. That didn't work, booting from one of the type A ports. Then I updated to the latest balena etcher and tried writing the image again with that on the x86_64 system, and again the same issue. Also, I installed mesa-utils under WSL2 and ran that through gWSL for a few minutes and didn't see any issues there either (to try to nail down any obvious hardware issue, but I've not had any instability under Windows at all, it just greedily eats all the RAM leaving me little for doing anything productive on the machine 😁.)

[richardnpaul]

Ahhh, kaktus178 says that he's using a 2 in 1 which means that it's probably a 83GH based model and probably explains some of the differences.

[jglathe]

Still baffled. Yes, his is 83GH IdeaPad 5 2-in-1 14Q8X9 BIOS Q1CN22WW. I'll look for differences.

[richardnpaul]

It's annoying that there's no way that I can tell to roll back the BIOS as there's no list of previous versions or way to download those versions to roll back for testing purposes

[jglathe]

Hmm I thought you provided the ACPI tables and hwinfo64 log, but you... didn't? Could you please, since they are different models apparently
What a naming mess

[richardnpaul]

aarch64-laptops/build#141

This was my PR which was merged in, I think that this was what you looked at.

[jglathe]

Sorry, too much going on, did look at the launchpad bug. Thank you for the pointer. But well then I will have another look, need to separate these two things out.

[jglathe]

Oh interesting the log shows another PCIe bus. If that's essential in any way (I could bet) this would explain that stall. So I guess I have a handle for a new try.

[richardnpaul]

I'm game if you are. Just make sure that you're okay, if you have too much going on take a little time, I'm not pressed for time to get this up and, semi, working.

[jglathe]

It is pcie3, not-too-often seen on these devices. Probably for the card reader (Microsoft does this for the SP7 iirc), we'll find out.

[jglathe]

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.
The pcie3 part gave errors on thetb16, but I guess this is to be expected since its not enabled there.

[jglathe]

Oof. Actually its on line less than previous, doesn't sound like progress. My next step would be to go all-in on the pcie3 definition and also add the port and PMIC switches in the hope that it at least throws a non-fatal error. Will change this and upload again.

[richardnpaul]

Oof. Actually its on line less than previous, doesn't sound like progress. My next step would be to go all-in on the pcie3 definition and also add the port and PMIC switches in the hope that it at least throws a non-fatal error. Will change this and upload again.

Okay that sounds good to me. I'm more than happy to test anything you manage to put together 😊

[jglathe]

Currently preparing the next one. Getting the full pcie3 port definition in (with 6.15.0-jg-9) in the hope it pushes the box over the bump to actually boot. Since it was an interesting week, we're also having working X1-45 GPU support now, this will also be on the image. The first of its kind, so its a bit more fiddling. Should drop in the next few hours.

[richardnpaul]

Oh wow, that's great news I'll be happy to give it a spin and see where we get to. Am I right in recalling that there was a 6.15.1 kernel with patches for overheating GPUs due to throttling not occurring? That might have been the x1e but I don't know if if would also apply to the X1p.
Anyway, hopefully I can test and feedback. I'm well aware this must all be a pain without the ability to get hands on the hardware.

[jglathe]

x1p42 is still so new that you won't find it in mainline. I guess I will do a first release without GPU enabled, will be fun enough when it comes up. I have X1-45 GPU running on my TB16, but its one more moving part - or three.

[jglathe]

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...)

[jglathe]

Hmm I've seen some small detail on the Microsoft laptops, also regarding pcie3. Overwriting the image again.

[richardnpaul]

I'll test when I can when I get home

[jglathe]

Ok the new one is up.

[richardnpaul]

Okay, moment of truth, reboot about to commence...

[richardnpaul]

Right, that didn't work failing exactly the same way, but I'm just checking the sha sum to ensure validity of the files (you never know when you're using files of the same name over and over.)

Edit: no such luck I'm afraid, checksum of fc244bde3bcf6632911926a360328dd1cc1ef8fb7fb0a5e14638afe18e6cb43e checks out locally.

[jglathe]

Hmm sorry to hear that. debating with my self if I want to spend €1000 to get that sob of a laptop up 😼

[jglathe]

There are actually technical / performance reasons for not using slots. DDR6 8448MT is something, I enjoy it very much.

[richardnpaul]

The LPDDR5X spec is available on LPCAMM2 which is one of the benefits of it as it supports both standards including the higher speeds, and the clk chips have already shown that we can achieve high speeds on slotted memory, that's also on sodimm - just look for 6400 DDR5 to find it, just for your information. There are other reasons for not using slots, speed just isn't one of them. I don't expect people to follow hardware as closely as I do and so to know this 😁.
Similarly, I had to tell a guy who works at Nvidia that I know that Nvidia GPU with ARM CPU chips for laptops were potentially coming as early as later this year, because he thought the possibility of that was a way off yet; he works on FOSS there so not expected to know what hardware is going to come down the pipe until it does.

[jglathe]

Good q if any vendor actually puts it into hardware you can and want to buy. I actually bought an Orion O6 board with 64GB soldered on because it is 64GB (and supposedly open - compared to qcom it is). This one will be a kvm server eventually, so it is crucial to have enough RAM in the system. Aside from that I hold it with Douglas Adams (?): Every technical invention beyond the age of 30 is black magic.

[richardnpaul]

I liked the look of the o6 when I saw that they were going to release it, but I have enough mini-pcs already (4) running proxmox (HA) and it's, the o6, just quite expensive, especially if you want the 64GB of RAM (3 of my proxmox instances have 64GB of RAM, the other just a spare 16GB stick).

Mostly I liked that it was uefi and acpi because DTB just does not look to be scalable to me (it doesn't help that you have the likes of qcom doing half a job, from what I understand, wrt acpi).

[jglathe]

O6 is getting an AMI BIOS if I read correctly, so not everything is bad. It was a change of user experience just installing the debian image and everything apparently worked ootb.

[HarryDo289]

Hi,
Lenovo Ideapad Slim 5(x) 14Q8X9 (83HL) can instal Ubuntu ARM64?
I try to install this image but not support
https://launchpad.net/~ubuntu-concept/+archive/ubuntu/x1e

[jglathe]

Okay, if this works, could you please give me the HWInfo64 log (from Windows, I thought I had yours) and the dmesg output to check for errors? Also, a list what doesn't work? Also, output of lsusb would be nice.

[richardnpaul]

Yes, you (the arch repo) have the hwinfo log, that's from my machine. I'll try to sort out dmesg and lsusb, this installer is very slow and unresponsive to ctrl+alt+t

[richardnpaul]

dmesg.log
lsusb.txt
Here we go, dmesg and lsusb from the installer (I've not tried to install yet so as for the what works/doesn't work yet, I don't know.)

https://github.com/aarch64-laptops/build/blob/master/misc/lenovo-ideapad-5-slim-14Q8X9/hwinfo-14Q8X9.LOG is the hwinfo log that I submitted.

[richardnpaul]

Hmmm, the trackpad can't be changed. Seems to be stuck in "natural" scrolling regardless of the setting chosen. I set up fingerprint unlock, closed the lid, opened the lid then I just get continuous authentication errors and can't shut the laptop down.

[richardnpaul]

Also the console was getting spammed with message about not being able to write to the journal by systemd. In the end, after trying to hit ctrl+alt+del to force a shutdown, it got stuck with systemd and also unattended upgrades not stopping, so I had to REISUB to get the laptop to reboot.

I don't see the card reader, so I expect that those code changes you made may be helpful in this, yes backlight doesn't work but I don't think that we were expecting it to and I've not heard any audio out of it (system sounds and the like) so that probably doesn't work, but that's the same as noted elsewhere. I have dumped the dmesg and verbose lsusb, just need to get signed into Github on it later to upload them.

[sandiecao-dc]

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: ***@***.***>

[jglathe]

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.

[sandiecao-dc]

We already disabled Bitlocker, but we still need to disabled copy_firmware.service.

[sandiecao-dc]

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: ***@***.***>

[jglathe]

Hmm good to know. So in your case, the Samsung driver works for the panel. Does Backlight brightness control work?

[jglathe]

Also, could you please send me the log file you can generate from HWInfo64? This contains the list of devices.

[jglathe]

output of lsusb and dmesg would also be great.

[sandiecao-dc]

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: ***@***.***>

[jglathe]

Hmm okay. This should be the same. The HWInfo log would be nice, though. And a list of what doesn't work :)

[sandiecao-dc]

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: ***@***.***>

[sandiecao-dc]

Here is the Hwinfo log.
XPLUS Hwinfo.zip

[sandiecao-dc]

The Backlight brightness control doesn't work.
The audio doesn't work.
The type-c can't work for booting.

dmesg.log
lsusb.log

[HarryDo28998]

Do it work to install in Lenovo Ideapad Slim 5(x) 14Q8X9 (83HL)

[jglathe]

@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.
Spammed dmesg log with systemd messages: probably lost access to the USB stick (broken file system, re-enumerated device). Could be a side effect of the clock WARN we're getting.
No sound: yes, a bit risky to activate that one (no speaker protection). But possible.
Type-C unusable for boot: known issue, unfixable, only by not using it.

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.

[richardnpaul]

Okay, so some things to fix up. So on the two different panels front, that's to be expected, there are at least two panels that are available for this model, an IPS LCD and an OLED. My laptop has the OLED panel; one of the two things that drew me to it, the other it being ARM based.

Upstreaming sounds good, as does getting this installed side by side on the NVMe.

[jglathe]

That clock splat might be a side effect of pcie3 (the card reader) not being in the dts. Will add it back.

[richardnpaul]

Feel free to send them over as patch files or whole files (it's been a minute since I've used a patch file but I have used/generated/applied them in the past) rather than rebuild and reuploads.

For the NVMe install it seems that we'll need something different as this img file didn't give you most/nearly all of the options in the installer that you usually get, including partitioning and location to install.

[jglathe]

Well, look at that

It says server, but that doesn't stop you from installing ubuntu-desktop afterwards
I guess we could do with this, will try

[jglathe]

New version of dtb to copy over:
x1p42100-lenovo-ideapad-slim5x.7z.txt

What's changed:

• re-enabled PCIE3, should enable the card reader
• added PWM backlight config of T14s, let's see if that one works

If it comes up, please send the dmesg and function reports.

[jglathe]

Having (at least similar) hardware improves the chances of discovering bugs a lot 😁 I managed to install on my 2in1, but it was very non-straightforward. However, I guess this is doable. Main hurdle is to have efivars, this ensures grub-install can set the bootloader entry . I'll write it up later as a wiki entry.

[davplsm]

Update: tested the ernstp/mesaaco PPA and it works 🚀 Also found efivars, RTC misconfigs (working now). Working on sound.

I've been trying to use kernel 6.16.0-12.12 from the Ubuntu Concept repository for a few days with same dtb, but the panel doesn't work.

[ 1.371286] /soc@0/gpu@3d00000: Unknown GPU revision: 67.3.12.0
[ 1.373492] /soc@0/display-subsystem@ae00000/displayport-controller@aea0000: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-co
ntroller@aea0000/aux-bus/panel
[ 1.374921] /soc@0/display-subsystem@ae00000/displayport-controller@aea0000/aux-bus/panel: Fixed dependency cycle(s) with /soc@0/display-subsystem@ae00000/displayport-controller@aea0000

[ 1.501228] ------------[ cut here ]------------
[ 1.501230] WARNING: CPU: 2 PID: 278 at drivers/gpu/drm/panel/panel-edp.c:814 generic_edp_panel_probe+0x140/0x290

Do you think it could be related to what you mentioned?
Thanks,

[jglathe]

Huh. Unknown GPU revision sounds interesting. Do you have the complete panel-edp splat? It is probably a different panel. Just got sound to work, will do a new image (I guess ) soon

[davplsm]

dmesg.txt
Attached dmesg using kernel 6.16.0-12-qcom-x1e and the same dtb that works for kernel 6.16.0-rc3-jg-2-qcom-x1e.
Thanks again for your help.

[richardnpaul]

I'll be testing out with the new firmware which was released (v01.50) when I get a bit of time.

I'd like to get an installation up and running at some point but I'll need directions.

This worked fine with the new EC and firmware

[digidude512]

nostubble kernel images seems to stop me from booting.
Should I be using the normal ones instead or have I just got something missing/misconfigured?

[1-Me-Abhi]

dmesg_full.txt
lsusb_tree.txt
apic.zip
HWiNFO64.LOG

i think this is all what you asked

[digidude512]

I'm experiencing the same regression.

Which isn't great because Windows 11 just decided it doesn't want to allow my Pin to work anymore.

[1-Me-Abhi]

dmesg_full.txt lsusb_tree.txt apic.zip HWiNFO64.LOG

i think this is all what you asked

hwids for the LCD is not added to stubble

[jglathe]

Need to find out how that work, tbh

[1-Me-Abhi]

So the new iso of 26.04 from Ubuntu will not work or the fedora 44

[1-Me-Abhi]

Title: Touchpad not working on Lenovo IdeaPad Slim 5x (X1P42100) – i2c_hid IRQ failure (-16)

Hardware:

• Lenovo IdeaPad Slim 5x 14Q8X9 (LCD)
• Qualcomm Snapdragon X Elite (x1p42100)
• Touchpad: hid-over-i2c (2808:0106)

Kernel:

• 6.19.12-jg-0-qcom-x1e (arm64)

Issue:
Touchpad is detected but does not produce input events.

dmesg shows:
i2c_hid_of 0-0038: Could not register for hid-over-i2c interrupt, irq = 226, ret = -16
i2c_hid_of 0-0038: IRQ request failed (-16), falling back to GPIO polling
genirq: Flags mismatch irq 226

Other i2c_hid devices (e.g. keyboard) successfully use IRQ.

Device is visible in /proc/bus/input/devices:
hid-over-i2c 2808:0106 Touchpad

DTB:

• x1p42100-lenovo-ideapad-slim5x-lcd.dtb
• also tested x1p42100-lenovo-ideapad-slim5x.dtb

Working kernel:

• <6.19.6-jg-6>

Notes:
Issue appears related to IRQ conflict or incorrect interrupt configuration
in device tree or i2c-hid driver regression.

[jglathe]

Hmm what is the splat @1.364190

Otherwise, no other i2c devices registered except keyboard.

[1-Me-Abhi]

Here is the i2c-related dmesg output:

<
dmesg_full.log
i2c_debug.log

Regarding your earlier question:

• The touchpad (2808:0106 at 0-0038) is detected and registered.
• libinput shows the device is added successfully.
• However, no input events are generated from the touchpad.

Keyboard (6243:0001) works fine and produces events.

Earlier dmesg showed:

• IRQ request failed (-16)
• fallback to GPIO polling for i2c_hid

It looks like:

• IRQ is not available for the touchpad
• polling fallback is active, but not producing events

Additionally, the touchpad appears to be initialized twice in dmesg, which might indicate duplicate DT nodes or probe issues.

Let me know if you want full dmesg or DT section.

[jglathe]

Oh. I have the same on my Thinkbook 16. This should help resolve it.

[jglathe]

6.19.12-jg-1 doesn't have the i2c polling variant. This will get debugged a bit for the next round. Other change is only a ufs patch affecting sp12 and Galxy Book 4.

[1-Me-Abhi]

Ok

[1-Me-Abhi]

System boots fine, DSPs initialize correctly. However, FastRPC reports missing reserved DMA memory. No immediate functional issue observed—just confirming whether this is expected for current DT support.

Kernel: 6.19.12-jg-2-qcom-x1e

[valpackett]

https://patchwork.kernel.org/project/linux-arm-msm/patch/20260418-hamoaaudio-v1-1-a92866f744a6@oss.qualcomm.com/ is possibly related but I'm pretty sure that reserved memory is not needed for anything

[jglathe]

Applied, thanks!

[s3ns3iadi]

anyone tried fedora? https://fedoraproject.org/wiki/Snapdragon_WoA_Laptop_Install
or
openSUSE Tumbleweed
??

[olav-st]

On the latest kernel 7.1-rc6-jg-2-qcom-x1 both the webcam and fingerprint reader works! 😄

$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 27c6:650a Shenzhen Goodix Technology Co.,Ltd. Goodix USB2.0 MISC
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 002: ID 04f2:b81b Chicony Electronics Co., Ltd Integrated Camera
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

But brightness control is not working anymore 🤔

[richardnpaul]

So I have a black screen on boot on 26.04 with the rc7 7.1 build that you posted Jens. I'll get a dmesg later when I'm back from the school run.

[1-Me-Abhi]

Same here 😭

[olav-st]

Yup I am also getting a black screen on 7.1-jg-0 🫤
dmesg.txt
(For anyone else testing, beware of the alphabetical sorting in Google Drive and the Grub menu. I didn't notice the new kernel at first 😅)

[jglathe]

Oh wow good news monday. Have you tried 7.1-jg-0? No -rc? That one is the newest (this morning) and because of the naming might be sorted far away from the -rc ones.

[richardnpaul]

Oh wow good news monday. Have you tried 7.1-jg-0? No -rc? That one is the newest (this morning) and because of the naming might be sorted far away from the -rc ones.

Ah dammit, I guess that I got caught out be the issue or ordering @olav-st just mentioned 🤦

[chestabrook-commits]

I get the same blank screen.

…

On Mon, Jun 15, 2026, 09:47 Jens Glathe ***@***.***> wrote: Oh wow good news monday. Have you tried 7.1-jg-0? No -rc? — Reply to this email directly, view it on GitHub <#36?email_source=notifications&email_token=CFS274QWKQNJMGPPMVUXRKT476S2RA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZTGA2DQOBWUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-17304886>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/CFS274TOJ5GNWT3BVM4OVMT476S2RAVCNFSNUABHKJSXA33TNF2G64TZHM3DKNJRHE2TCMZQHNCGS43DOVZXG2LPNY5TQNBSG44DCNVBOYBA> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/CFS274VIGWUHG2Q562WH67D476S2RA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZTGA2DQOBWUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSVGM33PORSXEX3JN5ZQ> and Android <https://github.com/notifications/mobile/android/CFS274UHCXZLKQSDBSMCUI3476S2RA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZTGA2DQOBWUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.*** com>

[jglathe]

Classic argh moment. @olav-st thank you for the dmesg. It's the same again, and apparently consistently on all slim5x:

[    9.830142] clk: couldn't get parent clock 0 for /soc@0/display-subsystem@ae00000/displayport-controller@ae9a000
[    9.830146] msm-dp-display ae9a000.displayport-controller: probe with driver msm-dp-display failed with error -2

I traced that controller, its mdss_dp2. The one I want disabled. Added an explicit disabled for the controller on lcd and oled. I will rebuild and notify when published. It stays 7.1-jg-0.

[jglathe]

Okay its uploading, 7.1-jg-1

[jglathe]

@chestabrook-commits no idea, never seen SSSD working. Like, never. Its something up the stack, not kernel.

[olav-st]

I tried 7.1-jg-1 and its behaving the same way as the previous version. Display works, but no brightness control (I tried slider and brightnessctl)

[richardnpaul]

Hehe, was just about to report back with the same. I did double check with uname -a that I was using the correct packages

[richardnpaul]

I've finally received my type-c to hdmi 2.1 adapter. Working fine in both orientations at 60hz and 4k in one of the ports on the 7.1-jg-1 kernel.

[jglathe]

Alright, I guess we've come full circle (or something). Then we can't resolve the brightness stuck after resume, that will be a research topic. I found another interesting thing in the slim5x dsdt, though: the reset gpio for the 4th ptn3222 eUSB2 redriver :)

I took a a hint from the yoga 7 (also 14q8x9) and switched the bl_en pin to 3.3V logic. On the Xoga 7 this changed the behaviour of the OLED panel.

The new build will be up later (or tomorrow morning) as 7.1-jg-1 again. Only the slim5x OLED devicetree is changed.

[jglathe]

Hi @rixbyte , thank you for the extensive data. So going into the danger zone with 3.3V logic level doesn't help... will revert that. Also, thanks for the refernce to 6.19.14-jg-2, I guess we will find this eventually - or my curiosity wins and I buy the one on ebay 😼

[1-Me-Abhi]

Hi,

7.1-jg-0
The new backlight fix works correctly on my Lenovo IdeaPad Slim 5x (X1P42100), but I'm having trouble switching to the LCD DTB.

The kernel package ships both:

• x1p42100-lenovo-ideapad-slim5x-lcd.dtb
• x1p42100-lenovo-ideapad-slim5x-oled.dtb

However, the system always boots with the OLED DTB. The running device tree reports:

compatible = "lenovo,ideapad-slim5x-oled", "lenovo,thinkpad-t14s", "qcom,x1p42100";

I tried:

• Adding "devicetree=/boot/x1p42100-lenovo-ideapad-slim5x-lcd.dtb" to GRUB entries.

• Creating a custom GRUB entry using:

  devicetree /boot/x1p42100-lenovo-ideapad-slim5x-lcd.dtb

• Confirmed the LCD DTB exists in:
  /usr/lib/firmware//device-tree/qcom/

After boot, "/sys/firmware/fdt" and "/proc/device-tree/compatible" still show the OLED DTB.

Could you clarify how the DTB is selected on this platform and what is the supported method to force the LCD DTB? Is the firmware/UEFI providing the DTB and overriding GRUB's "devicetree" command?

Thanks.

[jglathe]

@1-Me-Abhi you're saying that the OLED dtb works with backlight adjustable on your LCD model? What's not to like... really?

The overriding issue you see is Stubble. If it detects a match between the hwid and its internal lookup table, it selects the internal dtb (which is OLED). To ensure that it respects the given devicetree statement in grub (not devicetree= , mind) you need two additional options in the kernel command line:

debug stubble.dtb_override=false

The debug is to see what it's doing, the other parameter instructs it to not give priority to the linked-in dtb if there is more than one devicetree.

To explicitly use the lcd device tree, you need the kernel parameters, and the dtb file copied over to the /boot directory. You can also set up flash-kernel, which is a beast of its own, but very helpful with deviating setups. And you need the devicetree statement, for example:

devicetree /boot/x1p42100-lenovo-ideapad-slim5x-lcd.dtb

If you don't want to edit grub.cfg after every critical update or kernel install, flash-kernel is your friend.

[1-Me-Abhi]

No LCD dtb works fine on the device but I am having trouble switch to LCD dtb

After every update it it switch to old dtb

[jglathe]

That's what I meant with flash-kernel. To avoid this for the time being, add the kernel parameters and set up flash-kernel for your laptop.

[1-Me-Abhi]

Hi,

I'm testing on a Lenovo IdeaPad Slim 5x 14Q8X9 LCD model.

The laptop has two variants (LCD and OLED). My machine is the LCD variant, but the firmware-provided device tree identifies itself as:

compatible:
lenovo,ideapad-slim5x-oled
lenovo,thinkpad-t14s
qcom,x1p42100

model:
Lenovo IdeaPad Slim 5x 14Q8X9 (OLED)

I installed "flash-kernel" and configured it with:

Machine: Lenovo IdeaPad Slim 5x LCD
Kernel-Flavors: any
DTB-Id: qcom/x1p42100-lenovo-ideapad-slim5x-lcd.dtb

and:

/etc/flash-kernel/machine
Lenovo IdeaPad Slim 5x LCD

Initially "flash-kernel" could not find the DTB because the kernel package stores DTBs under:

/usr/lib/firmware//device-tree/

instead of the locations expected by stock flash-kernel.

As a workaround I copied:

x1p42100-lenovo-ideapad-slim5x-lcd.dtb

into:

/etc/flash-kernel/dtbs/qcom/

After that, "flash-kernel" successfully installed the DTB:

Using DTB: qcom/x1p42100-lenovo-ideapad-slim5x-lcd.dtb
Installing new x1p42100-lenovo-ideapad-slim5x-lcd.dtb

However, it still reports:

System running in EFI mode, skipping.

I also added:

GRUB_CMDLINE_LINUX="devicetree=/boot/x1p42100-lenovo-ideapad-slim5x-lcd.dtb"

and confirmed the parameter appears in "/proc/cmdline".

But the kernel logs show:

Unknown kernel command line parameters "devicetree=/boot/x1p42100-lenovo-ideapad-slim5x-lcd.dtb", will be passed to user space.

The LCD DTB itself contains:

compatible = "lenovo,ideapad-slim5x-lcd",
"lenovo,thinkpad-t14s",
"qcom,x1p42100";

and:

model = "Lenovo IdeaPad Slim 5x 14Q8X9 (LCD)";

but the running system still reports the OLED model/compatible string.

This suggests that on EFI systems the firmware-provided DTB is still being used and the LCD DTB is not actually being loaded.

As a temporary workaround I'm testing a custom GRUB menuentry that explicitly loads the LCD DTB using GRUB's "devicetree" command:

menuentry 'Debian LCD DTB Test' {
insmod gzio
insmod part_gpt
insmod ext2
insmod fdt

devicetree /boot/x1p42100-lenovo-ideapad-slim5x-lcd.dtb

linux /boot/vmlinuz-7.1-jg-0-qcom-x1e root=UUID=<root-uuid> ro quiet
initrd /boot/initrd.img-7.1-jg-0-qcom-x1e

}

I haven't yet confirmed whether this successfully overrides the firmware DTB.

Could you advise what the recommended method is to force the LCD DTB on Snapdragon X EFI systems, and whether flash-kernel or GRUB should be handling DTB loading for these machines?

Thanks.

[jglathe]

Hi @1-Me-Abhi,

on the unresolved dependencies: When I have this and can't resolve (or don't know what its about, but know its not essential) I do a sudo apt-get install -f and it either resolves or removes.

Re sound fuckery. I'm afraid that was me. alsa-ucm-conf accepted my patch, audioreach didn't, and before I knew it there was a new alsa-ucm-conf version out with a mismatching config. Checking out jg/master on my alsa-ucm-conf fork would help, or just master on the original (but it has some compander patches missing). The accepted patch got reversed. /me taking a stab at sound has caused some havoc I'm afraid. With the right ucm2 conf you have sound on speakers, headphone, and the type-c ports as well when doing dp altmode.
On the story behind sound and the why: wiki entry - still WIP, but with the dust settling I will finish the doc.

[1-Me-Abhi]

Thanks, that actually explains a lot.

It would fit with what I'm seeing, because on an earlier Debian installation on this same machine I had working speakers and microphone. After reinstalling and updating packages, audio stopped working.

The timing would also match with a newer "alsa-ucm-conf" package replacing the configuration that was previously working.

I'll try switching to the "jg/master" branch of your alsa-ucm-conf fork (or compare it against the version currently installed on my system) and see whether that changes anything.

The ADSP/initramfs issue is now fixed and the Q6/APM modules are loading, so it makes sense that the remaining problem could be in the UCM configuration layer.

Thanks for the explanation and for documenting the background. I'll also take a look at the wiki entry.

[jglathe]

You will find the matching topology on the audioreach link in that wiki. That way works too, but might break when alsa-ucm-conf updates again.

[chestabrook-commits]

Hi @jglathe, you probably know already that there is a kernel panic for 7.1.1-jg-0-20260622. I returned back to 7.1-jg-1-20260621.

[jglathe]

Yeah classic Monday screen. Sorry about that, will be an interesting search.

[chestabrook-commits]

My testing with 7.1-jg-1 indicates that backlight slider did not work. Only 7.0.0.32 works.

…

On Wed, Jun 17, 2026, 21:02 Jens Glathe ***@***.***> wrote: @chestabrook-commits <https://github.com/chestabrook-commits> this one has me baffled, still. Could be that Ubuntu has the hack to limit max-brightness to 2047. For the OLED panels I need to find the right setup. However, I would like some confirmation if the OLED has working brightnessctl with 7.1.0-jg-0. This would help agreat deal (and it would make sense). — Reply to this email directly, view it on GitHub <#36?email_source=notifications&email_token=CFS274XLDQXNAPN3KPSQ62D5ALTNJA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZTGQZDKMRTUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-17342523>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/CFS274W5G3QXUUEA7KJ5FK35ALTNJAVCNFSNUABHKJSXA33TNF2G64TZHM3DKNJRHE2TCMZQHNCGS43DOVZXG2LPNY5TQNBSG44DCNVBOYBA> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/CFS274VXTGGMZUCGHEYSM7L5ALTNJA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZTGQZDKMRTUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSVGM33PORSXEX3JN5ZQ> and Android <https://github.com/notifications/mobile/android/CFS274QT5Z5FBEBPVPV3JMD5ALTNJA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZTGQZDKMRTUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.*** com>

[richardnpaul]

sudo brightnessctl set 500
Updated device 'dp_aux_backlight':
Device 'dp_aux_backlight' of class 'backlight':
        Current brightness: 500 (24%)
        Max brightness: 2045

~ → sudo brightnessctl set 50
Updated device 'dp_aux_backlight':
Device 'dp_aux_backlight' of class 'backlight':
        Current brightness: 50 (2%)
        Max brightness: 2045

No change in brightness either time with the 7.1-jg-1 packages (the ones that you updated today, or yesterday)

[jglathe]

As I said this requires some physical access to the machine (and a lot of willpower). I am almost confident that leaving out that gpio is better, but I can't verify it. 6.19.14-jg-2 (or -4) is not bad, it is pretty good, actually, btw. Does this work for you, too?
I have just moved the tree over to ubuntu-mainline and shedded about 800 commits for Ubuntu that way, getting mainline builds. Maybe its worth trying with that again, too?
Trying to get a slim5 OLED is prohibitively expensive, sadly. As I said, I would be better off going for he x2p model (with a whole new set of advenuture ahead). Actually, trying to consolidate a bit. I still have an Orion-O6 64GB (unaffordable atm) waiting for its mini-itx case installation and being put to good use. And a Turing Pi2 cluster getting a new coil-whine safe (hopefully) case to run stuff on.

[jglathe]

...and as fate (or whoever) also has a word to say about that, I will soon have a Slim5x OLED in my household. So, there's that :)

[richardnpaul]

As I said this requires some physical access to the machine (and a lot of willpower). I am almost confident that leaving out that gpio is better, but I can't verify it. 6.19.14-jg-2 (or -4) is not bad, it is pretty good, actually, btw. Does this work for you, too? I have just moved the tree over to ubuntu-mainline and shedded about 800 commits for Ubuntu that way, getting mainline builds. Maybe its worth trying with that again, too? Trying to get a slim5 OLED is prohibitively expensive, sadly. As I said, I would be better off going for he x2p model (with a whole new set of advenuture ahead). Actually, trying to consolidate a bit. I still have an Orion-O6 64GB (unaffordable atm) waiting for its mini-itx case installation and being put to good use. And a Turing Pi2 cluster getting a new coil-whine safe (hopefully) case to run stuff on.

Okay, so brightnessctl and function key control over brightness works with this kernel configuration. I'm not sure what help it is to have dmesg and journalctl at this point, it sounds like you should soon make more progress but I'll attach them anyway.
6.19.14-journalctl.txt
dmesg-6.19.14-jg-4-brightness.txt

[jglathe]

Thanks for confirming. The plot thickens, epic bisect incoming.

[chestabrook-commits]

I'll try it soon. Dr. Charles Estabrook

…

On Wed, Jun 17, 2026, 21:12 Jens Glathe ***@***.***> wrote: What about 7.1-jg-0 as it can be found on the GDrive? I deleted 7.1-jg-1 because potential danger. Needs to be tested with sudo brightnessctl, though. Slider has the wrong scale. — Reply to this email directly, view it on GitHub <#36?email_source=notifications&email_token=CFS274RKMPGGNRHF6QG7JX35ALUQJA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZTGQZDMMBSUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-17342602>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/CFS274VSHFTT7TAJOPE5XAD5ALUQJAVCNFSNUABHKJSXA33TNF2G64TZHM3DKNJRHE2TCMZQHNCGS43DOVZXG2LPNY5TQNBSG44DCNVBOYBA> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/CFS274SEOXY4WWBTLQZL2T35ALUQJA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZTGQZDMMBSUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSVGM33PORSXEX3JN5ZQ> and Android <https://github.com/notifications/mobile/android/CFS274UE5HMS7RELS5LPYJL5ALUQJA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZTGQZDMMBSUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.*** com>

[jglathe]

@rixbyte I did a bit of digging into your 7.1-jg-1 and 6.19.14-jg-2 logs from the slim5x OLED. All the more baffling, there is no real difference in configuration of the backlight between these two versions, even the logs look very much the same. One works, the other doesn't. To find what the real cause, I'm afraid one needs to do a bit of bisecting. Which is a PITA if you have the hardware, and more like multi-person torture if you don't. I would need access to such a laptop to go any further.

[jglathe]

Female intuition, I tell ya. My wife never really cares about the laptops lying around here. That one, though... "oh what's that? Never seen around here." argh. 🤣 So I guess they got the design right. Went for a test drive with wife right away.

[chestabrook-commits]

Hi all,
I just installed 7.1.1-jg-1-qcom with flash-kernel. The brightness control (function slider) and brightnessctl both show no backlight or brightness changes. In other words, the brightness slider doesn't do anything. Ideas?
I've attached dmesg logs (dmesg_jun27.txt)

[jglathe]

Flash-kernel could be the issue tbh. Do you have a dtb file in /etc/flash/kernel/dtbs ? If yes, rename that one to .backup. Afterwards, please run sudo flash-kernel again. The boot entry in grub should either have no devicetree line (stubble detects and selects the device tree from the kernel file) or something like devicetree dtb-7.1.1-jg-1-qcom-x1e which is a symlink to the dtb file in dtbs/7.1.1-jg-1-qcom-x1e/qcom/.

[jglathe]

@chestabrook-commits the plot thickens when I look into the log file.

[    5.061047] kernel: (NULL device *): [drm] [eDP BL DEBUG] PWMGEN_BIT_COUNT (0x724) raw=0x0b (Pn=11), CAP_MIN (0x725)=0x0a (min=10), CAP_MAX (0x726)=0x10 (max=16)
[    5.061175] kernel: pci_bus 0003:00: resource 5 [mem 0x78300000-0x7bffffff]
[    5.061317] kernel: msm-dp-display aea0000.displayport-controller: dpu_dp_aux: no max-brightness property found

It should say this when the dtb shipped with 7.1.1-jg-1 is used.

[    1.590519] panel-simple-dp-aux aux-aea0000.displayport-controller: Detected SDC ATNA40CT01 (0x4187)
[    1.592441] msm-dp-display aea0000.displayport-controller: dpu_dp_aux: found max-brightness=2047 on panel

[chestabrook-commits]

I did the changes you suggested:
cd etc/flash/kernel/dtbs/qcom
sudo mv x1p42100-lenovo-ideapad-slim5x-oled.dtb x1p42100-lenovo-ideapad-slim5x-oled.dtb_save
sudo flash-kernel

And backlight/screeen brightness now works!!!!

[richardnpaul]

https://lore.kernel.org/linux-acpi/20260623145225.143218-1-johannes.goede@oss.qualcomm.com/ interesting to see see this RFC pop up yesterday of a patch series that doesn't disable loading ACPI when booting with DT on Linux.

[jglathe]

Yes, I've read that RFC. Quite positive about that, and it's first infrastructure to get real ACPI support for future qcom laptops. Also it has a religious note as it seems, I'm in favor of whatever works.

[jglathe]

If you plan to activate internal sound on the Ideapad, this is the link that needs to be there:

jglathe@ips5x-jg:~$ find /lib/firmware/ -type l -name *Ideapad*
/lib/firmware/updates/qcom/x1e80100/X1E80100-LENOVO-Ideapad-5-tplg.bin.zst
jglathe@ips5x-jg:~$ ll $(find /lib/firmware/ -type l -name *Ideapad*)
lrwxrwxrwx 1 root root 52 Jun 27 16:39 /lib/firmware/updates/qcom/x1e80100/X1E80100-LENOVO-Ideapad-5-tplg.bin.zst@ -> ../../../qcom/x1e80100/X1E80100-Romulus-tplg.bin.zst

And basically that's enough to get it up and running on the next reboot. If you want a slightly better sound config re quality settings, you probably should also install the jg/master branch from my alsa-ucm-conf repo. How to install:

1. clone the repo, like into ~/src/alsa-ucm-conf
2. check out the branch jg/master jglathe@ips5x-jg:~/src/alsa-ucm-conf$ git checkout jg/master
3. rsync over to the alsa install: sudo rsync -av ~/src/alsa-ucm-conf/ucm2 /usr/share/alsa/ucm2
4. restart pipewire: systemctl --user restart pipewire pipewire-pulse wireplumber

[RengokuSensei]

Bro, compile everything and make img/iso for IdeaPad slim 5x
With latest kernal,patches,updates etc

[richardnpaul]

@RengokuSensei I'm going to say this because Jens shouldn't have to respond to this. This is unacceptable behaviour and drips of entitlement, you are entitled to nothing and plenty of it.

Jens has very generously given up a lot of his time for this and then paid out for a laptop it seems. He probably will build an image everyone can boot from in future, as he has in the past, but he is probably now able to get the laptop into good shape as he has actual hardware. More constructive feedback is welcome, this isn't and it isn't that.

[RengokuSensei]

@RengokuSensei I'm going to say this because Jens shouldn't have to respond to this. This is unacceptable behaviour and drips of entitlement, you are entitled to nothing and plenty of it.

Jens has very generously given up a lot of his time for this and then paid out for a laptop it seems. He probably will build an image everyone can boot from in future, as he has in the past, but he is probably now able to get the laptop into good shape as he has actual hardware. More constructive feedback is welcome, this isn't and it isn't that.

Sorry bro,
I didn't ment to offend anyone, it's just I want to use linux but too much coding, compilation etc feels difficult. I do know that it's my weakness. So sorry

[richardnpaul]

@RengokuSensei I'm going to say this because Jens shouldn't have to respond to this. This is unacceptable behaviour and drips of entitlement, you are entitled to nothing and plenty of it.

Jens has very generously given up a lot of his time for this and then paid out for a laptop it seems. He probably will build an image everyone can boot from in future, as he has in the past, but he is probably now able to get the laptop into good shape as he has actual hardware. More constructive feedback is welcome, this isn't and it isn't that.

Sorry bro,
I didn't ment to offend anyone, it's just I want to use linux but too much coding, compilation etc feels difficult. I do know that it's my weakness. So sorry

That's better, there are ways to say things. If you had instead asked when might there a straightforward image available to install you would have got a much better response.

I'm not going to speak for Jens as to how far off he thinks that we are that he might build another, but it's feeling closer. There is this, I don't know if it's public and I've not installed it and don't know what state it's in but I expect that at some point it might be updated with the kernel and os/package tweaks that are starting to be developed to tune the system into a reasonable machine.

[jglathe]

Yes, the LinuxImages folder is intentionally public. There's also a Wiki for it which I amend a bit atm, there was a lot learned in the last months.