Re: Sound loses my analog speakers after suspend, and power settings don't affect monitor poweroff

On 8/12/23 01:05, Marco wrote: sudo dmesg | grep snd So I did that, and whether or not my analog audio was recognized, the output was: [    4.199233] snd_pci_acp6x :66:00.5: enabling device ( -> 0002) [    4.241643] snd_hda_intel :66:00.1: enabling device ( -> 0002) [    4.2

Re: Sound loses my analog speakers after suspend, and power settings don't affect monitor poweroff

Now run sudo dmesg | grep snd to see if any error in the kernel module occurs.

Re: Sound loses my analog speakers after suspend, and power settings don't affect monitor poweroff

On 8/10/23 02:54, Marco wrote: Am 09.08.2023 schrieb Carl Fink : I suspended my system from the System menu Monday night. When I woke it up Tuesday morning, sound was coming from the HDMI monitor. The Sound Settings didn't know about any other sound system. This sounds like a driver problem wi

Re: Sound loses my analog speakers after suspend, and power settings don't affect monitor poweroff

Am 09.08.2023 schrieb Carl Fink : > I suspended my system from the System menu Monday night. When I woke > it up Tuesday morning, sound was coming from the HDMI monitor. The > Sound Settings didn't know about any other sound system. This sounds like a driver problem with the soundcard. HDMI is re

Sound loses my analog speakers after suspend, and power settings don't affect monitor poweroff

Hi, I recently installed Debian Bookworm using the Mate environment. I noticed that no matter what power settings I choose, the monitors never power off. The screensaver can lock the screen, but it then just stays on for many hours. I have external analog speakers that I use, and also terrib

Re: Re: I cannot shutdown/poweroff after a HW upgrade - kernel gets stuck.

On Sun, Mar 26, 2023 at 11:33 PM Ram Ramesh wrote: > Hi Ramesh, > > this might help. The bug is fixed with kernel 6.0.2-1 > > https://groups.google.com/g/linux.debian.bugs.dist/c/p-sgJiTR00A?pli=1 > > All the best to you > Eike > > Elke, > > Thanks. v6.1 is available on bullseye-backports. I ins

Re: Re: I cannot shutdown/poweroff after a HW upgrade - kernel gets stuck.

Hi Ramesh, this might help. The bug is fixed with kernel 6.0.2-1 https://groups.google.com/g/linux.debian.bugs.dist/c/p-sgJiTR00A?pli=1 All the best to you Eike Elke, Thanks. v6.1 is available on bullseye-backports. I installed it and the trouble is gone now. BTW, does non-free firmware t

Re: I cannot shutdown/poweroff after a HW upgrade - kernel gets stuck.

On Sonntag, 26. März 2023 18:08:15 -04 Ram Ramesh wrote: > I wanted to upgrade my server from 10 year old HW to something newer. > THis server runs debian bullseye with v5.19 kernel from backports. [snip] > > The only trouble I have is that it refuses to > reboot/shutdown/poweroff

I cannot shutdown/poweroff after a HW upgrade - kernel gets stuck.

my RAID disks are working. No issue as long as it runs. The only trouble I have is that it refuses to reboot/shutdown/poweroff. It seem to go through all steps and reach the end but seem to get stuck in this endless cycle complaining about some blkdev issue.  Here are the last lines printed on

Re: [SOLVED] BIOS upgrade on an Acer laptop (was: Battery drain with poweroff)

Nicolas George (12021-02-08): > Now I need to see if it fixed my problem of battery drain; I have good > hope. Thanks to everybody who pitched for help. I confirm, after 36 hours of power down, the battery had not visibly changed. Regards, -- Nicolas George signature.asc Description: PGP si

[SOLVED] BIOS upgrade on an Acer laptop (was: Battery drain with poweroff)

Nicolas George (12021-02-08): > Thanks, I never think of BIOS updates. This is the one for my exact > model, and the title looks very promising. > > Now I need a way to apply it; apparently I need some way to boot > Windows. I hope I will not need to overwrite the complete drive with the > backup

Re: Battery drain with poweroff

Alexander V. Makartsev (12021-02-08): > I think fastest and easiest way is to swap current disk with another (if it > is available of course) and install Evaluation version of Windows 10 > Enterprise. [1] Unfortunately, switching the disk is not an option. Booting from a SD card could work, but I

Re: Battery drain with poweroff

On 08.02.2021 18:04, Marko Randjelovic wrote: Hi all, On Mon, 8 Feb 2021 13:26:12 +0100 Nicolas George wrote: Now I need a way to apply it; apparently I need some way to boot Windows. I hope I will not need to overwrite the complete drive with the backup image I made. There is a program named

Re: Battery drain with poweroff

On 08.02.2021 17:26, Nicolas George wrote: Alexander V. Makartsev (12021-02-08): Probably something to do with USB-Charger feature. Acer got a BIOS update 1.09 [1] that claims to fix similar issue. I don't know what is your model exactly, so look up BIOS update for your laptop using SNID code.

Re: Battery drain with poweroff

Hi all, On Mon, 8 Feb 2021 13:26:12 +0100 Nicolas George wrote: > Now I need a way to apply it; apparently I need some way to boot > Windows. I hope I will not need to overwrite the complete drive with the > backup image I made. There is a program named 'flashrom' in Debian, but I don't know how

Re: Battery drain with poweroff

Alexander V. Makartsev (12021-02-08): > Probably something to do with USB-Charger feature. > Acer got a BIOS update 1.09 [1] that claims to fix similar issue. > I don't know what is your model exactly, so look up BIOS update for your > laptop using SNID code. > > [1] https://www.acer.com/ac/en/US/

Re: Battery drain with poweroff

happens when the computer has been powered down with poweroff or an equivalent. I have checked, and it does not happen if I power down with a long press on the power button (after halt). Therefore, it is a sign of something staying powered with the normal kernel shutdown. I have checked that wake

Battery drain with poweroff

down with poweroff or an equivalent. I have checked, and it does not happen if I power down with a long press on the power button (after halt). Therefore, it is a sign of something staying powered with the normal kernel shutdown. I have checked that wake-on-lan, wake-on-RTC-clock and similar features

Re: Executing 'systemctl poweroff' from script run by cron.

On 11/24/20 5:05 AM, Nicholas Geovanis wrote: On Tue, Nov 24, 2020, 4:58 AM Reco > wrote:         Hi. On Tue, Nov 24, 2020 at 10:05:26AM +0100, to...@tuxteam.de wrote: . > > Thanks for the gory details.

Re: Executing 'systemctl poweroff' from script run by cron.

On Tue, Nov 24, 2020 at 06:05:14AM -0600, Nicholas Geovanis wrote: [...] > It must be said: Kuhscheiß, bullshit. > > Voices said that systemd was over-engineered before it was even really > available [...] My take (if it matters at all) is that I don't like that overcomplex design (not only sys

Re: Executing 'systemctl poweroff' from script run by cron.

On Tue, Nov 24, 2020, 4:58 AM Reco wrote: > Hi. > > On Tue, Nov 24, 2020 at 10:05:26AM +0100, to...@tuxteam.de wrote: > . > > > > Thanks for the gory details. You spoilt my breakfast ;-) > > I really feel sorry for that. > But in this regard systemd is akin to many other things in lif

