Re: package name just before power off

[Greg Wooledge]

On Thu, Mar 23, 2023 at 10:50:48AM -0400, John wrote:
> I get an error message which is absolutely the last thing before poweroff 
> that is NOT ever reported in kern.log nor by dmesg. 
> 
> It reads like this:
> 48.255417 DMAR: DRHD: handling fault status reg 2
> 48.255457 DMR: [DMA Read] request device [00:17.0] PASID  fault addr 
> aboe9000 [fault reason 06] PTE read access is not set
> 48.27 reboot: Power down
> 
> What pack age would this be in so I can file a bug?

Those look like kernel messages.  A Google search leads me to
 which reports a
similar (but worse) experience.  You can start there, or try your own
luck with Google searches.

If you're experiencing an actual problem, you might try contacting
the Linux kernel mailing list.  If it's just a few lines of text with
no other symptoms, personally I'd just ignore it.

Re: package name just before power off

[The Wanderer]

On 2023-03-23 at 10:50, John wrote:

> I get an error message which is absolutely the last thing before
> poweroff that is NOT ever reported in kern.log nor by dmesg.

Typically, the very last messages from before power-off would be
expected to come from the kernel, as it should be the last thing still
running.

> It reads like this:
> 48.255417 DMAR: DRHD: handling fault status reg 2
> 48.255457 DMR: [DMA Read] request device [00:17.0] PASID  fault addr 
> aboe9000 [fault reason 06] PTE read access is not set
> 48.27 reboot: Power down
> 
> What pack age would this be in so I can file a bug?

Googling for parts of these messages find multiple bug reports on
kernel.org (I've seen at least one from 2016 and one from 2019, both
apparently about the relevant messages appearing in floods), so that
seems to confirm that these messages are coming from there.

It will probably be relevant what kernel you're running.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

package name just before power off

[John]

I get an error message which is absolutely the last thing before poweroff that 
is NOT ever reported in kern.log nor by dmesg. 

It reads like this:
48.255417 DMAR: DRHD: handling fault status reg 2
48.255457 DMR: [DMA Read] request device [00:17.0] PASID  fault addr 
aboe9000 [fault reason 06] PTE read access is not set
48.27 reboot: Power down

What pack age would this be in so I can file a bug?

Note, similar problems have been reported but this is unique:
1) It only occurs at power off but not on reboot. No other handling fault 
errors reported by dmesg
2) Nothing is shown in any kern.log files probably because it is too late to 
write anything

John

Re: Machine won't power off after upgrade to bullseye.

[Tim Woodall]

On Tue, 23 Nov 2021, Tim Woodall wrote:


I have an old machine that I've just upgraded to bullseye. Now that it's
upgraded it does not power off when I do halt -p.

I see the following error: (copied so hopefully no typos)

Will now halt.
[  183.942475] ACPI BIOS Error (bug): Could not resolve symbol 
[\_SB.PCI0.LPCB.TPM.PTS], AE_NOT_FOUND (20200925/psargs-330)
[  183.942946] ACPI Error: Aborting method \_PTS due to previous error 
(AE_NOT_FOUND) (20200925/psparse-529)

[  183.943586] reboot: Power down

I found this old bug:

https://bugzilla.kernel.org/show_bug.cgi?id=199117

While this may well be a bios bug, I've never had this problem before.
Now I've got it on two different (older machines)

I'll try downgrading the kernel back to 4.19 but has anyone else seen
anything like this?

Tim.




Interestingly the other machine doesn't print any ACPI errors, it just
doesn't turn off.

But I've discovered that it's something to do with xen, not the kernel.
Booting exactly the same kernel outside of xen does power off
successfully with no errors.

And booting with the 4.19 kernel from buster doesn't turn off on the
4.14 hypervisor.

I'm not exactly sure how to roll back to the 4.11 hypervisor. Just
dpkg -i xen-hypervisor-4.11-amd64_4.11.4+107-gef32c7afa2-1_amd64.deb
is enough to get it to boot (although it complains about xen-utils being
the wrong version) and then halt -p does power off

(As expected poweroff behaves identically to halt -p)

And I find this bug has already been opened.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994899

Unfortunately, the bug isn't very easy to read but I think there might
already be a fix in the pipeline. If not it looks like I can build a
patched hypervisor that doesn't have this problem. I'll investigate
further another day.

Fortunately for me I've been using these machines to test a poor man's
IPMI that I've been developing using a Pi4. I can power them on and off
and watch the boot and shutdown sequence remotely and even tweak the
bios settings. One of the reasons for using these two old machines is
that one only has VGA output while the other has HDMI and also one of
them the normal keyboard gadget cannot control the bios - not sure why -
so I developed an ffs driver instead. So I had them setup specifically
for testing rebooting and power-cycling. Pure luck that I chose to
upgrade them to bullseye and found this issue there.

Tim.

Re: Machine won't power off after upgrade to bullseye.

[Brian]

On Tue 23 Nov 2021 at 18:56:23 +, Tim Woodall wrote:

> On Tue, 23 Nov 2021, Brian wrote:
> 
> > On Tue 23 Nov 2021 at 18:02:03 +, Tim Woodall wrote:
> > 
> > > I have an old machine that I've just upgraded to bullseye. Now that it's
> > > upgraded it does not power off when I do halt -p.
> > 
> > What happens with 'poweroff'?
> > 
> 
> What is the difference between poweroff and halt -p? I thought calling
> halt as poweroff just defaulted the -p. halt -p is one less keystroke
> :-)

The differnce is maybe immaterial. You tried the command. It didn't
work, as Tixy explained and forecast? Now you are into the nitty-gritty.

-- 
Brian.

Re: Machine won't power off after upgrade to bullseye.

[Tim Woodall]

On Tue, 23 Nov 2021, Brian wrote:


On Tue 23 Nov 2021 at 18:02:03 +, Tim Woodall wrote:


I have an old machine that I've just upgraded to bullseye. Now that it's
upgraded it does not power off when I do halt -p.


What happens with 'poweroff'?



What is the difference between poweroff and halt -p? I thought calling
halt as poweroff just defaulted the -p. halt -p is one less keystroke
:-)

Re: Machine won't power off after upgrade to bullseye.

[Tixy]

On Tue, 2021-11-23 at 18:37 +, Brian wrote:
> On Tue 23 Nov 2021 at 18:02:03 +, Tim Woodall wrote:
> 
> > I have an old machine that I've just upgraded to bullseye. Now that it's
> > upgraded it does not power off when I do halt -p.
> 
> What happens with 'poweroff'?
> 

Probably the same as with 'halt -p' because 'halt', 'poweroff' and
'reboot' are symlinks to the same program and according to the man page
the -p option means "Power-off the machine, regardless of which one of
the three commands is invoked".

-- 
Tixy

Re: Machine won't power off after upgrade to bullseye.

[Brian]

On Tue 23 Nov 2021 at 18:02:03 +, Tim Woodall wrote:

> I have an old machine that I've just upgraded to bullseye. Now that it's
> upgraded it does not power off when I do halt -p.

What happens with 'poweroff'?

-- 
Brian.

Machine won't power off after upgrade to bullseye.

[Tim Woodall]

I have an old machine that I've just upgraded to bullseye. Now that it's
upgraded it does not power off when I do halt -p.

I see the following error: (copied so hopefully no typos)

Will now halt.
[  183.942475] ACPI BIOS Error (bug): Could not resolve symbol 
[\_SB.PCI0.LPCB.TPM.PTS], AE_NOT_FOUND (20200925/psargs-330)
[  183.942946] ACPI Error: Aborting method \_PTS due to previous error 
(AE_NOT_FOUND) (20200925/psparse-529)
[  183.943586] reboot: Power down

I found this old bug:

https://bugzilla.kernel.org/show_bug.cgi?id=199117

While this may well be a bios bug, I've never had this problem before.
Now I've got it on two different (older machines)

I'll try downgrading the kernel back to 4.19 but has anyone else seen
anything like this?

Tim.

Re: After upgraded to Buster the Energy Settings is problematic: get blank scree on laptop and the power off is only applicable

[Csanyi Pal]

2019. 08. 01. 12:44 keltezéssel, Shahryar Afifi írta:

Do you have the package xfce4-goodies installed?
xfce has its own power management.

On Wed, 2019-07-31 at 21:38 +0200, Csanyi Pal wrote:

Hello,

I just upgraded to Debian Buster from Stretch.

I am running it on an Acer Aspire V3-571 laptop.

I am using XFCE Desktop Environment ( in Stretch I used it also ).

In the Energy ... Settings I did set up in Stretch that that after 3
minutes of inactivity the screen comes blank and it works.

But, from there I can't wake up the laptop, whatever I am doing:
moving
or clicking with the mice, hit Shift, Esc, Enter, Cursor Down or Up,
these does not help to get back to my Desktop.

The only way to get it back is to hold down the Power button until it
is
shut down, then hit again Power button to start the laptop.

I purge the apmd package, but that does not helped me out.

How can I solve this problem?

Meanwhile I switch off in the Energy ... Settings that that the
Screen
come blank after some inactivity.





Yes, I have installed xfce4-goodies package.

--
Best, Pali

Re: After upgraded to Buster the Energy Settings is problematic: get blank scree on laptop and the power off is only applicable

[Shahryar Afifi]

Do you have the package xfce4-goodies installed?
xfce has its own power management. 

On Wed, 2019-07-31 at 21:38 +0200, Csanyi Pal wrote:
> Hello,
> 
> I just upgraded to Debian Buster from Stretch.
> 
> I am running it on an Acer Aspire V3-571 laptop.
> 
> I am using XFCE Desktop Environment ( in Stretch I used it also ).
> 
> In the Energy ... Settings I did set up in Stretch that that after 3 
> minutes of inactivity the screen comes blank and it works.
> 
> But, from there I can't wake up the laptop, whatever I am doing:
> moving 
> or clicking with the mice, hit Shift, Esc, Enter, Cursor Down or Up, 
> these does not help to get back to my Desktop.
> 
> The only way to get it back is to hold down the Power button until it
> is 
> shut down, then hit again Power button to start the laptop.
> 
> I purge the apmd package, but that does not helped me out.
> 
> How can I solve this problem?
> 
> Meanwhile I switch off in the Energy ... Settings that that the
> Screen 
> come blank after some inactivity.
> 

Re: After upgraded to Buster the Energy Settings is problematic: get blank screen on laptop and the power off button is the only way

[Csanyi Pal]

2019. 08. 01. 9:14 keltezéssel, elvis írta:

I just upgraded to Debian Buster from Stretch.


I am running it on an Acer Aspire V3-571 laptop.

I am using XFCE Desktop Environment ( in Stretch I used it also ).

In the Energy ... Settings I did set up in Stretch that that after 3 
minutes of inactivity the screen comes blank and it works so far.


But, from there I can't wake up the laptop, whatever I am doing: 
moving or clicking with the mice, hit Shift, Esc, Enter, Cursor Down 
or Up, these does not help to get back to my Desktop.


The only way to get it back is to hold down the Power button until it 
is shutted down, then hit again Power button to start the laptop.


I purge the apmd package, but that does not helped me out.

How can I solve this problem?



I had a similar problem on a different distro and I fixed it by just 
upping the brightness when it was asleep. Fn f6 on a Thinkpad to 
increase brightness.



Instead of sleeping or hibernating sometimes the machine was just 
turning the screen brightness down...


I tried the Fn F6 too, but on my Debian Buster system this key 
combination is for show and switch between monitors.


Here the Fn Left decrease, Fn Right increase the screen brightness but 
that does not work either, probably because my external monitor - which 
is LG Flatron W2252TQ does not have such capability.


So, when my screen goes blank, I can't use Fn plus some keys to get my 
Desktop back.


But I just found the way: Ctrl+Alt+F1 to go to the Virtual Terminal, and 
from there Alt+F7 get me back to my Desktop.


But, is this the solution?

Before, on Stretch I just hit a Shift key and get back my Desktop out 
there. But here, on Buster, this does not work. Why?


Moreover, I just purge the sleepd package, but install again all acpi 
packages. So I use Ctrl+Alt+F1 and then Alt F7 to get back my Desktop.


Is there a better way to do it?

--
Best, Pali

Re: After upgraded to Buster the Energy Settings is problematic: get blank screen on laptop and the power off button is the only way

[elvis]

I just upgraded to Debian Buster from Stretch.


I am running it on an Acer Aspire V3-571 laptop.

I am using XFCE Desktop Environment ( in Stretch I used it also ).

In the Energy ... Settings I did set up in Stretch that that after 3 
minutes of inactivity the screen comes blank and it works so far.


But, from there I can't wake up the laptop, whatever I am doing: 
moving or clicking with the mice, hit Shift, Esc, Enter, Cursor Down 
or Up, these does not help to get back to my Desktop.


The only way to get it back is to hold down the Power button until it 
is shutted down, then hit again Power button to start the laptop.


I purge the apmd package, but that does not helped me out.

How can I solve this problem?



I had a similar problem on a different distro and I fixed it by just 
upping the brightness when it was asleep. Fn f6 on a Thinkpad to 
increase brightness.



Instead of sleeping or hibernating sometimes the machine was just 
turning the screen brightness down...






Meanwhile I switch off in the Energy ... Settings that that the Screen 
come blank after some inactivity, but that does not help either.



--
I eat where I want to eat, not because I've been given a discount there.

After upgraded to Buster the Energy Settings is problematic: get blank screen on laptop and the power off button is the only way

[Csanyi Pal]

Hello,

I just upgraded to Debian Buster from Stretch.

I am running it on an Acer Aspire V3-571 laptop.

I am using XFCE Desktop Environment ( in Stretch I used it also ).

In the Energy ... Settings I did set up in Stretch that that after 3 
minutes of inactivity the screen comes blank and it works so far.


But, from there I can't wake up the laptop, whatever I am doing: moving 
or clicking with the mice, hit Shift, Esc, Enter, Cursor Down or Up, 
these does not help to get back to my Desktop.


The only way to get it back is to hold down the Power button until it is 
shutted down, then hit again Power button to start the laptop.


I purge the apmd package, but that does not helped me out.

How can I solve this problem?

