Here is the output of cat /var/log/pacman.log:
[2022-06-21T14:43:08+0100] [PAMAC] synchronizing package lists
[2022-06-21T14:43:14+0100] [ALPM] transaction started
[2022-06-21T14:43:14+0100] [ALPM] installed manjaro-settings-samba (20210926-1)
[2022-06-21T14:43:14+0100] [ALPM-SCRIPTLET] ==> Attempting to enable Samba services...Created symlink /etc/systemd/system/multi-user.target.wants/smb.service → /usr/lib/systemd/system/smb.service.
[2022-06-21T14:43:14+0100] [ALPM-SCRIPTLET] Created symlink /etc/systemd/system/multi-user.target.wants/nmb.service → /usr/lib/systemd/system/nmb.service.
[2022-06-21T14:43:15+0100] [ALPM-SCRIPTLET] ==> Adding user 'michaelgv' to user-group 'sambashare'
[2022-06-21T14:43:15+0100] [ALPM-SCRIPTLET] ==> Samba services should now be enabled.==> Please add new users to 'sambashare' group.==> Reboot your system, so changes will take effect..
[2022-06-21T14:43:15+0100] [ALPM] transaction completed
[2022-06-21T14:45:24+0100] [PAMAC] synchronizing package lists
[2022-06-21T14:45:31+0100] [ALPM] transaction started
[2022-06-21T14:45:31+0100] [ALPM] installed thunar-gtk3 (2019.08.15-1)
[2022-06-21T14:45:31+0100] [ALPM] installed thunar-shares-plugin-gtk3 (0.3.0-1)
[2022-06-21T14:45:31+0100] [ALPM] transaction completed
[2022-06-21T14:45:31+0100] [ALPM] running '30-systemd-update.hook'...
[2022-06-21T16:28:06+0100] [ALPM] transaction started
[2022-06-21T16:28:06+0100] [ALPM] removed thunar-shares-plugin-gtk3 (0.3.0-1)
[2022-06-21T16:28:06+0100] [ALPM] removed thunar-gtk3 (2019.08.15-1)
[2022-06-21T16:28:07+0100] [ALPM] removed manjaro-settings-samba (20210926-1)
[2022-06-21T16:28:07+0100] [ALPM-SCRIPTLET] ==> Attempting to disable Samba services...Removed "/etc/systemd/system/multi-user.target.wants/smb.service".
[2022-06-21T16:28:07+0100] [ALPM-SCRIPTLET] Removed "/etc/systemd/system/multi-user.target.wants/nmb.service".
[2022-06-21T16:28:07+0100] [ALPM-SCRIPTLET] sambashare:x:964:michaelgv
[2022-06-21T16:28:07+0100] [ALPM-SCRIPTLET]
[2022-06-21T16:28:07+0100] [ALPM-SCRIPTLET] ==> Samba services should now be disabled. Reboot your system.
[2022-06-21T16:28:07+0100] [ALPM] transaction completed
[2022-06-21T16:28:07+0100] [ALPM] running '30-systemd-update.hook'...
[2022-06-21T17:19:15+0100] [PACMAN] Running 'pacman -Syyu'
[2022-06-21T17:19:15+0100] [PACMAN] synchronizing package lists
[2022-06-21T17:19:16+0100] [PACMAN] starting full system upgrade
I’ve seen that to disable Watchdog I need to do the following:
adding nowatchdog to the kernel parameters and blacklist iTCO_wdt in a conf file in /etc/modprobe.d/
But, I don’t know how add stuff to the kernel parameters. (I’m a n00b to linux only installed it recently.)
it removed 2 thunar related packages with it…etc/default/grub and put into GRUB_CMDLINE_LINUX_DEFAULT the following kernel parameter:nowatchdog - dont remove anything from there, just add it inside the quotes to already existing parameters, and just to be sure copy the line heresudo update-grubsudo nano /etc/modprobe.d/blacklist.confblacklist iTCO_wdtblacklist iTCO_vendor_supportCTRL+X, to save the filesudo mkinitcpio -P
Thanks, super helpful. After rebooting it twice I get a new error now:
Broadcast message from michaelgv@michael-xps179720 (*timestamp):
The system is going down for reboot NOW!
[ 89...] systemd-shutdown[1]: Waiting for process: 443 (systemd-udevd), 414 (systemd-udevd), 436 (systemd-udevd)
[ 179...] systemd-shutdown[1]: Waiting for process: 436 (systemd-udevd), 443 (systemd-udevd)
[ 245...] INFO: task systemd-udevd:436 blocked for more than 122 seconds.
[ 245...] Tainted: P OE 5.15.40-1-MANJARO #1
[ 245...] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 245...] INFO: task systemd-udevd:443 blocked for more than 122 seconds.
[ 245...] Tainted: P OE 5.15.40-1-MANJARO #1
[ 245...] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 269...] shutdown[1[ Waiting for process: 443 (systemd-udevd), 436 (systemd-udevd)
[ 359...] shutdown[1[ Waiting for process: 443 (systemd-udevd), 436 (systemd-udevd)
[ 368...] INFO: task systemd-udevd:436 blocked for more than 122 seconds.
[ 368...] Tainted: P OE 5.15.40-1-MANJARO #1
[ 368...] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 368...] INFO: task systemd-udevd:443 blocked for more than 122 seconds.
[ 368...] Tainted: P OE 5.15.40-1-MANJARO #1
[ 368...] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 439..] sd-unmoun[1967]: Failed to unmount /oldroot: Device or resource busy
[ 439..] sd-unmoun[1968]: Failed to unmount /oldroot/dev: Device or resource busy
[ 439...] shutdown[1]: Failed to finalize file systems, ignoring.
[ 491...] INFO: task systemd-udevd:436 blocked for more than 122 seconds.
[ 491...] Tainted: P OE 5.15.40-1-MANJARO #1
[ 491...] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 491...] INFO: task systemd-udevd:443 blocked for more than 122 seconds.
[ 491...] Tainted: P OE 5.15.40-1-MANJARO #1
[ 491...] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
install different kernel, for example the 5.10 lts and try with it
510 just gets stuck when trying to boot at the black screen with the flashing underscore.
Should I try a more recent version?
yes try the 5.18 and check output from these commands:cat /proc/sys/kernel/watchdogcat /proc/sys/kernel/nmi_watchdog
Yeah I got 0 for both of those.
5.18 is similar, this time the underscore doesn’t flash.
so you can boot only with the 5.15 kernel?
zbe
22 June 2022 10:26
15
If you can’t boot any other kernel then you have some bigger issues and misconfigurations we don’t know about.
First of all, try unplugging all usb dongles and retry.FS#63697 : systemd 243.0-1 poweroff/reboot umount errors
I didn’t have any usb dongles plugged in.
I tried adding the below (before the for loop that was already in there) to /usr/lib/systemd/system-shutdown/nvidia.shutdown:
# remove nvidia modules
/usr/bin/modprobe -r nvidia_drm nvidia_modeset nvidia_uvm && /usr/bin/modprobe -r nvidia
After two reboots that seems to have fixed it. Although I still can’t turn the computer on with a different Linux kernel. Only 5.15
UPDATE: Has stopped working again
zbe
23 June 2022 11:04
17
I think one of the solutions was to include ‘shutdown’ hook in /etc/mkinitcpio.conf's HOOKS array (and remake initramfs). But on the other hand there are mentions of this hook being deprecated.
I admit, I only skimmed over that page, so you might want to investigate further.
I’ve tried uninstalling Manjaro and loading it from the same USB that I used to install it and now it won’t even turn off from the USB either.
It previously worked fine from before and it’s the same version of Manjaro that I installed from initially.
Tried that too. I was wondering if it might be because I’m using Minimal Manjaro
you could try the normal version iso, not the minimal, and also use ventoy to flash the iso
At the moment I flash the ISO using the CLI on my Mac: sudo dd bs=4m if=manjaro-xfce-21.2.6-minimal-220416-linux515.iso of=/dev/disk4 That should do the job shouldn’t it?
with this i cant help you, i have no idea how to flash using dd…
Ok, I have no reason to suspect that that’s causing the issues. I’ve been reading around in some other threads and I’m thinking the issue might be to do with the Nvidia driver and that I should try to manually install it. I’m still trying to wrap my head around it all though.
@brahma I’m going to give up and try Fedora instead thanks for all your help.
