Posts by rolfie

rolfie · Hardware & System Configuration

Beowulf, Mate desktop. I run a script during user login that opens a Veracrypt volume. Veracrypt is installed same way as in ASCII, same settings in sudoers, script copied from ASCII with same permissions.

Situation is that in Beowulf I am asked to enter either a user or the root password. What can be the reason for this changed behaviour?

Thanks for any idea, rolfie

rolfie · Other Issues

Beowulf with Mate installed in parallel to ASCII.

I selectively copied over the session settings from .putty in my ASCII home to .putty on the new Beowulf home.

Direct look into putty, log off and in again, reboot: no listing of the old sessions in the Beowulf putty. Access rights are to the user.

When reading posts from the internet a simple copy should be enough.

What else might have changed?

rolfie

rolfie · Installation

Debuser2018 wrote:

With Beowulf, boot time takes almost 3 minutes due to udev waiting and time out. This happens with kernel 5.6 from beowuf-backports. I've posted here:https://dev1galaxy.org/viewtopic.php?pid=22907
No clues why this is happening.

Got Beowulf on kernel 5.6 running fine on two desktop machines. You must have individual hickups, hardware problems or a device that having issues.

rolfie

rolfie · Other Issues

Guess its system specific. Got two machines here that work fine with Beowulf and kernel linux-image-5.6.0-0.bpo.2-amd64. Though I am using the openrc version that comes with Beowulf.

rolfie

rolfie · Installation

Ok, Lars thinks your CPU does support 64bit, and the 64bit Life media also runs. Lets take that as granted.

Then lets look at the media used for installation.

CD: You got old mature HW including an older CD/DVD drive (at least I assume this). When you use oldfashioned CD or DVD drives to burn and read the media, the chance is high that it should work if the media quality is ok. From my experience: burning a CD on a BR drive and reading it in another PC with a BR drive may not work. Tried this with a gparted life CD: starting gparted is a gamble. I got lots of IO errors, sometimes gparted starts ok, sometimes not. The CD itself is fine, it booted perfectly with no IO errors in an older DVD burner. Same happened with Beowulf alpha and beta versions burned to CD, and installations typically fail when IO errors appear.

Memory stick: On my modern hardware I now only use flash drives for installation. I also used rufus on Win7 to generate the bootable sticks. Done that for ASCII, Arch, Beowulf in various steps, and gparted life, all worked fine.
Note: there are people around that insist in that only the dd copy is the correct way to generate a bootable flash drive. Never used this.

One thing that might cause an installation to fail is if the flash drive itself is dodgy. If you can exchange it and try a different brand. I use a Windows utility called h2testw to check the flash drives. Don't know if this is available in English too.

Another hint what might help: look on the other consoles if you see any errors showing up there.

Good luck, rolfie

rolfie · Installation

Hi Lars,

yes I got Ryzen 7 2700X that is clearly a 64bit CPU, I am on amd64. The OP has a Core2 CPU 4300, whatever that is, I have no idea. His/her lscpu printout indicates a 686 CPU with 64bit capability. Is that enough for amd64?

rolfie

rolfie · Installation

Perhaps because your CPU does not support x86_64 mode? You get: Architecture: i686, I think thats the i386 branch.

I am getting for a real 64 bit CPU:

# lscpu
Architecture:        x86_64
CPU op-mode(s):      32-bit, 64-bit
Byte Order:          Little Endian
Address sizes:       43 bits physical, 48 bits virtual
CPU(s):              16
On-line CPU(s) list: 0-15
Thread(s) per core:  2
Core(s) per socket:  8
Socket(s):           1
NUMA node(s):        1
Vendor ID:           AuthenticAMD
CPU family:          23
Model:               8
Model name:          AMD Ryzen 7 2700X Eight-Core Processor
Stepping:            2
CPU MHz:             2194.882
CPU max MHz:         3700,0000
CPU min MHz:         2200,0000
BogoMIPS:            7385.23
Virtualization:      AMD-V
L1d cache:           32K
L1i cache:           64K
L2 cache:            512K
L3 cache:            8192K
NUMA node0 CPU(s):   0-15
Flags:               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb hw_pstate sme ssbd sev ibpb vmmcall fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflushopt sha_ni xsaveopt xsavec xgetbv1 xsaves clzero irperf xsaveerptr arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov succor smca

Have you ever had a 64 bit distro working?

rolfie

rolfie · Installation

Make sure you have contrib main non-free enabled in your sources. It maybe worth also checking if there is an update of the firmware package available in backports.

rolfie

rolfie · Installation

There is a 5.6 kernel in the backports already. I am running this on two machines, and a 5.5 on my file server.

rolfie

rolfie · Desktop and Multimedia

Without knowing that fact, I now see that under ASCII pulse was installed. Maybe thats why the setup was quite easy and comfortable.

My conclusion: pure ALSA is not really comfortable, it lacks a reasonable control center that allows to setup the sound system according to the real HW and the users demands.

rolfie

rolfie · Desktop and Multimedia

And here is the same from my ASCII installation.

# cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version k4.19.0-0.bpo.8-amd64.

# apt list *alsa*
Auflistung... Fertig
alsa-utils/oldstable,now 1.1.3-1 amd64  [Installiert,automatisch]
alsamixergui/oldstable,now 0.9.0rc2-1-10 amd64  [installiert]
alsaplayer-alsa/oldstable,now 0.99.81-2 amd64  [Installiert,automatisch]
alsaplayer-common/oldstable,now 0.99.81-2 amd64  [Installiert,automatisch]
alsaplayer-gtk/oldstable,now 0.99.81-2 amd64  [installiert]
libalsaplayer0/oldstable,now 0.99.81-2 amd64  [Installiert,automatisch]
volumeicon-alsa/oldstable,now 0.4.6-2.2+b1 amd64  [installiert]

# apt list *pulse*
Auflistung... Fertig
apulse/oldstable,now 0.1.9-6 amd64  [installiert]
gstreamer1.0-pulseaudio/oldstable,now 1.10.4-1 amd64  [installiert]
libpulse-mainloop-glib0/oldstable,now 10.0-1+deb9u1 amd64  [Installiert,automatisch]
libpulse0/oldstable,now 10.0-1+deb9u1 amd64  [Installiert,automatisch]
libpulsedsp/oldstable,now 10.0-1+deb9u1 amd64  [Installiert,automatisch]
pulseaudio/oldstable,now 10.0-1+deb9u1 amd64  [installiert]
pulseaudio-utils/oldstable,now 10.0-1+deb9u1 amd64  [Installiert,automatisch]

# apt list *jack*
Auflistung... Fertig
libjack-jackd2-0/oldstable,now 1.9.10+20150825git1ed50c92~dfsg-5 amd64  [Installiert,automatisch]

# aplay -l
**** Liste der Hardware-Geräte (PLAYBACK) ****
Karte 0: HDMI [HDA ATI HDMI], Gerät 3: HDMI 0 [HDMI 0]
  Sub-Geräte: 1/1
  Sub-Gerät #0: subdevice #0
Karte 0: HDMI [HDA ATI HDMI], Gerät 7: HDMI 1 [HDMI 1]
  Sub-Geräte: 1/1
  Sub-Gerät #0: subdevice #0
Karte 0: HDMI [HDA ATI HDMI], Gerät 8: HDMI 2 [HDMI 2]
  Sub-Geräte: 1/1
  Sub-Gerät #0: subdevice #0
Karte 0: HDMI [HDA ATI HDMI], Gerät 9: HDMI 3 [HDMI 3]
  Sub-Geräte: 1/1
  Sub-Gerät #0: subdevice #0
Karte 0: HDMI [HDA ATI HDMI], Gerät 10: HDMI 4 [HDMI 4]
  Sub-Geräte: 1/1
  Sub-Gerät #0: subdevice #0
Karte 0: HDMI [HDA ATI HDMI], Gerät 11: HDMI 5 [HDMI 5]
  Sub-Geräte: 1/1
  Sub-Gerät #0: subdevice #0
Karte 1: Generic [HD-Audio Generic], Gerät 0: ALC1220 Analog [ALC1220 Analog]
  Sub-Geräte: 1/1
  Sub-Gerät #0: subdevice #0
Karte 1: Generic [HD-Audio Generic], Gerät 1: ALC1220 Digital [ALC1220 Digital]
  Sub-Geräte: 1/1
  Sub-Gerät #0: subdevice #0

# cat /proc/asound/cards
 0 [HDMI           ]: HDA-Intel - HDA ATI HDMI
                      HDA ATI HDMI at 0xfce60000 irq 106
 1 [Generic        ]: HDA-Intel - HD-Audio Generic
                      HD-Audio Generic at 0xfcd00000 irq 108

The Mate sound applet shows much more selections and a 5.1 loudspeaker system I have installed.

rolfie

rolfie · Desktop and Multimedia

Here is the output of a set of collected commands from my Beowulf setup. X470 mainboard with encrypted LVM on openrc with Mate desktop, manually installed from a cli minimal install using apt install xorg lightdm mate-desktop-environment-extras.

# lspci -knn | grep -A2 Audio
0c:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 580] [1002:aaf0]
	Subsystem: Sapphire Technology Limited Ellesmere [Radeon RX 580] [1da2:aaf0]
	Kernel driver in use: snd_hda_intel
--
0e:00.3 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) HD Audio Controller [1022:1457]
	Subsystem: ASUSTeK Computer Inc. Family 17h (Models 00h-0fh) HD Audio Controller [1043:8733]
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel

# aplay -l
**** Liste der Hardware-Geräte (PLAYBACK) ****
Karte 0: HDMI [HDA ATI HDMI], Gerät 3: HDMI 0 [HDMI 0]
  Sub-Geräte: 1/1
  Sub-Gerät #0: subdevice #0
Karte 0: HDMI [HDA ATI HDMI], Gerät 7: HDMI 1 [HDMI 1]
  Sub-Geräte: 1/1
  Sub-Gerät #0: subdevice #0
Karte 0: HDMI [HDA ATI HDMI], Gerät 8: HDMI 2 [HDMI 2]
  Sub-Geräte: 1/1
  Sub-Gerät #0: subdevice #0
Karte 0: HDMI [HDA ATI HDMI], Gerät 9: HDMI 3 [HDMI 3]
  Sub-Geräte: 1/1
  Sub-Gerät #0: subdevice #0
Karte 0: HDMI [HDA ATI HDMI], Gerät 10: HDMI 4 [HDMI 4]
  Sub-Geräte: 1/1
  Sub-Gerät #0: subdevice #0
Karte 0: HDMI [HDA ATI HDMI], Gerät 11: HDMI 5 [HDMI 5]
  Sub-Geräte: 1/1
  Sub-Gerät #0: subdevice #0
Karte 1: Generic [HD-Audio Generic], Gerät 0: ALC1220 Analog [ALC1220 Analog]
  Sub-Geräte: 0/1
  Sub-Gerät #0: subdevice #0
Karte 1: Generic [HD-Audio Generic], Gerät 1: ALC1220 Digital [ALC1220 Digital]
  Sub-Geräte: 1/1
  Sub-Gerät #0: subdevice #0

List cleaned out to only show the installed packages.

# apt list *alsa*
Auflistung... Fertig
alsa-tools/stable,now 1.1.7-1 amd64  [installiert]
alsa-utils/stable,now 1.1.8-2 amd64  [installiert]
alsamixergui/stable,now 0.9.0rc2-1-10 amd64  [installiert]
gstreamer1.0-alsa/stable,now 1.14.4-2 amd64  [installiert]
volumeicon-alsa/stable,now 0.5.1+git20170117-1 amd64  [installiert]

# apt list *pulse*
Auflistung... Fertig
libpulse-mainloop-glib0/stable,now 12.2-4+deb10u1 amd64  [Installiert,automatisch]
libpulse0/stable,now 12.2-4+deb10u1 amd64  [Installiert,automatisch]

# apt list *jack*
Auflistung... Fertig
libjack-jackd2-0/stable,now 1.9.12~dfsg-2 amd64  [Installiert,automatisch]

Looks like volumicon-alsa is overwritten by the Mate sound setting applet. Also qasmixer does not show up in the panel.

In this setup I have no chance to setup defaults. The Mate sound applet looks poor, I don't have the controls I have in ASCII. The Realtek is displayed as having a Mono speaker. Too bad, I have pasted some screenshots in a LO document together with the output from a lot of commands, should have saved them individually.

rolfie

rolfie · Desktop and Multimedia

Head_on_a_Stick wrote:

There are several ways to set the default audio device for ALSA: https://wiki.archlinux.org/index.php/Ad … sound_card

Thanks, I have been through that document several times. Its informative but does not cover all the issues.

rolfie

rolfie · Installation

Are you using LVM? I am using openrc on encrypted systems with LVM, no issues with shutdown except that you need a patch to speed the closing of the volumes and the LVM: https://dev1galaxy.org/viewtopic.php?id=2690&p=2 #34.

Read the thread if you experience similar problems. Maybe it helps.

rolfie

rolfie · Desktop and Multimedia

Hi Lars,

larsH wrote:

In voulmeicon (wich are solely using alsa) you can in preferences set your device. I am sure it will rembember it. And yes you will have to add it the startup of your desktop. In alsamixer F6 will allow you to do the same.

Don't know how you do that. Under Beowulf I do not get the option to change the soundcard in volumeicon. And no way to modify the default in alsamixer. I can select a device and configure the channels, the settings are remembered, but no way to assign the Realtek Analogue to default.

I found a way to get audio in Firefox working. Created a /etc/asound.conf with this contents:

defaults.pcm.!card Generic
defaults.ctl.!card Generic
defaults.pcm.!device 0
defaults.ctl.!device 0

where Generic points to my Realtek Audio chip on the main board, and device 0 to the Analogue output. And changed the Firefox starter to apulse /opt/firefox/firefox. Currently I am listening to a Youtube video playing Summer Wine from Nancy Sinatra & Lee Hazlewood......

Such a fiddeling.....

rolfie

rolfie · Desktop and Multimedia

A few reboots later: Audacious still working, volumeicon-alsa is in the tray, Firefox plays Youtube videos without sound.

Audacious seems to remember the settings which is perfect.

Mean thing about volumeicon-alsa is that you have to call (/usr/bin/)volumeicon in the Startup files.

Firefox seems to depend on the ALSA default, which still is not set.

Need to go on.

rolfie

rolfie · Desktop and Multimedia

It took quite a while to get Audacious to play sound on my X470 board. Finally it does. Here is a summary. Don't know yet if the result is persistant, but thats the next post probably.

Beowulf is installed in parallel to ASCII, where sound is working fine. I'm running Mate on an encrypted LVM, and since today with backports kernel 5.6. HW is a Prime X470 Pro mainboard with Realtek Audio and a RX570 Pulse AMD graphics card.

Copied my Audacious playlist from ASCII to Beowulf.

Per default libpulse0 and libpulse-mainloop-glib0, and if I am not mistaken, I can't get rid of them because Mate (mate-settings-daemon) depends on them.

alsamixer allows to select either HDMI from the RX570 as device 0 or the Realtek as device 1. The crucial thing is that I haven't found any way to set the Realtek as default. Audacious would react with the error message ALSA error: snd_pcm_open failed.

Searched this forum and the internet for hints to a solution, and was about to try to write a conf file, when I had the idea first to check the Audacious settings. And that did the job. Selecting the 5.1 Analog device from a very long list did the job, at least for the time being. Music is playing while I am typing this.

qasmixer is installed, but not visible as a tray icon. I guess I have to add this program to the startup folder.

Conclusion: there seems to be no easy way to configure nowadays sound systems under ALSA.

rolfie

rolfie · Other Issues

Again hurrah, finally got it sorted, its working now. I can boot into Beowulf from the grub in my ASCII installation, despite my bad EFI.

@HOAS: I owe you a crate of Frankonian beer.

Took me a while to sort everything. The uuids and the kernel were the easy part. I had to add insmod lvm and ext2, the hardest bit was to figure out what to replace "cryptroot" with. There you need to enter the /dev/mapper-name for the decrypted in my case ext4 root device.

Have a nice Sunday, cheers.

rolfie

PS: I would be interested where and how you found the above info. I was searching around with the duck with keywords grub(2) custom.cfg encrypted and found references to Arch and Ubuntu wikis and a lot of rants/posts from various forums, but none was really pointing to the right thing (for me at least).

rolfie · Other Issues

Hurrah, after renaming grubx64.efi an additional strange entry is displayed on F8, and it actually boots Beowulf. Thanks for the slab.

Lets see if I also can get the custom cfg to work, but that a topic for tomorrow, I am too tired already. Too many typos...

Have a nice evening, rolfie

rolfie · Other Issues

You got me, just copied grubx64.efi over. Will rename it and give it another try.

Well, also prepared a custom.cfg. The menu entry is added, but: both my ASCII and Beowulf are encrypted LVMs with unencrypted /boot partitions. I tried the UUID of the encrypted partition. When I select the new entry, it clearly states that vmlinuz isn't found. Don't know yet how to deal with this situation.

Thanks for your continous input, rolfie

rolfie · Other Issues

Another update to post #5:
Added EFI/BOOT/ to the efi partition and copied grubx64.efi from Beowulf into there. Rebooted and tried F8 = Boot override: no sign of a /BOOT entry. Just got Win7, ascii and a memory stick that on presented.

rolfie

rolfie · Other Issues

On my X470 from ASCII:

# cd /boot/efi/efi
/boot/efi/efi# ls -la
insgesamt 2
drwx------ 4 root root 512 Jun 18 21:23 .
drwx------ 4 root root 512 Jan  1  1970 ..
drwx------ 2 root root 512 Jun 18 09:45 ascii
drwx------ 2 root root 512 Jun 15 08:15 beowulf
/boot/efi/efi# cd /sys/firmware/efi
/sys/firmware/efi# ls -la
insgesamt 0
drwxr-xr-x  6 root root    0 Jun 20 21:25 .
drwxr-xr-x  6 root root    0 Jun 20 10:33 ..
-r--r--r--  1 root root 4096 Jun 20 22:59 config_table
drwxr-xr-x  2 root root    0 Jun 20 21:24 efivars
drwxr-xr-x  3 root root    0 Jun 20 22:59 esrt
-r--r--r--  1 root root 4096 Jun 20 22:59 fw_platform_size
-r--r--r--  1 root root 4096 Jun 20 22:59 fw_vendor
-r--r--r--  1 root root 4096 Jun 20 22:59 runtime
drwxr-xr-x 20 root root    0 Jun 20 22:59 runtime-map
-r--------  1 root root 4096 Jun 20 22:59 systab
drwxr-xr-x 14 root root    0 Jun 20 21:23 vars
root@rh050:/sys/firmware/efi# os-prober
/dev/sda1@/efi/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows:efi

Beowulf was installed in efi mode. 100% sure. Also tried the suggestion from post #5:

# mount -t efivarfs efivarfs /sys/firmware/efi/efivars
mount: efivarfs is already mounted or /sys/firmware/efi/efivars busy
       efivarfs is already mounted on /sys/firmware/efi/efivars
# efibootmgr -v
No BootOrder is set; firmware will attempt recovery

rolfie

rolfie · Other Issues

Follow up: maybe I am stubborn, but I have changed the setup of my X470 main board to pure EFI and I simply expect it to work, because every "expert" advertises EFI as the future and CSM as being outdated. I wanna use it. I am not trying to use it outside specs, or misuse it in some strange way. When I write an EFI entry I expect this procedure to work as described and that the entry still is present and selectable past the next bootup. And that I can select other entries I have written before, that they are not getting destroyed.

=> the BIOS/EFI of my X470 main board is bad and broken. If you carefully read what I have descibed in this thread I think you have to come to the same conclusion. Additionally it looks like there is no regular way to reset the EFI part to defaults.

@HOAS: Since I am on PURE EFI without CSM, there is no boot entry for Beowulf in my ASCII grub menu. os-prober does only find the Win7 boot manager on the Win7-SSD. The same on a different mainboard with X570 chipset. Arch and Beowulf are present on the same NVME, I only can start the second OS via the boot override. I have just seen that an Ubuntu wiki claims that os-prober should be able to find another OS on the PC - here in my environment it does not work in two instances.

I have searched the internet for ways to add a custom configuration other than Windows. Again I found something in the Ubuntu wiki, but I am not sure if that skript will avoid starting another grub from the ASCII grub. The procedure must be safe by not mingling the two distros together so that I can run updates safely. Haven't tried it yet. I might raise another thread about this topic.

I have done a compare of the X470 and the X570 EFI setting. Here is the result. X470 on the top, X570 on the bottom.

# efibootmgr -v
No BootOrder is set; firmware will attempt recovery

# efibootmgr -v -v
Could not read variable 'BootNext': No such file or directory
error trace:
 vars.c:318 vars_get_variable(): open(/sys/firmware/efi/vars/BootNext-8be4df61-93ca-11d2-aa0d-00e098032b8c/raw_var, O_RDONLY) failed: No such file or directory
 lib.c:145 efi_get_variable(): ops->get_variable failed: No such file or directory
Could not read variable 'BootCurrent': No such file or directory
error trace:
 vars.c:318 vars_get_variable(): open(/sys/firmware/efi/vars/BootCurrent-8be4df61-93ca-11d2-aa0d-00e098032b8c/raw_var, O_RDONLY) failed: No such file or directory
 lib.c:145 efi_get_variable(): ops->get_variable failed: No such file or directory
Could not read variable 'Timeout': No such file or directory
error trace:
 vars.c:318 vars_get_variable(): open(/sys/firmware/efi/vars/Timeout-8be4df61-93ca-11d2-aa0d-00e098032b8c/raw_var, O_RDONLY) failed: No such file or directory
 lib.c:145 efi_get_variable(): ops->get_variable failed: No such file or directory
Could not read variable 'BootOrder': No such file or directory
error trace:
 vars.c:318 vars_get_variable(): open(/sys/firmware/efi/vars/BootOrder-8be4df61-93ca-11d2-aa0d-00e098032b8c/raw_var, O_RDONLY) failed: No such file or directory
 lib.c:145 efi_get_variable(): ops->get_variable failed: No such file or directory
 efibootmgr.c:363 read_order(): efi_get_variable failed: No such file or directory
No BootOrder is set; firmware will attempt recovery
Could not read variable 'MirrorCurrent': No such file or directory
error trace:
 vars.c:318 vars_get_variable(): open(/sys/firmware/efi/vars/MirrorCurrent-7b9be2e0-e28a-4197-ad3e-32f062f9462c/raw_var, O_RDONLY) failed: No such file or directory
 lib.c:145 efi_get_variable(): ops->get_variable failed: No such file or directory
Could not read variable 'MirrorRequest': No such file or directory
error trace:
 vars.c:318 vars_get_variable(): open(/sys/firmware/efi/vars/MirrorRequest-7b9be2e0-e28a-4197-ad3e-32f062f9462c/raw_var, O_RDONLY) failed: No such file or directory
 lib.c:145 efi_get_variable(): ops->get_variable failed: No such file or directory

# mount -t efivarfs efivarfs /sys/firmware/efi/efivars
# cd /sys/firmware/efi/efivars
/sys/firmware/efi/efivars# ls -la
insgesamt 0
drwxr-xr-x 2 root root    0 Jun 20 21:24 .
drwxr-xr-x 6 root root    0 Jun 20 21:23 ..
-rw-r--r-- 1 root root   38 Jun 20 21:24 ConIn-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   40 Jun 20 21:24 ConOut-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root    5 Jun 20 21:24 CurrentPolicy-77fa9abd-0359-4d32-bd60-28f4e78f784b
-rw-r--r-- 1 root root    5 Jun 20 21:24 DeploymentModeNv-97e8965f-c761-4f48-b6e4-9ffa9cb2a2d6
-rw-r--r-- 1 root root    8 Jun 20 21:24 Kernel_ATPSiStatus-77fa9abd-0359-4d32-bd60-28f4e78f784b
-rw-r--r-- 1 root root    8 Jun 20 21:24 Kernel_EntRevokeSiStatus-77fa9abd-0359-4d32-bd60-28f4e78f784b
-rw-r--r-- 1 root root    8 Jun 20 21:24 Kernel_RvkSiStatus-77fa9abd-0359-4d32-bd60-28f4e78f784b
-rw-r--r-- 1 root root    8 Jun 20 21:24 Kernel_SiStatus-77fa9abd-0359-4d32-bd60-28f4e78f784b
-rw-r--r-- 1 root root    8 Jun 20 21:24 Kernel_SkuSiStatus-77fa9abd-0359-4d32-bd60-28f4e78f784b
-rw-r--r-- 1 root root    8 Jun 20 21:24 Kernel_WinSiStatus-77fa9abd-0359-4d32-bd60-28f4e78f784b
-rw-r--r-- 1 root root   11 Jun 20 21:24 SecureBootSetup-7b59104a-c00d-4158-87ff-f04d6396a915
-rw-r--r-- 1 root root 5804 Jun 20 21:24 StdDefaults-4599d26f-1a11-49b8-b91f-858745cff824