Re: Executing 'systemctl poweroff' from script run by cron.

on > > > requires authentication, while run from the same user terminal, it does > > > not. > > > > What "systemctl poweroff" actually does [...] > > Thanks for the gory details. You spoilt my breakfast ;-) I really feel sorry for that. But in this r

Re: Executing 'systemctl poweroff' from script run by cron.

nal, it does > > not. > > What "systemctl poweroff" actually does [...] Ugh. Thanks for the gory details. You spoilt my breakfast ;-) > It's a FreeDesktop standard, believe it or not. > A user should be allowed to reboot or poweroff the computer which they > h

Re: Executing 'systemctl poweroff' from script run by cron.

Hi. On Mon, Nov 23, 2020 at 10:55:50PM -, Juan R. de Silva wrote: > 1. Why, when the script is run by the user cron job, the execution > requires authentication, while run from the same user terminal, it does > not. What "systemctl poweroff" actually does (src/sy

Executing 'systemctl poweroff' from script run by cron.

I am running Buster after fairly deafult installation. One of my scripts executes '/usr/bin/systemctl poweroff' command. And I am having trouble executing this script from cron. 1. If run from user's CLI, the script succeeds. 2. If run from root crontab the script succeeds.

Re: Poweroff is not working on debian8.3

Hi, I had the same problem. Take a look. Often it's a video card driver. For me (on primus laptop) the problem was nouveau. Regards 2016-05-13 11:16 GMT-04:00 : > On Thu, May 12, 2016 at 03:05:01AM +, GU, Gladys wrote: > > Hi, Debian, We have a system with debian8.3, the p

Re: Poweroff is not working on debian8.3

On Thu, May 12, 2016 at 03:05:01AM +, GU, Gladys wrote: > Hi, Debian, We have a system with debian8.3, the poweroff is not working and > everytime it will be perform a restart instead. However when we use > debian8.4, it works normally. Below is the log, do you have any advice? Yes

Poweroff is not working on debian8.3

Hi, Debian, We have a system with debian8.3, the poweroff is not working and everytime it will be perform a restart instead. However when we use debian8.4, it works normally. Below is the log, do you have any advice? Stopping Permit User Sessions... Stopping Login Service

Re: reboot and poweroff fails on Zotac ZBOX Nano CI320

roblem with previous versions of BIOS. The root cause of the problem was that I set the "Boot Mode" to "Legacy Only" and "OS Selection" to "Windows 7". Instead, set it to "Windows 8.X". I saw the following problems when the OS Selection

reboot and poweroff fails on Zotac ZBOX Nano CI320

Hi all I have a new Zotac ZBOX Nano CI320. It's a mini-PC based on an Intel Celeron N2930 (Bay Trail). This has been a very problematic system. I blame my troubles on the less-than-quality Zotac (AMI) BIOS. My current problem is that the system will not reboot or poweroff correctl

Re: systemd fails to poweroff - "A stop job is running for Session 2 of user $USER"

On Fri, Aug 15, 2014 at 7:46 AM, Chris Bannister wrote: > On Thu, Aug 14, 2014 at 10:35:11AM -0400, Tom H wrote: >> >> "Stop" in "stop job" isn't an adjective, it's a noun (or an >> attributive noun) just like "office" in "office chair." > > Or it could be a verb, as in a command "Stop job!" :) >