Meanwhile I switch off in the Energy ... Settings that that the Screen 
come blank after some inactivity, but that does not help either.


--
Best, Pali

After upgraded to Buster the Energy Settings is problematic: get blank scree on laptop and the power off is only applicable

[Csanyi Pal]

Hello,

I just upgraded to Debian Buster from Stretch.

I am running it on an Acer Aspire V3-571 laptop.

I am using XFCE Desktop Environment ( in Stretch I used it also ).

In the Energy ... Settings I did set up in Stretch that that after 3 
minutes of inactivity the screen comes blank and it works.


But, from there I can't wake up the laptop, whatever I am doing: moving 
or clicking with the mice, hit Shift, Esc, Enter, Cursor Down or Up, 
these does not help to get back to my Desktop.


The only way to get it back is to hold down the Power button until it is 
shut down, then hit again Power button to start the laptop.


I purge the apmd package, but that does not helped me out.

How can I solve this problem?

Meanwhile I switch off in the Energy ... Settings that that the Screen 
come blank after some inactivity.


--
Best, Pali

Re: Not power off after shutdown in Jessie

[Miroslav Skoric]

On 06/10/2018 06:33 PM, The Wanderer wrote:


On 2018-05-31 at 02:01, Miroslav Skoric wrote:


After upgrading from Wheezy LTS to Jessie, one of my machines having 512
MB RAM, does not power off when it reached target shutdown. It seems
some old issue/bug with systemd or else. In fact, everything closes down
properly except it does not unmount the following:

/run/user/1000
/run/user/106
/var
/home
/tmp


How can you tell that these are still mounted?



Because the machine kept reporting 'failed unmount' for these above, 
something like this:


umounting /run/user/1000
failed to umount /run/user/1000
umounting /run/user/106
failed to umount /run/user/106
...
...

(Sorry I forgot the exact syntax of how the machine reported that, 
because it was last week. But it finally started to poweroff properly 
after I removed all clamav -related stuff from that machine. In fact, I 
noticed that all those clam* things still belonged to Wheezy, being in 
versions ...deb7u1 or so, after I upgraded Wheezy LTS to Jessie.)




Could it be a kernel/BIOS incompatibility? (I.e., probably something to
do with ACPI tables.)



I don't know ... I got that machine some 6-7 years ago, as a second-hand 
then. So it is probably some 10+ year old at least.




The only fix I've found for that problem, aside from reverting to the
older kernel, is to upgrade the BIOS on the affected computers. Some of
them had BIOS versions dating back to at least 2012, if not 2009;
bringing them up to the manufacturer's latest BIOS release for that
model got the new environments to shut down and reboot normally.



I see. But as I said, removing some packages returned the box to normal 
shutdown.


Furthermore, what wondered me even more is that another *older* box I 
have here (dated back to the beginning of the previous decade!), that 
runs with only 224MB RAM on Celeron 400MHz, did not experience failure 
in poweroff at all.

Re: Not power off after shutdown in Jessie

[The Wanderer]

On 2018-05-31 at 02:01, Miroslav Skoric wrote:

> After upgrading from Wheezy LTS to Jessie, one of my machines having 512 
> MB RAM, does not power off when it reached target shutdown. It seems 
> some old issue/bug with systemd or else. In fact, everything closes down 
> properly except it does not unmount the following:
> 
> /run/user/1000
> /run/user/106
> /var
> /home
> /tmp

How can you tell that these are still mounted?

> ... and hangs there forever. That did not happen in Wheezy. Any idea?

Could it be a kernel/BIOS incompatibility? (I.e., probably something to
do with ACPI tables.)

I've recently needed to experiment at work with some new versions of
what is basically a LiveCD-type environment; along with various other
updates, those new versions have an updated kernel, and I think that's
the relevant factor.

On some computer models, the new versions of that environment failed to
shut down or reboot all the way; they'd get as far (into the shutdown
messages) as the point where the screen should go blank for the reboot
or shutdown, and then hang there forever. Powering off resulted in a
clean boot next time, as if the shutdown had succeeded. On other
computer models, everything worked fine.

The only fix I've found for that problem, aside from reverting to the
older kernel, is to upgrade the BIOS on the affected computers. Some of
them had BIOS versions dating back to at least 2012, if not 2009;
bringing them up to the manufacturer's latest BIOS release for that
model got the new environments to shut down and reboot normally.

My best guess is that the newer kernel (and/or some drivers included
therein) is relying on updated expectations about what the BIOS will do
in response to a given input, and the BIOS on the affected machines
doesn't actually satisfy those expectations.

I don't know whether what you're seeing is the same behavior, but it
could be worth checking on.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: Not power off after shutdown in Jessie

[Miroslav Skoric]

On 06/04/2018 03:12 PM, Curt wrote:



I'm really too ignorant to be answering questions and should be asking some.

However I can't think of any.

Except: any clues in the logs?

Look here:

  /usr/share/doc/systemd/README.Debian.gz

under

  Debugging boot/shutdown problems
  

which explains how to create a root debug shell on VT 9 available quite
late in the shutdown process; or, failing or in lieu of that, generating a
shutdown-log.txt file instead.

Good luck.




Thank you for ideas. Well I am not an expert into debugging shutdown 
processes at all. However, systemctl in VT9 returned some "failed" units 
for boot (as well as many still "active" ones for shutdown), among which 
I saw "failed" clamd or some else service related to clamav. And since I 
really did not need any clam* things on that particular machine any 
more, I went to Synaptic manager and purged them all.


(Btw, I noticed that all those clam* things still belonged to Wheezy ... 
like deb7u1 or so, dunno whether they should had been automatically 
upgraded to some deb8u* during the distro upgrade Wheezy LTS >> Jessie.)


Whatever, the first next shutdown was successful, as well as the 
subsequent dozen ones, as well as the reboot sessions. Will keep an eye 
on that ... tnx for now.

Re: Not power off after shutdown in Jessie

[deloptes]

Miroslav Skoric wrote:

> Any idea?

yes this systemd thingie is cursed by design, so I have it pretty stable in
few devices where inevitable (phone, tablet etc) 

But everything else I install sysvinit-core and this makes it explicitly the
init process
(or add init=/lib/sysvinit/init to grub default kernel command line and
recreate initrd)

systemd is (still) not in position to handle stuff properly.

regards

Re: Not power off after shutdown in Jessie

[Miroslav Skoric]

On 05/31/2018 08:01 AM, Miroslav Skoric wrote:

After upgrading from Wheezy LTS to Jessie, one of my machines having 512 
MB RAM, does not power off when it reached target shutdown. It seems 
some old issue/bug with systemd or else. In fact, everything closes down 
properly except it does not unmount the following:


/run/user/1000
/run/user/106
/var
/home
/tmp

... and hangs there forever. That did not happen in Wheezy. Any idea?



Btw, after waiting for at least 3-4 hours for poweroff, I went to tty1 
console to try ctrl-alt-del there (because that did not work in tty7 
where the system left hanging). It did not help much there too, however 
I noticed two new lines there:


[74199.357014] systemd[1]: var.mount failed to run 'umount' task: Cannot 
allocate memory
[74199.380035] systemd[1]: home.mount failed to run 'umount' task: 
Cannot allocate memory



Any idea?

Re: Not power off after shutdown in Jessie

[Curt]

On 2018-06-03, Miroslav Skoric  wrote:
>
> I did so, and noticed just some few Gnome -related things to be active 
> for the user 106 - myself? (although I logged out from the Mate desktop 
> and not from Gnome), as well as a few items active for user 1000 i.e. 
> root (such as 'sudo su' and 'systemd-cgls').
>
> Anyway, to be sure whether any of those processes were needed to run or 
> not, I did in parallel the same test with another slower machine running 
> Jessie at only 224MB RAM (also the recent upgrade from Wheezy), but 
> which one performs proper shutdown/poweroff.
>
> You bet, at both machines exactly the same processes were listed as 
> still running for user 106 and user 1000. However, only the better one 
> box having 512 MB RAM, does not power off when reached target shutdown.
>
> Any other thing to try?
>
>

I'm really too ignorant to be answering questions and should be asking some.

However I can't think of any.

Except: any clues in the logs?  

Look here:

 /usr/share/doc/systemd/README.Debian.gz

under

 Debugging boot/shutdown problems
 

which explains how to create a root debug shell on VT 9 available quite
late in the shutdown process; or, failing or in lieu of that, generating a
shutdown-log.txt file instead.

Good luck.

Re: Not power off after shutdown in Jessie

[Miroslav Skoric]

On 05/31/2018 04:18 PM, Curt wrote:


On 2018-05-31, Miroslav Skoric  wrote:

After upgrading from Wheezy LTS to Jessie, one of my machines having 512
MB RAM, does not power off when it reached target shutdown. It seems
some old issue/bug with systemd or else. In fact, everything closes down
properly except it does not unmount the following:

/run/user/1000
/run/user/106
/var
/home
/tmp

... and hangs there forever. That did not happen in Wheezy. Any idea?




You could try logging out, I've read somewhere, switching to a console,
logging in as root (or another user entirely) and executing
'systemd-cgls' to determine what processes are still running for the
user in question (assuming for the moment your problem is related to
some program in your session being "stuck.")




I did so, and noticed just some few Gnome -related things to be active 
for the user 106 - myself? (although I logged out from the Mate desktop 
and not from Gnome), as well as a few items active for user 1000 i.e. 
root (such as 'sudo su' and 'systemd-cgls').


Anyway, to be sure whether any of those processes were needed to run or 
not, I did in parallel the same test with another slower machine running 
Jessie at only 224MB RAM (also the recent upgrade from Wheezy), but 
which one performs proper shutdown/poweroff.


You bet, at both machines exactly the same processes were listed as 
still running for user 106 and user 1000. However, only the better one 
box having 512 MB RAM, does not power off when reached target shutdown.


Any other thing to try?

Re: Not power off after shutdown in Jessie

[deloptes]

Miroslav Skoric wrote:

> That did not happen in Wheezy. Any idea?

it is not a bug, it is a feature :)

Re: Not power off after shutdown in Jessie

[Curt]

On 2018-05-31, Miroslav Skoric  wrote:
> After upgrading from Wheezy LTS to Jessie, one of my machines having 512 
> MB RAM, does not power off when it reached target shutdown. It seems 
> some old issue/bug with systemd or else. In fact, everything closes down 
> properly except it does not unmount the following:
>
> /run/user/1000
> /run/user/106
> /var
> /home
> /tmp
>
> ... and hangs there forever. That did not happen in Wheezy. Any idea?
>
>

You could try logging out, I've read somewhere, switching to a console,
logging in as root (or another user entirely) and executing
'systemd-cgls' to determine what processes are still running for the
user in question (assuming for the moment your problem is related to
some program in your session being "stuck.")

Not power off after shutdown in Jessie

[Miroslav Skoric]

After upgrading from Wheezy LTS to Jessie, one of my machines having 512 
MB RAM, does not power off when it reached target shutdown. It seems 
some old issue/bug with systemd or else. In fact, everything closes down 
properly except it does not unmount the following:


/run/user/1000
/run/user/106
/var
/home
/tmp

... and hangs there forever. That did not happen in Wheezy. Any idea?

Re: Setting up power-off icon

[Lisi Reisz]

On Thursday 01 June 2017 00:58:37 Ben Caradoc-Davies wrote:
> On 01/06/17 11:48, Lisi Reisz wrote:
> > On Thursday 01 June 2017 00:17:29 Lisi Reisz wrote:
> >> [Desktop Entry]
>
> [...]
>
> >> Icon=/usr/share/pixmaps/power-button-off_318-4.jpg
>
> [...]
>
> > I have one that is working via the desktop shortcut - but am now faced
> > with being unable to change the icon.  (Which is just a gear.)
>
> Lisi, have you tried using a PNG, with a ".png" extension?
>
> https://specifications.freedesktop.org/desktop-entry-spec/desktop-entry-spe
>c-1.0.html
> https://specifications.freedesktop.org/icon-theme-spec/icon-theme-spec-late
>st.html "The image files must be one of the types: PNG, XPM, or SVG, and the
> extension must be ".png", ".xpm", or ".svg" (lower case). The support for
> SVG files is optional. Implementations that do not support SVGs should just
> ignore any ".svg" files."
>
> Kind regards,

Thanks!!  Had just succeeded.  Now have an enormous, functioning poweroff 
icon!!

Thank you for the reply.  One icon down, three to go  (The others are just 
URLs and should be easy!  And I know now how to change the icon if I want 
to!)

Lisi

Re: Setting up power-off icon

[Ben Caradoc-Davies]

On 01/06/17 11:48, Lisi Reisz wrote:

On Thursday 01 June 2017 00:17:29 Lisi Reisz wrote:

[Desktop Entry]

[...]

Icon=/usr/share/pixmaps/power-button-off_318-4.jpg

[...]

I have one that is working via the desktop shortcut - but am now faced with
being unable to change the icon.  (Which is just a gear.)


Lisi, have you tried using a PNG, with a ".png" extension?

https://specifications.freedesktop.org/desktop-entry-spec/desktop-entry-spec-1.0.html
https://specifications.freedesktop.org/icon-theme-spec/icon-theme-spec-latest.html
"The image files must be one of the types: PNG, XPM, or SVG, and the 
extension must be ".png", ".xpm", or ".svg" (lower case). The support 
for SVG files is optional. Implementations that do not support SVGs 
should just ignore any ".svg" files."


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Re: Setting up power-off icon

[Lisi Reisz]

On Thursday 01 June 2017 00:17:29 Lisi Reisz wrote:
> I want to set up a large power-off icon on the desktop for a user with very
> poor sight.  I have found a suitable icon and am now struggling with
> setting up the icon on the desktop.
>
> Debian Jessie 8.8 with TDE 14.0.5.
>
> This is what I have so far:
>
> [Desktop Entry]
> Name=Shut_down
> Comment=Log out and power off
> Icon=/usr/share/pixmaps/power-button-off_318-4.jpg
> Exec=sudo /sbin/poweroff
> Type=Application
> Encoding=UTF-8
> Terminal=false
> Categories=None;
>
> saved in /home/$USER/Desktop/

