[SOLVED] "Locked Nvram detected" / API issue on reboot (Elementary and Mint)

Rafaelys

Rafaelys

Member
Joined
Jan 29, 2020
Messages
47
Reaction score
24
Credits
464
Hello everyone,

This was after an attempt to configure the HDD on /home folder together with an SSD, but It's probably unrelated to that, as the problem persists after several attempts to reinstall both Elementary and Linux Mint, and using Ubiquity to allocate the /home folder on the HDD.

Problem is, after installing any OS via live USB (.iso have been checked and are ok), the system does not survive the reboot. A black screen, tty terminal shows up (if activated) but that's it.

- I've tried to change some GRUB parameters from there following other threads (such as "GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=off"), but won't boot still.

- From what I gathered it can be something related to API. Before the black screen after the reboot, I was able to quickly read something related to problems with API. Some threads suggest downgrading kernel version in this case. If it helps,

Code: 
$$ cat /proc/version

Linux version 5.4.0-66-generic (buildd@lgw01-amd64-016)
(gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)) #74~18.04.2-Ubuntu
SMP Fri Feb 5 11:17:31 UTC 2021

- Timeshift snapshot taken before the reboot is not overloading any of the drives. On the other hand, restoring via the live session not solved the problem either.

- Boot Repair Summary (still made in the USB live session) is saying these things, also points to "Locked Nvram detected".

- I'll copy the results for "dmesg --level=warn" also:

Code: 
[    0.113817] MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
[    0.113867]  #3
[    0.118041] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[    1.271730] platform eisa.0: EISA: Cannot allocate resource for mainboard
[    1.271731] platform eisa.0: Cannot allocate resource for EISA slot 1
[    1.271732] platform eisa.0: Cannot allocate resource for EISA slot 2
[    1.271733] platform eisa.0: Cannot allocate resource for EISA slot 3
[    1.271734] platform eisa.0: Cannot allocate resource for EISA slot 4
[    1.271735] platform eisa.0: Cannot allocate resource for EISA slot 5
[    1.271736] platform eisa.0: Cannot allocate resource for EISA slot 6
[    1.271737] platform eisa.0: Cannot allocate resource for EISA slot 7
[    1.271738] platform eisa.0: Cannot allocate resource for EISA slot 8
[    1.427440] wmi_bus wmi_bus-PNP0C14:01: WQBC data block query control method not found
[    1.491014] r8169 0000:07:00.0: can't disable ASPM; OS doesn't have ASPM control
[    1.550907] MXM: GUID detected in BIOS
[    1.551129] ACPI Warning: \_SB.PCI0.RP05.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20190816/nsarguments-66)
[    1.666498] [Firmware Bug]: ACPI(PEGP) defines _DOD but not _DOS
[    1.669833] No Local Variables are initialized for Method [_BCL]
[    1.669834] No Arguments are initialized for method [_BCL]
[    4.383954] systemd[1]: /lib/systemd/system/systemd-udevd.service:31: Unknown lvalue 'RestrictSUIDSGID' in section 'Service'
[    5.123209] dell-smbios A80593CE-A997-11DA-B012-B622A1EF5492: WMI SMBIOS userspace interface not supported(0), try upgrading to a newer BIOS
[  435.251930] kauditd_printk_skb: 9 callbacks suppressed
[ 1669.658233] FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 2471.900434] printk: systemd: 51 output lines suppressed due to ratelimiting
[ 4147.698636] kauditd_printk_skb: 12 callbacks suppressed
[ 9171.352682] kauditd_printk_skb: 1 callbacks suppressed
[15140.862886] IRQ 47: no longer affine to CPU1
[15140.864667] IRQ 44: no longer affine to CPU2
[15140.866577] IRQ 18: no longer affine to CPU3
[15140.866586] IRQ 23: no longer affine to CPU3
[15141.610592] done.
[15145.367256] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0).
[15145.367259] atkbd serio0: Use 'setkeycodes e00d <keycode>' to make it known.
 
Last edited:


MODERATOR'S NOTE: Previous work done on @Rafaelys 's drive and partition is contained in this Thread https://linux.org/threads/taking-better-advantage-of-ssd-hdd-config-in-installation.32965/

Wizard

@Rafaelys A note on that Terminal command above, the syntax is incorrect.

