Re: u-boot debug, was: Re: U-boot on RPI3, sees disk but won't boot it
Mark Millard <[email protected]>
| Newsgroups | gmane.os.freebsd.devel.arm |
|---|---|
| Message-ID | <[email protected]> |
On 2022-Oct-1, at 11:42, bob prohaska <[email protected]> wrote: > On Sat, Oct 01, 2022 at 11:08:05AM -0700, Mark Millard wrote: >> On 2022-Oct-1, at 09:33, bob prohaska <[email protected]> wrote: >> >> >> >> I'll note that the: >> >> da0: <SABRENT 0214> Fixed Direct Access SPC-4 SCSI device >> da0: Serial Number DD564198838F9 >> >> does not match other log files: >> >> da0: <SABRENT 1214> Fixed Direct Access SPC-4 SCSI device >> da0: Serial Number 000000000000A >> >> but it may well be an example of garbage-in/garbage-out. >> > > 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. > > Apologies for not mentioning it, I didn't think anybody > would notice..... and then forgot. > 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. === Mark Millard marklmi at yahoo.com