Re: systemd fails to poweroff - "A stop job is running for Session 2 of user $USER"

On 20140814_1035-0400, Tom H wrote: > On Thu, Aug 14, 2014 at 1:04 AM, Paul E Condon > wrote: > > > > In English, both 'stop job' and 'stopped job' are an adjective > > modifying a noun. The noun in both cases is 'job'. 'stop job' is a > > noun phrase expressing a type of job, and must be some kin

Re: systemd fails to poweroff - "A stop job is running for Session 2 of user $USER"

Hi. On Sat, 16 Aug 2014 02:12:48 +1200 Chris Bannister wrote: > You mean systemd should shoulder some of the kernel's work? A database of conflicting processes is a half-measure. Moreover, an existing implementation of RDBMS older than systemd such as Postgres is surely a no-go :) You see, cu

Re: systemd fails to poweroff - "A stop job is running for Session 2 of user $USER"

On Fri, 15 Aug 2014, Jonathan de Boyne Pollard wrote: > Bonno Bloksma: > > I wonder if the people developing this are paying attention to a > > development in de Windows environment where the latest thing is that de > > service can report back that it is indeed still trying to stop and not > > just

Re: systemd fails to poweroff - "A stop job is running for Session 2 of user $USER"

On Fri, 15 Aug 2014, Erwan David wrote: > >> Right. Debian Sid. 'halt' does not poweroff with systemd. The halt/reboot/poweroff binary shipped from sysvinit source will request a direct power-off, halt or reboot to the kernel. Just give it the "-f" option. And

