Please share your Linux installation experience.

[tsuren]

No issues. Everything works comfortably for now.

A small correction now after using for a week or so, now I've found an issue.

Not so much about the OS, but with part of the hardware. I found out that there's a significant sound degradation with one of the Display Ports. The sound carried via this port is crackling. I thought first it was the cables I am using, or the connections, etc.. but at the end after checking each connections, cables, set up to pin down the problem, changing the DP to the left to right solved the issue.

As I do not need to use the second DP for now, this is not much of an issue for me, but I am curious to know if others have a similar experience.

 

[adrian]

I tried Fedora 26 Beta and there is still no wireless support. Even the workaround I posted does not work. Kinda bummed so I loaded up Pop!_OS 22.04 LTS and no wireless but the workaround does fix it. Going to try Arch when the new version drops on May 1.

This may not solve your problem.Check if Kernel 5.17 is available to install in your distro in many it is. From what I read on forum 5.17 solves the problem with WIFI. My system has the AX200 WIFI which works with older lernels so I can not check.

 

[sgtnasty11b20]

I can confirm the latest Fedora 36 works with WIFI in live boot. I installed it over my Arch Linux and its working flawlessly.

 

[eugene_]

Bought the barebone version in May and fitted with Gigabyte AORUS NVMe Gen4 SSD. Runs Gentoo with kernel 5.18.

The Mediatek wifi card was a disaster in many ways: did not detect 5 GHz stations from the first scan after power up, there were reconnects, VHT was not available most of the time. But what's more, the machine was not able to wake up neither from S3 nor S4 sleep reliably. In most of the cases after short sleep and always after a long one (longer than an hour) the machine became completely unresponsive, pressing the power button for any reasonable amount of time (even 1 min) did not wake it up (no fan spin up even). For the S4 sleep it helped to reconnect power supply and then it can be powered up. Never happened with the WiFi card took out, but happened even after unloading the mt7921e module. So, I replaced the card with Intel AX210, but the sleep problem still happened, albeit much less frequently. Adding pcie_aspm=off kernel parameter seems helped (but did not help with the Mediatek card) and the machine can be woken up from long S3 sleep. I did not test with another NVME drive.

Then there are GPU-related problems with suspending. Rarely suspending to S3 does not succeed due to some of the USB devices returns EBUSY and then the GPU finds itself in half-initialised state and the graphical session hangs. Resuming from S3 frequently resulted in GPU errors with kernels 5.17 and 5.18 and linux-firmware version 20220509
until I switched to the live (git) version of the linux-firmware package.

