Bug#899092: flash-kernel: Marvell 8040 MACCHIATOBin

On 2018-05-18, Heinrich Schuchardt wrote: > In the Linux kernel the model property has been changed to add an extra > 'C': > 8f667425f979 ("arm64: dts: marvell: mcbin: fix board name typo") > > To allow a safe upgrade the best solution is to duplicate the db entry. Since there's no difference

Bug#690210: Bug 690210 : debootstrap : debian-ports support

On 2018-04-17, Hideki Yamane wrote: > control: tags -1 +pending > > On Sat, 27 May 2017 11:27:06 +0200 jhcha54008 wrote: >> I am testing the updated ([1],[2]) version attached of a >> debootstrap script to accomodate the peculiarities of non >>

Bug#732551: make --foreign / qemu-user-static easier

On 2013-12-18, Joey Hess wrote: > If debootstrap installed qemu-user-static into the chroot > when --foreign was used, it could then immediately chroot in > and run commands (assuming the host system has binfmt-support > installed). > > This would allow debootstrap to go ahead

Bug#895700: installation-reports: Pinebook success with custom kernel

Package: installation-reports Severity: normal Pinebook install mostly worked, though required an updated 4.16 kernel with a custom device-tree, and a custom u-boot build. As some of that gets mainlined, this might actually be a workable arm64 laptop soon! live well, vagrant --

Bug#877467: Odroid-XU4: success despite several challenges

Package: installation-reports Followup-For: Bug #877467 Tested same model board with a newer debian-installer and buster, and this install went a bit easier(mostly due to USB being fixed in the current kernels), but still had many of the same problems. Modules needed to detect the ethernet

Bug#894059: installation-reports: rock64, difficult install

Package: installation-reports Severity: normal A bit of a rough install, despite eventual success... It required manually creating the boot media, appending all kernel modules to the initrd, using a device-tree from a newer kernel version, and installing u-boot-menu to have a working boot menu,

Re: Build regression on armhf

On 2018-03-21, Cyril Brulebois wrote: > We're getting an FTBFS on armhf following your recent changes: ... > | open header: No such file or directory at util/grub-gencfg line 175. > | config/arm.cfg:35: recipe for target 'arch_miniiso' failed > | make[2]: *** [arch_miniiso] Error

Bug#893154: #893154: installation-reports: pine64+ difficult install

On 2018-03-16, Vagrant Cascadian wrote: > I'm looking into enabling EFI emulation in u-boot to allow this > part to "just work" with the current grub-EFI images. I built a new version of u-boot with EFI emulation support enabled, and successfully booted the mini.iso, but still h

Bug#893154: installation-reports: pine64+ difficult install

Package: installation-reports Severity: normal This install, while successful, was a bit of a challenge. I had to manually create the boot media, customize the initrd to append additional kernel modules, and the microSD wasn't available to install the OS. More details below. live well, vagrant

Bug#892405: installation-reports: Theobroma Systems RK3399-Q7 SoM, partial success

Package: installation-reports Severity: normal Install required manual installation of firmware, boot loader, device-tree and initial boot configuration, but otherwise went mostly ok. Some of that will be fixed in upcoming u-boot and flash-kernel uploads. The install ran very slow, as cpu

Bug#884003: FDT overlay support

On 2017-12-12, Andre Heider wrote: > Subject: [PATCH 06/10] beaglebone: clean up boot script > > Use $fk_image_locations and distro compatible variable names, get rid > of the duplicated code from bootscr.uboot-generic, and use that script > additionally instead. > > Signed-off-by: Andre Heider

Bug#884003: FDT overlay support

On 2018-01-20, Vagrant Cascadian wrote: > On 2017-12-12, Andre Heider wrote: >> Subject: [PATCH 05/10] bootscr.uboot-generic: support multiple prefixes to >> load from >> Subject: [PATCH 06/10] beaglebone: clean up boot script > > I might try to rework 5-6 with a

Bug#884003: FDT overlay support

On 2017-12-12, Andre Heider wrote: > I added the ability to concatenate multiple scripts/snippets for the > final boot script. > Subject: [PATCH 01/10] bootscr.uboot-generic: quote bootargs > Subject: [PATCH 02/10] Allow compiling scripts from $tmpdir > Subject: [PATCH 03/10] Add support for

Bug#807709: Use blkid / handle PARTLABEL= and PARTUUID for root device

On 2015-12-11, Martin Michlmayr wrote: > Package: flash-kernel > Version: 3.52 > > I noticed these two patches: > > https://lists.debian.org/debian-kernel/2015/12/msg00167.html > https://lists.debian.org/debian-kernel/2015/12/msg00168.html > > flash-kernel probably needs a similar change, or

Bug#849532: flash-kernel does not remove dtb backups

On 2017-01-02, Martin Michlmayr wrote: > * Heinrich Schuchardt [2016-12-28 10:10]: >> The .bak file should not be created on the first install of a Linux kernel. > > Yeah, that's a separate issue but it's definitely something I noticed > too. The DTB handling code is run

Bug#860304: flash-kernel: Incorrect installation path for dtbs

Control: tags 860304 pending On 2017-09-20, Vagrant Cascadian wrote: > On 2017-08-27, Heinrich Schuchardt wrote: >> On 08/25/2017 05:31 PM, Vagrant Cascadian wrote: >>> On 2017-08-24, Heinrich Schuchardt wrote: >>>> is there really any need to keep /boot/dtbs/VERSIO

Bug#887803: flash-kernel: Machines without Kernel-Flavors do not generate boot.scr

Control: tags 887803 pending On 2018-01-19, Vagrant Cascadian wrote: > Version 3.90 of flash-kernel does not generate a boot.scr: ... > Apparently the code I added to attempt to allow the ability to specify > "any" kernel flavor to fix #883547 ... broke machines that do n

Bug#887803: flash-kernel: Machines without Kernel-Flavors do not generate boot.scr

Package: flash-kernel Severity: important Version: 3.90 Version 3.90 of flash-kernel does not generate a boot.scr: $ sudo flash-kernel Using DTB: armada-3720-espressobin.dtb Installing /usr/lib/linux-image-4.14.0-2-arm64/marvell/armada-3720-espressobin.dtb into

Bug#876773: flash-kernel: Please add support for the original SolidRun CuBox (Dove)

Control: tags 876773 pending On 2017-09-26, Josua Mayer wrote: > Am 25.09.2017 um 21:22 schrieb Vagrant Cascadian: >> On 2017-09-25, Josua Mayer wrote: >>> The SolidRun CuBox has very good support in Mainline Linux. >>> Thus it is a great candidate for supporting it i

Bug#871792: flash-kernel: please add support for Golden Delicious GTA04 phone

On 2017-08-11, Josua Mayer wrote: > Please add support for above mentioned phone. > Since debian armmp kernel 4.9.13-1 the board is reasonably well supported, > though charging isn't working, which is why I use a custom kernel here. > > It comes with a downstream u-boot variant based on 2016.11.

Bug#839595: flash-kernel: Please add support for SolidRun Clearfog

Control: tags 839595 pending Pushed a commit to git: https://anonscm.debian.org/git/d-i/flash-kernel.git/commit/?id=175f11c79927fbc9527f5cce1bdfd2ad60d3ed50 Should be included in the next upload. live well, vagrant signature.asc Description: PGP signature

Bug#824954: Bug#873390: [PATCH] flash-kernel: Provide hook to start EFI application

Control: tags 873390 pending On 2017-08-27, Heinrich Schuchardt wrote: > Instead of starting the Linux kernel from U-Boot we may want to > start an EFI application like grub or iPXE. Let us use a new > hook @@UBOOT_PREBOOT_EXTRA@@ in the boot.scr generation for this > purpose. The related hook

Bug#864525: flash-kernel: fails on fat32

Control: tags 864525 wontfix On 2017-06-10, Ian Campbell wrote: > On Sat, 2017-06-10 at 02:41 +0200, Heinrich Schuchardt wrote: >> On 06/10/2017 02:11 AM, Ben Hutchings wrote: >> > On Sat, 2017-06-10 at 00:59 +0200, Heinrich Schuchardt wrote: >> >> On 06/10/2017 12:31 AM, Martin Michlmayr wrote:

Bug#884375: bootscr.cubox-i

On 2018-01-13, Rainer Dorsch wrote: > wouldn't bootscr.cubox-i benefit from the same modification (?): Sure. > since it uses the same SoC (imx6), it needs the same cma bootarg: > > https://wiki.debian.org/InstallingDebianOn/Wandboard#cma Committed to git:

Bug#887670: installation-reports: Espressobin required workarounds

On 2018-01-18, Vagrant Cascadian wrote: > Ethernet interface appeared to detect, but could not get a DHCP > address. Used a USB-ethernet adapter as a workaround. A workaround appears to be to manually run "ip link set eth0 up" and then use the "wan" interface; the

Bug#887670: installation-reports: Espressobin required workarounds

Package: installation-reports Severity: normal Had partial success installing on Espressobin, but required a few manual steps and workarounds... live well, vagrant -- Package-specific info: Boot method: network Image version: https://d-i.debian.org/daily-images/arm64/20180110-02:05/netboot/

Bug#886970: installation-reports: Lamobo R1, success!

