Sponsored Content
Top Forums UNIX for Dummies Questions & Answers How to get grub to launch isolinux/syslinux boot menu. Post 302424870 by Fishi on Wednesday 26th of May 2010 12:43:11 PM
Old 05-26-2010
Hi,
my english is very bad .....Smilie

GRUB can not boot SYSLINUX , but GRUB.EXE can boot SYSLINUX
The way is:
GRUB to GRUB.EXE to SYSLINUX

My Situation:

I have grub installed on hd0,0

My Rescue SD-Card is hd1,0 with syslinux
I have the file /boot/grub/grub.exe on hd1,0 !!!!!!!!!Smilie

menu.lst from grub on hd0,0
Code:
title     Rescue SD-Card
root      (hd1,0)
kernel    /boot/grub/grub.exe --config-file="map (hd1,0)+1 (fd0); map --hook; root (fd0); chainloader +1; boot"

by Fishi
 

10 More Discussions You Might Find Interesting

1. Red Hat

linux will not boot, boot to grub prompt

my redhat 9 will not boot. We had a power failure and when the power came back, my redhat linux will not boot. The machine come up to grub prompt. I tried the following from grub prompt root (hd0, then press tab key partition num:0 filesystem type unknown, partition type 0x83... (7 Replies)
Discussion started by: hassan2
7 Replies

2. Solaris

Solaris X86 grub boot menu

I have a x4200 m2 that I've installed Solaris 10 on. I've created a raid 1 mirror using disk0 and disk1. I'm trying to add the mirror bootblk to the grub menu so in case of a failure of disk0, I can simply boot from the mirrored disk1. I'm looking for the syntax to add the alternate boot path to... (5 Replies)
Discussion started by: gonzotonka
5 Replies

3. Red Hat

Server won't boot up ... no GRUB menu

I dont know what the heck happen but one of our DBAs was working on a cluster for oracle. Rebooted the box and viola, the OS won't load. After the POST message, I get a blinking cursor on the upper left hand corner. Doesn't even say "GRUB" or anything, it just blinks. I tried going into rescue... (1 Reply)
Discussion started by: sdotsen
1 Replies

4. Emergency UNIX and Linux Support

Grub Doesn't show menu

Hi guys. I have installed Acronis disk director in windows XP and allocate some free space to install Debian beside fedora. after completion i rebooted and now grub is in command line mode and does not show the menu list. (I didn't remove the fedora partition. I just allocate some space from... (1 Reply)
Discussion started by: majid.merkava
1 Replies

5. Boot Loaders

GRUB not showing a menu

Hi there, I had a double boot of Windows 7 and Ubuntu 10.04. After messing up with UBUNTU I reinstalled it. But then Grub did not noticed the existence of my windows and it just boot into linux. I booted with windows 7 installation CD which noticed a problem with my booting and suggest to repair... (2 Replies)
Discussion started by: Nazarbaz
2 Replies

6. Red Hat

Not able to see the terminal icon in the applications menu to launch the command prompt in Centos

After installing centos iam not able to see the terminal icon in the applications menu to launch the command prompt in Centos. However iam able to see the Open Terminal menu, when i right click and it is not working. let me know what are the things i need to check.:b: (1 Reply)
Discussion started by: Kesavan
1 Replies

7. UNIX for Dummies Questions & Answers

Enter SYSLinux bootmenu from GRUB 2

hello guys! i found this thread on the internet and registered right here in this community. on a USB-drive i installed Debian. boot manager is GRUB 2 (1.99) . in a folder within my Debian i have some ISO-images of some linux-distros and other live-systems. one of these is Parted Magic,... (0 Replies)
Discussion started by: J0CH3N
0 Replies

8. Solaris

How to specify local boot up disk in CD boot Grub?

Hi Solaris 10 Experts, I am wondering what is the correct syntax to edit in Grub when trying to specify the local ZFS boot disk while booting up from a Solaris 10 x86 64bits DVD installation disk. In other word, I try to boot up from local disk without removing the Solaris installation disk... (0 Replies)
Discussion started by: gjackson123
0 Replies

9. UNIX for Beginners Questions & Answers

GRUB 2 Menu

The quick & dirty question I have is... What app/script actually loads the Grub 2 menu system? And where is it located? The longer question is I understand the core.img is loaded onto the first 63 sectors (stage 1.5) and after it loads I starts the stage 2 Grub bootloader which loads the Menu... (0 Replies)
Discussion started by: bodisha
0 Replies

10. Solaris

How to recover x86 Solaris 10 u10 boot record/grub menu overwritten by Debian 9?

I installed x86 Solaris 10 update 10 after Windows XP, later I removed xp and installed Debian 9 stretch on the same partition but, Debian couldn't find any other os so it deleted Solaris 10 grub or did something like that I couldn't got. I thought I would be able to recover the lost record by... (0 Replies)
Discussion started by: vectrum
0 Replies
Makebootfat Bootable FAT Disk Creation(1)		      General Commands Manual			 Makebootfat Bootable FAT Disk Creation(1)

NAME
makebootfat - Makebootfat Bootable FAT Disk Creation SYNOPSIS
makebootfat [options] IMAGE DESCRIPTION
This utility creates a bootable FAT filesystem and populates it with files and boot tools. It is mainly designed to create bootable USB and Fixed disk for the AdvanceCD project. The official site of AdvanceCD and makebootfat is: http://advancemame.sourceforge.net/ OPTIONS
-o, --output DEVICE Specify the output device. It must be the device where you want to setup the filesystem. You can use the special "usb" value to automatically select the USB Mass Storage device connected at the system. This option is always required. -b, --boot FILE -1, --boot-fat12 FILE -2, --boot-fat16 FILE -3, --boot-fat32 FILE Specify the FAT boot sector images to use. The -b option uses the same sector for all the FAT types. The other options can be used to specify a different sector for different FAT types. The FAT types for which a boot sector is not specified are not used. This option is always required. -m, --mbr FILE Specify the MBR sector image to use. If this option is specified a partition table is created on the disk. Otherwise the disk is filled without a partition table like a floppy disk. -F, --mbrfat Change the MBR image specified with the -m option to pretend to be a FAT filesystem starting from the first sector of the disk. This allows booting from USB-FDD (Floppy Disk Drive) also using a partition table generally required by USB-HDD (Hard Disk Drive). The MBR image specified with the -m option must have executable code positioned like a FAT boot sector. You can use the included 'mbr- fat.bin' file. -c, --copy FILE Copy the specified file in the root directory of the disk. The file is copied using the readonly attribute. -x, --exclude FILE Exclude the specified files and subdirectories in the IMAGE directory to copy. The path must be specified using the same format used in the IMAGE directory specification. -X, --syslinux2 Enforce the syslinux 2.xx FAT limitations. Syslinux 2.xx doesn't support FAT32 at all, and FAT16 with 64 and 128 sectors per cluster formats. This option excludes all the FAT formats not supported by syslinux. Please note that it limits the maximum size of filesystem to 1 GB. -Y, --syslinux3 Enforce the syslinux 3.xx FAT support. Syslinux 3.00 supports all the FAT types and sizes but it requires a special customisation of the boot sector and of the file 'ldlinux.sys'. This option does this customisation without the need to use the syslinux installer if the 'ldlinux.sys' file is copied on disk with the -c option. -Z, --zip If possible force the ZIP-Disk compatibility. It sets a geometry of 32 sectors and 64 heads. It also uses the 4'th partition entry in the partition table. It's required to boot also in USB-ZIP mode. -P, --partition Ensure to operate on a partition and not on a disk. -D, --disk Ensure to operate on a disk and not on a partition. -L, --label LABEL Set the FAT label. The label is a string of 11 chars. -O, --oem OEM Set the FAT OEM name. The OEM name is a string of 11 chars. -S, --serial SERIAL Set the FAT serial number. The serial number is a 32 bit unsigned integer. -E, --drive DRIVE Set the BIOS drive to setup in the FAT boot sector. Generally this value is ignored by boot sectors, with the exception of the FAT12 and FAT16 FreeDOS boot sectors that require the correct value or the value 255 to force auto detection. -v, --verbose Print some information on the device and on the filesystem created. -i, --interactive Show the errors in a message box. Only for Windows. -h, --help Print a short help. -V, --version Print the version number. IMAGE Directory image to copy on the disk. All the files and subdirectories present in this directory are copied on the disk. DISKS AND PARTITIONS NAMES
In Linux disk devices are named /dev/hdX or /dev/sdX where X is a letter. Partition devices are named /dev/hdXN or /dev/sdXN where X is a letter and N a digit. In Windows disk devices are named \.PhysicalDriveN where N is a digit. Partition devices are named \.X: where X is a letter, but some- times \.X: is a disk and not a partition, for example on floppies and on all the USB Mass Storage devices without a partition table. SYSLINUX
To make a bootable FAT using syslinux you must use the -X option for syslinux version 2.xx or the -Y option for syslinux version 3.xx. You must also copy in the root directory of the disk the files: ldlinux.sys The syslinux loader. syslinux.cfg The syslinux configuration file. linux The Linux kernel image (the file name may be different). initrd.img The initrd filesystem (the file name may be different or missing). You must also specify the 'ldlinux.bss' boot sector with the -b option and possibily the 'mbr.bin' MBR sector with the -m option. Both the sector images are present in the syslinux package. For example: makebootfat -o usb -Y -b ldlinux.bss -m mbr.bin -c ldlinux.sys -c syslinux.cfg -c linux -c initrd.img image LOADLIN AND FREEDOS
To make a bootable FAT using loadlin and FreeDOS you must copy in the root directory of the disk the files: kernel.sys The FreeDOS kernel. Remember to use the "32" kernel version to support FAT32. command.com The FreeDOS shell. autoexec.bat Used to start loadlin. loadlin.exe The loadlin executable. linux The Linux kernel image (the file name may be different). initrd.img The initrd filesystem (the file name may be different or missing). You must also specify the FreeDOS boot sectors available on the FreeDOS 'sys' source package with the -1, -2, -3 option. For the MBR you can use the sectors image available on the FreeDOS 'fdisk' source package. For example: makebootfat -o /dev/hda1 -E 255 -1 fat12com.bin -2 fat16com.bin -3 fat32lba.bin -c kernel.sys -c command.com -c autoexec.bat -c loadlin.exe -c linux -c initrd.img image MULTI STANDARD USB BOOTING
The BIOS USB boot support is generally differentiated in three categories: USB-HDD, USB-FDD and USB-ZIP. The USB-HDD (Hard Disk Drive) standard is the preferred choice and it requires the presence of a partition table in the first sector of the disk. You can create this type of disk using the -m option. The USB-FDD (Floppy Disk Drive) standard requires the presence of a filesystem starting from the first sector of the disk without a parti- tion table. You can create this type of disk without using the -m option. The USB-ZIP (ZIP Drive) standard requires the presence of a device with a very specific geometry. Specifically, it requires a geometry with 32 sectors and 64 heads. It also requires the presence of a partition table with only a bootable partition in the fourth entry. You can create this type of disk using the -m and -Z option. Generally these standards are incompatible, but using the -m, -F and -Z options you can create a disk compatible with all of them. To use the -F option, the MBR image specified must follow the constrains: o It must start with a standard FAT 3 bytes jump instruction. o It must have the bytes from address 3 to 89 (included) unused. And example of such image is in the 'mbrfat.bin' file. For example to create a syslinux image: makebootfat -o usb -Y -Z -b ldlinux.bss -m mbrfat.bin -F -c ldlinux.sys -c syslinux.cfg -c linux -c initrd.img image and for a FreeDOS and loadlin image: makebootfat -o usb -E 255 -Z -1 fat12com.bin -2 fat16com.bin -3 fat32chs.bin -m mbrfat.bin -F -c kernel.sys -c command.com -c autoexec.bat -c loadlin.exe -c linux -c initrd.img image Please note that FreeDos has some problems booting from USB. It works only on very few conditions. EXCLUSION
To exclude some files or directories in the image copy, you can use the -x option using the same path specification which are you using for the image directory. For example, if you need to exclude the 'isolinux' and 'syslinux' subdirectories from the 'image' directory you can use the command: makebootfat ... -x image/isolinux -x image/syslinux image COPYRIGHT
This file is Copyright (C) 2004, 2005 Andrea Mazzoleni SEE ALSO
syslinux(1), mkdosfs(1), dosfsck(1) Makebootfat Bootable FAT Disk Creation(1)
All times are GMT -4. The time now is 03:47 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy