LID switch broken - does not detect open lid

Question

I am posting this again, after getting no solutions a long time ago.
I am using a Razer Blade 14" 2013 with linux-ck kernel (although I have tested in the main kernel and the issue remains).
I like to be able to close the lid to suspend. But it is not working properly.
Note: I am using
cat /proc/acpi/button/lid/LID0/state
to figure out the state of the lid.
When I start the laptop, the lid is correctly reported as open. When I first close it, the laptop goes to sleep, and when I open it again, it wakes up.
However, it is now reported as closed, although I just woke it up by opening the lid.
If I close the lid, it also does not suspend (I have to manually suspend).
I originally posted this in: https://bbs.archlinux.org/viewtopic.php?id=173280
I tried searching for similar problems, and newer topics came up, but I'm not sure what to do related to those, since the problem does not seem to be exactly the same (as in, this does not work in any kernel I have experimented with, including linux-lts). For reference, these are the topics:
https://bbs.archlinux.org/viewtopic.php?id=168361
https://bbs.archlinux.org/viewtopic.php?id=179216
Some extra details: I disabled suspend on lid switch, so I wouldn't have to rely on it, but the problem remains: even if the laptop does not suspend, the lid goes to the closed state, and stays in that state.
For most cases, this is not a big issue, except if I plug in an external screen: then my laptop's main screen becomes unusable, since it's reported as having the lid closed.
Any suggestions would be very welcome.
Thank you,
Rodrigo

Answer 1

rgomes wrote:I apologize, I was under the impression that it was okay, as long as enough time had passed.
For extra information: this problem happens in other distros, so it seems to be a kernel problem (not a hardware problem because it works on Windows).
What steps should I take to diagnose this, or does anyone know who I should email about this?
Yeah, I should have posed more, but I was in a hurry.  We would definitely prefer that posts intended to reanimate a thread contain new information.  Share what you have learned about the problem -- it demonstrates initiative by establishing that one is not just waiting around for an answer.  Things like where you have searched, additional observations, new revisions of programs, etc...    It just helps keep the signal to noise ratio of the forums up.