Beowulf Beta is here!

fsmithred · 2020-03-25 18:14:55

Thanks. It does help to know what won't fix it.

Dutch_Master · 2020-03-25 18:19:40

Just for my understanding: if one already has Ascii installed, Beowulf is now ready/stable enough to be upgraded to?

Tia!

golinux · 2020-03-25 18:22:59

Dutch_Master wrote:

Just for my understanding: if one already has Ascii installed, Beowulf is now ready/stable enough to be upgraded to?

Yes. https://beta.devuan.org/os/install#upgr … to-beowulf

dev-1-dash-1 · 2020-03-25 18:24:52

It would be helpful if we had a few more datapoints here.
It's always possible that I've screwed something up on my own.

I DID check the sha256 sum and it matches.

aus9 · 2020-03-26 04:13:38

fsmithred wrote:

snip

apt purge pulseaudio avahi-daemon
apt autoremove

is easy.

Hi

Won't that break wireless printing setup that uses avahi?

I have installed to hard drive
devuan_beowulf_3.0.0_beta_amd64_desktop-live.iso

aus9 · 2020-03-26 04:17:43

and I won't do a bug report because its easy to fix,
but I flashed an usb stick with my above iso

booting up to live, my usb mouse froze.
pulling and re-inserting it fixed it instantly.

I have no such glitches on the hard drive install.

Thanks for reading.

fsmithred · 2020-03-26 09:10:19

aus9 wrote:

fsmithred wrote:
snip
apt purge pulseaudio avahi-daemon
apt autoremove
is easy.
Hi
Won't that break wireless printing setup that uses avahi?

Maybe. If you're using avahi, you shouldn't remove it. Same goes for pulseaudio.

stanz · 2020-03-26 19:07:51

Wow...that sounds familiar!!
Something new - on a usb burn tho. My usb wasn't affected, just cd burns.

aus9 wrote:

and I won't do a bug report because its easy to fix,
but I flashed an usb stick with my above iso
booting up to live, my usb mouse froze.
pulling and re-inserting it fixed it instantly.
I have no such glitches on the hard drive install.
Thanks for reading.

Yep, just running live - not carrying into install.
I don't get it, but now I don't feel alone!

aus9 · 2020-03-27 01:17:17

Yep, just running live - not carrying into install.
I don't get it

Yes I am in the process of installing on a HP intel onboard graphics and have no such usb mouse freeze.

so I booted my tower back up...mouse still freezes and the only log that shows some strangeness is below
original name /var/log/boot

