distro" boot
vs. the newer "bootstd" which I am less familiar with...
Mixed feelings about leaving the first 16MB unpartitioned vs. specifying
some partition for it that has some special flag set. Creating a
partition and marking it with MBR boot or legacy_bios_boot might trip up
broke anything!
live well,
vagrant
signature.asc
Description: PGP signature
uld essentially
have to implement a reproducible builds style test to check for
differences...
After upgrading the infrastructure to bookworm, testing usrmerge
variations broke again, and so is currently disabled... though I have
configured the paths_vary_due_to_usrmerge issue so that old known issues
are not automatically removed anymore.
live well,
vagrant
signature.asc
Description: PGP signature
packaged kernel
and all. Not so different from the mkimage-style support for u-boot.
It is a frustrating that there are so many ways to boot arm systems...
but that is the reality out there actually implemented in hardware...
live well,
vagrant
signature.asc
Description: PGP signature
likely take over
and not use the u-boot on the microsd, but I *think* it should support
those images, which should pass the correct device-tree at least. You
might need a USB-ethernet adapter if the wifi firmware is not included
in those images... or otherwise do the firmware dance to get the wifi
working (I've only ever used the pinebook-pro-rk3399 with USB
ethernet/wifi).
live well,
vagrant
signature.asc
Description: PGP signature
]
This is used by debian-installer, and they might want to make an RC
soon...
unblock flash-kernel/3.107
Thanks for considering!
live well,
vagrant
diff -Nru flash-kernel-3.106/bootscript/armhf/olpc.fth
flash-kernel-3.107/bootscript/armhf/olpc.fth
--- flash-kernel-3.106/bootscript/armhf
though the main drawback is having to
write to /etc/default/flash-kernel and then potentially having to handle
changes merged into it on flash-kernel upgrades...
I very much appreciate new energy on this issue; it seemed stuck on two
somewhat incompatible needs and also broke previous working
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
those who did not need to add the
firmware.
Another option would be to use a growable filesystem, and then grow it
to whatever size needed? Are FAT filesystems reasonably growable?
Thanks for all your work on this!
live well,
vagrant
signature.asc
Description: PGP signature
SD card images once
https://bugs.debian.org/1027176 is fixed or worked around.
live well,
vagrant
-- Package-specific info:
==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux
etc/network/interfaces.with-wifi and chmod 0600 it for the
previously discussed security reasons.
I would be more likely to notice a file sitting next to
/etc/network/interfaces rather than rummaging around in /root.
live well,
vagrant
signature.asc
Description: PGP signature
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
LE_CRYPTODISK=y' > /etc/grub.d/cryptdisk.cfg
# mkfs.ext4 on the device, add to fstab, mount, copy /boot files,
# update-grub, grub-install, etc...
Going through all that trouble feels a little silly, because /boot/efi
is still entirely unencrypted, but, well, shored up what I could,
support
for grub-efi-riscv64; some of the vendor u-boot platforms probably
support EFI, even if u-boot support isn't in Debian.
I think Ubuntu is using the EFI support on some riscv64 platforms, so it
must be theoretically possible, at least.
live well,
vagrant
signature.asc
Description: PGP signature
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
grub method.
live well,
vagrant
-- Package-specific info:
==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="12 (bookw
ssues with bullseye's installer too, so at least it's
not... a regression? :)
live well,
vagrant
-- Package-specific info:
==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="D
ooking for the
> relevant patch source repository and source file.
Getting your custom kernel into a custom-built installer image is a
little trickier...
live well,
vagrant
signature.asc
Description: PGP signature
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
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.
live well,
vagrant
-- Package-specific info:
==
erall install:[O]
Comments/Problems:
That was too easy!
I should see if it works via HDMI sometime...
live well,
vagrant
-- Package-specific info:
==
Installer lsb-release:
==
DISTRIB_ID=D
rts, merge requests, etc. as needed. :)
live well,
vagrant
signature.asc
Description: PGP signature
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
to be used on riscv as well?
>>
>>What are the plans here?
>
> I'm assuming that for riscv devices using U-Boot we should add
> flash-kernel there too. We'll need to build a hardware database there
> too. AFAICS Vagrant (in CC) is the most active flash-kernel devel
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
images in the less
typical use cases...
Don't have the time to write a patch right now, but somedaymaybe. :)
Thanks!
live well,
vagrant
signature.asc
Description: PGP signature
10.75...
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/usb/musb/musb_dsps.c?id=c2115b2b16421d93d4993f3fe4c520e91d6fe801
Hope to be able to look into this further at some point...
live well,
vagrant
signature.asc
Description: PGP signature
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
ler.postinst.in- chroot /target debconf-set-selections
I'm curious how other systems handle btrfs (e.g. grub on amd64); are
there any configuration options passed via debian-installer to set
"rootflags=subvol=@rootfs", or does grub have any configuration that are
set from update-grub or whatever ... or autodetected when rootfs is on
btrfs?
live well,
vagrant
signature.asc
Description: PGP signature
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
attached patch fixes this by passing -ffile-prefix-map to CFLAGS in
debian/rules.
Alternately, with recent versions of dpkg, using dpkg-buildflags to set
CFLAGS should pass this option by default.
Thanks for maintaining libdebian-installer!
live well,
vagrant
From
hat I needed to get the USB-C dock ethernet working.
Fixed in usb-modules udeb:
https://salsa.debian.org/kernel-team/linux/-/commit/da303eff9dcfd233997a9fc2583c66d8587315be
Other than the washed out colors, should work ok once the next kernel
version is used.
live well,
vagrant
-- Pa
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
>
soon and try to get more details...
live well,
vagrant
signature.asc
Description: PGP signature
d bootable.
Another option for some platforms is to install the boot firmware to SPI
flash instead of relying on boot media(some systems may do this or
something similar out of the box), which entirely avoids the problem.
live well,
vagrant
signature.asc
Description: PGP signature
/2021.01+dfsg-4
Thanks for your work managing the release!
live well,
vagrant
diff -Nru u-boot-2021.01+dfsg/debian/bin/u-boot-install-sunxi
u-boot-2021.01+dfsg/debian/bin/u-boot-install-sunxi
--- u-boot-2021.01+dfsg/debian/bin/u-boot-install-sunxi 2021-02-28
18:14:48.0 -0800
+++ 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
s to consistantly
result in no working ethernet interface.
Marked as found in 5.10.13-1, but I believe this affects all 5.10.x
versions I have seen.
Possibly related to changes to the mdio interface infrastructure, but
this pretty much needs someone to able take the time to git bisect an
dated every
time a relevent package gets updated, even it if still happens multiple
times in any given run...
That said, someone with a better understanding of dpkg triggers might be
able to come up with something better...
live well,
vagrant
signature.asc
Description: PGP signature
> intervening week, but I still got the same result: "No Ethernet card was
> detected."
>
> Do I need to file a bug report? If so, to which package? If I do, is there
> any chance it will be fixed before Bullseye is released into the wild?
> Is there a known workaround
e settings
> flash-kernel is likely to give a "Couldn't find DTB..." error on those boards.
Good catch, thanks! Also noticed another platform with the same
issue. Fixed in git:
https://salsa.debian.org/installer-team/flash-kernel/-/commit/756064cb049f4ac17961c4b67d680670c075
live well,
vagrant
signature.asc
Description: PGP signature
e settings
> flash-kernel is likely to give a "Couldn't find DTB..." error on those boards.
Yes, you're absolutely right.
live well,
vagrant
one in use when I boot with a working system.
Pretty sure it is not atheros, but handled by:
drivers/net/ethernet/freescale/fec_main.c
Not sure what exact module or built-in that ends up in.
live well,
vagrant
signature.asc
Description: PGP signature
f the eSATA.
If you interrupt the boot process and get to a u-boot prompt, you should
be able to see the order of devices u-boot tries to boot from with:
printenv boot_targets
Now that bullseye is in the early phases of freeze, please consider
testing bullseye, too, if you can! :)
live well,
vagrant
signature.asc
Description: PGP signature
ad.
Thanks for keeping at this issue!
live well,
vagrant
signature.asc
Description: PGP signature
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
>
> contain "chosen { stdout-path = &uart0; };".
Not all systems have stdout-path defined in the device-tree.
Maybe now those are the exceptions...
> So I'd say appending $console to $bootargs is some historical leftover,
> and it can just be removed from the generic scripts.
The problem is that *not* doing this with console can also result in an
unbootable system.
Reverting this would be breaking one thing to fix another. There's no
"correct" here, only different. :/
Downgraded severity, as this does not affect all systems.
live well,
vagrant
signature.asc
Description: PGP signature
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/arch/arm64/boot/dts/freescale/imx8mq-librem5-r3.dts
Merged. Thanks for the patches!
live well,
vagrant
signature.asc
Description: PGP signature
[ 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
SB ethernet and the built-in USB keyboard works.
So, debian-installer was able to produce a working, if limited system. A
few linux kernel versions down the road, it might become a usable arm64
laptop...
live well,
vagrant
==
Instal
8I_EMAC=y
>> CONFIG_AXP_DCDC5_VOLT=1200
>> CONFIG_AXP_DLDO3_VOLT=3300
>> CONFIG_AXP_SW_ON=y
>> CONFIG_USB_EHCI_HCD=y
>> CONFIG_USB_OHCI_HCD=y
>> CONFIG_USB_MUSB_HOST=y
>> CONFIG_SYS_USB_EVENT_POLL_VIA_INT_QUEUE=y
I presume this is configs/Sinovoip_BPI_M3_defconfig ?
> Some CONFIG_AXP_... are missing in the Debian configuration.
> Is it possible, that these missing AXP-configs have to be added in the Debian
> configuration?
>
> If i can do some tests, please let me know.
Debian doesn't have any patches that should affect this; CCing
upstream. Hopefully someone there has some suggestions or ideas.
live well,
vagrant
signature.asc
Description: PGP signature
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
Package: debootstrap
Version: 1.0.114
Severity: normal
The following patch fixes issues when the hard-coded
PATH=/sbin:/usr/sbin:/bin:/usr/bin does not contain chroot or other
commonly used utilities, by changing to PATH=$PATH:/sbin:...
live well,
vagrant
From
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
+ sed 's,^deb \[[^]]*\] ,deb ,' | \
grep -v
'\(security.debian.org\|volatile.debian.\(net\|org\)\)' | \
grep '[[:space:]]main' | \
awk '{print $1 " " $2}' | \
Happen to remember what it breaks to have these present? If it was a
workaround, perhaps it is no longer needed?
live well,
vagrant
signature.asc
Description: PGP signature
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
prompt unset the the variable that checks for extlinux:
setenv scan_dev_for_extlinux false
Alternately, remove /boot/extlinux/extlinux.conf and reboot.
live well,
vagrant
signature.asc
Description: PGP signature
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
d-i, or a lot of
manual fiddling within the installer. You could also patch
/target/etc/flash-kernel/db or /target/usr/share/flash-kernel/db from
within the install at just the right moment ...
live well,
vagrant
signature.asc
Description: PGP signature
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
be the name should be boot.scr instead. I will update once this
> has been decided.
Any status update? Not much time left to get into the next release...
live well,
vagrant
signature.asc
Description: PGP signature
mhf/
I've successfully tested version "20170615+deb9u5+b3", as well as at
least one other person. It should continue to work until the next point
release, and I'll do at least some minimal testing of the next point
release on armhf before pushing it to stretch so this doesn't happen
again.
More details in:
https://bugs.debian.org/924129
live well,
vagrant
signature.asc
Description: PGP signature
ernel upload into p-u, which will block a further rebuild here
>> as it brings an ABI bump. (The existing images should continue to work
>> until the older packages are decrufted in the next point release.)
>
> Thanks to Peter for the feedback.
>
> Vagrant (or anyone else) -
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
; https://lists.debian.org/debian-boot/2019/03/msg00165.html
>
> Currently waiting on some input from Vagrant:
> https://lists.debian.org/debian-boot/2019/03/msg00179.html
Sorry to keep folks waiting...
live well,
vagrant
from stretch.
> [...]
>
> Why is that a problem? The only change made in 4.9.144-3.1 is in the
> kernel image, and the module udebs don't have versioned dependencies.
If that's indeed the case, then that does seem like the best
approach. Happy to test images to confirm.
live well,
vagrant
signature.asc
Description: PGP signature
sort of
thing before release...
live well,
vagrant
signature.asc
Description: PGP signature
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
x and get it working for buster; the SoC support and most or all
drivers may already be present in 4.19.x.
live well,
vagrant
signature.asc
Description: PGP signature
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
done any d-i development
> for almost 10 years now so I may not be aware of the most
> productive, helpful and — above everything else! — friendly way of
> getting things merged, particularly in time for buster. Can you
> help? :-)
I went ahead and merged them into git.
live well,
vagrant
signature.asc
Description: PGP signature
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
ot possible, or it takes a long time, or some future
bug in arch-test comes around, it'd be nice to be able to override it
without uninstalling arch-test.
live well,
vagrant
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing'), (5
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
s EFI
implementation lacks some features (SMP, SATA).
Once booted with the USB firmware blob loaded and correct .dtb loaded,
the install worked fine.
live well,
vagrant
-- Package-specific info:
Boot method: microSD
Image version:
https://d-i.debian.org/daily-images/arm64/20190119-02:06/ne
, but it's an old enough platform that I'd recommend testing it
for those who want to ensure continued support...
live well,
vagrant
signature.asc
Description: PGP signature
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
installer to support them; just tried the pinebook
earlier today without much luck getting d-i running on the tty displayed
on the LCD.
live well,
vagrant
signature.asc
Description: PGP signature
r search path and look for it there.
>>> Currently most used and best documented source for rock64 U-Boot:
>>> https://github.com/ayufan-rock64/linux-u-boot/releases
>>>
>>> u-boot-erase-spi-rock64.img.xz can be used to flash u-boot to SPI flash
>>>
ribly
well-documented, but you can glean them from the script itself. It is a
bit annoying to support a split /boot partition.
You loose the flexibility of boot scripts that flash-kernel would give
you, and it's harder to do one-off commandline entries, but having an
actual menu is nice.
liv
d-i where and when I can, and intend to
continue to do so for the forseeable future.
live well,
vagrant
P.S. Please CC me on replies, as I'm not subscribed to debian-boot, or
feel free to reply privately if you prefer.
signature.asc
Description: PGP signature
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
-- Pa
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
dtb
> Boot-Script-Path: /boot/boot.scr
> U-Boot-Script-Name: bootscr.uboot-generic
> Required-Packages: u-boot-tools
> --
> 2.17.0
Thanks for the patch!
Committed to git.
live well,
vagrant
signature.asc
Description: PGP signature
ompare against /proc/device-tree/model ... might not be
particularily fast... but certainly doable. Could use dpkg triggers or a
kernel postinst hook or something, and update the database on
installation of relevent packages.
live well,
vagrant
signature.asc
Description: PGP signature
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
1 - 100 of 287 matches
Mail list logo
