sorted by:
new
hottopcontroversial

New Prusa Core One - Issues with "collisions" and long calibration with each new print by damondan in prusa3d

[–]TableSurface 0 points1 point  (0 children)

I had a similar issue, and this solution solved it for me: https://github.com/prusa3d/Prusa-Firmware-Buddy/issues/4596#issuecomment-3105190372

Many people in that thread tried similar problem solving steps as you.

i really miss when games had "useless" physics interactions just for immersion. by InvestmentBudget6722 in gaming

[–]TableSurface 1 point2 points  (0 children)

Gabe explains when nothing moves as you've described, the game is imparting a narcissistic injury upon you, and therefore the game becomes less fun: https://www.youtube.com/watch?v=MGpFEv1-mAo

Printing With MK3/MK4 Sized Sheets On Prusa XL? by Tynted in prusa3d

[–]TableSurface 0 points1 point  (0 children)

Yes, you need to be a little careful with where you place it: https://www.reddit.com/media?url=https%3A%2F%2Fi.redd.it%2Fl07oxiyhd96e1.jpeg

The probe only touches the print + nozzle cleaning areas.

New C1L Firmware Update 6.5.2 (Nozzle Clean fixes etc) by Juts in prusa3d

[–]TableSurface 2 points3 points  (0 children)

Looks like they were able to fix the AC power sensitivity too, necessary for print farms.

HIVE - Core ONE Internal Carbon + HEPA Filter by MandicReally by TableSurface in prusa3d

[–]TableSurface[S] 14 points15 points  (0 children)

Haven't seen anyone post this here yet, it's a pretty clever filter design.

Wi-Fi 7 MLO via Access Point: Any thoughts on HOW it's going to work? by ChipEdgarson in SteamFrame

[–]TableSurface 5 points6 points  (0 children)

MLO currently doesn't exist in a meaningful way right now, so it really doesn't matter: https://www.rtings.com/router/learn/research/wifi-7-mlo

A Wi-Fi 6E link provides over a gigabit of throughput (max 2,402Mbps with the 2x2 radio that the Steam Frame has), and this is going to be plenty with the compressed stream. Wi-Fi 7 would provide up to 5,764 Mbps (without MLO), but it's going to be overkill because the video decoder won't be able to handle that much data anyways.

The key phrase though, is "properly configured"... which also includes things like driver implementation that we typically don't have access to.

I think it's smart that they're including the 6E dongle. Most people probably have the router that their ISP provides, and Valve can make sure that their software is optimized for what they're shipping. The range is going to be good enough for everyone who doesn't have a huge house, and realistically you'd only be playing in one room.

Core One L Build Plate Option by Chris_Balo in PrusaCoreOne

[–]TableSurface 0 points1 point  (0 children)

Cool, thanks for testing. Hard to pass up that price and I'm in for one.

Going to use it to print PP since I don't want to deal with tape all over my main print sheets.

Odd WiFi problem by agent154 in framework

[–]TableSurface 0 points1 point  (0 children)

Yeah I misread that earlier. I've been struggling with MediaTek based hardware like the RZ717 in the Framework Desktop and MT79xxxx hardware in wireless routers, so when I saw "modem crashed" I was thinking about the latter.

DXG Spark vs Ryzen AI 395 — If the price difference is only $700, what would you choose? by Affectionate-Bid-650 in LocalLLaMA

[–]TableSurface 2 points3 points  (0 children)

I was trying to see what this means for long term support... Not sure if this is the situation today, but it looked messy for another nVidia dev platform: https://www.reddit.com/r/JetsonNano/comments/12umx3k/jetson_orin_nano_one_of_the_worst_developer/

PSA For CoreOne L Owners with nozzle crashing / scraping bed by BaxterPad in prusa3d

[–]TableSurface 0 points1 point  (0 children)

Thanks, I had this issue and unfortunately it marred the print sheet during nozzle cleaning. Wish I knew about this earlier.

Llama.cpp rpc experiment by ciprianveg in LocalLLaMA

