Laptop doesn’t stop (shut down complete but is still running)

[Member orthodox42]

Hi,

using an old laptop, running antix
cat /proc/version: Linux version 4.9.0.-264-antix.1-486-smp (gcc version 8.3.0-6)

inx -Fz:
System:
  Kernel: 4.9.0-264-antix.1-486-smp arch: i686 bits: 32 Desktop: IceWM
    v: 2.9.7 Distro: antiX-19.4_386-base Grup Yorum 20 May 2021
Machine:
  Type: Laptop System: Sony product: PCG-GRT785B(DE) v: 01
    serial: <superuser required>
  Mobo: N/A model: N/A serial: N/A BIOS: Phoenix v: R0043F0
    date: 01/16/2004
CPU:
  Info: single core model: Intel Pentium 4 bits: 32 cache: 512 KiB
    note: check
  Speed (MHz): 2673 min/max: N/A core: 1: 2673
Graphics:
  Device-1: NVIDIA NV17M [GeForce4 420 Go] driver: N/A
  Display: x11 server: X.Org v: 1.20.4 driver: X: loaded: nouveau,vesa
    unloaded: fbdev,modesetting gpu: N/A resolution: 1024x768
  OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6
Audio:
  Device-1: Silicon Integrated Systems [SiS] SiS7012 AC97 Sound
    driver: snd_intel8x0
  Sound Server-1: ALSA v: k4.9.0-264-antix.1-486-smp running: yes
Network:
  Device-1: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet
    driver: sis900
  IF: eth0 state: down mac: <filter>
Drives:
  Local Storage: total: 55.89 GiB used: 12.32 GiB (22.0%)
  ID-1: /dev/sda vendor: Hitachi model: DK23FA-60 size: 55.89 GiB
Partition:
  ID-1: / size: 10.79 GiB used: 2.68 GiB (24.9%) fs: ext4 dev: /dev/sda1
  ID-2: /home size: 43.14 GiB used: 9.64 GiB (22.3%) fs: ext4
    dev: /dev/sda3
Swap:
  ID-1: swap-1 type: partition size: 768 MiB used: 0 KiB (0.0%)
    dev: /dev/sda2
Sensors:
  Message: No sensor data found. Is lm-sensors configured?
Info:
  Processes: 124 Uptime: 8m Memory: 491.7 MiB used: 102.9 MiB (20.9%)
  Shell: Bash inxi: 3.3.19

Everything works quite well (Sea Monkey takes its time to open, no problem!)

Does anybody have an idea, why during shut down
(It says “system halted, but fan and light are still running)
the machine doesn’t stop completely?
And how to fix it?
At the moment I have to push the start/stop button for some 5 seconds.

Thanks in advance

[Member sybok]

Helpful

Up

0

::

Hi, search the forum, very similar topics have already been discussed. E.g. https://www.antixforum.com/forums/topic/antix19-32bit-does-not-resume-from-suspend/#post-42101 could help.

[Member orthodox42]

Helpful

Up

0

::

Thanks for the hint!
I did (as as recommended) install “acpi-support”. But this showed no difference.
I tried then to change /etc/default/grub from

GRUB_CMDLINE_LINUX_DEFAULT=”quiet splash”

into

GRUB_CMDLINE_LINUX_DEFAULT=”quiet splash acpi=force”

but this resulted only in producing
“Kernel panic – not syncing: Fatal exception in interrupt”

How do i now re-edit /etc/default/grub
(there is an identical live system on DVD)

[Member orthodox42]

Helpful

Up

0

::

Boot (from Live-DVD) stops with:
“MP-Bios bug: 8254 timer not connected to IO_APIC”

[Member sybok]

Helpful

Up

0

::

Hi, my advice would be to boot Live-DVD, chroot, mount root or BIOS-partition to a mount-point on the live system:
mkdir ~/mounting; sudo mount /dev/sdx? ~/mounting
I would expect it to be /dev/sdb<number>.
You can use ‘lsblk’ or other commands to list the partitions on the notebook/PC.
Then modify the grub (or chroot and reinstall grub) and unmount when finished (‘sudo umount ~/mounting’).

The failure to boot is unfortunate.
The error was discussed for example at https://www.linuxquestions.org/questions/linux-server-73/mp-bios-bug-8254-timer-not-connected-to-io-apic-860397/
The link points to Wikipedia, https://en.wikipedia.org/wiki/Advanced_Programmable_Interrupt_Controller, which discusses/mentions the 8254 explicitly.
It mentions to modify booting parameters of the live-DVD.
See also:
https://www.linuxquestions.org/questions/linux-hardware-18/mp-bios-bug-8254-timer-not-connected-use-noapic-option-to-boot-591891/#post3525893
https://www.youtube.com/watch?v=OOJv7Cmyp-4

Some of the links also suggest to update BIOS which may solve some of the issues.
Though it is a potentially dangerous operation failure of which may render your device essentially dead.
(I messed it up once; my suggestion: if trying, then follow manual for your motherboard, it typically suggests to use floppy/USB.)

