I tried that line:

RTLDLIST="/lib/ld-linux.so.2 /lib64/ld-linux-x86-64.so.2 /libx32/ld-linux-x32.so.2"

and with the 32 bit change:

RTLDLIST="/lib32/ld-linux.so.2 /lib64/ld-linux-x86-64.so.2 /libx32/ld-linux-x32.so.2"

No change.

Those / that file will still not run,

<>

root@ve1drg:/BPQbbs/ve3bwm# ldd linbpq
    not a dynamic executable

??? what does that mean?  Other than,  is this why the program is not executable..

OK.  Here is the file I would like to execute.  Or run.  Or whatever..

It is the file called linbpq found in the g8bpq directory. I can't post it here because I dont know how to attach it to this message.  Must be a way. But cant figure it out.

It is an executable file and is normally run using ./linbpq.

Of course when that file runs it brings up a G8BPQ BBS.

I even tried using 'source linbpq'  and that gave me the same error.
The file will not run.

But a few days ago it ran just fine. I had that program on another distribution (Jessie) and it worked there.
Maybe Ascii is just too tough for this little file, eh?

asc11 64.  And its any file I make up and make bootable. It wont work.
I get this error.

What a life, eh?  Must be a fix out there somewhere.

Thanks for that direction on kernel location and backports.
Uname -r now shows me  5.5.0-0.bpo.2-amd64.
And it works like a champ. Better than the 4.9.0-11-amd64 version I was running.

Thanks..

Well - I finally got Beowulf up and workiing on my new/fast machine. But not in the normal way.

What I did was I used apt-get dist-upgrade,  and I ended up with Beowulf,  from ASCII.

At boot time now I have the choice of booting with 4.19.0.09. Which is my first choice.  That one doesnt boot which has the same problem that I have had all along.

The second choice 4.19.0.11  works like a champ. I nearly fell down when it came up just fine.

So now I would like to know how I get edit out that first choice - 4.19.0.09.  So when things boot up automaticaly it will pick a kernel that works.

So how can I edit out that first line on the boot-screen,

Well I am back after a couple days.  Its been terrible here where I have tried to get this Beowulf working.  Or installed I guess.

I am about to give up.  But before that happens,  here is what I know so far.

Beuwulf LIVE comes up most of the time,  all ok using the LIVE CD.  It  seems to have something to do with UEFI/Legacy BIOS, .
The CD boots up all ok most of the time.  I have made a page of notes on what is happening and now that is confusing to me.

Somehow, if the bios is not set right (uefi or legacy) than I get nothing.  But if i pick to boot the disk using the 'sure-thing' line,  than it seems to get Beowulf up.
And UEFI and Legacy are important too.  Something one works while the other doesn't.

I normally boot JESSIE and ASCII using Legacy.  That works great.  But not this BEOWULF release.   Wow.  What a challenge. And I am sure that the problem really is with the (UEFI/Legacy BIOS)..settings.

Why would this release be so sensitve to what you are booting with?  But I do see when you install it,  that Grub has to sit on a small boot partition that must be formated as DOS.  Not EXT4 or something else.  This is getting more strange than ever before.

Well - I will try to install this rascal once again, but this time from the cdrom rather than the live disk.  This way it will look after the correct setting for grub. I think.
But than,  what do I know.

My last question... why is this release so different or complicated,  over something like ASCII??

I am trying to install BeoWulf 3.0.0 64bit. And tonight I noticed when I tried to bring it up  with it going through all that data stuff before it fails to a black nothing screen -  I see it says ......specified kvm group....   and that is it.  Everything goes black after that.

I havent tried the live Beowulf  version.  Yet.  But maybe that is something I can try.  Its worth it..

The other versions of Devuan are installed on another machine.  So there is no conflict.

Also I tried installing Lilo iinstead of grub and it failed with a kernel panic - not syncing...unable to mount. root fs unknown..

Always something.  Well. Let me run and try the live version now,  before I go crazy.  I just dont know what could be stopping Beowulf from booting up.
Strange indeed.

Here is what Jessie shows with the following commands..

root@localhost:/etc/init.d# lspci -knn | grep -A3 Network

03:00.0 Network controller [0280]: Qualcomm Atheros Device [168c:003e] (rev 32)
        Subsystem: Bigfoot Networks, Inc. Device [1a56:1535]
04:00.0 Ethernet controller [0200]: Qualcomm Atheros Device [1969:e0a1] (rev 10)
        Subsystem: Dell Device [1028:0859]
70:00.0 Non-Volatile memory controller [0108]: Device [1c5c:1639]

root@localhost:/files# lspci

00:00.0 Host bridge: Intel Corporation Device 3e30 (rev 0d)
00:01.0 PCI bridge: Intel Corporation Device 1901 (rev 0d)
00:02.0 Display controller: Intel Corporation Device 3e98 (rev 02)
00:08.0 System peripheral: Intel Corporation Device 1911
00:14.0 USB controller: Intel Corporation Device a2af
00:16.0 Communication controller: Intel Corporation Device a2ba
00:17.0 RAID bus controller: Intel Corporation 82801 SATA Controller [RAID mode]
00:1c.0 PCI bridge: Intel Corporation Device a291 (rev f0)
00:1c.2 PCI bridge: Intel Corporation Device a292 (rev f0)
00:1c.3 PCI bridge: Intel Corporation Device a293 (rev f0)
00:1c.4 PCI bridge: Intel Corporation Device a294 (rev f0)
00:1d.0 PCI bridge: Intel Corporation Device a298 (rev f0)
00:1e.0 Signal processing controller: Intel Corporation Device a2a7
00:1f.0 ISA bridge: Intel Corporation Device a2c9
00:1f.2 Memory controller: Intel Corporation Device a2a1
00:1f.3 Audio device: Intel Corporation Device a2f0
00:1f.4 SMBus: Intel Corporation Device a2a3
01:00.0 VGA compatible controller: NVIDIA Corporation Device 2182 (rev a1)
01:00.1 Audio device: NVIDIA Corporation Device 1aeb (rev a1)
01:00.2 USB controller: NVIDIA Corporation Device 1aec (rev a1)
01:00.3 Serial bus controller [0c80]: NVIDIA Corporation Device 1aed (rev a1)
02:00.0 USB controller: ASMedia Technology Inc. Device 1242
03:00.0 Network controller: Qualcomm Atheros Device 003e (rev 32)
04:00.0 Ethernet controller: Qualcomm Atheros Device e0a1 (rev 10)
70:00.0 Non-Volatile memory controller: Device 1c5c:1639

I reinstalled the Atheros files.  And iwlwifi as well.  Still no luck..

Yes I am aware that its end of life is soon.

But for the sake of amateur radio software,  Jessie has to be used. Rather than something like beautiful Ascii. 
I sure wish ascii would work. That is what I have running on my main computer.  Its really nice. But Jessie is needed for the node software and ax125 utils..

Its too bad..

But need to get this thing running on my new machine.  Or give up my amateur radio hobby.