thr3ads.net - Syslinux - [syslinux] no boot, no message [Jul 2016]

If this information is useful, please help other people find it:
Share via:

Jorge Almeida

2016-Jul-07 15:43 UTC

[syslinux] no boot, no message

On Thu, Jul 7, 2016 at 8:00 AM, Ady Ady via Syslinux <syslinux at
zytor.com> wrote:>
>>
> We would need at least:
>
> A_ the partitions and directory structure in which the following items
> are _located_ :
/dev/sda1:

#  tree .
.
??? extlinux
?   ??? ldlinux.c32
?   ??? ldlinux.sys
?   ??? libcom32.c32
?   ??? libmenu.c32
?   ??? libutil.c32
?   ??? menu.c32
?   ??? poweroff.c32
?   ??? poweroff.com
?   ??? reboot.c32
?   ??? syslinux.cfg
?   ??? syslinux.cfg~
?   ??? vesamenu.c32
??? gentoo
?   ??? vmlinuz -> vmlinuz-3.16.2
?   ??? vmlinuz-3.16.2
??? lost+found
??? slackware
    ??? vmlinuz-huge-4.4.14

4 directories, 15 files

#  cat syslinux.cfg
#UI menu.c32
DEFAULT menu.c32
#UI vesamenu.c32
#DEFAULT gentoo
#DEFAULT slack64
PROMPT 0
MENU TITLE Boot Menu
#MENU BACKGROUND default_blue.png
MENU RESOLUTION 1024 768
#MENU HIDDEN
#MENU HIDDENKEY Space
# hwinfo --framebuffer  (to find which resolutions are acceptable)
TIMEOUT 50

MENU WIDTH 78
MENU MARGIN 4
MENU ROWS 5
MENU VSHIFT 10
MENU TIMEOUTROW 13
MENU TABMSGROW 11
MENU CMDLINEROW 11
MENU HELPMSGROW 16
MENU HELPMSGENDROW 29

MENU COLOR border       30;44   #40ffffff #a0000000 std
MENU COLOR title        1;36;44 #9033ccff #a0000000 std
MENU COLOR sel          7;37;40 #e0ffffff #20ffffff all
MENU COLOR unsel        37;44   #50ffffff #a0000000 std
MENU COLOR help         37;40   #c0ffffff #a0000000 std
MENU COLOR timeout_msg  37;40   #80ffffff #00000000 std
MENU COLOR timeout      1;37;40 #c0ffffff #00000000 std
MENU COLOR msg07        37;40   #90ffffff #a0000000 std
MENU COLOR tabmsg       31;40   #30ffffff #00000000 std


LABEL  slack64
        MENU LABEL Slackware 14.2
        LINUX ../slackware/vmlinuz--huge-4.4.14
        APPEND root=/dev/sda7

LABEL gentoo
        MENU LABEL Gentoo
        LINUX ../gentoo/vmlinuz
        APPEND root=/dev/sda2
#       APPEND root=UUID=b2bbb1f8-972f-401c-9515-df3483834185

#
#LABEL gentoo
#       MENU LABEL Gentoo
#       LINUX ../gentoo/vmlinuz
##      APPEND root=/dev/sda1
#       APPEND root=PARTUUID=645c1577-e5d7-41eb-9c43-bfee52088197
#

LABEL gentoo_uuid
        MENU LABEL Gentoo (UUID)
        LINUX ../gentoo/vmlinuz
#       APPEND root=/dev/sda2
        APPEND root=UUID=b2bbb1f8-972f-401c-9515-df3483834185




MENU SEPARATOR

LABEL reboot
        MENU LABEL Reboot
        COM32 reboot.c32

LABEL poweroff
        MENU LABEL Power Off
        COMBOOT poweroff.com

MENU CLEAR


#  gdisk -l /dev/sda
GPT fdisk (gdisk) version 0.8.10

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 3907029168 sectors, 1.8 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 3C4B042A-0885-4F86-A10E-FC3F72E25128
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 3907029134
Partitions will be aligned on 2048-sector boundaries
Total free space is 2648225901 sectors (1.2 TiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048          514047   250.0 MiB   8300  Linux filesystem
   2          514048        42457087   20.0 GiB    8300  Linux filesystem
   3        42457088        84400127   20.0 GiB    8300  Linux filesystem
   4        84400128       503830527   200.0 GiB   8300  Linux filesystem
   5       503830528      1132976127   300.0 GiB   8300  Linux filesystem
   6      1132976128      1174919167   20.0 GiB    8300  Linux filesystem
   7      1174919168      1258805247   40.0 GiB    8300  Linux filesystem


Command (? for help): i
Partition number (1-7): 1
Partition GUID code: 0FC63DAF-8483-4772-8E79-3D69D8477DE4 (Linux filesystem)
Partition unique GUID: C66B0D94-4F3C-47E9-8630-141B5CC37B97
First sector: 2048 (at 1024.0 KiB)
Last sector: 514047 (at 251.0 MiB)
Partition size: 512000 sectors (250.0 MiB)
Attribute flags: 0000000000000004
Partition name: 'Linux filesystem'


#  lsattr extlinux/
---------------- extlinux/poweroff.c32
---------------- extlinux/reboot.c32
---------------- extlinux/libcom32.c32
---------------- extlinux/vesamenu.c32
---------------- extlinux/syslinux.cfg~
----i----------- extlinux/ldlinux.sys
---------------- extlinux/libmenu.c32
---------------- extlinux/syslinux.cfg
---------------- extlinux/libutil.c32
---------------- extlinux/poweroff.com
---------------- extlinux/ldlinux.c32
---------------- extlinux/menu.c32


TIA

Jorge

>
> A1_ each of the kernels + initrd + any other file relevant to the boot
> process and/or mentioned in the syslinux.cfg file;
>
> A2_ the syslinux.cfg file;
>
> A3_ any file related to EXTLINUX, such as "ldlinux.*" and
"*.c32"
> modules;
>
> B_ the complete content of the syslinux.cfg file.
>
> Probably by using "PROMPT 1", no TIMEOUT and no (vesa)menu.c32,
some
> message might show up. Let's see first the required info.
>
> Regards,
> Ady.
>
>> _______________________________________________
>> Syslinux mailing list
>> Submissions to Syslinux at zytor.com
>> Unsubscribe or set options at:
>> http://www.zytor.com/mailman/listinfo/syslinux
>
>
>
> _______________________________________________
> Syslinux mailing list
> Submissions to Syslinux at zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux

Ady Ady

2016-Jul-07 16:06 UTC

head link

[syslinux] no boot, no message

> On Thu, Jul 7, 2016 at 8:00 AM, Ady Ady via Syslinux <syslinux at
zytor.com> wrote:
> >
> 
> >>
> > We would need at least:
> >
> > A_ the partitions and directory structure in which the following items
> > are _located_ :
> 
> /dev/sda1:
> 
> #  tree .
> .
> ??? extlinux
> ?   ??? ldlinux.c32
> ?   ??? ldlinux.sys
> ?   ??? libcom32.c32
> ?   ??? libmenu.c32
> ?   ??? libutil.c32
> ?   ??? menu.c32
> ?   ??? poweroff.c32
> ?   ??? poweroff.com
> ?   ??? reboot.c32
> ?   ??? syslinux.cfg
> ?   ??? syslinux.cfg~
> ?   ??? vesamenu.c32
> ??? gentoo
> ?   ??? vmlinuz -> vmlinuz-3.16.2
> ?   ??? vmlinuz-3.16.2
> ??? lost+found
> ??? slackware
>     ??? vmlinuz-huge-4.4.14

Let's take note of this file name:

vmlinuz-huge-4.4.14
> 
> 4 directories, 15 files
> 
> #  cat syslinux.cfg
> #UI menu.c32
> DEFAULT menu.c32
> #UI vesamenu.c32
> #DEFAULT gentoo
> #DEFAULT slack64
> PROMPT 0
> MENU TITLE Boot Menu
> #MENU BACKGROUND default_blue.png
> MENU RESOLUTION 1024 768
> #MENU HIDDEN
> #MENU HIDDENKEY Space
> # hwinfo --framebuffer  (to find which resolutions are acceptable)
> TIMEOUT 50
> 
> MENU WIDTH 78
> MENU MARGIN 4
> MENU ROWS 5
> MENU VSHIFT 10
> MENU TIMEOUTROW 13
> MENU TABMSGROW 11
> MENU CMDLINEROW 11
> MENU HELPMSGROW 16
> MENU HELPMSGENDROW 29
> 
> MENU COLOR border       30;44   #40ffffff #a0000000 std
> MENU COLOR title        1;36;44 #9033ccff #a0000000 std
> MENU COLOR sel          7;37;40 #e0ffffff #20ffffff all
> MENU COLOR unsel        37;44   #50ffffff #a0000000 std
> MENU COLOR help         37;40   #c0ffffff #a0000000 std
> MENU COLOR timeout_msg  37;40   #80ffffff #00000000 std
> MENU COLOR timeout      1;37;40 #c0ffffff #00000000 std
> MENU COLOR msg07        37;40   #90ffffff #a0000000 std
> MENU COLOR tabmsg       31;40   #30ffffff #00000000 std
> 
> 
> LABEL  slack64
>         MENU LABEL Slackware 14.2
>         LINUX ../slackware/vmlinuz--huge-4.4.14
>         APPEND root=/dev/sda7
For convenience, I'll repeat the file name we took note above:

vmlinuz-huge-4.4.14

and we should compare it with the one being used in the syslinux.cfg:

vmlinuz--huge-4.4.14

Do you note the extra dash symbol "-"?

> 
> LABEL gentoo
>         MENU LABEL Gentoo
>         LINUX ../gentoo/vmlinuz
>         APPEND root=/dev/sda2
> #       APPEND root=UUID=b2bbb1f8-972f-401c-9515-df3483834185
> 
> #
> #LABEL gentoo
> #       MENU LABEL Gentoo
> #       LINUX ../gentoo/vmlinuz
> ##      APPEND root=/dev/sda1
> #       APPEND root=PARTUUID=645c1577-e5d7-41eb-9c43-bfee52088197
> #
> 
> LABEL gentoo_uuid
>         MENU LABEL Gentoo (UUID)
>         LINUX ../gentoo/vmlinuz
> #       APPEND root=/dev/sda2
>         APPEND root=UUID=b2bbb1f8-972f-401c-9515-df3483834185
> 
> 
> 
> 
> MENU SEPARATOR
> 
> LABEL reboot
>         MENU LABEL Reboot
>         COM32 reboot.c32
> 
> LABEL poweroff
>         MENU LABEL Power Off
>         COMBOOT poweroff.com
> 
> MENU CLEAR
> 
> 
> #  gdisk -l /dev/sda
> GPT fdisk (gdisk) version 0.8.10
> 
> Partition table scan:
>   MBR: protective
>   BSD: not present
>   APM: not present
>   GPT: present
> 
> Found valid GPT with protective MBR; using GPT.
> Disk /dev/sda: 3907029168 sectors, 1.8 TiB
> Logical sector size: 512 bytes
> Disk identifier (GUID): 3C4B042A-0885-4F86-A10E-FC3F72E25128
> Partition table holds up to 128 entries
> First usable sector is 34, last usable sector is 3907029134
> Partitions will be aligned on 2048-sector boundaries
> Total free space is 2648225901 sectors (1.2 TiB)
> 
> Number  Start (sector)    End (sector)  Size       Code  Name
>    1            2048          514047   250.0 MiB   8300  Linux filesystem
>    2          514048        42457087   20.0 GiB    8300  Linux filesystem
>    3        42457088        84400127   20.0 GiB    8300  Linux filesystem
>    4        84400128       503830527   200.0 GiB   8300  Linux filesystem
>    5       503830528      1132976127   300.0 GiB   8300  Linux filesystem
>    6      1132976128      1174919167   20.0 GiB    8300  Linux filesystem
>    7      1174919168      1258805247   40.0 GiB    8300  Linux filesystem
> 
> 
> Command (? for help): i
> Partition number (1-7): 1
> Partition GUID code: 0FC63DAF-8483-4772-8E79-3D69D8477DE4 (Linux
filesystem)
> Partition unique GUID: C66B0D94-4F3C-47E9-8630-141B5CC37B97
> First sector: 2048 (at 1024.0 KiB)
> Last sector: 514047 (at 251.0 MiB)
> Partition size: 512000 sectors (250.0 MiB)
> Attribute flags: 0000000000000004
> Partition name: 'Linux filesystem'
> 
> 
> #  lsattr extlinux/
> ---------------- extlinux/poweroff.c32
> ---------------- extlinux/reboot.c32
> ---------------- extlinux/libcom32.c32
> ---------------- extlinux/vesamenu.c32
> ---------------- extlinux/syslinux.cfg~
> ----i----------- extlinux/ldlinux.sys
> ---------------- extlinux/libmenu.c32
> ---------------- extlinux/syslinux.cfg
> ---------------- extlinux/libutil.c32
> ---------------- extlinux/poweroff.com
> ---------------- extlinux/ldlinux.c32
> ---------------- extlinux/menu.c32
> 
> 
> TIA
> 
> Jorge
> 
> 
I could post some additional comments / suggestions, but perhaps this 
is just a simple typo issue?

Regards,
Ady.

Didier Spaier

2016-Jul-07 16:53 UTC

head link

[syslinux] no boot, no message

[quoted lines from Ady on 07/07/2016 18:06]
<snip>> vmlinuz-huge-4.4.14
> 
> and we should compare it with the one being used in the syslinux.cfg:
> 
> vmlinuz--huge-4.4.14
> 
> Do you note the extra dash symbol "-"?
<snip>> I could post some additional comments / suggestions, but perhaps this 
> is just a simple typo issue?
Very likely. I have the same kernel installed and it is named
vmlinuz-huge-4.4.14, so removing the extra dash in syslinux.cfg is worth
trying.

Didier

Jorge Almeida

2016-Jul-07 17:13 UTC

head link

[syslinux] no boot, no message

On Thu, Jul 7, 2016 at 9:06 AM, Ady Ady via Syslinux <syslinux at
zytor.com> wrote:>
>
> vmlinuz-huge-4.4.14
>
>
> vmlinuz--huge-4.4.14
>
>
> I could post some additional comments / suggestions, but perhaps this
> is just a simple typo issue?
Indeed it is, and I can't believe how much time I lost with this. Thanks.

If you had suggestions on how to make syslinux spill out some error
message in such a case (kernel not found...) it would be great. I was
not able to find it in the documentation.

Jorge

Reasonably Related Threads

Search for more possibly parallel threads

Syslinux - Jul 2016 - no boot, no message

[syslinux] no boot, no message

[syslinux] no boot, no message

[syslinux] no boot, no message

[syslinux] no boot, no message

Reasonably Related Threads