Now wondering if it’s due to this issue -
https://bugzilla.redhat.com/show_bug.cgi?id=1861977
Have installed fedora for now, will see if want to reinstall centos8.
On Fri, Jul 31, 2020 at 08:13 Anshu Prateek wrote:
> Hi folks,
>
> I am able to install workstation successfully on a dedicated SS
On 31.07.20 04:52, Greg Bailey wrote:
m running CentOS 8.2 on an Intel NUC, and also hit this this morning.
> The way I was able to workaround this was to copy grub2-* and shim-*
> RPMs from the CentOS 8.2 installation media and use "rpm -Uvh grub2-*
> shim-* --oldpackage". The subsequent reboot
On 7/30/20 7:43 PM, Anshu Prateek wrote:
Hi folks,
I am able to install workstation successfully on a dedicated SSD w/ GPT
partition w/ UEFI boot using the latest `CentOS-8.2.2004-x86_64-dvd1.iso`
from a bootable pen drive.
The motherboard is ASRock x570 Gaming 4 (
https://www.asrock.com/mb/AMD
On Fri, 2020-01-31 at 08:05 -0500, Jonathan Billings wrote:
> On Thu, Jan 30, 2020 at 04:51:49PM -0500, Jerry Geis wrote:
> > This package is installed. Yes I am talking about installing a
> > CentOS 8guest on a centos 8 machine with UEFI.The dvd.iso is on the
> > host, which I point to. Nothing in
On Thu, Jan 30, 2020 at 04:51:49PM -0500, Jerry Geis wrote:
> This package is installed. Yes I am talking about installing a CentOS 8
> guest on a centos 8 machine with UEFI.
> The dvd.iso is on the host, which I point to. Nothing in the define new
> wizard mentions UEFI.
I believe in the virt-man
Am Donnerstag, 30. Januar 2020, 22:51:49 CET schrieb Jerry Geis:
> >Are you talking about booting a libvirt/kvm guest via UEFI?
> >
> >You need to install the edk2-ovmf package for a UEFI firmware before
> >you can create VMs with it.
>
> This package is installed. Yes I am talking about installin
>Are you talking about booting a libvirt/kvm guest via UEFI?
>You need to install the edk2-ovmf package for a UEFI firmware before
>you can create VMs with it.
This package is installed. Yes I am talking about installing a CentOS 8
guest on a centos 8 machine with UEFI.
The dvd.iso is on the host
On Thu, Jan 30, 2020 at 02:35:26PM -0500, Jerry Geis wrote:
> Are UEFI clients still not possible on 8.1 ?
> I was looking for a setup in the GUI and dont see it.
>
> Searching "suggests" that --boot-uefi may be a command line option - but
> again I see nothing on the GUI.
Are you talking about b
Cracked it.
Failure to boot was the result of including tboot in the install package set,
for some reason or other. It's not needed and removing it does the trick.
https://access.redhat.com/articles/2217041
And I thought I was going spare when it worked with one install package set and
not ano
isdtor writes:
> Gordon Messmer writes:
> > On 10/21/19 6:38 AM, isdtor wrote:
> > > Booting with CentOS6 /boot/efi/EFI/redhat/grub.efi, and the older style
> > > pxe config file as per ... results in a grub (legacy) prompt on the
> > > target machine.
> >
> >
> > Have you tried using the file
Gordon Messmer writes:
> On 10/21/19 6:38 AM, isdtor wrote:
> > Booting with CentOS6 /boot/efi/EFI/redhat/grub.efi, and the older style pxe
> > config file as per ... results in a grub (legacy) prompt on the target
> > machine.
>
>
> Have you tried using the file from the installation tree?
>
On 10/21/19 6:38 AM, isdtor wrote:
Booting with CentOS6 /boot/efi/EFI/redhat/grub.efi, and the older style pxe
config file as per ... results in a grub (legacy) prompt on the target machine.
Have you tried using the file from the installation tree?
http://centos.s.uw.edu/centos/6/os/x86_64/E
Chris Adams writes:
> Once upon a time, isdtor said:
> > Yes, it looks like I'm out of luck and need to find a newer machine to test
> > this with. Moving the tftp server works to an extent - server boots right
> > into a grub prompt.
>
> Weird. I have a couple of Intel-based systems that do U
On Sep 19, 2019, at 7:42 AM, Jerry Geis wrote:
> I installed my first UEFI disk yesterday. Seemed to go fine. CentOS 7.6
> x86_64
> I then took that disk "out" of that machine and put it another machine - it
> seems to not even boot.
> I put the original disk back in that machine and it boots fine
On Thu, 19 Sep 2019, Simon Matter via CentOS wrote:
Just wondering, will it still boot if he then puts the disk back to the
other machine?
My understanding is yes, as this is just updating the EFI Boot Manager, which
is stored in non-volatile storage on the motherboard.
If anyone knows bette
> On Thu, 19 Sep 2019, Jerry Geis wrote:
>
>> I installed my first UEFI disk yesterday. Seemed to go fine. CentOS 7.6
>> x86_64
>> I then took that disk "out" of that machine and put it another machine -
>> it
>> seems to not even boot.
>> I put the original disk back in that machine and it boots f
On Thu, 19 Sep 2019, Jerry Geis wrote:
I installed my first UEFI disk yesterday. Seemed to go fine. CentOS 7.6
x86_64
I then took that disk "out" of that machine and put it another machine - it
seems to not even boot.
I put the original disk back in that machine and it boots fine.
I put the UEF
On Thu, Sep 19, 2019 at 6:43 AM Jerry Geis wrote:
>
> I installed my first UEFI disk yesterday. Seemed to go fine. CentOS 7.6
> x86_64
> I then took that disk "out" of that machine and put it another machine - it
> seems to not even boot.
> I put the original disk back in that machine and it boots
I have been doing some more research on this and it appears that this is often
a problem with the BIOS / EFI implementation not correctly respecting the boot
order setting.
However, as it used to work on this laptop with the previous HDD I do not
believe this to be the point.
Oddly, when I put
On Thursday 30 May 2019 13:16:37 Jonathan Billings wrote:
> This is all I was asking you to check. See the PARTUUID in the output
> of blkid? PARTUUID="14c4ac1d-abd8-4121-84ee-c05a825920de"
> It matches the UUID of the boot entry:
> HD(2,GPT,14c4ac1d-abd8-4121-84ee-c05a825920de,0x145800,0x6400\0
On Thu, May 30, 2019 at 10:50:16AM +0100, Gary Stainburn wrote:
> [root@gary ~]# efibootmgr -v
> BootCurrent: 0004
> Timeout: 0 seconds
> BootOrder: 0002,3002,,0003,0004,0005,2001,2002,2003
> Boot* Linux
> HD(2,GPT,14c4ac1d-abd8-4121-84ee-c05a825920de,0x145800,0x64000)/File(\EFI\centos\shi
On Tuesday 28 May 2019 19:52:02 Jonathan Billings wrote:
> I suggest running 'blkid' and 'efibootmgr -v', and double-check that
> the UUID for the CentOS boot entry matches the UUID of the EFI disk.
>
> You can delete and recreate the boot entry with 'efibootmgr', which
> will likely solve the pro
On Tue, May 28, 2019 at 12:29:39PM +0100, Gary Stainburn wrote:
> I then wiped all the Linux partitions and did a clean C7 install
> using the latest ISO, all went well, but when it reboot it went
> straight into Windows. Using F9 on reboot I chose CentOS Linux and
> the new system booted. Using
On Tuesday 28 May 2019 13:30:44 Günther J. Niederwimmer wrote:
> Hello,
>
> change the bootorder
> > BootOrder: 0002,3002,,0003,0004,0005,2001,2002,2003
> your first boot is windows
>
I know, that's my problem. If you look further down the OP I successfully
change the boot sequence, but it
Hello,
change the bootorder
> BootOrder: 0002,3002,,0003,0004,0005,2001,2002,2003
your first boot is windows
Am Dienstag, 28. Mai 2019, 13:29:39 CEST schrieb Gary Stainburn:
> Morning all,
>
> I have a HP Envy dual boot system (Win8 for serious stuff, i.e. Train Sim
> and Flight Sim) and Ce
Once upon a time, isdtor said:
> Yes, it looks like I'm out of luck and need to find a newer machine to test
> this with. Moving the tftp server works to an extent - server boots right
> into a grub prompt.
Weird. I have a couple of Intel-based systems that do UEFI PXE boot
okay, but they're m
Chris Adams writes:
> Once upon a time, isdtor said:
> > 11:06:51.413549 IP (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto
> > UDP (17), length 390)
> > 10.1.2.2.67 > 255.255.255.255.68: [udp sum ok] BOOTP/DHCP, Reply,
> > length 362, xid 0x4007adc6, Flags [Broadcast] (0x8000)
> >
Once upon a time, isdtor said:
> 11:06:51.413549 IP (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto
> UDP (17), length 390)
> 10.1.2.2.67 > 255.255.255.255.68: [udp sum ok] BOOTP/DHCP, Reply, length
> 362, xid 0x4007adc6, Flags [Broadcast] (0x8000)
> Your-IP 10.1.2.57
>
James Peltier writes:
> Welcome to the world of UEFI. Certain UEFI versions have added additional
> support for things like the next-server option to actually be honoured. In
> some versions this _is_ in fact _ignored_ and you are expected to place the
> image on the server that answers the DH
> Just set up ISC DHCP on fresh CentOS 7 install and followed the redhat
> guide linked in this thread.
> Did what I thought was correct and duplicated the OPs problem.
> /me scratches head. . . off to `tcpdump -vv -nn -i ens192`. . . packets
> never lie. . .
> Vendor-Class Option 60,
On Thu, Apr 25, 2019 at 8:46 PM Chris Adams wrote:
> Once upon a time, Steven Tardy said:
> > The “ICMP unreachable” should be a dead giveaway. . .
>
> You cut out the part of the email where the OP said that the UEFI system
> was ignoring the next-server part of the DHCP reply and trying to TFT
Once upon a time, Steven Tardy said:
> The “ICMP unreachable” should be a dead giveaway. . .
You cut out the part of the email where the OP said that the UEFI system
was ignoring the next-server part of the DHCP reply and trying to TFTP
to the DHCP server instead of the TFTP server. Of course th
On Thu, Apr 25, 2019 at 5:25 AM isdtor wrote:
> 09:02:02.911381 IP client.cisco-ipsla > dhcp-server.tftp: 56 RRQ
> "linux-install/bootx64.efi" octet tsize 0 blksize 32768
> 09:02:02.911403 IP dhcp-server > client: ICMP dhcp-server udp port tftp
> unreachable, length 92
>
The “ICMP unreachable”
Chris Adams writes:
> Once upon a time, isdtor said:
> > We have a working PXE setup. I've tried to adapt it to UEFI as per
> > RHEL6 manual, but the client won't boot.
>
> I have BIOS+UEFI PXE boot set up, although it took some doing. I still
> use SYSLINUX for BIOS, but GRUB2 plus Red Hat's se
Once upon a time, isdtor said:
> We have a working PXE setup. I've tried to adapt it to UEFI as per
> RHEL6 manual, but the client won't boot.
I have BIOS+UEFI PXE boot set up, although it took some doing. I still
use SYSLINUX for BIOS, but GRUB2 plus Red Hat's secure boot shim for
UEFI. I neve
It's risky and a bit complicated. However I've tried it (on a
workstation, not on a laptop) and it worked (CentOS/Win8 dualboot)
fine. Backing up your entire disk to an img file before attempting to
make a dual-boot setup CentOS/Windows on a laptop would be an
excellent first step.
Create a USB im
Hi Jerry,
As UEFI and LEGACY mode installations are hardware features, you need to go
through the systems BIOS settings where you can find installation method
settings, then flip the method from LEGACY to UEFI . You need to reinstall
the OS after making this change.
Thanks,
__
There's this document:
https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/ch-Boot-x86.html
The important thing is that you need to install the OS with the firmware
that you want to run the system with, so you'll need to re-install the
system us
On 03/27/2013 09:25 AM, m.r...@5-cent.us wrote:
> why is it that the OEM does not provide the UEFI key with the
> hardware FOR THAT BOARD AND UEFI, rather than have it provided by M$?
Because then you'd have to install a version of Windows (or any other
OS) signed FOR THAT BOARD AND UEFI.
Secure
Waleed Harbi wrote:
> On Wednesday, March 27, 2013, wrote:
>
>> Y'know, I was just reading an article about a Spanish Linux group filing
>> a complaint with the EU regulators about UEFI, and I was struck by a
>> thought: why is it that the OEM does not provide the UEFI key with the
>> hardware FOR
It depends on the hardware vendor. Which hardware vendor they faced the
issue?
On Wednesday, March 27, 2013, wrote:
> Y'know, I was just reading an article about a Spanish Linux group filing a
> complaint with the EU regulators about UEFI, and I was struck by a
> thought: why is it that the OEM d
The 6.4 Minimal install does not work with UEFI. It was the first one I
downloaded, and it is broken. Comes up with an error after the initial
grub either a file not found or error 15 or something.
I haven't tried the full disk 1 yet though.
Our solution is a little more involved than that.
On 03/13/2013 01:30 PM, Skeeve Stevens wrote:
This has caused me to burn hours trying to figure what is going on until
> someone pointed me to: CentOS-6.3-x86_64-minimal-EFI.iso - which worked
> fine (except no LAN drivers for this device are present - damnit).
In 6.4 - the standard DVD's are EFI
Yeah.. investigated the UEFI Config very extensively.
There might be alternate firmware out there, but I assume that all devices
are going UEFI due to Windows 8 or something. It is killing me :(
...Skeeve
*Skeeve Stevens - *eintellego Networks Pty Ltd
ske...@eintellegonetworks.com ; www.eintelle
Skeeve Stevens wrote:
> Hey all,
>
> We've developed our own microserver platform sitting on top of CentOS 5.4.
> We deploy them in many locations and normally use netbooks for this
> purpose. This has worked fine for years, except most netbooks have
> started to disappear (in Australia).
But, d
45 matches
Mail list logo
