Displaying 3 results from an estimated 3 matches for "972f".
Did you mean:
972
2016 Jul 07
3
no boot, no message
...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...
2016 Jul 07
0
no boot, no message
...uld 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 (UU...
2016 Jul 07
3
no boot, no message
I have syslinux 5.10 on a 32bit gentoo system. It boots fine. Now I
installed another linux system in other partitions of the same drive
(a 64 bit system), updated syslinux.cfg, setup the new system as
default, and the new entry appears in the menu. Problem is: it doesn't
boot. On timeout, it starts counting down again, and that's it. No
error message whatsoever. Selecting the old system