Your message dated Tue, 17 Jan 2017 21:59:29 +0100 with message-id <[email protected]> and subject line Re: Bug#851469: flash-kernel: ARM new boot.scr does not allow the device to boot has caused the Debian Bug report #851469, regarding flash-kernel: ARM new boot.scr does not allow the device to boot to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 851469: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851469 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: flash-kernel Version: 3.73 Severity: important Dear Maintainer, I am using an OLinuXino A20 LIME with arm. boot.scr used to have the following content (I removed the initial non-readable characters) which let boot the device without issues: setenv mmcpart 1 setenv mmcroot /dev/mmcblk0p2 ro setenv mmcrootfstype btrfs rootwait fixrtc setenv mmcrootflags subvol=@ setenv console ttyS0,115200n8 setenv kernel_file vmlinuz-4.8.0-2-armmp-lpae setenv initrd_file initrd.img-4.8.0-2-armmp-lpae setenv fdtfile sun7i-a20-olinuxino-lime.dtb setenv loadaddr 0x46000000 setenv initrd_addr 0x48000000 setenv fdtaddr 0x47000000 setenv initrd_high 0xffffffff setenv fdt_high 0xffffffff setenv loadkernel load mmc ${mmcdev}:${mmcpart} ${loadaddr} ${kernel_file} setenv loadinitrd load mmc ${mmcdev}:${mmcpart} ${initrd_addr} ${initrd_file}\; setenv initrd_size \${filesize} setenv loadfdt load mmc ${mmcdev}:${mmcpart} ${fdtaddr} /dtbs/${fdtfile} setenv loadfiles run loadkernel\; run loadinitrd\; run loadfdt setenv mmcargs setenv bootargs console=${console} root=${mmcroot} rootfstype=${mmcrootfstype} rootflags=${mmcrootflags} run loadfiles; run mmcargs; bootz ${loadaddr} ${initrd_addr}: ${initrd_size} ${fdtaddr} <-- end of file The new content of that file is: # boot script for Allwinner SunXi-based devices # Mainline u-boot v2014.10 introduces a new default environment and # a new common bootcmd handling for all platforms, which is not fully # compatible with the old-style environment used by u-boot-sunxi. # This script therefore needs to check in which environment it # is running and set some variables accordingly. # On u-boot-sunxi, this script assumes that ${device} and ${partition} # are set. # The new-style environment predefines ${boot_targets}, the old-style # environment does not. if test -n "${boot_targets}" then echo "Mainline u-boot / new-style environment detected." # Mainline u-boot v2014.10 uses ${devtype}, ${devnum} and # ${bootpart} where u-boot-sunxi uses ${device} and ${partition}. # ${distro_bootpart} replaced ${bootpart} in u-boot v2016.01. if test -z "${device}"; then setenv device "${devtype}"; fi if test -z "${partition}${distro_bootpart}"; then setenv partition "${devnum}:${bootpart}"; fi if test -z "${partition}"; then setenv partition "${devnum}: ${distro_bootpart}"; fi else echo "U-boot-sunxi / old-style environment detected." # U-boot-sunxi does not predefine kernel_addr_r, fdt_addr_r and # ramdisk_addr_r, so they have to be manually set. Use the values # from mainline u-boot v2014.10, except for ramdisk_addr_r, # which is set to 0x44300000 to allow for initrds larger than # 13MB on u-boot-sunxi. setenv kernel_addr_r 0x42000000 setenv fdt_addr_r 0x43000000 setenv ramdisk_addr_r 0x44300000 fi if test -n "${console}"; then setenv bootargs "${bootargs} console=${console}" fi setenv bootargs ${bootargs} quiet image_locations='/boot/ /' if test -z "${fk_kvers}"; then setenv fk_kvers '4.8.0-2-armmp-lpae' fi if test -n "${fdtfile}"; then setenv fdtpath dtbs/${fk_kvers}/${fdtfile} else setenv fdtpath dtb-${fk_kvers} fi for pathprefix in ${image_locations} do if test -e ${device} ${partition} ${pathprefix}vmlinuz-${fk_kvers} then load ${device} ${partition} ${kernel_addr_r} ${pathprefix}vmlinuz-${fk_kvers} \ && load ${device} ${partition} ${fdt_addr_r} ${pathprefix}${fdtpath} \ && load ${device} ${partition} ${ramdisk_addr_r} ${pathprefix}initrd.img-${fk_kvers} \ && echo "Booting Debian ${fk_kvers} from ${device} ${partition}..." \ && bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r} fi done <- end of file Which does not allow the device to boot. None of the variables in that script is set in the current environment. As work-around I am currently copying a saved version of the former file content to boot.scr. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: armhf (armv7l) Kernel: Linux 4.8.0-2-armmp-lpae (SMP w/2 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (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.59 ii devio 1.2-1.2 ii initramfs-tools 0.126 ii linux-base 4.5 ii mtd-utils 1:2.0.0-1 ii ucf 3.0036 Versions of packages flash-kernel recommends: ii u-boot-tools 2016.11+dfsg1-3 flash-kernel suggests no packages. -- debconf information: flash-kernel/linux_cmdline: quiet Dietmar
--- End Message ---
--- Begin Message ---On Tue, Jan 17, 2017 at 07:41:20PM +0100, permondes - sagen wrote: > Am Montag, den 16.01.2017, 21:41 +0100 schrieb Karsten Merker: > > > > Shall we keep the bug against flash-kernel open or shall we close > > it? If the former, I would tag it "moreinfo" as we effectively > > cannot solve the issue without further information about what > > exactly happens during the boot process on your system. > > > > Regards, > > Karsten > > Please close the bug. I will try to get a fw_env.config or set up a new > system. The issue is probably Freedombox related and working on it does > not advance this project. > Thanks a lot for your support. > > Dietmar Closing the bug as requested above. Regards, Karsten -- Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich der Nutzung sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der Werbung sowie der Markt- oder Meinungsforschung.
--- End Message ---
