search for: anciennement

Bruno Cornec via Syslinux said on Sun, Oct 25, 2015 at 12:39:53PM +0100: >I'm indeed trying to have everything I need on the boot part of the >ISO9660 image (kernel and an initrd which is normally built by >MondoRescue which then mounts the ISO9660 FS to have access to >additional content once booted). For now I do not seem to get to boot the >kernel. > >My machines are HP

> Hi, > > some minor nitpicking on Ady's summary: > > > the real "genisoimage" is not really up to the task for > > UEFI-booting. > > In some distros, genisoimage offers option -e for embedding > a FAT filesystem image. > (genisoimage is a fork of mkisofs, so "real" is somewhat > misleading in respect to history.) > > For

On Tue, Oct 27, 2015 at 10:15 PM, Bruno Cornec via Syslinux <syslinux at zytor.com> wrote: > Bruno Cornec via Syslinux said on Wed, Oct 28, 2015 at 01:45:22AM +0100: >> >> Is there a way to increase the debug level of syslinux.efi in order to >> check what it tries to do and diagnose more precisely what happens ? > > > Ok, I tried to modify mk/devel.mk to put:

Thomas Schmitt via Syslinux said on Sat, Oct 24, 2015 at 12:56:49AM +0200: >Needed is a EFI FAT image > 32 MiB and a new xorriso (available >on demand). My test script on RHEL 7.1 creates that even if I could make it smaller as the kernel + initrd fits in less than 32 MB. So let me make that try first ! o I changed myline in the script to dd a 30 MB image file, burt the ISO with it, and

Bruno Cornec via Syslinux said on Wed, Oct 28, 2015 at 01:45:22AM +0100: >Is there a way to increase the debug level of syslinux.efi in order to >check what it tries to do and diagnose more precisely what happens ? Ok, I tried to modify mk/devel.mk to put: GCCWARN += -Wno-clobbered -DCORE_DEBUG=1 -DDEBUG_MALLOC -DDEBUG_THREAD And removing the -DDYNAMIC_DEBUG but now syslinux doesn't

Hello, Ady via Syslinux said on Sat, Oct 24, 2015 at 12:56:26AM +0300: >> EFI expects 0 "no emulation", although 4 "hard disk" would have >> been an obvious choice, too. >> But probably they wanted to avoid the need for partition table >> interpretation inside the EFI System Partition. >> > >And here is the issue :-O. Or I should say, the

Hello, Ady via Syslinux said on Fri, Oct 23, 2015 at 04:10:29PM +0300: >I still would like more details from Bruno. If indeed "everything" >needed to boot the OS is inside the FAT image, then at least 2 issues >could be relevant: >_ the exact complete characteristics of the FAT image; >_ the exact complete command line used to build the ISO image. Hopefully my other

To whom it may concern: Hi, I am looking for PXE boot loader that supports IA64 platform. Do you have the version of SYSLINUX that supports this platform? If not, do you plan to have such support for in the future? What are your suggestions and recommendations? Thank you in advance for your help. Sincerely, Albert To

...to all the domain it doesnt works is somebody got an explication thank you and sorry for my poor english -- ---------------------------------------------------- Pascal Legrand *IUT de Chartres* - _Service Informatique_ ---------------------------------------------------- 1, place Roger Joly (/anciennement/ /place/ /Pierre/ /Mend?s/ /France/) 28000 Chartres Tel : 02 37 91 83 36 - Fax: 02 37 91 83 01 courriel : Pascal.Legrand@univ-orleans.fr

