[syslinux] Error loading vesamenu.c32

[Angel]

-----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 en 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-----