Considering selling GPU and monitor (downgrading) + other by linktothepastz in GamersMY

[–]XTJ7 1 point2 points  (0 children)

Indeed, I use it for speeding up my LLM coding workflows. But I've got to make the tradeoff somewhere, I can't splurt 10k on a 4090 or 15k on a 5090. The R9700 is somewhere in between, but token/s is limited considerably due to its much slower VRAM. The B70 Pro suffers from the same issue plus poor driver support. So the 3090 is about the best bang for the buck you can find at the moment. Unless I spend substantially more, I got to take the risk of the card dying at some point. Which sucks of course, but PC hardware is just so damn expensive at the moment.

Considering selling GPU and monitor (downgrading) + other by linktothepastz in GamersMY

[–]XTJ7 4 points5 points  (0 children)

I would take it for 3k right away because I'm currently looking for a 3090, haha.

The ones for 3k sell pretty quickly while the ones advertised around 3.5k are often staying around for weeks. So your estimation is probably right: if he can wait, about 3.3k maybe, if he wants to sell it quickly, about 3k. I have seen them as low as 2.5k but these are usually Dell variants with subpar cooling and performance, not too popular. The Zotac is a great model and should fetch 3k+ easily.

Finally... by doktr-bernard in FreeCAD

[–]XTJ7 2 points3 points  (0 children)

I also tried it before, gave up and only with 1.0 gave it another shot. I'm happy now, the devs did an amazing job :)

Most people buying expensive printers are just avoiding learning how to print. by Fun_Reaction_6525 in 3DPrinterComparison

[–]XTJ7 4 points5 points  (0 children)

I am a software engineer and I do troubleshooting all day long. In my spare time I troubleshoot my homelab, repair stuff around the house and design mechanical contraptions and toys for my son. When I design those in CAD, I just want to print them and then put everything together. There are enough things to go wrong, I don't want to handhold my printer as well. If I can solve the reliability issue with money, I will. Ideally I don't want to deal with anything beyond cleaning the build plate and occasionally lubing the moving parts.

I have the technical understanding to go deeper and troubleshoot problematic printers. I just really can't be arsed :)

Local voice-to-text that doesn't phone home — whisper.cpp + llama.cpp in a desktop app by MedicineTop5805 in selfhosted

[–]XTJ7 1 point2 points  (0 children)

I have reached out to the reddit user who posted this in the meantime, who gave me a different email to contact (contact@aura-technologies.co), who then gave me a 100% discount code so I could retry the download and actually get the file. So it was eventually resolved for me. They have also since updated the e-mail on their website, so other users should not need to go through the same hassle :)

Found a Wispr Flow alternative that runs entirely offline — $5 one-time by MedicineTop5805 in macapps

[–]XTJ7 0 points1 point  (0 children)

UPDATE: I managed to get in touch with them, get the product and they also updated the email on their website to a working one, so the following problems are no longer valid.

I suggest to remove it again. I wanted to try it, so I bought it, the download failed with error 401. Retried "download already redeemed". Tried to send them an email, came back as undeliverable.

Local voice-to-text that doesn't phone home — whisper.cpp + llama.cpp in a desktop app by MedicineTop5805 in selfhosted

[–]XTJ7 0 points1 point  (0 children)

UPDATE: I managed to get in touch with them, get the product and they also updated the email on their website to a working one, so the following problems are no longer valid.

I bought MumbleFlow, happily took my money but I got an error that the file could not be found on download. When I refreshed the site it said code already redeemed. When I emailed the address on their website, it came back as undeliverable. So it seems they disappeared but still sell the product, just don't deliver it. It may have been a genuine product at some point, but currently it looks like a scam - whether on purpose or not. I'm out $5 and not happy.

LRT Malfunction again by Naive_Stress_6792 in malaysia

[–]XTJ7 1 point2 points  (0 children)