If a connected screen uses auto selection for the input port, the screen never enters DPMS sleep mode (https://gitlab.freedesktop.org/drm/amd/-/issues/662).

 

[solidus1983]

So my experience is no great.

As with @didli i am having the same error when running 2 2.5" SSD's in the system, infact the SSD in SATA Port 0 died constant bad blocks, lost some data too. I have backups of the photo's but lost some valued files but hey thats what you get when you erase the backup drive to make clean backups. PVE backup stated it backed up fine on ztsd however trying to extract it results in failure due to bad block.

So after replacing the cables and placing in a new SSD you guested it the on in SATA Port 0 got nuked again. Completely lost faith in the system waiting on the seller to contact me back as i got the system for the 2x 2.5" drives and the M.2 as it was going to be used for a Proxmox server only.

The strange thing is if only 1 2.5" drive is used all is fine even if its in SATA Port 0. Which means its down to power which means either the PSU supplied is not up to snuff or the Power delivery on the mainboard is not up to snuff. Either way its not good.

Not even sure if a Firmware Update will help either. I was so happy with the device before all this happened.

Update, simply trying to install Pop OS 21 on to the drive connected to SATA 0 whilst there is another drive in SATA 1 causes the same errors, however installing to SATA 1 works fine.

 

[Carbon fib'er]

As with @didli i am having the same error when running 2 2.5" SSD's in the system,

@DaneDevOps mentioned in another thread that the wifi antenna wires running under or close to the drives caused a problem similar to what you describe. They removed the m.2 wifi/bluetooth card, and their problem went away.

If that worked for you, but you needed wifi, you'd have to use a USB wifi adapter. (Or, maybe shielding the wires would do it. Or, lengthen the wires so they travel around the edge of the box? Not through the middle? I don't know if those wires are the antenna, or if the black bulges they connect to are. You'd have to understand that more before trying those ideas.).

 

[joey]

So my experience is no great.

As with @didli i am having the same error when running 2 2.5" SSD's in the system, infact the SSD in SATA Port 0 died constant bad blocks, lost some data too. I have backups of the photo's but lost some valued files but hey thats what you get when you erase the backup drive to make clean backups. PVE backup stated it backed up fine on ztsd however trying to extract it results in failure due to bad block.

So after replacing the cables and placing in a new SSD you guested it the on in SATA Port 0 got nuked again. Completely lost faith in the system waiting on the seller to contact me back as i got the system for the 2x 2.5" drives and the M.2 as it was going to be used for a Proxmox server only.

The strange thing is if only 1 2.5" drive is used all is fine even if its in SATA Port 0. Which means its down to power which means either the PSU supplied is not up to snuff or the Power delivery on the mainboard is not up to snuff. Either way its not good.

Not even sure if a Firmware Update will help either. I was so happy with the device before all this happened.

Update, simply trying to install Pop OS 21 on to the drive connected to SATA 0 whilst there is another drive in SATA 1 causes the same errors, however installing to SATA 1 works fine.

Please modify the following configuration to test
/sys/class/scsi_host/host1/link_power_management_policy
- and change the configuration to :
max_performance
Hope this information is helpful to you, thank you

 

[solidus1983]

Thank you @Carbon fib'er for your suggestion will try that tomorrow, i don't need Wireless as its will be a proxmox server again if i can get the issue solved.
Also @joey I shell also try your suggestion too. If this works, is there a way to make it perm via the grub config file?

Or will a udev rule work best?

SUBSYSTEM=="scsi_host", KERNEL=="host*", ATTR{link_power_management_policy}="max_performance"

 

[Carbon fib'er]

I shell also try your suggestion too. If this works, is there a way to make it perm via the grub config file?

This post (in the thread I linked to about the wifi antenna wires perhaps being the problem) shows how to script the "max-performance" setting. I've never used Promoxx. It should have a way to execute a script at startup. I'm pretty sure I saw something about how that setting can be done from GRUB too (after editing the conf file, and grub-update). I can't find it now. I never like messing with grub. I'd look for a way to run that command at startup.

 

[joey]

Thank you @Carbon fib'er for your suggestion will try that tomorrow, i don't need Wireless as its will be a proxmox server again if i can get the issue solved.
Also @joey I shell also try your suggestion too. If this works, is there a way to make it perm via the grub config file?

Or will a udev rule work best?

SUBSYSTEM=="scsi_host", KERNEL=="host*", ATTR{link_power_management_policy}="max_performance"

You could try creating a rules file to have udev set all scsi_host devices to max_performance on startup. Hope this information is helpful to you, thank you

 

[solidus1983]

@

You could try creating a rules file to have udev set all scsi_host devices to max_performance on startup. Hope this information is helpful to you, thank you

Update:

Right so after adding

echo 'SUBSYSTEM=="scsi_host", KERNEL=="host*", ATTR{link_power_management_policy}="max_performance"' > /etc/udev/rules.d/60-power.rules

as well as adding to grub or in my case systemd as i am testing with pop-os

libata.force=noncq

I was able to remove the errors that was until i then benchmarked the drive then the system started to produce

[    1.827632] ata1.00: FORCE: horkage modified (noncq)
[    1.829087] ata1.00: ATA-9: WDC WDS120G1G0A-00SS50, Z3311000, max UDMA/133
[    1.829091] ata1.00: 234441648 sectors, multi 1: LBA48 NCQ (not used)
[    1.834003] ata1.00: Features: Dev-Sleep
[    1.843539] ata1.00: configured for UDMA/133
[  162.644189] ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x2c0101 action 0x6 frozen
[  162.644201] ata1.00: irq_stat 0x08000000, interface fatal error
[  162.644207] ata1.00: failed command: READ DMA EXT
[  162.644209] ata1.00: cmd 25/00:00:b0:56:19/00:0a:02:00:00/e0 tag 17 dma 1310720 in
[  162.644214] ata1.00: status: { DRDY }
[  163.133697] ata1.00: configured for UDMA/133
[  164.700336] ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x2c0100 action 0x6 frozen
[  164.700353] ata1.00: irq_stat 0x08000000, interface fatal error
[  164.700365] ata1.00: failed command: READ DMA EXT
[  164.700368] ata1.00: cmd 25/00:f0:00:3b:84/00:06:02:00:00/e0 tag 30 dma 909312 in
[  164.700379] ata1.00: status: { DRDY }
[  165.193659] ata1.00: configured for UDMA/133
[  167.656315] ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x2c0100 action 0x6 frozen
[  167.656331] ata1.00: irq_stat 0x08000000, interface fatal error
[  167.656342] ata1.00: failed command: READ DMA EXT
[  167.656344] ata1.00: cmd 25/00:00:c8:37:f0/00:0a:02:00:00/e0 tag 11 dma 1310720 in
[  167.656354] ata1.00: status: { DRDY }
[  168.150058] ata1.00: configured for UDMA/133
[  169.724557] ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x2c0100 action 0x6 frozen
[  169.724567] ata1.00: irq_stat 0x08000000, interface fatal error
[  169.724578] ata1.00: failed command: READ DMA EXT
[  169.724580] ata1.00: cmd 25/00:f0:f8:24:5b/00:05:03:00:00/e0 tag 26 dma 778240 in
[  169.724593] ata1.00: status: { DRDY }
[  170.217682] ata1.00: configured for UDMA/133
[  173.916314] ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x2c0100 action 0x6 frozen
[  173.916331] ata1.00: irq_stat 0x08000000, interface fatal error
[  173.916344] ata1.00: failed command: READ DMA EXT
[  173.916347] ata1.00: cmd 25/00:00:c8:76:ea/00:0a:03:00:00/e0 tag 2 dma 1310720 in
[  173.916359] ata1.00: status: { DRDY }
[  174.409626] ata1.00: configured for UDMA/133
[  188.512563] ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x2c0100 action 0x6 frozen
[  188.512580] ata1.00: irq_stat 0x08000000, interface fatal error
[  188.512591] ata1.00: failed command: READ DMA EXT
[  188.512594] ata1.00: cmd 25/00:00:90:80:26/00:0a:06:00:00/e0 tag 28 dma 1310720 in
[  188.512606] ata1.00: status: { DRDY }
[  189.005684] ata1.00: configured for UDMA/133
[  195.900568] ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x2c0100 action 0x6 frozen
[  195.900585] ata1.00: irq_stat 0x08000000, interface fatal error
[  195.900596] ata1.00: failed command: READ DMA EXT
[  195.900599] ata1.00: cmd 25/00:f0:d0:82:44/00:06:07:00:00/e0 tag 18 dma 909312 in
[  195.900611] ata1.00: status: { DRDY }
[  196.393672] ata1.00: configured for UDMA/133
[  196.448878] ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x2c0100 action 0x6 frozen
[  196.448888] ata1.00: irq_stat 0x08000000, interface fatal error
[  196.448899] ata1.00: failed command: READ DMA EXT
[  196.448902] ata1.00: cmd 25/00:00:88:8f:44/00:0a:07:00:00/e0 tag 22 dma 1310720 in
[  196.448913] ata1.00: status: { DRDY }
[  196.941963] ata1.00: configured for UDMA/133
[  201.832568] ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x2c0100 action 0x6 frozen
[  201.832586] ata1.00: irq_stat 0x08000000, interface fatal error
[  201.832598] ata1.00: failed command: READ DMA EXT
[  201.832601] ata1.00: cmd 25/00:90:d0:69:d3/00:05:07:00:00/e0 tag 24 dma 729088 in
[  201.832613] ata1.00: status: { DRDY }
[  202.321690] ata1.00: configured for UDMA/133
[  202.644229] ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x2c0100 action 0x6 frozen
[  202.644239] ata1.00: irq_stat 0x08000000, interface fatal error
[  202.644246] ata1.00: failed command: READ DMA EXT
[  202.644248] ata1.00: cmd 25/00:00:98:83:d4/00:0a:07:00:00/e0 tag 23 dma 1310720 in
[  202.644256] ata1.00: status: { DRDY }
[  203.133923] ata1.00: configured for UDMA/133
[  206.940299] ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x2c0100 action 0x6 frozen
[  206.940316] ata1.00: irq_stat 0x08000000, interface fatal error
[  206.940328] ata1.00: failed command: READ DMA EXT
[  206.940331] ata1.00: cmd 25/00:60:b8:9a:3e/00:05:08:00:00/e0 tag 17 dma 704512 in
[  206.940343] ata1.00: status: { DRDY }
[  207.433613] ata1.00: configured for UDMA/133
[  207.640511] ata1.00: limiting speed to UDMA/100:PIO4
[  207.640520] ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x2c0100 action 0x6 frozen
[  207.640529] ata1.00: irq_stat 0x08000000, interface fatal error
[  207.640538] ata1.00: failed command: READ DMA EXT
[  207.640540] ata1.00: cmd 25/00:30:98:42:3f/00:06:08:00:00/e0 tag 22 dma 811008 in
[  207.640550] ata1.00: status: { DRDY }
[  208.133946] ata1.00: configured for UDMA/100
[  212.324286] ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x2c0100 action 0x6 frozen
[  212.324301] ata1.00: irq_stat 0x08000000, interface fatal error
[  212.324312] ata1.00: failed command: READ DMA EXT
[  212.324315] ata1.00: cmd 25/00:00:b8:de:aa/00:0a:08:00:00/e0 tag 4 dma 1310720 in
[  212.324326] ata1.00: status: { DRDY }
[  212.817889] ata1.00: configured for UDMA/100
[  217.644157] ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x2c0100 action 0x6 frozen
[  217.644171] ata1.00: irq_stat 0x08000000, interface fatal error
[  217.644182] ata1.00: failed command: READ DMA EXT
[  217.644185] ata1.00: cmd 25/00:f0:d8:8b:39/00:05:09:00:00/e0 tag 16 dma 778240 in
[  217.644196] ata1.00: status: { DRDY }
[  218.137630] ata1.00: configured for UDMA/100
[  228.188557] ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x2c0100 action 0x6 frozen
[  228.188573] ata1.00: irq_stat 0x08000000, interface fatal error
[  228.188585] ata1.00: failed command: READ DMA EXT
[  228.188588] ata1.00: cmd 25/00:00:60:aa:58/00:0a:0a:00:00/e0 tag 21 dma 1310720 in
[  228.188599] ata1.00: status: { DRDY }
[  228.681682] ata1.00: configured for UDMA/100
[  234.076536] ata1.00: limiting speed to UDMA/33:PIO4
[  234.076546] ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x2c0100 action 0x6 frozen
[  234.076555] ata1.00: irq_stat 0x08000000, interface fatal error
[  234.076566] ata1.00: failed command: READ DMA EXT
[  234.076569] ata1.00: cmd 25/00:70:18:20:0a/00:06:0b:00:00/e0 tag 21 dma 843776 in
[  234.076580] ata1.00: status: { DRDY }
[  234.569688] ata1.00: configured for UDMA/33
[code]

 

[solidus1983]

and as you can see the sata link crapped the bed.

[    1.054404] ata1: SATA max UDMA/133 abar m2048@0xfce00000 port 0xfce00100 irq 52
[    1.826583] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[  162.644203] ata1: SError: { RecovData UnrecovData CommWake 10B8B BadCRC }
[  162.644219] ata1: hard resetting link
[  163.116506] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[  163.144752] ata1: EH complete
[  164.700357] ata1: SError: { UnrecovData CommWake 10B8B BadCRC }
[  164.700386] ata1: hard resetting link
[  165.176498] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[  165.204691] ata1: EH complete
[  167.656336] ata1: SError: { UnrecovData CommWake 10B8B BadCRC }
[  167.656360] ata1: hard resetting link
[  168.132506] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[  168.161489] ata1: EH complete
[  169.724546] ata1: limiting SATA link speed to 3.0 Gbps
[  169.724571] ata1: SError: { UnrecovData CommWake 10B8B BadCRC }
[  169.724599] ata1: hard resetting link
[  170.200496] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[  170.229014] ata1: EH complete
[  173.916336] ata1: SError: { UnrecovData CommWake 10B8B BadCRC }
[  173.916366] ata1: hard resetting link
[  174.392439] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[  174.420634] ata1: EH complete
[  188.512584] ata1: SError: { UnrecovData CommWake 10B8B BadCRC }
[  188.512613] ata1: hard resetting link
[  188.988496] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[  189.016709] ata1: EH complete
[  195.900589] ata1: SError: { UnrecovData CommWake 10B8B BadCRC }
[  195.900618] ata1: hard resetting link
[  196.376495] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[  196.404734] ata1: EH complete
[  196.448868] ata1: limiting SATA link speed to 1.5 Gbps
[  196.448892] ata1: SError: { UnrecovData CommWake 10B8B BadCRC }
[  196.448923] ata1: hard resetting link
[  196.924511] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[  196.953708] ata1: EH complete
[  201.832591] ata1: SError: { UnrecovData CommWake 10B8B BadCRC }
[  201.832619] ata1: hard resetting link
[  202.304487] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[  202.333021] ata1: EH complete
[  202.644242] ata1: SError: { UnrecovData CommWake 10B8B BadCRC }
[  202.644262] ata1: hard resetting link
[  203.116495] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[  203.145370] ata1: EH complete
[  206.940321] ata1: SError: { UnrecovData CommWake 10B8B BadCRC }
[  206.940349] ata1: hard resetting link
[  207.416223] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[  207.444611] ata1: EH complete
[  207.640532] ata1: SError: { UnrecovData CommWake 10B8B BadCRC }
[  207.640556] ata1: hard resetting link
[  208.116496] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[  208.145496] ata1: EH complete
[  212.324305] ata1: SError: { UnrecovData CommWake 10B8B BadCRC }
[  212.324333] ata1: hard resetting link
[  212.800457] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[  212.829015] ata1: EH complete
[  217.644175] ata1: SError: { UnrecovData CommWake 10B8B BadCRC }
[  217.644203] ata1: hard resetting link
[  218.120493] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[  218.148679] ata1: EH complete
[  228.188578] ata1: SError: { UnrecovData CommWake 10B8B BadCRC }
[  228.188606] ata1: hard resetting link
[  228.664491] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[  228.693513] ata1: EH complete
[  234.076559] ata1: SError: { UnrecovData CommWake 10B8B BadCRC }
[  234.076587] ata1: hard resetting link
[  234.552499] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[  234.580993] ata1: EH complete

So going to try the wireless card removal next.

Update: I removed the Wireless card and ran the same tests guest what, the same errors are showing. So looking like a Faulty controller on the mainboard so guess its RMA time.

Also for them that are wondering what my testing logic is. Its the following.

Clean install of Pop OS, with the udev rule and noncq added to booting kernel options. Then opening the terminal and "sudo -s" read for dmesg, i will then load up the disk benchmark and select the WD Green SSD 128GB, i then run the benchmark and then run "dmesg | grep ata1" and "dmesg | grep ata2" after.

The RMA came through so sending the device back to company i purchased from.

 

[didli]

'Seems I was a bit more lucky for the same issue. The power_management_policy rule and swapping the drives from their respective slots did the trick (I now suspect that swapping the drives did nothing, but maybe replacing them helped a bit isolating them from the wire antenna issue ?).
@solidus1983 : I'm interested in your experience with RMA if you go with it (or already did).

 

[cherio]

Arch Linux, installed the Arch way.

I bought the Windows 16GB RAM / 256GB SSD version. But then upgraded RAM, added 2 HDDs and upgraded the SSD.

Purchased: Windows 16GB RAM / 256GB SSD version
Upgraded to
RAM: 64GB (Kingston FURY Impact 64GB (2x32GB) 3200MHz DDR4 CL20 KF432S20IBK2/64)
SSD: 1TB (SAMSUNG 980 PRO SSD 1TB PCIe 4.0 NVMe Gen 4 Gaming M.2, MZ-V8P1T0B)
HDD: 2TB x 2 (Western Digital 2TB WD Blue - WD20SPZX)

I did not have to change anything in BIOS.

I have not tried WiFi yet but everything else (USB, Bluetooth, 3.5 sockets, Integrated Graphics, HDMI, Ethernet, etc) work well.

 

[EthanH]

Arch Linux, installed the Arch way.

I bought the Windows 16GB RAM / 256GB SSD version. But then upgraded RAM, added 2 HDDs and upgraded the SSD.

Purchased: Windows 16GB RAM / 256GB SSD version
Upgraded to
RAM: 64GB (Kingston FURY Impact 64GB (2x32GB) 3200MHz DDR4 CL20 KF432S20IBK2/64)
SSD: 1TB (SAMSUNG 980 PRO SSD 1TB PCIe 4.0 NVMe Gen 4 Gaming M.2, MZ-V8P1T0B)
HDD: 2TB x 2 (Western Digital 2TB WD Blue - WD20SPZX)

I did not have to change anything in BIOS.

I have not tried WiFi yet but everything else (USB, Bluetooth, 3.5 sockets, Integrated Graphics, HDMI, Ethernet, etc) work well.

@cherio - thanks for your post. Have you seen any issues with the two 2.5inch drives? Thanks

 

[cherio]

@cherio - thanks for your post. Have you seen any issues with the two 2.5inch drives? Thanks

I had seen posts about possible interference from the WiFi module, when the HDD connecting wires run in proximity to it. As a preventative measure I routed the HDD wires at what I deemed to be a safe distance and even put a couple of dividers made of HVAC aluminium foil tape (ad-hoc electromagnetic shielding). Honestly I do not know if all that was even necessary ¯\_(ツ)_/¯ I was just playing safe.

The HDDs are set up as RAID1 and I've experienced no issues with them so far.

Since my previous post I had a chance to use WiFi via iwd. From my experience kernels 6.1 and 6.2 (Arch mainstream version at the moment) handle it without issues.

One BIOS customization that I made since my original post is related to the AMD stutter issue. The issue is caused by TPM. BIOS update reportedly does not fix the issue, but simply reduces the frequency of its occurrence. I personally think the risk of updating BIOS in this case is not worth the benefit. Since Linux doesn't really require it, I simply disabled TPM in BIOS.

Speaking of BIOS updates. I personally will likely hold off buying another computer from Minisforum until they solve their support issues with releasing new BIOS versions. This branch of business doesn't exist and you have a problem that can only be resolved via BIOS update - you are doomed. People in these forums complain, but it has had no effect so far.

 

[Peter47]

Arch Linux, installed the Arch way.

I bought the Windows 16GB RAM / 256GB SSD version. But then upgraded RAM, added 2 HDDs and upgraded the SSD.

Purchased: Windows 16GB RAM / 256GB SSD version
Upgraded to
RAM: 64GB (Kingston FURY Impact 64GB (2x32GB) 3200MHz DDR4 CL20 KF432S20IBK2/64)
SSD: 1TB (SAMSUNG 980 PRO SSD 1TB PCIe 4.0 NVMe Gen 4 Gaming M.2, MZ-V8P1T0B)
HDD: 2TB x 2 (Western Digital 2TB WD Blue - WD20SPZX)

I did not have to change anything in BIOS.

I have not tried WiFi yet but everything else (USB, Bluetooth, 3.5 sockets, Integrated Graphics, HDMI, Ethernet, etc) work well.

Hi @cherio - I hope it's ok to ask you on this older thread.... I was thinking about getting exactly the same ram as you but the Samsung 970 Evo Plus 1TB ‎MZ-V7S1T0BW instead of the 980 pro

The reason i was going for the 970 evo plus was obviously because of the pcie 3.0 and i notice the 980 pro is pcie 4.0

The price difference is very small, so I was wondering if there are any pros or cons to going for the 980? Like I guess it just drops back to gen 3 performance, or can you please share your thoughts?

I too am using Arch albeit an up to date Manjaro.... I thank you in advance

 

[7blade]

ZERO issues with Linux Mint Install.
Refer to my post for details:

RED DEATH INSTALL

Linux Mint works right out of the box. No drivers etc required. HOWEVER, Windows consistently fails regardless of mods made to install USB. Here's the backstory. Got the HX-90 with 32GB ram and stock 512GB M.2. Upgraded M.2 to 2TB and installed Linux Mint 21.2 from bootable USB. It was VERY easy...

bbs.minisforum.com

Bought my HX90 on July 4th, 2023. Delivered July 6th, 2023
Except for initial HW installs and OS/SW update reboots, been running 24/7 since.