Package: installation-reports Followup-For: Bug #886970 Successful install with the daily image from 20180111. Network card was detected and did DHCP without problem. live well, vagrant -- Package-specific info: Boot method: microSD Image version:

Bug#886970: installation-reports: Lamobo R1, partial success

Package: installation-reports Severity: normal On the Lamobo R1, the network card was detected but did not get a DHCP lease. Required manually loading the b53_mdio module, and then I was able to use the eth0 for installation. Another workaround was to use a USB r8152 ethernet adapter. I intend

Bug#883547: flash-kernel: please allow flavourless kernels

Control: tags 883547 pending On 2017-12-19, Adam Borowski wrote: > On Tue, Dec 19, 2017 at 04:04:34AM +0100, Adam Borowski wrote: >> On Mon, Dec 18, 2017 at 03:08:08PM -0800, Vagrant Cascadian wrote: >> > I think the following patch should work for this, by setting: >> &g

Bug#884375: Bug#884376: flash-kernel wandboard patches, NMU?

Control: tags 884376 pending Control: tags 884375 pending > Some feedback would be very welcome, but if there's none I can only > assume you're very busy and will thus proceed to help you out with a > NMU. (Despite these patches being pretty trivial, I'd still prefer to > have your opinion/review

Bug#884003: FDT overlay support

On 2017-12-12, Andre Heider wrote: > Attached a patch series with an implementation. Thanks for the patches! > I added the ability to concatenate multiple scripts/snippets for the > final boot script. > The new overlay handling snippet is supposed to be > used with this. But the feature

Bug#883547: flash-kernel: please allow flavourless kernels

Control: tag 883547 +patch On 2017-12-04, Adam Borowski wrote: > If for whatever reason you want or need to build your own kernels, the > preferred way these days is "make bindeb-pkg". It is also a good idea > to use CONFIG_LOCALVERSION_AUTO=y, which marks the exact tree used to > build the

Bug#883549: Debian Installer Buster Alpha 1 release - Hardware support of Xunlong Orange Pi zero

On 2017-12-05, Karsten Merker wrote: > On Tue, Dec 05, 2017 at 03:37:00AM +, Vasilis wrote: >> Happy to do any further tests. > > If you would be willing to commit to more or less regularly test > the Debian u-boot package on the board, the Debian u-boot > maintainer (Vag

Re: flash-kernel and dtbs

On 2017-11-26, Rainer Dorsch wrote: > On Sonntag, 26. November 2017 11:30:04 CET Vagrant Cascadian wrote: >> On 2017-11-26, Rainer Dorsch wrote: >> > I try to setup the correct dtb for a HummingBoard DualLite using >> > flash-kernel, >> > but the kernel

Re: flash-kernel and dtbs

On 2017-11-26, Rainer Dorsch wrote: > I try to setup the correct dtb for a HummingBoard DualLite using > flash-kernel, > but the kernel seems to load always the Cubox-i dtb: What u-boot do you have installed? Can you get to the u-boot console (probably serial console), and run the following

Bug#881969: making bootable SD cards

On 2017-11-17, Karsten Merker wrote: > On Thu, Nov 16, 2017 at 07:54:42PM -0400, Joey Hess wrote: >> A utility in flash-kernel would be much nicer than needing to puzzle out dd >> commands from README.Debian files and hope you got it right. I'm currently >> having to embed those dd commands inside

Bug#877467: Odroid-XU4: success despite several challenges

Package: installation-reports Severity: normal Thanks for maintaining debian-installer! This install was a bit rough, requring two workarounds to get USB working (a custom device-tree, and appending a cpio archive with all kernel modules to the initrd.gz), as well as some troublesome issues with

Bug#876773: flash-kernel: Please add support for the original SolidRun CuBox (Dove)

On 2017-09-25, Josua Mayer wrote: > The SolidRun CuBox has very good support in Mainline Linux. > Thus it is a great candidate for supporting it in Debian. ... > I have come up with the database entry below, and this preliminary > boot-script: > setenv loadaddr 0x0200 > setenv loadaddrrd

Bug#860304: flash-kernel: Incorrect installation path for dtbs

On 2017-08-27, Heinrich Schuchardt wrote: > On 08/25/2017 05:31 PM, Vagrant Cascadian wrote: >> On 2017-08-24, Heinrich Schuchardt wrote: >>> is there really any need to keep /boot/dtbs/VERSION/ if we have >>> /boot/dtbs/VERSION/VENDOR/? >> >> Yes, if the u

Bug#860304: Aw: Re: Bug#860304: [BUG 860304] flash-kernel: Incorrect installation path for dtbs

On 2017-08-24, Heinrich Schuchardt wrote: > is there really any need to keep /boot/dtbs/VERSION/ if we have > /boot/dtbs/VERSION/VENDOR/? Yes, if the u-boot version on the board sets fdtfile to BOARD.dtb. We have no way of knowing from flash-kernel what the u-boot on the board will set for

Bug#860304: [BUG 860304] flash-kernel: Incorrect installation path for dtbs

On 2017-08-11, Heinrich Schuchardt wrote: > On 08/11/2017 09:31 PM, Martin Michlmayr wrote: >> I just wanted to thank you for raising this issue and sending a patch. Indeed! >> Unfortunately, I'm not really active with flash-kernel anymore but I >> just spoke to Vagrant at

Bug#870615: debian-installer: FTBFS on armhf: missing firefly-rk3288/u-boot.img

On 2017-08-05, Vagrant Cascadian wrote: > On 2017-08-05, Cyril Brulebois wrote: >> Cyril Brulebois <k...@debian.org> (2017-08-05): >>> Vagrant Cascadian <vagr...@debian.org> (2017-08-04): >>> > And now fixed in u-boot 2017.07+dfsg1-3 (just uploaded), c

Bug#870615: debian-installer: FTBFS on armhf: missing firefly-rk3288/u-boot.img

On 2017-08-05, Cyril Brulebois wrote: > Cyril Brulebois <k...@debian.org> (2017-08-05): >> Vagrant Cascadian <vagr...@debian.org> (2017-08-04): >> > And now fixed in u-boot 2017.07+dfsg1-3 (just uploaded), corresponding >> > fix in debian-installer pushed

Bug#870615: debian-installer: FTBFS on armhf: missing firefly-rk3288/u-boot.img

Control: tags 870615 pending On 2017-08-03, Vagrant Cascadian wrote: > Control: severity 870615 important > > On 2017-08-03, Vagrant Cascadian wrote: >> On 2017-08-03, Cyril Brulebois wrote: >>> d-i now FTBFSes on armhf, due to: >>> ,---[ hd-media ]--- >>

Bug#870615: debian-installer: FTBFS on armhf: missing firefly-rk3288/u-boot.img

Control: severity 870615 important On 2017-08-03, Vagrant Cascadian wrote: > On 2017-08-03, Cyril Brulebois wrote: >> d-i now FTBFSes on armhf, due to: >> ,---[ hd-media ]--- >> | gen-hd-image: Installing /usr/lib/u-boot/firefly-rk3288/u-boot-spl.rksd at >> sect

Bug#870615: debian-installer: FTBFS on armhf: missing firefly-rk3288/u-boot.img

On 2017-08-03, Cyril Brulebois wrote: > d-i now FTBFSes on armhf, due to: > ,---[ hd-media ]--- > | gen-hd-image: Installing /usr/lib/u-boot/firefly-rk3288/u-boot-spl.rksd at > sector 64 ... > | gen-hd-image: Installing /usr/lib/u-boot/firefly-rk3288/u-boot.img at > sector 256 ... > |

Bug#869488: flash-kernel: Patch for Raspberry Pi 3 support

Control: tags 869488 pending On 2017-07-23, James Valleroy wrote: > On 07/23/2017 01:23 PM, Vagrant Cascadian wrote: >> On 2017-07-23, James Valleroy wrote: >>> Please consider the attached patch which adds support for Raspberry Pi >>> 3 Model B. ... >> I think t

Bug#869488: flash-kernel: Patch for Raspberry Pi 3 support

On 2017-07-23, James Valleroy wrote: > Please consider the attached patch which adds support for Raspberry Pi > 3 Model B. ... > +Machine: Raspberry Pi 3 Model B > +Kernel-Flavors: arm64 > +DTB-Id: bcm2836-rpi-3-b.dtb > +U-Boot-Script-Name: bootscr.uboot-generic > +Required-Packages: u-boot-tools

Bug#839595: flash-kernel: Please add support for SolidRun Clearfog

On 2017-07-23, Josua Mayer wrote: > Can anyone state the status here? If there is somethign missing, I'd be > perfectly willing to conduct some tests on my board if necessary. It looks like clearfog supports distro_bootcmd in mainline u-boot 2017.07 shipped in buster, including

Bug#864260: Missing kernel in debian-installer sd-card images for armhf (stretch)

On 2017-06-06, Karsten Merker wrote: > On Tue, Jun 06, 2017 at 10:47:55PM +0200, Karsten Merker wrote: > I guess I have found the problem: the images have a fixed size > (~40MB uncompressed) and the netboot build has grown a few kBytes > larger than that while the hd-media build still fits

Bug#860304: flash-kernel: Incorrect installation path for dtbs

On 2017-05-26, Heinrich Schuchardt wrote: > On 05/26/2017 08:58 PM, Vagrant Cascadian wrote: >> On 2017-05-26, Cyril Brulebois <k...@debian.org> wrote: > I recently created file /etc/flash-kernel/ubootenv.d/fdtfile with > > setenv fdtfile meson-gxbb-odroidc2.dtb Oh, I d

Bug#860304: flash-kernel: Incorrect installation path for dtbs

On 2017-05-26, Cyril Brulebois wrote: > And thanks for being persistent. Indeed, I've been working around this issue locally rather than doing the right things by filing bugs and writing patches... :) > Heinrich Schuchardt (2017-05-25): >> In >>

Bug#862746: unblock: simple-cdd/0.6.5

kernel_base + a) diff -Nru simple-cdd-0.6.4/debian/changelog simple-cdd-0.6.5/debian/changelog --- simple-cdd-0.6.4/debian/changelog 2017-01-17 15:10:07.0 -0800 +++ simple-cdd-0.6.5/debian/changelog 2017-05-15 14:10:37.0 -0700 @@ -1,3 +1,22 @@ +simple-cdd (0.6.5) unstable; urgenc

Bug#848075: cubox i4x4 hard drive seen in D-I but not in installed system.

On 2016-12-13, peter green wrote: > 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.hotplug=1 to the kernel

Bug#845818: Re: Bug#845818: flash-kernel: Add support for Hardkernel Odroid-C2

On 2017-03-17, Martin Michlmayr wrote: > * Heinrich Schuchardt [2017-03-18 02:39]: >> U-Boot 2017-3 does not contain MMC support for the Odroid C2. >> I have seen a recent patch series for MMC support. But I did not yet >> build with it. > > If they are

Re: d-i manual: 3 "jessie" remain in current guide

On 2017-04-08, Samuel Thibault wrote: > We need an answer, so as to update the documentation: is USB still not > supported in the stretch kernel on arm64? > > victory, on Mon 30 Jan 2017 21:53:52 +0900, wrote: >> boot-installer/arm.xml:108- >> ... Also USB is not supported in the jessie

Bug#845818: Re: Bug#845818: flash-kernel: Add support for Hardkernel Odroid-C2

On 2017-03-19, Vagrant Cascadian wrote: > On 2017-03-17, Martin Michlmayr wrote: >> * Heinrich Schuchardt <xypron.g...@gmx.de> [2017-03-18 02:39]: >>> U-Boot 2017-3 does not contain MMC support for the Odroid C2. >>> I have seen a recent patch series for MMC sup

Bug#845818: Re: Bug#845818: flash-kernel: Add support for Hardkernel Odroid-C2

On 2017-03-17, Martin Michlmayr wrote: > * Heinrich Schuchardt [2017-03-18 02:39]: >> U-Boot 2017-3 does not contain MMC support for the Odroid C2. >> I have seen a recent patch series for MMC support. But I did not yet >> build with it. > > If they are accepted for 2017.05,

Bug#853280: unblock: simple-cdd/0.6.4

pathname) +raise Fail("preseed file invalid: %s", p) def paranoid_checks(self): diff -Nru simple-cdd-0.6.3/debian/changelog simple-cdd-0.6.4/debian/changelog --- simple-cdd-0.6.3/debian/changelog 2016-11-27 18:40:54.0 -0800 +++ simple-cdd-0.6.4/debian/c

