The officially official Devuan Forum!

You are not logged in.

#1 Re: Installation » [SOLVED] linux-image-6.* / Chimaera » 2022-11-22 22:24:52

Agree, the CPU on my 5600G worked fine with 5.10, the issues I had were in support for the integrated GPU. This was improved with new GPU commits from AMD in 5:15.
I also have a nct6687-isa-0a20 fans sensor on the MSI AMD B550 MPG Gaming Plus Motherboard that I needed the 5.15 kernel headers so I could compile in its kernel module.
On my system upgrading to kernels 5.18 and 5.19 caused graphical glitching with Signal Desktop and Zoom and issues with getting reliable hibernation.

#2 Re: Installation » [SOLVED] linux-image-6.* / Chimaera » 2022-11-22 17:28:30

Yes, linux-image-6.0.0.0 and corresponding headers are now available in Chimaera backports.

Do you have newer hardware that actually needs anything later than the stable 5.10 kernel (which is still being updated with security patches)?

In my case I did update from 5.10 to 5.15 when I updated my processor and motherboard to ones that weren't fully covered by 5.10  (AMD 5600G and a new sensors chip on my B550 motherboard) however I found that subsequent kernels 5.18 and 5.19 contained regressions which caused certain programs I use to glitch so I reverted to 5.15.

I might try 6.0 but it's quite possible the regressions are still there and I'll have to revert.

#3 Re: Desktop and Multimedia » Can you suggest some tips and tricks for speed up Devuan? » 2022-11-17 11:55:52

Devarch wrote:

To speed up devuan I've disabled anacron. Sometimes it slows down shutdown.

This strikes me as odd.

Anacron is useful on personal PCs that  you turn on and off so that scheduled cron jobs run just after startup (you can set a possibly randomised delay). This avoids  cron jobs not being run because your machine would be turned off at the time set for the cron job. On an alway-on server you would typically run such jobs in the small hours.

The jobs run by anacron are those in /etc/cron.hourly/, /etc/cron.daily/, /etc/cron.weekly/ and /etc/cron.monthly. If a job is unnecessary for you then remove it from the respective /etc/cron.*. If you think it's using too much resource consider doing it less frequently.

As I mostly hibernate rather than shut down my personal PC overnight I've also set it up so that it also checks if anacron needs to run any daily, weekly or monthly when its woken.

I can't think of any reason why anacron should delay shutdown.

#4 Re: Other Issues » [SOLVED] Zoom in Devuan » 2022-10-14 15:00:27

Just to update: the issue I was having running Zoom and Signal Desktop on my AMD 5600G with Chimaera and a backported 5:18 kernel, seems to have been addressed and solved in kernel 5.19.

Correction: it seems it still isn't fixed in 5.19, at least if I'd had the system running for a while/been hibernated. So have reverted to kernel 5:15 again.

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

Having checked your AX210 is a wi-fi 6E card, while my AX200 is only wi-fi 6.

The AX210 is only supported by linux kernels >= 5.10, i.e. the standard Chimaera kernel.

https://wireless.wiki.kernel.org/en/use … rs/iwlwifi

Nevertheless, even though you say its Beowulf based Linux refracta 5.10.0-0.deb10.16-amd64 is presumably a 5:10 kernel.

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

Which iwlwifi and kernel versions are you using? This is quite a new wifi card compared to beowulf. You may need a backported kernel as well or even an upgrade to Chimaera.

I have a working AX200 card (earlier than yours, which is AX210) on  Chimaera. My ifwlwifi is version 20210315-3.

This is from my dmesg:

