Pc si avvia ma da errore di caricamento kernel

Questioni legate al Kernel Linux: configurazione, installazione, ottimizzazione, patch
Rispondi
Liviovarriale
Newbie
Newbie
Messaggi: 7
Iscritto il: 27/09/2021, 6:26

Pc si avvia ma da errore di caricamento kernel

Messaggio da Liviovarriale »

Salve, dopo aver aggiornato da buster a bullseye mi da al boot l’errore allegato in foto.

Il pc funziona e il dmesg non da errori , cosa può essere?

Mi hanno consigliato di eseguire il caricamento di initrd con questo comando

update-initramfs -k all -u

E noto che mi genera due kernel

sudo update-initramfs -k all -u
update-initramfs: Generating /boot/initrd.img-5.10.0-8-amd64
update-initramfs: Generating /boot/initrd.img-4.19.0-17-amd64

Grazie per quanto farete
Allegati
Foto boot
Foto boot
Avatar utente
azioga
Hero Member
Hero Member
Messaggi: 1329
Iscritto il: 03/09/2018, 7:53

Re: Pc si avvia ma da errore di caricamento kernel

Messaggio da azioga »

Guarda qui:
viewtopic.php?t=50640

Probabilmente i motivi sono diversi, ma l'indagine fatta ti può aiutare nella ricerca del modulo/i che presentano problemi.

Prova anche a veder nel journal con un:

Codice: Seleziona tutto

#  journalctl | grep systemd-modules-load
il -k all esegue update-initramfs per tutti i kernel installati che hanno già un initramfs.
Nel tuo caso è giusto: il kernel di buster e quello di bullseye.
Liviovarriale
Newbie
Newbie
Messaggi: 7
Iscritto il: 27/09/2021, 6:26

Re: Pc si avvia ma da errore di caricamento kernel

Messaggio da Liviovarriale »

