similar to: memdisk troubles while compiling with gcc 4.01

Hi there, while my memdisk setup works perfectly well an an Intel system it fails like this on a Via-C3 based Mini-ITX system (copied manualy, I hope I did not make a mistake): --cut-- Failed to Free base memory, sorry... MEMDISK 2.08 (Debian, 2003-12-22) Copyright 2001-2003 H. Peter Anvin e820: 0000000000000000 000000000009fc00 1 e820: 000000000009fc00 0000000000000400 1 e820: 00000000000f0000

Hi, I am working on the diskless booting over Infiniband networks. At the moment we have created and implemented architecture which allow diskless booting of Linux nodes on x86, x86_64 and Itanium platforms. The system works by booting first small custom made Linux kernel of the Infiniband adapter ROM. The kernel has enough of infiniband stack to setup TCP/IP networking over infiniband. Then it

Hello ALL, I've got a diskless server working (under Gentoo), booting on it works. (a linux session start with no problem.) My Big problem, is to get Memdisk to boot with PXE. In fact memdisk is loaded, but it cannot find the img file. I've tried a lot of thing, but nothing works... tftp use : /diskless the config file for PXE in then in : /diskless/pxelinux.cfg/ the root for the

Got to minimize (barely) my filesystem and kernel and fit it into my usb key (256mb) My kernel was compiles with scsi and usb support built-in. My problem now is i can't mount my root filesystem when i tried to boot. kernel somehow takes time before being able to recognize my usb as a valid scsi device thus displaying VFS: Cannot open root device 08:01 this is my lilo.conf boot=/dev/sda

From : Erwan Velu <erwan.velu at free.fr> This patch fixes the pci detection stuff demo'd in pcitest.c32 - Fix a wrong type in malloc - Incorrect use of strdup This two fixes makes pcitest.c32 working far better, no more crash when running it twice. I'd like to thank Sebastian Herbszt for its reports and tests. This patch was made for 3.62-pre16 but applies fine on 3.63-pre1.

From: Gene Cumm <gene.cumm at gmail.com> run.c: A simple COM32 module that will optionally clear the screen (using newlines) then run a command. Signed-off-by: Gene Cumm <gene.cumm at gmail.com> --- This is based on my alias COM32 module that I submitted back in October, with some improvements to clean up debugging code and optionally clear the screen. LABEL et KERNEL run.c32

From : Erwan Velu <erwan.velu at free.fr> This patch - remove the pci detection code from ethersel - add a find_pci_device() function in the PCI com32 module - make ethersel using the pci com32 module instead of builtin pci detection code Testing and feedback are welcome. Signed-off-by:Erwan Velu <erwan.velu at free.fr> -------------- next part -------------- A non-text attachment

On Fri, Sep 04, 2015 at 09:15:07AM -0700, syslinux-bot for Erwan Velu wrote: > Commit-ID: 66105926f3d748de827eb863913171efb9624165 > Gitweb: http://www.syslinux.org/commit/66105926f3d748de827eb863913171efb9624165 > Author: Erwan Velu <erwanaliasr1 at gmail.com> > AuthorDate: Wed, 2 Sep 2015 18:26:37 +0200 > Committer: Erwan Velu <erwanaliasr1 at gmail.com> >

From : Erwan Velu <erwan.velu at free.fr> As discussed on IRC, I've been reworking my patch, I resend it. This patch - add a new pci_dev_info structure : It contains additional informations about the pci devices like the product/vendor name and the associated linux kernel module - add a get_name_from_pci_ids() function in pci/scan.c This function reads a pci.ids file from the

Greetings, As a Google Summer of Code student for the SYSLINUX project, I had the chance to learn many interesting things from hpa regarding the internals of SYSLINUX. So besides my main task of implementing ELF modules loading & linking, I decided to put down in the wiki all the information I found concerning SYSLINUX development. In this regard, I have created a special category on the

-- Erwan Velu Pre-Sales Engineer Seanodes http://www.seanodes.com +33 (0)1 41 22 13 83 -------------- next part -------------- An embedded message was scrubbed... From: Pierre-Alexandre Meyer <pierre at mouraf.org> Subject: Re: [hdt] Serial Date: Wed, 6 May 2009 03:43:25 +0200 Size: 2726 URL: <http://www.zytor.com/pipermail/hdt/attachments/20090506/ffd99419/attachment.eml>

From : Erwan Velu <erwan.velu at free.fr> This patch add the ability to read the long-mode flag from the processor. This helps you to know if the processor is x86_64 capable or not. So "dmi->processor.cpu_flags.lm " is a boolean that represent the "Long Mode" cpu flag. It also add two bugfix : - some cpu flags were shifted due to some "null" messages in

It is supposed to match but sometimes it doesn't; I had the case where I contacted my local server on my public adress and responded from the loopback. So it was the same server from two different addresses which confused then the rest of the code. By adding this print I was able to get the situation immediately and fixed it. That's why I added that information on the debug print.

Ralf Carl a ?crit : > Hello Erwan, > > i just want to inform you, that there is still no memory entry in the > main menu (hdt_034 & hdt_035). > Typing in DMI mode "show module 0" etc. the memory modules are listet. You mean the menu mode isn't working whereas the cli mode works ? Do you confirm this , IF yes, It seems the Type 6 (the only one you have as you

Hi! I have problems to boot with memdisk and pxe the hard drive tests from seagate, hitachi, western digital... does has someone done it and can sym me how? (maxtor works perfectly) ByE

While playing with the current master of Syslinux, I figured out two bugs I'd like to share with you. 1- Missing menu entires If you consider a file with the following entries, only the first item appears label mga32 kernel anything label mga64 kernel anything Looks like the number at the end of the label is giving some headaches to gfxboot. If I do rename this two entries by

Your PxeLinux is really a good product and contains really good features (i.e memdisk). But PxeLinux is a very low level program, contains assembly code and seems to no be portable to Itanium architectures. Does a version of PxeLinux planned for Itanium architecture ? PS:On my configuration, option pxelinux.reboottime (code 211) you give in your documentation removes my "default router"

diff --git a/core/localboot.c b/core/localboot.c index 0b8769e4..30bfb272 100644 --- a/core/localboot.c +++ b/core/localboot.c @@ -63,7 +63,6 @@ __export void local_boot(int16_t ax) ireg.eax.w[0] = 0; /* Reset drive */ __intcall(0x13, &ireg, NULL); - memset(&ireg, 0, sizeof(ireg)); ireg.eax.w[0] = 0x0201; /* Read one sector */ ireg.ecx.w[0] = 0x0001; /* C/H/S = 0/0/1 (first

Hello, everyone; A few important questions if you use PXELINUX - Do you use the PXELINUX-specific DHCP options? - If you do, what DHCP server do you use? - Are you using vendor encapsulation (a vendor-option-space) or not (a site-option-space)? - Would it be inconvenient for you if these options were changed? RFC 3942 is flagging these option codes for reclamation as official options. I

Sorry for the totally newb question, but I coudn't find out from your website and posts if this is possible. Is it possible to use PXELinux to PXE boot a system and load a bootable ISO instead of a bootable floppy? If yes, are there size limitations on the ISO? I would like to PXE boot to WinPE using PXELinux if possible. Thanks