[Freedombox-discuss] boot partition full

Jonas Smedegaard jonas at jones.dk
Sat Jan 7 14:42:22 UTC 2017


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 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}
> 
> 
> 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 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

Oh, your working script totally custom - not using any Debian skeleton. 
Then I think you are better off discussing further with Sunil or others 
closely familiar with how FreedomBox has strayed away from Debian. :-(


> Currently, none of the variables of this script is set (checked with
> printenv).

That sounds like a sensible check you did.  sorry it didn't produce 
clues...


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private



More information about the Freedombox-discuss mailing list