電腦啟動時,會先加載MBR (/usr/lib/syslinux/mbr.bin
),然后MBR查找那些活動的分區(qū)(標注了可啟動的),找到這個分區(qū)后,卷啟動記錄程序(VBR=volume boot record)將被執(zhí)行。如果是ext2/3/4和fat 12/16/32,ldlinux.sys
開始的扇區(qū)是被寫死進卷啟動記錄程序里的,卷啟動記錄程序將執(zhí)行(ldlinux.sys
)。當然,如果ldlinux.sys
的位置發(fā)生改變,syslinux將無法加載。如果是btrfs,因為文件不斷移動導致ldlinux.sys
扇區(qū)的位置不斷變化,而讓上面方法失效。從而使得整個syslinux需要被存儲在文件系統(tǒng)之外。程序將被存儲在卷啟動記錄程序之后。
當syslinux完全加載完畢,它將自動尋找一個配置文件,名字叫 extlinux.conf
或者syslinux.cfg
.找到之后,將加載整個配置文件,否則,將給出提示。
syslinux-install_update腳本將自動安裝Syslinux, 復制COM32模塊到/boot/syslinux
, 設置啟動標識,安裝到MBR.可自動根據softraid處理MBR和 GPT磁盤。
下面是過程: 1. 安裝Syslinux
pacman -S syslinux
2. 確認/boot
是否已經加載
3. 運行腳本syslinux-install_update
,參數使用 -i (安裝) -a (設可啟動標識) -m (安裝到mbr)
/usr/sbin/syslinux-install_update -i -a -m
4. 修改配置文件 /boot/syslinux/syslinux.cfg
Make sure you have the syslinux package installed. Then install Syslinux onto your boot partition, which must contain a fat, ext2, ext3, ext4, or btrfs file system.
# mkdir /boot/syslinux# extlinux --install /boot/syslinux #run on a mounted directory (not /dev/sdXY)/boot/syslinux/ is device /dev/sda1
需要標識啟動分區(qū)為激活狀態(tài).可用這些工具實現:fdisk, cfdisk, sfdisk, (g)parted.最后結果看起來是這樣:
# fdisk -l /dev/sda[...] Device Boot Start End Blocks Id System/dev/sda1 * 2048 104447 51200 83 Linux/dev/sda2 104448 625142447 312519000 83 Linux
安裝到主啟動卷區(qū):
# dd bs=440 conv=notrunc count=1 if=/usr/lib/syslinux/mbr.bin of=/dev/sda
Main article GUID_Partition_Table
Bit 2 of the attributes for the /boot
partition need to be set.
# sgdisk /dev/sda --attributes=1:set:2
This would toggle the attribute legacy BIOS bootable on partition 1
Verify:
# sgdisk /dev/sda --attributes=1:show1:2:1 (legacy BIOS bootable)
安裝主啟動卷區(qū):
# dd bs=440 conv=notrunc count=1 if=/usr/lib/syslinux/gptmbr.bin of=/dev/sda
如果此時重啟,會有提示,以確認是自動啟動還是給出一個啟動菜單,此時需要創(chuàng)建一個配置文件。
syslinux的配置文件 syslinux.cfg
必須和syslinux放在同一個目錄下,在我們的例子中,是 '/boot/syslinux/'
啟動器將自動尋找這兩個配置文件:syslinux.cfg
(優(yōu)先) 或者 extlinux.conf
補充:
這是一個非常簡單的配置,有啟動提示,并且在5秒后自動啟動第一個系統(tǒng)。
配置文件:
PROMPT 1TIMEOUT 50DEFAULT archLABEL arch LINUX ../vmlinuz-linux APPEND root=/dev/sda2 ro INITRD ../initramfs-linux.imgLABEL archfallback LINUX ../vmlinuz-linux APPEND root=/dev/sda2 ro INITRD ../initramfs-linux-fallback.img
若不想看到提示,設置PROMPT(顯示時間)為0.
把模塊menu COM32復制到syslinux目錄中,即可使用文本菜單:
# cp /usr/lib/syslinux/menu.c32 /boot/syslinux/
若沒有給/boot單獨分區(qū),且和/usr同一分區(qū),那么,也可以僅使用一個軟鏈接:
# ln -s /usr/lib/syslinux/menu.c32 /boot/syslinux/
配置:
UI menu.c32PROMPT 0MENU TITLE Boot MenuTIMEOUT 50DEFAULT archLABEL arch MENU LABEL Arch Linux LINUX ../vmlinuz-linux APPEND root=/dev/sda2 ro INITRD ../initramfs-linux.imgLABEL archfallback MENU LABEL Arch Linux Fallback LINUX /vmlinuz-linux APPEND root=/dev/sda2 ro INITRD /initramfs-linux-fallback.img
更多信息可見: http://git.kernel.org/?p=boot/syslinux/syslinux.git;a=blob;f=doc/menu.txt.
把vesamenu COM32移入到syslinux目錄中,可使用圖形啟動界面:
# cp /usr/lib/syslinux/vesamenu.c32 /boot/syslinux/
若沒有給/boot單獨分區(qū),且和/usr同一分區(qū),那么,也可以僅使用一個軟鏈接: :
# ln -s /usr/lib/syslinux/vesamenu.c32 /boot/syslinux/
This config uses the same menu design as the Arch Install CD: syslinux.cfg
The background file can be found here: splash.png
Config:
UI vesamenu.c32DEFAULT archPROMPT 0MENU TITLE Boot MenuMENU BACKGROUND splash.pngTIMEOUT 50MENU WIDTH 78MENU MARGIN 4MENU ROWS 5MENU VSHIFT 10MENU TIMEOUTROW 13MENU TABMSGROW 11MENU CMDLINEROW 11MENU HELPMSGROW 16MENU HELPMSGENDROW 29# Refer to http://syslinux.zytor.com/wiki/index.php/Doc/menuMENU COLOR border 30;44 #40ffffff #a0000000 stdMENU COLOR title 1;36;44 #9033ccff #a0000000 stdMENU COLOR sel 7;37;40 #e0ffffff #20ffffff allMENU COLOR unsel 37;44 #50ffffff #a0000000 stdMENU COLOR help 37;40 #c0ffffff #a0000000 stdMENU COLOR timeout_msg 37;40 #80ffffff #00000000 stdMENU COLOR timeout 1;37;40 #c0ffffff #00000000 stdMENU COLOR msg07 37;40 #90ffffff #a0000000 stdMENU COLOR tabmsg 31;40 #30ffffff #00000000 stdLABEL arch MENU LABEL Arch Linux LINUX ../vmlinuz-linux APPEND root=/dev/sda2 ro INITRD ../initramfs-linux.imgLABEL archfallback MENU LABEL Arch Linux Fallback LINUX ../vmlinuz-linux APPEND root=/dev/sda2 ro INITRD ../initramfs-linux-fallback.img
Since Syslinux 3.84 vesamenu.c32 supports the "MENU RESOLUTION $WIDTH $HEIGHT" directive.To use it, insert "MENU RESOLUTION 1440 900" into your config for a 1440x900 resolution.The background picture has to have exactly the right resolution however as syslinux will otherwise refuse to load the menu.
If you want to chainload other operating systems (such as Windows) or boot loaders, copy (or symlink) thechain.c32 module to the syslinux folder (for details, see the instructions in the previous section). Then, create a section in the configuration file:
LABEL windows MENU LABEL Windows COM32 chain.c32 APPEND hd0 3
hd0 3 is the third partition on the first BIOS drive - drives are counted from zero, but partitions are counted from one. For more details about chainloading, see [1].
If you have grub2 installed in your boot partition, you can chainload it by using:
LABEL grub2 MENU LABEL Grub2 COM32 chain.c32 append file=../grub/boot.img
This maybe required for booting from iso images.
使用下面的 LABEL章節(jié)部分,可加載(需要安裝軟件包:memtest86+,否則不起作用):
LABEL memtest MENU LABEL Memtest86+ LINUX ../memtest86+/memtest.bin
HDT (Hardware Detection Tool) displays hardware information. Like before, the .c32 file has to be copied or symlinked from /boot/syslinux/.For pci info either copy or symlink /usr/share/hwdata/pci.ids
to /boot/syslinux/pci.ids
LABEL hdt MENU LABEL Hardware Info COM32 hdt.c32
Use the following sections to reboot or power off your machine.
LABEL reboot MENU LABEL Reboot COM32 reboot.c32LABEL poweroff MENU LABEL Power Off COMBOOT poweroff.com
You can type in the LABEL name of the entry that you want to boot (as per your syslinux.cfg). If you used the example configs just type
boot: arch
If you get an error that the config file could not be loaded you can pass your needed boot parameters, e.g.:
boot: ../vmlinuz-linux root=/dev/sda2 ro initrd=../initramfs-linux.img
If you don't have access to 'boot:' in ramfs, and therefore temporarily unable to boot kernel again
1) create temp directory, in order to mount your root partition (if it doesn't exist already)
mkdir -p /new_root
2) mount / under /new_root (in case /boot/ is on same partition, otherwise you'll need to mount them both)
mount /dev/sd[a-z][1-9] /new_root
3) use 'vi' and edit syslinux.cfg again to suit your needs and save file;
4) reboot
Certain motherboard manufacturers have less compatibility for booting from USB devices than others. While an ext4 formatted usb drive may boot on a more recent computer, some computers may hang if the boot partition containing the kernel and initrd are not on a fat16 partition. to prevent an older machine from loading ldlinux and failing to read syslinux.cfg, use cfdisk to create a fat-16 partition (<=2GB) and format with
# pacman -S dosfstools# mkfs.msdos -F 16 /dev/sda1
then install and configure syslinux.
If you get this message, check if the partition that contains /boot
has the boot flag enabled. If the flag is enabled, then perhaps this partition starts at sector 1 rather than sector 63 or 2048. Check this with fdisk -l. If it starts at sector 1, you can move the partition(s) with gparted from a rescue disk. Or, if you have a separate boot partition, you can back up /boot with
cp -a /boot /boot.bak
and then boot up with the arch install disk. Next, use cfdisk to delete the /boot partition, and recreate it. This time it should begin at the proper sector, 63. Now mount your partitions and chroot into your mounted system, as described in the beginners guide. Restore /boot with the command
cp -a /boot.bak/* /boot
Check if /etc/fstab is correct. Then run
/usr/sbin/syslinux-install_update -iam
and reboot.
Solution: Make sure the partition that contains /boot has the boot flag enabled. Also, make sure the boot flag is not enabled on the windows partition. See the installation section above.
The MBR that comes with syslinux looks for the first active partition that has the boot flag set. The windows partition was likely found first and had the boot flag set. If you wanted you could use the MBR that windows or msdos fdisk provides.
You select a menu entry and it does nothing. It "refreshes" the menu
This usually means that you have an error in your configuration. Hit TAB
to edit your boot parameters. Alternatively, press ESC
and type in the LABEL of your boot entry (Example: arch)
ldlinux.sys has the immutable attribute set which prevents the file from being deleted or overwritten. This is because the sector location of the file must not change or else syslinux has to be reinstalled.To remove:
chattr -i /boot/syslinux/ldlinux.sysrm /boot/syslinux/ldlinux.sys