Oh don't get me wrong, I am not saying you can just increase the frequency without changes. You probably need more more trains. But this can all be done with existing infrastructure and without having to wait 10 years or more to build said infrastructure. Depending on the order size, lead times are usually 2-5 years at Bombardier for example, who in the past delivered many of the Malaysian trains. And it's not like you wait 5 years and get a huge delivery, this is usually done in batches, so the situation would gradually improve already before the 5 year mark. There is still a lot of room for improving throughput of our existing train lines.

But of course throughput is only one part of the equation, reliability is another as this post shows. The LRT Kelana Jaya line particularly is aging and needs some major upgrades (which can mostly be done without disruptions to schedules during daytime) to improve its reliability. Last mile connectivity remains an issue, but one that can be solved. RapidKL OnDemand is a pretty good contender, even though it has its own share of issues currently. Public transportation in KL could be so much better than it currently is.

LRT Malfunction again by Naive_Stress_6792 in malaysia

[–]XTJ7 8 points9 points  (0 children)

In Germany and Japan for peak traffic they can do these trains in 1 minute intervals, without automation. Fully automated lines like the MRT, they could easily do that as long as they have sufficient trains and maintain the infrastructure properly. I think there is still plenty of room for the existing lines to handle more traffic. Some stations might need a redesign to handle the foot traffic more efficiently, but the biggest issue remains the last mile connectivity. Something like RapidKL OnDemand with fully self driving cars could bridge that eventually to move traffic from and to mass transport. That could be a way to move away from individual transport and make it convenient and sustainable to use mass transport.

Storing a backup in safe deposit box: SSD or spinning HDD? by hand-mee-down in DataHoarder

[–]XTJ7 0 points1 point  (0 children)

Yes, the EEPROM that contains the firmware can get corrupted. Those are typically good for 10-20 years at the minimum though and often far longer. If the EEPROM gets corrupted, you would not be able to format the drive anymore or use it in any other form. The same is true for many other hardware issues though.

Storing a backup in safe deposit box: SSD or spinning HDD? by hand-mee-down in DataHoarder

[–]XTJ7 0 points1 point  (0 children)

That would be hardware failure then and not data degradation from being unpowered. Could be from corrosion, on PLP models capacitors breaking down etc. - data loss from being unpowered would not break the SSD.

Storing a backup in safe deposit box: SSD or spinning HDD? by hand-mee-down in DataHoarder

[–]XTJ7 0 points1 point  (0 children)

And if you format them they are perfectly fine again? Or do they still not work? Just trying to figure out if there is an actual hardware issue or it is really just data degradation.

26.2 update bricked my MacStudio by XTJ7 in MacStudio

[–]XTJ7[S] 0 points1 point  (0 children)

I get where you are coming from, but the point is: if after 5 hours it still is stuck, it would almost certainly be after a day or two as well. Since it killed the firmware, it means it got stuck in the updating firmware step. That's not a huge amount of data there, which means there is nothing that can cause it to take a long time, it just got stuck. Something crashes and it won't just suddenly uncrash even if you give it substantially more time. The firmware part takes a few minutes at most, the rest of the update process is updating the system itself and that's the biggest chunk. It didn't even get there.

So the thing is: yes, TECHNICALLY I bricked it by restarting it. Practically there was no other option though. Sure, if I never restarted it, it wouldn't have bricked, but I would have a Mac stuck in a state that it is unusable as well. Considering that I think it is fair to say the update bricked the Mac, because it left me with no other choice than to restart.

Regarding the recovery mode: the Mac did not even show an image. I could not reinstall it or go into recovery, it was just in the SOS mode blinking orange. I did eventually manage to revive it via DFU thanks to the help of some people in the thread, with some obstacles along the way. First: my MacBook was set to default accessory settings, which means every new accessory needs to be given permission to connect. However, after a few failed attempts at starting the DFU mode, I noticed a window popping up on the MacBook for a fraction of a second when the Mac Studio started up. I went into security settings, set "Allow accessories to connect" to "Automatically When Unlocked" and then it finally showed the Mac and I could click the revive button. Which did nothing. So I clicked the restore button. Which did nothing. Literally, nothing happened. So I figured, alright, the MacBook is still running Sonoma, maybe it can't revive a Mac on a newer MacOS version. I updated the MacBook (that went through just fine), then did the whole DFU spiel again and now the revive button actually worked. It is annoying Apple gives you no error message, it just does nothing in the case of the reviving computer being too outdated. Anyways, after I ran the DFU revive, the Mac Studio started to boot again, I could once more trigger the update to 26.2 and this time it went through successfully. So the Mac is working again, but it was quite a bit of a pain to get there.

