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
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
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
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 n
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
> > > up
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
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
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.
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.LP
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.
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
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 inact
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
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
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 wo
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
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 ex
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
===
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 defau
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
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?
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
Miroslav Skoric wrote:
> That did not happen in Wheezy. Any idea?
it is not a bug, it is a feature :)
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
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
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
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
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.
>
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
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
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. Occasion
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 Jes
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.
I
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.
>
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&qu
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
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 debia
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
resume), 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
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 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 (stre
. 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
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", DR
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
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
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 "unsubscr
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
r 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 n
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
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
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
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 t
-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
f 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 rel
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 t
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 o
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
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 wi
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
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 fa
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 wa
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
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
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
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 Prec
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
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.
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 b
> 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 pr
. 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 a
ot; 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]
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 lap
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 lap
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
>
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 diff
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
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 /l
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
[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
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/c
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 moth
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 J
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
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:
Y
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 i
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 cab
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.
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 a
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 th
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
Som
n 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..
nd 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 th
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.
--
Pa
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'
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(){pr
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 con
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 abo
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 u
e 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'
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
1 - 100 of 378 matches
Mail list logo
