Download | Devuan.org | Git | Bugs | Packages

The officially official Devuan Forum!

You are not logged in.

Pages: 1 2 3 4 5 6

#26 Re: Desktop and Multimedia » [SOLVED] Waterfox and AppArmor. » 2026-01-16 08:01:34

devuan_dk_fan

I tried 

export PATH=$PATH:/opt/waterfox

with a previous install (Watt OS - Debian 12) and it didn't work either.

#27 Re: Desktop and Multimedia » [SOLVED] Waterfox and AppArmor. » 2026-01-16 00:27:35

devuan_dk_fan

Perhaps I wasn't clear? I was surprised that despite two programs residing in the /opt directory (simplenote and waterfox) only the one installed as a .deb package (simplenote) showed up in the $PATH. It was necessary to simlink the other (waterfox and waterfox-bin) to /usr/local/bin/ before it appeared in the $PATH. I don't believe that is normally necessary if both reside in the !modified $PATH... /opt

#28 Desktop and Multimedia » [SOLVED] Devuan Excalibur Alsa audio with multiple sound cards. » 2026-01-15 18:57:05

devuan_dk_fan
Replies: 8
$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Device [USB PnP Sound Device], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: Generic [HD-Audio Generic], device 3: HDMI 0 [S24C650]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 2: Generic_1 [HD-Audio Generic], device 0: ALC256 Analog [ALC256 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

I added the following to ~/.asoundrc, in connection with a new Devuan Excalibur install:

pcm.!default {
    type hw
    card 2
}

ctl.!default {
    type hw
    card 2
}

This appears to set the desired card to default:

$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Device [USB PnP Sound Device], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: Generic [HD-Audio Generic], device 3: HDMI 0 [S24C650]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 2: Generic_1 [HD-Audio Generic], device 0: ALC256 Analog [ALC256 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Everything looks good, but I am not getting any audio out, neither with alsa:

$ speaker-test -c 0

speaker-test 1.2.14

Playback device is default
Stream parameters are 48000Hz, S16_LE, 1 channels
Using 16 octaves of pink noise
Channels count (1) not available for playbacks: Invalid argument
Setting of hwparams failed: Invalid argument

YouTube in librewolf, firefox and waterfox don't output anything either.

I am trying to  keep this system as KISS as possible, as problems can sometimes appear as is, when I use websites that I need, that use midi over web and webgl.

Any ideas?

#29 Re: Desktop and Multimedia » [SOLVED] Waterfox and AppArmor. » 2026-01-15 18:20:36

devuan_dk_fan

Thanks. Part of my diagnostic process was exactly to make sure that both waterfox and waterfox-bin were executable. Good to see the info for disabling the AI hoi polloi.

#30 Re: Desktop and Multimedia » [SOLVED] Waterfox and AppArmor. » 2026-01-15 16:12:00

devuan_dk_fan

I am still in the process of getting this set up properly, however I have run through a diagnostic process. The conclusion appears to be that for some reason,

export PATH="$PATH:/opt"

also needed to be included in the ~/.bashrc file as well, despite the use of the login manager from the install being used.

Secondly I have also added links:

$ sudo ln -s /opt/waterfox/waterfox /usr/local/bin/waterfox

AND

$ sudo ln -s /opt/waterfox/waterfox-bin /usr/local/bin/waterfox-bin

I don't understand why it was necessary for a portable app, when it isn't necessary with a .deb program, both installed in the /opt directory.

At least now, waterfox appears in the <ALT> + <F2> LXDE run menu.

The next step will be installing spectrwm and notion to see if waterfox can be run from dmenu in spectrwm and the run menu in notion. I will post again, when I know if this issue is solved or not.

#31 Re: Desktop and Multimedia » [SOLVED] Waterfox and AppArmor. » 2026-01-15 14:50:05

devuan_dk_fan

OK, thanks for your reply and posting those links. Now I am less sure that it is AppArmor that is the culprit, but there is something that is definitely going on. From the LXDE environment, if I run the following, I get a longer response:

$ simplenote
Checking for beta autoupdate feature for deb/rpm distributions
Found package-type: deb

What is that autoupdate "feature"?

$ waterfox
bash: waterfox: command not found

Both programs reside in /opt, which is in my path... The binary paths are as follows:

/opt/Simplenote/simplenote
/opt/waterfox/waterfox

and

/opt/waterfox/waterfox-bin

Both programs appear to have the correct ownership for the /opt directory, so why will one run and the other not?

#32 Desktop and Multimedia » [SOLVED] Waterfox and AppArmor. » 2026-01-15 07:25:13

devuan_dk_fan
Replies: 20

I just installed the latest version of Devuan. I am running the LXDE desktop. I have downloaded waterfox and moved the directory to /opt. I have added /opt to my $PATH with:

export PATH=$PATH:/opt

to my ~/.bash_profile file and updated $PATH.

Currently, there are two programs, residing in each their folders, one was installed as a .deb file, the other is waterfox. Waterfox still does not appear to be recognized by the system, where as the other program does. I have created a waterfox.desktop file for waterfox, however, my experience with a previous install tells me that this doesn't work if using dmenu with spectrwm, which is my daily driver. It will only work if I include the full path to the binary. I assume that this has something to do with apparmor, but haven't a clue as to what to do, as I have no experience with it.

Can anyone provide some advice, before I start futzing around on my own?

#33 Re: Devuan » Devuan runit system pauses during first boot at net connect manager. » 2025-01-16 17:57:13

devuan_dk_fan

Weirdly, while I am unable to get a list of apps (including flatpaks) to install via Discover, I get prompted to update the system and am able to update the system in practice using Discover. So in some fashion, Discover is network aware, but not when it comes to software that hasn’t yet been installed…

#34 Re: Devuan » Devuan runit system pauses during first boot at net connect manager. » 2025-01-11 21:21:11

devuan_dk_fan

Thanks for the post Lorenzo. Things worked as described, but Discover still can’t find a connection, despite the ethernet connection clearly working.

#35 Re: Devuan » Devuan runit system pauses during first boot at net connect manager. » 2025-01-08 16:24:33

devuan_dk_fan

I just tried two more installs. What works best (relative term) on bare metal is the following:

# apt install xorg xinit xterm

# apt install kde-standard

# reboot

There are a few extra apps installed that I am not interested in, however for the most part, the system behaves as I expect it to. The exceptions are as follows:

SDDM is installed, but doesn't appear at boot. This is probably due to the second exception. Interestingly, SDDM appears when I choose one of the commands from the application menu (logout, restart, shutdown).

An ethernet connection is available and working, but not with NetworkManager, which is also likely the reason that Discover doesn't detect an internet connection.

Cups doesn't appear to be working either.

I can live without SDDM and Discover not working properly, but it would be nice if they did...

---

Not sure how, but Discover looks like it is working now. Only lacking SDDM...

#36 Re: Devuan » Devuan runit system pauses during first boot at net connect manager. » 2025-01-08 08:22:42

devuan_dk_fan

The Q4OS script solution, unfortunately still looks like the only way to get a fully functioning KDE Plasma install on a runit init base. I would have preferred a fully Devuan install, but it looks like the Q4OS script or a Peppermint OS runit install are the only options for getting a fully working runit Devuan based system, the later with XFCE not KDE…

#37 Re: Devuan » Devuan runit system pauses during first boot at net connect manager. » 2025-01-07 17:15:05

devuan_dk_fan

I followed the instructions exactly, but after having tried two more installs to get sddm working, I installed lightdm instead. Lightdm starts into a kde plasma gui that has a number of issues:

Unable to resize windows.

The kde application launcher kicked up some errors as well:

Errors:
file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/Kickoff.qml:157:34: Type FullRepresentation unavailable

file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/FullRepresentation.qml:80:22: Type NormalPage unavailable

file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/NormalPage.qml:43:13: Type Footer unavailable

file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/Footer.qml:155:5: Type LeaveButtons unavailable

file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/LeaveButtons.qml:14:1: module "org.kde.kitemmodels" is not installed

My wired ethernet connection functions, but there is no NetworkManager directory, and no .conf file:

# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet dhcp

# cd /etc/NetworkManager
bash: cd: /etc/NetworkManager: No such file or directory

#38 Re: Devuan » Devuan runit system pauses during first boot at net connect manager. » 2025-01-07 09:24:08

devuan_dk_fan

So far, so good. I followed your lead and installed a minimal system before adding xorg and kde-standard, with no recommendations. (I personally view this as counterintuitive, when I am using an “expert install”, but ok.)

Everything seems to have worked so far, but the system isn’t booting into sddm at start. Since this is a runit init install, I assume something needs to be done manually, but I am unsure if sddm is launched by runit or by one of the remaining sysv init scripts 🤔

—-

sddm appears in a list when I run the following:

# cd /etc
# ls sv

This would suggest that sddm should be started by runit. Running the following command would suggest that sddm does get started:

$ ps ax | grep run

returns “runsv sddm” and “runsv elogind”

I should mention that I continue to need to press the return key after boot is finished, to get a command line login.

#39 Re: Devuan » Devuan runit system pauses during first boot at net connect manager. » 2024-12-31 14:32:38

devuan_dk_fan

Here is a more in depth look at the result of running the q4os script on a Devuan KDE runit install:

$ ps ax | grep run
    1 ?        Ss     0:00 runit
 1542 ?        Ss     0:00 runsvdir -P /etc/service log: .....................................................................................................................................................................................................................................................................................................................................check: 3: socklog-check: not found check: 3: socklog-check: not found 
 1593 ?        S      0:00 /usr/sbin/smartd --pidfile /var/run/smartd.pid
 1685 ?        Ss     0:00 runsv getty-tty4
 1686 ?        Ss     0:00 runsv cups
 1687 ?        Ss     0:00 runsv getty-ttyS0
 1688 ?        Ss     0:00 runsv dbus
 1689 ?        Ss     0:00 runsv dhclient
 1690 ?        Ss     0:00 runsv getty-tty3
 1691 ?        Ss     0:00 runsv anacron
 1692 ?        Ss     0:00 runsv cron
 1693 ?        Ss     0:00 runsv sddm
 1694 ?        Ss     0:00 runsv acpid
 1695 ?        Ss     0:00 runsv elogind
 1696 ?        Ss     0:00 runsv getty-tty6
 1697 ?        Ss     0:00 runsv getty-tty5
 1698 ?        Ss     0:00 runsv rsyslog
 1699 ?        Ss     0:00 runsv dbus.dep-fixer
 1700 ?        Ss     0:00 runsv getty-tty2
 1701 ?        Ss     0:00 runsv default-syslog
 1702 ?        Ss     0:00 runsv getty-tty1
 1706 ?        S      0:00 svlogd -tt -b 2048 /var/log/runit/dbus
 1709 ?        S      0:00 svlogd -tt -b 2048 /var/log/runit/sddm
 1712 ?        S      0:00 svlogd -tt -b 2048 /var/log/runit/dhclient
 1716 ?        S      0:00 svlogd -tt -b 2048 /var/log/runit/anacron
 1719 ?        S      0:00 svlogd -tt /var/log/runit/acpid
 1919 ?        S      0:00 avahi-daemon: running [host_computer.local]
 1924 tty7     Ssl+   0:00 /usr/lib/xorg/Xorg -nolisten tcp -auth /var/run/sddm/{5bc3cb32-6e3c-4fe0-ae1b-8f42736e3c47} -background none -noreset -displayfd 17 -seat seat0 vt7
 1980 ?        S      0:00 /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant
 2112 ?        S      0:00 /usr/lib/x86_64-linux-gnu/sddm/sddm-helper --socket /tmp/sddm-auth5d07c714-2378-448c-b18f-637ebc26e64d --id 1 --start /usr/lib/x86_64-linux-gnu/libexec/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland --user brian
 2117 tty8     Ss+    0:00 dbus-run-session /usr/bin/startplasma-wayland
 2142 tty8     Sl+    0:03 /usr/bin/kwin_wayland --wayland-fd 7 --socket wayland-0 --xwayland-fd 8 --xwayland-fd 9 --xwayland-display :1 --xwayland-xauthority /run/user/1000/xauth_AViBbU --xwayland
 2163 tty8     Sl+    0:00 /usr/bin/Xwayland :1 -auth /run/user/1000/xauth_AViBbU -listenfd 49 -listenfd 50 -displayfd 41 -rootless -wm 44
 2328 tty8     S+     0:00 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 11 --address=unix:path=/run/user/1000/at-spi/bus_1
 2644 tty8     Sl+    0:00 /usr/lib/x86_64-linux-gnu/libexec/baloorunner
 2782 ?        Ss     0:00 fusermount3 -o rw,nosuid,nodev,fsname=portal,auto_unmount,subtype=portal -- /run/user/1000/doc
 3993 pts/1    S+     0:00 grep run

/etc/runit$ ls -1F runsvdir
current@
default/
default.run/
single/
solo/
svmanaged/

/etc/runit$ ls -1F runsvdir/default
acpid@
anacron@
cron@
cups@
dbus@
dbus.dep-fixer@
default-syslog@
dhclient@
elogind@
getty-tty1@
getty-tty2@
getty-tty3@
getty-tty4@
getty-tty5@
getty-tty6@
getty-ttyS0@
rsyslog@
sddm@

$ ls -F /etc/init.d
acpid*                   cups-browsed*           mountkernfs.sh*               saned*
alsa-utils*              dbus*                   mountnfs-bootclean.sh*        sddm*
anacron*                 elogind*                mountnfs.sh*                  seatd*
apparmor*                eudev*                  networking*                   sendsigs*
avahi-daemon*            gdomap*                 network-manager*              single*
bluetooth*               halt*                   openntpd                      smartmontools*
bootlogd*                hostname.sh*            procps*                       speech-dispatcher
bootlogs*                hwclock.sh*             pulseaudio-enable-autospawn*  stop-bootlogd*
bootmisc.sh*             keyboard-setup.sh*      rc@                           stop-bootlogd-single*
brightness*              killprocs*              rc.local*                     sudo*
checkfs.sh*              kmod*                   rcS@                          umountfs*
checkroot-bootclean.sh*  lm-sensors*             README@                       umountnfs.sh*
checkroot.sh*            mountall-bootclean.sh*  reboot*                       umountroot*
console-setup.sh*        mountall.sh*            rmnologin*                    unattended-upgrades*
cron*                    mount-configfs*         rsync*                        urandom*
cups*                    mountdevsubfs.sh*       rsyslog*                      x11-common*

#40 Re: Devuan » Devuan runit system pauses during first boot at net connect manager. » 2024-12-31 10:45:53

devuan_dk_fan

OK, I now have a working runit system, but I had to do some serious thinking outside of the box:

Comment out CD in /etc/apt/sources.list

If directories are lacking:
$ xdg-user-dirs-update

$ wget q4os.org/downloads/q4os-setup.sh
$ su (or sudo -s)
# sh q4os-setup.sh

Run the following after reboot to confirm running init system:
$ cat /proc/1/comm

The fundamental problem appears to have been that I could not get any desktop. Nouveau (if installed) didn't give me a GUI, and installing nvidia-driver ended with a dpkg error #1. Likewise, a guided disk formatting with a separate /home partition gave me a system with a home directory without any sub-directories (both sysv and runit). After having run the q4os script and rebooted, I now have a functioning system (KDE Plasma) using runit - confirmed by $ cat /proc/1/comm

Current status is that while I have a running system, /var/log/boot contains the following error message:
"Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon failed!"
which could be why Discovery doesn't appear to be able to access a wired internet connection. Synaptic works fine.

I as of yet have not installed the Nvidia drivers as I am trying to avoid the dpkg error again. It will be interesting to see how long I can do that... The computer has an NVIDIA TU116 [GeForce GTX 1660 SUPER] gpu.

#41 Re: Devuan » Devuan runit system pauses during first boot at net connect manager. » 2024-12-30 20:38:28

devuan_dk_fan

I have since the last post tried installing Devuan with LXQT, as well as another KDE Plasma directory configuration at install - both with runit init. The LXQT install could not complete a first system boot, pausing at "bluetooth". The KDE install paused at the same place. In both cases, pressing the return key returned a cli prompt to log in. Both installs appear to be malformed, as there are no directories in user /home. Likewise, an ls in /root returns nothing, however I was able to get into /usr and complete an ls of the directories inside. commands such as # poweroff, halt -h now, halt -r now, etc. did not work, despite a verification that they were there when doing an # ls in /sbin.

This is starting to look more and more like an issue of malformed installs...

#42 Devuan » Devuan runit system pauses during first boot at net connect manager. » 2024-12-30 15:43:32

devuan_dk_fan
Replies: 15

Devuan system new KDE Plasma install with runit init:
First boot pauses at “Starting network connection manager: NetworkManager.” Refuses to continue. From what I have read, Devuan's runit implementation is a hybrid form of some runit bits, while most startup items continue to use SystemV. I am not really sure how to address the above problem to successfully get a first boot. Any ideas? I know that a PeppermintOS based Devuan install with XFCE and runit work without problems, so my working hypothesis is that NetworkManager isn't getting loaded. While I assume that NetworkManager is still SysV, I have no idea how to solve this on a hybrid runit system.

Help?

#43 Re: Installation » [SOLVED] Very strange audio problem after testing USB sound card. » 2024-05-30 21:19:18

devuan_dk_fan

I think that I may have gotten this the wrong way round. From what I can see online, there never has been support for the sound card. I just always used it with a Behringer U-Phoria UMC202HD USB sound card, and never tried the built-in sound card until after I tried the AudioQuest sound card, making me think something happened due to that card… Unless someone has some ideas about a driver for the built-in sound card, I guess that this topic could be marked “solved”…

#44 Installation » [SOLVED] Very strange audio problem after testing USB sound card. » 2024-05-30 17:16:06

devuan_dk_fan
Replies: 2

I would like to install Devuan, but as I have been experiencing audio issues, I started by booting from the live desktop image and testing the hardware. I should preface this by writing that I have just picked up the computer today, from my local computer tech shop. I had taken the computer there because of the audio problems, and was told that there is nothing wrong with the hardware. Sooo... I brought the computer back home, only to find that only the hdmi sound (crappy speakers in a monitor) is working. the built-in sound card still doesn't work in Linux. Here is what the hardware look like, and I emphasize that it was working before I tested the sound card:

$ inxi -SMA
System:
  Host: devuan Kernel: 6.1.0-10-amd64 arch: x86_64 bits: 64 Desktop: Xfce
    v: 4.18.1 Distro: Devuan GNU/Linux 5 (daedalus)
Machine:
  Type: Desktop System: HUAWEI product: PUM-WDX9 v: M1010
    serial: <superuser required>
  Mobo: HUAWEI model: PUM-WDX9-PCB-B1 v: M1010 serial: <superuser required>
    UEFI: HUAWEI v: 1.28 date: 08/22/2022
Audio:
  Device-1: AMD Renoir Radeon High Definition Audio driver: snd_hda_intel
  Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor driver: N/A
  Device-3: AMD Family 17h/19h HD Audio driver: snd_hda_intel
  API: ALSA v: k6.1.0-10-amd64 status: kernel-api
  Server-1: PulseAudio v: 16.1 status: active
$ lsmod | grep snd
snd_hda_codec_realtek   172032  1
snd_hda_codec_generic    98304  1 snd_hda_codec_realtek
snd_hda_codec_hdmi     81920  1
snd_hda_intel          57344  3
snd_intel_dspcfg       36864  1 snd_hda_intel
snd_intel_sdw_acpi     20480  1 snd_intel_dspcfg
snd_hda_codec         184320  4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek
snd_hda_core          122880  5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek
snd_pci_acp6x          20480  0
snd_hwdep              16384  1 snd_hda_codec
snd_pcm               159744  5 snd_hda_codec_hdmi,snd_pci_acp6x,snd_hda_intel,snd_hda_codec,snd_hda_core
snd_timer              49152  1 snd_pcm
snd                   126976  14 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm
soundcore              16384  1 snd
snd_pci_acp5x          20480  0
snd_rn_pci_acp3x       20480  0
ledtrig_audio          16384  2 snd_hda_codec_generic,huawei_wmi
snd_acp_config         16384  1 snd_rn_pci_acp3x
snd_soc_acpi           16384  1 snd_acp_config
snd_pci_acp3x          20480  0

The USB sound card that I was testing is an AudioQuest DragonFly Black v1.5.

Any ideas about how I can get the hardware working?

#45 Re: Devuan Derivatives » [SOLVED] Exe GNU/Linux live user name and login? » 2024-05-30 13:58:34

devuan_dk_fan

Many thanks for the replies.

#46 Re: Devuan Derivatives » [SOLVED] Exe GNU/Linux live user name and login? » 2024-05-28 07:57:48

devuan_dk_fan

Thanks for the reply. I found that I am able to get to the Trinity desktop by choosing “nomodeset” in GRUB. There appears to be a problem using my Nvidia graphics card. All I can get is what looks like an 800x600 resolution. The card on my computer is an Nvidia GeForce GTX 1660 SUPER.

#47 Devuan Derivatives » [SOLVED] Exe GNU/Linux live user name and login? » 2024-05-27 18:57:24

devuan_dk_fan
Replies: 7

Trying to test Exe GNU/Linux, but I can't get past the cli login. Shouldn't it boot into a graphical environment, and why can't I find any information about user name and password? Trying to use exegnu64_daedalus-20231220

#48 Re: Installation » extlinux install from Devuan ASCII installer shell. » 2018-06-16 20:58:01

devuan_dk_fan

OK, the latest update is that I changed the Devuan /boot/extlinux/extlinux.conf back to the original setup:

UI menu.c32
PROMPT 0
MENU TITLE Welcome to Devuan - Debian without SystemD
TIMEOUT 100
DEFAULT devuan

	LABEL devuan
		MENU LABEL Devuan
		KERNEL /vmlinuz
		APPEND initrd=/initrd.img ro root=/dev/sdd1

by mounting the partition in Slackware and editing. When I rebooted, I was suddenly able to boot into the system again, so I uninstalled all kernels except for the low latency kernel and after having rerun the NVIDIA.run script, everything seems to be working fine. I will wait a couple of days before I mark this topic as solved, just in case there is something else.

#49 Re: Installation » extlinux install from Devuan ASCII installer shell. » 2018-06-16 15:16:00

devuan_dk_fan

@ fsmithred

Here I thought that I had everything sorted, but I compiled a low latency kernel following the instructions here and now even though I changed the entries in the Devuan /boot/extlinux/extlinux.conf to as follows, it refuses to boot, but just cycles through the countdown from 10-0 and back again:

UI menu.c32
PROMPT 0
MENU TITLE Welcome to Devuan - Debian without SystemD
TIMEOUT 100
DEFAULT devuan

	LABEL devuan
		MENU LABEL Devuan
		KERNEL /vmlinuz-4.9.88-lowlatency
		APPEND initrd=/initrd.img-4.9.88-lowlatency ro root=/dev/sdd1

Interestingly, if I mount the Devuan partition /boot/extlinux/ and manually rename all of the files that end in ".amd64" and add ".bak" at the end, and reboot, I get the same error about the partition /dev/sdd1 no longer existing, as I did when I tried editing the Devuan /etc/inittab and changed:

# The default runlevel.
id:2:initdefault:

to

# The default runlevel.
id:1:initdefault:

sooo I am pretty sure that there is some sort of glitch in Devuan ASCII, as switching runlevels in the /etc/inittab shouldn't cause an error like that, and I can't imagine that renaming files with ".bak" should do that either.

#50 Re: Installation » extlinux install from Devuan ASCII installer shell. » 2018-06-16 07:21:20

devuan_dk_fan
fsmithred wrote:

Sorry I don't have anything useful to add. When I get a chance, I'll try extlinux with a multi-boot system and let you know what I find.

I just successfully booted into Devuan ASCII on my triple boot system. Here are my extlinux.conf entries:

Slackware64 14.2 /boot/extlinux/extlinux.conf entry for Devuan ASCII install:

	LABEL devuan
		MENU LABEL Devuan - Debian without SystemD
		COM32 chain.c32
		APPEND hd3 1

Devuan ASCII /boot/extlinux/extlinux.conf entry (Devuan ASCII only):

UI menu.c32
PROMPT 0
MENU TITLE Welcome to Devuan - Debian without SystemD
TIMEOUT 100
DEFAULT devuan

	LABEL devuan
		MENU LABEL Devuan
		KERNEL /vmlinuz
		APPEND initrd=/initrd.img ro root=/dev/sdd1

On the Devuan ASCII side, I could make do with less, as I really don't need a menu. All I want to be able to do is to boot into the system from the Slackware extlinux menu, but it is the first thing that works.

Pages: 1 2 3 4 5 6

Board footer

Forum Software