@hamza according to the syslinux documentation:
All filenames inside the config file are assumed to be relative to the directory SYSLINUX.CFG is in, unless preceded with a slash or backslash.
If we have a leading slash, it should be an absolute path
As I look at this again, I see you have "root (hd0,4)" in your syslinux config file -- have you used this with syslinux in the past with success? I don't see this method of booting from another partition mentioned in the syslinux documentation, but maybe I'm missing it. This looks like a grub command. The information I've been reading makes it look like you would need to install syslinux to both partitions, then chainload from one partition to the next. In my opinion, it would be easier to put the 2.0 kernel/initrd on sda3 (where you have syslinux installed, presumably) and use a cheatcode to pull the rest of your porteus data from sda5, e.g. :
Code: Select all
MENU LABEL Porteus 2.0
APPEND initrd=/P20/boot/syslinux/initrd.xz login=root from=/dev/sda5 xfce
Run Porteus the best way we can.
Try to autoconfigure graphics
card and use the maximum
so sda3 would have /boot and /porteus for your old installation as well as /P20 which would have the /boot folder from 2.0 inside it. Another option would be to use grub (that's what I do for my hard disk installs).
I hope some portion of this is helpful