You are not logged in.
Update: when you just do an cli install without any DE, desktop-base isn't installed, and no Sapphire theme. Then also the them line is omitted in /etc/default/grub.
Why don't you use a zoom of e.g. 133%? Works fine with FirefoxESR.
Edith: pfff ... seconds too late ....
Some news: checked the SHA256 checksum of the iso on the Ventoj stick and found it was different from the one in my Download folder.
Well, replaced the file on the stick and made sure it had the same checksum as listed on the Devuan download page, now it is correct.
Trying to boot from that iso ends up in the "_", the computer seems to be locked. NUM is on as set in the bios, but no reaction on a keystroke. Also no way to open a console. Only way out is power off/on or hard reset. So now same behaviour as the two RC versions I tested.
I tried to install Daedalus AMD64 netinstall release in EFI mode via a Ventoj stick on this computer:
# inxi -F
System:
Host: rh032 Kernel: 6.1.0-11-amd64 arch: x86_64 bits: 64 Console: pty pts/0
Distro: Devuan GNU/Linux 5 (daedalus)
Machine:
Type: Desktop Mobo: ASUSTeK model: SABERTOOTH 990FX R2.0 v: Rev 1.xx
serial: xxx UEFI: American Megatrends v: 2901 date: 05/04/2016
CPU:
Info: 8-core model: AMD FX-8370 ... The special thing is that the computer is equipped with a NVME on an adapter card as boot device.
I end up with
No bootfile found for UEFI!
Maybe the image does not support x64 UEFINo matter if normal mode or grub2-mode. The SHA265 checksum of the image is correct.
Also tried RC5 and RC8, both end in a "_", a hard reset is required.
I did a successful installation with an old preview dated 220523.
Any ideas?
Strangely enough, the 6.1.0-11-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.38-4 (2023-08-08) x86_64 GNU/Linux is the up-to-date default kernel.
@Jorge: you might try one of the earlier 6.1 kernels.
Question: How to make the grub and theming reflect Daedalus instead of Chimaera
update-grub returned:Generating grub configuration file ... Found background image: splash.png Found linux image: /boot/vmlinuz-6.1.0-10-amd64 ... Adding boot menu entry for UEFI Firmware Settings ... doneAny help is appreciated.
On my system the first line past the header line shows:
Found theme: /boot/grub/themes/sapphire-grub/theme.txtThat is missing on your end. I had to move the themes from /usr/share/desktop-base/ to /boot due to encryption, grub has no access when required.
Inspect your /etc/default/grub, I guess the corresponding setting is commented out.
Maybe just the package firmware-amd-graphics is missing. The mean thing is that since Bookworm the non free firmware has moved to a new sub-repo non-free-firmware. Daedalus had to follow Debian.
https://wiki.debian.org/Firmware
You need to add this to your sources.list. Give it a try.
Give us a shout if further questions or problems come up. Good luck.
netinstall and a LAN cable should be fine.
When Bookworm shows the resolution of your monitor, there is no reason Chimaera or Daedalus shouldn't. Debian and Devuan share kernel, firmware and most software. Low resolution is mostly due to non-free firmware missing, in this case firmware-amd-graphics.
When trying again make sure the sources.list looks like this one:
deb http://deb.devuan.org/merged chimaera main contrib non-free
deb http://deb.devuan.org/merged chimaera-updates main contrib non-free
deb http://deb.devuan.org/merged chimaera-security main contrib non-freeUse apt list to find out if this firmware-package is installed.
Don't know without looking at details, its not the hardware itself. Except for: do you use the onboard graphics or a separate card?
Edith: just read post #3 again, sounds like you are using onboard as I do. Same lspci output.
I am using the onboard graphics. If the hardware still is good a Chimaera install should fire up fine.
Which medium did you use? How was it put on a stick? Did you use the Install or the Expert install? I am only using netinstall media and the expert installs nowadays.
How does your sources.list look like? One guess is that non-free and due to that firmware is missing.
Have pulled the PC and fired it up, it still works ok.
However, when I tried doing a test install on my rather old workstation (built circa 2011 by me, based on M4A89GTDPro motherboard), the installation came up in a very weird resolution of something like 640 - obviously it didn't detect my graphics card or monitor or whatever. Rather than get into all that (I'm frankly tired of messing with such things, sorry, just being honest) I went back to Bookworm. However however the issues with my code not working are piling up. So now I'm looking elsewhere again.
I do own such an old mainboard based PC. Got it working alright with Chimaera, legacy install with onboard graphics and a 1920x1200 monitor. The PC is sitting somewhere in a corner in my basement, not being used very often.
I guess Daedalus should also work on such hardware.
Devuan literally is a Debian minus systemd related packages. Look at the list of banned packages to get an impression. On top of the forum page there is a link to Devuan.org. There you can find this list.
All the rest like drivers, firmware, kernel, desktops, most programs is pure Debian. The sources.list to 95% uses the same syntax as Debian, i.e. Daedalus also requires the non-free-firmware to be added, same as Bookworm.
To the graphical install: that was abandoned a while ago by the Devuan team due to resource issues. Nothing to do with drivers. Due to the lack of manpower maintaining a parallel branch in the installer wasn't possible any more.
The Daedalus installer already includes usage of non-free stuff. That does not mean every hardware combination is working perfectly. There is too much HW out there that has bad bios or other bugs and glitches.
There seems to be a problem for as well Debian 12 isos (not the life ones) as for Devuan isos to get it to work in efi mode in the vbox. You end up eithe in a grey screen or some sort of kernel dump saying something about cannot open display. Same problem discussed in the German Debian Forum, also a thread open in the Virtualbox forum, and bug report 1036310 open against Debian.
Something along the line has changed in the way the graphics is setup between about Nov last year and before.
Thanks, a deliberate reload of the page did the job.
The main page https://www.devuan.org/ still shows the Devuan 4/Chimaera based information.
Ok, then you have your fallback option already. I am not 100% sure how that works in your case, I am used to use full disk encryption.
What happens in your case when the key stick isn't plugged in? Do you end up in the initramfs?
To make sure: you have not assigned a password to the encrypted /home as first step?
There is an option to cryptsetup named luksAddKey. With this option you can add further keys (either passwords or keyfiles) but this will ask for an already existing key. I have always used a passphrase as first key, and have no idea how to add a key with a keyfile as only option.
Normally this is a setting in the bios. Would be the first approach to fix this.
If ntp and nptdate aren't installed, you have no chance to use this path. BTW: with Daedalus(Bookworm) the path to the ntp.conf has changed to /etc/ntpsec.
Then cli remains: here is the link to an article that describes how to use the console to adjust date and time (scroll down towards the bottom past the timedatectl section): https://phoenixnap.com/kb/how-to-set-or … ime-ubuntu
First of all you should correct the fourth line to also read:
deb http://deb.devuan.org/merged daedalus-proposed-updates mainSince Daedalus isn't released yet, I would uncomment this line for the time being.
The rest looks ok, at least for amd64 it works.
You will need to add the NEW sub-repo non-free-firmware to be able to load something from there. Change your sources.list to:
deb http://deb.devuan.org/merged daedalus main contrib non-free non-free-firmwareSome reading:
https://www.debian.org/releases/bookwor … e-firmware
I assume you have installed Chimaera = Devuan Stable? Or did you use Daedalus = Devuan Testing?
Devuan kernels are Debian kernels. Generally spoken make sure you have the meta package linux-image-amd64 installed. That makes sure that the latest released kernel is pulled. For Stable you have the choice to add backports as sub-repo, currently on 6.1 kernel. Don't pull in other distros, you will create a Franken Devuan.
The initramfs will be created by the installation post-processing.
Some further information: https://github.com/NixOS/nixpkgs/issues/229450
None
Sometimes they write nonsense ....
Which release do you use?
Which kernel?
Which firmware is installed?