- This topic has 40 replies, 7 voices, and was last updated Apr 19-10:39 pm by Klaas Vaak.
-
Posts
-
Klaas Vaak
AntiX 17.2
When I reactivate my laptop from suspension, the keuboard is disabled, i.e. I cannot type letters anymore. The trackpad, however, is still enabled. I have to reboot to get the keyboard working again.
Any suggestions?Anonymous
Since you did not mention details of your hardware, the only breadcrumb I can suggest is this:
[SOLVED] Getting mouse or keyboard to wake PC from suspendSince you did not mention details of your hardware, the only breadcrumb I can suggest is this:
[SOLVED] Getting mouse or keyboard to wake PC from suspendHey Skidoo, here is the details of my hardware: 32GB HDD, 2GB RAM. Does that suffice?
The link you provided, apart from the fact that it relates to Mint, is about a different issue. There the person wants to de-suspend, so to speak, with their mouse or keyboard. That is not my issue.My issue is that AFTER de-suspension the keyboard is disabled. It requires a reboot to get re-enabled.
cyrilus31
To be more helpful you can follow Rokytnji how to topic
inxi is a very useful command to describe precisely your hardware configuration.
- This reply was modified 4 years, 1 month ago by cyrilus31.
OK, here goes:
inxi -Fxz System: Host: Yoga300 Kernel: 4.9.126-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 6.3.0 Desktop: IceWM 1.4.2 Distro: antiX-17.2_x64-full Helen Keller 4 October 2018 base: Debian GNU/Linux 9 (stretch) Machine: Type: Laptop System: LENOVO product: 80M0 v: Lenovo YOGA 300-11IBY serial: <filter> Mobo: LENOVO model: Mini v: SDK0J33995WIN serial: <filter> UEFI: LENOVO v: C0CN25WW date: 04/21/2015 Battery: ID-1: BAT1 charge: 6.7 Wh condition: 25.7/30.0 Wh (86%) model: SMP L14M2P22 status: Discharging CPU: Topology: Dual Core model: Intel Celeron N2840 bits: 64 type: MCP arch: Silvermont rev: 8 L2 cache: 1024 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 8666 Speed: 500 MHz min/max: 500/2582 MHz Core speeds (MHz): 1: 500 2: 500 Graphics: Device-1: Intel Atom Processor Z36xxx/Z37xxx Series Graphics & Display vendor: Lenovo driver: i915 v: kernel bus ID: 00:02.0 Display: server: X.Org 1.19.2 driver: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz OpenGL: renderer: Mesa DRI Intel Bay Trail v: 3.3 Mesa 13.0.6 direct render: Yes Audio: Device-1: Intel Atom Processor Z36xxx/Z37xxx Series High Definition Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus ID: 00:1b.0 Sound Server: ALSA v: k4.9.126-antix.1-amd64-smp Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Lenovo driver: r8169 v: 2.3LK-NAPI port: 1000 bus ID: 01:00.0 IF: eth0 state: down mac: <filter> Device-2: Intel Wireless 3160 driver: iwlwifi v: kernel port: 1000 bus ID: 02:00.0 IF: wlan0 state: up mac: <filter> Drives: Local Storage: total: 29.12 GiB used: 3.72 GiB (12.8%) ID-1: /dev/mmcblk0 model: BGND3R size: 29.12 GiB Partition: ID-1: / size: 7.81 GiB used: 3.72 GiB (47.6%) fs: ext4 dev: /dev/mmcblk0p2 ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/mmcblk0p3 Sensors: System Temperatures: cpu: 27.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 199 Uptime: 1h 41m Memory: 1.84 GiB used: 242.4 MiB (12.9%) Init: SysVinit runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 inxi: 3.0.29- This reply was modified 4 years, 1 month ago by Klaas Vaak.
OK, so here goes:
inxi -Fxz System: Host: Yoga300 Kernel: 4.9.126-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 6.3.0 Desktop: IceWM 1.4.2 Distro: antiX-17.2_x64-full Helen Keller 4 October 2018 base: Debian GNU/Linux 9 (stretch) Machine: Type: Laptop System: LENOVO product: 80M0 v: Lenovo YOGA 300-11IBY serial: <filter> Mobo: LENOVO model: Mini v: SDK0J33995WIN serial: <filter> UEFI: LENOVO v: C0CN25WW date: 04/21/2015 Battery: ID-1: BAT1 charge: 6.7 Wh condition: 25.7/30.0 Wh (86%) model: SMP L14M2P22 status: Discharging CPU: Topology: Dual Core model: Intel Celeron N2840 bits: 64 type: MCP arch: Silvermont rev: 8 L2 cache: 1024 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 8666 Speed: 500 MHz min/max: 500/2582 MHz Core speeds (MHz): 1: 500 2: 500 Graphics: Device-1: Intel Atom Processor Z36xxx/Z37xxx Series Graphics & Display vendor: Lenovo driver: i915 v: kernel bus ID: 00:02.0 Display: server: X.Org 1.19.2 driver: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz OpenGL: renderer: Mesa DRI Intel Bay Trail v: 3.3 Mesa 13.0.6 direct render: Yes Audio: Device-1: Intel Atom Processor Z36xxx/Z37xxx Series High Definition Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus ID: 00:1b.0 Sound Server: ALSA v: k4.9.126-antix.1-amd64-smp Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Lenovo driver: r8169 v: 2.3LK-NAPI port: 1000 bus ID: 01:00.0 IF: eth0 state: down mac: <filter> Device-2: Intel Wireless 3160 driver: iwlwifi v: kernel port: 1000 bus ID: 02:00.0 IF: wlan0 state: up mac: <filter> Drives: Local Storage: total: 29.12 GiB used: 3.72 GiB (12.8%) ID-1: /dev/mmcblk0 model: BGND3R size: 29.12 GiB Partition: ID-1: / size: 7.81 GiB used: 3.72 GiB (47.6%) fs: ext4 dev: /dev/mmcblk0p2 ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/mmcblk0p3 Sensors: System Temperatures: cpu: 27.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 199 Uptime: 1h 41m Memory: 1.84 GiB used: 242.4 MiB (12.9%) Init: SysVinit runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 inxi: 3.0.29Now what??
To be more helpful you can follow Rokytnji how to topic
inxi is a very useful command to describe precisely your hardware configuration.
I did post
inxi -Fxzbut then nobody answered anymore.Did you buy a 24/7 SW Support Contract?
🙂 🙂 🙂
First aid measure:
Stop using “suspension” (== suspend) if it doesn’t work, until somebody answers.
@noClue: no I did not buy a 24/7 support contract, and I am not expecting that kind of support. But since different people answered, I thought there would be smooth follow-up, as is usually the case in such situations.
Thanks for your 1st aid measure “advice”, I figured that out myself before I even opened this thread.
You have no clue as to what issue is with suspension – it so happens that switching off is not an option because my laptop does not stay switched off, an issue I have investigated for a long time without success. So suspension is my only option.To paraphrase the Lewis Carroll: Follow the white rabbit (== your logic)!
24/7 support contract you usually make with a manufacturer and it’s their duty to find and fix the problem in a given time (according to your contact) and if they can’t/don’t, they must replace you the product.
The forum support like here, depends on the previous experiences of users with the same kind of problem on the very same or at least, on a very similar HW.
People reacted quick, asked you for HW report, they saw what HW is in question and they have no clue (at least not yet) what might be the cause and so, the ‘smooth follow-up’ is missing.
No need to ask every couple of hours: Ain’t you gonna invest your time to fix my keyboard instead in your partner (or whoever/whatever)? PATIENCE!
If somebody get’s some idea, it’ll be posted here.
In a meanwhile, you wait and hope and you spend the time with bing’in’, google’in’, yandex’in’ and such and try to figure it out yourself.
No ‘bad blood’ here, just no ideas (yet).
I didn’t bother to look for the details about your exact model, but I looked at your inxi report. If I’m not very wrong on that one, we are here dealing with some sort of a hybrid machine, ‘convertible’, that kind of stuff where you might consider yourself lucky if it even works under Windows 10.
“Suspend does not turn off your computer. It puts the computer and all peripherals on a low power consumption mode. If the battery runs out or the computer turns off for some reason, the current session and unsaved changes will be lost.”
With suspend, the problem is in “It puts the computer and all peripherals on a low power consumption mode.” Some devices are sometimes not ‘playing nice’ — don’t wake up. Sometimes it’s because of crappy components used, sometimes it’s because of crappy drivers … the fact is, some machines are just not able to manage the power states properly and I saw (too) many ‘strangeputers’ having some kind of issues with ‘just close the lid’ (== suspend) way of usage.
“Hibernate saves the state of your computer to the hard disk and completely powers off. When resuming, the saved state is restored to RAM.”
Hibernate needs the swap partition as large as the amount of your RAM. Since you have that swap, did you try hibernate?
@noClue: I have no intention to get into polemics. I do insist on getting the record right: I may have been somewhat impatient and need to consider that people here are volunteers and have other things to do too. But I have NOT asked for a reply every couple of hours, OK? So, please do not exaggerate, to put it mildly.
The computer is indeed a hybrid – tablet/laptop. It ran perfectly well on Win 8.1/64-bit for 3 years, then the cursor froze and battery volume went to zero and could not be budged from there. No amount on internet research revealed a solution. I was ready to ditch it, when I decided to do a clean install of antiX, a nice & light OS, and wipe Windows completely. The cursor and battery issues did not recur, so were Win-related. The machine is running fine, no issues except the one I opened this thread for.
I must say that under Win the machine would reignite spontaneously when switched off, i.e. shut down. Could not get that fixed. Under antiX this issue has persisted, which indicates it is a hardware problem. Having said that, it is not serious in that 1x/week I shut it down completely for a short while to give the HD a rest, then fire it up again and @ the end of each day put it in suspension or when I am not using it for more than 30 mins.
The annoying thing is the keyboard disablement during suspension, although it does not happen after each suspension, and it did not happen under Win. As for hibernation, how do you do that? The Logout menu options are Lock screen, Log out, Restart session, Suspend, Reboot, Shutdown.
delix02
most likely, the reason why didn’t get an answer before is quiet simple :
nobody has a solution for it and it’s not very useful, if everybody without a solution posts this (more or less surprising) fact in the thread.“although it does not happen after each suspension”
here is serious part of the problem. For me, it seems to be a matter of the combination of hardware, kernel, boot process and time.
If you can find a solution for similar issue in the web, it is unlikely that you get more than some hints and tipps for your specific combination. Even for an expert of everything it would probably take days to find the source of the problem – not to say a solution.
I hope for you somebody will proof me wrong, anyway.I was simply reading …
April 3, 2019 at 2:24 am, “OK, so here goes …”
April 3, 2019 at 6:33 am, “Now what??”
April 3, 2019 at 10:14 am, “I did post … but then nobody answered anymore.”For me, that looks very much like you “asked for a reply every couple of hours”, however, “I have no intention to get into polemics” neither, just “getting the record right”.
As of hibernate, that’s a valid question, but unfortunately, the answer to it is out of my scope.
Basically, all you need to do to is, activate it with a simple command: systemctl hibernate
It wouldn’t work for you since you’re missing systemd.
Suspend and hibernate are part of the “pm-utils” package.
Debian has also a package named “hibernate”.
Then there is a package “uswsusp”.
Provides user space tools.Now, the actual problem is, that besides the fact that all needed components must be installed and enabled first, the Kernel and the OS would have to support it.
Theoretically they do of course, but there were many users filling bug trackers because, as many other things in Linux, it doesn’t work in practice.Some users were claiming that hibernate doesn’t work at all, some said that after 3 hours in suspend, computer automatically hibernates, some were reporting Kernel bugs while it worked with one Kernel, but not with another and the others said, it worked perfectly in Jessie, but it’s getting worse and worse in Stretch …
So, first thing you’d have to find out is, where the problem comes from, which state is causing it (“… although it does not happen after each suspension …”).
Just as example, what you say could also mean that you did suspend, that later changed into hibernate and your problem is not suspended state but a waking up from hibernate.Since all that has a strong HW dependency as a plus, I don’t really think that anybody is going to try to reconstruct and debug your problem.
Edit: Just as delix02 explained while I was still writing my answer.
@noClue: thank you.
- You must be logged in to reply to this topic.