I have one that is working via the desktop shortcut - but am now faced with 
being unable to change the icon.  (Which is just a gear.)

Lisi
>
> I get an icon (the wrong one!) on the desktop on which I can click and it
> launches the application launcher and asks for an application or URL.  If I
> delete the word sudo I get the menu opened up and get asked which
> application I want.
>
> I asked on the TDE list and was told to set up an con to execute the sudo
> command, then googled, and got the idea for this from:
> http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/gui/desk
>top-shortcuts but am now completely at sea and am probably asking the wrong
> questions.
>
> I have never been a lover of icons and am not very hot on their creation
> and use.
>
> The user got badly scammed, so I am doing this instead of just reinstalling
> Windows 7 and letting him get on with it.  If I can succeed, this will be
> much easier for him and MUCH less insecure.
>
> Lisi

I

Setting up power-off icon

[Lisi Reisz]

I want to set up a large power-off icon on the desktop for a user with very 
poor sight.  I have found a suitable icon and am now struggling with setting 
up the icon on the desktop.

Debian Jessie 8.8 with TDE 14.0.5.

This is what I have so far:

[Desktop Entry]
Name=Shut_down
Comment=Log out and power off
Icon=/usr/share/pixmaps/power-button-off_318-4.jpg
Exec=sudo /sbin/poweroff
Type=Application
Encoding=UTF-8
Terminal=false
Categories=None;

saved in /home/$USER/Desktop/

I get an icon (the wrong one!) on the desktop on which I can click and it 
launches the application launcher and asks for an application or URL.  If I 
delete the word sudo I get the menu opened up and get asked which application 
I want.

I asked on the TDE list and was told to set up an con to execute the sudo 
command, then googled, and got the idea for this from:
http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/gui/desktop-shortcuts
but am now completely at sea and am probably asking the wrong questions. 

I have never been a lover of icons and am not very hot on their creation and 
use.

The user got badly scammed, so I am doing this instead of just reinstalling 
Windows 7 and letting him get on with it.  If I can succeed, this will be 
much easier for him and MUCH less insecure.

Lisi

Re: shutdown fails to power off host

[Hans]

I had this issue in the past. Sometimes I could fix it by just reinstalling 
grub and the kernel.

However, what that fixed? Dunno, but worked for me.

Best

Hans

Re: shutdown fails to power off host

[Verde Denim]

On 1/17/2017 1:00 PM, Curt wrote:

On 2017-01-17,   wrote:

Since it's a desktop I told the users that it's safe to power off the thing
when in this state and filed it under "unsolved hardware/init system quirks".

I suffer from one of these unsolved quirks. Occasionally my machine will
shutdown correctly but will not power off. I have detected no
discernible pattern (or discerned no detectable pattern).

I power the machine off manually when the quirk occurs.



regards
- -- tomás




+1 - I have a win 8 vm that currently exhibits this lovely feature -  i 
boot the host, bring up the vm, log in, and get a black (blank) session 
window. I can force it to shut down by selecting "shut down" for the 
virtual machine and then closing the session window. I can also suspend 
the machine through normal action function. But either resuming the 
machine or shutting down and re-initializing brings the login and 
post-login brings the black hole of nothing. I've been scratching my 
head as to how this machine got into this state since it did seem to 
work the first 5 or  6 times I brought it up. Virtual machines seem 
(sometimes) to have their moments just as hosts do.


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

Re: shutdown fails to power off host

[Michael Biebl]

Am 18.01.2017 um 08:44 schrieb Joerg Desch:
> Am Wed, 04 Jan 2017 22:59:46 -0800 schrieb Bob McGowan:
> 
>> When I shutdown my desktop system, the screen displays messages from
>> systemd (I presume), the last of which is "Reached target Shutdown".
> 
> Just a thought...
> 
> I'm running Debian Jessie and I see the same behavior with my Thinkpad 
> T500.
> 
> In my case the reason is the Network Manager. I have 2 NFS shares mounted 
> over Wifi. The Network Manager stops Wifi before unmounting the NFS 
> shares. This leads to a long time out. After that, I see the "Reached 
> target Shutdown" message and the system in still powered.
> 
> I have to unmount the NFS volumes first and than I can shutdown the 
> system.

You could unmount the NFS shares via a dispatcher hook
See man NetworkManager → pre-down


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Re: shutdown fails to power off host

[Joerg Desch]

Am Wed, 04 Jan 2017 22:59:46 -0800 schrieb Bob McGowan:

> When I shutdown my desktop system, the screen displays messages from
> systemd (I presume), the last of which is "Reached target Shutdown".

Just a thought...

I'm running Debian Jessie and I see the same behavior with my Thinkpad 
T500.

In my case the reason is the Network Manager. I have 2 NFS shares mounted 
over Wifi. The Network Manager stops Wifi before unmounting the NFS 
shares. This leads to a long time out. After that, I see the "Reached 
target Shutdown" message and the system in still powered.

I have to unmount the NFS volumes first and than I can shutdown the 
system.

Re: shutdown fails to power off host

[Bob McGowan]

On 01/17/2017 02:39 AM, Hans wrote:
> I remember this discussion from sime time ago. Debian has changed a real 
> poweroff from "halt" to "halt -p". The second one is according to the manual.
> 
> As far as I remeber, "shutdown" is just a wrapper fpr the halt command, but I 
> am not quite sure. 
> 
> But one thing was cleared: To poweroff a debian systenm, the command "halt 
> -p" 
> is recommended.
> 
> Besides: This behaviour is also now in kali linux integrated, which was also 
> using the command "halt" for a long time. But now it's "halt -p", too, also 
> on 
> the livefile.
> 
> Best
> 
> Hans
> 

Hi,

Thanks for the suggestions and insight to the problem.

In my case:

1.  The problem was with *any* "shutdown", from the command line, via
halt or shutdown, or through menus of the window system.

2.  The comment by j...@jretrading.com about unmount issues rings a bell,
I think I saw something about failure to sync at one point.

3.  I did try 'halt -p', same result.

4.  There have been two or three updates since I sent my original
question, and the system is now halting and powering off as expected.

Bob

Re: shutdown fails to power off host

[Joe]

On Tue, 17 Jan 2017 18:00:00 + (UTC)
Curt  wrote:

> On 2017-01-17,   wrote:
> >
> > Since it's a desktop I told the users that it's safe to power off
> > the thing when in this state and filed it under "unsolved
> > hardware/init system quirks".  
> 
> I suffer from one of these unsolved quirks. Occasionally my machine
> will shutdown correctly but will not power off. I have detected no
> discernible pattern (or discerned no detectable pattern).
> 
> I power the machine off manually when the quirk occurs.
> 

Me too. Sid on LVM2, AMD video on Giga MB, fails maybe 10%-20% of
shutdowns. The small amount of evidence suggests trouble dismounting the
hard drive, with the device mapper showing an unknown number of devices
having failed to clear, and no sound of the heads parking. Replacing
the hard drive (just age, not for this problem) has improved speeds of
some actions, and not changed this behaviour at all.

There is also trouble booting sometimes, which appears not to correlate
at all with the shutdown trouble. I think that is something to do with
video driving, but I can't get any kind of evidence for that, either,
other than that it always crashes when the display switches from low-res
text to high-res text. Nothing in any log, nothing at all to put in a
bug report. Hey, it's sid.

-- 
Joe

Re: shutdown fails to power off host

[Curt]

On 2017-01-17,   wrote:
>
> Since it's a desktop I told the users that it's safe to power off the thing
> when in this state and filed it under "unsolved hardware/init system quirks".

I suffer from one of these unsolved quirks. Occasionally my machine will
shutdown correctly but will not power off. I have detected no
discernible pattern (or discerned no detectable pattern).

I power the machine off manually when the quirk occurs.


> regards
> - -- tomás
>
>


-- 
“It is enough that the arrows fit exactly in the wounds that they have made.”
Franz Kafka

Re: shutdown fails to power off host

[Hans]

I remember this discussion from sime time ago. Debian has changed a real 
poweroff from "halt" to "halt -p". The second one is according to the manual.

As far as I remeber, "shutdown" is just a wrapper fpr the halt command, but I 
am not quite sure. 

But one thing was cleared: To poweroff a debian systenm, the command "halt -p" 
is recommended.

Besides: This behaviour is also now in kali linux integrated, which was also 
using the command "halt" for a long time. But now it's "halt -p", too, also on 
the livefile.

Best

Hans

Re: shutdown fails to power off host

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tue, Jan 17, 2017 at 11:35:28AM +0200, Johann Spies wrote:
> On 5 January 2017 at 09:09, Bob McGowan  wrote:
> 
> > On 01/04/2017 10:59 PM, Bob McGowan wrote:
> > > I have done a search of the debian-user archive, using the same text as
> > > the subject, and found several references to emails with similar
> > > problems.  However, no exact solution was proposed.
> > >
> > > And this actually only happens on one of the two systems I have Debian
> > > installed on.
> > >
> > > I'm using testing (stretch).
> > >
> > > When I shutdown my desktop system, the screen displays messages from
> > > systemd (I presume), the last of which is "Reached target Shutdown".
> > >
> >
> 
> I get that when I use 'sudo halt'
> 
> When I use 'sudo halt -p'  it powers off.

"halt" is "shutdown" -- at least from where you are shooting. From halt's
man page:

 If halt or reboot is called when the system is not in runlevel
 0 or 6, in other words  when  it's  running  normally, shutdown
     will be invoked instead (with the -h or -r flag). For more info
 see the shutdown(8) manpage.

> So I would suggest you look at the underlying command on the button of the
> computer which do not power off and change the command.
> 
> Look at 'man shutdown'  for the options when you use 'shutdown'  in stead
> of 'halt'.

I agree, it should be in the options. That said, one of the systems I take
care of *sometimes* ends up in this state (i.e. "Reached target ..."), but
most of the time actually powers off.

Since it's a desktop I told the users that it's safe to power off the thing
when in this state and filed it under "unsolved hardware/init system quirks".

regards
- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlh98ooACgkQBcgs9XrR2kYHnwCdEUocDUqU6+ZCEKaVwVnhFRp0
yFwAn2t/TFQNikQsV+Y+79RWUWXr7Xp0
=7fMt
-END PGP SIGNATURE-

Re: shutdown fails to power off host

[Johann Spies]

On 5 January 2017 at 09:09, Bob McGowan  wrote:

> On 01/04/2017 10:59 PM, Bob McGowan wrote:
> > I have done a search of the debian-user archive, using the same text as
> > the subject, and found several references to emails with similar
> > problems.  However, no exact solution was proposed.
> >
> > And this actually only happens on one of the two systems I have Debian
> > installed on.
> >
> > I'm using testing (stretch).
> >
> > When I shutdown my desktop system, the screen displays messages from
> > systemd (I presume), the last of which is "Reached target Shutdown".
> >
>

I get that when I use 'sudo halt'

When I use 'sudo halt -p'  it powers off.

So I would suggest you look at the underlying command on the button of the
computer which do not power off and change the command.


Look at 'man shutdown'  for the options when you use 'shutdown'  in stead
of 'halt'.

Regards
Johann

Re: shutdown fails to power off host

[Bob McGowan]

On 01/04/2017 10:59 PM, Bob McGowan wrote:
> I have done a search of the debian-user archive, using the same text as
> the subject, and found several references to emails with similar
> problems.  However, no exact solution was proposed.
> 
> And this actually only happens on one of the two systems I have Debian
> installed on.
> 
> I'm using testing (stretch).
> 
> When I shutdown my desktop system, the screen displays messages from
> systemd (I presume), the last of which is "Reached target Shutdown".
> 
> It then just sits there.  I have taken to using a power strip with a
> switch as a way to quickly turn the host off, once it has reached the
> target.
> 
> On my laptop, I see the same message, followed by powering off the system.
> 
> Tonight, I happened to take longer than usual to get to my desktop
> system, and while writing down the exact wording of the message, the
> kernel panicked.
> 
> My laptop is around ten years old, an HP Pavilion dv9000, the desktop is
> about half that age, a home built "gamer" level hardware system.
> 
> Any ideas what I should be looking for?  The fact the kernel panics on
> my desktop would imply to me there is a kernel configuration issue of
> some sort, but I have no idea where to start.
> 
> Thanks,
> 
> Bob
> 

My apologies, I failed to mention:

I'm using Xfce4 as my windowing system on both hosts.

And I'm using the 'shutdown' menu option from the "Action Buttons" panel
plugin.

Bob

shutdown fails to power off host

[Bob McGowan]

I have done a search of the debian-user archive, using the same text as
the subject, and found several references to emails with similar
problems.  However, no exact solution was proposed.

And this actually only happens on one of the two systems I have Debian
installed on.

I'm using testing (stretch).

When I shutdown my desktop system, the screen displays messages from
systemd (I presume), the last of which is "Reached target Shutdown".

It then just sits there.  I have taken to using a power strip with a
switch as a way to quickly turn the host off, once it has reached the
target.

On my laptop, I see the same message, followed by powering off the system.

Tonight, I happened to take longer than usual to get to my desktop
system, and while writing down the exact wording of the message, the
kernel panicked.

My laptop is around ten years old, an HP Pavilion dv9000, the desktop is
about half that age, a home built "gamer" level hardware system.

Any ideas what I should be looking for?  The fact the kernel panics on
my desktop would imply to me there is a kernel configuration issue of
some sort, but I have no idea where to start.

Thanks,

Bob

Gnome Shell takes about a minute to respond to logout or power off

[Alan Chandler]

I have a fairly standard Debian Sid system with Gnome3 with the shell 
extensions installed.


If I log off (from the menu below my name on the top right) the system 
immediately puts up the dialog box saying it will log off in 60 seconds 
but inviting me to either cancel or log out immediately. If I say log 
out immediately, the screen greys out and the activities hot spot become 
inactive, but nothing further happens for about 60 seconds, when it 
suddenly logs out.


Similarly - with power off, it again pops up a dialog box and again when 
I say power off now, nothing happens for a minute.  This time, you can 
see it going though the power off sequence with the final line on the 
console saying I will now halt, but in actual fact the PC reboots.  The 
only way I can power down, is to press the power down switch on the 
computer just before the bios completes the pre-boot sequence.


