Re: [gentoo-user] shutdown: /run/initctl: No such file or directory ???
On 03/30 06:02, Tom H wrote: > On Fri, Mar 30, 2018 at 4:36 PM, Mike Gilbert wrote: > > On Fri, Mar 30, 2018 at 3:56 PM, wrote: > >> > >> just a minute before I wanted to shutdown my Linux box...and... > >> shutdown: /run/initctl: No such file or directory > > > > See bug 651990. https://bugs.gentoo.org/651990 > > > > Either upgrade to sysvinit-2.89-r1, or run the following command > > before rebooting or changing runlevels. > > > > ln -s /dev/initctl /run/initctl > > 2.89?! A new version after so many years! > > Looking at the upstream changelog: > > Added Robert Millan's Debian patch to use /run/initctl as the named pipe > for communicating. This works around a limitation on the kFreeBSD branch > which prevents us from using /dev/initctl for pipes. > Hi, thanks for all the help. An update this morning has fixed the problem...but good to know the backgrounds and workarounds, if anything like that happens again... ;) Cheers! Meino
Re: [gentoo-user] shutdown: /run/initctl: No such file or directory ???
On Fri, Mar 30, 2018 at 4:36 PM, Mike Gilbert wrote: > On Fri, Mar 30, 2018 at 3:56 PM, wrote: >> >> just a minute before I wanted to shutdown my Linux box...and... >> shutdown: /run/initctl: No such file or directory > > See bug 651990. https://bugs.gentoo.org/651990 > > Either upgrade to sysvinit-2.89-r1, or run the following command > before rebooting or changing runlevels. > > ln -s /dev/initctl /run/initctl 2.89?! A new version after so many years! Looking at the upstream changelog: Added Robert Millan's Debian patch to use /run/initctl as the named pipe for communicating. This works around a limitation on the kFreeBSD branch which prevents us from using /dev/initctl for pipes.
Re: [gentoo-user] shutdown: /run/initctl: No such file or directory ???
On Fri, Mar 30, 2018 at 3:56 PM, wrote: > > just a minute before I wanted to shutdown my Linux box...and... > shutdown: /run/initctl: No such file or directory Isn't "/run/initctl" a Debianism?!
Re: [gentoo-user] shutdown: /run/initctl: No such file or directory ???
On Fri, Mar 30, 2018 at 3:56 PM, wrote: > Hi, > > just a minute before I wanted to shutdown my Linux box...and... > shutdown: /run/initctl: No such file or directory > See bug 651990. https://bugs.gentoo.org/651990 Either upgrade to sysvinit-2.89-r1, or run the following command before rebooting or changing runlevels. ln -s /dev/initctl /run/initctl
Re: [gentoo-user] shutdown: /run/initctl: No such file or directory ???
Meino: > just a minute before I wanted to shutdown my Linux box...and... > shutdown: /run/initctl: No such file or directory ... $ ls -l /run/initctl prw--- 1 root root 0 Mar 16 21:50 /run/initctl| I.e. it is a named pipe, which you can use to tell init things, like to shutdown. # man init | grep -A2 SIGUSR SIGUSR1 On receipt of this signals, init closes and re-opens its control fifo, /dev/initctl. Useful for bootscripts when /dev is remounted. So, try "kill -SIGUSR1 1" to make init recreate that pipe. NOTE: If you use something else than sysv-init, the above might not apply. Regards, /Karl Hammar --- Aspö Data Lilla Aspö 148 S-742 94 Östhammar Sweden +46 173 140 57
[gentoo-user] shutdown: /run/initctl: No such file or directory ???
Hi, just a minute before I wanted to shutdown my Linux box...and... shutdown: /run/initctl: No such file or directory Today I did the following ubdates Fri Mar 30 04:03:37 2018 <<< net-misc/dhcpcd-7.0.1 Fri Mar 30 04:03:41 2018 >>> net-misc/dhcpcd-7.0.2 Fri Mar 30 04:04:24 2018 <<< app-editors/nano-2.9.4 Fri Mar 30 04:04:32 2018 >>> app-editors/nano-2.9.5 Fri Mar 30 14:36:35 2018 >>> dev-python/pyyaml-3.12 Fri Mar 30 14:36:42 2018 <<< sys-apps/sysvinit-2.88-r9 Fri Mar 30 14:36:45 2018 >>> sys-apps/sysvinit-2.89 Fri Mar 30 14:36:56 2018 <<< sys-apps/portage-2.3.26 Fri Mar 30 14:37:01 2018 >>> sys-apps/portage-2.3.27 Fri Mar 30 14:37:17 2018 <<< app-portage/repoman-2.3.7 Fri Mar 30 14:37:23 2018 >>> app-portage/repoman-2.3.9 Fri Mar 30 14:37:32 2018 <<< media-radio/gpredict-2.2 Fri Mar 30 14:37:35 2018 >>> media-radio/gpredict-2.2.1 What may have killed /run/initctl ? /run has currently this content: zsh:1: no such file or directory: /sl total 68 -rw--- 1 root root 0 Mar 30 03:56 agetty.reload drwx-- 2 root root 40 Mar 30 03:55 alsasound drwx--x--- 2 root apache 40 Mar 30 03:55 apache2 drwxr-xr-x 2 root root 40 Mar 30 03:55 apache_ssl_mutex -rw-r--r-- 1 root root 6 Mar 30 16:40 atop.pid -rw-r--r-- 1 root root 5 Mar 30 03:55 autofs.pid -- 1 root root 5 Mar 30 03:55 autofs-running -rw-r--r-- 1 root root 5 Mar 30 03:55 cgred.pid srw-rw 1 root root 0 Mar 30 03:55 cgred.socket drwxr-xr-x 2 root root 80 Mar 30 03:55 ConsoleKit drwx-- 2 root root 40 Mar 30 03:55 cryptsetup drwxrwxr-x 2 root root 60 Mar 30 03:55 dbus -rw-r--r-- 1 root root 5 Mar 30 03:55 dbus.pid drwxr-xr-x 4 root root 80 Mar 30 21:48 dhcpcd -rw-r--r-- 1 root root 5 Mar 30 03:55 dhcpcd.pid srw-rw 1 root root 0 Mar 30 03:55 dhcpcd.sock srw-rw-rw- 1 root root 0 Mar 30 03:55 dhcpcd.unpriv.sock srwxrwxrwx 1 root root 0 Mar 30 03:55 fcron.fifo -rw-r--r-- 1 root root 5 Mar 30 03:55 fcron.pid -- 1 root root 0 Mar 30 03:55 fcron.reboot drwx-- 2 fetchmail nobody 40 Mar 30 03:55 fetchmail -rw-r--r-- 1 root root 5 Mar 30 03:55 gpm.pid drwxrwxr-x 3 root uucp 80 Mar 30 21:50 lock drwxrwxr-x 2 root root 60 Mar 30 03:55 lvm -rw-r--r-- 1 root root 5 Mar 30 03:55 lvmetad.pid -rw-r--r-- 1 root root 5 Mar 30 03:55 metalog.pid drwxr-xr-x 2 root root 40 Mar 30 03:55 mount drwxrwxr-x 14 root root360 Mar 30 03:56 openrc drwxr-xr-x 4 root root 80 Mar 30 18:17 pm-utils -rw--- 1 root root 52 Mar 30 03:55 slim.auth -rw-r--r-- 1 root root 5 Mar 30 03:55 slim.pid -rw--- 1 root root 5 Mar 30 03:55 smartd.pid drwxr-xr-x 2 root root 40 Mar 30 03:55 smokeping -rw-r--r-- 1 root root 5 Mar 30 03:55 spamd.pid -rw-r--r-- 1 root root 5 Mar 30 03:56 sshd.pid drwxrwxr-x 2 root root 60 Mar 30 03:55 tmpfiles.d drwxr-xr-x 8 root root180 Mar 30 18:12 udev -rw-rw-r-- 1 root utmp 4224 Mar 30 03:56 utmp The timestamps look very suspicious... Any idea of what has happened to initctl? Cheers Meino
[gentoo-user] shutdown -r now hangs in qemu-vm
Since updating app-emulation/libvirt and/or app-emulation/qemu (both
were updated at the same time) I have a problem executing "shutdown -r
now" in the vm ("shutdown -h now" works fine).
When I execute "shutdown -r now" in the vm the shutdown process runs
perfect until "Remounting root-filesystem readonly" and than it hangs
and I have to "Force Power Off" to reboot.
Any suggestion what could be wrong and what I can do to solve it?
--
Dan Johansson,
***
This message is printed on 100% recycled electrons!
***
0x2FB894AD.asc
Description: application/pgp-keys
smime.p7s
Description: S/MIME Cryptographic Signature
Re: [gentoo-user] Shutdown through systemctl as a normal user
On Fri, 2016-01-22 at 19:47 -0500, Mike Gilbert wrote: > On Sat, Jan 16, 2016 at 1:34 PM, lukash wrote: > > Hi all, > > > > I'm reading on the internet that systemctl poweroff should work for > > normal user if he is the only one logged in, he is logged in > > locally > > and his session is active. I seem to be meeting these conditions: > > > > # loginctl > > SESSIONUID USER SEAT > > 2 1000 lukash seat0 > > > > $ loginctl show-session 2 > > Id=2 > > User=1000 > > Name=lu > > Timestamp=Sat 2016-01-16 17:27:30 CET > > TimestampMonotonic=9614418 > > VTNr=7 > > Seat=seat0 > > Display=:0 > > Remote=no > > Service=lightdm > > Desktop=awesome > > Scope=session-2.scope > > Leader=529 > > Audit=2 > > Type=x11 > > Class=user > > Active=yes > > State=active > > IdleHint=no > > IdleSinceHint=0 > > IdleSinceHintMonotonic=0 > > > > But invoking the command gives me: > > > > $ systemctl poweroff > > Failed to set wall message, ignoring: Access denied > > Failed to power off system via logind: Access denied > > Failed to start poweroff.target: Access denied > > > > How is this supposed to work on Gentoo? > > Make sure you have USE=policykit set for sys-apps/systemd. That did it! Thanks! I feel kind of stupid now... Lukas
Re: [gentoo-user] Shutdown through systemctl as a normal user
On Sat, Jan 16, 2016 at 1:34 PM, lukash wrote: > Hi all, > > I'm reading on the internet that systemctl poweroff should work for > normal user if he is the only one logged in, he is logged in locally > and his session is active. I seem to be meeting these conditions: > > # loginctl >SESSIONUID USER SEAT > 2 1000 lukash seat0 > > $ loginctl show-session 2 > Id=2 > User=1000 > Name=lu > Timestamp=Sat 2016-01-16 17:27:30 CET > TimestampMonotonic=9614418 > VTNr=7 > Seat=seat0 > Display=:0 > Remote=no > Service=lightdm > Desktop=awesome > Scope=session-2.scope > Leader=529 > Audit=2 > Type=x11 > Class=user > Active=yes > State=active > IdleHint=no > IdleSinceHint=0 > IdleSinceHintMonotonic=0 > > But invoking the command gives me: > > $ systemctl poweroff > Failed to set wall message, ignoring: Access denied > Failed to power off system via logind: Access denied > Failed to start poweroff.target: Access denied > > How is this supposed to work on Gentoo? Make sure you have USE=policykit set for sys-apps/systemd.
Re: [gentoo-user] Shutdown through systemctl as a normal user
On Mon, 2016-01-18 at 14:56 -0800, Willie Matthews wrote: > On Mon, 18 Jan 2016 23:31:39 +0100 > lukash wrote: > > > On Mon, 2016-01-18 at 20:00 +0100, waben...@gmail.com wrote: > > > lukash wrote: > > > > > > > Hi all, > > > > > > > > I'm reading on the internet that systemctl poweroff should work > > > > for normal user if he is the only one logged in, he is logged > > > > in > > > > locally > > > > and his session is active. I seem to be meeting these > > > > conditions: > > > > > > > > # loginctl > > > > SESSIONUID USER SEAT > > > > 2 1000 lukash seat0 > > > > > > > > $ loginctl show-session 2 > > > > Id=2 > > > > User=1000 > > > > Name=lu > > > > Timestamp=Sat 2016-01-16 17:27:30 CET > > > > TimestampMonotonic=9614418 > > > > VTNr=7 > > > > Seat=seat0 > > > > Display=:0 > > > > Remote=no > > > > Service=lightdm > > > > Desktop=awesome > > > > Scope=session-2.scope > > > > Leader=529 > > > > Audit=2 > > > > Type=x11 > > > > Class=user > > > > Active=yes > > > > State=active > > > > IdleHint=no > > > > IdleSinceHint=0 > > > > IdleSinceHintMonotonic=0 > > > > > > > > But invoking the command gives me: > > > > > > > > $ systemctl poweroff > > > > Failed to set wall message, ignoring: Access denied > > > > Failed to power off system via logind: Access denied > > > > Failed to start poweroff.target: Access denied > > > > > > > > How is this supposed to work on Gentoo? > > > > > > > > Thanks in advance, > > > > Lukas > > > > > > IIRC "CONFIG_AUDIT" and "CONFIG_HAVE_ARCH_AUDITSYSCALL" must be > > > set > > > in the kernel configuration. But as I don't use this method I > > > cannot > > > say this for sure. > > > > Thanks. But I've got those in my kernel already... > > > > > -- > > > Regards > > > wabe > > > > > > > Try this https://wiki.archlinux.org/index.php/allow_users_to_shutdown > , > I think you might be happy with it. I don't have systemd personally > so > I don't have any experience with it. From what I read on the wiki, > this will be an easy fix. > > Instead of using users in the "Users without sudo privileges" > section, I > think you can also use groups without the hostname. All you would > have > to do is make a group that you would like to be able to shutdown or > whatever with the computer. > Thank you, but I wanted to make the systemd-logind path work instead of the sudo magic which I find kinda hackish. I think my system meets the requirements, although I am not so sure when 'it should work' is mentioned in various places, whether it is supposed there are (for example) some polkit rules present in the system (of which I didn't find any on my gentoo box). The wiki link you mentioned does lead to some more information about the permission checking which I'll investigate when I have more time. But otherwise, short of installing Arch somewhere and have a look if there's anything present that could make this work I am clueless :( Cheers, Lukas
Re: [gentoo-user] Shutdown through systemctl as a normal user
On Mon, 18 Jan 2016 23:31:39 +0100 lukash wrote: > On Mon, 2016-01-18 at 20:00 +0100, waben...@gmail.com wrote: > > lukash wrote: > > > > > Hi all, > > > > > > I'm reading on the internet that systemctl poweroff should work > > > for normal user if he is the only one logged in, he is logged in > > > locally > > > and his session is active. I seem to be meeting these conditions: > > > > > > # loginctl > > > SESSIONUID USER SEAT > > > 2 1000 lukash seat0 > > > > > > $ loginctl show-session 2 > > > Id=2 > > > User=1000 > > > Name=lu > > > Timestamp=Sat 2016-01-16 17:27:30 CET > > > TimestampMonotonic=9614418 > > > VTNr=7 > > > Seat=seat0 > > > Display=:0 > > > Remote=no > > > Service=lightdm > > > Desktop=awesome > > > Scope=session-2.scope > > > Leader=529 > > > Audit=2 > > > Type=x11 > > > Class=user > > > Active=yes > > > State=active > > > IdleHint=no > > > IdleSinceHint=0 > > > IdleSinceHintMonotonic=0 > > > > > > But invoking the command gives me: > > > > > > $ systemctl poweroff > > > Failed to set wall message, ignoring: Access denied > > > Failed to power off system via logind: Access denied > > > Failed to start poweroff.target: Access denied > > > > > > How is this supposed to work on Gentoo? > > > > > > Thanks in advance, > > > Lukas > > > > IIRC "CONFIG_AUDIT" and "CONFIG_HAVE_ARCH_AUDITSYSCALL" must be set > > in the kernel configuration. But as I don't use this method I cannot > > say this for sure. > > Thanks. But I've got those in my kernel already... > > > -- > > Regards > > wabe > > > Try this https://wiki.archlinux.org/index.php/allow_users_to_shutdown , I think you might be happy with it. I don't have systemd personally so I don't have any experience with it. From what I read on the wiki, this will be an easy fix. Instead of using users in the "Users without sudo privileges" section, I think you can also use groups without the hostname. All you would have to do is make a group that you would like to be able to shutdown or whatever with the computer. -- Willie Matthews matthews.willi...@gmail.com (702) 659-9966 pgpTqKuRmPajL.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Shutdown through systemctl as a normal user
On Mon, 2016-01-18 at 20:00 +0100, waben...@gmail.com wrote: > lukash wrote: > > > Hi all, > > > > I'm reading on the internet that systemctl poweroff should work for > > normal user if he is the only one logged in, he is logged in > > locally > > and his session is active. I seem to be meeting these conditions: > > > > # loginctl > > SESSIONUID USER SEAT > > 2 1000 lukash seat0 > > > > $ loginctl show-session 2 > > Id=2 > > User=1000 > > Name=lu > > Timestamp=Sat 2016-01-16 17:27:30 CET > > TimestampMonotonic=9614418 > > VTNr=7 > > Seat=seat0 > > Display=:0 > > Remote=no > > Service=lightdm > > Desktop=awesome > > Scope=session-2.scope > > Leader=529 > > Audit=2 > > Type=x11 > > Class=user > > Active=yes > > State=active > > IdleHint=no > > IdleSinceHint=0 > > IdleSinceHintMonotonic=0 > > > > But invoking the command gives me: > > > > $ systemctl poweroff > > Failed to set wall message, ignoring: Access denied > > Failed to power off system via logind: Access denied > > Failed to start poweroff.target: Access denied > > > > How is this supposed to work on Gentoo? > > > > Thanks in advance, > > Lukas > > IIRC "CONFIG_AUDIT" and "CONFIG_HAVE_ARCH_AUDITSYSCALL" must be set > in the kernel configuration. But as I don't use this method I cannot > say this for sure. Thanks. But I've got those in my kernel already... > -- > Regards > wabe >
Re: [gentoo-user] Shutdown through systemctl as a normal user
lukash wrote: > Hi all, > > I'm reading on the internet that systemctl poweroff should work for > normal user if he is the only one logged in, he is logged in locally > and his session is active. I seem to be meeting these conditions: > > # loginctl > SESSIONUID USER SEAT > 2 1000 lukash seat0 > > $ loginctl show-session 2 > Id=2 > User=1000 > Name=lu > Timestamp=Sat 2016-01-16 17:27:30 CET > TimestampMonotonic=9614418 > VTNr=7 > Seat=seat0 > Display=:0 > Remote=no > Service=lightdm > Desktop=awesome > Scope=session-2.scope > Leader=529 > Audit=2 > Type=x11 > Class=user > Active=yes > State=active > IdleHint=no > IdleSinceHint=0 > IdleSinceHintMonotonic=0 > > But invoking the command gives me: > > $ systemctl poweroff > Failed to set wall message, ignoring: Access denied > Failed to power off system via logind: Access denied > Failed to start poweroff.target: Access denied > > How is this supposed to work on Gentoo? > > Thanks in advance, > Lukas IIRC "CONFIG_AUDIT" and "CONFIG_HAVE_ARCH_AUDITSYSCALL" must be set in the kernel configuration. But as I don't use this method I cannot say this for sure. -- Regards wabe
[gentoo-user] Shutdown through systemctl as a normal user
Hi all, I'm reading on the internet that systemctl poweroff should work for normal user if he is the only one logged in, he is logged in locally and his session is active. I seem to be meeting these conditions: # loginctl SESSIONUID USER SEAT 2 1000 lukash seat0 $ loginctl show-session 2 Id=2 User=1000 Name=lu Timestamp=Sat 2016-01-16 17:27:30 CET TimestampMonotonic=9614418 VTNr=7 Seat=seat0 Display=:0 Remote=no Service=lightdm Desktop=awesome Scope=session-2.scope Leader=529 Audit=2 Type=x11 Class=user Active=yes State=active IdleHint=no IdleSinceHint=0 IdleSinceHintMonotonic=0 But invoking the command gives me: $ systemctl poweroff Failed to set wall message, ignoring: Access denied Failed to power off system via logind: Access denied Failed to start poweroff.target: Access denied How is this supposed to work on Gentoo? Thanks in advance, Lukas
Re: [gentoo-user] Shutdown, Gentoo and the Arietta.G25
> On Dec 1, 2014, at 23:03, Fernando Rodriguez > wrote: > >> On Monday, December 01, 2014 7:34:35 PM meino.cra...@gmx.de wrote: >> Dale [14-12-01 19:16]: >>> meino.cra...@gmx.de wrote: Hi, another >sigh< from an Arietta adventure... I sintalled Gentoo on an Arietta G25 (http://www.acmesystems.it/arietta). For this I used Robert Nelsons Kernel for armv5tel platforms, which boots fine (using at91bootstrap, no U-Boot). But: Shutdown (as recommmended by acmesystems "shutdown -h -H now") REBOOTS the system instead of powering it down. The hardware is not to blame: Using the original Debian rootfs and the kernel 3.16.1 (Robert Nelsons kernel is 3.17.3.) the powerdown works fine. Firstly I blamed the kernel...but when using the 3.16.1 kernel and the Gentoo rootfs the problem remains. Then I copied the Gentoo shutdown to the Debian rootfs, boot that and tries to shutdown the Debian Linux with it. shutdown cries "no /dev/initctl" adn shutdowns the system only for rebooting it. Ok...seems to be the shutdown executable. I copied the Debian shutdown to Gentoo and tries that: The systems reboots. Slowly but surely I begin to think, that I dont understand anything at > all of It would be relly good news, that... "man shutdown" on the Debian image informs me, that the manpages were not installed (embedded system...). Shutdown --version gives a short help of the usual options...but nothing more. What is the difference here? Isn't it, that all shutdown applications only send some instructions to the kernel and the kernel is the main actor in bringing the system down? Is there any shutdown guru ;) out there, who is able to shed some light into this problem ? :) Thank you very much in advance for any torch send into my direction! Best regards, Meino >>> >>> Just shooting in the dark here, try -h and -H but not at the same time? >>> Maybe having both is clashing in some weird way??? >>> >>> Dale >>> >>> :-) :-) >> >> Hi Dale, >> >> The "Trouble shooting FAQ"*) by acmesystems explicitely say "shutdown -h >> -H now" (and it works with the Debian rootfs)...but I will try "the >> other shutdowns" and will see, what happens, >> >> Best regards, >> Meino >> >> >> >> *) http://www.acmesystems.it/qa > > Looking at the code for sysvinit, all shutdown does is set some environment > variables and switch runlevel. The actual shutdown is done by halt and it's > done through the reboot system call with RB_POWER_OFF. > > So, since you said the Gentoo system doesn't work even with Debian's kernel > and the shutdown, then it must be that either Debian has a different halt, or > more likely your Gentoo system calls halt with different options. So check > your > inittab on Gentoo and make sure it calls halt in the same way. Hi meino The thing is as Fernando pointed out: Kernel powers off the hardware and a system call is used to instruct kernel to do so. Test your system. Perform a system call to shutdown the board. As you perform this system call the arietta will instantly eighter boot or shutdown. See system call man page to see the list of available system calls. This way you can make sure the system works as expected... When you have found the right system call, then you need to make init call that system call as the last command in run level 0. -- -Matti
Re: [gentoo-user] Shutdown, Gentoo and the Arietta.G25
On Mon, Dec 1, 2014 at 2:51 PM, wrote: > Jc García [14-12-01 20:36]: >> >> I've not seen you using the -P flag. >> > > That's why the manufacturer of the Arietta G25 - Acmesystems said > to use shutdown -h -H now for that purpose: > http://www.acmesystems.it/qa > Second question below the title "Arietta G25 just on top of the > page... > > Have you just tried using -P to make sure that it doesn't work? The instructions also say to use Debian, not Gentoo. Since most of the shutdown behavior is in userspace and using components that vary significantly between distros, I wouldn't blindly follow the instructions written for one distro and expect it to just work with a different distro. Maybe Debian has some bug that makes -P not work, but -H does work. Maybe OpenRC doesn't have that bug. -- Rich
Re: [gentoo-user] Shutdown, Gentoo and the Arietta.G25
On Monday, December 01, 2014 7:34:35 PM meino.cra...@gmx.de wrote: > Dale [14-12-01 19:16]: > > meino.cra...@gmx.de wrote: > > > Hi, > > > > > > another >sigh< from an Arietta adventure... > > > > > > I sintalled Gentoo on an Arietta G25 > > > (http://www.acmesystems.it/arietta). > > > > > > For this I used Robert Nelsons Kernel for armv5tel platforms, > > > which boots fine (using at91bootstrap, no U-Boot). > > > > > > But: Shutdown (as recommmended by acmesystems "shutdown -h -H now") > > > REBOOTS the system instead of powering it down. > > > > > > The hardware is not to blame: Using the original Debian rootfs > > > and the kernel 3.16.1 (Robert Nelsons kernel is 3.17.3.) the > > > powerdown works fine. > > > > > > Firstly I blamed the kernel...but when using the 3.16.1 kernel > > > and the Gentoo rootfs the problem remains. > > > > > > Then I copied the Gentoo shutdown to the Debian rootfs, boot that > > > and tries to shutdown the Debian Linux with it. > > > shutdown cries "no /dev/initctl" adn shutdowns the system only for > > > rebooting it. > > > > > > Ok...seems to be the shutdown executable. > > > > > > I copied the Debian shutdown to Gentoo and tries that: > > > The systems reboots. > > > > > > Slowly but surely I begin to think, that I dont understand anything at all of > > > It would be relly good news, > > > that... > > > > > > "man shutdown" on the Debian image informs me, that the manpages > > > were not installed (embedded system...). Shutdown --version gives > > > a short help of the usual options...but nothing more. > > > > > > What is the difference here? > > > Isn't it, that all shutdown applications only send some instructions > > > to the kernel and the kernel is the main actor in bringing the system > > > down? > > > > > > Is there any shutdown guru ;) out there, who is able to shed some > > > light into this problem ? :) > > > > > > Thank you very much in advance for any torch send into my direction! > > > Best regards, > > > Meino > > > > > > > Just shooting in the dark here, try -h and -H but not at the same time? > > Maybe having both is clashing in some weird way??? > > > > Dale > > > > :-) :-) > > > > Hi Dale, > > The "Trouble shooting FAQ"*) by acmesystems explicitely say "shutdown -h > -H now" (and it works with the Debian rootfs)...but I will try "the > other shutdowns" and will see, what happens, > > Best regards, > Meino > > > > *) http://www.acmesystems.it/qa > Also AFAICT the -H option just set an env variable INIT_HALT and it looks like OpenRC ignores it so look at your init scripts on Debian and see what it does when it is set. -- Fernando Rodriguez frodriguez.develo...@outlook.com PGP Key: http://keys.gnupg.net/pks/lookup?op=get&search=0xF6CE157FF9525C1C signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Shutdown, Gentoo and the Arietta.G25
On Monday, December 01, 2014 7:34:35 PM meino.cra...@gmx.de wrote: > Dale [14-12-01 19:16]: > > meino.cra...@gmx.de wrote: > > > Hi, > > > > > > another >sigh< from an Arietta adventure... > > > > > > I sintalled Gentoo on an Arietta G25 > > > (http://www.acmesystems.it/arietta). > > > > > > For this I used Robert Nelsons Kernel for armv5tel platforms, > > > which boots fine (using at91bootstrap, no U-Boot). > > > > > > But: Shutdown (as recommmended by acmesystems "shutdown -h -H now") > > > REBOOTS the system instead of powering it down. > > > > > > The hardware is not to blame: Using the original Debian rootfs > > > and the kernel 3.16.1 (Robert Nelsons kernel is 3.17.3.) the > > > powerdown works fine. > > > > > > Firstly I blamed the kernel...but when using the 3.16.1 kernel > > > and the Gentoo rootfs the problem remains. > > > > > > Then I copied the Gentoo shutdown to the Debian rootfs, boot that > > > and tries to shutdown the Debian Linux with it. > > > shutdown cries "no /dev/initctl" adn shutdowns the system only for > > > rebooting it. > > > > > > Ok...seems to be the shutdown executable. > > > > > > I copied the Debian shutdown to Gentoo and tries that: > > > The systems reboots. > > > > > > Slowly but surely I begin to think, that I dont understand anything at all of > > > It would be relly good news, > > > that... > > > > > > "man shutdown" on the Debian image informs me, that the manpages > > > were not installed (embedded system...). Shutdown --version gives > > > a short help of the usual options...but nothing more. > > > > > > What is the difference here? > > > Isn't it, that all shutdown applications only send some instructions > > > to the kernel and the kernel is the main actor in bringing the system > > > down? > > > > > > Is there any shutdown guru ;) out there, who is able to shed some > > > light into this problem ? :) > > > > > > Thank you very much in advance for any torch send into my direction! > > > Best regards, > > > Meino > > > > > > > Just shooting in the dark here, try -h and -H but not at the same time? > > Maybe having both is clashing in some weird way??? > > > > Dale > > > > :-) :-) > > > > Hi Dale, > > The "Trouble shooting FAQ"*) by acmesystems explicitely say "shutdown -h > -H now" (and it works with the Debian rootfs)...but I will try "the > other shutdowns" and will see, what happens, > > Best regards, > Meino > > > > *) http://www.acmesystems.it/qa > Looking at the code for sysvinit, all shutdown does is set some environment variables and switch runlevel. The actual shutdown is done by halt and it's done through the reboot system call with RB_POWER_OFF. So, since you said the Gentoo system doesn't work even with Debian's kernel and the shutdown, then it must be that either Debian has a different halt, or more likely your Gentoo system calls halt with different options. So check your inittab on Gentoo and make sure it calls halt in the same way. -- Fernando Rodriguez frodriguez.develo...@outlook.com PGP Key: http://keys.gnupg.net/pks/lookup?op=get&search=0xF6CE157FF9525C1C signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Shutdown, Gentoo and the Arietta.G25
Jc García [14-12-01 20:36]: > 2014-12-01 12:40 GMT-06:00 : > > Rich Freeman [14-12-01 19:16]: > >> On Mon, Dec 1, 2014 at 12:46 PM, wrote: > >> > What is the difference here? > >> > Isn't it, that all shutdown applications only send some instructions > >> > to the kernel and the kernel is the main actor in bringing the system > >> > down? > >> > > >> > >> About the only thing the kernel might have a role in is turning off > >> the power. Almost all of the shutdown logic is in userspace and it > >> isn't surprising that copying scripts between distros is going to > >> cause issues since the whole service management component varies > >> GREATLY across distros. Maybe if you're using systemd you could copy > >> between distros since that is more standardized, but even then there > >> can be differences. > >> > >> In a traditional sysvinit system usually shutting down is accomplished > >> by changing runlevels, which immediately starts/stops anything in > >> inittab (generally only gettys) and calls a script which does all the > >> actual work. > >> > >> If the issue is that userspace shuts down fine but the system reboots > >> instead of powering off that could be a couple of things which > >> shouldn't be too hard to track down. An obvious question is whether > >> the hardware even supports being powered off in the first place - this > >> isn't an ATX motherboard. Powering off a system can sometimes be > >> remarkably tricky depending on how standardized the platform is. I > >> was reading an article on it a few years ago and I think linux > >> actually implements several different mechanisms that get tried in > >> series, with the final fallback being a halt without powering off. > >> > >> -- > >> Rich > >> > > > > Hi Rich, > > > > AH! :) Thanks for the informations! > > > > From what you say, it is a kernel problem, since the kernel > > is the one who switches off the lights... > > > > But even if I use the same kernel as used for the Debian system > > it does not work... > > > > May be shutdown says "power off the system" and the kernel understands > > "reboot the system"? > > I mean: In principle the kernel would be able to poweroff the system > > but there are some communications difficulties with the guys from > > userland? ;) > > > > Best regards, > > Meino > > > > > > > I've always turned off across linux distros (BSD is other story) with: > > # shutdown -hP now > > the help says : > -h: halt after shutdown. > -P: halt action is to turn off power. > -H: halt action is to just halt. > > I've not seen you using the -P flag. > That's why the manufacturer of the Arietta G25 - Acmesystems said to use shutdown -h -H now for that purpose: http://www.acmesystems.it/qa Second question below the title "Arietta G25 just on top of the page...
Re: [gentoo-user] Shutdown, Gentoo and the Arietta.G25
2014-12-01 12:40 GMT-06:00 : > Rich Freeman [14-12-01 19:16]: >> On Mon, Dec 1, 2014 at 12:46 PM, wrote: >> > What is the difference here? >> > Isn't it, that all shutdown applications only send some instructions >> > to the kernel and the kernel is the main actor in bringing the system >> > down? >> > >> >> About the only thing the kernel might have a role in is turning off >> the power. Almost all of the shutdown logic is in userspace and it >> isn't surprising that copying scripts between distros is going to >> cause issues since the whole service management component varies >> GREATLY across distros. Maybe if you're using systemd you could copy >> between distros since that is more standardized, but even then there >> can be differences. >> >> In a traditional sysvinit system usually shutting down is accomplished >> by changing runlevels, which immediately starts/stops anything in >> inittab (generally only gettys) and calls a script which does all the >> actual work. >> >> If the issue is that userspace shuts down fine but the system reboots >> instead of powering off that could be a couple of things which >> shouldn't be too hard to track down. An obvious question is whether >> the hardware even supports being powered off in the first place - this >> isn't an ATX motherboard. Powering off a system can sometimes be >> remarkably tricky depending on how standardized the platform is. I >> was reading an article on it a few years ago and I think linux >> actually implements several different mechanisms that get tried in >> series, with the final fallback being a halt without powering off. >> >> -- >> Rich >> > > Hi Rich, > > AH! :) Thanks for the informations! > > From what you say, it is a kernel problem, since the kernel > is the one who switches off the lights... > > But even if I use the same kernel as used for the Debian system > it does not work... > > May be shutdown says "power off the system" and the kernel understands > "reboot the system"? > I mean: In principle the kernel would be able to poweroff the system > but there are some communications difficulties with the guys from > userland? ;) > > Best regards, > Meino > > > I've always turned off across linux distros (BSD is other story) with: # shutdown -hP now the help says : -h: halt after shutdown. -P: halt action is to turn off power. -H: halt action is to just halt. I've not seen you using the -P flag.
Re: [gentoo-user] Shutdown, Gentoo and the Arietta.G25
Rich Freeman [14-12-01 19:16]: > On Mon, Dec 1, 2014 at 12:46 PM, wrote: > > What is the difference here? > > Isn't it, that all shutdown applications only send some instructions > > to the kernel and the kernel is the main actor in bringing the system > > down? > > > > About the only thing the kernel might have a role in is turning off > the power. Almost all of the shutdown logic is in userspace and it > isn't surprising that copying scripts between distros is going to > cause issues since the whole service management component varies > GREATLY across distros. Maybe if you're using systemd you could copy > between distros since that is more standardized, but even then there > can be differences. > > In a traditional sysvinit system usually shutting down is accomplished > by changing runlevels, which immediately starts/stops anything in > inittab (generally only gettys) and calls a script which does all the > actual work. > > If the issue is that userspace shuts down fine but the system reboots > instead of powering off that could be a couple of things which > shouldn't be too hard to track down. An obvious question is whether > the hardware even supports being powered off in the first place - this > isn't an ATX motherboard. Powering off a system can sometimes be > remarkably tricky depending on how standardized the platform is. I > was reading an article on it a few years ago and I think linux > actually implements several different mechanisms that get tried in > series, with the final fallback being a halt without powering off. > > -- > Rich > Hi Rich, AH! :) Thanks for the informations! >From what you say, it is a kernel problem, since the kernel is the one who switches off the lights... But even if I use the same kernel as used for the Debian system it does not work... May be shutdown says "power off the system" and the kernel understands "reboot the system"? I mean: In principle the kernel would be able to poweroff the system but there are some communications difficulties with the guys from userland? ;) Best regards, Meino
Re: [gentoo-user] Shutdown, Gentoo and the Arietta.G25
Dale [14-12-01 19:16]: > meino.cra...@gmx.de wrote: > > Hi, > > > > another >sigh< from an Arietta adventure... > > > > I sintalled Gentoo on an Arietta G25 > > (http://www.acmesystems.it/arietta). > > > > For this I used Robert Nelsons Kernel for armv5tel platforms, > > which boots fine (using at91bootstrap, no U-Boot). > > > > But: Shutdown (as recommmended by acmesystems "shutdown -h -H now") > > REBOOTS the system instead of powering it down. > > > > The hardware is not to blame: Using the original Debian rootfs > > and the kernel 3.16.1 (Robert Nelsons kernel is 3.17.3.) the > > powerdown works fine. > > > > Firstly I blamed the kernel...but when using the 3.16.1 kernel > > and the Gentoo rootfs the problem remains. > > > > Then I copied the Gentoo shutdown to the Debian rootfs, boot that > > and tries to shutdown the Debian Linux with it. > > shutdown cries "no /dev/initctl" adn shutdowns the system only for > > rebooting it. > > > > Ok...seems to be the shutdown executable. > > > > I copied the Debian shutdown to Gentoo and tries that: > > The systems reboots. > > > > Slowly but surely I begin to think, that I dont understand anything at all > > of > > It would be relly good news, > > that... > > > > "man shutdown" on the Debian image informs me, that the manpages > > were not installed (embedded system...). Shutdown --version gives > > a short help of the usual options...but nothing more. > > > > What is the difference here? > > Isn't it, that all shutdown applications only send some instructions > > to the kernel and the kernel is the main actor in bringing the system > > down? > > > > Is there any shutdown guru ;) out there, who is able to shed some > > light into this problem ? :) > > > > Thank you very much in advance for any torch send into my direction! > > Best regards, > > Meino > > > > Just shooting in the dark here, try -h and -H but not at the same time? > Maybe having both is clashing in some weird way??? > > Dale > > :-) :-) > Hi Dale, The "Trouble shooting FAQ"*) by acmesystems explicitely say "shutdown -h -H now" (and it works with the Debian rootfs)...but I will try "the other shutdowns" and will see, what happens, Best regards, Meino *) http://www.acmesystems.it/qa
Re: [gentoo-user] Shutdown, Gentoo and the Arietta.G25
meino.cra...@gmx.de wrote: > Hi, > > another >sigh< from an Arietta adventure... > > I sintalled Gentoo on an Arietta G25 > (http://www.acmesystems.it/arietta). > > For this I used Robert Nelsons Kernel for armv5tel platforms, > which boots fine (using at91bootstrap, no U-Boot). > > But: Shutdown (as recommmended by acmesystems "shutdown -h -H now") > REBOOTS the system instead of powering it down. > > The hardware is not to blame: Using the original Debian rootfs > and the kernel 3.16.1 (Robert Nelsons kernel is 3.17.3.) the > powerdown works fine. > > Firstly I blamed the kernel...but when using the 3.16.1 kernel > and the Gentoo rootfs the problem remains. > > Then I copied the Gentoo shutdown to the Debian rootfs, boot that > and tries to shutdown the Debian Linux with it. > shutdown cries "no /dev/initctl" adn shutdowns the system only for > rebooting it. > > Ok...seems to be the shutdown executable. > > I copied the Debian shutdown to Gentoo and tries that: > The systems reboots. > > Slowly but surely I begin to think, that I dont understand anything at all of > It would be relly good news, > that... > > "man shutdown" on the Debian image informs me, that the manpages > were not installed (embedded system...). Shutdown --version gives > a short help of the usual options...but nothing more. > > What is the difference here? > Isn't it, that all shutdown applications only send some instructions > to the kernel and the kernel is the main actor in bringing the system > down? > > Is there any shutdown guru ;) out there, who is able to shed some > light into this problem ? :) > > Thank you very much in advance for any torch send into my direction! > Best regards, > Meino > Just shooting in the dark here, try -h and -H but not at the same time? Maybe having both is clashing in some weird way??? Dale :-) :-)
Re: [gentoo-user] Shutdown, Gentoo and the Arietta.G25
On Mon, Dec 1, 2014 at 12:46 PM, wrote: > What is the difference here? > Isn't it, that all shutdown applications only send some instructions > to the kernel and the kernel is the main actor in bringing the system > down? > About the only thing the kernel might have a role in is turning off the power. Almost all of the shutdown logic is in userspace and it isn't surprising that copying scripts between distros is going to cause issues since the whole service management component varies GREATLY across distros. Maybe if you're using systemd you could copy between distros since that is more standardized, but even then there can be differences. In a traditional sysvinit system usually shutting down is accomplished by changing runlevels, which immediately starts/stops anything in inittab (generally only gettys) and calls a script which does all the actual work. If the issue is that userspace shuts down fine but the system reboots instead of powering off that could be a couple of things which shouldn't be too hard to track down. An obvious question is whether the hardware even supports being powered off in the first place - this isn't an ATX motherboard. Powering off a system can sometimes be remarkably tricky depending on how standardized the platform is. I was reading an article on it a few years ago and I think linux actually implements several different mechanisms that get tried in series, with the final fallback being a halt without powering off. -- Rich
[gentoo-user] Shutdown, Gentoo and the Arietta.G25
Hi, another >sigh< from an Arietta adventure... I sintalled Gentoo on an Arietta G25 (http://www.acmesystems.it/arietta). For this I used Robert Nelsons Kernel for armv5tel platforms, which boots fine (using at91bootstrap, no U-Boot). But: Shutdown (as recommmended by acmesystems "shutdown -h -H now") REBOOTS the system instead of powering it down. The hardware is not to blame: Using the original Debian rootfs and the kernel 3.16.1 (Robert Nelsons kernel is 3.17.3.) the powerdown works fine. Firstly I blamed the kernel...but when using the 3.16.1 kernel and the Gentoo rootfs the problem remains. Then I copied the Gentoo shutdown to the Debian rootfs, boot that and tries to shutdown the Debian Linux with it. shutdown cries "no /dev/initctl" adn shutdowns the system only for rebooting it. Ok...seems to be the shutdown executable. I copied the Debian shutdown to Gentoo and tries that: The systems reboots. Slowly but surely I begin to think, that I dont understand anything at all of It would be relly good news, that... "man shutdown" on the Debian image informs me, that the manpages were not installed (embedded system...). Shutdown --version gives a short help of the usual options...but nothing more. What is the difference here? Isn't it, that all shutdown applications only send some instructions to the kernel and the kernel is the main actor in bringing the system down? Is there any shutdown guru ;) out there, who is able to shed some light into this problem ? :) Thank you very much in advance for any torch send into my direction! Best regards, Meino
Re: [gentoo-user] shutdown for non-root users?
On Mon, Mar 10, 2014 at 09:15:13PM +0100, Jarry wrote > Hi, > how can I allow other (not-root) users to shut down system? > > I tried to add them to /etc/shutdown.allow but it works only > for "Ctrl-Alt-Del". When they try shutdown per command line > (/sbin/shutdown -a -h now) they still get: > > shutdown: you must be root to do that! > Usage: ... > > Is there any way to achieve this without installing sudo? You seem to be under the impression that sudo is all-or-nothing. There is a safe compromise. You can specify which commands, with which parameters, are runnable as toot by which user. E.g. my desktop is "d531" and my regular user ID is "waltdnes". I have file /etc/sudoers.d/001 containing stuff like... waltdnes d531 = (root) NOPASSWD: /sbin/hwclock --systohc waltdnes d531 = (root) NOPASSWD: /usr/bin/openrdate -n -s ca.pool.ntp.org ...and I have a script ~/bin/settime #!/bin/bash /usr/bin/sudo /usr/bin/openrdate -n -s ca.pool.ntp.org /usr/bin/sudo /sbin/hwclock --systohc ...which sets my clock. You would want... userid machine_name = (root) NOPASSWD: /sbin/shutdown -a -h now ...in /etc/sudoers.d/001 *NOTE*. Use "visudo" to edit any sudoers file. Do not edit directly with vim/nano/emacs/etc. "man visudo" for further details. -- Walter Dnes I don't run "desktop environments"; I run useful applications
Re: [gentoo-user] shutdown for non-root users?
On Mon, 10 Mar 2014 21:15:13 +0100, Jarry wrote: > how can I allow other (not-root) users to shut down system? > > I tried to add them to /etc/shutdown.allow but it works only > for "Ctrl-Alt-Del". When they try shutdown per command line > (/sbin/shutdown -a -h now) they still get: > > shutdown: you must be root to do that! > Usage: ... > > Is there any way to achieve this without installing sudo? Yes, but why do things the hard way when this is exactly the type of situation tat sudo is designed to handle. Allow selected, or all, users to run sudo shutdown without a password and set up an alias from shutdown to sudo /sbin/shutdown. -- Neil Bothwick A real programmer never documents his code. It was hard to make, it should be hard to read signature.asc Description: PGP signature
Re: [gentoo-user] shutdown for non-root users?
If it's your home system and especial security is unimportant you can try next: chmod +s /sbin/halt and use /sbin/halt to achieve the same effect. You can use ACPI power button event (see /etc/acpi/events/default and uncomment appropriate line). Also there was method with dbus (searching the web will give suggestions). 2014-03-10 22:15 GMT+02:00 Jarry : > Hi, > how can I allow other (not-root) users to shut down system? > > I tried to add them to /etc/shutdown.allow but it works only > for "Ctrl-Alt-Del". When they try shutdown per command line > (/sbin/shutdown -a -h now) they still get: > > shutdown: you must be root to do that! > Usage: ... > > Is there any way to achieve this without installing sudo? > > Jarry > -- > ___ > This mailbox accepts e-mails only from selected mailing-lists! > Everything else is considered to be spam and therefore deleted. > > -- Regards, Nikita
[gentoo-user] shutdown for non-root users?
Hi, how can I allow other (not-root) users to shut down system? I tried to add them to /etc/shutdown.allow but it works only for "Ctrl-Alt-Del". When they try shutdown per command line (/sbin/shutdown -a -h now) they still get: shutdown: you must be root to do that! Usage: ... Is there any way to achieve this without installing sudo? Jarry -- ___ This mailbox accepts e-mails only from selected mailing-lists! Everything else is considered to be spam and therefore deleted.
Re: [gentoo-user] Shutdown options not available xfce4
On Sat, 25 Aug 2012 22:17:58 +0200 Sebastian Beßler wrote: > On 25.08.2012 20:54, john wrote: > > > > For the last few days whenever I start my PC the options to > > shutdown, restart, hibernate are greyed out in xfce. After > > restarting consolekit (which is already running) the options are > > available. I have rebuilt consolekit, xfce but unsure why this > > should start happening. > > Do you have the systemd useflag enabled? > > I had this effect after I enabled the useflag even if I had booted > using openrc. > > Greetings > > Sebastian Beßler > Perhaps should have checked this out earlier but found that slim is the problem. When I disable xdm and start xfce4 using startx I don't get the problem. Sorry I didn't check this earlier as been working for a long time. systemd use flag is not enabled. -- John D Maunder
Re: [gentoo-user] Shutdown options not available xfce4
On 25.08.2012 20:54, john wrote: > > For the last few days whenever I start my PC the options to shutdown, > restart, hibernate are greyed out in xfce. After restarting consolekit > (which is already running) the options are available. I have rebuilt > consolekit, xfce but unsure why this should start happening. Do you have the systemd useflag enabled? I had this effect after I enabled the useflag even if I had booted using openrc. Greetings Sebastian Beßler
[gentoo-user] Shutdown options not available xfce4
For the last few days whenever I start my PC the options to shutdown, restart, hibernate are greyed out in xfce. After restarting consolekit (which is already running) the options are available. I have rebuilt consolekit, xfce but unsure why this should start happening. Can anyone recommend how to stop this? -- John D Maunder
[gentoo-user] shutdown: "device and target are missing"
Hi, I noticed one strange message when doing full shutdown. It appears at the very end, before turning computer off: ... * Stopping fcron ... [ ok ] * Stopping syslog-ng ... [ ok ] * Terminating remaining processes ... [ ok ] * Killing remaining processes ... [ ok ] * Saving dependency cache ... [ ok ] Device and target are missing; try '--help' for more information What does the last message mean? I have three nearly identical machines, and I see this message only on one of them. Seems to me like some typo-error, but obviously, logs do not say anything because log-server is already stopped... BTW, it is mostly stable system except for makedev, openrc, baselayout and sysvinit being ~amd64 (using baselayout-2)... Jarry -- ___ This mailbox accepts e-mails only from selected mailing-lists! Everything else is considered to be spam and therefore deleted.
RE: [gentoo-user] Shutdown -h now is not powering down system.
halt -dp worked for me...never tried it before. Now, I did do a couple
of things. I upgraded my kernel to 2.6.20r8 and set the acpi=force
kernel parameter. I don't know whether the acpi=force paramenter fixed
the problem. I did see the gentoo shutdown.sh script (which you can view
at the bottom of this message) and it seems to call the halt command
with the options -dp. This means that before the same halt -dp was being
used and the system did not shutdown properly. Now I manually enter the
halt -dp command and it works flawlessly. So, maybe it was the kernel
upgrade or the acpi=force kernel parameter that is causing it to work.
# Copyright 1999-2006 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
opts="-d"
[ "${INIT_HALT}" != "HALT" ] && opts="${opts}p" # here it is
[ "${RC_DOWN_INTERFACE}" = "yes" ] && opts="${opts}i"
[ "${RC_DOWN_HARDDISK}" = "yes" ] && opts="${opts}h"
/sbin/halt "${opts}"
# hmm, if the above failed, that's kind of odd ...
# so let's force a halt
/sbin/halt -f
On Fri, 2007-06-01 at 12:47 +0900, [EMAIL PROTECTED] wrote:
>
> > -Original Message-
> > From: Richard Marz [mailto:[EMAIL PROTECTED]
> > Sent: Friday, June 01, 2007 11:40 AM
> > To: gentoo-user@lists.gentoo.org
> > Subject: Re: [gentoo-user] Shutdown -h now is not powering
> > down system.
> >
> >
> > No. But, I will try it now. I'll let you know if it works in
> > a few minutes because I'm downloading the latests kernel
> > sources. On Thu, 2007-05-31 at 23:30 -0300, Davi wrote:
> > > shutdown -h now -P
> >
> > --
> > [EMAIL PROTECTED] mailing list
> >
>
> If shutodwn -h now -P doesn't work, try
> shutdown -P -h now
>
> I know that is just a matter of symantics, but a lot
> of programs want the "options" all in one spot. ^^;;
> Not sure about this one.
>
--
[EMAIL PROTECTED] mailing list
Re: [gentoo-user] Shutdown -h now is not powering down system.
I'll try this as well. On Thu, 2007-05-31 at 22:57 -0500, Dale wrote: > Richard Marz wrote: > > I have all the appropriate power management interfaces enabled in my > > kernel. ACPI is the one my system uses, but I've also tried APM and my > > system still doesn't manage to shut the power off on it's own. My > > motherboard is ATX but I'm forced to shut it down as if it were an AT > > mobo. Is there anything else that might have to be enabled in the kernel > > before the shutdown command can fully function. Any help would be > > appreciated. Thanks. > > > > > > Naturally this may not work for you but I use this one under APM: > > > [*] Use real mode APM BIOS call to power off > > I have video turned on under ACPI but I have no clue why. :/This is > my kernel version: > > > [EMAIL PROTECTED] / # uname -r > > 2.6.18-gentoo-r6 > > [EMAIL PROTECTED] / # > > Hope that helps, maybe. LOL > > Dale > > :-) :-) :-) > > > -- > www.myspace.com/-remove-me-dalek1967 > > Copy n paste then remove the -remove-me- part. > -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Shutdown -h now is not powering down system.
My Bios is up to date. It's not the BIOS. Shutdown has been confirmed to work with linux and freebsd kernels on my machine in the past. On Thu, 2007-05-31 at 23:51 -0300, Norberto Bensa wrote: > Richard Marz wrote: > > I have all the appropriate power management interfaces enabled in my > > kernel. ACPI is the one my system uses, but I've also tried APM and my > > How old is your bios? > > Have you tried acpi=force kernel param? -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Shutdown -h now is not powering down system.
I will try that right now. On Thu, 2007-05-31 at 23:51 -0300, Norberto Bensa wrote: > Richard Marz wrote: > > I have all the appropriate power management interfaces enabled in my > > kernel. ACPI is the one my system uses, but I've also tried APM and my > > How old is your bios? > > Have you tried acpi=force kernel param? -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Shutdown -h now is not powering down system.
It seems to be giving me the same behaviour as shutdown -h now. On Thu, 2007-05-31 at 22:39 -0400, Richard Marz wrote: > No. But, I will try it now. I'll let you know if it works in a few > minutes because I'm downloading the latests kernel sources. > On Thu, 2007-05-31 at 23:30 -0300, Davi wrote: > > shutdown -h now -P > -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Shutdown -h now is not powering down system.
Richard Marz wrote: > I have all the appropriate power management interfaces enabled in my > kernel. ACPI is the one my system uses, but I've also tried APM and my > system still doesn't manage to shut the power off on it's own. My > motherboard is ATX but I'm forced to shut it down as if it were an AT > mobo. Is there anything else that might have to be enabled in the kernel > before the shutdown command can fully function. Any help would be > appreciated. Thanks. > > Naturally this may not work for you but I use this one under APM: > [*] Use real mode APM BIOS call to power off I have video turned on under ACPI but I have no clue why. :/This is my kernel version: > [EMAIL PROTECTED] / # uname -r > 2.6.18-gentoo-r6 > [EMAIL PROTECTED] / # Hope that helps, maybe. LOL Dale :-) :-) :-) -- www.myspace.com/-remove-me-dalek1967 Copy n paste then remove the -remove-me- part. -- [EMAIL PROTECTED] mailing list
RE: [gentoo-user] Shutdown -h now is not powering down system.
> -Original Message- > From: Richard Marz [mailto:[EMAIL PROTECTED] > Sent: Friday, June 01, 2007 11:40 AM > To: gentoo-user@lists.gentoo.org > Subject: Re: [gentoo-user] Shutdown -h now is not powering > down system. > > > No. But, I will try it now. I'll let you know if it works in > a few minutes because I'm downloading the latests kernel > sources. On Thu, 2007-05-31 at 23:30 -0300, Davi wrote: > > shutdown -h now -P > > -- > [EMAIL PROTECTED] mailing list > If shutodwn -h now -P doesn't work, try shutdown -P -h now I know that is just a matter of symantics, but a lot of programs want the "options" all in one spot. ^^;; Not sure about this one. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Shutdown -h now is not powering down system.
Richard Marz wrote: > I have all the appropriate power management interfaces enabled in my > kernel. ACPI is the one my system uses, but I've also tried APM and my How old is your bios? Have you tried acpi=force kernel param? -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Shutdown -h now is not powering down system.
No. But, I will try it now. I'll let you know if it works in a few minutes because I'm downloading the latests kernel sources. On Thu, 2007-05-31 at 23:30 -0300, Davi wrote: > shutdown -h now -P -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Shutdown -h now is not powering down system.
Em Quinta 31 Maio 2007 23:24, Richard Marz escreveu: > I have all the appropriate power management interfaces enabled in my > kernel. ACPI is the one my system uses, but I've also tried APM and my > system still doesn't manage to shut the power off on it's own. My > motherboard is ATX but I'm forced to shut it down as if it were an AT > mobo. Is there anything else that might have to be enabled in the kernel > before the shutdown command can fully function. Any help would be > appreciated. Thanks. Have you tried: # shutdown -h now -P ? HTH -- Davi Vidal [EMAIL PROTECTED] [EMAIL PROTECTED] -- "Religion, ideology, resources, land, spite, love or "just because"... No matter how pathetic the reason, it's enough to start a war. " Por favor não faça top-posting, coloque a sua resposta abaixo desta linha. Please don't do top-posting, put your reply below the following line. pgpc7SWEiLnKW.pgp Description: PGP signature
[gentoo-user] Shutdown -h now is not powering down system.
I have all the appropriate power management interfaces enabled in my kernel. ACPI is the one my system uses, but I've also tried APM and my system still doesn't manage to shut the power off on it's own. My motherboard is ATX but I'm forced to shut it down as if it were an AT mobo. Is there anything else that might have to be enabled in the kernel before the shutdown command can fully function. Any help would be appreciated. Thanks. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Shutdown pauses partway with "Give root password"
Hans-Werner Hilse wrote: > Maybe you can cat your /proc/mounts > next time you're in that single-user mode? It might make things more > clear... > 3 power cycles later I duplicated the problem. Here is /proc/mounts, transcribed by hand. There is nothing obvious wrong here (to me) except that the filesystems are still rw. /proc/mounts: rootfs / rootfs rw 0 0 /dev/root / ext2 rw,noatime,nogrpid 0 0 proc /proc proc rw 0 0 sysfs /sys sysfs rw 0 0 udev /dev tmpfs rw,nosuid 0 0 devpts /dev/pts devpts rw 0 0 /dev/hda6 /usr ext2 rw,noatime,nogrpid 0 0 /dev/hda7 /var ext2 rw,noatime,nogrpid 0 0 shm /dev/shm tmpfs rw,nosuid,nodev,noexec 0 0 usbfs /proc/bus/usb usbfs rw 0 0 At this point, I manually remounted the 3 local partitions ro mount -n -o remount,ro / etc which went cleanly, and /proc/mounts now shows them ro. Is there any chance this could be a race condition thing, in which some processes aren't fully shut down yet when halt.sh tries to umount or remount? But they're all shut down now (a couple of minutes later) so the remounts go cleanly? Finally, after remounting the partitions (above), I pressed Ctrl-D to kill the sulogin shell, and the machine rebooted. It didn't power off, as I might have expected. glen -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Shutdown pauses partway with "Give root password"
Hans-Werner Hilse wrote: > Hi, > > On Tue, 09 May 2006 07:20:57 -0700 glen martin <[EMAIL PROTECTED]> > wrote: > >> Resending ... anyone have a clue as to why the "Give root password for >> maintenance ..." prompt would come up occasionally at shutdown time? >> > That's "sulogin". Did you mess up your /etc/inittab (like uncommenting > that line referring to sulogin)? > Nope, I don't recall ever changing that file on this system, and checking I find that this line is still commented. Though that would probably have been a problem. :) > But I rather guess its an unclean umount and sulogin is spawned > from /etc/init.d/halt.sh (l.189). > Possibly. Looking at that file it seems as if there's a 10 second(?) timeout on sulogin spawned from halt.sh. This one doesn't go away in any reasonable period of time. Also it looks as if there should be some messages about remounting and such before that sulogin would spawn, and I don't see such messages (presuming they should show up on this console). If it is starting from halt.sh, is there any chance this could be a race condition thing, in which some processes aren't fully shut down yet when halt tries to umount? > Maybe you can cat your /proc/mounts > next time you're in that single-user mode? It might make things more > clear... I'll try this. Thanks for the suggestions, glen -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Shutdown pauses partway with "Give root password"
Hi, On Tue, 09 May 2006 07:20:57 -0700 glen martin <[EMAIL PROTECTED]> wrote: > Resending ... anyone have a clue as to why the "Give root password for > maintenance ..." prompt would come up occasionally at shutdown time? That's "sulogin". Did you mess up your /etc/inittab (like uncommenting that line referring to sulogin)? But I rather guess its an unclean umount and sulogin is spawned from /etc/init.d/halt.sh (l.189). Maybe you can cat your /proc/mounts next time you're in that single-user mode? It might make things more clear... -hwh -- gentoo-user@gentoo.org mailing list
[gentoo-user] Shutdown pauses partway with "Give root password"
Resending ... anyone have a clue as to why the "Give root password for maintenance ..." prompt would come up occasionally at shutdown time? >>> Well, this is weird. We've all seen "Give root password for maintenance (or type Control-D to continue):", usually after an unclean shutdown. I'm getting it on shutdown itself. I've never even heard of this, and searching google I haven't found any reference to it. It isn't happening every time - it'll go 2 or 3 or 6 (but certainly not 4 or 5 :b) times with clean predictable shutdowns. I can't tell that anything is different in the times I shutdown fails - there aren't any symptoms of any misbehaviour until the message itself. This is a home theatre PC running MythTV. Frontend only, so there are no fancy drivers in the system, just video (nvidia 8756 driver), sound (snd_hda_intel), and lirc with streamzap. System was build from scratch for this purpose, recently, so it is pretty up to date. P4 with hyperthreading. Normally runs with no keyboard or mouse or VGA, only an SVIDEO-out from an NVidia card. BIOS has obviously been set to ignore post errors given the lack of keyboard. Myth running or not running is irrelevant, I've seen the shutdown problem in both situations. I've also seen the problem whether shutting down with a quick press to the power button, or using ssh to run a shutdown command. Here's a sequence: - press power button - this is presumably caught by acpid, which turns it into an "init 0" command - hdd lights blink, eventually X is stopped - when X stops, that initial login prompt that came out before X started is now displayed again, and right there I get the "Give root password ..." prompt. Sometimes the svideo-out console hasn't been restored so I can't see any of this, it is only on a connected monitor (if there is a connected monitor). Usually the svideo-out console is restored on X shutdown, so this does in fact display. After this happened a few times and didn't seem to be going away on its own :) I grumbled, dug up a keyboard and plugged it in, entered the root password. The log shows ntpd, sshd and syslog-ng shutdowns. There are no messages following the syslog-ng shutdown. :) ifconfig returns nothing. runlevel says "3 0" rc-status exhibits poor grammar "* Could not local current runlevel in /var/lib/init.d/softlevel * Assuming current runlevel is 'single'" Sure enough, there is no softlevel file at this point in a partway shutdown system. df shows local partitions (/, /var, /usr) still mounted, and the sole NFS mount has been taken down. local partitions are all ext2, no lvm or anything fancy. kernel is 2.6.16-gentoo-r3 System is vanilla, except for ~x86 keywords on nvidia-kernel and nvidia-driver to get the recent 8756 versions. Any suggestions on how to further debug? Or suggestions as to what may be going on? Thanks, glen -- gentoo-user@gentoo.org mailing list
[gentoo-user] Shutdown halts partway with "Give root password"
Well, this is weird. We've all seen "Give root password for maintenance (or type Control-D to continue):", usually after an unclean shutdown. I'm getting it on shutdown itself. I've never even heard of this, and searching google I haven't found any reference to it. This is a home theatre PC running MythTV. Frontend only, so there are no fancy drivers in the system, just video (nvidia 8756 driver), sound (snd_hda_intel), and lirc with streamzap. System was build from scratch for this purpose, recently, so it is pretty up to date. P4 with hyperthreading. Normally runs with no keyboard or mouse or VGA, only an SVIDEO-out from an NVidia card. BIOS has obviously been set to ignore boot errors. Myth running or not running is irrelevant, I've seen the shutdown problem in both situations. I've also seen the problem whether shutting down with a quick press to the power button, or using ssh to run a shutdown command. Here's a sequence: - press power button - this is presumably caught by acpid, which turns it into an "init 0" command - hdd lights blink, eventually X is stopped - when X stops, that initial login prompt that came out before X started is now displayed again, and right there I get the "Give root password ..." prompt. Sometimes the svideo-out console hasn't been restored so I can't see any of this, it is only on a connected monitor (if there is a connected monitor). Usually the svideo-out console is restored on X shutdown, so this does in fact display. After this happened a few times and didn't seem to be going away on its own :) I grumbled, dug up a keyboard and plugged it in, entered the root password. The log shows ntpd, sshd and syslog-ng shutdowns. There are no messages following the syslog-ng shutdown. :) ifconfig returns nothing. runlevel says "3 0" rc-status exhibits poor grammar "* Could not local current runlevel in /var/lib/init.d/softlevel * Assuming current runlevel is 'single'" Sure enough, there is no softlevel file at this point in a partway shutdown system. df shows local partitions (/, /var, /usr) still mounted, and the sole NFS mount has been taken down. local partitions are all ext2, no lvm or anything fancy. kernel is 2.6.16-gentoo-r3 System is vanilla, except for ~x86 keywords on nvidia-kernel and nvidia-driver to get the recent 8756 versions. Any suggestions on how to further debug? Or suggestions as to what may be going on? Thanks, glen -- gentoo-user@gentoo.org mailing list
[gentoo-user] Shutdown of hplip and adsl
Hello, when i shutdown my computer two failures are popping up. * Stopping hpiod ... start-stop-daemon: warning: failed to kill 13172: No such process start-stop-daemon: warning: failed to kill 13168: No such process * Stopping hpssd ... * Stopping eth0 * Bringing down eth0 * Stopping ADSL for eth0 adsl-stop: The adsl-connect script (PID 8863) appears to have died * Shutting down eth0 ... Does anybody know what this means? Is this just a problem with the hpiod and net.eth0 init-scripts, or is it something more serious. Thank you in advance, Daniel -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Shutdown/Restart Issue
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Martins Steinbergs wrote: >On Friday 04 November 2005 20:49, C. Beamer wrote: > >>Hi All, >> >>Recently, I've started to experience an issue when trying to restart >>or shutdown my computer using the K menu "Log Out" selection, which >>gives the options to "End Current Session", "Restart the Computer", >>"Turn of the Computer" and of course, "Cancel". If I select to >>restart or turn off the computer, the computer will do neither. My >>monitor shuts down, but the computer itself neither restarts or shuts >>off depending on which selection I've made. > > >i,v run into this problem few weeks ago too with no luck fixing it. yes, and >sometimes shutdown from console fails too. >only guess in list was - "It seems X f***s up your video memory, or something >of this kind". Anyway should check forums and bugs for something similar. Well, I'm certainly not an authority here, but based on your comment, I do recall that when I did a recent update (either the emerge of Open Office 2.0 or the upgrade of MySQL), one of them changed some files that were related to X and QT (sorry, this isn't a very good description - I just saw the listing go by on the screen). At the end of the emerge, I got told that some configuration files in /etc had changed and what to do to find out out the files were. When I ran etc-update, it then gave me 3 choices regarding what to do -1, -3, and - -5. I chose the -3 options, which replaces the config files. However, even knowing this, and surmising that this might be the problem, I have no idea what to do to correct it. Regards, Colleen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDbINb7FsR4jhcRJoRAizDAKDFaHqCqjWzypohH/4Z3rbrjLsRhQCgx7ZD 2UKDOF/UhVAd3TS7kmZyJfA= =hG2/ -END PGP SIGNATURE-
Re: [gentoo-user] Shutdown/Restart Issue
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Philip Webb wrote: >On Friday 04 November 2005 20:49, C. Beamer wrote: > >>Recently, when trying to restart or shutdown my computer >>using the K menu "Log Out" selection, which gives the options >>to "End Current Session", "Restart the Computer", "Turn of the Computer". >>If I select to restart or turn off, my monitor shuts down, >>but the computer itself neither restarts or shuts off. > > >For "shut off", the problem could result from a recent kernel update, >if you didn't activate the config line to allow power management. >I'm not sure if that would affect "restart" as well. >That's just 1 suggestion: HTH. > Not the case in this situation. True, when I did an emerge recently, it downloaded new kernel sources, but I haven't installed them yet. (This is because I am working on something that has a deadline and I've never updated the kernel in Gentoo before. Despite the fact that the Gentoo documentation is excellent, I don't want to risk making a "boo-boo" and then being at a point where I might have to spend days correcting my mistake.) Regards, Colleen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDbH937FsR4jhcRJoRAk/1AKC4nqAfcYWdFnwOtPe2owM3SkkGxQCg1yzN rt2jAuqqvbYrUFGdn5dC9Qc= =gI0v -END PGP SIGNATURE-
Re: [gentoo-user] Shutdown/Restart Issue
On Friday 04 November 2005 20:49, C. Beamer wrote: > Recently, when trying to restart or shutdown my computer > using the K menu "Log Out" selection, which gives the options > to "End Current Session", "Restart the Computer", "Turn of the Computer". > If I select to restart or turn off, my monitor shuts down, > but the computer itself neither restarts or shuts off. For "shut off", the problem could result from a recent kernel update, if you didn't activate the config line to allow power management. I'm not sure if that would affect "restart" as well. That's just 1 suggestion: HTH. -- ,, SUPPORT ___//___, Philip Webb : [EMAIL PROTECTED] ELECTRIC /] [] [] [] [] []| Centre for Urban & Community Studies TRANSIT`-O--O---' University of Toronto -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Shutdown/Restart Issue
On Friday 04 November 2005 20:49, C. Beamer wrote: > Hi All, > > Recently, I've started to experience an issue when trying to restart > or shutdown my computer using the K menu "Log Out" selection, which > gives the options to "End Current Session", "Restart the Computer", > "Turn of the Computer" and of course, "Cancel". If I select to > restart or turn off the computer, the computer will do neither. My > monitor shuts down, but the computer itself neither restarts or shuts > off depending on which selection I've made. i,v run into this problem few weeks ago too with no luck fixing it. yes, and sometimes shutdown from console fails too. only guess in list was - "It seems X f***s up your video memory, or something of this kind". Anyway should check forums and bugs for something similar. martins -- Linux 2.6.13 AMD Athlon(tm) 64 Processor 3200+ 09:46:18 up 45 min, 5 users, load average: 0.02, 0.09, 0.55 -- gentoo-user@gentoo.org mailing list
[gentoo-user] Shutdown/Restart Issue
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi All, Recently, I've started to experience an issue when trying to restart or shutdown my computer using the K menu "Log Out" selection, which gives the options to "End Current Session", "Restart the Computer", "Turn of the Computer" and of course, "Cancel". If I select to restart or turn off the computer, the computer will do neither. My monitor shuts down, but the computer itself neither restarts or shuts off depending on which selection I've made. I *can* restart or shutdown properly if I do it from the command line in a terminal window. This probably isn't a specific Gentoo issue. It *could* be a KDE issue, but I haven't done anything to KDE. When I installed KDE in September, I emerged kde-meta. I don't recall if there have been updates since then, but I know that I could shutdown or restart using the menu selection and no changes were made to KDE since before this behaviour started. This seemed to start around the same time as I upgraded mysql. I don't know specifically if that had anything to do with it. I'm just saying that this behaviour started around that time and up until then, everything was fine. Any ideas? Regards, Colleen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDa60h7FsR4jhcRJoRAh8uAJ9jLGfiwOKvEOSUIM/ZT68athfCNACguDYZ wfiSmWu9NoIINEgEgJPY/pM= =XoUS -END PGP SIGNATURE- -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] shutdown, restart problem
On Tuesday 25 October 2005 23:25, b.n. wrote: > >>>when xserver closes there is mess on screen and i > >>>loose any control over - just power button. Any ideas where to look? I > >>>dont keep track but possibly this is after baselayout and udev upgrade. > > Hmm. > It seems X f***s up your video memory, or something of this kind. > > What video card and corresponding Xorg driver are you using? > > m. Hi, Shuting down from console (X still runing) goes well but from within X it fails, is there different scripts with different order services are shut down? Xorg Latest version installed: 6.8.2-r6 mar bin # ./fglrxinfo display: :0.0 screen: 0 OpenGL vendor string: ATI Technologies Inc. OpenGL renderer string: RADEON 9600 Generic OpenGL version string: 1.3.5395 (X4.3.0-8.18.6) mar bin # ./fgl_glxgears 1856 frames in 5.0 seconds = 371.200 FPS 2039 frames in 5.0 seconds = 407.800 FPS -- Linux 2.6.13 AMD Athlon(tm) 64 Processor 3200+ -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] shutdown, restart problem
when xserver closes there is mess on screen and i loose any control over - just power button. Any ideas where to look? I dont keep track but possibly this is after baselayout and udev upgrade. Hmm. It seems X f***s up your video memory, or something of this kind. What video card and corresponding Xorg driver are you using? m. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] shutdown, restart problem
On Monday 24 October 2005 16:17, b.n. wrote: > > and cant > > > > find any logs on that. > > Do you mean xorg error logs and /var/log/messages say nothing? yes, logs has nothing relevant to any shutdown tasks > > > when xserver closes there is mess on screen and i > > loose any control over - just power button. Any ideas where to look? I > > dont keep track but possibly this is after baselayout and udev upgrade. > > What happens if you try to switch to a console with your xserver still > open? Anyway you can halt from inside X... i can do that, and i can switch back. ok, ill try halt from console, not kdm or gdm provided shutdown and restart. i did revdep-rebuild but there nothing important, just imagemagic and k3b martins -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] shutdown, restart problem
> and cant find any logs on that. Do you mean xorg error logs and /var/log/messages say nothing? when xserver closes there is mess on screen and i loose any control over - just power button. Any ideas where to look? I dont keep track but possibly this is after baselayout and udev upgrade. What happens if you try to switch to a console with your xserver still open? Anyway you can halt from inside X... m. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] shutdown, restart problem
On Mon, 2005-10-24 at 00:28 +0300, Martins Steinbergs wrote: > i run into this problem, calling for shutdown or restart wont work, and cant > find any logs on that. when xserver closes there is mess on screen and i > loose any control over - just power button. Any ideas where to look? I dont > keep track but possibly this is after baselayout and udev upgrade. Do you mean it _used_ to work, and doesn't any more, or it never worked properly? Do you have a laptop? What display driver are you using for X? Are you using a framebuffer console? I suspect it may be your X driver conflicting with your framebuffer driver. HTH, -- Iain Buchanan <[EMAIL PROTECTED]> -- gentoo-user@gentoo.org mailing list
[gentoo-user] shutdown, restart problem
hi, i run into this problem, calling for shutdown or restart wont work, and cant find any logs on that. when xserver closes there is mess on screen and i loose any control over - just power button. Any ideas where to look? I dont keep track but possibly this is after baselayout and udev upgrade. Martins -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Shutdown Issues
On Sun, 17 Jul 2005 11:12:13 -0300 (ART) "E. Pereira" <[EMAIL PROTECTED]> wrote: > During the shutdown Gentoo brings down my eth0 > connection, but my computer is connected to a router > that uses xDSL for connection, so my questions is: > Can I remove this, this way I won't have to reconnect > my xDSL connection? Or this shouldn't interfer in my > connection I I'm having to reconnect for other > reasons? > > Thanks, > e. pereira > This should interfere with your xDSL connection, afaik. I would guess that the xDSL connection is timing out. My router has options that tell it to create the connection on requirement or to keep it up all the time. Perhaps fiddling with any similar settings will solve the problem. -- Tom Wesley <[EMAIL PROTECTED]> pgpvdzT5BYQmJ.pgp Description: PGP signature
Re: [gentoo-user] Shutdown Issues
E. Pereira schreef: > During the shutdown Gentoo brings down my eth0 > connection, but my computer is connected to a router > that uses xDSL for connection, so my questions is: > Can I remove this, this way I won't have to reconnect > my xDSL connection? Or this shouldn't interfer in my > connection I I'm having to reconnect for other > reasons? > > Thanks, > e. pereira > I'm no network guru (by a long shot), but afaik, and ime (my PC is connected to a router with inbuilt modem), shutting down one PC should not affect the connection for others, because 1) DSL is "always on", and 2) your router should be directly connected to the DSL modem, thus unless your PC is turning the modem or the router off somehow (either of which would break the connection), the router should be able to ... route... the Internet connection for the other PCs on the network to the modem. Bringing down eth0 (turning off your PC), should just remove you from the network. That's the whole point of having a router (at least for me; it was driving me nuts that I had no connection whenever my Windows-using bf had to reboot for whatever reason, when we were stuck with software routing through his PC. Now he can have all the BSODs he can stand, and I just continue surfing/emerging/emailing happily, because the routing is handled by a separate piece of hardware that is not affected by the status of our individual PCs). Is this a recent problem, or has it "always" been like this? Is this a new setup (new equipment, change of ISP/level of membership/type of membership), or has nothing changed recently? HTH, Holly -- gentoo-user@gentoo.org mailing list
[gentoo-user] Shutdown Issues
During the shutdown Gentoo brings down my eth0 connection, but my computer is connected to a router that uses xDSL for connection, so my questions is: Can I remove this, this way I won't have to reconnect my xDSL connection? Or this shouldn't interfer in my connection I I'm having to reconnect for other reasons? Thanks, e. pereira ___ Yahoo! Acesso Grátis - Internet rápida e grátis. Instale o discador agora! http://br.acesso.yahoo.com/ -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] "shutdown -h" on Power-button...
Zac Medico wrote: Jarry wrote: Hi, I want to set up my computer so that it would do automatically "shutdown -h" after short pressing of "power" button. Is the only solution to emerge acpid (found on gentoo-forum)? Would not it be easier with apm? Because I remember once in the past having a comp with some other linux-distro, where I think I did not install acpid, only edited some file in /etc, and yet after pressing the "power" button it correctly shutdowned my computer. I just want to keep number of running daemons low. It is not a notebook, so I think it is not worth to have one more daemon running all the time just because of one possible event-trigger... Jarry AFAIK your choices are acpid and apmd. Either will do the job as log as it can detect power button events. I wouldn't worry about running the daemon because resource usage is probably quite low. Zac Acpid on my system is consuming 592K of memory and has accumulated 0 seconds of CPU time out of the 40-or-so hours that my laptop has been up. So it is definitely quite frugal on resources!! -Richard -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] "shutdown -h" on Power-button...
Jarry wrote: > Hi, > > I want to set up my computer so that it would do automatically > "shutdown -h" after short pressing of "power" button. > > Is the only solution to emerge acpid (found on gentoo-forum)? > Would not it be easier with apm? > > Because I remember once in the past having a comp with some other > linux-distro, where I think I did not install acpid, only edited > some file in /etc, and yet after pressing the "power" button it > correctly shutdowned my computer. > > I just want to keep number of running daemons low. It is not > a notebook, so I think it is not worth to have one more daemon > running all the time just because of one possible event-trigger... > > Jarry AFAIK your choices are acpid and apmd. Either will do the job as log as it can detect power button events. I wouldn't worry about running the daemon because resource usage is probably quite low. Zac -- gentoo-user@gentoo.org mailing list
[gentoo-user] "shutdown -h" on Power-button...
Hi, I want to set up my computer so that it would do automatically "shutdown -h" after short pressing of "power" button. Is the only solution to emerge acpid (found on gentoo-forum)? Would not it be easier with apm? Because I remember once in the past having a comp with some other linux-distro, where I think I did not install acpid, only edited some file in /etc, and yet after pressing the "power" button it correctly shutdowned my computer. I just want to keep number of running daemons low. It is not a notebook, so I think it is not worth to have one more daemon running all the time just because of one possible event-trigger... Jarry -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] shutdown
On 05/22/05 17:09, Jaap van Geffen wrote: On Sun, 22 May 2005 04:01:52 -0400, John Dangler <[EMAIL PROTECTED]> wrote: During shutdown, I get 2 errors - ERROR: problems stopping dependent services. "bootmisc" is still up. ERROR: problems stopping dependent services. "clock" is still up. Further down, I get a message saying "saving random seed", and nothing happens after that. I need to power the box off and back on. Did your computer correctly shutdown? If not,you get something like " (one of your partitions) not cleanly unmounted" when you startup. If your computer doesn't turnoff power is not a very serious problem.It might be the way you compile acpi in your kernel If it really "hangs" on shutdown it might be a big problem. No more messages coming on shutdown can be a minor problem (happened to me, but not on gentoo).but if there are no more messages because the computer hangs it is serious indeed. ERRORS are annoying and should be resolved but are not allways critical. sorry for my cryptic answer.I'm not a guru and if your problem is serious,I can not help you very much,I just wondered if your problem is not a coincidence of minor problems. Ciao In my case, at least, the computer does not hang, just the shutdown does. I can go to another console and use 'shutdown -c' to stop the shutdown and then use 'halt' or 'reboot', which work fine. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] shutdown
On Sun, 22 May 2005 04:01:52 -0400, John Dangler <[EMAIL PROTECTED]> wrote: During shutdown, I get 2 errors - ERROR: problems stopping dependent services. "bootmisc" is still up. ERROR: problems stopping dependent services. "clock" is still up. Further down, I get a message saying "saving random seed", and nothing happens after that. I need to power the box off and back on. Did your computer correctly shutdown? If not,you get something like " (one of your partitions) not cleanly unmounted" when you startup. If your computer doesn't turnoff power is not a very serious problem.It might be the way you compile acpi in your kernel If it really "hangs" on shutdown it might be a big problem. No more messages coming on shutdown can be a minor problem (happened to me, but not on gentoo).but if there are no more messages because the computer hangs it is serious indeed. ERRORS are annoying and should be resolved but are not allways critical. sorry for my cryptic answer.I'm not a guru and if your problem is serious,I can not help you very much,I just wondered if your problem is not a coincidence of minor problems. Ciao -- jaap -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] shutdown
On 05/22/05 04:01, John Dangler wrote: During shutdown, I get 2 errors - ERROR: problems stopping dependent services. "bootmisc" is still up. ERROR: problems stopping dependent services. "clock" is still up. Further down, I get a message saying "saving random seed", and nothing happens after that. I need to power the box off and back on. Are these problems related? Where can I look to resolve these? Thanks (as always) for any input. JD Just to say, I get the same problem with the "saving random seed" thing and then nothing else happening, but I can use the 'halt' and 'reboot' commands fine... -- gentoo-user@gentoo.org mailing list
[gentoo-user] shutdown
During shutdown, I get 2 errors - ERROR: problems stopping dependent services. "bootmisc" is still up. ERROR: problems stopping dependent services. "clock" is still up. Further down, I get a message saying "saving random seed", and nothing happens after that. I need to power the box off and back on. Are these problems related? Where can I look to resolve these? Thanks (as always) for any input. JD -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] shutdown now hangs on "Saving random seed..."
On 4/27/05, Jason Cooper <[EMAIL PROTECTED]> wrote: > Colin ([EMAIL PROTECTED]) scribbled: > > Whenever I type in "shutdown now," the kernel enters runlevel 1 and > > starts to shut down. All of these [ ok ] just fine: > > > > * Stopping local... > > * Stopping fcron... > > * Unmounting network filesystems... > > * Stopping syslog-ng... > > * Syncing hardware clock to system clock [Local Time]... > > * Bringing eth0 down... > > *Removing inet6 addresses... > > *eth0 inet6 del fe80::20e:2eff:fe0c:6041/64... > > *Stopping eth0... > > * Bringing lo down... > > > > But it just hangs on this one: > > > > * Saving random seed... > > > > I can Ctrl-C my way out of it and continue to work in Gentoo, but a > > software shutdown isn't possible. I just reboot, enter the BIOS and > > hold the switch. What can I do about this little bug? And is there > > even any purpose in loading and saving a random seed when random > > numbers are (AFAIK) seeded by the timer? > > Have you enabled apm or acpi in your kernel? ACPI is compiled into the kernel and enabled in the BIOS. I don't have APM on this computer, so it's not compiled in. -- Colin -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] shutdown now hangs on "Saving random seed..."
On 4/27/05, The Disguised Jedi <[EMAIL PROTECTED]> wrote: > > On 4/27/05, Jason Cooper <[EMAIL PROTECTED]> wrote: > > > Colin ([EMAIL PROTECTED] ) scribbled: > > > > Whenever I type in "shutdown now," the kernel enters runlevel 1 and > > > > starts to shut down. All of these [ ok ] just fine: > > > > > > > > * Stopping local... > > > > * Stopping fcron... > > > > * Unmounting network filesystems... > > > > * Stopping syslog-ng... > > > > * Syncing hardware clock to system clock [Local Time]... > > > > * Bringing eth0 down... > > > > *Removing inet6 addresses... > > > > *eth0 inet6 del fe80::20e:2eff:fe0c:6041/64... > > > > *Stopping eth0... > > > > * Bringing lo down... > > > > > > > > But it just hangs on this one: > > > > > > > > * Saving random seed... > > > > > I am wondering if it isn't the random number generator that is causing the > problem. Is ACPI and/or APM configured properly in your kernel? Did you > recently add these? I think the problem is that the kernel is trying to > signal shutdown on the machine, but it isn't configured right. ACPI is compiled in and enabled in the BIOS. I don't have APM, so I don't have support for that. My USE flags include "acpi -apm" > > I can Ctrl-C my way out of it and continue to work in Gentoo, but a > > software shutdown isn't possible. I just reboot, enter the BIOS and > > hold the switch. What can I do about this little bug? And is there > > even any purpose in loading and saving a random seed when random > > numbers are (AFAIK) seeded by the timer? > Check your ACPI and/or APM configuration. The thing that is bugging me here > is that you can get out of it, which makes me think that ACPI is signaling > the power supply to switch off, but it doesn't. Try "reboot" to see if that > works. I had a problem where my machine wouldn't power off, but it would > reboot, and it was just a kernel configuration problem. I doubt that, since when it reboots, there are more steps, ending with unmounting the filesystems and remounting them read-only. The power supply does switch off; I briefly installed WinXP SP2 to test the hardware and make sure everything worked, and there were no problems. -- Colin -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] shutdown now hangs on "Saving random seed..."
The Disguised Jedi ([EMAIL PROTECTED]) scribbled: > > On 4/27/05, Jason Cooper <[EMAIL PROTECTED]> wrote: > > > Colin ([EMAIL PROTECTED]) scribbled: > > > > Whenever I type in "shutdown now," the kernel enters runlevel 1 and > > > > starts to shut down. All of these [ ok ] just fine: > > > > > > > > * Stopping local... > > > > * Stopping fcron... > > > > * Unmounting network filesystems... > > > > * Stopping syslog-ng... > > > > * Syncing hardware clock to system clock [Local Time]... > > > > * Bringing eth0 down... > > > > * Removing inet6 addresses... > > > > * eth0 inet6 del fe80::20e:2eff:fe0c:6041/64... > > > > * Stopping eth0... > > > > * Bringing lo down... > > > > > > > > But it just hangs on this one: > > > > > > > > * Saving random seed... > > > > > I am wondering if it isn't the random number generator that is causing the > problem. Is ACPI and/or APM configured properly in your kernel? Did you > recently add these? I think the problem is that the kernel is trying to > signal shutdown on the machine, but it isn't configured right. > > > I can Ctrl-C my way out of it and continue to work in Gentoo, but a > > software shutdown isn't possible. I just reboot, enter the BIOS and > > hold the switch. What can I do about this little bug? And is there > > even any purpose in loading and saving a random seed when random > > numbers are (AFAIK) seeded by the timer? > Check your ACPI and/or APM configuration. The thing that is bugging me here > is that you can get out of it, which makes me think that ACPI is signaling > the power supply to switch off, but it doesn't. Try "reboot" to see if that > works. I had a problem where my machine wouldn't power off, but it would > reboot, and it was just a kernel configuration problem. > HTH, > > -- > The Disguised Jedi > [EMAIL PROTECTED] Please be more careful with your quoting. What I wrote isn't in there, yet you have attribution to me at the top. Also, your word-wrapping appears to be borked. cooper -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] shutdown now hangs on "Saving random seed..."
> On 4/27/05, Jason Cooper <[EMAIL PROTECTED]> wrote: > > Colin ([EMAIL PROTECTED] ) scribbled:> > > Whenever I type in "shutdown now," the kernel enters runlevel 1 and> > > starts to shut down. All of these [ ok ] just fine:> > >> > > * Stopping local... > > > * Stopping fcron...> > > * Unmounting network filesystems...> > > * Stopping syslog-ng...> > > * Syncing hardware clock to system clock [Local Time]...> > > * Bringing eth0 down... > > > *Removing inet6 addresses...> > > *eth0 inet6 del fe80::20e:2eff:fe0c:6041/64...> > > *Stopping eth0...> > > * Bringing lo down...> > > > > > But it just hangs on this one:> > >> > > * Saving random seed...> > > I am wondering if it isn't the random number generator that is causing the problem. Is ACPI and/or APM configured properly in your kernel? Did you recently add these? I think the problem is that the kernel is trying to signal shutdown on the machine, but it isn't configured right. > I can Ctrl-C my way out of it and continue to work in Gentoo, but a> software shutdown isn't possible. I just reboot, enter the BIOS and> hold the switch. What can I do about this little bug? And is there > even any purpose in loading and saving a random seed when random> numbers are (AFAIK) seeded by the timer?Check your ACPI and/or APM configuration. The thing that is bugging me here is that you can get out of it, which makes me think that ACPI is signaling the power supply to switch off, but it doesn't. Try "reboot" to see if that works. I had a problem where my machine wouldn't power off, but it would reboot, and it was just a kernel configuration problem. HTH, -- The Disguised Jedi[EMAIL PROTECTED]Now you have my $0.02. Or .01 Pounds, .014 Euros, or $0.025 CAN. I'm world-wide BABY! PHP rocks!"Knowledge is Power. Power Corrupts. Go to school, become evil"Disclaimer: Any disclaimer attached to this message may be ignored. However, I must say that the ENTIRE contents of this message are subject to other's criticism, corrections, and speculations. This message is Certified Virus Free
Re: [gentoo-user] shutdown now hangs on "Saving random seed..."
Colin ([EMAIL PROTECTED]) scribbled: > Whenever I type in "shutdown now," the kernel enters runlevel 1 and > starts to shut down. All of these [ ok ] just fine: > > * Stopping local... > * Stopping fcron... > * Unmounting network filesystems... > * Stopping syslog-ng... > * Syncing hardware clock to system clock [Local Time]... > * Bringing eth0 down... > *Removing inet6 addresses... > *eth0 inet6 del fe80::20e:2eff:fe0c:6041/64... > *Stopping eth0... > * Bringing lo down... > > But it just hangs on this one: > > * Saving random seed... > > I can Ctrl-C my way out of it and continue to work in Gentoo, but a > software shutdown isn't possible. I just reboot, enter the BIOS and > hold the switch. What can I do about this little bug? And is there > even any purpose in loading and saving a random seed when random > numbers are (AFAIK) seeded by the timer? Have you enabled apm or acpi in your kernel? Cooper. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] shutdown now hangs on "Saving random seed..."
On Wed, Apr 27, 2005 at 01:22:25AM -0400, Colin wrote: > But it just hangs on this one: > > * Saving random seed... > > I can Ctrl-C my way out of it and continue to work in Gentoo, but a > software shutdown isn't possible. I just reboot, enter the BIOS and > hold the switch. What can I do about this little bug? And is there > even any purpose in loading and saving a random seed when random > numbers are (AFAIK) seeded by the timer? man urandom: The random number generator gathers environmental noise from device drivers and other sources into an entropy pool. The generator also keeps an estimate of the number of bits of noise in the entropy pool. From this entropy pool random numbers are created. ... When a Linux system starts up without much operator interaction, the entropy pool may be in a fairly predictable state. This reduces the actual amount of noise in the entropy pool below the estimate. In order to counteract this effect, it helps to carry entropy pool infor- mation across shut-downs and start-ups. I guess you can remove urandom from boot runlevel # rc-update del urandom or, you can try to troubleshoot the problem (= The shutdown section of /etc/init.d/urandom is pretty much one line on my system: dd if=/dev/urandom of=/var/run/random-seed count=1 &> /dev/null You can try seeing what's wrong with that... W -- * Address: 45 Spelman Hall, Princeton University 08544 * * Phone: x68958 AIM: AngularJerk* *E-mail: [EMAIL PROTECTED]From: sep.dynalias.net * "He expanded his chest to make it totally clear that here was the sort of man you only dared to cross if you had a team of Sherpas with you. " Sortir en Pantoufles: up 15 days, 15:45 -- gentoo-user@gentoo.org mailing list
[gentoo-user] shutdown now hangs on "Saving random seed..."
Whenever I type in "shutdown now," the kernel enters runlevel 1 and starts to shut down. All of these [ ok ] just fine: * Stopping local... * Stopping fcron... * Unmounting network filesystems... * Stopping syslog-ng... * Syncing hardware clock to system clock [Local Time]... * Bringing eth0 down... *Removing inet6 addresses... *eth0 inet6 del fe80::20e:2eff:fe0c:6041/64... *Stopping eth0... * Bringing lo down... But it just hangs on this one: * Saving random seed... I can Ctrl-C my way out of it and continue to work in Gentoo, but a software shutdown isn't possible. I just reboot, enter the BIOS and hold the switch. What can I do about this little bug? And is there even any purpose in loading and saving a random seed when random numbers are (AFAIK) seeded by the timer? -- Colin -- gentoo-user@gentoo.org mailing list
