- This topic has 3 replies, 2 voices, and was last updated Sep 25-10:16 am by Robin.
-
Posts
-
ahoppin
I have been using antiX 21 64 bit on a Thinkpad T400 with outstanding performance for several months.
I used antiX 19 previously. One of the problems I had with it on this machine was that it did not suspend to RAM when the laptop lid was closed.
And when I re-opened the lid, the mouse pointer was gone.
That was with antiX 19.
When I installed antiX 21, that problem seemed to have been solved.
However – after several months of use – it has now returned to antiX 21.
Sometimes the computer will suspend on lid close, and resume on lid open ONCE ONLY. Then never again until reboot.
Most of the time:
– Close the lid, and the machine fails to suspend.
– Open the lid again, and there is no mouse pointer.
I have not found any way to restore the vanished pointer, other than rebooting.
NOTE: selecting Suspend from the Logout menu still works.
If I then close the lid, and re-open it, the computer resumes normally.
So it seems that “suspend on lid close” is not working properly, but “resume on lid open” is.
The lid-close function worked fine until now.
What could I have done to cause it to stop working?
How can I fix it?
Thank you for the help!
Robin
If this isn’t a hardware issue (like halfway broken lever of lid sensor, or broken cable, or contact issue), you should ask yourself whether this behaviour started after upgrading some specific driver package. If it worked before, and then it has ceased working, something must have happened. Try to find out what was this.
Btw, I’ve seen this behaviour always when using the nouveau driver on my notebook. Only using the propiretary driver from manufacturer, even when outdated and not updated any longer fixes this issue for me. But I don’t think you switched the graphics driver last time? And Thinkpad is ati and intel anyway, not nvidia, if I’m not mistaken.
Windows is like a submarine. Open a window and serious problems will start.
Thanks Robin!
I don’t think it’s hardware, as opening the lid resumes when it’s been suspended from the Logout menu.
You’re correct that this Thinkpad has ATI video.
I made no driver or software changes – at least not intentionally.
The only thing I can think of that I did differently right before this happened is that I unplugged the Ethernet cable while the laptop was suspended. I can’t recall now whether I plugged it back in before or after resuming.
I made no driver or software changes – at least not intentionally.
— What about apt-upgrades ? A driver or kernel update could cause this easily, if some code was removed, changed or added, which causes now incompatibilities on specific hardware, while it solves issues on other hardware. Maybe an additional boot code, e.g. for acpi, is needed now? Try to check out on a fresh live USB system which has not seen any of the last updates.
right before this happened is that I unplugged the Ethernet cable while the laptop was suspended.
— OK, this reminds me of something: Long ago on antiX 17 I needed to manually rmmod the ipw2200 wlan driver before suspending and modprobe afterwards. Only then the notebook slept and resumed properly.
So you could try to rmmod all drivers not mandatory needed (e.g. for wlan, lan, bluetooth, tv-card (not graphics/video!), sound, card reader, pcmcia, firewire/IEE1394 or whatever). Check, whether suspend and wake works then properly. You need to modprobe the respective drivers then again after wake up. By successively reducing/replacing the group or set of excluded drivers you might be able to identify the culprit. They you can add this driver to the suspend and wakeup script, so the removal and restart is done automatically for you.
— Another chance is your BIOS battery is getting weak, and there might have been lost some BIOS settings previously present. So make sure nothing has changed without your knowledge within BIOS.
Windows is like a submarine. Open a window and serious problems will start.
- You must be logged in to reply to this topic.
