11:24 a.m.
Dear friends,
I have a problem with grub on fedora 13.
After hibernation, I found that I couldn't boot into Windows 7 just because the
grub menu showed up and disappear immediately and then my laptop booted into
fedora right away. Fedora is my default entry. Now I must use a trick by adding
"hiddenmenu" option and rapidly press up/down arrow key to get to grub menu.
It's not a serious problem but I still would want to solve it. Here's my
menu.lst file.
timeout=10
splashimage=(hd0,5)/boot/grub/splash.xpm.gz
title Fedora 13
root (hd0,5)
kernel /boot/vmlinuz-2.6.33.6-147.2.4.fc13.x86_64 ro
root=UUID=7edc57de-27ec-4ee9-bfe1-eeafc39cb2e9 rd_NO_LUKS rd_NO_LVM rd_NO_MD
rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us
rhgb quiet
initrd /boot/initramfs-2.6.33.6-147.2.4.fc13.x86_64.img
title Windows 7
rootnoverify (hd0,0)
chainloader +1
Thank you.
5:31 p.m.
On Mon, 2010-08-23 at 15:49 -0500, Aaron Konstam wrote:
Somewhere the point is missed. The whole point of hibernate is to be
able to return to the same operating system in the same state.
So far, so good.
If you want to switch from Linux to Windows, restart does that.
Yes, but I want to switch to Windows, and *then* return to Linux in the
same state. It is possible to do this, I have done it in the past and it
is quite a time saver,
--Greg
11:46 a.m.
New subject: [SOLVED] grub menu is automatically skipped
Thank you a lot for you fast reply. Adding the "default" option make it work. I
keep the "timeout" option, because I want it and I remember that it was from the
original installation.
Hoang Le
________________________________
From: Pawan Sood <pawansood(a)gmail.com>
To: Community support for Fedora users <users(a)lists.fedoraproject.org>
Sent: Sun, August 22, 2010 11:34:16 PM
Subject: Re: grub menu is automatically skipped
On Sun, Aug 22, 2010 at 9:54 PM, Hoang Le <new.lehoang(a)yahoo.com> wrote:
Dear friends,
I have a problem with grub on fedora 13.
After hibernation, I found that I couldn't boot into Windows 7 just because the
grub menu showed up and disappear immediately and then my laptop booted into
fedora right away. Fedora is my default entry. Now I must use a trick by adding
"hiddenmenu" option and rapidly press up/down arrow key to get to grub menu.
It's not a serious problem but I still would want to solve it. Here's my
menu.lst file.
timeout=10
splashimage=(hd0,5)/boot/grub/splash.xpm.gz
title Fedora 13
root (hd0,5)
kernel /boot/vmlinuz-2.6.33.6-147.2.4.fc13.x86_64 ro
root=UUID=7edc57de-27ec-4ee9-bfe1-eeafc39cb2e9 rd_NO_LUKS rd_NO_LVM rd_NO_MD
rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us
rhgb quiet
initrd /boot/initramfs-2.6.33.6-147.2.4.fc13.x86_64.img
title Windows 7
rootnoverify (hd0,0)
chainloader +1
Thank you.
--
users mailing list
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
comment out the line "timeout=10".
there should be a line "default=0" above "timeout=10".
-Pawan
--
users mailing list
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
11:34 a.m.
On Sun, Aug 22, 2010 at 9:54 PM, Hoang Le <new.lehoang(a)yahoo.com> wrote:
Dear friends,
I have a problem with grub on fedora 13.
After hibernation, I found that I couldn't boot into Windows 7 just because the grub
menu showed up and disappear immediately and then my laptop booted into fedora right
away. Fedora is my default entry. Now I must use a trick by adding "hiddenmenu"
option and rapidly press up/down arrow key to get to grub menu.
It's not a serious problem but I still would want to solve it. Here's my menu.lst
file.
timeout=10
splashimage=(hd0,5)/boot/grub/splash.xpm.gz
title Fedora 13
root (hd0,5)
kernel /boot/vmlinuz-2.6.33.6-147.2.4.fc13.x86_64 ro
root=UUID=7edc57de-27ec-4ee9-bfe1-eeafc39cb2e9 rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM
LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rhgb quiet
initrd /boot/initramfs-2.6.33.6-147.2.4.fc13.x86_64.img
title Windows 7
rootnoverify (hd0,0)
chainloader +1
Thank you.
--
users mailing list
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
comment the line "timeout=10".
there should be a line "default=0" above "timeout=10".
-Pawan
11:34 a.m.
On Sun, Aug 22, 2010 at 9:54 PM, Hoang Le <new.lehoang(a)yahoo.com> wrote:
Dear friends,
I have a problem with grub on fedora 13.
After hibernation, I found that I couldn't boot into Windows 7 just because the grub
menu showed up and disappear immediately and then my laptop booted into fedora right
away. Fedora is my default entry. Now I must use a trick by adding "hiddenmenu"
option and rapidly press up/down arrow key to get to grub menu.
It's not a serious problem but I still would want to solve it. Here's my menu.lst
file.
timeout=10
splashimage=(hd0,5)/boot/grub/splash.xpm.gz
title Fedora 13
root (hd0,5)
kernel /boot/vmlinuz-2.6.33.6-147.2.4.fc13.x86_64 ro
root=UUID=7edc57de-27ec-4ee9-bfe1-eeafc39cb2e9 rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM
LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rhgb quiet
initrd /boot/initramfs-2.6.33.6-147.2.4.fc13.x86_64.img
title Windows 7
rootnoverify (hd0,0)
chainloader +1
Thank you.
--
users mailing list
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
comment out the line "timeout=10".
there should be a line "default=0" above "timeout=10".
-Pawan
10:48 a.m.
On Tuesday, 24 August, 2010 @06:13 zulu, Michael Schwendt scribed:
Where is the confusion? Linux and Windows don't share their
swap partition with eachother, so a Suspend-To-Disk option in
addition to Suspend-To-RAM is useful.
I'm not sure windows uses a separate swap space
for its hibernation file... it makes one the same
size as the amount of RAM installed as soon as
hibernation is enabled, in the root of the partition
where windows is installed. i.e. I think even if
you specify a different partition/logical volume
for its swap file, the hibernation file stays put.
Anyway, did you remind them of this use in the
"Is swap really needed when RAM's aplenty" thread?
9:29 a.m.
On 08/24/2010 02:13 AM, Michael Schwendt wrote:
On Mon, 23 Aug 2010 15:42:38 -0500, Aaron wrote:
> Either get rid of the hibernate option or arrange for the Boot
> process to detect the record of the system state saved by hibernate.
>
> Currently hibernate is useless.
What is useless about it? Have you ever used it before?
> Soo ir might as well not to have
> hibernate to confuse people.
Where is the confusion? Linux and Windows don't share their swap partition
with eachother, so a Suspend-To-Disk option in addition to Suspend-To-RAM
is useful.
Actually, it *is* possible (with a little work) for Windows and Linux to
share the swap partition.
Google for "Linux Windows share swap", you'll get a lot of hits.
The gist of it is:
1) create a Windows partition (FAT32) for Windows to put its swap
partition in.
2) shutdown Windows and boot Linux. Compress the Windows partition into
a small file.
3) Modify Linux start-up to do a mkswap on the partition during startup
and to restore the windows partition during shutdown (not hibernation).
Let the confusion reign.
--
Kevin J. Cummings
kjchome(a)rcn.com
cummings(a)kjchome.homeip.net
cummings(a)kjc386.framingham.ma.us
Registered Linux User #1232 (http://counter.li.org)
1:13 a.m.
On Mon, 23 Aug 2010 15:42:38 -0500, Aaron wrote:
Either get rid of the hibernate option or arrange for the Boot
process to detect the record of the system state saved by hibernate.
Currently hibernate is useless.
What is useless about it? Have you ever used it before?
Soo ir might as well not to have
hibernate to confuse people.
Where is the confusion? Linux and Windows don't share their swap partition
with eachother, so a Suspend-To-Disk option in addition to Suspend-To-RAM
is useful.
8:52 p.m.
On Mon, 2010-08-23 at 17:51 -0500, Chris Adams wrote:
You were lucky. Hibernating one OS, running another, and then
waking
up the first can leave the hardware in unpredictable states (IIRC the
power management modes don't define support for that). Linux tries to
reset things, but it isn't supported due to the unknowns.
Not really. When you hibernate, the final action is a power off. The
hardware is hard reset. When you resume, it's from a cold start, the
hardware is in a reset state, and the resume process should do a full
reset before actually resuming, to enforce the hardware being in a known
state. Though, in essence, the resuming will load up a state into the
hardware.
Switching from one OS to the next, with a hibernate in between, will
necessitate a reboot, anyway, as that's going to be the only way that
you'll get a boot choice menu.
--
[tim@localhost ~]$ uname -r
2.6.27.25-78.2.56.fc9.i686
Don't send private replies to my address, the mailbox is ignored. I
read messages from the public lists.
5:51 p.m.
Once upon a time, Greg Woods <woods(a)ucar.edu> said:
Yes, but I want to switch to Windows, and *then* return to Linux in
the
same state. It is possible to do this, I have done it in the past and it
is quite a time saver,
You were lucky. Hibernating one OS, running another, and then waking up
the first can leave the hardware in unpredictable states (IIRC the power
management modes don't define support for that). Linux tries to reset
things, but it isn't supported due to the unknowns.
--
Chris Adams <cmadams(a)hiwaay.net>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.
3:49 p.m.
On Mon, 2010-08-23 at 17:30 +0000, JB wrote:
Greg Woods <woods <at> ucar.edu> writes:
>
> On Mon, 2010-08-23 at 16:59 +0000, JB wrote:
>
> > Now, to try to accommodate your idea, the obvious requirement would be to
> > have a private hibernation area/file (swap file ?) for each
> > OS/distro/kernel's machine state.
>
> Only the OS's that you care about hibernating. With just a Linux swap
> partition, it is possible to hibernate Linux, boot Windows, shut down
> Windows, then resume Linux.
But if you present a menu selection between one Linux (hibernated) and Win, then
the user, immediatelly or after finishing with Win, may decide to NOT return to
last hibernated Linux, but instead select another Linux menu item, and then
the bets are off.
Somewhere the point is missed. The whole point of hibernate is to
be
able to return to the same operating system in the same state.
If you want to switch from Linux to Windows, restart does that.
> Multiple versions of Linux can be hibernated simultaneously as well, as
> long as they each have their own separate swap partition.
But this is not practical - you can not foresee how many Linux/kernel menu
selection items will be available (subject to potential hibernation). Having
the ability to create ad hoc swap partitions would be a practical impossibility.
JB
--
Aaron Konstam <akonstam(a)sbcglobal.net>
3:42 p.m.
On Mon, 2010-08-23 at 11:36 -0500, Mikkel wrote:
On 08/23/2010 08:48 AM, Aaron Konstam wrote:
> On Sun, 2010-08-22 at 19:05 -0500, Mikkel wrote:
>> On 08/22/2010 04:38 PM, Aaron Konstam wrote:
>>>
>>> I am glad you solved you problem but I am amazed that default worked.
>>> Hibernate saves the state of the system at the time you tell it to
>>> hibernate. When you return you load back the system to the state you
>>> had before hibernation. Which means to me that if you hibernate while in
>>> Linux it should come back to Linux. And booting into Windows 7 should be
>>> impossible. Would someone who suggested the default solution explain why
>>> this works?
>> I think you are confusing suspend to RAM with hibernation. When you
>> have the system hibernating, it has actually shut down. When you
>> boot Linux again, it checks swap to see if you saved the system
>> state, and reloads it if you did. But Grub and Windows do not test
>> this, so if you chose to load Windows, Grub happily does it. But it
>> probably is not a good idea.
>>
>> You can also chose to ignore the hibernating image and do a normal
>> reboot. I don't remember what you have to pass the kernel to have it
>> skip the check...
>>
>> Mikkel
>
> I am always glad to know new things. Hibernate anws suspend have similar
> functions in that a system state is saved on a disk or in RAM. Google
> "Linux hibernate" and it seems clear that when the machine is started
> the state of the system, is restored to what it was before hibernation
> or suspension. If Grub does not check if a state was saved then
> hibernation is worthless and I have learned something. To me what you
> describe is just plain crazy.
Grub is a general purpose boot loader. It does not know how to check
if there is an OS hibernating. I should also add that if the BIOS
supports it, and Linux know how to use it, it will resume directly
from disk without Grub ever entering the picture.
The above reminds me of an old joke. In this case Fedora developers must
decide. Either get rid of the hibernate option or arrange for the Boot
process to detect the record of the system state saved by hibernate.
Currently hibernate is useless. Soo ir might as well not to have
hibernate to confuse people.
With Windows, you normally have to set it up before you can use it.
I am not sure about Linux. I don't hibernate my systems often enough
to look into all the fancy options.
Mikkel
--
Aaron Konstam <akonstam(a)sbcglobal.net>
1:16 p.m.
On Mon, 2010-08-23 at 17:30 +0000, JB wrote:
But if you present a menu selection between one Linux (hibernated)
and Win, then
the user, immediatelly or after finishing with Win, may decide to NOT return to
last hibernated Linux, but instead select another Linux menu item,
Sorry for not being crystal clear. When I said "different versions of
Linux", I should have said "different Linux distributions". I was
thinking more along the lines of Ubuntu, Fedora, Gentoo, etc. installed
on their own separate root partitions, not different kernel versions of
the same distro. I have done things like this and had separate swap
partitions for each distro and had them all hibernated at the same time.
It works.
I do realize that it is not practical to have a separate swap partition
for every selectable kernel version, and selecting the wrong kernel
could cause a hibernated image to not load and possibly be overwritten.
A small risk, since I am the only "user" of my desktop system so I can
reasonably count on this not happening, and even if the hibernated image
is lost, the OS can still be booted up. I mainly use hibernate/suspend
to save time and I know better than to leave editor sessions with
critical files half-edited when hibernating, and so forth, so if a
hibernated image is lost, or if the system fails to resume from suspend
properly (which occasionally happens), all I lose is some time in having
to log back in, fire up all my applications, etc.
--Greg
12:30 p.m.
Greg Woods <woods <at> ucar.edu> writes:
On Mon, 2010-08-23 at 16:59 +0000, JB wrote:
> Now, to try to accommodate your idea, the obvious requirement would be to
> have a private hibernation area/file (swap file ?) for each
> OS/distro/kernel's machine state.
Only the OS's that you care about hibernating. With just a Linux swap
partition, it is possible to hibernate Linux, boot Windows, shut down
Windows, then resume Linux.
But if you present a menu selection between one Linux (hibernated) and Win, then
the user, immediatelly or after finishing with Win, may decide to NOT return to
last hibernated Linux, but instead select another Linux menu item, and then
the bets are off.
Multiple versions of Linux can be hibernated simultaneously as well,
as
long as they each have their own separate swap partition.
But this is not practical - you can not foresee how many Linux/kernel menu
selection items will be available (subject to potential hibernation). Having
the ability to create ad hoc swap partitions would be a practical impossibility.
JB
12:07 p.m.
On Mon, 2010-08-23 at 16:59 +0000, JB wrote:
Now, to try to accommodate your idea, the obvious requirement would
be to have
a private hibernation area/file (swap file ?) for each OS/distro/kernel's
machine state.
Only the OS's that you care about hibernating. With just a Linux swap
partition, it is possible to hibernate Linux, boot Windows, shut down
Windows, then resume Linux. If it was desired to hibernate Windows too,
then yes, Windows would need a place to store the hibernated image.
Multiple versions of Linux can be hibernated simultaneously as well, as
long as they each have their own separate swap partition.
--Greg
12:04 p.m.
On Mon, 2010-08-23 at 11:36 -0500, Mikkel wrote:
Grub is a general purpose boot loader. It does not know how to check
if there is an OS hibernating. I should also add that if the BIOS
supports it, and Linux know how to use it, it will resume directly
from disk without Grub ever entering the picture.
I will have to look in the BIOS and try to figure out which boot
parameter controls this. Something definitely knows that the system has
hibernated, because the immediate boot to Linux only happens after I
have hibernated. Suspending is of course a different deal, since resume
can only work with help from the BIOS. If a boot loader is loaded into
memory, the suspended image would be overwritten. A hibernated image can
be preserved even across booting an entirely different OS.
With Windows, you normally have to set it up before you can use it.
I think there has to be a hibernate partition. Windows doesn't normally
have a swap partition the way Linux does, so Linux just uses the swap
partition to store the hibernated image. If you have a Linux system
without swap, you won't be able to hibernate.
I am not sure about Linux. I don't hibernate my systems often
enough
to look into all the fancy options.
The boot option is "resume=/dev/<swap-partition-device)". This also
tells the kernel to use that swap partition for the hibernated image. I
have even had multiple versions of Linux hibernated at the same time,
which works as long as each has a different swap area.
A system that is having trouble resuming can bypass the hibernated image
and boot from scratch if "noresume" is given instead.
--Greg
11:59 a.m.
Greg Woods <woods <at> ucar.edu> writes:
On Mon, 2010-08-23 at 07:12 +0000, JB wrote:
> Aaron Konstam <akonstam <at> sbcglobal.net> writes:
> > Which means to me that if you hibernate while in
> > Linux it should come back to Linux.
I actually find it useful that it does not, and I have been frustrated
by the recent change in behavior. I used to be able to hibernate, then
boot into Windows, then resume Linux from hibernation. This works
because what hibernate actually does is save the RAM state to the swap
space. As long as the contents of the swap space are not overwritten, it
is possible to resume the hibernated image. Since Windows does not use
the Linux swap space, it is theoretically possible to boot into Windows,
then resume Linux later. This used to work, but now I find that when I
have hibernated, it immediately starts booting Linux again and I am not
given the chance to choose the boot option. If anyone knows of a way to
restore the old behavior, I'd love to hear about it.
--Greg
Hi,
this is a good idea, but on the first look can not be implemented with
hibernate-to-swap-partition approach. The reason is that swap partition can be
a destination for saving a machine state of only one OS/distro/kernel at
a time. That is the practical reason and requirement for coming back to
the same OS/distro/kernel that hibernated, without an intermediate boot loader
menu selection available. I think that's obvious.
Now, to try to accommodate your idea, the obvious requirement would be to have
a private hibernation area/file (swap file ?) for each OS/distro/kernel's
machine state.
These solutions actually exist; it comes down to different views of how they
should be implemented, in kernel or user space, etc.
You can read about it here:
http://superuser.com/questions/21020/can-i-hibernate-linux-without-a-swap...
http://en.wikipedia.org/wiki/TuxOnIce
JB
11:36 a.m.
On 08/23/2010 08:48 AM, Aaron Konstam wrote:
On Sun, 2010-08-22 at 19:05 -0500, Mikkel wrote:
> On 08/22/2010 04:38 PM, Aaron Konstam wrote:
>>
>> I am glad you solved you problem but I am amazed that default worked.
>> Hibernate saves the state of the system at the time you tell it to
>> hibernate. When you return you load back the system to the state you
>> had before hibernation. Which means to me that if you hibernate while in
>> Linux it should come back to Linux. And booting into Windows 7 should be
>> impossible. Would someone who suggested the default solution explain why
>> this works?
> I think you are confusing suspend to RAM with hibernation. When you
> have the system hibernating, it has actually shut down. When you
> boot Linux again, it checks swap to see if you saved the system
> state, and reloads it if you did. But Grub and Windows do not test
> this, so if you chose to load Windows, Grub happily does it. But it
> probably is not a good idea.
>
> You can also chose to ignore the hibernating image and do a normal
> reboot. I don't remember what you have to pass the kernel to have it
> skip the check...
>
> Mikkel
I am always glad to know new things. Hibernate anws suspend have similar
functions in that a system state is saved on a disk or in RAM. Google
"Linux hibernate" and it seems clear that when the machine is started
the state of the system, is restored to what it was before hibernation
or suspension. If Grub does not check if a state was saved then
hibernation is worthless and I have learned something. To me what you
describe is just plain crazy.
Grub is a general purpose boot loader. It does not know how to check
if there is an OS hibernating. I should also add that if the BIOS
supports it, and Linux know how to use it, it will resume directly
from disk without Grub ever entering the picture.
With Windows, you normally have to set it up before you can use it.
I am not sure about Linux. I don't hibernate my systems often enough
to look into all the fancy options.
Mikkel
--
Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!
11:28 a.m.
Hi Greg,
I have exactly the same problem that I can't choose OS after hibernating Linux.
But it doesn't really matter to me since Linux is my main OS.
I also noticed that Debian 5 (Lenny) didn't have this problem compared with
Fedora at that time ( I don't remember the version ).
Hoang Le
________________________________
From: Greg Woods <woods(a)ucar.edu>
To: Community support for Fedora users <users(a)lists.fedoraproject.org>
Sent: Mon, August 23, 2010 7:47:16 PM
Subject: Re: grub menu is automatically skipped
On Mon, 2010-08-23 at 07:12 +0000, JB wrote:
Aaron Konstam <akonstam <at> sbcglobal.net> writes:
> Which means to me that if you hibernate while in
> Linux it should come back to Linux.
I actually find it useful that it does not, and I have been frustrated
by the recent change in behavior. I used to be able to hibernate, then
boot into Windows, then resume Linux from hibernation. This works
because what hibernate actually does is save the RAM state to the swap
space. As long as the contents of the swap space are not overwritten, it
is possible to resume the hibernated image. Since Windows does not use
the Linux swap space, it is theoretically possible to boot into Windows,
then resume Linux later. This used to work, but now I find that when I
have hibernated, it immediately starts booting Linux again and I am not
given the chance to choose the boot option. If anyone knows of a way to
restore the old behavior, I'd love to hear about it.
--Greg
--
users mailing list
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
8:48 a.m.
On Sun, 2010-08-22 at 19:05 -0500, Mikkel wrote:
On 08/22/2010 04:38 PM, Aaron Konstam wrote:
>
> I am glad you solved you problem but I am amazed that default worked.
> Hibernate saves the state of the system at the time you tell it to
> hibernate. When you return you load back the system to the state you
> had before hibernation. Which means to me that if you hibernate while in
> Linux it should come back to Linux. And booting into Windows 7 should be
> impossible. Would someone who suggested the default solution explain why
> this works?
I think you are confusing suspend to RAM with hibernation. When you
have the system hibernating, it has actually shut down. When you
boot Linux again, it checks swap to see if you saved the system
state, and reloads it if you did. But Grub and Windows do not test
this, so if you chose to load Windows, Grub happily does it. But it
probably is not a good idea.
You can also chose to ignore the hibernating image and do a normal
reboot. I don't remember what you have to pass the kernel to have it
skip the check...
Mikkel
I am always glad to know new things. Hibernate anws suspend have similar
functions in that a system state is saved on a disk or in RAM. Google
"Linux hibernate" and it seems clear that when the machine is started
the state of the system, is restored to what it was before hibernation
or suspension. If Grub does not check if a state was saved then
hibernation is worthless and I have learned something. To me what you
describe is just plain crazy.
--
Aaron Konstam <akonstam(a)sbcglobal.net>
7:47 a.m.
On Mon, 2010-08-23 at 07:12 +0000, JB wrote:
Aaron Konstam <akonstam <at> sbcglobal.net> writes:
> Which means to me that if you hibernate while in
> Linux it should come back to Linux.
I actually find it useful that it does not, and I have been frustrated
by the recent change in behavior. I used to be able to hibernate, then
boot into Windows, then resume Linux from hibernation. This works
because what hibernate actually does is save the RAM state to the swap
space. As long as the contents of the swap space are not overwritten, it
is possible to resume the hibernated image. Since Windows does not use
the Linux swap space, it is theoretically possible to boot into Windows,
then resume Linux later. This used to work, but now I find that when I
have hibernated, it immediately starts booting Linux again and I am not
given the chance to choose the boot option. If anyone knows of a way to
restore the old behavior, I'd love to hear about it.
--Greg
2:12 a.m.
Aaron Konstam <akonstam <at> sbcglobal.net> writes:
...
I am glad you solved you problem but I am amazed that default worked.
Hi,
Aaron is right about his amazement.
info grub
...
-- Command: default num
Set the default entry to the entry number NUM. Numbering starts
from 0, and the entry number 0 is the default if the command is not
used.
...
So, the presence of default command is not required.
Hibernate saves the state of the system at the time you tell it to
hibernate.
$ less /var/log/pm-suspend.log
...
/usr/lib/pm-utils/sleep.d/01grub hibernate hibernate: success.
...
$ less /usr/lib/pm-utils/sleep.d/01grub
...
out=$(/sbin/grubby --info /boot/vmlinuz-$(uname -r) |grep index)
...
echo "savedefault --default=${current} --once" | \
...
In this case, the default entry is the entry saved with the command
`savedefault'.
When you return you load back the system to the state you
had before hibernation.
GRUB will choose the entry booted previously as the default entry.
Which means to me that if you hibernate while in
Linux it should come back to Linux. And booting into Windows 7 should be
impossible. Would someone who suggested the default solution explain why
this works?
Yes, Aaron. Do not let them off the hook :-)
JB
9:31 p.m.
I'm providing a little bit more detail if you're interested. I installed Windows
first and then came Fedora, I installed grub on MBR.
I don't know why but I tried fedora 13 once before and got the same problem. I
used fedora 13 for several days until I try hibernation and it didn't work
properly.
________________________________
From: Aaron Konstam <akonstam(a)sbcglobal.net>
To: Community support for Fedora users <users(a)lists.fedoraproject.org>
Sent: Mon, August 23, 2010 4:38:12 AM
Subject: Re: grub menu is automatically skipped
I am glad you solved you problem but I am amazed that default worked.
Hibernate saves the state of the system at the time you tell it to
hibernate. When you return you load back the system to the state you
had before hibernation. Which means to me that if you hibernate while in
Linux it should come back to Linux. And booting into Windows 7 should be
impossible. Would someone who suggested the default solution explain why
this works?
--
Aaron Konstam <akonstam(a)sbcglobal.net>
--
users mailing list
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
7:05 p.m.
On 08/22/2010 04:38 PM, Aaron Konstam wrote:
I am glad you solved you problem but I am amazed that default worked.
Hibernate saves the state of the system at the time you tell it to
hibernate. When you return you load back the system to the state you
had before hibernation. Which means to me that if you hibernate while in
Linux it should come back to Linux. And booting into Windows 7 should be
impossible. Would someone who suggested the default solution explain why
this works?
I think you are confusing suspend to RAM with hibernation. When you
have the system hibernating, it has actually shut down. When you
boot Linux again, it checks swap to see if you saved the system
state, and reloads it if you did. But Grub and Windows do not test
this, so if you chose to load Windows, Grub happily does it. But it
probably is not a good idea.
You can also chose to ignore the hibernating image and do a normal
reboot. I don't remember what you have to pass the kernel to have it
skip the check...
Mikkel
--
Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!
4:38 p.m.
On Mon, 2010-08-23 at 00:24 +0800, Hoang Le wrote:
Dear friends,
I have a problem with grub on fedora 13.
After hibernation, I found that I couldn't boot into Windows 7 just
because the grub menu showed up and disappear immediately and then my
laptop booted into fedora right away. Fedora is my default entry. Now
I must use a trick by adding "hiddenmenu" option and rapidly press
up/down arrow key to get to grub menu.
It's not a serious problem but I still would want to solve it. Here's
my menu.lst file.
timeout=10
splashimage=(hd0,5)/boot/grub/splash.xpm.gz
title Fedora 13
root (hd0,5)
kernel /boot/vmlinuz-2.6.33.6-147.2.4.fc13.x86_64 ro
root=UUID=7edc57de-27ec-4ee9-bfe1-eeafc39cb2e9 rd_NO_LUKS rd_NO_LVM
rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16
KEYBOARDTYPE=pc KEYTABLE=us rhgb quiet
initrd /boot/initramfs-2.6.33.6-147.2.4.fc13.x86_64.img
title Windows 7
rootnoverify (hd0,0)
chainloader +1
Thank you.
I am glad you solved you problem but I am amazed that default worked.
Hibernate saves the state of the system at the time you tell it to
hibernate. When you return you load back the system to the state you
had before hibernation. Which means to me that if you hibernate while in
Linux it should come back to Linux. And booting into Windows 7 should be
impossible. Would someone who suggested the default solution explain why
this works?
--
Aaron Konstam <akonstam(a)sbcglobal.net>
5031
days inactive
5033
days old
24 comments
11 participants
participants (11)
-
Aaron Konstam -
Chris Adams -
Darr -
Greg Woods -
Hoang Le -
JB -
Kevin Cummings -
Michael Schwendt -
Mikkel -
Pawan Sood -
Tim