# efibootmgr -v
BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0000,0001,000E,000F
Boot0000* devuan	HD(1,GPT,47fa57a7-5161-4d26-8b98-90abee299b5f,0x800,0x400000)/File(\EFI\DEVUAN\GRUBX64.EFI)
Boot0001* Arch	HD(1,GPT,47fa57a7-5161-4d26-8b98-90abee299b5f,0x800,0x400000)/File(\EFI\ARCH\GRUBX64.EFI)
Boot000E* debian	HD(1,GPT,47fa57a7-5161-4d26-8b98-90abee299b5f,0x800,0x400000)/File(\EFI\DEBIAN\GRUBX64.EFI)..BO
Boot000F* UEFI: SanDisk, Partition 1	PciRoot(0x0)/Pci(0x8,0x1)/Pci(0x0,0x3)/USB(1,0)/HD(1,MBR,0x97df71f4,0x800,0x1ca3800)..BO

# efibootmgr -v -v
Could not read variable 'BootNext': No such file or directory
error trace:
 vars.c:332 vars_get_variable(): open(/sys/firmware/efi/vars/BootNext-8be4df61-93ca-11d2-aa0d-00e098032b8c/raw_var, O_RDONLY) failed: No such file or directory
 lib.c:139 efi_get_variable(): ops->get_variable failed: No such file or directory
BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0000,0001,000E,000F
Boot0000* devuan	HD(1,GPT,47fa57a7-5161-4d26-8b98-90abee299b5f,0x800,0x400000)/File(\EFI\DEVUAN\GRUBX64.EFI)
Boot0001* Arch	HD(1,GPT,47fa57a7-5161-4d26-8b98-90abee299b5f,0x800,0x400000)/File(\EFI\ARCH\GRUBX64.EFI)
Boot000E* debian	HD(1,GPT,47fa57a7-5161-4d26-8b98-90abee299b5f,0x800,0x400000)/File(\EFI\DEBIAN\GRUBX64.EFI)..BO
Boot000F* UEFI: SanDisk, Partition 1	PciRoot(0x0)/Pci(0x8,0x1)/Pci(0x0,0x3)/USB(1,0)/HD(1,MBR,0x97df71f4,0x800,0x1ca3800)..BO
Could not read variable 'MirrorCurrent': No such file or directory
error trace:
 vars.c:332 vars_get_variable(): open(/sys/firmware/efi/vars/MirrorCurrent-7b9be2e0-e28a-4197-ad3e-32f062f9462c/raw_var, O_RDONLY) failed: No such file or directory
 lib.c:139 efi_get_variable(): ops->get_variable failed: No such file or directory
Could not read variable 'MirrorRequest': No such file or directory
error trace:
 vars.c:332 vars_get_variable(): open(/sys/firmware/efi/vars/MirrorRequest-7b9be2e0-e28a-4197-ad3e-32f062f9462c/raw_var, O_RDONLY) failed: No such file or directory
 lib.c:139 efi_get_variable(): ops->get_variable failed: No such file or directory

/boot/efi/efi# ls -la
insgesamt 20
drwx------ 5 root root 4096 Jun 11 16:58 .
drwx------ 5 root root 4096 Jan  1  1970 ..
drwx------ 2 root root 4096 Jun 10 17:41 Arch
drwx------ 2 root root 4096 Apr 22 17:29 debian
drwx------ 2 root root 4096 Apr 25 22:09 devuan

