On Wed, Oct 4, 2023 at 11:36 AM Peter Böhm <peter...@web.de> wrote:
>
> Am Mittwoch, 4. Oktober 2023, 05:42:17 CEST schrieb Valmor F. de Almeida:
>
> > -> cat /proc/cpuinfo
> >
> > processor : 0
> > vendor_id : GenuineIntel
> > cpu family : 6
> > model : 158
> > model name : Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
> > stepping : 9
> > microcode : 0x84
>
> At the moment this is our actual microcode for Intel CPUs:
>
> sys-firmware/intel-microcode-20230808_p20230804
>
> If you look into:
>
> https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/blob/main/
> releasenote.md
>
> You will see that version f4 is actual for your CPU (dec 6-158-9 is hex
> 6-9e-9) instead your version 84.
>
> KBL-G/H/S/X/E3 B0 06-9e-09/2a 000000f2 000000f4
> Core
> Gen7; Xeon E3 v6
>
> What you can always do:
>
> 1. Boot with our GentooMinimalCD (so you have the new/actual microcode active
> on your CPU)
> 2. Chroot into your system (like you do with a new installation)
> 3. Re-emerge all packages with "emerge -e ..."
>
> After this, if you boot your kernel-6.1.53-r1 you should have no problem.
>
>
I tried to chroot in the installation using the latest GentooMinimalCD
(it does run the linux-6.1.53-gentoo-r1 kernel) but I am unable to
mount the root directory.
-> lsblk
[snip]
nvme0n1 259:0 0 9453.9G 0 disk
|--nvme0n1p1 259.0 0 2M 0 part
|--nvme0n1p2. 259.0 0 128M 0 part
|--nvme0n1p3 259.0 0 1.6G 0 part
|--nvme0n1p4 259.0 0 952.2G 0 part
-> swapon /dev/nvme0n1p3
-> mount /dev/nvme0n1p4 /mnt/gentoo
mout: /mnt/gentoo: can't read superblock on /dev/nvme0n1p4.
dmesg(1) may have more information after failed mount system call.
-> dmesg
[snip]
nvme nvme0: controller is down; will reset: ....
nvme nvme0: Does your device have a faulty power saving mode enabled?
[snip]
EXT4-fs (nvme0n1p4): unable to read superblock
I am still able to boot with the old kernel 6-1-41-gentoo.
Does this mean I may have a hardware problem with the NVMe drive?
Thanks for inputs.
--
Valmor