The $ sign is a part of your prompt, as in for me

chris@elementaryOS-Hera:~$

... so lose it.

And there are no spaces between level and warn, so

dmesg --level=warn

Mine, from Elementary OS looks as follows

Code: 
chris@elementaryOS-Hera:~$ dmesg --level=warn
[    0.030306] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[    0.030307] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
[    0.037712] MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
[    0.037712]  #5 #6 #7
[    0.049226] No Local Variables are initialized for Method [PXSX]
[    0.049228] No Arguments are initialized for method [PXSX]
[    0.049563] No Local Variables are initialized for Method [PXSX]
[    0.049564] No Arguments are initialized for method [PXSX]
[    0.821843] (NULL device *): hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info().
[    0.863632] usb: port power management may be unreliable
[    0.865863] i8042: Warning: Keylock active
[    1.070728] wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found
[    1.152973] ATPX version 1, functions 0x00000033
[    1.153038] ATPX Hybrid Graphics
[    1.192243] CRAT table not found
[    1.243122] amdgpu: [powerplay] can't get the mac of 5
[    6.874057] amdgpu: [powerplay] VI should always have 2 performance levels
[   22.396791] ACPI Warning: \_SB.IETM._TRT: Return Package has no elements (empty) (20170831/nsprepkg-130)
[   22.419546] (NULL device *): hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info().
[   22.685783] i2c_hid i2c-DELL0811:00: i2c-DELL0811:00 supply vdd not found, using dummy regulator
[   23.053271] DELL0811:00 044E:120A: Invalid code 5 type 4
[   23.506201] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:03:00.0.bin failed with error -2
[   23.506269] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/cal-pci-0000:03:00.0.bin failed with error -2
[   24.475163] ath10k_pci 0000:03:00.0: Unknown eventid: 3
[   24.490179] ath10k_pci 0000:03:00.0: Unknown eventid: 118809
[   24.493026] ath10k_pci 0000:03:00.0: Unknown eventid: 90118
[   28.936173] amdgpu: [powerplay] can't get the mac of 5
[   32.287689] ath10k_pci 0000:03:00.0: Unknown eventid: 3
[   32.302424] ath10k_pci 0000:03:00.0: Unknown eventid: 118809
[   32.305301] ath10k_pci 0000:03:00.0: Unknown eventid: 90118
[   37.797633] amdgpu: [powerplay] VI should always have 2 performance levels
chris@elementaryOS-Hera:~$

These are warnings only, so of no particular concern.

The "locked Nvram" message in the Pastebin output may be beyond my paygrade, so if anyone else can assist here, I would be grateful. :)

A Linux Mint user here, had success by resetting CMOS jumper leads, but I have not ever performed that exercise.

https://forums.linuxmint.com/viewtopic.php?t=327158

1. I note, too, from the Pastebin output that your HDD /dev/sdb appears to be partitioned to MBR, but that /dev/sda the SSD is GPT.

It is not a good idea to mix the two. They are better as both GPT or else both MBR.

2. Previously, at your other Thread

sudo fdisk -l

output had both /dev/sda and /dev/sdb as

Code: 
Disc label type: dos

... which is MBR style.

Now, however, the Pastebin output is showing /dev/sda as

============================= Drive/Partition Info =============================

Disks info: ____________________________________________________________________

sda : is-GPT, no-BIOSboot, has---ESP,
Click to expand...

and

3. That ESP (EFI System Partition) is shown as being

Code: 
sda2  458588160 468860927  10272768   4.9G EFI System

4.9 GB? An ESP should be between 100 MB and 550 MB, average 300 MB.

What gives, I wonder?

I am just getting confused, I will have to think about this.

Wiz
 
wizardfromoz said:
These are warnings only, so of no particular concern.
Click to expand...

Good to know. Started google each line of it and it was crazy

wizardfromoz said:
@Rafaelys A note on that Terminal command above, the syntax is incorrect.
Click to expand...

Thanks. Now it's correct.

wizardfromoz said:
1. I note, too, from the Pastebin output that your HDD /dev/sdb appears to be partitioned to MBR, but that /dev/sda the SSD is GPT.

It is not a good idea to mix the two. They are better as both GPT or else both MBR.
Click to expand...

