similar to: microcode_ctl

Hi, I try to mount the file /boot/initrd-2.6.9-42.ELsmp but I have a error [root at localhost ~]# cp /boot/initrd-2.6.9-42.ELsmp.img /root/ [root at localhost ~]# mv initrd-2.6.9-42.ELsmp.img initrd-2.6.9-42.ELsmp.gz [root at localhost ~]# gunzip initrd-2.6.9-42.ELsmp.gz [root at localhost ~]# mount initrd-2.6.9-42.ELsmp /tmp -o loop [root at localhost ~]# mount: you must specify the

It's possible to mount cdrom in rescue mode ? because with centos 4.4 in linux rescue mode, the device "cdrom" doesn't exist -- Denis MACHARD dmachard at fr.netcentrex.net denis.machard at enst-bretagne.fr -------------- next part -------------- An HTML attachment was scrubbed... URL:

Today when I ran yum update two packages came up microcode_ctl and unbound-libs. The updating process went fine until it outputted Running transaction Updating : 2:microcode_ctl-2.1-61.6.el7_8.x86_64 then it just froze. I could no longer ssh to the machine and the console was just blank. I had to shut down it hard. It came back up seemingly fine. But yum update doesn't work anymore. It

After yum upgrade, the new CentOS5 kernel [ kernel-2.6.18-92.1.1.el5.i686 ] crashes each time early in boot process on Compaq ProLiant 3000 with dual Pentium3 CPU (600 MHz, CPU0: Intel Pentium III (Katmai) stepping 03, CPU1 the same). I get kernel panic at powernowk8_init+0x05e/0x1c3. The previous kernel [ kernel-2.6.18-53.1.21.el5.i686 ] seems to work fine. I am wondering if anyone has met

I have seen that file ftp://ftp.openbsd.org/pub/OpenBSD/OpenSSH/portable/openssh-3.4p1.tar.gz is continuosly changing. This seems strange to me as I expected it should be a 'frozen' file; The signature and diff file are still dated Jun 26. I am wondering whether this is intentional. Best regards, Wojtek

On Mon, 2020-06-15 at 22:25 +0200, Robin Lee wrote: > On Fri, 2020-06-12 at 09:20 +0200, Robin Lee wrote: > > Today when I ran yum update two packages came up microcode_ctl > > and unbound-libs. The updating process went fine until it > > outputted > > > > Running transaction > > Updating : 2:microcode_ctl-2.1-61.6.el7_8.x86_64 > > > > then

Hi can someone say me how to update the ?code of the cpu with xen? I have added the ucode=scan parameter to xen but it does not seem to work... the ?code version of my xeon is really old :/ model name : Intel(R) Xeon(R) CPU E3-1271 v3 @ 3.60GHz microcode : 0x10 -- ------ Greetz

it is working thx a lot... but it has included the GenuineIntel.bin only in actually used kernel... do I need to reinstall microcode_ctl every time I update the kernel? And second question, I quess I still need the ucode = scan as xen parameter right? Am 2018-09-19 20:08, schrieb Kevin Stange: > On 9/19/18 1:55 AM, Christoph wrote: >> >> Hi >> >> can someone say me

On 01/18/18 11:31, Matthew Miller wrote: > On Thu, Jan 18, 2018 at 11:01:18AM -0500, Pete Geenhuizen wrote: >> Do we update the microcode now or do we wait until the latest >> microcode_ctl rpm is available and then tackle this issue? > Check with your hardware vendor for BIOS/EFI firmware updates. Apply > those. > > > Thanks for the reply, but you missed what I was

I am enclosing scripts and config files to generate exact copy of CentOS 5.0 i386 installation DVD image, that is CentOS-5.0-i386-bin-DVD.iso if you have CD images for i386. If there is interest I can post the same for x86_64. Please follow README files for instructions. All the scripts are GPL. SHA1 for attached files: 439f7b0bd50722388a2836eedafeb1c227f97385 *00_README.txt

Thanks for the breakdown Paul - I've had to learn all my sysadmin stuff through organic interactions like this. Still though - someone manages the default repositories - so my question is, who decides when a package gets an update from whatever CentOS ships with default to a newer version? How does that process take place, and, can I affect it by adding microcode_ctl-2.1-18 ? On Wed, Jan 4,

On 01/18/18 09:01, Johnny Hughes wrote: > On 01/18/2018 07:51 AM, Phelps, Matthew wrote: >> On Thu, Jan 18, 2018 at 5:03 AM, Johnny Hughes <johnny at centos.org> wrote: >> >> So, if we applied the previous microcode update, and all our machines >> rebooted OK, then we don't need to fallback? >> >> Also, do we know if the updated CentOS microcode RPM

Hi, is there any guide for CPU microcode updates on CentOS6, Xen 4.10, kernel 4.9 ? Thanks Karel

Not sure about CentOS 6, but this was covered previously (at least for 7...not sure how much they differ)...not that I can find the message now, but here's what I recall/pieced together from bash history that works on CentOS 7: If the microcode you want is in the microcode_ctl package: mkdir -p /etc/microcode_ctl/ucode_with_caveats/ touch /etc/microcode_ctl/ucode_with_caveats/force yum

On Thu, Jan 18, 2018 at 5:03 AM, Johnny Hughes <johnny at centos.org> wrote: > On 01/18/2018 03:41 AM, Pete Biggs wrote: > > > >> Look at: > >> > >> https://t.co/6fT61xgtGH > >> > >> Get the latest microcode.dat file from here: > >> > >> https://t.co/zPwagbeJFY > >> > >> See how to update the microcode

Hello all! I'm brand new to the mailing list, and I've encountered an issue with the microcode_ctl package version 2.1-16 being installed during the CentOS 7.3 upgrade. It causes my servers to hard stop and they need to be forcibly powered off and back on again with the power button to continue. This RedHat thread https://bugzilla.redhat.com/show_bug.cgi?id=1398698 details the issue,

> Look at: > > https://t.co/6fT61xgtGH > > Get the latest microcode.dat file from here: > > https://t.co/zPwagbeJFY > > See how to update the microcode from the links at the bottom of this page: > > https://t.co/EOgclWdHCw > > An before anyone asks .. I have no idea why Red Hat chose this path, > they did. It doesn't matter if I (or anyone else)

/etc/init.d/microcode_ctl start /etc/init.d/microcode_ctl: microcode device /dev/cpu/microcode doesn't exist? This is on a clean install from the 4.1 x86 ISO. This is the 2nd box that is reporting this error. Adam Breaux Sr. Network Administrator Domain Bank, Inc. 23 W 4th St. Bethlehem, PA 18015 Phone: 610.317.9606 Fax: 610.317.9570 abreaux at domainbank.com

On 01/18/2018 09:42 AM, Valeri Galtsev wrote: > > > On 01/18/18 03:41, Pete Biggs wrote: >> >>> Look at: >>> >>> https://t.co/6fT61xgtGH >>> >>> Get the latest microcode.dat file from here: >>> >>> https://t.co/zPwagbeJFY >>> >>> See how to update the microcode from the links at the bottom of this

Hi All, What is the correct way to provide a CentOS 7 - WMware image for ESX ? As an amateur to VMware - I thought - great I can get VMplayer and ESX should be able to import my image... Wrong... I even went through the trouble of "converting" to VMWare workstation and thinking ESX could import that - Apparently still Wrong... I cannot for the life of me understand how one product