search for: common_problem

Thank you for pointing the direction. Indeed, ver. 6.03 works correctly. BTW, this project gets very complicated. I spent a lot of time guessing which files I would need. I hoped that reading Makefile would help me but I it did not. Maybe you could add a target for copying final results to a destination. (Target 'installer' do sth else ... /slackware 14.1/) Best regards P.O.

On Fri, Oct 10, 2014 at 7:18 AM, Ady <ady-sf at hotmail.com> wrote: > >> On Oct 10, 2014 4:00 AM, "Ady" <ady-sf at hotmail.com> wrote: >> > >> > >> > > Hello, >> > > >> > > I've encountered a strange problem with loading a font file. >> > > The environment: >> > > motherboard

Hi folks! In my system i have a SSD card, and i try to install extlinux in it. But, my extlinux installation not work!! I make a initrd to boot my machine on lan, and my init execute a installation of extlinux version 3.86 on my SSD card. The installation on init is similar to: http://pastebin.com/szcYCCjR The return of installation of extlinux is: /mnt is /dev/sda1 And the install not report

On 01/19/2014 03:47 PM, Ronald F. Guilmette wrote: > > Doesn't the Syslinux project provide (hopefully strong) specific > reccomendations, to its user base, for how these things should best > be done, you know, in order to insure maximal interoperability? > We try (see our wiki), but those recommendations can only come from mass testing across many, many systems -- which we

...me >> things like rename isolinux.cfg to syslinux.cfg, but with no >> success. > > That alone can be an issue. You should only use COM32 modules > from the same build. Crossing from 6.xx to 4.xx will definitely > not work. > > http://www.syslinux.org/wiki/index.php/Common_Problems#Modules Shouldn't be enough copy modules from /user/lib/syslinux....? > >> I'm sure the Debian isolinux.cfg is reached because I've added a >> line "SAY something" and the message is displayed, the problem is >> in the line "default vesamenu.c32&q...

...k." which would not have helped me to avoid Ronald's problem. I would have considered any existing FAT as "normal". Maybe one should add a link to a new section "Possible pitfalls of MS-DOS disk partitioning and formatting" in http://www.syslinux.org/wiki/index.php/Common_Problems It would give an overview or links about "partitioning", "filesystem", "FAT", "LBA", and "Cylinder/Head/Sector". Then it would advise Ady's layout of LBA driven FAT32 with conservative partitioning. I would volunteer as half-educated author...

...the cause of the problem. I've tried some things like > rename isolinux.cfg to syslinux.cfg, but with no success. That alone can be an issue. You should only use COM32 modules from the same build. Crossing from 6.xx to 4.xx will definitely not work. http://www.syslinux.org/wiki/index.php/Common_Problems#Modules > I'm sure the Debian isolinux.cfg is reached because I've added a line > "SAY something" and the message is displayed, the problem is in the > line "default vesamenu.c32" > > Best regards and thanks in advanced -- -Gene

...successfully, load kernel vmlinuz, then start to load initrd.img but reset a minute or two later. rhel7 kernel 3.10.0 works better in the VM and actually loads successfully and kickstarts, but the HP G9 blade still resets whilst loading initrd. The page at http://www.syslinux.org/wiki/index.php/Common_Problems states: Linux EFI pre-3.3 Most kernels before Linux-3.3 have also been observed to have other issues. Symptoms include spontaneous reboot at some point after kernel execution begins. So does this mean we can't efi net boot rhel6/7 centos 6/7 or any distro that uses pre 3.3 kernels? Thank...

...http://www.syslinux.org/wiki/index.php/User:Scdbackup The first section shall become the new text of http://www.syslinux.org/wiki/index.php/SYSLINUX#Creating_a_Bootable_Disk The second section shall become a new section Bad Heritage on MS-DOS disk in http://www.syslinux.org/wiki/index.php/Common_Problems [about USB Geometry] > My point was about the several possible ways such wording could be > interpreted by different users when reading them in the Syslinux > wiki. I meanwhile united the section "USB Miscellenous" with http://www.syslinux.org/wiki/index.php/Hardware_Comp...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hello. I'm trying to setup an multiboot USB, mainly to install Debian using netinst images. I've mounted one of iso image and copied to a directory in USB (made with syslinux 6.03) and copied too the kernel and initrd for hd install. I've setup a directory to start the USB and, well it starts, but when I jump (using CONFIG) to the