Hello, Ady via Syslinux said on Mon, Apr 06, 2015 at 09:57:02PM +0300: >Can 'syslinux.efi' v.6.03 boot some media formatted with ISO9660? > Not at this time, no. It took me quite some time to find that :-( Google didn't really help. I'd like to get a bit more details on this issue: 1/ Using syslinux.efi for PXE booting of a UEFI server is working for me. 2/ Using

Hello Thomas, Thomas Schmitt via Syslinux said on Sun, Oct 25, 2015 at 04:35:57PM +0100: >I assume you can boot Fedora Live CD on the same (virtual) hardware. Not sure for Fedora, but the system is installed with either RHEL6, RHEL7 or Ubuntu 14.04 depending on the Lab I'm making on it without issue. >Just to make sure that the firmware works so far. Globally they do ;-) >

Hello, Ady via Syslinux said on Sun, Oct 25, 2015 at 08:15:37PM +0200: >_ Creating filesystem that _does_ conform to ISO-9660; I think the only issue is with a tag. That same image boots with grub 0.99 >_ The fat image should not be bigger than 32MiB, and it should be >aligned. The latter suggestion is usually ignored by almost everyone, >but if we are troubleshooting... Tried with

Gene Cumm said on Wed, Oct 28, 2015 at 05:58:59AM -0400: >> Ok, I tried to modify mk/devel.mk to put: >> GCCWARN += -Wno-clobbered -DCORE_DEBUG=1 -DDEBUG_MALLOC -DDEBUG_THREAD >> And removing the -DDYNAMIC_DEBUG but now syslinux doesn't want to build: > >MALLOC and THREAD are two debugs you probably don't want. Ok I can drop them, but that doesn't change the

On Thu, Oct 22, 2015 at 1:56 PM, Bruno Cornec via Syslinux <syslinux at zytor.com> wrote: > 3/ Using syslinux.efi in a FAT32 image (similar to the previous 2 > confs) stored on a iso9660 media by genisoimage and its > -eltorito-alt-boot -efi-boot $imagefile -no-emul-boot option doesn't > work. I get a red screen with debug info (attached). However, I'm not >

> Hi, > > Ady wrote: > > Is this "32MiB" a limitation related to the UEFI specs in any way? Or > > is it relevant for BIOS (non-EFI) too? > > It comes from El Torito specs which are referred to by UEFI 2.4 > specs. In EL Torito 1.0, Figures 3 and 5, "Sector Count" is a 2-byte > "Word". So it can count up to 65535. > Sector count

Hello, Gene Cumm said on Thu, Oct 22, 2015 at 06:39:44PM -0400: >On Thu, Oct 22, 2015 at 1:56 PM, Bruno Cornec via Syslinux ><syslinux at zytor.com> wrote: > >> 3/ Using syslinux.efi in a FAT32 image (similar to the previous 2 >> confs) stored on a iso9660 media by genisoimage and its >> -eltorito-alt-boot -efi-boot $imagefile -no-emul-boot option doesn't

...beaulaton.fr/ # # Tel + 33 (0)5 57 89 27 17 # ############################### --------------------------------------------- Cemagref (French Institute of Agricultural and Environmental Engineering Research ) Unit? "Ecosyst?mes estuariens et poissons migrateurs amphihalins" (anciennement Unit? "Ressources aquatiques continentales") 50 avenue de Verdun F 33612 Cestas Cedex Tel + 33 (0)5 57 89 27 17 Fax + 33 (0)5 57 89 08 01 mailto:laurent.beaulaton at bordeaux.cemagref.fr http://www.laurent-beaulaton.fr/ http://www.bordeaux.cemagref.fr/rabx/

> Hello, > > Gene Cumm said on Thu, Oct 22, 2015 at 06:39:44PM -0400: > >On Thu, Oct 22, 2015 at 1:56 PM, Bruno Cornec via Syslinux > ><syslinux at zytor.com> wrote: > > > >> 3/ Using syslinux.efi in a FAT32 image (similar to the previous 2 > >> confs) stored on a iso9660 media by genisoimage and its > >> -eltorito-alt-boot -efi-boot

Hi All, My PXE configurations works fine for a bios PXE (the server in legacy mode) but hangs in an EUFI mode. Look like it can transfer the bootx64.efi but not the next one ldlinux.e64 Any ideas? Thanks Software> syslinux ver 6.3 atftp 7.1 Log server side >> Booting Embedded LOM 1 Port 1 : HP Ethernet 1Gb 4-port 331i Adapter - NIC (PXE IPv4) >> Booting PXE over

Bonjour Alex. Ce matin j'ai installer "rubyinstaller-1.9.1-p243-rc1.exe" "wxruby-ruby19-2.0.1-x86-mingw32.gem" "SciTE.exe 2.0.1.0" Quand j'exécute (avec scite) mon fichier "Rss-wxruby.rbw" qui est encodé en utf8 et qui habituellement(avec les anciennes versions de ruby, wxruby et scite) fonctionne correctement, j'obtient ce message