similar to: A usb flash drive on which syslinux fails to install

I am attempting to install Gentoo on my cdless machine using the thumbdrive as a boot device. The motherboard is an Intel D815EEA, and is the latest firmware revision (at least on the BIOS). I believe I have done everything right, but it tells me I have unknown keywords in my syslinux.cfg and corrupt kernel images. The steps I have followed are thus: 1) Starting with a 4GB flash device,

alex lupu via Syslinux <syslinux at zytor.com> writes: > On Mon, Mar 16, 2015 at 1:41 PM, Ady via Syslinux <syslinux at zytor.com> > wrote: > >> So, your "root" can still be pointing to sdd2; as long as the >> "vmlinuz-linux" and "initramfs-linux.img" files are located in sdd1 >> directly under the "EFI" directory.

On Wed, Mar 18, 2015 at 8:06 AM, Ferenc Wagner <wferi at niif.hu> wrote: > alex lupu <alupu01 at gmail.com> writes: > > > On Tue, Mar 17, 2015 at 4:16 AM, Ferenc Wagner <wferi at niif.hu> wrote: > >> alex lupu via Syslinux <syslinux at zytor.com> writes: > >>?>? Obviously it would work IF I moved the vmlinuz > >>> and initramfs

This is a post I sent by mistake directly to Ady without a reply to all (i.e., to the thread "Fail to set up UEFI syslinux on ArchLinux USB Flash Drive") It should go between Ady's post of Sun Mar 15 13:23:26 PDT 2015 and Ady's post of Mon Mar 16 06:03:58 PDT 2015 ---------- Forwarded message ---------- From: alex lupu <alupu01 at gmail.com> Date: Sun, Mar 15, 2015 at 7:07

alex lupu <alupu01 at gmail.com> writes: > On Tue, Mar 17, 2015 at 4:16 AM, Ferenc Wagner <wferi at niif.hu> wrote: > >> alex lupu via Syslinux <syslinux at zytor.com> writes: >> >>?>? Obviously it would work IF I moved the vmlinuz >>> and initramfs ?files from /dev/sdd2 to /dev/sdd1. >>> >>> I figured that would probably be

Hi, First, many thanks for your great work. Don't know if it's the good way to post .... But I want to give you a good information ( and also good for me). I try to make an usb bootable SystemrescueCd (www.sysrescd.org) on a new 2Gb Usb Key (noname, UT163 controller from USBest) and it was impossible with syslinux 3.31 release ( using win32 version syslinux.exe). The syslinux command

On Mon, Mar 16, 2015 at 1:41 PM, Ady via Syslinux <syslinux at zytor.com> wrote: > Hmm... AFAIK, efibootmgr currently accepts slash and automatically > converts it into backslash. So for a current version of efibootmgr, a > path like: > /EFI/syslinux/syslinux.efi > (including the initial slash) should be OK as command-line argument. > ?Right?. I just used the

@Alex, please next time use "Reply All" (instead of the simple "Reply") for the mailing list emails; that way the emails will get to the Syslinux Mailing List (instead of arriving to particular members). Now, to the matter in question... (snip) > > Just a minor detail (but it helps for understanding each other)... > > You probably mean "in UEFI

> > Is this "ArchLinux" entry equivalent to "\EFI\syslinux\syslinux.efi" > > in your UEFI firmware? > > Note: UEFI firmware is supposed to use (or show) backslash "\" as path > > separator. > > You have a great point there. > I redid the "efibootmgr" installation and instead of > > efibootmgr -c -d /dev/sdd -p 1 -l

On Tue, Mar 17, 2015 at 4:16 AM, Ferenc Wagner <wferi at niif.hu> wrote: > alex lupu via Syslinux <syslinux at zytor.com> writes: > > ?>? > Obviously it would work IF I moved the vmlinuz > > and initramfs ?files from /dev/sdd2 to /dev/sdd1. > > > > I figured that would probably be considered non-standard Arch > ? ...? > > The standard

