On Thu, Mar 23, 2017 at 11:04 PM, Val Lorentz <prog...@progval.net> wrote:
> > > On 23/03/2017 22:42, Michael Stapelberg wrote: > > • The space is intentional. This is how the option is parsed. > > Why is it an equal sign for other options, but not for this one? > Don’t ask me :). This is just how the proprietary firmware works. > > > • The preview image referenced at https://wiki.debian.org/RaspberryPi3 > boots > > for me. Are you using the preview image? > > No, because I prefer to limit the number of binary downloads outside > Debian's repo. > So instead I'm writing my own build script based on > https://github.com/niklasf/build-raspbian-image Not sure I understand the reasoning. You’re maintaining a build script (which isn’t packaged in Debian, I assume) so that you don’t have to use the result of our build script (which aims to be packaged in Debian eventually)? > > > > Are you using it on a Raspberry Pi 3 (no other version is supported)? > > Yes. > > > The raspi3-firmware package is supposed to be used with the preview > image. > > Is there anything in the preview image that is not available in a Debian > package in the official repos? > Most of the files in https://people.debian.org/~stapelberg/raspberrypi3/2017-03-22/ are not yet packaged (but will eventually be), so yes. > > > • You’re reporting a bug against an older version of the firmware > package. > > Why? The latest 2017-03-22 preview image uses the 1.20170317-3 firmware > > package. > > The version in Debian's repos is 1.20161123-2, and I can't find > 1.20170317-3 anywhere > (https://packages.debian.org/experimental/raspi3-firmware is a 404). > The package hasn’t been built yet, if I interpret https://buildd.debian.org/status/package.php?p=raspi3-firmware&suite=experimental correctly. You can get a pre-built version from https://people.debian.org/~stapelberg/raspberrypi3/2017-03-22/, or build one yourself (the source is in experimental). > > However, bootcode.bin, fixup*.dat, and start*.elf are installed using > https://github.com/Hexxeh/rpi-update after raspi3-firmware, so the issue > may come from them being are newer than those in raspi3-firmware. > > I will try soon to build an image without rpi-update and tell you what > happens. > Better yet: try comparing the boot partition contents of the preview image and your result. I can’t spend too much time on non-supported configurations, so any step you take to diagnosing this issue will result in a higher chance of it actually getting fixed. -- Best regards, Michael
