Can’t Poweroff. [SOLVED]

[Member tupp]

I just did a simple, custom install of Antix 21 (full), preserving my home partition and formatting over a Devuan root partition.

I have experienced a couple of problems. First, the menus didn’t fully populate, but I have already solved that issue. The lingering difficulty now is that I have not been able to shut down the system with a poweroff.

To no avail, I have tried halt, shutdown and poweroff with various flag combinations, as root and with sudo. The console always appears stuck with this line:
“INIT: no more processes left in this runlevel”

I noticed that the halt init script was not linked at the end of rc0.d, so I put it there using sysv-rc-conf (see image). That didn’t help.

In addition, there was no reference to /sbin nor to /usr/sbin in the path for root, so I added those paths. Still no joy.

I can reboot from the Antix installation, and the live version of Antix 21 has no problem powering off my machine.

What am I missing?

Thanks!

• This topic was modified 1 year, 5 months ago by tupp.
• This topic was modified 1 year, 5 months ago by tupp.

Attachments:

1. 

   sysv-rc-conf.jpg
   

[Moderator BobC]

Helpful

Up

1

::

What kind of machine is it and which kernel did you boot with?

Did you look for errors with dmesg?

Which exact antiX version did you install? Please also run inxi -Fxz and post the results here.

Its not clear whether the problem is with the kernel/boot parms, what was in the /home directory, or something else.

If you have space on the drive, do a normal antiX install to that partition, boot to it, and see if it functions normally or not.

[Moderator christophe]

Helpful

Up

1

::

I just did a simple, custom install of Antix 21 (full), preserving my home partition and formatting over a Devuan root partition.

I read this as your “custom” antiX is using your old Devuan home partition. Am I wrong?

confirmed antiX frugaler, since 2019

[Forum Admin Dave]

Helpful

Up

1

::

@ christophe: That is how I read it as well.
My quick suggestion to try would be to make a new user account and see if the same problems exist. However given the following line there is a different underlying problem.

tupp wrote:

To no avail, I have tried halt, shutdown and poweroff with various flag combinations, as root and with sudo. The console always appears stuck with this line:
“INIT: no more processes left in this runlevel”

For example the system could be having troubles using the acpi commands correctly to actually power off the machine.
The other issues with the incorrect path being set as well as issues with the runlevel configuration seems to suggest some level of corruption on the install. (Assuming the installation media / ISO has been verified ok via checksum)

• This reply was modified 1 year, 5 months ago by Dave.

Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown

[Member tupp]

Helpful

Up

0

::

Thanks everyone for the prompt replies!

BobC wrote:

What kind of machine is it and which kernel did you boot with?

I tired both kernels and neither allowed poweroff.

Here is the result of inxi -Fxz:

System:    Kernel: 5.10.57-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 10.2.1 Desktop: IceWM 2.8.0 
           Distro: antiX-21_x64-full Grup Yorum 31 October 2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop System: Dell product: OptiPlex 9010 v: 01 serial: <filter> 
           Mobo: Dell model: 0M9KCM v: A01 serial: <filter> BIOS: Dell v: A30 date: 06/28/2018 
CPU:       Info: Quad Core model: Intel Core i7-3770 bits: 64 type: MT MCP arch: Ivy Bridge rev: 9 cache: L2: 8 MiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 54271 
           Speed: 3850 MHz min/max: 1600/3900 MHz Core speeds (MHz): 1: 3850 2: 3032 3: 3844 4: 3757 5: 2297 6: 3553 7: 3833 
           8: 2293 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Caicos XT [Radeon HD 7470/8470 / R5 235/310 OEM] vendor: Dell 
           driver: radeon v: kernel bus-ID: 01:00.0 
           Display: x11 server: X.Org 1.20.11 driver: loaded: ati,radeon unloaded: fbdev,modesetting,vesa 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: AMD CAICOS (DRM 2.50.0 / 5.10.57-antix.1-amd64-smp LLVM 11.0.1) v: 3.3 Mesa 20.3.5 
           direct render: Yes 
Audio:     Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: Dell driver: snd_hda_intel v: kernel 
           bus-ID: 00:1b.0 
           Sound Server-1: ALSA v: k5.10.57-antix.1-amd64-smp running: yes 
Network:   Device-1: Intel 82579LM Gigabit Network vendor: Dell driver: e1000e v: kernel port: f040 bus-ID: 00:19.0 
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 2.57 TiB used: 66.26 GiB (2.5%) 
           ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 GiB 
           ID-2: /dev/sdb vendor: Maxtor model: STM3320620AS size: 298.09 GiB 
           ID-3: /dev/sdc vendor: Western Digital model: WD20EZRX-00D8PB0 size: 1.82 TiB 
Partition: ID-1: / size: 57.37 GiB used: 4.57 GiB (8.0%) fs: ext4 dev: /dev/sda1 
           ID-2: /home size: 389.93 GiB used: 61.69 GiB (15.8%) fs: ext4 dev: /dev/sda2 
Swap:      Alert: No swap data was found. 
Sensors:   System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: radeon temp: 46.5 C 
           Fan Speeds (RPM): N/A 
