[solved] AntiX-21 long boot – Waiting for /dev to be fully populated

[Member TheBigBadBoy]

I used AntiX-19 for 3 months, booting in 4~5 seconds.

After a fresh installation of AntiX-21 (full version), using the “5.10.57-antix.1-amd64-smp” kernel, all my boots take quite long time : after the message “Waiting for /dev to be fully populated…”, my computer does not show anything else during 1 min 20 sec, and then finally boot.

I tried to delete the boot parameter “quiet”. What can be found around the message :

Using make-file style concurrent boot in runlevel S.
Starting hot-plug events dispatcher: udevd
[    4.295284] udevd[597]: starting version 3.2.11
Synthesizing the initial hotplug events (subsystems)...done.
Synthesizing the initial hotplug events (devices)...done.
Waiting for /dev to be fully populated...
[    4.325922] udevd[597]: starting eudev-3.2.11

The only boot errors (from “dmesg”) are :

[    4.438878] nvidiafb: unknown NV_ARCH
[   69.920365] Bluetooth: hci0: HCI reset during shutdown failed
[ 1098.426907] i915 0000:00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun

Also, since this problem is propably due to some of my hardware :

$ inxi -Fxz
System:
  Kernel: 5.10.57-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 10.2.1 
  Desktop: IceWM 2.9.5 Distro: antiX-21_x64-full Grup Yorum 31 October 2021 
  base: Debian GNU/Linux 11 (bullseye) 
Machine:
  Type: Laptop System: MACHENIKE product: T58-V v: N/A serial: <filter> 
  Mobo: MACHENIKE model: NH55DP-HMx serial: <filter> UEFI: INSYDE 
  v: 1.07.04TQLM6 date: 01/14/2021 
CPU:
  Info: 8-Core model: Intel Core i7-10870H bits: 64 type: MT MCP 
  arch: Comet Lake rev: 2 cache: L2: 16 MiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 70399 
  Speed: 4766 MHz min/max: 800/5000 MHz Core speeds (MHz): 1: 4766 2: 4741 
  3: 4757 4: 4758 5: 4781 6: 4789 7: 4841 8: 4789 9: 2907 10: 4719 11: 4701 
  12: 4667 13: 4805 14: 4763 15: 4778 16: 4707 
Graphics:
  Device-1: Intel CometLake-H GT2 [UHD Graphics] vendor: CLEVO/KAPOK 
  driver: i915 v: kernel bus-ID: 00:02.0 
  Device-2: NVIDIA GA106M [GeForce RTX 3060 Mobile / Max-Q] 
  vendor: CLEVO/KAPOK driver: N/A bus-ID: 01:00.0 
  Device-3: Acer BisonCam NB Pro type: USB driver: uvcvideo bus-ID: 1-8:2 
  Display: x11 server: X.Org 1.20.11 driver: loaded: modesetting 
  unloaded: fbdev,vesa resolution: 1920x1080~144Hz 
  OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 20.3.5 
  direct render: Yes 
Audio:
  Device-1: Intel Comet Lake PCH cAVS vendor: CLEVO/KAPOK 
  driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 
  Device-2: NVIDIA driver: snd_hda_intel v: kernel bus-ID: 01:00.1 
  Sound Server-1: ALSA v: k5.10.57-antix.1-amd64-smp running: yes 
Network:
  Device-1: Intel Comet Lake PCH CNVi WiFi driver: iwlwifi v: kernel 
  port: 5000 bus-ID: 00:14.3 
  IF: wlan0 state: up mac: <filter> 
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: CLEVO/KAPOK driver: r8169 v: kernel port: 3000 bus-ID: 06:00.1 
  IF: eth0 state: down mac: <filter> 
Bluetooth:
  Device-1: Intel AX201 Bluetooth type: USB driver: btusb v: 0.8 
  bus-ID: 1-14:3 
  Report: hciconfig ID: hci0 rfk-id: 1 state: down bt-service: running 
  rfk-block: hardware: no software: yes address: <filter> 
RAID:
  Hardware-1: Intel Device driver: ahci v: 3.0 bus-ID: 00:17.0 