(Nothing has been logged yet. If you're still seeing this message your current init system might not write bootup messages to the system console at all.)
Fri Mar 27 00:35:23 2020: [....] Activating swap...??7[ ok 8??done.
Fri Mar 27 00:35:23 2020: [....] Creating compatibility symlink from /etc/mtab to /proc/mounts. ...??7[warn8?? (warning).
Fri Mar 27 00:35:23 2020: [....] Cleaning up temporary files... /tmp??7[ ok 8??.
Fri Mar 27 00:35:23 2020: [....] Starting early crypto disks...??7[ ok 8??done.
Fri Mar 27 00:35:23 2020: [info] Loading kernel module lp.
Fri Mar 27 00:35:23 2020: [info] Loading kernel module ppdev.
Fri Mar 27 00:35:23 2020: [info] Loading kernel module parport_pc.
Fri Mar 27 00:35:23 2020: [....] Setting up LVM Volume Groups... WARNING: Device /dev/loop0 not initialized in udev database even after waiting 10000000 microseconds.
Fri Mar 27 00:35:43 2020: WARNING: Device /dev/sda not initialized in udev database even after waiting 10000000 microseconds.
Fri Mar 27 00:35:54 2020: WARNING: Device /dev/sda1 not initialized in udev database even after waiting 10000000 microseconds.
Fri Mar 27 00:36:04 2020: WARNING: Device /dev/sda2 not initialized in udev database even after waiting 10000000 microseconds.
Fri Mar 27 00:36:14 2020: WARNING: Device /dev/sda3 not initialized in udev database even after waiting 10000000 microseconds.
Fri Mar 27 00:36:24 2020: WARNING: Device /dev/sdb not initialized in udev database even after waiting 10000000 microseconds.
Fri Mar 27 00:36:34 2020: WARNING: Device /dev/sdb1 not initialized in udev database even after waiting 10000000 microseconds.
Fri Mar 27 00:36:44 2020: WARNING: Device /dev/sdb2 not initialized in udev database even after waiting 10000000 microseconds.
Fri Mar 27 00:36:54 2020: WARNING: Device /dev/sdc not initialized in udev database even after waiting 10000000 microseconds.
Fri Mar 27 00:37:04 2020: WARNING: Device /dev/sdc1 not initialized in udev database even after waiting 10000000 microseconds.
Fri Mar 27 00:37:14 2020: WARNING: Device /dev/loop0 not initialized in udev database even after waiting 10000000 microseconds.
Fri Mar 27 00:37:24 2020: WARNING: Device /dev/sda1 not initialized in udev database even after waiting 10000000 microseconds.
Fri Mar 27 00:37:34 2020: WARNING: Device /dev/sda2 not initialized in udev database even after waiting 10000000 microseconds.
Fri Mar 27 00:37:44 2020: WARNING: Device /dev/sda3 not initialized in udev database even after waiting 10000000 microseconds.
Fri Mar 27 00:37:54 2020: WARNING: Device /dev/sdb1 not initialized in udev database even after waiting 10000000 microseconds.
Fri Mar 27 00:38:04 2020: WARNING: Device /dev/sdb2 not initialized in udev database even after waiting 10000000 microseconds.
Fri Mar 27 00:38:14 2020: WARNING: Device /dev/sdc1 not initialized in udev database even after waiting 10000000 microseconds.
Fri Mar 27 00:38:14 2020: ??7[ ok 8??done.
Fri Mar 27 00:38:14 2020: [....] Starting remaining crypto disks...??7[ ok 8??done.
Fri Mar 27 00:38:14 2020: [....] Checking file systems...fsck from util-linux 2.33.1
Fri Mar 27 00:38:14 2020: ??7[ ok 8??done.
Fri Mar 27 00:38:14 2020: [....] Mounting local filesystems...??7[ ok 8??done.
Fri Mar 27 00:38:14 2020: [....] Activating swapfile swap...??7[ ok 8??done.
Fri Mar 27 00:38:15 2020: [....] Cleaning up temporary files...??7[ ok 8??.
Fri Mar 27 00:38:15 2020: [....] Starting: AppArmor[....] $Mounting securityfs on /sys/kernel/security??7[ ok 8??.
Fri Mar 27 00:38:15 2020: [....] Loading AppArmor profiles...??7[ ok 8??done.
Fri Mar 27 00:38:18 2020: ??7[ ok 8??.
Fri Mar 27 00:38:18 2020: [....] Starting Setting kernel variables: sysctl??7[ ok 8??.
Fri Mar 27 00:38:18 2020: [....] Configuring network interfaces...??7[ ok 8??done.
Fri Mar 27 00:38:18 2020: [....] Starting RPC port mapper daemon: rpcbind??7[ ok 8??.
Fri Mar 27 00:38:18 2020: [....] Starting NFS common utilities: statd idmapd??7[ ok 8??.
Fri Mar 27 00:38:18 2020: [....] Cleaning up temporary files...??7[ ok 8??.
Fri Mar 27 00:38:18 2020: [....] Setting up ALSA...??7[ ok 8??done (none loaded).
Fri Mar 27 00:38:18 2020: [....] Setting sensors limits...No sensors found!
Fri Mar 27 00:38:18 2020: Make sure you loaded all the kernel drivers you need.
Fri Mar 27 00:38:18 2020: Try sensors-detect to find out which these are.
Fri Mar 27 00:38:18 2020: No sensors found!
Fri Mar 27 00:38:18 2020: Make sure you loaded all the kernel drivers you need.
Fri Mar 27 00:38:18 2020: Try sensors-detect to find out which these are.
Fri Mar 27 00:38:18 2020: ??7[ ok 8??done.
Fri Mar 27 00:38:18 2020: [....] Setting up X socket directories... /tmp/.X11-unix /tmp/.ICE-unix??7[ ok 8??.
Fri Mar 27 00:38:18 2020: INIT: Entering runlevel: 2
Fri Mar 27 00:38:18 2020: [info] Using makefile-style concurrent boot in runlevel 2.
Fri Mar 27 00:38:18 2020: [....] Setting up console font and keymap...??7[ ok 8??done.
Fri Mar 27 00:38:18 2020: [....] Starting LVM2 poll daemon: lvmpolld??7[ ok 8??.
Fri Mar 27 00:38:18 2020: [....] Starting enhanced syslogd: rsyslogd??7[ ok 8??.
Fri Mar 27 00:38:19 2020: [....] Starting ACPI services: acpid??7[ ok 8??.
Fri Mar 27 00:38:19 2020: [....] Starting anac(h)ronistic cron: anacron??7[ ok 8??.
Fri Mar 27 00:38:19 2020: [....] Starting periodic command scheduler: cron??7[ ok 8??.
Fri Mar 27 00:38:19 2020: [....] Starting system message bus: dbus??7[ ok 8??.
Fri Mar 27 00:38:19 2020: [....] Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon??7[ ok 8??.
Fri Mar 27 00:38:19 2020: [....] Starting bluetooth: bluetoothd??7[ ok 8??.
Fri Mar 27 00:38:19 2020: [....] Starting Common Unix Printing System: cupsd??7[ ok 8??.
Fri Mar 27 00:38:19 2020: [....] Starting CUPS Bonjour daemon: cups-browsed??7[ ok 8??.
Fri Mar 27 00:38:19 2020: [....] Starting session management daemon: elogind??7[ ok 8??.
Fri Mar 27 00:38:19 2020: [....] Starting MTA: exim4??7[ ok 8??.
Fri Mar 27 00:38:20 2020: [....] Starting MD monitoring service: mdadm --monitor??7[ ok 8??.
Fri Mar 27 00:38:20 2020: [....] Starting NTP server: ntpd??7[ ok 8??.
Fri Mar 27 00:38:20 2020: [....] Starting SANE network scanner server: saned??7[ ok 8??.
Fri Mar 27 00:38:20 2020: [....] Starting slim: slim??7[ ok 8??.

dmesg does not show any funniness for usb mouse...I have full log if anyone needs to see it

[ 1.791807] usbcore: registered new interface driver usbhid
[ 1.791922] usbhid: USB HID core driver
[ 1.793671] input: Logitech USB Optical Mouse as /devices/pci0000:00/0000:00:01.2/0000:12:00.0/usb1/1-3/1-3:1.0/0003:046D:C05A.0001/input/input3
[ 1.793940] hid-generic 0003:046D:C05A.0001: input,hidraw0: USB HID v1.11 Mouse [Logitech USB Optical Mouse] on usb-0000:12:00.0-3/input0

I am guessing the motherboard AMD and that kernel did not want to party as...my SSD boot file contains similar udev messages,
the difference of course is I see a fairly fast boot up compared to usb boot up which seems to take ages in comparison

fsmithred · 2020-03-27 01:34:31

Fri Mar 27 00:35:43 2020: WARNING: Device /dev/sda not initialized in udev database even after waiting 10000000 microseconds.
Fri Mar 27 00:35:54 2020: WARNING: Device /dev/sda1 not initialized in udev database even after waiting 10000000 microseconds.
Fri Mar 27 00:36:04 2020: WARNING: Device /dev/sda2 not initialized in udev database even after waiting 10000000 microseconds.

I've been informed that when you get these repeating messages, you can make them stop by switching to tty2 and then back to tty1.

Press
alt-F2 and then alt-F1

aus9 · 2020-03-27 05:56:17

@fsmithred

Yikes sorry for wasting time. I was using the iso dated Mar 11
downloading your newer one now.

post 56 does not show my atime date. So I mislead you.

EDIT

similar results for the iso dated 2020-03-25

I am not going to pursue this any further. My SSD boots up with decent speed.

cheers

Last edited by aus9 (2020-03-27 12:19:33)

dev-1-dash-1 · 2020-03-27 15:14:21

fsmithred wrote:

Fri Mar 27 00:35:43 2020: WARNING: Device /dev/sda not initialized in udev database even after waiting 10000000 microseconds.
Fri Mar 27 00:35:54 2020: WARNING: Device /dev/sda1 not initialized in udev database even after waiting 10000000 microseconds.
Fri Mar 27 00:36:04 2020: WARNING: Device /dev/sda2 not initialized in udev database even after waiting 10000000 microseconds.
I've been informed that when you get these repeating messages, you can make them stop by switching to tty2 and then back to tty1.
Press
alt-F2 and then alt-F1

I've just tried this fix and it didn't work when I booted from real dvd. Caps lock works, but not alt-f1/f2. The console font didnt change.
After that I rebooted from the same image located on hdd, and it worked. The console font changed.
It SEEMS that the probability of encountering this error is much higher when booting from real physical dvd.

I am using the image that fsmithred posted in this thread named
devuan_beowulf_3.0.0_beta_2020-03-25_amd64_desktop-live.iso

dev-1-dash-1 · 2020-03-27 15:17:06

Some more feedback:
I've installed another test system from the live cd using debootstrap, and when I boot this message appears:
udev: group "kvm" not registered (or not found)
The system boots fine though.
After about 10 reboots I got the "... not registered after 100000 microsecs" message when booting that system from hard drive. It only happened once.

EDIT: It is of course possible that I've screwed the already installed to hd system by myself, I've been doing horrible things with it since it's a test drive.
About 5 reboots right after the install were ok, although it's a more complex setup with lvm, crypt, and zfs.
The system seems to be working fine overall, though there were some oddities.

Last edited by dev-1-dash-1 (2020-03-27 15:33:47)

fsmithred · 2020-03-27 15:37:20

I burned the 3/25 iso to dvd, booted and got the udev warning. Pressing alt-F2 does nothing. Really nothing. I can't change to another tty. Pressinc ctrl-c seems to stop the warnings.

On another machine, I booted from a usb that has a regular install from a netinstall iso on it. When I got to the desktop, the keyboard was not working. Unplug/replug the keyboard fixed it.

Update: boot dvd on laptop, keyboard doesn't work, trackpad and trackpoint don't work. Can't unplug them.

danista · 2020-03-27 19:09:35

I installed 3.0.0_beta_i386_desktop.iso After removing the pulse, the shortcut remained in the menu (/usr/share/applications/pavucontrol.desktop)

refractasnapshot does not want to be installed. Depends: syslinux (<3: 6.03)

danista · 2020-03-27 19:30:30

It also installs 4.19.0-8-686 instead of 4.19.0-8-686-pae kernel, without headers from 4.19.0-8-686

fsmithred · 2020-03-27 19:57:05

If there was more to the refractasnapshot message, I'd like to see it. The syslinux dependency is as follows:

syslinux (< 3:6.03)  |  syslinux (>= 3:6.03), syslinux (< 3:6.03) | isolinux (>= 3:6.03)

It's been like that for a few years. (Translation: syslinux older than 6.03, which included isolinux, or both syslinux and isolinux at least version 6.03)

The non-pae kernel is default for those with old machines. The linux-headers package is in the iso, but it does not get installed by default. That's standard for debian and consequently for devuan.

You probably need to remove or purge the pavucontrol package to get rid of the .desktop file.

danista · 2020-03-27 21:27:31

fsmithred wrote:

The linux-headers package is in the iso, but it does not get installed by default.

# aptitude search headers
i A linux-headers-4.19.0-8-686-pae                                   - Header files for Linux 4.19.0-8-686-pae                                    
i A linux-headers-4.19.0-8-common                                    - Common header files for Linux 4.19.0-8                                     
i A linux-headers-686-pae                                            - Header files for Linux 686-pae configuration (meta-package)                
v   linux-kernel-headers

danista · 2020-03-27 21:38:00

fsmithred wrote:

If there was more to the refractasnapshot message, I'd like to see it.

The following packages have unmet dependencies:
 refractasnapshot-base : Depends: syslinux (< 3:6.03) but 3:6.04~git20190206.bf6db5b4+dfsg1-1 is to be installed or
                                  isolinux (>= 3:6.03) which is a virtual package and is not provided by any available package

The following actions will resolve these dependencies:

     Keep the following packages at their current version:
1)     refractasnapshot-base [Not Installed]

Marjorie · 2020-03-27 22:04:57

Just to report how I've (finally) managed to upgrade to Beowulf (Cinnamon edition).

System

My system: AMD Phenom II X4 910e, NVidia GeForce GT 710B. 8 GB RAM. 24" Dell U2415 (1920 x 1200 x 60 Hz).
ASCII installed (4.09-12 kernel) on 2 x 500GB SSD as RAID1 with root (/dev/md0), home (/dev/md1) and swap (/dev/md2) partitions. Collection of other SSD and spinning rust drives. I've using the NVidia default drivers.

I first mounted the Beowulf 3.0.0 ISO on one of my other hard drives and added it to grub (via 40_custom in /etc/grub.d).

Live ISO

Booted this up without difficulty. Network connect fine.

Then, having backed up the root (dev/md0) partition (using fsarchiver), I attempted to do do an upgrade in place.

Upgrade in place

I followed the beta.devian "Upgrade to Beowulf' guide.

This mostly seemed to work, however at the end of the process I ended up with a completely locked screen: a full hi-res graphic login screen, but mouse and keyboard frozen, so I couldn't even get a console. I chrooted into the system and managed to unlock root, however despite playing around in the console ('m much happier working with multiple xterms and graphical tools such as synnaptic and GParted to hand). I couldn't work out a solution. I'm a sudo user so I wouldn't normally have a root password.Also I think having the Nvidia drivers may have contributed since the following the instructions only main and not contrib and non-free are enabled in the repository and the nvidia pacvckages are in non-free.

Expert Install of root and link to /home

Had a number of goes at this, but eventually decided to use the devuan_beowulf_3.0.0_beta_amd64_desktop.iso and do an 'expert install' of the root partition: the expert option is required so as to get the cinnamon desktop and in my case control over where to install the new root file system.

Having done this before (when I installed ASCII on RAID) it wasn't particularly difficult. The main problem I had was knowing what sequence of choices I need to do in the partitioning step as I didn't want to destroy the other partitions on the various disks on my system. I also decided to not make the partition bootable, which came back to bite me later. I choose a user name and password and set myself up to sudo rather than enable a root password.

Anyway I completed the install. The desktop came up fine (nouveau vido driver) and network connection worked. I then backed this up and restored it to my original root partition (/dev/md0). I modified fstab to mount my asciil home partition (/dev/md1) at /home and removed the (short list of) existing files in /home.

Rebooted to get most of my ascii desktop. and used synaptic to install Evolution (my preferred mail client/Calendar/Contacts), this then reloaded my mail archive and account settings.I did have to install an /etc/aliases for access my mail spool (for root messages).

Rythmbox automatically found my Music.I did have to enable autospawn (etc/pulse/client.conf.d/00-disable-autospawn.conf) to get pulseaudio working.

Firefox kept nearly all of my settings, although it did disable DoH - naughty - should be my choice.

Network Manager (the default in Cinnamon) also worked, 'out of the box'.

I then had to install the grub packages and fix grub.

Having done another backup, and having enabled contrib and nonfree I ran sudo apt-get install nvidia-driver to make full us of my graphics card. Although it complained (as it had when I tried to do it via an upgrade), failing with Nvidia persistentd, it did work and I now have accelerated video again.

Final thoughts

For the moment I would suggest not upgrading in place if you are running the proprietary NVidia drivers or if you use sudo.

Installing a new Beowulf system in the root partition and then linking it with your /home partition seems more robust (but do back them up first). I suspect I could have linked them directly in the installer but out of an abundance of caution I didn't.

Last edited by Marjorie (2020-03-27 22:09:07)

fsmithred · 2020-03-27 22:05:52

That's really weird. I've installed refractasnapshot in beowulf a few times. And isolinux is a real package.

$ apt-cache policy isolinux
isolinux:
  Installed: 3:6.04~git20190206.bf6db5b4+dfsg1-1
  Candidate: 3:6.04~git20190206.bf6db5b4+dfsg1-1
  Version table:
 *** 3:6.04~git20190206.bf6db5b4+dfsg1-1 500
        500 http://deb.devuan.org/merged beowulf/main amd64 Packages
        100 /var/lib/dpkg/status

Make sure you have all three lines in /etc/apt/sources.list and run 'apt update'

deb http://deb.devuan.org/merged beowulf main
deb http://deb.devuan.org/merged beowulf-updates main
deb http://deb.devuan.org/merged beowulf-security main

If that isn't the problem, try installing syslinux and isolinux first, then install refractasnapshot.

aus9 · 2020-03-28 01:37:39

Hi guys

Altho I am still happy with my internal boot speed. Seeing others have some similar issues to me I thought I might search for the udev error.

I got a hit or 2 from a systemd based distro but they are discussing lvm2, and I do not use lvm.
Before I editted my last reply....I thought it might because of my AMD motherboard which asks users to have specific usb lead kb and mouse in ports next to the PS/2 connector.

So I did test swapping the leads to other connectors on my tower....no change.

I then deleted lvm2.......no change...but I restored that image for the moment.

but it might still be my hard drive set up.

su
/sbin/blkid
/dev/sda1: LABEL="s1" UUID="hidden" TYPE="ext4" PARTUUID="hidden"
/dev/sda2: LABEL="sswap" UUID="hidden" TYPE="swap" PARTUUID="hidden"
/dev/sda3: LABEL="s3" UUID="hidden" TYPE="ext4" PARTUUID="hidden"
second drive not relevant

In the install process I opted out of UUID fstab....then changed to a fstab like this

LABEL=s1 / ext4 defaults,noatime 0 1
LABEL=sswap none swap sw 0 0
LABEL=s3 /s3 ext4 users,rw 0 2

s3 is my data partition....I do not have a separate boot or home. I use fsarchiver to save restore images to s3 using a live usb.

Finally I should mention....this hard drive use to sit in a tradition MBR motherboard and my new mobo only allows me to choose CSM or UEFI....I choose CSM as I have no efi partition.

This may all be irrelevant, but what I am trying to say, it might be my setup that causes udev some issues?

EDIT
just rebooted with an UUID fstab no change to udev delays

thanks for reading

Last edited by aus9 (2020-03-28 01:46:52)

IdeaFix · 2020-03-28 09:11:53

Is Devuan 3 ready to update prod servers from 2.1? I have no heavy load servers, but I need a native php7.3 and a stable system without X, DE and other... actually, only LAMP (in ESXi).

aus9 · 2020-03-28 10:03:31

Hi
I finally spotted but needed prompting this post
https://dev1galaxy.org/viewtopic.php?id=1925

as my removal of systemd stuff is on the beta iso I thought I would share the little I know here
And I am glad that link is a sticky too.

For those anal creatures like me, who boasts they have no systemd on their PC....read on or ignore as you see fit. My testing is very sparse but FF streaming youtube is fine and local media files mp4 and mp3 are fine after doing this playing using VLC

This is tested only on beowulf_3.0.0_beta dated Mar 11 not Mar 25 clean install on internal hard drive.

# find / -name systemd
> /var/lib/systemd
> /lib/systemd
> /usr/lib/systemd
> /etc/systemd
> /run/systemd
# rm -rf /var/lib/systemd /lib/systemd /usr/lib/systemd /etc/systemd /run/systemd

full reboot finds only one gremlin found (so far)
I lose GUI restart and shutdown as per image
https://imgur.com/JVhuo4y

this I have fixed for now with 2 new desktops with contents

echo '[Desktop Entry]
Version=1.0
Type=Application
Exec=pkexec /sbin/shutdown -r now
Icon=system-log-out
StartupNotify=false
Terminal=false
Name=restart
Name[en_US.UTF-8]=restart' > Desktop/restart.desktop

echo '[Desktop Entry]
Version=1.0
Type=Application
Exec=pkexec /sbin/shutdown -h now
Icon=system-log-out
StartupNotify=false
Terminal=false
Name=shutdown' > Desktop/shutdown.desktop

chmod 755 Desktop/shutdown.desktop
chmod 755 Desktop/restart.desktop

YMMV

Torclyn · 2020-03-28 11:54:16

Hi there,

thanks for all your work on this!

System

AMD Ryzen 7 1700
ASUS Prime B350 Plus
AMD RX Vega 56

Install

I did a fresh install from the netinstall ISO, choosing KDE plasma with sddm and everything went fine. The system rebooted into console, no graphical interface came up. Not surprisingly, startx failed as well.
amdgpu was installed, as was mesa, but the firmware-amd-graphics package was missing. While at it I also installed amd64-microcode, and when rebooting the graphical login came up fine.
When installing packages, I keep getting messages about being unable to correctly set the locale because LC_something appears to be missing. I'll look into this later, but I thought you might be interested in the firmware issue.

On my mobile machine I upgraded from Ascii which went just smoothly.

Thanks again for this great OS!

The officially official Devuan Forum!

#51 2020-03-25 18:14:55

Re: Beowulf Beta is here!

#52 2020-03-25 18:19:40

Re: Beowulf Beta is here!

#53 2020-03-25 18:22:59

Re: Beowulf Beta is here!

#54 2020-03-25 18:24:52

Re: Beowulf Beta is here!

#55 2020-03-26 04:13:38

Re: Beowulf Beta is here!

#56 2020-03-26 04:17:43

Re: Beowulf Beta is here!

#57 2020-03-26 09:10:19

Re: Beowulf Beta is here!

#58 2020-03-26 19:07:51

Re: Beowulf Beta is here!

#59 2020-03-27 01:17:17

Re: Beowulf Beta is here!

#60 2020-03-27 01:34:31

Re: Beowulf Beta is here!

#61 2020-03-27 05:56:17

Re: Beowulf Beta is here!

#62 2020-03-27 15:14:21

Re: Beowulf Beta is here!

#63 2020-03-27 15:17:06

Re: Beowulf Beta is here!

#64 2020-03-27 15:37:20

Re: Beowulf Beta is here!

#65 2020-03-27 19:09:35

Re: Beowulf Beta is here!

#66 2020-03-27 19:30:30

Re: Beowulf Beta is here!

#67 2020-03-27 19:57:05

Re: Beowulf Beta is here!

#68 2020-03-27 21:27:31

Re: Beowulf Beta is here!

#69 2020-03-27 21:38:00

Re: Beowulf Beta is here!

#70 2020-03-27 22:04:57

Re: Beowulf Beta is here!

#71 2020-03-27 22:05:52

Re: Beowulf Beta is here!

#72 2020-03-28 01:37:39

Re: Beowulf Beta is here!

#73 2020-03-28 09:11:53

Re: Beowulf Beta is here!

#74 2020-03-28 10:03:31

Re: Beowulf Beta is here!

#75 2020-03-28 11:54:16

Re: Beowulf Beta is here!

Board footer