[Spce-user] mr13.5.1 Initial Configuration woes

[Newbie]

Again, thanks for your prompt response!  Our posts crossed.

Realised afterwards its convention is 'old' subdirectory.

It only has 2GB RAM (but that meets the stated Minimum requirements).

I made no change to any configuration.

`journalctl --priority=4` :-

Nov 05 17:11:21 spce kernel: ACPI BIOS Warning (bug): 32/64X length 
mismatch in FADT/Pm1aEventBlock: 32/16 (20240827/tbfadt-560)
Nov 05 17:11:21 spce kernel: ACPI BIOS Warning (bug): 32/64X length 
mismatch in FADT/PmTimerBlock: 32/24 (20240827/tbfadt-560)
Nov 05 17:11:21 spce kernel: ACPI BIOS Warning (bug): Invalid length for 
FADT/Pm1aEventBlock: 16, using default 32 (20240827/tbfadt-665)
Nov 05 17:11:21 spce kernel: ACPI BIOS Warning (bug): Invalid length for 
FADT/PmTimerBlock: 24, using default 32 (20240827/tbfadt-665)
Nov 05 17:11:22 spce kernel: mtrr: your CPUs had inconsistent variable 
MTRR settings
Nov 05 17:11:22 spce kernel: ACPI Warning: SystemIO range 
0x0000000000000428-0x000000000000042F conflicts with OpRegion 
0x0000000000000428-0x0000000000000429 (\GPE0) (20240827/utaddress-204)
Nov 05 17:11:22 spce kernel: ACPI Warning: SystemIO range 
0x0000000000000500-0x000000000000052F conflicts with OpRegion 
0x0000000000000518-0x000000000000051B (\BGPO) (20240827/utaddress-204)
Nov 05 17:11:22 spce kernel: ACPI Warning: SystemIO range 
0x0000000000000500-0x000000000000052F conflicts with OpRegion 
0x000000000000050C-0x000000000000050F (\IGPO) (20240827/utaddress-204)
Nov 05 17:11:22 spce kernel: lpc_ich: Resource conflict(s) found 
affecting gpio_ich
Nov 05 17:11:22 spce kernel: r8169 0000:01:00.0: can't disable ASPM; OS 
doesn't have ASPM control
Nov 05 17:11:23 spce kernel: device-mapper: core: 
CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will 
not be recorded in the IMA log.
Nov 05 17:11:28 spce lvm[389]: PV /dev/sda3 online, VG ngcp is complete.
Nov 05 17:11:28 spce lvm[389]: VG ngcp finished
Nov 05 17:11:29 spce (acpid)[397]: acpid.service: Referenced but unset 
environment variable evaluates to an empty string: OPTIONS
Nov 05 17:11:30 spce kernel: at24 0-0050: supply vcc not found, using 
dummy regulator
Nov 05 17:11:30 spce kernel: at24 0-0051: supply vcc not found, using 
dummy regulator
Nov 05 17:11:30 spce kernel: block sda: the capability attribute has 
been deprecated.
Nov 05 17:36:16 spce sshd[7597]: error: Bind to port 22 on :: failed: 
Address already in use.
Nov 05 17:36:16 spce sshd[7597]: error: Bind to port 22 on 0.0.0.0 
failed: Address already in use.
Nov 05 17:38:59 spce (mariadbd)[9233]: mariadb.service: Referenced but 
unset environment variable evaluates to an empty string: MYSQLD_OPTS, 
_WSREP_NEW_CLUSTER
Nov 05 17:39:12 spce /etc/mysql/debian-start[9258]: Reading datadir from 
the MariaDB server failed. Got the following error when executing the 
'mysql' command line client
Nov 05 17:39:12 spce /etc/mysql/debian-start[9258]: ERROR 1045 (28000): 
Access denied for user 'debian-sys-maint'@'localhost' (using password: YES)
Nov 05 17:39:12 spce /etc/mysql/debian-start[9258]: FATAL ERROR: Upgrade 
failed
Nov 05 17:43:25 spce kernel: coredump: 11174(sysctl): Unsafe 
core_pattern used with fs.suid_dumpable=2: pipe handler or fully 
qualified core dump path required. Set kernel.core_pattern before 
fs.suid_dumpable.


Searching for info on the BIOS bug, Lowell Gilbert wrote 10 years ago:-


:Newer versions of ACPI introduced 64-bit representations of General 

:Purpose Event (GPE) descriptions. The old 32-bit representations are 

:still  present  as  well,  but  are  supposed to be consistent with the 

:64-bit 

:versions. On your system, they are not; this could be an indicator that 

:your firmware is corrupted, but in that case you would also (probably) 

:get warnings about failed checksums. 

:> * What's needed to resolve the problem? 

:This message shows a bug in your BIOS. If there are no other signs of 

:problems, you don't need to worry about it (some of the functionality 

:that GPE0 is likely to describe would include temperature sensors, 

:sleep/wake functionality, hyperthreading, and so on). A manufacturer 

:BIOS  update  might  well  fix  the  bug,  but  the kernel will (as the 

:standard 

:requires) use the 64-bit GPE registers anyway. 

:Don't  pull  the  Panic  Lever too quickly for kernel warnings: if they 

:were 

:guaranteed to be a problem, they would be "errors" instead of 

:"warnings". I think a system will usually run without GPE0/1 handlers, 

:but the power management may be less functional. 

:Good luck. 

:-- 

:Lowell Gilbert, embedded/networking software engineer 



SuperMicro (the manufacturer) informed this morning that the motherboard
is not theirs but Intel's. (Sold as new FreePBX plug-n-play configured).

Replacement h/w being organised, but this was being used to evaluate C5.

TIA,

~Newbie