You are not logged in.
Why do you need it? Do you have Secure Boot enabled?
Sure, should work. Have you rebooted?
If that doesn't solve the problem, please post the output of inxi -F
In the interim, I tried install [on a different partition] without any X11 packages, just Console stuff, and on reboot it stopped [hung] after the message "Starting bluetooth: bluetoothd". I guess no-one tried that yet.
I done that on all my latest Devuan installations including Daedalus to be able to set up the graphical desktop my way. I use netinstalls and disable anything else but the standard system utilities in the sw selection, and do a reboot past the final steps including the grub install. Never had any issues, it simply worked. Independent from if I have network or not, on real HW or in a VM. The console should come up, sometimes when firmware is missing with not so nice graphics, but still readable. No Intel or NVidea involved though, pure AMD stuff.
Have you left out something, skipped an important step during expert install? What kind of PC we are talking about? efi or legacy install? What did you modify versus the procedure described here: https://www.devuan.org/os/documentation … all-devuan ?
Well, a fix could be to reformat it with the oldest distro that needs to access that partition.
I have something back in my mind that this problem maybe due to generating the file system with a brandnew kernel, and then trying to use it on an older distribution.
darktable is a 64bit only application. When you use the link to Packages in the top right corner you can check yourself.
And no, there is no easy way to convert to 64bit. You should download an amd64 medium and repeat the installation.
Before doing that make sure the cdrom entry is out of the way. Put a # in front of the line to uncomment it, or remove the cdrom entry completely.
Alternative on my Daedalus:
# apt list darktable
Auflistung… Fertig
darktable/stable 4.2.1-4 amd64
Anyhow, have a look at the right top of this web page. There are 5 links. Use Devuan.org and scan through the available information, it might be helpful for a beginner.
I guess desktop drives are being replaced by ssds and nvmes today. The enterprise drives go into servers, NAS storage etc.
Anyhow: I never bought a hard drive where the manufacturer did not trust its product for 5 years warranty. WD Black and HGST did fulfill this requirement, I have several of them still around. And I wanted full warranty with easy check and direct manufacturer contact, no dealer inbetween. Fujitsu and Toshiba did not qualify for me because of this.
Can't imagine that POS does an installation without this essential package.
Maybe you simply need to use su - to get root access instead of simply su. The difference is the path.
What exactly do have, and what do you want to achieve?
When the violett URL is clicked on the link is opened, and usually correct. I don't use screenshots to save URLs.
Just installed POS in a VM: indeed the installation calls the debian multimedia repo in the sources.list.d directory. Access in my VM went fine, question is why the OP has a problem to access it. Network not set up correctly? DNS trouble?
I also found that per default just the main repo is present in the sources.list, and non-free-firmware is missing which might be crucial for the graphics card setup.
The other entries are present just commented out. So its easy to enable them. Just remove the # on the beginning.
Problem: debian multimedia repo not working, error being: no access to repo/packages.
Apparently this leads to the nvidia proprietary driver packages (and I'm sure other stuff) being uninstallable.
I am not a NVidea user, but I am sure that the NVidea drivers do not require any package from the debian multimedia repo.
My suggestion: uncomment it for the time being in the sources.list and get your graphics to work.
ntpdate and ntpsec are not installed by default in Daedalus, has to be done afterwards. With ntpsec the conf dir has moved to /etc/ntpsec.
BTW: timedatectl is a systemd tool, afaik not present on Devuan.
Tried to look at my 2 dev1galaxy cookies, no luck. I need to find a tool that allows to read the contents of the cookie. Or is there a tool within FF that allows to read the contents?
I am not aware of any timeout related to the login time on the forum. I can stay logged in as long as I like. Using FF ESR latest version on Daedalus.
Sometimes I use gedit or geany to prepare a longer post. But mainly because I have to leave the topic alone for a while, and don't want to leave the browser open or shut down the PC.
Maybe your problem is related to a forced IP change of your internet provider?
Electrical cars as currently built will turn out to be a dead end.
Seeing that my hardware has not changed significantly since I first installed Devuan Jesse ca. 2017 and will most probably not change in the coming years, is a dist-upgrade necessary?
Some ideas: You determine your necessities. As long as you are happy with the OS and the software you are running, you may keep Beowulf.
The open question is: no more upgrades/safety fixes for Beowulf. Can you live with that? I have seen your posts about xorg security issues. They are getting fixed with Daedalus.
Risk with latest releases: removal of support for older hardware. Is a matter of test.
What bloat is concerned: yes its possible that things like CSD are trickling down. But they still can be removed. And an installation with --no-install-recommends may also help to keep the system clean from unwanted software.
If you can afford it install a new SSD in the workstation. I assume its a legacy installation, so switching drives should be painless.
Well, chaos. You have as well Testing as Unstable in your sources. What are you trying to achieve with this setup? Do you know what you are doing?
Wrong. 6.1.0-18-amd64 and Debian 6.1.76-1 are kernel versions, the first one the Debian package numbering, second the version from kernel.org debianised. And yes, Devuan is using 1:1 Debian kernels.
You are running Devuan 5 Daedalus. Have a look at: inxi -F or cat /etc/os-release.
To clarify: Have you replaced the placeholder <user> with your username? And the placeholder <UUID> with the correct UUID of the device?
Maybe you show us with the drive connected:
# blkid
# lsblk
Then: the unallocated space is fine. But why does the ext4 file system have a msftdata flag, a Windows descriptor?
@GlennW: you have to make up your mind what you want on this PC - either a legacy install (that was my initial impression) - or an (U)EFI installation. Unfortunately the prerequisites and boundary conditions slightly differ from each other. Both is possible, but you will need to take the right steps to achieve your goal.
Legacy installation on a GPT partitioned drive:
- You will need to add a 1M unformatted partition with bios_grub flag set for writing the legacy grub into that.
- Boot the install media in legacy mode. A legacy grub install to a selected device will be executed by the installer.
(U)EFI-Installation on a GPT partitioned drive:
- You will need an EFS partition (Debian and Ubuntu installers refer to the ESP by the name "EFI boot partition"), FAT32, suggested size 512M to 2048M (Win10 comes with about 110M, but this is small but not safe against update and unforeseen issues). Marked as ESP and in many cases boot flag set.
- Boot the install media in UEFI-Mode. A EFI grub install to the ESP will be executed by the installer.
Something to read: https://askubuntu.com/questions/500359/ … -partition
I maybe have an idea what went wrong:
If I try to install-grub /dev/sda2, I get an error...
install-grub: error: failed to get canonical path
You have prepared a bios_grub partition, why do you want to install grub to /? Use /dev/sda instead. If booted in legacy mode grub-install will take care for the rest.