The officially official Devuan Forum!

You are not logged in.

#1 Re: Other Issues » Preliminary excalibur desktop-live isos need testing » 2025-04-05 05:30:01

Regarding mc - I think if we have space for libreoffice, we can afford to include mc.
It may be added to refracta blacklist so as not to persist to user desktops.

Slackware live images include mc by default.

#2 Re: Other Issues » Preliminary excalibur desktop-live isos need testing » 2025-04-05 05:28:29

Just tested a beowulf and a daedalus live images -
Tty autologin works on both of them - there's a working command line of ttys 1-6, already logged on.
Mc output is garbled on both of them, in tty, unlike on desktop, where it works.

So on excalibur it's the autologin on tty that doesn't work. Ideal is to keep same behaviour as previous versions, i.e. autologin.
But a working login prompt is infinitely better than a black screen that doesn't respond to anything.

@fsmithred, please clarify, were you able to reproduce the tty non-working console problem on your hardware?

The xfconf-query command did not work for me.

I have a feeling this problem may resolve itself on it's own (i.e. get fixed upstream) as we get closer to release.

But, for now: where exactly does xfce store the desktop background info? Is it a conf file, or some dconf/registry kind of thing?
Also, I think we should pay attention to "apply to all workspaces" checkbox in the desktop background selection screen.

Worst case, dirty and ugly but probably working hack: replace the file with the xfce default wallpaper with the devuan one :-)

#3 Re: Other Issues » Preliminary excalibur desktop-live isos need testing » 2025-04-04 13:48:54

Add 'nottyautologin' and you will boot to the desktop with tty1-6 available with ctrl-alt-fn.

Yes, this works and gives the behaviour I expected from it - autologin to desktop, but all ttys are available for login in the background.
This should be the default behaviour, no?

I had problems with launching mc in tty, VERY garbled text output.
Launching it with LC_ALL=c mc fixed it.

BTW if it were up to me, I would probably include mc on the live cd.

#4 Re: Other Issues » Preliminary excalibur desktop-live isos need testing » 2025-04-04 10:34:52

Regarding daedalus - that's not an urgent problem or something. It's just that I was always able to find kernel headers of appropriate version in the live image, from jessie to chimaera, and also now on the excalibur preview. Just keep that in mind IF you're going to make a point release of daedalus for some more serious reason, try and make sure the kernel is of a version that has matching headers in the repos.

I'll make a live usb and boot on hardware to investigate the VT problem.

That may be a good idea. If you do, please report the results in this thread.

I was able to get to the command line by booting to runlevel 1, but not in any other way.

#5 Re: Other Issues » Preliminary excalibur desktop-live isos need testing » 2025-04-04 05:09:48

Slightly offtop, different version - I couldn't build zfs-dkms in daedalus live iso session. Or, rather, the modules got build, but for a wrong kernel version.
This is because kernel is something like 6.1.0-10, and the earliest headers available in the repos (that I could find) are something like 6.1.0-20-something.

Any way to get an earlier version of headers? Or do I have to download latest daedalus live image?

Also the command "fc-match monospace" return "deja vu sans mono" on all versions (including the excalibur preview), but on daedalus it return "noto sans mono", which shouldn't be the case, in my opinion.

#6 Re: Other Issues » Preliminary excalibur desktop-live isos need testing » 2025-04-04 05:06:00

Grabbed the new iso.

The (null) plugin error does not happen anymore.

Managed to build zfs and import the pools - had to manually install the kernel headers of the appropriate version, they are available in the repo, but not listed in the requirements for zfs-dkms, I think, and they WERE required and thus got auto-installed in previous versions. This is quite a big test, if this worked, means system is in a good shape already.

Have no idea why the wallpaper get auto-covered with the default xfce one. I right clicked on desktop, and it shows all the devuan ones, and an appropriate dark-blue one is even selected/highlighted, but still the wallpaper gets auto-changed. If this is the biggest problem, I wouldn't worry about it too much until we're farther in the freeze-cycle.

The biggest "WTF" for me is:
Why the hell I don't have a command line in ctrl-alt-f1, and ctrl-alt-f2 up to ctrl-alt-f6 are black screens ?!

#7 Re: Other Issues » Preliminary excalibur desktop-live isos need testing » 2025-04-04 02:58:15

Hi @fsmithred, thanks for you replies here.

I am wget'ting the new iso right now and will test it.

Regarding zfs - don't worry too much about it, it's not a hard requirement for devuan specifically. It may become a somewhat hard requirement if the equivalent debian live iso can do it but the devuan one can't. But we're too early in the freeze cycle to do extensive tests like that, I think.

BUT I was always able to do it in the live iso, since jessie. Sometimes I do have to heck around a bit before I get it to work.

The live isos have the live-tools package installed which replaces update-initramfs with one that won't update in the live session. You could try uninstalling live-tools first and then see if it works. Or, if you get to call update-initramfs manually during the zfs install, call the original update-initramfs. It's there under a slightly modified name -
/usr/sbin/update-initramfs.orig.initramfs-tools

This is useful info, but I have one follow-up question here: has anything changed specifically with the update-initramfs functionality since daedalus live isos?

#8 Re: Other Issues » Preliminary excalibur desktop-live isos need testing » 2025-04-02 04:12:17

Using this iso:

6fe3b7ad120e7afdf49cb6bcbe21be0dc27bbe65835db7f063517655fed31817  devuan_excalibur_6.0-preview-2025-03-22_amd64_desktop-live.iso

Iso on hdd, grub entry to boot it:

menuentry "devuan_excalibur_6.0-preview-2025-03-22" 
{
    insmod part_gpt
    search --no-floppy --label linux_iso --set root
    set isofile="/devuan_excalibur_6.0-preview-2025-03-22_amd64_desktop-live.iso"
    loopback loop ($root)$isofile
    linux (loop)/live/vmlinuz boot=live fromiso=/dev/disk/by-label/linux_iso$isofile username=devuan apparmor=0
    initrd (loop)/live/initrd.img
}

Equivalent entries work well for all earlier devuan versions.

Just tested it and I do get the (null) plugin error initially. Have to click "remove", or click "quit". Clicking quit removes the panel, I then have to open terminal by right-clicking on desktop, and manually running the panel again.

If I log out and then back in through the lightdm login screen as "devuan" user, the error doesn't happen.

One time the screen froze, no mouse movement or anything, though I could see hdd still working. Only hard power off helped.

I only get Ctrl-Alt-F1 screen where I see the boot log, but no login prompt, and the Ctrl-Alt-F7 screen with X.
Ctrl-Alt-F{2,3,4,5,6} screens are not available. So there's no possibility to log in using just the console.

I had problems accessing deb.devuan.org, but that's probably a network problem, not a devuan one. Fixed by specifying us.deb.devuan.org in sources.list.

Couldn't build zfs packages in the live session, it tried to install zfs-initramfs, but couldn't, told me something like "running in live environment, file system is readonly, so can't modify initramfs".  And withoud that package, other packages do not install.
Again, probably not a devuan problem, but I could always build zfs packages in devuan live sessions before. Maybe will retry with "toram=1" to have a proper read-write root fs.

Other than that, video device works fine, network works fine, so it's usable.

That's it for the moment.

#9 Re: Installation » [SOLVED] Daedalus live-image - can't boot iso on hd without manual intervention » 2022-12-12 16:00:24

aluma wrote:

@dev-1-dash-1
Maybe I'm wrong, but there is a mistake in your very first post.

Thank you for trying to help.
But you are wrong indeed.
See post #5 from this thread.
Problem is not in my grub entry, it works exactly as it needs to.

You can try booting the iso from hdd yourself, with or without "apparmor=0" parameter, and report your experiences.

This thread is marked solved for now, will keep an eye out for future versions.

#10 Re: Installation » [SOLVED] Beowulf's debootstrap doesn't contain "daedalus" script » 2022-12-12 01:51:55

ralph.ronnquist wrote:

The name of the link is used to nominate the "suite" being loaded.

Well, that much is obvious indeed.

Let's mark this one solved.

#11 Re: Installation » [SOLVED] Beowulf's debootstrap doesn't contain "daedalus" script » 2022-12-12 00:41:00

ralph.ronnquist wrote:

Note that all Devuan scripts are links to the ceres script. E.g.

/usr/share/debootstrap/scripts/daedalus -> ceres