Re: systemd fails to poweroff - "A stop job is running for Session 2 of user $USER"

Le 12/08/2014 17:48, Michael Biebl a écrit : > Am 12.08.2014 17:16, schrieb Hugo Vanwoerkom: > >> Right. Debian Sid. 'halt' does not poweroff with systemd. > Well, yeah. halt is not supposed to power off your system. > > But that is most likely not the issue Zena

Re: systemd fails to poweroff - "A stop job is running for Session 2 of user $USER"

On Fri, Aug 15, 2014 at 09:38:14AM -0400, Steve Litt wrote: > Some processes don't work well together, and systemd can maintain a > database of such processes, perhaps in Postgres, to prevent one of > those processes from running if the other is already running, unless > the processes themselves te

Re: systemd fails to poweroff - "A stop job is running for Session 2 of user $USER"

On Fri, 15 Aug 2014 09:19:48 + Bonno Bloksma wrote: > I wonder if the people developing this are paying attention to a > development in de Windows environment where the latest thing is that > de service can report back that it is indeed still trying to stop and > not just hung and not reporti

Re: systemd fails to poweroff - "A stop job is running for Session 2 of user $USER"

On 8/15/14, Henrique de Moraes Holschuh wrote: > On Fri, 15 Aug 2014, Bonno Bloksma wrote: >> I wonder if the people developing this are paying attention to a >> development in de Windows environment where the latest thing is that de >> service can report back that it is indeed still trying to sto

Re: systemd fails to poweroff - "A stop job is running for Session 2 of user $USER"

On Fri, 15 Aug 2014, Bonno Bloksma wrote: > I wonder if the people developing this are paying attention to a > development in de Windows environment where the latest thing is that de > service can report back that it is indeed still trying to stop and not > just hung and not reporting back. Windows

Re: systemd fails to poweroff - "A stop job is running for Session 2 of user $USER"

On Thu, Aug 14, 2014 at 10:35:11AM -0400, Tom H wrote: > On Thu, Aug 14, 2014 at 1:04 AM, Paul E Condon > wrote: > > > > In English, both 'stop job' and 'stopped job' are an adjective > > modifying a noun. The noun in both cases is 'job'. 'stop job' is a > > noun phrase expressing a type of job, a

RE: systemd fails to poweroff - "A stop job is running for Session 2 of user $USER"

Hi, > > I interpret the quoted string in the Subject: header as being flawed > > use of English language. 'stop' should be 'stopped'. And, there is a > > That would definitely be clearer. > > I was interpreting it as some special systemd shutdown-ey thing which > runs around trying to stop thi

Re: Grammatisticality: systemd fails to poweroff - "A stop job is running for Session 2 of user $USER"

ra? > > At this point, mightn't it be good to change the subject, just in case > the original poster still wants to hear some more technical > information about poweroff? That would be me :) I guess I do need to be charged with comedijacking my own thread. Sorry about that. And

Grammatisticality: systemd fails to poweroff - "A stop job is running for Session 2 of user $USER"

the subject, just in case the original poster still wants to hear some more technical information about poweroff? SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.

Re: systemd fails to poweroff - "A stop job is running for Session 2 of user $USER"

On 2014-08-14, Iain M Conochie wrote: > Yet this is exactly what my 2 year old car does now. I halt at the > lights and the engine powers off. Is this a bug? Depends. > Given enough usage, a bug can become a feature. Some clever folks turn bugs into features, I reckon: http://www.usatoday.co

Re: systemd fails to poweroff - "A stop job is running for Session 2 of user $USER"

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 08/14/2014 10:35 AM, Tom H wrote: > On Thu, Aug 14, 2014 at 1:04 AM, Paul E Condon > wrote: > >> In English, both 'stop job' and 'stopped job' are an adjective >> modifying a noun. The noun in both cases is 'job'. 'stop job' is a >> noun phras

Re: systemd fails to poweroff - "A stop job is running for Session 2 of user $USER"

On 12/08/14 22:23, Lisi Reisz wrote: On Tuesday 12 August 2014 17:53:19 Martin Steigerwald wrote: But if the english meaning of the words give exact this difference, so well. In my understanding there never was much of a difference between halt and poweroff. I'm not quite clear what yo