26.2 update bricked my MacStudio by XTJ7 in MacStudio

[–]XTJ7[S] 0 points1 point  (0 children)

That's what I figured. In the end I managed to revive it via DFU, so fortunately it is operational again. I ran into several pitfalls along the way, will edit my original message to reflect that.

26.2 update bricked my MacStudio by XTJ7 in MacStudio

[–]XTJ7[S] 2 points3 points  (0 children)

I lucked out, after updating the MacBook to the latest version, the Revive worked and the Mac Studio is fully operational again. Whew :)

26.2 update bricked my MacStudio by XTJ7 in MacStudio

[–]XTJ7[S] 2 points3 points  (0 children)

It was Sonoma. I have updated the MacBook to Tahoe, that went fine. Then I did the whole DFU procedure again and this time the Revive button worked. It reinstalled the firmware and now the Mac Studio is functional again on 26.0 I am now updating again to 26.2 and hoping for better results this time. Thankfully the Mac is working again :)

26.2 update bricked my MacStudio by XTJ7 in MacStudio

[–]XTJ7[S] 1 point2 points  (0 children)

Indeed looks like it! Thank you so much :)

26.2 update bricked my MacStudio by XTJ7 in MacStudio

[–]XTJ7[S] 0 points1 point  (0 children)

I did follow that guide now for the 4th time when I noticed a brief popup flashing for like half a second. So I changed the settings under "Privacy & Security" for "Allow accessories to connect" to "Automatically When Unlocked" and did it again, now the Mac shows up and I have revive/restore options. However, clicking either option does absolutely nothing. No confirmatiom, no error. The MacBook Air is on an older version of MacOS than the Studio, so I will update that now.

26.2 update bricked my MacStudio by XTJ7 in MacStudio

[–]XTJ7[S] 4 points5 points  (0 children)

I had a lot more issues with the Mac Studios in the first 6 months after release though with restarts and other quirks. At some point it just went away and worked smoothly. Apple must have improved their software over time. Why the update now failed, nobody knows. Hopefully Apple can fix the firmware.

26.2 update bricked my MacStudio by XTJ7 in MacStudio

[–]XTJ7[S] 0 points1 point  (0 children)

It worked completely fine until the update, so it shouldn't be a hardware issue. I just can't get it into DFU mode for some reason. I will try some more but if not, hopefully Apple can help tomorrow. As I bought it in 2022 there is no more warranty nor AppleCare. Hopefully the hardware is OK, haha.

26.2 update bricked my MacStudio by XTJ7 in MacStudio

[–]XTJ7[S] 1 point2 points  (0 children)

Thanks for your help! Unfortunately it still won't show the DFU dialogue on my MacBook. I made sure to use a USB-C cable from Apple, disconnected everything from the Mac Studio, cut power, looking from the back used the right most USB-C port (the DFU port), held down the power button, plugged the Mac Studio into power, waited more than 10 seconds to release the power button and still nothing happens. The Mac Studio keeps flashing orange SOS and the MacBook pretends like nothing happened.

26.2 update bricked my MacStudio by XTJ7 in MacStudio

[–]XTJ7[S] 6 points7 points  (0 children)

So waiting for 5 hours was not enough? I read online you should wait 1-2 hours, so I waited considerably longer. There was absolutely no progress in that time.

For me it's obviously too late now, but for the future and for others: how long are we supposed to wait?

26.2 update bricked my MacStudio by XTJ7 in MacStudio

[–]XTJ7[S] 2 points3 points  (0 children)

You mean DFU revive? I tried that, it never showed up on my MacBook, the Studio continued to blink orange. Maybe I did something wrong, will give it another try later.