I honestly don't know how it get to this, but I hope doing another clean install on ubiquity is a way to fix it

wizardfromoz said:
3. That ESP (EFI System Partition) is shown as being

Code: 
sda2  458588160 468860927  10272768   4.9G EFI System

4.9 GB? An ESP should be between 100 MB and 550 MB, average 300 MB.
Click to expand...

On some of these trial-and-error since last week, I've noticed Linux Mint (I guess) created this EFI partition. It was indeed 500 MB. I know what happened; I must have been dizzy searching for so many different error warnings at boot (among them things related to EFI / Legacy) that I decided to manually create such a partition, when trying a new clean install of Elementary. Certainly it was my mistake when estimating the size of the partition.

EDIT: Instead of the Linux Mint installation having created this EFI partition before, it may well have been me following some thread suggestion
 
Last edited:
wizardfromoz said:
The "locked Nvram" message in the Pastebin output may be beyond my paygrade, so if anyone else can assist here, I would be grateful. :)

A Linux Mint user here, had success by resetting CMOS jumper leads, but I have not ever performed that exercise.

https://forums.linuxmint.com/viewtopic.php?t=327158
Click to expand...

Interesting. As I understand it after a couple searches, it would be about resetting BIOS settings, but I'm not sure It's more than a hardware thing - there's many suggestions on google about removing motherboard battery in order to reset BIOS.

In this other thread someone's suggestin the following command:

Code: 
modprobe nvram
dd if=/dev/zero of=/dev/nvram

I tried to do this and, at least in the session I'm in now (keeping in mind that its no reboot for over 24 hours, so I guess this must be affect performance)

Code: 
dd: writing in '/dev/nvram': There is no space available on the device
1+0 check-ins
0+1 check-out
114 bytes copied, 0.000751448 s, 152 kB/s

I saw comments saying it can be risky to edit nvram directly. Anyway I tried to see what state it is in, with

Code: 
"bash /proc/driver/nvram"

And comparing with the results from the user on that topic, it doesn't look good:

Code: 
/proc/driver/nvram: line 1: Checksum: command not found
/proc/driver/nvram: line 3: Floppy: command not found
/proc/driver/nvram: line 4: Floppy: command not found
/proc/driver/nvram: line 5: HD: command not found
/proc/driver/nvram: line 6: HD: command not found
/proc/driver/nvram: line 7: HD: command not found
/proc/driver/nvram: line 8: HD: command not found
/proc/driver/nvram: line 9: DOS: command not found
/proc/driver/nvram: line 10: syntax error next to unexpected token `('
/proc/driver/nvram: `Extended memory: 0 kB (configured), 0 kB (tested) '


EDIT: if hardware info can be useful here, I'm giving results for "inxi -Fzzz" also:

System: Host: dre-Inspiron-3437 Kernel: 5.4.0-66-generic x86_64
bits: 64
Console: tty 2 Distro: elementary OS 5.1.7 Hera
Machine: Device: portable System: Dell product: Inspiron 3437 serial: <filter>
Mobo: Dell model: 02JX3T v: A10 serial: <filter>
UEFI: Dell v: A10 date: 06/07/2016
Battery BAT0: charge: 21.9 Wh 100.0% condition: 21.9/66.6 Wh (33%)
CPU: Dual core Intel Core i5-4200U (-MT-MCP-)
cache: 3072 KB
clock speeds: max: 2600 MHz 1: 1123 MHz 2: 1173 MHz
3: 1359 MHz 4: 1308 MHz
Graphics: Card-1: Intel Haswell-ULT Integrated Graphics Controller
Card-2: NVIDIA GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M]
Display Server: X.Org 1.20.4
drivers: modesetting (unloaded: fbdev,vesa)
Resolution: [email protected]
OpenGL: renderer: Mesa DRI Intel HD Graphics 4400 (HSW GT2)
version: 4.5 Mesa 20.0.8
Audio: Card-1 Intel 8 Series HD Audio Controller
driver: snd_hda_intel
Card-2 Intel Haswell-ULT HD Audio Controller
driver: snd_hda_intel
Sound: ALSA v: k5.4.0-66-generic
Network: Card-1: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter
driver: ath9k
IF: wlp6s0 state: up mac: <filter>
Card-2: Realtek RTL810xE PCIE Fast Ethernet controller
driver: r8169
IF: enp7s0 state: down mac: <filter>
Card-3: Atheros
IF: null-if-id state: N/A speed: N/A duplex: N/A
mac: N/A
Drives: HDD Total Size: 1248.3GB (37.3% used)
ID-1: /dev/sdb model: WDC_WD10JPVX size: 1000.2GB
ID-2: /dev/sda model: Patriot_Burst size: 240.1GB
ID-3: USB /dev/sdc model: Flash_Disk size: 8.1GB
Partition: ID-1: / size: 215G used: 9.4G (5%)
fs: ext4 dev: /dev/sda1
ID-2: /home size: 916G used: 422G (49%)
fs: ext4 dev: /dev/sdb1
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: 54.0C mobo: N/A
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 273 Uptime: 1 day Memory: 3722.8/5850.3MB
Client: Shell (bash) inxi: 2.3.56
 
