I’ve been using Ubuntu on a yoga 2 for nearly a decade. I haven’t used the touchscreen in ages but I used to do a lot of inking and it was pretty good out of the box. It only has a 4 gigs of ram though and isn’t upgradeable so it’s not as useful as it was
I have a ThinkPad X12 that supports Linux well. The pen works fairly well with Xournal++. I don’t use it that often because I prefer a traditional laptop form factor, but it’s great if you like the Surface style design.
I also have an X12. Ironically one of my issues is that it’s too surface-pro like I’m terms of form-factor. When I saw it online I thought the keyboard connection was more rigid like a surface book (more lap friendly). In terms of specs though it beat the pants off any of the comparable spro’s at the time
Wrecked my first Ubuntu install over the course of 2 years, wanted something new and tried Arch. The 4th time pacman wrecked my system I moved to Fedora at around F20 and have been happy ever since. I tried Gentoo in there somewhere, and managed to install it, but just the install burned me out. That was back when the Sakaki guide was one of the only ways to install on UEFI except with Fedora.
I would say my biggest mistake was not understanding the scope of Linux and that something like Arch and Gentoo are more for a CS grad student level of user.
I have a much better understanding of operating system design principals and architectures now, but I still prefer Fedora, really because the Anaconda system, Nvidia kernel driver build system, and UEFI shim are the best system for Linux I have encountered. The bootloader is one of the largest vulnerabilities in modern computers.
I’ve used Ardour to capture keyboard midi input before. Not beginner-friendly, but it works if you want to play something, pick a soundfile, edit a flubbed note or two, and add it to a project.
That’s…a lot of dependencies to manually get. This wouldn’t have worked. And I need a reproducible method so I can do this fully offline without having to match apt to anything online.
If the dependencies are in the repos you’ve added since, then apt-rdepends should be able to pull them.
I had to keep chaining grep -v to ignore packages that didn’t exist but the result was a success.
Had a 100X, back then with 2GB RAM. Worked OOTB with Linux w/o trouble, all hardware supported. Good times. Later, starting your browser maxed out the RAM so not a viable option anymore.
Nowadays I can happily recommend a HP Stream 11". Works perfectly with Fedora 39, good battery life. (Obviously you don’t want to use such a machine for more than casual work/internet surfing. But as a cheap/solid travel netbook, it is perfect. Typing this message on it.)
Firstly, check the logs directly to get a more concise error that we can analyse. journalctl is the standard systemd logging client you can use in the terminal. By specifying the unit (units can be socket files, timers, services) you can get logs specifically for said unit.
You can utelize flags such as -e to scroll to the end of a journal, -f to follow a journal in realtime and utelize the -p flag to set priorities like error, crit, warning (-o error) and others to filter away common journal entries so you don’t have to scroll through every line in the log.
Secondly, and this is gonna sound weird, but reboot into windows twice. The first time you boot windows run diskchk on the partition(s) in terminal/powershell/command as administrator. If it tells you it needs to do an offline scan, reboot and you’ll see an offline diskchk screen on boot before login. If not, reboot again into windows anyways, and then reboot into Linux.
The reason is that NTFS has a weird failsafe flag that NTFS on Linux considers a no-go, and it’s usually set if the system crashes more than twice, but not always. If Linux NTFS drivers see the flag, it won’t mount as a precaution. The only way to reset the flag is to reboot in windows twice. Not once, not three times, but twice.
This might be outdated info, but that was the fact some years ago. There might be a way to fix it with modern day Linux, but I don’t know, especially when I have no direct and informative errors to go by.
I have a Lenovo Yoga 6 13" that I’ve had a pretty good experience with. Screen rotation didn’t work properly on Ubuntu 20.04 when I tried it back then, but I switched to Fedora 36 KDE, which worked great for over a year. I’m now on Debian 12 + KDE with an equally good experience. Fingerprint reader is not supported, but I didn’t want to use it anyway.
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.