shutdown -r now zzz and sound problem

bob2112 said:
What's zzz?
Click to expand...
I learned the hard way when I was getting to know ZFS and was testing this experimental feature back then. I named my pool zzz and by accident I once didn't do zfs command but typed zzz instead. Unfortunately at that time I had no iLO access and had to call people in DC to restart my server. Since than I do two things after I upgrade the system with /now/ git: chmod 700 /root and rm `which zzz`.
 
With SirDice exploring the sound issue I'll ask about zzz(8), which is just a script wrapper for (usually):
acpiconf -s 3

The issue seems to be some difference in the running system after a warm boot (shutdown -r) compared to a cold boot (power on), which in theory shouldn't happen.

After a cold boot, can you suspend and resume reliably and repeatedly, before trying to shutdown -r?

If so, does examining /var/log/messages have lines for acpi ... suspend at (time) and acpi ... resume at (time)? Is each suspend / resume block look the same?

If not, what happens instead? Are there potential clues or error messsges in that file?

And after the warm boot, what actually happens when you issue zzz, where it fails? Is anything written to console? Or logged in the messages file? If so, exact messages should help.

You said it isn't a problem for you, but if suspend then fails, there are quite likely other things broken too, so it's worth fixing.

What make and model is the machine?

What FreeBSD version?
 
unbalancedskunk said:
i also noticed shutdown -h now fails also.
Click to expand...
What do you mean by "fail"? It doesn't turn off the machine? That's correct, it's not supposed to do that. shutdown -p now will power off the machine after halting it.

With FreeBSD there is a difference between shutdown -h now and shutdown -p now:
Code: 
     -h      The system is halted at the specified time.
{...}
     -p      The system is halted and the power is turned off (hardware
             support required, otherwise the system is halted) at the
             specified time.
 
unbalancedskunk said:
smithi FreeBSD 13-1, Dell Inspiron 5559
i also noticed shutdown -h now fails also.
Is it possible to reboot computer with acpiconf ?
Click to expand...

Have you examined the logs yet?

I'm afraid you're going to have to give us a lot more detailed information before we can help you debug any of this.

No, see acpiconf(8)

Also see reboot(8) which is what shutdown(8) calls after its other functions.

Please do read the manuals.
 
unbalancedskunk said:
well dear FreeBSD community. İ added apmd_enable="YES" to rc.conf and i think it solved all of my problems.
SirDice smithi
Click to expand...

Wow. How old is this machine, and what is it?

My trusty old Compaq Armada 1500c laptop ran on APM between c. 2005 and 2020, latterly as a mini server in a little bush shack on solar power.

Incredibly reliable; finally succumbed to a nearby lightning strike blowing the modem and network card.

I got it second hand, made in 1998 as I recall. Sorry, APM flashback nostalgia ...
 
You must log in or register to reply here.
Back
Top