Devuan takes a long time to start up

Daniell · 2022-01-07 19:20:26

Hello,

Devuan takes a long time to boot, I can't find a command for a 'no systemd' that allows me to show here the system boot time but it takes about 33 seconds...

I have two other systems,

root@kaos:~# fdisk -l
Disk /dev/nvme0n1: 238.47 GiB, 256060514304 bytes, 500118192 sectors
Disk model: PC SN520 NVMe WDC 256GB                 
Units: 1 * 512 sectors = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: gpt
Disk identifier: D3C3AE91-35A3-4FC3-8778-09C16F235FCF

Disposit.      Start End Sectors Size Type
/dev/nvme0n1p1 2048 3002367 3000320 1.4G System EFI
/dev/nvme0n1p2 3002368 5984255 2981888 1.4G Linux swap
/dev/nvme0n1p3 5984256 43108351 37124096 17.7G Linux Root (x86)
/dev/nvme0n1p4 43108352 63014911 19906560 9.5G Linux file system
/dev/nvme0n1p5 63014912 85743615 22728704 10.8G Linux filesystem
/dev/nvme0n1p6 85743616 500117503 414373888 197.6G Linux file system
root@kaos:~#

root@kaos:~# cat /etc/*release
PRETTY_NAME="Devuan GNU/Linux 4 (chimaera)"
NAME="Devuan GNU/Linux"
VERSION_ID="4"
VERSION="4 (chimaera)"
VERSION_CODENAME="chimaera"
ID=devuan
ID_LIKE=debian
HOME_URL="https://www.devuan.org/"
SUPPORT_URL="https://devuan.org/os/community"
BUG_REPORT_URL="https://bugs.devuan.org/"
root@kaos:~#

Thanks for any advice,

Regards.

Last edited by Daniell (2022-01-07 19:28:09)

ralph.ronnquist · 2022-01-07 22:56:22

... I can't find a command for a 'no systemd' that allows me to show here the system boot time ...

I think the last line in /var/log/dmesg should tell you how long time the last boot up took. And /var/log/dmesg.0 would be the previous boot. And successively /var/log/dmesg.N.gz the Nth boot before that (those files are in gzipped format though).

On that line, the first number counting from the left is a time stamp of relative time in seconds with fractions since the kernel started to, as I believe, when the "boot finished".

Daniell · 2022-01-07 23:21:13

Thank you for your response on this matter. Anyway, now what is pressing is to see what I can do to solve this delay.

oui · 2022-01-07 23:29:37

are you certain that all deamons you use can start fast? what is for ex. for connecting the web etc.?

Daniell · 2022-01-08 00:53:18

It's fine, it runs perfectly in everything else, very fast -- I have a feeling, I'm just a beginner, that it must be something to do with the Grub.

EDIT: there is another problem too, maybe not related with this one here https://dev1galaxy.org/viewtopic.php?id=4766 but i dont know, maybe it somethig with the stability of the system, just to let you know, thanks.

Last edited by Daniell (2022-01-08 01:04:22)

Head_on_a_Stick · 2022-01-08 12:04:43

Daniell wrote:

I have a feeling, I'm just a beginner, that it must be something to do with the Grub.

What makes you think that? What do you actually see during the boot process? Where exactly is the delay experienced?

Unfortunately I have no idea how to debug boot delays under sysvinit. I don't know of any equivalent for systemd-analyze, which can be tremendously useful for this sort of thing, as can the systemd journal.

Perhaps check /var/log/syslog to see if there are any clues there.

Ogis1975 · 2022-01-08 12:16:40

Head_on_a_Stick wrote:

Unfortunately I have no idea how to debug boot delays under sysvinit.

Maybe this can help https://gist.github.com/rmi1974/a8bc54d … 187e9b4b4b

fsmithred · 2022-01-08 13:24:43

Install bootlogd and look in /var/log/boot.
https://wiki.debian.org/bootlogd

There used to be a way to make that into a nice graph, but I can't find it.

