On 2024-10-25, Pascal Hambourg wrote:
> On 24/10/2024 at 22:04, Diederik de Haas wrote:
>> On Thu Oct 24, 2024 at 9:08 PM CEST, Holger Wansing wrote:
>>>
>>> here you have a device|installation, which has the legacy_boot flag
>>> installed, but it did not work|boot despite of this. And you changed
The default salsa-ci pipeline for installer-team projects has always
failed for flash-kernel, probably because flash-kernel builds no
arch:amd64 packages.
I recently merged a salsa-ci configuration from josch and switched
flash-kernel to use a a salsa-ci pipeline that used arm64 runners
instead, s
On 2023-07-16, Simon McVittie wrote:
> On Sat, 15 Jul 2023 at 18:27:24 +0200, Adam Borowski wrote:
>> But, what matters here is the CTTE ruling in #1035831 -- for the time being,
>> packages must not move files between locations affected by the aliasing.
>
> If that happens in reality, then yes, th
On 2023-04-30, Roger Shimizu wrote:
> I'm trying to support an ARM based RB3 / DB845c [1] dev-board with
> android-style boot image to flash-kernel.
...
> My question is:
> - Currently flash-kernel is mainly u-boot based, is it proper to add
> "mkbootimg" based devices?
My main worry here is inves
On 2023-04-02, znot...@mailbox.org wrote:
> On Wed, Mar 15, 2023 at 09:50:23AM -0400, Znoteer wrote:
>> On Tue, Mar 14, 2023 at 11:34:42PM +0100, Cyril Brulebois wrote:
>> > Znoteer (2023-03-14):
>> > How reliable is your storage?
>> >
>> > Mar 14 21:26:04 in-target: dpkg-deb (subprocess): decomp
es ]
+ * Add QEMU-related "dummy" entries
+
+ [ Daniel Serpell ]
+ * Add A20-OLinuXino_MICRO-eMMC. (Closes: #1019881)
+
+ [ Heinrich Schuchardt ]
+ * db: add Lenovo ThinkPad X13s
+
+ [ Francesco Dolcini ]
+ * Add machine db entries for Colibri iMX6ULL eMMC
+
+ [ Heinrich Schuchardt ]
On 2023-04-16, Johannes Schauer Marin Rodrigues wrote:
> On Fri, 31 Mar 2023 13:52:45 + Isaac True wrote:
>> As part of our CI/CD system, we are building images for target devices. The
>> images are set up in virtual machines which boot using EFI, but flash-kernel
>> installation always fails
On 2023-01-26, Cyril Brulebois wrote:
> Vagrant Cascadian (2023-01-25):
>> Though a larger image would take a bit longer and burn a few extra
>> write cycles for those who did not need to actually use the space.
>
> I have no idea how much people care how much time is
On 2023-01-25, Cyril Brulebois wrote:
> Cyril Brulebois (2023-01-24):
...
> # SD card images (might also be applicable to the upcoming ChromeOS images)
>
> Looking at how those images are built, it seems we have a predefined,
> per-arch image size (150M or 200M), and gen-hd-image that's called in
Package: installation-reports
Severity: normal
X-Debbugs-Cc: vagr...@debian.org
Boot method: microSD/USB
Image version:
https://d-i.debian.org/daily-images/arm64/20230103-02:24/netboot/mini.iso
Date: 2022-01-03 ~21:00 UTC
Machine: Hardkernel Odroid C2
Partitions:
FilesystemT
On 2021-12-13, David Wright wrote:
> Having just swatted away this bug while installing bullseye
> on a laptop that has 1xUSB3, 2xUSB-C and no ethernet, I thought
> I should share the workaround here. This is only necessary,
> I'm led to believe, when installing by WiFi without the
> installation o
On 2023-01-01, Vagrant Cascadian wrote:
> I tried manually partitioning to get an encrypted /boot partition, and
> that did not end up working really. It warned me about it, and I
> ignored the warnings. It did not give me a warning when I tried
> installing without a boot partition w
Package: installation-reports
Severity: normal
X-Debbugs-Cc: vagr...@debian.org
Boot method: USB
Image version:
https://d-i.debian.org/daily-images/amd64/20230101-00:19/netboot/mini.iso
Date: Late One New Years Eve 2022
Machine: framework laptop 11th gen intel
Partitions:
Filesystem
On 2022-09-26, Bo YU wrote:
> On Thu, Sep 22, 2022 at 11:27 AM Cyril Brulebois wrote:
>> The Debian Installer team[1] is pleased to announce the first alpha
>> release of the installer for Debian 12 "Bookworm".
...
>> * flash-kernel:
>> - Skip flash-kernel in all EFI systems.
>> - Add sup
exporting LC_ALL=C.UTF-8 in debian/rules.
Thanks for maintaining localechooser!
live well,
vagrant
From 29d0987352263aa2ebedf89c558ff2868dd777d4 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian
Date: Wed, 31 Aug 2022 01:04:15 +
Subject: [PATCH 1/2] debian/rules: Disable parallelism for
Package: installation-reports
Severity: normal
X-Debbugs-Cc: vagr...@debian.org
Boot method: network
Image version:
https://d-i.debian.org/daily-images/arm64/20220818-02:26/netboot/netboot.tar.gz
Date: 2022-08-18 teatime
Machine: Pine64+
Partitions:
Filesystem Type 1K-blocksUsed Avai
Package: installation-reports
Severity: normal
X-Debbugs-Cc: vagr...@debian.org
Boot method: network
Image version:
https://d-i.debian.org/daily-images/arm64/20220624-02:19/netboot/netboot.tar.gz
Date: 2022-06-24 after breakfast but before lunch
Machine: Solidrun Honeycomb LX2
Partitions:
udev
On 2022-05-24, David Kaiser wrote:
> I am interested in assisting in the development and testing of a patch
> for this bug report.
Thanks for looking into this!
> I am assuming that the patch may be very simple;
> e.g., simply editing a list of included module names.
Probably just adding phy-gm
On 2022-04-05, Vagrant Cascadian wrote:
> I should see if it works via HDMI sometime...
HDMI support required tracking down two modules already enabled in the
linux kernel but not present in the udebs used by debian-installer. This
should be fixed in the next linux upload:
ht
On 2022-04-13, Vagrant Cascadian wrote:
> I will admit I used a tained image that added a couple modules for
> HDMI output on another platform (rock64); I'll check without the extra
> modules and report back if they're needed.
Grahpical installer seems to work out of the bo
Package: installation-reports
Severity: normal
X-Debbugs-Cc: vagr...@debian.org
Boot method: microSD media
Image version:
https://d-i.debian.org/daily-images/arm64/20220413-02:17/netboot/gtk/SD-card-images/
Date: 2022-04-13 ~2:00:00 UTC
Machine: Pine64 Rockpro64 RK3399
Partitions:
Filesystem
Package: installation-reports
Severity: normal
X-Debbugs-Cc: vagr...@debian.org
Boot method: microSD
Image version:
https://d-i.debian.org/daily-images/arm64/20220405-02:29/netboot/SD-card-images/
firmware.rock64-rk3328.img.gz partition.img.gz
Date: 2022-04-05 ~16:10 -0700
Machine: Pine64 Roc
Just uploaded u-boot 2022.04+dfsg-1 to unstable.
I don't *expect* anything will break for debian-installer, but figured
it was a big enough change that you might appreciate a heads up.
I'll try to keep an eye on things, but as always, feel free to ping me
via irc, file bugs reports, merge request
On 2022-03-31, Vagrant Cascadian wrote:
> On 2022-04-01, Steve McIntyre wrote:
>> On Sat, Mar 26, 2022 at 09:30:25AM +0100, Domenico Andreoli wrote:
>>>How the u-boot boot.scr is supposed to be created on a riscv machine?
>>>
>>>On arm, flash-kernel w
On 2022-04-01, Steve McIntyre wrote:
> On Sat, Mar 26, 2022 at 09:30:25AM +0100, Domenico Andreoli wrote:
>>How the u-boot boot.scr is supposed to be created on a riscv machine?
>>
>>On arm, flash-kernel would do the job. Is there any better alternative
>>or is it going to be used on riscv as well?
On 2021-11-06, Holger Wansing wrote:
> Vagrant Cascadian wrote (Fri, 05 Nov 2021 18:13:58
> -0700):
>>
>> https://salsa.debian.org/installer-team/anna/-/commit/f6d5052a00df58c8f9d27d74c8ab585cc4d341e2
>>
>> commit f6d5052a00df58c8f9d27d74c8ab585cc4d341
Package: anna
Severity: wishlist
X-Debbugs-Cc: vagr...@debian.org
I was recently made aware of:
https://salsa.debian.org/installer-team/anna/-/commit/f6d5052a00df58c8f9d27d74c8ab585cc4d341e2
commit f6d5052a00df58c8f9d27d74c8ab585cc4d341e2
Author: Holger Wansing
Date: Wed Nov 6 00:04:
Thanks for the report... a little more detail below...
On 2021-11-05, David Kaiser wrote:
> Comments/Problems:
>
> U-Boot 2021.01+dfsg-5 (May 23 2021 - 04:32:45 +) successfully loads and
> starts up.
> U-Boot attempts to run bootscript from mmc0:
> This installer medium does not contain a
On 2021-10-17, Cyril Brulebois wrote:
> Vagrant Cascadian (2021-10-16):
>> On 2021-07-16, Cyril Brulebois wrote:
>> > I know we haven't always been stellar when it comes to merging repro
>> > build work, sorry about that. Any chance you could chase^Wremind us
>
On 2021-07-16, Cyril Brulebois wrote:
> Vagrant Cascadian (2021-07-16):
>> The build path is embedded in various places in
>> libdebian-installer-extra.so.*:
>>
>>
>> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/libdeb
On 2021-10-02, Vagrant Cascadian wrote:
> On 2021-02-15, Vieno Hakkerinen wrote:
>> I created a ext2 for /boot and luks+lvm+btrfs for /. As d-i defaults
>> to use a @rootfs subvolume for btrfs the linux bootargs need to have
>> set "rootflags=subvol=@rootfs". This w
On 2021-02-15, Vieno Hakkerinen wrote:
> I created a ext2 for /boot and luks+lvm+btrfs for /. As d-i defaults
> to use a @rootfs subvolume for btrfs the linux bootargs need to have
> set "rootflags=subvol=@rootfs". This was not set during configuration
> of flash-kernel. Without this argument debia
On 2021-07-16, Cyril Brulebois wrote:
> Vagrant Cascadian (2021-07-16):
>> The build path is embedded in various places in
>> libdebian-installer-extra.so.*:
>>
>>
>> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/libdeb
5222acd3ccb659da12cb877398375ceab2a44388 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian
Date: Fri, 16 Jul 2021 13:59:17 +
Subject: [PATCH] debian/rules: Add -ffile-prefix-map to CFLAGS.
This avoids embedding the build path in the resulting binaries and
debug symbols.
https://reproducible-builds.org/docs/build-path
Package: installation-reports
Severity: normal
X-Debbugs-Cc: vagr...@debian.org
Boot method: microSD
Image version:
https://d-i.debian.org/daily-images/arm64/20210605-02:29/netboot/SD-card-images/
Date: 2021-06-05 UTC-07 ~15:00
Machine: Pinebook Pro RK3399
Partitions:
Filesystem Type 1K-
On 2021-05-23, Cyril Brulebois wrote:
> Vagrant Cascadian (2021-05-22):
>> This could impact debian-installer as it build-depends on it for
>> armhf/arm64, though I think the chance of regressions are minimal. Is
>> there a release candidate planned in the immediate future
On 2021-05-16, Vagrant Cascadian wrote:
> On 2021-05-07, Vagrant Cascadian wrote:
>> On 2021-04-16, Bastian Germann wrote:
>>> On a Lamobo R1, I can verify 2021.01 versions not to boot with a
>>> default environment. However, 2020.10+dfsg-2 boots. Even though the
>
On 2021-04-22, Frédéric Bonnard wrote:
> Machine: Power10 machine but got it on Power8 as well
> This happens randomly when the installer menu starts, I get to the first
> menu "Choose language", but it is red saying "An installation failed...
> The failing step is: Choose language".
FWIW, I've s
Package: partman-base
Severity: normal
X-Debbugs-Cc: vagr...@debian.org, alk...@gmail.com
For armhf/arm64 rockchip platforms, the bootloader may be installed
somewhere past the typical initial partition of 2048, but some platforms
install parts of the boot firmware past this boundary.
This was fi
bian/changelog2021-03-01 00:00:18.0
-0800
+++ u-boot-2021.01+dfsg/debian/changelog2021-03-12 15:00:43.0
-0800
@@ -1,3 +1,18 @@
+u-boot (2021.01+dfsg-4) unstable; urgency=medium
+
+ [ Arnaud Ferraris ]
+ * Add support for the pinetab platform (Closes: #982982)
+ * u-boot
Package: installation-reports
Severity: normal
X-Debbugs-Cc: vagr...@debian.org
Boot method: network
Image version:
https://d-i.debian.org/daily-images/arm64/20210325-02:16/netboot/netboot.tar.gz
Date: 2021-03-25 ~17:00 UTC
Machine: apm mustang
Partitions:
Filesystem Type
Control: reassign 982270 linux
Control: retitle 982270 linux: [armhf] several imx6 systems unable to detect
ethernet
Control: found 982270 5.10.13-1
On 2021-02-07, Rick Thomas wrote:
> It booted fine but when it got to the "Detect network hardware" phase,
> it failed and said:
>
>> No Ethern
On 2017-05-08, Sylvain L. Sauvage wrote:
> I just updated my server (only a few packages) and the initramfs
> and kernel were flashed THREE times!
> First for the new version of udev (I guess). The trigger is
> deferred but immediately executed. Thus flashing outdated data
> (kernel being upda
On 2021-02-06, Rick Thomas wrote:
> On Fri, Jan 29, 2021, at 7:18 PM, Rick Thomas wrote:
>> Hi!
>>
>> On Fri, Jan 29, 2021, at 1:03 AM, Holger Wansing wrote:
>> > On https://www.debian.org/devel/debian-installer/
>> > you should look under the daily snapshots.
>> > For armhf that would be
>> > htt
On 2021-02-06, harr...@gmx.ph wrote:
> On Fri, 4 Sep 2020 06:38:25 +0200, Andre Heider wrote:
>>[...]
>>+Machine: Globalscale Marvell ESPRESSOBin Board (eMMC)
>>+DTB-Id: marvell/armada-3720-espressobin-emmc.dts
>>[...]
>>+Machine: Globalscale Marvell ESPRESSOBin Board V7
>>+DTB-Id: marvell/armada-3
On 2021-02-06, harr...@gmx.ph wrote:
> On Fri, 4 Sep 2020 06:38:25 +0200, Andre Heider wrote:
>>[...]
>>+Machine: Globalscale Marvell ESPRESSOBin Board (eMMC)
>>+DTB-Id: marvell/armada-3720-espressobin-emmc.dts
>>[...]
>>+Machine: Globalscale Marvell ESPRESSOBin Board V7
>>+DTB-Id: marvell/armada-3
On 2021-01-29, Rick Thomas wrote:
> Hi!
>
> On Fri, Jan 29, 2021, at 1:03 AM, Holger Wansing wrote:
>> On https://www.debian.org/devel/debian-installer/
>> you should look under the daily snapshots.
>> For armhf that would be
>> https://d-i.debian.org/daily-images/armhf/daily/netboot/SD-card-images
On 2021-01-27, Rick Thomas wrote:
> I'm trying to install Debian Buster [1] on my Cubox-i4P with an eSATA
> drive. Everything seems to be fine, but when it comes time to reboot,
> it boots into the installer again, rather than the installed system.
>
> Here's what I did, and what I observed:
>
> *)
Control: tags 914813 pending
On 2020-09-22, Bernhard wrote:
> Attached, there is the current kernel configuration in Armbian.
> Here, there is RSB configured:
>> CONFIG_MFD_AXP20X=y
>> CONFIG_MFD_AXP20X_I2C=y
>> CONFIG_MFD_AXP20X_RSB=y
CONFIG_MFD_AXP20X_RSB=y is also in noteworthy upstream defcon
On 2020-08-28, Andre Heider wrote:
> On 27/08/2020 22:43, Vagrant Cascadian wrote:
>> On 2020-08-27, Andre Heider wrote:
>>> Since [0] flash-kernel does:
>>>
>>> if test -n "${console}"; then
>>> setenv bootargs "${bootargs
he u-boot CC on follow-ups.
On 2020-09-03, Andre Heider wrote:
> On 03/09/2020 20:59, Vagrant Cascadian wrote:
>> On 2020-09-03, Andre Heider wrote:
>>> On 03/09/2020 18:40, Dennis Gilmore wrote:
>>> If so, adding fdtfile like that would break booting debian using its
>
Control: severity 969070 important
On 2020-08-27, Andre Heider wrote:
> Since [0] flash-kernel does:
>
>if test -n "${console}"; then
> setenv bootargs "${bootargs} console=${console}"
>fi
>
> The common $console format as set by u-boot includes the leading "console=":
> include/confi
Control: tags 968391 pending
On 2020-08-24, Guido Günther wrote:
> On Fri, Aug 14, 2020 at 11:36:50AM +0200, Guido Günther wrote:
>> To make it simpler to run plain Debian on the Librem 5 it would be great
>> to have flash-kernel support. The device tree is in the process of being
>> upstreamed:
>
[ Heinrich Schuchardt ]
> * Add FriendlyARM NanoPi NEO Plus2. (Closes: #955374)
>
> [ Vagrant Cascadian ]
> * Add support for Pinebook Pro.
>
> [ Adam Borowski ]
> * Add support for Pinebook (Closes: #930098)
>
> [ Sunil Mohan Adapa ]
> * Add entry for Oli
Package: installation-reports
Severity: normal
Installation over serial console went reasonably well, no video output
on LCD (will need to wait for improved support in newer linux kernel
versions). Some glitches around bootloader installation to be worked on.
-- Package-specific info:
Boot metho
On 2020-03-08, Bernhard wrote:
> I had an additional look for the possible problem with the AXP813 for
> BananaPi M3 in U-Boot.
> With help of Google, i found a patchset for U-Boot from 2016:
>
> https://lists.denx.de/pipermail/u-boot/2016-January/240259.html
>
>> +++ b/configs/Bananapi_m3_defconf
Package: release.debian.org
Severity: normal
X-Debbugs-CC: Vagrant Cascadian ,
debian-boot@lists.debian.org, debian-...@lists.debian.org
The new version of LTSP no longer ships the ltsp-client-builder .udeb,
so it should be removed from the relevent block-udeb rules.
I believe debian-edu, the
1:29:45.00000 -0700
@@ -1,3 +1,41 @@
+simple-cdd (0.6.7) unstable; urgency=medium
+
+ [ Vagrant Cascadian ]
+ * Remove invalid contact information from README.
+ * Output command run on gpg verification failure rather than passing an
+undefined variable. (Closes: #919572, #929651). Th
ons to fix builds from unsigned CDs (Closes: #929735).
+
+ -- Vagrant Cascadian Wed, 29 May 2019 13:02:07 -0700
+
+ltsp (5.18.12-2) unstable; urgency=medium
+
+ [ Frans Spiesschaert ]
+ * [INTL:nl] Dutch translation of debconf messages (Closes: #924103).
+
+ [ Vagrant Cascadian ]
+ * Add pa
05a3241df281608b710c71e41d9a03d99cc68109 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian
Date: Sun, 2 Jun 2019 10:57:29 -0700
Subject: [PATCH] Support distros with unconventional PATH values by adding
$PATH to calls in in_target_failmsg and in_target_nofail.
Add the $PATH environment variable to the chroot call, otherwise
28861).
+
+ [ Cyril Brulebois ]
+ * Remove Christian Perrier from Uploaders, with many thanks for all
+his contributions over the years! (Closes: #927488)
+
+ [ Heinrich Schuchardt ]
+ * Add Marvell 8040 MACCHIATOBin Double-shot and Single-shot.
+(Closes: #928951)
+
+ -- Vagrant Cascadian Fr
On 2019-05-18, Chris Lamb wrote:
>> Now, regarding building d-i as a normal package, I hit a bit of a
>> readblock because it fails while trying to download the files in the
>> nodes running in the future.
>
> Sounds about right:
>
>
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable
ystems
Sorry for the long delay...
Untested and refreshed patch against current git attached.
live well,
vagrant
From 846e0fec533875605d58a93aa0680fcc31c06c62 Mon Sep 17 00:00:00 2001
From: dann frazier
Date: Thu, 23 May 2019 10:26:06 -0700
Subject: [PATCH] support gzip'd kernel ima
elog
--- u-boot-2019.01+dfsg/debian/changelog2019-04-19 16:43:08.0
-0700
+++ u-boot-2019.01+dfsg/debian/changelog2019-05-13 19:07:44.0
-0700
@@ -1,3 +1,32 @@
+u-boot (2019.01+dfsg-7) unstable; urgency=medium
+
+ [ Sunil Mohan Adapa ]
+ * Enable pine64-lts target in
On 2019-05-15, Domenico Andreoli wrote:
> Scanning mmc 0:2...
> Found /boot/extlinux/extlinux.conf
> Retrieving file: /boot/extlinux/extlinux.conf
> 753 bytes read in 12 ms (60.5 KiB/s)
> U-Boot menu
> 1: Debian GNU/Linux kernel 4.19.0-4-arm64
> 2: Debian GNU/Linux kernel 4.19.0-4-arm64 (
On 2019-05-14, Domenico Andreoli wrote:
> On Sun, May 12, 2019 at 10:13:50AM -0700, Vagrant Cascadian wrote:
>> On 2019-05-12, Karsten Merker wrote:
>> > On Sun, May 12, 2019 at 10:40:39AM +0200, Domenico Andreoli wrote:
>> > > Please mind that the NanoPi NEO 2 t
nts to use the boot media for the OS installation.
For now, at least making the boot media start at the 4MB offset will be
a start.
One-line patch attached! :)
live well,
vagrant
From a05f428d987fadad1c2a1602d75245b42d6df89f Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian
Date: Tue, 14 May
On 2019-05-14, Domenico Andreoli wrote:
> On Sun, May 12, 2019 at 10:13:50AM -0700, Vagrant Cascadian wrote:
>> On 2019-05-12, Karsten Merker wrote:
>> > On Sun, May 12, 2019 at 10:40:39AM +0200, Domenico Andreoli wrote:
>> > > Please mind that the NanoPi NEO 2 t
On 2019-05-12, Karsten Merker wrote:
> On Sun, May 12, 2019 at 10:40:39AM +0200, Domenico Andreoli wrote:
>> +Machine: FriendlyARM NanoPi NEO 2
>> +Kernel-Flavors: arm64
>> +Boot-Script-Path: /boot/boot.scr
>> +DTB-Id: allwinner/sun50i-h5-nanopi-neo2.dtb
>> +U-Boot-Script-Name: bootscr.uboot-generi
lization for sun50i.
+ * Add patch by Vasily Khoruzhick to support Olimex Teres-I DIY laptop.
+ * Enable teres_i target in u-boot-sunxi (Closes: #926040).
+
+ [ Frédéric Danis ]
+ * Enable orangepi_zero_plus2 target in u-boot-sunxi (Closes: #927224).
+
+ -- Vagrant Cascadian Fri, 19 Apr 2019
-k2 and khadas-vim/vim2.
+
+ -- Vagrant Cascadian Mon, 08 Apr 2019 19:47:02 -0700
+
u-boot (2019.01+dfsg-3) unstable; urgency=medium
[ Romain Perier ]
diff -Nru u-boot-2019.01+dfsg/debian/targets u-boot-2019.01+dfsg/debian/targets
--- u-boot-2019.01+dfsg/debian/targets 2019-02-28 20:38
On 2018-07-17, Josua Mayer wrote:
> Sorry for the quick addition: a secodn uncertainty lies in the name of
> the boot script.
> We currently search for a bootargs.scr which was supposed to let distros
> set a few boot options, and then return control back to the menu.
>
> So maybe the name should b
On 2019-03-09, Adam D. Barratt wrote:
> On Thu, 2019-03-07 at 22:01 +, Ben Hutchings wrote:
>> On Thu, 2019-03-07 at 14:39 +0100, Cyril Brulebois wrote:
>> [...]
>> > > * Rebuild the debian-installer images, pulling in updates from
>> > > stretch-updates, leaving only armhf netboot targets br
On 2019-03-26, Adam D. Barratt wrote:
> On 2019-03-15 06:44, Adam D. Barratt wrote:
>> The updated images for armhf have been available in p-u for a couple of
>> days now.
>>
>> Feedback would be appreciated, as we would like to be able to accept
>> the new kernel upload into p-u, which will block
On 2019-03-10, Cyril Brulebois wrote:
> Vagrant Cascadian (2019-03-09):
>> >> Thanks for your report; that's known and fixed on the kernel side
>> >> already; how to deal with d-i is discussed in:
>> >> https://lists.debian.org/debian-boot/2019/03/ms
On 2019-03-09, Vagrant Cascadian wrote:
> On 2019-03-09, Cyril Brulebois wrote:
>> Peter Lebbing (2019-03-09):
>>> Debian kernel bug #922478 renders armhf systems unbootable. This bug was
>>> fixed, but the debian-installer images still use (I presume) kernel
>>&g
On 2019-03-09, Cyril Brulebois wrote:
> Peter Lebbing (2019-03-09):
>> Debian kernel bug #922478 renders armhf systems unbootable. This bug was
>> fixed, but the debian-installer images still use (I presume) kernel
>> version 4.9.144-3, the unbootable version. I noticed this today while
>> trying
On 2019-03-07, Ben Hutchings wrote:
> On Thu, 2019-03-07 at 14:39 +0100, Cyril Brulebois wrote:
> [...]
>> > * Rebuild the debian-installer images, pulling in updates from
>> > stretch-updates, leaving only armhf netboot targets broken.
>>
>> Expanding a bit: rebuilding src:debian-installer fro
Due to #922478, the debian-installer images for stretch are currently
not bootable on the armhf architecture.
While the linux kernel packages have been fixed in stretch-updates and
stretch-proposed-updates, the debian-installer images still were built
with the broken kernel.
Even rebuilding the d
Control: tags 921518 -patch
On 2019-02-06, Ben Hutchings wrote:
> On Wed, 2019-02-06 at 13:45 +0100, Alexandre GRIVEAUX wrote:
>> With adding correction of Raspberry pi 1 to use ARMEL flavour from feedback.
> [...]
>
> "armel" is the name of the Debian architecture that can run on the Pi
> 0/1, no
On 2019-03-03, Heinrich Schuchardt wrote:
> The Pine A64 LTS is supported in Linux upstream since v4.20 and the
> relevant device tree is contained in package linux-image-4.20.0-trunk-arm64
> (4.20-1~exp1).
The device-tree for Pine A64 LTS might be a good candidate to backport
to 4.19.x and get it
On 2019-02-22, Cyril Brulebois wrote:
> Cyril Brulebois (2019-02-22):
>> Vagrant Cascadian (2019-02-21):
>> > I went ahead and merged them into git.
>>
>> This seems to have broken all daily builds.
Ouch, very sorry...
> FWIW daily builds are run from
On 2019-02-21, Chris Lamb wrote:
> Chris Lamb wrote:
>> > #920631 debian-installer: Ensure build is reproducible regardless
>> > of the user's umask(2)
>> [..]
>> > #920676: debian-installer: Ensure build is reproducible
>> > regardless of the underlying filesystem ordering
>>
>> Thank you for dev
On 2019-02-20, John Paul Adrian Glaubitz wrote:
> On 2/19/19 11:56 PM, Vagrant Cascadian wrote:
>> I tried installing an armel chroot on an arm64 machine:
>>
>> $ sudo debootstrap --variant=minbase --arch=armel --no-merged-usr
>> --verbose sid /srv/chroots/arme
Package: debootstrap
Version: 1.0.114
Severity: normal
I tried installing an armel chroot on an arm64 machine:
$ sudo debootstrap --variant=minbase --arch=armel --no-merged-usr --verbose
sid /srv/chroots/armeltest http://deb.debian.org/debian/
E: Unable to execute target architecture
This a
On 2019-02-18, Josua Mayer wrote:
> Am 27.08.18 um 19:03 schrieb Vagrant Cascadian:
>> All arm64 linux dtbs are in sub-dirs, flash-kernel supports them in
>> sub-dirs, and u-boot should generally just append the value of fdtfile
>> to whatever search path and look for it ther
Package: installation-reports
Severity: normal
Overall install went ok, but requires manually constructing an image
to boot as USB requires binary firmware blob.
Using UEFI images are limited as they do not support loading a .dtb
matching the kernel, and the device-tree passed by u-boot's EFI
imp
On 2018-12-17, Rick Thomas wrote:
>> On Dec 15, 2018, at 2:26 PM, Cyril Brulebois wrote:
>>
>> Hardware support changes
>>
>>
>> * debian-installer:
>> - [armel] Disable OpenRD targets, no longer present in u-boot.
>
> Does this mean that my OpenRD hardware will no lon
On 2018-10-19, Ben Hutchings wrote:
> On Thu, 2018-10-18 at 23:43 -0700, Vagrant Cascadian wrote:
>> There are at least two arm64 laptops, but as far as I know they both
>> currently just support simplefb, though I'm not sure what needs to
>> change in debian-installer t
On 2018-10-18, Ben Hutchings wrote:
> On Thu, 2018-10-18 at 19:48 +0200, Marcin Juszkiewicz wrote:
> For current AMD chips the only native driver is amdgpu; for older chips
> it's radeon. Both of them will need some firmware just to light up the
> display.
>
>> - nouveau
There is a tegra laptop t
On 2018-08-27, Josua Mayer wrote:
> Am 24.08.2018 um 14:55 schrieb Héctor Orón Martínez:
>> Missatge de Josua Mayer del dia dg., 19
>> d’ag. 2018 a les 22:00:
>>> Only one important thing has to be dealt with: Getting the DTB loaded by
>>> U-Boot!
>>> U-Boot searches for rockchip/rk3328-rock64.d
On 2018-08-14, Joey Hess wrote:
> I'm using a custom device tree file to enable onewire temperature
> sensors. More generally,
> http://joeyh.name/blog/entry/easy-peasy-devicetree-squeezy/
> currently puts its device tree file in /etc/flash-kernel/dtbs/
> and thus is affected by the lack of kerne
I'm finding the need to apologize for neglecting to communicate to the
debian-installer development community over some BoF sessions at the
last two DebConfs regarding alternatives to and possible replacements
for debian-installer.
In retrospect, it was a terribly obvious oversight in communicatio
Control: block 900918 by 900409 900410
This requires fixes to mtools, marked as blocking bugs.
live well,
vagrant
signature.asc
Description: PGP signature
Package: installation-reports
Severity: normal
Pretty easy install for an armhf system.
Only complication is installing u-boot requires using the vendors signed
binaries(which can't be shipped in Debian), but the actual u-boot
binaries come from Debian.
live well,
vagrant
-- Package-specific
Package: installation-reports
Severity: normal
Install was a success in the end, with some rough edges related to
hardware support for this board; mainly ethernet, microsd, SMP support.
live well,
vagrant
-- Package-specific info:
Boot method: microSD
Image version:
https://d-i.debian.org/da
Control: tags 899093 +pending
On 2018-05-18, Heinrich Schuchardt wrote:
> Current U-Boot prepends 'allwinner/' to fdtfile.
>
> Signed-off-by: Heinrich Schuchardt
> ---
> db/all.db | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/db/all.db b/db/all.db
> index 97eff67..635f
On 2018-05-20, Geert Stappers wrote:
> On Sun, May 20, 2018 at 09:15:38PM +0200, Karsten Merker wrote:
>>
>> When looking at the defconfigs for several of these systems, I
>> see e.g. CONFIG_BOOTARGS settings that don't really match what I
>> would expect for systems using config_distro_bootcmd.h.
Control: tags 899092 +pending
On 2018-05-18, Vagrant Cascadian wrote:
> Since there's no difference other than the Machine, you should be able
> to simply specify the Machine entry twice with the same stanza:
>
> Machine: Marvell 8040 MACCHIATOBin
> Machine: Marv
Control: tags 899091 +pending
Thanks for the patch!
Pushed to git.
live well,
vagrant
On 2018-05-18, Heinrich Schuchardt wrote:
> Package: flash-kernel
> Version: 3.94
> Severity: normal
> Tags: patch
>
> Current U-Boot prepends 'rockchip/' path in fdtfile variable.
>
> Signed-off-by: Heinric
1 - 100 of 285 matches
Mail list logo
