Linux

48061 readers

698 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

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

my lid is being detected as a keyboard button (lemmy.ml)

submitted 1 year ago by beh_93825561489@lemmy.ml to c/linux@lemmy.ml

6 comments fedilink hide all child comments

yes I talked to the developers and well I guess I am supposed to figure it out myself but I don't know how so I am basically seeking help here this is the bug report: https://github.com/systemd/systemd/issues/28942

I guess I should post my own pr but I have no idea how to say to udev that the key specified as d8 is actually the lid being closed and the key specified as d7 is actually the lid being open

basically yes I am a noob and a helpful response will be just a documentation page to show me where can I begin to fix this problem

you are viewing a single comment's thread
view the rest of the comments

[–] beh_93825561489@lemmy.ml 5 points 1 year ago (4 children)

well as far as I understand adding "AttrLidSwitchReliability=unreliable" will not actually fix the issue and I hope this issue is fixable to be honest

[–] TuEstUnePommeDeTerre@midwest.social 4 points 1 year ago (3 children)

Then you'll likely have to mess with the udev rules and force the device to recognized as a lid switch.
Per the example under "Querying the hwdb," you need the ID_INPUT_SWITCH property to be set correctly.
There's an example of how to group devices in the Arch wiki for graphics tablets that may be of use if libinput will accept two different switches as one.

[–] beh_93825561489@lemmy.ml 4 points 1 year ago (2 children)

there is one problem with those links they are forcing a whole device to be another device and I just want the key with scan code d7 to be state 0 of SW_LID and d8 to be state 1

and fixing this issue in the udev level will automatically fix everything like I will finally be able to use logind.conf

yeah read that bug report and to be honest I don't understand the developer standpoint like sorry at least give where can I find the documentation for udev rules

even if I use libinput these are the id_input available: ID_INPUT_KEYBOARD, ID_INPUT_KEY, ID_INPUT_MOUSE, ID_INPUT_TOUCHPAD, ID_INPUT_TOUCHSCREEN, ID_INPUT_TABLET, ID_INPUT_JOYSTICK, ID_INPUT_ACCELEROMETER

and there is no lid one so yeah I don't know is this problem unfixable with udev rules alone + I made this whole thread just to not make that bug report one of the other 1.9k other open ones except the fact that I wanna improve my experience with linux

+_+

[–] TuEstUnePommeDeTerre@midwest.social 3 points 1 year ago (1 children)

ID_INPUT_SWITCH (Line 88 here) appears to be an option that is excluded from the list on the libinput page.
I went through some similar issues with PostmarketOS on a Chromebook. The libinput quirks and udev rules are highly undocumented and unstable right now. You have to piece together information from existing configurations and poking around in the libinput repo.

[–] beh_93825561489@lemmy.ml 1 points 1 year ago* (last edited 1 year ago)

update so after realising I have ACPI: button: The lid device is not compliant to SW_LID. in my logs I found a couple of bug reports in the kernel https://bugzilla.kernel.org/show_bug.cgi?id=192231 https://bugzilla.kernel.org/show_bug.cgi?id=202421

so I guess this can be as well a kernel issue

so I made a bug report in the arch linux bug reporter: https://bbs.archlinux.org/viewtopic.php?pid=2119116

so yeah I guess and I hope someone understand the problem fix it with udev or the linux kernel directly or at least give me the steps to do so anyway yeah that's all

and I guess if this plan didn't work I have to learn C to fix the issue