Bug#567239: grub-pc 1.98~20100126-1 fails to boot.

[Jos van Wolput]

Felix Zielcke wrote:
> Am Freitag, den 29.01.2010, 12:03 +0800 schrieb Jos van Wolput:
>   
>> Robert Millan wrote:
>>     
>>> What happens if you use the legacy "linux16" loader?
>>>
>>>   
>>>       
>>>> This buggy version of grub-pc  shows  a  lot  more output  than  the   
>>>> previous  one.
>>>>     
>>>>         
>>> Which output?
>>>   
>>>       
>> I don't know about 'the legacy "linux16" loader', can't find that 
>> package and don't intend to try other bootloaders,
>> I'm sorry, I really don't want more booting problems.
>>     
>
> He meant using linux16 and initrd16 command instead of the usual linux
> and initrd ones in your menuentry in GRUB.
>
>   
>> 'Which output?' I mean the output you always see on the screen when booting. It is much more than usual.
>>     
>
> Maybe the quiet Linux kernel option somehow got lost. Then you get much
> more output from it during boot.
>
>   
>> For your information I mention I am using runit, sysvinit and file-rc (the Sid versions) for booting.
>>
>> To avoid booting failures I would suggest you put buggy versions of grub-pc in the experimental distribution 
>> before putting them in Sid!
>>     
>
> We use experimental but unfortunately bugs slip through because they
> don't get much testing.
> We test of course ourself the uploads if they work for us. But as you
> see we aren't able to test every bug which could stop booting.
>   
Thanks for your additional info about linux16!
In the file /etc/grub.d/10_linux I replaced the commands linux and 
initrd by linux16 and initrd16, ran update-grub
and rebooted using grub-pc v.1.98~20100128-1 with KMS enabled.
My system now boots normally, without any problem. The output on the 
screen too looks normal.
Do I need to keep these changes in 10_linux after the next upgrade of 
grub-pc?