This same hardware has worked before for power down (it works in Wheezy 
- and powers down immediately), but I am not sure with regard to log out 
(since I am the only user of this machine I rarely have a requirement to 
log out) so something has changed.


Is anyone else experiencing these problems?  Any idea how they may be fixed?


--
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/51b962ff.4050...@chandlerfamily.org.uk

Re: "iwconfig wlan0 power off" on module load

[Selim T. Erdogan]

basti, 11.03.2013:
> I have fixed with
> 
> iface wlan0 inet dhcp
>   wireless-power off
> 
> in /etc/network/interfaces.
> This works for now.

I did it by adding a line to /etc/udev/rules.d/70-persistent-net.rules:

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="rt2500pci", KERNEL=="wlan0", 
RUN="/sbin/iwconfig wlan0 power off"

Selim

> Am 11.03.2013 20:58, schrieb basti:
> >Hello,
> >is the a way to do "iwconfig wlan0 power off" on module load
> >like "options rt2500usb nohwcrypt=1" can be?
> >
> >I don't find anythink about this.
> >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/20130313211514.ga29...@cs.utexas.edu

Re: "iwconfig wlan0 power off" on module load

[Wayne Topa]

On 03/11/2013 03:58 PM, basti wrote:

Hello,
is the a way to do "iwconfig wlan0 power off" on module load
like "options rt2500usb nohwcrypt=1" can be?

I don't find anythink about this.


The iwconfig man pages shows -power examples that you can use.

It is on your system so should be easy enough to see.

HTH

--
WT


--
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/513e4a72.5060...@gmail.com

Re: "iwconfig wlan0 power off" on module load

[basti]

I have fixed with

iface wlan0 inet dhcp
  wireless-power off

in /etc/network/interfaces.
This works for now.

Am 11.03.2013 20:58, schrieb basti:

Hello,
is the a way to do "iwconfig wlan0 power off" on module load
like "options rt2500usb nohwcrypt=1" can be?

I don't find anythink about this.
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/513e4812.1000...@arcor.de

"iwconfig wlan0 power off" on module load

[basti]

Hello,
is the a way to do "iwconfig wlan0 power off" on module load
like "options rt2500usb nohwcrypt=1" can be?

I don't find anythink about this.
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/513e3760.9030...@arcor.de

Re: suspend / power off

[Jon Dowland]

On Mon, Jan 16, 2012 at 08:53:53AM +, richard wrote:
> You didn't quite understand what I was asking :(
> If you suspend to RAM, S3, which I hope unmounts the hard drives.
> as suspend is set to power off the computer, does it really matter is running
> daemons and services are terminated by removing power ?

On a desktop computer, suspending does exactly the same thing as on a laptop:
the filesystems are synced (but not unmounted); processes (including daemons
and services) are frozen (but not terminated); the machine is powered *down*
(but not off - the mainboard and RAM are kept alive, and perhaps other bits and
pieces too depending on your setup, such as NICs).


-- 
Jon Dowland


-- 
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/20120116161928.GC23539@pris

Re: suspend / power off

[richard]

On Mon, 16 Jan 2012 00:26:10 +0200
Andrei Popescu  wrote:

> On Du, 15 ian 12, 18:23:22, richard wrote:
> > Greetings,
> > 
> > It may seem a daft question, BUT, what is the exact process when
> > suspending ?
> > 
> > On a laptop it doesn't matter as power is kept on when either the lid is
> > shut or suspended, the same action.
> > However, on a mains powered machine suspend will power off, I'm guessing a
> > write to ram and umount any active device ??
> > Anything written to ram will be lost, does it really mater now if running
> > daemons & services are just terminated instead of being properly shutdown ?
> > 
> > Now with gnome3 shell ALT has to be held don to go to the power off/restart
> > menu,
> > I wonder how many just do a rapid power off with suspend ?
> 
> Your question is a bit vague to me. Are you asking about Suspend-to-RAM
> (also known as S3)?
> http://en.wikipedia.org/wiki/Suspend_to_RAM
> 
> Or is this about Suspend to Disk (also known as Hibernate, S4)? 
> http://en.wikipedia.org/wiki/Suspend_to_disk
> 
> Anyway, as you might notice in those Wikipedia articles, there is no 
> difference between types of computers. What effect closing the lid on a 
> laptop has is usually configurable (BIOS and/or OS).
> 
> Kind regards,
> Andrei

Hi Andrei
You didn't quite understand what I was asking :(
If you suspend to RAM, S3, which I hope unmounts the hard drives.
as suspend is set to power off the computer, does it really matter is running
daemons and services are terminated by removing power ?

Richard


-- 
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/20120116085353.26f60...@lappy.g8jvm.com

Re: suspend / power off

[Andrei Popescu]

On Du, 15 ian 12, 18:23:22, richard wrote:
> Greetings,
> 
> It may seem a daft question, BUT, what is the exact process when suspending ?
> 
> On a laptop it doesn't matter as power is kept on when either the lid is shut
> or suspended, the same action.
> However, on a mains powered machine suspend will power off, I'm guessing a 
> write
> to ram and umount any active device ??
> Anything written to ram will be lost, does it really mater now if running
> daemons & services are just terminated instead of being properly shutdown ?
> 
> Now with gnome3 shell ALT has to be held don to go to the power off/restart
> menu,
> I wonder how many just do a rapid power off with suspend ?

Your question is a bit vague to me. Are you asking about Suspend-to-RAM
(also known as S3)?
http://en.wikipedia.org/wiki/Suspend_to_RAM

Or is this about Suspend to Disk (also known as Hibernate, S4)? 
http://en.wikipedia.org/wiki/Suspend_to_disk

Anyway, as you might notice in those Wikipedia articles, there is no 
difference between types of computers. What effect closing the lid on a 
laptop has is usually configurable (BIOS and/or OS).

Kind regards,
Andrei
-- 
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic


signature.asc
Description: Digital signature

suspend / power off

[richard]

Greetings,

It may seem a daft question, BUT, what is the exact process when suspending ?

On a laptop it doesn't matter as power is kept on when either the lid is shut
or suspended, the same action.
However, on a mains powered machine suspend will power off, I'm guessing a write
to ram and umount any active device ??
Anything written to ram will be lost, does it really mater now if running
daemons & services are just terminated instead of being properly shutdown ?

Now with gnome3 shell ALT has to be held don to go to the power off/restart
menu,
I wonder how many just do a rapid power off with suspend ?

Richard


-- 
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/20120115182322.5d97f...@lappy.g8jvm.com

Re: Hardware failure: power-off

[Camaleón]

El 2011-08-20 a las 12:34 +0200, Panayiotis Karabassis escribió:

(resending to the list)

> Thank you again!
> 
> $ acpi -V
> Battery 0: Full, 100%
> Battery 0: design capacity 4400 mAh, last full capacity 3558 mAh = 80%
> Adapter 0: on-line
> Thermal 0: ok, 58.8 degrees C
> Thermal 0: trip point 0 switches to mode critical at temperature 199.8
> degrees C
> Cooling 0: Processor 0 of 10
> Cooling 1: Processor 0 of 10
> 
> There is no way the temperature reached 199.8 degrees C!

Not al all :-}

"Trip points" are temperature levels triggers that activate preventive 
mesaures when they are reached (like powering-off the system or make 
your fans run faster). But 199.8℃ looks of course wrong, even for an 
ultra-low consumption microprocessor is a very high value, so there is a 
bug on acpi package/kernel or your BIOS is delivering wrong values that makes 
acpi goes nuts :-)

Try a BIOS update, if possible.

> All my important data is on my desktop PC.
> 
> I'll probably take it to the service center. There my a problem with the
> thermal glue on the processor + plus all those you described yourself.
> 
> Thanks again!

You're welcome.

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/20110820105259.ga4...@stt008.linux.site

Re: Hardware failure: power-off

[Camaleón]

On Sat, 20 Aug 2011 07:41:36 +0200, Panayiotis Karabassis wrote:

> On 08/19/2011 09:10 PM, Camaleón wrote:
>> Also check the hardware monitor section of the BIOS, if possible, they
>> will give you an accurate measure. You can also check the output of
>> "acpi -V" to find out additional data for trip points (is available).
>> 
>> Is it a laptop or a desktop computer?
> 
> It's a laptop. I couldn't find a hardware monitor in the BIOS. 

Hum, yes, laptops suck for this, I mean, their BIOS are so limited that 
look useless :-/

> Also I can't find the 'acpi' command, not even with apt-file.

ACPI is a package. I got it installed on both, desktops and laptops 
computers.

http://packages.debian.org/squeeze/acpi

On desktops, "acpi -V" displays little information but on laptops you can 
get useful values for CPU temperature, thermal trip points, fans and 
battery status. OTOH, lm-sensors can be also an option, as you said 
before, but this program has to be first tweaked to get usable and 
accurate values.

>> By your explanation, yep, looks like the micro is reaching a high
>> temperature and it shutdowns to avoid damage. Keep the system running
>> with the BIOS screen opened and watch fans speed rotation and system
>> temps... and keep it so for a while to see if it also powers-off.
> 
> I opened the laptop and cleaned the fan's airduct. Then the laptop was
> stable for many hours.
> 
> But. Before going to sleep, I activated a 3D screensaver. When I woke-up
> the laptop had powered-off again.
> 
> When using glxgears, the CPU cores' temperature skyrockets very fast,
> and the fan becomes very noisy.
> 
> I missed something, something I didn't clean. Do you think I can resolve
> this on my own (I am abroad), or should I pay a technician when I get
> home?

I would first look for a BIOS update if available, but yes, if you have 
no previous experience on laptops cleaning (while this a common task I 
always do by myself on desktops/servers is something I never did before 
on laptops) I would consider bringing the computer to the service support 
so they take a look (consider doing a full backup of your hard disk, just 
in case they break something...). 

It can be the fan that just needs to be replaced (maybe this is something 
you can try yourself) but it also can be the heatsink of the processor, 
that needs to be fully cleaned or even replaced with a new one, and this 
task can be tricky, depending on your computer brand/model.

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.08.20.09.09...@gmail.com

Re: Hardware failure: power-off

[Panayiotis Karabassis]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Thank you very much, Camaleón!

On 08/19/2011 09:10 PM, Camaleón wrote:
> Also check the hardware monitor section of the BIOS, if possible, they 
> will give you an accurate measure. You can also check the output of "acpi 
> -V" to find out additional data for trip points (is available).
> 
> Is it a laptop or a desktop computer?

It's a laptop. I couldn't find a hardware monitor in the BIOS. Also I
can't find the 'acpi' command, not even with apt-file.

> By your explanation, yep, looks like the micro is reaching a high 
> temperature and it shutdowns to avoid damage. Keep the system running 
> with the BIOS screen opened and watch fans speed rotation and system 
> temps... and keep it so for a while to see if it also powers-off.

I opened the laptop and cleaned the fan's airduct. Then the laptop was
stable for many hours.

But. Before going to sleep, I activated a 3D screensaver. When I woke-up
the laptop had powered-off again.

When using glxgears, the CPU cores' temperature skyrockets very fast,
and the fan becomes very noisy.

I missed something, something I didn't clean. Do you think I can resolve
this on my own (I am abroad), or should I pay a technician when I get home?

- -- 
Best regards,
Panayiotis Karabassis
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOT0kNAAoJEN7RcJcJCZJiM7IH/RcO+987pEPKlsPUu0RAbImt
4J+JYZTrYXe0sfCZp2h+S4Gkarg2AA1l2gEtavTISC/W6lyEVjSCVxCGzm0Ckuv8
NfyNkJIQki3dYcOxTtH3EcJ+hecMFKukZqbYsSxDBkNLrWTPlJq9vrdkRRhC/sEn
gsWWpodDPvMNzLJgf7XUKbERB3jMzQwSYX8qJYdw1Rq8Ze0YkoxlhCFVy4K5o5st
b2fxTqeDNwLWJ8PhWyBIjByB6kDdL3k97QFVgA+lu3leBzyAu2g65PCTJ6teFKO+
M/XQqV9CtdHFueoPwwQbH2NYTIKiMbdWjy4cDvX1f80nVug43NMHyHNKGsoeRXE=
=7GtV
-END PGP SIGNATURE-


-- 
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/4e4f4910.7030...@gmail.com

Re: Hardware failure: power-off

[Camaleón]

On Fri, 19 Aug 2011 07:46:55 +0200, Panayiotis Karabassis wrote:

> This is almost certainly a hardware problem, but I think readers of this
> list are knowledgeable enough to help me.
> 
> My laptop shuts down at unexpected times. There are no messages in the
> logs at the time of shutdown, but there are some ACPI failures at boot
> time.
> 
> When the power-off occurs, if I reboot the computer, another power-off
> occurs very shortly, and so on. It seems I have to let the computer
> "cool down" for a while, so I suspect this may be temperature related.
> 
> I have started monitoring the laptop temperatures through the
> sensors-applet package, and they seem to be within ranges.

Also check the hardware monitor section of the BIOS, if possible, they 
will give you an accurate measure. You can also check the output of "acpi 
-V" to find out additional data for trip points (is available).

Is it a laptop or a desktop computer?
 
> Also the power-off are less likely, if gdm3 has managed to start.
> 
> I appreciate any advice.

By your explanation, yep, looks like the micro is reaching a high 
temperature and it shutdowns to avoid damage. Keep the system running 
with the BIOS screen opened and watch fans speed rotation and system 
temps... and keep it so for a while to see if it also powers-off.

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.08.19.19.10...@gmail.com

Hardware failure: power-off

[Panayiotis Karabassis]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

This is almost certainly a hardware problem, but I think readers of this
list are knowledgeable enough to help me.

My laptop shuts down at unexpected times. There are no messages in the
logs at the time of shutdown, but there are some ACPI failures at boot time.

When the power-off occurs, if I reboot the computer, another power-off
occurs very shortly, and so on. It seems I have to let the computer
"cool down" for a while, so I suspect this may be temperature related.

I have started monitoring the laptop temperatures through the
sensors-applet package, and they seem to be within ranges.

Also the power-off are less likely, if gdm3 has managed to start.