# mount -t efivarfs efivarfs /sys/firmware/efi/efivars
# cd /sys/firmware/efi/efivars
/sys/firmware/efi/efivars# ls -la
insgesamt 0
drwxr-xr-x 2 root root    0 Jun 19 18:00 .
drwxr-xr-x 6 root root    0 Jun 19 17:15 ..
-rw-r--r-- 1 root root   14 Jun 19 18:00 AmdAcpiVar-79941ecd-ed36-49d0-8124-e4c31ac75cd4
-rw-r--r-- 1 root root  132 Jun 19 18:00 AMD_PBS_SETUP-a339d746-f678-49b3-9fc7-54ce0f9df226
-rw-r--r-- 1 root root   12 Jun 19 18:00 AMD_RAID-fe26a894-d199-47d4-8afa-070e3d54ba86
-rw-r--r-- 1 root root 1557 Jun 19 18:00 AmdSetup-3a997502-647a-4c82-998e-52ef9486a247
-rw-r--r-- 1 root root    8 Jun 19 18:00 AmiHardwareSignatureSetupUpdateCountVar-81c76078-bfde-4368-9790-570914c01a65
-rw-r--r-- 1 root root   28 Jun 19 18:00 AMITCGPPIVAR-a8a2093b-fefa-43c1-8e62-ce526847265e
-rw-r--r-- 1 root root  437 Jun 19 18:00 AOD_SETUP-5ed15dc0-edef-4161-9151-6014c4cc630c
-rw-r--r-- 1 root root    8 Jun 19 18:00 ApSyncFlagNv-ad3f6761-f0a3-46c8-a4cb-19b70ffdb305
-rw-r--r-- 1 root root    5 Jun 19 18:00 asusbkpsmmflag-3eb0ceb0-5890-4853-9a13-0942ec712222
-rw-r--r-- 1 root root   20 Jun 19 18:00 AsusRomLayout-2e0585e9-2b5e-4f1e-bbeb-e632c5ef44b8
-rw-r--r-- 1 root root   40 Jun 19 18:00 AutoDetectData-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9
-rw-r--r-- 1 root root  134 Jun 19 18:00 BiosEventLog-4034591c-48ea-4cdc-864f-e7cb61cfd0f2
-rw-r--r-- 1 root root   80 Jun 19 18:00 BiosSettingMappingTable-b57086d5-c2e5-4654-9e3a-0b55830fbb32
-rw-r--r-- 1 root root  122 Jun 19 18:00 Boot0000-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root  114 Jun 19 18:00 Boot0001-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root  126 Jun 19 18:00 Boot000E-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root  210 Jun 19 18:00 Boot000F-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root    6 Jun 19 18:00 BootCurrent-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root    5 Jun 19 18:00 BootFromUSB-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9
-rw-r--r-- 1 root root    8 Jun 19 18:00 BootOptionSupport-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   12 Jun 19 18:00 BootOrder-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root    6 Jun 19 18:00 CMOSfailflag-c89dc9c7-5105-472c-a743-b1621e142b41
-rw-r--r-- 1 root root   38 Jun 19 18:00 ConIn-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   38 Jun 19 18:00 ConInDev-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   52 Jun 19 18:00 ConOut-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   52 Jun 19 18:00 ConOutDev-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root    5 Jun 19 18:00 CurrentPolicy-77fa9abd-0359-4d32-bd60-28f4e78f784b
-rw-r--r-- 1 root root 6326 Jun 19 18:00 db-d719b2cb-3d3a-4596-a3bc-dad00e67656f
-rw-r--r-- 1 root root 6326 Jun 19 18:00 dbDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root 3728 Jun 19 18:00 dbx-d719b2cb-3d3a-4596-a3bc-dad00e67656f
-rw-r--r-- 1 root root 3728 Jun 19 18:00 dbxDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   12 Jun 19 18:00 DefaultBootOrder-45cf35f6-0d6e-4d04-856a-0370a5b16f53
-rw-r--r-- 1 root root    5 Jun 19 18:00 DeploymentModeNv-97e8965f-c761-4f48-b6e4-9ffa9cb2a2d6
-rw-r--r-- 1 root root    5 Jun 19 18:00 DownCoreStatus-29749bad-401b-4f6d-b124-cece8c590c48
-rw-r--r-- 1 root root    5 Jun 19 18:00 EntBootMode-d047ab6d-49eb-4a1f-a0bf-ac949bbea113
-rw-r--r-- 1 root root   68 Jun 19 18:00 EnWpData-cbab171f-f356-4009-baaa-6628353a0a29
-rw-r--r-- 1 root root   52 Jun 19 18:00 ErrOut-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   52 Jun 19 18:00 ErrOutDev-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root    5 Jun 19 18:00 EXTFanCard-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9
-rw-r--r-- 1 root root    5 Jun 19 18:00 FirstBootFlag-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9
-rw-r--r-- 1 root root    8 Jun 19 18:00 FPDT_Volatile-01368881-c4ad-4b1d-b631-d57a8ec8db6b
-rw-r--r-- 1 root root   14 Jun 19 18:00 FPLayoutOrder-4db88a62-6721-47a0-9082-280b00323594
-rw-r--r-- 1 root root    5 Jun 19 18:00 FTMActiveFlag-4034591c-48ea-4cdc-864f-e7cb61cfd0f2
-rw-r--r-- 1 root root   26 Jun 19 18:00 FTMEventLog-701d2531-684f-40d1-a1d5-e1466fb38321
-rw-r--r-- 1 root root   12 Jun 19 18:00 HiiDB-1b838190-4625-4ead-abc9-cd5e6af18fe0
-rw-r--r-- 1 root root   12 Jun 19 18:00 HW_Change_Warning-0025a1bf-fdc6-420a-8fc6-6cd9e4736a3b
-rw-r--r-- 1 root root 3577 Jun 19 18:00 KEK-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root 3577 Jun 19 18:00 KEKDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root    8 Jun 19 18:00 Kernel_ATPSiStatus-77fa9abd-0359-4d32-bd60-28f4e78f784b
-rw-r--r-- 1 root root    8 Jun 19 18:00 Kernel_DriverSiStatus-77fa9abd-0359-4d32-bd60-28f4e78f784b
-rw-r--r-- 1 root root    8 Jun 19 18:00 Kernel_RvkSiStatus-77fa9abd-0359-4d32-bd60-28f4e78f784b
-rw-r--r-- 1 root root    8 Jun 19 18:00 Kernel_SiStatus-77fa9abd-0359-4d32-bd60-28f4e78f784b
-rw-r--r-- 1 root root    8 Jun 19 18:00 Kernel_SkuSiStatus-77fa9abd-0359-4d32-bd60-28f4e78f784b
-rw-r--r-- 1 root root    8 Jun 19 18:00 Kernel_WinSiStatus-77fa9abd-0359-4d32-bd60-28f4e78f784b
-rw-r--r-- 1 root root   12 Jun 19 18:00 LegacyDevicesBuffer-5fc52485-15dd-434a-8c89-c2658a41dec1
-rw-r--r-- 1 root root   12 Jun 19 18:00 LegacyGroupMappingBuffer-f2af59e7-86c4-4f6e-8fbf-4d9ae6cb7fcf
-rw-r--r-- 1 root root    6 Jun 19 18:00 MaximumTableSize-4b3082a3-80c6-4d7e-9cd0-583917265df1
-rw-r--r-- 1 root root    5 Jun 19 18:00 MemoryOverwriteRequestControl-e20939be-32d4-41be-a150-897f85d49829
-rw-r--r-- 1 root root    5 Jun 19 18:00 MemoryOverwriteRequestControlLock-bb983ccf-151d-40e1-a07b-4a17be168292
-rw-r--r-- 1 root root    8 Jun 19 18:00 MonotonicCounter-01368881-c4ad-4b1d-b631-d57a8ec8db6b
-rw-r--r-- 1 root root   76 Jun 19 18:00 MyFav-4034591c-48ea-4cdc-864f-e7cb61cfd0f2
-rw-r--r-- 1 root root    6 Jun 19 18:00 NVRAM_Verify-15a9dd61-e4f8-4a99-80db-353b13d76490
-rw-r--r-- 1 root root   12 Jun 19 18:00 OsIndications-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   12 Jun 19 18:00 OsIndicationsSupported-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root    7 Jun 19 18:00 PasswordMode-2b2a9752-feaa-4f86-a313-4d4c7117cee8
-rw-r--r-- 1 root root  890 Jun 19 18:00 PK-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root  890 Jun 19 18:00 PKDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   10 Jun 19 18:00 PlatformLang-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   60 Jun 19 18:00 PlatformLangCodes-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root    8 Jun 19 18:00 PreVgaInfo-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9
-rw-r--r-- 1 root root   12 Jun 19 18:00 RsdpAddr-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9
-rw-r--r-- 1 root root    5 Jun 19 18:00 SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root    6 Jun 19 18:00 SetupAPMFeatures-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9
-rw-r--r-- 1 root root   19 Jun 19 18:00 SetupHWMFeatures-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9
-rw-r--r-- 1 root root    5 Jun 19 18:00 SetupMode-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root  148 Jun 19 18:00 SignatureSupport-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   12 Jun 19 18:00 SmbiosEntryPointTable-4b3082a3-80c6-4d7e-9cd0-583917265df1
-rw-r--r-- 1 root root   12 Jun 19 18:00 SmbiosEntryPointTableF000-4b3082a3-80c6-4d7e-9cd0-583917265df1
-rw-r--r-- 1 root root   12 Jun 19 18:00 SmbiosScratchBuffer-4b3082a3-80c6-4d7e-9cd0-583917265df1
-rw-r--r-- 1 root root   12 Jun 19 18:00 SmbiosV3EntryPointTable-4b3082a3-80c6-4d7e-9cd0-583917265df1
-rw-r--r-- 1 root root    6 Jun 19 18:00 Timeout-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root    5 Jun 19 18:00 TotalNumberOfRootBridges-fb5703f5-f8a7-f401-18b4-3f108deb2612
-rw-r--r-- 1 root root   10 Jun 19 18:00 TPMPERBIOSFLAGS-7d3dceee-cbce-4ea7-8709-6e552f1edbde
-rw-r--r-- 1 root root   12 Jun 19 18:00 TpmServFlags-7d3dceee-cbce-4ea7-8709-6e552f1edbde
-rw-r--r-- 1 root root    5 Jun 19 18:00 VendorKeys-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root    8 Jun 19 18:00 WpBufAddr-cba83c4a-a5fc-48a8-b3a6-d33636166544
-rw-r--r-- 1 root root   68 Jun 19 18:00 WriteOnceStatus-4b3082a3-80c6-4d7e-9cd0-583917265df1

