search for: sysdumps

It say to give a copy of dmidecode or sysdump if I need to use localboot -1 pxelinux.0 worked with localboot 0 but gpxelinux.0 didn't it needed localboot -1 This was on my hp machines

So I realized I really need a better way to collect information from problematic machines, so I spent today rewriting the old memdump tool into a new "sysdump" tool. sysdump can write its output either to a serial port using ymodem[1] or over the network using TFTP *if* it was booted from the network, using PXELINUX. John R.: I would obviously like you to try this on the machine that

From: Matt Fleming <matt.fleming at linux.intel.com> This series includes a patch (PATCH 1/6) that I sent previously but I thought it was worth sending it again since the rest of the series depends on it, and it also gives a bit of context. These cleanups make it simpler to do the big switchover to ELF modules on the elflink branch because the libraries in $LIBS are now contained in one

Hello. Use the z size specifier to printf-ing size_t variables to get rid of gcc warning format ?%08x? expects type ?unsigned int?, but argument 2 has type ?long unsigned int? -- MartinS diff --git a/com32/lib/syslinux/initramfs_file.c b/com32/lib/syslinux/initramfs_file.c index 7eb55b5..9f9fa75 100644 --- a/com32/lib/syslinux/initramfs_file.c +++ b/com32/lib/syslinux/initramfs_file.c @@

...h "Not enough memory to load specified image". This results in a few of our boot images (most importantly the Backup Rescue image (and parted magix pxe version)) failing. A12 BIOS works okay. So at the moment we stay at A12. 1) Can this problem be worked around somehow? I have created sysdumps (with sysdump.c32) of both BIOS states but can't read/understand the output. 2) Is it worth the trouble of reporting this to Dell? If yes, do they have a contact for this kind of bugs? I doubt regular Dell support is able to handle these kinds of problem. Best Regards Heiko Helmle

On Sat, Nov 22, 2014 at 10:39 AM, Martin Str|mberg <ams at ludd.ltu.se> wrote: > Hello. > > Use the z size specifier to printf-ing size_t variables to get rid of gcc > warning > format ?%08x? expects type ?unsigned int?, but argument 2 has type ?long unsigned int? Please, add the signed-off line. > > > -- > MartinS > > diff --git

This is an attempt to avoid potential confusion. Here are some example sizes for the two Syslinux versions mentioned in the e-mail subject. Your build results might be different. 4.06: 1 55 Sep 22 22:23 modules/int18.com 1 108 Nov 1 18:07 version.mk 1 138 Nov 1 18:07 version.gen 1 138 Nov 1 18:07 version.h 1 239 Sep 22 22:23 modules/poweroff.com 1 408 Sep 22 22:25

It has been observed that binaries contents are depending on the order of linked objects. This order is caused by GNU make's wildcard function and the position of sources on filesystem. This change tries to prevent this kind of randomness. Also consider building using -j1 flag to make it even more reproductible. Change-Id: Ie8eee7f336e6f1fa2863c4150d967afd15519f1d Bug:

From: Matt Fleming <matt.fleming at linux.intel.com> Move the MCONFIG files into a mk/ directory and give them more descriptive names. This is purely a cosmetic change to make the 'include' directives a bit more coherent by making it obvious exactly which MCONFIG file we're including. For example, in com32/lua/src/Makefile we exchange the line, include ../../MCONFIG for the

Hello, I poked a little bit to extract the list of modules dependencies in Syslinux v6 (see below). I have attached a bash script that generate a nice table from the tarball. The output can either be an ASCII table, or wiki markup, typically for the page Library_modules[1]. I am not in the wiki Editor group, so I can't put that in the wiki. anyway, here's an updated dependency tree for

Hi, First of all thank you so much for your prompt suggestions/help. I really appreciate this. Here is the syslinux.cfg which works perfect with syslinux-4.06 ---- PROMPT 0 TIMEOUT 50 SERIAL 0 DEFAULT mylabel LABEL mylabel KERNEL vmlinuz0 APPEND initrd=initrd.img root=/dev/mmcblk0p2 rootwait rootfstype=ext3 console=tty0 console=ttyS0,9600 ---- To further round off the error possibilities I used

Op 20100701 om 18:15 schreef syslinux-bot for H. Peter Anvin: > Commit-ID: 18de1534f9b69fb298a5b56e61919130d875b34b > Gitweb: http://syslinux.zytor.com/commit/18de1534f9b69fb298a5b56e61919130d875b34b > Author: H. Peter Anvin <hpa at linux.intel.com> > AuthorDate: Thu, 1 Jul 2010 18:12:41 -0700 > Committer: H. Peter Anvin <hpa at linux.intel.com> >

Fixed: cp -r syslinux-6.01/com32/libupload/*.h image/usr/share/syslinux/com32/include/ [snip] rm -rf image/usr/share/syslinux/com32/include [snip] cp: cannot create regular file `image/usr/share/syslinux/com32/include/serial.h': No such file or directory The cp is happened in the "libupload" dir, while "rm -fr" is happend in "lib" dir, let "libupload"

On 11/29/2014 09:20 AM, Ferenc Wagner wrote: > ?? ?? ??? <hetz at benhamo.org> writes: > >> I've converted a CentOS Live ISO to PXE, and I'm using lpxelinux.0 to boot >> it. >> Without any HTTP method in the lines, the files are transferring without >> any problems, but as soon as I use http, all the transferring action is >> super slow - 5-8

I'm seeing some sporadic build failures with 'make -j4'. The failures are: make[4]: *** No rule to make target 'hello.c32', needed by 'all'. Stop. I've only seen the failures with com32/samples/hello.c32 and com32/rosh/rosh.c32. I'm not a make expert, but I think it's due to missing dependencies. This patch seems to fix my failures, but I'm

Hi, Gene Cumm wrote: > > 3) It feels like this is a moving target where gcc keeps changing and > > different results get reported. Do we have indications that different versions of gcc5 cause different behavior on the same build and boot machines ? Ady wrote: > Since the issue is only present on specific > hardware / firmware, whatever might seem to "solve" the

Hi, I am trying to boot syslinux with an SD-Card on COMe-mBTi10 board, it works perfect with syslinux 4-06(as BIOS supports booting from SD-CARD), but hangs with syslinux-6.03 during 'Loading vmlinuz ... '. I tried various ways in which I could debug but no hints, just one time I got the error below the loading screen. 'Loading vmlinuz0 ... CHS: Error 8001 reading sector 34(0/3/3)

On Wed, Dec 17, 2014 at 5:54 AM, Willem Bargeman <willem at bargeman.eu> wrote: > On Wed, Dec 17, 2014 at 2:55 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >> On Tue, Dec 16, 2014 at 4:22 PM, Geert Stappers <stappers at stappers.nl> wrote: >>> On Tue, Dec 16, 2014 at 08:17:32PM +0100, Willem Bargeman wrote: >>>> >> Hi, >>>>

> On Jul 10, 2015 5:29 PM, "poma via Syslinux" <syslinux at zytor.com> wrote: > > > The same as with the ISOLINUX, stable and git. > > Only this time has nothing to do with the menu. > > 1) EXTLINUX is no longer a discrete variant. The installer extlinux now > installs SYSLINUX. > 2) William Kensington already saw a similar behavior wherein an

> > Hi > I have tried to install syslinux 4.06 on the SD card again, it works > like a charm. > > I am being very carefull with c32 files from the same version > bootloader. No success. > > I am also unmounting /dev/sdb1 before installing syslinux, as mentioned > in the given documentations. > In the pasted syslinux.cfg content--- I have also tried using only