[Member orthodox42]

Helpful

Up

0

::

Added noacpi and noapic during boot from DVD
at least I was able to reset “/etc/default/grub”
But still the system stops at
“Kernel panic – not syncing: Fatal exception in interrupt”

Probably “update-grub” doesn’t work from Live-DVD without further ado?

[Member stevesr0]

Helpful

Up

0

::

Hi orthodox42,

It sounds like you are talking about two different setups:

1) Running installed on a hard drive –> no shutoff.

2) Running from Live DVD –> Not completing boot.

If this is the case, for (1) I would time the machine while you are shutting it down – at least for five minutes — to ensure it doesn’t just have a long pause before poweroff. I had a problem with a suddenly prolonged boot time from 20 seconds to 300 seconds because of a coding error in an updated package.

The second problem was discussed by sybok and seems to be a known issue and I have nothing to add to that.

stevesr0

• This reply was modified 10 months ago by stevesr0.

[Member orthodox42]

Helpful

Up

0

::

Hi StevesrO,
you’re completely right, I was quite hectic, sorry.
Slowly from the beginning:
Running antix 19.4 everything was good except shutdown was not complete
(as I know today, perhaps I should have just waited for some 5 minutes …)

— I followed the advice of sybok and installed “acpi-support”

— no difference

— I changed “/etc/default/grub”

from

GRUB_CMDLINE_LINUX_DEFAULT=”quiet splash”

into

GRUB_CMDLINE_LINUX_DEFAULT=”quiet splash acpi=force”

— resulted in not booting at all
error message:
“MP-Bios bug: 8254 timer not connected to IO_APIC”

and after some further (to me looking normal) messages it stopped with

“Kernel panic – not syncing: Fatal exception in interrupt”

— I then tried to start from LIVE_DVD

The Live-DVD would not start (this was solved before I read the answer from sybok by using “noacpi” and “noapic” as boot parameter.)
So No 2 is solved. Live-DVD is running.

So I finally was able to change back my “/etc/default/grub” to the original entry.
But this didn’t make any difference.
Starting the notebook, I still experience the same error message:
1)
(the same as before with the live-DVD)
“MP-Bios bug: 8254 timer not connected to IO_APIC”
then after some messages (which seem to be quite normal)
comes the next
2)
“Kernel panic – not syncing: Fatal exception in interrupt”

booting stops

1) I made the assumption that “update-grub” did not work from the running live DVD.
2) Would it be useful to uninstall “acpi-support”. How do I do that from the Live-DVD?

Thanks for the help until now, but what can I do further?

• This reply was modified 10 months ago by orthodox42.

[Moderator Brian Masinick]

Helpful

Up

0

::

Just out of curiosity, if you type in the command sudo poweroff does it shut down the system and power it off, or does it “hang” as the usual method does?

I personally create a few alias commands for reboot, poweroff, etc —>

alias pow='sudo poweroff'
alias rb='sudo reboot'

--
Brian Masinick

[Member orthodox42]

Helpful

Up

0

::

Thanks Brian,

but this notebook doesn’t boot at all!

I only can start it by running the Live-DVD …

[Moderator Brian Masinick]

Helpful

Up

0

::

My comments are relative to post #85759; that system boots, but you could not shut down.

Regarding the fact that one version (the live one) will boot, but not shut down, that’s what my suggestion pertains to; sudo poweroff ought to work.
If not, I’d try killing the init process (process 1).

That is:

PID TTY STAT TIME COMMAND
1 ? Ss 0:00 init [5]

Regarding the “installable image”, are you booting from the same (live) image that won’t shut down, and attempt to install from the same image, but it won’t install?

If yes, that’s really curious; if not, use the live image and attempt to install from it. If no, hopefully you’ve tried a few times to get an installable image.
If the current ones don’t work, try going back, maybe to 17 (or further back, if you can find one archived somewhere). I noted in one post that you’re attempting to install version 19.4. Try earlier versions (and other versions) for comparison; same or different behavior?

--
Brian Masinick

[Member stevesr0]

Helpful

Up

0

::

Hi orthodox42,

As Brian implied, it might be good first to troubleshoot the install which DOES boot and function and focus on the presumptive failure to poweroff, rather than trying to deal with two different installs with two different problems.

If you can reproduce and run the install that booted and functioned, do so and see if it eventually shuts down if you wait “long enough” (I suggested at least 5 minutes, but that was arbitrary. You could also run it overnight to definitely demonstrate that it REFUSES to poweroff.)

stevesr0

[Moderator Brian Masinick]

Helpful

Up

0

::

orthodox42 wrote:

Hi,

using an old laptop, running antix
cat /proc/version: Linux version 4.9.0.-264-antix.1-486-smp (gcc version 8.3.0-6)

