Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: "Carlos E.R." Newsgroups: alt.os.linux,alt.comp.os.windows-11 Subject: Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) Date: Fri, 4 Apr 2025 11:36:55 +0200 Lines: 48 Message-ID: References: <7263clxr47.ln2@Telcontar.valinor> <4bm3clx6pp.ln2@Telcontar.valinor> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net 8XeSBvAfpMxcVQdM6XfFJgw9RJSFcbqC9h9NQB3cYxr5DUvMaa X-Orig-Path: Telcontar.valinor!not-for-mail Cancel-Lock: sha1:vUeky0HKM6NFypZvluOUI2970rY= sha256:AFsAV8QJyeNIAml+DQ94mb4OOqD3S/gsFWQXSXeCUXM= User-Agent: Mozilla Thunderbird Content-Language: es-ES, en-CA In-Reply-To: Xref: csiph.com alt.os.linux:81260 alt.comp.os.windows-11:18261 On 2025-04-04 05:33, Paul wrote: > On Thu, 4/3/2025 8:39 PM, Carlos E.R. wrote: >> On 2025-04-03 23:47, Paul wrote: >>> On Thu, 4/3/2025 4:01 PM, Carlos E.R. wrote: ... >> Sigh. >> >> >> So you think this is a firmware issue, and nothing can be done on the Linux side? >> > > It would seem "the underground" is distributing various firmwares for > this thing. Maybe the SPI bus really does have a firmware capability > to "fix" the stupid thing ? The architecture document isn't exactly honest > about this. > > jms578fwupdater.tgz 2,089,194 bytes > > JMS578FwUpdate 4,130,828 bytes > > I guess that means some of the devices, have a 4MB SPI flash chip. > and that's where the firmware is stored or something. THis could be > a small 8 pin DIP near the JMB578 on the circuit board. > > I don't like to quote "sources" for things like this, unless > there is some sort of traceability for them. > > The firmware may have been written by JMicron, but JMicron are > not likely to be serving the file like a RealTek might. > > And since it's a flasher-firmware thing, the OS firmware support > is not of the same delivery type (some devices accept dynamic > firmware which is stored in device RAM). This would be a firmware > that is stored in an outboard chip from the JMS578. It fixes issue > such as TRIM, UASP diaablement, proper support of power saving, > and so on. > > The work you are doing, is similar to the work an enclosure > engineer might do, before shipping this project. Each user > apparently expected to "sweep the web", "look for bootleg firmware", > "install" and "hope for the best". A science project. That's out of my league :-( -- Cheers, Carlos.