Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I installed Ubuntu 8.10, and it works as it should be - except for one thing. The shutter is not properly.
When I put Ubuntu to switch off, then go down the line as it should, but when the hard drive is off and the computer is going to turn off completely, so it stays lit. It shuts off only when I press any key on the keyboard, and it annoys me.
However, it is not always to do it, but it is only rarely that it turns off completely. I can solve the problem temporarily by taking out the battery and plugging it back until the problem occurs again a little while after.
Now I believe that it is an ACPI problem. I have stopped Powernowd, because otherwise the CPU running at paltry 800mhz.
Could it have anything to do with it?
I'm not sure it with GRUB list, think of if the computer can not start up, what do I do?
Did disabling powernowd fix the shutdown problem?
Adding acpi=force to the kernel line in grub's menu.lst would not prevent the system from starting up. If you first back up menu.lst before editing it like I showed in my last post, you can always restore the original menu.lst if something goes wrong.
Suppose you messed up menu.lst while editing it so that Ubuntu would not boot. To restore the original menu.lst, you can boot from the Ubuntu live CD, mount your Ubuntu partition, and replace the backed up menu.lst. For example, suppose Ubuntu is on /dev/sda2. You would do this from the Ubuntu live CD:
sudo mount /dev/sda2 /mnt
sudo cp /mnt/boot/grub/menu.lst.bak /mnt/boot/grub/menu.lst
Then save the file and close gedit. Then reboot and grub will be back the way it was before you messed it up.
If you don't know what partition Ubuntu is on look at /etc/fstab. The partition that has the mount point as / (for root) is your Ubuntu root partition.
I always back up any configuration file first before editing it for this reason.
Can you make a screenshot of the outcome, so I can see exactly how I should do?
Here is how you would add acpi=force to the kernel line for booting Ubuntu. Run gksudo gedit /boot/grub/menu.lst from terminal. Scroll down to the section ## ## End Default Options ##. The entries for booting Ubuntu are below that. There is an entry for booting Ubuntu, plus an entry for booting to recovery mode, for each kernel that you have. Here is the entry for booting Ubuntu from my menu.lst:
Then save the file and exit. Then reboot. If it don't work you can just edit menu.lst again and remove acpi=force.
You only need to add acpi=force to the first entry in grub for booting Ubuntu. Don't worry about the entries below that for older kernels you may have.
When I disabled Powernowd that was just the system faster. It did not resolve my problem.
Now I would like to have restored GRUB from the .bak file, but I can not doubleclick on the .bak file.
How I restore the GRUB list without making use of Live-CD?
Do you mean it fixes the shutdown problem? Or do you just mean that the system boots with acpi=force added to the kernel line in menu.lst? If it fixes the shutddown problem just leave it the way it is.
Originally Posted by Pazau
the only one who would have been nice to boot graphics still appear, and it does not. Is there a way to turn it on?
I'm not sure what you mean by that. What graphics are you talking about?
The -i switch added to the cp command is for interactive. It will ask you to confirm overwriting menu.lst. Just answer y for yes to confirm and this will restore menu.lst from the .bak file.
The "-i" switch is optional. It is a good safety feature because it asks you to confirm the overwrite, so you don't accidentally overwrite the wrong file. This is unlikely in this case, but in other cases many files have similar names, so a typo could accidentally overwrite the wrong file.