Re: USB on RPI4 8G (Was: Preliminary image for Raspberry Pi 4)
Lucas Nussbaum dijo [Fri, Jul 24, 2020 at 05:45:33PM +0200]: > I confirmed it works fine with a kernel built from the Debian kernel > team's git. For anyone needing a quick fix, a working kernel is > available at > https://people.debian.org/~lucas/rpi4/linux-image-5.8.0-rc6-arm64-unsigned_5.8~rc6-1~exp1_arm64.deb Great news! Looking forward to enable it for our builds.
USB on RPI4 8G (Was: Preliminary image for Raspberry Pi 4)
Hi, On 30/06/20 at 23:27 -0500, Gunnar Wolf wrote: > - However... There is a _very_ odd problem we will have to look into: > The image works fine in the 4GB version of the Rpi4. The 8GB version > does bring up wireless networking, but still does not manage to > enable USB :-( (we haven't yet seen reports for the 2GB version). I looked into this. This will be fixed in kernel 5.8. The patch serie is https://lkml.org/lkml/2020/5/5/998 I confirmed it works fine with a kernel built from the Debian kernel team's git. For anyone needing a quick fix, a working kernel is available at https://people.debian.org/~lucas/rpi4/linux-image-5.8.0-rc6-arm64-unsigned_5.8~rc6-1~exp1_arm64.deb Lucas
Re: Re: Preliminary image for Raspberry Pi 4
Just a heads-up for anyone who might be seeing this later while searching for pi4 images: images are now being auto-built. You should use those images rather than mine. I'll probably delete my images in a few months. https://gwolf.org/2020/07/raspberry-pi-4-now-running-your-favorite-distribution.html Get them from here: https://raspi.debian.net/tested-images/
Re: Re: Preliminary image for Raspberry Pi 4
Hello, jimmypierre.rouen.fra...@gmail.com dijo [Tue, Jun 30, 2020 at 01:55:25PM +0200]: > >>https://salsa.debian.org/dilinger/image-specs/-/commits/raspi4 > > >>5.7 works pretty well, with a USB keyboard and the wifi tested. Here's a > pi4 image that I built just now, for folks who don't want to do their own > build: > > >>https://people.debian.org/~dilinger/rpi4-20200626/ > > Just a line to report that the Pi3 B+ image from Gunnar worked well, Pi-Hole > is working fine as well as Wireguard on old kernel 4.9. > > I am writing because I have received a Pi 4 today, so before I venture with > the Pi-hole/Wireguard scenario, anything new that I need to know with the Pi > 4 image above please? > > Thanks Gunnar for your help! Just leaving this as probably valuable information for other people that want to try out Andres' images: - Some people, me included, have checked the image and are happy to report it works fine! - However... There is a _very_ odd problem we will have to look into: The image works fine in the 4GB version of the Rpi4. The 8GB version does bring up wireless networking, but still does not manage to enable USB :-( (we haven't yet seen reports for the 2GB version). Of course, we expect this to be easily fixable (but currently have no clue yet as to why it happens). There are a couple of issues to iron out before I think it's possible to enable the image to be autogenerated, but we are on the right track!
RE: Re: Preliminary image for Raspberry Pi 4
-Original Message- From: Andres Salomon Sent: 26 June 2020 09:05 To: lu...@debian.org Cc: debian-arm@lists.debian.org; gw...@debian.org Subject: Re: Re: Preliminary image for Raspberry Pi 4 Greetings, >>I've updated my branch to include a wifi fix: >>https://salsa.debian.org/dilinger/image-specs/-/commits/raspi4 >>5.7 works pretty well, with a USB keyboard and the wifi tested. Here's a pi4 image that I built just now, for folks who don't want to do their own build: >>https://people.debian.org/~dilinger/rpi4-20200626/ Just a line to report that the Pi3 B+ image from Gunnar worked well, Pi-Hole is working fine as well as Wireguard on old kernel 4.9. I am writing because I have received a Pi 4 today, so before I venture with the Pi-hole/Wireguard scenario, anything new that I need to know with the Pi 4 image above please? Thanks Gunnar for your help! Cheers, Jimmy
Re: Re: Preliminary image for Raspberry Pi 4
On Sun, May 10, 2020 at 22:52, Andres Salomon wrote: Hi Lucas, Thanks so much for your work on this! I took your older raspi_4.yaml and made it auto-generated, and just updated it now as well for the 5.6 boot fix. You can see that commit here: https://salsa.debian.org/dilinger/image-specs/-/commit/462abf1d43ca3c9037f9fc8a3a36674082dc2d0a That's now in my rpi4 branch, which I had previously requested that Gunnar merge. The MR fixed a minor bug and prepped the Makefile for adding and removing platforms. The merge request is here: https://salsa.debian.org/raspi-team/image-specs/-/merge_requests/9 I've updated my branch to include a wifi fix: https://salsa.debian.org/dilinger/image-specs/-/commits/raspi4 5.7 works pretty well, with a USB keyboard and the wifi tested. Here's a pi4 image that I built just now, for folks who don't want to do their own build: https://people.debian.org/~dilinger/rpi4-20200626/
Re: Re: Preliminary image for Raspberry Pi 4
Hi Lucas,
Thanks so much for your work on this! I took your older raspi_4.yaml
and made it auto-generated, and just updated it now as well for the 5.6
boot fix. You can see that commit here:
https://salsa.debian.org/dilinger/image-specs/-/commit/462abf1d43ca3c9037f9fc8a3a36674082dc2d0a
That's now in my rpi4 branch, which I had previously requested that
Gunnar merge. The MR fixed a minor bug and prepped the Makefile for
adding and removing platforms. The merge request is here:
https://salsa.debian.org/raspi-team/image-specs/-/merge_requests/9
Since the raspi_4.yaml is autogenerated, I've included a diff below
showing the difference between yours and mine. The main differences are
that I dropped experimental, I'm using the signed kernel images and
linux-image-arm64 from unstable, and the image size is 1.5gb instead of
2.5gb (not including stable + unstable images shrinks the size a bit).
--- /tmp/raspi_4.yaml 2020-05-10 22:09:56.793793902 -0400
+++ raspi_4.yaml2020-05-10 22:24:23.383962780 -0400
@@ -2,7 +2,7 @@
steps:
- mkimg: "{{ output }}"
-size: 2500M
+size: 1500M
- mklabel: msdos
device: "{{ output }}"
@@ -56,13 +56,9 @@
# Backports are _not_ enabled by default.
# Enable them by uncommenting the following line:
# deb http://deb.debian.org/debian buster-backports main contrib
non-free
- # unstable and experimental are used to fetch specific packages
using APT pinning
- deb http://deb.debian.org/debian unstable main contrib non-free
- deb http://deb.debian.org/debian experimental main contrib
non-free
-
+ deb http://deb.debian.org/debian/ unstable main contrib non-free
# raspi 4 needs the latest kernel (5.5 or higher) and raspi-firmware
newer than buster's
unless: rootfs_unpacked
-# Setup apt pinning
- chroot: /
shell: |
echo 'APT::Default-Release "stable";' > /etc/apt/apt.conf
@@ -77,9 +73,8 @@
- wireless-tools
- wpasupplicant
- raspi3-firmware/unstable
-- linux-image-arm64
+- linux-image-arm64/unstable
- firmware-brcm80211
-- linux-image-5.6.0-1-arm64-unsigned/unstable
tag: /
unless: rootfs_unpacked
@@ -116,14 +111,7 @@
# Copy the relevant device tree files to the boot partition
- chroot: /
shell: |
- install -m 644 -o root -g root
/usr/lib/linux-image-5.6.0-1-arm64/broadcom/bcm*rpi*.dtb /boot/firmware/
-
- # Do not set cma=. See
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951744#10
- - chroot: /
-shell: |
- sed -i 's/cma=$CMA //' /etc/kernel/postinst.d/z50-raspi-firmware
- sed -i 's/cma=64M //' /boot/firmware/cmdline.txt
-
+ install -m 644 -o root -g root
/usr/lib/linux-image-*-arm64/broadcom/bcm*rpi*.dtb /boot/firmware/
# Clean up archive cache (likely not useful) and lists (likely
outdated) to
# reduce image size by several hundred megabytes.
@@ -138,6 +126,8 @@
shell: |
ls -aR /boot
sed -i 's/.dev.mmcblk0p2/LABEL=RASPIROOT/'
/boot/firmware/cmdline.txt
+ sed -i 's/cma=64M //' /boot/firmware/cmdline.txt
+ sed -i 's/cma=$CMA //' /etc/kernel/postinst.d/z50-raspi-firmware
# TODO(https://github.com/larswirzenius/vmdb2/issues/24): remove
once vmdb
# clears /etc/resolv.conf on its own.
Re: Preliminary image for Raspberry Pi 4
Hi, Quick update on this. I updated https://salsa.debian.org/raspi-team/image-specs/-/blob/rpi4/raspi_4.yaml to use the 5.6 kernel. This required disabling the cma= setting on the kernel command line, that is set by raspi-firmware. (thanks to Bjørn Mork for noticing this). The next steps would be: - merge that branch - adjust raspi-firmware to avoid the cma= workaround - wait for #960129 (PCIE support, which blocks USB support) - wait for #960191 (thermal sensor support) Note: for wifi to work, I had to download https://github.com/RPi-Distro/firmware-nonfree/raw/master/brcm/brcmfmac43455-sdio.bin https://github.com/RPi-Distro/firmware-nonfree/raw/master/brcm/brcmfmac43455-sdio.txt https://github.com/RPi-Distro/firmware-nonfree/raw/master/brcm/brcmfmac43455-sdio.clm_blob to /lib/firmware/brcm/ Lucas On 26/04/20 at 21:58 +0200, Lucas Nussbaum wrote: > ( Ccing debian-arm for info ) > > Hi Gunnar, > > I (finally) wrapped up my work on building an RPI4 image. You will find > a suitable raspi_4.yaml file in > https://salsa.debian.org/raspi-team/image-specs/-/blob/rpi4/raspi_4.yaml > > I did not try merging it into the raspi_*.yaml generation script yet. I > don't think it's that useful at this point. > > It uses the 5.5 kernel from unstable, so only stuff that is listed as > working in 5.5 on https://github.com/lategoodbye/rpi-zero/issues/43 will > work. Most notably, USB does not work. > > I think that it could be added in its current state to > https://raspi.debian.net/ (I don't see any point in delaying this; early > testing would be great). > > I tested the image on the 2GB and 4GB variants. > > The main next step is to switch to linux 5.6, once it gets into > experimental (it was uploaded but failed to build, see > https://buildd.debian.org/status/logs.php?pkg=linux&arch=arm64 ). > > It would also be nice to use raspi-firmware and linux from > buster-backports once both are backported, but that's not a big issue > (pinning from unstable/experimental is probably fine for the time being). > > > I also did some work on booting with u-boot. See > https://salsa.debian.org/raspi-team/image-specs/-/blob/rpi4-wip/raspi_4.linux5.6_uboot.yaml > This ended up not being necessary for the RPI4, but I wonder if we > should switch to booting with u-boot for all images. > > I also noticed that you don't seem to use virt-sparsify (from > libguestfs-tools) to make the images smaller. It seems to save about 10% > off the .img.xz file. > > > My notes are on https://wiki.debian.org/RaspberryPi4 > > Lucas >
Re: Preliminary image for Raspberry Pi 4
Hello Florian, thanks for your work and the link. I have try to use the one from your repo. The rpi 4 hangs on the colored "init" screen and serial does show nothing. Are the images you provide patched against the rpi kernel? On 28.04.20 14:11, Florian La Roche wrote: > Hello Basti, > > the real error message must be earlier, if you sarch for "Error" (or > the German word "Fehler"). > > Current "master" from the Debian kernel branch builds fine for me. I > use the following script > on Debian testing (with native as well as cross-compile builds): > https://github.com/laroche/arm-devel-infrastructure/blob/master/vmdb2-debian/kernel56.sh > > A Debain kernel with also all raspbian patches applied can also be > compiled with the script and > such a compiled kernel can be downloaded from: > https://github.com/laroche/arm-devel-infrastructure/releases > (Caveat: I only have a RPi3, so this is not tested with Rpi4...) > > best regards, > > Florian La Roche >
Re: Preliminary image for Raspberry Pi 4
Hello basti, no that kernel is not installed onto the image, that is Debian-upstream until now. You could using a normal amd64-PC and change debian-rpi3-arm64.yaml to download and install this kernel for a read-to-use image. Maybe I'll add this for the next release image. best regards, Florian La Roche
Re: Preliminary image for Raspberry Pi 4
Hello Basti, the real error message must be earlier, if you sarch for "Error" (or the German word "Fehler"). Current "master" from the Debian kernel branch builds fine for me. I use the following script on Debian testing (with native as well as cross-compile builds): https://github.com/laroche/arm-devel-infrastructure/blob/master/vmdb2-debian/kernel56.sh A Debain kernel with also all raspbian patches applied can also be compiled with the script and such a compiled kernel can be downloaded from: https://github.com/laroche/arm-devel-infrastructure/releases (Caveat: I only have a RPi3, so this is not tested with Rpi4...) best regards, Florian La Roche
Re: Preliminary image for Raspberry Pi 4
On 27.04.20 21:20, Lucas Nussbaum wrote: >> debian/rules.gen and make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- >> defconfig like vanilla does not work. > > Did you find > https://salsa.debian.org/kernel-team/linux/-/blob/master/debian/README.source > ? > I did not try, but this seems like what should be followed. > > Lucas I have try to build like https://wiki.debian.org/HowToCrossBuildAnOfficialDebianKernelPackage This ends up in make[4]: *** [/backup_vm/debian-kernel/scripts/Makefile.build:510: net/ipv4] Error 2 make[3]: *** [/backup_vm/debian-kernel/Makefile:1696: net] Error 2 make[2]: *** [/backup_vm/debian-kernel/Makefile:180: sub-make] Error 2 make[2]: Leaving directory '/backup_vm/debian-kernel/debian/build/build_arm64_none_arm64' make[1]: *** [debian/rules.real:214: debian/stamps/build_arm64_none_arm64] Error 2 make[1]: Leaving directory '/backup_vm/debian-kernel' make: *** [debian/rules.gen:48: binary-arch_arm64_none_arm64_real] Error 2
Re: Preliminary image for Raspberry Pi 4
On 27/04/20 at 20:46 +0200, basti wrote: > Am 27.04.20 um 18:28 schrieb Lucas Nussbaum: > > On 27/04/20 at 15:30 +0200, basti wrote: > > > Hello lucas, > > > > > > thanks for the tip you provide there > > > (https://github.com/lategoodbye/rpi-zero/issues/43#issuecomment-619974846) > > > > > > As I can see in this Post here you have a working Image with Kernel 5.5 > > > without USB Support. I need the USB Support. So I try to Build a Image > > > with Kernel 5.6 with the result that the Image does not boot. > > > (see https://lists.debian.org/debian-arm/2020/04/msg00023.html) > > Did you try building 5.6 from the Debian kernel team git repo? > > https://salsa.debian.org/kernel-team/linux/-/tree/master > > > > There's a commit there that fixes the build failure that we are seeing > > in experimental. > > > Did you have some howto? i have try > https://wiki.debian.org/HowToCrossBuildAnOfficialDebianKernelPackage but the > is no > > debian/rules.gen and make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- > defconfig like vanilla does not work. Did you find https://salsa.debian.org/kernel-team/linux/-/blob/master/debian/README.source ? I did not try, but this seems like what should be followed. Lucas
Re: Preliminary image for Raspberry Pi 4
basti wrote: > It seems that the uboot is not build properly. The Serial console show a > lot of � (Replacement character). I was thinking it is because of the terminal type on the serial being vt100 or vt102 here. It shows not only on the RPi4
Re: Preliminary image for Raspberry Pi 4
Am 27.04.20 um 18:28 schrieb Lucas Nussbaum: On 27/04/20 at 15:30 +0200, basti wrote: Hello lucas, thanks for the tip you provide there (https://github.com/lategoodbye/rpi-zero/issues/43#issuecomment-619974846) As I can see in this Post here you have a working Image with Kernel 5.5 without USB Support. I need the USB Support. So I try to Build a Image with Kernel 5.6 with the result that the Image does not boot. (see https://lists.debian.org/debian-arm/2020/04/msg00023.html) Did you try building 5.6 from the Debian kernel team git repo? https://salsa.debian.org/kernel-team/linux/-/tree/master There's a commit there that fixes the build failure that we are seeing in experimental. Did you have some howto? i have try https://wiki.debian.org/HowToCrossBuildAnOfficialDebianKernelPackage but the is no debian/rules.gen and make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- defconfig like vanilla does not work.
Re: Preliminary image for Raspberry Pi 4
On 27/04/20 at 15:30 +0200, basti wrote: > Hello lucas, > > thanks for the tip you provide there > (https://github.com/lategoodbye/rpi-zero/issues/43#issuecomment-619974846) > > As I can see in this Post here you have a working Image with Kernel 5.5 > without USB Support. I need the USB Support. So I try to Build a Image > with Kernel 5.6 with the result that the Image does not boot. > (see https://lists.debian.org/debian-arm/2020/04/msg00023.html) Did you try building 5.6 from the Debian kernel team git repo? https://salsa.debian.org/kernel-team/linux/-/tree/master There's a commit there that fixes the build failure that we are seeing in experimental. > It seems that the uboot is not build properly. The Serial console show a > lot of � (Replacement character). U-boot should not be needed. Lucas
Re: Preliminary image for Raspberry Pi 4
Hello lucas, thanks for the tip you provide there (https://github.com/lategoodbye/rpi-zero/issues/43#issuecomment-619974846) As I can see in this Post here you have a working Image with Kernel 5.5 without USB Support. I need the USB Support. So I try to Build a Image with Kernel 5.6 with the result that the Image does not boot. (see https://lists.debian.org/debian-arm/2020/04/msg00023.html) It seems that the uboot is not build properly. The Serial console show a lot of � (Replacement character). basti
Preliminary image for Raspberry Pi 4
( Ccing debian-arm for info ) Hi Gunnar, I (finally) wrapped up my work on building an RPI4 image. You will find a suitable raspi_4.yaml file in https://salsa.debian.org/raspi-team/image-specs/-/blob/rpi4/raspi_4.yaml I did not try merging it into the raspi_*.yaml generation script yet. I don't think it's that useful at this point. It uses the 5.5 kernel from unstable, so only stuff that is listed as working in 5.5 on https://github.com/lategoodbye/rpi-zero/issues/43 will work. Most notably, USB does not work. I think that it could be added in its current state to https://raspi.debian.net/ (I don't see any point in delaying this; early testing would be great). I tested the image on the 2GB and 4GB variants. The main next step is to switch to linux 5.6, once it gets into experimental (it was uploaded but failed to build, see https://buildd.debian.org/status/logs.php?pkg=linux&arch=arm64 ). It would also be nice to use raspi-firmware and linux from buster-backports once both are backported, but that's not a big issue (pinning from unstable/experimental is probably fine for the time being). I also did some work on booting with u-boot. See https://salsa.debian.org/raspi-team/image-specs/-/blob/rpi4-wip/raspi_4.linux5.6_uboot.yaml This ended up not being necessary for the RPI4, but I wonder if we should switch to booting with u-boot for all images. I also noticed that you don't seem to use virt-sparsify (from libguestfs-tools) to make the images smaller. It seems to save about 10% off the .img.xz file. My notes are on https://wiki.debian.org/RaspberryPi4 Lucas
