Bug#773991: flash-kernel: Fails when mtdblock kernel module isn't loaded

[Uwe Kleine-König <uwe+debian@kleine-koenig.org>]

Package: flash-kernel
Version: 3.28
Severity: normal

Hello,

on my ReadyNAS 104 (see database entry included below) a typical run
after a fresh reboot looks as follows:

	$ sudo flash-kernel 
	Installing armada-370-netgear-rn104.dtb into /boot/dtb-3.16.0-4-armmp
	Taking backup of dtb-3.16.0-4-armmp.
	Installing new dtb-3.16.0-4-armmp.
	flash-kernel: installing version 3.16.0-4-armmp
	/dev/mtdblock2 is not a block device

After

	$ sudo modprobe mtdblock

it works just fine. I wonder if flash-kernel should be smart enough to
load the module itself.

Best regards
Uwe

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: armhf (armv7l)

Kernel: Linux 3.16.0-4-armmp (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages flash-kernel depends on:
ii  debconf [debconf-2.0]  1.5.55
ii  devio                  1.2-1
ii  initramfs-tools        0.116
ii  linux-base             3.5
ii  ucf                    3.0030

flash-kernel recommends no packages.

Versions of packages flash-kernel suggests:
ii  u-boot-tools  2014.10+dfsg1-2

-- Configuration Files:
/etc/flash-kernel/db changed:
Machine: NETGEAR ReadyNAS 104
DTB-Id: armada-370-netgear-rn104.dtb
DTB-Append: yes
Mtd-Kernel: uImage
Mtd-Initrd: minirootfs
U-Boot-Kernel-Address: 0x04000000
U-Boot-Initrd-Address: 0x05000000
Required-Packages: u-boot-tools


-- debconf information excluded