IPFire not rebooting(1)

[bcrandell (Bob Crandell)]

Hi,
We have bee using ZOTAC mini PC’s for awhile now and have been happy for the most part.
The one ongoing issue we have is rebooting. If they have been running for a few days they will hang at “Preparing for Reboot”
There is another post with this title:

Ipfire not rebooting

I did not find any anomalies from the register. I preferred to replace the machine, it belongs to a customer, in any case I want to investigate the matter since the old hardware is in my office. The procedure indicated by cfusco helped me to learn how to move in the logs with the various commands grep, cap etc. etc. you know coming from the windows world … HI. P.S. cfusco I send you a private msg about “Traverse Net-to-Net VPN from Road Warrior” I need same info about a configuration, I pref…

Arne.F said, “Some J1900 boards has problems that it hang in bios at reboot. Try to add reboot=b or reboot=k to the kernel commandline in /etc/default/grub and regenerate the grub config.
grub-mkconfig -o /boot/grub/grub.cfg”

I can’t find any information about reboot=k or reboot=b. Does somebody have chapter and verse that explains this?

In my case I discovered this miniPC had a BIOS update which I applied. Now I wait a few days to see if that fixed it.

Thanks

[loup001 (Loup)]

@bcrandell Hi !

From : The kernel’s command-line parameters — The Linux Kernel documentation

reboot=[KNL]
	Format (x86 or x86_64):
	[w[arm] | c[old] | h[ard] | s[oft] | g[pio]] \
	[[,]s[mp]#### \
	[[,]b[ios] | a[cpi] | k[bd] | t[riple] | e[fi] | p[ci]] \
	[[,]f[orce]

Where reboot_mode is one of warm (soft) or cold (hard) or gpio,
reboot_type is one of bios, acpi, kbd, triple, efi, or pci,
reboot_force is either force or not specified,
reboot_cpu is s[mp]#### with #### being the processor
to be used for rebooting.

Hope that help

[jon]

Docs for kernel 6.10:
https://www.kernel.org/doc/html/v6.1/admin-guide/kernel-parameters.html#

[bcrandell (Bob Crandell)]

Hi,

So I would need something like:

reboot=c,k,f

Thanks