You are not logged in.
I guess you need to load the kernel headers, afaik there is no linux-source in Devuan. You can either run an apt update as suggested by dice and then install linux-headers-amd64, or you try apt install linux-headers-4.19.0-9-amd64 which is outdated by now, but fits to the kernel you use.
rolfie
I ran into some problems when installing VirtualBox 6.1.18 on Beowulf-based Refracta.
Here's the relevant info:
$ cat /etc/apt/sources.list.d/virtualbox.list deb [arch=amd64] https://download.virtualbox.org/virtualbox/debian buster contrib# aptitude install virtualbox-6.1 -r The following NEW packages will be installed: libqt5opengl5{a} libqt5printsupport5{a} libsdl-ttf2.0-0{a} virtualbox-6.1 0 packages upgraded, 4 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/88.7 MB of archives. After unpacking 215 MB will be used. Do you want to continue? [Y/n/?] y Preconfiguring packages ... ... ...snip... ...
Well, I have used a different way to install VBox on my stock Beowulf installations (with backports kernels). Loaded the Debian10 package down to /tmp, installed it with dpkg -i followed by a apt -f install to correct all dependencies. No trace of any dbus errors. My latest learning: maybe an apt install ./package.deb takes care for the dependencies too.
In addition, I added the vboxdrv, vboxnetadp and vboxnetflt to the /etc/modules file.
I believe that this may be a solution (or partial solution):
# update-rc.d vboxdrv defaultsReference:
Instalando VirtualBox 6.0 en Devuan Beowulf
https://www.linuxito.com/cloud/1269-ins … an-beowulfVirtualBox runs and appears to (mostly) work. However, at least one function (USB passthrough) does not. The extension pack and guest additions have been installed, so that isn't the problem.
I have not seen any need to fool around with update-rc.d. Maybe the modules did the job.
Besides the installation of the extension pack, the USB passthrough depends on that the user using the machine is member of the vboxusers group. Make sure you/the user are member of this group. The group is created automagically, but the user(s) needs to be added manually.
P.S. Don't tell me not to use VirtualBox. I'm not ready to switch just yet.
Full ACK from my side.
rolfie
Also got a PCIe card with a Renesas 720201 installed. Used the same tools and failed:
05:00.0 USB controller: Renesas Technology Corp. uPD720201 USB 3.0 Host Controller (rev 03)Copied the files to /lib/firmware/renesas. I got:
/lib/firmware/renesas# ./upd72020x-load -r -b 05 -d 00 -f 0 -s -o 720201.org
Doing the reading
bus = 5
dev = 0
fct = 0
fname = (null)
ERROR: wrong vendorid/devid. Expected an UPD720201 or UPD720202 chip and this is not one!
reported vendorid/devid: 1912:0014
======> FAILEDI would claim the program finds the chip, but maybe still has the old NEC vendor ID coded? I tried to understand the .c file, buit couldn't find any reference to the expected/accepted vendor IDs. 1912:0014 is the correct ID for a 72020x device according https://pci-ids.ucw.cz/read/PC/1912/0014.
Program too old?
rolfie
Try apt -f install ....
rolfie
@Andre4freedom: I need the hybrid CSM mode with UEFI first to be able to boot the parallel Win7 installation I still need for a few things. When I have more time I should loook into copying the Win7-SSD to a VM.
@HOAS: I never use Secure Boot. For me all the culprits related to this do not matter. I am happily using EFI mode w/o SB. This allows to use modified efi entries like devuan3/devuan4 for my installations.
The PC is operating now with Beowulf and Chimaera on the new nvme plus the old Win7.
Strange was these locale issues, never had them before.
rolfie
Thanks rolfie.
Here what
apt list lsb
outputs for me:hermann@pinkman:~$ apt list lsb Auflistung... Fertig hermann@pinkman:~$Nothing obviously
@Head_on_a_Stick:
On https://lwn.net/Articles/658809/ I found: "Debian dropping the Linux standard base". Does this mean that lsb-modules are no longer necessary? And if so, does this also apply to devuan?
Thanks for answer
You forgot the most important thing: "*"
Have a very close look at what I did post and compare to yours.
rolfie
I am sorry, don't seem to find this button on my screen(s). ![]()
Being logged in, I call up one of my original posts (I assume the option is only available for the OP). No sign of a "Mark solved" link. I can find "post reply", Preview, all the bulletin tags, but no mark. Would be for sure nice to have .....
I am using Firefox ESR, latest update. UBlock Origin and Noscript are active. What are the boundary condition to get this link? Where exactly should it be?
rolfie
Edith: same with Palemoon, just tried it.
I have:
# apt list lsb*
Auflistung... Fertig
lsb-base/stable,stable,now 10.2019051400 all [installiert]
lsb-release/stable,stable,now 10.2019051400 all [Installiert,automatisch]rolfie
The button is called "Edit".
rolfie
Got the 3.1.0 with openrc to work, Cinnamon as desktop, efi mode, /boot unencrypted, encrypted LVM for root and swap, separate home.
Despite having a mirror set up, the CDROM still was present in the sources.list. Easy to fix.
The installation booted grub with shimx64.efi. I removed it afterwards.
Locale was fine with this setup.
Would say that runit is experimental in the current status.
rolfie
Update to todays status
Got the Beowulf 3.0.0 based Chimaera installation on P(artition)4/P5 on the new NMVe working fine with openrc as init and Cinnamon as desktop. I created a devuan4 entry in the efi flash which is used to start this installation.
Went on trying to revive the Beowulf 3.1.0 based installation on P2/P3 of the NVMe. There I am stuck.
I did a new install overwriting the last one. Used runit as init system, the rest being as before, i.e. efi expert install to cli, encrypted LVM with unencrypted boot. First thing that stuck my eye: the installation did not get stuck on the grub prompt but booted fine, the grub splash was shown immediately, I could enter the encryption key and log in as root.
The CD was still enabled in the sources.list, locale at C.UTF-8. Fixed the sources.list as first action. In the efi I found a debian entry holding a grub.cfg, and a devuan entry holding all the usual files including the shimx64.efi. Removed grub-efi-amd64-signed and did a new grub-install --bootloader-id=devuan3 --no-uefi-secure-boot. A new entry devuan3 was generated and points to grubx64.efi as expected. Removed the debian and devuan entries on the file system and cleaned the efi flash with the efibootmgr -b 000x -B.
The modifed setup boots up to the command prompt. Against my expectation, I still have the locale issue, and the efivarfs is not mounted. efibootmgr tells me that this system does not support efi variables. Well, mounted the efivarfs to the usual directory and can read the variables now. efibootmgr points to the correct entry, devuan3 still is present.
Is it possible that runit does forget to mount efivarfs?
rolfie
Update on the Beowulf 3.0.0 install on P4/P5:Same issues basically, the boot also ends in the grub-console, no grub menu shown.
Started the rescue mode and fixed issue #1. Looked at the locale, also is at C.UTF-8. Then fidelled a bit with boot, grub-install and update-grub, grub.cfg, efivars and the efibootmgr. Finally used efibootmgr -v and saw that all Devuan entries in the efi memeory were referring to shimx64.efi, despite my disabling Secure Boot.
Well, searched the man pages for grub-install and found the option --no-uefi-secure-boot.
A grub-install --no-uefi-secure-boot --bootloader-id=devuan4 brought a grubx64.efi into play. A reboot showed the usual blue grub splash screen, I am now working on P4/P5 and the Chimaera upgrade. The locale issue is gone too.
Next step is trying the same on the 3.1.0 install.
What I am wondering about: how did I get into this situation in the first place?
rolfie
Have installed a fresh nvme on my older workstation with X470 chipset, Ryzen7 2700X, AMD 570 graphics card. Now I try to bring up the PC with Beowulf and Chimaera in parallel installations, but I face several issues I did not see with 3.0.0 installs. HW set to Fast Boot disabled, CSM on, UEFI driver first, Secure Boot off. The old ASCII/Beowulf installs did work with that setup.
Downloaded the Desktop DVD image, copied this to a new USB stick with rufus (same procedure as used with 3.0.0). Stick booted in EFI mode, Expert install, German language and Keyboard, manual paritioning (P1=EFI, P2=/boot, P3=encrypted LVM), enable contrib/nonfree and backports, disable sources, use a mirror from Germany, ..... just go for a CLI install, no graphical desktop yet.
1.) Minor issue: The sources.list still contains one uncommented line referring to the CD-ROM.
2.) locale is set to LANG=C.UTF-8, LANGUAGE=de. dpkg-reconfigure locales in rescue mode does not change anything. I just have de-DE.UTF-8 selected, no errors produced, locale does not change??
3.) Managed to break the locale on the first install when trying to fix this. Couldn't enter my special characters composed with ALTGR any more. Did a second installation with same parameters, overwriting the first install. Now I end up in the grub console. Even after a rescue session and re-installing grub. Häääh?
Next thing I will try is doing an install from my old 3.0.0 medium generated last summer on P4=/boot for Chimaera and P5 for encrypted LVM for Chimaera.
Any feedback is welcome.
rolfie
It may not be that simple. All depends on if the meta package linux-image-amd64 is installed, and if this is linked to the main repository or to backports.
If you choose linux-image-amd64 during installation and not one of the presented dedicated kernel images, apt update && apt upgrade will check for updates and install them when available. For Beowulf this is the 4.19 kernels.
When you only install one dedicated kernel from backports, that will stay forever and not be affected by apt update && apt upgrade. Unless you install the meta-package from backports. Then the stock kernel is left alone and backports is updated.
You can't have both.
rolfie
You may give the latest BIOS a try, good luck with that, I hope it helps. In my case it did not do anything.
When I look at what you posted, the dump-type stuff does not belong there. That may be some data written by the linux kernel into EFI flash.
Good luck, rolfie
Read this thread: https://dev1galaxy.org/viewtopic.php?id=3616
My suspicion: on a crash the kernel overwrites contents of the efi flash. Got an older socket AMD3+ board that had a similar issue (https://dev1galaxy.org/viewtopic.php?id=2820).
Now all my installations have /sys/firmware/efi/efivars/ set to ro in fstab.
I had the ASUS Prime X470-Pro sent back to service. They flashed a new bios and fixed the efi memory, something I could not achieve with the means available to a normal user. Now the board works normal again.
rolfie
CD1 is called devuan_beowulf_3.1.0_amd64-server.iso
Beginning of February I downloaded a current Bullseye netinstall image and installed it in VBox. Can't remember that I got an init choice like in Devuan.
rolfie
Started off with sysvinit under ASCII some years ago, then experimented with openrc in VBox and finally installed an AMD470/Ryzen 2700X with openrc / ASCII. Motivation: refer to HOAS comment in the previous post.
Meanwhile all my active PCs at home have moved to openrc/Beowulf. With my kind of operation (office and internet, a nfs fileserver in the background) I have no issues found.
Currently I am investigating runit/Chimaera in VBox.
I can only encourage you to try openrc.
rolfie
Mate 1.20.4 from the Devuan repository.
Rolfie
sudo apt -t beowulf-backports install linux-image-amd64
Should also work and provide automatic kernel updates.
Kernel:
apt list linux-image-5*
apt install linux-image-5.10.0-0.bpo.3-amd64Firmware:
apt list firmware-linux-nonfree* -a
apt -t beowulf-backports install firmware-linux-nonfreeWhat happens on
apt full-upgrade?
rolfie wrote:The main repo is missing.
http://deb.devuan.org/merged beowulf main contrib non-freeConsider if you need to complie packages. If not, disable the deb-src lines.
What does non-free mean in this context? Licenses other than GPL, MIT, and their kin?
Have a read: https://www.debian.org/intro/free.en.html
non-free means code that is propriatry. Unfortunately you will need non-free stuff to get your tg3 working.
Same with me and my AMD GPUs.
rolfie
Actually your post is off topic, you would have better written a new post.
Read https://www.devuan.org/os/packages
rolfie