Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 1 Oct 2022 13:52:29 -0700
From:      Mark Millard <marklmi@yahoo.com>
To:        bob prohaska <fbsd@www.zefox.net>
Cc:        freebsd-arm <freebsd-arm@freebsd.org>, freebsd-uboot@freebsd.org
Subject:   Re: u-boot debug, was: Re: U-boot on RPI3, sees disk but won't boot it
Message-ID:  <6D8DF7FD-73E9-4DC1-9CC2-8B11F477C75E@yahoo.com>
In-Reply-To: <20221001184258.GB98055@www.zefox.net>
References:  <20220930002742.GA81169@www.zefox.net> <7A431698-1A8C-44BA-AFA2-EF5BAA69574F@googlemail.com> <924ED901-F9EB-4CFE-8376-1C2653FB6EBE@yahoo.com> <97AB11F6-2F4D-4026-8A96-50FC68B6EF8C@googlemail.com> <20220930214234.GA86711@www.zefox.net> <B25A7647-D109-48C9-AFDB-DE3F5AB08C56@yahoo.com> <20221001152242.GA97581@www.zefox.net> <51B729B0-3792-4870-9DEA-3E47F8BCB37F@yahoo.com> <20221001163323.GB97581@www.zefox.net> <D0FDFFBD-0582-4A5D-83C2-F7456944FD60@yahoo.com> <20221001184258.GB98055@www.zefox.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On 2022-Oct-1, at 11:42, bob prohaska <fbsd@www.zefox.net> wrote:

> On Sat, Oct 01, 2022 at 11:08:05AM -0700, Mark Millard wrote:
>> On 2022-Oct-1, at 09:33, bob prohaska <fbsd@www.zefox.net> wrote:
>>=20
>>=20
>>=20
>> I'll note that the:
>>=20
>> da0: <SABRENT  0214> Fixed Direct Access SPC-4 SCSI device
>> da0: Serial Number DD564198838F9
>>=20
>> does not match other log files:
>>=20
>> da0: <SABRENT  1214> Fixed Direct Access SPC-4 SCSI device
>> da0: Serial Number 000000000000A
>>=20
>> but it may well be an example of garbage-in/garbage-out.
>>=20
>=20
> If you're comparing past yesterday, probably not. I tried
> a different enclosure (same make/model) on the chance the
> first one was somehow damaged. There wasn't much difference
> in behavior, if anything it was a bit less likely to boot.
> For present purposes that seemed helpful so I kept it in place.
>=20
> Apologies for not mentioning it, I didn't think anybody=20
> would notice..... and then forgot.
>=20

Your two enclosures need not be strictly equivalent . . .

Original:

usb_msc_auto_quirk: UQ_MSC_NO_GETMAXLUN set for USB mass storage device =
JMicron SABRENT (0x152d:0x0583)
usb_msc_auto_quirk: UQ_MSC_NO_PREVENT_ALLOW set for USB mass storage =
device JMicron SABRENT (0x152d:0x0583)

Recent:

usb_msc_auto_quirk: UQ_MSC_NO_GETMAXLUN set for USB mass storage device =
JMicron USB Mass Storage (0x152d:0x0577)
usb_msc_auto_quirk: UQ_MSC_NO_PREVENT_ALLOW set for USB mass storage =
device JMicron USB Mass Storage (0x152d:0x0577)

So there is 0x0583 vs. 0x0577 for the product ID ( same vendor: 0x152d =
).

You will likely need to validate the behaviors of both.

=3D=3D=3D
Mark Millard
marklmi at yahoo.com




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6D8DF7FD-73E9-4DC1-9CC2-8B11F477C75E>