Bug#900799: linux-image-arm64: dts: rockchip: correct voltage selector Firefly-RK3399
On 6/1/22 11:28, Diederik de Haas wrote: On Fri, 22 Jun 2018 21:58:30 +0100 Ben Hutchings wrote: Version: 4.17.2-1~exp1 On 5 Jun 2018 07:33:11 +0200 Heinrich Schuchardt wrote: Please, add this patch to the Debian kernel patches until it is added upstream. Cf. https://lkml.org/lkml/2018/6/4/781 This was applied in the above merge but not mentioned in the changelog due to a mis-merge. In response Heiko says in https://lkml.org/lkml/2018/6/19/1167: "and dropped again. Sadly it looks like the patch causes conflicts with at least one firefly board in a kernelci lab. My own is currently not ready to use, so I cannot look myself right now. The issue kernelci people described sounded quite a lot like the one in your commit message, so my current theory is that the suspend-voltage-selector must in some form corespond to the cpu_b_sleep_h gpio setting we're currently not handling at all, which would therefore depend on how the bootloader sets this up." It's also not part of current upstream master, so this is a DTS change that is specific for Debian and possibly not needed and/or incorrect? Heinrich, can you tell us more about the current status of this patch? I have not been working on the board in the last years. My impression at the time was that one would have to detect the current state of the board at runtime which matches what you wrote. Best regards Heinrich
Bug#864807: b53_mdio module doesn't get loaded automatically on Lamobo R1
On 5/15/21 3:15 PM, Salvatore Bonaccorso wrote: Hi, Is this bug still an issue with recent kernels or can the issue be closed? Regards, Salvatore I am not using this board anymore. Best regards Heinrich
Bug#976093: linux-image-5.9.0-3-arm64: Network failure NanoPi Neo Plus2
The NanoPi Neo Plus2 is struck by the same error. I just sent out a patch: arm64: dts: allwinner: H5: NanoPi Neo Plus2: phy-mode rgmii-id https://lore.kernel.org/linux-arm-kernel/20201129194512.1475586-1-xypron.g...@gmx.de/T/#u
Bug#976093: linux-image-5.9.0-3-arm64: Network failure Pine A64 LTS
Package: src:linux X-Debbugs-Cc: xypron.g...@gmx.de Version: 5.9.9-1 Severity: normal Tags: patch upstream Dear Maintainer, since Bullseye switched to Linux v5.9 my Pine A64 LTS board fails to boot via iSCSI. I have posted a patch upstream. Please, consider it for inclusion: [PATCH 1/1] arm64: dts: allwinner: A64 Sopine: phy-mode rgmii https://lore.kernel.org/linux-arm-kernel/20201129162627.1244808-1-xypron.g...@gmx.de/T/#u Best regards Heinrich -- Package-specific info: ** Version: Linux version 5.9.0-3-arm64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.0-17) 10.2.0, GNU ld (GNU Binutils for Debian) 2.35.1) #1 SMP Debian 5.9.9-1 (2020-11-19)
Bug#947356: Missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw
Today firmware-realtek (20200421-1) was made available for Bullseye but the file https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/rtl_nic/rtl8125a-3.fw is still missing. Why does the maintainer not simply include all files from rtl_nic/ into the package? Best regards Heinrich
Bug#949833: linux-image-5.4.0-3-arm64: MACCHIATObin fails to boot
Package: src:linux Version: 5.4.13-1 Severity: important Dear Maintainer, with kernel linux-image-5.4.0-3-arm64 the Marvell 8040 MACCHIATOBin Double-shot fails to boot. There is no problem to boot with linux-image-5.3.0-3-arm64. Kernel linux-image-5.4.0-3-arm64 boots when using the 5.3.0-3-arm64 device tree. -- Package-specific info: ** Kernel log: boot messages should be attached This is the console output with earlyprintk: Found U-Boot script /boot.scr 2315 bytes read in 5 ms (452.1 KiB/s) ## Executing script at 04d0 20899696 bytes read in 412 ms (48.4 MiB/s) 32099 bytes read in 14 ms (2.2 MiB/s) 38877506 bytes read in 763 ms (48.6 MiB/s) Booting Debian 5.4.0-3-arm64 from scsi 0:2... ## Flattened Device Tree blob at 04f0 Booting using the fdt blob at 0x4f0 Loading Ramdisk to 7d5e6000, end 7faf9942 ... OK Loading Device Tree to 7d5db000, end 7d5e5d62 ... OK Starting kernel ... [0.00] Booting Linux on physical CPU 0x00 [0x410fd081] [0.00] Linux version 5.4.0-3-arm64 (debian-kernel@lists.debian.org) (gcc version 9.2.1 20200104 (Debian 9.2.1-22)) #1 SMP Debian 5.4.13-1 (2020-01-19) [0.00] Machine model: Marvell 8040 MACCHIATOBin Double-shot [0.00] efi: Getting EFI parameters from FDT: [0.00] efi: UEFI not found. [0.00] cma: Reserved 64 MiB at 0xbc00 [0.00] NUMA: No NUMA configuration found [0.00] NUMA: Faking a node at [mem 0x-0x00043fff] [0.00] NUMA: NODE_DATA [mem 0x43dfc5800-0x43dfc6fff] [0.00] Zone ranges: [0.00] DMA32[mem 0x-0x] [0.00] Normal [mem 0x0001-0x00043fff] [0.00] Movable zone start for each node [0.00] Early memory node ranges [0.00] node 0: [mem 0x-0x03ff] [0.00] node 0: [mem 0x0420-0xbfff] [0.00] node 0: [mem 0x0001-0x00043fff] [0.00] Initmem setup node 0 [mem 0x-0x00043fff] [0.00] psci: probing for conduit method from DT. [0.00] psci: PSCIv1.1 detected in firmware. [0.00] psci: Using standard PSCI v0.2 function IDs [0.00] psci: MIGRATE_INFO_TYPE not supported. [0.00] psci: SMC Calling Convention v1.1 [0.00] percpu: Embedded 32 pages/cpu s93464 r8192 d29416 u131072 [0.00] Detected PIPT I-cache on CPU0 [0.00] CPU features: detected: EL2 vector hardening [0.00] Speculative Store Bypass Disable mitigation not required [0.00] Built 1 zonelists, mobility grouping on. Total pages: 4128264 [0.00] Policy zone: Normal [0.00] Kernel command line: earlyprintk iommu=soft [0.00] Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear) [0.00] Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear) [0.00] mem auto-init: stack:off, heap alloc:off, heap free:off [0.00] software IO TLB: mapped [mem 0xb800-0xbc00] (64MB) [0.00] Memory: 16264480K/16775168K available (10044K kernel code, 1720K rwdata, 3544K rodata, 5056K init, 544K bss, 445152K reserved, 65536K cma-reserved) [0.00] random: get_random_u64 called from __kmem_cache_create+0x4c/0x5c8 with crng_init=0 [0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [0.00] ftrace: allocating 35366 entries in 139 pages [0.00] rcu: Hierarchical RCU implementation. [0.00] rcu: RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=4. [0.00] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies. [0.00] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4 [0.00] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0 [0.00] GIC: Adjusting CPU interface base to 0xf022f000 [0.00] GIC: Using split EOI/Deactivate mode [0.00] GICv2m: DT overriding V2M MSI_TYPER (base:160, num:32) [0.00] GICv2m: range[mem 0xf028-0xf0280fff], SPI[160:191] [0.00] GICv2m: DT overriding V2M MSI_TYPER (base:192, num:32) [0.00] GICv2m: range[mem 0xf029-0xf0290fff], SPI[192:223] [0.00] GICv2m: DT overriding V2M MSI_TYPER (base:224, num:32) [0.00] GICv2m: range[mem 0xf02a-0xf02a0fff], SPI[224:255] [0.00] GICv2m: DT overriding V2M MSI_TYPER (base:256, num:32) [0.00] GICv2m: range[mem 0xf02b-0xf02b0fff], SPI[256:287] [0.00] arch_timer: cp15 timer(s) running at 25.00MHz (phys). [0.00] clocksource: arch_sys_counter: mask: 0xff max_cycles: 0x5c40939b5, max_idle_ns: 440795202646 ns [0.01] sched_clock: 56 bits at 25MHz, resolution 40ns, wraps every 4398046511100ns [0.000197] Console: colour dummy device 80x25 [0.000343] printk: console [tty0] enabled [0.000384] Calibrating delay loop
Bug#949825: linux-image-arm64: add CONFIG_BCMGENET=m
Package: linux-image-arm64
Version: 5.5~rc5+1~exp1
Severity: wishlist
Dear Maintainer,
the Raspberry Pi 4 has in the dtb:
ethernet@7d58 {
compatible = "brcm,bcm2711-genet-v5";
Cf. arch/arm/boot/dts/bcm2711.dtsi
To provide the driver for Ethernet, please, enable
CONFIG_BCMGENET=m
Cf. drivers/net/ethernet/broadcom/genet/bcmgenet.c
Best regards
Heinrich Schuchardt
Bug#947356: realtek-firmware: missing rtl8125a-3.fw
This driver for the RTL8125 2.5GbE Controller is in Debian kernel linux-image-5.4.0-trunk-amd64 Best regards Heinrich
Bug#947356: realtek-firmware: missing rtl8125a-3.fw
Package: firmware-realtek Version: 20190717-2 Severity: normal Tags: upstream Dear maintainer, file rtl8125a-3.fw required for the Realtek 8125 is missing in the package. Kindly update the package from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/rtl_nic/ Best regards Heinrich
Bug#939681: linux-image-5.2.0-2-armmp-lpae: Enable serial console on Raspberry Pi 3 Model B Plus Rev 1.3
Package: src:linux Version: 5.2.9-2 Severity: normal Dear Maintainer, with the 32bit kernel I do not have a serial console on my RPi 3B+. The serial console works fine with the 64bit kernel. Please, add the missing configuration items to enable the console: SERIAL_8250_EXTENDED=y SERIAL_8250_SHARE_IRQ=y SERIAL_8250_BCM2835AUX=y Best regards Heinrich -- Package-specific info: ** Version: Linux version 5.2.0-2-armmp-lpae (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-21)) #1 SMP Debian 5.2.9-2 (2019-08-21)
Bug#910727: Overlays cannot be applied to dtbs - missing DTC_FLAGS='-@'
Package: linux-source Version: 4.18+98 Priority: wishlist Many boards like the Odroid-C2 come with optional add on boards. E.g. for the Odroid C2 there is an RTC module. The overlays can be applied by U-Boot using the 'fdt apply' command. For successful application of device tree overlays the dtb files must be built with the environment variable DTC_FLAGS='-@'. This flag adds a __symbols__ section to the dtb file. Unfortunately the flag '-@' is not set for packages linux-image-arm64 and linux-image-armhf. Pleae, adjust the build rules. Best regards Heinrich Schuchardt
Bug#900799: Fwd: Re: [PATCH 1/1] arm64: dts: rockchip: correct voltage selector Firefly-RK3399
The patch has been accepted by the upstream maintainer. https://lkml.org/lkml/2018/6/14/365 Forwarded Message applied for 4.19. I've amended your commit message with the info from your reply about the vendor kernel using the same value and added an appropriate Fixes tag to possibly get it merged into stable. Thanks Heiko
Bug#901159: linux-image-arm64: enable configuration options needed by Firefly-RK3399 board
Package: linux-latest Version: 94 Severity: wishlist Dear maintainer, 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 CONFIG_ROCKCHIP_DW_MIPI_DSI CONFIG_ROCKCHIP_EFUSE CONFIG_ROCKCHIP_IOMMU CONFIG_ROCKCHIP_SARADC CONFIG_ROCKCHIP_THERMAL The corresponding drivers are selected by the device tree. Best regards Heinrich Schuchardt
Bug#900799: linux-image-arm64: dts: rockchip: correct voltage selector Firefly-RK3399
Package: linux-image-arm64
Version: 4.16.12-1
Severity: normal
Tags: patch
Please, add this patch to the Debian kernel patches until it is added
upstream. Cf.
https://lkml.org/lkml/2018/6/4/781
Without this patch the Firefly-RK3399 board boot process hangs after these
lines:
fan53555-regulator 0-0040: FAN53555 Option[8] Rev[1] Detected!
fan53555-reg: supplied by vcc_sys
vcc1v8_s3: supplied by vcc_1v8
Blacklisting driver fan53555 allows booting.
The device tree uses a value of fcs,suspend-voltage-selector different to
any other board.
Changing this setting to the usual value is sufficient to enable booting.
Signed-off-by: Heinrich Schuchardt
---
arch/arm64/boot/dts/rockchip/rk3399-firefly.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/boot/dts/rockchip/rk3399-firefly.dts
b/arch/arm64/boot/dts/rockchip/rk3399-firefly.dts
index 4f28628aa091..50940ef844a7 100644
--- a/arch/arm64/boot/dts/rockchip/rk3399-firefly.dts
+++ b/arch/arm64/boot/dts/rockchip/rk3399-firefly.dts
@@ -458,7 +458,7 @@
vdd_cpu_b: regulator@40 {
compatible = "silergy,syr827";
reg = <0x40>;
- fcs,suspend-voltage-selector = <0>;
+ fcs,suspend-voltage-selector = <1>;
regulator-name = "vdd_cpu_b";
regulator-min-microvolt = <712500>;
regulator-max-microvolt = <150>;
--
2.17.1
Bug#897163: Remove CONFIG_SYSTEM_TRUSTED_KEYS="debian/certs/b...@debian.org.cert.pem"
Package: linux-image-amd64 Version: 4.15+91~bpo9+1 Severity: normal Tags: security The Debian kernels are currently built with CONFIG_SYSTEM_TRUSTED_KEYS="debian/certs/b...@debian.org.cert.pem" This was introduced with https://alioth-lists-archive.debian.net/pipermail/kernel-svn-changes/2016-April/022904.html We are now two years after Ben's contribution and we are still not using kernel module signing (CONFIG_MODULE_SIG is not set in config). As there is no need for the kernel trusting Ben's certificate, please, remove the setting. Best regards Heinrich Schuchardt -- System Information: Debian Release: 9.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (100, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: arm64, armhf, i386 Kernel: Linux 4.15.0-0.bpo.2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-image-amd64 depends on: ii linux-image-4.15.0-0.bpo.2-amd64 4.15.11-1~bpo9+1 linux-image-amd64 recommends no packages. linux-image-amd64 suggests no packages. -- no debconf information
Bug#888537: linux-image-4.14.0-3-arm64: BUG: Bad page state in process cc1 pfn:75cbd
Package: src:linux Version: 4.14.13-1 Severity: normal Dear Maintainer, I am running an Odroid C2 on iSCSI. Under heavy load I see bad page errors like the ones below. This is not gcc specific. Same happens when git is handling large repositories. The reserved memory matches my firmware. reserved-memory/secmon@1000/reg 00 00 00 00 10 00 00 00 00 00 00 00 00 20 00 00 reserved-memory/hwrom@0/reg 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00 Please, give advice for further analysis. Best regards Heinrich Schuchardt -- Package-specific info: ** Version: Linux version 4.14.0-3-arm64 (debian-kernel@lists.debian.org) (gcc version 7.2.0 (Debian 7.2.0-19)) #1 SMP Debian 4.14.13-1 (2018-01-14) ** Command line: BOOT_IMAGE=/vmlinuz-4.14.0-3-arm64 root=UUID=afa724eb-deb7-4779-ba7d-b6553f4e34d3 ro quiet ** Tainted: B (32) * System has hit bad_page. ** Kernel log: [ 11.936949] systemd[1]: File /lib/systemd/system/systemd-journald.service:35 configures an IP firewall (IPAddressDeny=any), but the local system does not support BPF/cgroup based firewalling. [ 11.936958] systemd[1]: Proceeding WITHOUT firewalling in effect! (This warning is only shown for the first loaded unit using IP firewalling.) [ 12.105689] systemd[1]: dev-disk-by\x2duuid-84185ebb\x2d74ba\x2d4879\x2d93ba\x2d56adcdfbe8c7.device: Dependency Before=network-online.target ignored (.device units cannot be delayed) [ 12.105705] systemd[1]: dev-disk-by\x2duuid-84185ebb\x2d74ba\x2d4879\x2d93ba\x2d56adcdfbe8c7.device: Dependency Before=network.target ignored (.device units cannot be delayed) [ 12.109332] systemd[1]: dev-disk-by\x2duuid-1F97\x2dB63B.device: Dependency Before=network-online.target ignored (.device units cannot be delayed) [ 12.109347] systemd[1]: dev-disk-by\x2duuid-1F97\x2dB63B.device: Dependency Before=network.target ignored (.device units cannot be delayed) [ 12.115281] systemd[1]: Created slice System Slice. [ 12.270402] EXT4-fs (sda3): re-mounted. Opts: errors=remount-ro [ 12.326234] systemd-journald[225]: Received request to flush runtime journal from PID 1 [ 12.365796] iscsi: registered transport (iser) [ 12.609622] EFI Variables Facility v0.08 2004-May-17 [ 12.609640] efivars: get_next_variable: status=8007 [ 12.611877] pstore: using zlib compression [ 12.611894] pstore: Registered efi as persistent store backend [ 12.719455] scsi 0:0:0:0: Attached scsi generic sg0 type 12 [ 12.719557] sd 0:0:0:1: Attached scsi generic sg1 type 0 [ 13.215460] audit: type=1400 audit(1513289398.720:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=332 comm="apparmor_parser" [ 13.215471] audit: type=1400 audit(1513289398.720:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man//filter" pid=332 comm="apparmor_parser" [ 13.215477] audit: type=1400 audit(1513289398.720:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man//groff" pid=332 comm="apparmor_parser" [ 13.252407] audit: type=1400 audit(1513289398.756:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/ntpd" pid=333 comm="apparmor_parser" [ 13.971676] random: crng init done [ 16.601127] audit: type=1400 audit(1513289402.104:6): apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" name="/usr/local/sbin/" pid=382 comm="ntpd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 16.601139] audit: type=1400 audit(1513289402.104:7): apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" name="/usr/local/bin/" pid=382 comm="ntpd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 16.803865] EXT4-fs (sda2): mounting ext2 file system using the ext4 subsystem [ 16.811713] EXT4-fs (sda2): mounted filesystem without journal. Opts: (null) [ 16.920231] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. [ 1609.725807] BUG: Bad page state in process cc1 pfn:75cbd [ 1609.725859] page:7e0001d72f40 count:0 mapcount:0 mapping: (null) index:0x4 [ 1609.733512] flags: 0x0460320(lru|slab|owner_priv_1|reclaim|swapbacked) [ 1609.740671] raw: 00460320 0004 [ 1609.748345] raw: dead0100 dead0200 [ 1609.756018] page dumped because: PAGE_FLAGS_CHECK_AT_PREP flag set [ 1609.762137] bad because of flags: 0x60320(lru|slab|owner_priv_1|reclaim|swapbacked) [ 1609.769727] Modules linked in: nls_ascii nls_cp437 vfat fat meson_drm meson_saradc drm_kms_helper industr
Bug#880615: linux-latest: systemd complains about CONFIG_BPF_SYSCALL not being set
The systemd documentation at https://github.com/systemd/systemd/blob/master/README states: Required for IPAddressDeny= and IPAddressAllow= in resource control unit settings: CONFIG_CGROUP_BPF Please, enable this in the kernel configuration. Best regards Heinrich Schuchardt
Bug#883023: linux-image-armmp: enable CONFIG_IMX_THERMAL=m
Package: linux-image-4.13.0-1-armmp Version: 4.13.13-1 Severity: wishlist Dear Maintainer, the i.MX6 CPU has a thermal sensor. To use it the appropriate kernel module has to be built. Please, enable CONFIG_IMX_THERMAL=m Best regards Heinrich Schuchardt -- System Information: Debian Release: 9.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: armhf (armv7l) Kernel: Linux 4.9.0-4-armmp (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#877246: linux-image-arm64: rk3399-firefly.dtb missing
Package: src:linux Version: 4.12.13-1 Severity: normal Dear Maintainer, file linux-arm64/usr/lib/linux-image-4.12.0-2-arm64/rockchip/rk3399-firefly.dtb is missing in package linux-image-4.12.0-2-arm64. This leads to an error in flash-kernel. Please, add the missing file in the next version. Best regards Heinrich Schuchardt -- Package-specific info: ** Version: -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: arm64 (aarch64) Kernel: Linux 4.12.0-2-arm64
Bug#837809: [drm:si_dpm_set_power_state [radeon]] *ERROR* si_restrict_performance_levels_before_s
The message still occurs with Stretch kernel 4.9.0-3-amd64. [ +0.000192] fbcon: radeondrmfb (fb0) is primary device [ +0.179799] [drm:si_dpm_set_power_state [radeon]] *ERROR* si_restrict_performance_levels_before_s [ +0.122488] Console: switching to colour frame buffer device 480x135 [ +0.087282] radeon :01:00.0: fb0: radeondrmfb frame buffer device [ +0.094945] [drm] Initialized radeon 2.48.0 20080528 for :01:00.0 on minor 0 The message is created in drivers/gpu/drm/radeon/si_dpm.c if si_restrict_performance_levels_before_switch fails. My graphics adapter is 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X] (prog-if 00 [VGA controller]) xset dpms force standby works fine on my system. Regards Heinrich Schuchardt
Bug#864807: b53_mdio module doesn't get loaded automatically on Lamobo R1
The following is necessary to get a running network on the Lamobo R1 with a current kernel: Load the b53_mdio module, file /etc/modules: # /etc/modules: kernel modules to load at boot time. # # This file contains the names of kernel modules that should be loaded # at boot time, one per line. Lines beginning with "#" are ignored. b53_mdio Define a bridge, file /etc/network/interfaces.d/br0: auto br0 iface br0 inet dhcp Setup the switch. With the commands below all ports are connected together in the same vlan. For usage as a router we would have to create at least two vlans. One for the wan port and one for ports lan1-lan4. Maybe we should create a package with different configuration files for the switch which the user can choose from. File /etc/network/if-pre-up.d/switch (chmod 755): #!/bin/sh # # Setup interfaces and VLANs # Reset eth0 ip link set eth0 down ip addr flush eth0 ip link set eth0 up # Create VLAN 101 on interface eth0: eth0.101 ip link add link eth0 name eth0.101 type vlan id 101 # Create bridge br0 as disabled for STP (Spanning Tree Protocol). ip link add br0 type bridge ip link set dev br0 type bridge stp_state 0 bridge vlan # Assign ports to bridge ip link set lan1 master br0 bridge vlan add vid 101 dev lan1 pvid untagged bridge vlan add vid 101 dev lan1 pvid untagged self ip link set lan1 up ip link set lan2 master br0 bridge vlan add vid 101 dev lan2 pvid untagged bridge vlan add vid 101 dev lan2 pvid untagged self ip link set lan2 up ip link set lan3 master br0 bridge vlan add vid 101 dev lan3 pvid untagged bridge vlan add vid 101 dev lan3 pvid untagged self ip link set lan3 up ip link set lan4 master br0 bridge vlan add vid 101 dev lan4 pvid untagged bridge vlan add vid 101 dev lan4 pvid untagged self ip link set lan4 up ip link set wan master br0 bridge vlan add vid 101 dev wan pvid untagged bridge vlan add vid 101 dev wan pvid untagged self ip link set wan up ip link set eth0.101 master br0 bridge vlan add vid 101 dev eth0.101 pvid untagged bridge vlan add vid 101 dev eth0.101 pvid untagged self ip link set eth0.101 up bridge vlan Best regards Heinrich Schuchardt
Bug#864807: debian-installer: Lamobo R1 requires modprobe b53_mdio
On 06/15/2017 12:57 PM, Karsten Merker wrote: > Cyril Brulebois wrote: >> On Thu, Jun 15, 2017 at 10:43:18AM +0100, Ben Hutchings wrote: >>> Control: tag -1 moreinfo >>> >>> On Thu, 2017-06-15 at 08:34 +0200, Heinrich Schuchardt wrote: >>>> Package: debian-installer >>>> Version: stretch >>>> Severity: normal >>>> >>>> Dear Maintainer, >>>> >>>> the Lamobo R1 is an Arm system based on the Amlogic A20. >>>> The network interface of the A20 is connected to a switch. >>>> If the switch is not configured there is no external >>>> network access and subsequently a network install fails. >>>> >>>> On an installed system it is sufficient to have a line >>>> in /etc/modules: >>>> b53_mdio >>>> >>>> I suggest the following corrections to the installer: >>>> >>>> The initrd.img should include the b53_mdio module and its >>>> prerequisites b53_common and dsa_core plus aforementioned >>>> file /etc/modules. >>>> >>>> The installer should compare the content of >>>> /proc/device-tree/model >>>> to the string >>>> Lamobo R1 >>>> >>>> If this string is found, the file /etc/modules should be >>>> appended with b53_mdio on the installed system. >>> >>> Why is this necessary? It should load automatically. >> >> Because of missing i2c? Lamobo R1 is listed here: >> https://bugs.debian.org/864536#15 >> >> (Didn't check the recursive list of dependencies though.) > > If I understood the original submitter correctly, the problem > also exists in the installed system, not only in d-i. The > i2c-modules udeb issue (or other modules unavailable in the udebs > but available in the regular kernel deb) would explain problems > inside d-i, but not in the installed system. > > Heinrich, can you clarify on that? > > Regards, > Karsten > Yes, the problems exists both in the installer and in an installed system. I set up the installed system via debootstrap: https://github.com/xypron/debian-image-lamobo-r1/commit/8fa1b7cb3a0cc2bfd44475d0c9972115ffb82e15 Best regards Heinrich Schuchardt
Bug#864807: debian-installer: Lamobo R1 requires modprobe b53_mdio
On 06/15/2017 11:43 AM, Ben Hutchings wrote: > Control: tag -1 moreinfo > > On Thu, 2017-06-15 at 08:34 +0200, Heinrich Schuchardt wrote: >> Package: debian-installer >> Version: stretch >> Severity: normal >> >> Dear Maintainer, >> >> the Lamobo R1 is an Arm system based on the Amlogic A20. >> The network interface of the A20 is connected to a switch. >> If the switch is not configured there is no external >> network access and subsequently a network install fails. >> >> On an installed system it is sufficient to have a line >> in /etc/modules: >> b53_mdio >> >> I suggest the following corrections to the installer: >> >> The initrd.img should include the b53_mdio module and its >> prerequisites b53_common and dsa_core plus aforementioned >> file /etc/modules. >> >> The installer should compare the content of >> /proc/device-tree/model >> to the string >> Lamobo R1 >> >> If this string is found, the file /etc/modules should be >> appended with b53_mdio on the installed system. > > Why is this necessary? It should load automatically. > > Ben. > The device tree has a string: compatible = "brcm,bcm53125" Same string is in the b53_mdio MODULE_DEVICE_TABLE. So I would have guessed it should create a match in b53_mdio.c. But with linux-image-4.9.0-3-armmp the module is not loaded automatically. I have tested as follows: Remove b53_mdio from /etc/modules. sudo update-initramfs -k $(uname -r) -u sudo reboot ==> no network address assigned by DHCP sudo modprobe b53_mdio results in output b53_common: found switch: BCM53125, rev 4 Add b53_mdio to /etc/modules. sudo update-initramfs -k $(uname -r) -u sudo reboot ==> Network is available dmesg has these lines: [ +0.325134] libphy: mdio_driver_register: bcm53xx [ +0.005595] b53_common: found switch: BCM53125, rev 4 [ +0.013589] DSA: switch 0 0 parsed [ +0.003438] DSA: tree 0 parsed Best regards Heinrich signature.asc Description: OpenPGP digital signature
Bug#852132: linux-latest: Add support for Hardkernel Odroid-C2
On 01/24/2017 05:47 PM, Ben Hutchings wrote: > On Sat, 21 Jan 2017 21:00:18 +0100 Heinrich Schuchardt > <xypron.g...@gmx.de> wrote: >> Package: linux-latest >> Severity: wishlist >> >> Dear Maintainer, >> >> please, add support for the Hardkernel Odroid C2 to the kernel configuration. >> >> For 4.9 kernels this involves: >> >> CONFIG_ARCH_MESON=y >> CONFIG_SERIAL_MESON=y >> CONFIG_SERIAL_MESON_CONSOLE=y >> CONFIG_HW_RANDOM_MESON=m >> CONFIG_I2C_MESON=m >> CONFIG_SPI_MESON_SPIFC=m >> CONFIG_PINCTRL_MESON=y >> CONFIG_MESON_GXBB_WATCHDOG=y >> CONFIG_PWM_MESON=m >> CONFIG_RESET_MESON=y >> CONFIG_MESON_SM=y >> CONFIG_COMMON_CLK_AMLOGIC=y > > I can do all this, except I think the watchdog driver can and should be > a module. > >> For 4.10 kernels this involves >> >> CONFIG_ARCH_MESON=y >> CONFIG_DWMAC_MESON=y >> CONFIG_MESON_GXL_PHY=y >> CONFIG_SERIAL_MESON=y >> CONFIG_SERIAL_MESON_CONSOLE=y >> CONFIG_HW_RANDOM_MESON=m >> CONFIG_I2C_MESON=m >> CONFIG_SPI_MESON_SPIFC=m >> CONFIG_PINCTRL_MESON=y >> CONFIG_MESON_GXBB_WATCHDOG=y >> CONFIG_MESON_WATCHDOG=y >> CONFIG_DRM_MESON=m >> CONFIG_MMC_MESON_GX=y >> CONFIG_PWM_MESON=m >> CONFIG_RESET_MESON=y >> CONFIG_PHY_MESON8B_USB2=m >> CONFIG_MESON_SM=y >> CONFIG_COMMON_CLK_AMLOGIC=y > > Given that we're going to be using 4.9 in Debian 9 'stretch', are you > interested in getting the Meson changes in 4.10 backported? USB is not yet really usable in 4.10. So what would deserve backporting is MMC and some networking patches. I append the patch series that should provide MMC. This week I am without access to my Odroid C2 so I was only able to test that the patches are applicable to v4.9 but not if they alone provide the necessary functionality. 0903-0955 I only included to avoid any reworking of the other patches. But maybe that is not your preferred way of backporting. > >> The following patch is essential. It is queued for 4.10-rc6: >> >> ARM64: dts: meson-gx: Add firmware reserved memory zones >> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=ecb88f3001ed9ee8c53450d971de8c18bcbf7925 > > This is queued up for the next upload. For 4.9 I had to change the > filename to arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi Probably that is due to missing appended patch 0903-ARM64-dts-amlogic-Add-Meson-GX-dtsi-from-GXBB.patch Could you, please, indicate on which git repository/branch I should base any testing? Best regards Heinrich odroid-c2-mmc.tar.gz Description: GNU Zip compressed data
Bug#852132: linux-latest: Add support for Hardkernel Odroid-C2
Package: linux-latest Severity: wishlist Dear Maintainer, please, add support for the Hardkernel Odroid C2 to the kernel configuration. For 4.9 kernels this involves: CONFIG_ARCH_MESON=y CONFIG_SERIAL_MESON=y CONFIG_SERIAL_MESON_CONSOLE=y CONFIG_HW_RANDOM_MESON=m CONFIG_I2C_MESON=m CONFIG_SPI_MESON_SPIFC=m CONFIG_PINCTRL_MESON=y CONFIG_MESON_GXBB_WATCHDOG=y CONFIG_PWM_MESON=m CONFIG_RESET_MESON=y CONFIG_MESON_SM=y CONFIG_COMMON_CLK_AMLOGIC=y For 4.10 kernels this involves CONFIG_ARCH_MESON=y CONFIG_DWMAC_MESON=y CONFIG_MESON_GXL_PHY=y CONFIG_SERIAL_MESON=y CONFIG_SERIAL_MESON_CONSOLE=y CONFIG_HW_RANDOM_MESON=m CONFIG_I2C_MESON=m CONFIG_SPI_MESON_SPIFC=m CONFIG_PINCTRL_MESON=y CONFIG_MESON_GXBB_WATCHDOG=y CONFIG_MESON_WATCHDOG=y CONFIG_DRM_MESON=m CONFIG_MMC_MESON_GX=y CONFIG_PWM_MESON=m CONFIG_RESET_MESON=y CONFIG_PHY_MESON8B_USB2=m CONFIG_MESON_SM=y CONFIG_COMMON_CLK_AMLOGIC=y The following patch is essential. It is queued for 4.10-rc6: ARM64: dts: meson-gx: Add firmware reserved memory zones https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=ecb88f3001ed9ee8c53450d971de8c18bcbf7925 Best regards Heinrich Schuchardt -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: arm64 (aarch64) Kernel: Linux 4.10.0-rc3-R001-arm64 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system)
Bug#845075: kernel-image-4.8.0-1-armmp-di: Lamobo R1 cannot access network
On 01/05/2017 08:52 AM, Vagrant Cascadian wrote: > On 2017-01-04, Ben Hutchings wrote: >>> I want to install Debian Stretch on my Lamobo R1 using the network >>> installer. >>> >>> It is unable to connect to the DHCP server. >>> >>> Please, add the b53 module to the kernel. >>> >>> CONFIG_B53=y >>> 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 clear that we do want >> B53_MDIO_DRIVER and not B53_SPI_DRIVER. Are you sure the installer >> version you used had a verison 4.8 kernel, not 4.7? I used https://d-i.debian.org/daily-images/armhf/daily/netboot/SD-card-images/ as of 2016-11-20. According to https://packages.qa.debian.org/l/linux-signed/news/20161116T173404Z.html on Debian was using Kernel 4.8 since 2016-11-16. > > I had very mixed luck with the switch driver with 4.7.x and 4.8.x, but > ethernet generally worked ok. With 4.9.x, I was able to get all ports > working well. > > Were you plugging into the WAN port, or one of the switch ports? I tried both, none worked. > > Is the b53 module listed in nic-modules udeb? I don't see mention of it > at a quick glance, or is it pulled in with some globbing? > > > live well, > vagrant > > p.s. I've haven't been tracking the udebs as much lately, tired of > playing whack-a-mole with the exact right modules in the exact right > udeb... instead I've been manually appending all the drivers into the > initrd as an additional cpio archive... > signature.asc Description: OpenPGP digital signature
Bug#845075: kernel-image-4.8.0-1-armmp-di: Lamobo R1 cannot access network
Package: kernel-image-4.8.0-1-armmp-di Version: 4.8.5-1 Severity: normal Dear Maintainer, I want to install Debian Stretch on my Lamobo R1 using the network installer. It is unable to connect to the DHCP server. Please, add the b53 module to the kernel. CONFIG_B53=y CONFIG_B53_SPI_DRIVER=y Best regards Heinrich Schuchardt -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: armhf (armv7l) Kernel: Linux 4.8.0-1-armmp (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#833876: Acknowledgement (firmware-iwlwifi: Direct firmware load for iwlwifi-8000C-21.ucode failed with error -2)
The most current versions of the firmware seem to be available at http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git Here you find iwlwifi-8000C-22.ucode iwlwifi-8000C-21.ucode Best regards Heinrich Schuchardt
Bug#833876: firmware-iwlwifi: Direct firmware load for iwlwifi-8000C-21.ucode failed with error -2
Package: firmware-iwlwifi Version: 20160110-1 Severity: normal Dear Maintainer, when booting I get the following errors. Please, add the current firmware. [ 11.778714] iwlwifi :04:00.0: Direct firmware load for iwlwifi-8000C-21.ucode failed with error -2 [ 11.778723] iwlwifi :04:00.0: Direct firmware load for iwlwifi-8000C-20.ucode failed with error -2 [ 11.778731] iwlwifi :04:00.0: Direct firmware load for iwlwifi-8000C-19.ucode failed with error -2 [ 11.778737] iwlwifi :04:00.0: Direct firmware load for iwlwifi-8000C-18.ucode failed with error -2 [ 11.778744] iwlwifi :04:00.0: Direct firmware load for iwlwifi-8000C-17.ucode failed with error -2 iwlwifi-8000C-21.ucode is available at least for 5 months now. Cf. https://github.com/OpenELEC/iwlwifi-firmware/tree/master/firmware Best regards Heinrich Schuchardt -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) firmware-iwlwifi depends on no packages. firmware-iwlwifi recommends no packages. Versions of packages firmware-iwlwifi suggests: ii initramfs-tools 0.125 -- debconf information excluded
Bug#823493: BananaPi: libphy: PHY stmmac-0:ffffffff not found
Package: linux-image-4.5.0-1-armmp-lpae Version: 4.5.1-1 Severity: Normal Dear maintainer, after upgrading my BananaPi to Debian stretch I cannot connect to ethernet anymore. I get the following messages: [ 649.676499] libphy: PHY stmmac-0: not found [ 649.681594] eth0: Could not attach to PHY [ 649.685745] stmmac_open: Cannot attach to PHY (error: -19) The same problem occurs with experimental package linux-image-4.5.0-2-armmp (4.5.2-1) The problem is described in https://lkml.org/lkml/2016/4/1/59 The patches described there are in Linux 4.6-rc6. Please, apply them to the Debian linux-image. Best regards Heinrich Schuchardt
Bug#819393: linux-image-marvell: missing kirkwood-ds112.dtb
On 03/31/2016 06:25 PM, Roger Shimizu wrote: > I made the change and push to alioth already. > Please confirm it's exactly what you want. > - https://anonscm.debian.org/cgit/kernel/linux.git/commit/?h=sid=b1e9b1 debian/bin/genorig.py linux-4.4.6.tar.xz make -f debian/rules orig worked fine. Looks good to me. Please, close the bug. Regards Heinrich Schuchardt
Bug#819393: linux-image-marvell: missing kirkwood-ds112.dtb
Gregory Clement maintainer of arch/arm/boot/dts/kirkwood applied the patches [PATCH 1/1] ARM: dts: kirkwood: add kirkwood-ds112.dtb to Makefile [PATCH 1/1] ARM: dts: kirkwood: add kirkwood-nsa320.dtb to Makefile to the dt branch of http://git.infradead.org/linux-mvebu.git . Best regards Heinrich Schuchardt
Bug#819393: linux-image-marvell: missing kirkwood-ds112.dtb
On 03/28/2016 02:47 AM, Roger Shimizu wrote: > So you need to submit a patch to add it upstream first. I have submitted today https://lkml.org/lkml/2016/3/28/96 [PATCH 1/1] ARM: dts: kirkwood: add kirkwood-ds112.dtb to Makefile https://lkml.org/lkml/2016/3/28/107 [PATCH 1/1] ARM: dts: kirkwood: add kirkwood-nsa320.dtb to Makefile Best regards Heinrich Schuchardt
Bug#819393: linux-image-marvell: missing kirkwood-ds112.dtb
Package: linux-image-4.4.0-1-marvell Version: 4.4.6-1 Severity: wishlist Dear maintainer, please, add file kirkwood-ds112.dtb to support the Synology DiskStation DS112. Best regards Heinrich Schuchardt
Bug#813881: linux-image-4.3.0-1-armmp install wrong dtb on Wandboard Quad Rev B1
On 03/16/2016 10:00 AM, Ian Campbell wrote: > On Mon, 2016-03-14 at 10:48 -0700, Vagrant Cascadian wrote: >> 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 >>>>> leaving me with a system that will not boot. >>>>> >>>>> With imx6q-wandboard-revb1.dtb the system boots. >> ... >>>> When the revc was added, backwards compatibility was broken by renaming >>>> the revb .dtb file instead of keeping it and introducing the revc in a >>>> new .dtb... kind of hard to fix correctly now... >> >>>> Adding support for flash-kernel to copy multiple, or even optionally all >>>> .dtb files could at least work around the issue. >> >>> flash-kernel's DTB entry can reference a script to run which prints the >>> DTB filename to use, so if you can distinguish the variants by poking >>> at /sys etc (e.g the current sole user is kirkwood-qnap which looks at >>> properties of the PCI host bridge etc) then that might be an option? >> >> I still think it would be better to copy multiple .dtb files, to make >> sure all variants are available. This also makes it possible to use the >> same SD card image on multiple wandboards. > > That would be fine too. > >>> Were any of these boards supported in Jessie? >> >> In Jessie, they both work using the same .dtb provided by linux 3.16.x, >> although installing 4.x from jessie-backports on a wandboard rev B might >> cause issues. > > OK, so we do need to worry about the upgrade path then. Linus Torvalds pulled this patch into kernel 4.6-rc1: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d59561479e6f91d5905db37f668e1cbfdac2 Flash-kernel is already patched. So no upgrade problems will occur for Debian Stretch or Jessie backports with a kernel 4.6 or later on a Wandboard Dual or Quad rev B1. Best regards Heinrich Schuchardt
Bug#813881: linux-image-4.3.0-1-armmp install wrong dtb on Wandboard Quad Rev B1
On 08.02.2016 04:50, Vagrant Cascadian wrote: > Adding support for flash-kernel to copy multiple, or even > optionally all .dtb files could at least work around the issue. > The advandtage of copying all dtb files would be the ability to swap a disk between two armmp systems. E.g. take a Wandboard disk and plug it into a Banana Pi. The Wandboard is not the only system with a problem in /proc/device-tree/model. See ARM: dts: kirkwood: use unique machine name for ds112 https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=9d021c9d1b4b774a35d8a03d58dbf029544debda Best regards Heinrich Schuchardt
Bug#815853: Cannot modprobe due to wrong kernel version string
The error was caused by the system not using the kernel installed in /boot but reading it from /dev/mmcblk0p1. Please, close the message. Best regards Heinrich Schuchardt
Bug#815853: Cannot modprobe due to wrong kernel version string
Package: linux-image-3.16.0-4-armmp-lpae Version: 3.16.7-ckt20-1+deb8u2 Severity: grave The package installs modules in /lib/modules/3.16.0-4-armmp-lpae but uname -r returns 3.16.0-4-armmp This means that modules cannot be loaded, e.g. $ sudo modprobe nls_cp437 modprobe: ERROR: ../libkmod/libkmod.c:557 kmod_search_moddep() could not open moddep file '/lib/modules/3.16.0-4-armmp/modules.dep.bin' For lpae kernels append -lpae to the kernel version string. Best regards Heinrich Schuchardt
Bug#815850: missing symbolic link /boot/vmlinux
Package: linux-image-armmp Version: 3.16.0-4 Severity: normal When first removing the current kernel and then installing a new kernel a symbolic link /boot/vmlinux is created. sudo apt-get remove linux-image-3.16.0-4-armmp sudo apt-get install linux-image-armmp-lpae When first installing an additional kernel and then removing the current kernel the symbolic link /boot/vmlinux is removed instead of replacing it. sudo apt-get install linux-image-armmp-lpae sudo apt-get remove linux-image-3.16.0-4-armmp My expectation is that irrespective of the sequence of operations the symbolic link /boot/vmlinux should be created for the current kernel. Same for /boot/initrd.img. The problem occurs in linux-image-3.16.0-4-armmp.postrm Best regards Heinrich Schuchardt 0 aktualisiert, 0 neu installiert, 2 zu entfernen und 0 nicht aktualisiert. Nach dieser Operation werden 102 MB Plattenplatz freigegeben. Möchten Sie fortfahren? [J/n] j (Lese Datenbank ... 177337 Dateien und Verzeichnisse sind derzeit installiert.) Entfernen von linux-image-armmp (3.16+63) ... Entfernen von linux-image-3.16.0-4-armmp (3.16.7-ckt20-1+deb8u3) ... Ok, proceeding with removing running kernel image. /etc/kernel/postrm.d/initramfs-tools: update-initramfs: Deleting /boot/initrd.img-3.16.0-4-armmp /etc/kernel/postrm.d/zz-flash-kernel: DTB: sun7i-a20-bananapi.dtb flash-kernel: Kernel 3.16.0-4-armmp has been removed. flash-kernel: A higher version (3.16.0-4-armmp-lpae) is still installed, no reflashing required. The link /boot/vmlinuz is a damaged link Removing symbolic link vmlinuz You may need to re-run your boot loader The link /boot/initrd.img is a damaged link Removing symbolic link initrd.img You may need to re-run your boot loader
Bug#813881: [PATCH 1/1 v3] ARM: dts: imx6dlq-wandboard-revb1.dts: use unique model id
Shawn Guo the Linux kernel maintainer of ARM/Freescale IMX / MXC ARM
architecture has accepted my appended patch 0001-ARM... to change the
model id of the Wandboard Quad Rev B1 and the Wandboard Dual Rev B1.
See
https://lkml.org/lkml/2016/2/14/34
https://lkml.org/lkml/2016/2/7/270
I suggest to add the patch to
linux-source-4.3 (debian/patches/bugfix/arm)
and to update flash-kernel (patch 0001-db... appended).
Best regards
Heinrich Schuchardt
>From 929c1ba8dc75dfca231a751e7c82032e333bc93e Mon Sep 17 00:00:00 2001
From: Heinrich Schuchardt <xypron.g...@gmx.de>
Date: Sun, 14 Feb 2016 09:50:35 +0100
Subject: [PATCH 1/1] db/all.db: rev B1 of Wandboard Dual Lite and Quad
Wandboard Dual Lite and Quad exist in different revisions requiring
different dtb files.
Revision C1 works with the existing entries in the database.
New entries for revision B1 are created. These are based on
https://lkml.org/lkml/2016/2/7/270
Signed-off-by: Heinrich Schuchardt <xypron.g...@gmx.de>
---
db/all.db | 14 ++
1 file changed, 14 insertions(+)
diff --git a/db/all.db b/db/all.db
index 970f803..38241ce 100644
--- a/db/all.db
+++ b/db/all.db
@@ -1115,6 +1115,13 @@ Boot-Script-Path: /boot/boot.scr
U-Boot-Script-Name: bootscr.wandboard
Required-Packages: u-boot-tools
+Machine: Wandboard i.MX6 Dual Lite Board rev B1
+Kernel-Flavors: armmp
+DTB-Id: imx6dl-wandboard-revb1.dtb
+Boot-Script-Path: /boot/boot.scr
+U-Boot-Script-Name: bootscr.wandboard
+Required-Packages: u-boot-tools
+
Machine: Wandboard i.MX6 Quad Board
Kernel-Flavors: armmp
DTB-Id: imx6q-wandboard.dtb
@@ -1122,6 +1129,13 @@ Boot-Script-Path: /boot/boot.scr
U-Boot-Script-Name: bootscr.wandboard
Required-Packages: u-boot-tools
+Machine: Wandboard i.MX6 Quad Board rev B1
+Kernel-Flavors: armmp
+DTB-Id: imx6q-wandboard-revb1.dtb
+Boot-Script-Path: /boot/boot.scr
+U-Boot-Script-Name: bootscr.wandboard
+Required-Packages: u-boot-tools
+
Machine: Wexler TAB7200
Kernel-Flavors: armmp armmp-lpae
Boot-Script-Path: /boot/boot.scr
--
2.1.4
>From 370f5078a2b1561bf2b7a6f3c73f78cb54176ef9 Mon Sep 17 00:00:00 2001
From: Heinrich Schuchardt <xypron.g...@gmx.de>
Date: Mon, 8 Feb 2016 01:55:08 +0100
Subject: [PATCH 1/1 v3] ARM: dts: imx6dlq-wandboard-revb1.dts: use unique model
id
Downstream packages like Debian flash-kernel use
/proc/device-tree/model
to determine which dtb file to install.
Hence each dts in the Linux kernel should provide a unique model
identifier.
Commit 8536239e371f ("ARM: dts: Restructure imx6qdl-wandboard.dtsi for new
rev C1 board.")' created new files imx6dl-wandboard-revb1.dts and
imx6q-wandboard-revb1.dts but used the same model identifier as in
imx6dl-wandboard.dts and imx6q-wandboard.dts.
This patch provides unique model identifiers for revision B1 of
the Wandboard Dual and Wandbaord Quad.
The patch leaves imx6dl-wandboard.dts and imx6q-wandboard.dts unchanged
because it is not foreseeable if the same dts will valid for future
board revisions or not. Furthermore we should avoid unnecessary
changes.
v3:
update imx6dl-wandboard-revb1.dts
v2:
correct name of referenced Debian package
Signed-off-by: Heinrich Schuchardt <xypron.g...@gmx.de>
---
arch/arm/boot/dts/imx6dl-wandboard-revb1.dts | 2 +-
arch/arm/boot/dts/imx6q-wandboard-revb1.dts | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/imx6dl-wandboard-revb1.dts b/arch/arm/boot/dts/imx6dl-wandboard-revb1.dts
index f607d4f..8c314ee 100644
--- a/arch/arm/boot/dts/imx6dl-wandboard-revb1.dts
+++ b/arch/arm/boot/dts/imx6dl-wandboard-revb1.dts
@@ -13,7 +13,7 @@
#include "imx6qdl-wandboard-revb1.dtsi"
/ {
- model = "Wandboard i.MX6 Dual Lite Board";
+ model = "Wandboard i.MX6 Dual Lite Board rev B1";
compatible = "wand,imx6dl-wandboard", "fsl,imx6dl";
memory {
diff --git a/arch/arm/boot/dts/imx6q-wandboard-revb1.dts b/arch/arm/boot/dts/imx6q-wandboard-revb1.dts
index 20bf3c2..9207d80 100644
--- a/arch/arm/boot/dts/imx6q-wandboard-revb1.dts
+++ b/arch/arm/boot/dts/imx6q-wandboard-revb1.dts
@@ -13,7 +13,7 @@
#include "imx6qdl-wandboard-revb1.dtsi"
/ {
- model = "Wandboard i.MX6 Quad Board";
+ model = "Wandboard i.MX6 Quad Board rev B1";
compatible = "wand,imx6q-wandboard", "fsl,imx6q";
memory {
--
2.1.4
Bug#813881: [PATCH 1/1 v3] ARM: dts: imx6dlq-wandboard-revb1.dts: use unique model id
The accepted kernel patch is here: https://git.kernel.org/cgit/linux/kernel/git/shawnguo/linux.git/commit/?h=for-next=ee10774a9b48e8785f1426e273059c4ba038a27f
Bug#814068: Reboot fails on Banana Pi
Package: linux-image-armmp-lpae Version: 4.3.0-1 Severity: normal Dear maintainer, with linux-image-4.3.0-1-armmp-lpae, linux-image-3.16.0-4-armmp and linux-image-3.16.0-4-armmp-lpae the Banana Pi fails to reboot. When issueing 'sudo reboot' these are the last lines on the serial console: [ OK ] Reached target Shutdown. [ OK ] Reached target Final Step. Starting Reboot... [ 94.397735] watchdog watchdog0: watchdog did not stop! [ 94.610015] reboot: Restarting system Only after pressing the reset button the system restarts. The problem did not exist with a kernel supplied with Bananian https://www.bananian.org/ but is specific to the Debian kernel. Best regards Heinrich Schuchardt Package: flash-kernel Version: 3.35+deb8u2 Package: u-boot Version: 2014.10+dfsg1-5
Bug#813881: Acknowledgement (linux-image-4.3.0-1-armmp install wrong dtb on Wandboard Quad Rev B1)
The problem stems from this patch: https://lkml.org/lkml/2014/7/8/579 It introduced two dts with the same machine name. I have submitted Kernel patch [PATCH 1/1] imx6q-wandboard-revb1.dts: use unique machine name https://lkml.org/lkml/2016/2/6/58 When upstream accepts the patch, please, consider to add it to Debian. Together with an update of file all.db in package flash-image this should fix the problem. Best regards Heinrich Schuchardt
Bug#813876: [linux-image-armmp] Unable to handle kernel NULL pointer dereference
Package: linux-image-armmp Version: 4.3.0-1 Severity: important I try to boot my Wandboard Quad with http://ftp.uk.debian.org/debian/dists/stretch/main/installer-armhf/current/images/netboot/SD-card-images/firmware.Wandboard.img.gz + partition.img.gz If no HDMI monitor is connected the kernel stops with an error: [2.852064] imx-drm display-subsystem: failed to bind 12.hdmi (ops dw_hdmi_imx_platform_driver_exit [dw_hdmi_imx]): -517 [2.877979] Unable to handle kernel NULL pointer dereference at virtual address 0004 Starting system log daemon: [2.886157] pgd = c0004000 If a monitor is connected the failure does not occur. But since I want to run the Wandboard without monitor this is no solution. Best regards Heinrich Schuchardt U-Boot SPL 2015.10+dfsg1-4 (Dec 08 2015 - 16:59:47) U-Boot 2015.10+dfsg1-4 (Dec 08 2015 - 16:59:47 +) CPU: Freescale i.MX6Q rev1.2 at 792 MHz Reset cause: POR Board: Wandboard rev B1 I2C: ready DRAM: 2 GiB MMC: FSL_SDHC: 0, FSL_SDHC: 1 *** Warning - bad CRC, using default environment No panel detected: default to HDMI Display: HDMI (1024x768) In:serial Out: serial Err: serial Net: FEC [PRIME] Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot.scr reading /boot.scr 1575 bytes read in 15 ms (102.5 KiB/s) ## Executing script at 1200 Mainline u-boot / new-style environment detected. reading vmlinuz 3415424 bytes read in 215 ms (15.1 MiB/s) reading dtbs/imx6q-wandboard-revb1.dtb 32014 bytes read in 153 ms (204.1 KiB/s) reading initrd.gz 15045264 bytes read in 839 ms (17.1 MiB/s) Booting the Debian installer... Kernel image @ 0x1200 [ 0x00 - 0x341d80 ] ## Flattened Device Tree blob at 1800 Booting using the fdt blob at 0x1800 Using Device Tree in place at 1800, end 1800ad0d Starting kernel ... [0.00] Booting Linux on physical CPU 0x0 [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct [0.00] Linux version 4.3.0-1-armmp (debian-kernel@lists.debian.org) (gcc version 4.9.3 (Debian 4.9.3-10) ) #1 SMP Debian 4.3.3-5 (2016-01-04) [0.00] CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c5387d [0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [0.00] Machine model: Wandboard i.MX6 Quad Board [0.00] Memory policy: Data cache writealloc [0.00] PERCPU: Embedded 12 pages/cpu @ee5a6000 s19852 r8192 d21108 u49152 [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 522578 [0.00] Kernel command line: console=ttymxc0,115200 [0.00] PID hash table entries: 4096 (order: 2, 16384 bytes) [0.00] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) [0.00] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) [0.00] Memory: 2051428K/2097152K available (6965K kernel code, 810K rwdata, 2396K rodata, 828K init, 395K bss, 45724K reserved, 0K cma-reserved, 1318912K highmem) [0.00] Virtual kernel memory layout: [0.00] vector : 0x - 0x1000 ( 4 kB) [0.00] fixmap : 0xffc0 - 0xfff0 (3072 kB) [0.00] vmalloc : 0xf000 - 0xff00 ( 240 MB) [0.00] lowmem : 0xc000 - 0xef80 ( 760 MB) [0.00] pkmap : 0xbfe0 - 0xc000 ( 2 MB) [0.00] modules : 0xbf00 - 0xbfe0 ( 14 MB) [0.00] .text : 0xc0008000 - 0xc092ca18 (9363 kB) [0.00] .init : 0xc092d000 - 0xc09fc000 ( 828 kB) [0.00] .data : 0xc09fc000 - 0xc0ac68f8 ( 811 kB) [0.00].bss : 0xc0ac9000 - 0xc0b2bc3c ( 396 kB) [0.00] Hierarchical RCU implementation. [0.00] Build-time adjustment of leaf fanout to 32. [0.00] NR_IRQS:16 nr_irqs:16 16 [0.00] L2C-310 erratum 769419 enabled [0.00] L2C-310 enabling early BRESP for Cortex-A9 [0.00] L2C-310 full line of zeros enabled for Cortex-A9 [0.00] L2C-310 ID prefetch enabled, offset 1 lines [0.00] L2C-310 dynamic clock gating enabled, standby mode enabled [0.00] L2C-310 cache controller enabled, 16 ways, 1024 kB [0.00] L2C-310: CACHE_ID 0x41c7, AUX_CTRL 0x76470001 [0.00] Switching to timer-based delay loop, resolution 333ns [0.07] sched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every 715827882841ns [0.31] clocksource: mxc_timer1: mask: 0x max_cycles: 0x, max_idle_ns: 637086815595 ns [0.002604] Console: colour dummy device 80x30 [0.002633] Calibrating delay loop (skipped), value calculated using timer frequency.. 6.00 BogoMIPS (lpj=12000) [0.002651] pid_max: default: 32768 minimum: 301 [0.002814] Security Framework initialized [0.002829] Yama: disabled
Bug#813881: linux-image-4.3.0-1-armmp install wrong dtb on Wandboard Quad Rev B1
Package: linux-image-4.3.0-1-armmp Version: 4.3.3-7 Severity: important I have installed my Wandboard Quad with http://ftp.uk.debian.org/debian/dists/stretch/main/installer-armhf/current/images/netboot/SD-card-images/firmware.Wandboard.img.gz + partition.img.gz Booting with u-boot-imx requires imx6q-wandboard-revb1.dtb. linux-image-4.3.0-1-armmp installs imx6q-wandboard.dtb leaving me with a system that will not boot. With imx6q-wandboard-revb1.dtb the system boots. The system circuit board is marked as REV:B1. Package: linux-image-4.3.0-1-armmp Source: linux Version: 4.3.3-7 Package: u-boot-imx Source: u-boot Version: 2016.01+dfsg1-1
Bug#762066: CONFIG_OCTEON_USB=y
At least the following also have to be changed: CONFIG_USB=y CONFIG_USB_STORAGE=y Best regards Heinrich Schuchardt -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/trinity-53bb6c50-ca7c-4cd8-899a-382229327c9d-1411019821361@3capp-gmx-bs63
Bug#762066: CONFIG_OCTEON_USB=y
Am 18.09.14 um 19:15 schrieb Aurelien Jarno On Thu, Sep 18, 2014 at 07:25:09AM +0200, Heinrich Schuchardt wrote: Package: linux-image-octeon Version: 3.16+60 Severity: important Booting from the internal USB drive of an Ubiquity EdgeRouter Lite requires CONFIG_OCTEON_USB=y Please, add this to the kernel config file of Octeon Linux images. At least as of Kernel 3.17-rc4 the driver works without problems. Why do you need it defined as built-in? Couldn't it be defined as a module instead and then loaded though by initramfs? If using initramfs this would be on the same partition of the USB device as vmlinux. U-boot loads vmlinux. How can vmlinux read initramfs from USB without built in USB support? Which package will generate initramfs? Best regards Heinrich Schuchardt -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/trinity-9d752d66-722b-4694-b99d-c1be87c99b23-1411066115779@msvc031
Bug#762066: CONFIG_OCTEON_USB=y
Am 18.09.14 um 21:41 schrieb Aurelien Jarno On Thu, Sep 18, 2014 at 08:48:35PM +0200, Heinrich Schuchardt wrote: Am 18.09.14 um 19:15 schrieb Aurelien Jarno On Thu, Sep 18, 2014 at 07:25:09AM +0200, Heinrich Schuchardt wrote: Package: linux-image-octeon Version: 3.16+60 Severity: important Booting from the internal USB drive of an Ubiquity EdgeRouter Lite requires CONFIG_OCTEON_USB=y Please, add this to the kernel config file of Octeon Linux images. At least as of Kernel 3.17-rc4 the driver works without problems. Why do you need it defined as built-in? Couldn't it be defined as a module instead and then loaded though by initramfs? If using initramfs this would be on the same partition of the USB device as vmlinux. True U-boot loads vmlinux. How can vmlinux read initramfs from USB without built in USB support? Which package will generate initramfs? vmlinux doesn't load the initramfs, it's the responsibility of U-boot to do so. The initramfs should be created automatically with a recent Debian kernel (= 3.14). In your case we still need to activate CONFIG_OCTEON_USB. That could be done easily as a module, we don't want it as built-in. How do we ensure that the octeon USB driver module ends up in initramfs? Is some modprobe configuration file entry needed? Will this entry be part of package linux-image-octeon? Best regards Heinrich Schuchardt -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/trinity-1ae2fb52-e3d2-4089-a185-6a95d49a973a-1411070997112@msvc009
Bug#762066: CONFIG_OCTEON_USB=y
Package: linux-image-octeon Version: 3.16+60 Severity: important Booting from the internal USB drive of an Ubiquity EdgeRouter Lite requires CONFIG_OCTEON_USB=y Please, add this to the kernel config file of Octeon Linux images. At least as of Kernel 3.17-rc4 the driver works without problems. Best regards Heinrich Schuchardt -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/trinity-a0b6835a-dfe3-4c7f-9cc4-963224633377-1411017909373@3capp-gmx-bs63
Bug#690737: CONFIG_FANOTIFY_ACCESS_PERMISSIONS
On 23.06.2013 21:19, Bastian Blank wrote: Can you please describe what this interface brings for our users? I only see message by you and noone else. Bastian In many enterprise environment servers are only allowed to be installed together with a software to scan for viruses. CONFIG_FANOTIFY_ACCESS_PERMISSIONS=y allows to install virus scanning software. Fedora already has this setting http://pkgs.fedoraproject.org/cgit/kernel.git/plain/config-generic The setting enables the part of the fanotify API that is responsible for file access control. Only users having the CAP_SYS_ADMIN capability (typically only root) can use the API. A virus scanner analyzes files before they opened and disallows access if a file content is deemed dangerous. It has to interact with the opening process of files on kernel level. Before the fanotify interface was introduced this required a special kernel module to be compiled. Up to Linux kernel 2.6.34 this could be implemented using the Dazuko stackable filesystem. With CONFIG_FANOTIFY_ACCESS_PERMISSIONS=y no special Kernel module is needed. As I believe in free software I want to be able to run completely free virus scanning solution. I developed a solution based on the fanotify interface ClamAV and packaged it for Debian. See http://xypron.github.io/skyldav CONFIG_FANOTIFY_ACCESS_PERMISSIONS=y will also allow to install existing commercial solutions. Best regards Heinrich Schuchardt -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51cbd7cb.9060...@gmx.de
Bug#690737: CONFIG_FANOTIFY_ACCESS_PERMISSIONS
Hello Ben, I hope you as the uploader of the latest versions of linux-image packages, can help me with Debian bug #690737. The fanotify interface is the basis for on access malware detection in the Linux kernel. The development of a prior solution (DazukoFS) has been stopped therefore. Both free (ClamAV) as well as commercial viurs scanners (Sophos Anti-Virus, AVG) using this interface exist. Since kernel version 3.8.0 the implementation of the fanotify inter- face is errorfree enough to be used on a productive system. Unfortunately Debian users have to build their own custom kernel (with kpkg) if they want to use a virus scanner relying on the fanotify interface as CONFIG_FANOTIFY_ACCESS_PERMISSIONS is set to N even in the most recent uploads. Greg Kroah-Hartman the current Linux kernel maintainer for the -stable branch wrote that he expects the distros to enable the API (https://lkml.org/lkml/2013/6/15/174): We only set options to 'default Y' if they are needed in order to keep your machine working properly. Now that this option has been around for a while, changing the default will not affect anyone's machines, as they will not see that change. Why not just work with the distros to enable fanotify, that's where you need this enabled, not here. Those are the majority of users, not kernel developers who pick their own kernel configurations. Best regards Heinrich Schuchardt -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51c7450d.7070...@gmx.de
Bug#690737: CONFIG_FANOTIFY_ACCESS_PERMISSIONS is not set
One example of a virus scanner requiring CONFIG_FANOTIFY_ACCESS_PERMISSIONS is AVG Linux Server Edition. Best regards Heinrich Schuchardt http://www.xypron.de -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/517f2586.6070...@gmx.de
