On Mon, 20 May 2013 12:46:11 -0400
Bill Davidsen wrote:
> Kevin Fenzi wrote:
> > On Sat, 18 May 2013 19:35:23 -0700
> > Joe Zeff wrote:
> >
> >> On 05/18/2013 06:40 PM, Bill Davidsen wrote:
> >>>
> >>>
> >>> So is dropping the kernel command line options a bug, or
> >>> deliberate policy?
> >>
>
Kevin Fenzi wrote:
On Sat, 18 May 2013 19:35:23 -0700
Joe Zeff wrote:
On 05/18/2013 06:40 PM, Bill Davidsen wrote:
So is dropping the kernel command line options a bug, or deliberate
policy?
Neither. When you install a new kernel, the file is rebuilt, using
/etc/default/grub as a templat
Am 19.05.2013 03:40, schrieb Bill Davidsen:
> It appears the when a kernel upgrade is applied by yum, the rebuild of
> grub2.conf seems to reset the kernel command
> lines to default, dropping options to use working video and network drivers
> and stable clocks. Even the vital
> "nomodeset" opt
On Sat, 18 May 2013 19:35:23 -0700
Joe Zeff wrote:
> On 05/18/2013 06:40 PM, Bill Davidsen wrote:
> >
> >
> > So is dropping the kernel command line options a bug, or deliberate
> > policy?
>
> Neither. When you install a new kernel, the file is rebuilt, using
> /etc/default/grub as a template
On 05/18/2013 06:40 PM, Bill Davidsen wrote:
So is dropping the kernel command line options a bug, or deliberate policy?
Neither. When you install a new kernel, the file is rebuilt, using
/etc/default/grub as a template. If you need to add something
permanently, you need to add it there.
It appears the when a kernel upgrade is applied by yum, the rebuild of
grub2.conf seems to reset the kernel command lines to default, dropping options
to use working video and network drivers and stable clocks. Even the vital
"nomodeset" option is dropped from the old stanzas in the original gru
