The officially official Devuan Forum!

You are not logged in.

#1351 Re: News & Announcements » Beowulf Beta is here! » 2020-06-22 12:34:06

danista wrote:

The iso image contain pae kernel headers instead of non-pae. I reported this in the post above. (

Thanks for clarifying. I misunderstood. I filed a bug report so it can get fixed in the point-release.
https://bugs.devuan.org/cgi/bugreport.cgi?bug=487

#1352 Re: News & Announcements » Beowulf Beta is here! » 2020-06-21 18:12:27

danista wrote:
fsmithred wrote:

The non-pae kernel is default for those with old machines. The linux-headers package is in the iso, but it does not get installed by default. That's standard for debian and consequently for devuan.
.

I'm upset that the bug was not fixed in the final version of the disk Devuan GNU/Linux 3.0 (beowulf) i386 - desktop 20200526

I'm confused. What did you want to happen? What are you calling a bug?

#1353 Re: Desktop and Multimedia » no sound after beowulf upgrade » 2020-06-21 09:56:02

Pulseaudio is still around in beowulf. The difference is that if you're using systemd, you should not let pulseaudio autospawn itself, because systemd will do that for you. Since this is devuan and there is no systemd to handle everything, pulseaudio has to autospawn itself.

PA is removable if you prefer to be without it.

#1354 Installation » desktop-live encrypted install does not boot » 2020-06-20 13:21:40

fsmithred
Replies: 1

Encrypted root partition with unencrypted /boot, bios boot, installed from desktop-live does not boot.

It seems that grub-pc package no longer runs a configure dialog when you install it with 'dpkg -i' which is what the desktop-live wants to do for a bios install. This doesn't seem to be a problem with unencrypted root partition and a single hard drive (virtual). In that case, grub gets installed to the MBR of /dev/sda without asking you. I don't think it's a problem with full-disk encryption, but it's been at least a couple months since I've done one of those.

There are two possible solutions:
1. Use the cli installer instead of the graphical. Run 'refractainstaller' from a root terminal (or with sudo).
or
2. If you really want to use the graphical installer, edit /usr/bin/refractainstaller-yad to uncomment line 1762 to enable the choose_grub function after the grub-pc package gets installed.

I think someone may have reported this when we were testing the betas, but I don't feel like looking for it right now. I did file a bug report: https://bugs.devuan.org/cgi/bugreport.cgi?bug=485

#1355 Re: Devuan Derivatives » Can live isos be burned to optical media? » 2020-06-16 01:38:42

There's a bug report for the same issue, not a live-iso, but it's the same problem.
Put the sleep after start-stop-daemon and right before 'udevadm trigger --action=add'.
https://bugs.devuan.org/cgi/bugreport.cgi?bug=483

#1356 Re: Other Issues » [SOLVED] Security update delays » 2020-06-13 22:45:04

Thanks. For some reason, security updates on pkgmaster are going to *-proposed-updates. We're not yet sure why. Until then you can add ascii-proposed-updates or beowulf-proposed-updtates, whichever is appropriate.

e.g.

deb http://deb.devuan.org/merged ascii-proposed-updates main contrib non-free

#1357 Re: Hardware & System Configuration » Nonpersistent and encrypted image » 2020-06-13 16:53:32

Haven't done it, but I have some thoughts. I normally do an encrypted persistent volume for live-usb systems. The squashfs is not encrypted, but it is read-only, so it's pretty safe.

It might be possible to encrypt the partition that holds the squashfs and use grub as the bootloader. You'd have to edit the grub.cfg to add the same stuff that gets added when you do full-disk encryption. Set the usb up like a multi-boot live usb, except make the first partition a luks-encrypted volume with ext4 filesystem.

#1358 Re: Off-topic » system info practice script » 2020-06-13 14:22:43

Works here on my beowulf. I didn't feel like installing wmctrl, so I changed that line to

printf  $titles "wm:" ; basename $(cat /etc/X11/default-display-manager)

#1359 Re: Installation » Boot menu says "Debian" instead of "Devuan" » 2020-06-09 23:09:16

I still don't get "If you're booting UEFI mode, you will also need to remove grub-efi-amd64-signed and just use grub-efi-amd64.", though. Any explanation what to do or what is meant appreciated.

Are you using secure boot?
Are you unable to boot your os?

If your answer to the second question is 'yes' then you will need to do something. We will help you figure that out. Otherwise, you can ignore it.

In previous testing, the bootloader had to be named 'debian' if you used the signed grub package. Otherwise, it could not find the bootloader, because $prefix was hard-coded as EFI/debian. I don't know if that's still true in beowulf.

#1360 Re: Devuan Derivatives » [NEW]-FluXuan Linux-[RELEASE] » 2020-06-09 22:46:54

Refractainstaller has only been used on x86 architectures. I don't know what changes you'd need to make for arm.

If you wanted to use an existing fluxuan iso with the pi-imager, I think you would unpack the iso, then unpack filesystem.squashfs and use that in place of the debootstrapped system. Then make whatever changes you need to make to it.

Edit: Of course, that won't work. Packages are for the wrong arch.

#1361 Re: Installation » Boot menu says "Debian" instead of "Devuan" » 2020-06-09 22:25:10

lsb-base and lsb-release in ascii are devuanized packages. You can tell because 'devuan' is in the version. In beowulf, chimaera and ceres, we're using the unchanged debian versions.

The code you're looking for might be here: https://salsa.debian.org/debian/lsb

#1362 Re: Installation » Boot menu says "Debian" instead of "Devuan" » 2020-06-09 14:40:32

Changing the 'ID=' line in /etc/os-release will also change the name of the bootloader created by 'grub-install'.

Correction:
With ID=mydevuan, grub-install creates a bootloader at /boot/efi/EFI/mydevuan
With ID=devuan, it does not. It just went back to using /boot/efi/EFI/debian.

So, like I said before, I probably can't explain it.

#1363 Re: Installation » Boot menu says "Debian" instead of "Devuan" » 2020-06-09 13:47:11

jdev wrote:

Could someone please explain what exactly needs to be done?

Probably not, but I'll try. I think the behavior of grub has changed since that was tested for the release notes. To change it in the boot menu, you can either change it in /etc/default/grub or /etc/os-release and re-run update-grub.

Like this works:

GRUB_DISTRIBUTOR=Devuan

Changing the 'ID=' line in /etc/os-release will also change the name of the bootloader created by 'grub-install'. I don't think /etc/default/grub will do that. Correct me if you find otherwise.

Changing it in /etc/lsb-release works, too, but you won't have that file unless you created it. Or maybe I created it for you, if you're running Refracta.

If you have secure boot enabled, I don't know what will happen. Some time ago, the bootloader directory on the efi partition needed to be named 'debian' if you were using the signed version of grub-efi-amd64, even without secure boot enabled. That appears to have changed in chimaera. Either that or my motherboard is lying to me about secure boot. That's a distinct possibility, since manufacturers can seem to agree on uefi implementations.

#1364 Re: Other Issues » [solved] Refracta Installer - disable auto login after installation » 2020-06-08 13:25:40

cp /usr/lib/refractainstaller/inittab.debian /etc/inittab

That's the easiest way.

#1365 Re: Forum Feedback » Why Fie? » 2020-06-07 19:22:05

Welcome to Devuan.

You've been around linux long enough to see that every release gets bigger and more hungry for resources. Part of the reason we left the graphical installer out of the installer isos was to leave more room for applications that might be needed when installing without a network connection.

If you've used graphical installers on other distros, you might be disappointed with the debian-installer's rendition. The ncurses variety that you saw is actually easier to use - it requires less motion.

You can see for yourself. There's a graphical installer in the mini.iso on this page.
https://pkgmaster.devuan.org/devuan/dis … tboot/gtk/

The mini.isos get made when the installer gets rebuilt. They're mainly for testing, and they require a wired network connection to get even the most minimal working system.

The live isos use a different installer that just copies the system from the media to the hard drive. It takes about 10 minutes, but you don't get to choose the software.

.

#1366 Re: Installation » quick note on chimaera installs (attn: fsmithred) » 2020-06-07 17:22:43

Thanks. I just finished a dist-upgrade from beowulf to chimaera on a laptop. Had some trouble with conflicts and had to remove libpolkit-backend-1-0 manually (it no longer exists) and upgrade one of the libpolkit packages manually. Also used a combination of apt and aptitude to get through it. I didn't take notes, so I don't have instructions for anyone.

This was with xfce. I think it was a refracta-ascii that I upgraded to beowulf a year ago. Now it's chimaera and seems to be working ok.

#1367 Re: Hardware & System Configuration » AMDGPU-PRO 20.10 on Devuan Beowulf with an AMD RX5600 » 2020-06-06 16:22:02

A condensed version with the essentials is always good, especially when I don't have to do it. Thanks. smile

#1368 Re: Hardware & System Configuration » Shutdown encrypted LVM on Beowulf » 2020-06-06 15:17:37

The copy of cryptdisks-functions that I linked has two patches applied to it. One for lvm and one for plain luks-encrypted partitions.

For jessie and ascii, the file is cryptdisks.functions, not cryptidisks-functions. The files are very different, but the same changes work. I'm sure it's documented in several threads on this forum, probably including this one.

We did not fork cryptsetup, so you'll get the shutdown delay no matter how you install the system.

#1369 Re: Hardware & System Configuration » Shutdown encrypted LVM on Beowulf » 2020-06-06 10:59:42

Vizitor wrote:
Stopping remaining crypt disks...root_fs (busy)...root_fs (busy).....root_fs (busy).....root_fs (busy).....root_fs (busy).....root_fs (busy)...... 

hmm

Replace /lib/cryptsetup/cryptdisks-functions with the patched copy I linked above.

#1371 Re: Installation » upgrade to chimaera » 2020-06-05 16:11:50

Just this in sources.list. There's no -security or -updates (or anything else) for chimaera or ceres. You could add contrib and non-free if you want.

deb http://deb.devuan.org/merged chimaera main

#1372 Re: Hardware & System Configuration » Shutdown encrypted LVM on Beowulf » 2020-06-05 10:42:14

Here's a copy of patched /lib/cryptsetup/cryptdisks-functions for beowulf:
https://git.devuan.org/devuan/cryptsetu … -functions
This will eventually be packaged and added to the devuan repo.

#1373 Re: Desktop and Multimedia » AmaroK » 2020-06-05 10:15:52

There's no amarok in buster, therefore there is no amarok in beowulf. Try stevepusser's build. I recommend downloading the packages to install manually rather than adding a foreign repo.
http://forums.debian.net/viewtopic.php? … dd5b92d7be

#1374 Hardware & System Configuration » AMDGPU-PRO 20.10 on Devuan Beowulf with an AMD RX5600 » 2020-06-04 16:44:22

fsmithred
Replies: 6

From nemo in #devuan on freenode irc:

AMDGPU-PRO 20.10 on Devuan Beowulf with an AMD RX5600

The fundamental problem is that the open source drivers, even in Beowulf Backports do not appear to yet support this released card. AMD *does* have a closed source driver for Debian. It has a few gotchas however that I'll try to document here.

The first is that their installer checks for a "legit" debian based distro. For them, that's an ID of debian, mint, or ubuntu (this was an improvement over 16.40 that only supported ubuntu). Adding |devuan to the amdgpu-install script in the os_release() section is fairly trivial.

Once that's done, the install proceeds smoothly. It creates a new file repo for the .debs it installed.

The problems start if you attempt to reboot. The symptoms I experienced were that the AMDGPU-PRO 20.10 appears to use a Video ABI of 23 (this is visible on stderr if you startx) and causes crashes in Xorg (visible in log) causing fallback in Xorg and an endless flickering loop probably 'cause kernel has wildly different stuff loaded.

The only fix I could find was to downgrade Xorg from 1.20 to 1.19 to match the video ABI. ascii-xorg.pref does this. You just toss it into your /etc/apt/preferences.d, append deb http://deb.devuan.org/merged ascii main non-free contrib sources.list, and update/upgrade.

The downside. Two meta packages, task-desktop and task-mate-desktop that I had installed (and probably related desktop metas) seem to force depend on 1.20 for some reason (why, no idea - you'd think that'd be a lower dependency if necessary) and have to be removed. This *will* confuse apt autoremove. In my case I was able to manage things by explicitly installing libreoffice.

Once you've done that and rebooted, everything seems to work fine! Graphics are working beautifully, and I assume the pro package lets me play around with ML/opencl stuff too, but haven't tried that yet.

#1375 Re: News & Announcements » Updating Sources to Beowulf stable » 2020-06-01 22:56:57

It's not a bug. It's just that events are happening slightly out of sequence. Official announcement is coming soon. Say yes. If you were already up to date, you won't see any new packages.

Board footer

Forum Software