Date: Wed, 22 Dec 2021 09:35:14 -0800 From: bob prohaska <fbsd@www.zefox.net> To: Mark Millard <marklmi@yahoo.com> Cc: freebsd-arm@freebsd.org Subject: Re: ld: error: bzlib.pico:147: unclosed quote Message-ID: <20211222173514.GA93415@www.zefox.net> In-Reply-To: <17ED22E1-E08E-47FF-85A7-16DA8303C8A3@yahoo.com> References: <20211221180041.GA29679@www.zefox.net> <0E4548B1-B8F6-45D8-AB30-634E47511688@yahoo.com> <4349F44D-C77B-44DD-9A96-0E8C4E7EA046@yahoo.com> <20211222040334.GB30154@www.zefox.net> <17ED22E1-E08E-47FF-85A7-16DA8303C8A3@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Dec 21, 2021 at 08:14:58PM -0800, Mark Millard wrote: > On 2021-Dec-21, at 20:03, bob prohaska <fbsd@www.zefox.net> wrote: > > > On Tue, Dec 21, 2021 at 05:51:59PM -0800, Mark Millard wrote: > > Not noise? Which adapter was in use during the corruption? > Does this mean that you have showed 2 disks to have issues > using the same adapter on the same RPi3* (but with different > firmware/U-Boot/Loader/kernel/World's on the 2 disks)? > No, I don't think so. I expected the enumeration problem to move with the disks. Instead neither disk enumerated readily when moved. The disks have different bridge chips. > Whatever the details, such would be good information to > know. I've been offered a Windows 7 machine that can be used to apply the Sabrent firmware updater. That seems like the obvious thing to try next in light of the error reported on the Pi3: Read NVMe Identify Controller failed: scsi error unsupported field in scsi command No clue if it'll help, but it's a relatively easy experiment. The observations will be added to http://www.zefox.net/~fbsd/slow_usb_notes I'll try to keep them somewhat more coherent if others are trying to follow the story. Thanks for your help and attention! bob prohaska
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20211222173514.GA93415>