Bug#755804: very nice stuff

Hello, Just take a look at that stuff, I think it is something you really need) Please check this out <http://wire.mentalchaos.net/e6zd/2> Best, Vagrant Cascadian

Bug#843916: debian-installer: fails to FTBFS when u-boot bits go missing

1 had: > | u-boot (2016.09+dfsg1-2) unstable; urgency=medium > […] > | * Remove openrd targets, as they do not boot (Closes: #837629). > | > | -- Vagrant Cascadian <vagr...@debian.org> Sun, 23 Oct 2016 19:36:36 -0700 > > I might have missed messages on debian-boot@, but

Re: Install on Orange Pi Plus eMMC work but no reboot

ely on the boot ROM of the board what order it searches for the bootloader... Given that experience, I tend to strongly prefer installing u-boot on SD card when possible, as you can easily remove the SD card and reinstall a known-good u-boot from another machine. >> I'll put looking i

Bug#837509: installation-reports: Partial success on Novena (no USB during install)

Package: installation-reports Severity: normal Install mostly worked fine, but was unable to install to USB disk. -- Package-specific info: Boot method: network Image version: https://d-i.debian.org/daily-images/armhf/20160904-00:17/netboot/netboot.tar.gz Date: Mon Sep 12 01:00:00 UTC 2016

Bug#834974: Installation Report: Stretch Alpha 7 on Cubox-i4pro

On 2016-09-04, Rick Thomas wrote: > On Sep 4, 2016, at 3:12 AM, Rick Thomas <rbtho...@pobox.com> wrote: > >>> On Sep 2, 2016, at 5:12 PM, Vagrant Cascadian <vagr...@debian.org> wrote: >>> >>>> I'd be curious if you re-install and delete each parti

Bug#834974: Installation Report: Stretch Alpha 7 on Cubox-i4pro

n't know anything about this device so unfortunately I cannot help > you. Maybe Vagrant Cascadian knows something? In the past, I've had issues on other boards where it failed if the partitioning process zero'ed out the partition table. In my experience, re-installing u-boot usually resolv

Re: flash-kernel: handle DTBs in vendor subdir

On 2016-07-30, Martin Michlmayr wrote: > DTBs on arm64 are stored as vendor/dtb rather than everything in one > directory. flash-kernel doesn't handle this at the moment. I see two > options: > > 1) Strip the vendor dir away and install the dtb as > /boot/dtbs/$kvers/dtb > > 2) Keep the

Re: flash-kernel: arm64 doesn't have bootz

On 2016-07-30, Martin Michlmayr wrote: > bootscript/all/bootscr.uboot-generic uses bootz but arm64 requires > booti. > > My idea was to copy bootscript/all/bootscr.uboot-generic to arm64 and > replace bootz with booti: > > sed "s/bootz/booti/" bootscript/all/bootscr.uboot-generic > >

Re: Next d-i alpha release: late June

On 2016-06-27, Cyril Brulebois <k...@debian.org> wrote: > [ Unknown signature status ] > Vagrant Cascadian <vagr...@debian.org> (2016-06-27): >> On 2016-06-27, Cyril Brulebois wrote: >> > for some reasons I failed at double checking when u-boot is used; it's >

Re: Next d-i alpha release: late June

On 2016-06-27, Cyril Brulebois wrote: > Cyril Brulebois (2016-06-27): >> FWIW I'm going to upload debian-installer very shortly; it'd be nice if >> u-boot could be uploaded while src:debian-installer is getting built, >> urgented, and dak copy-installer'd into testing; so that it

Re: Next d-i alpha release: late June

rom u-boot 2016.05 to >> u-boot 2016.03 and to urgent the result into testing before doing the >> d-i release (CCing Vagrant Cascadian, the u-boot maintainer). >> >> Kibi, Vagrant: what's your opinion on the topic? > > If the fixes are identified and can be applied on t

Re: Bug#781873: Correct the guruplug.config to match the new upstream env address

Control: tags 781783 -pending Control: tags 781873 pending Typo in bug number, sorry for the noise! live well, vagrant On 2016-05-28, Debian Bug Tracking System wrote: > Processing control commands: > >> tags 781783 pending > Bug #781783 [hw-detect] Add open-vm-tools when installing in a

debian-installer for Odroid-XU4

On 2016-05-15, Steinar H. Gunderson wrote: > On Sun, May 15, 2016 at 12:53:33AM +0200, Steinar H. Gunderson wrote: >> I suppose there's no d-i support happening for the XU4 anytime soon? :-) I *think* pxe/tftp using distro_bootcmd was working fine from mainline u-boot on the Odroid-XU4; if so the

Bug#823020: Bug#823500: cannot boot from ext4

Control: block 823020 by 823500 Control: tags 823500 confirmed On 2016-05-05, Heinrich Schuchardt wrote: > u-boot-imx fails to read file > /dtbs/4.5.0-1-armmp/imx6q-wandboard-revb1.dtb > from an ext4 partition though the file exists. > > lsext4 mmc 0 dtbs > does not show the subdirectories in the

Bug#823020: installation-reports: problems with u-boot and ext4

Package: installation-reports Severity: important X-Debbugs-Cc: ma...@denx.de I've done several installs now on both a Wandboard Solo and an Novena board, and u-boot has problems reading the the dtbs subdirectory needed to load the device-trees, and fails to boot after an otherwise successful

Bug#807720: Information about Wandboard Quad out-of-date

On 2016-02-06, Vagrant Cascadian wrote: > On 2015-12-11, Martin Michlmayr wrote: >> en/hardware/supported/arm.xml says: >> >> [..] Support for >> the onboard audio options (analog, S/PDIF, HDMI-Audio) and for >> the onboard WLAN/

Bug#807720: Information about Wandboard Quad out-of-date

On 2016-02-06, Vagrant Cascadian wrote: > On 2015-12-11, Martin Michlmayr wrote: >> [..] Support for >> the onboard audio options (analog, S/PDIF, HDMI-Audio) and for >> the onboard WLAN/Bluetooth module is not available in >>

Bug#807720: Information about Wandboard Quad out-of-date

On 2015-12-11, Martin Michlmayr wrote: > en/hardware/supported/arm.xml says: > > [..] Support for > the onboard audio options (analog, S/PDIF, HDMI-Audio) and for > the onboard WLAN/Bluetooth module is not available in > 8. I can test some of the

Bug#812242: flash-kernel: SolidRun HummingBoard isn't supported

ontains an > entry for the SolidRun HummingBoard Dual/Quad: > > https://anonscm.debian.org/cgit/d-i/flash-kernel.git/commit/?id=e903f3d5d99b6795f59ab67be33dc79104e8096f > > The only difference to the one above is that is uses > > U-Boot-Script-Name: bootscr.uboot-generic > > in

Re: Bug#762634: initramfs-tools: [armhf] mounting rootfs on USB disk fails / some USB host controller drivers missing in initramfs

On 2014-09-30, Ben Hutchings wrote: > On Tue, 2014-09-30 at 08:19 +0100, Ian Campbell wrote: >> On Fri, 2014-09-26 at 00:08 +0100, Ben Hutchings wrote: >> > However, at the moment initramfs-tools won't include PHY drivers even in >> > that configuration. >> >> I spent some time last week hunting

Bug#802546: /usr/sbin/debootstrap: 399: cd: can't cd to http://ftp.debian.org

On 2015-10-20, Jeffrey Walton wrote: > # qemu-debootstrap --arch=ppc64 --keyring > /usr/share/keyrings/debian-archive-keyring.gpg --variant=buildd > --exclude=debfoster debian-ppc64 http://ftp.debian.org/debian > I: Running command: debootstrap --arch ppc64 --foreign --keyring >

Installing u-boot from debian-installer

I've been meaning to work on further integrating u-boot support into debian-installer, and I see a few different routes forward... Currently, the thre are installer images available for boot media on several media, but nothing handles upgrading u-boot after the initial installation. Also, using

Bug#793157: flash-kernel: syslinux-style boot configuration on recent u-boot versions

On 2015-07-21, Thibaut Girka wrote: syslinux-style /boot/extlinux/extlinux.conf superseed boot.scr in recent u-boot versions and seems to be the way forward for u-boot configuration, but I couldn't find anything to automatically generate them in Debian. ... I'm not sure whether flash-kernel

Re: U-Boot, d-i and selecting the console device

On 2015-06-21, Karsten Merker wrote: If we don't pass a console variable to the kernel, d-i starts on the console device defined by the platform's stdout-path property, i.e. usually on a serial console - again bad luck for people having only a framebuffer console. If we set the console

Bug#783074: flash-kernel: improvements to uboot-generic bootscript

On 2015-06-07, Ian Campbell wrote: On Mon, 2015-05-04 at 12:01 -0700, Vagrant Cascadian wrote: I can confirm that wandboard, cubox-i and hummingboard all default to console=ttymxc0, and several other boards by grepping through u-boot's include/configs. Some actually do setenv bootargs console

Bug#782574: installation-reports: d-i does not boot on beaglebone black

On 2015-05-27, François-Régis wrote: Le 27/05/2015 20:36, Vagrant Cascadian a écrit : I don't see anything mentioned in the errata yet: https://www.debian.org/releases/stable/debian-installer/#errata Not sure what the process is to update that, but I'd be happy to work on some text

Bug#782574: installation-reports: d-i does not boot on beaglebone black

On 2015-04-15, Cyril Brulebois wrote: Karsten Merker mer...@debian.org (2015-04-15): On Tue, Apr 14, 2015 at 06:42:57PM -0700, Vagrant Cascadian wrote: I've tested that it boots the armhf daily hd-media installer and boots an installed system. I could upload a new version of u-boot if it's

Bug#782574: installation-reports: d-i does not boot on beaglebone black

On 2015-05-27, François-Régis wrote: Le 27/05/2015 20:36, Vagrant Cascadian a écrit : On 2015-04-15, Cyril Brulebois wrote: Karsten Merker mer...@debian.org (2015-04-15): On Tue, Apr 14, 2015 at 06:42:57PM -0700, Vagrant Cascadian wrote: So I've been thinking about this for a while and I'm

Bug#786367: flash-kernel: support BeagleBone Black with u-boot 2015.04+

On 2015-05-25, Cyril Brulebois wrote: Ian Campbell i...@debian.org (2015-05-25): On Mon, 2015-05-25 at 03:37 +0200, Cyril Brulebois wrote: Uploading now looks good to me, but I don't want to stomp on anyone's toes. Ian, are you fine with my uploading a new version with these changes?

Bug#786369: debian-installer: Updates for cubox-i/wandboard with u-boot 2015.04+

On 2015-05-25, Cyril Brulebois wrote: Vagrant Cascadian vagr...@debian.org (2015-05-24): On 2015-05-24, Cyril Brulebois wrote: Vagrant Cascadian vagr...@debian.org (2015-05-20): The version of u-boot in experimental requires some changes for debian-installer to generate appropriate u-boot

Bug#786369: debian-installer: Updates for cubox-i/wandboard with u-boot 2015.04+

On 2015-05-24, Cyril Brulebois wrote: The version of u-boot in experimental requires some changes for debian-installer to generate appropriate u-boot images. ... The update to debian-installer and u-boot 2015.04+ uploaded to unstable should be coordinated to minimize the time that the daily

Bug#786369: debian-installer: Updates for cubox-i/wandboard with u-boot 2015.04+

On 2015-05-24, Cyril Brulebois wrote: Vagrant Cascadian vagr...@debian.org (2015-05-20): The version of u-boot in experimental requires some changes for debian-installer to generate appropriate u-boot images. The mx6_cubox-i target which was not previously upstream, is now named mx6cuboxi

Bug#786367: flash-kernel: support BeagleBone Black with u-boot 2015.04+

Package: flash-kernel Version: 3.37 Severity: wishlist Tags: patch The version of u-boot in experimental, 2015.04+dfsg1-1 contains a patch to the u-boot environment to support distro_bootcmd, but is incompatible with the current bootscript in flash-kernel. The following patch should fix this by

Bug#786369: debian-installer: Updates for cubox-i/wandboard with u-boot 2015.04+

Package: debian-installer Version: 20150422 Severity: wishlist Tags: patch The version of u-boot in experimental requires some changes for debian-installer to generate appropriate u-boot images. The mx6_cubox-i target which was not previously upstream, is now named mx6cuboxi upstream; I've

Bug#783073: bootscripts: Support using fdtfile variable passed from u-boot

On 2015-05-03, Ian Campbell wrote: On Tue, 2015-04-21 at 08:54 -0700, Vagrant Cascadian wrote: load ${device} ${partition} ${loadaddr} ${pathprefix}vmlinuz-${kvers} \ - load ${device} ${partition} ${fdtaddr} ${pathprefix}dtb-${kvers} \ + load ${device} ${partition} ${fdtaddr

Bug#783073: bootscripts: Support using fdtfile variable passed from u-boot

On 2015-05-02, Ian Campbell wrote: On Tue, 2015-04-21 at 08:54 -0700, Vagrant Cascadian wrote: The following patch prefers the use of the dtb file identified by the u-boot variable ${fdtfile}, which makes it easier to support installs where a single u-boot image can support multiple boards

Bug#783074: flash-kernel: improvements to uboot-generic bootscript

On 2015-05-03, Ian Campbell wrote: On Tue, 2015-04-21 at 09:12 -0700, Vagrant Cascadian wrote: This patch adds a few improvements to the uboot-generic bootscript: * Use kernel version in versioned files * Include kernel version, device and partition in boot message * Set the console

Bug#783769: flash-kernel: Add support for Hummingboard i1/i2ex.

: Vagrant Cascadian vagr...@debian.org Date: Tue, 21 Apr 2015 07:37:08 -0700 Subject: [PATCH] Add entries for SolidRun HummingBoard DL/Solo and SolidRun HummingBoard Dual/Quad. --- db/all.db | 14 ++ 1 file changed, 14 insertions(+) diff --git a/db/all.db b/db/all.db index 611b769

Bug#783073: bootscripts: Support using fdtfile variable passed from u-boot

Package: flash-kernel Version: 3.35 Severity: wishlist Tags: patch The following patch prefers the use of the dtb file identified by the u-boot variable ${fdtfile}, which makes it easier to support installs where a single u-boot image can support multiple boards, but need to load different fdt

Bug#783074: flash-kernel: improvements to uboot-generic bootscript

Package: flash-kernel Version: 3.35 Severity: wishlist Tags: patch This patch adds a few improvements to the uboot-generic bootscript: * Use kernel version in versioned files * Include kernel version, device and partition in boot message * Set the console in bootargs * Set workaround for console

Bug#782574: installation-reports: d-i does not boot on beaglebone black

Control: tags -1 +patch On 2015-04-14, Karsten Merker wrote: On Tue, Apr 14, 2015 at 03:51:45PM +0200, François-Régis wrote: Le 14/04/2015 14:05, Ben Hutchings a écrit : On Tue, 2015-04-14 at 13:24 +0200, Francois-Regis Vuillemin wrote: Here is the console log : [...] Running bootscript

<    1   2   3   >