Drives:
  Local Storage: total: 1.94 TiB used: 157.61 GiB (8.0%) 
  ID-1: /dev/sda vendor: Western Digital model: WD20SPZX-22UA7T0 
  size: 1.82 TiB 
  ID-2: /dev/sdb type: USB vendor: JMicron Tech model: Generic 
  size: 119.24 GiB 
Partition:
  ID-1: / size: 110.65 GiB used: 10.66 GiB (9.6%) fs: ext4 dev: /dev/sdb2 
  ID-2: /boot/efi size: 252 MiB used: 274 KiB (0.1%) fs: vfat dev: /dev/sdb1 
Swap:
  ID-1: swap-1 type: partition size: 6 GiB used: 0 KiB (0.0%) dev: /dev/sdb3 
Sensors:
  System Temperatures: cpu: 63.0 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 289 Uptime: 9m Memory: 31.19 GiB used: 1.47 GiB (4.7%) 
  Init: SysVinit runlevel: 5 Compilers: gcc: 10.2.1 Packages: 1566 
  Shell: Bash v: 5.1.4 inxi: 3.3.06

Thank you for any time spent to try to help me, and don’t hesitate to ask me to do manipulation, or add information (then which ones ?).

• This topic was modified 1 year, 3 months ago by TheBigBadBoy.
• This topic was modified 1 year, 3 months ago by TheBigBadBoy.
• This topic was modified 1 year, 2 months ago by christophe.

[Forum Admin anticapitalista]

Helpful

Up

0

::

Does the same happen if you boot the other 4.9 kernel?

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member TheBigBadBoy]

Helpful

Up

0

::

With the 4.9.0-294 kernel (kernel-antiX_64bit_meltdown_patched), I could not even get a GUI. After about 6 seconds I am dropped in a terminal login.

The errors I obtained (in brief) :

ACPI Error : Namespace lookup failure, AE_NOT_FOUND
udevd[605]: could not read from '/sys/module/acpi_cpufreq/initstate': No such device

Don’t know if it helps, but my computer is quite new.

Should I try other kernels from the Package installer ? Such as kernel-antiX_64bit_meltdown_patched (5.10.88) ?
Also, I don’t know why that version (5.10.88) is bigger (newer ?) than the one I am running (5.10.57), since my installation is up to date (update, upgrade & dist-upgrade).

• This reply was modified 1 year, 3 months ago by TheBigBadBoy.

[Forum Admin anticapitalista]

Helpful

Up

0

::

You could try the newer 5.10.88.
Which kernel works ok on antiX-19.3?

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member TheBigBadBoy]

Helpful

Up

0

::

No change with the 5.10.88 (“Waiting for /dev to be fully populated”).

The kernel that worked (yes, I completely erased the “old” antiX-19) with antiX 19.4 is normally 5.8.16.

I think that the most of the time I used my “old” antiX installation, it was antiX-19.4 with 5.10 kernel, but not sure.

[Anonymous]

Helpful

Up

0

::

What happens to the kernel parameter
intel_iommu=igfx_off

[Member TheBigBadBoy]

Helpful

Up

0

::

If you meant to add it to the boot parameters (by changing grub), then unfortunately it is the same as before (“Waiting for /dev […]”). Used with 5.10.88.

[Member ModdIt]

Helpful

Up

0

::

Have you already tried the rm /user/lib/udev/hid2hci
instead of removing you could rename. There is a long history of the error being related to udev
and bluetooth.

Long thread over at MX might be helpful
https://forum.mxlinux.org/viewtopic.php?t=53578&start=30

• This reply was modified 1 year, 3 months ago by ModdIt.

[Member TheBigBadBoy]

Helpful

Up

0

::

I renamed the file /usr/lib/udev/hid2hci and then rebooted, still have the message “Waiting for /dev […]”.

I did tried this without the kernel parameter intel_iommu, should I ?

• This reply was modified 1 year, 3 months ago by TheBigBadBoy.

[Anonymous]

Helpful

Up

0

::

Normally you get there by pressing e.
Then Ctrl+x to boot (you don’t need to move the cursor back).
Sorry I had the wrong picture.

[Member TheBigBadBoy]

Helpful

Up

0

::