dmesg |grep iwlwifi
[    5.797902] iwlwifi 0000:21:00.0: firmware: failed to load iwlwifi-cc-a0-66.ucode (-2)
[    5.797969] iwlwifi 0000:21:00.0: Direct firmware load for iwlwifi-cc-a0-66.ucode failed with error -2
[    5.797979] iwlwifi 0000:21:00.0: firmware: failed to load iwlwifi-cc-a0-65.ucode (-2)
[    5.798003] iwlwifi 0000:21:00.0: Direct firmware load for iwlwifi-cc-a0-65.ucode failed with error -2
[    5.798010] iwlwifi 0000:21:00.0: firmware: failed to load iwlwifi-cc-a0-64.ucode (-2)
[    5.798034] iwlwifi 0000:21:00.0: Direct firmware load for iwlwifi-cc-a0-64.ucode failed with error -2
[    5.798041] iwlwifi 0000:21:00.0: firmware: failed to load iwlwifi-cc-a0-63.ucode (-2)
[    5.798064] iwlwifi 0000:21:00.0: Direct firmware load for iwlwifi-cc-a0-63.ucode failed with error -2
[    5.801899] iwlwifi 0000:21:00.0: firmware: direct-loading firmware iwlwifi-cc-a0-62.ucode
[    5.801904] iwlwifi 0000:21:00.0: api flags index 2 larger than supported by driver
[    5.801910] iwlwifi 0000:21:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.37
[    5.802068] iwlwifi 0000:21:00.0: loaded firmware version 62.49eeb572.0 cc-a0-62.ucode op_mode iwlmvm
[    5.802081] iwlwifi 0000:21:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2)
[    5.870642] iwlwifi 0000:21:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340
[    6.000186] iwlwifi 0000:21:00.0: Detected RF HR B3, rfid=0x10a100
[    6.065031] iwlwifi 0000:21:00.0: base HW address: dc:21:48:57:1b:5b
[12516.990241] (NULL device *): firmware: direct-loading firmware iwlwifi-cc-a0-62.ucode

I note that I finally get my slightly older card running on iwlwifi-cc-a0-62.ucode, which is a higher number than any your system tries to load: iwlwifi-ty-a0-gf-a0-59.ucode down to iwlwifi-ty-a0-gf-a0-39.ucode.

#7 Re: Other Issues » [SOLVED] Zoom in Devuan » 2022-10-03 21:44:54

Well I've no reason to believe that appimage would solve the issue.
And I wouldn't want to start using appimage just to solve this issue given all the issues that all such similar solutions (appimage, flatpack, etc.) bring.

Remember I'm on Chimaera. I only upgraded to backports in the first instance to handle my newish hardware (AMD Zen3 5600G, B550 motherboard) and some issues with suspend/hibernate. If 5.15 works why upgrade further to a newer kernel if that has a regression?

But I an happy to try and pinpoint what that regression is, so that when I do move to a stable Daedalus and no doubt even newer kernel it has been solved.

#8 Re: Other Issues » [SOLVED] Zoom in Devuan » 2022-10-03 18:08:37

Not keen on using appimage.

I did try HOS's suggestion to disable hardware acceleration. That didn't solve the problem.