Re: systemd fails to poweroff - "A stop job is running for Session 2 of user $USER"

On Thu, Aug 14, 2014 at 1:04 AM, Paul E Condon wrote: > > In English, both 'stop job' and 'stopped job' are an adjective > modifying a noun. The noun in both cases is 'job'. 'stop job' is a > noun phrase expressing a type of job, and must be some kind of geeky > usage. OTOH, the noun phrase 'stopp

Re: systemd fails to poweroff - "A stop job is running for Session 2 of user $USER"

Zenaan Harkness writes: > ChrisBanalGrammatistica, Grammatistica? Which language does this word belong to? Ancient Debianese, possibly pre-Vax era? -- /\ ___Ubuntu: ancient /___/\_|_|\_|__|___Gian Uberto Lauri_ African word //-

Re: systemd fails to poweroff - "A stop job is running for Session 2 of user $USER"

On 8/14/14, Darac Marjal wrote: > On Thu, Aug 14, 2014 at 10:03:31PM +1000, Zenaan Harkness wrote: >> On 8/14/14, Paul E Condon wrote: >> > I should stop. I really have very little firm knowledge of systemd, >> > just opinions that make sense to me. (tm) >> >> That's "TM" for YOU son! It's formal

Re: systemd fails to poweroff - "A stop job is running for Session 2 of user $USER"

On Thu, Aug 14, 2014 at 10:03:31PM +1000, Zenaan Harkness wrote: > On 8/14/14, Paul E Condon wrote: > > I should stop. I really have very little firm knowledge of systemd, > > just opinions that make sense to me. (tm) > > That's "TM" for YOU son! It's formal english thank you very much. and > "(t

Re: systemd fails to poweroff - "A stop job is running for Session 2 of user $USER"

On 8/14/14, Paul E Condon wrote: > I should stop. I really have very little firm knowledge of systemd, > just opinions that make sense to me. (tm) That's "TM" for YOU son! It's formal english thank you very much. and "(tm)" is a very sloppy rendition!! I don't know that we can tolerate this level

Re: systemd fails to poweroff - "A stop job is running for Session 2 of user $USER"

On 20140813_1033+0100, Darac Marjal wrote: > On Wed, Aug 13, 2014 at 11:15:22AM +1000, Zenaan Harkness wrote: > > On 8/13/14, Paul E Condon wrote: > > > I interpret the quoted string in the Subject: header as being flawed > > > use of English language. 'stop' should be 'stopped'. And, there is a >

Re: systemd fails to poweroff - "A stop job is running for Session 2 of user $USER"

On Wed, Aug 13, 2014 at 11:15:22AM +1000, Zenaan Harkness wrote: > On 8/13/14, Paul E Condon wrote: > > I interpret the quoted string in the Subject: header as being flawed > > use of English language. 'stop' should be 'stopped'. And, there is a > > That would definitely be clearer. > > I was in

Re: systemd fails to poweroff - "A stop job is running for Session 2 of user $USER"

On Tue, Aug 12, 2014 at 2:51 PM, Paul E Condon wrote: > > I interpret the quoted string in the Subject: header as being flawed > use of English language. 'stop' should be 'stopped'. And, there is a > bug in the script that fails to evaluate the variable USER and > therefore fails to print the name

Re: systemd fails to poweroff - "A stop job is running for Session 2 of user $USER"

here? I'm not sure on what a systemd "session" is. I know Ctrl-Alt-2 to go to console 2, but that was just blank. > Does the message really keep the system from executing poweroff? Or, > does it just introduce a delay long enough for the user who is > requesting the power

Re: systemd fails to poweroff - "A stop job is running for Session 2 of user $USER"

starting this thread: 0) apt-get dist-upgrade 1) Reboot, then log in at console, then sudo poweroff. This 'worked'. 2) Reboot, console log in, then "startx" - actually this function 'se' I put into my env, pursuant to help from helpful people on this list a while ba

Re: systemd fails to poweroff - "A stop job is running for Session 2 of user $USER"

