You are not logged in.

Pages: 1

#1 2023-11-14 13:49:39

darthdeus
Member
Registered: 2017-03-04
Posts: 6

Boot stuck for 90 seconds each time

I switched my arch install to a new computer (motherboard/cpu everything, just basically moved the hard drive), and while everything seems to work fine, I started having the following issue where every time I boot it spends 83 seconds waiting for this "nct6775: Found NCT6798D or compatible chip at 0x2e:0x290".

I haven't really been able to figure out what this is or why it happens, but it's 100% consistent. I'm not even sure if this line in the log being delayed by 83 seconds is the reason it's happening, but not sure how else to diagnose it. Here's the relevant section of dmesg

[    6.374698] usbhid: USB HID core driver
[    6.381032] usb 1-7.1.4: New USB device found, idVendor=1532, idProduct=0053, bcdDevice= 2.00
[    6.383039] usb 1-7.1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    6.384684] usb 1-7.1.4: Product: Razer Naga Chroma
[    6.386453] usb 1-7.1.4: Manufacturer: Razer
[    6.401752] input: Razer Razer Naga Chroma as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7.1/1-7.1.4/1-7.1.4:1.0/0003:1532:0053.0005/input/input12
[    6.405578] hid-generic 0003:1532:0053.0005: input,hidraw4: USB HID v1.11 Mouse [Razer Razer Naga Chroma] on usb-0000:00:14.0-7.1.4/input0
[    6.410306] input: Razer Razer Naga Chroma Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7.1/1-7.1.4/1-7.1.4:1.1/0003:1532:0053.0006/input/input13
[    6.452999] usb 1-7.3.1: new high-speed USB device number 15 using xhci_hcd
[    6.466452] input: Razer Razer Naga Chroma as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7.1/1-7.1.4/1-7.1.4:1.1/0003:1532:0053.0006/input/input14
[    6.469892] hid-generic 0003:1532:0053.0006: input,hidraw5: USB HID v1.11 Keyboard [Razer Razer Naga Chroma] on usb-0000:00:14.0-7.1.4/input1
[    6.473669] input: Razer Razer Naga Chroma as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7.1/1-7.1.4/1-7.1.4:1.2/0003:1532:0053.0007/input/input15
[    6.533168] hid-generic 0003:1532:0053.0007: input,hidraw6: USB HID v1.11 Keyboard [Razer Razer Naga Chroma] on usb-0000:00:14.0-7.1.4/input2
[    6.561150] usb 1-7.3.1: New USB device found, idVendor=0499, idProduct=170f, bcdDevice= 1.04
[    6.565079] usb 1-7.3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    6.568583] usb 1-7.3.1: Product: Steinberg UR22mkII
[    6.569604] usb 1-7.3.1: Manufacturer: Yamaha Corporation
[    6.632901] usb 1-7.1.5: new high-speed USB device number 16 using xhci_hcd
[    6.727958] usb 1-7.1.5: New USB device found, idVendor=0bda, idProduct=1100, bcdDevice= 1.01
[    6.731952] usb 1-7.1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    6.735270] usb 1-7.1.5: Product: USB2.0 HID
[    6.736298] usb 1-7.1.5: Manufacturer: Realtek
[    6.747803] hid-generic 0003:0BDA:1100.0008: hiddev98,hidraw7: USB HID v1.11 Device [Realtek USB2.0 HID] on usb-0000:00:14.0-7.1.5/input0
[    6.910035] input: Razer Razer Naga Chroma as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7.1/1-7.1.4/1-7.1.4:1.0/0003:1532:0053.0005/input/input16
[    6.913983] razermouse 0003:1532:0053.0005: input,hidraw4: USB HID v1.11 Mouse [Razer Razer Naga Chroma] on usb-0000:00:14.0-7.1.4/input0
[    6.993711] input: Razer Razer Naga Chroma as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7.1/1-7.1.4/1-7.1.4:1.1/0003:1532:0053.0006/input/input17
[    7.053582] razermouse 0003:1532:0053.0006: input,hidraw5: USB HID v1.11 Keyboard [Razer Razer Naga Chroma] on usb-0000:00:14.0-7.1.4/input1
[    7.180195] input: Razer Razer Naga Chroma as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7.1/1-7.1.4/1-7.1.4:1.2/0003:1532:0053.0007/input/input18
[    7.240368] razermouse 0003:1532:0053.0007: input,hidraw6: USB HID v1.11 Keyboard [Razer Razer Naga Chroma] on usb-0000:00:14.0-7.1.4/input2
[    7.344280] mousedev: PS/2 mouse device common for all mice
[   10.842066] usbcore: registered new interface driver snd-usb-audio
[   93.140402] nct6775: Found NCT6798D or compatible chip at 0x2e:0x290
[   93.148236] 8021q: 802.1Q VLAN Support v1.8
[   93.799238] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[   93.802923] Bridge firewalling registered
[   96.497134] igc 0000:05:00.0 eno2: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[   96.603362] IPv6: ADDRCONF(NETDEV_CHANGE): eno2: link becomes ready