On Mon, Mar 16, 2015 at 9:03 AM, Ady via Syslinux <syslinux at zytor.com> wrote: Hi Ady, > please next time use "Reply All" (instead of the simple "Reply") for the mailing list emails ... Sorry about that. Please add my reply to the list for me. Thanks. > Is this "ArchLinux" entry equivalent to "\EFI\syslinux\syslinux.efi" > in your UEFI

On Thu, Jan 19, 2017 at 9:17 AM, Rackover, Zvi <zvi.rackover at intel.com> wrote: > Hi Sanjay, > > > > I agree we should also discuss **if** this canonicalization is beneficial. > > For starters, do we have a concrete case where we would benefit from > canonicalizing shuffles <-> truncates in LLVM IR? > > IMO, we should not count benefits for codegen

Anne Wilson <cannewilson at googlemail.com> wrote: > Can't argue with you :-) It does seem likely, as 1GB flash drives wouldn't > have been a possibility at that time. I never owned one at all until > relatively recently. > > >>> > > They didn't work in 98 first edition, nor in NT4 or Win2000 - again, from >>> > > memory,

Hi, Ady wrote: > In the last few years, ISOLINUX has received very low attention, both > upstream and downstream. Nevertheless the well established Linux distros use it for their ISOs. Most have adopted mjg's isohybrid --uefi layout. Only SuSE does it different. So for me with my xorriso hat on, ISOLINUX is as an important partner as is GRUB. > So I' am about to (attempt to)

Hello, there is a "fdboot.img" floppy drive image included with FreeDOS ISO file. It's a floppy image file: root at debian64:~# file -s /home/martin/FreeDOS/isolinux/fdboot.img /home/martin/FreeDOS/isolinux/fdboot.img: x86 boot sector, FREE-DOS BEta 0.9 Bootloader KERNEL.SYS, code offset 0x40, OEM-ID "FreeDOS ", sectors/cluster 2, root entries 112, sectors 720 (volumes

Trying to set up UEFI Syslinux boot on an ArchLinux USB 4GB stick. - Host system: 64-bit Ubuntu 14.10 on 56 GB hard drive - Hardware: ASUS P8H77-I, Bios v1101, i7-3770 at 3.40 GHz, 16 GB DDR3 - ArchLinux Instructions followed: https://wiki.archlinux.org/index.php/Syslinux#UEFI_Systems > ? ? 2. UEFI Systems > 2.2 Installation - Arch syslinux v.6.03 196352 Oct 13 22:25 /usr/sbin/syslinux

> On 03/18/2017 04:15 PM, Ady Ady via Syslinux wrote: > > > >> On 03/18/2017 01:18 AM, Ady Ady via Syslinux wrote: > >>> _ With the USB device connected to (one of) the problematic > >>> computer(s), power up the system and get into the BIOS setup. In > >>> the BIOS setup screen(s), change the boot order in such way that > >>> the

> > The computer has a HDD mobile rack. I removed the HDD when testing the > Debian installer image on a USB flash drive. So, the only drive other > than the USB flash drive under test was the optical drive. > > In my last email, I forgot to emphasize the following generic procedure. In the BIOS setup screen(s), one set of options are intended for sorting the boot order

Just wondering if someone could help me debug this: I was moving data from an ATARAID (via Promise FastTrack100 Controller) into the LVM device below: 58,1: # cat /proc/lvm/VGs/foo3/LVs/bar name: /dev/foo3/bar size: 476315648 access: 3 status: 1 number: 0 open: 1 allocation: 0 device: 58:01 # /sbin/pvscan pvscan -- reading all physical volumes

I resolved topic 1 please diregard ( libvirtd.conf : Authentication / auth_tcp="none") . Please answer topic 2 as ver 0.8.8 claims cpu controller (cgroups) is not mounted while it is thanks Zvi Dubitzky Email:dubi at il.ibm.com libvirt-users-bounces at redhat.com wrote on 27/03/2011 18:00:05: > From: libvirt-users-request at redhat.com > To: libvirt-users at redhat.com