I appreciate any advice.

- -- 
Best regards,
Panayiotis Karabassis
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOTfjMAAoJEN7RcJcJCZJiDZkIAJPN2C7Ia/C9trVsir8XXjQC
eYDvuRQ6L7QLywJM5r+8It5RiIw6gJqvmvFCUsfJBLdyvnCzUfAZvwGB9+GrzzXq
v5dOCx6g5zsUaPLzkLhumUpFDpzqWNuGc10lt1SRQvBMoKKj81FQgcJcRsC/zW3U
BY2IZx+pLl4EJPlRiX8GEpBmbAspO6q0UBSTk3AezmOVTO3635a9qTjGBPc6KkP3
qDVSiTuzJ3H9EMtoSlr8rYbIJwiumvwviv8PW4LVMgMAgBS+Np5diHsDKnLQdtWp
kRvShawvxHlSVI4M0Jto6F5Fp/LGXRFVbGLSb5E0h+aKvk5cfOnofYOkuru9tAE=
=gu94
-END PGP SIGNATURE-


-- 
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/4e4df8cf.8030...@gmail.com

Re: Power button does not power off any more

[Sven Joachim]

On 2010-07-13 18:28 +0200, T o n g wrote:

> When I press the power button on my box, I used to be able to power off 
> my machine, but not now (nothing happens). It's the same machine. 
>
> How can I get back the feature so that when I press the power button my 
> box powers off?

Do you have the acpi-support-base package installed?  And in which
version?

Sven


-- 
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/87lj9fs026@turtle.gmx.de

hotplug disk (howto power off)

[nico]

i have a HP server with 3 hotplug disks, 2 in one array 5 and 1 that i 
use for backup,

the problem is that i cannot power the disk off from debian.
I'm pluging it, use hpacucli and i create the array 0, the kernel detect 
the disk, i mount it, copy all the info, then i umount it and here is 
the problem, how can i power the disk off before i unplug it, now i just 
unplug it, then i delete the array using hpacucli and till now i have no 
errors on the disk but i guess i have to send a command to the kernel so 
it power the disk off or just stop it.
i so that in red hat yo can echo 1 > /sys/block/disk/delete and it just 
delete the disk from memory.


I want to know if what i'm doing is right because the kernel do it 
automatically or if i have to do something, i google a lot and i cannot 
found a solution for debian.


THANKS FOR THE HELP


--
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/4b91aa86.6020...@yahoo.com.ar

Re: sudden power off ... ?!?

[Neal Hogan]

On Mon, Sep 21, 2009 at 12:07 PM, Dan  wrote:

>   Hello List,
>
> It is few days that I installed (standard installation) Debian Lenny on
> this pc.


Which pc? If it's a harware issue, perhaps letting us know what hardware you
have may help (dmesg?). Perhaps someone may have had similar issues with
similar hardware.


>   Randomly (maybe once or sometimes two a day) it powers off like if it
> has suddenly been plugged off from the AC. If I then soon turn it on no
> problems to start up. I suspect this could be a hardware fault. I would like
> to check also any settings in the BIOS.
> Are there any possibilities that this problem is related to any software
> bug ?
>

Again, what hardware you have and which software you're using may help you
get help.


>
> Thanks, dan
>
>

Re: sudden power off ... ?!?

[Aioanei Rares]

Dan wrote:

Hello List,

It is few days that I installed (standard installation) Debian Lenny 
on this pc. Randomly (maybe once or sometimes two a day) it powers off 
like if it has suddenly been plugged off from the AC. If I then soon 
turn it on no problems to start up. I suspect this could be a hardware 
fault. I would like to check also any settings in the BIOS.
Are there any possibilities that this problem is related to any 
software bug ?


Thanks, dan


I think it's HW related, but you could try with a livecd of your Linux 
distro of choice and see if the symptoms persist.



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

sudden power off ... ?!?

[Dan]

Hello List,

It is few days that I installed (standard installation) Debian Lenny on this 
pc. Randomly (maybe once or sometimes two a day) it powers off like if it has 
suddenly been plugged off from the AC. If I then soon turn it on  no problems 
to start up. I suspect this could be a hardware fault. I would like to check 
also any settings in the BIOS.
Are there any possibilities that this problem is related to any software bug ?

Thanks, dan 



  

power off without acpi

[Engi Zoltán]

Hi everybody,

How can I shutdown my computer without acpi?
In the grub menu, I have next line:
/boot/vmlinuz-2.6.26-1-amd64 root=/dev/hdc6 ro acpi=off

So, I can switch off acpi, but after "shutdown -h now" command the 
computer doesn't switch off. I get next message: "Sytem halted".


I don't want use acpi because if acpi switch off computer the bios can't 
switch on tomorrow.


Zoli


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: Getting power off to work in Etch...

[Digby Tarvin]

On Tue, Oct 30, 2007 at 09:44:38PM +0100, Nigel Henry wrote:
> On Tuesday 30 October 2007 18:58, Digby Tarvin wrote:
> > Does anyone know the secret to getting Etch to power down the system
> > after a halt. I have tried 'apt-get install apmd', but it doesn't
> > seem to have helped.
> >
> > I know the hardware can do it, because it worked with the very old
> > version of Ubuntu I tried before Debian (5.04).
> >
> > The machine is a Dell Precision 410 with new Etch netinst just done...
> >
> > Thanks,
> > DigbyT
> 
> Hi Digby. Just an update. I found the the link to the bugreport for the 
> shutdown problem. It may, or may not resolve your problem, but is below.
> 
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=390547
> 
> Cordialement.
> 
> Nigel.

Hi Nigel,

I went through that bugreport, and creating a /etc/modprobe.d/apm containing
options apm power_off=1
fixed it for me.

Many thanks for all the pointers.

Regards,
DigbyT
-- 
Digby R. S. Tarvin  digbyt(at)digbyt.com
http://www.digbyt.com


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Getting power off to work in Etch...

[Nigel Henry]

On Tuesday 30 October 2007 18:58, Digby Tarvin wrote:
> Does anyone know the secret to getting Etch to power down the system
> after a halt. I have tried 'apt-get install apmd', but it doesn't
> seem to have helped.
>
> I know the hardware can do it, because it worked with the very old
> version of Ubuntu I tried before Debian (5.04).
>
> The machine is a Dell Precision 410 with new Etch netinst just done...
>
> Thanks,
> DigbyT

Hi Digby. Just an update. I found the the link to the bugreport for the 
shutdown problem. It may, or may not resolve your problem, but is below.

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=390547

Cordialement.

Nigel.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Getting power off to work in Etch...

[Nigel Henry]

On Tuesday 30 October 2007 18:58, Digby Tarvin wrote:
> Does anyone know the secret to getting Etch to power down the system
> after a halt. I have tried 'apt-get install apmd', but it doesn't
> seem to have helped.
>
> I know the hardware can do it, because it worked with the very old
> version of Ubuntu I tried before Debian (5.04).
>
> The machine is a Dell Precision 410 with new Etch netinst just done...
>
> Thanks,
> DigbyT

Hi Digby. There's a multitude of possible fixes for this one. I've had no 
problems with my Debian, Sarge, Etch, and Lenny installs, all on the same 
machine, but a Fedora version had shutdown problems on this machine, and 
appending the kernel line with acpi=force in /boot/grub/grub.conf fixed it.

I did see another possible fix in the Debian archives, but will have to look 
for that.

Nigel.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Getting power off to work in Etch...

[Digby Tarvin]

Does anyone know the secret to getting Etch to power down the system
after a halt. I have tried 'apt-get install apmd', but it doesn't
seem to have helped.

I know the hardware can do it, because it worked with the very old
version of Ubuntu I tried before Debian (5.04).

The machine is a Dell Precision 410 with new Etch netinst just done...

Thanks,
DigbyT
-- 
Digby R. S. Tarvin  digbyt(at)digbyt.com
http://www.digbyt.com


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: why sarge can't power off PC

[Wulfy]

Andrew Sackville-West wrote:

On Fri, Aug 1
well, my experience with a power-up not "catching" ended up being a
failing mobo. I think it can come from failing memory too. I think it
can also come from a failing power supply that doesn't give enough
juice over all the lines resulting in some parts of the
mobo/chipset/proc not powering up properly. ymmv.

A
  
I had the though of a not-powerful-enough power supply in the back of my 
mind.  I hope it's that...  I think I could manage to replace that.  
Memory seems to be OK, at least it passes memtest86+ tests...


Thanks for your help!

--
Blessings

Wulfmann

Wulf Credo:
Respect the elders. Teach the young. Co-operate with the pack. 
Play when you can. Hunt when you must. Rest in between.

Share your affections. Voice your opinion. Leave your Mark.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: why sarge can't power off PC

[Andrew Sackville-West]

On Fri, Aug 11, 2006 at 12:18:44AM +0100, Wulfy wrote:
> Andrew Sackville-West wrote:
> >>Well, half done.  The reboot hangs after the keyboard lights flash and 
> >>before the BIOS screen shows... I have to power off by the button and 
> >>power on again.  And that doesn't always work.
> >>
> >
> >I've been watching this thread, and I think you might be facing a
> >hardware problem there. If the machine goes for reboot and gets to the
> >keyboard flash and nothing else, then you aren't into the software
> >yet. Does powerup from a cold box cause intermittent problems like
> >this too?
> >
> >A
> Hmm.  I rarely shut-down the box unless there's a problem.  I seem to 
> recall that it sometimes doesn't "catch" the first time I boot from 
> off.  Definitely didn't notice a problem with that until recently, but,. 
> as I say, I keep my box on all the time. I've been doing some reading 
> and found out why it didn't always catch when I switched off then on...  
> needs a couple of seconds before it recognises a change in the button, 
> apparently.  I did have a hard-drive die on me and a CDROM that refused 
> to work.  Fortunately there was nothing much on the hard-drive.  I 
> changed from "nv" to the nVidia driver to get 3D acceleration working.  
> Those are the only things I can think oif that I've changed in the last 
> couple of months or so...
> 
> What do you suspect?

well, my experience with a power-up not "catching" ended up being a
failing mobo. I think it can come from failing memory too. I think it
can also come from a failing power supply that doesn't give enough
juice over all the lines resulting in some parts of the
mobo/chipset/proc not powering up properly. ymmv.

A


signature.asc
Description: Digital signature

Re: why sarge can't power off PC

[Wulfy]

Andrew Sackville-West wrote:
Well, half done.  The reboot hangs after the keyboard lights flash and 
before the BIOS screen shows... I have to power off by the button and 
power on again.  And that doesn't always work.



I've been watching this thread, and I think you might be facing a
hardware problem there. If the machine goes for reboot and gets to the
keyboard flash and nothing else, then you aren't into the software
yet. Does powerup from a cold box cause intermittent problems like
this too?

A
Hmm.  I rarely shut-down the box unless there's a problem.  I seem to 
recall that it sometimes doesn't "catch" the first time I boot from 
off.  Definitely didn't notice a problem with that until recently, but,. 
as I say, I keep my box on all the time. I've been doing some reading 
and found out why it didn't always catch when I switched off then on...  
needs a couple of seconds before it recognises a change in the button, 
apparently.  I did have a hard-drive die on me and a CDROM that refused 
to work.  Fortunately there was nothing much on the hard-drive.  I 
changed from "nv" to the nVidia driver to get 3D acceleration working.  
Those are the only things I can think oif that I've changed in the last 
couple of months or so...


What do you suspect?

--
Blessings

Wulfmann

Wulf Credo:
Respect the elders. Teach the young. Co-operate with the pack. 
Play when you can. Hunt when you must. Rest in between.

Share your affections. Voice your opinion. Leave your Mark.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: why sarge can't power off PC

[Andrew Sackville-West]

> Well, half done.  The reboot hangs after the keyboard lights flash and 
> before the BIOS screen shows... I have to power off by the button and 
> power on again.  And that doesn't always work.

I've been watching this thread, and I think you might be facing a
hardware problem there. If the machine goes for reboot and gets to the
keyboard flash and nothing else, then you aren't into the software
yet. Does powerup from a cold box cause intermittent problems like
this too?

A



signature.asc
Description: Digital signature

Re: why sarge can't power off PC

[Wulfy]

Florian Kulzer wrote:

I see. I only hopped into this thread after the post in which you asked
about the KDE power control settings and the error messages about the
incomplete ACPI installation. From that I got the impression that you
wanted to activate these laptop-specific ACPI features in KDE. I think
it is normal that the "battery" and "ac" modules have no effect on a
desktop machine.
  

Sorry for the confusion.

I now realize that your original question was about the shutdown/power
off function. That seems to work again since you switched from APM to
ACPI, so we are done, right?
Well, half done.  The reboot hangs after the keyboard lights flash and 
before the BIOS screen shows... I have to power off by the button and 
power on again.  And that doesn't always work.


Does ACPI do anything else for desktops apart from shut-down/reboot?  
There's a number of modules loaded. though some would be for laptops, I 
assume...


--
Blessings

Wulfmann

Wulf Credo:
Respect the elders. Teach the young. Co-operate with the pack. 
Play when you can. Hunt when you must. Rest in between.

Share your affections. Voice your opinion. Leave your Mark.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: why sarge can't power off PC

[Florian Kulzer]

On Thu, Aug 10, 2006 at 19:34:27 +0100, Wulfy wrote:
> Florian Kulzer wrote:
> >ACPI seems to be broken for you. Are there any "helpful" error messages
> >during boot? Try to run
> >
> >dmesg | grep -i acpi
> >
> >ACPI can be a real pain in the neck on some hardware. Your best bet is
> >probably to go to tuxmobil.org and see how far other people have gotten
> >with your laptop model and what tricks they had to use.
>
> But my system is a desktop, not a laptop... now I'm really confused...  :(

I see. I only hopped into this thread after the post in which you asked
about the KDE power control settings and the error messages about the
incomplete ACPI installation. From that I got the impression that you
wanted to activate these laptop-specific ACPI features in KDE. I think
it is normal that the "battery" and "ac" modules have no effect on a
desktop machine.

I now realize that your original question was about the shutdown/power
off function. That seems to work again since you switched from APM to
ACPI, so we are done, right?