inx -Fz:
System:
Kernel: 4.9.0-264-antix.1-486-smp arch: i686 bits: 32 Desktop: IceWM
v: 2.9.7 Distro: antiX-19.4_386-base Grup Yorum 20 May 2021
Machine:
Type: Laptop System: Sony product: PCG-GRT785B(DE) v: 01
serial: <superuser required>
Mobo: N/A model: N/A serial: N/A BIOS: Phoenix v: R0043F0
date: 01/16/2004
CPU:
Info: single core model: Intel Pentium 4 bits: 32 cache: 512 KiB
note: check
Speed (MHz): 2673 min/max: N/A core: 1: 2673
Graphics:
Device-1: NVIDIA NV17M [GeForce4 420 Go] driver: N/A
Display: x11 server: X.Org v: 1.20.4 driver: X: loaded: nouveau,vesa
unloaded: fbdev,modesetting gpu: N/A resolution: 1024×768
OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6
Audio:
Device-1: Silicon Integrated Systems [SiS] SiS7012 AC97 Sound
driver: snd_intel8x0
Sound Server-1: ALSA v: k4.9.0-264-antix.1-486-smp running: yes
Network:
Device-1: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet
driver: sis900
IF: eth0 state: down mac: <filter>
Drives:
Local Storage: total: 55.89 GiB used: 12.32 GiB (22.0%)
ID-1: /dev/sda vendor: Hitachi model: DK23FA-60 size: 55.89 GiB
Partition:
ID-1: / size: 10.79 GiB used: 2.68 GiB (24.9%) fs: ext4 dev: /dev/sda1
ID-2: /home size: 43.14 GiB used: 9.64 GiB (22.3%) fs: ext4
dev: /dev/sda3
Swap:
ID-1: swap-1 type: partition size: 768 MiB used: 0 KiB (0.0%)
dev: /dev/sda2
Sensors:
Message: No sensor data found. Is lm-sensors configured?
Info:
Processes: 124 Uptime: 8m Memory: 491.7 MiB used: 102.9 MiB (20.9%)
Shell: Bash inxi: 3.3.19

Everything works quite well (Sea Monkey takes its time to open, no problem!)

Does anybody have an idea, why during shut down
(It says “system halted, but fan and light are still running)
the machine doesn’t stop completely?
And how to fix it?
At the moment I have to push the start/stop button for some 5 seconds.

Thanks in advance

Your system was built in 2004. Therefore the oldest distribution you can get might work though support will be lacking.

antiX 15, 16, or 17 are worth a try!

Using noacpi and noapic boots from Live so 1) will start.

sudo kill -9 1 should bring it down.

--
Brian Masinick

[Moderator caprea]

Helpful

Up

0

::

orthodox42 wrote:

— I followed the advice of sybok and installed “acpi-support”

— no difference

— I changed “/etc/default/grub”

from

GRUB_CMDLINE_LINUX_DEFAULT=”quiet splash”

into

GRUB_CMDLINE_LINUX_DEFAULT=”quiet splash acpi=force”

— resulted in not booting at all
error message:
“MP-Bios bug: 8254 timer not connected to IO_APIC”

If understand your summary correctly and you can get to the bootscreen it should be possible to try:
Press the letter “e” on the line with your kernel on bootscreen.
On the following screen go (with up and down arrows) to the line starting with “linux”
At the end of the line (possibly running over two lines) you can delete now the acpi=force
By pressing F10 (if I remember right, in any case it’s shown there which letters) you can boot now into the system with the changed bootoptions for one time
and do your changes including update-grub for a permanent change.

[Member orthodox42]

Helpful

Up

0

::

First of all, thank you for the help received!
In the end, I could not boot from either the live DVD or the hard drive (error code as described above).

Since it is a really old laptop, I do not have exaggerated hopes.
To be honest, it is the device of a friend who is a dedicated “don’t throw-away-what-still-can-be-used” representative.

I appreciate these people more than those who constantly buy new things, even though the old things are still usable.

But …
I do not want to bother people with my problems,that are not so important.

For me, it’s more about a certain sporting ambition.

You are welcome to join me if you enjoy it, the others would like to get on with the more important things please!

😉

Summary:
Well, Nothing worked anymore!
Neither booting from the hard disk, nor from Live-DVD.

As there were all data secured, I decided to make a new installation.
The old problem vanished, the laptop is going down and switches off as intended.
Problem solved? No, it is more feeling like: thank God, I don’t have to struggle any more …

In the end, there are two questions left:
— during install I saw once more a lot of “locales” I am very shure I never will make use of
and
if I search by search-function for “locales” on this forum, I don’t get any result.
Really? No one ever thought of reducing that amount of “locales”?
Or is this a silly quetion and once installed it doesn’t play a large role whether all these “locales” are installed or not?
(To me, it takes a lot of time during installation)

Best regards

• This reply was modified 9 months, 4 weeks ago by orthodox42.
• This reply was modified 9 months, 4 weeks ago by orthodox42.

[Author]

Posts