UEFI boot loader does not show up in firmware menu, System dont boot anymore

On my system i disable CSM completely to go UEFI only as i’ve had some issues with it in the past due to buggy implementation by the vendor.

CSM, also known as Compatibility Support Module, is a component of the UEFI firmware, which provides legacy BIOS compatibility by emulating a BIOS environment, allowing legacy operating systems that do not support UEFI to still be used.

2 Likes

It should be disabled by default. In any case, I haven’t changed anything, I’ll have a look at it later. thank you

1 Like

I have just checked and deactivated CSM. It immediately started the UEFI boot menu in which the kernel can be selected.

Maybe it was because CSM was enabled.
I will continue to monitor it

I have just started two tests with smartctl and nvme-cli. I cannot find any errors.

sudo smartctl -t long -a /dev/nvme0n1

smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.1.66-1-lts] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       Samsung SSD 980 PRO 250GB
Serial Number:                      S5GZNJ0RC12478R
Firmware Version:                   4B2QGXA7
PCI Vendor/Subsystem ID:            0x144d
IEEE OUI Identifier:                0x002538
Total NVM Capacity:                 250.059.350.016 [250 GB]
Unallocated NVM Capacity:           0
Controller ID:                      6
NVMe Version:                       1.3
Number of Namespaces:               1
Namespace 1 Size/Capacity:          250.059.350.016 [250 GB]
Namespace 1 Utilization:            64.917.123.072 [64,9 GB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            002538 bc11413eba
Local Time is:                      Mon Dec 11 17:38:25 2023 CET
Firmware Updates (0x16):            3 Slots, no Reset required
Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
Optional NVM Commands (0x0057):     Comp Wr_Unc DS_Mngmt Sav/Sel_Feat Timestmp
Log Page Attributes (0x0f):         S/H_per_NS Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg
Maximum Data Transfer Size:         128 Pages
Warning  Comp. Temp. Threshold:     82 Celsius
Critical Comp. Temp. Threshold:     85 Celsius

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +     8.49W       -        -    0  0  0  0        0       0
 1 +     4.48W       -        -    1  1  1  1        0     200
 2 +     3.18W       -        -    2  2  2  2        0    1000
 3 -   0.0400W       -        -    3  3  3  3     2000    1200
 4 -   0.0050W       -        -    4  4  4  4      500    9500

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
 0 +     512       0         0

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        33 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    5%
Data Units Read:                    7.771.871 [3,97 TB]
Data Units Written:                 40.846.584 [20,9 TB]
Host Read Commands:                 108.250.433
Host Write Commands:                858.819.343
Controller Busy Time:               1.188
Power Cycles:                       786
Power On Hours:                     298
Unsafe Shutdowns:                   21
Media and Data Integrity Errors:    0
Error Information Log Entries:      0
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Temperature Sensor 1:               33 Celsius
Temperature Sensor 2:               39 Celsius

Error Information (NVMe Log 0x01, 16 of 64 entries)
No Errors Logged

Read Self-test Log failed: Invalid Field in Command (0x002)

sudo watch -n 1 nvme smart-log /dev/nvme0n1

Smart Log for NVME device:nvme0n1 namespace-id:ffffffff
critical_warning                        : 0
temperature                             : 33 °C (306 K)
available_spare                         : 100%
available_spare_threshold               : 10%
percentage_used                         : 5%
endurance group critical warning summary: 0
Data Units Read                         : 7771645 (3.98 TB)
Data Units Written                      : 40846577 (20.91 TB)
host_read_commands                      : 108246789
host_write_commands                     : 858818894
controller_busy_time                    : 1188
power_cycles                            : 786
power_on_hours                          : 298
unsafe_shutdowns                        : 21
media_errors                            : 0
num_err_log_entries                     : 0
Warning Temperature Time                : 0
Critical Composite Temperature Time     : 0
Temperature Sensor 1           : 33 °C (306 K)
Temperature Sensor 2           : 39 °C (312 K)
Thermal Management T1 Trans Count       : 0
Thermal Management T2 Trans Count       : 0
Thermal Management T1 Total Time        : 0
Thermal Management T2 Total Time        : 0
1 Like

@dalto @fred666 @ainz

I have now booted several times and also rebooted several times. Everything works as expected.

It looks like the activated CSM was the reason for that issue.

I will mark this topic as solved. If further errors occur I will start a new topic.

A thousand thanks to all of you for your ideas, help and time

2 Likes

@swh glad you found the issue! Didn’t think of csm

Stil this confirms my thoughts about buggy bios as csm is apparently poorly implanted by Gigabyte
But if you only use UEFI then disabling csm eliminates this problem

1 Like

I simply don’t have the knowledge to go that deep. That’s why I’m very happy to meet such helpful people here in the forum. Someone always has an idea to find a solution.

Learning with you is a great pleasure!

2 Likes

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.