P9 Simple Linux not shutting down on desktop

[gosts 87]

Here is:

[Δημητριος]

sorry from here

[gosts 87]

I understood. It's just not clear why the 5.7 kernel is not in the repository list.

[Δημητριος]

with value   help of ghost 87 , we found this lines on dmesg,

Код: [Выделить]

[    9.672282] EDAC amd64: DRAM ECC disabled.
[    9.672293] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
                Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
                (Note that use of the override may cause unknown side effects.)
[    9.688236] EDAC amd64: DRAM ECC disabled.
[    9.688249] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
                Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
                (Note that use of the override may cause unknown side effects.)
[    9.709050] EDAC amd64: DRAM ECC disabled.
[    9.709065] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
                Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
                (Note that use of the override may cause unknown side effects.)
[    9.709641] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:10.0/0000:02:00.1/sound/card1/input12
[    9.709865] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:10.0/0000:02:00.1/sound/card1/input13
[    9.710043] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:10.0/0000:02:00.1/sound/card1/input14
[    9.710220] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:10.0/0000:02:00.1/sound/card1/input15
[    9.729242] EDAC amd64: DRAM ECC disabled.
[    9.729256] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
                Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
                (Note that use of the override may cause unknown side effects.)
[    9.744053] EDAC amd64: DRAM ECC disabled.
[    9.744063] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
                Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
                (Note that use of the override may cause unknown side effects.)
[    9.759183] EDAC amd64: DRAM ECC disabled.
[    9.759196] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
                Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
                (Note that use of the override may cause unknown side effects.)
[    9.779059] EDAC amd64: DRAM ECC disabled.
[    9.779069] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
                Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
                (Note that use of the override may cause unknown side effects.)
[    9.811160] EDAC amd64: DRAM ECC disabled.
[    9.811172] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
                Either enable ECC checking or force module loading by setting 'ecc_enable_override'.


Код: [Выделить]

[ 2.539741] nvidia-nvlink: Nvlink Core is being initialized, major device number 247

[ 2.539756] NVRM: The NVIDIA probe routine was not called for 1 device(s).

[ 2.539757] NVRM: This can occur when a driver such as:

NVRM: nouveau, rivafb, nvidiafb or rivatv

NVRM: was loaded and obtained ownership of the NVIDIA device(s).

[ 2.539757] NVRM: Try unloading the conflicting kernel module (and/or

NVRM: reconfigure your kernel without the conflicting

NVRM: driver(s)), then try loading the NVIDIA kernel module

NVRM: again.

[ 2.539758] NVRM: No NVIDIA graphics adapter probed!

[ 2.539759] nvidia-nvlink: Unregistered the Nvlink Core, major device number 247

[ 2.543407] hid-generic 0003:06A3:0728.0002: input,hiddev0,hidraw2: USB HID v1.11 Device [Chicony Saitek Cyborg Keyboard] on usb-0000:00:04.0-1/input1

[ 2.595408] hid-generic 0003:13BA:0018.0004: input,hidraw3: USB HID v1.10 Mouse [Barcode Reader ] on usb-0000:00:02.0-1/input1

[ 2.836988] random: crng init done



[asy]

dmesg.txt (63.71 кБ - загружено 3 раз.)

Код: [Выделить]

[    1.091156] PM: Checking hibernation image partition /dev/disk/by-uuid/d9df8c72-8c3d-4fd8-aaa3-27c9b4887cf6
[    1.128225] PM: Hibernation image not present or could not be loaded.

Can you put output of "blkid" here? swap partition must have UUID d9df8c72-8c3d-4fd8-aaa3-27c9b4887cf6 and must have size equal or more then RAM. And check "cat /proc/cmdline" for resume option.

[Δημητριος]

dmesg.txt (63.71 кБ - загружено 3 раз.)

Код: [Выделить]

[    1.091156] PM: Checking hibernation image partition /dev/disk/by-uuid/d9df8c72-8c3d-4fd8-aaa3-27c9b4887cf6
[    1.128225] PM: Hibernation image not present or could not be loaded.

Can you put output of "blkid" here? swap partition must have UUID d9df8c72-8c3d-4fd8-aaa3-27c9b4887cf6 and must have size equal or more then RAM. And check "cat /proc/cmdline" for resume option.

cat /proc/cmdline

Код: [Выделить]

BOOT_IMAGE=/boot/vmlinuz root=UUID=f81b8c12-c981-4103-b3c1-6c99f25872bb ro quiet resume=/dev/disk/by-uuid/d9df8c72-8c3d-4fd8-aaa3-27c9b4887cf6 panic=30 splash

[asy]

"resume" option corresponds dmesg. But is which UUID of the swap partition really? run "blkid".

[Δημητριος]

resume" option corresponds dmesg. But is which UUID of the swap partition really ?

perhaps this is reason to freeze some time my pc???

Код: [Выделить]

~]# blkid
/dev/sda1: LABEL="M-NM-^TM-NM-5M-OM-^CM-NM-<M-NM-5M-OM-^EM-NM-<M-NM--M-NM-=M-NM-? M-NM-1M-OM-^@M-OM-^L M-OM-^DM-NM-? M-OM-^CM-OM-^MM-OM-^CM-OM-^DM-NM-7M-NM-<M-NM-1" UUID="0CF898A5F8988E98" TYPE="ntfs" PARTUUID="e21956b7-01"
/dev/sda2: LABEL="Windows_7 OS" UUID="60BC9B9EBC9B6CF2" TYPE="ntfs" PARTUUID="e21956b7-02"
/dev/sda5: UUID="d9df8c72-8c3d-4fd8-aaa3-27c9b4887cf6" TYPE="swap" PARTUUID="e21956b7-05"
/dev/sda6: UUID="f81b8c12-c981-4103-b3c1-6c99f25872bb" TYPE="ext4" PARTUUID="e21956b7-06"
/dev/sda7: UUID="79d8acc0-ebc6-491b-9d01-ee0b7642a939" TYPE="ext4" PARTUUID="e21956b7-07"