Head_on_a_Stick · 2022-01-08 14:23:02

There was the old bootchart2 package but it was replaced with a version that uses systemd-analyze plot.

The .deb is installable in chimaera but the related pybootchartgui package is not (because the Python dependencies cannot be satisfied).

To install that clone the upstream git repository:

git clone https://github.com/xrmx/bootchart
cd bootchart
make

Then run

./pybootchartgui.py

Once the bootchard tarball is created (see below).

To run bootchard append these kernel parameters:

initcall_debug printk.time=y init=/sbin/bootchartd

Then check /var/log/bootchart.tgz, which is a tarball containing all the log files.

Altoid · 2022-01-08 15:00:59

Hello:

Daniell wrote:

Devuan takes a long time to boot ...

dmesg is a good place to start:

For example, if I look at my dmesg printout, I can see that it starts like this ...

~$ sudo dmesg
[    0.000000] microcode: microcode updated early to revision 0xa0b, date = 2010-09-28
[    0.000000] Linux version 5.10.0-0.bpo.3-amd64 (debian-kernel@lists.debian.org) (gcc-8 (Debian 8.3.0-6) 8.3.0, GNU ld (GNU Binutils for Debian) 2.31.1) #1 SMP Debian 5.10.13-1~bpo10+1 (2021-02-11)
[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.10.0-0.bpo.3-amd64 root=UUID=d6841f29-e39b-4c87-9c52-3a9c3bafe2d3 ro acpi_osi=Linux security=none apparmor=0 nmi_watchdog=0 pci_aspm=off agp=off ipv6.disable=1 enable_mtrr_cleanup "Loading initial ramdisk ..."
[    0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[    0.000000] x86/fpu: Enabled xstate features 0x3, context size is 576 bytes, using 'standard' format.
--- snip ---

... and ends like this:

--- snip ---
[   37.892157] vboxdrv: 000000002116db4c VBoxDDR0.r0
[   37.947857] VBoxNetFlt: attached to 'eth0' / 00:14:4f:4a:a2:81
[   37.982379] vboxdrv: 00000000384878d7 VBoxEhciR0.r0
[   37.984508] VMMR0InitVM: eflags=246 fKernelFeatures=0x0 (SUPKERNELFEATURES_SMAP=0)
[   37.989539] device eth0 entered promiscuous mode
[   39.843407] logitech-hidpp-device 0003:046D:4096.0004: HID++ 4.5 device connected.
[   49.257052] elogind-daemon[2112]: New session 1 of user groucho.
[   49.799164] fuse: init (API version 7.32)
~$

The time stamps (in seconds) at the start of each line tell me how much time each step is taking with respect to the previous one.

eg: loading the Adaptec driver for the card that drives my trusty Umax S-6E scanner takes ~4s.

--- snip ---
[   17.741513] scsi host0: Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 7.0
                       <Adaptec 2940 Ultra SCSI adapter>
                       aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBs
[   21.823271] process '/usr/bin/fstype' started with executable stack
--- snip ---

Check dmesg for errors as suggested above and for long time gaps, you may find a clue there.

Best,

A.

Daniell · 2022-01-09 00:16:18

keos@kaos:~$ sudo dmesg | grep -i "error\|warning\|fail\|segfault\|fatal"
[sudo] password for keos: 
[    0.068975] unchecked MSR access error: RDMSR from 0x123 at rIP: 0xffffffff8aa6b314 (native_read_msr+0x4/0x30)
[    0.068992] unchecked MSR access error: WRMSR to 0x123 (tried to write 0x0000000000000001) at rIP: 0xffffffff8aa6b3e4 (native_write_msr+0x4/0x20)
[    0.225962] ACPI Error: No pointer back to namespace node in package 000000007bc4ef27 (20200925/dsargs-301)
[    0.234415] ACPI Error: No pointer back to namespace node in package 000000007bc4ef27 (20200925/dsargs-301)
[    0.235788] ACPI Error: No pointer back to namespace node in package 000000007bc4ef27 (20200925/dsargs-301)
[    0.236624] ACPI Error: No pointer back to namespace node in package 000000007bc4ef27 (20200925/dsargs-301)
[    0.237400] ACPI Error: No pointer back to namespace node in package 000000007bc4ef27 (20200925/dsargs-301)
[    0.238111] ACPI Error: No pointer back to namespace node in package 000000007bc4ef27 (20200925/dsargs-301)
[    0.239101] ACPI Error: No pointer back to namespace node in package 000000007bc4ef27 (20200925/dsargs-301)
[    0.239890] ACPI Error: No pointer back to namespace node in package 000000007bc4ef27 (20200925/dsargs-301)
[    0.241080] ACPI Error: No pointer back to namespace node in package 000000007bc4ef27 (20200925/dsargs-301)
[    0.241886] ACPI Error: No pointer back to namespace node in package 000000007bc4ef27 (20200925/dsargs-301)
[    0.659067] pcieport 0000:00:1d.0: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
[    0.659441] pcieport 0000:00:1d.4: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
[    0.664477] i8042: Warning: Keylock active
[    1.281809] psmouse serio1: elantech: elantech_send_cmd query 0x02 failed.
[    1.281871] psmouse serio1: elantech: failed to query capabilities.
[    2.821907] psmouse serio1: Failed to enable mouse on isa0060/serio1
[   32.946216] i915 0000:00:02.0: firmware: failed to load i915/kbl_dmc_ver1_04.bin (-2)
[   32.946229] i915 0000:00:02.0: Direct firmware load for i915/kbl_dmc_ver1_04.bin failed with error -2
[   32.946233] i915 0000:00:02.0: [drm] Failed to load DMC firmware i915/kbl_dmc_ver1_04.bin. Disabling runtime power management.
[   33.338777] ath10k_pci 0000:02:00.0: firmware: failed to load ath10k/pre-cal-pci-0000:02:00.0.bin (-2)
[   33.338794] ath10k_pci 0000:02:00.0: firmware: failed to load ath10k/cal-pci-0000:02:00.0.bin (-2)
[   35.350810] EXT4-fs (nvme0n1p5): re-mounted. Opts: errors=remount-ro
keos@kaos:~$

This is the information that leaves the result of that command but I don't understand it, no idea what it all means or what to do, thanks for any suggestions.

Altoid · 2022-01-09 00:36:18

Hello:

Daniell wrote:

... information that leaves the result of that command ...
... don't understand it ...

Seems like read/write errors to a solid state drive, ACPI/BIOS errors and various firmware errors.

Is this a very new laptop?
Brand? Model?
Do you have the latest available BIOS installed?

Let's see what that shows us.

Best,

A.

Daniell · 2022-01-09 00:43:07

I have MXLinux and Sparky installed, there is no problem with these system to boot.

$ sudo dmesg | grep -i "error\|warning\|fail\|segfault\|fatal"
[sudo] password for keos: 
[    0.231646] ACPI Error: No pointer back to namespace node in package 00000000fe75de7d (20200925/dsargs-301)
[    0.239817] ACPI Error: No pointer back to namespace node in package 00000000fe75de7d (20200925/dsargs-301)
[    0.241192] ACPI Error: No pointer back to namespace node in package 00000000fe75de7d (20200925/dsargs-301)
[    0.242026] ACPI Error: No pointer back to namespace node in package 00000000fe75de7d (20200925/dsargs-301)
[    0.242801] ACPI Error: No pointer back to namespace node in package 00000000fe75de7d (20200925/dsargs-301)
[    0.243513] ACPI Error: No pointer back to namespace node in package 00000000fe75de7d (20200925/dsargs-301)
[    0.244506] ACPI Error: No pointer back to namespace node in package 00000000fe75de7d (20200925/dsargs-301)
[    0.245295] ACPI Error: No pointer back to namespace node in package 00000000fe75de7d (20200925/dsargs-301)
[    0.246480] ACPI Error: No pointer back to namespace node in package 00000000fe75de7d (20200925/dsargs-301)
[    0.247289] ACPI Error: No pointer back to namespace node in package 00000000fe75de7d (20200925/dsargs-301)
[    1.152939] pcieport 0000:00:1d.0: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
[    1.153322] pcieport 0000:00:1d.4: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
[    1.160119] i8042: Warning: Keylock active
[    1.871325] psmouse serio1: elantech: elantech_send_cmd query 0x02 failed.
[    1.871337] psmouse serio1: elantech: failed to query capabilities.
[    3.400264] psmouse serio1: Failed to enable mouse on isa0060/serio1
[    5.568940] platform regulatory.0: firmware: failed to load regulatory.db (-2)
[    5.568950] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[    5.568953] cfg80211: failed to load regulatory.db
[    5.889717] wl: module verification failed: signature and/or required key missing - tainting kernel
[    5.991526] ath10k_pci 0000:02:00.0: firmware: failed to load ath10k/pre-cal-pci-0000:02:00.0.bin (-2)
[    5.991559] ath10k_pci 0000:02:00.0: firmware: failed to load ath10k/cal-pci-0000:02:00.0.bin (-2)
keos@kaos:~
$

$  inxi -Fxxxrza
System:    Host: kaos Kernel: 5.10.0-10-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-10-amd64 
           root=UUID=41b80119-0195-4d8b-94fd-86ff37006b7b ro quiet splash 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 
           dm: LightDM 1.26.0 Distro: MX-21_x64 Wildflower October 20  2021 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: Dell product: Inspiron 3583 v: N/A serial: <filter> Chassis: 
           type: 10 serial: <filter> 
           Mobo: Dell model: 0WHCP7 v: A00 serial: <filter> UEFI: Dell v: 1.5.1 
           date: 05/30/2019 
Battery:   ID-1: BAT0 charge: 39.9 Wh condition: 39.9/42.0 Wh (95%) volts: 12.7/11.4 
           model: SMP DELL VM73283 type: Li-poly serial: <filter> status: Full 
CPU:       Topology: Quad Core model: Intel Core i5-8265U bits: 64 type: MT MCP 
           arch: Kaby Lake family: 6 model-id: 8E (142) stepping: C (12) microcode: EA 
           L2 cache: 6144 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28800 
           Speed: 500 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 500 2: 500 3: 500 
           4: 500 5: 500 6: 500 7: 500 8: 500 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 
           mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Enhanced IBRS, IBPB: conditional, RSB filling 
           Type: srbds mitigation: TSX disabled 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel WhiskeyLake-U GT2 [UHD Graphics 620] vendor: Dell driver: i915 
           v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 
           Display: x11 server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1366x768~60Hz 
           OpenGL: renderer: Mesa Intel UHD Graphics 620 (WHL GT2) v: 4.6 Mesa 20.3.5 
           direct render: Yes 
Audio:     Device-1: Intel Cannon Point-LP High Definition Audio vendor: Dell 
           driver: snd_hda_intel v: kernel bus ID: 00:1f.3 chip ID: 8086:9dc8 
           Sound Server: ALSA v: k5.10.0-10-amd64 
Network:   Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell driver: r8169 
           v: kernel port: 3000 bus ID: 01:00.0 chip ID: 10ec:8136 
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> 
           Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter vendor: Dell 
           driver: ath10k_pci v: kernel port: 3000 bus ID: 02:00.0 chip ID: 168c:0042 
           IF: wlan0 state: down mac: <filter> 
           Device-3: Qualcomm Atheros type: USB driver: btusb bus ID: 1-10:5 
           chip ID: 0cf3:e009 
Drives:    Local Storage: total: 238.47 GiB used: 9.67 GiB (4.1%) 
           ID-1: /dev/nvme0n1 model: PC SN520 NVMe WDC 256GB size: 238.47 GiB block size: 
           physical: 512 B logical: 512 B speed: 15.8 Gb/s lanes: 2 serial: <filter> 
           rev: 20200012 scheme: GPT 
Partition: ID-1: / raw size: 17.70 GiB size: 17.17 GiB (97.01%) used: 9.65 GiB (56.2%) 
           fs: ext4 dev: /dev/nvme0n1p3 
Sensors:   System Temperatures: cpu: 38.0 C mobo: N/A 
           Fan Speeds (RPM): cpu: 0 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian/ bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian/ bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security/ bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://www.gtlib.gatech.edu/pub/MX-Linux/workspace/mx/repo/ bullseye main non-free
           Active apt repos in: /etc/apt/sources.list.d/vivaldi.list 
           1: deb [arch=amd64] http://repo.vivaldi.com/stable/deb/ stable main
Info:      Processes: 229 Uptime: 6m Memory: 7.65 GiB used: 747.7 MiB (9.6%) Init: SysVinit 
           v: 2.96 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: bash 
           v: 5.1.4 running in: xfce4-terminal inxi: 3.0.36 
keos@kaos:~
$

hevidevi · 2022-01-09 05:07:24

just out of curiosity, is it slow to get to the grub boot menu or slow after the grub boot menu?

I had issues i dont know why but the splash.png inside /boot/grub/ made it super slow to get to the grub boot menu so i deleted that and it was a lot quicker to boot to grub screen. Deleting the splash.png or whatever it swas called reverts thegrub boot menu to the old look so no blue devuan background just the dialog blue look.

Last edited by hevidevi (2022-01-09 05:08:48)

Daniell · 2022-01-09 09:02:41

When I turn on the PC a list of installed systems appears (the grub is in MXLinux).

Then, I click on Devuan ... then the delay for the login page to appear is about 38 seconds.

This does not occur in any of the other installed systems.

Thanks

Last edited by Daniell (2022-01-09 09:05:51)

fsmithred · 2022-01-09 11:09:09

It looks like it's taking around 30 seconds for the system to figure out that it can't load the i915 firmware. You could install firmware-misc-nonfree and see if that helps.

Daniell · 2022-01-09 13:19:34

It is installed but ... nothing changed.

During installation this call my atention:

update-initramfs: Generating /boot/initrd.img-5.10.0-10-amd64
W: initramfs-tools configuration sets RESUME=UUID=774e937d-2d3d-4cae-aa8a-22a95d62048e
W: but no matching swap device is available.

Head_on_a_Stick · 2022-01-09 14:18:15

https://lists.debian.org/debian-user/20 … 00866.html

You will have to repeat those steps whenever the swap partition is re-formatted, which most distributions do when they're installed.

EDIT: and if you had actually answered this question the thread would be a lot shorter and you wouldn't have wasted other people's time:

I wrote:

What do you actually see during the boot process?

The "gave up waiting for suspend/resume device" message should have been shown during the delay and I would have known exactly what it meant and how to fix it.

Last edited by Head_on_a_Stick (2022-01-09 14:30:39)

Daniell · 2022-01-09 14:42:28

I'm referring to the installation of

firmware-misc-nonfree

After reading what appears in that information, I do not understand the reason why I have to do something in swap when I have two other systems installed that do not have any problem to boot -- No, I think I could destroy everything, in that case I uninstall Devuan which are already two problems apart from this one here, something is not right with Devuan.

Going back to post#11, command:

sudo dmesg | grep -i "error||warning|fail|segfault|fatal"

.

A firmware is missing but fails to install because that package does not exist:

firmware: failed to load ath10k/pre-cal-pci-0000:02:00.0.bin (-2)

I also believe that I am already wasting my time with this system.

Thank you.

Last edited by Daniell (2022-01-09 15:11:57)

Head_on_a_Stick · 2022-01-09 15:35:24

Daniell wrote:

I do not understand the reason why I have to do something in swap

Because the resume device was set in the initramfs image when you installed Devuan but when you installed another distribution the installer re-formatted the swap partition which changed the UUID that the initramfs image was using to find the swap.

If the initramfs image can't find the resume device (swap) during boot it waits 30 seconds just in case it is slow to attach, hence the delay.

Just to confirm: do you see the message "gave up waiting for suspend/resume device" during the boot delay?

Daniell wrote:

Going back to post#11, command:
sudo dmesg | grep -i "error||warning|fail|segfault|fatal"
.
A firmware is missing but fails to install because that package does not exist:
firmware: failed to load ath10k/pre-cal-pci-0000:02:00.0.bin (-2)

Do you not know how to use a search engine?

I entered that exact message into the search box at startpage.com and this was the top result:

https://forums.debian.net/viewtopic.php?p=703288

And arochester's answer gives this link which explains exactly why that message is totally irrelevant:

https://unix.stackexchange.com/question … 0k-cal-pci

Last edited by Head_on_a_Stick (2022-01-09 15:35:58)

Daniell · 2022-01-09 15:54:11

I have done the same with the other systems and nothing wrong ever happened, I install or uninstall the systems previously copied with Gparted (as backups) only with Devuan there are problems, plus the one in the other post, solution: UNINSTALL IT.

Sorry for your lost time ... mine? didn't it count ...? Thanks.

Head_on_a_Stick · 2022-01-09 15:57:53

Daniell wrote:

mine? didn't it count ...?

Not to me. Goodbye.

PedroReina · 2022-01-09 17:27:07

Daniell wrote:

I have done the same with the other systems and nothing wrong ever happened

Sometimes we do something slightly different and we are not aware of doing it. I'm quite sure that there are good technical explanaitions on what you are talking about.

For more that 25 years I've been learning a lot from what was apparently a malfunction of my UNIX-like system: from Coherent all the way to Devuan. Almost always I was wrong, not the system.

In this very forum I read every day a lot of expert advice.

The explanaition of HoaS about the delay of your system at boot is excelent. I spent a rewarding amount of time reading it. Thanks, HoaS.

The officially official Devuan Forum!

#1 2022-01-07 19:20:26

Devuan takes a long time to start up

#2 2022-01-07 22:56:22

Re: Devuan takes a long time to start up

#3 2022-01-07 23:21:13

Re: Devuan takes a long time to start up

#4 2022-01-07 23:29:37

Re: Devuan takes a long time to start up

#5 2022-01-08 00:53:18

Re: Devuan takes a long time to start up

#6 2022-01-08 12:04:43

Re: Devuan takes a long time to start up

#7 2022-01-08 12:16:40

Re: Devuan takes a long time to start up

#8 2022-01-08 13:24:43

Re: Devuan takes a long time to start up

#9 2022-01-08 14:23:02

Re: Devuan takes a long time to start up

#10 2022-01-08 15:00:59

Re: Devuan takes a long time to start up

#11 2022-01-09 00:16:18

Re: Devuan takes a long time to start up

#12 2022-01-09 00:36:18

Re: Devuan takes a long time to start up

#13 2022-01-09 00:43:07

Re: Devuan takes a long time to start up

#14 2022-01-09 05:07:24

Re: Devuan takes a long time to start up

#15 2022-01-09 09:02:41

Re: Devuan takes a long time to start up

#16 2022-01-09 11:09:09

Re: Devuan takes a long time to start up

#17 2022-01-09 13:19:34

Re: Devuan takes a long time to start up

#18 2022-01-09 14:18:15

Re: Devuan takes a long time to start up

#19 2022-01-09 14:42:28

Re: Devuan takes a long time to start up

#20 2022-01-09 15:35:24

Re: Devuan takes a long time to start up

#21 2022-01-09 15:54:11

Re: Devuan takes a long time to start up

#22 2022-01-09 15:57:53

Re: Devuan takes a long time to start up

#23 2022-01-09 17:27:07

Re: Devuan takes a long time to start up

Board footer