What does seem to have solved the problem is downgrading my kernel to 5:15 from 5:18 (I needed a backported 5:15+ image as stable 5:10 doesn't address some amdgpu and motherboard chip recognition issues I had).

I can't see any relevant kernel bug reports in 5:16/5:18 or 5:18 so may attempt to at least identify in which kernel the regression occurred and then report it.

I've also found a 'signature' in syslog that occurs while the kernel is glitching:

Sep 19 17:08:35 grendel kernel: [91634.237980] amdgpu 0000:30:00.0: amdgpu: failed to write reg 1a6f4 wait reg 1a706
Sep 19 17:08:56 grendel kernel: [91655.526407] amdgpu 0000:30:00.0: amdgpu: failed to write reg 28b4 wait reg 28c6

This was previously reported in association with a resume bug back in kernel 5:05 that was then solved.

#9 Re: Installation » Installing from USB thumb drive » 2022-10-02 09:57:26

Micronaut wrote:

But when I plugged the USB drive into the machine and tried to get it to install it complained it could not 'mount' the install media. ??? Didn't it already 'mount' the install media if the installer is running

Just too check: can I assume that having plugged in the usb drive you then rebooted, having prioritised the usb drive over the hard disk(s) in the bios?

#10 Re: Other Issues » [SOLVED] Zoom in Devuan » 2022-09-21 14:42:05

Thanks for the suggestion. I'll try that.

#11 Re: Other Issues » [SOLVED] Zoom in Devuan » 2022-09-21 14:22:49

Marjorie wrote:

Currently I'm on the latest 5.11.10 version.
Hhowever recently it [Zoom] become extremely slow starting up, particularly if I've not rebooted the system recently. I'm currently running Chimaera on an AMD 5600G with 16GB RAM and the 5.18.0-0.deb11.4-amd64 kernel.

On my set up at least there does seem a problem with the most recent versions of Zoom.
Start-up is painfully slow, with long pauses while it repaints the screen and meanwhile doesn't respond to the keyboard.
I thought the problem was related to the most recent versions using chromium libraries to write to the screen (signal-desktop uses a similar set-up). I downgraded to an earlier version (5.11.0, downloaded in June) that uses Qt libraries. I thought initially the downgrade sorted the problem but it hasn't. And I'm also now seeing the same problem with signal-desktop.
Hibernating and reawakening (as well the previously mentioned rebooting) does, at least temporarily, restore normal service.
Both Zoom and Signal install in /opt with their own set of libraries. Signal is from the Debian/Devuan repositories.

Any suggestions for what could be causing the problem?

#12 Re: Other Issues » [SOLVED] Zoom in Devuan » 2022-09-14 13:01:35

I've been running Zoom via their site's Debian deb packages since at least June 2020.
Its clearly a 'portable' package (runs on any Debian 9.0+) and installs in /opt.
Download from https://zoom.us/download#client_4meeting
You normally have to check for updates manually as there is no repository. Currently I'm on the latest 5.11.10 version.
Its always worked well, however recently it's become extremely slow starting up, particularly if I've not rebooted the system recently. I'm currently running Chimaera on an AMD 5600G with 16GB RAM and the 5.18.0-0.deb11.4-amd64 kernel.

#13 Re: Other Issues » GRUB update lands at 'grub rescue>' prompt » 2022-09-11 11:36:17

Just for clarification, is this a general problem with the latest upgrade of grub?

I've just been updating my legacy-bios Chimaera installation (using synaptic).
There are lots of upgrades available today, including one to grub-pc, from 2.04-20 to 2:06-3~deb11u1.
I've installed all the other upgrades.
Is this safe to install the grub upgrade or will it just give me a grub rescue> prompt and a headache?

#14 Re: Hardware & System Configuration » [SOLVED] LUKS Full Disk Encryption » 2022-09-11 10:56:35

unixdan22 wrote:

Does hibernate work with a swap partition inside an LVM?

It does on my PC (AMD5600G, Chimaera, emulated legacy boot, no encryption, kernel 5.18.0-0.deb11.4-amd64. RAID1).

I'm still finding hibernation a bit flaky - sometimes it attempt a reboot and I have to kill it with the power button (but then still resumes OK subsequently).

If you were to try to hibernate to a swapfile one obvious, bur solvable, problem is that you would have to make it significantly larger than 256Mb as it has to have space for what's in your RAM).

#16 Re: Hardware & System Configuration » [done] Hibernate not working » 2022-08-25 08:10:37

Have you told the system where swap for hiberation is?

The usual place is in the file /etc/initramfs-tools/conf.d/resume

On my system swap in on a LVM volume, so I have:

marjorie@grendel:~$  cat /etc/initramfs-tools/conf.d/resume
RESUME=/dev/mapper/grendel--vg-grendel--swap

For a non-LVM system this would be:
RESUME=/dev/sdxn

where /dev/sdxn is your swap partition.

You can also specify swap using UUID
RESUME=UUID=

To disable change it to
RESUME=NONE

You will then need to update your initramfs to make it work.

sudo update-initramfs -u
sudo reboot

#17 Re: Other Issues » rsyslogd is using up all my CPU and filling up /var » 2022-08-21 21:32:20

Update: on the messages you are seeing in syslog.

I've now had a look in mine and by comparison I think the ones you are citing may be normal and are simply being repeated when you sleep/resume.

This is what I get on resume from hibernation:

Aug 20 22:43:34 grendel kernel: [63606.742486] ------------[ cut here ]------------
Aug 20 22:43:34 grendel kernel: [63606.742487] WARNING: CPU: 0 PID: 2045 at drivers/iommu/amd/init.c:851 amd_iommu_enable_interrupts+0x32a/0x400
Aug 20 22:43:34 grendel kernel: [63606.742494] Modules linked in: fuse rfcomm ccm cmac algif_hash algif_skcipher af_alg bnep binfmt_misc ip6t_REJECT nf_reject_ipv6 xt_hl ip6_tables ip6t_rt ipt_REJECT nf_reject_ipv4 xt_LOG nf_log_syslog nft_limit xt_limit xt_addrtype xt_tcpudp ip_tables xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_compat x_tables nf_tables nct6687(OE) nfnetlink hwmon_vid firewire_sbp2 firewire_core crc_itu_t msr parport_pc ppdev lp parport intel_rapl_msr intel_rapl_common edac_mce_amd iwlmvm btusb btrtl wmi_bmof btbcm btintel kvm mac80211 btmtk bluetooth irqbypass crc32_pclmul snd_hda_codec_realtek libarc4 ghash_clmulni_intel snd_hda_codec_generic ledtrig_audio iwlwifi aesni_intel uvcvideo crypto_simd cryptd snd_hda_codec_hdmi videobuf2_vmalloc snd_usb_audio videobuf2_memops jitterentropy_rng videobuf2_v4l2 videobuf2_common snd_hda_intel rapl pcspkr sha512_ssse3 snd_intel_dspcfg videodev k10temp snd_usbmidi_lib snd_intel_sdw_acpi sha512_generic snd_hda_codec cfg80211 snd_rawmidi
Aug 20 22:43:34 grendel kernel: [63606.742531]  snd_seq_device ctr mc snd_hda_core joydev drbg r8169 snd_hwdep ansi_cprng snd_pcm sp5100_tco realtek watchdog ecdh_generic snd_timer mdio_devres ecc i2c_piix4 libphy snd ccp rfkill soundcore sr_mod rng_core cdrom sg video button acpi_cpufreq wmi amd_pmc ext4 crc16 mbcache jbd2 raid10 raid456 libcrc32c crc32c_generic async_raid6_recov async_memcpy async_pq async_xor xor async_tx raid6_pq raid0 multipath linear dm_mod evdev raid1 md_mod hid_generic amdgpu sd_mod usbhid drm_ttm_helper t10_pi ttm hid gpu_sched crc64_rocksoft crc64 crc_t10dif i2c_algo_bit crct10dif_generic drm_dp_helper drm_kms_helper ahci libahci xhci_pci drm libata xhci_hcd usbcore scsi_mod cec crct10dif_pclmul crct10dif_common crc32c_intel rc_core usb_common scsi_common gpio_amdpt gpio_generic
Aug 20 22:43:34 grendel kernel: [63606.742566] CPU: 0 PID: 2045 Comm: elogind-daemon Tainted: G        W  OE     5.18.0-0.bpo.1-amd64 #1  Debian 5.18.2-1~bpo11+1
Aug 20 22:43:34 grendel kernel: [63606.742568] Hardware name: Micro-Star International Co., Ltd. MS-7C56/MPG B550 GAMING PLUS (MS-7C56), BIOS 1.50 01/14/2021
Aug 20 22:43:34 grendel kernel: [63606.742570] RIP: 0010:amd_iommu_enable_interrupts+0x32a/0x400
Aug 20 22:43:34 grendel kernel: [63606.742572] Code: ff ff 48 8b 7b 18 89 04 24 e8 72 e6 ef ff 8b 04 24 e9 78 fd ff ff 0f 0b 48 8b 1b 48 81 fb 10 ad 1f 90 0f 85 33 fd ff ff eb 96 <0f> 0b 48 8b 1b 48 81 fb 10 ad 1f 90 0f 85 1f fd ff ff eb 82 31 c9
Aug 20 22:43:34 grendel kernel: [63606.742573] RSP: 0018:ffffbf3ac3493cd0 EFLAGS: 00010046
Aug 20 22:43:34 grendel kernel: [63606.742575] RAX: 0000001ff3504f4a RBX: ffff9ebd8004b000 RCX: 0000000000000000
Aug 20 22:43:34 grendel kernel: [63606.742576] RDX: 000000000000a12e RSI: 00000000000096d9 RDI: 0000001ff34fae1c
Aug 20 22:43:34 grendel kernel: [63606.742577] RBP: 0000000000000000 R08: 0000000000000000 R09: 000000000000002f
Aug 20 22:43:34 grendel kernel: [63606.742577] R10: 0000000000000000 R11: ffff9ec02e2928d8 R12: 0000000080000000
Aug 20 22:43:34 grendel kernel: [63606.742578] R13: 000ffffffffffff8 R14: 0800000000000000 R15: 0008000000000000
Aug 20 22:43:34 grendel kernel: [63606.742579] FS:  00007f06861fe980(0000) GS:ffff9ec01f800000(0000) knlGS:0000000000000000
Aug 20 22:43:34 grendel kernel: [63606.742580] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 20 22:43:34 grendel kernel: [63606.742581] CR2: 00007f82300032f6 CR3: 000000010869c000 CR4: 0000000000750ef0
Aug 20 22:43:34 grendel kernel: [63606.742582] PKRU: 55555554
Aug 20 22:43:34 grendel kernel: [63606.742583] Call Trace:
Aug 20 22:43:34 grendel kernel: [63606.742584]  <TASK>
Aug 20 22:43:34 grendel kernel: [63606.742587]  ? memcpy_toio+0x1c/0xb0
Aug 20 22:43:34 grendel kernel: [63606.742591]  amd_iommu_reenable+0x39/0x40
Aug 20 22:43:34 grendel kernel: [63606.742592]  lapic_resume+0x279/0x2d0
Aug 20 22:43:34 grendel kernel: [63606.742595]  syscore_resume+0x4a/0x160
Aug 20 22:43:34 grendel kernel: [63606.742597]  hibernation_snapshot+0x227/0x490
Aug 20 22:43:34 grendel kernel: [63606.742601]  hibernate.cold+0x8b/0x206
Aug 20 22:43:34 grendel kernel: [63606.742604]  state_store+0xcb/0xd0
Aug 20 22:43:34 grendel kernel: [63606.742606]  kernfs_fop_write_iter+0x124/0x1b0
Aug 20 22:43:34 grendel kernel: [63606.742609]  new_sync_write+0x109/0x190
Aug 20 22:43:34 grendel kernel: [63606.742612]  vfs_write+0x20d/0x290
Aug 20 22:43:34 grendel kernel: [63606.742614]  ksys_write+0x5f/0xe0
Aug 20 22:43:34 grendel kernel: [63606.742615]  do_syscall_64+0x3b/0xc0
Aug 20 22:43:34 grendel kernel: [63606.742618]  entry_SYSCALL_64_after_hwframe+0x44/0xae
Aug 20 22:43:34 grendel kernel: [63606.742620] RIP: 0033:0x7f0686413f6f
Aug 20 22:43:34 grendel kernel: [63606.742626] Code: Unable to access opcode bytes at RIP 0x7f0686413f45.
Aug 20 22:43:34 grendel kernel: [63606.742626] RSP: 002b:00007fff5a227fc0 EFLAGS: 00000293 ORIG_RAX: 0000000000000001
Aug 20 22:43:34 grendel kernel: [63606.742628] RAX: ffffffffffffffda RBX: 0000000000000005 RCX: 00007f0686413f6f
Aug 20 22:43:34 grendel kernel: [63606.742628] RDX: 0000000000000005 RSI: 00007fff5a2280d0 RDI: 0000000000000011
Aug 20 22:43:34 grendel kernel: [63606.742629] RBP: 00007fff5a2280d0 R08: 0000000000000000 R09: 00007fff5a2271f0
Aug 20 22:43:34 grendel kernel: [63606.742630] R10: 00007fff5a2270a4 R11: 0000000000000293 R12: 0000000000000005
Aug 20 22:43:34 grendel kernel: [63606.742630] R13: 00005612510ba2a0 R14: 0000000000000005 R15: 00007f06864e48a0
Aug 20 22:43:34 grendel kernel: [63606.742632]  </TASK>
Aug 20 22:43:34 grendel kernel: [63606.742632] ---[ end trace 0000000000000000 ]---
Aug 20 22:43:34 grendel kernel: [63607.283878] LVT offset 0 assigned for vector 0x400
Aug 20 22:43:34 grendel kernel: [63607.284206] Enabling non-boot CPUs ...

So I suspect whatever is intermittently spamming your syslog is something else.

#18 Re: Other Issues » rsyslogd is using up all my CPU and filling up /var » 2022-08-21 16:37:29

I'm afraid I've no experience of this sort of error: It seems the kernel is throwing some sort of exception and triggering a trace. Could be something specific to your acer or your kernel version. I do note that the bios is from 2007 - might be worth checking if there is a newer version.

Maybe someone else can make a suggestion?

Meanwhile you could make changes to logrotate to limit the size of the files being generated:
1) Switch from weekly to daily rotations.
2) Remove the delaycompress command so gzip is done immediately
or I would suggest:
3) Change from a periodic (hourly/daily/weekly/monthly) to using a log file size or maxsize parameter. This would force log rotation when the log gets to a specific size. Maxsize works in combination with periodic rotation, size instead of.
You might want to do this just for the messages, kern and syslog log files, thoug I suspect any reasonably generous maxsize wont limit other log files too much.
You can look up the definitions of these parameters in man logrotate.