udo journalctl | grep systemd-modules-load
ago 22 09:49:43 OrcaWhale systemd-modules-load[508]: Inserted module 'lp'
ago 22 09:49:43 OrcaWhale systemd-modules-load[508]: Inserted module 'ppdev'
ago 22 09:49:43 OrcaWhale systemd-modules-load[508]: Inserted module 'parport_pc'
ago 22 09:49:44 OrcaWhale systemd-modules-load[508]: Inserted module 'firewire_sbp2'
ago 22 09:49:49 OrcaWhale systemd-modules-load[508]: Inserted module 'nvidia_drm'
ago 22 20:53:14 OrcaWhale systemd-modules-load[468]: Inserted module 'lp'
ago 22 20:53:14 OrcaWhale systemd-modules-load[468]: Inserted module 'ppdev'
ago 22 20:53:14 OrcaWhale systemd-modules-load[468]: Inserted module 'parport_pc'
ago 22 20:53:14 OrcaWhale systemd-modules-load[468]: Inserted module 'firewire_sbp2'
ago 22 20:53:15 OrcaWhale systemd-modules-load[468]: Inserted module 'nvidia_drm'
ago 22 22:54:33 OrcaWhale systemd[1]: systemd-modules-load.service: Succeeded.
set 19 16:58:24 OrcaWhale systemd-modules-load[466]: Inserted module 'lp'
set 19 16:58:25 OrcaWhale systemd-modules-load[466]: Inserted module 'ppdev'
set 19 16:58:25 OrcaWhale systemd-modules-load[466]: Inserted module 'parport_pc'
set 19 16:58:25 OrcaWhale systemd-modules-load[466]: Inserted module 'firewire_sbp2'
set 19 16:58:25 OrcaWhale systemd-modules-load[466]: Inserted module 'coretemp'
set 19 16:58:25 OrcaWhale systemd-modules-load[466]: Inserted module 'i5500_temp'
set 19 16:58:25 OrcaWhale systemd-modules-load[466]: Failed to insert module 'w83627ehf': Device or resource busy
set 19 16:58:26 OrcaWhale systemd-modules-load[466]: Inserted module 'nvidia_drm'
set 19 16:58:26 OrcaWhale systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
set 19 16:58:26 OrcaWhale systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
set 19 16:58:32 OrcaWhale systemd-modules-load[757]: Failed to insert module 'w83627ehf': Device or resource busy
set 19 16:58:32 OrcaWhale systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
set 19 16:58:32 OrcaWhale systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
set 19 16:58:32 OrcaWhale systemd-modules-load[766]: Failed to insert module 'w83627ehf': Device or resource busy
set 19 16:58:32 OrcaWhale systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
set 19 16:58:32 OrcaWhale systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
set 19 17:07:34 OrcaWhale systemd-modules-load[468]: Inserted module 'lp'
set 19 17:07:34 OrcaWhale systemd-modules-load[468]: Inserted module 'ppdev'
set 19 17:07:35 OrcaWhale systemd-modules-load[468]: Inserted module 'parport_pc'
set 19 17:07:35 OrcaWhale systemd-modules-load[468]: Inserted module 'firewire_sbp2'
set 19 17:07:35 OrcaWhale systemd-modules-load[468]: Inserted module 'coretemp'
set 19 17:07:35 OrcaWhale systemd-modules-load[468]: Inserted module 'i5500_temp'
set 19 17:07:35 OrcaWhale systemd-modules-load[468]: Failed to insert module 'w83627ehf': Device or resource busy
set 19 17:07:36 OrcaWhale systemd-modules-load[468]: Inserted module 'nvidia_drm'
set 19 17:07:36 OrcaWhale systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
set 19 17:07:36 OrcaWhale systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
set 19 17:07:38 OrcaWhale systemd-modules-load[780]: Failed to insert module 'w83627ehf': Device or resource busy
set 19 17:07:38 OrcaWhale systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
set 19 17:07:38 OrcaWhale systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
set 19 19:00:49 OrcaWhale systemd[1]: systemd-modules-load.service: Succeeded.
set 23 19:53:33 OrcaWhale systemd-modules-load[480]: Inserted module 'lp'
set 23 19:53:33 OrcaWhale systemd-modules-load[480]: Inserted module 'ppdev'
set 23 19:53:33 OrcaWhale systemd-modules-load[480]: Inserted module 'parport_pc'
set 23 19:53:34 OrcaWhale systemd-modules-load[480]: Inserted module 'firewire_sbp2'
set 23 19:53:34 OrcaWhale systemd-modules-load[480]: Inserted module 'coretemp'
set 23 19:53:34 OrcaWhale systemd-modules-load[480]: Inserted module 'i5500_temp'
set 23 19:53:34 OrcaWhale systemd-modules-load[480]: Failed to insert module 'w83627ehf': Device or resource busy
set 23 19:53:35 OrcaWhale systemd-modules-load[480]: Inserted module 'nvidia_drm'
set 23 19:53:35 OrcaWhale systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
set 23 19:53:35 OrcaWhale systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
set 23 19:53:39 OrcaWhale systemd-modules-load[753]: Failed to insert module 'w83627ehf': Device or resource busy
set 23 19:53:39 OrcaWhale systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
set 23 19:53:39 OrcaWhale systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
set 26 18:18:39 OrcaWhale systemd-modules-load[463]: Inserted module 'lp'
set 26 18:18:40 OrcaWhale systemd-modules-load[463]: Inserted module 'ppdev'
set 26 18:18:40 OrcaWhale systemd-modules-load[463]: Inserted module 'parport_pc'
set 26 18:18:40 OrcaWhale systemd-modules-load[463]: Inserted module 'firewire_sbp2'
set 26 18:18:40 OrcaWhale systemd-modules-load[463]: Inserted module 'coretemp'
set 26 18:18:40 OrcaWhale systemd-modules-load[463]: Inserted module 'i5500_temp'
set 26 18:18:40 OrcaWhale systemd-modules-load[463]: Failed to insert module 'w83627ehf': Device or resource busy
set 26 18:18:42 OrcaWhale systemd-modules-load[463]: Inserted module 'nvidia_drm'
set 26 18:18:42 OrcaWhale systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
set 26 18:18:42 OrcaWhale systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
set 26 18:18:47 OrcaWhale systemd-modules-load[737]: Failed to insert module 'w83627ehf': Device or resource busy
set 26 18:18:47 OrcaWhale systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
set 26 18:18:47 OrcaWhale systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
set 26 18:18:47 OrcaWhale systemd-modules-load[741]: Failed to insert module 'w83627ehf': Device or resource busy
set 26 18:18:47 OrcaWhale systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
set 26 18:18:47 OrcaWhale systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
Avatar utente
azioga
Hero Member
Hero Member
Messaggi: 1329
Iscritto il: 03/09/2018, 7:53

Re: Pc si avvia ma da errore di caricamento kernel

Messaggio da azioga »

Codice: Seleziona tutto

set 26 18:18:47 OrcaWhale systemd-modules-load[741]: Failed to insert module 'w83627ehf': Device or resource busy
set 26 18:18:47 OrcaWhale systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
il problema sembra questo, fai ricerche in merito.
Liviovarriale
Newbie
Newbie
Messaggi: 7
Iscritto il: 27/09/2021, 6:26

