similar to: Fail to set up UEFI syslinux on ArchLinux USB Flash Drive

Displaying 20 results from an estimated 8000 matches similar to: "Fail to set up UEFI syslinux on ArchLinux USB Flash Drive"

2015 Mar 16
0
Fail to set up UEFI syslinux on ArchLinux USB Flash Drive
@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
2015 Mar 16
0
Fwd: Fail to set up UEFI syslinux on ArchLinux USB Flash Drive
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
2015 Mar 16
2
Fail to set up UEFI syslinux on ArchLinux USB Flash Drive
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
2015 Mar 16
0
Fail to set up UEFI syslinux on ArchLinux USB Flash Drive
> > 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
2015 Mar 16
2
Fail to set up UEFI syslinux on ArchLinux USB Flash Drive
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
2015 Mar 17
2
Fail to set up UEFI syslinux on ArchLinux USB Flash Drive
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
2015 Mar 17
0
Fail to set up UEFI syslinux on ArchLinux USB Flash Drive
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.
2015 Mar 18
0
Fail to set up UEFI syslinux on ArchLinux USB Flash Drive
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
2015 Mar 19
1
Fail to set up UEFI syslinux on ArchLinux USB Flash Drive
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
2009 May 22
2
USB issues
I am using centos5.3 x86_64 on a gigabyte GA-MA78GM-US2H motherboard. When I insert a USB thumbdrive its detected with dmesg, I mount it and start to copy files. Then I start getting errors: sdd: assuming drive cache: write through sdd: sdd1 sdd2 sd 7:0:0:0: Attached scsi removable disk sdd sd 7:0:0:0: Attached scsi generic sg4 type 0 usb-storage: device scan complete usb 1-5: reset high speed
2007 Nov 29
1
RAID, LVM, extra disks...
Hi, This is my current config: /dev/md0 -> 200 MB -> sda1 + sdd1 -> /boot /dev/md1 -> 36 GB -> sda2 + sdd2 -> form VolGroup00 with md2 /dev/md2 -> 18 GB -> sdb1 + sde1 -> form VolGroup00 with md1 sda,sdd -> 36 GB 10k SCSI HDDs sdb,sde -> 18 GB 10k SCSI HDDs I have added 2 36 GB 10K SCSI drives in it, they are detected as sdc and sdf. What should I do if I
2009 May 01
1
Compositing Manager Crash over XDMCP on .8.2.1 on Archlinux?
Danny, Kristian, All, First let me tell you guys whatever you are doing with compiz, keep it up! It's looking great! I have a new error on ArchLinux when running compiz 0.8.2.1 that I have never seen before. I installed Archlinux on 2 boxes to check it out. One on a x86_64 box with the nvidia driver (no problems there) and one on an i686 box with onboard intel video. When connecting over
2015 Feb 18
5
CentOS 7: software RAID 5 array with 4 disks and no spares?
Hi, I just replaced Slackware64 14.1 running on my office's HP Proliant Microserver with a fresh installation of CentOS 7. The server has 4 x 250 GB disks. Every disk is configured like this : * 200 MB /dev/sdX1 for /boot * 4 GB /dev/sdX2 for swap * 248 GB /dev/sdX3 for / There are supposed to be no spare devices. /boot and swap are all supposed to be assembled in RAID level 1 across
2017 Aug 23
9
[Bug 102368] New: Since Archlinux testing migrate to mesa 17.1.7, I got a pink overlay in webcam software.
https://bugs.freedesktop.org/show_bug.cgi?id=102368 Bug ID: 102368 Summary: Since Archlinux testing migrate to mesa 17.1.7, I got a pink overlay in webcam software. Product: Mesa Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium
2010 Dec 03
1
Archlinux port of libguestfs
Hello, I am looking into porting libguestfs to Archlinux, as I understand it I need to add a stanza to the if/else statement in the appliance/make.sh.into handle the image creation for ArchLinux. But I am wondering, the image used in the binary libguestfs is much larger than the one in the fedora libguestfs, and they appear to be packaged as initramfs images. So my question is this, should I
2010 Jul 12
1
archlinux as dom0, oops and quirks
Hi, I''m running an archlinux x64 dom0. Since yesterday, after an upgrade which is hard to revert, I am having problems with my domU domains. I can start two domU domains, consecutive domains fail. The error is: Error: Device 0 (vif) could not be connected. Hotplug scripts not working. I am using a kernel that has been patched with the gentoo xen sources. The build process is visible at
2012 Dec 03
1
packagelist.in for archlinux
latest archlinux has some small changes: btrfs-progs-unstable --> btrfs-progs genisoimage --> cdrkit iproute --> iproute2 module-init-tools --> kmod procps --> procps-ng udev --> systemd util-linux-ng --> util-linux and could you plz add the below packages lrzip less sed -- Evaggelos Balaskas - Unix System Engineer http://gr.linkedin.com/in/evaggelosbalaskas
2006 Mar 23
2
rails lighttpd fastcgi archlinux
When I try to access the rails app, it''s giving me "Routing Error: Recognition failed for "/"" displayed on my browser. Has anyone ran into this problem before? -- Vincent H Gov -------------- next part -------------- An HTML attachment was scrubbed... URL: http://wrath.rubyonrails.org/pipermail/rails/attachments/20060323/78ccb76e/attachment.html
2011 Sep 27
1
"make check" on ArchLinux: "This kernel requires an x86-64 CPU, but only detected an i686 CPU"
I'm updating the ArchLinux libguestfs package to 1.12.7, but the "make check" tests fail in qemu with: Booting from ROM... This kernel requires an x86-64 CPU, but only detected an i686 CPU. Unable to boot - please use a kernel appropriate for your CPU. How does qemu detect the CPU type? I'm running a 64-bit ArchLinux (without KVM) on an Intel Xeon E5420 processor. I'm
2013 Nov 23
9
Sysinux 6 will not boot ISOs on BIOS (i.e. pre-UEFI) systems
-- Re-sent as original may be stuck at awaiting "authorisation" (originally sent before I joined the mailing list) Hi All, It is impossible to boot Linux-based ISOs that use Syslinux 6.02 via CD or DVD on older - non-UEFI - systems. Any attempt to do so will result in the following error message: ISOLINUX 6.02 ETCDisolinux: Disk error 01, AX = 4279, drive FE It is still possible to