Yes, this is what I did : edit /etc/default/grub and add the parameter to GRUB_CMDLINE_LINUX_DEFAULT (then upgrade-grub).

I could see the option when booting by hitting [e]. Anyway it does not seem to change something.

Udev is for many hardware pieces (if I read correclty the wiki). Are we sure it is due to the intel cpu ? How could we know which way to lookup ?

P.S. Sorry for any English mistakes

[Member stevesr0]

Helpful

Up

0

::

In 2018, I also had a problem when I switched from antiX 16 to antix 17. My boot time went up to 5 minutes from about 30 seconds.

My delay had two distinct causes.

One part of my problem was an issue with updated software in the newer antiX version which recognized my WACOM digitizer and caused a delay because of a coding bug which delayed startup. Anticapitalista sugested running ‘bootchart” which showed a particular point of delay and led to finding a coding error where a delay of 300 msec was changed to 300 SEC. (I just saw a post that said bootchart2 is NOT in bullseye (21) – there is probably another tool for displaying what starts when, tho.)

After that was fixed I still had a significant but lesser delay. I edited the grub command line to read: GRUB_CMDLINE_LINUX_DEFAULT=”quiet splash video=SVIDEO-1:d” (see post #11308 for where I got that advice).

After those two things, the boot time decreased to about 30 seconds, which I accepted given the age of the hardware.

Hope that is helpful.

stevesr0

• This reply was modified 1 year, 3 months ago by stevesr0.
• This reply was modified 1 year, 3 months ago by stevesr0.
• This reply was modified 1 year, 3 months ago by stevesr0.

[Moderator Brian Masinick]

Helpful

Up

0

::

TheBigBadBoy wrote

The kernel that worked (yes, I completely erased the “old” antiX-19) with antiX 19.4 is normally 5.8.16.

Try that kernel and see if it works. If not, I agree with the suggestions from Moddit; the MX Linux thread has several good ideas, particularly the one in that thread from ‘bitjam’; he’s a very knowledgeable person.

• This reply was modified 1 year, 3 months ago by Brian Masinick.

--
Brian Masinick

[Member TheBigBadBoy]

Helpful

Up

0

::

OK, so here is what I tried in addition to my last post :
– GRUB_CMDLINE_LINUX_DEFAULT=”splash video=SVIDEO-1:d”, without noticeable difference
– GRUB_CMDLINE_LINUX_DEFAULT=”bp=b9 toram” + removing the file /usr/lib/udev/hid2hci, without noticeable difference
(the boot time is approx. 1 min 20)

So tomorrow I’ll dig in the whole MX thread, and test the antiX-19 kernel. Perhaps also try ‘bootchart’.
But I just got an idea : first of all I’ll try to recreate a usb with a new fresh installation of antiX-21, perhaps something I did went wrong (like editing fstab) ?

Also, my current antiX-21 installation is not on a live-usb.

In any case, I would like to thank you all for you help ! (Even if it is not finished ^^ )

[Member TheBigBadBoy]

Helpful

Up

0

::

Big news !

I fully installed (not an usb-live), antiX-21-FULL with kernel 5.10.57 on the same machine. This new installation works absolutely fine : taking about 6 seconds for the whole boot process, with defaults kernel params. (During the boot I saw “Waiting for /dev […]”, but it took only ~2 sec).

So, first of all : I am really sorry to have bother you for a thing that, apparently, I broke myself. Once again, sorry.

–> Then, the problem is not really the same (or the approach to solve it).
What can I do to find what I broke in the antix taking 1 min 20 to boot ? Read differences of the ‘dmes’ output ?

In the possibility to not be able to find the problem, how can I create an iso (containing all the customisation I have done : packages, appearance, theme, config files of navigator, …), and then reinstall that iso which will (I hope) boot in ~6 sec

(As a side note, during the installation of antiX, I discovered that we can not install antiX-21 on some devices – for example a usb-stick 3.0 I have; while for another usb-stick 3.0 it worked directly like a charm. I’m sure the partitions were well set, since there were the same between the 2 usb. Also, I prefer installing antiX on an usb than an usb-live system, due to personal choice/taste.)

[Author]

Posts