[syslinux] extlinux from syslinux 4.04 failed hard after choosing bzImage.

Tyler Durden tylerdu at bounced.me
Sat Nov 19 16:57:35 PST 2011


On 20.11.2011 01:27, Gene Cumm wrote:
> On Nov 19, 2011 7:17 PM, "Gene Cumm"<gene.cumm at gmail.com>  wrote:
>>
>> On Sat, Nov 19, 2011 at 18:03, Tyler Durden<tylerdu at bounced.me>  wrote:
>>> On 19.11.2011 16:11, Piotr Karbowski wrote:
>>>>
>>>> Hi,
>>>>
>>>> Today I replaced grub(1) with syslinux on my laptop, after rebooting to
>>>> syslinux and selecting kernel I got massive freeze along with colorful
>>>> output to screen - http://i.imgur.com/lFjFc.jpg
>>>>
>>>> I think I tried everything, even doing esc and writing after boot:
>>>> /bzImage-3.1.0, after enter I had the same freeze with the same screen
>>>> artefacts.
>>>>
>>>
>>> Last week I stumbled across the same bug. Couldn't boot kernel 3.1.0
> with
>>> exactly the same symptoms as you (screen full of weird characters).
>>> Fortunately, there's a simple workaround I found here:
>>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=647603
>>>
>>> Just rename the kernel image to something that doesn't end with zero
> (e.g.
>>> bzImage-3.1) and it will boot just fine.
>>>
>>> Somehow extlinux chokes on kernel image names with zero in the last
> place.
>>> Strange...
>>
>> It's a feature for the file type "guessing" documented in
>> syslinux.txt.  I should have seen that one.
>
> Try the LINUX directive instead KERNEL.  ".0" means NBP (network boot
> program.
>

Yep, that fixes it properly, just tested. Thanks Gene!

So, it seems this is a Debian bug after all. It's extlinux-update script 
populates linux.cfg file with "kernel" directives, but it should use 
"linux" instead.
-- 
Tyler




More information about the Syslinux mailing list