SliTaz Forum
You are not logged in.
Pages: 1
Hi,
i've installed slitaz on /dev/sda3 without installing the bootloader on it.
the boot partition on this computer is /dev/sda4 with another linux installed and syslinux as bootloader
so I added these lines into syslinux.cfg presents on sda4 :
LABEL slitaz
MENU LABEL SliTaz GNU/Linux [5.0]\(Kernel vmlinuz-3.2.53-slitaz)
LINUX /boot/vmlinuz-3.2.53-slitaz
APPEND root=/dev/sda3 quiet
the problem when I try to boot on this entry I got a message like "fille not found". I don't understand what's go wrong here... of course on sda3 I have /boot/vmlinuz-3.2.53-slitaz
Offline
Brainlessmutant,
Seems like syslinux searches your "/boot/vmlinuz-3.2.53-slitaz" on the boot partition /dev/sda4, not on /dev/sda3.
Imagine, if I could be syslinux I'll do the same.
Offline
yes... but no... or it's a bug... I thought like you but I check on another comp where I have two linux installed (not slitaz). There is the same structure.
Moreover, the lines I added come from the syslinux.cfg that slitaz installed automatically on sda3 /boot/syslinux...
one thing I wonder is there is no initrd, even in syslinux.cfg on sda3...
Offline
@brainlessmutant
I didn't use syslinux for a while but in my memory you should have[c]
kernel /boot/vmlinuz-3.2.53-slitaz[/c]
and not[c]
linux /boot/vmlinuz-3.2.53-slitaz[/c]
and /boot/vmlinuz-3.2.53-slitaz must be on the same partition than syslinux is installed.
Offline
https://wiki.archlinux.org/index.php/Syslinux
Note: Syslinux cannot access files from partitions other than its own. For an alternative bootloader with the multi-fs feature see GRUB.
Offline
@mojo look I used to another linux on sda3 before I installed slitaz, and I boot on sda3 and sda4 without trouble in the pas. Moreover on another computer I have sda1 sd2 with syslinux too and I boot them without trouble too
@ceel i'll check this. ====> don't work
Offline
@brainlessmutant
If you want to boot SliTaz from another partition with syslinux here is a solution (not really elegant... but used with extlinux and it works)
Syslinux is installed on your sda3; copy chain.c32 (from the same version that the syslinux installed) in your /boot/syslinux directory.
Add in your syslinux.cfg this entry:[c]
LABEL SDA4
MENU LABEL SliTaz on /dev/sda4
kernel chain.c32
append hd0 4[/c]
Then install syslinux on sda4; sda4 mustn't be boot.
Create a syslinux.cfg in /boot/syslinux on sda4 with[c]
LABEL slitaz
MENU LABEL SliTaz 5.0 (kernel vmlinuz-3.2.53-slitaz)
LINUX /boot/vmlinuz-3.2.53-slitaz
APPEND root=/dev/sda4 quiet[/c]
My mistake; the LINUX instruction works too
Offline
ok, so I copied vmlinuz-3.2.53-slitaz in (sda4) /boot, then I was able to boot (right now I'm writing from tazweb). I start to understand why I never noticed this in the past.
first all my OS installed in all computers are archlinux since archlinux name his kernel vmlinuz-linux, it was transparent. At that point one thing suprise me, I have on a computer a ssh server (only used for maintenance) that I never updated... and when I boot it I don't see any warning or error... so for me the fact that syslinux can't boot on another partition was transparent.
second, I boot iso trough syslinux, for example in all computer I have a slitaz.iso and boot it if needed (for emergency...), iso are always installed on the same partition than syslinux...
first and second point never drove me to the problem that I've faced today..
anyway thank you
Offline
@Ceel : I shall test your solution in the future, I plan to install slitaz on a second computer too.
Offline
Pages: 1
[ Generated in 0.018 seconds, 7 queries executed - Memory usage: 1.55 MiB (Peak: 1.77 MiB) ]