The downside to doing this is that you obviously have fewer logs available to debug problems.

#19 Re: Other Issues » rsyslogd is using up all my CPU and filling up /var » 2022-08-21 13:35:22

OK, logrotate is working as intended.

If you suspend or hibernate and resume then it's probably that anacron will only do it's daily execute and call logrotate when you resume.

However it looks likely that some process has 'spammed' your systems logs between 31 July 31 and 7 August: 65Mb of compressed log files in that period is impressive - obviously it would have been much more when it happened and the log file was uncompressed.

I suggest you have a look in /var/log/syslog.3.gz for what is causing the problem. I assume that whatever it is is triggering happens intermittently if the partitions are filling up repeatedly.

#20 Re: Other Issues » rsyslogd is using up all my CPU and filling up /var » 2022-08-21 12:30:00

Thanks. That's not the problem then.

Is logrotate working properly?

If I look in /var/log for messages (for example) I see:

marjorie@grendel:~$ ls -alF /var/log/messages* 
-rw-r----- 1 root adm 224595 Aug 21 13:07 /var/log/messages
-rw-r----- 1 root adm 992245 Aug 18 17:24 /var/log/messages.1
-rw-r----- 1 root adm 159582 Aug  8 21:47 /var/log/messages.2.gz
-rw-r----- 1 root adm  63014 Jul 23 10:18 /var/log/messages.3.gz
-rw-r----- 1 root adm 110513 Jul 13 21:37 /var/log/messages.4.gz