...uot;supposedly" bootable in BIOS and/or (U)EFI > systems at the time (e.g. Slackware 14.0 / 14.1, Debian 7 Wheezy, RHEL > 6.x / 7 ) > _ BIOS and/or (U)EFI systems > > As a remainder and FWIW, from prior discussions (2014Q4) we have: > http://www.syslinux.org/wiki/index.php/Common_Problems#Linux_EFI_kernels http://www.syslinux.org/archives/2013-October/021021.html is the only possible match I see on the list, if that helps. Plus the Fedora and Arch bug reports.

...(EFISTUB) standards", "supposedly" bootable in BIOS and/or (U)EFI systems at the time (e.g. Slackware 14.0 / 14.1, Debian 7 Wheezy, RHEL 6.x / 7 ) _ BIOS and/or (U)EFI systems As a remainder and FWIW, from prior discussions (2014Q4) we have: http://www.syslinux.org/wiki/index.php/Common_Problems#Linux_EFI_kernels Yet, "fallback" method(s) should be allowed (in some way; with and/or without user intervention, and/or with/without printing information for the user). This feature is currently not present in Syslinux 6.03. Additionally, I would tend to think that whichever the co...

Hi all, I did my first steps on syslinux 6.03 with EFI... I prepared the disk with GPT, EFI system partition and formatted it FAT32. I added the files to EFI/BOOT including the syslinux libraries and syslinux.cfg The system starts booting, loads kernel and initrd (I see the loading output on the screen), but then the system resets and the loop restarts (infinitely). I took the same

...ootstrap program -- i.e., what's in your dhcpd.conf file) for efi32 should be efi32/core/syslinux.efi and for efi64, it should be efi64/core/syslinux.efi. You said this. The syslinux "Common Problems" page *sort of* says this. This link: http://www.syslinux.org/wiki/index.php/Common_Problems "Multi-Arch" section sort of says this -- if you understand that "core binary" means PXE NBP. (I did not). At least I get further -- syslinux.efi loads, then TFTP errors in loading ldlinux.e64. I'm trying again with 6.0.3-pre6. (Another suggestion). If someone finds t...

...other cases, such >> as for kernel 3.2 (which is going to be alive in Debian Wheezy for at >> least a couple more years). >> >> So, can someone please clarify this situation? > >In an effort to get things started, I just wrote >http://www.syslinux.org/wiki/index.php/Common_Problems#Linux_EFI_kernels > >I understand the CONFIG_RELOCATABLE issue well enough to write about >it however Ady seems to have stumbled upon a real key for the >pre-Linux-3.3 kernels. If I'm understanding correctly, I think H. Peter Anvin on Tues Nov 18th, 10:24:15 PST 2014 explained thi...

...39;s what I think WDS demands - or at least for whatever chainloads the PXELinux off another TFTP server. 2) As a fallback, PXEChain as I understand requires another DHCP server http://www.vcritical.com/2011/06/peaceful-coexistence-wds-and-linux-pxe-servers/ http://www.syslinux.org/wiki/index.php/Common_Problems#pxechain.com-2 These docs look good by they don't explain how it all plays together with PXELinux dual booting with EFI/Non EFI shared configuration. Does PXEChain do everything I want? Can it even a pass configuration file for PXELinux to start with.pxechain This looks very interesting - T...

> On 10/10/17 12:28, Manuel Wagesreither via Syslinux wrote: > > Dear all, > > > > I'm working on a shell script which is producing a bootable image file. It contains a populated MBR and a single file system (ext4) which again contains a debootstrabed debian stable distribution. > > Used versions: > > extlinux 6.03 > > QEMU emulator version

On Thu, Feb 12, 2015 at 09:33:27AM +0200, Ady wrote: > On Thu, Feb 12, 2015 at 05:17:08PM +1100, Paul Daniels wrote: > > Im a long time PXE boot fan. I use it for wimbooting windows PE, linux > > images via http, and memtest mainly. > > > > Ive got it nicely customised with my own graphics etc. > > > > Then UEFI booting came along. Till now ive been

On Sat, 7 Feb 2015, Ady via Syslinux wrote: > Thank you for this meaningful report. Ideally, I would suggest > performing a similar test (at least with the same kernel built with all > the above "config_*=y" settings) with official pre-built Syslinux > versions 4.07 and 3.86 (remembering that all Syslinux-related files, > including c32 modules, if being used, shall

> > http://www.syslinux.org/wiki/index.php/Common_Problems#Modules > > Shouldn't be enough copy modules from /user/lib/syslinux....? > 1_ Booting with Syslinux, in the Syslinux "boot:" prompt press "Ctrl+V" so to see relevant information. The c32 modules shall match the same version. 2_ The Current Working Directory...