by akatik » Fri Jun 29, 2018 9:42 am
erazersan wrote: ↑Thu Jun 28, 2018 3:28 pm
What application do you use to edit wtware.pxe?
Sorry, not wtware.pxe. wtware.pxe is a binary executable.
pxe.cfg is a config for wtware.pxe, and linux kernel command line for PXE boot lives in pxe.cfg. syslinux.cfg on boot USB stick for USB boot. It's a usual text file, use Notepad to edit. Add something like "acpi=force" before "quiet" word.
erazersan wrote: ↑Thu Jun 28, 2018 3:28 pm
Maybe i will try... But i think i will do the workaround with autoshutdown parameter.
There is no workaround in WTware config. Linux kernel can not deal with ACPI in BIOS. Solution is in linux kernel options or in BIOS.
[quote=erazersan post_id=78022 time=1530188937 user_id=19109]
What application do you use to edit wtware.pxe?
[/quote]
Sorry, not wtware.pxe. wtware.pxe is a binary executable.
pxe.cfg is a config for wtware.pxe, and linux kernel command line for PXE boot lives in pxe.cfg. syslinux.cfg on boot USB stick for USB boot. It's a usual text file, use Notepad to edit. Add something like "acpi=force" before "quiet" word.
[quote=erazersan post_id=78022 time=1530188937 user_id=19109]
Maybe i will try... But i think i will do the workaround with autoshutdown parameter.
[/quote]
There is no workaround in WTware config. Linux kernel can not deal with ACPI in BIOS. Solution is in linux kernel options or in BIOS.