Bug#1033663: linux: reproducible-builds: Embedded build path in various binaries

On 2023-07-14, Ben Hutchings wrote: > On Wed, 2023-03-29 at 09:58 -0700, Vagrant Cascadian wrote: >> The build path is embedded in various binaries: >> >> >> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/diffoscope-results/linux.html

Bug#1033663: linux: reproducible-builds: Embedded build path in various binaries

On 2023-03-29, Vagrant Cascadian wrote: > The build path is embedded in various binaries: > > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/diffoscope-results/linux.html > > /usr/sbin/bpftool > > /build/1st/linux-6.1.20/tools/lib/bpf/libbpf.c:

Bug#1033663: linux: reproducible-builds: Embedded build path in various binaries

2001 From: Vagrant Cascadian Date: Tue, 28 Mar 2023 14:49:01 -0700 Subject: [PATCH 1/4] debian/rules.d/tools/bpf/bpftool/Makefile: Pass -ffile-prefix-map via EXTRA_CFLAGS. --- debian/rules.d/tools/bpf/bpftool/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian

Bug#1033301: linux: arm64 kernel size increased from 31 to 39 MB, causing u-boot-rpi to fail

Adding u-boot maintainers for rpi (Matthias Brugger, Peter Robinson) platforms and u-boot list to CC. On 2023-03-22, Salvatore Bonaccorso wrote: > Thanks for tracking this down. I would like to loop in Masahiro and > upstream to see if something can/should be done on upstream side. > > Masahiro,

Re: Assist in Development of Patch for Bug 1011542 - Missing phy-gmii-sel.ko Module in Debian Bullseye Installer for Armhf

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

Bug#1009858: linux: please consider building the modules necessary for the MNT Reform laptop

On 2022-04-24, Vagrant Cascadian wrote: > On 2022-04-19, Johannes Schauer Marin Rodrigues wrote: >> currently, we add the following to the arm64 kernel config provided by >> the Debian kernel packaging to build a kernel that powers the MNT Reform >> 2 open source laptop: &

Bug#1009858: linux: please consider building the modules necessary for the MNT Reform laptop

Control: tags 1009858 pending On 2022-04-24, Vagrant Cascadian wrote: > On 2022-04-19, Johannes Schauer Marin Rodrigues wrote: >> currently, we add the following to the arm64 kernel config provided by >> the Debian kernel packaging to build a kernel that powers the MNT Reform &

Bug#1009858: linux: please consider building the modules necessary for the MNT Reform laptop

On 2022-04-19, Johannes Schauer Marin Rodrigues wrote: > currently, we add the following to the arm64 kernel config provided by > the Debian kernel packaging to build a kernel that powers the MNT Reform > 2 open source laptop: Thanks! Merged most of the changes so far except... >

Bug#982270: Re Bug#982270 (installer can not find an ehternet driver for CuBox-i4Pro)

Control: tags 982270 pending On 2021-06-18, Vagrant Cascadian wrote: > On 2021-06-01, Vagrant Cascadian wrote: >> On 2021-06-01, Rick Thomas wrote: >>> Is there any estimate of when the assumed fix (linux/5.10.40-1) will >>> show up in the installer at [1] ? I'd lov

Bug#982270: Re Bug#982270 (installer can not find an ehternet driver for CuBox-i4Pro)

Control: tags 982270 confirmed On 2021-06-01, Vagrant Cascadian wrote: > On 2021-06-01, Rick Thomas wrote: >> Is there any estimate of when the assumed fix (linux/5.10.40-1) will >> show up in the installer at [1] ? I'd love to test it! > ... >> [1] https://d-i.debia

Bug#982270: Re Bug#982270 (installer can not find an ehternet driver for CuBox-i4Pro)

On 2021-06-01, Rick Thomas wrote: > Is there any estimate of when the assumed fix (linux/5.10.40-1) will > show up in the installer at [1] ? I'd love to test it! ... > [1] https://d-i.debian.org/daily-images/armhf/daily/netboot/SD-card-images/ It should already be there kernel version 5.10.38-1

Bug#988966: /boot/vmlinuz-5.10.0-6-armmp-lpae: lamobo-r1 ethernet/bridge failure