Offline

#2 2023-11-14 14:03:41

Khere
Member
From: Italy
Registered: 2020-03-04
Posts: 169

Re: Boot stuck for 90 seconds each time

Please post the output of

systemd-analyze critical-chain
systemd-analyze blame

Fan of Giorgio Moroder & Mohammad Ammax enemy

Offline

#3 2023-11-14 23:49:32

darthdeus
Member
Registered: 2017-03-04
Posts: 6

Re: Boot stuck for 90 seconds each time

Here's the output

$ systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @1min 32.911s
└─multi-user.target @1min 32.911s
  └─docker.service @1min 32.254s +656ms
    └─containerd.service @1min 32.004s +208ms
      └─network.target @1min 32.004s
        └─dhcpcd.service @1min 32.004s
          └─basic.target @1min 31.997s
            └─sockets.target @1min 31.997s
              └─docker.socket @1min 31.958s +38ms
                └─sysinit.target @1min 31.941s
                  └─systemd-update-done.service @2.308s +58ms
                    └─systemd-journal-catalog-update.service @2.203s +56ms
                      └─systemd-tmpfiles-setup.service @2.072s +81ms
                        └─local-fs.target @2.071s
                          └─tmp.mount @2.070s +828us
                            └─swap.target @2.030s
                              └─home-darth-gen-swapfile.swap @1.960s +40ms
                                └─home-darth-gen.mount @1.814s +50ms
                                  └─systemd-fsck@dev-disk-by\x2duuid-ddfe7504\x2d8c5f\x2d4574\x2d8fa3\x2d4138585d2b81.service @1.558s +71ms
                                    └─dev-disk-by\x2duuid-ddfe7504\x2d8c5f\x2d4574\x2d8fa3\x2d4138585d2b81.device @1.464s

and

$ systemd-analyze blame
1min 30.105s systemd-modules-load.service
       778ms dev-nvme1n1p4.device
       656ms docker.service
       355ms systemd-udev-trigger.service
       302ms mullvad-early-boot-blocking.service
       299ms systemd-remount-fs.service
       208ms containerd.service
       189ms systemd-vconsole-setup.service
       177ms modprobe@fuse.service
       168ms ldconfig.service
       151ms lvm2-monitor.service
       150ms modprobe@drm.service
       149ms avahi-daemon.service
       141ms systemd-journal-flush.service
       139ms systemd-timesyncd.service
       138ms systemd-update-utmp.service
       129ms user@1000.service
       122ms systemd-fsck@dev-disk-by\x2duuid-7C2F\x2d2C75.service
       111ms lm_sensors.service
        90ms systemd-tmpfiles-setup-dev-early.service
        81ms systemd-tmpfiles-setup.service
        71ms systemd-fsck@dev-disk-by\x2duuid-ddfe7504\x2d8c5f\x2d4574\x2d8fa3\x2d4138585d2b81.service
        70ms systemd-user-sessions.service
        58ms systemd-update-done.service
        56ms systemd-journal-catalog-update.service
        56ms systemd-tmpfiles-setup-dev.service
        54ms alsa-restore.service
        53ms systemd-random-seed.service
        53ms systemd-sysusers.service
        51ms dbus.service
        50ms boot.mount
        50ms home-darth-gen.mount
        48ms upower.service
        46ms modprobe@configfs.service
        45ms kmod-static-nodes.service
        43ms systemd-logind.service
        41ms systemd-journald.service
        40ms home-darth-gen-swapfile.swap
        38ms docker.socket
        37ms systemd-udevd.service
        34ms systemd-binfmt.service
        34ms systemd-tmpfiles-clean.service
        32ms systemd-sysctl.service
        29ms atop-rotate.service
        29ms user-runtime-dir@1000.service
        28ms modprobe@loop.service
        22ms polkit.service
        15ms bluetooth.service
        10ms dev-hugepages.mount
        10ms sys-fs-fuse-connections.mount
        10ms atop.service
        10ms dev-mqueue.mount
         9ms sys-kernel-config.mount
         9ms sys-kernel-debug.mount
         8ms sys-kernel-tracing.mount
         8ms home-darth-projects.mount
         7ms modprobe@dm_mod.service
         3ms rtkit-daemon.service
       841us proc-sys-fs-binfmt_misc.mount
       828us tmp.mount

