The officially official Devuan Forum!

You are not logged in.

#151 Re: Off-topic » Obarun » 2022-12-08 19:23:03

That's unfortunate. My hope is that we can learn some things from this distro. Perhaps some of the better ideas/features could be incorporated into Debian/Devuan -- or one of their derivatives.

#152 Off-topic » Obarun » 2022-12-07 22:33:07

pcalvert
Replies: 3

Out of curiosity, I recently decided to try Obarun. Even though it's running in a rather limited (only 1560 MB of RAM) virtual machine on a 12-year-old computer, it boots up surprisingly fast and is quite responsive. I'm using it with the JWM window manager.

#153 Re: Other Issues » Hdd CHS values... recover files » 2022-12-02 06:25:06

Do you have a larger HDD with at least 3TB of free space? If so, you should make an image backup of the drive using GNU ddrescue.

Package info:
https://packages.debian.org/stable/gddrescue

If you're interested, I may have some links to some ddrescue tutorials. I need to look for them, and it's past my bedtime, so it will have to wait until later.

#154 Re: Off-topic » Google in trouble again » 2022-11-20 03:11:42

Devarch wrote:

Why not dnscrypt-proxy?

I haven't gotten around to trying that yet.

Devarch wrote:

Blocklists are not enough. Ublock or smth else is a must.

I agree. I like NoScript and uBlock Origin. I usually use one or the other, but I've seen some people recommend using both together (with NoScript set to "Allow Scripts Globally"), a combination I have not tried.

#155 Re: Off-topic » Google in trouble again » 2022-11-18 21:05:34

Head_on_a_Stick wrote:

To stop Google's Analytics tracking you across the web simply install the official GA opt-out add-on for your browser:

https://tools.google.com/dlpage/gaoptout?hl=en

You can also block Google Analytics using your hosts file or, like I do, using dnsmasq.

#156 Re: Off-topic » Google in trouble again » 2022-11-05 18:49:53

Since the topic of the thread is Google, I thought I'd link to a video I just watched:

Do You Want to Tether Your Life to Google? How to Resist
https://rumble.com/v1mrt49-do-you-want- … esist.html

Even though the video is fairly short, his coverage of the topic is quite thorough.

#157 Re: Installation » How to make sure that the system is restored after a breakdown? » 2022-10-23 18:21:58

Try using aptitude. It is much better at dealing with dependency problems. You may need to install it.

Like this:

# apt install aptitude

Then try this:

# aptitude -f install

Be sure to read the output very carefully before allowing aptitude to do anything.

#158 Re: Hardware & System Configuration » [SOLVED] TP-Link AX3000 (Archer TX3000E) PCIe WiFi card not working on Refracta » 2022-10-23 17:27:27

I did a test installation of Chimaera-based Refracta on an external laptop HDD. I couldn't get the Wi-Fi card working, so I then tried a test installation of Refracta based on Daedalus. After enabling Wi-Fi using connman, I was able to see and connect to the router. However, internet access was still not working. I then had the idea to disable the onboard LAN (wired Ethernet adapter) in the BIOS, and after I did that I had working wireless internet.

Based on my experience with Daedalus, I decided to try Chimaera again. This time, after installing the firmware packages, I installed linux-image-amd64 and linux-headers-amd64 from Chimaera backports. I then rebooted, disabled the onboard LAN again, and when the system came back up I had working wireless internet. Yay!

#159 Re: Hardware & System Configuration » ACPI 2.0 question » 2022-10-20 21:23:54

Thanks for the suggestion. It tried it and most of the messages are related to missing firmware. A couple are related to ACPI, though:

# dmesg | grep -i "error\|warning\|fail\|segfault\|fatal" | grep -i acpi
[    0.531264] acpi PNP0A08:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
[    3.900266] ACPI Warning: SystemIO range 0x0000000000000828-0x000000000000082F conflicts with OpRegion 0x0000000000000800-0x000000000000084F (\PMRG) (20200925/utaddress-213)

#160 Devuan Derivatives » Refracta - HDD space required? » 2022-10-15 14:56:41

pcalvert
Replies: 2

I was wondering how much disk space is needed for Refracta. I have an old laptop HDD in an external case that I was thinking of using for a test installation. I believe that there is a 7.5 GB, Windows 2000 partition on that HDD that I could sacrifice for the test installation. Would that be big enough? I'm not planning to install any software, just some firmware packages.