Package: src:linux Version: 5.10.28-1 Severity: normal File: /boot/vmlinuz-5.10.0-6-armmp-lpae X-Debbugs-Cc: vagr...@debian.org Control: block 986767 by -1 The ethernet bridge fails to work on 5.10.x (also tried 5.10.38-1), but works fine on 4.19.x from buster. (This was also reported in

Bug#982270: linux: [armhf] several imx6 systems unable to detect ethernet

On 2021-02-11, Vagrant Cascadian wrote: > 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 go

Bug#988574: linux-image-armmp-lpae: ethernet on orange pi plus does not work

Source: linux Version: 5.10.28-1 Severity: normal Tags: patch X-Debbugs-Cc: vagr...@reproducible-builds.org When upgrading the reproducible builds infrastructure to bullseye, on the orange pi plus ethernet stopped working with 5.10.x. Applying a fix from upstream for a similar board appears to

Bug#987638: linux-image-5.10.0-6-arm64: Missing kernel modules for Pine64's Pinebook Pro (usb-c, battery gauge, audio)

On 2021-04-27, Lionel Fourquaux wrote: > On Mon, Apr 26, 2021 at 11:19:29PM +0200, Vincent Blut wrote: >>A merge request [1] has been proposed today to improve support for the >>Pinebook >>Pro. > > Thanks! (The merge request and this report are related.) > > Some additional information: I

Re: Bug#982270: linux: [armhf] several imx6 systems unable to detect ethernet

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

Bug#973369: linux-image-5.9.0: No network at Banana Pi M3

On 2020-11-17, Salvatore Bonaccorso wrote: > On Mon, Nov 09, 2020 at 02:32:21PM +0100, Bernhard wrote: >> Regarding correction: >>

Bug#960152: linux-image-5.6.0-1-arm64: Enable compressed modules

Package: src:linux Version: 5.6.7-1 Severity: wishlist The on-disk kernel modules take up a significant amount of the package installation size, and most modules aren't actively used on any given system. In debian-installer, the "on-disk" modules take up space in ram during the installation.

Bug#946510: Support for accelerated graphics and video decoding on PINE A64+ in bullseye

Control: tags 946510 pending On 2019-12-14, Andrei POPESCU wrote: > On Vi, 06 dec 19, 19:57:07, Andrei POPESCU wrote: >> On Vi, 06 dec 19, 15:05:32, Marcin Juszkiewicz wrote: >> > Use Lima (Pine A64) or Panfrost (Rock64)? >> >> Sure... how? >> >> I changed my xorg.conf as per [1], but not

Re: Bug#926387: oxygen-icons5: FTBFS randomly (Directory renamed before its status could be extracted)

On 2019-06-07, Guillem Jover wrote: > On Tue, 2019-04-09 at 10:02:25 +0200, Santiago Vila wrote: >> Hmm, I said: >> > Is dpkg in buster calling tar with any options that makes this >> > behaviour to happen more easily? Is tar in buster more prone to this >> > failure when using overlayfs? >> >>

Bug#928451: linux: riscv64 updates (change kernel image type to flat image and enable vdso)

Control: tags 928451 pending On 2019-05-05, Karsten Merker wrote: > the riscv64 architecture is changing its standard kernel image > format from ELF to a flat kernel image with a PE/COFF-compatible > header (similar to arm64) to make EFI stub support possible, so > we need to ship

Bug#928457: arm64: please apply workaround for A64 timer instability

Control: tag 928457 pending On 2019-05-05, Andrei POPESCU wrote: > The Allwinner A64 is affected by a bug that makes the clock jump, > usually 95 years into the future. > > The mainline kernel contains a workaround merged for 5.1: >

Re: Fixing stretch debian-installer on armhf

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

Bug#913119: Bug#913138: linux-image-4.18.0-2-amd64: Hangs on lvm raid1

Control: tag 913138 pending Control: tag 913119 pending On 2019-02-26, martin wrote: > On 2019-02-26 21:11, Cesare Leonardi wrote: >> On 13/02/19 18:21, Dragan Milenkovic wrote: >>> This patch is already on its way to stable branches. I have tested it >>> and confirmed that it resolves the

Bug#923988: /boot/vmlinuz-4.19.0-2-arm64: dmidecode causes kernel panic (puma-rk3399)

Package: src:linux Version: 4.19.16-1 Severity: normal File: /boot/vmlinuz-4.19.0-2-arm64 X-Debbugs-Cc: klaus.go...@theobroma-systems.com When running dmidecode as root on puma-rk3399, it consistantly causes a kernel panic. Other similar rockchip rk3399 boards do not seem to have this problem.

Re: Fixing stretch debian-installer on armhf

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

Fixing stretch debian-installer on armhf

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

Bug#922478: upgrade linux-image-4.9.0-8-armmp-lpae:armhf from 4.9.130-2 to 4.9.144-3 renders many systems unbootable

On 2019-02-17, Vagrant Cascadian wrote: > On 2019-02-17, Timo Sigurdsson wrote: >> Cyril Brulebois schrieb am 17.02.2019 19:38: >>> Jürgen Löb (2019-02-16): > FWIW, I also built a local package from 4.9.155-1~ from salsa/stretch > git, and it worked on a wandboard quad

Bug#922478: upgrade linux-image-4.9.0-8-armmp-lpae:armhf from 4.9.130-2 to 4.9.144-3 renders many systems unbootable

Control: retitle 922478 upgrade linux-image-4.9.0-8-armmp-lpae:armhf from 4.9.130-2 to 4.9.144-3 renders many systems unbootable On 2019-02-17, Timo Sigurdsson wrote: > Cyril Brulebois schrieb am 17.02.2019 19:38: >> Jürgen Löb (2019-02-16): >>> Package: linux-image-4.9.0-8-armmp-lpae >>>

Bug#922478: have yet to find an armhf board that works with 4.9.144-3

After upgrading to the latest 4.9.x kernel in sid, all of the armhf boards running this kernel failed to boot. Adding to the list: imx6: Cubox-i4pro, Cubox-i4x4, Wandboard Quad exynos5: Odroid-XU4 exynos4: Odroid-U3 rk3328: firefly-rk3288 sunxi A20: Cubietruck So it clearly impacts a wide

Bug#906769: arm kernels fail to boot

On 2018-08-21, Salvatore Bonaccorso wrote: > armhf packages: > https://people.debian.org/~carnil/tmp/linux/armhf/ Looks good to me! Tested successfully on boards that previously failed: Cubietruck Firefly-rk3288 (2gb variant) Firefly-rk3288 (4gb variant) Jetson-TK1 Odroid-XU4 Odroid-U3 Also

Bug#906769: arm kernels fail to boot

On 2018-08-20, Vagrant Cascadian wrote: > I can confirm this on several machines in the reproducible builds zoo, > running linux-image-4.9.0-8-armmp-lpae version 4.9.110-3+deb9u3. > > What I've noticed is that machines running the "armmp" variant appear to > be unaff

Bug#886440: linux: Support to build linux-libc-dev for the upcoming riscv64 architecture

Control: tags 886440 pending On 2018-01-06, Manuel A. Fernandez Montecelo wrote: > 2018-01-06 18:15 GMT+01:00 Ben Hutchings : >> On Sat, 2018-01-06 at 01:09 +0100, Manuel A. Fernandez Montecelo wrote: >>> The 4.15 kernel comes with initial support for RISC-V. >>> >>> Enabling support to build

Bug#901159: linux-image-arm64: enable configuration options needed by Firefly-RK3399 board

Control: tags 901159 pending On 2018-06-09, Heinrich Schuchardt wrote: > to fully support the Firefly-RK3399 board, please, enable the following > configuration items for linux-image-arm64: > > CONFIG_DRM_ROCKCHIP > CONFIG_PHY_ROCKCHIP_TYPEC > CONFIG_ROCKCHIP_ANALOGIX_DP > CONFIG_ROCKCHIP_DW_HDMI

Bug#895490: cpufreq problems on Odroid-XU4.

Package: src:linux Version: 4.15.11-1 Severity: normal File: /lib/modules/4.15.0-2-armmp-lpae/kernel/drivers/cpufreq/cpufreq-dt.ko Accessing files in /sys regarding cpufreq stats doesn't appear to work. $ ls -l /sys/devices/system/cpu/cpufreq/policy0/stats/time_in_state -r--r--r-- 1 root

Bug#884061: This bug severely affects anybody using intel graphics cards from 2015

Control: fixed 884061 4.9.80-1 On 2018-01-22, Marga Manterola wrote: > This bug can make machines that include the affected graphics card > completely unusable. ... > Any chance we can get a new kernel without that commit? I can confirm 4.9.80-1 from stretch-proposed-updates fixes the issue for

Bug#884061: #884061: linux-image-4.9.0-4-amd64: screen scrolls wildly

least two users that makes the system almost unusable. From 4c01095ae53794023e772f9afb753bef67c3d84c Mon Sep 17 00:00:00 2001 From: Vagrant Cascadian <vagr...@debian.org> Date: Thu, 28 Dec 2017 11:21:30 -0800 Subject: [PATCH] Revert "drm/i915: Do not rely on wm preservation for ILK watermarks" This reverts commit 7d

Bug#884061: linux-image-4.9.0-4-amd64: screen scrolls wildly

On 2017-12-10, Vagrant Cascadian wrote: > Since upgrading to 4.9.65-3, my screen occasionally starts rapidly > scrolling sideways, flashing on and off repeatedly... ... > When this starts to happen, usually there is a log in the dmesg output > like this: > > [drm:gen8_irq_hand

Bug#884061: linux-image-4.9.0-4-amd64: screen scrolls wildly

Package: src:linux Version: 4.9.65-3 Severity: normal Since upgrading to 4.9.65-3, my screen occasionally starts rapidly scrolling sideways, flashing on and off repeatedly... looks almost like the refresh rate or sync was off, and it's displaying the leftmost part of the screen on the rightmost

Bug#879072: /boot/vmlinuz-4.14.0-rc5-arm64: eMMC corruption on Odroid-c2

Control: found 879072 4.14-1~exp1 On 2017-10-18, Vagrant Cascadian wrote: > I tried upgrading from 4.13 to the 4.14.0-rc5 kernel, and it caused eMMC > corruption, with messages like this scattered throughout the boot > process: > > [ 27.286913] mmcblk1: response CRC error

Bug#879072: /boot/vmlinuz-4.14.0-rc5-arm64: eMMC corruption on Odroid-c2

Package: src:linux Version: 4.14~rc5-1~exp1 Severity: normal File: /boot/vmlinuz-4.14.0-rc5-arm64 Control: found -1 4.14~rc3-1~exp1 I tried upgrading from 4.13 to the 4.14.0-rc5 kernel, and it caused eMMC corruption, with messages like this scattered throughout the boot process: [ 27.286913]

Bug#843448: linux-image-4.8.0-1-armmp-lpae: fails to boot on Odroid-Xu4 with rootfs on USB

Control: found 4.13.4-1 4.14~rc3-1~exp1 On 2017-10-02, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the src:linux package: > > #843448: linux-image-4.8.0-1-armmp-lpae: fails to boot on Odroid-Xu4 with > rootfs on USB

Bug#843448: linux-image-4.8.0-1-armmp-lpae: fails to boot on Odroid-Xu4 with rootfs on USB

On 2017-09-24, Jochen Sprickerhof wrote: > Finally I had the time and hardware available to look into this again > and found a better way to fix it. Applying the attached patch results in > a new exynos5422-odroidxu4.dtb that could simply be copied to /boot/dtbs/*/ > I've tested this with the

Bug#876035: linux: i386: i/o with PAE kernels and > 8GB ram

Source: linux Severity: important Version: 4.2 Tags: upstream Control: affects -1 jenkins.debian.org Control: block 875990 by -1 It seems that since linux 4.2, PAE systems suffer from severe i/o write performance issues on systems with more than 8GB of ram. The bug was probably there all along,

Bug#843448: linux-image-4.8.0-1-armmp-lpae: fails to boot on Odroid-Xu4 with rootfs on USB

On 2017-07-16, Vagrant Cascadian wrote: > On 2017-07-10, Vagrant Cascadian wrote: >> On 2017-07-08, Steinar H. Gunderson wrote: >>> On Sat, Jul 08, 2017 at 07:50:03AM +0200, Jochen Sprickerhof wrote: >>>> For v4.9 the only patch needed is: >>>> >>

Bug#843448: linux-image-4.8.0-1-armmp-lpae: fails to boot on Odroid-Xu4 with rootfs on USB

On 2017-07-10, Vagrant Cascadian wrote: > On 2017-07-08, Steinar H. Gunderson wrote: >> On Sat, Jul 08, 2017 at 07:50:03AM +0200, Jochen Sprickerhof wrote: >>> For v4.9 the only patch needed is: >>> >>> https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bu

Bug#843448: linux-image-4.8.0-1-armmp-lpae: fails to boot on Odroid-Xu4 with rootfs on USB

On 2017-07-08, Steinar H. Gunderson wrote: > On Sat, Jul 08, 2017 at 07:50:03AM +0200, Jochen Sprickerhof wrote: >> For v4.9 the only patch needed is: >> >>

Bug#843448: linux-image-4.8.0-1-armmp-lpae: fails to boot on Odroid-Xu4 with rootfs on USB

On 2017-07-07, Jochen Sprickerhof wrote: > I've created patches for v4.12 (applies to v4.11 as well) and git > master and send them to the subsystem maintainers. Would be great to see > them included in the Debian kernel as well. Thanks! Is this the only patch needed? Does it also need one of

Bug#860976: linux: [arm64] Enable support for Rockchip systems

On 2017-05-04, Vagrant Cascadian wrote: > On 2017-04-22, Vagrant Cascadian wrote: >> Please add the following options to enable Rockchip support on arm64. >> >> Tested on a firefly-rk3399 using linux 4.11.0-rc7 to boot stretch >> debian-installer. > > Updated patch

Bug#863907: Fix cross compilation build-dependencies for 4.9.x

Package: src:linux Version: 4.9.25-1 Severity: normal Please consider cherry-picking the following commit from the master branch to fix cross-compilation: commit 84e53d21c3676c8165e959687e3b9417e242400c Author: Ben Hutchings Date: Thu Feb 2 02:35:55 2017 +

Bug#843448: linux-image-4.8.0-1-armmp-lpae: fails to boot on Odroid-Xu4 with rootfs on USB

On 2017-05-27, Vagrant Cascadian wrote: > I've also got a BeagleBoard-X15 that works reasonably well without the > patch; will test the patched kernel to see if it appears to cause any > problems. Of course, the BeagleBoard-X15 isn't using USB for anything, so this isn't much of a test,

Bug#843448: linux-image-4.8.0-1-armmp-lpae: fails to boot on Odroid-Xu4 with rootfs on USB

On 2017-05-27, Steinar H. Gunderson wrote: > On Wed, May 24, 2017 at 11:37:36PM +0200, Steinar H. Gunderson wrote: >> Well, it's a revert of something that's supposed to only be a >> cleanup/refactor (but isn't, presumably due to phy bugs). So it _should_ be >> safe, at least in theory. >> >>

Bug#843448: linux-image-4.8.0-1-armmp-lpae: fails to boot on Odroid-Xu4 with rootfs on USB

On 2017-05-23, Steinar H. Gunderson wrote: > > https://github.com/hardkernel/linux/commit/74b9605e5587b30912d6b6093e9d7fb06d043c33 ... > I've applied the former patch (the revert) on top of Debian's 4.9.25 kernel > (linux-image-4.9.0-3-armmp-lpae), and it boots with working USB and thus >

Bug#860976: linux: [arm64] Enable support for Rockchip systems

On 2017-04-22, Vagrant Cascadian wrote: > Please add the following options to enable Rockchip support on arm64. > > Tested on a firefly-rk3399 using linux 4.11.0-rc7 to boot stretch > debian-installer. Updated patch, tested with 4.11.0-trunk: diff --git a/debian/config/arm64/con

Bug#860976: linux: [arm64] Enable support for Rockchip systems

Package: linux Version: 4.10.7-1~exp1 Severity: wishlist Tags: patch Please add the following options to enable Rockchip support on arm64. Tested on a firefly-rk3399 using linux 4.11.0-rc7 to boot stretch debian-installer. The device-tree used isn't yet in mainline, but I used patches from the

Bug#843448: linux-image-4.8.0-1-armmp-lpae: fails to boot on Odroid-Xu4 with rootfs on USB

On 2017-04-22, Vagrant Cascadian wrote: > On 2016-11-12, Ben Hutchings wrote: >> On Sun, 2016-11-06 at 10:00 -0800, Vagrant Cascadian wrote: >>> When upgrading to linux 4.8.x on an Odroid-XU4 system, it no longer >>> detects the USB sata adapter where rootfs is lo

Bug#843448: linux-image-4.8.0-1-armmp-lpae: fails to boot on Odroid-Xu4 with rootfs on USB

On 2016-11-12, Ben Hutchings wrote: > On Sun, 2016-11-06 at 10:00 -0800, Vagrant Cascadian wrote: >> When upgrading to linux 4.8.x on an Odroid-XU4 system, it no longer >> detects the USB sata adapter where rootfs is located. >> >> Downgrading to the 4.7.x kernel from

Bug#860855: linux: [arm64] Please add support for Allwinner boards (pine64)

Package: linux Version: 4.10.7-1~exp1 Severity: wishlist Tags: patch The following config options should enable support for basic SUNXI boards on arm64. Tested on Pine64+ board with MMC, USB and serial console working. Requires linux 4.11-rc+ for all of the features to work. diff --git

Bug#852132: linux-latest: Add support for Hardkernel Odroid-C2

On 2017-01-24, Heinrich Schuchardt wrote: > On 01/24/2017 05:47 PM, Ben Hutchings wrote: >> On Sat, 21 Jan 2017 21:00:18 +0100 Heinrich Schuchardt >> wrote: >>> please, add support for the Hardkernel Odroid C2 to the kernel >>> configuration. >>> >>> For 4.9 kernels this

Bug#845075: kernel-image-4.8.0-1-armmp-di: Lamobo R1 cannot access network

CONFIG_B53_SPI_DRIVER=y > > I think we already enabled the necessary options: > >   * [armhf] dsa: Enable drivers for Lamobo R1 (aka BPi-R1): B53, > B53_MDIO_DRIVER as modules (Closes: #836231, thanks to Vagrant Cascadian) > > From the device tree, it seems pretty cl

Bug#843448: linux-image-4.8.0-1-armmp-lpae: fails to boot on Odroid-Xu4 with rootfs on USB

Package: src:linux Version: 4.8.5-1 Severity: important When upgrading to linux 4.8.x on an Odroid-XU4 system, it no longer detects the USB sata adapter where rootfs is located. Downgrading to the 4.7.x kernel from jessie-backports works fine. I didn't see anything obviously missing when

Bug#840137: linux-image-4.7.0-1-armmp: Please add device-tree for imx53-usbarmory.

ej Rosano <and...@inversepath.com> Tested-by: Vagrant Cascadian <vagr...@debian.org> Signed-off-by: Shawn Guo <shawn...@kernel.org> --- arch/arm/boot/dts/Makefile| 1 + arch/arm/boot/dts/imx53-usbarmory.dts | 224 ++ 2 files changed, 225 insertions(+)

Bug#836251: linux: [armhf] Please enable support for veyron-speedy

On 2016-08-31, Vagrant Cascadian wrote: > Please enable support for veyron-speedy (a.k.a. ASUS Chromebook C201) > to linux 4.8.x. ... > Haven't had success getting output form the speakers or headphone > jack, though the OS seems to detect at least one device. headphone jack works,

Bug#837627: [armhf] linux-image-4.7.0-1-armmp: Enable options for Novena

Package: linux Version: 4.7.2-1 Severity: wishlist Tags: patch Please enable the following options to add support for hardware present on Novena systems. Thanks! live well, vagrant diff --git a/debian/config/armhf/config b/debian/config/armhf/config index 0a9be6f..d17e003 100644 ---

Bug#821027: Additional modules for HiKey support

On 2016-09-09, Ben Hutchings wrote: > On Fri, 2016-09-09 at 15:42 -0700, Vagrant Cascadian wrote: >> Unfortunately, I'm unable to get a serial console with both 4.7 and 4.8 >> (4.6 from jessie-backports gets a serial console, but not much >> else). After adding "earlycon

Bug#821027: Additional modules for HiKey support

On 2016-09-02, Martin Michlmayr wrote: > * Vagrant Cascadian <vagr...@debian.org> [2016-06-04 18:20]: ... > I enabled these (and some more) options in git, so please try out the > next upload to experimental. Thanks! Unfortunately, I'm unable to get a serial console with both 4

Bug#837110: linux: armhf: nic-modules: FTBFS: dwmac-socfpga module renamed to dwmac-altr-socfpga

Package: linux Version: 4.8~rc5-1~exp1 Severity: grave Tags: patch Justification: renders package unusable It appears the dwmac-socfpga module was renamed to dwmac-altr-socfpga in 4.8.x, in commit: commit fb3bbdb859891e6bc27fd1afb3a07319f82c2ee4 Author: Tien Hock Loh

Bug#711470: ath9k_htc updated firmware for firmware-linux-free

It seems like the biggest blocker is that building ath9k_htc requires building an entire (cross)toolchain. There is an open issue about getting ath9k_htc firmware into Debian at: https://github.com/qca/open-ath9k-htc-firmware/issues/90 These issues are also mentioned in an RFP for

Bug#836251: linux: [armhf] Please enable support for veyron-speedy

Package: linux Severity: wishlist Tags: patch Please enable support for veyron-speedy (a.k.a. ASUS Chromebook C201) to linux 4.8.x. It detects all four cores and 4GB of ram. Tested working HDMI, LCD panel, touchpad (w/ some multitouch), keyboard, microSD, cpufreq, battery and charger. All in

Bug#836231: linux: [armhf] Please enable B53 mdio switch driver

Source: linux Severity: wishlist Tags: patch Please enable the B53 mdio switch driver modules introduced in linux 4.8.x, which is used on the Lamobo-R1 (a.k.a. BPI-R1, Bananpi-R1). live well, vagrant diff --git a/debian/config/armhf/config b/debian/config/armhf/config index 0a9be6f..18d2f74

Bug#835893: linux-image-4.7.0-rc7-armmp: Please add support for OpenPandora

Package: linux-image-4.7.0-rc7-armmp Version: 4.7~rc7-1~exp1 Severity: wishlist Tags: patch Please enable the following options in the armhf kernel configuration, to enable support for the OpenPandora console. It's still a little rough around the edges but MMC, NAND, serial console, cpufreq, LCD

Bug#825139: linux-image-4.5.0-2-armmp: Please support Odroid-U3 (Exynos4)

On 2016-05-28, Roger Shimizu wrote: >> +## drivers/mfd/Kconfig >> +CONFIG_MFD_MAX77686=m >> + >> +## drivers/regulator/Kconfig >> +CONFIG_REGULATOR_MAX77686=m >> + >> +## drivers/rtc/Kconfig >> +CONFIG_RTC_DRV_MAX77686=m >> + >> +## drivers/mmc/host/Kconfig >> +CONFIG_MMC_SDHCI_S3C=m > > Thanks! >

Bug#825139: linux-image-4.5.0-2-armmp: Please support Odroid-U3 (Exynos4)

Package: src:linux Version: 4.5.4-1 Severity: wishlist Tags: patch Please enable the following options in the armmp kernel configuration, which enables support for Exynos4, tested on Odroid-U3. It detects all four CPUs, 2GB of ram, ethernet, and supports USB on both 4.5.x and 4.6.x. It also

Bug#820622: linux-image-4.5.0-trunk-armmp-lpae: raspberry pi 2: smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped

On 2016-05-02, Vagrant Cascadian wrote: > On 2016-05-02, Ben Hutchings wrote: >> On Sun, 2016-05-01 at 18:20 -0700, Vagrant Cascadian wrote: >>> On 2016-04-28, Ben Hutchings wrote: >>> > Could you test with turbo_mode re-enabled and with this patch applied? >>&g

Bug#820622: linux-image-4.5.0-trunk-armmp-lpae: raspberry pi 2: smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped

On 2016-05-02, Ben Hutchings wrote: > On Sun, 2016-05-01 at 18:20 -0700, Vagrant Cascadian wrote: >> On 2016-04-28, Ben Hutchings wrote: >> > Could you test with turbo_mode re-enabled and with this patch applied? >> > >> > Also could you test network rece

Bug#820622: linux-image-4.5.0-trunk-armmp-lpae: raspberry pi 2: smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped

Control: tag 820622 -moreinfo On 2016-04-28, Ben Hutchings wrote: > Could you test with turbo_mode re-enabled and with this patch applied? > > Also could you test network receive throughput (e.g. with netperf -t > TCP_STREAM, sending *to* the RPi) in these three different > configurations: Ok,

Bug#821311: linux-image-4.5.0-1-armmp-lpae: ethernet fails to detect carrier on Firefly boards

Control: notfound 821311 4.6~rc3-1~exp1 On 2016-04-17, Vagrant Cascadian wrote: > Running the 4.5.x kernel doesn't appear to have working carrier > detection on ethernet for the Firefly board. Earlier 4.4.x versions of > the kernel work fine. Well, at least the 4.6-rc3 kernel from exp

Bug#821311: linux-image-4.5.0-1-armmp-lpae: ethernet fails to detect carrier on Firefly boards

Package: src:linux Version: 4.5.1-1 Severity: important Running the 4.5.x kernel doesn't appear to have working carrier detection on ethernet for the Firefly board. Earlier 4.4.x versions of the kernel work fine. ~$ ip address show dev eth0 2: eth0: mtu 1500 qdisc noop

Bug#812540: [arm64] Additional modules for HiKey support

Control: clone 812540 -1 Control: retitle -1 [arm64] Additional modules for HiKey support Control: severity -1 wishlist On 2016-04-10, Vagrant Cascadian wrote: > I was able to get it to boot with both 4.4 and 4.5 to an initramfs > prompt and a serial console, but MMC support still

Bug#820622: linux-image-4.5.0-trunk-armmp-lpae: raspberry pi 2: smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped

On 2016-04-10, Vagrant Cascadian wrote: > On 2016-04-10, Ben Hutchings wrote: >> On Sun, 2016-04-10 at 22:49 +0200, Diederik de Haas wrote: >>> At https://plugwash.raspbian.org/linux_3.18/ you can find the things for >>> the  >>> latest raspbian.org kernel. >

Bug#820834: linux: [armhf] Please enable watchdog timer module for Firefly-RK3288

Source: linux Version: 4.5-1~exp1 Severity: wishlist Tags: patch Please enable the designware watchdog timer module, used on the Firefly-RK3288. Tested on 4.5, but is also available in 4.4.x and would be nice to have there too. diff --git a/debian/config/armhf/config.armmp

Bug#820622: linux-image-4.5.0-trunk-armmp-lpae: raspberry pi 2: smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped

On 2016-04-10, Vagrant Cascadian wrote: > On 2016-04-10, Ben Hutchings wrote: >> Vagrant, could you try putting "options smsc95xx turbo_mode=N" in >> /etc/modprobe.d/smsc95xx.conf ? > > Added to one of the two machines, updated the initramfs (just in case > t

Bug#820622: linux-image-4.5.0-trunk-armmp-lpae: raspberry pi 2: smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped

On 2016-04-10, Ben Hutchings wrote: > On Sun, 2016-04-10 at 22:49 +0200, Diederik de Haas wrote: >> At https://plugwash.raspbian.org/linux_3.18/ you can find the things for the  >> latest raspbian.org kernel. > > Thanks.  That has a patch to turn off the turbo_mode module parameter > by default. >

Bug#812540: Add ARCH_HISI for Lemaker HiKey support

On 2016-03-13, Ian Campbell wrote: > That makes sense, thanks for the info. Since MMC + serial in 4.4 is a > basically useful thing (and I'm hoping the WiFi is some preexisting > driver too) this seemed like a useful set of stuff to enable. So I have > done so in git. Thanks for enabling it! I

Bug#820622: linux-image-4.5.0-trunk-armmp-lpae: raspberry pi 2: smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped

On 2016-04-10, Ben Hutchings wrote: > On Sun, 2016-04-10 at 11:15 -0700, Vagrant Cascadian wrote: >> Thanks for enabling support for raspberry pi 2! > > Thanks for confirming it works, because I was working without any > access to hardware. For what it's worth, I've not been abl

Bug#820622: linux-image-4.5.0-trunk-armmp-lpae: raspberry pi 2: smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped

Package: src:linux Version: 4.5-1~exp1 Severity: normal Thanks for enabling support for raspberry pi 2! It works for the most part, but floods syslog with messages: [501966.870273] net_ratelimit: 35702 callbacks suppressed [501966.875438] smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped

Bug#819390: linux-image-4.5.0-trunk-armmp-lpae: Ethernet on Firefly-RK3288

Package: src:linux Version: 4.5-1~exp1 Severity: normal When upgrading to linux 4.5-1~exp1, the ethernet no longer responds correctly. Downgrading back to 4.4.6-1 from sid/stretch fixes the issue. I see these messages in syslog: Mar 27 21:25:37 ff2a systemd[1]: Reached target System Time

Bug#819379: linux: arrmp-lpae: Please support octa-core systems.

Source: linux Version: 4.5-1~exp1 Severity: wishlist Tags: patch Tested the following patch on an Odroid-XU4 to enable all 8 CPU cores. The options are also available on 4.4.x, but I haven't tested with that version. diff --git a/debian/config/armhf/config.lpae b/debian/config/armhf/config.lpae

Bug#819377: linux: Please enable watchdog timer module for Odroid-XU4.

Source: linux Version: 4.5-1~exp1 Severity: wishlist Tags: patch Please enable the watchdog timer used on Odroid-XU4 systems, and possibly others. Tested the following patch on an Odroid-XU4. The module is also available in 4.4.x, although I haven't tested it. diff --git

Bug#813881: linux-image-4.3.0-1-armmp install wrong dtb on Wandboard Quad Rev B1

On 2016-03-14, Ian Campbell wrote: > On Sun, 2016-02-07 at 19:50 -0800, Vagrant Cascadian wrote: >> On 2016-02-06, Heinrich Schuchardt wrote: >> > Booting with u-boot-imx requires imx6q-wandboard-revb1.dtb. >> > linux-image-4.3.0-1-armmp installs imx6q-wandboard.dtb &g

Bug#812540: Add ARCH_HISI for Lemaker HiKey support

On 2016-03-12, Ian Campbell wrote: > On Fri, 2016-03-11 at 20:03 -0800, Vagrant Cascadian wrote: >> On 2016-03-10, Martin Michlmayr wrote: >> > * Ian Campbell <i...@debian.org> [2016-01-25 09:57]: >> Most drivers aren't even available in 4.4.x, and some aren't even

Bug#812540: Add ARCH_HISI for Lemaker HiKey support

On 2016-03-10, Martin Michlmayr wrote: > * Ian Campbell [2016-01-25 09:57]: >> I suppose it will need more than just ARCH_HISI. Are you able to identify >> the full set of options (e.g. drivers and such) which are needed to make >> useful Lemaker support? If so I'd appreciate it

Bug#815848: linux: [armhf] udeb: Include modules needed on BeagleBoard-X15

Source: linux Version: 4.4.2-3 Severity: normal Tags: patch The following modules are needed to support USB disk installs on BeagleBoard-X15. diff --git a/debian/installer/armhf/modules/armhf-armmp/usb-modules b/debian/installer/armhf/modules/armhf-armmp/usb-modules index 7861c82..f82d68b

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

On 2016-02-24, Vagrant Cascadian wrote: > On 2016-02-04, Ben Hutchings wrote: >> Oh, so the MODULES=most case is bust and we need to list more host >> controller drivers (or include all modules under drivers/usb/host/). >> How about MODULES=dep; does that work now? > >

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

On 2016-02-04, Ben Hutchings wrote: > On Wed, 2016-02-03 at 15:43 -0800, Vagrant Cascadian wrote: >> On 2016-01-25, Ben Hutchings wrote: >> > On Thu, 12 Nov 2015 09:49:33 + Ian Campbell <i...@hellion.org.uk> >> > wrote: >> > > On Wed, 2015-

Bug#815476: linux: [armhf] udeb: Add modules needed on Firefly-RK3288.

On 2016-02-23, Vagrant Cascadian wrote: > With a couple more changes (there were some phy-usb modules missing), > the patch below adds the additional modules needed for rockchip and a > few others. Tried adding wildcards for the regulator modules, but was > unsuccessful. This p

Bug#815476: linux: [armhf] udeb: Add modules needed on Firefly-RK3288.

On 2016-02-22, Ben Hutchings wrote: > We need to either exclude the USB-attached MMC host controllers from > mmc-modules: > > ushc - > vub300 - That still needed more exclusions; I didn't track them all down... > or make mmc-modules depend on usb-modules. Adding usb-modules dependency worked

Bug#815476: linux: [armhf] udeb: Add modules needed on Firefly-RK3288.

On 2016-02-21, Ben Hutchings wrote: > On Sun, 2016-02-21 at 16:11 -0800, Vagrant Cascadian wrote: >> On 2016-02-21, Ben Hutchings wrote: >> > > --- a/debian/installer/armhf/modules/armhf-armmp/mmc-modules >> > > +++ b/debian/installer/armhf/modules/armhf-armm

Bug#815476: linux: [armhf] udeb: Add modules needed on Firefly-RK3288.

On 2016-02-21, Ben Hutchings wrote: >> --- a/debian/installer/armhf/modules/armhf-armmp/mmc-modules >> +++ b/debian/installer/armhf/modules/armhf-armmp/mmc-modules >> @@ -5,4 +5,5 @@ mmci >>  omap_hsmmc >>  sunxi-mmc >>  dw_mmc-exynos >> +dw_mmc-rockchip >>  sdhci-bcm2835 > > Would it make sense

Bug#815476: linux: [armhf] udeb: Add modules needed on Firefly-RK3288.

Source: linux Version: 4.4.2-2 Severity: normal Tags: patch The following modules are needed in order to support ethernet, USB, and MMC on Firefly-RK3288 in debian-installer. Please consider enabling them! live well, vagrant commit 60653f57a9eac67bfde342604fb0adf5b4e2d359 Author: Vagrant

  1   2   3   >