You are not logged in.
not 100% sure but i guess the problem is before upgrading from daedalus to excalibur you will need to install the usrmerge package.
and on excalibur you just have one line active in your sources.list:
deb http://deb.devuan.org/merged/ excalibur main contrib non-free non-free-firmware
Scan this forum for threads about this issue ...
Well, I have got two VBox VMs running Excalibur, based on Daedalus netinstalls and upgraded, one running LightDM and Mate, one Cinnamon, both on sysvinit, efi, encrypted, no Autologin. Can't tell when I set them, about summer last year? Both work fine so far. Looked at the syslinux packages in both VM's, none of them is installed.
I would first try with normal login.
As I looked into Devuan 5.0.1 ISOs I saw that I had it wrong: that ISO does not consider any Ventoy labelled partition. I then realized I have been referring to an unpublished Daedalus 5.1.0 that was handed out specifically to someone some while ago.
I remember reading that thread too.
But what does "mount" say (when chimaera installer at partitioning)? And does that partitioner offer a large number of partition types?
Ventoy stick booted, Secure Boot off, Chimaera netinstall started in efi mode.
When the partitioning is started and waits for the method to partition, Alt-F2 to the 2nd console, mount tells me:
rootfs, tmpfs, sysfs, devtmpfs, devpts, and then the interesting things:
/dev/sde2 on /cdrom type iso9660 (ro,relatime,nojoliet,check=s,map=n,blocksize=2048,iocharset=utf8)
none on /sys/firmware/efi/efivars type efivarfs (rw,relatime)
As mentioned in the private mail: I only had problems when skipping the topic "Loading additional modules" in the expert installer mode. I have got full choice, I am using manual partitioning and I am encrypting all my installations (with very few exceptions in a VM).
Hope that helps.
blkid output is this:
/dev/sdg1: LABEL="Ventoy" UUID="D7EA-AE3B" BLOCK_SIZE="512" TYPE="exfat" PTTYPE="dos" PARTUUID="f078671f-01"
/dev/sdg2: SEC_TYPE="msdos" LABEL_FATBOOT="VTOYEFI" LABEL="VTOYEFI" UUID="B2C8-40D2" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="f078671f-02"
I have not modified anything. Just used the Ventoy installer, let it do the job, nothing tweaked. Except for added a Tools folder to the exFAT partition for additional SW and files.
Hi Ralph,
my Ventoy stick is shown as this:
# fdisk -l /dev/sdg
Disk /dev/sdg: 114,61 GiB, 123060879360 bytes, 240353280 sectors
Disk model: SanDisk 3.2Gen1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xf078671f
Device Boot Start End Sectors Size Id Type
/dev/sdg1 * 2048 240287743 240285696 114,6G 7 HPFS/NTFS/exFAT
/dev/sdg2 240287744 240353279 65536 32M ef EFI (FAT-12/16/32)
I can boot the older Devuan releases as well in efi as in legacy mode and install them from the boot of the iso, the first language selection dialogue until the final eject media, they are fully installed afterwards. No limits.
Thanks, interesting news.
For sure remove the AMD Catalyst driver completely. Its outdated and useless.
Maybe you simply do a re-installation. If recklesswing is right support by the kernel is enough. Nevertheless, on first boot watch out for messages about missing firmware. If such messages appear, add non-free-firmware to your sources.list, do an apt update and install firmware-amd-graphics. I have got 5800 cards that require firmware.
PS: you say you got that card working on Debian Bookworm? Then there is no reason why it shouldn't work in Daedalus. Uses the same packages as Bookworm.
How is that card listed by lspci?
So far I haven't installed anything to support bluetooth on my travelling laptop. Wifi is working, that was enough.
As preparation for an aniversary party I want to enable bluetooth to be able to connect to a Sonos system to play some music. The laptop is running Daedalus with pipewire, that works fine on the internal speakers and headset if that is connected.
When I now look at what is happening when I try to install blueman, pipewire-alsa is removed and pulseaudio is installed instead. I don't want that.
Do I have alternatives?
My assumption is that the Atheros chipset is supporting as well wifi as bluetooth. Correct? Wifi is installed, drivers and firmware are present. Are any additions required for bluetooth?
lspci
...
04:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)7
Thanks, rolfie
Is this your first Daedalus installation? The fsmithreds suggestion is very relevant.
AMD cards are normally fully supported by kernel and firmware-amd-graphics.
Although I'd still like to ask here, since there's an ongoing conversation about it, is there an easy way to tell when an ISO will work on Ventoy or does the project need to specifically mention this? The reason I ask is because in the past I had similar problems with other ISO files, but I wasn't sure if they were caused because of this or just a bad USB stick.
No, there isn't an easy way. As far as I am concerned, Daedalus is the only release that fails on Ventoy. ASCII, Beowulf and Chimaera work fine. Same for all Debians I have tried, Arch Linux, AcroLinux, Mint > 20.1, LMDE 5 and 6, ...
On the other hand, Ventoy seems to be sort of dead, according to their web page there will be no further version past 0.99.
Devuan Daedalus is not compatible to Ventoy. Does not work.
Use dd or cp to write the image to an empty stick, that works fine.
If I am not mistaken you got 16G of RAM. Thats more than enough for a normal Devuan office use. You could easily allow 4G for a VM and not notice any performance limitations. Prerequisite: limit the number of open tabs in your browser.
A swap larger than the RAM is only required if you want to use hibernation.
regarding whether i can use my ssd as a buffer memory, i will need some more info on how to investigate and implementation
Forget about this idea. This was promoted for a while by Intel, they also had a product for that, and Seagate also had some hard disks with SSD cache on board in the portfolio, but never was really adopted in a bigger scale. This is sort of dead by now.
Give that a try:
groucho ALL=(root) NOPASSWD: /sbin/ifup eth0 /sbin/ifdown eth0
If Debian does Devuan should also do. Devuan is Debian - systemd packages + replacements. Kernel and drivers are the same.
I just gave examples, no guaranteed solutions. The OP does not use Testing or Unstable anyhow. Its his job to find out whats the best for him.
You obviously did not read nor understand the page I linked.
1.) Do not use the Devuan root server http://pkgmaster.devuan.org in your sources.list. This puts heavy load onto the master server.
2.) Use http://deb.devuan.org/merged and if that gives you not resolved or something similar, you might try:
3.) Use http://de.deb.devuan.org/merged as example for Germany. de. is the country prefix. If you are living in one of the worlds bigger countries, this migth be an option. Warning: I did use the de. option for a while some years ago, then it became a problem. I am back to 2.) with minimum hasle.
3.) Brr, the mirror_list.txt has been converted from an easy human readable format to the new Debian standard called DEB882 which is better readable by machines. Last but not least you might use this example: http://ftp.fau.de/merged using the mirror ftp.fau.de from Germany. Adapt to your needs.
As an apt user I use the following two commands:
# apt update
# apt full-upgrade -V
and I am getting the full picture every time.
There is a link to devuan.org on the top of the forum page. There you find a lot of useful information.
Try this page first: https://www.devuan.org/os/packages
I had some fun with hibernation recently. Finally it turned out that an older NEC based USB card in combination with some Toshiba memory stick caused my problems. Here is a link: https://dev1galaxy.org/viewtopic.php?id=6631
Carefully check the messages around going to sleep and when trying to wakeup whats going on there.
The screenshots you are showing here try to access beowulf which is Devuan 3. Daedalus is Devuan 5. You need to upgrade to Chimaera = Devuan 4 first and then to Devuan 5.
Edit /etc/apt/sources.list and replace beowulf with chimaera as a first step. I hope you are familiar with nano?
BTW: looks like there is an additional problem with resolving deb.devuan.org. There are several posts in the forum about this issue and hints how to resolve.
Looks like you are trying Ventoy, that tool does not work with Daedalus. And I would assume its the same with Excalibur.
Nothing should be commented out in a Daedalus sources.list, it isn't neccessary. It should look like this:
deb http://deb.devuan.org/merged/ daedalus main contrib non-free non-free-firmware
deb http://deb.devuan.org/merged/ daedalus-security main contrib non-free non-free-firmware
deb http://deb.devuan.org/merged/ daedalus-updates main contrib non-free
deb http://deb.devuan.org/merged/ daedalus-backports main contrib non-free non-free-firmware
I am using the recommended default. It works to about 99.9% for me. If you run into problems, replace deb.devuan.org with a suitable mirror.
Later I was on the web and tried to use the install scripts from firefox, brave and librewolf. All of them wouldn't install because it said it needed use stable instead of daedalus.
I am pretty sure dedicated install scripts for Debian will fail when they read a Daedalus sources.list. None of them will consider Devuan and like, they are written for stock Debian. No Devuan problem in itself. You have to do the installation manually. Read the instructions on the web pages and adapt the descriptions to Devuan Daedalus.
I run the Firefox ESR from the Mozilla website directly. Nowadays there is a deb package also.
I am sorry, you did not even give some basics about what your system looks alike. Which Devuan release? Which desktop and display manager? X11 or Wayland?
What about posting the output of inxi -Fzr?