:: Re: [DNG] devuan-jessie-i386-alpha4…
トップ ページ
このメッセージを削除
このメッセージに返信
著者: Haines Brown
日付:  
To: dng
題目: Re: [DNG] devuan-jessie-i386-alpha4-netboot.iso has AMD64 files?
On Sun, Apr 24, 2016 at 05:53:38AM +0200, aitor_czr wrote:
>
> On 04/24/2016 12:57 AM, Haines Brown <haines@???> wrote:
>
>     I downloaded devuan-jessie-i386-alpha4-netboot.iso and installed it on a
>     key with unetbootin. However, it would not boot, and when I looked more
>     closely at it I find that its /boot directory has the initrd0.amd
>     vmlinuz0.amd.

>
>     Was the reason for my key not booting that it is for an AMD64 system?
>     Is not devuan-jessie-i386-alpha4-netboot.iso for a 32 bit system?

>
>     Haines Brown

>
>
> Unetbootin generates a file named syslinux.cfg in the parent directory of the
> USB stick. You can modify it because the stick is not protected, unlike using
> dd. Here you are an example:
>
> default menu.c32
> prompt 0
> menu title [...]
> timeout 100
>
> label ubnentry0
>   menu label ^[...]
>   kernel /live/vmlinuz
>   append initrd=/live/initrd.img boot=live config locales=en_US.UTF-8 keyb=es
> quiet splash
>
> label ubnentry1
>   [... etc ...]
>
> Use the content of isolinux/menu.cfg for that.


Aitor, I had a little trouble following your suggestion. I assume the
second and third stanza in the example is what appears in menu.cfg and
so does affect what gets booted.

Syslinux automatically boots the /linux file although bootloaders
usually load a vmlinuz file, which in the present case is
boot/vmlinuz0.amd. That's a strange name for a vmlinuz file in a i386
system. If it is loaded and is an AMD64 file, it is not surprising the
bootloader fails to work. Or rather, because the linux file is booted,
are the vmlinuz0.amd and initrd0.amd files simply ignored?

I understand the two label stanzas above are in menu.cfg. The example of
the syslinux.cfg you describe is essentially what I already have.

Your example:

default menu.c32
prompt 0
menu title [...]
timeout 100

What I have:

path
include menu.cfg
default /menu.c32
prompt 0
timeout 0

I could change prompt to 1 and timeout to 5, bring my system down, and
at the boot: prompt try: boot: /linux or boot: vmlinuz0.amd.

Haines Brown