Displaying 20 results from an estimated 500 matches similar to: "5.10 regression (from 5.01) MENU INCLUDE broken."
2013 Sep 05
3
5.10 regression (from 5.01) MENU INCLUDE broken.
On 09/05/2013 01:55 AM, Gene Cumm wrote:
> On Wed, Sep 4, 2013 at 2:34 PM, Piotr Karbowski
> <piotr.karbowski at gmail.com> wrote:
>
>> With syslinux (extlinux) it will jump to last INCLUDE'ed menu always, with
>> 5.01 it will display list of elements, then allow me to choose which one I
>> want to enter.
>>
>> Even if the include part contain a
2011 Aug 17
3
Live linux booting
I have a need to have a live Linux (Debian or sysrescued ) to boot off a hard-drive so that the
hard-drive ends up umounted after boot. (for running partimage ).
I've gone down the memdisk iso route and read about the issues there - I've seen a way to do this by
mounting over nfs (messy) - but I want to do this without the network.
I'm thinking that there should be a way to loop
2013 Jul 18
4
FW: pxelinux 5.x, 6.x memtest problem
Hi,
OK. I build syslinux-6.02-pre6 from
https://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/6.02/syslinux-6.02-pre6.tar.gz
on a Debian jessie/sid system (with gnu-efi_3.0u+debian-2 from
experimental):
root at jessie: ~# cd /tmp
root at jessie:/tmp# wget
https://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/6.02/syslinux-6.02-pre6.tar.gz
root at jessie:/tmp# tar xfz
2013 Jul 18
2
FW: pxelinux 5.x, 6.x memtest problem
Hi,
if you can provide a prepared src tarball like you do for releases, I can test.
But I still cannot build from git source (as you may remember).
--
Regards,
Igor
2013 Sep 06
1
5.10 regression (from 5.01) MENU INCLUDE broken.
>
> > On 09/05/2013 01:55 AM, Gene Cumm wrote:
> > > On Wed, Sep 4, 2013 at 2:34 PM, Piotr Karbowski
> > > <piotr.karbowski at gmail.com> wrote:
> > >
> > >> With syslinux (extlinux) it will jump to last INCLUDE'ed menu always, with
> > >> 5.01 it will display list of elements, then allow me to choose which one I
> >
2011 Jun 14
3
Questions about setup
I have worked in IT for several years and programming or anything related to
this is not exactly one of my strengths. I need help creating a vesamenu..
Im trying to setup up so I can access my Acronis backup and disaster
recovery 10 server, knoppix live cd, hardware diagnostics - pcdoctor and
maybe a hiren type boot cd. I checked the Linux irc channel which I guess is
now abandoned. If anyone
2012 Sep 04
1
ifcpu64.c32 not working properly when used in a menu include file
The following is a pxelinux problem, specifically to do with
including config files with the menu include directive and the
ifcpu64.c32 com module.
I have a working ifcpu64.c32 setup that jumps to the label rescue64
in the case of a 64-bit CPU. The label "rescue64" defines a 64-bit
kernel and a 64-bit initrd.img. The setup jumps to a label named
"rescue32" in the case of a
2013 Apr 29
3
ifcpu[64].c32 functions drop to command line
I'm having issues with the ifcpu[64].c32 modules. I am building a menu system (as opposed to the command line only options I was previously using) to make it easier for my boss to use PXE. I discovered the modules for auto detecting the CPU and thought hey, that's great! However, I'm having an issue where when I select to boot say System Rescue CD, it drops me to the command line
2013 Jul 18
0
FW: pxelinux 5.x, 6.x memtest problem
> Hi,
>
> OK. I build syslinux-6.02-pre6 from
> https://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/6.02/syslinux-6.02-pre6.tar.gz
> on a Debian jessie/sid system (with gnu-efi_3.0u+debian-2 from
> experimental):
>
> root at jessie: ~# cd /tmp
> root at jessie:/tmp# wget
>
2013 Jun 12
2
KBDMAP - extlinux 5.xx
On Thu, 06 Jun, at 01:11:53AM, poma wrote:
>
> Standalone directive 'kbdmap <kbd>.ktl' doesn't work within series 5.
> Tested via 5.00, 5.01 and 5.10.
> It works within series 4 - tested via 4.05 and 4.06.
> Is it a bug, or is it a feature?
Could you provide me with your .ktl file?
--
Matt Fleming, Intel Open Source Technology Center
2013 Jun 13
2
KBDMAP - extlinux 5.xx
On Thu, 13 Jun, at 12:40:48PM, poma wrote:
> Regarding [1], [2], and [3], I somehow doubt that this is a '*.ktl' i.e.
> "Keyboard Table for Lilo" problem.
> Which ones of these[4] produced by the 'keytab-lilo' you need?
> All of them[4] were tested. ;)
Any one will do. I just want to reproduce this bug.
--
Matt Fleming, Intel Open Source Technology Center
2012 Mar 29
1
Defect ISO generation after yum upgrade
[cid:9FBAC256-5A30-4061-B74E-53A6B7B3D7BA at c-team.local]
Hi all,
Our own appliance is a Linux Kernel and 2 initrd files for filesystem - one system and one config partition. After the yum upgrade on our build machine ISO files are generated but useless. I you are able to see the picture I would like to know "who" writes the -
Loading /system.igz? failed!
Is it the kernel already
2015 Dec 29
2
keytab-lilo: update to support kbd 2.0.3 format
> On 27.12.2015 23:57, Jernej Simon?i? via Syslinux wrote:
> > On Sunday, December 27, 2015, 23:34:11, Ady via Syslinux wrote:
> >
> >> How this change would affect users with older versions of kbd /
> >> loadkeys / or in older OSes? I mean, let's assume a user using a newer
> >> version of Syslinux (containing this proposed change in its keytab-lilo
2016 Mar 07
2
keytab-lilo: update to support kbd 2.0.3 format
On 29.12.2015 22:51, poma wrote:
> On 29.12.2015 22:20, Ady via Syslinux wrote:
>>
>>> On 27.12.2015 23:57, Jernej Simon?i? via Syslinux wrote:
>>>> On Sunday, December 27, 2015, 23:34:11, Ady via Syslinux wrote:
>>>>
>>>>> How this change would affect users with older versions of kbd /
>>>>> loadkeys / or in older OSes? I
2006 Mar 23
1
Syslinux keyboard mappings
Hi,
I finally want to end the fights we have had in the past with keyboard
mappings. I already curse the person who is responsible for this keyboard
mess (and even more the persons who could have create a 'detect keyboard'
kind of functionality in modern PCs :))
But the general problem is this, BIOSes are US qwerty, Belgium uses
be-latin1 (azerty with lots of custom keys). And to
2011 Jan 04
1
isolinux, extlinux and accented characters
Hello,
First of all, thanks very much for this piece of software, it's working
like a charm.
I'm using it to boot a Linux distro I'm working on.
What I want to deal with is the display of accented characters in ISOLINUX.
First, I set EXTLINUX up to boot an ext2-formatted USB stick. No problem
so far.
I wrote a config file ordering to load a font (lat-9w) to display french
2015 Dec 27
2
keytab-lilo: update to support kbd 2.0.3 format
On Sunday, December 27, 2015, 23:34:11, Ady via Syslinux wrote:
> How this change would affect users with older versions of kbd /
> loadkeys / or in older OSes? I mean, let's assume a user using a newer
> version of Syslinux (containing this proposed change in its keytab-lilo
> perl script) but with an older OS / older version of kbd / loadkeys /
> map files.
The changed
2008 Apr 30
1
help text key F10 in pxelinux > 3.61
Hi,
i have a strange problem since pxelinux 3.62 with the F10 help key.
I configured this:
DISPLAY pxelinux.cfg/schlunix_new.txt
F1 pxelinux.cfg/helps/schlunix
F2 pxelinux.cfg/helps/schlunix64
F3 pxelinux.cfg/helps/rescue
F4 pxelinux.cfg/helps/rescue64
F5 pxelinux.cfg/helps/stress
F6 pxelinux.cfg/helps/stress64
F7 pxelinux.cfg/helps/dosimages
F8 pxelinux.cfg/helps/mailsystem
F9
2009 Jul 19
2
Patch for chain.c32: Set default boot drive to CD drive from which ISOLINUX is booted
chain.c32 of SYSLINUX 3.82 does set the boot drive passed to the DL register to 0x80 and not to the boot drive (CD-drive).
This can be a problem if you want to chainload grldr (grub4dos bootloader) from a CD and if you want to let grldr search for its menu.lst file on the CD.
For more info:
http://www.boot-land.net/forums/index.php?showtopic=8457
This 1 line patch fixes the issue (Thanks to
2017 Aug 05
1
menu.c32 background problem
On 8/5/17, Ady Ady via Syslinux <syslinux at zytor.com> wrote:
> Since you are using only 2 menu entries, would you consider the
> possibility of using the msg file(s) and the boot prompt, while
> avoiding the use of (vesa)menu.c32 for this particular project? If you
> do, there is room for improvements.
>
>
Thanks for the info.
Yes, I previously did not have a menu, for