[asy]

Код: [Выделить]

blkid:   /dev/sda5: UUID="d9df8c72-8c3d-4fd8-aaa3-27c9b4887cf6" TYPE="swap" PARTUUID="e21956b7-05"
cmdline: resume=/dev/disk/by-uuid/d9df8c72-8c3d-4fd8-aaa3-27c9b4887cf6
dmesg:   PM: Checking hibernation image partition /dev/disk/by-uuid/d9df8c72-8c3d-4fd8-aaa3-27c9b4887cf6All the same, ok. Then another question: which output of "free" utility?

[Δημητριος]

Then another question: which output of "free" utility?

please what do you mean

[Speccyfighter]

I understood. It's just not clear why the 5.7 kernel is not in the repository list.

Оно есть, в p9:

Код: [Выделить]

# aptitude search ~nkernel-image-un-def
v   kernel-image-un-def                                                -                                                                             
p   kernel-image-un-def#1:5.7.19-alt1:p9+256869.100.1.1@1598980297     - The Linux kernel (the core of the Linux operating system)                   

Но update-kernel увидит и установит ядро с другим флавором, только при явном указании флавора через опция/параметр. Без указания опция/флавор, update-kernel проверяет наличие свежей версии используемого ядра, только его флавора.
Проще говоря, если система запущена с ядром std-def, то update-kernel без указания опция/флавор, будет проверять наличие свежей версии только для std-def. И это ядро 5.4.*. А ядро 5.7, это un-def флавор.

[Speccyfighter]

...

Код: [Выделить]

[    9.672282] EDAC amd64: DRAM ECC disabled.
[    9.672293] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
                Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
                (Note that use of the override may cause unknown side effects.)
...
...

- What is the full name of the motherboard model?
- Do you have DRAM ECC memory modules installed?
- To search and read what DRAM ECC and non-ECC are, see the System memory section in the Mainboard User guide for the type of required memory and BIOS.

For example, the H61M-PRO motherboard user manual says that:
1.4.2 Memory configurations
You may install 1GB, 2GB, 4GB, and 8GB unbuffered non-ECC DDR3 DIMMs into the DIMM sockets.

That is, the H61M-PRO motherboard requires unbuffered memory modules without error correction.

[Δημητριος]

...

Код: [Выделить]

[    9.672282] EDAC amd64: DRAM ECC disabled.
[    9.672293] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
                Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
                (Note that use of the override may cause unknown side effects.)
...
...

- What is the full name of the motherboard model?
- Do you have DRAM ECC memory modules installed?
- To search and read what DRAM ECC and non-ECC are, see the System memory section in the Mainboard User guide for the type of required memory and BIOS.

For example, the H61M-PRO motherboard user manual says that:
1.4.2 Memory configurations
You may install 1GB, 2GB, 4GB, and 8GB unbuffered non-ECC DDR3 DIMMs into the DIMM sockets.

That is, the H61M-PRO motherboard requires unbuffered memory modules without error correction.

my mainboard is this  and i thing not support ECC

however neither do the memories support ECC gskill
 and I think the (driver=водители машины)  mistakenly recognizes the ECC
but on bios acpi there is a possibility like check ready bit logically after suspension , maybe this is the problem  with the wrong recognition ECC from driver , because the driver sees it as ecc, an opinion

[Speccyfighter]

and I think the (driver=водители машины)  mistakenly recognizes the ECC
but on bios acpi there is a possibility like check ready bit   , maybe this is the problem with misidentification ECC from driver , because the driver sees it as ecc, an opinion

Yes, I looked at the User manual M3N78D FX and the F3-2400C11D-8GAB specification. This is a gross error of the Linux kernel - an incorrect definition of the type of RAM, it is not ECC. And your M3N78D FX motherboard does not support DRAM ECC.

This error will not be fixed by altlinux and will probably have to go to bugzilla.kernel.org.

Да, посмотрел User manual M3N78D FX и спецификацию F3-2400C11D-8GAB. Это грубая ошибка ядра Линукс, - неверное определение типа оперативной памяти, она не ECC. И ваша системная плата M3N78D FX не поддерживает DRAM ECC.

Такую ошибку altlinux не исправят и вероятно придётся идти на bugzilla.kernel.org.

[Δημητριος]

and I think the (driver=водители машины)  mistakenly recognizes the ECC
but on bios acpi there is a possibility like check ready bit   , maybe this is the problem with misidentification ECC from driver , because the driver sees it as ecc, an opinion

Yes, I looked at the User manual M3N78D FX and the F3-2400C11D-8GAB specification. This is a gross error of the Linux kernel - an incorrect definition of the type of RAM, it is not ECC. And your M3N78D FX motherboard does not support DRAM ECC.

This error will not be fixed by altlinux and will probably have to go to bugzilla.kernel.org.

Да, посмотрел User manual M3N78D FX и спецификацию F3-2400C11D-8GAB. Это грубая ошибка ядра Линукс, - неверное определение типа оперативной памяти, она не ECC. И ваша системная плата M3N78D FX не поддерживает DRAM ECC.

Такую ошибку altlinux не исправят и вероятно придётся идти на bugzilla.kernel.org.

Я думаю, что это драйвер машины для чипсета amd 9 серии-мнение
i thing this is a driver(=drivers machine=водители автомобилей)  for amd chipset 9 series -an opinion

PS:I hope the bugs get fixed soon 🥺