EDAC amd64: Error: F0 not found, device 0x1650 (broken BIOS?)

HNAG

Cadet
Joined
Dec 12, 2020
Messages
2

morganL

Captain Morgan
Administrator
Moderator
iXsystems
Joined
Mar 10, 2018
Messages
2,694
It sounds like an incompatibility between Debian 11 and the BIOS on that motherboard.... can you confirm the BIOS.

It would be interesting to see if a vanilla Debian 11 install had the same issues. Apart from the message... what happens?
 

HNAG

Cadet
Joined
Dec 12, 2020
Messages
2
Hello,

I have version 3.11.

I go to the selection of the hard drive. But after selecting the Samsung SSD 850 EVO M.2 250GB, the installation tells me no disk selected and it returns me to the shell.

In attached the dmesg.

I have successfully installed debian 10.7.0

$ uname -a
Linux debian 4.19.0-13-amd64 # 1 SMP Debian 4.19.160-2 (2020-11-28) x86_64 GNU / Linux
$ cat /etc/debian_version
10.7

Out of curiosity I also install:
https://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-netinst.iso
with success.

Have a good day
H.
 

Attachments

  • dmesg.txt
    86.6 KB · Views: 297
  • dmesg.txt
    86.6 KB · Views: 561

morganL

Captain Morgan
Administrator
Moderator
iXsystems
Joined
Mar 10, 2018
Messages
2,694
If no-one responds, to this, please report it as a bug.
 

avatar4d

Cadet
Joined
Mar 18, 2021
Messages
1
I came across this post because I am in the process of migrating from FreeBSD to Debian on a new NAS build. I am running Debian 10.8 and the same mobo as the OP. I confirm that I am receiving the same message on startup.

Everything seems to be running fine though as far as I can tell. System has been fast and stable. I imported my zpool and can access it without any issue so far. That said, it was only installed and running for a few hours starting today so may be too soon to tell, but the to answer the question of "what happens?" seems to be not much at this point.
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,700
I have successfully installed debian 10.7.0
As originally requested, a vanilla install of debian 11 (not 10) is required to eliminate the issue being one from SCALE and not debian bullseye (and the new linux kernel it uses, which is different from the one used in debian 10 buster).

The version 5 kernel may be a factor here and you're only testing version 4 with debian 10.
 
Top