sigmoid.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A social space for people researching, working with, or just interested in AI!

Server stats:

588
active users

#troubleshooting

5 posts5 participants0 posts today

something is eating my RAM and it's pretty stealthy.
My used memory is about double of what it should be according to process usage. This is with #linux 6.16, gnome, browser and mailer running.

If I start a VM with 16 GB allocation, it runs into #OOM pretty quickly. If I start said VM with 12 GB, it also OOMs, just slower. Stealth usage increases there otherwise it wouldn't run OOM.

Found this promising thread but it's not this unix.stackexchange.com/questio

any idea?

Hey 3d printing friendos! I'm having some issues with resin printing, and curious if fedi would be able to assist!

So my Mars Pro seems to be in mostly working order. I can print minis with great detail still, and seem to get no failures when auto-generating "medium" sized supports with Lychee. That said, I've been trying to use provided pre-supported files, in hope of nicer details from smaller support sizes.

So, the problem -

On some surfaces, I'm noticing that a chunk of the model almost gets "torn away" from the supports during printing. It's happened on a few different models, so i'm more inclined to think a setting or parameter change on the printer might help?

Does this sort of thing look familiar to anyone? Are there any obvious settings on my Printer that I should try changing?

(Thanks for taking the time and reading, peeps. <3 )

I need help troubleshooting my network simulation. This simulation simulates simple network with a router and a client (both are jails). The router provides internet to client 1 through netgraph.

Setup:
1. Host-Router (Epair)
2. Router-Bridge-Client1 (NetGraph)

What were working:
1. Router can ping 1.1.1.1 (Internet Access)
2. Router can ping host gateway (192.168.200.1)
3. Router can ping client 1 (192.168.150.10)
4. Client 1 can ping the router (192.168.150.1)

What were not working:
1. Client 1 cannot ping 192.168.200.1
2. Client 1 cannot ping 1.1.1.1

What I have done:
1. Enabled gateway_enable in rc.conf
2. Configured all forwarding in sysctl
3. Create default route to 192.168.200.1

Garden Troubleshooting

My radishes did a weird thing. By seed packet info, they should have been ready last week, but they were still a long, reddish root.

Today, I pull them out and got this. They never swelled into orbs, just stayed long. And now they taste very astringent.

Anyone else have this happen and have a possible reason?

ETA: Seems like heat is a probable culprit, we've had a few 85+F days. Not a summer crop - lesson learned!

Just spent five hours troubleshooting my home network - tried everything from checking cables to reconfiguring routers and switches. Turned out the fix was the classic: turn it off and back on again.

Honestly, the ultimate IT hack never gets old. 😂

Lesson learned: patience and persistence pay off, but sometimes it’s the simplest solution that wins.

Anyone else have those epic “wasted hours for a reboot” stories? Share ‘em!

Replied in thread

@NVAccess I'll include this link in the issue but here is another example as far as chrome is concerned where the graphic raps and control down arrow does not appear to work 100 percent of the time.
salesforceben.com/practical-ex
unless I'm doing something wrong which could be the case.
#NVDA #Troubleshooting

Salesforce Ben · 5+ Practical Examples of Salesforce Case FormulasBy Tom M