Bug 117590

Summary:	9.3->10.0 upgrade silently undoes grub config changes
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Dan Winship <danw>
Component:	Installation	Assignee:	Jiri Srain <jsrain>
Status:	RESOLVED WONTFIX	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Major
Priority:	P5 - None
Version:	RC 4
Target Milestone:	---
Hardware:	i686
OS:	All
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Dan Winship 2005-09-16 22:43:49 UTC

After upgrading to RC4, my Thinkpad X40 can no longer resume after suspending
(to RAM). This had worked fine in 9.3 and in earlier 10.0 releases.

I don't remember what release I was running before RC4 (it might have been
RC2), but I can check if you tell me what to look for in the logs.

Comment 1 Forgotten User ZhJd0F0L3x 2005-09-19 12:53:43 UTC

hm. Which graphics chipset does your X40 have (lspci), do you need strange
options on the command line (cat /proc/cmdline) to make suspend to RAM work?

/var/log/suspend2ram.log could contain additional hints, so it would be great if
you could attach it.

Comment 2 Pavel Machek 2005-09-19 14:12:36 UTC

Does suspend to disk work?

Comment 3 Dan Winship 2005-09-20 01:11:08 UTC

comment #1 reminded me that long long ago, I'd had to add "acpi_sleep=s3_bios"
to my grub.conf to make suspend-to-ram work. The upgrade seems to have removed
it. Adding it back fixed things.

Changing the Summary to reflect, but this might be NOTABUG/WONTFIX? (I'm sure
other people will run into this problem too, but the updater obviously can't
handle arbitrary grub.conf changes... It would be nice if it could at least
notice that it had been changed from the default and warn that it was being
rewritten though.)

Comment 4 Forgotten User ZhJd0F0L3x 2005-09-20 09:35:27 UTC

maybe, but this is a YaST bug, then ;-)

Comment 5 Jiří Suchomel 2005-09-20 11:24:01 UTC

Yes, upgrade removes such changes.

Comment 6 Jiri Srain 2005-09-26 10:53:28 UTC

Upgrade recreates the sections which are related to your system from scratch. 
The reason is that there is newer kernel which may need another parameters 
that the old version didn't need. I find this behavior fine. You still have 
the older file in /boot/grub/menu.lst.old and can use the original section. I 
won't change it.