When I install openSUSE and I boot back into Windows 7, Windows won’t sleep. Meaning, when I put it to sleep, it immediately wakes up.
I thought maybe it was a program I was running in Windows that was the problem. But after going through two installs of Windows 7 and openSUSE and troubleshooting, it seems that the problem begins only once I install openSUSE.
Any ideas why this might be? I’m not sure what other info you might need (hardware is in the sig), but let me know and I’ll supply it. This is a fresh install with Windows 7 and a fresh install of openSUSE. Windows goes to sleep fine after it’s installed, drivers updated, AV and whatnot installed, but once openSUSE is installed Windows sleep breaks. So strange.
pagefile.sys is a hidden system file, you have to find folder options in view menu of explorer to see it. I am not sure they write out that data to disk, when suspending to RAM, because it’s instant unlike Hibernate where they save pages to a disk file.
It’s usually “Hibernate” aka Suspend to Disk, which would be disrupted, when Windows knows it doesn’t have control of it’s boot process, or hiberfil.sys gets deleted for some reason.
Not sleeping aka Suspend to RAM is an odd one. I go from openSUSE to Vista & Win 7, and sleep always has worked for me, in the other OS (but not unfortunately now in 11.2, 11.1 it did work).
I should poweroff the machine for 5 mins, then try booting cold into Windows. It could be that a Win driver fails to initialise things correctly, or relies on the BIOS doing it for you, and some optimisation has taken place.
My wife’s laptop does this with Vista sometimes. It has no opensuse installed (her wireless card was not supported when we got it and now she’s grown used to vista).
After reading about this issue, I tried to “sleep” in Win 7, and like other, Win 7 will go to see, then wake immediately. Prior to installing OpenSUSE 11.2, Win7’s sleep worked flawlessly. Any ideas?
I went into Ctrl panel/Sys and security/System /advanced system setting/ advanced /performance /advanced, and moved the virtual memory to the 2nd HD, which does not have a Linux partition. Didn’t help.
Boot the W7 DVD and fix the Windows bootcode
Now it should be as if there is no Linux installed.
Does it work now?
Actually, chances are your bootcode is intact and all you need to do is switch the boot flag back to the W7 install. See this: All About Grub - openSUSE
But when you repair grub you will probably find it easier just to install grub on the MBR.
No, just the boot code. When you boot the DVD you can fix what is commonly referred to as the MBR (Master Boot Record) - It’s well known. W7 is a bit different than XP was. I have done it several times earlier in the year on test machine. I was breaking grub, re-installing it, breaking windows and so on, just for testing. It’s easy. Just scary if you have never done it before.
Seems to be something with the openSUSE install since I just did a full reinstall (might as well, since I’ve been doing it a couple times over the past few days trying to troubleshoot) and tried the new Ubuntu and sleep works just fine. Is there a difference in the way that Ubuntu loads on dual boot and openSUSE loads on dual boot? Like, would there be an option that I need to manually set while installing openSUSE so that the problem might go away?
Cause I’d rather have openSUSE as my linux partition–openSUSE is a lot more slick than the new Ubuntu (and Ubuntu has this strange popping noise when a sound plays).
I have noticed when installing OpenSUSE 11.2, That I had to enable install to MBR on the setup overview screen, The page that has the botton you click to install.
It is disable by default ever time I have went to install it and that fixed my netbook. I had problem with the boot because it was installing the boot record some where the netbook did not like, not sure where now, It has been awhile.
It may or may not be you problem, I do not Know how. But it is something to watch for.
By default on a Laptop or PC with windows only. The installer will shrink windows and create an extended partition and put 3 logical partitions in it:
swap
root
home
It will switch the boot flag from Windows to the extended partition and the boot loader will go there (not the MBR). This is preferred and you can read about it here: All About Grub - openSUSE
Well If it is not touching his MBR, I wounld not think it is his problem, But who knows at this point. Since he has a lot of loading going on over there it may be something to try.
That may be the preferred way , only if it works and it didn’t work on may end on may test netbook, I can’t remember what the problem was.
I think this is a change in this release isn’t it. Hasn’t it always ( the boot loader) installed to the MBR by default.
Hasn’t it always ( the boot loader) installed to the MBR by default.
No. Well Yes and No. It’s debatable I think. I recall discussions on this and users would always experience differing results at install, which to some extent is understandable. No two systems are identical (generally speaking).
Though MBR is my preferred option and is by far the simplest to manage from a new users point of view.
I’m fairly certain Ubuntu will write to the MBR. I’m running test on Ub* and grub 2 and from all I see it does go to MBR
The 2 key scripts to repair/update grun are:
‘update-grub’ and ‘grub-install’
In that order