You are not logged in.
But you did something like startx -- :1, right?
To complete #2:
I never tried to boot the kernel with the error during module compilation, just returned to daedalus' 6.1.
And there is a nvidia card involved as well, using the current driver version.
No solution, but it is quite similar in daedalus using the liquorix kernel. It worked up to 6.3, 6.4 shows an error as above.
The drive has several partitions with different distributions [antix, void] that I do not want to distrurb.
There can be only ONE grub in the MBR.
Booting the respective installation and doing update-grub (or aquivalent command) should find the new installed devuan and make a boot-entry for it.
The following worked for me to migrate bookworm to daedalus in a virtual machine.
ssh'ed in the vm, then copy-pasted commands.
No guaranty!
$ cat migration.notes.txt
# commands done as "root"
# stage 1:
apt update
apt upgrade
#apt install sysvinit-core ntp # no X
apt install sysvinit-core ntp slim openbox # simple DM and WM to not loose X eventually
reboot
# stage 2
# keep network as it is
echo 'GRUB_CMDLINE_LINUX="net.ifnames=1"' >>/etc/default/grub
update-grub
keyring="devuan-keyring_2023.05.28_all.deb" # daedalus
[ ! -f "$keyring" ] && wget http://deb.devuan.org/merged/pool/DEVUAN/main/d/devuan-keyring/"$keyring"
dpkg -i "$keyring"
file="/etc/apt/sources.list.debian"
[ ! -f "$file" ] && cp -a /etc/apt/sources.list "$file"
cat << EOF >/etc/apt/sources.list
deb http://deb.devuan.org/merged daedalus main contrib non-free non-free-firmware
# add recommended repos
EOF
apt update
apt upgrade
apt dist-upgrade
apt purge systemd # just to be sure
# likely, more stuff was de-installed
# a syslogd may be missingThe problem seems to be with removing systemd at Pid 1, and not locking the system.
# apt install sysvinit-core
# rebootand init is pid 1.
Just curious: Does the sound work in devuan when using /etc/modprobe.d/alsa-base.conf from ubuntu?
Usually not.
$ sudo apt purge nvidia-persistencedIt took me a lot of time to come to that point.
Or, if you want to keep it:
$ sudo /etc/init.d/nvidia-persistenced stop
$ sudo apt install Then apt should be happy again.
Sound is not a general problem. Notebooks can be special in different degrees.
A bit of googling:
Ubuntu seems to produce custom images for the Latitude 3420. https://ubuntu.com/certified/202101-28600
There was a question about missing sound here: https://askubuntu.com/questions/1291829 … -ubuntu-20
Not exactly the same model, maybe the answer applies to your case too.
The point on appimage is to have no dependencies.
Try the big one - the small one is a broken, it has the mentioned dependency.
Ubuntu which came pre-installed has everything working out of the box with kernel version 5.14 and pulseaudio. I am unable to understand if this is a problem specific to 5.10.
Don't know either, there should be no problem with 5.10. Alsa devices are looking good too.
I did a bit of testing, but have no speaker connected to any HDMI output ... .
I temporary installed pulsaudio, and could switch to a HDMI output device. The config was present.
qasmixer shows no level-fader for the HDMI audio output.
The generic name for the current kernel is "linux-image-amd64"
$ sudo apt install linux-image-amd64should install daedalus' kernel 6.1.
I would
(1) invest in a new small SSD - just 20 bugs, it's worth it.
(2) use the the nvidia drivers from the non-free devuan repo (not the installer offered by nvidia)
(3) sysV-init is default
The counterpart to debian bookworm is devuan daedalus (but not yet released as new stable), the current stable release is still chimaera.
You mentioned the kernel version: 5.10 is chimaera, daedalus has 6.1 and I would use this. Maye the old kernel is still booted as default for some reason?
The following command shows all sound devices on my box:
$ cat /proc/asound/pcm
00-00: ALC1150 Analog : ALC1150 Analog : playback 1 : capture 1
00-01: ALC1150 Digital : ALC1150 Digital : playback 1
00-02: ALC1150 Alt Analog : ALC1150 Alt Analog : capture 1
01-03: HDMI 0 : HDMI 0 : playback 1
01-07: HDMI 1 : HDMI 1 : playback 1That's all I got ...
The title includes "dual-boot" and "best method".
20 bugs for an addional SSD - it's worth it.
One operating system per physical drive is a clear approach.
Installations can be done in a way that each drive can boot its operating system independently.
Since only one drive can boot as default, other drives may be selected through the "BIOS boot menu" ([F12] on my computer).
But grub can detect and start most operating systems anyway.
Just recognised:
root@devuan:~# ssh devuan is (herer) equal to
root@devuan:~# ssh root@devuanTo login with a non-roor-user:
root@devuan:~# ssh your-non-root-user@devuanDoes this work?
Sorry, I messed up the fist answer rerspective systemctl ... just one missing "no" .
This is systemd stuff and does not apply to devuan. Scrpts like "ssh.service" may exist but are not used here.
root login via ssh might be forbidden by default. Does a non-root-user can login via ssh?
To get the state of sshd:
$ /etc/init.d/ssh statusGood morning. Not sure about the question, there is systemctl in devuan. I usually do
$ sudo apt install task-ssh-serverto have ssh server installed and running.
EDIT:
Ooops, I messed this up entirely: "... there is no systemctl in my devuan" is correct.
Would like to add: lspci may give a hint to the needed firmware.
And for new'ish hardware, daedalus might be an option. It will become the new stable in the near future anyway.
I would fix /etc/fstab first:
a) the error in line 1
b) temporary comment-out all non-linux filesystems
And try a live system (knoppix, or whatever you prefer) to confirm the hardware is ok.
Are there other OS'es, and if so do they show errors too?
Is it a new or an old installation?
If it is new one, I probably would just re-install. Or maybe trying to update to daedalus.
Sometimes it has to lolcat ... for a colourful experience. ![]()
$ neofetch | lolcat Nobody has ever had and probably never will have a repository for "Debian Chimaera".
Of course not.
But this is what you get, when using the linked installation instructions on chimaera.
Let's say there was a temptation to suggest "wouldn't you like to do a dist-upgrade to daedalus?", instead of answering the question.
Probably something strange in your user's $HOME or ~/.config ?
I would delete ~/.cache; can not hurt.
Then create a new user and check.
Some thoughts:
Correct BIOS time and non-fucntional RTC sounds contrary. Both are the same device, aren't they?
Debian shows correct time: Probably systemd-timesync forces a clock-update. ntpd could do so too with addional switches. google found e.g. https://askubuntu.com/questions/254826/ … -using-ntp
cat /proc/interrupts|grep -i rtc on my 97x-based mainboard looks almost equal, only one of the four zeros is not zero. Just to mention, whatever it means.
Excellent - Thanks a lot, guys!
And something learned again.
Thanks for the info - I was not aware of that possibilty.
At least there is nothing strange happening, as thought before.