Also, I noticed that the forum link on the Refracta website appears to be dead. It should probably be replaced with this link.

#161 Re: Other Issues » Broken after dist-upgrade Daedalus » 2022-10-14 19:26:25

Monitoring this forum may be helpful for Ceres users:

Siduction Forum » Upgrade Warnings (DE / EN)
https://forum.siduction.org/index.php?board=22.0

Of course, that's more applicable to Debian than Devuan, but monitoring that forum is likely be at least somewhat helpful for Ceres users.

#162 Re: Devuan » Devuan kFreeBSD » 2022-10-14 18:58:54

I believe that the Hyperbola Project working on something similar. Maybe giving them a hand would be the way to go.

#163 Hardware & System Configuration » ACPI 2.0 question » 2022-10-12 20:50:00

pcalvert
Replies: 3

I have a desktop computer with an Intel-based ASUS motherboard from 2009 that has the old-style BIOS. I was recently looking through the settings and noticed that ACPI 2.0 is disabled by default. Should I enable it or leave it the way it is? The computer shuts down, hibernates, and suspends normally, so I am inclined to leave it the way it is, but if there is a good reason to enable it, I will.

#164 Re: Hardware & System Configuration » [SOLVED] TP-Link AX3000 (Archer TX3000E) PCIe WiFi card not working on Refracta » 2022-10-12 20:41:14

Thank you everyone for your replies. Hopefully, installing Chimaera will solve this problem. If not, I am willing to go as far as installing Daedalus or Ceres.

#165 Re: Hardware & System Configuration » [SOLVED] TP-Link AX3000 (Archer TX3000E) PCIe WiFi card not working on Refracta » 2022-10-10 18:30:10

Hi Marjorie,

Thank you for your replies. I tried this workaround (hack) and had partial success:

https://notes.prkr.ca/2021/10/Intel-AX2 … Mint-20-2/

I found that here:
https://forums.linuxmint.com/viewtopic.php?p=2092127

After renaming the PNVM file and rebooting, there was no change. However, I then decided to run update-initramfs and reboot again. After doing so, I could see two local network devices -- the router and a wireless printer. Unfortunately, attempting to connect to the router was unsuccessful.

I will probably not spend much more time on this since I've been planning to install Chimaera. I would already be running it except for the fact that something urgent recently got in the way.

#166 Hardware & System Configuration » [SOLVED] TP-Link AX3000 (Archer TX3000E) PCIe WiFi card not working on Refracta » 2022-10-10 02:51:02

pcalvert
Replies: 7

I recently purchased a "TP-Link WiFi 6 AX3000 PCIe WiFi Card (Archer TX3000E)" from Amazon and installed it in my desktop computer. My current OS is Beowulf-based Refracta. I installed firmware-iwlwifi from Beowulf (Buster) backports, but the card does not appear to be working.

Here is some (hopefully) relevant information:

$ uname -a
Linux refracta 5.10.0-0.deb10.16-amd64 #1 SMP Debian 5.10.127-2~bpo10+1 (2022-07-28) x86_64 GNU/Linux
$ lspci -knn |grep -i -A5 network
01:00.0 Network controller [0280]: Intel Corporation Device [8086:2725] (rev 1a)
	Subsystem: Intel Corporation Device [8086:0020]
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi
$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
$ dmesg |grep iwlwifi
[   15.257720] iwlwifi 0000:01:00.0: firmware: direct-loading firmware iwlwifi-ty-a0-gf-a0-59.ucode
[   15.257752] iwlwifi 0000:01:00.0: api flags index 2 larger than supported by driver
[   15.257820] iwlwifi 0000:01:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 93.8.63.28
[   15.259105] iwlwifi 0000:01:00.0: loaded firmware version 59.601f3a66.0 ty-a0-gf-a0-59.ucode op_mode iwlmvm
[   15.259172] iwlwifi 0000:01:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2)
[   17.521002] iwlwifi 0000:01:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420
[   17.703923] iwlwifi 0000:01:00.0: firmware: direct-loading firmware iwlwifi-ty-a0-gf-a0.pnvm
[   17.703950] iwlwifi 0000:01:00.0: loaded PNVM version 0x324cd670
[   17.953703] iwlwifi 0000:01:00.0: Timeout waiting for PNVM load!
[   17.953751] iwlwifi 0000:01:00.0: Failed to start RT ucode: -110
[   17.953785] iwlwifi 0000:01:00.0: iwl_trans_send_cmd bad state = 0
[   17.965793] iwlwifi 0000:01:00.0: Failed to run INIT ucode: -110
[   17.977709] iwlwifi 0000:01:00.0: retry init count 0
[   17.978211] iwlwifi 0000:01:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420
[   18.401722] iwlwifi 0000:01:00.0: Timeout waiting for PNVM load!
[   18.401768] iwlwifi 0000:01:00.0: Failed to start RT ucode: -110
[   18.401802] iwlwifi 0000:01:00.0: iwl_trans_send_cmd bad state = 0
[   18.413819] iwlwifi 0000:01:00.0: Failed to run INIT ucode: -110
[   18.425759] iwlwifi 0000:01:00.0: retry init count 1
[   18.426235] iwlwifi 0000:01:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420
[   18.849710] iwlwifi 0000:01:00.0: Timeout waiting for PNVM load!
[   18.849792] iwlwifi 0000:01:00.0: Failed to start RT ucode: -110
[   18.849854] iwlwifi 0000:01:00.0: iwl_trans_send_cmd bad state = 0
[   18.862103] iwlwifi 0000:01:00.0: Failed to run INIT ucode: -110
[   18.874390] iwlwifi 0000:01:00.0: retry init count 2
# grep -i fail kern.log
Oct  8 21:59:29 refracta kernel: [    0.531173] acpi PNP0A08:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct  8 21:59:29 refracta kernel: [   11.848003] platform regulatory.0: firmware: failed to load regulatory.db (-2)
Oct  8 21:59:29 refracta kernel: [   11.848129] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
Oct  8 21:59:29 refracta kernel: [   11.848139] cfg80211: failed to load regulatory.db
Oct  8 21:59:29 refracta kernel: [   13.012137] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-ty-a0-gf-a0-59.ucode (-2)
Oct  8 21:59:29 refracta kernel: [   13.012190] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-59.ucode failed with error -2
Oct  8 21:59:29 refracta kernel: [   13.012228] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-ty-a0-gf-a0-58.ucode (-2)
Oct  8 21:59:29 refracta kernel: [   13.012275] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-58.ucode failed with error -2
Oct  8 21:59:29 refracta kernel: [   13.012297] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-ty-a0-gf-a0-57.ucode (-2)
Oct  8 21:59:29 refracta kernel: [   13.012344] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-57.ucode failed with error -2
Oct  8 21:59:29 refracta kernel: [   13.012365] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-ty-a0-gf-a0-56.ucode (-2)
Oct  8 21:59:29 refracta kernel: [   13.012410] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-56.ucode failed with error -2
Oct  8 21:59:29 refracta kernel: [   13.012432] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-ty-a0-gf-a0-55.ucode (-2)
Oct  8 21:59:29 refracta kernel: [   13.012477] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-55.ucode failed with error -2
Oct  8 21:59:29 refracta kernel: [   13.012498] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-ty-a0-gf-a0-54.ucode (-2)
Oct  8 21:59:29 refracta kernel: [   13.012561] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-54.ucode failed with error -2
Oct  8 21:59:29 refracta kernel: [   13.012582] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-ty-a0-gf-a0-53.ucode (-2)
Oct  8 21:59:29 refracta kernel: [   13.012676] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-53.ucode failed with error -2
Oct  8 21:59:29 refracta kernel: [   13.012700] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-ty-a0-gf-a0-52.ucode (-2)
Oct  8 21:59:29 refracta kernel: [   13.012780] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-52.ucode failed with error -2
Oct  8 21:59:29 refracta kernel: [   13.012799] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-ty-a0-gf-a0-51.ucode (-2)
Oct  8 21:59:29 refracta kernel: [   13.012878] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-51.ucode failed with error -2
Oct  8 21:59:29 refracta kernel: [   13.012899] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-ty-a0-gf-a0-50.ucode (-2)
Oct  8 21:59:29 refracta kernel: [   13.012977] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-50.ucode failed with error -2
Oct  8 21:59:29 refracta kernel: [   13.012998] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-ty-a0-gf-a0-49.ucode (-2)
Oct  8 21:59:29 refracta kernel: [   13.013077] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-49.ucode failed with error -2
Oct  8 21:59:29 refracta kernel: [   13.013098] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-ty-a0-gf-a0-48.ucode (-2)
Oct  8 21:59:29 refracta kernel: [   13.013177] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-48.ucode failed with error -2
Oct  8 21:59:29 refracta kernel: [   13.013198] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-ty-a0-gf-a0-47.ucode (-2)
Oct  8 21:59:29 refracta kernel: [   13.013276] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-47.ucode failed with error -2
Oct  8 21:59:29 refracta kernel: [   13.013304] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-ty-a0-gf-a0-46.ucode (-2)
Oct  8 21:59:29 refracta kernel: [   13.013389] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-46.ucode failed with error -2
Oct  8 21:59:29 refracta kernel: [   13.013412] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-ty-a0-gf-a0-45.ucode (-2)
Oct  8 21:59:29 refracta kernel: [   13.013490] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-45.ucode failed with error -2
Oct  8 21:59:29 refracta kernel: [   13.013510] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-ty-a0-gf-a0-44.ucode (-2)
Oct  8 21:59:29 refracta kernel: [   13.013589] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-44.ucode failed with error -2
Oct  8 21:59:29 refracta kernel: [   13.013609] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-ty-a0-gf-a0-43.ucode (-2)
Oct  8 21:59:29 refracta kernel: [   13.013688] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-43.ucode failed with error -2
Oct  8 21:59:29 refracta kernel: [   13.013744] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-ty-a0-gf-a0-42.ucode (-2)
Oct  8 21:59:29 refracta kernel: [   13.013823] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-42.ucode failed with error -2
Oct  8 21:59:29 refracta kernel: [   13.013844] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-ty-a0-gf-a0-41.ucode (-2)
Oct  8 21:59:29 refracta kernel: [   13.013922] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-41.ucode failed with error -2
Oct  8 21:59:29 refracta kernel: [   13.013943] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-ty-a0-gf-a0-40.ucode (-2)
Oct  8 21:59:29 refracta kernel: [   13.014030] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-40.ucode failed with error -2
Oct  8 21:59:29 refracta kernel: [   13.014053] iwlwifi 0000:01:00.0: firmware: failed to load iwlwifi-ty-a0-gf-a0-39.ucode (-2)
Oct  8 21:59:29 refracta kernel: [   13.014147] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-39.ucode failed with error -2
Oct  8 21:59:43 refracta kernel: [   74.316064] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel
Oct  8 22:05:24 refracta kernel: [    0.530090] acpi PNP0A08:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct  8 22:05:24 refracta kernel: [   11.490114] platform regulatory.0: firmware: failed to load regulatory.db (-2)
Oct  8 22:05:24 refracta kernel: [   11.490224] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
Oct  8 22:05:24 refracta kernel: [   11.490231] cfg80211: failed to load regulatory.db
Oct  8 22:05:24 refracta kernel: [   14.150194] iwlwifi 0000:01:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2)
Oct  8 22:05:24 refracta kernel: [   16.809751] iwlwifi 0000:01:00.0: Failed to start RT ucode: -110
Oct  8 22:05:24 refracta kernel: [   16.821800] iwlwifi 0000:01:00.0: Failed to run INIT ucode: -110
Oct  8 22:05:24 refracta kernel: [   17.261819] iwlwifi 0000:01:00.0: Failed to start RT ucode: -110
Oct  8 22:05:24 refracta kernel: [   17.273814] iwlwifi 0000:01:00.0: Failed to run INIT ucode: -110
Oct  8 22:05:24 refracta kernel: [   17.709819] iwlwifi 0000:01:00.0: Failed to start RT ucode: -110
Oct  8 22:05:24 refracta kernel: [   17.721843] iwlwifi 0000:01:00.0: Failed to run INIT ucode: -110
Oct  8 22:05:37 refracta kernel: [   39.785007] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel
Oct  9 13:07:32 refracta kernel: [    0.528058] acpi PNP0A08:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct  9 13:07:32 refracta kernel: [   12.211680] platform regulatory.0: firmware: failed to load regulatory.db (-2)
Oct  9 13:07:32 refracta kernel: [   12.211782] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
Oct  9 13:07:32 refracta kernel: [   12.211791] cfg80211: failed to load regulatory.db
Oct  9 13:07:32 refracta kernel: [   14.805559] iwlwifi 0000:01:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2)
Oct  9 13:07:32 refracta kernel: [   17.457229] iwlwifi 0000:01:00.0: Failed to start RT ucode: -110
Oct  9 13:07:32 refracta kernel: [   17.469243] iwlwifi 0000:01:00.0: Failed to run INIT ucode: -110
Oct  9 13:07:32 refracta kernel: [   17.905242] iwlwifi 0000:01:00.0: Failed to start RT ucode: -110
Oct  9 13:07:32 refracta kernel: [   17.917262] iwlwifi 0000:01:00.0: Failed to run INIT ucode: -110
Oct  9 13:07:32 refracta kernel: [   18.353220] iwlwifi 0000:01:00.0: Failed to start RT ucode: -110
Oct  9 13:07:32 refracta kernel: [   18.365234] iwlwifi 0000:01:00.0: Failed to run INIT ucode: -110
Oct  9 13:07:46 refracta kernel: [   40.665598] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel
Oct  9 13:15:53 refracta kernel: [    0.531163] acpi PNP0A08:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct  9 13:15:53 refracta kernel: [   42.062592] platform regulatory.0: firmware: failed to load regulatory.db (-2)
Oct  9 13:15:53 refracta kernel: [   42.062713] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
Oct  9 13:15:53 refracta kernel: [   42.062722] cfg80211: failed to load regulatory.db
Oct  9 13:15:53 refracta kernel: [   44.950297] iwlwifi 0000:01:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2)
Oct  9 13:15:53 refracta kernel: [   47.621714] iwlwifi 0000:01:00.0: Failed to start RT ucode: -110
Oct  9 13:15:53 refracta kernel: [   47.634009] iwlwifi 0000:01:00.0: Failed to run INIT ucode: -110
Oct  9 13:15:53 refracta kernel: [   48.069733] iwlwifi 0000:01:00.0: Failed to start RT ucode: -110
Oct  9 13:15:53 refracta kernel: [   48.081711] iwlwifi 0000:01:00.0: Failed to run INIT ucode: -110
Oct  9 13:15:53 refracta kernel: [   48.521752] iwlwifi 0000:01:00.0: Failed to start RT ucode: -110
Oct  9 13:15:53 refracta kernel: [   48.533731] iwlwifi 0000:01:00.0: Failed to run INIT ucode: -110
Oct  9 13:16:07 refracta kernel: [   70.568770] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel
Oct  9 15:31:02 refracta kernel: [    0.528841] acpi PNP0A08:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct  9 15:31:02 refracta kernel: [   12.646318] platform regulatory.0: firmware: failed to load regulatory.db (-2)
Oct  9 15:31:02 refracta kernel: [   12.646430] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
Oct  9 15:31:02 refracta kernel: [   12.646437] cfg80211: failed to load regulatory.db
Oct  9 15:31:02 refracta kernel: [   15.259172] iwlwifi 0000:01:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2)
Oct  9 15:31:02 refracta kernel: [   17.953751] iwlwifi 0000:01:00.0: Failed to start RT ucode: -110
Oct  9 15:31:02 refracta kernel: [   17.965793] iwlwifi 0000:01:00.0: Failed to run INIT ucode: -110
Oct  9 15:31:02 refracta kernel: [   18.401768] iwlwifi 0000:01:00.0: Failed to start RT ucode: -110
Oct  9 15:31:02 refracta kernel: [   18.413819] iwlwifi 0000:01:00.0: Failed to run INIT ucode: -110
Oct  9 15:31:02 refracta kernel: [   18.849792] iwlwifi 0000:01:00.0: Failed to start RT ucode: -110
Oct  9 15:31:02 refracta kernel: [   18.862103] iwlwifi 0000:01:00.0: Failed to run INIT ucode: -110
Oct  9 15:31:15 refracta kernel: [   40.319270] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel

Any thoughts or ideas on what the problem is or might be?

#167 Re: Off-topic » Executables in home directory » 2022-07-17 15:15:44

Hi Chris,

Thank you for your suggestions. My plan is to move those directories immediately after installation, while the system is offline, so the risk of malware ever being able to write to those directories should be very, very small.

#168 Off-topic » Executables in home directory » 2022-07-16 11:02:40

pcalvert
Replies: 2

I was just digging around in my home directory and noticed that some software puts executable files in there, which is something that I'm not a fan of. I like to put home on a separate partition that is marked "nosuid, noexec" in the fstab file. Obviously, this will cause problems for executable files that are in my home directory.

So far, these are the places where I've found executable files:

~/bin
~/.local/bin
~/.wine

Does anyone know if there are any others? My original plan was to move these to a directory on the root (system) partition and replace the originals with symbolic links. I'll probably do that if I can depend on executable files to only be present in a few, predictable locations in my home directory.

By the way, the reason for doing this is that I have a personal security policy, and part of that policy is that "threat gate" applications like web browsers, email clients, etc., should not have write access to any file system where files can be executed. That way, if any malicious code (e.g., a malware "dropper") is written to disk, that code will not be allowed to execute.

#169 Re: Other Issues » Chimaera and VirtualBox after kernel update » 2022-07-16 03:54:41

