You are not logged in.
Pages: 1
I have bin using syslinux for a couple of months and it works rely well except that it do not support ntfs. But after reading some stuff on internet i got the feeling that it should bee supported in 4.05. So i tried first whit
LABEL Windows
MENU LABEL Windows
COM32 chain.c32
APPEND hd1 1
but it yest sad NTLDR is missing so i read the arch wiki and fond this link:
http://www.syslinux.org/wiki/index.php/ … /chain.c32
then i tried
LABEL Windows
MENU LABEL Windows
COM32 chain.c32
APPEND hd1 1 ntldr=ntldr
now it says:
Loading the boot file...
Faild to load the boot file
So is this all wrong and my window partition is of course located on the second disk on the first partition or have i got it all wrong and ntfs is not yet supported?
Last edited by Moosey_Linux (2012-10-04 21:48:15)
Offline
Syslinux is certainly able to load Windows from NTFS, I'm doing it now.
What version of Windows are we talking about? Newer versions have a separate boot partition.
Last edited by Scimmia (2012-10-04 18:12:40)
Offline
Please rename the title, because it's very misleading. The current title is actually referring to Syslinux being INSTALLED on an NTFS partition, not chainloading to a Windows install.
And please use [ code ] tags when posting code. It's easier to read this way, and also: https://wiki.archlinux.org/index.php/Fo … s_and_Code
https://wiki.archlinux.org/index.php/Sy … ainloading
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.
Windows 7 (and 8) by default create a 100 MB "System Reserved" partition (unless you selected an already created partition when installing Windows), and you need to chainload to that one. Finally, check that you actually have a "/boot/syslinux/chain.c32" file, and don't forget to mark this topic as solved (by editing the first post), so that other people (including yourself sometimes) may find useful.
I have made a personal commitment not to reply in topics that start with a lowercase letter. Proper grammar and punctuation is a sign of respect, and if you do not show any, you will NOT receive any help (at least not from me).
Offline
Sorry for the misguiding title for my defense i´m not from an English speaking country ;-)
I´m running Windows XP for the moment old computer needs old OS. Can it bee that its located on the second disk right now i´m chain loading grub legacy and then i chain load Windows whit it. In my grub/menu.lst I use mapping is there something similar in syslinux?
grub/menu.lst
# (2) Windows
title Windows strip to the bone
map (hd0) (hd1)
map (hd1) (hd0)
rootnoverify (hd1,0)
makeactive
chainloader +1
Offline
Finally, check that you actually have a "/boot/syslinux/chain.c32"
I have copied it to /boot/syslinux but not symlinkt it.
Offline
Does your entire second drive contain the Windows installation (including Windows bootloader written to the MBR)?
If so, you could trying chainloading the second drive and let Windows' bootloader take over:
LABEL Windows
MENU LABEL Windows
COM32 chain.c32
APPEND hd1
Offline
No the first partition contains Windows the second partition is an old arch /boot partition whit grub legacy. Could that bee a problem chain loading Windows from a disk whit grub on it? Any way i tried to boot howl disk yest in case but nothing new.
LABEL Windows
MENU LABEL Windows
COM32 chain.c32
APPEND hd1
NTLDR is missing
LABEL Windows
MENU LABEL Windows
COM32 chain.c32
APPEND hd1 ntldr=ntldr
Loading the boot file...
Faild to load the boot file
Offline
I'm confused. Which bootloader do you have installed? GRUB Legacy or Syslinux? Because there can only be one bootloader installed to the MBR. What does it say when you boot up? Does it say "GRUB Legacy 0.97" ? Then it means that you're not using Syslinux, and you are editing "/boot/syslinux/syslinux.cfg" for nothing. Reinstall Syslinux with (not "whit") the instructions from the Beginners' Guide: https://wiki.archlinux.org/index.php/Be … e#Syslinux
Remember, with Syslinux, drives are counted from zero, partitions from one. This is relevant to the BIOS settings, not the kernel names (/dev/sda, /dev/sdb, etc). In my case, I have Windows XP installed on the second drive and on the SECOND partition (meaning /dev/sdb2), and here's the entry from my /boot/syslinux/syslinux.cfg:
LABEL xp
MENU LABEL Windows XP
KERNEL chain.c32
APPEND hd0 2
"hd0 2" because it's the second partition. For you, it would be "hd0 1", from what I understand. If you still can't nail it, press Tab when the menu shows up and try "hd1 1" or something like that (maybe even "hd1", which translates as "use whatever bootloader is installed on the second drive's MBR").
I have made a personal commitment not to reply in topics that start with a lowercase letter. Proper grammar and punctuation is a sign of respect, and if you do not show any, you will NOT receive any help (at least not from me).
Offline
I'm confused. Which bootloader do you have installed? GRUB Legacy or Syslinux?
Yes i know it sounds rely strange but it is not. This computer have been white me for many years and so has Linux and now Arch Linux but one year ago bought a new hard disk. I wanted to try Lucks and dm-crypt for a while and decided to crypt and make a fresh install on my new disk. Everything went well Grub legacy loaded both my old Arch Linux and my XP from my old first disk that now had become my second disk. Then i read about syslinux on Planet Arch i decided to try it. It works really well and is much simpler and less annoying than Grub2 but i couldn’t get it to load windows. I read some more on Planet Arch and found a comment saying that it didn’t yet support ntfs. So i decided to do some kind of workaround and chain loaded white syslinux on my first disk Grub legacy on the second disk then whit it a chain loaded XP.
Maybe the problem is that i have syslinux installed on my first disk and Grub legacy on my second disk. But if that’s the case haw cold tow of Gurb legacy work?
And i try d
LABEL Windows
MENU LABEL Windows
KERNEL chain.c32
APPEND hd1 1
NTLDR is missing
Offline
But if that’s the case haw cold tow of Gurb legacy work?
WTF?
Offline
Moosey_Linux wrote:But if that’s the case haw cold tow of Gurb legacy work?
WTF?
Not everyone has English as their primary language. What Moosey_Linux means is quite clear from the context. So don't try to be a grammar Nazi !
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
And i try d
LABEL Windows MENU LABEL Windows KERNEL chain.c32 APPEND hd1 1
NTLDR is missing
Sounds silly as a fix - but do please humour me...
Change the first item to lowercase:
LABEL windows
I spend half a day chasing syslinux "errors" when changing the case of the label was all that was required. Can't find reference to this fact in the wiki but I found the snippet online somewhere...
************** EDIT **********
Your "KERNEL" line should say
COM32 chain.c32
*********** END ********
Last edited by satanselbow (2012-10-05 19:05:03)
Offline
satanselbow: It works either way. Either with "KERNEL" or "COM32", and either with "LABEL xp" or "LABEL Xp". I can't find any reference either. Maybe it was fixed in 4.05.
Moosey_Linux: Ok, so /dev/sda has Arch Linux and Syslinux, and Windows is installed on /dev/sdb1. If /dev/sda is set to boot first in the BIOS (which is usually the case), then you need to chainload to "hd1 1" (second drive, first partition).
Post the output of:
# fdisk -l
Last edited by DSpider (2012-10-05 20:07:40)
I have made a personal commitment not to reply in topics that start with a lowercase letter. Proper grammar and punctuation is a sign of respect, and if you do not show any, you will NOT receive any help (at least not from me).
Offline
Maybe it was fixed in 4.05.
Either that or I have started dreaming in Linux... might have been late 3 series (cough... hide...)
Offline
Hi guys thanks for all the replays and sorry for my lack of replays this last days butte 6 of October was my birth day so I was far to drunk to type.
This syslinux issue is starting to turn in to a big mystery it seems like the should work white the current configurations and now body knows way it not. Except posting the fdisk -l i think I post the howl /boot/syslinux/syslinux.cfg to make sure noting is wrong whit it.
# Config file for Syslinux -
# /boot/syslinux/syslinux.cfg
#
# Comboot modules:
# * menu.c32 - provides a text menu
# * vesamenu.c32 - provides a graphical menu
# * chain.c32 - chainload MBRs, partition boot sectors, Windows bootloaders
# * hdt.c32 - hardware detection tool
# * reboot.c32 - reboots the system
# * poweroff.com - shutdown the system
#
# To Use: Copy the respective files from /usr/lib/syslinux to /boot/syslinux.
# If /usr and /boot are on the same file system, symlink the files instead
# of copying them.
#
# If you do not use a menu, a 'boot:' prompt will be shown and the system
# will boot automatically after 5 seconds.
#
# Please review the wiki: https://wiki.archlinux.org/index.php/Syslinux
# The wiki provides further configuration examples
#DEFAULT arch
#PROMPT 0 # Set to 1 if you always want to display the boot: prompt
#TIMEOUT 50
# You can create syslinux keymaps with the keytab-lilo tool
#KBDMAP de.ktl
# Menu Configuration
# Either menu.c32 or vesamenu32.c32 must be copied to /boot/syslinux
#UI menu.c32
#UI vesamenu.c32
# Refer to https://wiki.archlinux.org/index.php/Syslinux
UI vesamenu.c32
DEFAULT arch
PROMPT 0
MENU TITLE Boot Menu
MENU BACKGROUND resistance-1280x1024.png
TIMEOUT 1200
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
# Refer to http://www.syslinux.org/wiki/index.php/Comboot/menu.c32
# Refer to http://syslinux.zytor.com/wiki/index.php/Doc/menu
MENU TITLE Arch Linux
#MENU BACKGROUND splash.png
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
MENU RESOLUTION 1280 1024
# boot sections follow
#
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
#
#-*
LABEL arch
MENU LABEL Arch Linux
LINUX ../vmlinuz-linux
APPEND root=/dev/disk/by-uuid/cdb6e767-33d1-4b24-a631-5967027a37a9 cryptdevice=/dev/disk/by-uuid/9acb107e-2639-4b40-bf42-ed494979009f:root ro vga=773
INITRD ../initramfs-linux.img
LABEL archfallback
MENU LABEL Arch Linux Fallback
LINUX ../vmlinuz-linux
APPEND root=/dev/disk/by-uuid/cdb6e767-33d1-4b24-a631-5967027a37a9 cryptdevice=/dev/disk/by-uuid/9acb107e-2639-4b40-bf42-ed494979009f:root
INITRD ../initramfs-linux-fallback.img
LABEL GRUB Leagacy
MENU LABEL GRUB Leagacy
COM32 chain.c32
#map (hd0) (hd1)
#map (hd1) (hd0
APPEND hd1 2
LABEL Windows
MENU LABEL Windows
KERNEL chain.c32
APPEND hd1 1
LABEL hdt
MENU LABEL HDT (Hardware Detection Tool)
COM32 hdt.c32
LABEL memtest
MENU LABEL Memtest86+
LINUX ../memtest86+/memtest.bin
LABEL reboot
MENU LABEL Reboot
COM32 reboot.c32
LABEL off
MENU LABEL Power Off
COMBOOT poweroff.com
and in my /boot/syslinux/ directory following files and directory’s are located
[storken@Cikoniedoj ~]$ sudo /boot/syslinux/
Earth-Wallpaper-1280-1024.png pci.ids
SYSLINUX_AUTOUPDATE poweroff.com
chain.c32 reboot.c32
hdt.c32 resistance-1280x1024.png
ldlinux.sys syslinux.cfg
menu.c32 vesamenu.c32
and then the fdisk -l
Disk /dev/sda: 500.1 GB, 500107862016 bytes, 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xf8ab3f65
Device Boot Start End Blocks Id System
/dev/sda1 63 40965749 20482843+ 7 HPFS/NTFS/exFAT
/dev/sda2 40965750 80035829 19535040 83 Linux
/dev/sda3 * 80035830 80276804 120487+ 83 Linux
/dev/sda4 80276805 976773167 448248181+ 5 Extended
/dev/sda5 80276868 138865859 29294496 83 Linux
/dev/sda6 138865923 144729584 2931831 83 Linux
/dev/sda7 144729648 976773167 416021760 83 Linux
Disk /dev/sdb: 160.0 GB, 160041885696 bytes, 312581808 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x53d653d6
Device Boot Start End Blocks Id System
/dev/sdb1 * 63 40965749 20482843+ 7 HPFS/NTFS/exFAT
/dev/sdb2 40965750 41945714 489982+ 83 Linux
/dev/sdb3 41945715 98590904 28322595 f W95 Ext’d (LBA)
/dev/sdb4 98590905 312576704 106992900 7 HPFS/NTFS/exFAT
/dev/sdb5 41945778 45849509 1951866 83 Linux
/dev/sdb6 45849573 75152069 14651248+ 83 Linux
/dev/sdb7 75152133 84919589 4883728+ 83 Linux
/dev/sdb8 84919653 98590904 6835626 83 Linux
Disk /dev/sdc: 251.0 GB, 251000193024 bytes, 490234752 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000f3104
Device Boot Start End Blocks Id System
/dev/sdc1 63 490234751 245117344+ 83 Linux
Disk /dev/mapper/root: 30.0 GB, 29995466752 bytes, 58584896 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/XL: 426.0 GB, 426004185088 bytes, 832039424 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/BIG: 251.0 GB, 250998063616 bytes, 490230593 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/SWAP: 3000 MB, 3000097792 bytes, 5859566 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/VolBIG-lvolBlack: 21.5 GB, 21474836480 bytes, 41943040 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/VolBIG-lvolWhite: 229.5 GB, 229520703488 bytes, 448282624 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
As you can see i have three ntfs partitions /dev/sda1, /dev/sdb1 and /dev/sdb4. When i installed arch again i also installed windows again butte something happen d to it so it stopt working after only 4 boots so i stayed white my old install on /dev/sdb1 and /dev/sdb4 is an ntfs storing partition for my windows.
Thanks again for all your effort to help it wood bee really nice to find the root to this mystical problem.
Offline
Sounds silly as a fix - but do please humour me...
It works weary well butte its super retarded and that’s way i wane fix it
Offline
Pages: 1