similar to: bug in ifcpu64 if !pae and only two options?

New module which check if the PLoP Boot Loader already has booted a CDROM or USB drive by checking for the presence of the PLoP INT13h hook. The following assembly code (NASM) can detect the PLoP INT13h hook: mov eax,'PoLP' ; Reverse of 'PLoP' mov ebp,'DKHC' ; Reverse of 'CHKD' int 13h cmp eax,' sey' ; Reverse of 'yes ' jz

Even though Doug's out of the office, I'm submitting a patch to the ifcpu[|64].c32 COMBOOT32 modules for testing. Also available for perusal with a web browser at: http://git.zytor.com/?p=users/sha0/syslinux.git;a=commitdiff;h=cc70d0fa5 5e35fabf250f4dccbaed2fa44f56da7 - Shao Miller --- >From cc70d0fa55e35fabf250f4dccbaed2fa44f56da7 Mon Sep 17 00:00:00 2001 From: Shao

I wrote a new module "whichsys.c32" which detemines which command to execute, based on the Syslinux bootloader variant. In the near future it should/can be replaced by a lua script. But for people who want small binaries: whichsys.c32 is +/- eighty times smaller than lua.c32, atm. Usage: whichsys.c32 [-iso- command] [-pxe- command] [-sys- command] Examples: whichsys.c32 -iso-

ifgpxe.c32 is a com32 module that will run one command if gPXE extensions are available, and a different command if not. At VMware, we use this module to chain-load gpxelinux.0 from pxelinux.0. Both of those binaries use exactly the same configuration file, and this module allows us to differentiate between the two cases and break the infinite chain-loading loop that might result. Typical usage:

Below, attached, and available at the 'ifmemdsk' branch at: http://git.zytor.com/?p=users/sha0/syslinux.git;a=commitdiff;h=a975c12919bbd48739fede4ebfe099d98b87192e Review welcome! - Shao Miller ----- From a975c12919bbd48739fede4ebfe099d98b87192e Mon Sep 17 00:00:00 2001 From: Shao Miller <shao.miller at yrdsb.edu.on.ca> Date: Sat, 6 Aug 2011 05:24:46 -0400 Subject: [PATCH]

Another issue which looks like a bug. If 'ipappend' is set globally (not uncommon in network/pxelinux environment), the last entry for ifcpu64.c32 gets messed up -- to the 2nd (or 3rd) label all the chars from ipappend gets appended, without spaces, resulting in a messy label. Adding -- after the 3rd entry does not help -- the minuses too gets addedd to the command line. For now I

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

Note: I could simply direct boot the appropriate kernel/initrd to get the alpha1 installation going as always done in the past, but I think this should work. The Debian alpha 1 installer page says it should. Details $ sudo xm create -c wheezytest.cfg Using config file "./wheezytest.cfg". Error: Boot loader didn''t return any data! direct pygrub test run: # pygrub

Hi Is there a doc/wiki page which explains, the kind of domu images/appliances/kernels can be run with what type of dom0 kernels(xen_caps). For example : -- Can a 32 bit, non-PAE domU run on 64 bit, PAE dom 0 in PV mode ? (or HVM mode ?) Are there any checks that can be done before doing the migration ? Is there any programmatic way (from python) to find out if the kernel in a domU disk

Processing commands for control at bugs.debian.org: > reassign 463121 xen-unstable Bug#463121: xen-unstable non non-pae hypervisor package is not pae Bug reassigned from package `xen-unstable' to `xen-unstable'. > -- Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)

Package: xen-hypervisor-3.0-i386-pae Severity: normal Forwarding a problem reported by Nathan Hawkins. > I ran into a problem with the PAE version of the hypervisor. I'm looking at > xen-hypervisor-3.0-i386-pae_3.0.2+hg9611-1_i386.deb from alioth, and I > ran into a problem with PAE being disabled in the binary: > > $ zcat xen-3.0-i386-pae.gz | strings | grep PAE

Package: xen-hypervisor-3.0-i386-pae Severity: wishlist The description of the package should give hints as to why it is different from xen-hypervisor-3.0-i386. Mike -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-686 Locale:

Hello, as said in the subject; I am having problems with ifcpu.c32 and ifcpu64.c32 detecting a Athlon II X4 CPU correctly as a 64Bit capable CPU. Ifcpu64.c32 does not detect PAE capabilities, also. Both boot the last (32Bit, non-PAE) entry. On two other Core2-based machines I have here, everything works. Can someone tell me what exactly these modules are looking for? Maybe I can compare that

I stumbled across the following patch and wondered if it wouldn't be a good idea to have it included. http://foldingcd.svn.sourceforge.net/viewvc/*checkout*/foldingcd/trunk/folding_cd/patches/syslinux-3.51-64bit.patch?revision=5 It adds a default64 keyword and detection of a 64bit processor. It could be useful for mixed environments. The patch is against 3.51, but looks like it would port

Hi, I was wondering if anyone would know the cons of running a PAE kernel...? I have a 4GB pc and was wondering if it was worth going the PAE way to gain those exta 700MB... In the past, I heard that these 700MB were normally reserved for bios or chipset stuff... And that running in PAE would slow down some processes. By the way, I know 64 bits would solve this dilemn but right now I am

In a word, is it stable? I''m seeing some odd things; segfaults by postgres in a domU, when pae is enabled. And, this last time, I got this on the ssh I had to the domU: == database:/home/shared/doogie# Message from syslogd@database at Wed Dec 14 18:55:05 2005 ... database kernel: [27073.874149] Bad page state at prep_new_page (in process ''postmaster'', page c1326ca0)

Why are these APIC clock init hooks dependent on CONFIG_X86_PAE ? include/asm/paravirt.h: static inline void setup_boot_clock(void) { paravirt_ops.setup_boot_clock(); } static inline void setup_secondary_clock(void) { paravirt_ops.setup_secondary_clock(); } (via the vmi timer patch). - James -- James Morris <jmorris@namei.org>

During tracking down a PAE compile failure, I found that config.h was being included in a bunch of places in i386 code. It is no longer necessary, so drop it. Signed-off-by: Zachary Amsden <zach@vmware.com> =================================================================== --- a/arch/i386/boot/video.S +++ b/arch/i386/boot/video.S @@ -10,8 +10,6 @@ * For further information, look at

Adjustments deemed necessary to properly support PAE (only compile-tested). Signed-off-by: Jan Beulich <jbeulich@novell.com> Index: 2007-01-11/tools/libxc/xc_ptrace.c =================================================================== --- 2007-01-11.orig/tools/libxc/xc_ptrace.c 2006-12-14 22:49:56.000000000 +0100 +++ 2007-01-11/tools/libxc/xc_ptrace.c 2007-01-12 14:10:45.000000000 +0100 @@

Hello, I have a problem with a new install of xen. I work on a Dell poweredge 2950, bi xeon Quadcore ang 32G of memory. The domain0 run on a gentoo 32 Bits. I use xen 3.1.2 with pae xen kernel : 2.6.20 So when i boot on a normal kernel, i see all of my memory. But when i boot on the xen kernel, i have only 15G memory available. I try to force the size memory in the boot options in grub