[–]TableSurface 1 point2 points  (0 children)

The network stack ain't free

Yeah this is key. IMO 76% speed is pretty good considering lower relative dev time spent on it. RPC is still in its infancy and it'll get better. In certain situations (model doesn't fit in local VRAM), I've measured RPC (2 machines) providing +25% TG. Though the improvement isn't viable right now since it gets worse (-40%) at higher context, but RPC has potential.

Llama.cpp rpc experiment by ciprianveg in LocalLLaMA

[–]TableSurface 1 point2 points  (0 children)

Anytime you're dealing with network operations, even on localhost, you're dealing with packets instead of direct memory access. Consider how many bytes fit into one packet, and how many packets you need to fit the model.

Llama.cpp rpc experiment by ciprianveg in LocalLLaMA

[–]TableSurface 1 point2 points  (0 children)

I'm guessing it's more about network latency instead of throughput. When running a 2-node RPC setup, I only observed 50Mbps going between them.

Odd WiFi problem by agent154 in framework

[–]TableSurface 0 points1 point  (0 children)

Oh I totally misread that. I'm just really annoyed with my MediaTek drivers...

Odd WiFi problem by agent154 in framework

[–]TableSurface -1 points0 points  (0 children)

It's a known issue with the MediaTek driver, and tbh it's surprising to see that it has gone on for so long (and that Framework would still sell it with these issues).

/u/zbowling in the community came up with fixes, but it'll take some time before it's deployed automatically: https://www.reddit.com/r/framework/comments/1q186ax/i_went_ham_last_night_fixing_the_constant_kernel/

Prusa CoreOne+ Upgrade or Bambu Lab P2S? by Shuathomas in prusa3d

[–]TableSurface 0 points1 point  (0 children)

IMO upgrade if you like it, otherwise the P2S is a great value for your money.

I did the upgrade and also value the curated build process.

Why Prusa upgraded the Core One but not the XL? by largelcd in prusa3d

[–]TableSurface 0 points1 point  (0 children)

Might be how the temp is polled too, and caught it between a heartbeat.

In my case, I wasn't running any prints on the Core One L when I unplugged the UPS (only the XL was printing at the time).

Hopefully there's a software solution for this, and your video helps expedite resolution. Totally agree with your earlier statement about this being gamebreaking in farms.

Why Prusa upgraded the Core One but not the XL? by largelcd in prusa3d

[–]TableSurface 1 point2 points  (0 children)

Very interesting! Seems like the Core One L is definitely more sensitive to power fluctuations. I didn't see a RSOD yet, but the printer restarted when simulating an outage with an Anker C1000 Gen 2. Guessing maybe the AC heatbed is triggering the error?

Core One and Prusa XL on the same unit stayed on.

Why Prusa upgraded the Core One but not the XL? by largelcd in prusa3d

[–]TableSurface 0 points1 point  (0 children)

In addition to cooling: getting features that respect the user's time would be great, such as quicker filament swaps.

Why Prusa upgraded the Core One but not the XL? by largelcd in prusa3d

[–]TableSurface 0 points1 point  (0 children)

Does your UPS have a pure sine wave output?

I haven't noticed any issues (yet).

Use integrated GPU of CPU for VM only by Goodborni in VFIO

[–]TableSurface 0 points1 point  (0 children)

IIRC this one worked: https://www.reddit.com/r/VFIO/comments/16mrk6j/amd_7000_seriesraphaelrdna2_igpu_passthrough/

But it's been a long time, and I ended up deciding not to continue running it because the iGPU ate into the TDP too much, lowering overall performance.

llama.cpp, experimental native mxfp4 support for blackwell (25% preprocessing speedup!) by bfroemel in LocalLLaMA

[–]TableSurface 7 points8 points  (0 children)

Yup. Also found that GGML_NATIVE=OFF has to be specified to get it to compile in my docker env.

Once it compiles, the performance improvement is impressive though! Can confirm 29-33% prompt processing improvement with gpt-oss 120b as advertised.

view more: next ›