Timeline for ThinkPad X220 with Fedora 23 does not wake up any more
Current License: CC BY-SA 3.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 1, 2020 at 6:01 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Dec 2, 2019 at 2:02 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jul 28, 2019 at 23:01 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Mar 28, 2019 at 2:24 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Mar 21, 2016 at 20:29 | comment | added | Gilles 'SO- stop being evil' | If that's the only obstacle, you could run tp-acpi from an Ubuntu live CD/USB. You may even be able to run that program under Fedora (it depends whether the tool requires a kernel version or option that Fedora doesn't have). | |
| Mar 21, 2016 at 20:22 | comment | added | Martin Ueding | Taking the battery out sounds like a good thing. I am reluctant to do this as this would reset the charge-levels I have set with tp-acpi on Ubuntu. It is not packaged in Fedora, so I cannot change the charge levels back to my 80%/85% I currently have. Therefore I would really like to leave the battery until I have packaged that. | |
| Mar 21, 2016 at 20:21 | history | edited | Martin Ueding | CC BY-SA 3.0 | Update UEFI upgrade |
| Mar 21, 2016 at 20:00 | answer | added | Doug | timeline score: 0 | |
| Mar 20, 2016 at 18:16 | comment | added | Gilles 'SO- stop being evil' | If software that worked before no longer does, that's surely a hardware issue... But do try unplugging the computer and removing the battery, wait a few minutes, then plug them back. I've had problems with laptops where the firmware was buggy and left something in a bad state that a mere power off didn't fix. | |
| Mar 20, 2016 at 15:38 | history | edited | Martin Ueding | CC BY-SA 3.0 | added 245 characters in body |
| Mar 20, 2016 at 14:55 | history | edited | Martin Ueding | CC BY-SA 3.0 | added 223 characters in body |
| Mar 20, 2016 at 14:15 | history | edited | Martin Ueding | CC BY-SA 3.0 | added 655 characters in body |
| Mar 20, 2016 at 13:49 | history | asked | Martin Ueding | CC BY-SA 3.0 |