On 2024-01-12 13:32, Vagrant Cascadian wrote: > On 2024-01-12, Vagrant Cascadian wrote: > > On 2024-01-12, Vagrant Cascadian wrote: > >> On 2024-01-12, Michael Fladischer wrote: > >>> I was able to boot my Hifive Unmatched Rev B board via SPI from NVME with > >>> u-boot-sifive-2023.07+dfsg-1. After upgrading to 2024.01+dfsg-1 u-boot is > >>> no > >>> longer able to see any NVME drives: > > ... > >> I am getting this too. I had tested with a local build of > >> 2024.01~rc6-1~0 and that worked fine, so I am a bit surprised as none of > >> the very few commits between v2024.01-rc6 and v2024.01 seem relevent. > > > > I should also note that I am testing with u-boot on microSD, so it is > > not specific to u-boot from SPI. > > > >> I also wonder about opensbi, which was fairly recently upgraded, > >> although I *thought* I tested opensbi 1.4-1 with the ~rc6 build I had > >> done... > > > > I verified u-boot-sifive 2024.01~rc6+dfsg-2 (formerly in experimental) > > works, which was built with the same opensbi version. In fact, the only > > difference in the installed build-dependencies were perl related: > > > > - libperl5.36 (= 5.36.0-10+b1), > > + libperl5.38 (= 5.38.2-2), > > - perl (= 5.36.0-10+b1), > > - perl-base (= 5.36.0-10+b1), > > - perl-modules-5.36 (= 5.36.0-10), > > + perl (= 5.38.2-2), > > + perl-base (= 5.38.2-2), > > + perl-modules-5.38 (= 5.38.2-2), > > > > I am attempting a local rebuild, will see how that goes... > > Well, rebuilding and just adding a new debian/changelog > entry... worked. both from a reboot and from a cold start. > > That does not leave much to investigate, so is a bit worrying, but > perhaps a binNMU would "fix" it?
I tried to do a build from the sources using sbuild, and I ended up with exactly the same binaries, so unfortunately I doubt a binNMU would fix it. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://aurel32.net
signature.asc
Description: PGP signature
