Hello,
On 3/20/22 13:38, Uwe Kleine-König wrote:
the builtin wifi hardware (broadcom) wasn't autodetected. I didn't look
into it yet, doesn't work out-of-the-box in the installed system either.
FTR: The right driver is contained in the broadcom-sta-dkms package.
With that the
Package: installation-reports
Severity: normal
X-Debbugs-Cc: u...@kleine-koenig.org
Boot method: SD card
Image version: firmware-11.2.0-amd64-i386-netinst
Date: 2022-03-20
Machine: Apple MacBook Air
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't
Hello,
On 9/10/21 11:07 PM, Uwe Kleine-König wrote:
when the active machine entry has an "Mtd-Kernel" field, flash-kernel
checks if the kernel fits into the specified mtd partition. However if
the machine entry also has "DTB-Append: yes" the image written to said
partition
Package: flash-kernel
Version: 3.104
Severity: normal
Hello,
when the active machine entry has an "Mtd-Kernel" field, flash-kernel
checks if the kernel fits into the specified mtd partition. However if
the machine entry also has "DTB-Append: yes" the image written to said
partition is a combinati
Package: flash-kernel
Version: 3.104
Severity: normal
Hello,
for the Netgear ReadyNAS 104 there is an entry in the shipped db that
looks as follows:
Machine: NETGEAR ReadyNAS 104
DTB-Id: armada-370-netgear-rn104.dtb
DTB-Append: yes
Mtd-Kernel: uImage
Mtd-I
Package: flash-kernel
Version: 3.99
Severity: normal
Hello,
I just upgraded my Debian installation from an older testing to Buster
and the kernel update failed with:
Setting up initramfs-tools (0.133+deb10u1) ...
update-initramfs: deferring update (trigger activated)
Proc
Hello Alexander,
On Thu, Jul 20, 2017 at 11:43:44AM +0200, Alexander Syring wrote:
> Package: flash-kernel
> Version: 3.79
> Severity: minor
> Tags: newcomer
>
> Please add a switch to disable the use of an initrd-image.
>
> I'm compiling my kernel with make dep-pkg
> and I'm not using an initrd
Hi Holger,
On 1/28/20 11:16 PM, Holger Wansing wrote:
> I would like to upload flash-kernel to unstable soon.
>
> There are commits where you were involved, targeting:
>
> * Add support for Librem 5 devkit
>
> * Add support for bootspec entries
> * Fix a corner case that makes flash-kerne
Package: flash-kernel
Version: 3.37
Severity: normal
Hello,
flash-kernel 3.37 introduced the following in flash-kernel:
+ # installation-report #781742 included:
+ # Can't find /boot/vmlinuz-[...] or /boot/initrd.img-[...]
+ #
+ # It's unclear how this can have happen
Package: flash-kernel
Version: 3.99
Severity: wishlist
Tags: patch
Hello,
barebox can boot from partitions that contain a so called
bootspec entry (or several of them). It would be great if flash-kernel
supported writing these. I already opened a merge request for
flash-kernel at
https:/
Package: debootstrap
Version: 1.0.114
Severity: minor
Hello,
I used deboostrap with --arch=armhf --foreign, then booted a system with
the resulting rootfs. The rootfs was mounted read-only. Then starting
the second stage looks as follows:
I have no name!@192:/# /debootstrap/debootstrap -
Hey Joey,
On 08/14/2018 04:16 PM, Joey Hess wrote:
> Uwe Kleine-König wrote:
>> Right, in theory the dtbs are independant from the kernel, but real life
>> is different. That's why the linux image packages ship their matchin
>> device trees. I don't know your setup,
Package: busybox
Version: 1:1.27.2-2
Severity: normal
Hello
user@host:~$ busybox microcom
Segmentation fault (core dumped)
reproduces on two different amd64 machines. Could also reproduce on an
armel porter machine (abel, in the sid schroot).
1:1.22.0-19+b3 isn't affected.
Best
Hello Joey,
On Thu, Feb 08, 2018 at 11:35:33AM -0400, Joey Hess wrote:
> Package: flash-kernel
> Version: 3.90
> Severity: normal
>
> There's a good chance that the devicetree file for one version of the
> kernel will not work with another version. I suspect this was the case,
> and confirmed it
Control: tag -1 + pending
Hello,
On Thu, Mar 09, 2017 at 08:34:24AM +0100, Marc Kleine-Budde wrote:
> On 03/09/2017 02:35 AM, Sebastian Reichel wrote:
> > On Wed, Mar 08, 2017 at 08:53:50PM +, Marc Kleine-Budde wrote:
> >> +Machine: TI OMAP4 PandaBoard-ES
> >> +Kernel-Flavors: armmp armmp-lpa
On Wed, Oct 05, 2016 at 10:09:30AM +0200, Uwe Kleine-König wrote:
> Hello again,
>
> On Wed, Oct 05, 2016 at 09:15:05AM +0200, Uwe Kleine-König wrote:
> > when booting the installer kernel + initramfs the kernel just hangs
> > after some time. Below is the complete boot log
Hello again,
On Wed, Oct 05, 2016 at 09:15:05AM +0200, Uwe Kleine-König wrote:
> when booting the installer kernel + initramfs the kernel just hangs
> after some time. Below is the complete boot log. After the last line the
> machine doesn't react at all, neither on normal key
Package: installation-reports
Severity: normal
Hello,
when booting the installer kernel + initramfs the kernel just hangs
after some time. Below is the complete boot log. After the last line the
machine doesn't react at all, neither on normal key presses nor on sysrq
stuff.
There are messages ab
Hi Martin,
On 02/18/2016 08:36 PM, Martin Michlmayr wrote:
> Uwe, does that look ok?
Yes, the rn104 entry is what I'm using, I'm just missing the
Kernel-Flavors line, which looks ok, too.
Do we need "Bootloader-Sets-Incorrect-Root: yes"? I modified the u-boot
env to pass the right root= and root
Control: tag 813995 + jessie sid
Hello,
among the supported machines (i.e. those in flash-kernel's db) there is
only a single type affected by this bug. That is "D-Link DNS-320 NAS
(Rev A1)" which has the respective mtd partitions on nand.
IMHO this means we should fix jessie's flash-kernel, too
Package: flash-kernel
Version: 3.35+deb8u2
Severity: critical
Justification: causes serious data loss
Control: block 806926 with -1
Hello,
when flash-kernel writes a kernel/initrd to NAND flash it uses plain
write(2) to /dev/mtdX (flash-kernel < 3.52) or flashcp
(flash-kernel >= 3.52). If the dev
Package: installation-reports
Version: 2.58
Severity: minor
Hello,
during installation of a PC from the pre-EFI area I was faced by a
dialog (grub-installer/force-efi-extra-removable) that reads:
It seems that this computer is configured to boot via EFI, but
[...]
I'm sure my ma
Package: virtinst
Version: 1:1.0.1-3
Followup-For: Bug #579138
Hello,
attached it an admittedly ugly patch[1] to make it possible to start an
installation from debian-jessie-DI-rc1-amd64-DVD-1.iso. The patch
applies on top of debian/1%1.0.1-4.
Best regards
Uwe
[1] I think part of the reason tha
Hello Ian,
Uwe, any chance you could try this please:
diff --git a/functions b/functions
index d45a4e6..a7ff6de 100644
--- a/functions
+++ b/functions
@@ -41,7 +41,11 @@ error() {
mtdblock() {
local mtdname="$1"
- sed -rn "s,^mtd([^:]*).*\"$mtdname\"\$,/dev/mtdblock\\1,p" "$PRO
Package: flash-kernel
Version: 3.28
Severity: normal
Hello,
on my ReadyNAS 104 (see database entry included below) a typical run
after a fresh reboot looks as follows:
$ sudo flash-kernel
Installing armada-370-netgear-rn104.dtb into /boot/dtb-3.16.0-4-armmp
Taking backup
tag 767744 + patch
quit
Hello,
On 11/03/2014 07:10 PM, Cyril Brulebois wrote:
> Ian Campbell (2014-11-03):
>> On Sun, 2014-11-02 at 12:08 +0100, Uwe Kleine-König wrote:
>>> Package: flash-kernel
>>> Version: 3.28
>>> Severity: wishlist
>>>
>&
Package: flash-kernel
Version: 3.28
Severity: wishlist
Hello,
I want to use flash-kernel on a machine that uses a device tree blob that isn't
included in the kernel package. So flash-kernel's assumption to find
/usr/lib/linux-image-$kvers/$dtb_id is wrong.
Maybe something like:
# if dtb
Hello,
On Thu, May 02, 2013 at 10:31:20PM +0200, Uwe Kleine-König wrote:
> I didn't test this
> patch yet because I still have to work out how to create an installer
> image with an updated libdebian-installer udeb, but sti
image with an updated libdebian-installer udeb, but still I think the
patch below does the trick.
->8---
From: Uwe Kleine-König
Date: Thu, 2 May 2013 22:18:35 +0200
Subject: [PATCH] subarch-arm-linux.c: add current kernel flavours and a match
for machines s
Package: debootstrap
Version: 1.0.37
Severity: normal
Hello,
currently there are two versions of perl-modules in sid:
$ apt-cache policy perl-modules
perl-modules:
Installed: 5.12.4-6
Candidate: 5.12.4-6
Version table:
5.14.2-5 0
ds
Uwe
--
Uwe Kleine-König
http://www.google.com/search?q=e+%5E+%28i+pi%29
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
31 matches
Mail list logo
