Hi,

On 23/11/19 4:38 am, Arnt Karlsen wrote:
> On Sat, 23 Nov 2019 03:17:58 +1100, Andrew wrote in message
> <c5fc27fa-d0a4-c3e8-f1e4-684b08c6a623@???>:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA256
>>
>> Jo.
>>
>> On 23/11/19 12:26 am, Ismael L. Donis Garcia wrote:
>>> In the worst case we would not be able to rely on MX Linux?
>>
>> I think not.
>>
>> MX is not exactly against systemd, they use it still, but not as the
>> init system. And MX is reliant upon Debian anyway.... so sad that
>> Debian is being destroyed by systemd. I don't know what the answer
>> is, but it would have been best if the original TC chose against
>> systemd, but that ship has sailed and the damage is well and truly
>> done and it's only getting worse.
>>
>> I prefer Devuan over MX, but at this time I am using MX on a machine
>> as an interim until my machine is properly supported by Devuan (if
>> that ever happens properly).
>
> ..what's missing?

Okay, first off, I didn't see your email in the list yet, but it is
addressed to the list; so I'll reply with list inclusion...

I have tried ASCII 2.0 -- but it looks like there is a new 2.1 version
just about to be announced?

My machine is a NUC8i7HVK with the following hardware details:



# inxi -F -z --no-host -y 80
System:
Kernel: 4.19.0-5-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
Distro: MX-18.3_x64 Continuum May 26 2019
Machine:
Type: Desktop System: Intel product: NUC8i7HVK v: J71485-503
serial: <filter>
Mobo: Intel model: NUC8i7HVB v: J68196-503 serial: <filter> UEFI: Intel
v: HNKBLi70.86A.0058.2019.0705.1646 date: 07/05/2019
CPU:
Topology: Quad Core model: Intel Core i7-8809G bits: 64 type: MT MCP
L2 cache: 8192 KiB
Speed: 800 MHz min/max: 800/4200 MHz Core speeds (MHz): 1: 800 2: 800
3: 800
4: 801 5: 801 6: 800 7: 800 8: 800
Graphics:
Device-1: Intel driver: i915 v: kernel
Device-2: AMD driver: amdgpu v: kernel
Display: server: X.Org 1.19.2 driver: amdgpu,ati,modesetting
unloaded: fbdev,radeon,vesa resolution: 3840x2160~60Hz, 2560x1440~60Hz
OpenGL: renderer: AMD VEGAM (DRM 3.27.0 4.19.0-5-amd64 LLVM 7.0.0)
v: 4.5 Mesa 18.2.6
Audio:
Device-1: Intel driver: snd_hda_intel
Device-2: AMD driver: snd_hda_intel
Sound Server: ALSA v: k4.19.0-5-amd64
Network:
Device-1: Intel Ethernet I219-LM driver: e1000e
IF: eth1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Intel I210 Gigabit Network driver: igb
IF: eth0 state: down mac: <filter>
Drives:
Local Storage: total: 1.36 TiB used: 74.17 GiB (5.3%)
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 1TB
size: 931.51 GiB
ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 970 EVO Plus 1TB
size: 931.51 GiB
ID-3: /dev/sda type: USB vendor: Samsung model: Portable SSD T5
size: 465.76 GiB
Partition:
ID-1: / size: 118.75 GiB used: 74.09 GiB (62.4%) fs: ext4 dev: /dev/dm-0
ID-2: /boot size: 487.9 MiB used: 85.7 MiB (17.6%) fs: ext4 dev:
/dev/sda2
Sensors:
System Temperatures: cpu: 49.0 C mobo: N/A gpu: amdgpu temp: 37 C
Fan Speeds (RPM): N/A
Info:
Processes: 254 Uptime: 53m Memory: 31.34 GiB used: 3.59 GiB (11.5%)
Shell: bash inxi: 3.0.36


Installing with ASCII 2.0 wouldn't boot properly to the XFCE desktop and
I wasn't interested in changing kernels or doing anything else to make
it work out of the box, including trying to work out why XFCE was a
problem with Devuan ASCII.


Maybe I should try ASCII 2.1 -- but I was expecting Beowulf to be here
"any time soon" ... for a longggg while now.


The MX installer doesn't support installation installation on RAID1
mdadm devices! I prefer to use RAID1 for everything, then LUKS on all
but the /boot partition with LVM2 -- that sort of setup isn't possible
with the MX installer.

But XFCE works perfectly out of the box with MX, so I have something to
work with in the meantime.

Kind Regards
AndrewM