-- 
Regards,
  Florian


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: why sarge can't power off PC

[Wulfy]

Florian Kulzer wrote:

ACPI seems to be broken for you. Are there any "helpful" error messages
during boot? Try to run

dmesg | grep -i acpi

ACPI can be a real pain in the neck on some hardware. Your best bet is
probably to go to tuxmobil.org and see how far other people have gotten
with your laptop model and what tricks they had to use.
  

Here's my output...

[EMAIL PROTECTED]:~$ dmesg | grep -i acpi
 BIOS-e820: 1fff - 1fff8000 (ACPI data)
 BIOS-e820: 1fff8000 - 2000 (ACPI NVS)
ACPI: RSDP (v000 AMI   ) @ 0x000fa1d0
ACPI: RSDT (v001 AMIINT SiS740XX 0x1000 MSFT 0x010b) @ 0x1fff
ACPI: FADT (v001 AMIINT SiS740XX 0x0011 MSFT 0x010b) @ 0x1fff0030
ACPI: MADT (v001 AMIINT SiS740XX 0x1000 MSFT 0x010b) @ 0x1fff00c0
ACPI: DSDT (v001SiS  740 0x0100 MSFT 0x010d) @ 0x
ACPI: PM-Timer IO Port: 0x808
ACPI: Local APIC address 0xfee0
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0])
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Using ACPI (MADT) for SMP configuration information

[My processor is an AMD Duron...  not SMP]

ACPI: Subsystem revision 20040326
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (00:00)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: Power Resource [URP1] (off)
ACPI: Power Resource [URP2] (off)
ACPI: Power Resource [FDDP] (off)
ACPI: Power Resource [LPTP] (off)
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 10 11 12 14 15) *0, 
disabled.

ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 7 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 *5 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 *5 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 7 10 11 12 14 15) *0, 
disabled.

ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 *5 7 10 11 12 14 15)
PCI: Using ACPI for IRQ routing
ACPI: PCI interrupt :00:02.1[B] -> GSI 17 (level, low) -> IRQ 169
ACPI: PCI interrupt :00:02.7[C] -> GSI 18 (level, low) -> IRQ 177
ACPI: PCI interrupt :00:03.0[A] -> GSI 20 (level, low) -> IRQ 185
ACPI: PCI interrupt :00:03.1[B] -> GSI 21 (level, low) -> IRQ 193
ACPI: PCI interrupt :00:03.2[D] -> GSI 23 (level, low) -> IRQ 201
ACPI: PCI interrupt :00:04.0[A] -> GSI 19 (level, low) -> IRQ 209
ACPI: PCI interrupt :01:00.0[A] -> GSI 16 (level, low) -> IRQ 217
ACPI: (supports S0 S1 S4 S5)
ACPI: PCI interrupt :00:04.0[A] -> GSI 19 (level, low) -> IRQ 209
ACPI: PCI interrupt :00:03.0[A] -> GSI 20 (level, low) -> IRQ 185
ACPI: PCI interrupt :00:03.1[B] -> GSI 21 (level, low) -> IRQ 193
ACPI: PCI interrupt :00:02.7[C] -> GSI 18 (level, low) -> IRQ 177
ACPI: PCI interrupt :00:03.2[D] -> GSI 23 (level, low) -> IRQ 201
ACPI: Processor [CPU1] (supports C1)
ACPI: Power Button (FF) [PWRF]
ACPI: Sleep Button (CM) [SLPB]
ACPI: PCI interrupt :01:00.0[A] -> GSI 16 (level, low) -> IRQ 217
The power button script works...  shuts me right down to "off"...  
nothing else in /etc/acpi.


--
Blessings

Wulfmann

Wulf Credo:
Respect the elders. Teach the young. Co-operate with the pack. 
Play when you can. Hunt when you must. Rest in between.

Share your affections. Voice your opinion. Leave your Mark.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: why sarge can't power off PC

[Wulfy]

Florian Kulzer wrote:

ACPI seems to be broken for you. Are there any "helpful" error messages
during boot? Try to run

dmesg | grep -i acpi

ACPI can be a real pain in the neck on some hardware. Your best bet is
probably to go to tuxmobil.org and see how far other people have gotten
with your laptop model and what tricks they had to use.

But my system is a desktop, not a laptop... now I'm really confused...  :(

--
Blessings

Wulfmann

Wulf Credo:
Respect the elders. Teach the young. Co-operate with the pack. 
Play when you can. Hunt when you must. Rest in between.

Share your affections. Voice your opinion. Leave your Mark.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: why sarge can't power off PC

[Florian Kulzer]

On Wed, Aug 09, 2006 at 23:58:48 +0100, Wulfy wrote:
> Florian Kulzer wrote:
> >I think that KDE should recognize that the AC adapter and the battery
> >ACPI modules are loaded. Let's check some ACPI functions: Do you have
> >the /proc/acpi/ac_adapter/ and /proc/acpi/battery/ directories? Test if
> >you can do things like:
> >
> >
> >
> >(The sub-directories might have different names on your system, but you
> > should be able to get similar information about the AC adaptor and the
> > battery.)
> I have both /proc/acpi/ac_adaptor and /proc/acpi/battery but both 
> directories are empty.  Other directories contain text files (info and 
> others) but all these documents are empty.

ACPI seems to be broken for you. Are there any "helpful" error messages
during boot? Try to run

dmesg | grep -i acpi

ACPI can be a real pain in the neck on some hardware. Your best bet is
probably to go to tuxmobil.org and see how far other people have gotten
with your laptop model and what tricks they had to use.

-- 
Regards,
  Florian


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: why sarge can't power off PC

[Wulfy]

Florian Kulzer wrote:

I think that KDE should recognize that the AC adapter and the battery
ACPI modules are loaded. Let's check some ACPI functions: Do you have
the /proc/acpi/ac_adapter/ and /proc/acpi/battery/ directories? Test if
you can do things like:



(The sub-directories might have different names on your system, but you
 should be able to get similar information about the AC adaptor and the
 battery.)
I have both /proc/acpi/ac_adaptor and /proc/acpi/battery but both 
directories are empty.  Other directories contain text files (info and 
others) but all these documents are empty.


--
Blessings

Wulfmann

Wulf Credo:
Respect the elders. Teach the young. Co-operate with the pack. 
Play when you can. Hunt when you must. Rest in between.

Share your affections. Voice your opinion. Leave your Mark.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: why sarge can't power off PC

[Florian Kulzer]

On Wed, Aug 09, 2006 at 06:49:15 +0100, Wulfy wrote:
> Florian Kulzer wrote:

[...]

> >Try to modprobe "ac", "power" and "battery" and check if that makes any
> >difference.
> acpi-related modules in lsmod;
> 
> thermal12816  0
> fan 4044  0
> button  6360  0
> processor  17392  1 thermal
> ac  4876  0
> battery 9484  0

I think that KDE should recognize that the AC adapter and the battery
ACPI modules are loaded. Let's check some ACPI functions: Do you have
the /proc/acpi/ac_adapter/ and /proc/acpi/battery/ directories? Test if
you can do things like:

$ cat /proc/acpi/ac_adapter/AC0/state
state:   off-line

$ cat /proc/acpi/battery/BAT0/state
present: yes
capacity state:  ok
charging state:  discharging
present rate:10850 mW
remaining capacity:  64694 mWh
present voltage: 11760 mV

$ cat /proc/acpi/battery/BAT0/info
present: yes
design capacity: 66640 mWh
last full capacity:  66640 mWh
battery technology:  rechargeable
design voltage:  14000 mV
design capacity warning: 6664 mWh
design capacity low: 3332 mWh
capacity granularity 1:  59976 mWh
capacity granularity 2:  56644 mWh
model number:M2N
serial number:
battery type:LIon
OEM info:ASUSTEK

(The sub-directories might have different names on your system, but you
 should be able to get similar information about the AC adaptor and the
 battery.)

-- 
Regards,
  Florian


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: why sarge can't power off PC

[Wulfy]

Florian Kulzer wrote:

On Wed, Aug 09, 2006 at 19:23:55 +0100, Wulfy wrote:
  

Liam O'Toole wrote:


I don't know of a module called 'power'. Try this command to find
power-related modules:

   find /lib/modules/$(uname-r) -name *power*
  

I ran the command;

[EMAIL PROTECTED]:~$ find /lib/modules/$(uname -r) -name *power*
/lib/modules/2.6.8-3-k7/kernel/arch/i386/kernel/cpu/cpufreq/powernow-k6.ko
/lib/modules/2.6.8-3-k7/kernel/arch/i386/kernel/cpu/cpufreq/powernow-k7.ko
/lib/modules/2.6.8-3-k7/kernel/arch/i386/kernel/cpu/cpufreq/powernow-k8.ko
/lib/modules/2.6.8-3-k7/kernel/drivers/cpufreq/cpufreq_powersave.ko
/lib/modules/2.6.8-3-k7/kernel/drivers/usb/input/powermate.ko

None of these show in lsmod.



I mentioned "power" because I have

/usr/src/linux-source-2.6.17/drivers/acpi/power.c

It does not seem to be in 2.6.8, though, so I apologize for sending you
on a wild goose chase.
power.c appears in my /usr/src/kernel-source-2.6.8/drivers/acpi/ folder, 
too...


but not in the corresponding .../kernel-source-2.6.8-3/... or 
.../kernel-source-2.6.8-3-k7/... folders...


Curiouser and curiouser, as Alice would say...  :)

Of course, when it comes to this sort of thing, I'm more 
monkey-see-monkey-do than understanding :)


--
Blessings

Wulfmann

Wulf Credo:
Respect the elders. Teach the young. Co-operate with the pack. 
Play when you can. Hunt when you must. Rest in between.

Share your affections. Voice your opinion. Leave your Mark.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: why sarge can't power off PC

[Florian Kulzer]

On Wed, Aug 09, 2006 at 19:23:55 +0100, Wulfy wrote:
> Liam O'Toole wrote:
> >I don't know of a module called 'power'. Try this command to find
> >power-related modules:
> >
> >find /lib/modules/$(uname-r) -name *power*
> 
> I ran the command;
> 
> [EMAIL PROTECTED]:~$ find /lib/modules/$(uname -r) -name *power*
> /lib/modules/2.6.8-3-k7/kernel/arch/i386/kernel/cpu/cpufreq/powernow-k6.ko
> /lib/modules/2.6.8-3-k7/kernel/arch/i386/kernel/cpu/cpufreq/powernow-k7.ko
> /lib/modules/2.6.8-3-k7/kernel/arch/i386/kernel/cpu/cpufreq/powernow-k8.ko
> /lib/modules/2.6.8-3-k7/kernel/drivers/cpufreq/cpufreq_powersave.ko
> /lib/modules/2.6.8-3-k7/kernel/drivers/usb/input/powermate.ko
> 
> None of these show in lsmod.

I mentioned "power" because I have

/usr/src/linux-source-2.6.17/drivers/acpi/power.c

It does not seem to be in 2.6.8, though, so I apologize for sending you
on a wild goose chase.

-- 
Regards,
  Florian


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: why sarge can't power off PC

[Wulfy]

[EMAIL PROTECTED] wrote:

On Wed, Aug 09, 2006 at 08:12:59AM -0700, Paul Johnson wrote:
  

On Tuesday 08 August 2006 22:54, Wulfy wrote:



Is there any way to check the power supply's wattage without opening the
case?
  
Yes, but it generally requires lightning for approximately the same reasons 
changing a motherboard without opening the case requires high 
explosives.  :o)



uhh.. wouldn't the high explosive open the case?
And how *would* you use lightning to measure the power supply's wattage?

-- straight-man hendrik

Hehe.  Well, I asked Thor *not* to send lightening to my power supply... :)

--
Blessings

Wulfmann

Wulf Credo:
Respect the elders. Teach the young. Co-operate with the pack. 
Play when you can. Hunt when you must. Rest in between.

Share your affections. Voice your opinion. Leave your Mark.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: why sarge can't power off PC

[Wulfy]

Liam O'Toole wrote:

I don't know of a module called 'power'. Try this command to find
power-related modules:

find /lib/modules/$(uname-r) -name *power*


I ran the command;

[EMAIL PROTECTED]:~$ find /lib/modules/$(uname -r) -name *power*
/lib/modules/2.6.8-3-k7/kernel/arch/i386/kernel/cpu/cpufreq/powernow-k6.ko
/lib/modules/2.6.8-3-k7/kernel/arch/i386/kernel/cpu/cpufreq/powernow-k7.ko
/lib/modules/2.6.8-3-k7/kernel/arch/i386/kernel/cpu/cpufreq/powernow-k8.ko
/lib/modules/2.6.8-3-k7/kernel/drivers/cpufreq/cpufreq_powersave.ko
/lib/modules/2.6.8-3-k7/kernel/drivers/usb/input/powermate.ko

None of these show in lsmod.

--
Blessings

Wulfmann

Wulf Credo:
Respect the elders. Teach the young. Co-operate with the pack. 
Play when you can. Hunt when you must. Rest in between.

Share your affections. Voice your opinion. Leave your Mark.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: why sarge can't power off PC

[hendrik]

On Wed, Aug 09, 2006 at 08:12:59AM -0700, Paul Johnson wrote:
> On Tuesday 08 August 2006 22:54, Wulfy wrote:
> 
> > Is there any way to check the power supply's wattage without opening the
> > case?
> 
> Yes, but it generally requires lightning for approximately the same reasons 
> changing a motherboard without opening the case requires high 
> explosives.  :o)

uhh.. wouldn't the high explosive open the case?
And how *would* you use lightning to measure the power supply's wattage?

-- straight-man hendrik


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: why sarge can't power off PC

[Paul Johnson]

On Tuesday 08 August 2006 22:54, Wulfy wrote:

> Is there any way to check the power supply's wattage without opening the
> case?

Yes, but it generally requires lightning for approximately the same reasons 
changing a motherboard without opening the case requires high 
explosives.  :o)

-- 
Paul Johnson
Email and IM (XMPP & Google Talk): [EMAIL PROTECTED]
Jabber: Because it's time to move forward  http://ursine.ca/Ursine:Jabber