Last edited:
Well, guys, for some reason when shutting down the system after a few days of work, I was ready to reinstall it but nothing unusual happened: system initialization is ok (Elementary).

The downside is that I have no idea what went wrong, let alone what it solved. It was days of testing, reinstalling, being able to work only through live session.

I'd really wish it were like that when I was testing Mint, but that's enough. As they say here in Brazil - when the team is winning, it's better not to make changes :)
 
Rafaelys said:
Hello everyone,

This was after an attempt to configure the HDD on /home folder together with an SSD, but It's probably unrelated to that, as the problem persists after several attempts to reinstall both Elementary and Linux Mint, and using Ubiquity to allocate the /home folder on the HDD.

Problem is, after installing any OS via live USB (.iso have been checked and are ok), the system does not survive the reboot. A black screen, tty terminal shows up (if activated) but that's it.

- I've tried to change some GRUB parameters from there following other threads (such as "GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=off"), but won't boot still.

- From what I gathered it can be something related to API. Before the black screen after the reboot, I was able to quickly read something related to problems with API. Some threads suggest downgrading kernel version in this case. If it helps,

Code: 
$$ cat /proc/version

Linux version 5.4.0-66-generic (buildd@lgw01-amd64-016)
(gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)) #74~18.04.2-Ubuntu
SMP Fri Feb 5 11:17:31 UTC 2021

- Timeshift snapshot taken before the reboot is not overloading any of the drives. On the other hand, restoring via the live session not solved the problem either.

- Boot Repair Summary (still made in the USB live session) is saying these things, also points to "Locked Nvram detected".

- I'll copy the results for "dmesg --level=warn" also:

Code: 
[    0.113817] MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
[    0.113867]  #3
[    0.118041] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[    1.271730] platform eisa.0: EISA: Cannot allocate resource for mainboard
[    1.271731] platform eisa.0: Cannot allocate resource for EISA slot 1
[    1.271732] platform eisa.0: Cannot allocate resource for EISA slot 2
[    1.271733] platform eisa.0: Cannot allocate resource for EISA slot 3
[    1.271734] platform eisa.0: Cannot allocate resource for EISA slot 4
[    1.271735] platform eisa.0: Cannot allocate resource for EISA slot 5
[    1.271736] platform eisa.0: Cannot allocate resource for EISA slot 6
[    1.271737] platform eisa.0: Cannot allocate resource for EISA slot 7
[    1.271738] platform eisa.0: Cannot allocate resource for EISA slot 8
[    1.427440] wmi_bus wmi_bus-PNP0C14:01: WQBC data block query control method not found
[    1.491014] r8169 0000:07:00.0: can't disable ASPM; OS doesn't have ASPM control
[    1.550907] MXM: GUID detected in BIOS
[    1.551129] ACPI Warning: \_SB.PCI0.RP05.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20190816/nsarguments-66)
[    1.666498] [Firmware Bug]: ACPI(PEGP) defines _DOD but not _DOS
[    1.669833] No Local Variables are initialized for Method [_BCL]
[    1.669834] No Arguments are initialized for method [_BCL]
[    4.383954] systemd[1]: /lib/systemd/system/systemd-udevd.service:31: Unknown lvalue 'RestrictSUIDSGID' in section 'Service'
[    5.123209] dell-smbios A80593CE-A997-11DA-B012-B622A1EF5492: WMI SMBIOS userspace interface not supported(0), try upgrading to a newer BIOS
[  435.251930] kauditd_printk_skb: 9 callbacks suppressed
[ 1669.658233] FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

