---> I only use a KDE desktop. My sole OS is Linux distro MX 17.1 <---
I don't know if the following is a software or hardware problem but it began some weeks ago.
I have a 9 years old desktop tower computer which is plugged into a powerstrip. In the past, I'd made BIOS settings so that for years, I'd just throw the powerstrip switch and the monitor and desktop tower would go on. Then, some weeks ago, this no longer happened. I fussed with the 3 power options in the BIOS and finally got it back to normal, automatic start-up for more than 1 week but recently the problem has returned: I'm forced to push the POWER button on the tower and I really don't like doing this.
My BIOS only has these 3 options under "Power":
- "Last state" which restores system to the same state it was on before power failure
- "Stay off" - system will remain off once power's restored
- "Power on"
I'm wondering if software can cause changes somewhere so that I'm forced to use the tower's POWER button. Or could this problem mean hardware is starting to fail?
I've already tried a different powerstrip but the problem still continues.
When I finally shut down my computer each day, I use the "Shutdown" in my K menu. Then all I have to do is throw the powerstrip switch to shut off the monitor.
---> I only use a KDE desktop. My sole OS is Linux distro MX 17.1 <---
Here's output from inxi:
Code:
$ inxi -F
System: Host: mx17 Kernel: 4.13.0-1-amd64 x86_64 bits: 64 Desktop: KDE Plasma 5.8.6
Distro: MX-17.1_x64 Horizon December 15 2017
Machine: Type: Desktop System: DakTech product: Discovery8 v: 2009 serial: <root required>
Mobo: Intel model: DG41RQ v: AAE54511-202 serial: <root required> BIOS: Intel
v: RQG4110H.86A.0010.2009.0408.1515 date: 04/08/2009
CPU: Topology: Dual Core model: Intel Core2 Duo E8500 bits: 64 type: MCP L2 cache: 6144 KiB
Speed: 3167 MHz min/max: 1998/3163 MHz Core speeds (MHz): 1: 3167 2: 3167
Graphics: Device-1: Intel 4 Series Integrated Graphics driver: i915 v: kernel
Display: x11 server: X.Org 1.19.2 driver: modesetting unloaded: fbdev,vesa
resolution: 1280x1024~60Hz
OpenGL: renderer: Mesa DRI Intel G41 v: 2.1 Mesa 13.0.6
Audio: Device-1: Intel NM10/ICH7 Family High Definition Audio driver: snd_hda_intel
Sound Server: ALSA v: k4.13.0-1-amd64
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169
IF: eth0 state: down mac: 00:1c:c0:ca:00:e1
Device-2: Realtek RTL8192CU 802.11n WLAN Adapter type: USB driver: rtl8192cu
IF: wlan0 state: up mac: a4:2b:b0:bf:56:ae
Drives: Local Storage: total: 372.61 GiB used: 256.31 GiB (68.8%)
ID-1: /dev/sda vendor: Seagate model: ST3400832AS size: 372.61 GiB
Partition: ID-1: / size: 14.96 GiB used: 10.01 GiB (66.9%) fs: ext4 dev: /dev/sda1
ID-2: /home size: 2.55 GiB used: 1.85 GiB (72.5%) fs: ext4 dev: /dev/sda6
ID-3: swap-1 size: 3.78 GiB used: 66.0 MiB (1.7%) fs: swap dev: /dev/sda5
Sensors: System Temperatures: cpu: 65.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info: Processes: 175 Uptime: 2h 32m Memory: 3.83 GiB used: 3.28 GiB (85.8%) Shell: bash inxi: 3.0.24
kdf gives partition usages different from inxi's just above:
- dev/sda1 / 4.1 GB free (72% full)
- dev/sda6 /home 502.8 MB free (81% full)
- dev/sda7 /media/data 83.2 GB free (76% full)
Does it seem that this is a hardware problem? If "Yes", what can I test or maybe replace if something's failing? What about software causing this kind of problem? Is some software a possible or likely culprit?
Once turned on by pushing the POWER button, I have no problems with software nor with hardware during my long sessions.
Desktop no longer turning on automatically by any BIOS setting
