<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/4.8.5">
</HEAD>
<BODY>
Am Samstag, den 07.01.2017, 15:01 -0500 schrieb James Valleroy:
<BLOCKQUOTE TYPE=CITE>
<PRE>
On 01/07/2017 09:21 AM, permondes - sagen wrote:
<FONT COLOR="#737373">> The currently running boot.scr with kernel 4.3:</FONT>
<FONT COLOR="#737373">></FONT>
<FONT COLOR="#737373">>> ...:/boot$ cat boot.scr</FONT>
<FONT COLOR="#737373">>> 'V=�ѠV����#�Bi�setenv mmcdev 0</FONT>
<FONT COLOR="#737373">>> setenv mmcpart 1</FONT>
<FONT COLOR="#737373">>></FONT>
<FONT COLOR="#737373">>> setenv mmcroot /dev/mmcblk0p2 ro</FONT>
<FONT COLOR="#737373">>> setenv mmcrootfstype btrfs rootwait fixrtc</FONT>
<FONT COLOR="#737373">>> setenv mmcrootflags subvol=@</FONT>
<FONT COLOR="#737373">>></FONT>
<FONT COLOR="#737373">>> setenv console ttyS0,115200n8</FONT>
<FONT COLOR="#737373">>></FONT>
<FONT COLOR="#737373">>> setenv kernel_file vmlinuz-4.3.0-1-armmp-lpae</FONT>
<FONT COLOR="#737373">>> setenv initrd_file initrd.img-4.3.0-1-armmp-lpae</FONT>
<FONT COLOR="#737373">>> setenv fdtfile sun7i-a20-olinuxino-lime.dtb</FONT>
<FONT COLOR="#737373">>></FONT>
<FONT COLOR="#737373">>> setenv loadaddr 0x46000000</FONT>
<FONT COLOR="#737373">>> setenv initrd_addr 0x48000000</FONT>
<FONT COLOR="#737373">>> setenv fdtaddr 0x47000000</FONT>
<FONT COLOR="#737373">>></FONT>
<FONT COLOR="#737373">>> setenv initrd_high 0xffffffff</FONT>
<FONT COLOR="#737373">>> setenv fdt_high 0xffffffff</FONT>
<FONT COLOR="#737373">>></FONT>
<FONT COLOR="#737373">>> setenv loadkernel load mmc ${mmcdev}:${mmcpart} ${loadaddr} ${kernel_file}</FONT>
<FONT COLOR="#737373">>> setenv loadinitrd load mmc ${mmcdev}:${mmcpart} ${initrd_addr} ${initrd_file}\; setenv initrd_size \${filesize}</FONT>
<FONT COLOR="#737373">>> setenv loadfdt load mmc ${mmcdev}:${mmcpart} ${fdtaddr} /dtbs/${fdtfile}</FONT>
<FONT COLOR="#737373">>></FONT>
<FONT COLOR="#737373">>> setenv loadfiles run loadkernel\; run loadinitrd\; run loadfdt</FONT>
<FONT COLOR="#737373">>> setenv mmcargs setenv bootargs console=${console} root=${mmcroot} rootfstype=${mmcrootfstype} rootflags=${mmcrootflags}</FONT>
<FONT COLOR="#737373">>></FONT>
<FONT COLOR="#737373">>> run loadfiles; run mmcargs; bootz ${loadaddr} ${initrd_addr}:${initrd_size} ${fdtaddr}</FONT>
<FONT COLOR="#737373">></FONT>
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.
</PRE>
</BLOCKQUOTE>
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.<BR>
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.<BR>
<BR>
Dietmar
<BLOCKQUOTE TYPE=CITE>
<PRE>
_______________________________________________
Freedombox-discuss mailing list
<A HREF="mailto:Freedombox-discuss@lists.alioth.debian.org">Freedombox-discuss@lists.alioth.debian.org</A>
<A HREF="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss</A>
</PRE>
</BLOCKQUOTE>
</BODY>
</HTML>