While sadly true, it is close enough for a Java 17 LTS subset, even though it is Google's .NET with Kotlin having a C# like role.

Didn't went out the same way as with J++, unfortunately.

I have a tuxedo 14" i7-12700H with 3050. And it is terrible. Specs are nice, price was hefty, but in the end it does not deliver. Battery is horrible, charging is disruptive, power budget is not enough. All stems from the nvidia card that I paid serious bucks to get included but it makes a decent laptop into a very bad one as the power delivery system just does not seem to be able to cope with it.

Anyway I would go with FRAMEWORK there. Sadly they did not deliver to my address when I was in the market, but now they do.

Hopefully latest Tuxedo does have better hardware support? Mine has problems with charging, usb-c charging is even worse (slow charge normal performance or ok charge and 5W throttling which makes all cores go at 1GHz), battery saving feature that hides 10% of battery capacity in firmware etc. They also stopped delivering any firmware updates after a few months.

Which thinkpad was the one you had so many issues with, and which dock? I’ve had a few issues with my caldigit ts3 and ryzen 7840 p14s thinkpad but on the whole everything works pretty well. Worst issue has been a dumb regression with the Qualcomm ath12k firmware that wasn’t backed out for months.

That was a problem at some point, but I think most of the GPL3-to-GPL2-relicense-issues have been solved by now?

> ite_829x

Huh, so Tuxedo developed their own ITE 829x kernel driver.

I have a Clevo based laptop, similar to the ones they sell. Years ago I reverse engineered the keyboard's features and wrote a user space driver.

https://github.com/matheusmoreira/ite-829x

I interacted with Tuxedo quite a few times back then while I was figuring this stuff out. They even sent me source code for a pre-release version of their Electron app. It didn't help much in the end but they proved to be much nicer and more responsive than other manufacturers and even Clevo itself.

Wish they'd emailed me about their driver. I could have helped develop it, especially if they had given me documentation.

I briefly explored the idea of turning it into a kernel module and contributing it to the kernel. While reading Linux driver source code, some comments gave me the impression they'd prefer code remained in user space if possible. Since I already had a working user space driver, I decided not to contribute it.

I wrote the above program because Clevo's app was Windows only and so aggravating to use it defies description. Looks like Tuxedo ran into the same problem with their Electron app, if the complaints in this thread are any indication... Déjà vu.

I would describe it as exactly "resolving a license compatibility issue". Taint in linux kernel refers to marking this kernel as not supported, which often just means not purely GPLv2 compatible anymore. Proprietary AMD and nVidia drivers also cause taints. https://unix.stackexchange.com/a/118117/251582

It is, specifically because Tuxedo licensed their modules as GPLv3, instead of GPLv2 (the module license declaration only has 'GPL', to make this confusing), causing a mild license compatibility issue, and since they've had external contributions, it's not so easy for them to fix it. And it's not a ban, just a flag that gets set.

That's a shame, I got a 13 w/ the previous non-AI AMD 7 7840U in April, and it's been rock-solid running Pop_OS. I wondered at the time if I should have waited for the newer CPUs...

at least with framework you know exactly how much the replacement parts will cost ahead of time.

> issues with suspend on linux

Oh? I'd seriously considered buying the 13 w/this AMD CPU and I guess I naively thought it would be ideal. What sort of problems with suspend are you seeing?

While StarLabs has shipped products before, I'd be careful with them. That StarFighter laptop was supposed to ship years ago, and I don't think any have been delivered yet. Here's a Reddit thread [1] from three years ago saying delivery would be in a few months.

[1] https://www.reddit.com/r/linuxhardware/comments/yjuahx/star_...

Don’t bother with these. In my eyes the gold standard for Linux laptops is Framework or Lenovo.

The display unit is nothing an enduser should replace. Does every user know how to handle the delicate display and how to carefully install the LVDS cable? In most modern cars you cant replace the windscreen with cameras, heating wires in your backyard without the calibration software. You can try it, but you will fail.

Yep. I think pretty much every youngster gets some basic education (besides getting years of physics in high-school): disarm the group/fuse, double check with a power tester, make sure you are not causing any shorts. I don't know anyone who calls an electrician for replacing a light fitting, a power outlet, or light switches.

Besides that some European countries have required for decades that new houses/apartment have central residual-current circuit breakers for the whole house (unlike the US where as far as I understand they are only required in certain areas and are often in the socket and not centralized).

I do that work almost every day. What if the untalented handyman crunches a live cable and the metallic frame is on fire? You can repair how and what you want, its your house and children.

What are the 5 safety guidelines?

Ever heard of the old displays with an inverter that produced around 700V? Can zap grandpa into the coffin... THats why they did not sell it to customers.

I used to be quite cynical about these posts. I used Linux as my main desktop from 1994-2007 and switched to Mac then. I would periodically try on laptops Linux again, but there were always things broken in bad ways.

Early this year I bought a ThinkPad T14 Gen 5 AMD. In contrast to when I had a T14 Gen 1 AMD early 2020s, everything just works. All the hardware works, suspend/resume works, all the hardware comes up after a resume, etc.

Lately I have been using my ThinkPad much more than my MacBook Pro. NixOS is a superpower to me and having NixOS on a laptop is living the dream.

Can attest - Thinkpads and Linux go great together. Used for 2 years, then was forced into Windows crap by corporate policy. No, WSL is not the same.

I know, there are dozens on Linux forums, every time I was searching for workarounds.

Also it isn't as if I haven't subscribed to Linux Journal during its whole lifetime, or LWN, or even used to write M$ on email signatures and Usenet messages, for that matter.

Signed someone that knows Linux since kernel 1.0.9, yet has better things to do than making it work.

What I love about Lenovo besides PSRef and all the maintenance/repair manuals (with part numbers, so that you know what to get if something needs to be replaced), etc. is that they often certify laptops for Linux.

They also seem to really care about supporting Linux. E.g. WWAN modems need proprietrary unlock procedures these days thanks to the FCC [1]. Most vendors would shrug and say 'sorry, we only support Windows', Lenovo has a repo with Linux support for all the modems that ThinkPads support (you can only use supported modems, because the FCC apparently only certifies laptop/modem combinations, not individual modems):

https://github.com/lenovo/lenovo-wwan-unlock

[1] https://modemmanager.org/docs/modemmanager/fcc-unlock/

Yes. This is why I rather check Linux support od chips in a machine that I am planning to buy. Not that much work but you will not get unpleasant surprise when Wi-Fi do not work.

No system is without issues. We used ThunderBolt docks that worked perfectly with macOS, until one major release they became a hell to use because Apple broke something (which manifested as a display not coming back after resume, requiring several plugs/unplugs).

As everyone knows, Windows has its own fair share of issues. The first is that it is not a Unix :).

In this case it turns out they got… one comment that was strongly pro-Linux, one that mentioned they didn’t have trouble but only as an aside before going on to discuss Tuxedo, and one that was softly positive but acknowledged the trouble of checking hardware beforehand.