u/NoncarbonatedClack

Hi,

I'm on Fedora 44, Plasma 6.7.5.

My Nikon auto-mounts as a camera and I cannot unmount it. This prevents Darktable from being able to shoot tethered.

In settings -> disks & cameras -> digital camera, I'm unable to remove the device. the apply button does not work. If I remove the device, and try to go to device auto-mount or device actions, I'm prompted if I want to save pending changes. If I click yes, and come back to digital camera, it's mounted again.

How can I stop KDE from automounting the camera?

Mods, I hope this is ok, I'm totally lost at this point with my issue!

Here is the rig specs:

• CPU: AMD Ryzen 9 7950X
• MEM: G.Skill Trident Z5 2 x 32GB F5-6400J3239G32GX2-TZ5RW
• MOBO: MSI x670e godlike
• BIOS: 7D68v1L3
• VGA 1: PowerColor Radeon RX 7900 GRE
• VGA 2: AMD Radeon Pro W5500
• PSU: Corsair HX1000i
• NVMe drives:
• 2x SK Hynix P41 Platinum 1TB
• 1x SK Hynix P41 Platinum 2TB
• 1x Samsung 990 PRO 4TB

I've got a weird issue that popped up a while ago and seems to have gotten worse.. I can't do a warm reboot. Reboots result in being stuck at "00" for a post code, with the RAM LED light lit up on the diag LED. Cold boots work fine every time.

Resetting BIOS to defaults works. So, stock JEDEC speeds work fine as far as I can tell.

This presents when AMP/EXPO are enabled, or if I set manual RAM settings. I wasn't pushing any OC but was prepping to start some RAM OC. The reboot from the UEFI to save and apply settings also fails when any non-stock RAM settings are applied. If I leave everything at JEDEC speeds, I can change whatever I want in the UEFI and save + reboot works.

I am aware that this RAM kit is not on the QVL for this mobo, but that's never been an issue for me in 15+ years of building PCs. This issue also did not present for a couple months after buying this kit.

I'm posting here since I can't really find other examples of this issue elsewhere and I figured someone in r/overclocking might have seen this before. I'm hoping someone has some advice, otherwise I'm going to be bald by the time I figure this out.

What I've done:

• Updated to the latest BIOS (I was 3 revisions behind).
• Cleared CMOS with the button on the back of the mobo (done this at least 10 times).
• Unplugged the power from the machine, held the power button for 30 seconds, and let it sit unpowered for 24 hours (seen that one fix stranger things).
• Validated Stock vs EXPO/AMP/manual settings 5 times.
• Re-flashed the BIOS using the bios flashback button on the motherboard 2 times.
• Blown the RAM slots out with compressed air, reseating sticks.
• Swapped RAM slots.
• Adjusted CPU cooler mounting pressure.
• Ran 4 passes of memtest86+ on stock speeds, and 4 passes on EXPO, all passed.
• Tested to see if it's temperature dependent. Shut the machine down overnight, booted, and rebooted immediately, no change in the issue.
• Removed my mild CPU OC that's been stable for about a year.

What haven't done yet due to lack of time:

• Tested one stick at a time.
• Tested the power supply (tester is on the way).
• Swapped to the backup BIOS (much older version).
• Swapped any hardware, I don't have spares of any AM5/DDR5 hardware to do this.
• Bumped any voltages to see if this helps, I'm not up to speed on Ryzen 7000 voltages and what's what.
• Removed all other hardware except CPU and RAM.
• Used the voltage checkpoints on the board to check voltage.

I've been trying to figure out podman for a minute.. and I'm struggling. I'm coming from Docker, so I'm not totally new to containers. My plan is to start with running standalone containers, move to pods, and eventually quadlets.

All that aside, I can't find where the .container files (or anything config related) are stored. I've tried rootless, and now I'm running podman as root, I think, on Fedora server. I figured I'd have an easier time getting started by managing some containers with cockpit.. I've got a running container that's accessible, but I still can't find the config files.

I haven't confirmed if it's possible to have podman containers without sytemd untit files? I feel like it is possible but I'm not seeing much info there. Probably a search query issue.

I've checked these locations for systemd unit files (and probably others that I'm forgetting):

• /etc/containers/systemd/
• /usr/share/containers/systemd/
• $XDG_CONFIG_HOME/containers/systemd/
• ~/.config/containers/systemd/

Can someone please point me in the right direction, while I still have hair?

I purchased a Sigma 30mm ART lens, and I think I need to calibrate it. The focus seems slightly off when I'm relying on autofocus. I've got a Nikon D5600, which doesn't have any adjustment available in-body.

I purchased a vello calibration tool, but I didn't see any instructions related to how far away from the tool the lens needs to be. When looking online for information on how to calibrate a lens, I see that the distance between the lens and the calibration tool depends on the focal length of the lens.. but I can't figure out how to determine that.

Can someone point me in the right direction please?

I have a Nikon D5600 that NINA will not detect. I’m on windows 11, on a Microsoft Surface pro 7+. I’ve also tried this on a windows 11 virtual machine, on a different computer, to rule out an issue with the surface.

The computer detects the camera fine, and I’m able to control the camera with darktable using the same usb cable, so I don’t think it’s that.

• I have not installed any Nikon software.
• Windows was freshly installed on both the surface and VM.
• I installed the latest ASCOM platform, then installed NINA.
• my camera is supported by the NINA SDK, from what I can find.

I’ve seen some users that report their camera worked out of the box, and some that needed a 3rd party ASCOM driver. I’d like to avoid the 3rd party driver if possible.

What can I check next? I’ve looked through the NINA settings and don’t see anything obvious.