Bug#933971: linux-image-4.19.0-5-marvell: Kernel fails to parse mtdparts arg in cmdline. Impacts usage of fw_setenv on plug devices to config uboot.

On Mon, 2019-08-05 at 20:30 +0200, Evrard, Benjamin wrote: > It is indeed the same bug and the proposed workaround works fine. > > Still, I think that the choice of compiling the corresponding driver > as a module instead of embedding it in the kernel is a decision that > will impact many users

Bug#933971: linux-image-4.19.0-5-marvell: Kernel fails to parse mtdparts arg in cmdline. Impacts usage of fw_setenv on plug devices to config uboot.

It is indeed the same bug and the proposed workaround works fine. Still, I think that the choice of compiling the corresponding driver as a module instead of embedding it in the kernel is a decision that will impact many users when they upgrade their plug device from Debian Stretch to Buster.

Bug#933971: linux-image-4.19.0-5-marvell: Kernel fails to parse mtdparts arg in cmdline. Impacts usage of fw_setenv on plug devices to config uboot.

This appears to be the same as bug #931852, where you will find a workaround: . Ben. -- Ben Hutchings Beware of programmers who carry screwdrivers. - Leonard Brandwein signature.asc Description: This is a digitally signed message part

Bug#933971: linux-image-4.19.0-5-marvell: Kernel fails to parse mtdparts arg in cmdline. Impacts usage of fw_setenv on plug devices to config uboot.

Package: src:linux Version: 4.19.37-5 Severity: normal User: debian...@lists.debian.org Dear maintainer, After upgrading a Dockstar and a GoflexNet from Debian Stretch to Debian Buster, it becomes impossible to use the fw_setenv tool to update uboot settings on the device: # fw_setenv test 2