Re: Wheezy, XFCE: system shutdown
Hi. I have a configuration problem with Wheezy and XFCE and didn't find the appropriate docu: The Log-Out-Dialog (from the upper panel) offers Log Out, Restart and Shut Down icons. But only Log Out is usable, the other two are disabled. How can I enable the Shutdown button? Log out and login as root again only for shutdown - hmm, it works, but ... Did you check your group settings? Do you have pm-utils and xfce4-power-manager installed? xfce4-power-mangager was missing, but installing it did not solve the problem. group settings: there is no group named *power* or similar. What would be the rigth group configuration? Thanks, Hartwig -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201211191945.55393.hartwig.atr...@arcor.de
Re: Wheezy, XFCE: system shutdown
* On 2012 19 Nov 12:46 -0600, Hartwig Atrops wrote: xfce4-power-mangager was missing, but installing it did not solve the problem. group settings: there is no group named *power* or similar. What would be the rigth group configuration? My user is in the powerdev group. I get even the Suspend and Hibernate buttons on this desktop machine even though I don't use them. $ cat /etc/group | grep power powerdev:x:115:username - Nate -- The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true. Ham radio, Linux, bikes, and more: http://www.n0nb.us -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121119185152.gh6...@n0nb.us
Re: Wheezy, XFCE: system shutdown
--- On Mon, 11/19/12, Nate Bargmann n...@n0nb.us wrote: From: Nate Bargmann n...@n0nb.us Subject: Re: Wheezy, XFCE: system shutdown To: debian-user@lists.debian.org Date: Monday, November 19, 2012, 12:51 PM * On 2012 19 Nov 12:46 -0600, Hartwig Atrops wrote: xfce4-power-mangager was missing, but installing it did not solve the problem. group settings: there is no group named *power* or similar. What would be the rigth group configuration? My user is in the powerdev group. I get even the Suspend and Hibernate buttons on this desktop machine even though I don't use them. $ cat /etc/group | grep power powerdev:x:115:username I'm on gnome squeeze right now, am NOT in the powerdev group and still have working hibernate suspend. Will check xfce wheezy groups in a bit. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1353351915.35853.yahoomailclas...@web163406.mail.gq1.yahoo.com
Re: Wheezy, XFCE: system shutdown
On Monday 19 November 2012 20:05:15 Go Linux wrote: --- On Mon, 11/19/12, Nate Bargmann n...@n0nb.us wrote: From: Nate Bargmann n...@n0nb.us Subject: Re: Wheezy, XFCE: system shutdown To: debian-user@lists.debian.org Date: Monday, November 19, 2012, 12:51 PM * On 2012 19 Nov 12:46 -0600, Hartwig Atrops wrote: xfce4-power-mangager was missing, but installing it did not solve the problem. group settings: there is no group named *power* or similar. What would be the rigth group configuration? My user is in the powerdev group. I get even the Suspend and Hibernate buttons on this desktop machine even though I don't use them. $ cat /etc/group | grep power powerdev:x:115:username I'm on gnome squeeze right now, am NOT in the powerdev group and still have working hibernate suspend. Will check xfce wheezy groups in a bit. Hmm... I have a Squeeze / XFCE installation running on a Sun Blade 100 (Debian Sparc), the buttons are all there and are usable. Groups: root@PEKING:~# grep power /etc/group powerdev:x:110: i.e. group exists, but no users in it Shutdown works anyway. Regards, Hartwig -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201211192203.31593.hartwig.atr...@arcor.de
Re: Wheezy, XFCE: system shutdown
--- On Mon, 11/19/12, Hartwig Atrops hartwig.atr...@arcor.de wrote: From: Hartwig Atrops hartwig.atr...@arcor.de Subject: Re: Wheezy, XFCE: system shutdown To: debian-user@lists.debian.org Date: Monday, November 19, 2012, 3:03 PM On Monday 19 November 2012 20:05:15 Go Linux wrote: --- On Mon, 11/19/12, Nate Bargmann n...@n0nb.us wrote: From: Nate Bargmann n...@n0nb.us Subject: Re: Wheezy, XFCE: system shutdown To: debian-user@lists.debian.org Date: Monday, November 19, 2012, 12:51 PM * On 2012 19 Nov 12:46 -0600, Hartwig Atrops wrote: xfce4-power-mangager was missing, but installing it did not solve the problem. group settings: there is no group named *power* or similar. What would be the rigth group configuration? My user is in the powerdev group. I get even the Suspend and Hibernate buttons on this desktop machine even though I don't use them. $ cat /etc/group | grep power powerdev:x:115:username I'm on gnome squeeze right now, am NOT in the powerdev group and still have working hibernate suspend. Will check xfce wheezy groups in a bit. Hmm... I have a Squeeze / XFCE installation running on a Sun Blade 100 (Debian Sparc), the buttons are all there and are usable. Groups: root@PEKING:~# grep power /etc/group powerdev:x:110: i.e. group exists, but no users in it Shutdown works anyway. Regards, Hartwig OK. Now on refracta wheezy xfce. There isn't even a powerdev group listed and all five shutdown options are present and functioning. In addition to pm-utils and xfce4-power-manager, I have upower and libupower-glib1 installed. You might also look at acpi-support. Though it's not installed here, your hardware might need it. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1353365533.46636.yahoomailclas...@web163406.mail.gq1.yahoo.com
Shutdown Problem
Debian 6.0.6 (64 bit)/KDE 4.4.5 For some reason when I shutdown the system, either as a user or as root, the process hangs on: Currently running process (pstree): The only recourse I seem to have is to hit the reset button. Reinstalling psmisc did not solve the problem. Assistance in solving this problem will be appreciated. Thanks in advance. -- Stephen P. Molnar, Ph.D. Life is a fuzzy set Foundation for Chemistry Stochastic and multivariate www.FoundationForChemistry.com (614)312-7528 (c) Skype: smolnar1 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5072e2b9.6000...@sbcglobal.net
Re: Shutdown Problem
On Mon 08 Oct 2012 at 10:27:05 -0400, Stephen P. Molnar wrote: Debian 6.0.6 (64 bit)/KDE 4.4.5 For some reason when I shutdown the system, either as a user or as root, the process hangs on: Currently running process (pstree): The only recourse I seem to have is to hit the reset button. Reinstalling psmisc did not solve the problem. Everything you see on the screen when the hang occurs can only be of help. pstree itself is probably not the problem. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121008204020.GG30872@desktop
Re: No shutdown after processor change
On Thu, Sep 27, 2012 at 5:44 AM, Stan Hoeppner s...@hardwarefreak.com wrote: On 9/26/2012 11:14 AM, Artifex Maximus wrote: On Sun, Sep 23, 2012 at 9:55 AM, Selim T. Erdogan se...@alumni.cs.utexas.edu wrote: Artifex Maximus, 18.09.2012: Did you make any software updates to the system? I have a pretty old computer that is using wheezy and as I updated debian within the past weeks it went back and forth between turning off properly and stalling with system halted on the screen. I don't remember which one it's been doing most recently. No I did not upgrade my system that time. Since then I do several times but with the same result. The problem probably somewhere else because if I am in the BIOS and press power button the system (CPU) stops/freeze but the screen remains on and have to switch off with power button on PSU. Later the system does not always detect the HDDs at system start which is scaring. So I bought a new ASUS G41 board and a new PSU. Hope that works. Actually I do not have time for build the new system so there will be no new info till Friday. Might I first will try to change only the CPU back to E5200 and see the errors gone or still there. If gone the problem is clearly CPU related. Sorry for being late for the game. In nearly all cases this behavior is a result of a new processor and an old BIOS whose code was not written for the new processor. Simply flashing the system with the latest BIOS usually fixes such issues. I don't see that mentioned above. Before installing the new Asus board, I suggest putting the E5200 back in. Confirm everything works as it did before relating to power switch, device detection, etc. If it works, flash with the latest BIOS. Reboot and verify new BIOS is working. If so, power down and install the E8400. The problems should be gone. Thanks for your answer. I already installed my new board and everything is fine. I tried E5200 and old motherboard lives again. So my old board clearly not handle E8400. So bad. My new motherboard handle E8400 and knows VT which is great. I might be able to give you definitive information but you didn't state your current mobo make/model. This problem is likely documented in the errata, along with the solution, which is likely upgrade to BIOS version x.xx.xxx or later. It's a Fujitsu-Siemens G31T-M2 manufactured by ECS but no such board on ECS site. I flashed the last BIOS some years ago as BIOS is from 2008 and no success. Fujitsu support wrote an email that Linux and E8400 is not supported by them. Bye, a -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/capkuxveas+ouim5bttftke1kev7rkvzu2qk1ouz49nln_v0...@mail.gmail.com
Re: No shutdown after processor change
On Sun, Sep 23, 2012 at 9:55 AM, Selim T. Erdogan se...@alumni.cs.utexas.edu wrote: Artifex Maximus, 18.09.2012: On Mon, Sep 17, 2012 at 8:29 PM, lee l...@yun.yagibdah.de wrote: Artifex Maximus artife...@gmail.com writes: I've changed my processor from E5200 to E8400. Since then my computer does not shutdown. It's possible that you damaged your board in the process. Thanks for your answer. I did it several times and otherwise works perfectly so I do not think so. Sometimes the display and motherboard LEDs become blank but PSU cooler runs. It's a feature of some PSUs to leave the fan running until they have cooled down some after turning off the computer. Never ever did before. I think this is not the case here. Sometimes Debian stops at System halted line and no blank screen and machine keeps running. At that point, your system is shut down and the only thing it doesn't do is turning itself off. That can be a software issue --- I never figured out what kernel modules are needed for that. I think that only CPU change cannot made such problem. I tried BIOS default setup loading but no change. Any idea what to change? I have no idea. You could start by looking at what's in syslog and dmesg and by checking the loaded modules. You could boot from a live/installer DVD/CD and see if the computer turns off when you shut it down to get an indication if there is a software or a hardware problem. I don't know if the DVDs/CDs actually turn the computer off, though, something to find out first. Thank you. I'll take a look on it. Did you make any software updates to the system? I have a pretty old computer that is using wheezy and as I updated debian within the past weeks it went back and forth between turning off properly and stalling with system halted on the screen. I don't remember which one it's been doing most recently. No I did not upgrade my system that time. Since then I do several times but with the same result. The problem probably somewhere else because if I am in the BIOS and press power button the system (CPU) stops/freeze but the screen remains on and have to switch off with power button on PSU. Later the system does not always detect the HDDs at system start which is scaring. So I bought a new ASUS G41 board and a new PSU. Hope that works. Actually I do not have time for build the new system so there will be no new info till Friday. Might I first will try to change only the CPU back to E5200 and see the errors gone or still there. If gone the problem is clearly CPU related. Bye, a -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAPkuXvE2b3j80b=2dszaf0mgvndolaz6wofi8pnxz+lbey0...@mail.gmail.com
Re: No shutdown after processor change
On 9/26/2012 11:14 AM, Artifex Maximus wrote: On Sun, Sep 23, 2012 at 9:55 AM, Selim T. Erdogan se...@alumni.cs.utexas.edu wrote: Artifex Maximus, 18.09.2012: On Mon, Sep 17, 2012 at 8:29 PM, lee l...@yun.yagibdah.de wrote: Artifex Maximus artife...@gmail.com writes: I've changed my processor from E5200 to E8400. Since then my computer does not shutdown. It's possible that you damaged your board in the process. Thanks for your answer. I did it several times and otherwise works perfectly so I do not think so. Sometimes the display and motherboard LEDs become blank but PSU cooler runs. It's a feature of some PSUs to leave the fan running until they have cooled down some after turning off the computer. Never ever did before. I think this is not the case here. Sometimes Debian stops at System halted line and no blank screen and machine keeps running. At that point, your system is shut down and the only thing it doesn't do is turning itself off. That can be a software issue --- I never figured out what kernel modules are needed for that. I think that only CPU change cannot made such problem. I tried BIOS default setup loading but no change. Any idea what to change? I have no idea. You could start by looking at what's in syslog and dmesg and by checking the loaded modules. You could boot from a live/installer DVD/CD and see if the computer turns off when you shut it down to get an indication if there is a software or a hardware problem. I don't know if the DVDs/CDs actually turn the computer off, though, something to find out first. Thank you. I'll take a look on it. Did you make any software updates to the system? I have a pretty old computer that is using wheezy and as I updated debian within the past weeks it went back and forth between turning off properly and stalling with system halted on the screen. I don't remember which one it's been doing most recently. No I did not upgrade my system that time. Since then I do several times but with the same result. The problem probably somewhere else because if I am in the BIOS and press power button the system (CPU) stops/freeze but the screen remains on and have to switch off with power button on PSU. Later the system does not always detect the HDDs at system start which is scaring. So I bought a new ASUS G41 board and a new PSU. Hope that works. Actually I do not have time for build the new system so there will be no new info till Friday. Might I first will try to change only the CPU back to E5200 and see the errors gone or still there. If gone the problem is clearly CPU related. Sorry for being late for the game. In nearly all cases this behavior is a result of a new processor and an old BIOS whose code was not written for the new processor. Simply flashing the system with the latest BIOS usually fixes such issues. I don't see that mentioned above. Before installing the new Asus board, I suggest putting the E5200 back in. Confirm everything works as it did before relating to power switch, device detection, etc. If it works, flash with the latest BIOS. Reboot and verify new BIOS is working. If so, power down and install the E8400. The problems should be gone. I might be able to give you definitive information but you didn't state your current mobo make/model. This problem is likely documented in the errata, along with the solution, which is likely upgrade to BIOS version x.xx.xxx or later. -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5063cb9c.3050...@hardwarefreak.com
Re: pppd shutdown
Have you found the problem yet? On Thu, Sep 20, 2012 at 01:21:33PM -0700, Mike McClain wrote: Howdy, I'm on dialup using pppd and loosing the connection often in the middle of fetching mail or loading some URL in the browser. I'm hoping for suggestions to help me debug the problem. Hopefully, you have an external modem. That way you can make sure the CD (carrier detect) is on. If the CD is off or flickers, you have a problem between your modem and the modem at the other end. -- If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing. --- Malcolm X -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120925123325.GK8247@tal
Re: No shutdown after processor change
Artifex Maximus, 18.09.2012: On Mon, Sep 17, 2012 at 8:29 PM, lee l...@yun.yagibdah.de wrote: Artifex Maximus artife...@gmail.com writes: I've changed my processor from E5200 to E8400. Since then my computer does not shutdown. It's possible that you damaged your board in the process. Thanks for your answer. I did it several times and otherwise works perfectly so I do not think so. Sometimes the display and motherboard LEDs become blank but PSU cooler runs. It's a feature of some PSUs to leave the fan running until they have cooled down some after turning off the computer. Never ever did before. I think this is not the case here. Sometimes Debian stops at System halted line and no blank screen and machine keeps running. At that point, your system is shut down and the only thing it doesn't do is turning itself off. That can be a software issue --- I never figured out what kernel modules are needed for that. I think that only CPU change cannot made such problem. I tried BIOS default setup loading but no change. Any idea what to change? I have no idea. You could start by looking at what's in syslog and dmesg and by checking the loaded modules. You could boot from a live/installer DVD/CD and see if the computer turns off when you shut it down to get an indication if there is a software or a hardware problem. I don't know if the DVDs/CDs actually turn the computer off, though, something to find out first. Thank you. I'll take a look on it. Did you make any software updates to the system? I have a pretty old computer that is using wheezy and as I updated debian within the past weeks it went back and forth between turning off properly and stalling with system halted on the screen. I don't remember which one it's been doing most recently. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120923075541.ga8...@cs.utexas.edu
Re: pppd shutdown
On Fri, 21 Sep 2012 12:40:20 -0700, Mike McClain wrote: On Fri, Sep 21, 2012 at 02:53:52PM +, Camale?n wrote: snip You can try by adding/enabling crtscts and also the modem options at the config file. depending on the hardware you're using, these were to alleviate the kind of errors you get although OTOH, dialup links are very unreliable, it's quite usual to get random disconnects. snip I think the first to do would be enabling verbose/debug logging for pppd. Since my first post showed that crtscts, modem and debug are included Ooops, you're right, I overlooked it. Try the opposite (#commenting out), as these are hardware related features maybe your modem does not fully or properly support them. in /etc/ppp/options I assume you are saying they should be somewhere else as well but you forgot to say where. No, they should be where they are, it was my head that wasn't in the right place :-). As per the debug flag, it's quite rare because the verbosity of messages is very scarce, did you send the complete logs? Also, you can do a Google search to find out more ideas on how to overcome the problem: http://bit.ly/PwxvEx Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/k3k80u$mv$5...@ger.gmane.org
Re: pppd shutdown
On Thu, 20 Sep 2012 13:21:33 -0700, Mike McClain wrote: I'm on dialup using pppd and loosing the connection often in the middle of fetching mail or loading some URL in the browser. I'm hoping for suggestions to help me debug the problem. (...) My logs show this when I close the connection with 'poff': (...) Sep 16 08:56:01 playground pppd[13474]: sent [LCP TermReq id=0x2 User request] That looks like a manual hang off. Often I see this: (...) Sep 16 14:12:52 playground pppd[1762]: sent [LCP TermReq id=0x2 Peer not responding] (...) You can try by adding/enabling crtscts and also the modem options at the config file. depending on the hardware you're using, these were to alleviate the kind of errors you get although OTOH, dialup links are very unreliable, it's quite usual to get random disconnects. I can see that sometimes my ISP seems to go to sleep but other times it appears to be some other problem and I just don't know how to gather the data to make an informed diagnosis. Any suggestions on how to track pppd's shutdown with greater resolution will be appreciated. I think the first to do would be enabling verbose/debug logging for pppd. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/k3hv20$oni$4...@ger.gmane.org
Re: pppd shutdown
On Fri, Sep 21, 2012 at 02:53:52PM +, Camale?n wrote: snip You can try by adding/enabling crtscts and also the modem options at the config file. depending on the hardware you're using, these were to alleviate the kind of errors you get although OTOH, dialup links are very unreliable, it's quite usual to get random disconnects. snip I think the first to do would be enabling verbose/debug logging for pppd. Since my first post showed that crtscts, modem and debug are included in /etc/ppp/options I assume you are saying they should be somewhere else as well but you forgot to say where. Thanks, Mike -- Though I do use Linux, I don't appreciate being called a Linutic. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120921194020.GA10358@playground
pppd shutdown
Howdy, I'm on dialup using pppd and loosing the connection often in the middle of fetching mail or loading some URL in the browser. I'm hoping for suggestions to help me debug the problem. root@/deb60:~ grep -v '^\s*$\|^#' /etc/ppp/options asyncmap 0 auth crtscts lock hide-password modem debug lcp-echo-interval 30 lcp-echo-failure 4 noipx My logs show this when I close the connection with 'poff': Sep 16 08:56:01 playground pppd[13474]: Script /etc/ppp/ip-down started (pid 13504) Sep 16 08:56:01 playground pppd[13474]: sent [LCP TermReq id=0x2 User request] Sep 16 08:56:01 playground pppd[13474]: Script /etc/ppp/ip-down finished (pid 13504), status = 0x0 Sep 16 08:56:01 playground pppd[13474]: rcvd [LCP TermAck id=0x2] Often I see this: Sep 16 14:07:23 playground pppd[1762]: Script /etc/ppp/ip-up started (pid 1773) Sep 16 14:07:23 playground pppd[1762]: Script /etc/ppp/ip-up finished (pid 1773), status = 0x0 Sep 16 14:12:52 playground pppd[1762]: Script /etc/ppp/ip-down started (pid 1955) Sep 16 14:12:52 playground pppd[1762]: sent [LCP TermReq id=0x2 Peer not responding] Sep 16 14:12:53 playground pppd[1762]: Script /etc/ppp/ip-down finished (pid 1955), status = 0x0 I also see this: Sep 20 07:21:36 playground pppd[24179]: Script /etc/ppp/ip-up started (pid 24185) Sep 20 07:21:36 playground pppd[24179]: Script /etc/ppp/ip-up finished (pid 24185), status = 0x0 Sep 20 07:23:56 playground pppd[24179]: Script /etc/ppp/ip-down started (pid 24208) Sep 20 07:23:58 playground pppd[24179]: Script /etc/ppp/ip-down finished (pid 24208), status = 0x0 Here I should think there would be a longer wait if there were a timeout for lack of response. Sep 20 09:22:55 playground pppd[24397]: sent [LCP EchoReq id=0x3 magic=0xfc0294d0] Sep 20 09:22:55 playground pppd[24397]: rcvd [LCP EchoRep id=0x3 magic=0x0] Sep 20 09:23:25 playground pppd[24397]: sent [LCP EchoReq id=0x4 magic=0xfc0294d0] Sep 20 09:23:50 playground pppd[24397]: Script /etc/ppp/ip-down started (pid 24416) Sep 20 09:23:52 playground pppd[24397]: Script /etc/ppp/ip-down finished (pid 24416), status = 0x0 Again I expect ip-down came before the timeout: Sep 20 09:22:55 playground pppd[24397]: rcvd [LCP EchoRep id=0x3 magic=0x0] Sep 20 09:23:25 playground pppd[24397]: sent [LCP EchoReq id=0x4 magic=0xfc0294d0] Sep 20 09:23:50 playground pppd[24397]: Script /etc/ppp/ip-down started (pid 24416) Sep 20 09:23:52 playground pppd[24397]: Script /etc/ppp/ip-down finished (pid 24416), status = 0x0 I can see that sometimes my ISP seems to go to sleep but other times it appears to be some other problem and I just don't know how to gather the data to make an informed diagnosis. Any suggestions on how to track pppd's shutdown with greater resolution will be appreciated. Thanks; Mike -- Satisfied user of Linux since 1997. O ascii ribbon campaign - stop html mail - www.asciiribbon.org -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120920202133.GA24662@playground
Re: No shutdown after processor change
On Tue, 18 Sep 2012 20:30:04 +0200, Artifex Maximus wrote: On Mon, Sep 17, 2012 at 4:36 PM, Camaleón noela...@gmail.com wrote: I would look for a BIOS update, just in case. Whether in doubt, ask your motherboard's manufacturer about this step. Thanks. Motherboard has the latest BIOS from 2008 and wrote for support to manufacturer (Fujitsu-Siemens). The answer is what I expect: we are sorry, but probably problem is because of the OS and changed CPU. None of them are supported. Supported OS is: Windows Vista and supported CPUs are: 38006431 CPU INTEL PDC E2140 / 775 38006431 CPU INTEL PDC E2140 / 775 38009419 CPU INTEL PDC E2160 775 45W Wow... how bad. Is not only that the manufacturer does not provide a new BIOS update, but neither provides support for Linux (expected) nor for the model of microprocessor you have bought. Nice. So no help from manufacturer as I am using not supported CPU and systems. Typical problem of brand name and its support. The poblem here is that these motherboards are too much customized for the computer manufacturer and can implement settings and instructions which are not available when sold as stand-alone (separate) items. I still have no idea why system cannot shutdown with different CPU. It does not have to be related but in your case it quite evident there's a straight cause-effect relation. Given that shutting down problems are usually close related to ACPI and ACPI is handled in first place by the BIOS revisions, an upgrade could have helped to solve the problem but if there are no new firmwares available you can try to load an updated kernel. What Debian flavour are you running? Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/k3cmo6$s2t$8...@ger.gmane.org
Re: No shutdown after processor change
On Mon, Sep 17, 2012 at 4:36 PM, Camaleón noela...@gmail.com wrote: On Mon, 17 Sep 2012 11:48:53 +0200, Artifex Maximus wrote: I've changed my processor from E5200 to E8400. Since then my computer does not shutdown. Sometimes the display and motherboard LEDs become blank but PSU cooler runs. Sometimes Debian stops at System halted line and no blank screen and machine keeps running. I think that only CPU change cannot made such problem. I tried BIOS default setup loading but no change. Any idea what to change? I have no idea. I would look for a BIOS update, just in case. Whether in doubt, ask your motherboard's manufacturer about this step. Thanks. Motherboard has the latest BIOS from 2008 and wrote for support to manufacturer (Fujitsu-Siemens). The answer is what I expect: we are sorry, but probably problem is because of the OS and changed CPU. None of them are supported. Supported OS is: Windows Vista and supported CPUs are: 38006431 CPU INTEL PDC E2140 / 775 38006431 CPU INTEL PDC E2140 / 775 38009419 CPU INTEL PDC E2160 775 45W Nice. So no help from manufacturer as I am using not supported CPU and systems. Typical problem of brand name and its support. I still have no idea why system cannot shutdown with different CPU. Bye, a -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/capkuxvhr_+zqvn7ahpjcmqntol36rflyzbxygksu0kiqpku...@mail.gmail.com
Re: No shutdown after processor change
On Mon, Sep 17, 2012 at 8:29 PM, lee l...@yun.yagibdah.de wrote: Artifex Maximus artife...@gmail.com writes: I've changed my processor from E5200 to E8400. Since then my computer does not shutdown. It's possible that you damaged your board in the process. Thanks for your answer. I did it several times and otherwise works perfectly so I do not think so. Sometimes the display and motherboard LEDs become blank but PSU cooler runs. It's a feature of some PSUs to leave the fan running until they have cooled down some after turning off the computer. Never ever did before. I think this is not the case here. Sometimes Debian stops at System halted line and no blank screen and machine keeps running. At that point, your system is shut down and the only thing it doesn't do is turning itself off. That can be a software issue --- I never figured out what kernel modules are needed for that. I think that only CPU change cannot made such problem. I tried BIOS default setup loading but no change. Any idea what to change? I have no idea. You could start by looking at what's in syslog and dmesg and by checking the loaded modules. You could boot from a live/installer DVD/CD and see if the computer turns off when you shut it down to get an indication if there is a software or a hardware problem. I don't know if the DVDs/CDs actually turn the computer off, though, something to find out first. Thank you. I'll take a look on it. Bye, a -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/capkuxvgnmuxvweexad33ycc0hmkbwxchsmqzuwtmdlgo2fe...@mail.gmail.com
No shutdown after processor change
Hello! I've changed my processor from E5200 to E8400. Since then my computer does not shutdown. Sometimes the display and motherboard LEDs become blank but PSU cooler runs. Sometimes Debian stops at System halted line and no blank screen and machine keeps running. I think that only CPU change cannot made such problem. I tried BIOS default setup loading but no change. Any idea what to change? I have no idea. Bye, a -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAPkuXvFQRuBgMmv7rpg2j+Kbz29jMN77R_+PmmTxnqAjmJ=a...@mail.gmail.com
Re: No shutdown after processor change
On Mon, 17 Sep 2012 11:48:53 +0200, Artifex Maximus wrote: I've changed my processor from E5200 to E8400. Since then my computer does not shutdown. Sometimes the display and motherboard LEDs become blank but PSU cooler runs. Sometimes Debian stops at System halted line and no blank screen and machine keeps running. I think that only CPU change cannot made such problem. I tried BIOS default setup loading but no change. Any idea what to change? I have no idea. I would look for a BIOS update, just in case. Whether in doubt, ask your motherboard's manufacturer about this step. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/k37cgh$cqa$7...@ger.gmane.org
Re: No shutdown after processor change
Artifex Maximus artife...@gmail.com writes: I've changed my processor from E5200 to E8400. Since then my computer does not shutdown. It's possible that you damaged your board in the process. Sometimes the display and motherboard LEDs become blank but PSU cooler runs. It's a feature of some PSUs to leave the fan running until they have cooled down some after turning off the computer. Sometimes Debian stops at System halted line and no blank screen and machine keeps running. At that point, your system is shut down and the only thing it doesn't do is turning itself off. That can be a software issue --- I never figured out what kernel modules are needed for that. I think that only CPU change cannot made such problem. I tried BIOS default setup loading but no change. Any idea what to change? I have no idea. You could start by looking at what's in syslog and dmesg and by checking the loaded modules. You could boot from a live/installer DVD/CD and see if the computer turns off when you shut it down to get an indication if there is a software or a hardware problem. I don't know if the DVDs/CDs actually turn the computer off, though, something to find out first. -- Debian testing amd64 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87txuwzeo0@yun.yagibdah.de
Annoying Shutdown Beep
Please help anyone to disable the silly shutdown beep ! Tried several options, didn't help. Also disabling the speaker via the BIOS is not an option for me. - Andrejs -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/74d93671-9372-4b19-b02f-80166502f...@gmail.com
Re: Annoying Shutdown Beep
Andrejs Igumenovs wrote at 2012-07-17 14:03 -0500: Please help anyone to disable the silly shutdown beep ! You could try creating file /etc/modprobe.d/local.conf with contents: blacklist pcspkr signature.asc Description: Digital signature
Re: Annoying Shutdown Beep
I know it's possible because all my system sounds are disabled but I can't for the life of me remember how I did it. Probably Googled till I found the solution. Here I think this is where to do it on Gnome. At least it's a start: /etc/gdm3/greeter.gconf-defaults # Play system beeps - especially the one when the greeter is ready /desktop/gnome/sound/event_sounds false --- On Tue, 7/17/12, green greenfreedo...@gmail.com wrote: From: green greenfreedo...@gmail.com Subject: Re: Annoying Shutdown Beep To: debian-user@lists.debian.org Date: Tuesday, July 17, 2012, 2:31 PM Andrejs Igumenovs wrote at 2012-07-17 14:03 -0500: Please help anyone to disable the silly shutdown beep ! You could try creating file /etc/modprobe.d/local.conf with contents: blacklist pcspkr -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1342558882.55031.yahoomailclas...@web163402.mail.gq1.yahoo.com
Re: Shutdown and suspend not working on laptop
On 16 July 2012 01:34, DJ Amireh cactus...@gmail.com wrote: I am having trouble with power management on my laptop. I cannot get suspend or shutdown to work, attempting either causes my laptop to have a black screen and not respond to any input and I am forced to manually shutdown by holding the power button. I am running Debian Squeeze with KDE. Shutting down I attempt through KDE's menu and through running shutdown. Suspending I attempt by shutting my laptop lid on battery which causes it to Suspend to RAM. My laptop is a Compaq Presario CQ61. I would appreciate any help. Thanks I run Wheezy on an Acer Aspire One where wake-up from suspend does not work, it just crashes horribly (kernel panic?). Same with Debian Stable and several other Linux distributions I've tried on that particular notebook. /Helgi Örn -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cakulek7bxlp5rxjnpkjv0gu5mawkhuy+-ndc0c+ck2mdc0s...@mail.gmail.com
Shutdown and suspend not working on laptop
I am having trouble with power management on my laptop. I cannot get suspend or shutdown to work, attempting either causes my laptop to have a black screen and not respond to any input and I am forced to manually shutdown by holding the power button. I am running Debian Squeeze with KDE. Shutting down I attempt through KDE's menu and through running shutdown. Suspending I attempt by shutting my laptop lid on battery which causes it to Suspend to RAM. My laptop is a Compaq Presario CQ61. I would appreciate any help. Thanks
Shutdown Filesystem Problems?
As of late, on my Debian Sid box, every bootup shows recovering journal on all my ext3 filesystems. There ia often a bunch of orphaned inodes on the /usr! It is as if I hit the switch instead of an orderly halt shutdown. System otherwise is OK. Bug? Which package? Workaround (tried sync in my rc.local equivalent for stop). -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201206141042.06898.d_ba...@012.net.il
[Solved ?] Re: fsck forced when using /sbin/shutdown
On Mon, 2012-04-23 at 20:43 +, Camaleón wrote: [...] Mmm... what worries me is why an fsck is even needed just because a non- vital application is not being closed gracefully on shutdown, that's not something I would consider worth for a fsck :-? Steven, have you considered a hardware related problem? Just in case, running smartctl over the disk that holds the partition won't hurt. I checked the drive with gsmartcontrol, no errors found. The problem hasn't occurred with normal use for the past 2 days, so I assume an update fixed it. Kind regards, Steven signature.asc Description: This is a digitally signed message part
Re: fsck forced when using /sbin/shutdown
On Fri, 2012-04-20 at 15:09 +, Camaleón wrote: [...] /dev/sdc1 is the partition with data inconsistency, what we have to find out is why it's left in such state. Another possibility, should you have the chance, could be backup the full partition, reformat it and start over. Being just your /home this won't present any difficulty. Apart from the fact that I need someway to backup the data :) While not crucial data, I'd rather keep it. It's just a bit too big to add to my current backup system. I wonder what difference can be in shutting down from GNOME and doing it from the command line, mmm... :-? Is is perhaps possible that Gnome is writing out some config files in my home directory during shutdown and the system cuts power prematurely? I also noticed a message saying the device from / is busy during the shutdown sequence, but never /home, while the root filesystem doesn't need the check. (...) Yes, that was indeed the aim of my dumb suggestion :-) Well, any suggestion is welcome. I did some tests and it doesn't look like it's Gnome itself, at least not right after booting. First test: 1) boot 2) log in using a tty instead of gdm (Ctrl + Alt + F1) 3) issue the sudo /sbin/shutdown -h +1 command result: no fsck needed Second test: 1) boot 2) log in using gdm3 and starting a regular Gnome session 3) switch to tty1, login there 4) issue the sudo /sbin/shutdown -h +1 command result: no fsck needed Third test: I changed the +1 to +2, so as to give the previous command in the script enough time (which is a killall java). After normal operation, the command is issued, but this time a fsck was needed again. I'm thinking about it, there are only 2 applications running right before that command gets executed. - Vuze - pgl-gui (peerguardian for Linux) The complete script actually looks like this: vlc -f play killall java sudo /sbin/shutdown -h +2 vlc is started full screen with playlist file play, the last item in the playlist tells vlc to exit. Then killall java is executed to tell vuze to terminate (failing to do so results in vuze complaining about suddenly being stopped, due to the shutdown procedure). That is also the reason for the 1 minute delay, so as to give Vuze enough time to properly terminate. I had no problems with this before the reinstall. I'll remember to stop pgl-gui today, if that doesn't fix it, I'm out of ideas. Kind regards, Steven signature.asc Description: This is a digitally signed message part
Re: fsck forced when using /sbin/shutdown
On Mon, Apr 23, 2012 at 11:54, Steven Post redalert.comman...@gmail.com wrote: I'm thinking about it, there are only 2 applications running right before that command gets executed. - Vuze - pgl-gui (peerguardian for Linux) The complete script actually looks like this: vlc -f play killall java sudo /sbin/shutdown -h +2 vlc is started full screen with playlist file play, the last item in the playlist tells vlc to exit. Then killall java is executed to tell vuze to terminate (failing to do so results in vuze complaining about suddenly being stopped, due to the shutdown procedure). That is also the reason for the 1 minute delay, so as to give Vuze enough time to properly terminate. I had no problems with this before the reinstall. I'll remember to stop pgl-gui today, if that doesn't fix it, I'm out of ideas. Is it possible to shutdown vuze gracefully instead of killing java out from under it? Or there are a lot of torrent clients that are likely to be better behaved than vuze... Cheers, Kelly Clowers -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAFoWM=93TFG67d9B=AOnoONjECEQux+dziUtCsy=sx+q781...@mail.gmail.com
Re: fsck forced when using /sbin/shutdown
On Mon, 2012-04-23 at 12:07 -0700, Kelly Clowers wrote: [...] Is it possible to shutdown vuze gracefully instead of killing java out from under it? I couldn't find anything back when I wrote the script besides killing java. But I just did another search and came up with vuze --closedown which seems to work fine. Or there are a lot of torrent clients that are likely to be better behaved than vuze... True, but I find that they lack configuration options with regard to queuing. I searched for other clients before, as Vuze was having regular crashes (whether this was down to Vuze or the JRE used, I don't know, but it doesn't crash anymore, so it isn't as much of an issue anymore). That aside, I don't believe it is Vuze's fault that the filesystem is corrupted, for that matter, I think it is up to the OS to prevent that by killing the applications, then writing out the remaining buffers and cleanly unmount the filesystem. Which is clearly not happening here, however I'm fairly sure that about any Linux system, especially Debian, does this kind of thing right, leaving aside power failures and hardware problems. Still puzzled about this. Kind regards, Steven signature.asc Description: This is a digitally signed message part
Re: fsck forced when using /sbin/shutdown
On Mon, 23 Apr 2012 20:54:31 +0200, Steven Post wrote: On Fri, 2012-04-20 at 15:09 +, Camaleón wrote: [...] /dev/sdc1 is the partition with data inconsistency, what we have to find out is why it's left in such state. Another possibility, should you have the chance, could be backup the full partition, reformat it and start over. Being just your /home this won't present any difficulty. Apart from the fact that I need someway to backup the data :) While not crucial data, I'd rather keep it. It's just a bit too big to add to my current backup system. Okay then :-) Is is perhaps possible that Gnome is writing out some config files in my home directory during shutdown and the system cuts power prematurely? I also noticed a message saying the device from / is busy during the shutdown sequence, but never /home, while the root filesystem doesn't need the check. (...) Yes, that was indeed the aim of my dumb suggestion :-) Well, any suggestion is welcome. I did some tests and it doesn't look like it's Gnome itself, at least not right after booting. First test: 1) boot 2) log in using a tty instead of gdm (Ctrl + Alt + F1) 3) issue the sudo /sbin/shutdown -h +1 command result: no fsck needed Second test: 1) boot 2) log in using gdm3 and starting a regular Gnome session 3) switch to tty1, login there 4) issue the sudo /sbin/shutdown -h +1 command result: no fsck needed Third test: I changed the +1 to +2, so as to give the previous command in the script enough time (which is a killall java). After normal operation, the command is issued, but this time a fsck was needed again. Mmm... what worries me is why an fsck is even needed just because a non- vital application is not being closed gracefully on shutdown, that's not something I would consider worth for a fsck :-? Steven, have you considered a hardware related problem? Just in case, running smartctl over the disk that holds the partition won't hurt. I'm thinking about it, there are only 2 applications running right before that command gets executed. - Vuze - pgl-gui (peerguardian for Linux) The complete script actually looks like this: vlc -f play killall java sudo /sbin/shutdown -h +2 vlc is started full screen with playlist file play, the last item in the playlist tells vlc to exit. Then killall java is executed to tell vuze to terminate (failing to do so results in vuze complaining about suddenly being stopped, due to the shutdown procedure). That is also the reason for the 1 minute delay, so as to give Vuze enough time to properly terminate. I had no problems with this before the reinstall. When you shutdown the system all of the opened applications and those in memory should be automatically closed but yet again, IMO a fsck is too much for an application that was not closed properly. I'll remember to stop pgl-gui today, if that doesn't fix it, I'm out of ideas. Well, to discard any of these applications as the source of the problem, you can manually run the commands of the script, one by one and before you issue the shutdown run ps to check whether there's any instance of that applications running in the background and if so, kill them and then proceed with the shutdown. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jn4et7$68l$9...@dough.gmane.org
Re: fsck forced when using /sbin/shutdown
On Thu, 19 Apr 2012 20:54:46 +0200, Steven Post wrote: On Thu, 2012-04-19 at 17:31 +, Camaleón wrote: And is it true that there were errors? What does the fsck log say? I found no further clue in /var/log/fsck/checkfs, here is the complete output: (...) /dev/sdc1 contains a file system with errors, check forced. /dev/sdc1: 398799/38772736 files (3.9% non-contiguous), 112892386/155062264 blocks Mmm, the file system on that partition had errors, the fsck was right. I can see the fsck making progress and after it reaches 100% the system just continues to boot. sde1 in this case is /boot on the SSD, sdc1 is /home on the HDD. The lvm volume I hadn't mentioned are different hard drives, those don't cause any problems and were present in the same configuration on the previous install. /dev/sdc1 is the partition with data inconsistency, what we have to find out is why it's left in such state. Another possibility, should you have the chance, could be backup the full partition, reformat it and start over. Being just your /home this won't present any difficulty. I wonder what difference can be in shutting down from GNOME and doing it from the command line, mmm... :-? Is is perhaps possible that Gnome is writing out some config files in my home directory during shutdown and the system cuts power prematurely? I also noticed a message saying the device from / is busy during the shutdown sequence, but never /home, while the root filesystem doesn't need the check. (...) Yes, that was indeed the aim of my dumb suggestion :-) Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jmru7s$o0u$1...@dough.gmane.org
can't get virsh shutdown (kvm) working with ACPI, ACPI events not detected
Hi, I have a Debian (testing) virtual image above KVM, but I can't get the shutdown event work. I installed in my virtual image acpi-support (and acpi) packages to get acpi support and I tried to load the button kernel module (as it seems shutdown event maps to button event). However, looking with acpi_listen, or kacpimonitor, I can't see any event passing through when executing the shutdown command with virsh. Has anyone an idea on how to fix this (or investigate it) ? Thanks Olivier -- gpg key id: 4096R/326D8438 (keyring.debian.org) Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f9006a4.5010...@irisa.fr
Re: can't get virsh shutdown (kvm) working with ACPI, ACPI events not detected
Le 4/19/12 2:35 PM, Olivier Sallou a écrit : Hi, I have a Debian (testing) virtual image above KVM, but I can't get the shutdown event work. I installed in my virtual image acpi-support (and acpi) packages to get acpi support and I tried to load the button kernel module (as it seems shutdown event maps to button event). However, looking with acpi_listen, or kacpimonitor, I can't see any event passing through when executing the shutdown command with virsh. Has anyone an idea on how to fix this (or investigate it) ? Answer to myself after many tests. Installing acpi packages of course, plus modprobe on button and evdev Thanks Olivier -- Olivier Sallou IRISA / University of Rennes 1 Campus de Beaulieu, 35000 RENNES - FRANCE Tel: 02.99.84.71.95 gpg key id: 4096R/326D8438 (keyring.debian.org) Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f901944.9030...@irisa.fr
Re: fsck forced when using /sbin/shutdown
On Wed, 18 Apr 2012 21:19:09 +0200, Steven Post wrote: I have this really annoying problem when I shutdown the machine using sudo /sbin/shutdown -h +1 The machine seems to properly shutdown, but I always (at least I think) get the message that a filesystem contains errors and needs to be checked. When I use the shutdown option in Gnome, the system boots fine without the fsck. And is it true that there were errors? What does the fsck log say? I wonder what difference can be in shutting down from GNOME and doing it from the command line, mmm... :-? This is really annoying, especially as both / and /boot are on an SSD, the system that is checked is always another rotational hard disk mounted on /home. The problem started when I reinstalled Debian Wheezy on the new SSD, using the AMD64 architecture. At the same time I got rid of an old, unused, partition on the HDD and extended the existing ext4 partition to include the newly claimed space. All this using the Debian installer. Before the reinstall the system was running Wheezy on the i386 architecture and the now extended partition was already used as /home, it was not changed other then extending it. Any ideas? One dumb idea, yup. Before you shutdown the system from command line, logout from your current GNOME session, go to a tty and then run the shutdown sequence from there. Is the fsck still coming up when you boot? Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jmpi51$kai$1...@dough.gmane.org
Re: fsck forced when using /sbin/shutdown
On Thu, 2012-04-19 at 17:31 +, Camaleón wrote: On Wed, 18 Apr 2012 21:19:09 +0200, Steven Post wrote: I have this really annoying problem when I shutdown the machine using sudo /sbin/shutdown -h +1 The machine seems to properly shutdown, but I always (at least I think) get the message that a filesystem contains errors and needs to be checked. When I use the shutdown option in Gnome, the system boots fine without the fsck. And is it true that there were errors? What does the fsck log say? I found no further clue in /var/log/fsck/checkfs, here is the complete output: ### Log of fsck -C -R -A -a Thu Apr 19 20:21:12 2012 fsck from util-linux 2.20.1 /dev/sde1: clean, 241/61056 files, 13476/243968 blocks /dev/sdc1 contains a file system with errors, check forced. /dev/sdc1: 398799/38772736 files (3.9% non-contiguous), 112892386/155062264 blocks /dev/mapper/mydatavolumegroup-mydatalv: clean, 285499/183148544 files, 723935104/732567552 blocks (check in 2 mounts) fsck died with exit status 1 # I can see the fsck making progress and after it reaches 100% the system just continues to boot. sde1 in this case is /boot on the SSD, sdc1 is /home on the HDD. The lvm volume I hadn't mentioned are different hard drives, those don't cause any problems and were present in the same configuration on the previous install. I wonder what difference can be in shutting down from GNOME and doing it from the command line, mmm... :-? Is is perhaps possible that Gnome is writing out some config files in my home directory during shutdown and the system cuts power prematurely? I also noticed a message saying the device from / is busy during the shutdown sequence, but never /home, while the root filesystem doesn't need the check. [...] Any ideas? One dumb idea, yup. Before you shutdown the system from command line, logout from your current GNOME session, go to a tty and then run the shutdown sequence from there. Is the fsck still coming up when you boot? I'll try that this evening, thanks for the suggestion. Kind regards, Steven signature.asc Description: This is a digitally signed message part
fsck forced when using /sbin/shutdown
Hi list, I have this really annoying problem when I shutdown the machine using sudo /sbin/shutdown -h +1 The machine seems to properly shutdown, but I always (at least I think) get the message that a filesystem contains errors and needs to be checked. When I use the shutdown option in Gnome, the system boots fine without the fsck. This is really annoying, especially as both / and /boot are on an SSD, the system that is checked is always another rotational hard disk mounted on /home. The problem started when I reinstalled Debian Wheezy on the new SSD, using the AMD64 architecture. At the same time I got rid of an old, unused, partition on the HDD and extended the existing ext4 partition to include the newly claimed space. All this using the Debian installer. Before the reinstall the system was running Wheezy on the i386 architecture and the now extended partition was already used as /home, it was not changed other then extending it. Any ideas? Kind regards, Steven signature.asc Description: This is a digitally signed message part
Re: shutdown not working in Gnome / KDE
On Sun, 18 Mar 2012 21:44:35 +0100, Peter Baranyi wrote: I can only shut down my pc from a root terminal with 'poweroff' (or shutdown) but not from graphical environments. From Gnome2, sometimes it shuts down, sometimes I get back to gdm. From gdm, the shutdown action sometimes works, sometimes it just quits gdm. GNOME2? What Debian flavour are you running? In KDE 4.7.4, shutdown in the application launcher menu does nothing, or dims the screen. How do I fix this? I do not see any error messages. If it used to work, I would report it. Debian unstable, 3.1.0-1-686-pae Unstable and GNOME2? :-? Anyway, that kernel is old. Try to update it (now 3.2.10). Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jk74pu$6c2$6...@dough.gmane.org
Re: shutdown not working in Gnome / KDE
On Mon, 2012-03-19 at 11:20 +, Camaleón wrote: On Sun, 18 Mar 2012 21:44:35 +0100, Peter Baranyi wrote: If it used to work, I would report it. you mean with the reportbug program? I don't know in which package this bug is. (I never reported any Debian bugs before) Debian unstable, 3.1.0-1-686-pae Unstable and GNOME2? :-? I didn't do a dist upgrade, so some packages are older. I wanted to keep gnome2 because I won't use gnome3. Anyway, that kernel is old. Try to update it (now 3.2.10). OK I will try it, thanks. Regards, Peter -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1332184558.4994.11.camel@timeout
Re: shutdown not working in Gnome / KDE
On Mon, 19 Mar 2012 20:15:58 +0100, Peter Baranyi wrote: On Mon, 2012-03-19 at 11:20 +, Camaleón wrote: On Sun, 18 Mar 2012 21:44:35 +0100, Peter Baranyi wrote: If it used to work, I would report it. you mean with the reportbug program? Or manually (by e-mail), you can choose what's best way for you: http://www.debian.org/Bugs/Reporting.en.html I don't know in which package this bug is. (I never reported any Debian bugs before) As the problem it presents when you're inside X (you can shutdown the system on a tty) you can register the bug against gnome or kde package. Don't worry for a bad assignation, devels/packagers will correct it should needed. Debian unstable, 3.1.0-1-686-pae Unstable and GNOME2? :-? I didn't do a dist upgrade, so some packages are older. I wanted to keep gnome2 because I won't use gnome3. This can be also a source for problems and a big can of worms... GNOME 2 (and its associated libraries) will be dropped sooner or later and keeping it up-to-date from wheezy onwards it does not have to be an easy task. Anyway, that kernel is old. Try to update it (now 3.2.10). OK I will try it, thanks. It sounds more a DE issue than nothing but who knows, it may help. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jk893r$6c2$3...@dough.gmane.org
shutdown not working in Gnome / KDE
Hi, I can only shut down my pc from a root terminal with 'poweroff' (or shutdown) but not from graphical environments. From Gnome2, sometimes it shuts down, sometimes I get back to gdm. From gdm, the shutdown action sometimes works, sometimes it just quits gdm. In KDE 4.7.4, shutdown in the application launcher menu does nothing, or dims the screen. How do I fix this? I do not see any error messages. Debian unstable, 3.1.0-1-686-pae thanks. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1332103475.3812.11.camel@timeout
Re: problematic poweroff on shutdown
On 2012-01-03, Bob Proulx b...@proulx.com wrote: Now you say rebooting requires and entails the exact same electrical event as a poweroff? I don't quite understand. You mean that reboot powers off the machine, and then turns it back on again immediately, whereas a shutdown/poweroff simply powers the machine off? =20 Isn't that the way that it works? I always thought that it did. All of the behavior indicates to me that it does. But I could easily be wrong about it. Perhaps one of our loyal readers will know the answer off the top of their head and will type in a response concerning actual power supply operation. Otherwise I will need to put a probe on the power pins and determine the answer by looking. Wikipedia says a soft reboot involves restarting the computer under software control without removing power, whereas a hard reboot according to them is some sort of unfortunate accident (or desperate last-ditch alternative to an unresponsive system) in which the power is cut and then restored without a proper shutdown procedure having taken place. http://en.wikipedia.org/wiki/Rebooting_(computing) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/slrnjg8921.51q.cu...@einstein.electron.org
Re: problematic poweroff on shutdown [Fwd:]
On 2012-01-03, Don Juan donjuans...@gmail.com wrote: you could always do alt+sysrq REISUB that's a gentler way to shut down No, I couldn't, because the system is halted and there's no magic left. This machine, an Acer X1430 running debian squeeze with a 2.6.32-5-amd64 kernel, always shuts down properly but periodically fails to power off. If its a nvidia or ati card you could have the dreaded issues of xorg-server not playing nicely. I just recently had to pin xorg-server in sid to be able to cleanly shutdown and reboot again. There are a bunch of bugs open in regards to nvidia and ati and most are in relation to xorg-server. I have an ATI card. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/slrnjg67vg.41k.cu...@einstein.electron.org
Re: problematic poweroff on shutdown
Curt wrote: Periodically, for no reason I can fathom, or trace to a specific cause, when I shutdown my machine, it fails to power off. The shutdown procedure unrolls, or unfurls, as expected, but at the point where it says at the console Will now halt, instead of a power off taking place, the console displays an additional message: Power off. At that point, my only alternative is to press the power buttom at the front of the machine for five seconds, which turns the machine off (this seems a gentler alternative to yanking out the power cord from the socket, as the psu on this 'puter has no power switch). How would I go about trouble-shooting this erratic behavior? Just two months ago I had this exact same problem with a brand new Intel motherboard. Searching the motherboard site for BIOS upgrades I found that there was one available and in my case the changelog for it listed reboot problems as one of the fixes. I upgraded the BIOS and my problem was resolved. I don't know if this will be your problem too but the BIOS firmware is where I would start looking for the problem. Bob signature.asc Description: Digital signature
Re: problematic poweroff on shutdown
On 2012-01-03, Bob Proulx b...@proulx.com wrote: Just two months ago I had this exact same problem with a brand new Intel motherboard. Searching the motherboard site for BIOS upgrades I found that there was one available and in my case the changelog for it listed reboot problems as one of the fixes. I upgraded the BIOS and my problem was resolved. Reboot problems? I don't have any of those; sometimes when shutting down the machine it will not power off. I'm talking uniquely and exclusively about the electrical acpi event that occurs after the shutdown procedure has successfully terminated. Maybe in my ignorance my terminology is faulty. I don't know if this will be your problem too but the BIOS firmware is where I would start looking for the problem. I'll look into that. Thank you. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/slrnjg6olp.58t.cu...@einstein.electron.org
Re: problematic poweroff on shutdown
Curt wrote: Bob Proulx wrote: Just two months ago I had this exact same problem with a brand new Intel motherboard. Searching the motherboard site for BIOS upgrades I found that there was one available and in my case the changelog for it listed reboot problems as one of the fixes. I upgraded the BIOS and my problem was resolved. Reboot problems? I don't have any of those; sometimes when shutting down the machine it will not power off. Power-off hang. Reboot hang. Neither worked. They are the same thing. Both actions could not control the power supply from software. It just hung. Required a finger on the physical power button. Wasn't that what you said your problem was too? If not then sorry for the noise. I thought it was the same problem. Bob signature.asc Description: Digital signature
Re: problematic poweroff on shutdown
On 2012-01-03, Bob Proulx b...@proulx.com wrote: Power-off hang. Reboot hang. Neither worked. They are the same thing. Both actions could not control the power supply from software. Well, now I'm confused. I might have a reboot problem and not know about it in the sense that I hardly ever reboot (I think the only linux reboot that was ever required of me in the course of my usage of the OS was after a kernel update). Now you say rebooting requires and entails the exact same electrical event as a poweroff? I don't quite understand. You mean that reboot powers off the machine, and then turns it back on again immediately, whereas a shutdown/poweroff simply powers the machine off? I'm talking soft reboot here, shutdown -r now. You must surely be talking hard reboot? I turn off my machine once a day, at night. There have been no problems turning it back on again, no hangs on rebooting (hard). Sorry for leading you down this trail of confusion. that what you said your problem was too? If not then sorry for the noise. I thought it was the same problem. Bob --IrhDeMKUP4DT/M7F Content-Type: application/pgp-signature; name=signature.asc Content-Description: Digital signature --IrhDeMKUP4DT/M7F-- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/slrnjg6rj5.5he.cu...@einstein.electron.org
Re: problematic poweroff on shutdown
Curt wrote: Bob Proulx wrote: Power-off hang. Reboot hang. Neither worked. They are the same thing. Both actions could not control the power supply from software. Well, now I'm confused. I might have a reboot problem and not know about it in the sense that I hardly ever reboot (I think the only linux reboot that was ever required of me in the course of my usage of the OS was after a kernel update). Now you say rebooting requires and entails the exact same electrical event as a poweroff? I don't quite understand. You mean that reboot powers off the machine, and then turns it back on again immediately, whereas a shutdown/poweroff simply powers the machine off? Isn't that the way that it works? I always thought that it did. All of the behavior indicates to me that it does. But I could easily be wrong about it. Perhaps one of our loyal readers will know the answer off the top of their head and will type in a response concerning actual power supply operation. Otherwise I will need to put a probe on the power pins and determine the answer by looking. With the AT power standard computers only had the big clunk switch and that was the only way to power them off. With the introduction of the ATX power standard this became software controllable. But remember that there is always the +5V standby power which is always on regardless of other settings. In addition there is the Power Good signal which acts as a hardware reset signal. When the supply is off then the Power Good signal is off. Power Good should pause a few milliseconds before signaling good to allow the power supply to stabilize. Those signals come from the power supply to the computer circuitry. Going from the computer circuitry to the power supply is the Power On signal. Pulling the power on signal low signals the supply to turn on. And bringing it high will turn it off. Moving the signal high and then low again will cause the supply to turn off and then back on again and the Power Good signal will send a reset. I'm talking soft reboot here, shutdown -r now. You must surely be talking hard reboot? I turn off my machine once a day, at night. There have been no problems turning it back on again, no hangs on rebooting (hard). I was talking about both 'shutdown -h now' and 'shutdown -r now' behavior. It didn't matter. Both would hang. Upgrading the BIOS solved the problem. The note says: Fixed Linux reboot failure. http://downloadmirror.intel.com/20541/eng/MW_0098_ReleaseNotes.pdf Rebooting *is* very important. The Linux kernel routinely has security upgrades published for it. After installing the new security patch kernel it is important that the system be rebooted to the new kernel so that the security vulnerability is mitigated. I definitely want my systems to be able to reboot unattended. Sorry for leading you down this trail of confusion. Happy trails! :-) Bob signature.asc Description: Digital signature
problematic poweroff on shutdown
Periodically, for no reason I can fathom, or trace to a specific cause, when I shutdown my machine, it fails to power off. The shutdown procedure unrolls, or unfurls, as expected, but at the point where it says at the console Will now halt, instead of a power off taking place, the console displays an additional message: Power off. At that point, my only alternative is to press the power buttom at the front of the machine for five seconds, which turns the machine off (this seems a gentler alternative to yanking out the power cord from the socket, as the psu on this 'puter has no power switch). How would I go about trouble-shooting this erratic behavior? I hijacked another thread in which I posited that the problem was related to plugging in an external usb hard drive. This supposition has turned out to be false (post hoc ergo propter hoc), as so many of my suppositions do these days. ;-) There's nothing in the logs to distinguish the no poweroff shutdowns from the poweroff ones (I don't think; I have looked). -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/slrnjg3n43.419.cu...@einstein.electron.org
Re: problematic poweroff on shutdown
G'day Curt. On 03/01/12 02:34, Curt wrote: There's nothing in the logs to distinguish the no poweroff shutdowns from the poweroff ones (I don't think; I have looked). I wouldn't think there would be at the very end, because everything is expecting to be powered off. Which makes everything all the more tricky. I'm assuming this is a laptop? There's a couple of things you can try, but I would suggest looking at playing about with reboot= kernel parameters. This is a pretty straight-forward thing to set up but will require some trial and error to see what works. Have a look here: http://linux.koolsolutions.com/2009/08/04/howto-fix-linux-hangfreeze-during-reboots-and-restarts/ (Just press e and add them to the kernel temporarily initially. If you find one that works you can set it up in grub later on) Also, does this occur only on shutdown? Does it happen sometimes if you're rebooting rather than powering off? Another option is to update to a newer kernel - could please clarify what you're using (Squeeze, Wheezy etc)? Cheers, Ashton. -- Ashton Fagg (ash...@fagg.id.au) Web: http://www.fagg.id.au/~ashton/ Keep calm and call Batman. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f02404c.2030...@fagg.id.au
Re: problematic poweroff on shutdown [Fwd:]
Original Message Subject:Re: problematic poweroff on shutdown Date: Mon, 02 Jan 2012 08:42:08 -0800 From: Don Juan donjuans...@gmail.com To: Curt cu...@free.fr On 01/02/2012 08:34 AM, Curt wrote: Periodically, for no reason I can fathom, or trace to a specific cause, when I shutdown my machine, it fails to power off. The shutdown procedure unrolls, or unfurls, as expected, but at the point where it says at the console Will now halt, instead of a power off taking place, the console displays an additional message: Power off. At that point, my only alternative is to press the power buttom at the front of the machine for five seconds, which turns the machine off (this seems a gentler alternative to yanking out the power cord from the socket, as the psu on this 'puter has no power switch). How would I go about trouble-shooting this erratic behavior? I hijacked another thread in which I posited that the problem was related to plugging in an external usb hard drive. This supposition has turned out to be false (post hoc ergo propter hoc), as so many of my suppositions do these days. ;-) There's nothing in the logs to distinguish the no poweroff shutdowns from the poweroff ones (I don't think; I have looked). you could always do alt+sysrq REISUB that's a gentler way to shut down (reboot actually) in an extreme case like that, then you could always edit grub and go directly to init 3. Depending on your kernel adding kernel.sysrq = 1 will activate it REISUB But I think you have to enable it in sysctl.conf, if I remember correctly off the top of my head. What kind of video card are you running. Have you tried switching to another console when it freezes? If its a nvidia or ati card you could have the dreaded issues of xorg-server not playing nicely. I just recently had to pin xorg-server in sid to be able to cleanly shutdown and reboot again. There are a bunch of bugs open in regards to nvidia and ati and most are in relation to xorg-server. Best guess I can make without info Sorry sent this earlier but I did not send the reply to the list. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f024af0.7050...@gmail.com
Re: problematic poweroff on shutdown
On 2012-01-02, Ashton Fagg ash...@fagg.id.au wrote: G'day Curt. On 03/01/12 02:34, Curt wrote: There's nothing in the logs to distinguish the no poweroff shutdowns from the poweroff ones (I don't think; I have looked). I wouldn't think there would be at the very end, because everything is expecting to be powered off. Which makes everything all the more tricky. I'm assuming this is a laptop? This is not a laptop. This is an Acer x1430 running debian squeeze. There's a couple of things you can try, but I would suggest looking at playing about with reboot= kernel parameters. This is a pretty straight-forward thing to set up but will require some trial and error to see what works. Have a look here: http://linux.koolsolutions.com/2009/08/04/howto-fix-linux-hangfreeze-during-reboots-and-restarts/ (Just press e and add them to the kernel temporarily initially. If you find one that works you can set it up in grub later on) Also, does this occur only on shutdown? Does it happen sometimes if you're rebooting rather than powering off? There are no freezes or hangs, nor does this have anything to do with rebooting the machine; after the shutdown procedure has terminated, the machine periodically simply fails to power off. That is all. Another option is to update to a newer kernel - could please clarify what you're using (Squeeze, Wheezy etc)? curty@einstein:~$ uname -a Linux einstein 2.6.32-5-amd64 #1 SMP Thu Nov 3 03:41:26 UTC 2011 x86_64 GNU/Linux Thanks for your time. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/slrnjg5c17.3c2.cu...@einstein.electron.org
X being shutdown without warning
Since yesterday (and I presume something which got updated in my SID desktop) I can reliably crash X when running Mythtv. I just move the mouse about/offscreen. It doesn't lockup, like is normally the case, rather I instantly logout, and am left with the gdm login screen. Looking at the end of Xorg.0.Log.old is see the following lines which aren't in the current Xorg. [ 35741.884] (II) Power Button: Close [ 35741.884] (II) UnloadModule: evdev [ 35741.884] (II) Unloading evdev [ 35741.900] (II) Power Button: Close [ 35741.900] (II) UnloadModule: evdev [ 35741.900] (II) Unloading evdev [ 35741.944] (II) Logitech USB-PS/2 Optical Mouse: Close [ 35741.944] (II) UnloadModule: evdev [ 35741.944] (II) Unloading evdev [ 35741.944] (II) Logitech Logitech Illuminated Keyboard: Close [ 35741.944] (II) UnloadModule: evdev [ 35741.944] (II) Unloading evdev [ 35741.964] (II) Logitech Logitech Illuminated Keyboard: Close [ 35741.964] (II) UnloadModule: evdev [ 35741.964] (II) Unloading evdev [ 35742.649] Server terminated successfully (0). Closing log file. Its not very helpful - it seems to indicate that the PowerButton has been pressed - but that didn't happen. I would like to report a bug, but I am not sure where to go from here to find what actually caused it. I don't think MythTV updated yesterday, so I assume it wasn't that Anyone any ideas what could have happened here. -- Alan Chandler http://www.chandlerfamily.org.uk -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ee24057.6010...@chandlerfamily.org.uk
Re: X being shutdown without warning
On 09/12/11 17:07, Alan Chandler wrote: Anyone any ideas what could have happened here. just seen a message on debian-kde that implies it could have been libdrm-intel1 -- Alan Chandler http://www.chandlerfamily.org.uk -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ee2423b.2080...@chandlerfamily.org.uk
Re: X being shutdown without warning
On Friday 09 December 2011 18:15:39 Alan Chandler wrote: On 09/12/11 17:07, Alan Chandler wrote: Anyone any ideas what could have happened here. just seen a message on debian-kde that implies it could have been libdrm-intel1 Last week I had a problem playing videos. When I tried to watch a video, the system threw me to the login screen. I started to uninstall the last upgrade and then I discovered that the problem was the libdrm-intel1. After that I've decided to downgrade to testing. Regards Michel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201112091832.50807.michel.blankle...@gmail.com
Re: X being shutdown without warning
On 12/09/2011 09:32 AM, Michel Blankleder wrote: On Friday 09 December 2011 18:15:39 Alan Chandler wrote: On 09/12/11 17:07, Alan Chandler wrote: Anyone any ideas what could have happened here. just seen a message on debian-kde that implies it could have been libdrm-intel1 Last week I had a problem playing videos. I had a similar problem with a flash movie on a webpage, but it isn't consistent. There did seem to be a connection between the movie and moving the mouse. I had this happen a lot in Ubuntu and various window managers, which is why I switched back to Debian. I don't think it ever happened with Debian stable, but I recently moved to Sid and I think it has happened once. I haven't been able to reliably recreate it, though. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ee2705e.6050...@yahoo.com
LUKS and LVM sequence at boot and shutdown incorrect
My laptop hard drive configuration: sda1 - win7 sda2 - /boot sda3 - LVM on top of LUKS partition - (separate LVs for /, /home, and SWAP) sda5 - FAT32 for the most part everything seems to be working fine except the order of modules/components when Debian boots up. When I boot Debian, it first looks for the LVM VG and LV, and then the LUKS container. - I encrypted the PV, I thought the order should be the other way around. So when it boots, message on the screen says it failed to load the VG and the LVs and then gives me an option to enter my pass-phrase. Because I have LVM on top of LUKS I thought it would first open the LUKS container and then load the LVM container. I have the same problem when shutting down. It closes the LUKS container and then throws up an error saying it cannot find VG and LVs (or something similar). Of course it will not find hte VG once the LUKS container is closed. Not sure how this happened. Can anyone explain how to fix this. Thanks -- Kind regards, Yudi
Re: LUKS and LVM sequence at boot and shutdown incorrect
On Fri, Aug 19, 2011 at 10:50:12AM CEST, yudi v yudi@gmail.com said: My laptop hard drive configuration: sda1 - win7 sda2 - /boot sda3 - LVM on top of LUKS partition - (separate LVs for /, /home, and SWAP) sda5 - FAT32 for the most part everything seems to be working fine except the order of modules/components when Debian boots up. When I boot Debian, it first looks for the LVM VG and LV, and then the LUKS container. - I encrypted the PV, I thought the order should be the other way around. So when it boots, message on the screen says it failed to load the VG and the LVs and then gives me an option to enter my pass-phrase. Because I have LVM on top of LUKS I thought it would first open the LUKS container and then load the LVM container. I have the same problem when shutting down. It closes the LUKS container and then throws up an error saying it cannot find VG and LVs (or something similar). Of course it will not find hte VG once the LUKS container is closed. Not sure how this happened. Can anyone explain how to fix this. Did you try to use the early option in cryptsetup ? It make sthe luks part being done earlier at boot time (in the cryptdisks-early boot script). -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110819085641.gj32...@rail.eu.org
Re: LUKS and LVM sequence at boot and shutdown incorrect
Did you try to use the early option in cryptsetup ? It make sthe luks part being done earlier at boot time (in the cryptdisks-early boot script). did not know that, thanks for pointing it out. I did not read anything about it in the installation documentation. I thought the installer will be smart enough to figure out that it needs to open the LUKS container to get to the LVs. I will definitely read up on this issue. -- Kind regards, Yudi
Re: LUKS and LVM sequence at boot and shutdown incorrect
On Fri, Aug 19, 2011 at 11:23:42AM CEST, yudi v yudi@gmail.com said: Did you try to use the early option in cryptsetup ? It make sthe luks part being done earlier at boot time (in the cryptdisks-early boot script). did not know that, thanks for pointing it out. I did not read anything about it in the installation documentation. I thought the installer will be smart enough to figure out that it needs to open the LUKS container to get to the LVs. I will definitely read up on this issue. Thinking about it there surely is something to do about the initrd.img, which is in use when you boot (because / is not yet mounted). I do not know much about it, it surely is worth reading about. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110819101857.gk32...@rail.eu.org
Re: LUKS and LVM sequence at boot and shutdown incorrect
Thinking about it there surely is something to do about the initrd.img, I thought so too. looks like I need to build a new initrd.img. -- Kind regards, Yudi
shutdown problem in combination with autofs/NFS
Hello, occassionally our Debian 6 boxes don't shutdown. The shutdown process hangs forever with the last messages: Turning off quotas:...Checking for running unattended-upgrades: I assume, I found the reason for this issue, but no solution. Our linux computers mount some directories via NFS. The directories /home and /sw are managed by the automounter. /usr/local is a symlink to /sw/local.debian-6 which is mounted from the NFS server. While shutting down, sometimes the automounter finishes to early. Afterwards all scripts in /etc/init.d which look for binaries in /usr/local/bin hang. Until Debian 5 this wasn't an issue, because the automounter finishes at a well defined time relatively to other services. But with the new dependency based init system, this time seems to vary and sometimes the automounter finishes to early. If this situation occurs, all local terminals are dead and can be used for debugging. But from an open ssh session I can restart autofs and then the shutdown goes further. First I tried to remove /usr/local/bin from the PATH variable in /etc/profiles. But this doesn't not help, because a lot of init scripts define theire own PATH variable: # grep -l PATH.*/usr/local/bin /etc/init.d/* /etc/init.d/alsa-utils /etc/init.d/apache2 /etc/init.d/binfmt-support /etc/init.d/cpufrequtils /etc/init.d/cups /etc/init.d/hal /etc/init.d/ipmievd /etc/init.d/libvirt-bin /etc/init.d/networking /etc/init.d/quota /etc/init.d/quotarpc /etc/init.d/saned /etc/init.d/schroot /etc/init.d/sysstat /etc/init.d/unattended-upgrades Next we tried to adjust the dependencies in /etc/init.d/autofs. But we didn't found a working solution. Is there a simple solution or workaround for this? I didn't filed a bug until now, because of the nonstandard configuration with /usr/local via NFS/autofs. Or should I do this? Ingo Rogalsky -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e42640e.70...@web.de
kernel 3.0 : shutdown issue
Hello List: I have just installed kernel 3.0.0 on my Squeeze box (with some Wheezy stuff): while shutdown process works well with kernel 2.6.39 , it gets into troubles with kernel 3.0.0. In fact, I do not where to look. Any hints is welcome, Jerome -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e31082c.3060...@rezozer.net
Re: kernel 3.0 : shutdown issue
On Thu, Jul 28, 2011 at 2:56 PM, Jerome BENOIT g62993...@rezozer.net wrote: Hello List: I have just installed kernel 3.0.0 on my Squeeze box (with some Wheezy stuff): while shutdown process works well with kernel 2.6.39 , it gets into troubles with kernel 3.0.0. What's kind of trouble. you may wanna be more specific. I tried 3.0.0 on Wheezy. So far so good. In fact, I do not where to look. Any hints is welcome, Jerome -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e31082c.3060...@rezozer.net -- Best Regards, lina -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cag9cjmne8urwiaejw3kt8caur1ku7vvu2wnc38+1ggj3w+p...@mail.gmail.com
Re: kernel 3.0 : shutdown issue
Hello List: On 28/07/11 17:32, lina wrote: On Thu, Jul 28, 2011 at 2:56 PM, Jerome BENOITg62993...@rezozer.net wrote: Hello List: I have just installed kernel 3.0.0 on my Squeeze box (with some Wheezy stuff): while shutdown process works well with kernel 2.6.39 , it gets into troubles with kernel 3.0.0. What's kind of trouble. you may wanna be more specific. You are right. I tried 3.0.0 on Wheezy. So far so good. Thanks for the feed-back. Finally I figure out the issue: it appears that the trouble comes from chrony . I will dig it. Sorry for the noise, Jerome In fact, I do not where to look. Any hints is welcome, Jerome -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e31082c.3060...@rezozer.net -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e31c983.50...@rezozer.net
Re: shutdown via ssh
ola Vitor halt aceita reboot tbm ok abraço 2011/7/11 Vitor Hugo vitorhug...@ymail.com o debian 6 aceita shutdown via ssh? dei um su pra ir pra root e nada de dar shutdown sera que ele bloqueia?
Re: shutdown via ssh
Aceita init 0 também. Saudações, Humberto Araujo de Sousa humbe...@dontec.com.br Em 11/7/2011 20:41, Vitor Hugo escreveu: o debian 6 aceita shutdown via ssh? dei um su pra ir pra root e nada de dar shutdown sera que ele bloqueia? -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e1e39f1.2050...@dontec.com.br
shutdown via ssh
o debian 6 aceita shutdown via ssh? dei um su pra ir pra root e nada de dar shutdown sera que ele bloqueia?
Re: shutdown via ssh
Vitor, tentou ''shutdown -h now'' e/ou ''halt'' ? 2011/7/11 Vitor Hugo vitorhug...@ymail.com o debian 6 aceita shutdown via ssh? dei um su pra ir pra root e nada de dar shutdown sera que ele bloqueia?
Différence entre notable entre shutdown -r now et shutdown -r -n now?
Bonjour. Je fais un script qui se termine par un redémarrage du serveur. Je n'arrive pas à voir la différence transcendante entre shutdown -r now et un shutdown -r -n now J'ai lu le man qui dit que L'option -n empêche shutdown d'appeler init, et lui fait tuer les processus en cours d'exécution lui-même. shutdown désactive ensuite les quotas, les comptes, la mémoire partagée et démonte tous les systèmes de fichiers. En quoi est ce une différence transcendantalle? je capte pas... -- Savez-vous ce que signifie MICROSOFT? Most Intelligent Customers Realize Our Software Only (for) Fools () Teenagers. http://www.linux-squad.com -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: http://lists.debian.org/22dac7da1142346ef7dfa729c64f23b9@localhost
Re: Différence entre notable entre shutdown -r now et shutdown -r -n now?
Le jeudi 30 juin 2011 à 11:15 +0200, Olivier Pavilla a écrit : Je fais un script qui se termine par un redémarrage du serveur. Je n'arrive pas à voir la différence transcendante entre shutdown -r now et un shutdown -r -n now J'ai lu le man qui dit que L'option -n empêche shutdown d'appeler init, et lui fait tuer les processus en cours d'exécution lui-même. shutdown désactive ensuite les quotas, les comptes, la mémoire partagée et démonte tous les systèmes de fichiers. En quoi est ce une différence transcendantalle? je capte pas... selon le man : -n [OBSOLÈTE] Ne pas appeler init(8) pour l'arrêt, mais le faire soi-même. L'utilisation de cette option est découragée, et ses résultats ne sont pas toujours ceux espérés. Qui dit obsolète dit que ce n'est pas la peine de se griller des neurones pour ça : ne l'utilise pas. -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: http://lists.debian.org/1309431593.10658.4.ca...@azuki.aranha.ici
Can I have repeated login failures at the console cause a shutdown?
Does anyone know whether there is a PAM module or equivalent which can be used to make a system shutdown if there are repeated login failures at the console, sort of like pam_tally2 or denyhosts, but with configurable behaviour? My idea is: if I've left my laptop logged on with the screen locked, and it is stolen at that point, I'd like a sequence of failed login attempts in a row to cause the system to shut down, thereby locking my crypto disks. (I know this is not a perfect security approach, but it just makes it somewhat more difficult for a knowledgeable thief to do anything useful with my data.) Julian -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110622163551.ga7...@d-and-j.net
Re: Can I have repeated login failures at the console cause a shutdown?
On 06/22/11 at 05:35pm, Julian Gilbey wrote: Does anyone know whether there is a PAM module or equivalent which can be used to make a system shutdown if there are repeated login failures at the console, sort of like pam_tally2 or denyhosts, but with configurable behaviour? Try pam_exec. With the right stacking, you should be able to get it to do what you need. My idea is: if I've left my laptop logged on with the screen locked, and it is stolen at that point, I'd like a sequence of failed login attempts in a row to cause the system to shut down, thereby locking my crypto disks. Why are you leaving your laptop logged on in an insecure area? You could at the very least set a boot password and suspend to ram or hibernate. -- Liam signature.asc Description: Digital signature
Re: No Display Manager + shutdown/reboot
On Tue, Jun 7, 2011 at 13:46, Perry Thompson ryperven...@yahoo.fr wrote: Hi all. I am using Debian Wheezy with Xfce4. After some testing with different DMs, I decided to start X from a tty using startx. I was told in the Debian IRC channel that it works fine by just removing all DMs. I enjoy using my computer this way, however I am unable to... 1) shutdown my computer by pressing the power button, and 2) choose Shut Down or Restart after pressing ctrl+alt+del (I made a custom keyboard shortcut to call xfce4-session-logout). Both Shut Down and Restart are grayed out, but Log Out works fine. Don't know about xfce, but as an alternative, if you have consolekit installed, then the following commands can be used to shutdown and reboot without needing root privileges. I forget where I got them from, but they work for me (I startx with openbox and no DM). dbus-send --system --print-reply --dest=org.freedesktop.ConsoleKit \ /org/freedesktop/ConsoleKit/Manager org.freedesktop.ConsoleKit.Manager.action where action is either Stop for shutdown or Restart for a reboot. I put them in a script and call them from the openbox menu HTH -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/BANLkTi=mY+0EfjJOQCNp6aLxWfQZ=+4...@mail.gmail.com
Re: No Display Manager + shutdown/reboot
On Tue 07 Jun 2011 at 01:46:49 -0400, Perry Thompson wrote: 1) shutdown my computer by pressing the power button, and You might need xfce4-power-manager for this but I'm not sure. 2) choose Shut Down or Restart after pressing ctrl+alt+del (I made a custom keyboard shortcut to call xfce4-session-logout). Both Shut Down and Restart are grayed out, but Log Out works fine. Install sudo. Use vigr to add yourself to the sudo group. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110607093252.GB19914@desktop
Re: No Display Manager + shutdown/reboot
On 06/07/2011 05:32 AM, Brian wrote: On Tue 07 Jun 2011 at 01:46:49 -0400, Perry Thompson wrote: 1) shutdown my computer by pressing the power button, and You might need xfce4-power-manager for this but I'm not sure. 2) choose Shut Down or Restart after pressing ctrl+alt+del (I made a custom keyboard shortcut to call xfce4-session-logout). Both Shut Down and Restart are grayed out, but Log Out works fine. Install sudo. Use vigr to add yourself to the sudo group. I have xfce4-power-manager and am in the sudoers list. This worked before when I had GDM, but not when I was without a DM or when I tried Slim or NODM. I have not been able to get this to work in any of those three situations. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dee3e93.1010...@yahoo.fr
Re: No Display Manager + shutdown/reboot
On Tue, 07 Jun 2011 11:06:59 -0400, Perry Thompson wrote: On 06/07/2011 05:32 AM, Brian wrote: On Tue 07 Jun 2011 at 01:46:49 -0400, Perry Thompson wrote: 1) shutdown my computer by pressing the power button, and You might need xfce4-power-manager for this but I'm not sure. 2) choose Shut Down or Restart after pressing ctrl+alt+del (I made a custom keyboard shortcut to call xfce4-session-logout). Both Shut Down and Restart are grayed out, but Log Out works fine. Install sudo. Use vigr to add yourself to the sudo group. I have xfce4-power-manager and am in the sudoers list. This worked before when I had GDM, but not when I was without a DM or when I tried Slim or NODM. I have not been able to get this to work in any of those three situations. Not sure if you already tried some of these tips: Handle acpi event for power button, show Xfce logout options http://wiki.xfce.org/tips#handle_acpi_event_for_power_button_show_xfce_logout_options Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.06.07.15.18...@gmail.com
Re: No Display Manager + shutdown/reboot
On 06/07/11 at 11:06am, Perry Thompson wrote: On 06/07/2011 05:32 AM, Brian wrote: On Tue 07 Jun 2011 at 01:46:49 -0400, Perry Thompson wrote: 1) shutdown my computer by pressing the power button, and You might need xfce4-power-manager for this but I'm not sure. 2) choose Shut Down or Restart after pressing ctrl+alt+del (I made a custom keyboard shortcut to call xfce4-session-logout). Both Shut Down and Restart are grayed out, but Log Out works fine. Install sudo. Use vigr to add yourself to the sudo group. I have xfce4-power-manager and am in the sudoers list. This worked before when I had GDM, but not when I was without a DM or when I tried Slim or NODM. I have not been able to get this to work in any of those three situations. in the sudoers list is a bit vague. Do you have the ability to run anything with sudo without password (not that I am recommending this at all)? Does xfce-session-logout know to run the shutdown command with sudo? Perhaps you should modify your custom keyboard shortcut to call sudo xfce4-session-logout instead. When run from a DM, these programs would have root permissions to shut down and reboot your computer. You need to give those permissions back somehow, and sudo seems the easiest way. -- Liam signature.asc Description: Digital signature
Re: No Display Manager + shutdown/reboot
On 06/07/11 at 10:32am, Brian wrote: On Tue 07 Jun 2011 at 01:46:49 -0400, Perry Thompson wrote: 1) shutdown my computer by pressing the power button, and You might need xfce4-power-manager for this but I'm not sure. 2) choose Shut Down or Restart after pressing ctrl+alt+del (I made a custom keyboard shortcut to call xfce4-session-logout). Both Shut Down and Restart are grayed out, but Log Out works fine. Install sudo. Use vigr to add yourself to the sudo group. vigr aside, the sudo group does nothing by default. You don't need to be in it unless you've uncommented the line in sudoers to allow members of that group to do as they please. I don't recommend that use (v. little difference between that and running as root). -- Liam signature.asc Description: Digital signature
Re: No Display Manager + shutdown/reboot
On Tue 07 Jun 2011 at 14:14:06 -0400, William Hopkins wrote: vigr aside, the sudo group does nothing by default. You don't need to be in it As I've just discovered. On my Wheezy xfce4 box I'd never got round to enabling Shutdown and Restart for a user. It turns out installing sudo is all I have to do. No membership of the sudo group at all, Which is what I've seen advised. (I've also seen it recommended to be a member of the powerdev group, but I'm not). So it's mystifying! All users get to shutdown the machine if sudo is on the it. Why don't you need to be in the group sudo? unless you've uncommented the line in sudoers to allow members of that group to do as they please. I don't recommend that use (v. little difference between that and running as root). The %sudo line in /etc/sudoers is uncommented by default. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110607185757.GE19914@desktop
Re: No Display Manager + shutdown/reboot
On Tue 07 Jun 2011 at 19:57:57 +0100, Brian wrote: So it's mystifying! All users get to shutdown the machine if sudo is on the it. Mystery cleared up. I could have been more thorough in what I did and checked everything. Installing sudo ungreys the buttons in the session closing dialogue and rebooting or shutting down is permissable for users in the sudo group or if /etc/sudoers allows it. Otherwise permission is denied. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110607233156.GF19914@desktop
Re: No Display Manager + shutdown/reboot
On Tue 07 Jun 2011 at 11:06:59 -0400, Perry Thompson wrote: I have xfce4-power-manager and am in the sudoers list. This worked before when I had GDM, but not when I was without a DM or when I tried Slim or NODM. I have not been able to get this to work in any of those three situations. How about putting perry ALL=NOPASSWD: /usr/lib/xfce4/session/xfsm-shutdown-helper in /etc/sudoers? You'd better check xfsm-shutdown-helper is in the location given. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110607234458.GG19914@desktop
Re: No Display Manager + shutdown/reboot
On 2011年06月07日 19:44, Brian wrote: On Tue 07 Jun 2011 at 11:06:59 -0400, Perry Thompson wrote: I have xfce4-power-manager and am in the sudoers list. This worked before when I had GDM, but not when I was without a DM or when I tried Slim or NODM. I have not been able to get this to work in any of those three situations. How about putting perry ALL=NOPASSWD: /usr/lib/xfce4/session/xfsm-shutdown-helper in /etc/sudoers? You'd better check xfsm-shutdown-helper is in the location given. I tried that and still no success. I tried it with my screen name, with %users, I tried adding ALL=(root) instead of just ALL=, all of which I found on websites. None of them worked. Any ideas why others have had success and not me? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4deee0f5.3090...@yahoo.fr
No Display Manager + shutdown/reboot
Hi all. I am using Debian Wheezy with Xfce4. After some testing with different DMs, I decided to start X from a tty using startx. I was told in the Debian IRC channel that it works fine by just removing all DMs. I enjoy using my computer this way, however I am unable to... 1) shutdown my computer by pressing the power button, and 2) choose Shut Down or Restart after pressing ctrl+alt+del (I made a custom keyboard shortcut to call xfce4-session-logout). Both Shut Down and Restart are grayed out, but Log Out works fine. Is there any way I can have this do what I want while not using a display manager? Or would I really have to get one? I also tried nodm, but had the same problems. I would still rather not use a DM if possible. Please let me know all of my options and if a solution exists for my problem. Thank you. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dedbb49.5040...@yahoo.fr
Re: Correct usage of -t in shutdown?
On Mon, May 16, 2011 at 9:45 PM, Alex Lardner linuxtu...@gmail.com wrote: Hello, I am stumped over how to use -t during shutdown. I tried: shutdown -t 60 System going down in one minute! and shutdown -t 60 now System going down in one minute! but neither worked as expected. Help me, please! What is the expectation? If it is to shutdown after a minute, replace now with actual time when you want the system to shutdown. For example: shutdown -h 12:34 System going down in one minute! For further information; man shutdown Regards, Burhan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/BANLkTimcq+pOQ2XdWyK7t5t=nwmgl9z...@mail.gmail.com
Correct usage of -t in shutdown?
Hello, I am stumped over how to use -t during shutdown. I tried: shutdown -t 60 System going down in one minute! and shutdown -t 60 now System going down in one minute! but neither worked as expected. Help me, please! Thanks, Alex -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/alpine.deb.2.00.1105161843320.1...@debian.magnolia.oaks
Re: Correct usage of -t in shutdown?
On 05/16/2011 09:45 PM, Alex Lardner wrote: Hello, I am stumped over how to use -t during shutdown. I tried: shutdown -t 60 System going down in one minute! and shutdown -t 60 now System going down in one minute! but neither worked as expected. Help me, please! Thanks, Alex The -t option is to set the delay between warning and kill signal shutdown time (no -t) is what you want, where time is a [hh:]mm time value. From the man page for shutdown: The time argument can have different formats. First, it can be an absolute time in the format hh:mm, in which hh is the hour (1 or 2 digits) and mm is the minute of the hour (in two digits). Second, it can be in the format +m, in which m is the number of minutes to wait The word now is an alias for +0. -- Michael Checca -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dd1df13.4050...@gmail.com
kvm hypervisor host network problem during VM startup/shutdown
(please CC me on replies) I have been running kvm on this host for almost two years now. Using bridged networking, rather simple setup, with about 4 VMs and the hypervisor. There is one bridge, br1 (there is an unused br0 which has no connection out) which is connected to the physical ethernet, one of the VMs is providing DHCP to the whole network. Things work fine, except, when I attempt to create a new host, or destroy a running host. I am playing with FAI profiles now, and so have tested this many times. Every time, the hypervisor briefly (5-10 seconds or so) stopps responding on the network, though, other systems which use the same bridge, have no issue. Script used to start the new VM: virt-install \ --connect qemu:///system \ --pxe \ -n test \ -r 512 \ --vcpus=1 \ --disk path=/dev/vg0/test \ --vnc \ --noautoconsole \ --os-type linux \ --os-variant debianLenny \ --accelerate \ --network=bridge:br1 \ --hvm I run this and get: Starting install... Creating domain... 0 B 00:00 Domain installation still in progress. You can reconnect to the console to complete the installation process. Timeout, server not responding. Then I am back on my local host (I ssh in to the hypervisor). I connect back in, and I can now use virt-viewer to see the console and watch the install (already in progress). The same thing happens when I destroy test via virsh (why graceful shutdown a system being blown away?) I have found that other systems (like the DHCP VM) still respond to ping during this time. In fact, one of them is providing the VPN end point which I am using to get to the hypervisor, and the VPN connection never drops. In the logs, at the same time, I see only the following, though, looking around indicates that these are common and probably not indicitive of an error: May 10 15:27:38 hyper kernel: [492763.100101] device vnet5 entered promiscuous mode May 10 15:27:38 hyper kernel: [492763.104224] br1: port 6(vnet5) entering listening state May 10 15:27:47 hyper kernel: [492772.133560] br1: port 6(vnet5) entering learning state May 10 15:27:56 hyper kernel: [492781.146314] br1: topology change detected, propagating May 10 15:27:56 hyper kernel: [492781.150297] br1: port 6(vnet5) entering forwarding state Bridge is setup in /etc/network/interfaces as follows: auto br1 iface br1 inet static address 192.168.0.6 network 192.168.0.0 netmask 255.255.255.0 gateway 192.168.0.1 bridge_ports eth100 bridge_hello 2 bridge_fd 9 bridge_stp on Anyone else run into this? Any ideas? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dc99589.3020...@carpanet.net
Re: slapcat - unclean shutdown detected; attempting recovery.
Hello. I think, i make a mistake. For a slapcat output theses 2 lines : /unclean shutdown detected; attempting recovery. recovery skipped in read-only mode. Run manual recovery if errors are encountered. / are not an error ! Simply it's because the slapd is running. If i do an ldapadd with good arguments and ldif file, I have a good adding in my ldap. So my bdb is not in read only ! Thanks. L. J. Le 11/04/2011 10:37, Lambert JEANNOU a écrit : Hope you 'll excuse me for my bad english. I have the same problem with my slapd 2.4.23-7 on a new squeeze. unclean shutdown detected; attempting recovery. recovery skipped in read-only mode. Run manual recovery if errors are encountered. I have tried the following : # rm -rf /var/lib/ldap # echo -en set_cachesize 0 1500 1\nset_lg_bsize 2097152\n /var/lib/ldap/DB_CONFIG # slapadd ldap.ldif (before created by slacat ldap.ldif) # /etc/init.d/ldap start That seems ok but at the reboot the same error repeats itself. Thanks for your help. Lambert JEANNOU attachment: lambert_jeannou.vcf
Re: slapcat - unclean shutdown detected; attempting recovery.
Hope you 'll excuse me for my bad english. I have the same problem with my slapd 2.4.23-7 on a new squeeze. unclean shutdown detected; attempting recovery. recovery skipped in read-only mode. Run manual recovery if errors are encountered. I have tried the following : # rm -rf /var/lib/ldap # echo -en set_cachesize 0 1500 1\nset_lg_bsize 2097152\n /var/lib/ldap/DB_CONFIG # slapadd ldap.ldif (before created by slacat ldap.ldif) # /etc/init.d/ldap start That seems ok but at the reboot the same error repeats itself. Thanks for your help. Lambert JEANNOU attachment: lambert_jeannou.vcf
Re: How to run a command as root when I shutdown system automatically ?
On Tue, Apr 5, 2011 at 1:41 AM, Kumar Appaiah a.ku...@alumni.iitm.ac.in wrote: On Tue, Apr 05, 2011 at 11:57:31AM +0800, waterloo wrote: How to run a command as root when I shutdown system automatically ? I use Debian 6 amd64. Searching online led me to this: http://synapse.wordpress.com/2007/03/24/run-a-script-on-startup-shutdown-in-linux/ HTH. Kumar Off the top of my head (and requires debugging) #!/usr/bin/env (ba)sh # (your choice of bash or sh) execute-your-cmd-here shutdown -r now # swap -r for -h if you wish to halt instead of reboot inversely you can 'man (or info) bash' and learn how to use case so you can pass switches to your script ... i.e. /root/bin/your-shutdown-script -r or /root/bin/your-shutdown-script -h If given enough inclination, I might be able to write something in python (albeit it crude and rudimentary but it should get the job done) -- Did you know... If you play a Windows 2000 CD backwards, you hear satanic messages, but what's worse is when you play it forward ...it installs Windows 2000 -- Alfred Perlstein on chat at freebsd.org
Re: How to run a command as root when I shutdown system automatically ?
On Tue, Apr 05, 2011 at 11:57:31AM +0800, waterloo wrote: How to run a command as root when I shutdown system automatically ? I use Debian 6 amd64. Make it an init script that is only called in runmodes 0 (for shutdown) and 6 (for reboot)? I think the proper way to do this would be to set Default-Start to Default-Start: 0 6 in the header. signature.asc Description: Digital signature
How to run a command as root when I shutdown system automatically ?
How to run a command as root when I shutdown system automatically ? I use Debian 6 amd64.
Re: How to run a command as root when I shutdown system automatically ?
w == waterloo waterloo2...@gmail.com writes: w How to run a command as root when I shutdown system automatically ? w I use Debian 6 amd64. make a /root/bin/myshutdown script and run that instead perhaps. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87zko5l2ym@jidanni.org
Re: How to run a command as root when I shutdown system automatically ?
On Tue, Apr 05, 2011 at 11:57:31AM +0800, waterloo wrote: How to run a command as root when I shutdown system automatically ? I use Debian 6 amd64. Searching online led me to this: http://synapse.wordpress.com/2007/03/24/run-a-script-on-startup-shutdown-in-linux/ HTH. Kumar -- The chat program is in public domain. This is not the GNU public license. If it breaks then you get to keep both pieces. -- Copyright notice for the chat program -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110405054125.ga15...@bluemoon.alumni.iitm.ac.in
Re: Prevent shutdown in Gnome
On Mon, Mar 28, 2011 at 3:29 PM, Liam O'Toole liam.p.oto...@gmail.com wrote: On 2011-03-28, Klistvud quotati...@aliceadsl.fr wrote: Dne, 28. 03. 2011 13:22:10 je Paul van der Vlis napisal(a): I would like to remove the shutdown option in the Gnome menu, it's to prevent shutdown by mistake. Is here somebody who knows how? I looked into this problem last month (following the release of squeeze) and, after much head scratching and reading of the man page for pklocalauthority (and then more head scratching), I arrived at the following alternative solution. Create a file in the directory /etc/polkit-1/localauthority/50-local.d/. Ensure that the name of the file is unique and that it ends in .pkla. To prevent shutdown and poweroff, and a stanza such as the following to the file: [consolekit] Identity=unix-user:* Action=org.freedesktop.consolekit.system.* ResultAny=no ResultInactive=no ResultActive=no To prevent suspend and hibernate, add this stanza: [upower] Identity=unix-user:* Action=org.freedesktop.upower.* ResultAny=no ResultInactive=no ResultActive=no The result will be that the relevant options are removed from the System menu in GNOME. They will still be present at the login screen, but will be ignored. Doesn't that prevent anyone from shutting down, etc without su-ing to root in a terminal and doing so there? Wouldn't ResultActive=auth_admin be better? (IIUC, you'd have to supply the root password in order to shut down, etc.) I'd add man polkit to man pklocalauthority as *interesting* reading... -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktikk2chgk1bxeoglut_e5ffio8efshknmsgcw...@mail.gmail.com
Re: Prevent shutdown in Gnome
On 2011-03-29, Tom H tomh0...@gmail.com wrote: On Mon, Mar 28, 2011 at 3:29 PM, Liam O'Toole liam.p.oto...@gmail.com wrote: On 2011-03-28, Klistvud quotati...@aliceadsl.fr wrote: Dne, 28. 03. 2011 13:22:10 je Paul van der Vlis napisal(a): I would like to remove the shutdown option in the Gnome menu, it's to prevent shutdown by mistake. Is here somebody who knows how? I looked into this problem last month (following the release of squeeze) and, after much head scratching and reading of the man page for pklocalauthority (and then more head scratching), I arrived at the following alternative solution. Create a file in the directory /etc/polkit-1/localauthority/50-local.d/. Ensure that the name of the file is unique and that it ends in .pkla. To prevent shutdown and poweroff, and a stanza such as the following to the file: [consolekit] Identity=unix-user:* Action=org.freedesktop.consolekit.system.* ResultAny=no ResultInactive=no ResultActive=no To prevent suspend and hibernate, add this stanza: [upower] Identity=unix-user:* Action=org.freedesktop.upower.* ResultAny=no ResultInactive=no ResultActive=no The result will be that the relevant options are removed from the System menu in GNOME. They will still be present at the login screen, but will be ignored. Doesn't that prevent anyone from shutting down, etc without su-ing to root in a terminal and doing so there? Yes. My intention is to allow shutdown only by means of /sbin/poweroff and friends. Wouldn't ResultActive=auth_admin be better? (IIUC, you'd have to supply the root password in order to shut down, etc.) Better if that is the desired behaviour :-) I'd add man polkit to man pklocalauthority as *interesting* reading... -- Liam O'Toole Cork, Ireland -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/slrnip36c6.20h.liam.p.otoole@dipsy.tubbynet
Re: Prevent shutdown in Gnome
On Tue, Mar 29, 2011 at 4:34 AM, Liam O'Toole liam.p.oto...@gmail.com wrote: On 2011-03-29, Tom H tomh0...@gmail.com wrote: Wouldn't ResultActive=auth_admin be better? (IIUC, you'd have to supply the root password in order to shut down, etc.) Better if that is the desired behaviour :-) OK. I was thinking simpler for admin. :) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/AANLkTi=918otjylsu1pu1xyeowjroeyhqk-+s5qb0...@mail.gmail.com
