𝒍𝒆𝒎𝒂𝒏𝒏

Hey 👋 I’m Lemann: mark II

I like tech, bicycles, and nature.

Otherwise known as; @[email protected] and @[email protected]

Dancing Parrot wearing sunglasses

  • 7 Posts
  • 298 Comments
Joined 6 months ago
cake
Cake day: December 22nd, 2023

help-circle
  • ASMedia is the only controller IC manufacturer that can be trusted for these IME. They also have the best Linux support compared to the other options and support pass-through commands. These are commonly found in USB DAS enclosures, and a very small fraction of single disk SATA enclosures

    Innostor controllers max out at SATA 2 and lock up when you issue pass-through commands (e.g. to read SMART data). These also return an incorrect serial number. These are commonly found in ultra cheap desktop hard drive docks, and 40pin IDE/44pin IDE/SATA to USB converters

    JMicron controllers (not affiliated with the reputable Micron) should be avoided unless you know what you are doing… UASP is flaky, and there are hacky kernel boot time parameters required to get these working on Raspberry Pi boards. Unfortunately these are the most popular ones on the market due to very low cost





  • IIRC when looking into this originally, there are multiple tools necessary due to additional metadata on the MCs: mcpaste for PS1 saves, psupaste for PS2 saves, and the PS3 uses an entirely different format that needs to be converted prior to use (I don’t remember if you need to jailbreak to get the keys for this)

    Felt there was a bit too much manual stuff involved which could allow human error to come in and mess something up. I did do a copy + psupaste to the internal HDD on a new partition just in-case, but there was no way I was going to risk copying those back onto my only memory card to test if it actually was done right 😅

    The original MC was near full as well, so it’s pretty nice to also be able to spin up new ones when needed (to be fair I believe OPL has a similar feature built in, although some games may freeze using it)






  • Not the case with ARM processors sadly, IMO they’re a bit of a mess from that perspective. Proprietary blobs for hardware, unusual kernel hacks for some devices, and no device tree support so you can’t just boot any image on any device. I think Windows for ARM encouraged some standardization in that regard, but for the most part looking at Android devices it’s still very much the wild west.

    This is one of the many reasons why Raspberry Pi ARM boards remain popular for the time being, despite there being so many other cheap alternatives available: they actually keep supporting their old boards & ensure hardware on their boards works from the get-go.

    There are also some rare cases where Raspberry Pi rewrite open source implementations of Broadcom’s proprietary blob drivers, in one instance for the built in CSI (optional camera)


  • I wholeheartedly agree with this tbh. Love FreeCAD for my 3D printing stuff, pretty much use it daily, however compared to something like Solidworks or AutoCAD it would be torture IMO to willingly chose FreeCAD for a complex real world product.

    The biggest roadblock for FreeCAD right now is that is isn’t that forgiving, you often have to go into a “technical” way of thinking to work around its quirks. The reality is, designers want to design, not become technical experts at navigating FreeCAD.

    Even something like creating a thread shouldn’t be as involved as FreeCAD makes it - once you get used to it it’s OK, but in other CAD solutions it’s often as simple as clicking a hole and choosing a thread creation tool…