pgpd1fKx1yW39.pgp
Description: PGP signature

Re: (Solved) Re: why sarge can't power off PC

[michael]

On Wed, 2006-08-09 at 13:34 +0200, Alexander Farber wrote:
> Hello,
> 
> I have same problem with my dual-PIII HP Kayak XAs (dmesg attached
> below) running Debian 3.1 r2 and kernel-image-2 2.6.8-16sarge4.
> 
> Could you please elaborate, how could I use APM instead of ACPI?
> 
> Regards
> Alex

My understanding is that APM is not compatible with SMP boxes.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: (Solved) Re: why sarge can't power off PC

[Alexander Farber]

Hello,

I have same problem with my dual-PIII HP Kayak XAs (dmesg attached
below) running Debian 3.1 r2 and kernel-image-2 2.6.8-16sarge4.

Could you please elaborate, how could I use APM instead of ACPI?

Regards
Alex

--
http://preferans.de

On 8/8/06, Serena Cantor <[EMAIL PROTECTED]> wrote:

You are right. My PC is old, I try apm, it works!

--- Colin <[EMAIL PROTECTED]> wrote:

> Serena Cantor wrote:
> > Every time I shutdown, I have to unplug power
> cord.
> > Other distro, such as mandrake can poweroff.
> >
> > How should I do? Thanks!
>
> This is usually a problem with computer made before
> 2001 (Pentium 3 and
> older).  In these cases you have to use apm instead
> of acpi.



Linux version 2.6.8-3-686-smp ([EMAIL PROTECTED]) (gcc version 3.3.5 (Debian 
1:3.3.5-13)
) #1 SMP Sat Jul 15 08:52:57 UTC 2006
BIOS-provided physical RAM map:
BIOS-e820:  - 0009f000 (usable)
BIOS-e820: 0009f000 - 000a (reserved)
BIOS-e820: 000f - 0010 (reserved)
BIOS-e820: 0010 - 2000 (usable)
BIOS-e820: fec0 - fec1 (reserved)
BIOS-e820: fee0 - fee01000 (reserved)
BIOS-e820:  - 0001 (reserved)
0MB HIGHMEM available.
512MB LOWMEM available.
found SMP MP-table at 000f70a0
On node 0 totalpages: 131072
 DMA zone: 4096 pages, LIFO batch:1
 Normal zone: 126976 pages, LIFO batch:16
 HighMem zone: 0 pages, LIFO batch:1
DMI not present.
ACPI: Unable to locate RSDP
Intel MultiProcessor Specification v1.4
   Virtual Wire compatibility mode.
OEM ID: HP   Product ID: XU/XWAPIC at: 0xFEE0
Processor #1 6:7 APIC version 17
Processor #0 6:7 APIC version 17
I/O APIC #2 Version 17 at 0xFEC0.
Enabling APIC mode:  Flat.  Using 1 I/O APICs
Processors: 2
Built 1 zonelists
Kernel command line: root=/dev/sda1 ro
Initializing CPU#0
PID hash table entries: 4096 (order 12: 32768 bytes)
Detected 547.636 MHz processor.
Using tsc for high-res timesource
Console: colour VGA+ 80x25
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 510784k/524288k available (1665k kernel code, 12724k reserved, 771k data
, 168k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay loop... 1081.34 BogoMIPS
Security Scaffold v1.0.0 initialized
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: After generic identify, caps: 0383fbff   
CPU: After vendor identify, caps:  0383fbff   
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 512K
CPU: After all inits, caps:0383fbff   0040
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
CPU0: Intel Pentium III (Katmai) stepping 03
per-CPU timeslice cutoff: 1462.36 usecs.
task migration cache decay timeout: 2 msecs.
enabled ExtINT on CPU#0
ESR value before enabling vector: 
ESR value after enabling vector: 
Booting processor 1/0 eip 3000
Initializing CPU#1
masked ExtINT on CPU#1
ESR value before enabling vector: 
ESR value after enabling vector: 
Calibrating delay loop... 1093.63 BogoMIPS
CPU: After generic identify, caps: 0383fbff   
CPU: After vendor identify, caps:  0383fbff   
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 512K
CPU: After all inits, caps:0383fbff   0040
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#1.
CPU1: Intel Pentium III (Katmai) stepping 03
Total of 2 processors activated (2174.97 BogoMIPS).
ENABLING IO-APIC IRQs
Setting 2 in the phys_id_present_map
...changing IO-APIC physical APIC ID to 2 ... ok.
init IO_APIC IRQs
IO-APIC (apicid-pin) 2-0, 2-9, 2-11, 2-16, 2-20, 2-21, 2-22, 2-23 not connected
.
..TIMER: vector=0x31 pin1=2 pin2=0
number of MP IRQ sources: 18.
number of IO-APIC #2 registers: 24.
testing the IO APIC...
IO APIC #2..
 register #00: 0200
...: physical APIC id: 02
...: Delivery Type: 0
...: LTS  : 0
 register #01: 00170011
... : max redirection entries: 0017
... : PRQ implemented: 0
... : IO APIC version: 0011
 register #02: 
... : arbitration: 00
 IRQ redirection table:
NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
00 000 00  100   0   00000
01 001 01  000   0   01139
02 001 01  000   0   01131
03 001 01  000   0   01141
04 001 01  000   0   01149
05 001 01  000   0   01151
06 001 01  000   0   01159
07 001

Re: why sarge can't power off PC

[Liam O'Toole]

On Wed, 09 Aug 2006 06:49:15 +0100
Wulfy <[EMAIL PROTECTED]> wrote:

> Florian Kulzer wrote:
> > On Tue, Aug 08, 2006 at 23:27:06 +0100, Wulfy wrote:
> >   
> >> Further to the last e-mail:
> >>
> >> I removed apm using aptitude, it removed libapm0 and
> >> powermgmt-base as well.  Then I checked in my BIOS setup and
> >> there's no mention anywhere of apm though acpi defaults to S1 (I
> >> think that's "shutdown" as opposed to "sleep" or "suspend").
> >>
> >> Yet I find in my log:
> >>
> >> Aug  8 19:22:35 localhost kernel: apm: BIOS version 1.2 Flags 0x03
> >> (Driver version 1.16ac)
> >> Aug  8 19:22:35 localhost kernel: apm: overridden by ACPI.
> >> Aug  8 19:23:50 localhost kernel: apm: BIOS version 1.2 Flags 0x03
> >> (Driver version 1.16ac)
> >> Aug  8 19:23:50 localhost kernel: apm: overridden by ACPI.
> >>
> >> and apm.ko is
> >> at /lib/modules/2.6.8-3-k7/kernel/arch/i386/kernel/apm.ko .
> >>
> >> Should it not have been removed with the other apm-related bits?
> >> 
> >
> > apm.ko is the kernel module which contains the APM routines. As
> > such it is part of the kernel-image-2.6.8-3-k7 package.  Removing
> > the apm daemon and apm-related library/tools packages does not (and
> > should not) result in the removal of kernel modules.
> >   
> Ah.  I should have realised.  I feel silly...  :)
> 
> I was surprised it appeared in the logs, though.  It does not appear
> in lsmod.

The log messages are telling you that apm is yielding to acpi, and
the former gives up and goes home. Hence no entry in the output of
lsmod.

> >> The only thing in Control  Centre under Power Control is Laptop 
> >> Battery.  It reports:
> >>
> >> Your computer seems to have a partial ACPI installation. ACPI was 
> >> probably enabled, but some of the sub-options were not - you need
> >> to enable at least 'AC Adaptor' and 'Control Method Battery' and
> >> then rebuild your kernel.
> >>
> >> Should there be more under Power Control?  If so, how do I get it
> >> there? 
> >
> > Try to modprobe "ac", "power" and "battery" and check if that makes
> > any difference.
> acpi-related modules in lsmod;
> 
> thermal12816  0
> fan 4044  0
> button  6360  0
> processor  17392  1 thermal
> ac  4876  0
> battery 9484  0
> 
> Two of them are there.  I modprobed power...
> 
> Yewdales-lodge:~# modprobe power
> FATAL: Module power not found.
> 

I don't know of a module called 'power'. Try this command to find
power-related modules:

find /lib/modules/$(uname-r) -name *power*

-- 

Liam


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: why sarge can't power off PC

[Mike McCarty]

Wulfy wrote:


I have one 80GiB(? new units I think?) HD and a CDROM.  nVidia video 
card.  There's not a lot attached...  I hope it's not power supply 
related...  :(


Is there any way to check the power supply's wattage without opening the 
case?


Possibly. Look in the back where the power cable plugs into
the power supply. There may be a sticker there which gives
some information.

Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: why sarge can't power off PC

[Mike McCarty]

Wulfy wrote:

Mike McCarty wrote:


Wulfy wrote:



I have a similar problem.  During the recent very hot weather here in 
the UK, my box kept crashing.  So I had to reboot a lot.  I noticed that 



Define "very hot weather". We've been two weeks now hitting a high
over 100F (38C) here in Texas.

[snip]

Mike


Somewhere in the 90s F with 85% humidity?  Cool for you but very hot, as 
in people were dying, here...  The humidity did go down to 18%, an 
unprecedented low figure, In my experience. for a day.  Being an island, 
our humidity is normally >50%...


Ouch. Yes, the humidity makes a difference. We have people dying
here as well. Perhaps 18 or so so far. I used to live near Houston,
Texas, and often the humidity and temperature would be the same.
I know just how it feels. You have my sympathy.

Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: why sarge can't power off PC

[Wulfy]

Andrew Sackville-West wrote:

On Tue, Aug 08, 2006 at 04:46:39PM -0700, Paul Johnson wrote:
  

On Tuesday 08 August 2006 11:39, Wulfy wrote:



I have a similar problem.  During the recent very hot weather here in
the UK, my box kept crashing.  So I had to reboot a lot.  I noticed that
when I hit the power switch, it didn't always "catch", the power supply
and fan started but the boot sequence didn't start.  I had to power off
and on again.  Then for some routine maintenance, when I shut the
machine down, it didn't power off...  just to the black screen and the
fans still running.  When I reboot, it gets to the point of the keyboard
lights flashing then stops screen powered down (light flashing rather
than on) and I have to power off with the switch and power on again.
  
Power supply can't provide enough juice to get started.  I should seriously 
consider replacing that power supply with something with 50w or 100w more 
maximum output to get around that.  Replacing the power supply will also make 
the components last longer:  I've seen machines give up the ghost from trying 
to power on with too little juice too many times.


I have a feeling your situation has more to do with a hardware addition that 
happened or an aging power supply rather than a kernel upgrade.





I've also seen very similar behavior from a failing
motherboard. intermittent crashing, failing to POST and boot on power
up etc. all of it intermittent and unpredictable. finally it wouldn't
POST at all... process of elimination gets me a new
motherboard. weee...


A
  

Thanks for answering, Paul and Andrew.

I have one 80GiB(? new units I think?) HD and a CDROM.  nVidia video 
card.  There's not a lot attached...  I hope it's not power supply 
related...  :(


Is there any way to check the power supply's wattage without opening the 
case?


--
Blessings

Wulfmann

Wulf Credo:
Respect the elders. Teach the young. Co-operate with the pack. 
Play when you can. Hunt when you must. Rest in between.

Share your affections. Voice your opinion. Leave your Mark.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: why sarge can't power off PC

[Wulfy]

Florian Kulzer wrote:

On Tue, Aug 08, 2006 at 23:27:06 +0100, Wulfy wrote:
  

Further to the last e-mail:

I removed apm using aptitude, it removed libapm0 and powermgmt-base as 
well.  Then I checked in my BIOS setup and there's no mention anywhere 
of apm though acpi defaults to S1 (I think that's "shutdown" as opposed 
to "sleep" or "suspend").


Yet I find in my log:

Aug  8 19:22:35 localhost kernel: apm: BIOS version 1.2 Flags 0x03 (Driver 
version 1.16ac)

Aug  8 19:22:35 localhost kernel: apm: overridden by ACPI.
Aug  8 19:23:50 localhost kernel: apm: BIOS version 1.2 Flags 0x03 (Driver 
version 1.16ac)

Aug  8 19:23:50 localhost kernel: apm: overridden by ACPI.

and apm.ko is at /lib/modules/2.6.8-3-k7/kernel/arch/i386/kernel/apm.ko .

Should it not have been removed with the other apm-related bits?



apm.ko is the kernel module which contains the APM routines. As such it
is part of the kernel-image-2.6.8-3-k7 package.  Removing the apm daemon
and apm-related library/tools packages does not (and should not) result
in the removal of kernel modules.
  

Ah.  I should have realised.  I feel silly...  :)

I was surprised it appeared in the logs, though.  It does not appear in 
lsmod.
The only thing in Control  Centre under Power Control is Laptop 
Battery.  It reports:


Your computer seems to have a partial ACPI installation. ACPI was 
probably enabled, but some of the sub-options were not - you need to 
enable at least 'AC Adaptor' and 'Control Method Battery' and then 
rebuild your kernel.


Should there be more under Power Control?  If so, how do I get it there?



Try to modprobe "ac", "power" and "battery" and check if that makes any
difference.

acpi-related modules in lsmod;

thermal12816  0
fan 4044  0
button  6360  0
processor  17392  1 thermal
ac  4876  0
battery 9484  0

Two of them are there.  I modprobed power...

Yewdales-lodge:~# modprobe power
FATAL: Module power not found.



--
Blessings

Wulfmann

Wulf Credo:
Respect the elders. Teach the young. Co-operate with the pack. 
Play when you can. Hunt when you must. Rest in between.

Share your affections. Voice your opinion. Leave your Mark.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: why sarge can't power off PC

[Wulfy]

Mike McCarty wrote:

Wulfy wrote:


I have a similar problem.  During the recent very hot weather here in 
the UK, my box kept crashing.  So I had to reboot a lot.  I noticed that 


Define "very hot weather". We've been two weeks now hitting a high
over 100F (38C) here in Texas.

[snip]

Mike
Somewhere in the 90s F with 85% humidity?  Cool for you but very hot, as 
in people were dying, here...  The humidity did go down to 18%, an 
unprecedented low figure, In my experience. for a day.  Being an island, 
our humidity is normally >50%...


--
Blessings

Wulfmann

Wulf Credo:
Respect the elders. Teach the young. Co-operate with the pack. 
Play when you can. Hunt when you must. Rest in between.

Share your affections. Voice your opinion. Leave your Mark.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: why sarge can't power off PC

[Andrew Sackville-West]

On Tue, Aug 08, 2006 at 04:46:39PM -0700, Paul Johnson wrote:
> On Tuesday 08 August 2006 11:39, Wulfy wrote:
> 
> > I have a similar problem.  During the recent very hot weather here in
> > the UK, my box kept crashing.  So I had to reboot a lot.  I noticed that
> > when I hit the power switch, it didn't always "catch", the power supply
> > and fan started but the boot sequence didn't start.  I had to power off
> > and on again.  Then for some routine maintenance, when I shut the
> > machine down, it didn't power off...  just to the black screen and the
> > fans still running.  When I reboot, it gets to the point of the keyboard
> > lights flashing then stops screen powered down (light flashing rather
> > than on) and I have to power off with the switch and power on again.
> 
> Power supply can't provide enough juice to get started.  I should seriously 
> consider replacing that power supply with something with 50w or 100w more 
> maximum output to get around that.  Replacing the power supply will also make 
> the components last longer:  I've seen machines give up the ghost from trying 
> to power on with too little juice too many times.
> 
> I have a feeling your situation has more to do with a hardware addition that 
> happened or an aging power supply rather than a kernel upgrade.
> 

I've also seen very similar behavior from a failing
motherboard. intermittent crashing, failing to POST and boot on power
up etc. all of it intermittent and unpredictable. finally it wouldn't
POST at all... process of elimination gets me a new
motherboard. weee...


A


signature.asc
Description: Digital signature

Re: why sarge can't power off PC

[Paul Johnson]

On Tuesday 08 August 2006 11:39, Wulfy wrote:

> I have a similar problem.  During the recent very hot weather here in
> the UK, my box kept crashing.  So I had to reboot a lot.  I noticed that
> when I hit the power switch, it didn't always "catch", the power supply
> and fan started but the boot sequence didn't start.  I had to power off
> and on again.  Then for some routine maintenance, when I shut the
> machine down, it didn't power off...  just to the black screen and the
> fans still running.  When I reboot, it gets to the point of the keyboard
> lights flashing then stops screen powered down (light flashing rather
> than on) and I have to power off with the switch and power on again.

Power supply can't provide enough juice to get started.  I should seriously 
consider replacing that power supply with something with 50w or 100w more 
maximum output to get around that.  Replacing the power supply will also make 
the components last longer:  I've seen machines give up the ghost from trying 
to power on with too little juice too many times.

I have a feeling your situation has more to do with a hardware addition that 
happened or an aging power supply rather than a kernel upgrade.

-- 
Paul Johnson
Email and IM (XMPP & Google Talk): [EMAIL PROTECTED]
Jabber: Because it's time to move forward  http://ursine.ca/Ursine:Jabber


pgpdbRqM1xK5C.pgp
Description: PGP signature

Re: why sarge can't power off PC

[Paul Johnson]

On Tuesday 08 August 2006 00:07, Serena Cantor wrote:
> Every time I shutdown, I have to unplug power cord.

Or you could hold the power button down for four seconds after it says System 
Halted.

> Other distro, such as mandrake can poweroff.

Same with Debian.  Make sure apm is turned on.

-- 
Paul Johnson
Email and IM (XMPP & Google Talk): [EMAIL PROTECTED]
Jabber: Because it's time to move forward  http://ursine.ca/Ursine:Jabber


pgpTyhdOLwLDy.pgp
Description: PGP signature

Re: why sarge can't power off PC

[Florian Kulzer]

On Tue, Aug 08, 2006 at 23:27:06 +0100, Wulfy wrote:
> Liam O'Toole wrote:
> >I suspect that the kernel has acpi enabled. You can check by seeing 
> >if the directory /proc/acpi exists and is populated. To use apm,
> >you will need to disable acpi. You do this by passing the argument
> >'acpi=off' to the kernel, either on the grub command line or in the
> >grub configuration file, /boot/grub/menu.lst. (I'm assuming that you
> >use grub; with lilo the procedure is similar.)
> First.  Thanks for your help so far.
> 
> Further to the last e-mail:
> 
> I removed apm using aptitude, it removed libapm0 and powermgmt-base as 
> well.  Then I checked in my BIOS setup and there's no mention anywhere 
> of apm though acpi defaults to S1 (I think that's "shutdown" as opposed 
> to "sleep" or "suspend").
> 
> Yet I find in my log:
> 
> Aug  8 19:22:35 localhost kernel: apm: BIOS version 1.2 Flags 0x03 (Driver 
> version 1.16ac)
> Aug  8 19:22:35 localhost kernel: apm: overridden by ACPI.
> Aug  8 19:23:50 localhost kernel: apm: BIOS version 1.2 Flags 0x03 (Driver 
> version 1.16ac)
> Aug  8 19:23:50 localhost kernel: apm: overridden by ACPI.
> 
> and apm.ko is at /lib/modules/2.6.8-3-k7/kernel/arch/i386/kernel/apm.ko .
> 
> Should it not have been removed with the other apm-related bits?

apm.ko is the kernel module which contains the APM routines. As such it
is part of the kernel-image-2.6.8-3-k7 package.  Removing the apm daemon
and apm-related library/tools packages does not (and should not) result
in the removal of kernel modules.

> The only thing in Control  Centre under Power Control is Laptop 
> Battery.  It reports:
> 
> Your computer seems to have a partial ACPI installation. ACPI was 
> probably enabled, but some of the sub-options were not - you need to 
> enable at least 'AC Adaptor' and 'Control Method Battery' and then 
> rebuild your kernel.
> 
> Should there be more under Power Control?  If so, how do I get it there?

Try to modprobe "ac", "power" and "battery" and check if that makes any
difference.

-- 
Regards,
  Florian


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: why sarge can't power off PC

[Mike McCarty]

Wulfy wrote:


I have a similar problem.  During the recent very hot weather here in 
the UK, my box kept crashing.  So I had to reboot a lot.  I noticed that 


Define "very hot weather". We've been two weeks now hitting a high
over 100F (38C) here in Texas.

[snip]

Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: why sarge can't power off PC

[Wulfy]

Liam O'Toole wrote:
I suspect that the kernel has acpi enabled. You can check by seeing 
if the directory /proc/acpi exists and is populated. To use apm,

you will need to disable acpi. You do this by passing the argument
'acpi=off' to the kernel, either on the grub command line or in the
grub configuration file, /boot/grub/menu.lst. (I'm assuming that you
use grub; with lilo the procedure is similar.)

First.  Thanks for your help so far.

Further to the last e-mail:

I removed apm using aptitude, it removed libapm0 and powermgmt-base as 
well.  Then I checked in my BIOS setup and there's no mention anywhere 
of apm though acpi defaults to S1 (I think that's "shutdown" as opposed 
to "sleep" or "suspend").


Yet I find in my log:

Aug  8 19:22:35 localhost kernel: apm: BIOS version 1.2 Flags 0x03 (Driver 
version 1.16ac)
Aug  8 19:22:35 localhost kernel: apm: overridden by ACPI.
Aug  8 19:23:50 localhost kernel: apm: BIOS version 1.2 Flags 0x03 (Driver 
version 1.16ac)
Aug  8 19:23:50 localhost kernel: apm: overridden by ACPI.

and apm.ko is at /lib/modules/2.6.8-3-k7/kernel/arch/i386/kernel/apm.ko .

Should it not have been removed with the other apm-related bits?

The only thing in Control  Centre under Power Control is Laptop 
Battery.  It reports:


Your computer seems to have a partial ACPI installation. ACPI was 
probably enabled, but some of the sub-options were not - you need to 
enable at least 'AC Adaptor' and 'Control Method Battery' and then 
rebuild your kernel.


Should there be more under Power Control?  If so, how do I get it there?

Most of my googling has brought up either laptop stuff or installation 
on 2.4 series kernels.


--
Blessings

Wulfmann

Wulf Credo:
Respect the elders. Teach the young. Co-operate with the pack. 
Play when you can. Hunt when you must. Rest in between.

Share your affections. Voice your opinion. Leave your Mark.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: why sarge can't power off PC

[Wulfy]

Liam O'Toole wrote:

On Tue, 08 Aug 2006 19:39:59 +0100
Wulfy <[EMAIL PROTECTED]> wrote:

  
I have a similar problem.  During the recent very hot weather here in 
the UK, my box kept crashing.  



Not something we have to worry about very often :-)
  

True! :)