On 8/13/14, Tom H wrote: > On Tue, Aug 12, 2014 at 10:50 AM, Zenaan Harkness wrote: >> >> Debian sid >> >> systemd currently fails to poweroff for me >> >> XFCE (appears to) exit, the mouse point shows >> for a while, then the kernel/ shutdown log a

Re: systemd fails to poweroff - "A stop job is running for Session 2 of user $USER"

On Tuesday 12 August 2014 17:53:19 Martin Steigerwald wrote: > But if the english meaning of the words give > exact this difference, so well. In my understanding there never was much of > a difference between halt and poweroff. I'm not quite clear what you are saying, but if you a

[OT] on wording of computer messages [was: Re: systemd fails to poweroff - "A stop job is running for Session 2 of user $USER"]

On Ma, 12 aug 14, 12:51:12, Paul E Condon wrote: > I interpret the quoted string in the Subject: header as being flawed > use of English language. 'stop' should be 'stopped'. And, there is a ... > In a better formulated message, there should be a comma ',' between > 'user' and '$USER'. Thus if the

Re: systemd fails to poweroff - "A stop job is running for Session 2 of user $USER"

b in Session 2. Did OP attempted to connect to Session 2 and terminate the job there? Does the message really keep the system from executing poweroff? Or, does it just introduce a delay long enough for the user who is requesting the poweroff to reconsider and abort his request? What did the OP

Re: systemd fails to poweroff - "A stop job is running for Session 2 of user $USER"

On Tue, Aug 12, 2014 at 10:50 AM, Zenaan Harkness wrote: > > Debian sid > > systemd currently fails to poweroff for me > > XFCE (appears to) exit, the mouse point shows > for a while, then the kernel/ shutdown log appears. > > The last message is: > "A stop job

Re: systemd fails to poweroff - "A stop job is running for Session 2 of user $USER"

Am Dienstag, 12. August 2014, 17:48:10 schrieb Michael Biebl: > Am 12.08.2014 17:16, schrieb Hugo Vanwoerkom: > > Right. Debian Sid. 'halt' does not poweroff with systemd. > > Well, yeah. halt is not supposed to power off your system. Interestingly in the last te

Re: systemd fails to poweroff - "A stop job is running for Session 2 of user $USER"

On Tue, Aug 12, 2014 at 5:16 PM, Hugo Vanwoerkom wrote: > Zenaan Harkness wrote: >> >> Debian sid >> >> systemd currently fails to poweroff for me >> >> XFCE (appears to) exit, the mouse point shows >> for a while, then the kernel/ shutdown log appea

Re: systemd fails to poweroff - "A stop job is running for Session 2 of user $USER"

On Tue, Aug 12, 2014 at 10:16:27AM -0500, Hugo Vanwoerkom wrote: > Zenaan Harkness wrote: > >Debian sid > > > >systemd currently fails to poweroff for me > > > >XFCE (appears to) exit, the mouse point shows > >for a while, then the kernel/ shutdown log app

Re: systemd fails to poweroff - "A stop job is running for Session 2 of user $USER"

Am 12.08.2014 17:16, schrieb Hugo Vanwoerkom: > Right. Debian Sid. 'halt' does not poweroff with systemd. Well, yeah. halt is not supposed to power off your system. But that is most likely not the issue Zenaan is having -- Why is it that all of the instruments seeking intelligen

Re: systemd fails to poweroff - "A stop job is running for Session 2 of user $USER"

On Wed, 13 Aug 2014 00:50:31 +1000 Zenaan Harkness wrote: > Red asterisks (up to 3) appear to oscillate at left > edge in an ascii "wait for me" animation. You're a lucky guy: I don't have even one asterisk (only a white underscore and a blinking cursor - on a laptop). But I'm not that sure it

Re: systemd fails to poweroff - "A stop job is running for Session 2 of user $USER"

Zenaan Harkness wrote: Debian sid systemd currently fails to poweroff for me XFCE (appears to) exit, the mouse point shows for a while, then the kernel/ shutdown log appears. The last message is: "A stop job is running for Session 2 of user me" Red asterisks (up to 3) appear to os