Last edited by darthdeus (2023-11-14 23:49:54)

Offline

#4 2023-11-15 00:02:48

loqs
Member
Registered: 2014-03-06
Posts: 17,596

Re: Boot stuck for 90 seconds each time

Please post the full system journal for a boot with the issue.

Offline

#5 2023-11-15 01:35:09

darthdeus
Member
Registered: 2017-03-04
Posts: 6

Re: Boot stuck for 90 seconds each time

Here's the full log, it's a bit log so I put it in a gist, hope that's ok https://gist.github.com/darthdeus/b6609 … d3e86dc40f

Offline

#6 2023-11-15 02:36:02

loqs
Member
Registered: 2014-03-06
Posts: 17,596

Re: Boot stuck for 90 seconds each time

Nov 15 02:28:02 pipik systemd[1]: systemd-modules-load.service: start operation timed out. Terminating.
Nov 15 02:28:02 pipik systemd[1]: systemd-modules-load.service: Main process exited, code=killed, status=15/TERM
Nov 15 02:28:02 pipik systemd[1]: systemd-modules-load.service: Failed with result 'timeout'.
Nov 15 02:28:02 pipik systemd[1]: Failed to start Load Kernel Modules.

What is the output of:

tail /etc/modules-load.d/*.conf /usr/lib/modules-load.d/*.conf

Offline

#7 2023-11-15 03:01:55

darthdeus
Member
Registered: 2017-03-04
Posts: 6

Re: Boot stuck for 90 seconds each time

$ tail /etc/modules-load.d/*.conf /usr/lib/modules-load.d/*.conf
==> /etc/modules-load.d/gnutls.conf <==
#tls

==> /usr/lib/modules-load.d/bluez.conf <==
crypto_user

==> /usr/lib/modules-load.d/multipath.conf <==
# load dm-multipath early, both multipathd and multipath depend on it
# (note that multipath may be called from udev rules!)
dm-multipath

==> /usr/lib/modules-load.d/nvidia-utils.conf <==
nvidia-uvm

Offline

#8 2023-11-15 03:27:38

loqs
Member
Registered: 2014-03-06
Posts: 17,596

Re: Boot stuck for 90 seconds each time

Are those modules loaded or at least available?

lsmod
modinfo crypto_user dm-multipath nvidia-uvm

Offline

#9 2023-11-15 07:52:53

seth
Member
Registered: 2012-09-03
Posts: 52,299

Re: Boot stuck for 90 seconds each time

Nov 15 02:26:30 pipik kernel: traps: Missing ENDBR: init_module+0x0/0x1000 [v4l2loopback_dc]

https://aur.archlinux.org/packages?K=droidcam
=> Add "ibt=off" to the https://wiki.archlinux.org/title/Kernel_parameters

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#10 2023-11-15 22:36:44

loqs
Member
Registered: 2014-03-06
Posts: 17,596

Re: Boot stuck for 90 seconds each time

@darthdeus You could try something like the following,  which replaces v4l2loopback-dc-dkms with v4l2loopback-dkms which I believe does support ibt.

diff --git a/PKGBUILD b/PKGBUILD
index 6b21fcd..5797362 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -4,7 +4,7 @@
 # Past Contributor: James An <james@jamesan.ca>
 
 pkgbase=droidcam
-pkgname=('droidcam' 'v4l2loopback-dc-dkms')
+pkgname=droidcam
 pkgver=2.0.0
 pkgrel=1
 epoch=1
@@ -12,24 +12,18 @@ pkgdesc='A tool for using your android device as a wireless/usb webcam'
 arch=('x86_64')
 url="https://github.com/aramg/${pkgbase}"
 license=('GPL')
+depends=('alsa-lib' 'libjpeg-turbo' 'ffmpeg' 'libusbmuxd')
 makedepends=('libappindicator-gtk3' 'gtk3' 'ffmpeg' 'libusbmuxd')
-
+optdepends=('gtk3: use GUI version in addition to CLI interface' 'libappindicator-gtk3: use GUI version in addition to CLI interface')
 source=("${pkgbase}.desktop"
-        "dkms.conf"
         "${pkgbase}.conf"
         "${pkgbase}-${pkgver}.zip::${url}/archive/v${pkgver}.zip"
 )
 
 sha256sums=('90dd73cf146fae0de0c11b46e97412d2aaca50ec879e1be2d793261e853dd0d3'
-            '1e91f58ae83d433d32b483b14f1bb39cc245d2ace711b12c894de27dd2ea3413'
             '1d4b3ff98b4af9de77a24d1b6fad6e004deadf1f157eb800aa878ba1e7693dac'
             'a81a0b31c5693f63c56cf29484639c7b827ea8ce458a367bfba1e4c850beba4e')
 
-prepare() {
-  # Generate the module loading configuration files
-  echo "options v4l2loopback_dc width=640 height=480" >| "${pkgbase}.modprobe.conf"
-}
-
 build() {
   cd ${pkgbase}-${pkgver}
 
@@ -40,11 +34,9 @@ build() {
   make JPEG_DIR="" JPEG_INCLUDE="" JPEG_LIB="" JPEG=$(pkg-config --libs --cflags libturbojpeg) USBMUXD=-lusbmuxd-2.0
 }
 
-package_droidcam() {
-  depends=('alsa-lib' 'libjpeg-turbo' 'ffmpeg' 'v4l2loopback-dc-dkms' 'libusbmuxd')
-  optdepends=('gtk3: use GUI version in addition to CLI interface' 'libappindicator-gtk3: use GUI version in addition to CLI interface')
-
-  pushd ${pkgbase}-${pkgver}
+package() {
+  depends+=('v4l2loopback-dkms')
+  cd ${pkgbase}-${pkgver}
 
   # Install droidcam program files
   install -Dm755 "${pkgbase}" "$pkgdir/usr/bin/${pkgbase}"
@@ -55,31 +47,3 @@ package_droidcam() {
   install -Dm644 "${srcdir}/${pkgbase}.conf" "${pkgdir}/etc/modules-load.d/${pkgbase}.conf"
   install -Dm644 README.md "${pkgdir}/usr/share/licenses/${pkgbase}/LICENSE"
 }
-
-package_v4l2loopback-dc-dkms() {
-  depends=('dkms')
-  backup=("etc/modprobe.d/${pkgbase}.conf")
-
-  _pkgname=v4l2loopback-dc
-  local install_dir="${pkgdir}/usr/src/${_pkgname}-${pkgver}"
-
-  # Copy dkms.conf
-  install -Dm644 dkms.conf "${install_dir}/dkms.conf"
-
-  # Set name and version
-  sed -e "s/@_PKGNAME@/${_pkgname}/" -e "s/@PKGVER@/${pkgver}/" -i "${install_dir}/dkms.conf"
-
-  # Install module loading configuration
-  install -Dm644 "${pkgbase}.modprobe.conf" "${pkgdir}/etc/modprobe.d/${pkgbase}.conf"
-
-  # Install module source
-  cd ${pkgbase}-${pkgver}/v4l2loopback
-
-  for d in $(find . -type d); do
-    install -dm755 "${install_dir}/${d}"
-  done
-
-  for f in $(find . -type f ! -name '.gitignore'); do
-    install -m644 "${f}" "${install_dir}/${f}"
-  done
-}

@seth if you have any free time could you look at https://bbs.archlinux.org/viewtopic.php … 4#p2132034

Offline

Pages: 1

Board footer

Powered by FluxBB