You'll need to set that.

Thanks for the reply.

Does the actual link name (i.e. "daedalus" in this case) have any effect on the result, or I can just call it "qwiehpjadshflakjhds", link it to ceres, and it will install the same testing/ceres system?

Also, is there any difference between, say, creating a "daedalus" link on my beowulf system, and getting a later (from chimaera) version of debootstrap and using that? I usually use the latter approach.

#12 Re: Installation » [SOLVED] Daedalus live-image - can't boot iso on hd without manual intervention » 2022-12-11 22:22:23

dzz wrote:

? It boots here with or without "apparmor=0" ..

It most certainly doesn't boot here without "apparmor=0". I just tried it again.

I always found "findiso" simpler to configure than "fromiso"..

Irrelevant. Tried both. Makes no difference, unlike apparmor parameter.

menuentry "devuan5 preview" {
	insmod part_gpt
	set isofile='(hd0,gpt7)/devuan_daedalus_5.0.preview_20221022_amd64_desktop-live.iso'
	loopback loop $isofile
	linux (loop)/live/vmlinuz boot=live tzdata=Europe/London locales=en_GB.UTF-8 username=devuan findiso=/devuan_daedalus_5.0.preview_20221022_amd64_desktop-live.iso
	initrd (loop)/live/initrd.img
	}

If you'd like to kick the thread a little bit more, we can try and find the difference that makes the difference. On first glance:
1) You have gpt partition table, I have msdos.
2) I don't have tzdata param

But I consider this "solved" because a real live image, when burned to usb/dvd, will use apparmor=0 param. Thus I am replicating  a real live boot with this, and since it seems to work as intended, case should be closed for now.

#13 Re: Installation » [SOLVED] Daedalus live-image - can't boot iso on hd without manual intervention » 2022-12-11 21:21:26

Adding the boot parameter apparmor=0 allows the system to boot.

In jessie and all the way up to chimaera, this wasn't neccessary, but it is now.

#14 Re: Installation » [SOLVED] Daedalus live-image - can't boot iso on hd without manual intervention » 2022-12-11 18:47:38

Head_on_a_Stick wrote:

EDIT: btw hd1,9 in GRUB translates to /dev/sdb9. hd0,9 would be better but the UUID is the best approach IMO.

Nice try. :-D

I boot from sdb by default (set in bios).
Thus hd1,9 becomes "the other hd". It works for all other distros, I've tested it extensively . Also, like I've said grub can get the the kernel and initrd from within the iso image.
I've tested also the "findiso=$isofile" option, which means, as far as I know, to look thru all partitions looking for iso with the given name.

#15 Re: Installation » [SOLVED] Daedalus live-image - can't boot iso on hd without manual intervention » 2022-12-11 18:43:34

Head_on_a_Stick wrote:

Try

menuentry "devuan5 preview" {
   search.fs_uuid=$uuid
   set isofile="/devuan_daedalus_5.0.preview_20221022_amd64_desktop-live.iso"
   loopback loop ($root)$isofile
   linux (loop)/live/vmlinuz boot=live fromiso=/dev/disk/by-uuid/$uuid$isofile username=devuan
   initrd (loop)/live/initrd.img
}

Replace both $uuid instances with the actual (filesystem) UUID for /dev/sda9.

EDIT: btw hd1,9 in GRUB translates to /dev/sdb9. hd0,9 would be better but the UUID is the best approach IMO.

And why don't you try your own remedy before recommending it to me? :-D

Your approach changes the grub's behaviour, while the problem is clearly happening later. Grub is fine, because it can get the kernel and initrd from within the iso.

As for a workaround, I've already said I have one - just mount the fs manually to alternative location using "break=premount".

Besides, the exact same grub entry (with only the iso filename changed) works for all other devuan's, from jessie to chimaera. So it should work here.

The big question is:
Is there some more serious problem lurking deep beneath the surface, that will rear it's head when we least expect.

#16 Re: Installation » [SOLVED] Daedalus live-image - can't boot iso on hd without manual intervention » 2022-12-11 18:20:21

Same happens if the partition is xfs.
The volume gets mounted, and then immediately unmounted.