[...]

  

I followed the above instructions and this is the result;

Yewdales-lodge:~# modprobe apm power_off=1
FATAL: Error inserting apm 
(/lib/modules/2.6.8-3-k7/kernel/arch/i386/kernel/apm.ko): No such

device [The file, apm.ko, is there, I checked.]
Yewdales-lodge:~# apm
No APM support in kernel




[...]

I suspect that the kernel has acpi enabled. You can check by seeing 
if the directory /proc/acpi exists and is populated. To use apm,

you will need to disable acpi. You do this by passing the argument
'acpi=off' to the kernel, either on the grub command line or in the
grub configuration file, /boot/grub/menu.lst. (I'm assuming that you
use grub; with lilo the procedure is similar.)
Yes, acpi is there.  Is there a way to use it to restore my 
power-down/reboot stuff?  There doesn't seem to be a man page for it.


--
Blessings

Wulfmann

Wulf Credo:
Respect the elders. Teach the young. Co-operate with the pack. 
Play when you can. Hunt when you must. Rest in between.

Share your affections. Voice your opinion. Leave your Mark.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: why sarge can't power off PC

[Liam O'Toole]

On Tue, 08 Aug 2006 19:39:59 +0100
Wulfy <[EMAIL PROTECTED]> wrote:

> Liam O'Toole wrote:
> > On Tue, 8 Aug 2006 00:53:29 -0700 (PDT)
> > Serena Cantor <[EMAIL PROTECTED]> wrote:
> >
> >   
> >> Thanks! I use sarge's default kernel, 2.4.
> >>
> >> It seems that I would wait for Debian 4.0, which use
> >> kernel 2.6, in Dec, 2006
> >> 
> >
> > APM (Advanced Power Management) should work with that kernel. Is the
> > apm module already loaded? What is the output of 'lsmod | grep
> > apm'?
> >
> > If the module is not loaded, run the command 'modprobe apm
> > power_off=1'. Add the line 'apm power_off=1' to /etc/modules so that
> > the module will be loaded automatically the next time you boot.
> I have a similar problem.  During the recent very hot weather here in 
> the UK, my box kept crashing.  

Not something we have to worry about very often :-)

[...]

> 
> I followed the above instructions and this is the result;
> 
> Yewdales-lodge:~# modprobe apm power_off=1
> FATAL: Error inserting apm 
> (/lib/modules/2.6.8-3-k7/kernel/arch/i386/kernel/apm.ko): No such
> device [The file, apm.ko, is there, I checked.]
> Yewdales-lodge:~# apm
> No APM support in kernel
> 

[...]

I suspect that the kernel has acpi enabled. You can check by seeing 
if the directory /proc/acpi exists and is populated. To use apm,
you will need to disable acpi. You do this by passing the argument
'acpi=off' to the kernel, either on the grub command line or in the
grub configuration file, /boot/grub/menu.lst. (I'm assuming that you
use grub; with lilo the procedure is similar.)

-- 

Liam


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: why sarge can't power off PC

[Wulfy]

Liam O'Toole wrote:

On Tue, 8 Aug 2006 00:53:29 -0700 (PDT)
Serena Cantor <[EMAIL PROTECTED]> wrote:

  

Thanks! I use sarge's default kernel, 2.4.

It seems that I would wait for Debian 4.0, which use
kernel 2.6, in Dec, 2006



APM (Advanced Power Management) should work with that kernel. Is the
apm module already loaded? What is the output of 'lsmod | grep
apm'?

If the module is not loaded, run the command 'modprobe apm
power_off=1'. Add the line 'apm power_off=1' to /etc/modules so that
the module will be loaded automatically the next time you boot.
I have a similar problem.  During the recent very hot weather here in 
the UK, my box kept crashing.  So I had to reboot a lot.  I noticed that 
when I hit the power switch, it didn't always "catch", the power supply 
and fan started but the boot sequence didn't start.  I had to power off 
and on again.  Then for some routine maintenance, when I shut the 
machine down, it didn't power off...  just to the black screen and the 
fans still running.  When I reboot, it gets to the point of the keyboard 
lights flashing then stops screen powered down (light flashing rather 
than on) and I have to power off with the switch and power on again.


It used to work at one time, I believe before I installed the k7 version 
of 2.6.8 - I'd had the 686 version before.


I followed the above instructions and this is the result;

Yewdales-lodge:~# modprobe apm power_off=1
FATAL: Error inserting apm 
(/lib/modules/2.6.8-3-k7/kernel/arch/i386/kernel/apm.ko): No such device

[The file, apm.ko, is there, I checked.]
Yewdales-lodge:~# apm
No APM support in kernel

Any ideas how to get it back?  The only things I can think of is some 
change in my BIOS or a udev problem...  of course, it's really something 
of a mystery to me, so I could be wrong.  If you need more info, please ask.


My processor is an AMD Duron 1GHz.

Yewdales-lodge:~# uname -a
Linux Yewdales-lodge 2.6.8-3-k7 #1 Sat Jul 15 09:58:38 UTC 2006 i686 
GNU/Linux




--
Blessings

Wulfmann

Wulf Credo:
Respect the elders. Teach the young. Co-operate with the pack. 
Play when you can. Hunt when you must. Rest in between.

Share your affections. Voice your opinion. Leave your Mark.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: why sarge can't power off PC

[Johannes Wiedersich]

Serena Cantor wrote:

I installed kernel 2.6 in the past, it has many
problems. Thanks to other nice guys, the problem is
solved. Thanks anyway!


> You are right. My PC is old, I try apm, it works!

Maybe your kernel 2.6 problems will be gone as well on using apm?
Just guessing, but you could try.

Johannes


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]