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 by hand boots it as
usual.
Is it normal for extlinux to not produce an error message?
The extlinux partition is sda1, with ext2 fs. The motherboard is ASUS
H97-PRO. It is configured to work in CSM mode. Some maybe relevant data:
description: Desktop Computer
product: All Series (All)
vendor: ASUS
version: System Version
serial: System Serial Number
width: 32 bits
capabilities: smbios-2.8 dmi-2.7 smp-1.4 smp
configuration: administrator_password=disabled boot=normal
chassis=desktop cpus=2 family=ASUS MB frontpanel_password=disabled
keyboard_password=disabled power-on_password=disabled sku=All
uuid=E0B2C736-DAD7-DD11-AB81-40167EAD5491
*-core
description: Motherboard
product: H97-PRO
vendor: ASUSTeK COMPUTER INC.
physical id: 0
version: Rev X.0x
serial: 140526027201371
slot: To be filled by O.E.M.
*-firmware
description: BIOS
vendor: American Megatrends Inc.
physical id: 0
version: 0333
date: 05/08/2014
size: 64KiB
capacity: 15MiB
capabilities: pci apm upgrade shadowing cdboot bootselect
socketedrom edd int13floppy1200 int13floppy720 int13floppy2880
int5printscreen int9keyboard int14serial int17printer acpi usb
biosbootspecification uefi
*-cpu:0
description: CPU
product: Intel(R) Core(TM) i3-4150 CPU @ 3.50GHz
vendor: Intel Corp.
physical id: 46
bus info: cpu at 0
version: 6.12.3
serial: 0003-06C3-0000-0000-0000-0000
slot: SOCKET 1150
size: 3500MHz
capacity: 3900MHz
width: 64 bits
clock: 100MHz
capabilities: x86-64 boot fpu fpu_exception wp vme de pse
tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts
acpi mmx fxsr sse sse2 ss ht tm pbe nx pdpe1gb rdtscp constant_tsc
arch_perfmon pebs bts xtopology nonstop_tsc aperfmperf eagerfpu pni
pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 fma cx16 xtpr pdcm
pcid sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes xsave avx f16c
rdrand lahf_lm abm arat epb xsaveopt pln pts dtherm tpr_shadow vnmi
flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms
invpcid cpufreq
configuration: cores=2 enabledcores=2 id=0 threads=4
Thanks,
Jorge Almeida
On Thu, Jul 7, 2016 at 5:09 AM, Jorge Almeida via Syslinux <syslinux at zytor.com> wrote:> 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 by hand boots it as > usual. > > Is it normal for extlinux to not produce an error message?EXTLINUX (boot loader) was merged with SYSLINUX back in v4.00. extlinux (installer) and syslinux still both exist but the former is for mounted file systems while the latter is for unmounted FAT* file systems. It is common for (vesa)menu.c32 to hide the error. Your best bet is executing the new system's LABEL outside of menu.c32 to see the error. -- -Gene
> 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 driveHmm, partitions... OK.> (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 by hand boots it as > usual. > > Is it normal for extlinux to not produce an error message?It depends on the "error". The menu combined with the timeout might be overwriting any (error) message on the screen.> > The extlinux partition is sda1, with ext2 fs. The motherboard is ASUS > H97-PRO. It is configured to work in CSM mode. Some maybe relevant data:(snip)> > > > Thanks, > > Jorge AlmeidaWe would need at least: A_ the partitions and directory structure in which the following items are _located_ : 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
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