Re: poweroff and shutdown -p now only reboot my machine
Just to get this here. I've moved the SSD drive containing NetBSD to another machine and both commands are working properly. Regards Den mån 30 juli 2018 16:29Pedro Pinho skrev: > Ok! I've checked hp's webpage. > No BIOS updates available under Linux. Of course, there's no reference to > any BSD. > There're updates available to both BIOS and firmware under Windows, but I > don't have any Windows machine. > I can try to make a DOS bootable USB and boot in UEFI mode to try to > update the BIOS, but I won't be able to do this before earliest next week
Re: poweroff and shutdown -p now only reboot my machine
Ok! I've checked hp's webpage. No BIOS updates available under Linux. Of course, there's no reference to any BSD. There're updates available to both BIOS and firmware under Windows, but I don't have any Windows machine. I can try to make a DOS bootable USB and boot in UEFI mode to try to update the BIOS, but I won't be able to do this before earliest next week. Regards Den mån 30 juli 2018 11:19Martin Husemann skrev: > On Mon, Jul 30, 2018 at 11:12:46AM +0200, Pedro Pinho wrote: > > I'll check if there are any BIOS updates available and reply back. > > No error messages at all. The only line displayed after X closes is > > syncing disks...done > > > > There are some errors related to acpi. If I boot with acpi, I get 12 > errors > > while detecting hardware. If I boot without acpi, I get just 5 errors. > > > > Would it help if I post dmesg output? > > Yes, please (both with and without acpi). You are seeing the shutdown not > being done through ACPI, which is very strange on any machine made after > ~ 2000. > > Martin >
Re: poweroff and shutdown -p now only reboot my machine
On Mon, Jul 30, 2018 at 10:39:35AM +0200, Pedro Pinho wrote: > All the following commands act like reboot: > sudo poweroff > sudo shutdown -p now > sudo halt -v > The machine closes down all running applications and apears to shutdown, > but immediately starts booting again, exactly like reboot. Actually, I see > no difference if I issue > sudo reboot OK. After it shuts down everything, there should be a few kernel messages (in green) on the text console. The last one is typically something like: acpi: entering S5 or similar. Do you see those? Any errors printed there in the last seconds before it reboots? This may be a problem with you BIOS/Firmware and it is worth to check if there is an update available. Martin
Re: poweroff and shutdown -p now only reboot my machine
First of all thank you for your reply. I'm really enjoying this system. Yes, of course. All the following commands act like reboot: sudo poweroff sudo shutdown -p now sudo halt -v The machine closes down all running applications and apears to shutdown, but immediately starts booting again, exactly like reboot. Actually, I see no difference if I issue sudo reboot Also, when booting it shows random_seed: /etc/entropy-file: Not present, which I belive is consistent with rebooting behaviour. If I hard shutdown by pressing the power bottom, which I know I shouldn’t do, the random_seed is present and read at boot. Currently, I shutdown the laptop and press the power button when it starts to boot up again, but I would prefer if I could shutdown the system properly. NetBSD-8 running now is updated from the RC_2 release if that matters. Thanks Den mån 30 juli 2018 10:20Martin Husemann skrev: > On Sun, Jul 29, 2018 at 09:03:04PM +, Pedro Pinho wrote: > > All these are my last attempts at shutting down my machine. > > Please find the full log here, https://pastebin.com/PKEtRqWP > > Can you please give concrete commands that you invoke and explain > the result? Nothing in that log looks wrong. Ignore the syslog restart > messages. > > Martin >
Re: poweroff and shutdown -p now only reboot my machine
On Sun, Jul 29, 2018 at 09:03:04PM +, Pedro Pinho wrote: > All these are my last attempts at shutting down my machine. > Please find the full log here, https://pastebin.com/PKEtRqWP Can you please give concrete commands that you invoke and explain the result? Nothing in that log looks wrong. Ignore the syslog restart messages. Martin