I just replied to someone else below with regards to the drive checks. I could also go ask on the arch forums, or maybe in some irc chats if theres people actually in there

As I mentioned replying to @just_another_person@lemmy.world, my root partition is on an NVME which is not even 3 years old yet, and I have not had any other problems with it apart from discord, so I don't think its a drive failure issue, but better safe rather than sorry, so if you'd be so kind as to let me know how you'd like me to test/verify its health I'd appreciate it :)

Is it possible that the read-only error occurs because the directory its trying to write to doesn't exist (/opt/discord/resources/app.asar/node_modules/electron-log/src/core/ doesnt exist)? It may be a stupid question but as I said I've no idea how node works so consider me as having the intelligence of a rock when it comes to it

$ ls -lh /opt
total 36K
drwxr-xr-x 7 root root 4.0K Nov 24 15:04 app1
drwx--x--x 4 root root 4.0K Aug 15 16:43 containerd
drwxr-xr-x 4 root root 4.0K Nov 25 17:00 discord
drwxr-xr-x 5 root root 4.0K Nov 24 15:04 app2
drwxr-xr-x 4 root root 4.0K Feb 25  2025 app3
drwxr-xr-x 6 root root 4.0K Nov 24 15:04 app4
drwxrwxrwx 6 root root 4.0K Nov 25 17:00 app5
drwxr-xr-x 4 root root 4.0K Mar 20  2025 texlive
drwxr-xr-x 4 root root 4.0K Jun  4 00:59 app6

$ ls -lh /opt/discord
total 216M
-rw-r--r-- 1 root root 164K Nov 25 00:11 chrome_100_percent.pak
-rw-r--r-- 1 root root 254K Nov 25 00:11 chrome_200_percent.pak
-rwxr-xr-x 1 root root 1.5M Nov 25 00:11 chrome_crashpad_handler
-rwsr-xr-x 1 root root  15K Nov 25 00:11 chrome-sandbox
-rwxr-xr-x 1 root root 182M Nov 25 00:11 Discord
-rw-r--r-- 1 root root  299 Nov 25 00:11 discord.desktop
-rw-r--r-- 1 root root 6.9K Nov 25 00:11 discord.png
-rw-r--r-- 1 root root  10M Nov 25 00:11 icudtl.dat
-rw-r--r-- 1 root root 247K Nov 25 00:11 libEGL.so
-rw-r--r-- 1 root root 3.9M Nov 25 00:11 libffmpeg.so
-rw-r--r-- 1 root root 6.2M Nov 25 00:11 libGLESv2.so
-rw-r--r-- 1 root root 4.6M Nov 25 00:11 libvk_swiftshader.so
-rw-r--r-- 1 root root 600K Nov 25 00:11 libvulkan.so.1
drwxr-xr-x 2 root root 4.0K Nov 25 17:00 locales
drwxr-xr-x 3 root root 4.0K Nov 25 17:00 resources
-rw-r--r-- 1 root root 5.8M Nov 25 00:11 resources.pak
-rw-r--r-- 1 root root 333K Nov 25 00:11 snapshot_blob.bin
-rw-r--r-- 1 root root 702K Nov 25 00:11 v8_context_snapshot.bin
-rw-r--r-- 1 root root  107 Nov 25 00:11 vk_swiftshader_icd.json

As for the drive, my root partition is on an NVME drive which should be fine considering its not even 3 years old.

What info does this give you? As someone more experienced, what jumps out at you when looking at this (trying to improve my knowledge while troubleshooting - 2 for the price of 1 xD)

Well i hardly expect the pope to be a smoker

These 2 boards are part of my circuit, which I want to move from my breadboard to a PCB, so I need a way to attach these boards to the PCB. Due to the fact that I want the ability to re-use these boards in other projects, and also not have them stick up from the PCB vertically, I decided to go with right-angled headers so that I have both of these features (easy plugging in/unplugging of the boards from the final PCB, and a more compact final design).

However since they will need to hang over some degree you need to look at the 2d drawing and make sure the right angle header pins are long enough to mate to the matching component on the board.

By this do you mean I need to make sure the pins on the boards will fit in the hole of the headers? I was under the impression that pin length is quite standard, much like pin separation. I believe mine are 2.54 mm because they fit nicely in my arduino headers, as well as the breadboard. I'd assume the length is also standardised. Please correct me if Im wrong.

If you are sending the board out to be made at a shop you will need to define these features and tolerances in the manufacturing layer that will export as part of the gerber file and possibly provide a 2d drawing.

By this I assume you mean that I need to make sure the boards will clear any other components on the PCB? I've been getting through this playlist: https://www.youtube.com/watch?v=ZHH4G_EWhm0&list=PL3bNyZYHcRSUhUXUt51W6nKvxx2ORvUQB&index=4&t=2s

as I go through each step of the process. When he gets to the point about designing the PCB I'll see if he mentions how to make sure I have enough clearance for all my components, otherwise I guess I'll look for other videos explaining how to do this.

A few guys at my work actually just asled us what we wanted from the cafeteriawhen we were doing long fixes on their laptops (I work in a uni)

I've got it set up like that. In my NIC section, under device model, the selected option is e1000e, but still no eth0 interface or anything other than lo and sit0

Edit: unless I misunderstood and that's not enough to use the e1000 driver

I want to avoid flatpacks, and I dont want to have to use it just for steam and nothing else.

Nope, I dont.

Please elaborate?

I can't stand the smell of garlic to the point of retching if I do. Just the thought of it makes me unwell. It's a long story, why I'm like this xD

Heres a recipe: https://cypruspassion.net/elies-tsakistes-coriander-crushed-olives-recipe/