similar to: "keeppxe" broken in 3.74 - short-cycle 3.75

A kind request for help please. MEMDISK is causing an issue with the Dell OptiPlex GX280 and GX620 platforms. Booting a PC-DOS/Ghost, disk image is successful (and proper) when using version 3.83. See results below: MEMDISK 3.83: Ramdisk at 0x07eeaa00, length 0x007bc000 command line: initrd=images/ghostclient/280_620/osbootc.img BOOT_IMAGE=memdisk MEMDISK: Image seems to have fractional end

Good day to you, too. No worries about the delay. I understand how busy everyone is with SYSLINUX. Gladly, the project continues to develop and improve. With that said, thanks for today's flurry of activity regarding my reported problem. Impressively, the debug version of MEMDISK that you had directed me to use appears to have done the trick. Results below. command line:

Hi, Currently I am building a new PXE boot environment and during that I noticed something odd while attempting to boot using one of those universal netbootdisks based on the '3Com Universal NDIS driver v1.00' (aka undis3c) driver. Using pxelinux.0 this works like a charm, but when I switch to gpxelinux.0 the 3Com driver bails out on me... all other configuration is the same. Have

Hello syslinuxers I'm stuck with a scientific problem which gives me headaches: I have a laptop (Gateway MX3410) which has a SD memory card reader. Recently an interesting thought crossed my mind: why don't I setup a 2GB SD card as a harddrive and put some rescue tools on it. So I dug on the net and I came across the idea of using memdisk to boot floppy images without the need of a

The subject says it all really, I''m pretty sure the system and bios are NUMA aware but I''m not sure if it''s enabled? Is it supported in 3.2.1 stable? Thanks, Rob \ \/ /___ _ __ |___ / |___ \ / | \ // _ \ ''_ \ |_ \ __) | | | / \ __/ | | | ___) | / __/ _| | /_/\_\___|_| |_| |____(_)_____(_)_| (XEN) Xen version 3.2.1

I am unable to boot Dom0 on my IBM eServer BladeCenter HS20, type 8843, EMT64 blades. I have read reports that Dom0 boots on Opteron boxes, but on my EMT64 blades, it does not. Has anyone else encountered this problem on EMT64 hardware? Here are the errors I am getting: This is on a SLES 9 box, gcc version 3.3.3 (SuSE Linux): kernel (hd0,0)/boot/xen.gz dom0_mem=256000 com2=19200,8n1

I'm working on getting the latest Linux distros working well on one of our prototype machines, however, some of them are failing to boot into the installer from the CD/DVD images. I've narrowed it down to isolinux hanging just before displaying the graphical menu. After a little bisecting between the last version that worked (3.73) and the first version which was broken (3.74), I found

Let's try to get this thing released. Dag: will you do your RPM buildathon on this drop? Changes in 3.74: * New UI directive, which allows a more natural way to specify a menu system (or not.) With the UI directive specifying the menu system, the DEFAULT directive can be used to select the default entry inside the menus. * kbdmap.c32: new module

Well, here it is. This is a historic Syslinux release -- it's the first one in 15 years in which the majority of the work was not done by myself; mostly because of the *huge* effort Erwan and Pierre have put in on HDT. I also want to give a special thank you to my new(ish) employer, Intel Corporation, for letting me continue to work on Syslinux. :) From here, onward and upward. I

Hi everybody. I have a xen full virtualized guest running with 32 bit WIN 2003 Enterprise edition with 8 GB RAM assigned to it, but when the Virtual Machine starts only recognize 3,75 GB. I Have edit boot.ini with /PAE switch but still don't work. In addition,when i set pae value = 1 in the guest config file, the system gave me a blue screen after the windows splash screen. Kind regards

but it works well with pxelinux.0 in 3.75

In pxelinux.asm the xchg instruction in xchg ax,ax . data_on_top: should be xchg ax,dx, I think At the end of pxe_get_cached_info routine,there is and ax,ax jnz .err It is supposed to test for AX status, but since pxenv does pushad and popad, AX doesn't contain status. In fact the other routines calling pxenv don't have this bug.

./configure works fine. make generates the error ...... gcc -g -O2 -I../include -I../../src/include -c saveload.c -o saveload.o In file included from /usr/include/sys/turnstile.h:12, from /usr/include/sys/t_lock.h:20, from /usr/include/sys/vnode.h:37, from /usr/include/sys/stream.h:21, from /usr/include/netinet/in.h:38,

3.75 is a bug fix release for 3.74. Changes in 3.75: * PXELINUX: fix the "keeppxe" option, which was broken in 3.74. * MEMDISK: correct the extraction of geometry information from the MBR of a hard disk image, again broken in 3.74. * extlinux(1) man page from Brian Pellin. * Simple menu: MENU SAVE is now controllable on a menu-by-menu

When you add "quiet" to the append line, Syslinux doesn't display the file reading progress anymore. When you use this option to boot an image with MEMDISK, you still get a lot of text. ========================== LABEL mydisk LINUX memdisk INITRD mydisk.img APPEND raw quiet ========================== The following patch makes MEMDISK silent when the quiet keyword is passed to the

Helle, I'm facing a strange issue with memdisk The context : syslinux 3.75 gpxelinux.0 the gpxe stript called from a menu executed through menu.c32 : #!gpxe kernel /modules/memdisk initrd=/freedos initrd /freedos The output before the freeze : /boot.gpxe. ok /modules/memdisk. ok /freedos...... ok MEMDISK 3.75 3.75 Copyright 2001-2009 H. Peter Anvin et al e820: 0000000000000000

Hello! I am encountering a problem with one of the machines I am using and the timer going backwards. It looks like the problem is due to to a bad PM-Timer entry being found. Though when debugging further, the real source of the problem stems from an ACPI table of type DSDT being parsed as an FADT during boot and certainly a bogus PM-Timer is found there. Here''s the output from

Hello. Minimal testcase for my problem: No X running, just a TTY. Use of the nouveau kernel module as of today (or any older) with an up to date vanilla kernel. Hardware: DELL Vostro 3500 with Geforce 310M. To suspend to ram I use this script, as suggested in Documentation/power/s2ram.txt: #!/bin/sh sync echo 1 > /sys/power/pm_trace echo mem > /sys/power/state When I try to suspend to

I just built 4.3.0 in order to get > 2GB of RAM in domU with GPU passthrough without crashes. Unfortunately, the same crashes still happen. Massive frame buffer corruption on domU before it locks up solid. It seems the PCI memory stomp is still happening. I am using qemu-dm, as I did on Xen 4.2.x. So whatever fix for this went into 4.3.0 didn''t fix it for me. Passing less than 2GB

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-4 Severity: normal Tags: squeeze When the monitor is being restored from power saving mode via DPMS, X will lock up/restart. This only occurs when running Xen hypervisor. Running just 2.6.32-5 -xen-amd64 doesn't produce this effect. Note that both 2.6.32-5-xen-amd64 and 2.6.32-5-xen-amd64 with Xen 4.0.1 are running with nopat (to workaround