The X470 entries show the problem, and the efivars displayed are much less than the ones from the new board.

During my research I stumbled across an older article in the internet that talked about that a linux developer bricked a Samsung laptop by writing debug info into the EFI variables, all according to the official specs. My gut feeling tells me that I am in a similar situation. This is the second board where I have some trouble with regarding EFI. When you dig a bit into my posts here you may find a thread about a M5A99X Evo R2 having EFI trouble. And now the X470. Maybe something is happening in the background from the linux kernels side or somethhing else I don't know yet. I want to find out to be able to address the problem with the mainboard supplier.

@larsH: maybe your suggestion to enable CSM again is the way out for a while. Nevertheless, I wanna understand why the EFI is half way bricked. And I do not believe CSM fixes the problems forever. I think the BIOS and EFI programmers need to fix their issues. I have found an issue.

Happy reading, have a nice weekend. And thank you for your input.

rolfie

rolfie · Other Issues

larsH wrote:

If you did know everything well enough then you would not have a problem ;-)) So please don't be rude.

I am sorry, I know that I am no more than a talented amateur and a private user. But I have got my experience with Linux, with Devuan and Beowulf installations and I have sorted one of the other problem and so on. Don't want to be rude, but concentrate on the issue as I see it. Please convince me that I am wrong.

larsH wrote:

Many other people have this board running well with linux.

Refer to post #1: I have this board and a Ryzen 7 2700X working with ASCII for about 2 years now, backports kernel. HOAS did not believe me that this is possible, I have proven him wrong. Sorry for that.

larsH wrote:

Again: How is your partioning. How is your fstab.

# blkid
/dev/nvme0n1: PTUUID="6dfae043-b76f-47ba-8c8c-dade8f545e70" PTTYPE="gpt"
/dev/nvme0n1p1: UUID="26AA-7EAE" TYPE="vfat" PARTUUID="e5604745-edac-4815-bc08-bbf2747deed4"
/dev/nvme0n1p2: LABEL="boot" UUID="6b1a5449-77ac-487b-b9e6-737ec8b8c677" TYPE="ext4" PARTLABEL="nvme_boot" PARTUUID="3a9d4e90-bbb7-4cbd-a54d-df62d98925f6"
/dev/nvme0n1p3: UUID="d1231306-6a42-4e5c-b609-60909d8e210b" TYPE="crypto_LUKS" PARTUUID="03f2a4dc-073f-485f-bce4-7368356daff4"
/dev/nvme0n1p4: LABEL="BeoBoot" UUID="4980605c-6b41-4d4b-81ec-f66c0eb45a8e" TYPE="ext4" PARTLABEL="DevBoot" PARTUUID="5be64e0b-1275-480b-aea9-74483d979008"
/dev/nvme0n1p5: UUID="0f8ed665-79ed-4a19-83ba-6671827567c6" TYPE="crypto_LUKS" PARTLABEL="DevRoot" PARTUUID="c2fa81d3-7e4e-40b1-bee2-bbdeca365611"
/dev/sda1: LABEL="1905E1E68X8" UUID="AEB3-D480" TYPE="vfat" PARTLABEL="ssdefi" PARTUUID="2a66036e-a832-4654-b12f-773f42bc027a"
/dev/sda2: LABEL="Win7Ult" UUID="6CD3FFAC25F17123" TYPE="ntfs" PTTYPE="dos" PARTLABEL="W7Ultimate" PARTUUID="8f878125-d8e2-4e24-ba40-6b884f77f78b"
/dev/sda3: LABEL="SSDData" UUID="5B83C3811BAE211B" TYPE="ntfs" PTTYPE="dos" PARTLABEL="W7Data" PARTUUID="cbfd11d2-df24-4f51-a8c6-952704d130bc"

# <file system> <mount point>   <type>  <options>       <dump>  <pass>
/dev/mapper/vgsys-1_root /               ext4    discard,relatime,errors=remount-ro 0       1

# /boot was on /dev/nvme0n1p2 during installation
UUID=6b1a5449-77ac-487b-b9e6-737ec8b8c677 /boot           ext4    defaults        0       2

# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=26AA-7EAE  /boot/efi       vfat    umask=0077      0       1

/dev/mapper/vgsys-2_swap none            swap    sw              0       0

/dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0       0

I removed a bit of info for the other devices. The NVME is GPT partitioned, p1 is the efi partition, p2 the ASCII boot, p3 an encrypted LVM for root and swap. p4 was added a few days ago as boot for Beowulf, p5 is an encrypted LVM for root and swap for Beowulf. sda holds a Windows7 installation that is detected and listed in the grub menu.

larsH wrote:

Try with bios fail-safe settings.

What is this?

larsH wrote:

Beowulf does mostly install well on secreboot only machines. This is one af the main features of Debian Buster.

I don't care about secure boot, its disabled and all keys are deleted in the bios. I am using pure efi without secure boot.

larsH wrote:

If you are doing all sorts of tricks, chances are you are screwing things up. And if you want help please provide the necessary information. We do all make simple mistakes from time to time.

I am pretty sure that I haven't made a generic error on the Beowulf install. The efi problem did exist before the install. My mistake and an important learning was that ASCII and Beowulf will install the efi bootloader in the same directory /boot/efi/EFI/debian. I solved this now by booting the Beowulf and ASCII install media in resue mode and doing a grub-install --bootloader-id=beowulf re --bootloader-id=ascii.
Current entries left on the efi partition are:

