search for: boot_imag

Hello! SSIA - when syslinux sees 'BOOT_IMAGE=' on the append line, something seems to go terribly wrong (didn't investigate in detail). You don't even get to see a boot-prompt, even if you try to force it. pxelinux shows the same problem, so I figure it's something generic in the config parser ... Best regards, Andreas...

...ev/sda3" Is it possible to to boot like tihs? Am I missing something? The contents of syslinux.cfg follows ------------------------------------------------------ DEFAULT linux APPEND ramdisk_size=100000 init=/etc/init lang=us apm=power-off vga=791 initrd=minirt.gz nomce loglevel=0 quiet BOOT_IMAGE=knoppix TIMEOUT 300 PROMPT 1 DISPLAY boot.msg F1 boot.msg F2 f2 F3 f3 LABEL knoppix KERNEL linux APPEND ramdisk_size=100000 init=/etc/init lang=us apm=power-off vga=791 initrd=minirt.gz nomce loglevel=0 quiet BOOT_IMAGE=knoppix LABEL expert KERNEL linux APPEND ramdisk_size=100000 init=/etc/init l...

Hello Booting with 4.06 cmdline looks like: # cat /proc/cmdline archisobasedir=arch archisolabel=ARCH_201301 initrd=boot/i686/archiso.img console=ttyS0 BOOT_IMAGE=boot/i686/vmlinuz while using 5.01: # cat /proc/cmdline boot/i686/vmlinuz boot/i686/vmlinuz archisobasedir=arch archisolabel=ARCH_201302 initrd=boot/i686/archiso.img console=ttyS0 And this cause some issues for cmdline parsing, I guess this is a bug right? Relevant cfg file: LABEL arch32 TE...

...I saw that there is a debug version of isolinux but could not find something similar for syslinux. Does such a thing exist? I have attached my syslinux.conf. * * * * * * * * * * DEFAULT linux24 APPEND ramdisk_size=100000 init=/etc/init lang=us apm=power-off vga=791 initrd=minirt24.gz nomce quiet BOOT_IMAGE=knoppix TIMEOUT 300 PROMPT 1 DISPLAY boot.msg F1 boot.msg F2 f2 F3 f3 LABEL knoppix KERNEL linux24 APPEND ramdisk_size=100000 init=/etc/init lang=us apm=power-off vga=791 initrd=minirt24.gz nomce quiet BOOT_IMAGE=knoppix LABEL memtest KERNEL memtest APPEND initrd= LABEL knoppix-txt KERNEL linux24...

Okay, now, before 3.10 is finalized... what bug reports am I still forgetting? -hpa

...ize from 256 to 1024, tomatch capability in syslinux 3.08. It seems to work. Is this all there is to it ? One of the reasons I did this was to figure out what extra options are appearing, and why. b4 extending: (the last bit is truncated) Jun 4 06:31:05 truck kernel: Kernel command line: BOOT_IMAGE=vmlinuz-2.6.12-rc5-mm2-soekris-v1 console=ttyS0,115200n81 root=/dev/nfs nfsroot=192.168.42.1:/nfshost/truck nfsaddrs=192.168.42.100:192.168.42.1:192.168.42.1:255.255.255.0:soekris:eth0 panic=5 initrd=initrd-2.6.12-rc5-mm2-soekris-v1.img kgdbwai Jun 4 07:33:58 truck kernel: Kernel command line...

...ELTORITO.SYS itself, as MDISKCHK lists the drive properly as E0. Below captured from redirecting to COM1 in QEMU: Drive 00 is MEMDISK 4.04: Address = 0x094ce000, len = 720 sectors, chs = 40/2/9, loader = 0x33 (ISOLINUX), cmdline = nopassany initrd=/isolinux/fdboot.img BOOT_IMAGE=/isolinux/memdisk Drive E0 is MEMDISK 4.04: Address = 0x09549000, len = 7461 sectors, chs = 65535/255/15, loader = 0x33 (ISOLINUX), cmdline = iso initrd=/isolinux/fdbootcd.iso BOOT_IMAGE=/isolinux/memdisk Drive 00 is MEMDISK 4.04: Address = 0x094ce000, len = 72...

...he user sits behind one > of these corporate firewalls that modifies the download payload and > replaces it with something like "You are not authorized to download > this file"... $0.02: - Casting to a uintptr_t is ugly (and not C89, not that Syslinux cares about that) - The boot_image + boot_image_len calculation is loop invariant, so some kind of boot_image_end or wpe pointer before the loop might be nicer. Unfortunately, the 8-bit boot_image_len (bytes) versus the 32-bit wp stride complicates things Maybe something like: const uint32_t * wpe = (const uint32_t *) boot...

...-16-15:10:52-458 Reported: https://retrace.fedoraproject.org/faf/reports/bthash/d5f5d4f75b200eeab2f83c8340a37c5d507e29a3 id e6955aa621a0d296d4cdd05421523885e85a179b reason: BUG: soft lockup - CPU#0 stuck for 36s! [swapper/0:0] time: Tue 09 Aug 2016 04:46:33 PM CLT cmdline: BOOT_IMAGE=/vmlinuz-3.10.0-327.28.2.el7.x86_64 root=/dev/mapper/centos_vmguest-root ro crashkernel=auto rd.lvm.lv=centos_vmguest/root rd.lvm.lv=centos_vmguest/swap rhgb quiet LANG=en_US.UTF-8 package: kernel uid: 0 (root) count: 1 Directory: /var/spool/abrt/oops-2016-08-09-16:...

If the ldlinux being processed is garbage, the search for LDLINUX_MAGIC will overflow its buffer - fix that. I did encounter this issue in Rufus as, due to notorious incompatibilities between different versions of ldlinux.sys and the com32's residing on an ISO, we download a version specific ldlinux.sys from our server... which may get trashed if the user sits behind one of these

...he command-line received by the kerenel is (for another similar stanza) Kernel command line: console=ttyS0,19200n81 root=/dev/nfs nfsroot=192.168.42.1:/nfshost/foo nfsaddrs=192.168.42.100:192.168.42.1:192.168.42.1:255.255.255.0:soekris:eth0 panic=5 initrd=initrd-2.6.10-r10c2-soekris-int-v1.img BOOT_IMAGE=vmlinuz-2.6.10-r10c2-soekris-int-v1 The '4' appears to be getting trashed by the BOOT_IMAGE info appended automatically. I have no IPAPPEND statement in the pxe boot config tia jimc

...T has detected 3 problem(s). For more info run: abrt-cli list --since 1428078184 When I do that, I get: id (blah, blah) reason: WARNING: at drivers/gpu/drm/i915/intel_display.c:869 intel_wait_for_vblank+0x211/0x220 [i915]() time: Fri 03 Apr 2015 11:41:49 AM CDT cmdline: BOOT_IMAGE=/vmlinuz-3.10.0-229.1.2.el7.x86_64 root=UUID=(blah, blah) ro vconsole.keymap=us vconsole.font=latarcyrheb-sun16 rhgb quiet LANG=en_US.UTF-8 count: 1 Directory: /var/tmp/abrt/oops-2015-04-03-11:41:49-590-0 id (blah, blah) reason: WARNING: at drivers/gpu/drm/i915/intel_display...

Hi, I have setup pxelinux like this, default linux label=linux kernel linux append initrd=rootfs.img ipappend 1 I have my dhcpd.conf like this, allow booting; allow bootp; group{ filename "pxelinux.cfg/pxelinux.0"; host deploy { next-server 192.168.1.254; hardware ethernet 00:0E:A6:22:28:21;

...RHEL 5.7 PXE server and trying to get a WinPE ISO to work. Currently PXE seems to handle the image properly but the process stops after Loading boot sector... booting... Full list of what is going on. Ramdisk at 0x72b9c00, length 0x0a680000 command line: iso initrd=../images/windows/winpe_x86.iso BOOT_IMAGE=../memdisk Disk is hard disk 0, 170496 K C/H/S = 340992/1/1 Total size needed = 2091 bytes, allocating 3K Old dos memory at 0x9bc00 (map says 09c00), loading at 09b00 1588: 0xffff 15E801: 03c00 0x71b9 INT 13 08: Success, count = 1, BPT = 0000:0000 old: int13 = f000827c int15 = f000cebe new: int...

...t I get for the different DOS images is as follows: * FreeDOS: (what I have on the screen!): e820: 000000001ff80000 0000000000080000 2 e820: 00000000ff800000 0000000000400000 2 e820: 00000000ffc00000 0000000000400000 2 Ramdisk at 0x1fdf0000, length 0x00168000 command line: initrd=freedos.img BOOT_IMAGE=memdisk.zi Disk is floppy, 1440 K, C/H/S = 80/2/18 Total size needed = 1494 bytes, allocating 2K Old dos memory at 0x9f000 (map says 0x9f000), loading at 0x9e800 1588: 0xffff 15E801: 0x3c00 0x1edf INT 13 08: Success, count = 1, BPT = f000:8ccd old: int13 = f00066ea int15 = f00066ef new: i...

Hi. I'm working on replacing a PXELINUX/MEMDISK loaded DOS based installation image with a PXELINUX/MEMDISK loaded WinPE ISO image. So far everything seems to work well (appending "bigraw" to memdisk solved booting problems on several machines), but I kind of miss the option of using getargs.com to get/set environment variables from the memdisk command line. Is there any way to

not just console= This is to allow vendor-specific boot parameters to survive when the image is installed to disk. Signed-off-by: Alan Pevec <apevec at redhat.com> --- scripts/ovirt-early | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/scripts/ovirt-early b/scripts/ovirt-early index 4b85102..c17ea74 100755 --- a/scripts/ovirt-early +++ b/scripts/ovirt-early @@

...etic logic, unless you specifically use uintptr_t. But, considering your other very valid point, let me see if I can work something better here, that could eliminate this cast. > With the proposed patch's uintptr_t stuff, if the magic isn't found: > > * <------- boot_image_len dictates the final byte > * <-------- wp is less than boot_image_len > 00001111222233XXYYYY <- XX are out-of-bound bytes > * <---- Where wp is when the loop breaks > * <------ As far as any kind of pointer should point >...

sorry: centos7 "fresh" minimal with a actual update cat proc/cmdline: BOOT_IMAGE=/vmlinuz-3.10.0-229.20.1.el7.x86_64 root=/dev/mapper/centos_root ro rd.lvm.lv=centos/root rd.lvm.lv=centos/swap crashkernel=auto rhgb quiet LANG=de_DE.UTF-8 systemd.debug ls /dev/mapper: centos-swap control Zitat von Gordon Messmer <gordon.messmer at gmail.com>: > On 12/02/2015...

...herwise improper initrd (cpio format, > compression, etc). Consider trying your old kernel with new initrd and/or > new kernel with old initrd to start diagnosis. >> >> --Gene > > [ 0.000000] Kernel command line: root=/dev/sda1 initrd=rootfs.ext2 > console=ttyS0,115200 BOOT_IMAGE=bzImage > > [ 0.297992] Unpacking initramfs... > [ 0.298619] Initramfs unpacking failed: junk in compressed archive > [ 0.299718] Freeing initrd memory: 5636k freed If GPT used instead of MBR, no initrd required... Regards, Alexey