[/QUOTE]
Click to expand...

Rafaelys said:
Hello everyone,

This was after an attempt to configure the HDD on /home folder together with an SSD, but It's probably unrelated to that, as the problem persists after several attempts to reinstall both Elementary and Linux Mint, and using Ubiquity to allocate the /home folder on the HDD.

Problem is, after installing any OS via live USB (.iso have been checked and are ok), the system does not survive the reboot. A black screen, tty terminal shows up (if activated) but that's it.

- I've tried to change some GRUB parameters from there following other threads (such as "GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=off"), but won't boot still.

- From what I gathered it can be something related to API. Before the black screen after the reboot, I was able to quickly read something related to problems with API. Some threads suggest downgrading kernel version in this case. If it helps,

Code: 
$$ cat /proc/version

Linux version 5.4.0-66-generic (buildd@lgw01-amd64-016)
(gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)) #74~18.04.2-Ubuntu
SMP Fri Feb 5 11:17:31 UTC 2021

- Timeshift snapshot taken before the reboot is not overloading any of the drives. On the other hand, restoring via the live session not solved the problem either.

- Boot Repair Summary (still made in the USB live session) is saying these things, also points to "Locked Nvram detected".

- I'll copy the results for "dmesg --level=warn" also:

Code: 
[    0.113817] MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
[    0.113867]  #3
[    0.118041] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[    1.271730] platform eisa.0: EISA: Cannot allocate resource for mainboard
[    1.271731] platform eisa.0: Cannot allocate resource for EISA slot 1
[    1.271732] platform eisa.0: Cannot allocate resource for EISA slot 2
[    1.271733] platform eisa.0: Cannot allocate resource for EISA slot 3
[    1.271734] platform eisa.0: Cannot allocate resource for EISA slot 4
[    1.271735] platform eisa.0: Cannot allocate resource for EISA slot 5
[    1.271736] platform eisa.0: Cannot allocate resource for EISA slot 6
[    1.271737] platform eisa.0: Cannot allocate resource for EISA slot 7
[    1.271738] platform eisa.0: Cannot allocate resource for EISA slot 8
[    1.427440] wmi_bus wmi_bus-PNP0C14:01: WQBC data block query control method not found
[    1.491014] r8169 0000:07:00.0: can't disable ASPM; OS doesn't have ASPM control
[    1.550907] MXM: GUID detected in BIOS
[    1.551129] ACPI Warning: \_SB.PCI0.RP05.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20190816/nsarguments-66)
[    1.666498] [Firmware Bug]: ACPI(PEGP) defines _DOD but not _DOS
[    1.669833] No Local Variables are initialized for Method [_BCL]
[    1.669834] No Arguments are initialized for method [_BCL]
[    4.383954] systemd[1]: /lib/systemd/system/systemd-udevd.service:31: Unknown lvalue 'RestrictSUIDSGID' in section 'Service'
[    5.123209] dell-smbios A80593CE-A997-11DA-B012-B622A1EF5492: WMI SMBIOS userspace interface not supported(0), try upgrading to a newer BIOS
[  435.251930] kauditd_printk_skb: 9 callbacks suppressed
[ 1669.658233] FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 2471.900434] printk: systemd: 51 output lines suppressed due to ratelimiting
[ 4147.698636] kauditd_printk_skb: 12 callbacks suppressed
[ 9171.352682] kauditd_printk_skb: 1 callbacks suppressed
[15140.862886] IRQ 47: no longer affine to CPU1
[15140.864667] IRQ 44: no longer affine to CPU2
[15140.866577] IRQ 18: no longer affine to CPU3
[15140.866586] IRQ 23: no longer affine to CPU3
[15141.610592] done.
[15145.367256] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0).
[15145.367259] atkbd serio0: Use 'setkeycodes e00d <keycode>' to make it known.
Click to expand...
I deleted my main partition, recreated a new one, installed Mint 21 and the laptop boots normally.

Before doing the partition work, every install would fail at bootloader write.
 
You must log in or register to reply here.

Staff online

Members online

Total: 382 (members: 6, guests: 376)

Latest posts

Top