Re: systemd fails to poweroff - "A stop job is running for Session 2 of user $USER"

Am 12.08.2014 16:50, schrieb Zenaan Harkness: > Debian sid > > systemd currently fails to poweroff for me > > XFCE (appears to) exit, the mouse point shows > for a while, then the kernel/ shutdown log appears. > > The last message is: > "A stop job is running fo

systemd fails to poweroff - "A stop job is running for Session 2 of user $USER"

Debian sid systemd currently fails to poweroff for me XFCE (appears to) exit, the mouse point shows for a while, then the kernel/ shutdown log appears. The last message is: "A stop job is running for Session 2 of user me" Red asterisks (up to 3) appear to oscillate at left edge i

Cannot suspend, even poweroff system

Hi List, The other day, I found my debian cannot suspend or poweroff. I use pm-suspend on my desktop. By looking up pm-suspend.log, I saw it does suspend the system, but then immediately wake up. The same thing happens when I issue "s2ram". pm-utils on my desktop: 1.4.1-13

Re: System will no poweroff, noisy boot.

(Apologies for the lack of an original message ID, I'm subscribed to the digest.) > Sometimes it helps, to reinstall the kernel again. Also reinstalling grub > might help, too. Hans: thank you for the tip. Sadly I don't know what happened, but the following commands successfully elided the noisy

Re: System will no poweroff, noisy boot.

On Sun, Jul 29, 2012 at 12:58:31PM +0100, Bernado Da Vinci wrote: > A related problem is horrifically noisy messages from kernel at boot time. You might post a sample of those messages. > At a bit of loss here as to what to try next! Post the relevant parts of, say, syslog? -- Carl Fink

Re: System will no poweroff, noisy boot.

Am Sonntag, 29. Juli 2012 schrieb Bernado Da Vinci: > I'm running kernel `3.2.0-3-amd64`on Wheezy. I use a ThinkPad T420. > > My first problem is that when I request my laptop to shutdown or reboot, it > gets to the final [info] Will now halt. but then just hangs. I sometimes > get messages from o

System will no poweroff, noisy boot.

I'm running kernel `3.2.0-3-amd64`on Wheezy. I use a ThinkPad T420. My first problem is that when I request my laptop to shutdown or reboot, it gets to the final [info] Will now halt. but then just hangs. I sometimes get messages from other kernel modules such as echi_hcd, sd, hda_intel and thinkp

Re: problematic poweroff on shutdown

On 2012-01-03, Bob Proulx 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

Re: problematic poweroff on shutdown

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 u

Re: problematic poweroff on shutdown

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 mach

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

Re: problematic poweroff on shutdown

On 2012-01-03, 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

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 > pla

Re: problematic poweroff on shutdown [Fwd:]

On 2012-01-03, Don Juan 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 period

Re: problematic poweroff on shutdown

On 2012-01-02, Ashton Fagg 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

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 To: Curt 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

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. Wh

problematic poweroff on shutdown

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? Cont

Re: Debian wheezy：machine auto booted after poweroff

On Sun, 26 Jun 2011 16:37:19 +0800, xuyuanwei wrote: > 在 2011-06-24五的 00:02 +0800，yuanwei xu写道： >> 2011/6/23 yuanwei xu : >> > 2011/6/23 Camaleón : (...) >> >> Hum... so at init 1 there is no "acpid" service running on >> >> background. This can be relevant for your issue when powering off >> >>

Re: Debian wheezy：machine auto booted after poweroff

s for your reply. Hope there will be a final > >>>>> solution soon. > >>>> > >>>> It worked?? Hum... I didn't expect it did. > >>> > >>> At least, it had not auto booted in one night after "#init 1" and > >>> &qu

Re: Debian wheezy：machine auto booted after poweroff

On Fri, Jun 24, 2011 at 12:02:54AM +0800, yuanwei xu wrote: > 2011/6/23 yuanwei xu : > > 2011/6/23 Camaleón : > >> On Thu, 23 Jun 2011 22:07:29 +0800, yuanwei xu wrote: > >> > This could be something to investigate further. At a first glance I can > think in acpi being the culprit... is t

Re: Debian wheezy：machine auto booted after poweroff

gt;> >>>> It worked?? Hum... I didn't expect it did. >>> >>> At least, it had not auto booted in one night after "#init 1" and >>> "#poweroff". >> >> Good. >> >>>> This could be something to investigate f

Re: Debian wheezy：machine auto booted after poweroff

ct it did. >> >> At least, it had not auto booted in one night after "#init 1" and >> "#poweroff". > > Good. > >>> This could be something to investigate further. At a first glance I can >>> think in acpi being the culprit... is t

Re: Debian wheezy：machine auto booted after poweroff

auto booted in one night after "#init 1" and > "#poweroff". Good. >> This could be something to investigate further. At a first glance I can >> think in acpi being the culprit... is the "acpid" service loaded in >> single-user mode? > > In /etc/rc2.d

Re: Debian wheezy：machine auto booted after poweroff

2011/6/22 Camaleón : > On Wed, 22 Jun 2011 22:43:06 +0800, yuanwei xu wrote: > >> 2011/6/19 Camaleón : >>> On Sun, 19 Jun 2011 15:13:37 +0800, yuanwei xu wrote: >>> >>>> After upgrade from Squeeze to Wheezy, my notebook always auto booted >>&

Re: Debian wheezy：machine auto booted after poweroff

On Wed, 22 Jun 2011 22:43:06 +0800, yuanwei xu wrote: > 2011/6/19 Camaleón : >> On Sun, 19 Jun 2011 15:13:37 +0800, yuanwei xu wrote: >> >>> After upgrade from Squeeze to Wheezy, my notebook always auto booted >>> after I shutdowned it using #poweroff in gnome

Re: Debian wheezy：machine auto booted after poweroff

2011/6/19 Camaleón : > On Sun, 19 Jun 2011 15:13:37 +0800, yuanwei xu wrote: > >> After upgrade from Squeeze to Wheezy, my notebook always auto booted >> after I shutdowned it using #poweroff in gnome terminal. Sometimes, it >> auto booted in 1 minutes, sometimes in 3 m

Re: Debian wheezy：machine auto booted after poweroff

On Sun, 19 Jun 2011 15:13:37 +0800, yuanwei xu wrote: > After upgrade from Squeeze to Wheezy, my notebook always auto booted > after I shutdowned it using #poweroff in gnome terminal. Sometimes, it > auto booted in 1 minutes, sometimes in 3 minutes after poweroff. I have > to use

Re: Debian wheezy machine auto booted after poweroff - Re: debian-user-digest Digest V2011 #1177

On Sun, 2011-06-19 at 13:52 +0200, Ralf Mardorf wrote: > There's an option that enables to 'boot' a new kernel without rebooting > completely, you only need to re-edit a line in a script from true to > false or vv. I can't remember that script. > > I had this issue with Ubuntu Studio or Debian thi

Debian wheezy machine auto booted after poweroff - Re: debian-user-digest Digest V2011 #1177

There's an option that enables to 'boot' a new kernel without rebooting completely, you only need to re-edit a line in a script from true to false or vv. I can't remember that script. I had this issue with Ubuntu Studio or Debian this or last month, but can't find the solution that is somewhere in

Debian wheezy：machine auto booted after poweroff

Hi, After upgrade from Squeeze to Wheezy, my notebook always auto booted after I shutdowned it using #poweroff in gnome terminal. Sometimes, it auto booted in 1 minutes, sometimes in 3 minutes after poweroff. I have to use #poweroff to shutdown it once more, and it wouldn't auto boot anymo

Re: Where is the display poweroff standby set?

On Sat, Feb 12, 2011 at 12:49:36PM +0200, Andrei Popescu wrote: > On Sb, 12 feb 11, 00:17:12, Roger Leigh wrote: > > > > Any ideas on what I'm missing here? There must be some other > > setting I'm overlooking, only I haven't come across it in 14 > > years of using Debian! > > ,[ /etc/X11/xo

  1   2   >