-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 18/01/15 a las 13:18, Gene Cumm escribi?:> On Sun, Jan 18, 2015 at 6:44 AM, Angel <angelv64 at gmail.com> wrote: >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 >> >> Hello. >> >> I'm trying to setup an multiboot USB, mainly to install Debian >> using netinst images. >> >> I've mounted one of iso image and copied to a directory in USB >> (made with syslinux 6.03) and copied too the kernel and initrd >> for hd install. >> >> I've setup a directory to start the USB and, well it starts, but >> when I jump (using CONFIG) to the isolinux.cfg from Debian >> directory I get all the times a message "Failed to load COM32 >> file vesamenu.c32" >> >> I think th iso image for netinst is made using syslinux 4.02, but >> I don't know if is the cause of the problem. I've tried some >> things like rename isolinux.cfg to syslinux.cfg, but with no >> success. > > That alone can be an issue. You should only use COM32 modules > from the same build. Crossing from 6.xx to 4.xx will definitely > not work. > > http://www.syslinux.org/wiki/index.php/Common_Problems#ModulesShouldn't be enough copy modules from /user/lib/syslinux....?> >> I'm sure the Debian isolinux.cfg is reached because I've added a >> line "SAY something" and the message is displayed, the problem is >> in the line "default vesamenu.c32" >> >> Best regards and thanks in advanced >-----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJUu9GwAAoJEPploz+wCpxHcJYP/RuT+Sgx1QDdxptuejxCzJYl 1xfTyk5wHeQvha48GuyIg1FRmnV2CZmQi1cUM887++HqRrsRPUTTjanmVTSjPfog LXwbeGK1FbgiVEEAvv5OBIve0SlN1JBFzcCG46SnAEEEesTvUVbJlSvU1QYJxEDH KEM6Nydc27oxPb2fmpR1DtEmSJxnRs1q3e8a5/iGGAunqpF2oMYWVLHsvfATwgAq 1cUXkznlBtbd+JsydNfp7DrICRnVyFehQwJj92yFCxSqdpg5pSXDMgtCgZph1F+d YdXf4DTl68O22CRieO1gzoyn9o4rbeDe4P81+0w/SRMLUcsIm7ze0M4xgsebO93J JgMLUVJzwBbB3Sqw2G55hfEr5jVNjOmlyQFZiUrd98ZeEjl5ZsNbHALBz1/TPqTZ RLJWV7HUjNCYnhma60bYkPNG9Z87Iwrcyj3Y7nOJXuqAfUT44eo/Oy24cD6jUrVp bvO/y3OSluN9YeAIPUZpeOcDlHMxtBHuRgQfm5dQfSV/zQQPGSlQ5KbhefJYHxJj w2nGZoE5XyWiiFNJ2lNzkKPPhBUpeYbyqquOJA7BfVDYMQSQUPOgSqYKGtJGelfn 7IWptm3/bwjxEHL4shufbdnJ55azf8LbtQ8gu9EEp95dK3i2UlV1Zfy0x+0DghE3 NwCtXaSezBxyOnyUjUuL =eVo+ -----END PGP SIGNATURE-----
> > http://www.syslinux.org/wiki/index.php/Common_Problems#Modules > > Shouldn't be enough copy modules from /user/lib/syslinux....? >1_ Booting with Syslinux, in the Syslinux "boot:" prompt press "Ctrl+V" so to see relevant information. The c32 modules shall match the same version. 2_ The Current Working Directory is relevant, specially for relative paths. The CONFIG directive is capable of changing the CWD. The pwd.c32 module can display the CWD in the Syslinux CLI. 3_ Not every error regarding Syslinux-related files means that there is an error or a bug in Syslinux itself. Syslinux-related packages, their versions, and auxiliary tools, are frequently a source of inconveniences. User "error" is probably more frequent than we might think. Of course Syslinux itself has its own issues/bugs. 4_ Since version 5.0, Syslinux needs a core module and c32 Library modules: http://www.syslinux.org/wiki/index.php/Library_modules 5_ The c32 Library modules shall also match the same version of the bootloader. 6_ After resolving any Syslinux-related matters, each Linux distro might have its own kernel parameters related to expected file locations (kernel, initrd, sqfs...). This is usually an issue in "multiboot" scenarios. 7_ Some (ISO) images might not include the necessary conditions to boot from specific media. For instance (and I am _not_ referring to any specific distro/case): _ a "mini" ISO image might not include "all/every/automatic/any/some" network capabilities; or, _ some minimal network installation method might be only suitable for network installation and not for "optical/USB/other" media; or, _ some "Live" ISO image might not be the "recommended" method to install the OS (even if there seems to be such option available). 8_ Some distros do not support mixing some versions of certain packages, or updating/installing in certain ways. Regards, Ady.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 18/01/15 a las 17:44, Ady escribi?:> >>> http://www.syslinux.org/wiki/index.php/Common_Problems#Modules >> >> Shouldn't be enough copy modules from /user/lib/syslinux....? >> > > 1_ Booting with Syslinux, in the Syslinux "boot:" prompt press > "Ctrl+V" so to see relevant information. The c32 modules shall > match the same version.Version 6.03, I've copied vesa*.c32 version 6.03 to isolinux directory, pwd.c32 too> > 2_ The Current Working Directory is relevant, specially for > relative paths. The CONFIG directive is capable of changing the > CWD. The pwd.c32 module can display the CWD in the Syslinux CLI.Here you put me in the correct path: after launch Debian I couldn't execute pwd.c32 because it was not found, so I tried writting the path before the name: /Debian<bla.>/isolinux/pwd.c32, in this case the module was found, so I've adjusted the path in the line with CONFIG call and now runs O.K. I had to adjust some other thing no syslinux related. Thank you very much for open mine eyes.> > 3_ Not every error regarding Syslinux-related files means that > there is an error or a bug in Syslinux itself. Syslinux-related > packages, their versions, and auxiliary tools, are frequently a > source of inconveniences. User "error" is probably more frequent > than we might think. Of course Syslinux itself has its own > issues/bugs. > > 4_ Since version 5.0, Syslinux needs a core module and c32 Library > modules: http://www.syslinux.org/wiki/index.php/Library_modules > > 5_ The c32 Library modules shall also match the same version of the > bootloader. > > 6_ After resolving any Syslinux-related matters, each Linux distro > might have its own kernel parameters related to expected file > locations (kernel, initrd, sqfs...). This is usually an issue in > "multiboot" scenarios. > > 7_ Some (ISO) images might not include the necessary conditions to > boot from specific media. For instance (and I am _not_ referring to > any specific distro/case): > > _ a "mini" ISO image might not include > "all/every/automatic/any/some" network capabilities; or, _ some > minimal network installation method might be only suitable for > network installation and not for "optical/USB/other" media; or, _ > some "Live" ISO image might not be the "recommended" method to > install the OS (even if there seems to be such option available).I had to download a initrd to mount file systems other than iso9660>Now I have a major problem with the old laptop: after update BIOS, is not possible to boot from any USB port, but this is other story.> > Regards,Regards and thanks again> Ady. _______________________________________________ Syslinux > mailing list Submissions to Syslinux at zytor.com Unsubscribe or set > options at: http://www.zytor.com/mailman/listinfo/syslinux >-----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJUvrahAAoJEPploz+wCpxH97MP/3B+Cew7GU9m/cWvhMZs7NJ2 C7UIqe8p7ko4+oxWXePEj4SE5HacYPJfjighHnQI+AMzJy8FF3Sf6bXN8QhHk45r zuhn8q7kiHcSEj4KYeesuZ+lOjuMk21Xyw5BYGUZEWx0meoHbjy5A3NxEYr/w20X 2VQ2iGfl3qpsNHhC7AC+zPGnb+sTFjx+o6s5PY8oFrmSpW/fAHA8O+F9Pybabkcb OWS6D06WXnpoIabOSvrKPXPRQVLcnfrZAwewizKNyXJRtQfxGkZjMEfiRt7K63Zv qFIr8gSxb3jBe7bdcbccN43y7gb+UnvQIBUpJVcEBHL0w1J+VePEwdXVxNY+MGJb vj8BaAgvcnXea7KilILojHC99ZTFaX8pbmCe5Cpw4YUxAOiSCtEWaNzyOL5oGP0t bx0IJqluDDtc19c61659A+/hGpQPC7JCeVrPVnnbCEfiGGQm35t3/BUqcK1pNT2K ruD7wH8NmdmJsija/OtO1Fz9iLOA4/ztwoNfBWRGAqHZu0nnLHJLGvcYLlUgiamM ZslxjnPtXpyvNzMClOuB1TkDFv/zKUrQkPeIFAem3uofQA7ERLPtb2kvSgL0Uoiu NhRixPNNza06QJ5PvYiOEcBVWQKIfv4VvHBWmKhhasMYXoka8d4BOzX9wNjfaDsp FqJY5LnQtFbMizf13/1S =VDa6 -----END PGP SIGNATURE-----