Am Samstag, den 07.01.2017, 23:12 +0100 schrieb Jonas Smedegaard: > Quoting permondes - sagen (2017-01-07 21:43:59) > > Am Samstag, den 07.01.2017, 15:01 -0500 schrieb James Valleroy: > > > > > On 01/07/2017 09:21 AM, permondes - sagen wrote: > > > > The currently running boot.scr with kernel 4.3: > > > > > > > >> ...:/boot$ cat boot.scr > > > >> 'V=�ѠV����#�Bi�setenv mmcdev 0 > > > >> 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.3.0-1-armmp-lpae > > > >> setenv initrd_file initrd.img-4.3.0-1-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} > > > > > > > > > > Maybe this will work, as a temporary workaround: > > > > > > Take the old boot.cmd (for kernel 4.3) and update it for kernel 4.8 > > > (just change the kernel_file and initrd_file to match the files in > > > /boot). Then you can produce a new boot.scr with the following: > > > > > > mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr > > > > > > We used to do this in freedom-maker, but we switched (last March) to > > > using flash-kernel to set up the boot script. > > > > Wonderful, James, I am in and on kernel 4.8.0-2. Now, to switch to using > > flash-kernel, should I reconfig this kernel? The system will do so with > > the next update anyway, I guess. > > If the dpkg-reconfigure command works then I doubt that next package > update will be any better. > > > > Also, I would like to remove the 4.3.0 and the 4.8.0-1 stuff. It does > > not appear in aptitude. I'd like to have more free space on /boot, just > > to be safe. > > Now that 4.8.0-2 boots (even if using manual hack) you can safely remove > 4.8.0-1 and 4.3.0.
My /boot is clean now, I will later-on give the reconfig of linux-image another trial. If that should cause the same issue again, I will put this aside for the moment and rather work on my LDAP issue. But now it's time to enjoy the hot temperatures (rose to -2 °C from -10) and the heavy snow we had last night. > > > - Jonas > Have a nice week-end Dietmar
_______________________________________________ Freedombox-discuss mailing list Freedombox-discuss@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss