Re: [Freedombox-discuss] boot partition full
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 0x4600
> > > >> setenv initrd_addr 0x4800
> > > >> setenv fdtaddr 0x4700
> > > >>
> > > >> setenv initrd_high 0x
> > > >> setenv fdt_high 0x
> > > >>
> > > >> 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
Re: [Freedombox-discuss] boot partition full
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 0x4600
> > >> setenv initrd_addr 0x4800
> > >> setenv fdtaddr 0x4700
> > >>
> > >> setenv initrd_high 0x
> > >> setenv fdt_high 0x
> > >>
> > >> 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.
- Jonas
--
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private
___
Freedombox-discuss mailing list
Freedombox-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
Re: [Freedombox-discuss] boot partition full
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 0x4600
> >> setenv initrd_addr 0x4800
> >> setenv fdtaddr 0x4700
> >>
> >> setenv initrd_high 0x
> >> setenv fdt_high 0x
> >>
> >> 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.
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.
Dietmar
>
>
> ___
> Freedombox-discuss mailing list
> Freedombox-discuss@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
___
Freedombox-discuss mailing list
Freedombox-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
Re: [Freedombox-discuss] boot partition full
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 0x4600
>> setenv initrd_addr 0x4800
>> setenv fdtaddr 0x4700
>>
>> setenv initrd_high 0x
>> setenv fdt_high 0x
>>
>> 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.
signature.asc
Description: OpenPGP digital signature
___
Freedombox-discuss mailing list
Freedombox-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
Re: [Freedombox-discuss] boot partition full
Quoting permondes - sagen (2017-01-07 15:21:36)
> Am Samstag, den 07.01.2017, 14:59 +0100 schrieb Jonas Smedegaard:
> > Quoting permondes - sagen (2017-01-07 14:31:34)
> > > Am Samstag, den 07.01.2017, 18:24 +0530 schrieb Sunil Mohan Adapa:
> > > > On 01/07/2017 06:17 PM, permondes - sagen wrote:
> > > > [...]
> > > > > But the device does not boot!
> > > > > I can unplug the micro-SD card to check some log files on my
> > > > > computer, do you have an idea where to start?
> > > >
> > > > Unfortunately, you won't have logs stored about this stage of booting.
> > > >
> > > > Check if you have uEnv.txt and move it to see if you are able to boot.
> > > >
> > > > To restore to earlier state, you can restore boot.scr files from backup.
> > > > (flash-kernel also takes a backup with the name boot.scr.bak)
> > > >
> > >
> > > I saved boot.scr and copied boot.scr.bak, so I am back in 4.3.0. I am
> > > glad that worked, because starting all over again (ikiwiki, radicale,
> > > privoxy, IRC) does not look too attractive to me.
> > > There was previously the issue with LDAP, where I could not add nor
> > > change users in Plinth anymore. I intended to approach that problem
> > > afterwards, did not think they are related.
> > >
> > > There is no file uEnv.txt in /boot, nothing similar to that.
> > >
> > > If you think, my system is totally screwed up and starting from scratch
> > > makes more sense, then I'll do that. Slowly, and probably taking
> > > tutorial videos, and lots of questions on how to recover (mostly)
> > > ikiwiki ;-). Please advice.
> >
> > I think your system is not totally screwed. Try share both working and
> > non-working boot.scr - they might indicate what configuration file might
> > be wrongly setup to now produce broken boot files.
>
> 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 0x4600
> > setenv initrd_addr 0x4800
> > setenv fdtaddr 0x4700
> >
> > setenv initrd_high 0x
> > setenv fdt_high 0x
> >
> > 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}
>
>
> The one for kernel 4.8, which did not start
>
>
> > ...:/boot$ cat boot.scr.480
> > 'V�or�Xp�Z _
> > C� boot script W# 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 0x4430 to allow for initrds larger than
> > # 13MB on u-boot-sunxi.
> > setenv kernel_addr_r 0x4200
> > setenv fdt_addr_r 0x4300
> > setenv ramdisk_addr_r 0x4430
> > fi
> >
> > if test -n "${console}"; then
> > setenv bootargs "${bootargs} console=${console}"
> > fi
> >
> > setenv bootargs ${bootargs} quiet
> >
> >
> > image_locati
Re: [Freedombox-discuss] boot partition full
Am Samstag, den 07.01.2017, 14:59 +0100 schrieb Jonas Smedegaard:
> Quoting permondes - sagen (2017-01-07 14:31:34)
> > Am Samstag, den 07.01.2017, 18:24 +0530 schrieb Sunil Mohan Adapa:
> >
> > > On 01/07/2017 06:17 PM, permondes - sagen wrote:
> > > [...]
> > > > But the device does not boot!
> > > > I can unplug the micro-SD card to check some log files on my computer,
> > > > do you have an idea where to start?
> > >
> > > Unfortunately, you won't have logs stored about this stage of booting.
> > >
> > > Check if you have uEnv.txt and move it to see if you are able to boot.
> > >
> > > To restore to earlier state, you can restore boot.scr files from backup.
> > > (flash-kernel also takes a backup with the name boot.scr.bak)
> > >
> >
> > I saved boot.scr and copied boot.scr.bak, so I am back in 4.3.0. I am
> > glad that worked, because starting all over again (ikiwiki, radicale,
> > privoxy, IRC) does not look too attractive to me.
> > There was previously the issue with LDAP, where I could not add nor
> > change users in Plinth anymore. I intended to approach that problem
> > afterwards, did not think they are related.
> >
> > There is no file uEnv.txt in /boot, nothing similar to that.
> >
> > If you think, my system is totally screwed up and starting from scratch
> > makes more sense, then I'll do that. Slowly, and probably taking
> > tutorial videos, and lots of questions on how to recover (mostly)
> > ikiwiki ;-). Please advice.
>
> I think your system is not totally screwed. Try share both working and
> non-working boot.scr - they might indicate what configuration file might
> be wrongly setup to now produce broken boot files.
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 0x4600
> setenv initrd_addr 0x4800
> setenv fdtaddr 0x4700
>
> setenv initrd_high 0x
> setenv fdt_high 0x
>
> 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}
The one for kernel 4.8, which did not start
> ...:/boot$ cat boot.scr.480
> 'V�or�Xp�Z _
> C� boot script W# 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 0x4430 to allow for initrds larger than
> # 13MB on u-boot-sunxi.
> setenv kernel_addr_r 0x4200
> setenv fdt_addr_r 0x4300
> setenv ramdisk_addr_r 0x4430
> 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 -
Re: [Freedombox-discuss] boot partition full
Quoting permondes - sagen (2017-01-07 14:31:34) > Am Samstag, den 07.01.2017, 18:24 +0530 schrieb Sunil Mohan Adapa: > > > On 01/07/2017 06:17 PM, permondes - sagen wrote: > > [...] > > > But the device does not boot! > > > I can unplug the micro-SD card to check some log files on my computer, do > > > you have an idea where to start? > > > > Unfortunately, you won't have logs stored about this stage of booting. > > > > Check if you have uEnv.txt and move it to see if you are able to boot. > > > > To restore to earlier state, you can restore boot.scr files from backup. > > (flash-kernel also takes a backup with the name boot.scr.bak) > > > > I saved boot.scr and copied boot.scr.bak, so I am back in 4.3.0. I am > glad that worked, because starting all over again (ikiwiki, radicale, > privoxy, IRC) does not look too attractive to me. > There was previously the issue with LDAP, where I could not add nor > change users in Plinth anymore. I intended to approach that problem > afterwards, did not think they are related. > > There is no file uEnv.txt in /boot, nothing similar to that. > > If you think, my system is totally screwed up and starting from scratch > makes more sense, then I'll do that. Slowly, and probably taking > tutorial videos, and lots of questions on how to recover (mostly) > ikiwiki ;-). Please advice. I think your system is not totally screwed. Try share both working and non-working boot.scr - they might indicate what configuration file might be wrongly setup to now produce broken boot files. > Sunil, does the Olinuxino A20 LIME (not LIME2!)run with amd64 as well? > Currently I use armhf No - LIME and LIME2 differ in (those binary parts in the top of) boot scripts, but both run the "armhf" flavor of Linux, and can only run the simpler "armel" flavor from same architecture family, not "amd64" wich is a modern flavor the _another_ computer architecture. Here is a bit of perspective that might help (I am 15 years into Linux too, and learned about multiple architectures with Apple machines): Debian hardware flavors, related to underlying hardware architectures: * "x86" family Intel/AMD hardware includes "i386" and "amd64". * "860x0" family Motorola hardware includes "m68k". * "PowerPC" family Apple/IBM hardware includes "powerpc" and "ppc64". * some family of ARM hardware includes "armel", "armhf" and "arm64". - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private ___ Freedombox-discuss mailing list Freedombox-discuss@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
Re: [Freedombox-discuss] boot partition full
Am Samstag, den 07.01.2017, 18:24 +0530 schrieb Sunil Mohan Adapa: > On 01/07/2017 06:17 PM, permondes - sagen wrote: > [...] > > But the device does not boot! > > I can unplug the micro-SD card to check some log files on my computer, do > > you have an idea where to start? > > Unfortunately, you won't have logs stored about this stage of booting. > > Check if you have uEnv.txt and move it to see if you are able to boot. > > To restore to earlier state, you can restore boot.scr files from backup. > (flash-kernel also takes a backup with the name boot.scr.bak) > I saved boot.scr and copied boot.scr.bak, so I am back in 4.3.0. I am glad that worked, because starting all over again (ikiwiki, radicale, privoxy, IRC) does not look too attractive to me. There was previously the issue with LDAP, where I could not add nor change users in Plinth anymore. I intended to approach that problem afterwards, did not think they are related. There is no file uEnv.txt in /boot, nothing similar to that. If you think, my system is totally screwed up and starting from scratch makes more sense, then I'll do that. Slowly, and probably taking tutorial videos, and lots of questions on how to recover (mostly) ikiwiki ;-). Please advice. Sunil, does the Olinuxino A20 LIME (not LIME2!)run with amd64 as well? Currently I use armhf Dietmar ___ Freedombox-discuss mailing list Freedombox-discuss@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
Re: [Freedombox-discuss] boot partition full
On 01/07/2017 06:17 PM, permondes - sagen wrote: [...] > But the device does not boot! > I can unplug the micro-SD card to check some log files on my computer, do you > have an idea where to start? Unfortunately, you won't have logs stored about this stage of booting. Check if you have uEnv.txt and move it to see if you are able to boot. To restore to earlier state, you can restore boot.scr files from backup. (flash-kernel also takes a backup with the name boot.scr.bak) -- Sunil signature.asc Description: OpenPGP digital signature ___ Freedombox-discuss mailing list Freedombox-discuss@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
Re: [Freedombox-discuss] boot partition full
Am Samstag, den 07.01.2017, 12:07 +0100 schrieb Jonas Smedegaard: > Quoting permondes - sagen (2017-01-07 10:39:28) > > Am Samstag, den 07.01.2017, 12:17 +0530 schrieb Sunil Mohan Adapa: > > > > > On 01/07/2017 05:43 AM, Jonas Smedegaard wrote: > > > [...] > > > >> So it is still booting the 4.3 kernel, which is unknown to aptitude. > > > > > > > > Seems your hardware is ARM-based. Commonly ARM-based hardware need the > > > > package flashkernel to copy installed kernel + initramfs to the > > > > different (hardware-specific) location where the bootloader looks for > > > > it. > > > > > > Indeed you need flash-kernel package. > > > > > > If you have boot.cmd instead of boot.scr and also don't have > > > flash-kernel package, you must upgrading and running a FreedomBox image > > > from many releases ago. > > > > > > To fix the situation, > > > > > > 1. Take backup of your SD card. > > > > > > 2. Make sure /boot is ext2fs and not vfat. > > > > > > 3. Install flash-kernel. This will create the proper /boot/boot.scr > > > file with a line like "setenv fk_kvers '4.8.0-2-armmp-lpae'". > > > > > > 4. Optionally set /etc/flash-kernel/machine to "Olimex > > > A20-OLinuXino-LIME2" (depending on your board). This should not be > > > required as flash-kernel will properly detect the machine when you are > > > running it from within the machine. > > > > > > 4. Move /boot/boot.cmd to /boot/boot.cmd.bak. > > > > > > 5. Reboot and check that boot happens properly. > > > > > > If you already have flash-kernel package and /boot/boot.scr, then simply > > > moving /boot/boot.cmd should fix the situation. > > > > > > > Thanks Jonas, Sunil. flash-kernel was indeed missing. However, > > installing, moving boot.cmd did not help, I am still in 4.3.0 (checked > > with uname -r), boot.cmd was not newly generated. I realize that the > > file boot.scr has some non-readable characters at the beginning, this > > was actually already the case before: > > > > > > > > > ...:/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 > > > ... > > > > Should I move also boot.scr, then reinstall flash-kernel and restart? > > When flash-kernel is installed, it have added a hook to the kernel > install routines, so instead of moving things around manually it should > be enough (and safer, and easier to debug) that you afterwards run > dpkg-reconfigure linux-image-4.8.0-2-armmp-lpae (adjust for the kernel > you want to reinstall). > > As for the stuff it beginning of the file: I believe it is opposite: the > compiled file as a convenience embeds the cleartext content too at the > end ;-) > > > - Jonas Hi Jonas, unfortunately, I am rather kind of the target user for the Freedombox, all these things are far beyond my knowledge of Linux - even though I celebrated my 10 years with Linux last summer. So the reconfig went through successfully (I think), here is the output: > ...:/boot$ sudo dpkg-reconfigure linux-image-4.8.0-2-armmp-lpae > > [sudo] Passwort für Dietmar: > > /etc/kernel/postinst.d/apt-auto-removal: > > N: Datei »50unattended-upgrades.ucf-dist« in Verzeichnis > »/etc/apt/apt.conf.d/« wird ignoriert, da sie eine ungültige > Dateinamen-Erweiterung hat. > > N: Datei »50unattended-upgrades.ucf-dist« in Verzeichnis > »/etc/apt/apt.conf.d/« wird ignoriert, da sie eine ungültige > Dateinamen-Erweiterung hat. > > N: Datei »50unattended-upgrades.ucf-dist« in Verzeichnis > »/etc/apt/apt.conf.d/« wird ignoriert, da sie eine ungültige > Dateinamen-Erweiterung hat. > > /etc/kernel/postinst.d/initramfs-tools: > > update-initramfs: Generating /boot/initrd.img-4.8.0-2-armmp-lpae > > DTB: sun7i-a20-olinuxino-lime.dtb > > Installing > /usr/lib/linux-image-4.8.0-2-armmp-lpae/sun7i-a20-olinuxino-lime.dtb into > /boot/dtbs/4.8.0-2-armmp-lpae/sun7i-a20-olinuxino-lime.dtb > > Installing new sun7i-a20-olinuxino-lime.dtb. > > Installing > /usr/lib/linux-image-4.8.0-2-armmp-lpae/sun7i-a20-olinuxino-lime.dtb into > /boot/dtbs/4.8.0-2-armmp-lpae/sun7i-a20-olinuxino-lime.dtb > > Taking backup of sun7i-a20-olinuxino-lime.dtb. > > Installing new sun7i-a20-olinuxino-lime.dtb. > > flash-kernel: deferring update (trigger activated) > > /etc/kernel/postinst.d/zz-flash-kernel: > > DTB: sun7i-a20-olinuxino-lime.dtb > > Installing > /usr/lib/linux-image-4.8.0-2-armmp-lpae/sun7i-a20-olinuxino-lime.dtb into > /boot/dtbs/4.8.0-2-armmp-lpae/sun7i-a20-olinuxino-lime.dtb > > Taking backup of sun7i-a20-olinuxino-lime.dtb. > > Installing new sun7i-a20-olinuxino-lime.dtb. > > Installing > /usr/lib/linux-image-4.8.0-2-armmp-lpae/sun7i-a20-olinuxino-lime.dtb in
Re: [Freedombox-discuss] boot partition full
On 01/07/2017 03:09 PM, permondes - sagen wrote: [...] > Thanks Jonas, Sunil. flash-kernel was indeed missing. However, > installing, moving boot.cmd did not help, I am still in 4.3.0 (checked > with uname -r), boot.cmd was not newly generated. I realize that the > file boot.scr has some non-readable characters at the beginning, this > was actually already the case before: > > >> ...:/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 >> ... > Should I move also boot.scr, then reinstall flash-kernel and restart? Looks like boot.scr was not regenerated after install flash-kernel. Jonas' command should take care of that. I was wrong about having to move boot.cmd. boot.scr is generated from boot.cmd. What I meant was /boot/uEnv.txt. If it is present, move it. uEnv.txt was used for booting earlier, but now boot.scr is used. -- Sunil signature.asc Description: OpenPGP digital signature ___ Freedombox-discuss mailing list Freedombox-discuss@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
Re: [Freedombox-discuss] boot partition full
Quoting permondes - sagen (2017-01-07 10:39:28) > Am Samstag, den 07.01.2017, 12:17 +0530 schrieb Sunil Mohan Adapa: > > > On 01/07/2017 05:43 AM, Jonas Smedegaard wrote: > > [...] > > >> So it is still booting the 4.3 kernel, which is unknown to aptitude. > > > > > > Seems your hardware is ARM-based. Commonly ARM-based hardware need the > > > package flashkernel to copy installed kernel + initramfs to the > > > different (hardware-specific) location where the bootloader looks for > > > it. > > > > Indeed you need flash-kernel package. > > > > If you have boot.cmd instead of boot.scr and also don't have > > flash-kernel package, you must upgrading and running a FreedomBox image > > from many releases ago. > > > > To fix the situation, > > > > 1. Take backup of your SD card. > > > > 2. Make sure /boot is ext2fs and not vfat. > > > > 3. Install flash-kernel. This will create the proper /boot/boot.scr > > file with a line like "setenv fk_kvers '4.8.0-2-armmp-lpae'". > > > > 4. Optionally set /etc/flash-kernel/machine to "Olimex > > A20-OLinuXino-LIME2" (depending on your board). This should not be > > required as flash-kernel will properly detect the machine when you are > > running it from within the machine. > > > > 4. Move /boot/boot.cmd to /boot/boot.cmd.bak. > > > > 5. Reboot and check that boot happens properly. > > > > If you already have flash-kernel package and /boot/boot.scr, then simply > > moving /boot/boot.cmd should fix the situation. > > > > Thanks Jonas, Sunil. flash-kernel was indeed missing. However, > installing, moving boot.cmd did not help, I am still in 4.3.0 (checked > with uname -r), boot.cmd was not newly generated. I realize that the > file boot.scr has some non-readable characters at the beginning, this > was actually already the case before: > > > > > ...:/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 > > ... > > Should I move also boot.scr, then reinstall flash-kernel and restart? When flash-kernel is installed, it have added a hook to the kernel install routines, so instead of moving things around manually it should be enough (and safer, and easier to debug) that you afterwards run dpkg-reconfigure linux-image-4.8.0-2-armmp-lpae (adjust for the kernel you want to reinstall). As for the stuff it beginning of the file: I believe it is opposite: the compiled file as a convenience embeds the cleartext content too at the end ;-) - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private ___ Freedombox-discuss mailing list Freedombox-discuss@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
Re: [Freedombox-discuss] boot partition full
Am Samstag, den 07.01.2017, 12:17 +0530 schrieb Sunil Mohan Adapa: > On 01/07/2017 05:43 AM, Jonas Smedegaard wrote: > [...] > >> So it is still booting the 4.3 kernel, which is unknown to aptitude. > > > > Seems your hardware is ARM-based. Commonly ARM-based hardware need the > > package flashkernel to copy installed kernel + initramfs to the > > different (hardware-specific) location where the bootloader looks for > > it. > > Indeed you need flash-kernel package. > > If you have boot.cmd instead of boot.scr and also don't have > flash-kernel package, you must upgrading and running a FreedomBox image > from many releases ago. > > To fix the situation, > > 1. Take backup of your SD card. > > 2. Make sure /boot is ext2fs and not vfat. > > 3. Install flash-kernel. This will create the proper /boot/boot.scr > file with a line like "setenv fk_kvers '4.8.0-2-armmp-lpae'". > > 4. Optionally set /etc/flash-kernel/machine to "Olimex > A20-OLinuXino-LIME2" (depending on your board). This should not be > required as flash-kernel will properly detect the machine when you are > running it from within the machine. > > 4. Move /boot/boot.cmd to /boot/boot.cmd.bak. > > 5. Reboot and check that boot happens properly. > > If you already have flash-kernel package and /boot/boot.scr, then simply > moving /boot/boot.cmd should fix the situation. > Thanks Jonas, Sunil. flash-kernel was indeed missing. However, installing, moving boot.cmd did not help, I am still in 4.3.0 (checked with uname -r), boot.cmd was not newly generated. I realize that the file boot.scr has some non-readable characters at the beginning, this was actually already the case before: > ...:/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 > ... Should I move also boot.scr, then reinstall flash-kernel and restart? Dietmar ___ Freedombox-discuss mailing list Freedombox-discuss@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
Re: [Freedombox-discuss] boot partition full
On 01/07/2017 05:43 AM, Jonas Smedegaard wrote: [...] >> So it is still booting the 4.3 kernel, which is unknown to aptitude. > > Seems your hardware is ARM-based. Commonly ARM-based hardware need the > package flashkernel to copy installed kernel + initramfs to the > different (hardware-specific) location where the bootloader looks for > it. Indeed you need flash-kernel package. If you have boot.cmd instead of boot.scr and also don't have flash-kernel package, you must upgrading and running a FreedomBox image from many releases ago. To fix the situation, 1. Take backup of your SD card. 2. Make sure /boot is ext2fs and not vfat. 3. Install flash-kernel. This will create the proper /boot/boot.scr file with a line like "setenv fk_kvers '4.8.0-2-armmp-lpae'". 4. Optionally set /etc/flash-kernel/machine to "Olimex A20-OLinuXino-LIME2" (depending on your board). This should not be required as flash-kernel will properly detect the machine when you are running it from within the machine. 4. Move /boot/boot.cmd to /boot/boot.cmd.bak. 5. Reboot and check that boot happens properly. If you already have flash-kernel package and /boot/boot.scr, then simply moving /boot/boot.cmd should fix the situation. -- Sunil signature.asc Description: OpenPGP digital signature ___ Freedombox-discuss mailing list Freedombox-discuss@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
Re: [Freedombox-discuss] boot partition full
Quoting permondes - sagen (2017-01-06 22:54:29) > Am Freitag, den 06.01.2017, 20:25 +0100 schrieb permondes - sagen: > > > Am Freitag, den 06.01.2017, 18:41 +0100 schrieb permondes - sagen: > > > > > Am Freitag, den 06.01.2017, 16:35 +0100 schrieb Petter > > > Reinholdtsen: > > > > > > > [permondes - sagen] > > > > > I think that with the kernel and initrd-updates the old version were > > > > > not > > > > > removed. Can I simply remove them with "rm"? Just keeping the latest > > > > > version? > > > > > > > > I would instead use 'dpkg -S /boot/v*' to identify packages to remove, > > > > and 'apt purge ' to remove them. > > > > > > > > > > I think the issue is related to the fact that I am still running > > > Linux 4.3.0-1-armmp-lpae, but also kernels 4.5, 4.6, 4.8 are loaded. > > > How do I make FreedomBox use the other kernels? A simple restart did > > > not help. > > > > I removed packages linux-image 4.5 and 4.7 and purged the conf files > > of 4.5, 4.6 and 4.7. Now I have again about 40 MB free space on boot. > > Apt did some configuration stuff with the 4.8 kernel, but after a > > restart, it booted again into 4.3. How can I make it understand to use > > the most recent kernel? > > Which kernels are you running? > > /boot/boot.cmd contains these 2 lines even after an > /etc/kernel/postinst.d/initramfs-tools: > update-initramfs: Generating /boot/initrd.img-4.8.0-2-armmp-lpae > > > > setenv kernel_file vmlinuz-4.3.0-1-armmp-lpae > > setenv initrd_file initrd.img-4.3.0-1-armmp-lpae > > So it is still booting the 4.3 kernel, which is unknown to aptitude. Seems your hardware is ARM-based. Commonly ARM-based hardware need the package flashkernel to copy installed kernel + initramfs to the different (hardware-specific) location where the bootloader looks for it. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private ___ Freedombox-discuss mailing list Freedombox-discuss@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
Re: [Freedombox-discuss] boot partition full
On 01/06/2017 12:41 PM, permondes - sagen wrote: > Am Freitag, den 06.01.2017, 16:35 +0100 schrieb Petter Reinholdtsen: >> [permondes - sagen] >> > I think that with the kernel and initrd-updates the old version >> were not >> > removed. Can I simply remove them with "rm"? Just keeping the latest >> > version? >> >> I would instead use 'dpkg -S /boot/v*' to identify packages to remove, >> and 'apt purge ' to remove them. >> > I think the issue is related to the fact that I am still running Linux > 4.3.0-1-armmp-lpae, but also kernels 4.5, 4.6, 4.8 are loaded. > How do I make FreedomBox use the other kernels? A simple restart did > not help. What hardware are you running on? signature.asc Description: OpenPGP digital signature ___ Freedombox-discuss mailing list Freedombox-discuss@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
Re: [Freedombox-discuss] boot partition full
Am Freitag, den 06.01.2017, 20:25 +0100 schrieb permondes - sagen: > Am Freitag, den 06.01.2017, 18:41 +0100 schrieb permondes - sagen: > > > Am Freitag, den 06.01.2017, 16:35 +0100 schrieb Petter > > Reinholdtsen: > > > > > [permondes - sagen] > > > > I think that with the kernel and initrd-updates the old version were not > > > > removed. Can I simply remove them with "rm"? Just keeping the latest > > > > version? > > > > > > I would instead use 'dpkg -S /boot/v*' to identify packages to remove, > > > and 'apt purge ' to remove them. > > > > > > > I think the issue is related to the fact that I am still running > > Linux 4.3.0-1-armmp-lpae, but also kernels 4.5, 4.6, 4.8 are loaded. > > How do I make FreedomBox use the other kernels? A simple restart did > > not help. > > I removed packages linux-image 4.5 and 4.7 and purged the conf files > of 4.5, 4.6 and 4.7. Now I have again about 40 MB free space on boot. > Apt did some configuration stuff with the 4.8 kernel, but after a > restart, it booted again into 4.3. How can I make it understand to use > the most recent kernel? > Which kernels are you running? /boot/boot.cmd contains these 2 lines even after an /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.8.0-2-armmp-lpae > setenv kernel_file vmlinuz-4.3.0-1-armmp-lpae > setenv initrd_file initrd.img-4.3.0-1-armmp-lpae So it is still booting the 4.3 kernel, which is unknown to aptitude. > ___ > Freedombox-discuss mailing list > Freedombox-discuss@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss ___ Freedombox-discuss mailing list Freedombox-discuss@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
Re: [Freedombox-discuss] boot partition full
Am Freitag, den 06.01.2017, 18:41 +0100 schrieb permondes - sagen: > Am Freitag, den 06.01.2017, 16:35 +0100 schrieb Petter Reinholdtsen: > > > [permondes - sagen] > > > I think that with the kernel and initrd-updates the old version were not > > > removed. Can I simply remove them with "rm"? Just keeping the latest > > > version? > > > > I would instead use 'dpkg -S /boot/v*' to identify packages to remove, > > and 'apt purge ' to remove them. > > > > I think the issue is related to the fact that I am still running Linux > 4.3.0-1-armmp-lpae, but also kernels 4.5, 4.6, 4.8 are loaded. > How do I make FreedomBox use the other kernels? A simple restart did > not help. I removed packages linux-image 4.5 and 4.7 and purged the conf files of 4.5, 4.6 and 4.7. Now I have again about 40 MB free space on boot. Apt did some configuration stuff with the 4.8 kernel, but after a restart, it booted again into 4.3. How can I make it understand to use the most recent kernel? Which kernels are you running? ___ Freedombox-discuss mailing list Freedombox-discuss@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
Re: [Freedombox-discuss] boot partition full
Am Freitag, den 06.01.2017, 16:35 +0100 schrieb Petter Reinholdtsen: > [permondes - sagen] > > I think that with the kernel and initrd-updates the old version were not > > removed. Can I simply remove them with "rm"? Just keeping the latest > > version? > > I would instead use 'dpkg -S /boot/v*' to identify packages to remove, > and 'apt purge ' to remove them. > I think the issue is related to the fact that I am still running Linux 4.3.0-1-armmp-lpae, but also kernels 4.5, 4.6, 4.8 are loaded. How do I make FreedomBox use the other kernels? A simple restart did not help. ___ Freedombox-discuss mailing list Freedombox-discuss@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
Re: [Freedombox-discuss] boot partition full
[permondes - sagen] > I think that with the kernel and initrd-updates the old version were not > removed. Can I simply remove them with "rm"? Just keeping the latest > version? I would instead use 'dpkg -S /boot/v*' to identify packages to remove, and 'apt purge ' to remove them. -- Happy hacking Petter Reinholdtsen ___ Freedombox-discuss mailing list Freedombox-discuss@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