# cd /boot/efi/efi
root@....:/boot/efi/efi# ls -la
insgesamt 2
drwx------ 4 root root 512 Jun 18 21:23 .
drwx------ 4 root root 512 Jan  1  1970 ..
drwx------ 2 root root 512 Jun 18 09:45 ascii
drwx------ 2 root root 512 Jun 15 08:15 beowulf

Is there something I have overlooked? I am posting from ASCII now, Beowulf is no more present in the boot override menu. If I want to boot it again I need to reboot from the Beowulf install USB stick, use rescue mode, install grub again into the beowulf directory, then I can use Beowulf and have lost the ascii entry as side effect.

On the weekend I may try HOAS hint to create the /EFI/BOOT/ entry as a copy of the beowulf efi entry. Lets see if that allows me to select either ascii or beowulf.

The efi variables problem remains:

# mount -t efivarfs efivarfs /sys/firmware/efi/efivars
root@.....:/# efibootmgr -v
No BootOrder is set; firmware will attempt recovery
# cd /sys/firmware/efi/efivars
root@.....:/sys/firmware/efi/efivars# ls -la
insgesamt 0
drwxr-xr-x 2 root root    0 Jun 18 23:09 .
drwxr-xr-x 6 root root    0 Jun 18 23:09 ..
-rw-r--r-- 1 root root   38 Jun 18 23:09 ConIn-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root   40 Jun 18 23:09 ConOut-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root    5 Jun 18 23:09 CurrentPolicy-77fa9abd-0359-4d32-bd60-28f4e78f784b
-rw-r--r-- 1 root root    5 Jun 18 23:09 DeploymentModeNv-97e8965f-c761-4f48-b6e4-9ffa9cb2a2d6
-rw-r--r-- 1 root root    8 Jun 18 23:09 Kernel_ATPSiStatus-77fa9abd-0359-4d32-bd60-28f4e78f784b
-rw-r--r-- 1 root root    8 Jun 18 23:09 Kernel_EntRevokeSiStatus-77fa9abd-0359-4d32-bd60-28f4e78f784b
-rw-r--r-- 1 root root    8 Jun 18 23:09 Kernel_RvkSiStatus-77fa9abd-0359-4d32-bd60-28f4e78f784b
-rw-r--r-- 1 root root    8 Jun 18 23:09 Kernel_SiStatus-77fa9abd-0359-4d32-bd60-28f4e78f784b
-rw-r--r-- 1 root root    8 Jun 18 23:09 Kernel_SkuSiStatus-77fa9abd-0359-4d32-bd60-28f4e78f784b
-rw-r--r-- 1 root root    8 Jun 18 23:09 Kernel_WinSiStatus-77fa9abd-0359-4d32-bd60-28f4e78f784b
-rw-r--r-- 1 root root   11 Jun 18 23:09 SecureBootSetup-7b59104a-c00d-4158-87ff-f04d6396a915
-rw-r--r-- 1 root root 5804 Jun 18 23:09 StdDefaults-4599d26f-1a11-49b8-b91f-858745cff824

Useful hints are welcome. I am considering to replace the mainboard. But: the X470 is swept from the market, at least in Germany, and an replacement could be a X570 board, but that does no more have Win7 drivers that I still require for one or the other task (I will never upgrade on Win10, do not suggest something like that).

rolfie

rolfie · Other Issues

The efi trouble is not due to Beowulf and the install. Somehow the efi memory of the mainboard is bugged, and I see now way to clean out and reset the stuff. The usual tricks to save a not booting system do not help.

BTW: pure EFI install, CSM off, Secure boot off, all keys deleted, all disks GPT. I have read enough to get this right.

I am posting from my original ASCII now, the Beowulf entry still is present on /boot/efi/.., but no more shown in the Bios. Only ASCII and Win7 present (that is crashed also after disabling CSM despite being an UEFI installation, for the moment that isn't important).

Again, is there anybody around who knows the real dirty tricks?

rolfie

The officially official Devuan Forum!

#951 Hardware & System Configuration » [Solved] Password required for startup script » 2020-06-26 20:29:52

#952 Other Issues » [Solved] Copy putty sessions does not work » 2020-06-26 20:07:30

#953 Re: Installation » SOLVED: Beowulf: quite good, but ...... » 2020-06-25 17:00:25

#954 Re: Other Issues » [Solved] linux-5.6.0-0.bpo.2 stucks at "waiting for /dev.... udevd" » 2020-06-25 15:38:16

#955 Re: Installation » devuan_beowulf_3.0.0_amd64-netinstall hangs » 2020-06-24 16:11:16

#956 Re: Installation » devuan_beowulf_3.0.0_amd64-netinstall hangs » 2020-06-24 11:52:28

#957 Re: Installation » devuan_beowulf_3.0.0_amd64-netinstall hangs » 2020-06-24 11:19:13

#958 Re: Installation » SOLVED: Beowulf: quite good, but ...... » 2020-06-23 14:13:17

#959 Re: Installation » SOLVED: Beowulf: quite good, but ...... » 2020-06-23 11:23:50

#960 Re: Desktop and Multimedia » Sound with Beowulf - always trouble? » 2020-06-22 20:05:25

#961 Re: Desktop and Multimedia » Sound with Beowulf - always trouble? » 2020-06-22 20:01:21

#962 Re: Desktop and Multimedia » Sound with Beowulf - always trouble? » 2020-06-22 19:55:22

#963 Re: Desktop and Multimedia » Sound with Beowulf - always trouble? » 2020-06-22 19:41:27

#964 Re: Installation » SOLVED: Beowulf: quite good, but ...... » 2020-06-22 19:29:31

#965 Re: Desktop and Multimedia » Sound with Beowulf - always trouble? » 2020-06-21 21:05:39

#966 Re: Desktop and Multimedia » Sound with Beowulf - always trouble? » 2020-06-21 20:07:53

#967 Desktop and Multimedia » Sound with Beowulf - always trouble? » 2020-06-21 19:18:28

#968 Re: Other Issues » EFI trouble » 2020-06-21 13:46:49

#969 Re: Other Issues » EFI trouble » 2020-06-20 21:50:52

#970 Re: Other Issues » EFI trouble » 2020-06-20 21:35:39

#971 Re: Other Issues » EFI trouble » 2020-06-20 21:17:58

#972 Re: Other Issues » EFI trouble » 2020-06-20 21:02:53

#973 Re: Other Issues » EFI trouble » 2020-06-20 20:36:17

#974 Re: Other Issues » EFI trouble » 2020-06-18 21:18:25

#975 Re: Other Issues » EFI trouble » 2020-06-18 19:59:28

Board footer