similar to: SysLinux Development Questions

Displaying 20 results from an estimated 4000 matches similar to: "SysLinux Development Questions"

2013 Oct 17
1
[PATCH] chain: Fix chainloading on 6.02
From: Raphael S. Carvalho <raphael.scarv at gmail.com> My commit 09f4ac33 broke 'com32/lib/syslinux/disk.c' __lowmem doesn't work for declarations outside the core. Using __lowmem outside the core wouldn't have the desired effect, then lmalloc must be used instead to store dapa into the correct section (".lowmem"). Reported-by: Dark Raven <drdarkraven at
2013 Sep 06
1
[PATCH 2/2 v2] com32/disk: Improve flow at disk_write_sectors and disk_read_sectors.
This patch will improve the flow at disk_write_sectors and disk_read_sectors. It does that by creating a table of values respective to the operation. Besides, read and write operations are pretty similar to each other, so I redesigned the routines to avoid duplication. Signed-off-by: Raphael S.Carvalho <raphael.scarv at gmail.com> --- com32/include/syslinux/disk.h | 18 ++++
2013 Sep 17
2
[PATCH 1/4 v2] com32/lib/: Avoid unneeded allocation.
eparam would only be used if EBIOS is available. If it is not, then there is no reason to allocate eparam. Signed-off-by: Raphael S.Carvalho <raphael.scarv at gmail.com> --- com32/lib/syslinux/disk.c | 10 +++++----- 1 files changed, 5 insertions(+), 5 deletions(-) diff --git a/com32/lib/syslinux/disk.c b/com32/lib/syslinux/disk.c index 093751a..d96acbf 100644 ---
2013 Sep 06
1
[PATCH 2/2] com32/disk: Improve flow at disk_write_sectors and disk_read_sectors.
This patch will improve the flow at disk_write_sectors and disk_read_sectors significantly, but it *will* introduce bugs if either of the above functions gets called before disk_get_params. --- com32/include/syslinux/disk.h | 21 +++++ com32/lib/syslinux/disk.c | 170 +++++++++++++++++++++-------------------- 2 files changed, 108 insertions(+), 83 deletions(-) diff --git
2013 Sep 06
2
[PATCH 1/2] com32/lib/: Avoid unneeded allocation.
eparam will only be used if EBIOS is available on the underlying disk. If not so, then there is no reason to allocate eparam. --- com32/lib/syslinux/disk.c | 13 +++++++------ 1 files changed, 7 insertions(+), 6 deletions(-) diff --git a/com32/lib/syslinux/disk.c b/com32/lib/syslinux/disk.c index 093751a..554bed3 100644 --- a/com32/lib/syslinux/disk.c +++ b/com32/lib/syslinux/disk.c @@ -73,7
2011 Jan 03
1
[PATCH] COM32R documentation: fix typo 'pm_cs'
Signed-off-by: Paul Bolle <pebolle at tiscali.nl> --- doc/comboot.txt | 12 ++++++------ 1 files changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/comboot.txt b/doc/comboot.txt index 4b4b880..04d5deb 100644 --- a/doc/comboot.txt +++ b/doc/comboot.txt @@ -986,27 +986,27 @@ AX=0024h [3.80] Cleanup, shuffle and boot, raw version ++++ 32-BIT ONLY API CALLS ++++ -void
2011 Feb 16
1
[PATCH] [RESEND] COM32R documentation: fix typo 'pm_cs'
Signed-off-by: Paul Bolle <pebolle at tiscali.nl> --- doc/comboot.txt | 12 ++++++------ 1 files changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/comboot.txt b/doc/comboot.txt index 4b4b880..04d5deb 100644 --- a/doc/comboot.txt +++ b/doc/comboot.txt @@ -986,27 +986,27 @@ AX=0024h [3.80] Cleanup, shuffle and boot, raw version ++++ 32-BIT ONLY API CALLS ++++ -void
2012 Apr 17
2
[GIT PULL] elflink warning fixes and auto extension support
Hi, I just pushed out changes that fix pretty much all the compiler build warnings on the elflink branch. Also, I've added "auto extension" support so that if the user doesn't type the file name extension it will automatically be looked up, e.g. now typing "ls" will execute "ls.c32". The following changes since commit
2008 Aug 06
1
pid$target::malloc:entry does not work
In Solaris 10 6/06, etc. I used to do things like pid$target::malloc:entry { ustack(); } and got stack traces from my application calling malloc as expected. In Solaris 10 8/07 I only see stack traces from functions inside libc calling a function called lmalloc() but not my malloc calls: ld.so.1`lmalloc ld.so.1`tsort+0xb4
2007 Jul 10
1
not valid FAT fs
hi I'm new to this, and already havin some trouble :( I tried to make my usb pen drive bootable with sysliux, but I got this message: syslinux: this doesn't look like a valid FAT filesystem But I already formatted the usb pen drive int FAT16 fs with cfdisk AND with qtparted (in both cases I got the same message). Anyone that could help me about this?
2008 Jul 10
1
Syslinux
Hello Marc I am having the same issue mentioned below. I ran the mkdosfs, and received the following: /dev/sdb contains a mounted filesystem Can you help? On Tuesday 10 July 2007 11:16, Visar Zejnullahu wrote: >* hi I'm new to this, and already havin some trouble :( *>* *>* I tried to make my usb pen drive bootable with sysliux, but I got this *message: >* *>* syslinux: this
2013 Jan 07
2
chain.c32 bug
i`ve found a bug in chain.c32 in v4.06. When i use isolinux it does not run windows7 installation, chainloading bootmgr. the error is: Can't find myself on the drive I booted from. chain.c32 from syslinux 3.xx works like a charm! chain.c32 from syslinux 5 shous tat this is not a com32 app
2014 Jun 16
2
Chainload pxelinux from pxelinux and pass parameters or change root dir?
When chainloading one pxelinux from another (e.g., chainloading from say pxelinux 4.07 to pxelinux 6.02), can one pass parameters or somehow control the root directory and/or server IP address? Here's the need: we have a loaded-up PXE server working great under 4.07, and I'm not prepared to just switch the entire setup to a newer version of pxelinux, too many folks depending on a
2016 Mar 25
2
Fw: new message
Hey! Open message <http://thekalyanacentre.com/paid.php?a> r0m30 at r0m30.com
2014 Jun 16
5
Chainload pxelinux from pxelinux and pass parameters or change root dir?
On 06/16/2014 10:41 AM, Gene Cumm wrote: > [...] Initially I wrote pxechn.c32 to allow further > modifications of the DHCP data [...] Awesome! In fact, this might allow us to install an automatic 'http' prefix on all subsequent requests, to avoid slow tftp --- or is that a bad idea, and/or is there a way to default all transfers to http without using pxechn and without prefixing
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
2013 Sep 17
1
[PATCH 2/4 v3] com32/disk: Code cleanup at disk_write_sectors and disk_read_sectors.
Pulled common code out of these functions into new ones. The functions chs_setup and ebios_setup were created for this purpose. Signed-off-by: Raphael S.Carvalho <raphael.scarv at gmail.com> --- com32/include/syslinux/disk.h | 7 ++ com32/lib/syslinux/disk.c | 173 +++++++++++++++++++++-------------------- 2 files changed, 97 insertions(+), 83 deletions(-) diff --git
2014 Jun 17
1
Chainload pxelinux from pxelinux and pass parameters or change root dir?
On 06/16/2014 05:14 PM, Gene Cumm wrote: > This sounds like you're using gpxelinux.0 4.07 which as I stated will > introduce issues. Instead of using gpxelinux.0 4.07, try pxelinux.0 > 4.07 then do your chainload to lpxelinux.0 6.02. If this doesn't > solve it, try 6.03-pre14. When I DHCP boot to lpxelinux.0 6.02, and then pxechn.c32 back to lpxelinux.0 6.02 with the http
2014 Nov 24
2
Windows PE booting without chainloading ipxe
Adding an option for initrdfile= boot argument to be ignored by wimboot worked just fine. They can add this patch, which is probably most sane, or syslinux could add the INITRDFILE configuration option instead of having to append the option for linux.c32 wimboot-2.4.0/src/cmdline.c @ Line ~107 } else if ( key == cmdline ) { /* Ignore unknown initial
2014 Jun 02
2
Is it possible to chainload isolinux.bin file from syslinux
I have a USB disk with syslinux files installed in /boot/syslinux, and the bootloader is installed into MBR or VBR I then extracted a *.iso file which uses syslinux as the bootloader, into root dir of the disk. The iso file contains a rescue OS or an OS installer. Now I got the directory /isolinux with files isolinux.bin and isolinux.cfg in this folder I can now boot into syslinux, but *what to