The officially official Devuan Forum!

You are not logged in.

#1 Re: Other Issues » [SOLVED] Failed to check for processor microcode upgrades(x86_64) » 2026-07-09 07:01:02

There is an amd64 microcode package. I reckon that you should install it. Sorry if I made a mistake, I don't have the best knowledge of hardware and firmware.

#2 Re: Other Issues » [SOLVED] Failed to check for processor microcode upgrades(x86_64) » 2026-07-08 18:05:00

I simply installed the intel-microcode package. That was easy. But I searched online, and I'm amazed from how little info there is about this issue.

#3 Re: Other Issues » [SOLVED] Failed to check for processor microcode upgrades(x86_64) » 2026-07-07 09:41:00

lscpu output:
Architecture:                x86_64
  CPU op-mode(s):            32-bit, 64-bit
  Address sizes:             39 bits physical, 48 bits virtual
  Byte Order:                Little Endian
CPU(s):                      8
  On-line CPU(s) list:       0-7
Vendor ID:                   GenuineIntel
  Model name:                Intel(R) Core(TM) i5-1035G1 CPU @ 1.00GHz
    CPU family:              6
    Model:                   126
    Thread(s) per core:      2
    Core(s) per socket:      4
    Socket(s):               1
    Stepping:                5
    CPU(s) scaling MHz:      28%
    CPU max MHz:             3600.0000
    CPU min MHz:             400.0000
    BogoMIPS:                2380.80
    Flags:                   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pg
                             e mca cmov pat pse36 clflush dts acpi mmx fxsr sse
                             sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm cons
                             tant_tsc art arch_perfmon pebs bts rep_good nopl xt
                             opology nonstop_tsc cpuid aperfmperf tsc_known_freq
                              pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ss
                             se3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2ap
                             ic movbe popcnt tsc_deadline_timer aes xsave avx f1
                             6c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb
                              ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow flex
                             priority ept vpid ept_ad fsgsbase tsc_adjust bmi1 a
                             vx2 smep bmi2 erms invpcid avx512f avx512dq rdseed
                             adx smap avx512ifma clflushopt intel_pt avx512cd sh
                             a_ni avx512bw avx512vl xsaveopt xsavec xgetbv1 xsav
                             es split_lock_detect dtherm ida arat pln pts hwp hw
                             p_notify hwp_act_window hwp_epp hwp_pkg_req vnmi av
                             x512vbmi umip pku ospke avx512_vbmi2 gfni vaes vpcl
                             mulqdq avx512_vnni avx512_bitalg avx512_vpopcntdq r
                             dpid fsrm md_clear flush_l1d arch_capabilities
Virtualization features:     
  Virtualization:            VT-x
Caches (sum of all):         
  L1d:                       192 KiB (4 instances)
  L1i:                       128 KiB (4 instances)
  L2:                        2 MiB (4 instances)
  L3:                        6 MiB (1 instance)
NUMA:                       
  NUMA node(s):              1
  NUMA node0 CPU(s):         0-7
Vulnerabilities:             
  Gather data sampling:      Vulnerable: No microcode
  Indirect target selection: Mitigation; Aligned branch/return thunks
  Itlb multihit:             KVM: Mitigation: Split huge pages
  L1tf:                      Not affected
  Mds:                       Not affected
  Meltdown:                  Not affected
  Mmio stale data:           Vulnerable: Clear CPU buffers attempted, no microco
                             de; SMT vulnerable
  Reg file data sampling:    Not affected
  Retbleed:                  Mitigation; Enhanced IBRS
  Spec rstack overflow:      Not affected
  Spec store bypass:         Mitigation; Speculative Store Bypass disabled via p
                             rctl
  Spectre v1:                Mitigation; usercopy/swapgs barriers and __user poi
                             nter sanitization
  Spectre v2:                Mitigation; Enhanced / Automatic IBRS; IBPB conditi
                             onal; PBRSB-eIBRS SW sequence; BHI SW loop, KVM SW
                             loop
  Srbds:                     Vulnerable: No microcode
  Tsa:                       Not affected
  Tsx async abort:           Not affected
  Vmscape:                   Not affected

#4 Other Issues » [SOLVED] Failed to check for processor microcode upgrades(x86_64) » 2026-07-07 09:40:26

WEBDEVDESTROYER2000
Replies: 8

.$$$$$`    Uptime: 2 hours, 29 mins
                         ;$$$$$P    Packages: 2359 (dpkg), 6 (flatpak)
                      .:P$$$$$$`    Shell: bash 5.2.37
                  .,:b$$$$$$$;'     Display (CMN1388): 1920x1080 @ 60 Hz in 13" [Built-in]   .,:dP$$$$$$$$b:'
      .,:;db$$$$$$$$$$Pd'`          DE: Xfce4 4.20
,db$$$$$$$$$$$$$$b:'`              WM: Xfwm4 (X11)
:$$$$$$$$$$$$b:'`                   WM Theme: Clearlooks-Phenix-Sapphire
`$$$$$bd:''`                       Theme: Clearlooks-Phenix-Sapphire [GTK2/3/4]
   `'''`                            Icons: Deepsea [GTK2/3/4]
                                    Font: Sans (10pt) [GTK2/3/4]
                                    Cursor: DMZ-White
                                    Terminal: xfce4-terminal 1.1.4
                                    Terminal Font: CodeNewRoman Nerd Font Mono (12pt)
                                    CPU: Intel(R) Core(TM) i5-1035G1 (8) @ 3.60 GHz
                                    GPU: Intel Iris Plus Graphics G1 (Ice Lake) @ 1.05 GHz [Integrated]
                                    Memory: 2.45 GiB / 7.44 GiB (33%)
                                    Swap: 0 B / 7.67 GiB (0%)
                                    Disk (/): 15.57 GiB / 225.18 GiB (7%) - ext4
                                    Local IP (wlan0): 192.168.1.135/24
                                    Battery (UX325): 90% (2 hours, 56 mins remaining) [Discharging]
                                    Locale: en_US.UTF-8

How to fix?

#5 Other Issues » Other sources of documentation » 2026-07-05 16:39:38

WEBDEVDESTROYER2000
Replies: 12

I would like to ask a question concerning the future of documentation in Devuan. Will all documentation for Devuan remain on this forum, or will there be some kind of wiki or another site to help out with documentation? Just asking!

#7 Re: Off-topic » [SOLVED] Why hasn't sysvinit been abandoned yet? » 2026-07-04 16:51:45

Now I get your nic. Hopefully you'll grow up some day .

Rude.

#8 Re: Off-topic » [SOLVED] Why hasn't sysvinit been abandoned yet? » 2026-07-04 16:31:39

If it works, don't fix it. Shiny new s**t just stirs the pot and is a waste of time and resources IMO.

I see your point 100%. But I imagine that due to its age, sysvinit could lead to security vulnerabilities and just horrible bugs in general. If that ever is the case, will sysvinit ever be dropped or will it forever remain the main init system for Devuan?

#10 Off-topic » [SOLVED] Why hasn't sysvinit been abandoned yet? » 2026-07-04 15:11:27

WEBDEVDESTROYER2000
Replies: 18

Sysvinit is quite old, so why hasn't it been abandoned in favor of another init system such as dinit? Just asking, not stating that sysvinit SHOULD be removed.

Board footer

Forum Software