Also: in the beginning, when udev runs detection, the font on-screen doesn't change after the resolution changes, this might indicate that there are problems with udev, if so, that could be the root cause.

#17 Installation » [SOLVED] Beowulf's debootstrap doesn't contain "daedalus" script » 2022-12-11 18:00:59

dev-1-dash-1
Replies: 4

In beowulf official repos, there are 2 versions of debootstrap.
A standard one, and a backported one.
Neither one contains "daedalus" script in "/usr/share/debootstrap/functions".

#18 Installation » [SOLVED] Daedalus live-image - can't boot iso on hd without manual intervention » 2022-12-11 17:48:15

dev-1-dash-1
Replies: 11

Trying to boot the daedalus preview live image.
Live image is on hard drive, on ext3 filesystem.
(Note: not ext4, but ext3.)

grub entry:

menuentry "devuan5 preview" {
            set root="hd1,9"
            set isofile="/devuan_daedalus_5.0.preview_20221022_amd64_desktop-live.iso"
            loopback loop ($root)$isofile
            linux (loop)/live/vmlinuz boot=live fromiso=/dev/sda9$isofile username=devuan
            initrd (loop)/live/initrd.img
        }

The same type of entry works for everything from jessie to chimaera.

On boot, I see can't mount /dev/sda, can't mount /dev/sdb repeated entries,
also I see fs mounted, but then unmounted.

When booting with break=premount and then mounting the partition (sda9, that contains the isos) to an alternative location, say "/alternate_mounts/sda9", and then ^D to continue boot and everything works, I get to desktop. But, it doesn't work without this manual step, always the same error.

To reproduce: just put preview iso on hd, and create grub entry like the one I posted.

#19 Re: Devuan Derivatives » Refracta 11 (Chimaera) XFCE beta isos » 2021-09-14 18:43:43

Try and check the environment variables that are set, before and after lightdm startup.

I had to add something like "export ETC_PROFILE_SOURCED=1" to /etc/profile and "export USER_PROFILE_SOURCED=1" to ~/.profile to find out that lightdm simply doesn't pass --login parameter to the shell it executes to find the root cause of some trouble I've had with it.

Can't think of anything else right now.

#20 Re: Devuan Derivatives » Refracta 11 (Chimaera) XFCE beta isos » 2021-09-13 16:52:02

LightDM can be a bit finicky.

Take a look at these bugs.

https://bugs.debian.org/cgi-bin/bugrepo … bug=636108
https://bugs.debian.org/cgi-bin/bugrepo … bug=752129

On my Beowulf main box, I had to create ~/.xsessionrc file that would source /etc/profile and ~/.profile to work around.

Also, lightdm is likely to just break and refuse to start if there's some gsettings conf value missing, or something equally unimportant and minor happens.

For a live cd, slim is probably better.

ps) When do we get a daedalus script for debootstrap?

edit: typo

#21 Re: News & Announcements » Testing for beowulf 3.1 point release » 2020-12-07 21:31:22

Got it to work by applying the same changes gparted-live people did.

Patching the file

9990-misc-helpers.sh

with the following patch

474a475,481
>   if [ "${fstype}" = "ntfs" ]; then
>       if type ntfs-3g >/dev/null 2>&1; then
>           return 0
>       else
>           return 1
>       fi
>   fi

seems to be enough.

Pro-tip: for a quick test you can avoid rebuilding the initrd by booting the iso with "break=mount" command line parameter, and applying the patch right in the shell.

#22 Re: News & Announcements » Testing for beowulf 3.1 point release » 2020-12-07 13:36:34

fsmithred wrote:

If you try patching 9990-misc-helpers.sh please let me know how it goes. That file already gets patched for refracta2usb, and I could add the ntfs support next time I touch that package.

I've tried patching it myself, but I am unable to boot with a modified initrd which I've reconstructed by myself.

Maybe you can suggest something?

I unpack the beowulf-live initrd with

unmkinitramfs initrd.img /path/to/extracted/initrd-tree

After I've applied some changes, how do I compress it in exactly the same format?
I've tried the following:

find . | cpio -H newc -o > ../initramfs.cpio
cat initramfs.cpio | gzip > initramfs.igz

But boot failed immediately and dropped me to the shell even though I've only added some debug prints.