Info:      Processes: 191 Uptime: 5m Memory: 15.59 GiB used: 631.1 MiB (4.0%) Init: SysVinit runlevel: 5 Compilers: 
           gcc: 10.2.1 Packages: 1645 Shell: Bash v: 5.1.4 inxi: 3.3.06

BobC wrote:

Did you look for errors with dmesg?

I found this:

[    2.513780] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20160831/utaddress-238)
[    2.513787] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[    2.513790] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20160831/utaddress-238)
[    2.513794] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[    2.513795] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20160831/utaddress-238)
[    2.513799] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[    2.513800] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20160831/utaddress-238)
[    2.513803] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[    2.513804] lpc_ich: Resource conflict(s) found affecting gpio_ich

BobC wrote:

Its not clear whether the problem is with the kernel/boot parms, what was in the /home directory, or something else. If you have space on the drive, do a normal antiX install to that partition, boot to it, and see if it functions normally or not.

I might just try a complete reinstall and completely clean out the /home directory.

christophe wrote:

I read this as your “custom” antiX is using your old Devuan home partition. Am I wrong?

You are correct. I cleaned out a lot of cruft, but there are certain config files which I would like to keep in /home.

Dave wrote:

@ christophe: That is how I read it as well.
My quick suggestion to try would be to make a new user account and see if the same problems exist. However given the following line there is a different underlying problem.

Thanks. It might be better to just move everything in /home to another partition and do a clean reinstall, and then carefully copy everything back.

Dave wrote:

For example the system could be having troubles using the acpi commands correctly to actually power off the machine.

Indeed. There were some acpi errors in dmesg (see above).

Dave wrote:

The other issues with the incorrect path being set as well as issues with the runlevel configuration seems to suggest some level of corruption on the install. (Assuming the installation media / ISO has been verified ok via checksum)

Yes. That is why I am thinking of a reinstall. The checksum matched the iso.

By the way, the last time it got stuck in the console without powering down, for kicks I pressed “ctrl-alt-bkspace” and the messages in the attached photo appeared. It can’t seem to make it to the halt command.

• This reply was modified 1 year, 5 months ago by tupp.
• This reply was modified 1 year, 5 months ago by tupp.

Attachments:

1. 

   console_message.jpg
   

[Moderator BobC]

Helpful

Up

1

::

Google found:
system-does-not-power-off-on-poweroff-just-halts

Try adding

acpi=noirq

to your boot command line

[Member tupp]

Helpful

Up

0

::

BobC wrote:

Google found:
system-does-not-power-off-on-poweroff-just-halts

Try adding

acpi=noirq

to your boot command line

That’s a great find! Thanks!

I added that parameter to grub2, but unfortunately it didn’t work.

Here is what solved the problem: I re-installed Antix 21 Full.

Now I can poweroff the system!

Sorry that I took the easy way out without tracking down the actual cause of problem(s). However, it must have been some “corruption” problem (as @Dave surmized) and/or I somehow borked the original install when I initially set which services would load.

Interestingly, poweroff works with the halt script being absent in rc0.d (which seems to be the default configuration).

Prior to the re-install, I also removed from the /home directory anything having to do with Xorg and icewm, to see if the icewm menus would populate properly.

Unfortunately, like before, a minimal menu of Antix-specific apps appeared. However, I got around that problem by renaming the existing, minimal Antix icewm menu and then running this command:
desktop-menu --write-out menu --desktop-code icewm

I then copied and pasted the original Antix menu entries within the icewm menu.

That way, there is a nice clean menu that favors the the general applications, but one can still access the Antix-specific apps.

By the way, one can run the above command with a slight modification to make the general applications dovetail seamlessly with the Antix icewm menu structure:
desktop-menu --write-out menu-applications --desktop-code icewm

Another problem that I forgot to mention was that conky was blocky and ugly. I don’t really need Conky, so I permanently disabled it via ‘Control Centre > Session > User Desktop-Session > desktop-session.conf > LOAD_CONKY=”false”‘

Thanks everyone for the help!

• This reply was modified 1 year, 5 months ago by tupp.
• This reply was modified 1 year, 5 months ago by tupp.
• This reply was modified 1 year, 5 months ago by tupp.

[Member ModdIt]

Helpful

Up

1

::

I don’t really need Conky,
I have repeatedly noticed problems by watching the info conky shows, that included headless running browsers

miners now run witout full CPU but it is enough telltale when you are used to your system, a browser crashes
or you close it and mem and cpu do not drop as far as expected..

It uses minimal rescources considering its usefullness. want pretty, just theme it.

[Moderator BobC]

Helpful

Up

1

::

I see you marked it solved. Did you get power off working?

If so, what worked to fix that?

It’s always nice to put the solution in the thread so that when people search, they find the problem and what solved it.

[Member tupp]

Helpful

Up

0

::

BobC wrote:

I see you marked it solved. Did you get power off working?

If so, what worked to fix that?

It’s always nice to put the solution in the thread so that when people search, they find the problem and what solved it.

Yes, poweroff now works!.

The solution was to reinstall Antix 21.

That solution is included in my previous message, but I see that is easy to miss within the message. I’ll edit the message to try to make the solution more apparent.

[Author]

Posts