Re: Pc si avvia ma da errore di caricamento kernel

Messaggio da Liviovarriale »

PEr il primo ho lanciato sensor detect, secondo te devo eseguire questo comando com consiglia alla fine? /etc/init.d/kmod start'

sudo sensors-detect
# sensors-detect version 3.6.0
# Board: ASUSTeK Computer INC. Rampage III Extreme
# Kernel: 5.10.0-8-amd64 x86_64
# Processor: Intel(R) Core(TM) i7 CPU 950 @ 3.07GHz (6/26/5)

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): yes
Module cpuid loaded successfully.
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD Family 10h thermal sensors... No
AMD Family 11h thermal sensors... No
AMD Family 12h and 14h thermal sensors... No
AMD Family 15h thermal sensors... No
AMD Family 16h thermal sensors... No
AMD Family 17h thermal sensors... No
AMD Family 15h power sensors... No
AMD Family 16h power sensors... No
Hygon Family 18h thermal sensors... No
Intel digital thermal sensor... Success!
(driver `coretemp')
Intel AMB FB-DIMM thermal sensor... No
Intel 5500/5520/X58 thermal sensor... Success!
(driver `i5500_temp')
VIA C7 thermal sensor... No
VIA Nano thermal sensor... No

Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): yes
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... Yes
Found `Winbond W83667HG Super IO Sensors' Success!
(address 0x290, driver `w83627ehf')
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... No

Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no): yes
Probing for `IPMI BMC KCS' at 0xca0... No
Probing for `IPMI BMC SMIC' at 0xca8... No

Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (yes/NO): yes
Probing for `National Semiconductor LM78' at 0x290... No
Probing for `National Semiconductor LM79' at 0x290... No
Probing for `Winbond W83781D' at 0x290... No
Probing for `Winbond W83782D' at 0x290... No

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): yes
Using driver `i2c-i801' for device 0000:00:1f.3: Intel ICH10
Module i2c-dev loaded successfully.

Next adapter: NVIDIA i2c adapter 4 at 3:00.0 (i2c-0)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: NVIDIA i2c adapter 6 at 3:00.0 (i2c-1)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: NVIDIA i2c adapter 7 at 3:00.0 (i2c-2)
Do you want to scan it? (yes/NO/selectively): y


Now follows a summary of the probes I have just done.
Just press ENTER to continue:

Driver `i5500_temp':
* Chip `Intel 5500/5520/X58 thermal sensor' (confidence: 5)

Driver `coretemp':
* Chip `Intel digital thermal sensor' (confidence: 9)

Driver `w83627ehf':
* ISA bus, address 0x290
Chip `Winbond W83667HG Super IO Sensors' (confidence: 9)

To load everything that is needed, add this to /etc/modules:
#----cut here----
# Chip drivers
coretemp
i5500_temp
w83627ehf
#----cut here----
If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones!

Do you want to add these lines automatically to /etc/modules? (yes/NO)yes
Successful!

Monitoring programs won't work until the needed modules are
loaded. You may want to run '/etc/init.d/kmod start'
to load them.

Unloading i2c-dev... OK
Unloading cpuid... OK
Avatar utente
azioga
Hero Member
Hero Member
Messaggi: 1329
Iscritto il: 03/09/2018, 7:53

Re: Pc si avvia ma da errore di caricamento kernel

Messaggio da azioga »

Liviovarriale ha scritto: 27/09/2021, 11:31 PEr il primo ho lanciato sensor detect, secondo te devo eseguire questo comando com consiglia alla fine? /etc/init.d/kmod start'
non direi perchè già prova a caricarli systemd:

Codice: Seleziona tutto

set 19 16:58:25 OrcaWhale systemd-modules-load[466]: Inserted module 'coretemp'
set 19 16:58:25 OrcaWhale systemd-modules-load[466]: Inserted module 'i5500_temp'
ma fallisce col terzo:

Codice: Seleziona tutto

set 19 16:58:25 OrcaWhale systemd-modules-load[466]: Failed to insert module 'w83627ehf': Device or resource busy
cosa dice se provi a caricarlo manualmente quel modulo con:

Codice: Seleziona tutto

# modprobe w83627ehf
Spesso questi moduli dei sensori occupano aree di memoria in conflitto col sistema.
Liviovarriale
Newbie
Newbie
Messaggi: 7
Iscritto il: 27/09/2021, 6:26

Re: Pc si avvia ma da errore di caricamento kernel

Messaggio da Liviovarriale »

modprobe: ERROR: could not insert 'w83627ehf': Device or resource busy
Liviovarriale
Newbie
Newbie
Messaggi: 7
Iscritto il: 27/09/2021, 6:26

Re: Pc si avvia ma da errore di caricamento kernel

Messaggio da Liviovarriale »

Questo è il comando sensors, mi hanno suggerito di blacklistare il modulo, che dici?


sensors
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +54.0°C (high = +80.0°C, crit = +100.0°C)
Core 1: +54.0°C (high = +80.0°C, crit = +100.0°C)
Core 2: +54.0°C (high = +80.0°C, crit = +100.0°C)
Core 3: +51.0°C (high = +80.0°C, crit = +100.0°C)atk0110-acpi-0
Adapter: ACPI interface
3.3V Voltage: 3.33 V (min = +2.97 V, max = +3.63 V)
5V Voltage: 5.00 V (min = +4.50 V, max = +5.50 V)
12V Voltage: 12.14 V (min = +10.20 V, max = +13.80 V)
DRAM Bus Voltage: 1.65 V (min = +1.40 V, max = +1.90 V)
CPU Voltage: 926.00 mV (min = +0.80 V, max = +1.80 V)
ICH Voltage: 1.11 V (min = +0.90 V, max = +1.35 V)
ICH PCIE Voltage: 1.51 V (min = +1.20 V, max = +1.80 V)
CPU PLL Voltage: 1.81 V (min = +1.50 V, max = +2.00 V)
IOH PCIE Voltage: 1.81 V (min = +1.20 V, max = +1.80 V)
IOH Voltage: 1.16 V (min = +0.90 V, max = +1.35 V)
QPI/DRAM Core Voltage: 1.37 V (min = +0.80 V, max = +1.50 V)
CPU FAN Speed: 2680 RPM (min = 600 RPM, max = 7200 RPM)
CHA_FAN1 FAN Speed: 0 RPM (min = 600 RPM, max = 7200 RPM)
CHA_FAN2 FAN Speed: 0 RPM (min = 600 RPM, max = 7200 RPM)
CHA_FAN3 FAN Speed: 0 RPM (min = 600 RPM, max = 7200 RPM)
PWR_FAN FAN Speed: 1074 RPM (min = 600 RPM, max = 7200 RPM)
OPT_FAN1 FAN Speed: 1116 RPM (min = 600 RPM, max = 7200 RPM)
OPT_FAN2 FAN Speed: 0 RPM (min = 600 RPM, max = 7200 RPM)
OPT_FAN3 FAN Speed: 0 RPM (min = 600 RPM, max = 7200 RPM)
CPU Temperature: +56.0°C (high = +60.0°C, crit = +65.0°C)
MB Temperature: +40.0°C (high = +45.0°C, crit = +55.0°C)
SB Temperature: +57.0°C (high = +65.0°C, crit = +65.0°C)
NB Temperature: +56.0°C (high = +80.0°C, crit = +80.0°C)
OPT_TEMP1 Temperature: +0.0°C (high = +45.0°C, crit = +45.0°C)
OPT_TEMP2 Temperature: +0.0°C (high = +45.0°C, crit = +45.0°C)
OPT_TEMP3 Temperature: +0.0°C (high = +45.0°C, crit = +45.0°C)
Avatar utente
azioga
Hero Member
Hero Member
Messaggi: 1329
Iscritto il: 03/09/2018, 7:53

Re: Pc si avvia ma da errore di caricamento kernel

Messaggio da azioga »

puoi blacklistare il modulo o toglierlo da /etc/modules
Liviovarriale
Newbie
Newbie
Messaggi: 7
Iscritto il: 27/09/2021, 6:26

Re: Pc si avvia ma da errore di caricamento kernel

Messaggio da Liviovarriale »

ho eseguito il comando

Codice: Seleziona tutto

 sudo nano /etc/modprobe.d/blacklistconf
ed ho inserito nel foglio bianco

Codice: Seleziona tutto

blacklist w83627ehf
Va bene così?
Avatar utente
azioga
Hero Member
Hero Member
Messaggi: 1329
Iscritto il: 03/09/2018, 7:53

Re: Pc si avvia ma da errore di caricamento kernel

Messaggio da azioga »

è più corretto /etc/modprobe.d/blacklist.conf
però trovo contorto mettere in blacklist un modulo che tu in /etc/modules dici al sistema di caricare.

se in /etc/modules trovi w83627ehf ti basta cancellarlo/commentarlo
Liviovarriale
Newbie
Newbie
Messaggi: 7
Iscritto il: 27/09/2021, 6:26

Re: Pc si avvia ma da errore di caricamento kernel

Messaggio da Liviovarriale »

Grazie Mille, sei stato gentilissimo.

Questo errore resterà cmq un mistero
Rispondi