you have faulty hardware, whether it’s RAM or cooling or storage related, no way to tell but crashes like that don’t happen nowadays.
edit: I recall having some issues with a 7490 a few years back, it needed some special module for the fan or the sensors, not sure. don’t know if that’s your issue, but look it up.
I think you mistyped the model, if it’s a 7390 it should be the same hardware as the 7490 I’ve mentioned. the module I needed was i8k, check if your model needs it.
The RAM is fine (Memtest ran 4 times without faults), and cooling seems to work well enough. Storage is ok and I used two different SSDs through this whole process and saw the same problems on both.
I tried the previous known-good kernel options on the Manjaro install and it seems to be OK now. According to the Arch Wiki the Intel 8th Gen mobile CPUs and especially iGPUs are known to be a little problematic on Linux so the kernel options to disable some power saving options are basically non-optional. It’s weird though that it works now and didn’t on the Tumbleweed reinstall.
I have an issue involving similar hardware, can you share the mandatory stuff for 8th gen iGPUs? read through the intel_graphics article but found no direct mention.
I linked the specific wiki page section in an edit to the main post. It’s in the troubleshooting part at the end.
I didn’t try the i8k module but looking at a couple things it looks like the issue was more apparent around Linux kernel 4.15 from a few years ago. I also don’t have any specific complaints with temperature control. The fans only ramp up in the 70-80C range which seems to be quite reasonable.
I used to use the command line, Bash, Awk, Sed, Cut, Grep, and Find (often piped to one another) quite often. I can recall that the few times I used Awk was usually for collating lines from logs or CSV files.
But then I switched to using Emacs as my editor, and it gathers together the functionality of all of those tools into one, nice, neat little bundle of APIs that you can easily program in the Emacs Lisp programming language, either as code or by recording keystrokes as a “macro.”
Now I don’t use shell pipelines hardly at all anymore. Mostly I run a process, buffer its output, and edit it interactively. I first edit by hand, then record a macro once I know what I want to do, then apply the macro to every line of the buffer. After that, I might save the buffer to a file, or maybe stream it to another process, recapturing its output. This technique is much more interactive, with the ability to undo mistakes, and so it is easier to manipulate data than with Awk and shell pipelines.
This is fascinating to me. Do you have any links or suggestions for this workflow to learn more?
I am glad you asked, because I actually wrote a series of blog posts on the topic of how Emacs replaced my old Tmux+Bash CLI-based workflow. The link there is to the introductory article, in the “contents” section there are links to each of the 4 articles in the series. The “Shell Basics” (titled “Emacs as a Shell”) might be of particular interest to you.
If you have any specific questions, or if you have recommendations for something you think you would like to learn from one of my blog posts, please let me know. I would like to write a few more entries in this blog series.
Are you using Firefox within a flatpak perchance ?
There seems to be a bug to it relating to use of bitmap fonts, you can fix the issue by disabling them via a config file in firefox’s fonts: bugzilla.mozilla.org/show_bug.cgi?id=1621915
I have a similar problem, but on Lemmy.zip (Lemmy.world looks fine). However, I am running Fedora Kinoite (immutable), where Firefox is not installed as Flatpak.
I don’t give a flying fuck about anything NT. They have more changes to that book than there are letters in it.
Don’t get me wrong, I don’t take the OT with any literality either but at least they didn’t make edits like that so there really is some attribution that can be handed to the writers back in the day. Notably, that they actually wrote that. I don’t really go any further than that though.
Do you know how we have knowledge of that level of accuracy in what we can read today?
Also, that, because I do have zero belief in anything, ever. That’s like paying donating to a guy to rape your kids. Literally.
“that thing you used to do is now impossible to do consistently across different implementations, if at all. But it’s all ok, because we have decided it’s not our responsibility!”
That is not what users want to hear. From a user’s point of view, it is broken.
I see what you’re getting at. It’s a matter of perspective, I guess.
If you presented someone with a list of features from two similar but different pieces of software, they wouldn’t say software b is broken because it’s featureset is different from software a, right? But I acknowledge it’s not that straightforward. It’s more like telling them software b is going to replace software a that you’re currently using, get ready to say goodbye to some features.
I still don’t consider wayland broken, but I understand argument that it is.
yes, if i combare kicad with blender, neither is broken because they have different features. But also, nobody is telling users that kicad’s days are over and it should be replaced by blender. If they did, and a user wanted to design a circuit board, the user is out of luck. The user is told that it is a replacement. From the user’s point of view it most definitely is not.
The probeem isn’t just that wayland doesn’t do everything x does. But that users are told that it will replace x, deal with it and quit complaining.
We have to keep in mind that the fact that we know what wayland is in the first place puts us squarely into the “technical user” category, not regular users. Regular users are the ones who don’t even know (nor should they have to care) what wayland even is
Been on Wayland since 2016 and to this day my only issues (apart from when I had an Nvidia card for a few months, that is…) was video sharing in Discord/steam in-home streaming, both of which still don’t work right.
Other than that, it’s been great. Multi-monitor works way better, far fewer bugs, my desktop feels a lot more fluid and smooth.
On laptops, Wayland+Gnome gestures are exceptional, putting even Apple’s gestures to shame. I cannot stress enough how good of a job Gnome+Wayland does with trackpad gestures. It makes other gesture systems, especially ones under X11, feel like they were cobbled together by a Fallout 3 modder.
Overall Wayland has been great for me. I just wish Discord would fix their shitty app.
There are still a number of clock sync issues with the Zen4 chips. I’ve had issues on 6.4/5/6 with similar sounding audio/video that I’ve been able to somewhat mitigate by getting my amd_pstate settings to stop competing with other power tuning tools. Turn off EVERYTHING you have running dealing with cpufreq management, and just let the kernel amd_pstate do it’s thing. No TLP, no desktop tuning tools, just the upstate.
Also, double check that your memory frequencies aren’t bouncing all over the place, and consider under locking in the BIOS to exactly match the channel freq for CPU/mem.
I believe the only power tuning I had was cpupower. I just stopped it and will give it some time. Do you know a tool that’ll graph out my memory frequency? My memory seems pretty stable at 4800 MHz but I’ll watch it with “watch lshw -short -C memory”
This is the big thing that all these Nvidia comments miss. It’s not up to Wayland to support a given GPU. Nvidia is actively hostile to Linux users. If you aren’t making money with cuda there are zero reasons to choose Nvidia on a Linux machine over the competition. I’ve been on Wayland for almost a decade now and there’s no way I’m going back to X at this point.
FWIW, I’m typing this on the latest GNOME, on wayland, on nvidia proprietary drivers; and it works just fine — EXCEPT for suspend & resume, which is annoying to be sure; but on 2 screens with different refresh rates & different dpi ratios I at least don’t run into some of the weird behavior I do run into using X11.
I used to be an Xfce purist; but this particular setup is even less taxing on the GPU (GTX 970) compared to Xfce’s standard compositor (around 20W on light usage, vs. 35+W); & and the font rendering is slighly better, which is a huge factor AFAIC.
Well we’ve had binary packages for ages for big builds like firerox and default is still to use source packages.
Still I’m really excited for this, having the whole, or big parts of the package tree, will speed up initial installations by a lot on weak arm systems for example. Now initial installation can be done quick and later you could still compile stuff yourself for the full gentoo experience.
linux
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.