Hi guys, I'd like to ask you a couple of things regarding my core 6 install. How do I shut it down? I mean, completely power off? Rebooting is not a problem, but when I choose shutdown, it stops everything, and then says "system halted" and that's it. I believe it even puts to sleep the hard drive, but the computer is still on. What should I do? The second one is about VmWare, during the install it can't find the kernel c headers, and I have no idea where they are. Where are they? By the way, I have the 64 version for pc. Many many thanks! Jessica
_________________________________________________________________ Need a break? Find your escape route with Live Search Maps. http://maps.live.com/?icid=hmtag3
JJ JJ wrote:
Hi guys, I'd like to ask you a couple of things regarding my core 6 install. How do I shut it down? I mean, completely power off? Rebooting is not a problem, but when I choose shutdown, it stops everything, and then says "system halted" and that's it. I believe it even puts to sleep the hard drive, but the computer is still on. What should I do?
Hi ! I didn't face this problem till now. I have added the shutdown button to my panel and when I click it, it asks for shutdown,reboot etc. I click for shutdown and it is perfect. Maybe you can see the power manager settings.
The second one is about VmWare, during the install it can't find the kernel c headers, and I have no idea where they are. Where are they?
I believe you get them when you install the kernel-devel package which doesn't get installed by default. Check the /lib/modules/<uname -r> directory with a ls -l option. If the build doesn't point to anything, then the kernel-devel package is not installed. Install it along with kernel-headers and glibc and gcc headers. Hopefully this will solve your problems. Thats all I can figure out now.
By the way, I have the 64 version for pc. Many many thanks! Jessica
Need a break? Find your escape route with Live Search Maps. http://maps.live.com/?icid=hmtag3
Thanks and regards, Amit.
On 4/23/07, JJ JJ jj28h@hotmail.com wrote:
Hi guys, I'd like to ask you a couple of things regarding my core 6 install. How do I shut it down? I mean, completely power off? Rebooting is not a problem, but when I choose shutdown, it stops everything, and then says "system halted" and that's it. I believe it even puts to sleep the hard drive, but the computer is still on. What should I do?
For now, push the power button. You need to have the proper kernel configuration for your hardware. Since you make no mention of what you have there is not much we can tell you.
The second one is about VmWare, during the install it can't find the kernel c headers, and I have no idea where they are. Where are they?
You need to install the kernel-devel package.
By the way, I have the 64 version for pc.
Insufficient data. You can do better. Use "uname -a" from command line/terminal.
Many many thanks! Jessica
JJ JJ wrote:
Hi guys, I'd like to ask you a couple of things regarding my core 6 install. How do I shut it down? I mean, completely power off? Rebooting is not a problem, but when I choose shutdown, it stops everything, and then says "system halted" and that's it. I believe it even puts to sleep the hard drive, but the computer is still on. What should I do?
There is a command "/usr/bin/poweroff". Depending on your board and BIOS, it can poweroff your machine.
The second one is about VmWare, during the install it can't find the kernel c headers, and I have no idea where they are. Where are they? By the way, I have the 64 version for pc. Many many thanks! Jessica
Need a break? Find your escape route with Live Search Maps. http://maps.live.com/?icid=hmtag3
On Mon, 2007-04-23 at 23:17 -0700, JJ JJ wrote:
I'd like to ask you a couple of things regarding my core 6 install. How do I shut it down? I mean, completely power off? Rebooting is not a problem, but when I choose shutdown, it stops everything, and then says "system halted" and that's it. I believe it even puts to sleep the hard drive, but the computer is still on. What should I do?
You might need to play with BIOS options regarding enabling/disabling of ACPI. You might need to play with kernel options regarding ACPI and APM. Install the "kernel-doc" package, and read the kernel-parameters file for what you can do.
less /usr/share/doc/kernel-doc*/Documentation/kernel-parameters.txt
(Or find a copy on-line somewhere, and read it off the web.)
On Mon, 2007-04-23 at 23:17 -0700, JJ JJ wrote:
Hi guys, I'd like to ask you a couple of things regarding my core 6 install. How do I shut it down? I mean, completely power off? Rebooting is not a problem, but when I choose shutdown, it stops everything, and then says "system halted" and that's it. I believe it even puts to sleep the hard drive, but the computer is still on. What should I do? The second one is about VmWare, during the install it can't find the kernel c headers, and I ^ and older hardware.
1. Check that ACPI is on in your BIOS 2. check that the init.d script acpid is running 3. after boot do a grep on dmesg for lines with ACPI or acpi. In my case it told me to add the kernel parameter lacpi to the kernel line in grub.conf and that worked. YMMV
By the way poweroff is not the answer
Hello everybody, Jessica again. Ok, this is what I got from the term for kernel: Linux localhost.localdomain 2.6.20-1.2944.fc6xen #1 SMP Tue Apr 10 18:03:37 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux Also, I found the command poweroff in the bin dir like someone told me. I run it, but still the same. System halted, and that's it. Computer still on. I'd like to mention that I have 2 copies of Windows on this rig, and they both shutdown just fine, so I don't think I have to look in the bios settings. I also forgot to mention that this is my first experience with linux, but I believe you've realized it by now. What should I do now? Thanks again, JJ
On 4/23/07, JJ JJ jj28h@hotmail.com wrote:
Hi guys, I'd like to ask you a couple of things regarding my core 6 install. How do I shut it down? I mean, completely power off? Rebooting is not a problem, but when I choose shutdown, it stops everything, and then says "system halted" and that's it. I believe it even puts to sleep the hard drive, but the computer is still on. What should I do?
For now, push the power button. You need to have the proper kernel configuration for your hardware. Since you make no mention of what you have there is not much we can tell you.
The second one is about VmWare, during the install it can't find the kernel c headers, and I have no idea where they are. Where are they?
You need to install the kernel-devel package.
By the way, I have the 64 version for pc.
Insufficient data. You can do better. Use "uname -a" from command line/terminal.
Many many thanks! Jessica
_________________________________________________________________ Interest Rates NEAR 39yr LOWS! $430,000 Mortgage for $1,299/mo - Calculate new payment http://www.lowermybills.com/lre/index.jsp?sourceid=lmb-9632-19132&moid=1...
On 4/24/07, JJ JJ jj28h@hotmail.com wrote:
Hello everybody, Jessica again. Ok, this is what I got from the term for kernel: Linux localhost.localdomain 2.6.20-1.2944.fc6xen #1 SMP Tue Apr 10 18:03:37 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux Also, I found the command poweroff in the bin dir like someone told me. I run it, but still the same. System halted, and that's it. Computer still on. I'd like to mention that I have 2 copies of Windows on this rig, and they both shutdown just fine, so I don't think I have to look in the bios settings. I also forgot to mention that this is my first experience with linux, but I believe you've realized it by now. What should I do now? Thanks again, JJ
Have you tried Aaron's suggestions? Whether or not #1 applies, #2 should be true and it's possible #3 (dmesg | grep -i acpi) could help you diagnose the problem.
In my experience, you should be able to add a parameter to grub.conf to get a full shutdown - but that parameter's going to vary based on your hardware.
Chris
On 4/24/07, Chris Mohler cr33dog@gmail.com wrote:
On 4/24/07, JJ JJ jj28h@hotmail.com wrote:
Hello everybody, Jessica again. Ok, this is what I got from the term for kernel: Linux localhost.localdomain 2.6.20-1.2944.fc6xen #1 SMP Tue Apr 10 18:03:37 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux Also, I found the command poweroff in the bin dir like someone told me. I run it, but still the same. System halted, and that's it. Computer still on. I'd like to mention that I have 2 copies of Windows on this rig, and they both shutdown just fine, so I don't think I have to look in the bios settings. I also forgot to mention that this is my first experience with linux, but I believe you've realized it by now. What should I do now? Thanks again, JJ
Have you tried Aaron's suggestions? Whether or not #1 applies, #2 should be true and it's possible #3 (dmesg | grep -i acpi) could help you diagnose the problem.
In my experience, you should be able to add a parameter to grub.conf to get a full shutdown - but that parameter's going to vary based on your hardware.
Chris
OK, you have a AMD64 compatible computer running the XEN (virtualization enabled) version of the kernel. What happens if you choose the non-xen kernel? (By the way, you do not need to run VMware under the XEN kernel.)
On Tue, 2007-04-24 at 14:41 -0700, JJ JJ wrote:
I'd like to mention that I have 2 copies of Windows on this rig, and they both shutdown just fine, so I don't think I have to look in the bios settings.
I wouldn't say that. There's different ways of powering down a system, and you may have to tweak the BIOS to suit both OSs. Been there, done that, myself, with a couple of dual boot PCs.
If you get desperate, you can reboot instead of try to shut down, and use GRUB to power off the PC. Stick the following below your kernel choices lines in the grub.conf file:
title switch off halt
Depending on your motherboard, you might have to try:
title switch off halt --no-apm
On 4/24/07, JJ JJ jj28h@hotmail.com wrote:
Hi guys, I'd like to ask you a couple of things regarding my core 6 install. How do I shut it down? I mean, completely power off? Rebooting is not a problem, but when I choose shutdown, it stops everything, and then says "system halted" and that's it. I believe it even puts to sleep the hard drive, but the computer is still on. What should I do?
Push the power button after that and it will turn off. Linux is shut down (completely), it just failed to tell the motherboard/PSU to turn off. This is an issue with ACPI (the fact that Windows works is irrelevant). Begin looking for ACPI messages in /var/log/messages as others have suggested. Run this command as root: grep -i acpi /var/log/messages
Jonathan
Hi again, a quick note to show you the log of yesterday session:
Apr 24 23:21:57 localhost kernel: ACPI: PCI Interrupt 0000:02:0a.0[A] -> GSI 17 (level, low) -> IRQ 17 Apr 24 23:21:57 localhost kernel: ACPI: PCI Interrupt 0000:02:09.0[A] -> GSI 16 (level, low) -> IRQ 16 Apr 24 23:21:57 localhost kernel: ACPI: PCI Interrupt 0000:00:07.5[B] -> GSI 17 (level, low) -> IRQ 17 Apr 24 23:21:57 localhost kernel: ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16 Apr 24 23:21:57 localhost kernel: ACPI: Power Button (FF) [PWRF] Apr 24 23:21:57 localhost kernel: ACPI: Power Button (CM) [PWRB] Apr 24 23:21:57 localhost kernel: ibm_acpi: ec object not found
and a whole lot of other lines before that. So, maybe I have to check the bios....a task that I dread! Regarding VmWare, I saw the Virtual Machine Manager, but it can only perform network installations (right?), and I've never done those. Any good tutorial around that can teach me? JJ
On 4/24/07, JJ JJ jj28h@hotmail.com wrote:
Hi guys, I'd like to ask you a couple of things regarding my core 6 install. How do I shut it down? I mean, completely power off? Rebooting is not a problem, but when I choose shutdown, it stops everything, and then says "system halted" and that's it. I believe it even puts to sleep the hard drive, but the computer is still on. What should I do?
Push the power button after that and it will turn off. Linux is shut down (completely), it just failed to tell the motherboard/PSU to turn off. This is an issue with ACPI (the fact that Windows works is irrelevant). Begin looking for ACPI messages in /var/log/messages as others have suggested. Run this command as root: grep -i acpi /var/log/messages
Jonathan
_________________________________________________________________ Exercise your brain! Try Flexicon. http://games.msn.com/en/flexicon/default.htm?icid=flexicon_hmemailtaglineapr...
JJ JJ kirjoitti viestissään (lähetysaika keskiviikko, 25. huhtikuuta 2007):
Regarding VmWare, I saw the Virtual Machine Manager, but it can only perform network installations (right?),
VMWare can install from ISO images on the host system or from physical CD/DVD disks.
On Wed, 2007-04-25 at 06:07 -0700, JJ JJ wrote:
i again, a quick note to show you the log of yesterday session:
Apr 24 23:21:57 localhost kernel: ACPI: PCI Interrupt 0000:02:0a.0[A] -> GSI 17 (level, low) -> IRQ 17 Apr 24 23:21:57 localhost kernel: ACPI: PCI Interrupt 0000:02:09.0[A] -> GSI 16 (level, low) -> IRQ 16 Apr 24 23:21:57 localhost kernel: ACPI: PCI Interrupt 0000:00:07.5[B] -> GSI 17 (level, low) -> IRQ 17 Apr 24 23:21:57 localhost kernel: ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16 Apr 24 23:21:57 localhost kernel: ACPI: Power Button (FF) [PWRF] Apr 24 23:21:57 localhost kernel: ACPI: Power Button (CM) [PWRB] Apr 24 23:21:57 localhost kernel: ibm_acpi: ec object not found
and a whole lot of other lines before that. So, maybe I have to check the bios....a task that I dread!
Why do you dreas it. You bring up the BIOS screen and there is an ACPI line which is either on or off. Should be on (or whatever seems to mean in). It is easy. -- ======================================================================= QOTD: "I don't think they could put him in a mental hospital. On the other hand, if he were already in, I don't think they'd let him out." ======================================================================= Aaron Konstam telephone: (210) 656-0355 e-mail: akonstam@sbcglobal.net
Ok, I checked the bios and the acpi is enabled. So, now do I have to modify some script? JJ
and a whole lot of other lines before that. So, maybe I have to check the bios....a task that I dread!
Why do you dreas it. You bring up the BIOS screen and there is an ACPI line which is either on or off. Should be on (or whatever seems to mean in). It is easy.
_________________________________________________________________ MSN is giving away a trip to Vegas to see Elton John. Enter to win today. http://msnconcertcontest.com?icid-nceltontagline
On Thursday 26 April 2007 23:35, JJ JJ wrote:
Ok, I checked the bios and the acpi is enabled. So, now do I have to modify some script? JJ
Ok. I've had this problem on FC5, and Aarons had it on FC6.
There are things you can try when you boot up, and Grubs menu comes up. When you see Grubs menu, type "a". This will make it possible to append the kernel bootup arguments. In my case with FC5, adding acpi=force to this line fixed my problem. In Aarons case with FC6, adding lacpi to the kernel line fixed his problem. There are other options. You could also try lapic, and there are other options as well.
Anyway. Start the machine, when you see Grubs menu type "a". Do one space on the keyboard, and type lacpi, then ENTER, which will then boot the machine. When it's booted up, shut it down, and see if it completes the shutdown.
If it doesn't, you can bootup again, and try the acpi=force option that worked for me with FC5, or the lapic option.
These additions to the kernel that you make at bootup are once only. if one of them works you need to edit /boot/grub/grub.conf to make the one that works permanent. If one works and you don't know how to edit the file, post back.
We have the technology, this will be fixed. Hopefully!!
Nigel.
On Thu, 2007-04-26 at 14:35 -0700, JJ JJ wrote:
Ok, I checked the bios and the acpi is enabled. So, now do I have to modify some script? JJ
You can try Nigel's suggestions, but first I would do the: dmesg |grep ACPI (or acpi) right after boot and see if the boot messages give you a hint as to what to do.
Hey Aaron, sorry I saw your message only now. I tried Nigel's tips, and still no go. So, at the grub menu I have to digit this line: dmesg |grep ACPI am I correct? I also noticed that at the end, I get this message: acpi: pci interrupt for device 0000:02:03.0 disabled My guess is that if I enable it, this P.O.S. should work, but how do I enable it? Thanks again!! JJ
On Thu, 2007-04-26 at 14:35 -0700, JJ JJ wrote:
Ok, I checked the bios and the acpi is enabled. So, now do I have to modify some script? JJ
You can try Nigel's suggestions, but first I would do the: dmesg |grep ACPI (or acpi) right after boot and see if the boot messages give you a hint as to what to do. -- Aaron Konstam akonstam@sbcglobal.net
_________________________________________________________________ Get a FREE Web site, company branded e-mail and more from Microsoft Office Live! http://clk.atdmt.com/MRT/go/mcrssaub0050001411mrt/direct/01/
On Friday 27 April 2007 22:31, JJ JJ wrote:
Hey Aaron, sorry I saw your message only now. I tried Nigel's tips, and still no go. So, at the grub menu I have to digit this line: dmesg |grep ACPI am I correct? I also noticed that at the end, I get this message: acpi: pci interrupt for device 0000:02:03.0 disabled My guess is that if I enable it, this P.O.S. should work, but how do I enable it? Thanks again!! JJ
You run dmesg from the CLI (Konsole/Terminal) once you have booted up. if you just run dmesg from the CLI you get all of the bootup stuff displayed in the terminal. Running dmesg | grep acpi limits the output to what just applies to acpi.
This is a horrible problem, and seems to appear with more recent kernels, and just on some hardware. My original kernel that was installed from the cdroms for FC5 still shutsdown ok, but kernels 2.6.17. and later have this shutdown problem, and in my case on FC5 acpi=force added to the kernel lines in /boot/grub/grub.conf seems to fix the problem.
Hope we can fix this for you, as it's an inconvenience having to push the button to shutdown.
Nigel.
Thank you for the clarifications, Nigel. Here's a list of what I got running the command:
ACPI: RSDP (v002 ACPIAM ) @ 0x00000000000f6cf0 ACPI: XSDT (v001 A M I OEMXSDT 0x06000514 MSFT 0x00000097) @ 0x000000007fff0100 ACPI: FADT (v001 A M I OEMFACP 0x06000514 MSFT 0x00000097) @ 0x000000007fff0281 ACPI: MADT (v001 A M I OEMAPIC 0x06000514 MSFT 0x00000097) @ 0x000000007fff0380 ACPI: OEMB (v001 A M I OEMBIOS 0x06000514 MSFT 0x00000097) @ 0x000000007ffff040 ACPI: HPET (v001 A M I OEMHPET 0x06000514 MSFT 0x00000097) @ 0x000000007fff3990 ACPI: ASF! (v001 AMIASF AMDSTRET 0x00000001 INTL 0x02002026) @ 0x000000007fff39d0 ACPI: DSDT (v001 0AAAA 0AAAA000 0x00000000 INTL 0x02002026) @ 0x0000000000000000 ACPI: Local APIC address 0xfee00000 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: IRQ0 used by override. ACPI: IRQ2 used by override. ACPI: IRQ9 used by override. Using ACPI (MADT) for SMP configuration information ACPI: Core revision 20060707 ACPI: bus type pci registered ACPI: Interpreter enabled ACPI: Using IOAPIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (0000:00) ACPI: PCI Interrupt Routing Table [_SB_.PCI0._PRT] ACPI: PCI Interrupt Routing Table [_SB_.PCI0.PCI1._PRT] ACPI: PCI Interrupt Routing Table [_SB_.PCI0.P0P2._PRT] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12 14 15) ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *9 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 9 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 *10 11 12 14 15) pnp: PnP ACPI init pnp: PnP ACPI: found 14 devices PCI: Using ACPI for IRQ routing ACPI: Processor [CPU1] (supports 8 throttling states) ACPI Exception (acpi_processor-0677): AE_NOT_FOUND, Processor Device is not present [20060707] ACPI Exception (acpi_processor-0677): AE_NOT_FOUND, Processor Device is not present [20060707] ACPI: PCI Interrupt 0000:02:0b.0[A] -> GSI 17 (level, low) -> IRQ 17 ACPI: PCI Interrupt 0000:02:0b.1[B] -> GSI 18 (level, low) -> IRQ 18 ACPI: PCI Interrupt 0000:02:00.0[D] -> GSI 19 (level, low) -> IRQ 19 ACPI: PCI Interrupt 0000:02:00.1[D] -> GSI 19 (level, low) -> IRQ 19 ACPI: PCI Interrupt 0000:02:0b.2[C] -> GSI 19 (level, low) -> IRQ 19 ACPI: PCI Interrupt 0000:02:05.0[A] -> GSI 19 (level, low) -> IRQ 19 ACPI: PCI Interrupt 0000:02:03.0[A] -> GSI 18 (level, low) -> IRQ 18 ACPI: PCI Interrupt 0000:02:07.0[A] -> GSI 19 (level, low) -> IRQ 19 ACPI: PCI Interrupt 0000:02:09.2[B] -> GSI 17 (level, low) -> IRQ 17 ACPI: PCI Interrupt 0000:02:0a.0[A] -> GSI 17 (level, low) -> IRQ 17 ACPI: PCI Interrupt 0000:02:09.0[A] -> GSI 16 (level, low) -> IRQ 16 ACPI: PCI Interrupt 0000:00:07.5[B] -> GSI 17 (level, low) -> IRQ 17 ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16 ACPI: Power Button (FF) [PWRF] ACPI: Power Button (CM) [PWRB]
this problem itself is not a really big deal, the only issue is that I have to be present until the very end of the shutdown sequence, since I can't leave the rig unattended. Oh, well....
On Friday 27 April 2007 22:31, JJ JJ wrote:
Hey Aaron, sorry I saw your message only now. I tried Nigel's tips, and still no
go.
So, at the grub menu I have to digit this line: dmesg |grep ACPI am I correct? I also noticed that at the end, I get this message: acpi: pci interrupt for device 0000:02:03.0 disabled My guess is that if I enable it, this P.O.S. should work, but how do I enable it? Thanks again!! JJ
You run dmesg from the CLI (Konsole/Terminal) once you have booted up. if you just run dmesg from the CLI you get all of the bootup stuff displayed in the terminal. Running dmesg | grep acpi limits the output to what just applies to acpi.
This is a horrible problem, and seems to appear with more recent kernels, and just on some hardware. My original kernel that was installed from the cdroms for FC5 still shutsdown ok, but kernels 2.6.17. and later have this shutdown problem, and in my case on FC5 acpi=force added to the kernel lines in /boot/grub/grub.conf seems to fix the problem.
Hope we can fix this for you, as it's an inconvenience having to push the button to shutdown.
Nigel.
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
_________________________________________________________________ Interest Rates NEAR 39yr LOWS! $430,000 Mortgage for $1,299/mo - Calculate new payment http://www.lowermybills.com/lre/index.jsp?sourceid=lmb-9632-19132&moid=1...
On Friday 27 April 2007 23:18, JJ JJ wrote:
Thank you for the clarifications, Nigel. Here's a list of what I got running the command:
<snip of dmesg | grep acpi output>
this problem itself is not a really big deal, the only issue is that I have to be present until the very end of the shutdown sequence, since I can't leave the rig unattended. Oh, well....
Hmmm. I've never used dmesg | grep acpi before. My! That's some output, and it's way beyond my understanding. Normally I just use the dmesg command, and can make some sort of sense from the output from that.
I'll throw that back to Aaron to interpret that, as he suggested it.
If you just run dmesg, and scroll down a bit you should see references to acpi, along with some suggestions as there are problems with it. If you can post the relevant acpi bits from that it might be helpfull.
A kindly tip. Can you post your replies at the bottom of the previous posting, as it makes it much easier to follow the thread. Any irrelevant stuff from the previous post can be snipped. For example, I've just snipped the output of dmesg | grep acpi from this reply, as it is easily seen on the previous post. Of course you don't want to snip so much, that you lose the context, and your reply no longer makes any sense to someone just seeing the thread for the first time.
I see many one liner replies, and often have no idea what the reply is referencing.
01:04 now in Northern France. 4 beers down, feeling tired, and going upstairs to share a yogourt with my dog before going to bed.
Nigel.
Hmmm. I've never used dmesg | grep acpi before. My! That's some output, and it's way beyond my understanding. Normally I just use the dmesg command, and can make some sort of sense from the output from that.
I'll throw that back to Aaron to interpret that, as he suggested it.
If you just run dmesg, and scroll down a bit you should see references to acpi, along with some suggestions as there are problems with it. If you can post the relevant acpi bits from that it might be helpfull.
Nigel.
Hello Nigel, here's some lines from my term. window as you suggested:
ACPI: RSDP (v002 ACPIAM ) @ 0x00000000000f6cf0 ACPI: XSDT (v001 A M I OEMXSDT 0x06000514 MSFT 0x00000097) @ 0x000000007fff0100 ACPI: FADT (v001 A M I OEMFACP 0x06000514 MSFT 0x00000097) @ 0x000000007fff0281 ACPI: MADT (v001 A M I OEMAPIC 0x06000514 MSFT 0x00000097) @ 0x000000007fff0380 ACPI: OEMB (v001 A M I OEMBIOS 0x06000514 MSFT 0x00000097) @ 0x000000007ffff040 ACPI: HPET (v001 A M I OEMHPET 0x06000514 MSFT 0x00000097) @ 0x000000007fff3990 ACPI: ASF! (v001 AMIASF AMDSTRET 0x00000001 INTL 0x02002026) @ 0x000000007fff39d0 ACPI: DSDT (v001 0AAAA 0AAAA000 0x00000000 INTL 0x02002026) @ 0x0000000000000000 ACPI: Local APIC address 0xfee00000 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) IOAPIC[0]: apic_id 2, version 17, address 0xfec00000, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: IRQ0 used by override. ACPI: IRQ2 used by override. ACPI: IRQ9 used by override. Setting APIC routing to xen Using ACPI (MADT) for SMP configuration information
ACPI: Core revision 20060707
ACPI: bus type pci registered PCI: Using configuration type 1 ACPI: Interpreter enabled ACPI: Using IOAPIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (0000:00) PCI: Probing PCI hardware (bus 00) Boot video device is 0000:01:00.0 ACPI: PCI Interrupt Routing Table [_SB_.PCI0._PRT] ACPI: PCI Interrupt Routing Table [_SB_.PCI0.PCI1._PRT] ACPI: PCI Interrupt Routing Table [_SB_.PCI0.P0P2._PRT] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12 14 15) ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *9 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 9 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 *10 11 12 14 15) Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI init pnp: PnP ACPI: found 14 devices
ACPI: Processor [CPU1] (supports 8 throttling states) ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707] ACPI: Getting cpuindex for acpiid 0x3 ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not present [20060707] ACPI: Getting cpuindex for acpiid 0x4 Real Time Clock Driver v1.12ac hpet_acpi_add: no address or irqs in _CRS
ACPI: PCI Interrupt 0000:02:0b.0[A] -> GSI 17 (level, low) -> IRQ 16 and others similar to this line.
This is pretty much all I could find running the command acpi related. I hope there's some useful info. Thanks again! JJ
_________________________________________________________________ Download Messenger. Join the im Initiative. Help make a difference today. http://im.live.com/messenger/im/home/?source=TAGHM_APR07
On Saturday 28 April 2007 09:57, JJ JJ wrote:
If you just run dmesg, and scroll down a bit you should see references to acpi, along with some suggestions as there are problems with it. If you can post the relevant acpi bits from that it might be helpfull.
Nigel.
Hello Nigel, here's some lines from my term. window as you suggested:
ACPI: RSDP (v002 ACPIAM ) @ 0x00000000000f6cf0 ACPI: XSDT (v001 A M I OEMXSDT 0x06000514 MSFT 0x00000097) @ 0x000000007fff0100 ACPI: FADT (v001 A M I OEMFACP 0x06000514 MSFT 0x00000097) @ 0x000000007fff0281 ACPI: MADT (v001 A M I OEMAPIC 0x06000514 MSFT 0x00000097) @ 0x000000007fff0380 ACPI: OEMB (v001 A M I OEMBIOS 0x06000514 MSFT 0x00000097) @ 0x000000007ffff040 ACPI: HPET (v001 A M I OEMHPET 0x06000514 MSFT 0x00000097) @ 0x000000007fff3990 ACPI: ASF! (v001 AMIASF AMDSTRET 0x00000001 INTL 0x02002026) @ 0x000000007fff39d0 ACPI: DSDT (v001 0AAAA 0AAAA000 0x00000000 INTL 0x02002026) @ 0x0000000000000000 ACPI: Local APIC address 0xfee00000 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) IOAPIC[0]: apic_id 2, version 17, address 0xfec00000, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: IRQ0 used by override. ACPI: IRQ2 used by override. ACPI: IRQ9 used by override. Setting APIC routing to xen Using ACPI (MADT) for SMP configuration information
Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI init pnp: PnP ACPI: found 14 devices
This is pretty much all I could find running the command acpi related. I hope there's some useful info. Thanks again! JJ
Hi JJ. There don't appear to be any errors showing there, but when I had my FC5 shutdown problem, someone asked if I was using an SMP kernel, as that could be causing the problem, and unless I've got it wrong, you are.
uname -r will show your kernel version.
Out of interest this is what dmesg shows on FC5 for a kernel that is not using acpi=force.
ACPI: RSDP (v000 VIA601 ) @ 0x000f63c0 ACPI: RSDT (v001 VIA601 AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x3f7f3000 ACPI: FADT (v001 VIA601 AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x3f7f3040 ACPI: DSDT (v001 VIA601 AWRDACPI 0x00001000 MSFT 0x0100000c) @ 0x00000000 ACPI: Disabling ACPI support and Local APIC disabled by BIOS -- you can enable it with "lapic" mapped APIC to ffffd000 (017f7000)
And again on FC5 with a different kernel that boots using acpi=force.
IO/L-APIC disabled because your old system seems to be old overwrite with "apic" ACPI: RSDP (v000 VIA601 ) @ 0x000f63c0 ACPI: RSDT (v001 VIA601 AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x3f7f3000 ACPI: FADT (v001 VIA601 AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x3f7f3040 ACPI: DSDT (v001 VIA601 AWRDACPI 0x00001000 MSFT 0x0100000c) @ 0x00000000 ACPI: acpi=force override ACPI: PM-Timer IO Port: 0x4008 and Kernel command line: ro root=LABEL=/1 acpi=force mapped APIC to ffffd000 (017f7000)
If it is a problem with a XEN/SMP kernel, I don't know the fix, but hopefully someone will come in on the thread, and may be able to help.
Nigel.
On Fri, 2007-04-27 at 14:18 -0700, JJ JJ wrote:
Thank you for the clarifications, Nigel. Here's a list of what I got running the command:
ACPI: RSDP (v002 ACPIAM ) @ 0x00000000000f6cf0 ACPI: XSDT (v001 A M I OEMXSDT 0x06000514 MSFT 0x00000097) @ 0x000000007fff0100 ACPI: FADT (v001 A M I OEMFACP 0x06000514 MSFT 0x00000097) @ 0x000000007fff0281 ACPI: MADT (v001 A M I OEMAPIC 0x06000514 MSFT 0x00000097) @ 0x000000007fff0380 ACPI: OEMB (v001 A M I OEMBIOS 0x06000514 MSFT 0x00000097) @ 0x000000007ffff040 ACPI: HPET (v001 A M I OEMHPET 0x06000514 MSFT 0x00000097) @ 0x000000007fff3990 ACPI: ASF! (v001 AMIASF AMDSTRET 0x00000001 INTL 0x02002026) @ 0x000000007fff39d0 ACPI: DSDT (v001 0AAAA 0AAAA000 0x00000000 INTL 0x02002026) @ 0x0000000000000000 ACPI: Local APIC address 0xfee00000 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: IRQ0 used by override. ACPI: IRQ2 used by override. ACPI: IRQ9 used by override. Using ACPI (MADT) for SMP configuration information ACPI: Core revision 20060707 ACPI: bus type pci registered ACPI: Interpreter enabled ACPI: Using IOAPIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (0000:00) ACPI: PCI Interrupt Routing Table [_SB_.PCI0._PRT] ACPI: PCI Interrupt Routing Table [_SB_.PCI0.PCI1._PRT] ACPI: PCI Interrupt Routing Table [_SB_.PCI0.P0P2._PRT] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12 14 15) ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *9 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 9 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 *10 11 12 14 15) pnp: PnP ACPI init pnp: PnP ACPI: found 14 devices PCI: Using ACPI for IRQ routing ACPI: Processor [CPU1] (supports 8 throttling states) ACPI Exception (acpi_processor-0677): AE_NOT_FOUND, Processor Device is not present [20060707] ACPI Exception (acpi_processor-0677): AE_NOT_FOUND, Processor Device is not present [20060707] ACPI: PCI Interrupt 0000:02:0b.0[A] -> GSI 17 (level, low) -> IRQ 17 ACPI: PCI Interrupt 0000:02:0b.1[B] -> GSI 18 (level, low) -> IRQ 18 ACPI: PCI Interrupt 0000:02:00.0[D] -> GSI 19 (level, low) -> IRQ 19 ACPI: PCI Interrupt 0000:02:00.1[D] -> GSI 19 (level, low) -> IRQ 19 ACPI: PCI Interrupt 0000:02:0b.2[C] -> GSI 19 (level, low) -> IRQ 19 ACPI: PCI Interrupt 0000:02:05.0[A] -> GSI 19 (level, low) -> IRQ 19 ACPI: PCI Interrupt 0000:02:03.0[A] -> GSI 18 (level, low) -> IRQ 18 ACPI: PCI Interrupt 0000:02:07.0[A] -> GSI 19 (level, low) -> IRQ 19 ACPI: PCI Interrupt 0000:02:09.2[B] -> GSI 17 (level, low) -> IRQ 17 ACPI: PCI Interrupt 0000:02:0a.0[A] -> GSI 17 (level, low) -> IRQ 17 ACPI: PCI Interrupt 0000:02:09.0[A] -> GSI 16 (level, low) -> IRQ 16 ACPI: PCI Interrupt 0000:00:07.5[B] -> GSI 17 (level, low) -> IRQ 17 ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16 ACPI: Power Button (FF) [PWRF] ACPI: Power Button (CM) [PWRB]
this problem itself is not a really big deal, the only issue is that I have to be present until the very end of the shutdown sequence, since I can't leave the rig unattended. Oh, well....
I can't say I understand what all these messages mean. My messages were more informative. But trying some of the suggested kernel optiosn seems to be worth trying. lacpi or acpi=force seems like possibilities. But in your case acpi seems to be doing something. On my machine it was not. -- ======================================================================= Man who falls in blast furnace is certain to feel overwrought. ======================================================================= Aaron Konstam telephone: (210) 656-0355 e-mail: akonstam@sbcglobal.net
On Sat, 2007-04-28 at 14:06 +0200, Nigel Henry wrote:
On Saturday 28 April 2007 09:57, JJ JJ wrote:
If you just run dmesg, and scroll down a bit you should see references to acpi, along with some suggestions as there are problems with it. If you can post the relevant acpi bits from that it might be helpfull.
Nigel.
Hello Nigel, here's some lines from my term. window as you suggested:
ACPI: RSDP (v002 ACPIAM ) @ 0x00000000000f6cf0 ACPI: XSDT (v001 A M I OEMXSDT 0x06000514 MSFT 0x00000097) @ 0x000000007fff0100 ACPI: FADT (v001 A M I OEMFACP 0x06000514 MSFT 0x00000097) @ 0x000000007fff0281 ACPI: MADT (v001 A M I OEMAPIC 0x06000514 MSFT 0x00000097) @ 0x000000007fff0380 ACPI: OEMB (v001 A M I OEMBIOS 0x06000514 MSFT 0x00000097) @ 0x000000007ffff040 ACPI: HPET (v001 A M I OEMHPET 0x06000514 MSFT 0x00000097) @ 0x000000007fff3990 ACPI: ASF! (v001 AMIASF AMDSTRET 0x00000001 INTL 0x02002026) @ 0x000000007fff39d0 ACPI: DSDT (v001 0AAAA 0AAAA000 0x00000000 INTL 0x02002026) @ 0x0000000000000000 ACPI: Local APIC address 0xfee00000 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) IOAPIC[0]: apic_id 2, version 17, address 0xfec00000, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: IRQ0 used by override. ACPI: IRQ2 used by override. ACPI: IRQ9 used by override. Setting APIC routing to xen Using ACPI (MADT) for SMP configuration information
Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI init pnp: PnP ACPI: found 14 devices
This is pretty much all I could find running the command acpi related. I hope there's some useful info. Thanks again! JJ
Hi JJ. There don't appear to be any errors showing there, but when I had my FC5 shutdown problem, someone asked if I was using an SMP kernel, as that could be causing the problem, and unless I've got it wrong, you are.
uname -r will show your kernel version.
Out of interest this is what dmesg shows on FC5 for a kernel that is not using acpi=force.
ACPI: RSDP (v000 VIA601 ) @ 0x000f63c0 ACPI: RSDT (v001 VIA601 AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x3f7f3000 ACPI: FADT (v001 VIA601 AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x3f7f3040 ACPI: DSDT (v001 VIA601 AWRDACPI 0x00001000 MSFT 0x0100000c) @ 0x00000000 ACPI: Disabling ACPI support and Local APIC disabled by BIOS -- you can enable it with "lapic" mapped APIC to ffffd000 (017f7000)
The above were the messages that lead me to add the lacpi kernel option. In FC6 the same kernel works for smp and non-smp kernels so smp can't be the problem.
And again on FC5 with a different kernel that boots using acpi=force.
IO/L-APIC disabled because your old system seems to be old overwrite with "apic" ACPI: RSDP (v000 VIA601 ) @ 0x000f63c0 ACPI: RSDT (v001 VIA601 AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x3f7f3000 ACPI: FADT (v001 VIA601 AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x3f7f3040 ACPI: DSDT (v001 VIA601 AWRDACPI 0x00001000 MSFT 0x0100000c) @ 0x00000000 ACPI: acpi=force override ACPI: PM-Timer IO Port: 0x4008 and Kernel command line: ro root=LABEL=/1 acpi=force mapped APIC to ffffd000 (017f7000)
If it is a problem with a XEN/SMP kernel, I don't know the fix, but hopefully someone will come in on the thread, and may be able to help.
Nigel.
-- ======================================================================= I request a weekend in Havana with Phil Silvers! ======================================================================= Aaron Konstam telephone: (210) 656-0355 e-mail: akonstam@sbcglobal.net
ACPI: RSDP (v002 ACPIAM ) @
0x00000000000f6cf0 ACPI: PCI Interrupt 0000:02:09.2[B] -> GSI 17 (level, low) -> IRQ 17 ACPI: PCI Interrupt 0000:02:0a.0[A] -> GSI 17 (level, low) -> IRQ 17 ACPI: PCI Interrupt 0000:02:09.0[A] -> GSI 16 (level, low) -> IRQ 16 ACPI: PCI Interrupt 0000:00:07.5[B] -> GSI 17 (level, low) -> IRQ 17 ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16 ACPI: Power Button (FF) [PWRF] ACPI: Power Button (CM) [PWRB]
this problem itself is not a really big deal, the only issue is that I have to be present until the very end of the shutdown sequence, since I can't leave the rig unattended. Oh, well....
I can't say I understand what all these messages mean. My messages were more informative. But trying some of the suggested kernel optiosn seems to be worth trying. lacpi or acpi=force seems like possibilities. But in your case acpi seems to be doing something. On my machine it was not.
Hello Aaron, some good news, for a change. I booted up the second kernel, and now the system shuts down completely. These are my 2 kernels: 2.6.20-1.2944fc6xen 2.6.18-1.2798fc6xen the first one is the one that has issues. By the way, is the choice of 2 kernels a linux feature or is it just my install? Thanks, JJ
_________________________________________________________________ The average US Credit Score is 675. The cost to see yours: $0 by Experian. http://www.freecreditreport.com/pm/default.aspx?sc=660600&bcd=EMAILFOOTE...
On Sunday 29 April 2007 15:35, JJ JJ wrote:
ACPI: RSDP (v002 ACPIAM ) @
0x00000000000f6cf0 ACPI: PCI Interrupt 0000:02:09.2[B] -> GSI 17 (level, low) -> IRQ 17 ACPI: PCI Interrupt 0000:02:0a.0[A] -> GSI 17 (level, low) -> IRQ 17 ACPI: PCI Interrupt 0000:02:09.0[A] -> GSI 16 (level, low) -> IRQ 16 ACPI: PCI Interrupt 0000:00:07.5[B] -> GSI 17 (level, low) -> IRQ 17 ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16 ACPI: Power Button (FF) [PWRF] ACPI: Power Button (CM) [PWRB]
this problem itself is not a really big deal, the only issue is that I have to be present until the very end of the shutdown sequence, since I can't leave the rig unattended. Oh, well....
I can't say I understand what all these messages mean. My messages were more informative. But trying some of the suggested kernel optiosn seems to be worth trying. lacpi or acpi=force seems like possibilities. But in your case acpi seems to be doing something. On my machine it was not.
Hello Aaron, some good news, for a change. I booted up the second kernel, and now the system shuts down completely. These are my 2 kernels: 2.6.20-1.2944fc6xen 2.6.18-1.2798fc6xen the first one is the one that has issues. By the way, is the choice of 2 kernels a linux feature or is it just my install? Thanks, JJ
Hi JJ. Glad you got to shutdown completely using the earlier kernel. You have obviously done a yum update, and a newer kernel was installed. If you are using yum for updates, and want to keep the kernel that is shutting down ok, you need the edit something. Yum as default only keeps 2 kernels, so if you run yum update again, and there is a yet newer kernel, it will install that, and remove the oldest one, which in your case is the one you want to keep.
You can change this behaviour by either disabling the plugin, or changing the number of kernels to save.
Open the CLI, and su to root, open a text editor, go to /etc/yum/pluginconf.d/installonlyn.conf.
My FC6 one looks like this.
[main] enabled=0 # this sets the number of package versions which are kept tokeep=2
I just disable the plugin by just changing "enabled=1 to enabled=0", but you can just change the "tokeep=2" to whatever number you like. 5 might be a good number. It's possible that the next kernel update from the one that's not shutting down completely will again shutdown completely, but you can't be sure, so you want to keep the 2.6.18 one which is doing what you want.
After saving the changes, keep the text editor open, and go to /boot/grub/grub.conf . Afew lines down you'll see this.
#boot=/dev/hda default=3 timeout=30 splashimage=(hd1,0)/boot/grub/splash.xpm.gz title Fedora Core (2.6.10-2.3.legacy_FC2)
I say this, but this is from FC2. The "default" line sets the kernel you want to boot. Grub starts at "0", so you can change this to "1", then at the moment it will boot the 2.6.18 kernel that works ok. The "timeout" line I have already changed. The default is 5 secs, and it's worth changing this to 30, as it gives you a bit more time to make decisions as to which kernel you want to boot. The next line "splashimage" IIRC is "hiddenimage" on FC5, and FC6. if you are not seeing the grub menu when you bootup, you can put a "#" at the start of this line (no double quotes), which will comment out the line.
Just a few suggestions, so you don't lose your working kernel, along with the grub stuff.
Nigel.
Btw. I use apt, and synaptic as update managers, so am not involved in this ptential kernel problem with yum.
The average US Credit Score is 675. The cost to see yours: $0 by Experian. http://www.freecreditreport.com/pm/default.aspx?sc=660600&bcd=EMAILFOOTE... ERAGE
Hi JJ. Glad you got to shutdown completely using the earlier kernel. You have obviously done a yum update, and a newer kernel was installed. If you are using yum for updates, and want to keep the kernel that is shutting down ok, you need the edit something. Yum as default only keeps 2 kernels, so if you run yum update again, and there is a yet newer kernel, it will install that, and remove the oldest one, which in your case is the one you want to keep.
You can change this behaviour by either disabling the plugin, or changing the number of kernels to save.
Open the CLI, and su to root, open a text editor, go to /etc/yum/pluginconf.d/installonlyn.conf.
My FC6 one looks like this.
[main] enabled=0 # this sets the number of package versions which are kept tokeep=2
I just disable the plugin by just changing "enabled=1 to enabled=0", but you can just change the "tokeep=2" to whatever number you like. 5 might be a good number. It's possible that the next kernel update from the one that's not shutting down completely will again shutdown completely, but you can't be sure, so you want to keep the 2.6.18 one which is doing what you want.
After saving the changes, keep the text editor open, and go to /boot/grub/grub.conf . Afew lines down you'll see this.
#boot=/dev/hda default=3 timeout=30 splashimage=(hd1,0)/boot/grub/splash.xpm.gz title Fedora Core (2.6.10-2.3.legacy_FC2)
I say this, but this is from FC2. The "default" line sets the kernel you want to boot. Grub starts at "0", so you can change this to "1", then at the moment it will boot the 2.6.18 kernel that works ok. The "timeout" line I have already changed. The default is 5 secs, and it's worth changing this to 30, as it gives you a bit more time to make decisions as to which kernel you want to boot. The next line "splashimage" IIRC is "hiddenimage" on FC5, and FC6. if you are not seeing the grub menu when you bootup, you can put a "#" at the start of this line (no double quotes), which will comment out the line.
Just a few suggestions, so you don't lose your working kernel, along with the grub stuff.
Nigel.
Btw. I use apt, and synaptic as update managers, so am not involved in this ptential kernel problem with yum.
Hey Nigel, thank you for the suggestions, much appreciated. Jessica.
_________________________________________________________________ Mortgage refinance is Hot. *Terms. Get a 5.375%* fix rate. Check savings https://www2.nextag.com/goto.jsp?product=100000035&url=%2fst.jsp&tm=...
On Sun, 2007-04-29 at 06:35 -0700, JJ JJ wrote:
ACPI: RSDP (v002 ACPIAM ) @
0x00000000000f6cf0 ACPI: PCI Interrupt 0000:02:09.2[B] -> GSI 17 (level, low) -> IRQ 17 ACPI: PCI Interrupt 0000:02:0a.0[A] -> GSI 17 (level, low) -> IRQ 17 ACPI: PCI Interrupt 0000:02:09.0[A] -> GSI 16 (level, low) -> IRQ 16 ACPI: PCI Interrupt 0000:00:07.5[B] -> GSI 17 (level, low) -> IRQ 17 ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16 ACPI: Power Button (FF) [PWRF] ACPI: Power Button (CM) [PWRB]
this problem itself is not a really big deal, the only issue is that I have to be present until the very end of the shutdown sequence, since I can't leave the rig unattended. Oh, well....
I can't say I understand what all these messages mean. My messages were more informative. But trying some of the suggested kernel optiosn seems to be worth trying. lacpi or acpi=force seems like possibilities. But in your case acpi seems to be doing something. On my machine it was not.
Hello Aaron, some good news, for a change. I booted up the second kernel, and now the system shuts down completely. These are my 2 kernels: 2.6.20-1.2944fc6xen 2.6.18-1.2798fc6xen the first one is the one that has issues. By the way, is the choice of 2 kernels a linux feature or is it just my install? Thanks, JJ
Thi s is sort of a late reply but you change the number of kernels kept in the file: /etc/yum/pluginconf.d/installonlyn.conf
-
Aaron Konstam -
Amitakhya Phukan -
Chris Mohler -
JJ JJ -
Joachim Backes -
Jonathan Berry -
Kam Leo -
Markku Kolkka -
Nigel Henry -
Tim