I can't really say when it stopped working because I multiboot an assortment of Linux distros on more than one computer. and it's only recently that I happened to spend some time in the virtual console under antiX on the gateway laptop. (never got this error with other distros etc...)
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
Note: reguarding the"repetitive error text on tty1:
S. H. Engine unavailable
side issue below...
Thanks to masinick's reply (
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"antix.freeforu ms.org/post24495.html#p24495"
linktext was:"antix.freeforu ms.org/post24495.html#p24495"
====================================
) I found when the same error message happened in the console(s) with a subsequent antiX install to my gateway (amd_64) laptop I could at least eliminate the error messages from the consoles via:and rebooting... Don't really understand acpi well enough to be sure which of them I needed to turn off, so I did both.[/color]Code: Select all
update-rc.d acpi-support stop 3 . update-rc.d acpid stop 3 .
But since the above fix no longer works, I dug in a bit deeper, and located the script that masinick had indicated was the source of the error.
And accordingly edited the file:
/usr/share/acpi-support/eeepc-acpi-scripts/lib/shengine.sh
to add $DISPLAY based conditional branching to the two lines containing:
Code: Select all
notify error 'S. H. Engine unavailable'
Code: Select all
*)notify error 'S. H. Engine unavailable'
esac
else
notify error 'S. H. Engine unavailable'
fi
Code: Select all
*) if ["$DISPLAY" ="" ]
then
dummY=$DISPLAY
else
notify error 'S. H. Engine unavailable'
fi;;
esac
else
case $DISPLAY in
"")dummY=$DISPLAY;;
*)notify error 'S. H. Engine unavailable';;
esac
fi
So Like the subject asks, Is this safe?