PengouinPdt wrote:

PS: One tips, reboot on oldier kernel…
(if available)

This works. I had the same problem on Beowulf because I use a kernel from backports. After spending a lot of time trying to repair Windows 8.1, I began to suspect that the problem is not in the guest but on the host. I decided to try rebooting with the previous kernel, and when I did the problem was gone.

#170 Re: Devuan Derivatives » Lion Linux » 2022-07-05 06:23:48

Ogis1975 wrote:

I don't really understand the essence of this distribution. After all, you can always install a minimal system and then install what you need.

Although that is technically true, many people are not willing or able to do that. They may lack the necessary experience required, or they may be lazy, impatient, etc.

#171 Re: Installation » [SOLVED] Anacron symlinked to "true", again. » 2022-06-28 23:04:58

fsmithred wrote:

I could put the fix in a postinstall script in the next version, but I think the user should be warned and asked to OK it.

I don't think that's really necessary. On a live system it doesn't make sense to have anacron running. However, once the system has been installed, having anacron running is the normal and expected behavior. IMO, asking the user to OK the fix is asking for trouble since some users will likely be confused by this.

#172 Off-topic » Linux Hardening Guide » 2022-06-12 13:36:11

pcalvert
Replies: 2

I recently started looking for guides on how to harden GNU/Linux systems. This is the best one that I've found so far:

https://madaidans-insecurities.github.i … ening.html

#173 Re: Installation » [SOLVED] UFW causes errors under Chimaera » 2022-05-27 01:56:43

I recommend giving FireHOL a try. It uses a simple, human-readable configuration file.

Package name: firehol

More info:
https://firehol.org/
https://packages.debian.org/stable/firehol

For most desktop and laptop computers, the default configuration should be sufficient. For a server you would need to configure the firewall according to the services that are running on it.

#174 Re: Installation » Why is only main repo is active in sources.list? » 2022-05-05 07:26:04

rolfie wrote:

non-free: propriatary stuff - you want to enable this when you need firmware for your hardware to work

Most people probably will need to enable non-free in order to install one of these packages:

amd64-microcode
intel-microcode

#175 Re: Hardware & System Configuration » Important - log4j exploit alarm affecting Linux » 2022-03-18 16:18:14

I have LibreOffice installed and a search for "log4j" found nothing. However, I am selective about what I install and don't allow software to install recommended packages by default. It looks like I installed LibreOffice Writer and then later installed LibreOffice Math. Those are the only parts of LibreOffice that I installed because I really don't have a need for the rest of it. Because of LibreOffice's bloat, I've long preferred to use AbiWord and Gnumeric instead.

My result:

$ apt list | grep installed | grep java

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

javascript-common/oldstable,now 11 all [installed,automatic]
libjavascriptcoregtk-4.0-18/oldstable-security,now 2.34.6-1~deb10u1 amd64 [installed,automatic]

Here's another option worth considering:
https://portableapps.com/apps/office/li … legacy-5.4

I sometimes use that in a Windows XP VM.

Board footer

Forum Software