Linux

48186 readers

1699 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

nooter692@lemmy.ml

AgreeableLandscape@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

[Solved] Thinkpad X200 Tablet stylus brokie on Void Linux (lemmy.world)

submitted 7 months ago* (last edited 2 months ago) by TMP_NKcYUEoM7kXg4qYe@lemmy.world to c/linux@lemmy.ml

5 comments fedilink hide all child comments

Edit: Solved according to this: reddit Obviously Void has no systemd service but I just created a script service containing a single line isdv4-serial-inputattach /dev/ttyS0 --baudrate 19200. The serial communication often crashes but runit automatically restarts it so that's fine. Also 6.6 kernel is kinda buggy but 6.10(custom compiled) and 6.1(from void's repo) work fine. Yeah and don't forget to enable the ttySx service otherwise it cannot work.

I cannot get sway to detect my tablet device on Void Linux installed on a Thinkpad X200 Tablet. Anyone knows how to fix it? I have both libwacom and xf86-input-wacom installed. It worked fine on Debian.

Now when I think about it, I don't have libwacom-32bit installed, because I'm using musl library which is 64bit only. That might be the issue considering how old my hardware is. I'm going to try to investigate but I'm going post this here anyways in case anybody knows more than me.

top 5 comments

sorted by: hot top controversial new old

[–] thequantumcog@lemmy.world 5 points 7 months ago

Can be caused by musl. Try glibc version

[–] just_another_person@lemmy.world 1 points 7 months ago (1 children)

I think your kernel version is probably going to more the culprit here. What are you on now?

[–] TMP_NKcYUEoM7kXg4qYe@lemmy.world 1 points 7 months ago (1 children)

6.6.25_1

Though I've just tried 6.1.83_1 and it didn't help. Don't know whether there is a big difference between 6.1.0 and 6.1.83. I guess I'll have to try the glibc version.

[–] just_another_person@lemmy.world 2 points 7 months ago* (last edited 7 months ago) (1 children)

Check dmesg then, and look for any errors related to the device not being loaded. Good luck.

[–] TMP_NKcYUEoM7kXg4qYe@lemmy.world 1 points 6 months ago

Thanks for your tips but I did not find anything. (probably skill issue) I tried different distros and it's weird. Arch (endeavorOS live iso) does not work, debian does but antix does not, fedora works. So I'm going back to debian. Thank you either way.