Obviously in your case what you see may depend on when messages is logrotated, but the size and number of archives should be similar.

You might also want to check the syslog and kern log files for size and dates.

Also check that you have a logrotate cron job: mines run daily by anacron so I have:

marjorie@grendel:~$ ls -alF /etc/cron.daily/logrotate
-rwxr-xr-x 1 root root 377 Aug 28  2018 /etc/cron.daily/logrotate*

#21 Re: Other Issues » rsyslogd is using up all my CPU and filling up /var » 2022-08-20 19:51:03

Have you got your logrotate set up properly? You should be limiting how long/how many log messages you keep.

Can you report the content of your /etc/logrotate.d/rsyslog.

Mine looks like this:

/var/log/syslog
/var/log/mail.info
/var/log/mail.warn
/var/log/mail.err
/var/log/mail.log
/var/log/daemon.log
/var/log/kern.log
/var/log/auth.log
/var/log/user.log
/var/log/lpr.log
/var/log/cron.log
/var/log/debug
/var/log/messages
{
	rotate 4
	weekly
	missingok
	notifempty
	compress
	delaycompress
	sharedscripts
	postrotate
		/usr/lib/rsyslog/rsyslog-rotate
	endscript
}

#22 Re: Desktop and Multimedia » Alternative browser for Devuan/Debian - Brave » 2022-08-06 18:11:53

