[Bug 620434] New: kernel parameters are not kept on kernel updates
http://bugzilla.novell.com/show_bug.cgi?id=620434 http://bugzilla.novell.com/show_bug.cgi?id=620434#c0 Summary: kernel parameters are not kept on kernel updates Classification: openSUSE Product: openSUSE 11.3 Version: RC 2 Platform: All OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: estellnb@gmail.com QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; de; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6 It is a real annoyance that user defined kernel parameters which are ment to be kept permanently are lost on every kernel update. With os11.2 I had to patch the resume= parameter on every kernel update (because it was always lost) and often could not suspend to disk because I simply forgot about it seeking for the error in a totally different place and thus wasting lots of precious time. This time with os11.3 I have to set the nomodeset parameter, have remebered wrong about it (as modeset or modset=0) and thus another time wasted huge amounts of time. The bug does not seem to serious but it provides a true utterly annoying hazard. Please fix this before the release of os11.3! It should not be a great deal, at least to keep all parameters behind the final runlevel stating (5 or 3, usually). The parameters there can only having been entered by a user. Reproducible: Always -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=620434
http://bugzilla.novell.com/show_bug.cgi?id=620434#c
Michal Marek
http://bugzilla.novell.com/show_bug.cgi?id=620434
http://bugzilla.novell.com/show_bug.cgi?id=620434#c1
Leonardo Chiquitto
http://bugzilla.novell.com/show_bug.cgi?id=620434
http://bugzilla.novell.com/show_bug.cgi?id=620434#c2
--- Comment #2 from Elmar Stellnberger
http://bugzilla.novell.com/show_bug.cgi?id=620434
http://bugzilla.novell.com/show_bug.cgi?id=620434#c3
Elmar Stellnberger
http://bugzilla.novell.com/show_bug.cgi?id=620434
http://bugzilla.novell.com/show_bug.cgi?id=620434#c4
Leonardo Chiquitto
http://bugzilla.novell.com/show_bug.cgi?id=620434
http://bugzilla.novell.com/show_bug.cgi?id=620434#c5
Elmar Stellnberger
http://bugzilla.novell.com/show_bug.cgi?id=620434
http://bugzilla.novell.com/show_bug.cgi?id=620434#c6
--- Comment #6 from Elmar Stellnberger
http://bugzilla.novell.com/show_bug.cgi?id=620434
http://bugzilla.novell.com/show_bug.cgi?id=620434#c
Jiri Srain
http://bugzilla.novell.com/show_bug.cgi?id=620434
http://bugzilla.novell.com/show_bug.cgi?id=620434#c7
Josef Reidinger
http://bugzilla.novell.com/show_bug.cgi?id=620434
http://bugzilla.novell.com/show_bug.cgi?id=620434#c8
Robin Knapp
http://bugzilla.novell.com/show_bug.cgi?id=620434
http://bugzilla.novell.com/show_bug.cgi?id=620434#c9
Josef Reidinger
Just tested it, but... if I update /etc/sysconfig/bootloader - nothing happens. Running update-bootloader --refresh - nothing happens.
Of course, refresh is just to install bootloader to its location. It doesn't change configuration.
I have to either update a kernel to add these options or edit both /etc/sysconfig/bootloader AND /boot/grub/menu.lst which is suboptimal.
So either don't remove custom automatically, try to detect them: if it's different from what's defined in /etc/sysconfig/bootloader, find out custom options and add them with the new kernel.
/etc/sysconfig/bootloader is parameters for newly installed kernels. /boot/grub/menu.lst is actual settings. I detect custom settings, but if defined variables in sysconfig I use it. It is because we want clear solution for customer, because in past sometime happen that when customer has different kernel favors with different options and we use bad parameters for newly added kernel, so we use solution where is clear which parameters is used for new kernels.
Or provide a command to update the bootloader.
tool to edit bootloader is yast. Pbl is library, so you can create own tool using it. It is opensource.
Or use yast
But this is not a good solution - people cried for years that you can only configure your system using yast; editing configuration files will break your system. This has become much better recently, but now it returns in a very critical place: the bootloader.
So do we really want to return to "use yast or die"?
It is not "use yast or die". It is edit menu.lst for current kernels and edit /etc/sysconfig/bootloader for newly installed kernels ( e.g. ubuntu has both in one file and it is horrible mess, so we have two files ) None solution is the best one, always there is some users which complain. I hope that current solution is flexible and text in menu.lst should help user to know what is needed to edit to preserve settings after adding new kernel. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=620434
http://bugzilla.novell.com/show_bug.cgi?id=620434#c10
--- Comment #10 from Robin Knapp
To set this permanently, add it to the kernel command line in /boot/grub/menu.lst.
Which will cause trouble after the first kernel update -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=620434
http://bugzilla.novell.com/show_bug.cgi?id=620434#c11
Elmar Stellnberger
http://bugzilla.novell.com/show_bug.cgi?id=620434
http://bugzilla.novell.com/show_bug.cgi?id=620434#c12
Josef Reidinger
http://bugzilla.novell.com/show_bug.cgi?id=620434
http://bugzilla.novell.com/show_bug.cgi?id=620434#c13
Karl Eichwalder
http://bugzilla.novell.com/show_bug.cgi?id=620434
http://bugzilla.novell.com/show_bug.cgi?id=620434#c14
--- Comment #14 from Robin Knapp
https://bugzilla.novell.com/show_bug.cgi?id=620434
https://bugzilla.novell.com/show_bug.cgi?id=620434#c15
--- Comment #15 from Josef Reidinger
https://bugzilla.novell.com/show_bug.cgi?id=620434
https://bugzilla.novell.com/show_bug.cgi?id=620434#c16
Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=620434
https://bugzilla.novell.com/show_bug.cgi?id=620434#c17
--- Comment #17 from Josef Reidinger
FWIW, I habitually change menu.lst manually, as I run several multiboot systems with Factory, and for Factory I _always_ want showopts before root= on kernel line. I can find no way to have /etc/sysconfig/bootloader do that for me.
Sorry, but this is not possible. order of elements is hardcoded and don't see much reason to have root which allow change of itself ( if it work, then let it be and if not, then change it permanently )
Also I want runlevel number as last item on Grub kernel lines. I would expect separate vga= configuration line must be null in my /etc/sysconfig/bootloader for that to happen. On fresh install this cannot happen because there is no way in installation to specify no vga config.
Also still problem is that it is hardcoded, so it is not easy way to do. Of course if you have special requirements you can disable automatic change of boot menu and do it manually. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=620434
https://bugzilla.novell.com/show_bug.cgi?id=620434#c18
--- Comment #18 from Felix Miata
order of elements is hardcoded
Where and why?
and don't see much reason to have root which allow change of itself ( if it work, then let it be and if not, then change it permanently )
In Factory, sometimes it doesn't work and some experimenting is necessary to get a boot and find out why. e.g. for a long while, root=LABEL= syntax was not working, and still might not be in certain cases. Also, modern root=/dev/disk* syntax makes most kernel lines are longer than the text editor screen is wide (wrapping makes more confusion), which means also /dev/disk entries are too long for human brains to remember for manual typing. And, sometimes troubleshooting requires /dev/sdX# syntax. When dropping back to text mode to edit cmdline and mistake is made, grub doesn't recover nicely, and reboot to restart Grub is often required to retry. So, showopts before root= in gfxmenu is nice facility.
Also I want runlevel number as last item on Grub kernel lines. I would expect separate vga= configuration line must be null in my /etc/sysconfig/bootloader for that to happen. On fresh install this cannot happen because there is no way in installation to specify no vga config.
Also still problem is that it is hardcoded, so it is not easy way to do.
Again, hardcoded where? It seems to me during installation select list could also have additional option to make vga=normal not result on default kernel cmdline made by perl-Bootloader. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=620434
https://bugzilla.novell.com/show_bug.cgi?id=620434#c19
--- Comment #19 from Josef Reidinger
(In reply to comment #17)
order of elements is hardcoded
Where and why?
In perl-bootloader which add new sections to boot menu. And reason is to contain all parts from sysconfig and hard coded one is better then random :) Of course it is possible to have option which allow change of order, but noone yet find it useful. If you think it is useful please add it to features.opensuse.org and if there is enough positive responses I can do it.
and don't see much reason to have root which allow change of itself ( if it work, then let it be and if not, then change it permanently )
In Factory, sometimes it doesn't work and some experimenting is necessary to get a boot and find out why. e.g. for a long while, root=LABEL= syntax was not working, and still might not be in certain cases. Also, modern root=/dev/disk* syntax makes most kernel lines are longer than the text editor screen is wide (wrapping makes more confusion), which means also /dev/disk entries are too long for human brains to remember for manual typing. And, sometimes troubleshooting requires /dev/sdX# syntax. When dropping back to text mode to edit cmdline and mistake is made, grub doesn't recover nicely, and reboot to restart Grub is often required to retry. So, showopts before root= in gfxmenu is nice facility.
Yes, but it is quite specific case, I think common user doesn't find much benefit to have line which contain very long root before remaining parameters like nomodeset which is more useful to him.
Also I want runlevel number as last item on Grub kernel lines. I would expect separate vga= configuration line must be null in my /etc/sysconfig/bootloader for that to happen. On fresh install this cannot happen because there is no way in installation to specify no vga config.
Also still problem is that it is hardcoded, so it is not easy way to do.
Again, hardcoded where? It seems to me during installation select list could also have additional option to make vga=normal not result on default kernel cmdline made by perl-Bootloader.
Yes, it sounds reasonable. Could you please open separate bug report to easier track as it is out of context of this bug report? Thanks -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=620434
https://bugzilla.novell.com/show_bug.cgi?id=620434#c20
--- Comment #20 from Felix Miata
If you think it is useful please add it to features.opensuse.org and if there is enough positive responses I can do it.
https://features.opensuse.org/310673
Could you please open separate bug report to easier track as it is out of context of this bug report? Thanks
https://bugzilla.novell.com/show_bug.cgi?id=643984 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=620434
https://bugzilla.novell.com/show_bug.cgi?id=620434#c21
Elmar Stellnberger
https://bugzilla.novell.com/show_bug.cgi?id=620434
https://bugzilla.novell.com/show_bug.cgi?id=620434#c22
--- Comment #22 from Josef Reidinger
Open a different report for enhanced customization of kernel command line? That could be a feature request although I believe it is a too specialized issue for a public poll. The other side of the medal appears more like a bug an can therefore not be placed usefully on features.opensuse.org, I believe. Wouldn`t it really be a job that could be done with bounded effort to detect manual menu.lst changes to leave this entries simply in place eventually changing the kernel release number on updates? What is the script responsible for creating new menu.lsts??
Hi, in general problem is that each additional customization of kernel line make tool more and more "expert" like as it require more advanced knowledge. So features helps to manage which is still in scope of tool and what is out of scope. It is not so easy with changing booting menu, as GRUB allow many options and e.g. it allow different parameters for different kernels. If you have just one kernel and want to have same parameters you can simple disable autoadapting (set LOADER_TYPE in /etc/sysconfig/bootloader to 'none' and set your in menu section kernel and initrd as symlinks). Reason why it is not so simple is two. If you have more kernel with different flavors, then it is not so easy to detect which one is correct. The second one is also important. If you change flavor of kernel ( so e.g. from default to desktop) and remove old one, then it is not ensure, that new one is installed before old one, so in one moment there could be no section in menu.lst and I need to get somewhere parameters and this is why it is introduced /boot/sysconfig/bootloader, which store it and it is always clear what is used during upgrade of kernel. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=620434
https://bugzilla.novell.com/show_bug.cgi?id=620434#c23
Josef Reidinger
participants (1)
-
bugzilla_noreply@novell.com