You are not logged in.
A few words to partitioning and file system:
Allow for GPT partitioning. Its the modern way and painless together with Uefi.
You will need an ESP, FAT formatted. 100MB is enough for normal operation. My personal recommendation is to use 512 or 1024MB because sometimes firmware updates want some space on the ESP and if that is just enough for the OS files firmware updates may fail.
If you want to use Suspend/Hibernate, allow for a swap partition that is about twice the size of your RAM.
And I recommend to use a separate /home partition.
To the boot stick: how was that generated? The method might be another trap if done by some Windows tool.
Me myself never had such an experience. There shouldn't be any difference in graphics for the installer between legacy and efi mode.
Looking at mainboard and CPU, both are somewhat older and should be mature, i.e. any installation should be a nobrainer without difficulty.
Well, on the other hand, there is one newer bios available if I am not mistaken. I would load that in any case.
Then reset the bios to defaults, and switch off secure boot. Then give it another try, first of all boot a live cd in efi mode, then with the netinstall also booted in efi mode.
Whats that? Is the latest bios installed on the mainboard?
Which Ryzen3 are we talking about? Which mainboard?
Maybe running inxi -Fz from the live iso could give us the required info.
Yes, thats the typical symptoms of a legacy installation on an Uefi motherboard.
When you boot your installation stick, you will find the stick twice in the boot menu. Make sure you boot the one that is marked efi/uefi. Then select "Rescue mode" and follow that until you get a chroot into the system. There do a
# grub-install without further parameters.
That should fix the issue.
I guess its due to the "bios" of this new machine. Have you ever worked with UEFI? I guess this Framework laptop is UEFI only.
To boot an USB stick you will need to call up a function called boot override. On my workstation its F8, on my travelling laptop its F12. Read the manual to find out how this works with your new toy.
Thanks for the explain; so if I want to stay with nouveau then I shouldn't install it. Right now nouveau is driving my temporary nvidia card, I presume that when I change the AMD card nouveau will simply use its non-proprietary AMD driver?
You are thinking in Windows terms.
No, a parallel installation of the amd graphics firmware will not kill you nouveau stuff or interfere in any way. They are no "drivers" in Windows terms. They are just firmware that is required for a reasonable display.
And they are not used at all if the kernel does not detect an AMD graphics during boot.
What you could refer to as driver for the AMD card is already contained in the kernel itself. There are no separate files like for an nvidea card. And there is no split into free and proprietary drivers for AMD. The one thats build in works fine.
That means you are not resolving anything - nameserver ::1, nameserver 127.0.0.1 means localhost.
That kills any DNS re. internet access.
firmware-amd-graphics adds firmware files for AMD graphics chips to /lib/firmware/amdgpu so that they are available during boot time. They are only pulled if an AMD graphics card is detected. No need to remove them. They will not hurt.
Otter: refer to https://otter-browser.org/
Just done an apt update for Daedalus. Worked ok. Try again.
If it fails again check if your DNS is working alright.
# apt update
Holen:1 http://deb.devuan.org/merged daedalus InRelease [43,0 kB]
Holen:2 http://deb.devuan.org/merged daedalus-security InRelease [33,2 kB]
Holen:3 http://deb.devuan.org/merged daedalus-updates InRelease [33,4 kB]
Holen:4 http://deb.devuan.org/merged daedalus-backports InRelease [33,2 kB]
Holen:5 http://deb.devuan.org/merged daedalus-security/main amd64 Packages [178 kB]
Holen:6 http://deb.devuan.org/merged daedalus-security/main i386 Packages [176 kB]
Holen:7 http://deb.devuan.org/merged daedalus-security/main Translation-en [107 kB]
Holen:8 http://deb.devuan.org/merged daedalus-backports/main amd64 Packages [227 kB]
Holen:9 http://deb.devuan.org/merged daedalus-backports/main i386 Packages [224 kB]
Holen:10 http://deb.devuan.org/merged daedalus-backports/main Translation-en [203 kB]
Holen:11 http://deb.devuan.org/merged daedalus-backports/main i386 Contents (deb) [747 kB]
Holen:12 http://deb.devuan.org/merged daedalus-backports/main amd64 Contents (deb) [644 kB]
Holen:13 http://deb.devuan.org/merged daedalus-backports/contrib i386 Packages [5.520 B]
Holen:14 http://deb.devuan.org/merged daedalus-backports/contrib amd64 Packages [5.652 B]
Holen:15 http://deb.devuan.org/merged daedalus-backports/non-free i386 Packages [1.296 B]
Holen:16 http://deb.devuan.org/merged daedalus-backports/non-free amd64 Packages [1.648 B]
Es wurden 2.663 kB in 5 s geholt (554 kB/s).
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
Aktualisierung für 15 Pakete verfügbar. Führen Sie »apt list --upgradable« aus, um sie anzuzeigen.To get information about your system inxi would be a good choice.
An AMD graphics card requires a suitable kernel and the firmware-amd-graphics package.
Well, I am happy with Daedalus and Cinnamon as desktop. It works fine ....
From any Linux, use any USB stick that large enough for the iso and can be overwritten, and use cp or dd to the raw device, i.e. /dev/sda. Not to a partition like /dev/sda1.
In expert mode you can skip that step. The description is for normal mode.
Well, under the assumption that you have Daedalus installed, you will need to add "non-free-firmware" to your sources.list, do an apt update, and install firmware-amd-graphics, then reboot.
Falkon is a KDE browser. If it does not depend on systemd (and I don't think so it does, haven't checked*), the version in Daedalus is the same as in Debian Stable/Bookworm.
Firefox ESR which I use also is labelled outdated by various websites. I am ignoring these messages.
* Edith: You may check yourself if you look at the list of forbidden packages, have a look at the link on top of this page to Devuan.org.
hddtemp=0.3-beta15-54 is the Chimaera version. When you upgrade you may keep it.
AFAIK because there is no more maintainer for quite a while.
And no direct replacement.
hddtemp has been removed as depracated. Its a pitty, but also a fact.
Forget about legacy mode. Do an EFI mode installation on that laptop. Boot the installation stick within the boot (override) menu with the prefix uefi, then you run the installer in (u)efi mode.
Having looked at some of your input, I fear you are confusing things.
1.) As a matter of fact your laptop is equipped with an ordinary SATA3 SSD. It is not equipped with a NVME SSD. That also explains the /dev/sda. A NVME would be listed as /dev/nvmexxxx.
2.) You want to keep Windows10. The SSD runs with GPT partition table, so Win10 is running in efi mode. Any parallel Linux installation has to use the same mode. A legacy install is impossible if you want to keep Win10. You have to start the installation drive in uefi mode, and run the Devuan installation.
Only if you do a Linux only installation, you might be able to install Daedalus in legacy mode on a GPT partitioned disk.
There are posts on the forum about pipewire, e.g. https://dev1galaxy.org/viewtopic.php?id=5867. I am using it on my travelling laptop. There it works ok for me.
Haven't converted my workstation yet, still works with pulse. Didn't get audio to work with pure ALSA.
RAM and SSD size are fine. Devuan Daedalus should work without issues. For the CPU you may need a backports kernel, not sure, I am using AMD only.
Which desktop you choose is up to you. All available shall work fine with that RAM and SSD size.
What might be interesting is the GPU installed. Is that a CPU with integrated GPU or is a separate e.g. NVidea on board?
I have had two motherboards with locked efi flash, no more way to write any new information. I guess it was because the kernel may use the efi flash to write crash dumps into there. There are some threads in this forum from me and others, and a way to avoid this happening.
Some background: the efi partition (ESR) on the disk holds entries for the operating systems that are on the PC. Here my travelling laptop dual boot Chimaera/Daedalus:
/boot/efi/EFI# ls -la
insgesamt 16
drwx------ 4 root root 4096 16. Sep 2022 .
drwx------ 4 root root 4096 1. Jan 1970 ..
drwx------ 2 root root 4096 29. Apr 2021 devuan4
drwx------ 2 root root 4096 16. Sep 2022 devuan5Also there is a flash memory in the bios that can be accessed via the efibootmgr. That shows what the bios can address and is able to start. Here is what is present on my laptop:
# efibootmgr -v
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0000,0001,2001,2002,2003
Boot0000* devuan4 HD(1,GPT,4a3fa84d-e7a5-4232-8341-02ef88af07d9,0x800,0xf3800)/File(\EFI\devuan4\grubx64.efi)
Boot0001* devuan5 HD(1,GPT,4a3fa84d-e7a5-4232-8341-02ef88af07d9,0x800,0xf3800)/File(\EFI\devuan5\grubx64.efi)
Boot2001* EFI USB Device RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network RCYou see the two operating systems plus the system drives labelled Boot200x.
Its good practice to first remove the operatings systems before you delete the efi directory on the hard disk (HD, SSD or NVME).
rolfie wrote:In a second step, you may use a gparted live iso to write a new partition table to the nvme. Then all exisiting partitions are history., and you may set up you desired partitioning scheme.
As I said, I want to keep my partition table. Like this I don't have to erase the luks header and have to learn another password.
What hinders you to set up the exact same scheme again with gparted?
Well you have to set up luks again, but you can you the same PW. What hinders you? I do that all the time when I am not happy with what I got.
My advice is: with any live system, first of all delete all existing entries of operating systems that efibootmgr shows. Keep the ones that point to internal devices like cdrom, usb ... That makes sure the efi flash memeory in the bios is more or less cleared. There usually is no other way.
In a second step, you may use a gparted live iso to write a new partition table to the nvme. Then all exisiting partitions are history., and you may set up you desired partitioning scheme.