Note:
Maybe linux 6.2 will bring some improvements to the CPU
Intel’s In-Field Scan feature which will help system administrators detect faulty CPU cores was introduced in Linux kernel 5.19. However, it was not working properly. Now, Intel engineers have fixed the issues and it will be available in kernel 6.2. Going on with the news from Intel, the Intel On Demand platform, which is basically a pay-to-unlock and subscription-model hardware is receiving some improvements, including rebranding from Software Defined Silicon and some low-level changes as well.
The Alder Lake and Raptor Lake processors are receiving new updates for HWP (hardware P-states) in order to better calibrate the resulting frequencies on hybrid CPUs.
Intel drm-intel-next driver is receiving refactoring in the display code. The drm-intel-gt-next driver has also been updated for memory management improvements and some other small changes. With the treatment change in the Intel i915 driver, Mesa 23.0 for Vulcan can be able able to deliver performance metrics for Intel Arc Graphics. Furthermore, Intel is making its preparations for bringing Meteor Lake integrated graphics support, which will be the series of CPUs that will be introduced in 2023. There are 5 GPU IDs added for Meteor Lake, but they are disabled as expected.
There are also some misc changes which may be revelant:
USB and Thunderbolt interfaces are being updated as well, with many small changes. The USB driver drops support for some older hardware in Linux kernel 6.2 and brings wake-on-connect and wake-on-disconnect features for the USB4 interface.
Wake-on-connect … interesting, but another potential error source.
@Matt_Hartley
I’ve had success with running the above settings on tlp against 6.1.7 and had not a single nvme disconnect again so far (2 days without one). Lets hope it’s not a coincidence.
I’ll let it run a few more days without restarting and if all is well I figured out a configuration that I’ll keep for now.
Display freezes for a short period every 6-7 seconds even with i915.enable_psr=0
There is no kernel entry about this, audio plays during the whole time and everything else is smooth. Maybe it’s just a gpu buffer getting cleaned aggressively.
Just realized even the mouse moves smoothly.
Audio pops on first module usage (snd_hda_intel)
I hope the first one is fixed with the 6.3 kernel, possibly the 6.2 one as well.
The second one … I have no idea. I’ve disabled audio power saving pretty much everywhere I found related settings and it still pops. It’s annoying, but I can live with that for now.
All in all, I am happy to have bought the laptop right now and not earlier, as I’m still having quite a few issues even with recent kernels (I’m on a rolling release, not everybody has the advantage of getting kernel updates so frequently and uptodate).
Edit:
Update, my nvme disconnected again this morning after nearly 3 days of not doing so. What a bummer. I’ll keep investigating, I already ruled out bad RAM. I guess it’s time to put Ubuntu on my usb stick and see if the issues are the same.
Edit2:
The stutter every 5 seconds is gone! I found a script that is run every 5 seconds that queries xrandr but did not pass --current to the command, so that it always tries to poll for hardware changes. Yay!
Edit3:
I can rule out a faulty RAM and bad kernel modules (I’ve tried a lot of stable and unstable kernel versions) and also any combination with ASPM/ACPI/NVME.maxlatency and TLP.
Since I’m on the latest firmware for both the laptop and the nvme I believe either the drive is faulty, the motherboard has an issue or the combination is bugged. I will run another test with Ubuntu 22.10 and one with no expansion ports plugged to see if it makes any difference. If this doesn’t work I will probably order a Samsung 990 PRO M.2 NVMe SSD and (or Crucial P5 Plus 1TB M.2 PCIe Gen4 NVMe) hope for reimbursement as I really don’t trust NVME disks of WD at this point and don’t want a replacement of them.
So I’ve actually bough the Samsung 990 Pro, cloned all my data to it and it’s running 6+ days now without a single disconnect!
In fact I strongly believe now that my WD-NVME is faulty. I’ve asked Framework Support to send the drive back and get the money back, as I’m very happy with my new Samsung NVME.
There are still some issues left, which I’m about to go down in the coming weeks, but nothing that really stops me from being productive.
@Matt_Hartley in fact since I’ve switched the NVME two weeks ago to a Samsung one I haven’t had a single disconnect. So it confirmed,- my drive was not fine.
I’ll try to revert some of the changes, mainly the nvme+aspm kernel-parameters to see if I can finally remove all this cruft with a working NVME now.
I’m very pleased with my setup now! It’s fast, silent and very convinient. This laptop rocks!
Delighted to hear you’ve gotten this resolved with a different drive. For the sake of tracking, what drive did you have previously once again? The model of WD specifically. Thanks
HDMI Splitter does not reliably work
ToDo: Try to set up EDID manually for it to work
Sometimes expansion ports stop working and need replugging
IDEA: Related to kernel updates?
Sometimes does not wake up from suspend
IDEA: Remove ACPI/NVME fixes
Audio pops on first module usage (snd_hda_intel)
BETTER: Setup modprobe.blacklist=hid_sensor_hub,pcspkr,snd_pcsp
My past issues:
Short graphical stutters every X seconds even with i915.enable_psr=0
Better than without, but still not gone.
DONE: xrandr needs --current to not poll for changes
Thanks for the details above. On the point of the HDMI splitter, something I had to do for my display card was to set up a kernel parameter as sometimes the DP card wouldn’t kick on when I also had HDMI connected.
For me, I used video=DP-1:1920x1080M@60 which gave me the desired resolution and framerate (changed to the desired settings). Takes affect the login screen. Basically forces the port to wake up regardless of other settings. So for you, it would be video=HDMI-1 or -2, then set the resolution.
I got a Razer Core X eGPU case with an ASRock RX 6600 GPU and guess what?
$ DRI_PRIME=1 glmark2
=======================================================
glmark2 2023.01
=======================================================
OpenGL Information
GL_VENDOR: AMD
GL_RENDERER: AMD Radeon RX 6600 (navi23, LLVM 12.0.1, DRM 3.49, 6.1.15_1)
GL_VERSION: 4.6 (Compatibility Profile) Mesa 22.3.5
Surface Config: buf=32 r=8 g=8 b=8 a=8 depth=24 stencil=0 samples=0
Surface Size: 800x600 windowed
=======================================================
[build] use-vbo=false: FPS: 1041 FrameTime: 0.961 ms
[build] use-vbo=true: FPS: 1358 FrameTime: 0.737 ms
[texture] texture-filter=nearest: FPS: 1301 FrameTime: 0.769 ms
[texture] texture-filter=linear: FPS: 1303 FrameTime: 0.767 ms
[texture] texture-filter=mipmap: FPS: 1300 FrameTime: 0.770 ms
[shading] shading=gouraud: FPS: 1060 FrameTime: 0.944 ms
[shading] shading=blinn-phong-inf: FPS: 1082 FrameTime: 0.925 ms
[shading] shading=phong: FPS: 1296 FrameTime: 0.772 ms
[shading] shading=cel: FPS: 1294 FrameTime: 0.773 ms
[bump] bump-render=high-poly: FPS: 1300 FrameTime: 0.769 ms
[bump] bump-render=normals: FPS: 1300 FrameTime: 0.769 ms
[bump] bump-render=height: FPS: 1301 FrameTime: 0.769 ms
It works without any issues. In fact, the fans do not even start spinning because it’s not enough load … I guess I will try to run Unigine now to really check what this GPU is capable off.
Oh and also congratz to the Framework team! I connected my eGPU, rebooted and … that was it! I can use my external eGPU.
I’m interested in trying out Void Linux myself (currently using PopOS), but I’m not sure I understand how to apply the changes you made - but maybe with the continued open issues I should hold off for now.
I’m experiencing what seems like the same issue on the AMD Framework 13" DIY running Fedora 40. This has been difficult to diagnose* because the whole system freezes when the harddisk becomes read only.
Wondering if anyone could help me confirm this is the WD Black drive… If this is not the same issue described in this thread please let me know and I will create a separate issue.
* (For a long time I was having issues related to sleep/wake on AMD, confounding this issue. Then because of the non-responsiveness I thought I was running out of memory or something).
Disk Information: WD_BLACK SN770 250GB (731100WD) BTRFS/LUKS
Software Information:
Firmware Version: 03.05
OS Name: Fedora Linux 40 (Workstation Edition)
OS Build: (null)
OS Type: 64-bit
GNOME Version: 46
Windowing System: Wayland
Kernel Version: Linux 6.6.6-200.fc39.x86_64
Issue Description:
I’ll be using my computer as usual when suddenly it freezes up. Most typically I am in Firefox or VSCode. Usually an issue with the current application presents first** then within a few seconds the whole system freezes. This happens sometimes more than once per day, sometimes only every few days.
** (e.g. “Firefox is not responding” or VSCode cannot save the file because the disk is read only).
Usually It’s a total lockup. I cannot switch to a vterm. The computer is completely unresponsive and I must do a hard power off
Once I was able to leave dmesg --follow-new in an open terminal to catch the issue
