Re: d-i on Firefly-rk3288

2016-12-20 Thread Diego Roversi
On Tue, 13 Dec 2016 00:29:05 +0100 Philip Hands wrote: > As I said, I'm pretty sure you just need to produce kernel udebs, and > dump them in the build/localudebs directory -- the thing that normally > trips me up is forgetting to bump the version so that the local udeb is > a higher version than

Re: u-boot fw_env for SD card based boot

2016-12-20 Thread Vagrant Cascadian
On 2016-12-20, Simon H wrote: > For me, the important variable is 'fdtfile', as I'm not currently > using the correct dtb for my device (because either it does not work, > or my device does not work! :), and so adjusting the boot parameters > could be important if I try to investigate the dtb. You

Re: u-boot fw_env for SD card based boot

2016-12-20 Thread Simon H
Thank you Vagrant, you are of course correct. I was searching the installed image for fdtfile=, and did not find it except inside the uboot binary (the default), but if i search for it after having used setenv in uboot, then I find the env section at 0x88000, before the FAT at 0x10. (I'm on uS

Re: cubox i4x4 hard drive seen in D-I but not in installed system.

2016-12-20 Thread peter green
On 20/12/16 12:50, Gunnar Wolf wrote: I have a CuBox-i 4 (not 4x4). It's currently in stable use, and have not fiddled with it for long (and right now, it sits 7000Km away from me), but if I recall correctly, any USB media needed for the boot process (i.e. a keyboard) has to be inserted in the l

Re: u-boot fw_env for SD card based boot

2016-12-20 Thread Vagrant Cascadian
On 2016-12-20, Simon H wrote: > Got Debian working nicely on an allwinner device with SD boot. > > The uboot variables seem to be stored in a file boot.scr in mmcblk0p1 > (or are they in /boot/boot.scr?) The u-boot environment is not typically stored in a file on allwinner/sunxi platforms, rather

Re: cubox i4x4 hard drive seen in D-I but not in installed system.

2016-12-20 Thread Gunnar Wolf
peter green dijo [Tue, Dec 13, 2016 at 10:05:12PM +]: > On 13/12/16 21:42, peter green wrote: > > > >I would guess at this point either a race condition or a power glitch > >(maybe powering the HDD off one of the USB ports wasn't such a good idea). > > > OK, I found that adding ahci-imx.hotplu

Re: u-boot fw_env for SD card based boot

2016-12-20 Thread Simon H
Actually I'm wrong about it reading the boot.scr file If I disable the failure on read, boot.scr does NOT contain a valid uboot environment set. Any ideas welcome On Tue, Dec 20, 2016 at 11:35 AM, Simon H wrote: > Hi all, > > Got Debian working nicely on an allwinner device with SD boot

u-boot fw_env for SD card based boot

2016-12-20 Thread Simon H
Hi all, Got Debian working nicely on an allwinner device with SD boot. The uboot variables seem to be stored in a file boot.scr in mmcblk0p1 (or are they in /boot/boot.scr?) Although the fw_env I have does seem to support the new style entry in fw_env.config : # VFAT example /mnt/dos/boot.scr

Re: armel after Stretch (was: Summary of the ARM ports BoF at DC16)

2016-12-20 Thread Christoph Biedl
Lennart Sorensen wrote... > I actually highly doubt there are that many armv7 boxes running armel. > armhf was a nice performance improvement and worth the hassle to reinstall > if you had such a box in the first place. I think most armel systems > are probably armv5, often the marvell chips. No

Re: armel after Stretch (was: Summary of the ARM ports BoF at DC16)

2016-12-20 Thread Wouter Verhelst
On Sat, Dec 17, 2016 at 08:15:15PM +0800, Paul Wise wrote: > On Sat, 2016-12-17 at 09:45 +0100, Wouter Verhelst wrote: > > > Yes, but that still says: > > Ack. > > > I think a proper procedure should involve a script that: > > > > - is packaged in Debian; > > Ack. > > > - checks whether the h