Hi Alex,

no I don't think it's that:
the curl command on the website (that I copied and pasted and executed, sorry should have also listed in my message) uses https://...
For some reason the error message refer to http://..
Changing the curl command to use http://.. results in the same error message when I run sudo apt update.

#23 Re: Desktop and Multimedia » Alternative browser for Devuan/Debian - Brave » 2022-08-06 10:57:16

I would be interested in having Ungoogled Chromium since I use firefox-esr with security/privacy extensions and there are a small number of commercial websites that don't play ball. I'm not keen on using the standard chromium deb in the Chimaera repositories, though I did install it on a spare PC for a guest who relies on his saved google setting (bookmarks, etc).

However having gone to https://github.com/ungoogled-software/u … d-chromium I tried to follow the download instructions here:
https://github.com/ungoogled-software/u … ium-debian (since there isn't a devuan repository) and get stuck at the apt update stage:

marjorie@grendel:~$ sudo apt update
Hit:1 https://updates.signal.org/desktop/apt xenial InRelease
Get:2 http://download.opensuse.org/repositories/home:/ungoogled_chromium/Debian_Bullseye  InRelease [1,565 B]               
Err:2 http://download.opensuse.org/repositories/home:/ungoogled_chromium/Debian_Bullseye  InRelease                                
  The following signatures were invalid: EXPKEYSIG 02456C79B2FD48BF home:ungoogled_chromium OBS Project <home:ungoogled_chromium@build.opensuse.org>
Hit:3 http://deb.devuan.org/merged chimaera InRelease                                                 
Hit:4 http://deb.devuan.org/merged chimaera-updates InRelease                                         
Hit:5 http://deb.devuan.org/merged chimaera-security InRelease
Hit:6 https://debian.rickslab.com/gpu-utils eddore InRelease
Hit:7 http://deb.devuan.org/merged chimaera-backports InRelease
Reading package lists... Done
W: GPG error: http://download.opensuse.org/repositories/home:/ungoogled_chromium/Debian_Bullseye  InRelease: The following signatures were invalid: EXPKEYSIG 02456C79B2FD48BF home:ungoogled_chromium OBS Project <home:ungoogled_chromium@build.opensuse.org>
E: The repository 'http://download.opensuse.org/repositories/home:/ungoogled_chromium/Debian_Bullseye  InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

#24 Re: Installation » moving /-partition to LVM after installation (Devuan 4) » 2022-07-26 13:01:47

Just checking.

Can you post the code for your
/etc/fstab,
the primary menuentry from /etc/boot/grub/grub.cfg
the results of sudo blkid
and the results of sudo fdisk -l?

I'm wondering whether with your copying root partition contents around the UUID have got misaligned or you are using the wrong /dev/ (LVM vols. are usually on /dev/mapper/)

#25 Re: Other Issues » "Temporary failure resolving 'deb.devuan.org' " » 2022-07-20 14:09:40

Grumpy wrote:

Both laptops also have a flavour of Ubuntu installed with DNS being looped in some way by systemd (127.0.0.63)  I think. I have no idea about systemd, Both Ubuntu installs resolved deb.devuan.org.
Any ideas?

Indeed, systemd in it's usual feature creep tries to provide DNS resolution (and just about anything else) as well as init functions in this case with systemd-resolved.
Of course you don't find it on Devuan.
I use dsncrypt-proxy which uses a similar redirection to 127.0.0.1#53 to provide a local first-point-of-call for DNS (Port 53 is the default port for DNS queries). Along with local caching the proxy then looks up DNS on DNS servers out there on the internet. In the case of dnscrypt-proxy these are dns-over-https or dnscrypt servers and mine polls for ones that are DNSSEC and local.
In dnscrypt-proxy I can block evil DNS and IP. I don't know whether systemd-resolved has this capability, however clearly a systemd OS would be rather foolish to use deb.devuan.org as its repositories are systemd-free.

Board footer

Forum Software