Do I have to insert the initrd into the iso image itself, or can I simply modify grub entry to load the custom initrd and it should work?

#23 Re: News & Announcements » Testing for beowulf 3.1 point release » 2020-12-07 13:31:53

I've tested the gparted-live-1.0.0-3 live image, which is being discussed in the forum post I've linked at message #8 in this thread.
The url for the actual live image is:
https://sourceforge.net/projects/gparte … o/download

I was able to boot it to desktop from an ntfs partition.

I looked into the initrd, /lib/live/boot directory and ran a diff command between beowulf's files at the same location in the initrd.
There are a number of differences, I'm not posting full diff because most of them don't seem related to ntfs.
However, here's the diff between the 9990-misc-helpers.sh file:

82c82
<   elif echo "${sysfs_path}" | grep -q '^/block/vd[a-z]$'
---
>   elif echo "${sysfs_path}" | grep -q '^/block/[hsv]d[a-z]$'
474a475,482 
>   # For ntfs, since user space program ntfs-3g will be used. Check ntfs-3g instead of kernel module.
>   if [ "${fstype}" = "ntfs" ]; then
>       if type ntfs-3g >/dev/null 2>&1; then
>           return 0
>       else
>           return 1
>       fi
>   fi
1222c1230
<       if [ "$(cat ${sysblock}/removable)" = "1" ]
---
>       if [ "$(cat ${sysblock}/removable 2>/dev/null)" = "1" ]
1270c1278
<       if [ "$(cat ${sysblock}/removable)" = "0" ]
---
>       if [ "$(cat ${sysblock}/removable 2>/dev/null)" = "0" ]

The second difference looks almost exactly like the post you linked to in message #9 of this thread.

#24 Re: News & Announcements » Testing for beowulf 3.1 point release » 2020-12-07 13:00:10

fsmithred wrote:

I think this post has the magic sauce: https://lists.debian.org/debian-live/20 … 00038.html
That function, is_supported_fs is in /lib/live/boot/9990-misc-helpers.sh

That seems close to the target.
If I have some time and energy in the next few days, maybe I'll try looking into it more. It might be just a few lines of code needed to fix it.

For the moment, we can conclude that it's another feature that has been working for decades but has been cancelled by Debian.
Thus it doesn't block release of beowulf 3.1.

#25 Re: News & Announcements » Testing for beowulf 3.1 point release » 2020-12-06 18:55:16

fsmithred wrote:

Where the hell did ntfs.ko go? On my installed beowulf system, it's missing. Same ntfs packages are installed as in my ascii, which does have ntfs.ko.

Thanks for paying attention and replying, fsmithred. That's why I (and I'm sure many others) use devuan - because of the sensible attitude towards resolving actual issues.

However, in this case:
FALSE ALARM!
I've just tested the debian-live-10.7.0-mate-amd64.iso directrly from debian.

It behaves exactly the same. No ntfs.ko in initramfs. "Warning: unable to mount /dev/sda3" when trying to access iso on ntfs partition.

Therefore: it's a Debian change, and Devuan simply mirrored it, and there's no direct obligation for Devuan team to do anything about it since it isn't connected to *ystemd.

In ascii, apt-file shows that it comes with the kernel. In beowulf, apt-file doesn't find ntfs.ko.

I can see the same results for ascii. I don't have a beowulf system right now near me.

If we were to try:
The simplest way to include ntfs.ko into the initramfs would probably be modifying "/etc/initramfs-tools/modules", but first making sure that the modules themselves are installed on the base system of course. I don't know why they aren't there on beowulf.

Can you tell me how big a partition I would need to install a minimal beowulf 3.1 system from the live image? If I have a partition big enough I can maybe try and find an easy solution.

In the meantime - this isn't a Devuan problem, so it's a non-blocking issue if you are planning to release 3.1.
As I described, the beowulf 3.0 problems with eudev are not present in 3.1, so progress has already been made.

Update:
Debian has dropped the support of ntfs.ko: (see: 29 June 2019: GParted Live 1.0.0-3 Stable Release)
https://gparted.org/news.php?item=224Release

And here people seem to be solving the same problem:
http://gparted-forum.surf4.info/viewtopic.php?pid=35358

Board footer

Forum Software