Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
/dev/sda1: clean, 219799/1831424 files, 2776005/7323904 blocks
[FAILED] Failed to start Load Kernel Modules.
[ OK ] Finished Tell Plymouth To Write Out Runtime Data.
[ OK ] Finished Set console font and keymap.
[ OK ] Finished Create Volatile Files and Directories.
Starting Network Time Synchronization...
Starting Record System Boot/Shutdown in UTMP...
[ OK ] Started Load/Save RF Kill Switch Status.
[ OK ] Finished Record System Boot/Shutdown in UTMP.
[ OK ] Finished Load AppArmor profiles.
[ OK ] Started Network Time Synchronization.
[ OK ] Reached target System Time Set.
Starting Raise network interfaces...
Starting Load AppArmor pro…managed internally by snapd...
[ OK ] Finished Load AppArmor pro…s managed internally by snapd.
Starting Load Kernel Modules...
[ OK ] Finished Raise network interfaces.
[FAILED] Failed to start Load Kernel Modules.
See 'systemctl status systemd-modules-load.service' for details.
[ OK ] Reached target System Initialization.
[ OK ] Started CUPS Scheduler.
[ OK ] Started Trigger anacron every hour.
[ OK ] Started Daily apt download activities.
[ OK ] Started Daily apt upgrade and clean activities.
[ OK ] Started Daily dpkg database backup timer.
[ OK ] Started Periodic ext4 Onli…ata Check for All Filesystems.
[ OK ] Started Discard unused blocks once a week.
[ OK ] Started Refresh fwupd metadata regularly.
[ OK ] Started Daily rotation of log files.
[ OK ] Started Daily man-db regeneration.
[ OK ] Started Daily Cleanup of Temporary Directories.
[ OK ] Reached target Path Units.
[ OK ] Reached target Timer Units.
[ OK ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
[ OK ] Listening on CUPS Scheduler.
[ OK ] Listening on D-Bus System Message Bus Socket.
Starting Socket activation for snappy daemon...
[ OK ] Listening on Socket activation for snappy daemon.
[ OK ] Reached target Socket Units.
[ OK ] Reached target Basic System.
Starting Accounts Service...
[ OK ] Started Run anacron jobs.
Starting Avahi mDNS/DNS-SD Stack...
[ OK ] Started Regular background program processing daemon.
Starting D-Bus System Message Bus...
Starting Remove Stale Onli…t4 Metadata Check Snapshots...
[ OK ] Reached target Login Prompts.
Starting NVIDIA Persistence Daemon...
Starting Authorization Manager...
Starting Power Profiles daemon...
Starting System Logging Service...
Starting Snap Daemon...
Starting Switcheroo Control Proxy service...
Starting User Login Management...
Starting Disk Manager...
[ OK ] Started System Logging Service.
[FAILED] Failed to start NVIDIA Persistence Daemon.
See 'systemctl status nvidia-persistenced.service' for details.
[ OK ] Finished Remove Stale Onli…ext4 Metadata Check Snapshots.
[ OK ] Started D-Bus System Message Bus.
Starting Network Manager...
Starting WPA supplicant...
[ OK ] Started Avahi mDNS/DNS-SD Stack.
[ OK ] Started Switcheroo Control Proxy service.
Starting Save/Restore Sound Card State...
[ OK ] Started Authorization Manager.
Starting Modem Manager...
[ OK ] Started Power Profiles daemon.
[ OK ] Finished Save/Restore Sound Card State.
[ OK ] Reached target Sound Card.
[ OK ] Started Accounts Service.
[ OK ] Started User Login Management.
[ OK ] Started WPA supplicant.
[ OK ] Started Network Manager.
[ OK ] Reached target Network.
Starting Network Manager Wait Online...
Starting CUPS Scheduler...
Starting Permit User Sessions...
[ OK ] Started Unattended Upgrades Shutdown.
[ OK ] Finished Permit User Sessions.
Starting GNOME Display Manager...
Starting Hold until boot process finishes up...
Starting Hostname Service...
[ OK ] Started Modem Manager.
[ OK ] Started CUPS Scheduler.
[ OK ] Started GNOME Display Manager.
[ OK ] Started Hostname Service.
The first problem is on the very first line. And i assume that the two others are linked to the first. But i don't know how to solve it.
How did you install your NVIDIA proprietary drivers? Looks like they need rebuilding against the current kernel version. DKMS would do that automagically so I suspect you have not used the package from the Debian repositories.
Head_on_a_Stick wrote: ↑2022-06-19 18:04How did you install your NVIDIA proprietary drivers? Looks like they need rebuilding against the current kernel version. DKMS would do that automagically so I suspect you have not used the package from the Debian repositories.
I used the debian debian repository to install the nvidia driver. I actually install everything from theses repositories.
Head_on_a_Stick wrote: ↑2022-06-19 18:04Disclaimer: if it's testing/unstable you're on your own
4D696B65 wrote: ↑2022-06-19 18:09
Sid? Sometimes it takes a day or two for nvidia to be patched to build on a new kernel. Use an older kernel for now.
A day or two? Very optimistic. Sometimes it can be relatively quick but I have seen it take weeks for Nvidia to catch up for a new kernel version.
The joys of running testing or sid.
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”Remember toBACKUP!
4D696B65 wrote: ↑2022-06-19 18:09
Sid? Sometimes it takes a day or two for nvidia to be patched to build on a new kernel. Use an older kernel for now.
A day or two? Very optimistic. Sometimes it can be relatively quick but I have seen it take weeks for Nvidia to catch up for a new kernel version.
The joys of running testing or sid.
You were right ! Yesterday i got an Nvidia upgrade and now everything works fine again.