Bug#1081837: flash-kernel: Please add support for AM64 based HummingBoard-T
Package: flash-kernel Version: 3.108 Severity: wishlist X-Debbugs-Cc: jo...@solid-run.com Dear Maintainer, Please add support for AM64 based HummingBoard-T, which is supported since Linux v6.10. Some kernel drivers are not yet enabled in linux-image-arm64, there is a separate issue on that. I have opened a merge request: https://salsa.debian.org/installer-team/flash-kernel/-/merge_requests/64 sincerely Josua Mayer -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: arm64 (aarch64) Kernel: Linux 6.10.9-arm64 (SMP w/2 CPU threads) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages flash-kernel depends on: ii debconf [debconf-2.0] 1.5.87 ii devio 1.2-3 ii initramfs-tools0.145 ii linux-base 4.10.1 ii mtd-utils 1:2.2.0-2 ii ucf3.0043+nmu1 Versions of packages flash-kernel recommends: ii u-boot-tools 2024.01+dfsg-5+b2 flash-kernel suggests no packages. -- Configuration Files: /etc/flash-kernel/db changed: Machine: SolidRun AM642 HummingBoard-T Kernel-Flavors: arm64 DTB-Id: ti/k3-am642-hummingboard-t.dtb Boot-Script-Path: /boot/boot.scr U-Boot-Script-Name: bootscr.uboot-generic Required-Packages: u-boot-tools -- debconf information: flash-kernel/linux_cmdline: quiet
Bug#1081836: linux-image-6.10.9-1-arm64: Please enable drivers for am64 hummingboard-t
Package: linux-image-6.10.9-1-arm64 Version: linux-image-6.10.9-arm64 Severity: wishlist X-Debbugs-Cc: jo...@solid-run.com Dear Maintainer, Please enable drivers for AM64 based HummingBoard-T, the board is fully supported as per Linux v6.10. I have opened a merge request on salsa: https://salsa.debian.org/kernel-team/linux/-/merge_requests/1204 The merge request also adds some modules to udebs for installer, this part I am unsure which package some of the modules should go into. sincerely Josua Mayer -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: arm64 (aarch64) Kernel: Linux 6.10.9-arm64 (SMP w/2 CPU threads) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1081550: Acknowledgement (linux-image-6.1.0-25-armmp: Missing imx2_wdt module during installation)
Dear Maintainers, As an experiment I have added the imx2_wdt.ko kernel module to the debian-installer initrd.gz, as per http://ftp.debian.org/debian/dists/bookworm/main/installer-armhf/20230607+deb12u7/images/hd-media/hd-media.tar.gz: cd /; echo lib/modules/6.1.0-25-armmp/kernel/drivers/watchdog/imx2_wdt.ko | cpio -H newc -o | gzip > ~/wdtmod.cpio.gz cat wdtmod.cpio.gz >> initrd.gz After booting installer with this modified initrd, the system does not reset and stays up as long as it takes. So installer does indeed service the watchdog! Please include watchdog driver in udeb for future installer builds, ideally for both bookworm and sid. sincerely Josua Mayer Am 12.09.24 um 19:03 schrieb Debian Bug Tracking System: > Thank you for filing a new Bug report with Debian. > > You can follow progress on this Bug here: 1081550: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081550. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > As you requested using X-Debbugs-CC, your message was also forwarded to > jo...@solid-run.com > (after having been given a Bug report number, if it did not have one). > > Your message has been sent to the package maintainer(s): > Debian Kernel Team > > If you wish to submit further information on this problem, please > send it to 1081...@bugs.debian.org. > > Please do not send mail to ow...@bugs.debian.org unless you wish > to report a problem with the Bug-tracking system. >
Bug#1081550: linux-image-6.1.0-25-armmp: Missing imx2_wdt module during installation
Package: src:linux Version: 6.1.106-3 Severity: normal Tags: d-i X-Debbugs-Cc: jo...@solid-run.com Dear Maintainer, It appears that freescale i.mx family cpus watchdog driver is not included in any udeb, thereby not available during installation. This leads to two issues: 1. i.xm6 hummingboard and cubox-i get stuck after on reboot after installation is complete, since watchdog is used for reboot on this platform. 2. if u-boot had enabled the watchdog, during debian installation there is no chance of servicing, leading inevitably to system reset after 128 seconds. I do not know if debian-installer currently will service a watchdog, if so, many watchdog drivers should be shipped by udebs for the installer. i.MX6 (5/4/3/2) watchdogs can not be disabled once enabled. If a bootloader has chosen to enable watchdog automatically, the only way to succeed at a debian installation is programming a different u-boot binary. Watchdog reset is however desirable to handle crashes during Linux especially on embedded or headless systems. Hence (imo) it would be nice if debian-installer would service watchdogs. For reference a related issue had been closed several years ago: https://lists.debian.org/debian-boot/2017/07/msg00177.html best regards Josua Mayer -- Package-specific info: ** Version: Linux version 6.1.0-25-armmp (debian-ker...@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP Debian 6.1.106-3 (2024-08-26) ** Command line: console=ttymxc0,115200 quiet ** Tainted: C (1024) * staging driver was loaded ** Kernel log: [ 15.742964] etnaviv etnaviv: bound 2204000.gpu (ops gpu_ops [etnaviv]) [ 15.743123] etnaviv-gpu 13.gpu: model: GC2000, revision: 5108 [ 15.743556] etnaviv-gpu 134000.gpu: model: GC320, revision: 5007 [ 15.743643] etnaviv-gpu 2204000.gpu: model: GC355, revision: 1215 [ 15.743659] etnaviv-gpu 2204000.gpu: Ignoring GPU with VG and FE2.0 [ 15.744463] [drm] Initialized etnaviv 1.4.0 20151214 for etnaviv on minor 0 [ 15.755543] dwhdmi-imx 12.hdmi: Detected HDMI TX controller v1.30a with HDCP (DWC HDMI 3D TX PHY) [ 15.854852] imx_media_common: module is from the staging directory, the quality is unknown, you have been warned. [ 15.874051] CAN device driver interface [ 15.879514] imx-drm display-subsystem: bound imx-ipuv3-crtc.2 (ops imx_drm_exit [imxdrm]) [ 15.879727] imx-drm display-subsystem: bound imx-ipuv3-crtc.3 (ops imx_drm_exit [imxdrm]) [ 15.88] imx-drm display-subsystem: bound imx-ipuv3-crtc.6 (ops imx_drm_exit [imxdrm]) [ 15.880186] imx-drm display-subsystem: bound imx-ipuv3-crtc.7 (ops imx_drm_exit [imxdrm]) [ 15.880299] imx-drm display-subsystem: bound 12.hdmi (ops dw_hdmi_imx_ops [dw_hdmi_imx]) [ 15.881161] [drm] Initialized imx-drm 1.0.0 20120507 for display-subsystem on minor 1 [ 15.881455] imx-drm display-subsystem: [drm] Cannot find any crtc or sizes [ 15.881684] imx-drm display-subsystem: [drm] Cannot find any crtc or sizes [ 15.893582] imx6_media: module is from the staging directory, the quality is unknown, you have been warned. [ 15.978631] coda 204.vpu: firmware: failed to load vpu_fw_imx6q.bin (-2) [ 15.997415] coda 204.vpu: firmware: failed to load vpu_fw_imx6q.bin (-2) [ 16.004560] coda 204.vpu: Direct firmware load for vpu_fw_imx6q.bin failed with error -2 [ 16.025308] coda 204.vpu: firmware: failed to load vpu/vpu_fw_imx6q.bin (-2) [ 16.041242] coda 204.vpu: firmware: failed to load vpu/vpu_fw_imx6q.bin (-2) [ 16.046567] fsl-ssi-dai 2028000.ssi: No cache defaults, reading back from HW [ 16.048720] coda 204.vpu: Direct firmware load for vpu/vpu_fw_imx6q.bin failed with error -2 [ 16.057374] coda 204.vpu: firmware: failed to load v4l-coda960-imx6q.bin (-2) [ 16.068498] coda 204.vpu: firmware: failed to load v4l-coda960-imx6q.bin (-2) [ 16.076070] coda 204.vpu: Direct firmware load for v4l-coda960-imx6q.bin failed with error -2 [ 16.085251] coda 204.vpu: firmware request failed [ 16.277022] imx_thermal 20c8000.anatop:tempmon: Extended Commercial CPU temperature grade - max:105C critical:100C passive:95C [ 16.307265] caam 210.crypto: Entropy delay = 3200 [ 16.368071] caam 210.crypto: Instantiated RNG4 SH0 [ 16.428834] caam 210.crypto: Instantiated RNG4 SH1 [ 16.546664] caam 210.crypto: device ID = 0x0a160100 (Era 4) [ 16.546687] caam 210.crypto: job rings = 2, qi = 0 [ 16.648120] sgtl5000 0-000a: sgtl5000 revision 0x11 [ 16.653413] sgtl5000 0-000a: Using internal LDO instead of VDDD: check ER1 erratum [ 16.839820] debugfs: File 'Headphone Jack' in directory 'dapm' already present! [ 16.920908] imx6_media_csi: module is from the staging directory, the quality is unknown, you have been warned. [ 16.927858] imx6_media_csi: module is from the staging directory, the quality is unknown, you have been warned. [ 16.92
Bug#1076934: linux: please enable drivers for arm64 cn913x solidrun boards
Source: linux Severity: wishlist X-Debbugs-Cc: jo...@solid-run.com Dear Maintainer, Several boards based on Marvell CN9130 SoC will be supported with Linux 5.11. flash-kernel database entries were already been added. Please enable the kernel config option below, to support the usb-2.0 phys. Their driver missing leads to usb ports not functioning: josua@cn9130-cf-pro:~$ grep UTMI /boot/config-6.9.9-arm64 # CONFIG_PHY_MVEBU_CP110_UTMI is not set ^^ Should be set =m sincerely Josua Mayer -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: arm64 (aarch64) Kernel: Linux 6.9.9-arm64 (SMP w/4 CPU threads) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1076085: flash-kernel: Please add support for LX2162 Clearfog, CN913x Clearfog
Package: flash-kernel Version: 3.107 Severity: wishlist X-Debbugs-Cc: jo...@solid-run.com Dear Maintainer, Please add machine db entries for several new SolidRun arm boards, which have recently been supported upstream in the kernel: - LX2162 Clearfog - CN9130 Clearfog Base - CN9130 Clearfog Pro - CN9131 SolidWAN - CN9132 Clearfog I have already created a merge request on Salsa: https://salsa.debian.org/installer-team/flash-kernel/-/merge_requests/61 best regards Josua Mayer -- System Information: Debian Release: 12.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: arm64 (aarch64) Kernel: Linux 6.9.8-arm64 (SMP w/16 CPU threads) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages flash-kernel depends on: ii debconf [debconf-2.0] 1.5.82 ii devio 1.2-1.3 ii initramfs-tools0.142 ii linux-base 4.9 ii mtd-utils 1:2.1.5-1 ii ucf3.0043+nmu1 Versions of packages flash-kernel recommends: ii u-boot-tools 2023.01+dfsg-2+deb12u1 flash-kernel suggests no packages. -- Configuration Files: /etc/flash-kernel/db changed: Machine: SolidRun LX2162A Clearfog Kernel-Flavors: arm64 DTB-Id: freescale/fsl-lx2162a-clearfog.dtb Boot-Script-Path: /boot/boot.scr U-Boot-Script-Name: bootscr.uboot-generic Required-Packages: u-boot-tools -- debconf information excluded
Bug#1065611: Additional support for SolidRun HoneyComb
Hi Diederik, May I ask if you are analyzing dts manually, or whether you are aware of an automatic tool? sincerely Josua Mayer Am 12.03.24 um 18:04 schrieb Diederik de Haas: > Hi Josua, > > On Tuesday, 12 March 2024 16:28:06 CET Josua Mayer wrote: >> I believe I found the answer: >> EDAC_MPC85XX is for power-pc only, >> EDAC_LAYERSCAPE is for arm (see drivers/edac/layerscape_edac.c). > You're right. In the commit I referenced earlier (ea2eb9a8b6207ee4), > I misinterpreted the commit message. > That commit also created ``drivers/edac/fsl_ddr_edac.c`` which got the arch > independent (or at least dual arch) parts. Its header has this: > ``` > * Support Power-based SoCs including MPC85xx, MPC86xx, MPC83xx and > * ARM-based Layerscape SoCs including LS2xxx. Originally split > * out from mpc85xx_edac EDAC driver. > ``` > >> Am 12.03.24 um 16:13 schrieb Josua Mayer: >>> Thank you for taking care of this! >>> First the additional changes you found seem reasonable. > Excellent, then I'll make a MR for them (except EDAC_MPC85XX): > - drivers/hwmon/pmbus: Enable PMBUS, SENSORS_PMBUS and >SENSORS_LTC2978 as modules > - drivers/nvmem: Enable NVMEM_LAYERSCAPE_SFP as module > - drivers/rtc: Enable RTC_DRV_FSL_FTM_ALARM as module > - drivers/soc/fsl: Enable FSL_RCPM > >>> Regarding edac - I checked NXPs reference BSP for LX2160, >>> and their linux fork has the same status, driver can not be enabled on >>> arm64. >>> However I also agree it should be enabled if it were possible. >>> The driver appears to setup ecc bit error interrupts so that hey can be >>> reported by Linux. >>> ... >>> I may have access to an lx2160a system with ecc memory within the coming >>> week, so I could test (on vendor kernel based on 5.10 only) whether any >>> problems show up. If not, perhaps a patch to the kernel is advisable. > As EDAC_LAYERSCAPE got enabled in 5.5.17-1 via bug 948576 (with a patch from > you), ECC support should already work with the Stable 6.1 kernel (or newer). > >>> Am 07.03.24 um 13:34 schrieb Diederik de Haas: >>>> On Thursday, 18 January 2024 17:40:38 CET Josua Mayer wrote: >>>> >>>>> LX2160 SoC early silicon revisions have a pci-e generation 4 >>>>> controller. >>>>> It requires a different driver from newer gen-3 silicon. >>>>> >>>>> This affects the SolidRun Honeycomb Workstation which >>>>> is otherwise fully supported in Debian. >>>> I cloned bug report #1061116 into #1065611 to discuss some additional >>>> support for the SolidRun HoneyComb. >>>> >>>> I analyzed the HoneyComb dts file and the following included .dtsi >>>> files: >>>> - arch/arm64/boot/dts/freescale/fsl-lx2160a-clearfog-itx.dtsi >>>> - arch/arm64/boot/dts/freescale/fsl-lx2160a-cex7.dtsi >>>> - arch/arm64/boot/dts/freescale/fsl-lx2160a.dtsi > If my MR gets merged, then there's truly full support in Debian :) > > Cheers, > Diederik
Bug#1065611: Additional support for SolidRun HoneyComb
Hi Diederik, I believe I found the answer: EDAC_MPC85XX is for power-pc only, EDAC_LAYERSCAPE is for arm (see drivers/edac/layerscape_edac.c). br Josua Am 12.03.24 um 16:13 schrieb Josua Mayer: > Hi Diederik, > > Thank you for taking care of this! > First the additional changes you found seem reasonable. > > Regarding edac - I checked NXPs reference BSP for LX2160, > and their linux fork has the same status, driver can not be enabled on arm64. > > However I also agree it should be enabled if it were possible. > The driver appears to setup ecc bit error interrupts so that hey can be > reported by Linux. > > Here is what other qoriq drivers do: > drivers/crypto/caam/Kconfig: depends on FSL_SOC || ARCH_MXC || > ARCH_LAYERSCAPE > > I may have access to an lx2160a system with ecc memory within the coming week, > so I could test (on vendor kernel based on 5.10 only) whether any problems > show up. > If not, perhaps a patch to the kernel is advisable. > > Am 07.03.24 um 13:34 schrieb Diederik de Haas: > >> Hi Josua, >> >> On Thursday, 18 January 2024 17:40:38 CET Josua Mayer wrote: >>> LX2160 SoC early silicon revisions have a pci-e generation 4 controller. >>> It requires a different driver from newer gen-3 silicon. >>> >>> This affects the SolidRun Honeycomb Workstation which >>> is otherwise fully supported in Debian. >> I cloned bug report #1061116 into #1065611 to discuss some additional >> support >> for the SolidRun HoneyComb. >> >> I analyzed the HoneyComb dts file and the following included .dtsi files: >> - arch/arm64/boot/dts/freescale/fsl-lx2160a-clearfog-itx.dtsi >> - arch/arm64/boot/dts/freescale/fsl-lx2160a-cex7.dtsi >> - arch/arm64/boot/dts/freescale/fsl-lx2160a.dtsi >> >> If I exclude the kernel modules from 1061116 and 1061117, then I still have >> the following list of additional modules to enable: >> - drivers/edac: Enable EDAC_MPC85XX >> - drivers/hwmon/pmbus: Enable PMBUS, SENSORS_PMBUS and >> SENSORS_LTC2978 as modules >> - drivers/nvmem: Enable NVMEM_LAYERSCAPE_SFP as module >> - drivers/rtc: Enable RTC_DRV_FSL_FTM_ALARM as module >> - drivers/soc/fsl: Enable FSL_RCPM >> >> If you agree that this is a good list I can make a MR to get them enabled. >> A MR for 1061116 and 1061117 has just been merged in our 'master' branch. >> >> But I ran into an issue when looking at the ``EDAC_MPC85XX`` stanza >> in``drivers/edac/Kconfig``: >> ``depends on FSL_SOC && EDAC=y`` >> >> But ``FSL_SOC`` is (only) defined in ``arch/powerpc/Kconfig``, which means >> ``EDAC_MPC85XX`` can not be enabled on ``arm64``. >> That module was found based on ``compatible = >> "fsl,qoriq-memory-controller"``, >> which sounds like something you would want to have. >> >> Upstream commit ea2eb9a8b6207ee4 has the following commit message: >> ``` >> EDAC, fsl-ddr: Separate FSL DDR driver from MPC85xx >> >> The mpc85xx-compatible DDR controllers are used on ARM-based SoCs too. >> Carve out the DDR part from the mpc85xx EDAC driver in preparation to >> support both architectures. >> ``` >> Which I interpret as all (?) the preparations for supporting both powerpc >> and >> ARM were made, but they forgot to update the strict dependency of >> ``EDAC_MPC85XX`` to powerpc to actually support both architectures? >> >> Can you shed some light on this? >> >> Cheers, >> Diederik
Bug#1065611: Additional support for SolidRun HoneyComb
Hi Diederik, Thank you for taking care of this! First the additional changes you found seem reasonable. Regarding edac - I checked NXPs reference BSP for LX2160, and their linux fork has the same status, driver can not be enabled on arm64. However I also agree it should be enabled if it were possible. The driver appears to setup ecc bit error interrupts so that hey can be reported by Linux. Here is what other qoriq drivers do: drivers/crypto/caam/Kconfig: depends on FSL_SOC || ARCH_MXC || ARCH_LAYERSCAPE I may have access to an lx2160a system with ecc memory within the coming week, so I could test (on vendor kernel based on 5.10 only) whether any problems show up. If not, perhaps a patch to the kernel is advisable. Am 07.03.24 um 13:34 schrieb Diederik de Haas: > Hi Josua, > > On Thursday, 18 January 2024 17:40:38 CET Josua Mayer wrote: >> LX2160 SoC early silicon revisions have a pci-e generation 4 controller. >> It requires a different driver from newer gen-3 silicon. >> >> This affects the SolidRun Honeycomb Workstation which >> is otherwise fully supported in Debian. > I cloned bug report #1061116 into #1065611 to discuss some additional support > for the SolidRun HoneyComb. > > I analyzed the HoneyComb dts file and the following included .dtsi files: > - arch/arm64/boot/dts/freescale/fsl-lx2160a-clearfog-itx.dtsi > - arch/arm64/boot/dts/freescale/fsl-lx2160a-cex7.dtsi > - arch/arm64/boot/dts/freescale/fsl-lx2160a.dtsi > > If I exclude the kernel modules from 1061116 and 1061117, then I still have > the following list of additional modules to enable: > - drivers/edac: Enable EDAC_MPC85XX > - drivers/hwmon/pmbus: Enable PMBUS, SENSORS_PMBUS and > SENSORS_LTC2978 as modules > - drivers/nvmem: Enable NVMEM_LAYERSCAPE_SFP as module > - drivers/rtc: Enable RTC_DRV_FSL_FTM_ALARM as module > - drivers/soc/fsl: Enable FSL_RCPM > > If you agree that this is a good list I can make a MR to get them enabled. > A MR for 1061116 and 1061117 has just been merged in our 'master' branch. > > But I ran into an issue when looking at the ``EDAC_MPC85XX`` stanza > in``drivers/edac/Kconfig``: > ``depends on FSL_SOC && EDAC=y`` > > But ``FSL_SOC`` is (only) defined in ``arch/powerpc/Kconfig``, which means > ``EDAC_MPC85XX`` can not be enabled on ``arm64``. > That module was found based on ``compatible = > "fsl,qoriq-memory-controller"``, > which sounds like something you would want to have. > > Upstream commit ea2eb9a8b6207ee4 has the following commit message: > ``` > EDAC, fsl-ddr: Separate FSL DDR driver from MPC85xx > > The mpc85xx-compatible DDR controllers are used on ARM-based SoCs too. > Carve out the DDR part from the mpc85xx EDAC driver in preparation to > support both architectures. > ``` > Which I interpret as all (?) the preparations for supporting both powerpc and > ARM were made, but they forgot to update the strict dependency of > ``EDAC_MPC85XX`` to powerpc to actually support both architectures? > > Can you shed some light on this? > > Cheers, > Diederik
Bug#1061117: linux-image-6.1.0-17-arm64: please enable support for lx2160a serdes runtime configuration
Package: src:linux Version: 6.1.69-1 Severity: important X-Debbugs-Cc: jo...@solid-run.com Dear Maintainer, Please enable support for lx2160a serdes configuration driver in arm64 flavour: CONFIG_PHY_FSL_LYNX_28G This driver is essential for supporting the SFP+ connectors on SolidRun Honeycomb Workstation. Since mainline added references to SerDes via "phys" properties in v5.18, Debian can not probe the netdev's, breaking all 10Gbps NICs. Ideally this will be enabled for current stable release, too. Sincerely Josua Mayer -- Package-specific info: ** Version: Linux version 6.1.0-17-arm64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP Debian 6.1.69-1 (2023-12-30) ** Command line: arm-smmu.disable-bypass=0 console=ttyAMA0,38400n8 quiet ** Not tainted ** Kernel log: [4.330447] alg: No test for authenc(hmac(md5),cbc(aes)) (authenc-hmac-md5-cbc-aes-caam-qi2) [4.330532] alg: No test for echainiv(authenc(hmac(md5),cbc(aes))) (echainiv-authenc-hmac-md5-cbc-aes-caam-qi2) [4.334627] audit: type=1400 audit(1705595241.215:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lsb_release" pid=525 comm="apparmor_parser" [4.335982] audit: type=1400 audit(1705595241.215:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=526 comm="apparmor_parser" [4.335991] audit: type=1400 audit(1705595241.215:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=526 comm="apparmor_parser" [4.336012] alg: No test for echainiv(authenc(hmac(sha1),cbc(aes))) (echainiv-authenc-hmac-sha1-cbc-aes-caam-qi2) [4.336100] alg: No test for authenc(hmac(sha224),cbc(aes)) (authenc-hmac-sha224-cbc-aes-caam-qi2) [4.336178] alg: No test for echainiv(authenc(hmac(sha224),cbc(aes))) (echainiv-authenc-hmac-sha224-cbc-aes-caam-qi2) [4.339390] alg: No test for echainiv(authenc(hmac(sha256),cbc(aes))) (echainiv-authenc-hmac-sha256-cbc-aes-caam-qi2) [4.339495] alg: No test for authenc(hmac(sha384),cbc(aes)) (authenc-hmac-sha384-cbc-aes-caam-qi2) [4.339619] alg: No test for echainiv(authenc(hmac(sha384),cbc(aes))) (echainiv-authenc-hmac-sha384-cbc-aes-caam-qi2) [4.340663] audit: type=1400 audit(1705595241.219:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=528 comm="apparmor_parser" [4.340674] audit: type=1400 audit(1705595241.219:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=528 comm="apparmor_parser" [4.340680] audit: type=1400 audit(1705595241.219:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=528 comm="apparmor_parser" [4.342833] alg: No test for echainiv(authenc(hmac(sha512),cbc(aes))) (echainiv-authenc-hmac-sha512-cbc-aes-caam-qi2) [4.342951] alg: No test for authenc(hmac(md5),cbc(des3_ede)) (authenc-hmac-md5-cbc-des3_ede-caam-qi2) [4.343067] alg: No test for echainiv(authenc(hmac(md5),cbc(des3_ede))) (echainiv-authenc-hmac-md5-cbc-des3_ede-caam-qi2) [4.343743] alg: No test for echainiv(authenc(hmac(sha1),cbc(des3_ede))) (echainiv-authenc-hmac-sha1-cbc-des3_ede-caam-qi2) [4.344850] alg: No test for echainiv(authenc(hmac(sha224),cbc(des3_ede))) (echainiv-authenc-hmac-sha224-cbc-des3_ede-caam-qi2) [4.345868] alg: No test for echainiv(authenc(hmac(sha256),cbc(des3_ede))) (echainiv-authenc-hmac-sha256-cbc-des3_ede-caam-qi2) [4.346863] alg: No test for echainiv(authenc(hmac(sha384),cbc(des3_ede))) (echainiv-authenc-hmac-sha384-cbc-des3_ede-caam-qi2) [4.347587] alg: No test for echainiv(authenc(hmac(sha512),cbc(des3_ede))) (echainiv-authenc-hmac-sha512-cbc-des3_ede-caam-qi2) [4.347693] alg: No test for authenc(hmac(md5),cbc(des)) (authenc-hmac-md5-cbc-des-caam-qi2) [4.347810] alg: No test for echainiv(authenc(hmac(md5),cbc(des))) (echainiv-authenc-hmac-md5-cbc-des-caam-qi2) [4.348851] alg: No test for echainiv(authenc(hmac(sha1),cbc(des))) (echainiv-authenc-hmac-sha1-cbc-des-caam-qi2) [4.349882] alg: No test for echainiv(authenc(hmac(sha224),cbc(des))) (echainiv-authenc-hmac-sha224-cbc-des-caam-qi2) [4.350874] alg: No test for echainiv(authenc(hmac(sha256),cbc(des))) (echainiv-authenc-hmac-sha256-cbc-des-caam-qi2) [4.351895] alg: No test for echainiv(authenc(hmac(sha384),cbc(des))) (echainiv-authenc-hmac-sha384-cbc-des-caam-qi2) [4.352897] alg: No test for echainiv(authenc(hmac(sha512),cbc(des))) (echainiv-authenc-hmac-sha512-cbc-des-caam-qi2) [4.353008] alg: No test for authenc(hmac(md5)
Bug#1061116: linux-image-6.1.0-17-arm64: please enable support for lx2160a pcie gen4 controller on early silicon
Package: src:linux Version: 6.1.69-1 Severity: normal X-Debbugs-Cc: jo...@solid-run.com Dear Maintainer, Please enable "PCIE_LAYERSCAPE_GEN4" for arm64 flavour, in addition to already enabled "PCIE_LAYERSCAPE". LX2160 SoC early silicon revisions have a pci-e generation 4 controller. It requires a different driver from newer gen-3 silicon. This affects the SolidRun Honeycomb Workstation which is otherwise fully supported in Debian. Ideally the config option wll be enabled for debian stable, too. -- Package-specific info: ** Version: Linux version 6.1.0-17-arm64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP Debian 6.1.69-1 (2023-12-30) ** Command line: arm-smmu.disable-bypass=0 console=ttyAMA0,38400n8 quiet ** Not tainted ** Kernel log: [4.330447] alg: No test for authenc(hmac(md5),cbc(aes)) (authenc-hmac-md5-cbc-aes-caam-qi2) [4.330532] alg: No test for echainiv(authenc(hmac(md5),cbc(aes))) (echainiv-authenc-hmac-md5-cbc-aes-caam-qi2) [4.334627] audit: type=1400 audit(1705595241.215:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lsb_release" pid=525 comm="apparmor_parser" [4.335982] audit: type=1400 audit(1705595241.215:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=526 comm="apparmor_parser" [4.335991] audit: type=1400 audit(1705595241.215:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=526 comm="apparmor_parser" [4.336012] alg: No test for echainiv(authenc(hmac(sha1),cbc(aes))) (echainiv-authenc-hmac-sha1-cbc-aes-caam-qi2) [4.336100] alg: No test for authenc(hmac(sha224),cbc(aes)) (authenc-hmac-sha224-cbc-aes-caam-qi2) [4.336178] alg: No test for echainiv(authenc(hmac(sha224),cbc(aes))) (echainiv-authenc-hmac-sha224-cbc-aes-caam-qi2) [4.339390] alg: No test for echainiv(authenc(hmac(sha256),cbc(aes))) (echainiv-authenc-hmac-sha256-cbc-aes-caam-qi2) [4.339495] alg: No test for authenc(hmac(sha384),cbc(aes)) (authenc-hmac-sha384-cbc-aes-caam-qi2) [4.339619] alg: No test for echainiv(authenc(hmac(sha384),cbc(aes))) (echainiv-authenc-hmac-sha384-cbc-aes-caam-qi2) [4.340663] audit: type=1400 audit(1705595241.219:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=528 comm="apparmor_parser" [4.340674] audit: type=1400 audit(1705595241.219:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=528 comm="apparmor_parser" [4.340680] audit: type=1400 audit(1705595241.219:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=528 comm="apparmor_parser" [4.342833] alg: No test for echainiv(authenc(hmac(sha512),cbc(aes))) (echainiv-authenc-hmac-sha512-cbc-aes-caam-qi2) [4.342951] alg: No test for authenc(hmac(md5),cbc(des3_ede)) (authenc-hmac-md5-cbc-des3_ede-caam-qi2) [4.343067] alg: No test for echainiv(authenc(hmac(md5),cbc(des3_ede))) (echainiv-authenc-hmac-md5-cbc-des3_ede-caam-qi2) [4.343743] alg: No test for echainiv(authenc(hmac(sha1),cbc(des3_ede))) (echainiv-authenc-hmac-sha1-cbc-des3_ede-caam-qi2) [4.344850] alg: No test for echainiv(authenc(hmac(sha224),cbc(des3_ede))) (echainiv-authenc-hmac-sha224-cbc-des3_ede-caam-qi2) [4.345868] alg: No test for echainiv(authenc(hmac(sha256),cbc(des3_ede))) (echainiv-authenc-hmac-sha256-cbc-des3_ede-caam-qi2) [4.346863] alg: No test for echainiv(authenc(hmac(sha384),cbc(des3_ede))) (echainiv-authenc-hmac-sha384-cbc-des3_ede-caam-qi2) [4.347587] alg: No test for echainiv(authenc(hmac(sha512),cbc(des3_ede))) (echainiv-authenc-hmac-sha512-cbc-des3_ede-caam-qi2) [4.347693] alg: No test for authenc(hmac(md5),cbc(des)) (authenc-hmac-md5-cbc-des-caam-qi2) [4.347810] alg: No test for echainiv(authenc(hmac(md5),cbc(des))) (echainiv-authenc-hmac-md5-cbc-des-caam-qi2) [4.348851] alg: No test for echainiv(authenc(hmac(sha1),cbc(des))) (echainiv-authenc-hmac-sha1-cbc-des-caam-qi2) [4.349882] alg: No test for echainiv(authenc(hmac(sha224),cbc(des))) (echainiv-authenc-hmac-sha224-cbc-des-caam-qi2) [4.350874] alg: No test for echainiv(authenc(hmac(sha256),cbc(des))) (echainiv-authenc-hmac-sha256-cbc-des-caam-qi2) [4.351895] alg: No test for echainiv(authenc(hmac(sha384),cbc(des))) (echainiv-authenc-hmac-sha384-cbc-des-caam-qi2) [4.352897] alg: No test for echainiv(authenc(hmac(sha512),cbc(des))) (echainiv-authenc-hmac-sha512-cbc-des-caam-qi2) [4.353008] alg: No test for authenc(hmac(md5),rfc3686(ctr(aes))) (authenc-hmac-md5-rfc3686-ctr-aes-caam-qi2) [4.353112] alg: No test for seqiv(authenc(hmac(md5),rfc3686(ctr(aes (seqiv-authenc-hmac-md5-rfc3686-ctr-aes-caam-qi2) [4.353323] alg: No test for seqiv(authenc(hmac(sha1),rfc3686(ctr(aes (seqiv-authenc-hmac-sha1-rfc3686-ctr-aes-caam-qi2) [4.353425] alg: No
Bug#1043354: linux-image-6.1.0-10-armmp: please enable analog devices ethernet phy driver "adin"
Package: src:linux Version: 6.1.38-2+sr1 Severity: normal Tags: patch X-Debbugs-Cc: josua.maye...@gmail.com Dear Maintainer, Please enable the "adin" driver for analog devices ADIN1300 ethernet phy. SolidRun i.MX6 SoMs revision 1.9 and later replaced the original Atheros ethernet PHY with ADIN1300. This combination is fully supported in Linux 6.1. Therefore please enable the kernel module for armhf target. Sincerely Josua Mayer -- Package-specific info: ** Version: Linux version 6.1.0-10-armmp (debian-ker...@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP Debian 6.1.38-2+sr1 (2023-08-03) ** Command line: console=ttymxc0,115200 deferred_probe_timeout=10 ahci_imx.hotplug=1 cma=128M log_level=7 net.ifnames=0 ** Tainted: C (1024) * staging driver was loaded ** Kernel log: [ 18.664358] Registered IR keymap rc-empty [ 18.716304] rc rc0: gpio_ir_recv as /devices/platform/ir-receiver/rc/rc0 [ 18.759979] imx-ipuv3 240.ipu: IPUv3H probed [ 18.774524] rc rc0: lirc_dev: driver gpio_ir_recv registered at minor = 0, raw IR receiver, no transmitter [ 18.800230] imx-ipuv3 280.ipu: IPUv3H probed [ 18.815890] input: gpio_ir_recv as /devices/platform/ir-receiver/rc/rc0/input0 [ 18.848755] mc: Linux media interface: v0.10 [ 18.947000] etnaviv etnaviv: bound 13.gpu (ops gpu_ops [etnaviv]) [ 18.953152] videodev: Linux video capture interface: v2.00 [ 19.011893] dwhdmi-imx 12.hdmi: Detected HDMI TX controller v1.30a with HDCP (DWC HDMI 3D TX PHY) [ 19.040476] etnaviv etnaviv: bound 134000.gpu (ops gpu_ops [etnaviv]) [ 19.078395] imx_media_common: module is from the staging directory, the quality is unknown, you have been warned. [ 19.096468] etnaviv etnaviv: bound 2204000.gpu (ops gpu_ops [etnaviv]) [ 19.103221] etnaviv-gpu 13.gpu: model: GC2000, revision: 5108 [ 19.136549] imx6_media: module is from the staging directory, the quality is unknown, you have been warned. [ 19.167734] etnaviv-gpu 134000.gpu: model: GC320, revision: 5007 [ 19.211360] etnaviv-gpu 2204000.gpu: model: GC355, revision: 1215 [ 19.217588] etnaviv-gpu 2204000.gpu: Ignoring GPU with VG and FE2.0 [ 19.242861] CAN device driver interface [ 19.311072] [drm] Initialized etnaviv 1.3.0 20151214 for etnaviv on minor 0 [ 19.330363] coda 204.vpu: firmware: failed to load vpu_fw_imx6q.bin (-2) [ 19.337504] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware [ 19.352112] coda 204.vpu: firmware: failed to load vpu_fw_imx6q.bin (-2) [ 19.359277] coda 204.vpu: Direct firmware load for vpu_fw_imx6q.bin failed with error -2 [ 19.382870] fsl-ssi-dai 2028000.ssi: No cache defaults, reading back from HW [ 19.419980] imx-drm display-subsystem: bound imx-ipuv3-crtc.2 (ops imx_drm_exit [imxdrm]) [ 19.429343] coda 204.vpu: firmware: direct-loading firmware vpu/vpu_fw_imx6q.bin [ 19.454390] imx-drm display-subsystem: bound imx-ipuv3-crtc.3 (ops imx_drm_exit [imxdrm]) [ 19.461379] coda 204.vpu: Using fallback firmware vpu/vpu_fw_imx6q.bin [ 19.511767] coda 204.vpu: Firmware code revision: 46076 [ 19.517435] coda 204.vpu: Initialized CODA960. [ 19.522318] coda 204.vpu: Firmware version: 3.1.1 [ 19.538475] imx-drm display-subsystem: bound imx-ipuv3-crtc.6 (ops imx_drm_exit [imxdrm]) [ 19.582536] imx-drm display-subsystem: bound imx-ipuv3-crtc.7 (ops imx_drm_exit [imxdrm]) [ 19.614946] coda 204.vpu: coda-jpeg-encoder registered as video0 [ 19.626811] imx-drm display-subsystem: bound 12.hdmi (ops dw_hdmi_imx_ops [dw_hdmi_imx]) [ 19.678814] [drm] Initialized imx-drm 1.0.0 20120507 for display-subsystem on minor 1 [ 19.688579] coda 204.vpu: coda-jpeg-decoder registered as video1 [ 19.705350] imx_thermal 20c8000.anatop:tempmon: Extended Commercial CPU temperature grade - max:105C critical:100C passive:95C [ 19.726904] coda 204.vpu: coda-video-encoder registered as video2 [ 19.746329] imx-drm display-subsystem: [drm] Cannot find any crtc or sizes [ 19.768188] coda 204.vpu: coda-video-decoder registered as video3 [ 19.823963] imx-drm display-subsystem: [drm] Cannot find any crtc or sizes [ 19.888081] caam 210.crypto: Entropy delay = 3200 [ 19.953984] caam 210.crypto: Instantiated RNG4 SH0 [ 20.014746] caam 210.crypto: Instantiated RNG4 SH1 [ 20.051209] caam 210.crypto: device ID = 0x0a160100 (Era 4) [ 20.057950] caam 210.crypto: job rings = 2, qi = 0 [ 20.258432] sgtl5000 0-000a: sgtl5000 revision 0x11 [ 20.320280] sgtl5000 0-000a: Using internal LDO instead of VDDD: check ER1 erratum [ 20.553197] debugfs: File 'Headphone Jack' in directory 'dapm' already present! [ 20.687846] imx6_media_csi: module is from the staging directory, the quality is unknown, you have been warned. [ 20.694504] imx6_media_csi: module is from the staging dire
Bug#993859: linux-image-5.10.0-8-armmp: HDMI audio playback broken on i.MX6 HummingBoard
Package: src:linux Version: 5.10.46-4 Severity: normal X-Debbugs-Cc: josua.maye...@gmail.com Dear Maintainer, During testing I found that audio playback to the HDMI port produces just loud noise. I was playing the amarok jingle as a test: ogg123 -d alsa -o dev:dmix:CARD=DWHDMI first_run_jingle.ogg Hopefully I'll find some time to investiaget - find a point where it still worked, and bisect. Sincerely Josua Mayer This worked previously, but I can put my finger on when exactly. CVhanges since then: -- Package-specific info: ** Version: Linux version 5.10.0-8-armmp (debian-ker...@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.46-4 (2021-08-03) ** Command line: console=ttymxc0,115200 deferred_probe_timeout=10 ahci_imx.hotplug=1 log_level=7 net.ifnames=0 cma=128M ** Tainted: WCE (9728) * kernel issued warning * staging driver was loaded * unsigned module was loaded ** Kernel log: [ 12.069422] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point. [ 12.096480] systemd[1]: Reached target Local Encrypted Volumes. [ 12.120468] systemd[1]: Reached target Paths. [ 12.140339] systemd[1]: Reached target Remote File Systems. [ 12.160262] systemd[1]: Reached target Slices. [ 12.176432] systemd[1]: Reached target Swap. [ 12.193295] systemd[1]: Listening on fsck to fsckd communication Socket. [ 12.216699] systemd[1]: Listening on initctl Compatibility Named Pipe. [ 12.241412] systemd[1]: Listening on Journal Audit Socket. [ 12.265183] systemd[1]: Listening on Journal Socket (/dev/log). [ 12.289322] systemd[1]: Listening on Journal Socket. [ 12.318746] systemd[1]: Listening on udev Control Socket. [ 12.341053] systemd[1]: Listening on udev Kernel Socket. [ 12.365221] systemd[1]: Condition check resulted in Huge Pages File System being skipped. [ 12.379484] systemd[1]: Mounting POSIX Message Queue File System... [ 12.416554] systemd[1]: Mounting Kernel Debug File System... [ 12.461157] systemd[1]: Mounting Kernel Trace File System... [ 12.502351] systemd[1]: Starting Create list of static device nodes for the current kernel... [ 12.537094] systemd[1]: Starting Load Kernel Module configfs... [ 12.569557] systemd[1]: Starting Load Kernel Module drm... [ 12.601128] systemd[1]: Starting Load Kernel Module fuse... [ 12.672399] systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped. [ 12.711060] fuse: init (API version 7.32) [ 12.726776] systemd[1]: Starting File System Check on Root Device... [ 12.768988] systemd[1]: Starting Journal Service... [ 12.818378] systemd[1]: Starting Load Kernel Modules... [ 12.866644] systemd[1]: Starting Coldplug All udev Devices... [ 12.981618] systemd[1]: Mounted POSIX Message Queue File System. [ 13.014393] systemd[1]: Mounted Kernel Debug File System. [ 13.068936] systemd[1]: Mounted Kernel Trace File System. [ 13.115109] systemd[1]: Finished Create list of static device nodes for the current kernel. [ 13.159261] systemd[1]: modprobe@configfs.service: Succeeded. [ 13.185653] systemd[1]: Finished Load Kernel Module configfs. [ 13.226694] systemd[1]: modprobe@drm.service: Succeeded. [ 13.248464] systemd[1]: Finished Load Kernel Module drm. [ 13.286712] systemd[1]: modprobe@fuse.service: Succeeded. [ 13.310263] systemd[1]: Finished Load Kernel Module fuse. [ 13.351342] systemd[1]: Finished File System Check on Root Device. [ 13.395286] systemd[1]: Finished Load Kernel Modules. [ 13.448559] systemd[1]: Mounting FUSE Control File System... [ 13.494279] systemd[1]: Mounting Kernel Configuration File System... [ 13.554210] systemd[1]: Started File System Check Daemon to report status. [ 13.610566] systemd[1]: Starting Remount Root and Kernel File Systems... [ 13.682070] systemd[1]: Starting Apply Kernel Variables... [ 13.754329] systemd[1]: Mounted FUSE Control File System. [ 13.823376] systemd[1]: Mounted Kernel Configuration File System. [ 13.927190] systemd[1]: Finished Apply Kernel Variables. [ 13.932734] EXT4-fs (mmcblk1p1): re-mounted. Opts: (null) [ 13.982485] systemd[1]: Started Journal Service. [ 14.285169] systemd-journald[170]: Received client request to flush runtime journal. [ 14.329445] systemd-journald[170]: File /var/log/journal/2ebf67f9996a43629433b9fd557084ee/system.journal corrupted or uncleanly shut down, renaming and replacing. [ 16.708767] random: crng init done [ 16.712184] random: 7 urandom warning(s) missed due to ratelimiting [ 17.413602] Registered IR keymap rc-empty [ 17.500182] rc rc0: gpio_ir_recv as /devices/platform/ir-receiver/rc/rc0 [ 17.513362] imx-ipuv3 240.ipu: IPUv3H probed [ 17.588254] rc rc0: lirc_dev: driver gpio_ir_recv registered at minor = 0, raw IR receiver, no transmitter [ 17.764881] input: gpio_ir_recv as /devices/platform/ir-receiver/rc/rc0/input0 [ 17.8
Bug#987019: (no subject)
Hi Vincent, Thanks for your quick reply (which I failed to notice ) So I did a test today with GPIO_MXC=m, and initramfs-tools in default configuration. gpio_mxc module is included in initramfs automatically, and the system can boot from microSD just fine. Therefore, setting it as a module would do. Yours sincerely Josua mayer
Bug#987365: linux-image-5.10.0-6-armmp: please enabvle support for i.mx6 mipi-csi capture devices
Package: src:linux Version: 5.10.28-1 Severity: wishlist Tags: patch X-Debbugs-Cc: josua.maye...@gmail.com Dear Maintainer, Please enable support for the mipi-csi capture devices on i.MX6 SoCs, as used e.g. by the SolidRun i.MX6 HummingBoard (config patch attached). Yours sincerely Josua Mayer -- Package-specific info: ** Version: Linux version 5.10.0-6-armmp (debian-ker...@lists.debian.org) (arm-linux-gnueabihf-gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.28-1 (2021-04-09) ** Command line: console=ttymxc0,115200 deferred_probe_timeout=10 ahci_imx.hotplug=1 log_level=7 net.ifnames=0 ** Tainted: WCE (9728) * kernel issued warning * staging driver was loaded * unsigned module was loaded ** Kernel log: [ 11.819025] systemd[1]: modprobe@fuse.service: Succeeded. [ 11.834720] systemd[1]: Finished Load Kernel Module fuse. [ 11.859671] systemd[1]: Finished Load Kernel Modules. [ 11.879573] systemd[1]: Finished Remount Root and Kernel File Systems. [ 11.915841] systemd[1]: Mounting FUSE Control File System... [ 11.955104] systemd[1]: Mounting Kernel Configuration File System... [ 11.998308] systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. [ 12.007284] systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped. [ 12.023562] systemd[1]: Starting Load/Save Random Seed... [ 12.050667] systemd[1]: Starting Apply Kernel Variables... [ 12.078727] systemd[1]: Starting Create System Users... [ 12.114011] systemd[1]: Started Journal Service. [ 12.303087] systemd-journald[173]: Received client request to flush runtime journal. [ 14.239809] Registered IR keymap rc-empty [ 14.289888] rc rc0: gpio_ir_recv as /devices/platform/ir-receiver/rc/rc0 [ 14.302153] imx-ipuv3 240.ipu: IPUv3H probed [ 14.329978] imx-ipuv3 280.ipu: IPUv3H probed [ 14.344837] rc rc0: lirc_dev: driver gpio_ir_recv registered at minor = 0, raw IR receiver, no transmitter [ 14.469667] input: gpio_ir_recv as /devices/platform/ir-receiver/rc/rc0/input0 [ 14.512465] random: crng init done [ 14.515899] random: 7 urandom warning(s) missed due to ratelimiting [ 14.560825] imx_media_common: module is from the staging directory, the quality is unknown, you have been warned. [ 14.618396] imx6_media: module is from the staging directory, the quality is unknown, you have been warned. [ 14.626716] etnaviv etnaviv: bound 13.gpu (ops gpu_ops [etnaviv]) [ 14.644798] coda 204.vpu: firmware: failed to load vpu_fw_imx6q.bin (-2) [ 14.651935] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware [ 14.661415] coda 204.vpu: Direct firmware load for vpu_fw_imx6q.bin failed with error -2 [ 14.708623] etnaviv etnaviv: bound 134000.gpu (ops gpu_ops [etnaviv]) [ 14.740237] coda 204.vpu: firmware: direct-loading firmware vpu/vpu_fw_imx6q.bin [ 14.756779] coda 204.vpu: Using fallback firmware vpu/vpu_fw_imx6q.bin [ 14.768056] coda 204.vpu: Firmware code revision: 46076 [ 14.773727] coda 204.vpu: Initialized CODA960. [ 14.778621] coda 204.vpu: Firmware version: 3.1.1 [ 14.785300] coda 204.vpu: encoder registered as video0 [ 14.795329] coda 204.vpu: decoder registered as video1 [ 14.801191] coda 204.vpu: encoder registered as video2 [ 14.807040] coda 204.vpu: decoder registered as video3 [ 14.813297] etnaviv etnaviv: bound 2204000.gpu (ops gpu_ops [etnaviv]) [ 14.819955] etnaviv-gpu 13.gpu: model: GC2000, revision: 5108 [ 14.830926] etnaviv-gpu 134000.gpu: model: GC320, revision: 5007 [ 14.837222] etnaviv-gpu 2204000.gpu: model: GC355, revision: 1215 [ 14.843443] etnaviv-gpu 2204000.gpu: Ignoring GPU with VG and FE2.0 [ 14.850929] [drm] Initialized etnaviv 1.3.0 20151214 for etnaviv on minor 0 [ 14.864206] imx-drm display-subsystem: bound imx-ipuv3-crtc.2 (ops imx_drm_exit [imxdrm]) [ 14.938450] imx-drm display-subsystem: bound imx-ipuv3-crtc.3 (ops imx_drm_exit [imxdrm]) [ 14.991703] imx-drm display-subsystem: bound imx-ipuv3-crtc.6 (ops imx_drm_exit [imxdrm]) [ 15.041668] CAN device driver interface [ 15.074860] imx-drm display-subsystem: bound imx-ipuv3-crtc.7 (ops imx_drm_exit [imxdrm]) [ 15.140711] dwhdmi-imx 12.hdmi: Detected HDMI TX controller v1.30a with HDCP (DWC HDMI 3D TX PHY) [ 15.175608] fsl-ssi-dai 2028000.ssi: No cache defaults, reading back from HW [ 15.225615] imx-drm display-subsystem: bound 12.hdmi (ops dw_hdmi_imx_ops [dw_hdmi_imx]) [ 15.293255] [drm] Initialized imx-drm 1.0.0 20120507 for display-subsystem on minor 1 [ 15.347856] imx-drm display-subsystem: [drm] Cannot find any crtc or sizes [ 15.899289] sgtl5000 0-000a: Error reading chip id -6 [ 16.087363] imx_thermal 20c8000.anatop:tempmon: Extended Commercial CPU temperature grade - max:105C critical:100C passive:95C [ 16.168504] sd 0:0:0:0
Bug#987361: linux-image-5.10.0-6-armmp: bluetooth broken on i.MX6 Cubox-i and related devices
Package: src:linux Version: 5.10.28-1 Severity: important Tags: patch X-Debbugs-Cc: josua.maye...@gmail.com Dear Maintainer, Bluetooth drivers for the two chips used on SolidRun i.MX6 SoMs have recently disappeared from the debian kernel package. Please re-add them, patch attached and verified with both BCM4330 and WL1837. Yours sincerely Josua Mayer -- Package-specific info: ** Version: Linux version 5.10.0-6-armmp (debian-ker...@lists.debian.org) (arm-linux-gnueabihf-gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.28-1 (2021-04-09) ** Command line: root=/dev/mmcblk1p1 console=ttymxc0,115200 deferred_probe_timeout=10 log_level=7 net.ifnames=0 ** Tainted: WE (8704) * kernel issued warning * unsigned module was loaded ** Kernel log: [ 10.481988] systemd[1]: Mounting Kernel Debug File System... [ 10.510173] systemd[1]: Mounting Kernel Trace File System... [ 10.539156] systemd[1]: Starting Create list of static device nodes for the current kernel... [ 10.570585] systemd[1]: Starting Load Kernel Module configfs... [ 10.598475] systemd[1]: Starting Load Kernel Module drm... [ 10.631165] systemd[1]: Starting Load Kernel Module fuse... [ 10.654693] systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped. [ 10.664703] systemd[1]: Condition check resulted in File System Check on Root Device being skipped. [ 10.675493] fuse: init (API version 7.32) [ 10.698147] systemd[1]: Starting Journal Service... [ 10.734232] systemd[1]: Starting Load Kernel Modules... [ 10.763521] systemd[1]: Starting Remount Root and Kernel File Systems... [ 10.799102] systemd[1]: Starting Coldplug All udev Devices... [ 10.835732] systemd[1]: Mounted POSIX Message Queue File System. [ 10.844498] EXT4-fs (mmcblk1p1): re-mounted. Opts: (null) [ 10.869237] systemd[1]: Mounted Kernel Debug File System. [ 10.891964] systemd[1]: Mounted Kernel Trace File System. [ 10.917529] systemd[1]: Finished Create list of static device nodes for the current kernel. [ 10.949890] systemd[1]: modprobe@configfs.service: Succeeded. [ 10.958122] systemd[1]: Finished Load Kernel Module configfs. [ 10.985586] systemd[1]: modprobe@drm.service: Succeeded. [ 10.993079] systemd[1]: Finished Load Kernel Module drm. [ 11.021581] systemd[1]: modprobe@fuse.service: Succeeded. [ 11.029043] systemd[1]: Finished Load Kernel Module fuse. [ 11.051899] systemd[1]: Started Journal Service. [ 11.258052] systemd-journald[196]: Received client request to flush runtime journal. [ 11.288371] systemd-journald[196]: File /var/log/journal/9bbcae0a3ade4af68637450cb7940ea7/system.journal corrupted or uncleanly shut down, renaming and replacing. [ 12.656525] Registered IR keymap rc-empty [ 12.661105] rc rc0: gpio_ir_recv as /devices/platform/ir-receiver/rc/rc0 [ 12.672050] rc rc0: lirc_dev: driver gpio_ir_recv registered at minor = 0, raw IR receiver, no transmitter [ 12.703052] input: gpio_ir_recv as /devices/platform/ir-receiver/rc/rc0/input1 [ 12.842870] rc rc0: two consecutive events of type space [ 12.847048] imx-ipuv3 240.ipu: IPUv3H probed [ 12.858932] etnaviv etnaviv: bound 13.gpu (ops gpu_ops [etnaviv]) [ 12.875330] imx-ipuv3 280.ipu: IPUv3H probed [ 12.875434] etnaviv etnaviv: bound 134000.gpu (ops gpu_ops [etnaviv]) [ 12.964800] etnaviv etnaviv: bound 2204000.gpu (ops gpu_ops [etnaviv]) [ 12.972142] etnaviv-gpu 13.gpu: model: GC2000, revision: 5108 [ 13.069408] etnaviv-gpu 134000.gpu: model: GC320, revision: 5007 [ 13.077309] etnaviv-gpu 2204000.gpu: model: GC355, revision: 1215 [ 13.086018] etnaviv-gpu 2204000.gpu: Ignoring GPU with VG and FE2.0 [ 13.092640] coda 204.vpu: firmware: failed to load vpu_fw_imx6q.bin (-2) [ 13.099867] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware [ 13.109337] coda 204.vpu: Direct firmware load for vpu_fw_imx6q.bin failed with error -2 [ 13.183812] coda 204.vpu: firmware: failed to load vpu/vpu_fw_imx6q.bin (-2) [ 13.191344] coda 204.vpu: Direct firmware load for vpu/vpu_fw_imx6q.bin failed with error -2 [ 13.191801] [drm] Initialized etnaviv 1.3.0 20151214 for etnaviv on minor 0 [ 13.208912] coda 204.vpu: firmware: failed to load v4l-coda960-imx6q.bin (-2) [ 13.218928] coda 204.vpu: Direct firmware load for v4l-coda960-imx6q.bin failed with error -2 [ 13.230904] coda 204.vpu: firmware request failed [ 13.449889] imx-drm display-subsystem: bound imx-ipuv3-crtc.2 (ops imx_drm_exit [imxdrm]) [ 13.479351] imx-drm display-subsystem: bound imx-ipuv3-crtc.3 (ops imx_drm_exit [imxdrm]) [ 13.500464] imx-drm display-subsystem: bound imx-ipuv3-crtc.6 (ops imx_drm_exit [imxdrm]) [ 13.519712] imx-drm display-subsystem: bound imx-ipuv3-crtc.7 (ops imx_drm_exit [imxdrm]) [ 13.532962] dwhdmi-imx 12.hdmi: Detected HDMI TX controller v1.30a with HDCP
Bug#987054: xserver-xorg-core: modesetting driver fails with etnaviv when GPU is Vivante GC2000
Package: xserver-xorg-core Version: 2:1.20.10-3 Severity: normal Tags: patch X-Debbugs-Cc: josua.maye...@gmail.com Dear Maintainer, The Vivante GC2000 supported by etnaviv will report support for Desktop OpenGL 1.3, which in turn makes the modesetting driver fail because it requires 2.1 or later. There is already a patch [1] in the master branch of xorg addressing this issue, please consider backporting it to Debian for a chance of inclusion in Bullseye. Yours sincerely Josua Mayer [1] https://gitlab.freedesktop.org/xorg/xserver/-/commit/26004df63c25061586a967f3586795a75280acc2 -- Package-specific info: /etc/X11/X does not exist. /etc/X11/X is not a symlink. /etc/X11/X is not executable. VGA-compatible devices on PCI bus: -- /etc/X11/xorg.conf does not exist. Contents of /etc/X11/xorg.conf.d: - total 4 -rw-r--r-- 1 root root 205 Apr 16 13:04 etnaviv.conf /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 5.10.0-6-armmp (debian-ker...@lists.debian.org) (arm-linux-gnueabihf-gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.28-1 (2021-04-09) Xorg X server log files on system: -- -rw-r--r-- 1 debian debian 17199 Apr 15 22:03 /home/debian/.local/share/xorg/Xorg.1.log -rw-r--r-- 1 root root 16334 Apr 16 14:22 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [ 17477.754] X.Org X Server 1.20.10 X Protocol Version 11, Revision 0 [ 17477.754] Build Operating System: linux Debian [ 17477.754] Current Operating System: Linux sr-imx6 5.10.0-6-armmp #1 SMP Debian 5.10.28-1 (2021-04-09) armv7l [ 17477.754] Kernel command line: console=ttymxc0,115200 log_level=7 net.ifnames=0 console=tty cma=256M [ 17477.755] Build Date: 17 February 2021 09:17:43AM [ 17477.755] xorg-server 2:1.20.10-3 (https://www.debian.org/support) [ 17477.755] Current version of pixman: 0.40.0 [ 17477.755]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 17477.755] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 17477.755] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Apr 16 14:22:18 2021 [ 17477.760] (==) Using config directory: "/etc/X11/xorg.conf.d" [ 17477.760] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 17477.762] (==) No Layout section. Using the first Screen section. [ 17477.762] (==) No screen section available. Using defaults. [ 17477.762] (**) |-->Screen "Default Screen Section" (0) [ 17477.762] (**) | |-->Monitor "" [ 17477.769] (==) No device specified for screen "Default Screen Section". Using the first device section listed. [ 17477.769] (**) | |-->Device "etnaviv" [ 17477.769] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 17477.769] (**) Option "AutoAddGPU" "false" [ 17477.769] (==) Automatically adding devices [ 17477.769] (==) Automatically enabling devices [ 17477.769] (**) Not automatically adding GPU devices [ 17477.769] (==) Max clients allowed: 256, resource mask: 0x1f [ 17477.769] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 17477.769]Entry deleted from font path. [ 17477.769] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist. [ 17477.769]Entry deleted from font path. [ 17477.770] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist. [ 17477.770]Entry deleted from font path. [ 17477.770] (WW) The directory "/usr/share/fonts/X11/Type1" does not exist. [ 17477.770]Entry deleted from font path. [ 17477.770] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist. [ 17477.770]Entry deleted from font path. [ 17477.770] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist. [ 17477.770]Entry deleted from font path. [ 17477.770] (==) FontPath set to: /usr/share/fonts/X11/misc, built-ins [ 17477.770] (==) ModulePath set to "/usr/lib/xorg/modules" [ 17477.770] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 17477.770] (II) Loader magic: 0x655f58 [ 17477.770] (II) Module ABI versions: [ 17477.770]X.Org ANSI C Emulation: 0.4 [ 17477.770]X.Org Video Driver: 24.1 [ 17477.770]X.Org XInput driver : 24.1 [ 17477.770]X.Org Server Extension : 10.0 [ 17477.781]
Bug#987019: (no subject)
Dear Maintainers, I have found a configuration change that makes the microSD port function again, verified by rebuilding 5.10.0-6: diff --git a/debian/config/armhf/config b/debian/config/armhf/config index bdf0fa118db1..7c39d00d7aae 100644 --- a/debian/config/armhf/config +++ b/debian/config/armhf/config @@ -343,6 +343,7 @@ CONFIG_GPIO_DA9052=m CONFIG_GPIO_PALMAS=y CONFIG_GPIO_TWL4030=y CONFIG_GPIO_TWL6040=y +CONFIG_GPIO_MXC=y ## ## file: drivers/gpu/drm/Kconfig Yours sincerely Josua Mayer
Bug#987019: linux-image-5.10.0-6-armmp: microSD not recognized on i.MX6 HummingBoard
Package: src:linux Version: 5.10.28-1 Severity: important X-Debbugs-Cc: josua.maye...@gmail.com Dear Maintainer, Since the 5.10.0-5-armmp kernel package, microSD does no longer function on the i.MX6 Hummingboard Pro. The last known-working version is: 5.9.0-0.bpo.5-armmp Judging from a diff of the .config files between the 2 versions, the likely cause is removal of the GPIO driver for i.MX SoCs via CONFIG_GPIO_MXC. I will b reporting if re-enabling of that setting fixes the problem. Yours sincerely Josua Mayer ** Model information Hardware: Freescale i.MX6 Quad/DualLite (Device Tree) Revision: Device Tree model: SolidRun HummingBoard Dual/Quad ** PCI devices: 00:00.0 PCI bridge [0604]: Synopsys, Inc. DWC_usb3 / PCIe bridge [16c3:abcd] (rev 01) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport ** USB devices: Bus 002 Device 002: ID 04b4:6570 Cypress Semiconductor Corp. Unprogrammed CY7C65632/34 hub HX2VL Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: armhf (armv7l) Kernel: Linux 5.9.0-0.bpo.5-armmp (SMP w/2 CPU threads) Kernel taint flags: TAINT_WARN, TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-image-5.10.0-6-armmp depends on: ii initramfs-tools [linux-initramfs-tool] 0.140 ii kmod28-1 ii linux-base 4.6 Versions of packages linux-image-5.10.0-6-armmp recommends: pn apparmor pn firmware-linux-free Versions of packages linux-image-5.10.0-6-armmp suggests: pn debian-kernel-handbook pn linux-doc-5.10 Versions of packages linux-image-5.10.0-6-armmp is related to: pn firmware-amd-graphics pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x pn firmware-brcm80211 pn firmware-cavium pn firmware-intel-sound pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv pn firmware-iwlwifi pn firmware-libertas pn firmware-linux-nonfree ii firmware-misc-nonfree 20210315-2 pn firmware-myricom pn firmware-netxen pn firmware-qlogic pn firmware-realtek pn firmware-samsung pn firmware-siano ii firmware-ti-connectivity 20210315-2 pn xen-hypervisor -- no debconf information
Bug#958023: flash-kernel: please add layerscape lx2160a honeycomb and clearfog cx devices
Package: flash-kernel Version: 3.99 Severity: wishlist Tags: patch Dear Maintainer, Please add database entries for the new NXP LX2160a based SolidRun Devices. They are supported in mainline since linux 5.6.0, and currently have a distro-boot enabled vendor u-boot available. Yours sincerely josua Mayer -- System Information: Debian Release: 10.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: arm64 (aarch64) Kernel: Linux 5.5.0-trunk-arm64 (SMP w/16 CPU cores) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages flash-kernel depends on: ii debconf [debconf-2.0] 1.5.71 ii devio 1.2-1.2+b1 ii initramfs-tools0.133+deb10u1 ii linux-base 4.6 ii mtd-utils 1:2.0.1-1 ii ucf3.0038+nmu1 Versions of packages flash-kernel recommends: ii u-boot-tools 2019.01+dfsg-7 flash-kernel suggests no packages. -- Configuration Files: /etc/flash-kernel/db changed [not included] -- debconf information excluded >From 9065ffd52888230d9c33046908b8917c61246121 Mon Sep 17 00:00:00 2001 From: Josua Mayer Date: Fri, 17 Apr 2020 16:22:31 +0200 Subject: [PATCH] add db entries for SolidRun LX2160A Honeycomb and Clearfog CX The DTSs are included in Linux since the release of 5.6.0; and while not mainline, a vendor fork of U-Boot supporting distro-boot is available and has been tested to load the generic boot script on the Honeycomb Workstation. Signed-off-by: Josua Mayer --- db/all.db | 14 ++ 1 file changed, 14 insertions(+) diff --git a/db/all.db b/db/all.db index 3630a02..788a8c6 100644 --- a/db/all.db +++ b/db/all.db @@ -1695,6 +1695,20 @@ Boot-Script-Path: /boot/boot.scr U-Boot-Script-Name: bootscr.uboot-generic Required-Packages: u-boot-tools +Machine: SolidRun LX2160A Clearfog CX +Kernel-Flavors: arm64 +DTB-Id: freescale/fsl-lx2160a-clearfog-cx.dtb +Boot-Script-Path: /boot/boot.scr +U-Boot-Script-Name: bootscr.uboot-generic +Required-Packages: u-boot-tools + +Machine: SolidRun LX2160A Honeycomb +Kernel-Flavors: arm64 +DTB-Id: freescale/fsl-lx2160a-honeycomb.dtb +Boot-Script-Path: /boot/boot.scr +U-Boot-Script-Name: bootscr.uboot-generic +Required-Packages: u-boot-tools + Machine: Theobroma Systems RK3399-Q7 SoM Kernel-Flavors: arm64 DTB-Id: rockchip/rk3399-puma-haikou.dtb -- 2.26.0
Bug#948576: closed by Debian FTP Masters (reply to Ben Hutchings ) (Bug#948576: fixed in linux 5.5.17-1)
Thanks! \o/ Am 17.04.20 um 05:03 schrieb Debian Bug Tracking System: > This is an automatic notification regarding your Bug report > which was filed against the src:linux package: > > #948576: linux: please enable support for the layerscape SoCs and the > Honeycomb workstation board > > It has been closed by Debian FTP Masters > (reply to Ben Hutchings ). > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Debian FTP Masters > (reply to Ben Hutchings ) > by > replying to this email. > >
Bug#951409: (no subject)
Hi Joel, I have already opened a bug report requesting the comphy driver be enabled in Debian. Sadly I did not notice the regression, so I only marked it as low priority...: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948298 But clearly it was a breaking change between buster and buster-backports now. Yours sincerely Josua Mayer
Bug#948576: Update - tested with 5.5.4
Hi everybody, I have rebased my patch on 5.5.4-1~exp1 from the packaging master branch. While at it I have also cleaned it up removing any options that were implicitly selected, leaving only those that really need to be enabled manually. Boot tested, everything that worked before still does, namely the standalone ethernet port, USB, microSD and eMMC. Please consider enabling these config options - The device-tree for the Honeycomb Workstation has been merged with 5.6-rc1 and it would be great to have Debian work as pieces start landing upstream. Yours sincerely Josua Mayer >From 17590120f8352874ba1b7c686c3c3fd46c0c Mon Sep 17 00:00:00 2001 From: Josua Mayer Date: Tue, 18 Feb 2020 21:36:40 +0100 Subject: [PATCH] enable support for the Honeycomb arm64 workstation This enables support for the Layerscape architecture in general, as well as - drivers for the Soc listed in (fsl-lx2160a.dtsi) - drivers for peripherals listed in (fsl-lx2160a-cex7.dtsi) . Signed-off-by: Josua Mayer --- debian/config/arm64/config | 47 ++ 1 file changed, 47 insertions(+) diff --git a/debian/config/arm64/config b/debian/config/arm64/config index a2638cf1307a..0796f1fd3f59 100644 --- a/debian/config/arm64/config +++ b/debian/config/arm64/config @@ -56,6 +56,7 @@ CONFIG_KVM=y CONFIG_ARCH_SUNXI=y CONFIG_ARCH_BCM2835=y CONFIG_ARCH_HISI=y +CONFIG_ARCH_LAYERSCAPE=y CONFIG_ARCH_MESON=y CONFIG_ARCH_MVEBU=y CONFIG_ARCH_QCOM=y @@ -100,6 +101,7 @@ CONFIG_ANDROID=y CONFIG_SATA_AHCI_PLATFORM=m CONFIG_AHCI_CEVA=m CONFIG_AHCI_MVEBU=m +CONFIG_AHCI_QORIQ=m CONFIG_AHCI_TEGRA=m CONFIG_AHCI_XGENE=m CONFIG_SATA_AHCI_SEATTLE=m @@ -117,6 +119,11 @@ CONFIG_HISILICON_LPC=y CONFIG_QCOM_EBI2=y CONFIG_TEGRA_ACONNECT=y +## +## file: drivers/bus/fsl-mc/Kconfig +## +CONFIG_FSL_MC_BUS=y + ## ## file: drivers/char/hw_random/Kconfig ## @@ -182,6 +189,7 @@ CONFIG_SUN8I_DE2_CCU=y CONFIG_CPU_FREQ_DEFAULT_GOV_SCHEDUTIL=y ## end choice CONFIG_CPUFREQ_DT=m +CONFIG_QORIQ_CPUFREQ=m ## ## file: drivers/cpufreq/Kconfig.arm @@ -203,6 +211,11 @@ CONFIG_CRYPTO_DEV_QCE=m CONFIG_CRYPTO_DEV_QCOM_RNG=m CONFIG_CRYPTO_DEV_SAFEXCEL=m +## +## file: drivers/crypto/caam/Kconfig +## +CONFIG_CRYPTO_DEV_FSL_DPAA2_CAAM=m + ## ## file: drivers/crypto/cavium/cpt/Kconfig ## @@ -249,6 +262,7 @@ CONFIG_QCOM_HIDMA=m ## file: drivers/edac/Kconfig ## CONFIG_EDAC=y +CONFIG_EDAC_LAYERSCAPE=m CONFIG_EDAC_THUNDERX=m CONFIG_EDAC_XGENE=m @@ -278,6 +292,7 @@ CONFIG_GPIO_ZYNQ=m CONFIG_GPIO_PCA953X=y CONFIG_GPIO_PCA953X_IRQ=y CONFIG_GPIO_MAX77620=y +CONFIG_GPIO_MPC8XXX=y ## ## file: drivers/gpu/drm/Kconfig @@ -388,6 +403,7 @@ CONFIG_I2C_HID=m ## ## file: drivers/hwmon/Kconfig ## +CONFIG_SENSORS_LM90=m CONFIG_SENSORS_XGENE=m ## @@ -406,6 +422,7 @@ CONFIG_I2C=y CONFIG_I2C_BCM2835=m CONFIG_I2C_DESIGNWARE_PLATFORM=m CONFIG_I2C_GPIO=m +CONFIG_I2C_IMX=m CONFIG_I2C_MESON=m CONFIG_I2C_MV64XXX=m CONFIG_I2C_PXA=m @@ -418,6 +435,11 @@ CONFIG_I2C_XLP9XX=m CONFIG_I2C_CROS_EC_TUNNEL=m CONFIG_I2C_XGENE_SLIMPRO=m +## +## file: drivers/i2c/muxes/Kconfig +## +CONFIG_I2C_MUX_PCA954x=m + ## ## file: drivers/iio/accel/Kconfig ## @@ -560,6 +582,7 @@ CONFIG_MMC_QCOM_DML=y CONFIG_MMC_SDHCI_ACPI=m CONFIG_MMC_SDHCI_PLTFM=m CONFIG_MMC_SDHCI_OF_ARASAN=m +CONFIG_MMC_SDHCI_OF_ESDHC=m CONFIG_MMC_SDHCI_TEGRA=m CONFIG_MMC_SDHCI_F_SDH30=m CONFIG_MMC_SDHCI_IPROC=m @@ -666,6 +689,18 @@ CONFIG_NET_VENDOR_DLINK=y CONFIG_SUNDANCE=m # CONFIG_SUNDANCE_MMIO is not set +## +## file: drivers/net/ethernet/freescale/Kconfig +## +CONFIG_FSL_XGMAC_MDIO=m +CONFIG_NET_VENDOR_FREESCALE=y + +## +## file: drivers/net/ethernet/freescale/dpaa2/Kconfig +## +CONFIG_FSL_DPAA2_ETH=m +CONFIG_FSL_DPAA2_PTP_CLOCK=m + ## ## file: drivers/net/ethernet/hisilicon/Kconfig ## @@ -967,6 +1002,11 @@ CONFIG_AXP288_FUEL_GAUGE=m CONFIG_CHARGER_QCOM_SMBB=m CONFIG_CHARGER_CROS_USBPD=m +## +## file: drivers/ptp/Kconfig +## +CONFIG_PTP_1588_CLOCK_QORIQ=m + ## ## file: drivers/pwm/Kconfig ## @@ -1030,6 +1070,7 @@ CONFIG_RTC_DRV_ARMADA38X=m CONFIG_RTC_DRV_PM8XXX=m CONFIG_RTC_DRV_TEGRA=y CONFIG_RTC_DRV_XGENE=y +CONFIG_RTC_DRV_PCF2127=m ## ## file: drivers/scsi/Kconfig @@ -1042,6 +1083,11 @@ CONFIG_SCSI_DMX3191D=m CONFIG_SCSI_HISI_SAS=m CONFIG_SCSI_HISI_SAS_PCI=m +## +## file: drivers/soc/fsl/Kconfig +## +CONFIG_FSL_MC_DPIO=m + ## ## file: drivers/soc/bcm/Kconfig ## @@ -1075,6 +1121,7 @@ CONFIG_SPI_ARMADA_3700=m CONFIG_SPI_BCM2835=m CONFIG_SPI_BCM2835AUX=m CONFIG_SPI_MESON_SPIFC=m +CONFIG_SPI_NXP_FLEXSPI=m CONFIG_SPI_ROCKCHIP=m CONFIG_SPI_QUP=m CONFIG_SPI_TEGRA114=m -- 2.25.0
Bug#948576: linux: please enable support for the layerscape SoCs and the Honeycomb workstation board
Source: linux
Severity: wishlist
Tags: patch
Dear Maintainer,
Please enable a set of drivers requried for the layerscape based arm64
honeycomb board.
It is a mini-itx board for use as a workstation machine. Its support in
mainline is not complete yet,
but many bits are already functional.
I am attaching a patch for enabling the options I have found through reading
the dts from RMKs cex7 branch.
Changes were tested on 5.5-rc5 built from the debian kernel packaging tree.
Some drivers are currently enabled implicitly, i.e. not listed in either
debian/config/{,arm64/}config:
CONFIG_PTP_1588_CLOCK=m
CONFIG_I2C_MUX=m
CONFIG_SENSORS_LM90=m
CONFIG_RTC_DRV_PCF2127=m
CONFIG_ARM_GIC_V3_ITS_FSL_MC=y
^^ Not sure how you decide when to make options explicit, and when not ... so
these are *not* included in my attached patch!
The PCI Express driver is still pending inclusion in Linux:
https://patchwork.kernel.org/patch/11253015/
Once that lands, CONFIG_PCIE_LAYERSCAPE_GEN4=m should also be enabled.
Yours sincerely
Josua Mayer
-- System Information:
Debian Release: 10.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: arm64 (aarch64)
Kernel: Linux 5.5.0-rc5-arm64 (SMP w/16 CPU cores)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
>From 216cdc9faf2cdcbdd593af90a8b7bacc4195c2ac Mon Sep 17 00:00:00 2001
From: Josua Mayer
Date: Thu, 9 Jan 2020 23:36:15 +
Subject: [PATCH] enable support for the Honeycomb arm64 workstation
This enables support for the Layerscape architecture in general,
as well as
- drivers for the Soc listed in (fsl-lx2160a.dtsi)
- drivers for peripherals listed in (fsl-lx2160a-cex7.dtsi)
.
Some drivers are currently enabled implicitly, i.e. not listed in either
debian/config/{,arm64/}config:
CONFIG_PTP_1588_CLOCK=m
CONFIG_I2C_MUX=m
CONFIG_SENSORS_LM90=m
CONFIG_RTC_DRV_PCF2127=m
CONFIG_ARM_GIC_V3_ITS_FSL_MC=y
The PCI Express driver is still pending inclusion in Linux:
https://patchwork.kernel.org/patch/11253015/
Once that lands, CONFIG_PCIE_LAYERSCAPE_GEN4=m should also be enabled.
Signed-off-by: Josua Mayer
---
debian/config/arm64/config | 51 ++
1 file changed, 51 insertions(+)
diff --git a/debian/config/arm64/config b/debian/config/arm64/config
index 9841e44ce42f..285d881310fc 100644
--- a/debian/config/arm64/config
+++ b/debian/config/arm64/config
@@ -67,6 +67,7 @@ CONFIG_ARCH_THUNDER2=y
CONFIG_ARCH_VEXPRESS=y
CONFIG_ARCH_XGENE=y
CONFIG_ARCH_ZYNQMP=y
+CONFIG_ARCH_LAYERSCAPE=y
##
## file: drivers/acpi/Kconfig
@@ -102,6 +103,7 @@ CONFIG_AHCI_MVEBU=m
CONFIG_AHCI_TEGRA=m
CONFIG_AHCI_XGENE=m
CONFIG_SATA_AHCI_SEATTLE=m
+CONFIG_AHCI_QORIQ=m
##
## file: drivers/bluetooth/Kconfig
@@ -116,6 +118,11 @@ CONFIG_HISILICON_LPC=y
CONFIG_QCOM_EBI2=y
CONFIG_TEGRA_ACONNECT=y
+##
+## file: drivers/bus/fsl-mc/Kconfig
+##
+CONFIG_FSL_MC_BUS=y
+
##
## file: drivers/char/hw_random/Kconfig
##
@@ -147,6 +154,7 @@ CONFIG_TCG_TIS_I2C_INFINEON=m
CONFIG_COMMON_CLK_RK808=y
CONFIG_COMMON_CLK_HI655X=y
CONFIG_COMMON_CLK_XGENE=y
+CONFIG_CLK_QORIQ=y
##
## file: drivers/clk/bcm/Kconfig
@@ -181,6 +189,7 @@ CONFIG_SUN8I_DE2_CCU=y
CONFIG_CPU_FREQ_DEFAULT_GOV_SCHEDUTIL=y
## end choice
CONFIG_CPUFREQ_DT=m
+CONFIG_QORIQ_CPUFREQ=m
##
## file: drivers/cpufreq/Kconfig.arm
@@ -202,6 +211,11 @@ CONFIG_CRYPTO_DEV_QCE=m
CONFIG_CRYPTO_DEV_QCOM_RNG=m
CONFIG_CRYPTO_DEV_SAFEXCEL=m
+##
+## file: drivers/crypto/caam/Kconfig
+##
+CONFIG_CRYPTO_DEV_FSL_DPAA2_CAAM=m
+
##
## file: drivers/crypto/cavium/cpt/Kconfig
##
@@ -250,6 +264,7 @@ CONFIG_QCOM_HIDMA=m
CONFIG_EDAC=y
CONFIG_EDAC_THUNDERX=m
CONFIG_EDAC_XGENE=m
+CONFIG_EDAC_LAYERSCAPE=m
##
## file: drivers/extcon/Kconfig
@@ -277,6 +292,7 @@ CONFIG_GPIO_ZYNQ=m
CONFIG_GPIO_PCA953X=y
CONFIG_GPIO_PCA953X_IRQ=y
CONFIG_GPIO_MAX77620=y
+CONFIG_GPIO_MPC8XXX=y
##
## file: drivers/gpu/drm/Kconfig
@@ -388,6 +404,7 @@ CONFIG_I2C_HID=m
## file: drivers/hwmon/Kconfig
##
CONFIG_SENSORS_XGENE=m
+CONFIG_SENSORS_LM90=m
##
## file: drivers/hwspinlock/Kconfig
@@ -398,6 +415,7 @@ CONFIG_HWSPINLOCK_QCOM=m
## file: drivers/i2c/Kconfig
##
CONFIG_I2C=y
+CONFIG_I2C_MUX=m
##
## file: drivers/i2c/busses/Kconfig
@@ -416,6 +434,12 @@ CONFIG_I2C_THUNDERX=m
CONFIG_I2C_XLP9XX=m
CONFIG_I2C_CROS_EC_TUNNEL=m
CONFIG_I2C_XGENE_SLIMPRO=m
+CONFIG_I2C_IMX=m
+
+##
+## file: drivers/i2c/muxes/Kconfig
+##
+CONFIG_I2C_MUX_PCA954x=m
##
## file: drivers/iio/accel/Kconfig
@@ -572,6 +596,7 @@ CONFIG_MMC_DW_ROCKCHIP=m
CONFIG_MMC_SUNXI=m
CONFIG_MMC_BCM2835=m
CONFIG_MMC_SDHCI_XENON=m
+CONFIG_MMC_SDHCI_OF_ESDHC=m
##
## file: drivers/mtd/spi-nor/Kconfig
@@ -660,6 +685,18 @@ CONFIG_NET_VENDOR_DLINK=y
CONFIG_SUNDANCE=m
# CONFIG_SUNDANCE_MMIO is not set
+##
+## file: drivers
Bug#948298: linux-image-5.3.0-0.bpo.2-armmp: please enable armada 38x comphy driver for armmp
Package: src:linux Version: 5.3.9-2~bpo10+1sr1 Severity: normal Tags: patch Dear Maintainer, As of Linux v5.1 a special comphy driver was introduced for Armada 38x SoCs. It is actively referenced by the dts for the Clearfog Base and Clearfog Pro - and used by the new Clearfog GTR (which has its device-tree posted to lkml in v3). Please enable this driver as a module for the armmp kernel flavour. I am attaching the patch to enable this module - and the dmesg of when I verified that the resulting kernel works as expected. Also, it would be nice if this change could make it into buster-backports ;) Yours sincerely Josua Mayer -- Package-specific info: ** Version: Linux version 5.3.0-0.bpo.2-armmp (debian-ker...@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-2)) #1 SMP Debian 5.3.9-2~bpo10+1sr1 (2020-01-06) ** Command line: console=ttyS0,115200 log_level=7 net.ifnames=0 ** Not tainted ** Kernel log: ** Model information [6.952015] usb 4-1: Manufacturer: TOSHIBA [6.956130] usb 4-1: SerialNumber: 0E70657012733A39 [6.967191] usb-storage 4-1:1.0: USB Mass Storage device detected [6.973990] scsi host4: usb-storage 4-1:1.0 [6.978439] usbcore: registered new interface driver usb-storage [6.985921] usbcore: registered new interface driver uas [6.986841] libphy: mdio: probed [7.118832] mv88e6085 f1072004.mdio-mii:04: switch 0x3900 detected: Marvell 88E6390, revision 1 [7.181531] libphy: mdio: probed [7.299011] mv88e6085 f1072004.mdio-mii:04: switch 0x3900 detected: Marvell 88E6390, revision 1 [7.352811] libphy: mdio: probed [7.478658] mv88e6085 f1072004.mdio-mii:04: switch 0x3900 detected: Marvell 88E6390, revision 1 [7.541070] libphy: mdio: probed [7.655533] mv88e6085 f1072004.mdio-mii:04: switch 0x3900 detected: Marvell 88E6390, revision 1 [7.716804] libphy: mdio: probed [7.832195] mv88e6085 f1072004.mdio-mii:04: switch 0x3900 detected: Marvell 88E6390, revision 1 [7.895216] libphy: mdio: probed [8.004389] scsi 4:0:0:0: Direct-Access TOSHIBA TransMemory 5.00 PQ: 0 ANSI: 0 CCS [8.017642] mv88e6085 f1072004.mdio-mii:04: switch 0x3900 detected: Marvell 88E6390, revision 1 [8.026886] sd 4:0:0:0: [sda] 2013184 512-byte logical blocks: (1.03 GB/983 MiB) [8.034467] sd 4:0:0:0: [sda] Write Protect is off [8.039301] sd 4:0:0:0: [sda] Mode Sense: 23 00 00 00 [8.039469] sd 4:0:0:0: [sda] No Caching mode page found [8.044814] sd 4:0:0:0: [sda] Assuming drive cache: write through [8.054320] sda: sda1 [8.058169] sd 4:0:0:0: [sda] Attached SCSI removable disk [8.080803] libphy: mdio: probed [8.212177] mv88e6085 f1072004.mdio-mii:04: switch 0x3900 detected: Marvell 88E6390, revision 1 [8.275624] libphy: mdio: probed [8.397802] mv88e6085 f1072004.mdio-mii:04: switch 0x3900 detected: Marvell 88E6390, revision 1 [8.460802] libphy: mdio: probed [8.580273] mv88e6085 f1072004.mdio-mii:04: switch 0x3900 detected: Marvell 88E6390, revision 1 [8.643294] libphy: mdio: probed [8.763092] mv88e6085 f1072004.mdio-mii:04: switch 0x3900 detected: Marvell 88E6390, revision 1 [8.830193] libphy: mdio: probed [8.900734] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [8.967203] mv88e6085 f1072004.mdio-mii:04: switch 0x3900 detected: Marvell 88E6390, revision 1 [9.028725] libphy: mdio: probed [9.110343] mv88e6085 f1072004.mdio-mii:04: switch 0x3900 detected: Marvell 88E6390, revision 1 [9.141298] Not activating Mandatory Access Control as /sbin/tomoyo-init does not exist. [9.172705] libphy: mdio: probed [9.954303] systemd[1]: Inserted module 'autofs4' [ 10.019965] systemd[1]: systemd 241 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid) [ 10.041719] systemd[1]: Detected architecture arm. [ 10.068617] systemd[1]: Set hostname to . [ 10.081427] systemd[1]: Failed to bump fs.file-max, ignoring: Invalid argument [ 10.595635] mv88e6085 f1072004.mdio-mii:04 lan8 (uninitialized): PHY [!soc!internal-regs!mdio@72004!switch0@4!mdio:01] driver [Marvell 88E6390] [ 10.608585] mv88e6085 f1072004.mdio-mii:04 lan8 (uninitialized): phy: setting supported 00,,22ef advertising 00,,22ef [ 10.612489] mv88e6085 f1072004.mdio-mii:04 lan7 (uninitialized): PHY [!soc!internal-regs!mdio@72004!switch0@4!mdio:02] driver [Marvell 88E6390] [ 10.622680] random: systemd: uninitialized urandom read (16 bytes read) [ 10.625451] mv88e6085 f1072004.mdio-mii:04 lan7 (uninitialized): phy: setting supported 00,,22ef advertising 00,,22ef [ 10.635967] mv88e6085 f1072004.mdio-mii:04 lan6 (uninitialized): PHY [!soc!internal-regs!mdio@72004!switch0@4!mdio:03] driver [Marvell 88E6390] [ 10.636784] random: systemd: uni
Bug#945967: libgstreamer-plugins-base1.0-dev: depends explicitly on mesa
Package: libgstreamer-plugins-base1.0-dev Severity: wishlist Dear Maintainer, The gstreamer devel packages currently depend explicitly on mesa -dev packages, libgl1-mesa-dev, libegl1-mesa-dev, libgles2-mesa-dev in particular. I suggest using the virtual packages libgl-dev for starters, which will make it a little easier to install custom providers of OpenGL cleanly. If there were virtual packages for gles2 and egl, I would suggest switching those too, but so far there isn't ... :( br Josua Mayer -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: arm64 (aarch64) Kernel: Linux 4.19.35-05162-gee5a4376dc84-dirty (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages libgstreamer-plugins-base1.0-dev depends on: ii gir1.2-gst-plugins-base-1.0 1.16.1-1 ii imx-gpu-viv-dev [libgles2-mesa-dev] 6.4.0.p1.0 ii libc6-dev [libc-dev] 2.29-3 pn libegl1-mesa-dev pn libgl1-mesa-dev ii libglib2.0-dev 2.62.3-1 ii libgstreamer-gl1.0-0 1.16.1-1 ii libgstreamer-plugins-base1.0-0 1.16.1-1 ii libgstreamer1.0-dev 1.16.1-1 ii liborc-0.4-dev 1:0.4.31-1 ii pkg-config 0.29-6 libgstreamer-plugins-base1.0-dev recommends no packages. libgstreamer-plugins-base1.0-dev suggests no packages.
Bug#939261: flash-kernel: please add missing models of Cubox-i
Package: flash-kernel Version: 3.99 Severity: wishlist Dear Maintainer, While most models of the i.MX6 Cubox-i and HummingBoard are in the flash-kernel database, the dual-lite variants of Cubox-i are missing: - SolidRun Cubox-i Solo/DualLite - SolidRun Cubox-i Solo/DualLite (1.5som) - SolidRun Cubox-i Solo/DualLite (1.5som+emmc) I have prepared the entries below based on the model fields in linux (master): Machine: SolidRun Cubox-i Solo/DualLite Kernel-Flavors: armmp DTB-Id: imx6dl-cubox-i.dtb Boot-Script-Path: /boot/boot.scr U-Boot-Script-Name: bootscr.imx-base bootscr.uboot-generic Required-Packages: u-boot-tools Machine: SolidRun Cubox-i Solo/DualLite (1.5som) Kernel-Flavors: armmp DTB-Id: imx6dl-cubox-i-som-v15.dtb Boot-Script-Path: /boot/boot.scr U-Boot-Script-Name: bootscr.imx-base bootscr.uboot-generic Required-Packages: u-boot-tools Machine: SolidRun Cubox-i Solo/DualLite (1.5som+emmc) Kernel-Flavors: armmp DTB-Id: imx6dl-cubox-i-emmc-som-v15.dtb Boot-Script-Path: /boot/boot.scr U-Boot-Script-Name: bootscr.imx-base bootscr.uboot-generic Required-Packages: u-boot-tools Please add these to the flash-kernel db. sincerely Josua Mayer -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable'), (90, 'unstable') Architecture: armhf (armv7l) Kernel: Linux 4.19.0-5-armmp (SMP w/2 CPU cores) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages flash-kernel depends on: ii debconf [debconf-2.0] 1.5.71 ii devio 1.2-1.2+b1 ii initramfs-tools0.133 ii linux-base 4.6 ii mtd-utils 1:2.0.1-1 ii ucf3.0038+nmu1 Versions of packages flash-kernel recommends: ii u-boot-tools 2019.01+dfsg-7 flash-kernel suggests no packages. -- debconf information excluded
Bug#934812: python3.7: please enable optimizations for arm64, too
Hi, That is an unexpected shout! How is arm64 different wrt gcc than the exhaustive list of architectures that both of these options have been enabled for already? Am 23.08.19 um 17:49 schrieb Thorsten Glaser: > On Thu, 15 Aug 2019, Josua Mayer wrote: > >> Please enable LTO and PGO for arm64 builds of python. > > No, please do NOT enable LTO builds because we use GCC. > > See https://lists.debian.org/debian-devel/2019/07/msg00611.html > and https://lists.debian.org/debian-devel/2019/07/msg00610.html > for more of this sad story (tl;dr: buggy, nobody cares). > > Thanks, > //mirabilos >
Bug#934812: python3.7: please enable optimizations for arm64, too
Package: python3.7 Version: 3.7.3-2 Severity: wishlist Tags: patch Dear Maintainer, Please enable LTO and PGO for arm64 builds of python. These optimizations area already enabled for an exhaustive list of architectures, including the slowest of arm. Please find attached a small patch extending the list of architectures for both pgo and lto. Yours sincerely Josua Mayer -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: arm64 (aarch64) Kernel: Linux 5.1.0-trunk-arm64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python3.7 depends on: ii libpython3.7-stdlib 3.7.3-2 ii mime-support 3.62 ii python3.7-minimal3.7.3-2 python3.7 recommends no packages. Versions of packages python3.7 suggests: ii binutils2.31.1-16 pn python3.7-doc pn python3.7-venv -- no debconf information diff --git a/debian/rules b/debian/rules index a43e5dd..6b1b34c 100755 --- a/debian/rules +++ b/debian/rules @@ -171,13 +171,13 @@ endif ifeq ($(DEB_HOST_GNU_TYPE),$(DEB_BUILD_GNU_TYPE)) ifeq ($(DEB_HOST_ARCH_OS),linux) -ifneq (,$(findstring $(DEB_HOST_ARCH), amd64 armel armhf i386 powerpc ppc64 ppc64el s390x)) +ifneq (,$(findstring $(DEB_HOST_ARCH), amd64 arm64 armel armhf i386 powerpc ppc64 ppc64el s390x)) with_pgo := yes endif endif endif -ifneq (,$(findstring $(DEB_HOST_ARCH), amd64 armel armhf i386 powerpc ppc64 ppc64el s390x)) +ifneq (,$(findstring $(DEB_HOST_ARCH), amd64 arm64 armel armhf i386 powerpc ppc64 ppc64el s390x)) with_lto := yes endif diff --git a/debian/rules b/debian/rules index a43e5dd..6b1b34c 100755 --- a/debian/rules +++ b/debian/rules @@ -171,13 +171,13 @@ endif ifeq ($(DEB_HOST_GNU_TYPE),$(DEB_BUILD_GNU_TYPE)) ifeq ($(DEB_HOST_ARCH_OS),linux) -ifneq (,$(findstring $(DEB_HOST_ARCH), amd64 armel armhf i386 powerpc ppc64 ppc64el s390x)) +ifneq (,$(findstring $(DEB_HOST_ARCH), amd64 arm64 armel armhf i386 powerpc ppc64 ppc64el s390x)) with_pgo := yes endif endif endif -ifneq (,$(findstring $(DEB_HOST_ARCH), amd64 armel armhf i386 powerpc ppc64 ppc64el s390x)) +ifneq (,$(findstring $(DEB_HOST_ARCH), amd64 arm64 armel armhf i386 powerpc ppc64 ppc64el s390x)) with_lto := yes endif
Bug#934303: ITP: stratis-cli -- cli interface to stratisd storage management service
Package: wnpp Severity: wishlist Owner: Josua Mayer * Package name: stratis-cli Version : 1.0.4 Upstream Author : RedHat, Inc. * URL : https://stratis-storage.github.io/ * License : Apache 2.0 Programming Lang: Python 3 Description : cli interface to stratisd storage management service Stratis is a storage management solution built on device-mapper and XFS, featuring both volume management and snapshot capability. Being a rather new solution stratis is not yet commonly used. Version 1.0 was released late 2018. Quoting their announcement, it "is ready for more widespread testing and evaluation by potential users". At this point the package will be useful for evaluation and testing of Stratis outside of RedHat systems. My personal motivation is that I am running Debian on a NAS, and want to explore Stratis on it. It is my believe that ultimately Stratis will be a much more user-friendly alternative to LVM - and interesting from a technology standpoint. Obviously the CLI client alone is not useful, instead my goal is to package both the daemon, and the management application. However the client utility is integral to testing of the daemon package, so it should be done first imo. What I am looking for in the community is co-maintainers /-developers and a packaging team to join for access to build infrastructure, as well as some assistance with the packaging if I come across roadblocks.
Bug#931707: linux: HW_RANDOM_OMAP disabled for arm64 --> please enable
Source: linux Severity: normal Dear Maintainer, While testing Debian 10 on a Marvell 8040 SoC I found that the rng and SSH were coming up extremely slow, taking over a minute to start. This is caused by somebody disabling the rng driver for arm64 kernels a long time ago: linux (4.14.13-1) unstable; urgency=medium ... [ Riku Voipio ] * [arm64] disable CONFIG_HW_RANDOM_OMAP until the IRQ storm bug is fixed What is this IRQ storm bug? Has it been fixed? Can we re-enable this driver? Yours sincerely Josua Mayer -- System Information: Debian Release: 10.0 APT prefers testing APT policy: (500, 'testing') Architecture: arm64 (aarch64) Kernel: Linux 5.1.0-trunk-arm64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#906696: flash-kernel: Please add an entry for the Rock64
Hi Vagrant, thanks for your quick response. I checked on buster - and it does carry a version exhibiting the described behaviour. So I think it is safe to establish rockchip/rk3328-rock64.dtb for rock64. ^^ which is also in line with pine64+: allwinner/sun50i-a64-pine64-plus.dtb After a lot of thought I have come to believe the sane approach is to use a boot.scr when flash-kernel is involved, just like all other boards do. No messing with efi partition like I tried earlier. So I propose using following machine entry: Machine: Pine64 Rock64 Kernel-Flavors: arm64 DTB-Id: rockchip/rk3328-rock64.dtb Boot-Script-Path: /boot/boot.scr U-Boot-Script-Name: bootscr.uboot-generic Required-Packages: u-boot-tools Yours sincerely Josua Mayer
Bug#906696: flash-kernel: Please add an entry for the Rock64
Hi Vagrant, Am 27.08.18 um 19:03 schrieb Vagrant Cascadian: > All arm64 linux dtbs are in sub-dirs, flash-kernel supports them in > sub-dirs, and u-boot should generally just append the value of fdtfile > to whatever search path and look for it there. How does flash-kernel support creating those sub directories? It seems to me that it will search for dtbs in sub directories, but then install them at the root level :( We have arrived in a world where those prefixes are established. Examples are: All marvell 8xxx based boards: include/configs/mvebu_armada-8k.h: "fdtfile=marvell/" CONFIG_DEFAULT_DEVICE_TREE ".dtb\0" \ Many rockchip boards configs/chromebook_bob_defconfig:CONFIG_DEFAULT_FDT_FILE="rockchip/rk3399-gru-bob.dtb" configs/evb-px5_defconfig:CONFIG_DEFAULT_FDT_FILE="rockchip/rk3368-px5-evb.dtb" configs/evb-rk3328_defconfig:CONFIG_DEFAULT_FDT_FILE="rockchip/rk3328-evb.dtb" configs/evb-rk3399_defconfig:CONFIG_DEFAULT_FDT_FILE="rockchip/rk3399-evb.dtb" configs/firefly-rk3399_defconfig:CONFIG_DEFAULT_FDT_FILE="rockchip/rk3399-firefly.dtb" configs/geekbox_defconfig:CONFIG_DEFAULT_FDT_FILE="rockchip/rk3368-geekbox.dtb" configs/lion-rk3368_defconfig:CONFIG_DEFAULT_FDT_FILE="rockchip/rk3368-lion-haikou.dtb" configs/puma-rk3399_defconfig:CONFIG_DEFAULT_FDT_FILE="rockchip/rk3399-puma-haikou.dtb" configs/rock960-rk3399_defconfig:CONFIG_DEFAULT_FDT_FILE="rockchip/rk3399-rock960.dtb" configs/sheep-rk3368_defconfig:CONFIG_DEFAULT_FDT_FILE="rockchip/rk3368-sheep.dtb" I didn't look any further - but it seems to me we need a way to have those sub-directories. Yours sincerely Josua Mayer
Bug#918589: linux-image-4.19.0-1-amd64: please enable support for audio in Lenovo Yoga 11e Chromebook (3th generation)
Package: src:linux Version: 4.19.12-1 Severity: wishlist Dear Maintainer, Audio does not currently work on above mentioned laptop. The device features a Celeron N3150 and appears to use its intgerated audio capabilities. A little googling suggests that the audio codec is an es8316. I will try to enable support for it in the kernel config and report back if I can get it to work. Yours sincerely Josua Mayer -- Package-specific info: ** Version: Linux version 4.19.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 8.2.0 (Debian 8.2.0-13)) #1 SMP Debian 4.19.12-1 (2018-12-22) ** Command line: BOOT_IMAGE=/vmlinuz-4.19.0-1-amd64 root=/dev/mmcblk0p3 ro quiet ** Tainted: W (512) * Taint on warning. ** Kernel log: [ 97.980302] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 97.981828] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 97.983457] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 97.984813] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 97.986170] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 97.987501] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 97.989000] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 97.990282] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 97.991571] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 97.992839] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 97.994135] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 97.995482] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 97.996798] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 97.998065] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 97.999604] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.000826] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.002081] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.003398] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.004643] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.006184] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.007846] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.009493] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.010953] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.012306] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.013663] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.015286] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.016743] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.017971] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.019268] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.020595] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.021812] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.023104] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.024365] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.025951] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.027168] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.028436] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.030084] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.031830] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.033416] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.034657] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.036004] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.037715] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.039271] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.040893] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.042504] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.043768] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.044989] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.046278] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.047994] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.049937] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.051464] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.053224] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.054554] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.056055] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.057614] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.059051] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.060446] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.061740] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.063135] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.064442] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.065701] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.067016] elan_i2c i2c-ELAN:00: invalid report
Bug#918156: some omitted details
I forgot to mention some important bits: 1. this is for armmp flavour only 2. the options I chose enable some more by default that I did not list 3. maybe all HCIUART drivers should be enabled, just like on x86?
Bug#918156: linux-image-4.18.0-0.bpo.3-armmp: please enable support for Ti WL1838 Bluetooth
Package: src:linux Version: 4.18.20-2~bpo9+1 Severity: wishlist Tags: patch Dear Maintainer, Please enable support for above mentioned bluetooth chip. It is used in SolidRun Ltd. i.MX6 MicroSOMs since revision 1.5, thereby applying to all Hummingboards and Cuboxes with a recent SoM. I enabled the necessary options and tested with a local build of 4.20 from the debian kernel source tree, and am attaching the diff. Yours sincerely Josua Mayer -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information Hardware: Freescale i.MX6 Quad/DualLite (Device Tree) Revision: Device Tree model: SolidRun HummingBoard2 Dual/Quad (1.5som+emmc) ** PCI devices: 00:00.0 PCI bridge [0604]: Synopsys, Inc. Device [16c3:abcd] (rev 01) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport Kernel modules: dwc3_haps ** USB devices: Bus 002 Device 002: ID 04b4:6570 Cypress Semiconductor Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub -- System Information: Debian Release: 9.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: armhf (armv7l) Kernel: Linux 4.20.0-trunk-armmp (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-image-4.18.0-0.bpo.3-armmp depends on: ii initramfs-tools [linux-initramfs-tool] 0.130 ii kmod23-2 ii linux-base 4.5 Versions of packages linux-image-4.18.0-0.bpo.3-armmp recommends: ii apparmor 2.11.0-3+deb9u2 ii firmware-linux-free 3.4 ii irqbalance 1.1.0-2.3 Versions of packages linux-image-4.18.0-0.bpo.3-armmp suggests: pn debian-kernel-handbook pn linux-doc-4.18 Versions of packages linux-image-4.18.0-0.bpo.3-armmp is related to: pn firmware-amd-graphics pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x pn firmware-brcm80211 pn firmware-cavium pn firmware-intel-sound pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv pn firmware-iwlwifi pn firmware-libertas pn firmware-linux-nonfree ii firmware-misc-nonfree 20180825+dfsg-1~bpo9+1 pn firmware-myricom pn firmware-netxen pn firmware-qlogic pn firmware-realtek pn firmware-samsung pn firmware-siano ii firmware-ti-connectivity 20161130-4 pn xen-hypervisor -- no debconf information >From 38737c0c24a8d7c23b46cd0a28e8dcf932ce06e1 Mon Sep 17 00:00:00 2001 From: Josua Mayer Date: Thu, 3 Jan 2019 20:59:05 +0100 Subject: [PATCH] armmp: enable BT_HCIUART_LL This allows using the wl1837-st bluetooth chip on the SolidRun i.MX6 SoMs Revision 1.5. Signed-off-by: Josua Mayer --- debian/config/armhf/config | 4 1 file changed, 4 insertions(+) diff --git a/debian/config/armhf/config b/debian/config/armhf/config index 48d26fea8269..e390fe168b42 100644 --- a/debian/config/armhf/config +++ b/debian/config/armhf/config @@ -179,6 +179,10 @@ CONFIG_DMA_CMA=y ## ## file: drivers/bluetooth/Kconfig ## +CONFIG_BT_HCIUART=m +CONFIG_BT_HCIUART_3WIRE=y +CONFIG_BT_HCIUART_LL=y +CONFIG_BT_HCIUART_SERDEV=y CONFIG_BT_WILINK=m ## -- 2.20.1
Bug#914634: Sorry for the noise
Hi there again, I might have noticed what is going wrong on my side :( I did some evil dependency mangling about libegl1. So please close this report! best regards Josua Mayer
Bug#914634: logs
Please find attached the log of installing the build environment, and the log file from the failed fmtutil run. fmtutil: fmtutil is using the following fmtutil.cnf files (in precedence order): fmtutil: /usr/share/texmf/web2c/fmtutil.cnf fmtutil: /usr/share/texlive/texmf-dist/web2c/fmtutil.cnf fmtutil: fmtutil is using the following fmtutil.cnf file for writing changes: fmtutil: /etc/texmf/web2c/fmtutil.cnf fmtutil [INFO]: writing formats under /var/lib/texmf/web2c fmtutil [INFO]: --- remaking luatex with luatex fmtutil: running `luatex -ini -jobname=luatex -progname=luatex luatex.ini' ... luatex: error while loading shared libraries: libEGL.so.1: cannot open shared object file: No such file or directory fmtutil [INFO]: --- remaking pdftex with pdftex fmtutil: running `pdftex -ini -jobname=pdftex -progname=pdftex -translate-file=cp227.tcx *pdfetex.ini' ... This is pdfTeX, Version 3.14159265-2.6-1.40.17 (TeX Live 2016/Debian) (INITEX) restricted \write18 enabled. (/usr/share/texlive/texmf-dist/web2c/cp227.tcx) entering extended mode (/usr/share/texlive/texmf-dist/tex/plain/config/pdfetex.ini (/var/lib/texmf/tex/generic/config/pdftexconfig.tex) (/usr/share/texlive/texmf-dist/tex/plain/etex/etex.src (/usr/share/texlive/texmf-dist/tex/plain/base/plain.tex Preloading the plain format: codes, registers, parameters, fonts, more fonts, macros, math definitions, output routines, hyphenation (/usr/share/texlive/texmf-dist/tex/generic/hyphen/hyphen.tex [skipping from \patterns to end-of-file...])) (/usr/share/texlive/texmf-dist/tex/plain/etex/etexdefs.lib Skipping module "grouptypes"; Loading module "interactionmodes"; Skipping module "nodetypes"; Skipping module "iftypes";) (/usr/share/texlive/texmf-dist/tex/generic/config/language.def (/usr/share/texlive/texmf-dist/tex/generic/hyphen/hyphen.tex)) Augmenting the Plain TeX definitions: \tracingall; Adding new e-TeX definitions: \eTeX, \loggingall, \tracingnone, register allocation; extended register allocation; Recycling: \addlanguage, \@nswer (not defined), \@sk, \b@dresponsetrue, \b@dresponsefalse, \ch@ckforyn, \mayber@cycle, \et@xabort, \et@xbuf, \et@xfmtsrc, \et@xfilehdr, \et@xinf, \et@xpatterns, \l@ngdefnfile, \n@xt, \p@rse (not defined), \pr@mpt (not defined), \pr@mptloop (not defined), \forcer@cycle, \usef@llback, \usef@llbacktrue, \usef@llbackfalse, Retaining: \et@xerr, \et@xinput, \et@xlibhdr, \et@xmsg, \et@xtoks, \et@xwarn, \et@xl@@d, \et@xl@ad, \et@xload, \et@xlang, \et@xhash, \eTeX, \etexhdrchk, \etexstatus, \module, \uselanguage, \r@tain, \r@cycle,) (/usr/share/texlive/texmf-dist/tex/plain/config/pdftexmagfix.tex) ) Beginning to dump on file pdftex.fmt (preloaded format=pdftex 2018.11.25) 2895 strings of total length 43145 7960 memory locations dumped; current usage is 203&7321 1263 multiletter control sequences \font\nullfont=nullfont \font\tenrm=cmr10 \font\preloaded=cmr9 \font\preloaded=cmr8 \font\sevenrm=cmr7 \font\preloaded=cmr6 \font\fiverm=cmr5 \font\teni=cmmi10 \font\preloaded=cmmi9 \font\preloaded=cmmi8 \font\seveni=cmmi7 \font\preloaded=cmmi6 \font\fivei=cmmi5 \font\tensy=cmsy10 \font\preloaded=cmsy9 \font\preloaded=cmsy8 \font\sevensy=cmsy7 \font\preloaded=cmsy6 \font\fivesy=cmsy5 \font\tenex=cmex10 \font\preloaded=cmss10 \font\preloaded=cmssq8 \font\preloaded=cmssi10 \font\preloaded=cmssqi8 \font\tenbf=cmbx10 \font\preloaded=cmbx9 \font\preloaded=cmbx8 \font\sevenbf=cmbx7 \font\preloaded=cmbx6 \font\fivebf=cmbx5 \font\tentt=cmtt10 \font\preloaded=cmtt9 \font\preloaded=cmtt8 \font\preloaded=cmsltt10 \font\tensl=cmsl10 \font\preloaded=cmsl9 \font\preloaded=cmsl8 \font\tenit=cmti10 \font\preloaded=cmti9 \font\preloaded=cmti8 \font\preloaded=cmti7 \font\preloaded=cmu10 \font\preloaded=cmmib10 \font\preloaded=cmbsy10 \font\preloaded=cmcsc10 \font\preloaded=cmssbx10 \font\preloaded=cmdunh10 \font\preloaded=cmr7 at 14.51799pt \font\preloaded=cmtt10 at 14.4pt \font\preloaded=cmssbx10 at 14.4pt \font\preloaded=manfnt 14787 words of font info for 50 preloaded fonts 14 hyphenation exceptions Hyphenation trie of length 6075 has 181 ops out of 35111 181 for language 0 0 words of pdfTeX memory 0 indirect objects No pages of output. Transcript written on pdftex.log. fmtutil [INFO]: /var/lib/texmf/web2c/pdftex/pdftex.fmt installed. fmtutil [INFO]: --- remaking tex with tex fmtutil: running `tex -ini -jobname=tex -progname=tex tex.ini' ... This is TeX, Version 3.14159265 (TeX Live 2016/Debian) (INITEX) (/usr/share/texlive/texmf-dist/tex/plain/config/tex.ini (/usr/share/texlive/texmf-dist/tex/plain/base/plain.tex Preloading the plain format: codes, registers, parameters, fonts, more fonts, macros, math definitions, output routines, hyphenation (/usr/share/texlive/texmf-dist/tex/generic/hyphen/hyphen.tex)) ) Beginning to dump on file tex.fmt (preloaded format=tex 2018.11.25) 2027 strings of total length 29297 4990 memory locations dumped; current usage is 110&4877 926 multiletter control sequences \font\nullfont=nullfont \font\tenrm=cmr10
Bug#914634: texlive-binaries: luatex requires libEGL
Package: texlive-binaries Version: 2016.20160513.41080.dfsg-2+deb9u1 Severity: normal Dear Maintainer, While doing automated builds using the openbuildservice to rebuild quilt from stretch-backports, I have encountered a failing maintainer script of tex-common. Investigating the produced log-file shows that the luatex application attempts to load libEGL.so.1, and fails: luatex: error while loading shared libraries: libEGL.so.1: cannot open shared object file: No such file or directory Sure enough in the produced build-root nothing has pulled in libegl1. I suspect that the texlive-binaries package should have a dependency on libegl1. I will attach the full logs to a reply. Yours sincerely Josua Mayer -- System Information: Debian Release: 9.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: armhf (armv7l) Kernel: Linux 4.9.124-imx6-sr (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages texlive-binaries depends on: ii dpkg 1.18.25 ii libc6 2.24-11+deb9u3 ii libcairo2 1.14.8-1sr1 ii libfontconfig12.11.0-6.7+b1 ii libfreetype6 2.6.3-3.2 ii libgcc1 1:6.3.0-18+deb9u1 ii libgmp10 2:6.1.2+dfsg-1 ii libgraphite2-31.3.10-1 ii libgs99.25~dfsg-0+deb9u1 ii libharfbuzz-icu0 1.4.2-1 ii libharfbuzz0b 1.4.2-1 ii libice6 2:1.0.9-2 ii libicu57 57.1-6+deb9u2 ii libkpathsea6 2016.20160513.41080.dfsg-2+deb9u1 ii libmpfr4 3.1.5-1 ii libpaper1 1.1.24+nmu5 ii libpixman-1-0 0.34.0-1 ii libpng16-16 1.6.28-1 ii libpoppler64 0.48.0-2+deb9u2 ii libpotrace0 1.13-3 ii libptexenc1 2016.20160513.41080.dfsg-2+deb9u1 ii libsm62:1.2.2-1+b3 ii libstdc++66.3.0-18+deb9u1 ii libsynctex1 2016.20160513.41080.dfsg-2+deb9u1 ii libtexlua52 2016.20160513.41080.dfsg-2+deb9u1 ii libtexluajit2 2016.20160513.41080.dfsg-2+deb9u1 ii libx11-6 2:1.6.4-3+deb9u1 ii libxaw7 2:1.0.13-1+b2 ii libxext6 2:1.3.3-1+b2 ii libxi62:1.7.9-1 ii libxmu6 2:1.1.2-2 ii libxpm4 1:3.5.12-1 ii libxt61:1.1.5-1 ii libzzip-0-13 0.13.62-3.1 ii perl 5.24.1-3+deb9u4 ii t1utils 1.39-2 ii tex-common6.06 ii zlib1g1:1.2.8.dfsg-5 Versions of packages texlive-binaries recommends: ii python2.7.13-2 ii ruby 1:2.3.3 ii texlive-base 2016.20170123-5 ii tk [wish] 8.6.0+9 texlive-binaries suggests no packages. -- no debconf information
Bug#914016: flash-kernel: please add support for Helios 4 NAS
Package: flash-kernel Version: 3.95 Severity: wishlist Dear Maintainer, Support for the Helios-4 NAS finally landed in linux 4.19 by acceptance of the DTB. There is 2018.11 based u-boot available, and it can use the generic boot-script: https://github.com/helios-4/u-boot/commits/helios4 Tested with linux-image-armmp 4.19.2 built from pkg-linux. Please find below the required snippet for the flash-kernel database. kind regards Josua Mayer -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: armhf (armv7l) Kernel: Linux 4.19.0-trunk-armmp (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages flash-kernel depends on: ii debconf [debconf-2.0] 1.5.69 ii devio 1.2-1.2+b1 ii initramfs-tools0.132 ii linux-base 4.5 ii mtd-utils 1:2.0.1-1 ii ucf3.0038 Versions of packages flash-kernel recommends: ii u-boot-tools 2018.05+dfsg-1 flash-kernel suggests no packages. -- Configuration Files: /etc/flash-kernel/db changed: Machine: Helios4 DTB-Id: armada-388-helios4.dtb Boot-Script-Path: /boot/boot.scr U-Boot-Script-Name: bootscr.uboot-generic Required-Packages: u-boot-tools -- debconf information excluded
Bug#908967: boot logs
Please find the boot logs attached U-Boot 2018.01-02296-g457cdd60c3 (May 17 2018 - 22:59:22 +0200), Build: jenkins-u-boot-imx6-variant=sdhc-2 CPU: Freescale i.MX6D rev1.5 996 MHz (running at 792 MHz) CPU: Extended Commercial temperature grade (-20C to 105C) at 48C Reset cause: WDOG Board: MX6 HummingBoard Watchdog enabled DRAM: 1 GiB MMC: FSL_SDHC: 0, FSL_SDHC: 1 auto-detected panel HDMI Display: HDMI (1024x768) In:serial Out: serial Err: serial Net: FEC starting USB... USB0: USB EHCI 1.00 scanning bus 0 for devices... 1 USB Device(s) found USB1: USB EHCI 1.00 scanning bus 1 for devices... 2 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found /boot/extlinux/extlinux.conf Retrieving file: /boot/extlinux/extlinux.conf 297 bytes read in 121 ms (2 KiB/s) i.MX6 1: default 2: hack Enter choice: 1 1: default Retrieving file: /boot/extlinux/../initrd 8817476 bytes read in 690 ms (12.2 MiB/s) Retrieving file: /boot/extlinux/../zImage 7137904 bytes read in 535 ms (12.7 MiB/s) append: root=UUID=febfadf2-ffa2-48ad-9802-d7b67b5e7818 rootfstype=auto rootwait Retrieving file: /boot/extlinux/../dtb-dir/imx6q-hummingboard.dtb 45535 bytes read in 854 ms (51.8 KiB/s) ## Flattened Device Tree blob at 1800 Booting using the fdt blob at 0x1800 Using Device Tree in place at 1800, end 1800e1de Starting kernel ... [0.00] Booting Linux on physical CPU 0x0 [0.00] Linux version 4.9.124-imx6-sr (abuild@ddd2fcb3ed55) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP Sat Sep 15 05:01:08 UTC 2018 [0.00] CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c53c7d [0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [0.00] OF: fdt:Machine model: SolidRun HummingBoard Dual/Quad [0.00] Reserved memory: created CMA memory pool at 0x2c00, size 320 MiB [0.00] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool [0.00] Memory policy: Data cache writealloc [0.00] percpu: Embedded 14 pages/cpu @db6ba000 s26764 r8192 d22388 u57344 [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 260416 [0.00] Kernel command line: root=UUID=febfadf2-ffa2-48ad-9802-d7b67b5e7818 rootfstype=auto rootwait [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: 686640K/1048576K available (9216K kernel code, 418K rwdata, 3088K rodata, 1024K init, 549K bss, 34256K reserved, 327680K cma-reserved, 262144K highmem) [0.00] Virtual kernel memory layout: [0.00] vector : 0x - 0x1000 ( 4 kB) [0.00] fixmap : 0xffc0 - 0xfff0 (3072 kB) [0.00] vmalloc : 0xf080 - 0xff80 ( 240 MB) [0.00] lowmem : 0xc000 - 0xf000 ( 768 MB) [0.00] pkmap : 0xbfe0 - 0xc000 ( 2 MB) [0.00] modules : 0xbf00 - 0xbfe0 ( 14 MB) [0.00] .text : 0xc0008000 - 0xc0a0 (10208 kB) [0.00] .init : 0xc0e0 - 0xc0f0 (1024 kB) [0.00] .data : 0xc0f0 - 0xc0f68880 ( 419 kB) [0.00].bss : 0xc0f68880 - 0xc0ff1dd8 ( 550 kB) [0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1 [0.00] Hierarchical RCU implementation. [0.00] Build-time adjustment of leaf fanout to 32. [0.00] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2. [0.00] RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2 [0.00] NR_IRQS:16 nr_irqs:16 16 [0.00] L2C-310 errata 752271 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 16 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.08] sched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every 715827882841ns [0.24] clocksource: mxc_timer1: mask: 0x max_cycles: 0x, max_idle_ns: 637086815595 ns [0.001250] Console: colour dummy device 80x30 [0.001747] console [tty0] enabled [0.001778] Calibrating delay loop (skipped), value calculated using timer frequency.. 6.00 BogoMIPS (lpj=3000) [0.001813] pid_max: default: 32768 minimum: 301 [0.001922] Security Framework initialized [0.001949] SELinux: Initializing. [0.
Bug#908967: initramfs-tools: mount fails with rootfstype=auto
Package: initramfs-tools Version: 0.130 Severity: normal Dear Maintainer, I encountered a strange problem mounting the rootfs with a freshly debootstrapped system. Note: possible duplicate of #845302 but due to the details I found it probably warrants its own topic. Steps: - used debootstrap with --variant=minbase to create an armhf rootfs - added custom packages such as vendor kernel, systemd, initramfs-tools - created extlinux.conf to boot - bootargs: root=UUID=... rootfstype=auto rootwait Observations: - root=/dev/mmcblk0p1 rootfstype=auto: fails - root=/dev/mmcblk0p1 rootfstype=ext4: works - root=UUID=... rootfstype=ext4: works How did I find this? I added "set -x" to - /usr/share/initramfs-tools/init - /usr/share/initramfs-tools/scripts/init-bottom/udev The serial console then finally revealed what is going wrong. When it fails (rootfstype=auto): + [ auto != unknown ] + mount -r -t auto /dev/mmcblk0p1 /root mount: No such device When it works (rootfstype=ext4): + [ ext4 != unknown ] + mount -r -t ext4 /dev/mmcblk0p1 /root [9.979060] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: (null) So I see two solutions: - If rootfstype=auto, and the actual type is known through a previous call to blkid, e.g. while running fsck, use the known type - fix the mount command to deal with type auto I am submitting the full boot logs by email as follow-up. Yours sincerely Josua Mayer -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 8.5M Sep 16 20:04 /boot/initrd.img-4.9.124-imx6-sr -- /proc/cmdline root=UUID=febfadf2-ffa2-48ad-9802-d7b67b5e7818 rootfstype=ext4 rootwait -- /proc/filesystems ext3 ext2 ext4 vfat fuseblk f2fs -- lsmod Module Size Used by bnep 20480 2 mxc_v4l2_capture 40960 0 ipu_bg_overlay_sdc 16384 1 mxc_v4l2_capture ipu_still 16384 1 mxc_v4l2_capture ipu_prp_enc16384 1 mxc_v4l2_capture ipu_csi_enc16384 1 mxc_v4l2_capture ipu_fg_overlay_sdc 20480 1 mxc_v4l2_capture hci_uart 49152 0 btbcm 16384 1 hci_uart nvmem_core 24576 1 hci_uart ov5647_camera_mipi 36864 0 v4l2_int_device16384 3 ov5647_camera_mipi,ipu_csi_enc,mxc_v4l2_capture xt_connmark16384 2 iptable_nat16384 0 nf_conntrack_ipv4 16384 3 nf_defrag_ipv4 16384 1 nf_conntrack_ipv4 nf_nat_ipv416384 1 iptable_nat nf_nat 24576 1 nf_nat_ipv4 nf_conntrack 106496 4 nf_conntrack_ipv4,xt_connmark,nf_nat_ipv4,nf_nat iptable_mangle 16384 1 iptable_filter 16384 0 ir_lirc_codec 16384 0 galcore 372736 0 ir_rc6_decoder 16384 0 lirc_dev 20480 1 ir_lirc_codec rc_rc6_mce 16384 0 gpio_ir_recv 16384 0 bluetooth 360448 12 hci_uart,bnep,btbcm rfkill 24576 4 bluetooth ip_tables 24576 3 iptable_mangle,iptable_filter,iptable_nat x_tables 28672 4 iptable_mangle,ip_tables,iptable_filter,xt_connmark imx_sdma 28672 8 virt_dma 16384 1 imx_sdma -- /etc/initramfs-tools/modules -- /etc/initramfs-tools/initramfs.conf MODULES=most BUSYBOX=auto KEYMAP=n COMPRESS=gzip DEVICE= NFSROOT=auto -- /etc/initramfs-tools/update-initramfs.conf update_initramfs=yes backup_initramfs=no -- /proc/mdstat Personalities : unused devices: -- mkinitramfs hooks /etc/initramfs-tools/hooks/: imx-sdma /usr/share/initramfs-tools/hooks: dmsetup fsck fuse keymap klibc-utils kmod ntfs_3g resume thermal udev -- System Information: Debian Release: 9.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: armhf (armv7l) Kernel: Linux 4.9.124-imx6-sr (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages initramfs-tools depends on: ii initramfs-tools-core 0.130 ii linux-base4.5 initramfs-tools recommends no packages. Versions of packages initramfs-tools suggests: pn bash-completion -- no debconf information
Bug#906696: flash-kernel: Please add an entry for the Rock64
Hi, Am 24.08.2018 um 14:55 schrieb Héctor Orón Martínez: > Hello, > > Missatge de Josua Mayer del dia dg., 19 > d’ag. 2018 a les 22:00: >> There is a vendor u-boot available based on 2017.09. It fully supports >> distro boot and >> loading EFI applications. > Do you happen to know what's missing in the Debian u-boot package to > be usable in that board? Everything. Because there is no support for the rock64 in upstream u-boot. And then it is a little evil in that the last time I checked blobs were required to construct a signed image with ATF. > >> Therefore the rock64 can be booted with grub-arm-efi. > Great! > >> Only one important thing has to be dealt with: Getting the DTB loaded by >> U-Boot! >> U-Boot searches for rockchip/rk3328-rock64.dtb in /, /dtb/, /dtb/current on >> the EFI partition. >> >> The attached db entry takes care ot this particular path by storing it at >> /boot/efi/dtb/rockchip/rk3328-rock64.dtb. > This is with vendor u-boot instead Debian u-boot, right? Right. More precsisely: U-Boot (upstream) has efi_dtb_prefixes=/ /dtb/ /dtb/current/. It searches for $fdtfile in those places before loading and efi application. This is shared by the vendor u-boot. The only trouble is that fdtfile is set to "rockchip/rk3328-rock64.dtb" rather than plain "rk3328-rock64.dtb" like other rockchip boards supported in upstream do. ^^ I think this is the pain point. > >> Other rockchip boards supported by mainline u-boot omit the rockchip >> subdirectory and just search for the dtb name. >> However there is no support for the rock64 in mainline u-boot so I think >> carrying this weird prefix is acceptable. > Not sure I agree on that. Is someone working on mainline u-boot to > support rock64? I have been watching the u-boot mailinglist and there was nothing. There only seems to be this single person Kamil Trzciński doing serious work in this direction. E.g. see his mainline branch on github: https://github.com/ayufan-rock64/linux-u-boot/commits/mainline-master It looks like he might want to push these up stream at one point. It was his decision to go with the rockchip subfolder: https://github.com/ayufan-rock64/linux-u-boot/commit/9c204e7343577e8b922556bf9349a457c139976e I guess we could ask him to accept a patch allowing the dtb to reside at the root level? That way it would behave like upstream rockchip boards. > >> Currently most used and best documented source for rock64 U-Boot: >> https://github.com/ayufan-rock64/linux-u-boot/releases >> >> u-boot-erase-spi-rock64.img.xz can be used to flash u-boot to SPI flash once; >> from then on everything is standard: >> - debootstrap >> - linux-image-arm64 >> - grub-arm-efi >> - grub-install --target=arm-efi --removable >> >> Yours sincerely >> Josua Mayer >> >> -- System Information: >> Debian Release: buster/sid >> APT prefers testing >> APT policy: (500, 'testing') >> Architecture: arm64 (aarch64) >> >> Kernel: Linux 4.17.0-1-arm64 (SMP w/4 CPU cores) >> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), >> LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) >> Shell: /bin/sh linked to /bin/dash >> Init: systemd (via /run/systemd/system) >> LSM: AppArmor: enabled >> >> Versions of packages flash-kernel depends on: >> ii debconf [debconf-2.0] 1.5.69 >> ii devio 1.2-1.2+b1 >> ii initramfs-tools0.132 >> ii linux-base 4.5 >> ii mtd-utils 1:2.0.1-1 >> ii ucf3.0038 >> >> Versions of packages flash-kernel recommends: >> ii u-boot-tools 2018.05+dfsg-1 >> >> flash-kernel suggests no packages. >> >> -- Configuration Files: >> /etc/flash-kernel/db changed: >> Machine: Pine64 Rock64 >> Boot-DTB-Path: /boot/efi/rockchip/rk3328-rock64.dtb >> DTB-Id: rockchip/rk3328-rock64.dtb >> >> >> -- debconf information excluded > >
Bug#906696: second thoughts
While the db entry I provided works just fine, maybe because this is u-boot, using a generic boot.scr would be preferred. Any opinions?
Bug#906696: flash-kernel: Please add an entry for the Rock64
Package: flash-kernel Version: 3.94 Severity: wishlist Tags: patch Dear Maintainer, The rock64 from pine64 works acceptable with linux-image-arm64. There is a vendor u-boot available based on 2017.09. It fully supports distro boot and loading EFI applications. Therefore the rock64 can be booted with grub-arm-efi. Only one important thing has to be dealt with: Getting the DTB loaded by U-Boot! U-Boot searches for rockchip/rk3328-rock64.dtb in /, /dtb/, /dtb/current on the EFI partition. The attached db entry takes care ot this particular path by storing it at /boot/efi/dtb/rockchip/rk3328-rock64.dtb. Other rockchip boards supported by mainline u-boot omit the rockchip subdirectory and just search for the dtb name. However there is no support for the rock64 in mainline u-boot so I think carrying this weird prefix is acceptable. Currently most used and best documented source for rock64 U-Boot: https://github.com/ayufan-rock64/linux-u-boot/releases u-boot-erase-spi-rock64.img.xz can be used to flash u-boot to SPI flash once; from then on everything is standard: - debootstrap - linux-image-arm64 - grub-arm-efi - grub-install --target=arm-efi --removable Yours sincerely Josua Mayer -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: arm64 (aarch64) Kernel: Linux 4.17.0-1-arm64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages flash-kernel depends on: ii debconf [debconf-2.0] 1.5.69 ii devio 1.2-1.2+b1 ii initramfs-tools0.132 ii linux-base 4.5 ii mtd-utils 1:2.0.1-1 ii ucf3.0038 Versions of packages flash-kernel recommends: ii u-boot-tools 2018.05+dfsg-1 flash-kernel suggests no packages. -- Configuration Files: /etc/flash-kernel/db changed: Machine: Pine64 Rock64 Boot-DTB-Path: /boot/efi/rockchip/rk3328-rock64.dtb DTB-Id: rockchip/rk3328-rock64.dtb -- debconf information excluded >From 94fb0ab7075b3f2424b8aef673d430896191f3ac Mon Sep 17 00:00:00 2001 From: Josua Mayer Date: Sun, 19 Aug 2018 21:55:17 +0200 Subject: [PATCH] Add Rock64 Signed-off-by: Josua Mayer --- db/all.db | 4 1 file changed, 4 insertions(+) diff --git a/db/all.db b/db/all.db index 7031d21..8d946c6 100644 --- a/db/all.db +++ b/db/all.db @@ -1402,6 +1402,10 @@ Boot-Script-Path: /boot/boot.scr U-Boot-Script-Name: bootscr.uboot-generic Required-Packages: u-boot-tools +Machine: Pine64 Rock64 +Boot-DTB-Path: /boot/efi/rockchip/rk3328-rock64.dtb +DTB-Id: rockchip/rk3328-rock64.dtb + Machine: PlatHome OpenBlocks AX3-4 board Kernel-Flavors: armmp armmp-lpae DTB-Id: armada-xp-openblocks-ax3-4.dtb -- 2.18.0
Bug#906268: rules
Please find the current rules file and script attached.
#
# This udev rule connects the USB ID pin with the charging current setting
# of the twl4030 through a helper script.
#
# This allows to use default charging current 500 mA and switch to higher
# values if a more capable power supply indicates through the ID pin.
#
# Implementation is a little tricky since an udev rule can'd dynamically
# identify two different nodes. And ATTR{} can not reference arbitrary
# files relative to root (ATTR is relative to /sys/%p even if it starts
# with a /). And we can't create symlinks within /sysfs.
#
# Therefore connecting two device nodes in /sys is beyond udev rules
# and we need a helper script.
#
# 1. provide stable name to access the id pin of the USB connector and the
max_current setting for the usb charger
# /dev/usb_id ->
/sys/devices/platform/6800.ocp/4807.i2c/i2c-0/0-0048/4807.i2c:twl@48:twl4030-usb/id
# /dev/usb_max_current ->
/sys/devices/platform/6800.ocp/4807.i2c/i2c-0/0-0048/4807.i2c:twl@48:bci/power_supply/twl4030_usb/input_current_limit
# to find patters use e.g. udevadm info -a -p
/sys/devices/platform/6800.ocp/4807.i2c/i2c-0/0-0048/4807.i2c:twl@48:bci/power_supply/twl4030_usb
ACTION=="add", SUBSYSTEM=="platform", KERNEL=="*twl4030-usb",
DRIVER=="twl4030_usb", RUN+="/bin/ln -s /sys%p/id /dev/usb_id"
ACTION=="add", SUBSYSTEM=="power_supply", KERNEL=="twl4030_usb",
ATTR{type}=="USB", RUN+="/bin/ln -s /sys%p/input_current_limit
/dev/usb_max_current"
# 2. default to 500 mA right after boot (independently what the ID pin says)
ACTION=="add", SUBSYSTEM=="power_supply", KERNEL=="twl4030_usb",
ATTR{type}=="USB", ATTR{input_current_limit}="50"
# 3. this is preparation for the Pyra but neither tested nor complete nor
working
ACTION=="add", SUBSYSTEM=="power_supply", KERNEL=="bq24297", ATTR{type}=="USB",
RUN+="/bin/ln -s /sys%p/id /dev/usb_id"
ACTION=="add", SUBSYSTEM=="power_supply", KERNEL=="bq24297", ATTR{type}=="USB",
RUN+="/bin/ln -s /sys%p/input_current_limit /dev/usb_max_current"
# 4. charger has been plugged in (or removed): run external script
# this script reads the id pin value and make a decision for the current
setting of /dev/usb_max_current
ACTION=="change", SUBSYSTEM=="power_supply", KERNEL=="twl4030_usb",
ATTR{type}=="USB", RUN+="/etc/udev/rules.d/charging.sh"
charging.sh
Description: application/shellscript
Bug#906268: udev: enable fast charging from udev rule
Package: udev Version: 232-25+deb9u4 Severity: wishlist Dear Maintainer, Please note that I am not sure if udev (systemd) is the place to solve my issue. I have a gta04 phone that supports fast charging. But it has to ne explicitly enabled from user space :( This is because handling that in kernel has been rejected in the past. So I have: - The ID pin of the charging (usb) port exposed to userspace: /sys/devices/platform/6800.ocp/4807.i2c/i2c-0/0-0048/4807.i2c:twl@48:twl4030-usb/id - known values indicating a compatible charger: 102k GND - Existing udev rules that were used for a few years now Now fast-charging is very important on this device because it has just a small battery, and because it will discharge and eventually die under load on the default maximum current of 500mA. Therefore it should eventually end up in debian-installer as well (though I guess it can be done from a preseed file). Can this go into the debian udev package? Is there a better place for such rules? Yours sincerely Josua Mayer -- Package-specific info: -- System Information: Debian Release: 9.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: armhf (armv7l) Kernel: Linux 4.17.0-0.bpo.1-armmp (SMP w/1 CPU core) 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) Versions of packages udev depends on: ii adduser 3.115 ii dpkg 1.18.25 ii libacl1 2.2.52-3+b1 ii libblkid12.29.2-1+deb9u1 ii libc62.24-11+deb9u3 ii libgcc1 1:6.3.0-18+deb9u1 ii libkmod2 23-2 ii libselinux1 2.6-3+b3 ii libudev1 232-25+deb9u4 ii lsb-base 9.20161125 ii procps 2:3.3.12-3+deb9u1 ii util-linux 2.29.2-1+deb9u1 udev recommends no packages. udev suggests no packages. Versions of packages udev is related to: ii systemd 232-25+deb9u4 -- no debconf information P: /devices/breakpoint E: DEVPATH=/devices/breakpoint E: SUBSYSTEM=event_source P: /devices/kprobe E: DEVPATH=/devices/kprobe E: SUBSYSTEM=event_source P: /devices/platform/Fixed MDIO bus.0 E: DEVPATH=/devices/platform/Fixed MDIO bus.0 E: MODALIAS=platform:Fixed MDIO bus E: SUBSYSTEM=platform P: /devices/platform/Fixed MDIO bus.0/mdio_bus/fixed-0 E: DEVPATH=/devices/platform/Fixed MDIO bus.0/mdio_bus/fixed-0 E: SUBSYSTEM=mdio_bus P: /devices/platform/alarmtimer E: DEVPATH=/devices/platform/alarmtimer E: DRIVER=alarmtimer E: MODALIAS=platform:alarmtimer E: SUBSYSTEM=platform P: /devices/platform/etnaviv E: DEVPATH=/devices/platform/etnaviv E: DRIVER=etnaviv E: MODALIAS=platform:etnaviv E: SUBSYSTEM=platform P: /devices/platform/etnaviv/drm/card0 N: dri/card0 E: DEVNAME=/dev/dri/card0 E: DEVPATH=/devices/platform/etnaviv/drm/card0 E: DEVTYPE=drm_minor E: ID_FOR_SEAT=drm-platform-etnaviv E: ID_PATH=platform-etnaviv E: ID_PATH_TAG=platform-etnaviv E: MAJOR=226 E: MINOR=0 E: SUBSYSTEM=drm E: TAGS=:uaccess:seat:master-of-seat: E: USEC_INITIALIZED=14090470 P: /devices/platform/etnaviv/drm/renderD128 N: dri/renderD128 E: DEVNAME=/dev/dri/renderD128 E: DEVPATH=/devices/platform/etnaviv/drm/renderD128 E: DEVTYPE=drm_minor E: ID_FOR_SEAT=drm-platform-etnaviv E: ID_PATH=platform-etnaviv E: ID_PATH_TAG=platform-etnaviv E: MAJOR=226 E: MINOR=128 E: SUBSYSTEM=drm E: TAGS=:uaccess:seat: E: USEC_INITIALIZED=14086934 P: /devices/platform/gpu-subsystem E: DEVPATH=/devices/platform/gpu-subsystem E: MODALIAS=of:Ngpu-subsystemTCmarvell,dove-gpu-subsystem E: OF_COMPATIBLE_0=marvell,dove-gpu-subsystem E: OF_COMPATIBLE_N=1 E: OF_FULLNAME=/gpu-subsystem E: OF_NAME=gpu-subsystem E: SUBSYSTEM=platform P: /devices/platform/i2c-mux E: DEVPATH=/devices/platform/i2c-mux E: DRIVER=i2c-mux-pinctrl E: MODALIAS=of:Ni2c-muxTCi2c-mux-pinctrl E: OF_COMPATIBLE_0=i2c-mux-pinctrl E: OF_COMPATIBLE_N=1 E: OF_FULLNAME=/i2c-mux E: OF_NAME=i2c-mux E: SUBSYSTEM=platform P: /devices/platform/ir-receiver E: DEVPATH=/devices/platform/ir-receiver E: DRIVER=gpio_ir_recv E: MODALIAS=of:Nir-receiverTCgpio-ir-receiver E: OF_COMPATIBLE_0=gpio-ir-receiver E: OF_COMPATIBLE_N=1 E: OF_FULLNAME=/ir-receiver E: OF_NAME=ir-receiver E: SUBSYSTEM=platform P: /devices/platform/ir-receiver/rc/rc0 E: DEVPATH=/devices/platform/ir-receiver/rc/rc0 E: DEV_NAME=gpio_ir_recv E: DRV_NAME=gpio_ir_recv E: NAME=rc-empty E: SUBSYSTEM=rc P: /devices/platform/ir-receiver/rc/rc0/input0 E: DEVPATH=/devices/platform/ir-receiver/rc/rc0/input0 E: EV=100013 E: ID_FOR_SEAT=input-platform-ir-receiver E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_PATH=platform-ir-receiver E: ID_PATH_TAG=platform-ir-receiver E: KEY=100 0 0 0 0 E: MODALIAS=input:b0019v0001p0001e0100-e0,1,4,14,k98,ram4,lsfw E: MSC=10 E: NAME="gpio_ir_recv" E: PHYS="gpio_ir_recv/input0" E: PRODUCT=19/1/1/100 E: PROP=0 E: SUBSYSTEM=input E: TAGS=:seat: E: USEC_INITIALIZED=13899715 P: /devices/platform/ir-receive
Bug#906054: Tested
(SMF,km) : 0km Length (SMF) : 0m Length (50um) : 150m Length (62.5um) : 70m Length (Copper) : 0m Length (OM3) : 0m Laser wavelength : 850nm Vendor name : AVAGO Vendor OUI: 00:17:6a Vendor PN : AFBR-57R5AEZ Vendor rev: Option values : 0x00 0x1a Option: RX_LOS implemented Option: TX_FAULT implemented Option: TX_DISABLE implemented BR margin, max: 0% BR margin, min: 0% Vendor SN : A90751H94G Date code : 071221 Optical diagnostics support : Yes Laser bias current: 0.000 mA Laser output power: 0. mW / -inf dBm Receiver signal average optical power : 0. mW / -inf dBm Module temperature: 41.08 degrees C / 105.95 degrees F Module voltage: 3.3189 V Alarm/warning flags implemented : Yes Laser bias current high alarm : Off Laser bias current low alarm : On Laser bias current high warning : Off Laser bias current low warning: On Laser output power high alarm : Off Laser output power low alarm : On Laser output power high warning : Off Laser output power low warning: On Module temperature high alarm : Off Module temperature low alarm : Off Module temperature high warning : Off Module temperature low warning: Off Module voltage high alarm : Off Module voltage low alarm : Off Module voltage high warning : Off Module voltage low warning: Off Laser rx power high alarm : Off Laser rx power low alarm : On Laser rx power high warning : Off Laser rx power low warning: On Laser bias current high alarm threshold : 10.000 mA Laser bias current low alarm threshold: 2.000 mA Laser bias current high warning threshold : 10.000 mA Laser bias current low warning threshold : 2.000 mA Laser output power high alarm threshold : 0.7000 mW / -1.55 dBm Laser output power low alarm threshold: 0.0500 mW / -13.01 dBm Laser output power high warning threshold : 0.6000 mW / -2.22 dBm Laser output power low warning threshold : 0.1000 mW / -10.00 dBm Module temperature high alarm threshold : 100.00 degrees C / 212.00 degrees F Module temperature low alarm threshold: -40.00 degrees C / -40.00 degrees F Module temperature high warning threshold : 85.00 degrees C / 185.00 degrees F Module temperature low warning threshold : -10.00 degrees C / 14.00 degrees F Module voltage high alarm threshold : 3.9000 V Module voltage low alarm threshold: 2.7000 V Module voltage high warning threshold : 3.6300 V Module voltage low warning threshold : 2.9700 V Laser rx power high alarm threshold : 6.5500 mW / 8.16 dBm Laser rx power low alarm threshold: 0. mW / -inf dBm Laser rx power high warning threshold : 1.1000 mW / 0.41 dBm Laser rx power low warning threshold : 0.0490 mW / -13.10 dBm >From 2ac29b08004b43ed280c3935dd775d7488dc0bbe Mon Sep 17 00:00:00 2001 From: Josua Mayer Date: Mon, 13 Aug 2018 18:42:45 +0200 Subject: [PATCH] armmp: enable SFP support Signed-off-by: Josua Mayer --- debian/config/armhf/config | 2 ++ 1 file changed, 2 insertions(+) diff --git a/debian/config/armhf/config b/debian/config/armhf/config index 79ee427b5..a7121d185 100644 --- a/debian/config/armhf/config +++ b/debian/config/armhf/config @@ -839,6 +839,8 @@ CONFIG_SKFP=m ## file: drivers/net/phy/Kconfig ## CONFIG_MDIO_SUN4I=y +CONFIG_PHYLINK=m +CONFIG_SFP=m ## ## file: drivers/net/wireless/broadcom/brcm80211/Kconfig -- 2.18.0
Bug#906054: linux-image-4.18.0-rc5-armmp: Please enable support for SFP modules
Package: src:linux Version: 4.18~rc5-1~exp1 Severity: normal Dear Maintainer, With the release of linux 4.14 support for SFP pages has been introduced. Please enable support for this in the armmp and arm64 flavours. To name two devices that have an SFP port and can run debian testing: - solidrun clearfog (armhf) - marvell macchiatobin (arm64) The config option is declared in drivers/net/phy/Kconfig. Yours sincerely Josua Mayer -- Package-specific info: ** Version: Linux version 4.18.0-rc5-armmp (debian-ker...@lists.debian.org) (gcc version 7.3.0 (Debian 7.3.0-26)) #1 SMP Debian 4.18~rc5-1~exp1 (2018-07-19) ** Command line: console=ttyS0,115200 log_level=7 ** Not tainted ** Kernel log: [4.370612] xhci-hcd f10f8000.usb3: irq 49, io mem 0xf10f8000 [4.376577] usb usb4: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.18 [4.384886] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [4.392136] usb usb4: Product: xHCI Host Controller [4.397033] usb usb4: Manufacturer: Linux 4.18.0-rc5-armmp xhci-hcd [4.403319] usb usb4: SerialNumber: f10f8000.usb3 [4.408405] hub 4-0:1.0: USB hub found [4.412195] hub 4-0:1.0: 1 port detected [4.416332] xhci-hcd f10f8000.usb3: xHCI Host Controller [4.421697] xhci-hcd f10f8000.usb3: new USB bus registered, assigned bus number 5 [4.429790] xhci-hcd f10f8000.usb3: Host supports USB 3.0 SuperSpeed [4.436290] usb usb5: We don't know the algorithms for LPM for this host, disabling LPM. [4.75] usb usb5: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 4.18 [4.452770] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [4.460015] usb usb5: Product: xHCI Host Controller [4.460964] mvebu-pcie soc:pcie: PCI host bridge to bus :00 [4.464910] usb usb5: Manufacturer: Linux 4.18.0-rc5-armmp xhci-hcd [4.464913] usb usb5: SerialNumber: f10f8000.usb3 [4.481873] ata2: SATA link down (SStatus 0 SControl 300) [4.487368] pci_bus :00: root bus resource [io 0x1000-0xf] [4.488374] hub 5-0:1.0: USB hub found [4.494057] pci_bus :00: root bus resource [mem 0xe000-0xe7ff] [4.497548] hub 5-0:1.0: 1 port detected [4.504344] pci_bus :00: root bus resource [bus 00-ff] [4.504452] pci :00:02.0: [11ab:6828] type 01 class 0x060400 [4.531154] pci :00:03.0: [11ab:6828] type 01 class 0x060400 [4.533396] PCI: bus0: Fast back to back transfers disabled [4.539034] pci :00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring [4.540534] libphy: mv88e6xxx SMI: probed [4.547067] pci :00:03.0: bridge configuration invalid ([bus 00-00]), reconfiguring [4.547176] pci :01:00.0: [168c:003c] type 00 class 0x028000 [4.559162] pci :01:00.0: reg 0x10: [mem 0x-0x001f 64bit] [4.559188] pci :01:00.0: reg 0x30: [mem 0x-0x pref] [4.559291] pci :01:00.0: supports D1 D2 [4.559419] pci :00:02.0: ASPM: current common clock configuration is broken, reconfiguring [4.588832] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [4.591384] ata3: SATA link down (SStatus 0 SControl 300) [4.595836] PCI: bus1: Fast back to back transfers enabled [4.605962] pci_bus :01: busn_res: [bus 01-ff] end is updated to 01 [4.606019] ata1.00: ATA-10: 32GB SATA Flash Drive, SFPS925A, max UDMA/133 [4.612921] ata1.00: 62533296 sectors, multi 16: LBA48 NCQ (depth 32) [4.620224] PCI: bus2: Fast back to back transfers enabled [4.625742] pci_bus :02: busn_res: [bus 02-ff] end is updated to 02 [4.625771] pci :00:02.0: BAR 8: assigned [mem 0xe000-0xe02f] [4.630724] ata4: SATA link down (SStatus 0 SControl 300) [4.632602] pci :01:00.0: BAR 0: assigned [mem 0xe000-0xe01f 64bit] [4.645343] pci :01:00.0: BAR 0: error updating (0xe004 != 0x) [4.645353] ata1.00: configured for UDMA/133 [4.652590] pci :01:00.0: BAR 0: error updating (high 0x00 != 0x) [4.652596] pci :01:00.0: BAR 6: assigned [mem 0xe020-0xe020 pref] [4.671623] pci :00:02.0: PCI bridge to [bus 01] [4.673105] scsi 0:0:0:0: Direct-Access ATA 32GB SATA Flash 925A PQ: 0 ANSI: 5 [4.676614] pci :00:02.0: bridge window [mem 0xe000-0xe02f] [4.691545] pci :00:03.0: PCI bridge to [bus 02] [4.692950] sd 0:0:0:0: [sda] 62533296 512-byte logical blocks: (32.0 GB/29.8 GiB) [4.696594] pcieport :00:02.0: enabling device (0140 -> 0142) [4.705364] sd 0:0:0:0: [sda] Write Protect is off [4.715059] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [4.715739] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [4.726012] sda: sda1 sda2 sda3 < sda5 > [4.731729] sd 0:0:0:0: [sda] Attached SCSI removable disk [4.783902] random: fast init
Bug#906052: checked history
I have found no earlier version where this worked with the debian kernel. All of the following exhibit the problem with similar errors: - linux-image-4.9.0-7-armmp_4.9.110-3+deb9u1_armhf.deb - linux-image-4.16.0-2-armmp_4.16.16-2_armhf.deb - linux-image-4.18.0-rc5-armmp_4.18~rc5-1~exp1_armhf.deb So maybe this should be addresses directly to linux.
Bug#906052: linux-image-4.17.0-1-armmp: Compex WLE900VX (ath10k) doesn't probe
Package: src:linux Version: 4.17.8-1 Severity: normal Dear Maintainer, The Compex pci express wifi module fails to probe apparently because it isn't waking up. I can't see anything wrong here, and the module used to work with older (vendor) kernels. Any clues what is going on? Yours sincerely Josua Mayer -- Package-specific info: ** Version: Linux version 4.17.0-1-armmp (debian-ker...@lists.debian.org) (gcc version 7.3.0 (Debian 7.3.0-26)) #1 SMP Debian 4.17.8-1 (2018-07-20) ** Command line: console=ttyS0,115200 log_level=7 ** Not tainted ** Kernel log: [4.416771] xhci-hcd f10f8000.usb3: irq 49, io mem 0xf10f8000 [4.422722] usb usb4: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.17 [4.431024] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [4.438269] usb usb4: Product: xHCI Host Controller [4.443161] usb usb4: Manufacturer: Linux 4.17.0-1-armmp xhci-hcd [4.449273] usb usb4: SerialNumber: f10f8000.usb3 [4.454319] hub 4-0:1.0: USB hub found [4.458105] hub 4-0:1.0: 1 port detected [4.462249] xhci-hcd f10f8000.usb3: xHCI Host Controller [4.467591] xhci-hcd f10f8000.usb3: new USB bus registered, assigned bus number 5 [4.475109] xhci-hcd f10f8000.usb3: Host supports USB 3.0 SuperSpeed [4.481601] usb usb5: We don't know the algorithms for LPM for this host, disabling LPM. [4.489774] usb usb5: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 4.17 [4.498067] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [4.505312] usb usb5: Product: xHCI Host Controller [4.507447] libphy: mv88e6xxx SMI: probed [4.510205] usb usb5: Manufacturer: Linux 4.17.0-1-armmp xhci-hcd [4.510210] usb usb5: SerialNumber: f10f8000.usb3 [4.525199] mvebu-pcie soc:pcie: PCI host bridge to bus :00 [4.531163] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [4.537424] pci_bus :00: root bus resource [io 0x1000-0xf] [4.538185] hub 5-0:1.0: USB hub found [4.543750] pci_bus :00: root bus resource [mem 0xe000-0xe7ff] [4.547530] hub 5-0:1.0: 1 port detected [4.554399] ata1.00: ATA-10: 32GB SATA Flash Drive, SFPS925A, max UDMA/133 [4.565229] ata1.00: 62533296 sectors, multi 16: LBA48 NCQ (depth 31/32) [4.573566] pci_bus :00: root bus resource [bus 00-ff] [4.579734] pci :00:02.0: [11ab:6828] type 01 class 0x060400 [4.579934] pci :00:03.0: [11ab:6828] type 01 class 0x060400 [4.581309] PCI: bus0: Fast back to back transfers disabled [4.586922] pci :00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring [4.594958] pci :00:03.0: bridge configuration invalid ([bus 00-00]), reconfiguring [4.603149] ata1.00: configured for UDMA/133 [4.607484] pci :01:00.0: [168c:003c] type 00 class 0x028000 [4.607516] pci :01:00.0: reg 0x10: [mem 0x-0x001f 64bit] [4.607542] pci :01:00.0: reg 0x30: [mem 0x-0x pref] [4.607632] pci :01:00.0: supports D1 D2 [4.607759] scsi 0:0:0:0: Direct-Access ATA 32GB SATA Flash 925A PQ: 0 ANSI: 5 [4.607790] pci :00:02.0: ASPM: current common clock configuration is broken, reconfiguring [4.624813] sd 0:0:0:0: [sda] 62533296 512-byte logical blocks: (32.0 GB/29.8 GiB) [4.632799] sd 0:0:0:0: [sda] Write Protect is off [4.637615] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [4.637642] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [4.647734] sda: sda1 sda2 sda3 < sda5 > [4.652559] sd 0:0:0:0: [sda] Attached SCSI removable disk [4.658927] PCI: bus1: Fast back to back transfers enabled [4.664475] pci_bus :01: busn_res: [bus 01-ff] end is updated to 01 [4.665827] PCI: bus2: Fast back to back transfers enabled [4.671365] pci_bus :02: busn_res: [bus 02-ff] end is updated to 02 [4.671391] pci :00:02.0: BAR 8: assigned [mem 0xe000-0xe02f] [4.678247] pci :01:00.0: BAR 0: assigned [mem 0xe000-0xe01f 64bit] [4.685609] pci :01:00.0: BAR 0: error updating (0xe004 != 0x) [4.692890] pci :01:00.0: BAR 0: error updating (high 0x00 != 0x) [4.700416] pci :01:00.0: BAR 6: assigned [mem 0xe020-0xe020 pref] [4.706967] random: fast init done [4.707688] pci :00:02.0: PCI bridge to [bus 01] [4.716066] pci :00:02.0: bridge window [mem 0xe000-0xe02f] [4.722883] pci :00:03.0: PCI bridge to [bus 02] [4.730477] pcieport :00:02.0: enabling device (0140 -> 0142) [5.339193] Marvell 88E1540 mv88e6xxx-0:00: attached PHY driver [Marvell 88E1540] (mii_bus:phy_addr=mv88e6xxx-0:00, irq=64) [5.431158] Marvell 88E1540 mv88e6xxx-0:01: attached PHY driver [Marvell 88E1540] (mii_bus:phy_addr=mv88e6xxx-0:01, irq=65) [5.521407] Marvell 88E1540 mv88e6xxx-0:02:
Bug#905965: debian-installer: preseeding language fails
Hi Phil, Am 13.08.2018 um 16:08 schrieb Philip Hands: > Ben Hutchings writes: > >> On Sun, 2018-08-12 at 13:11 +, Josua Mayer wrote: >>> Package: debian-installer >>> Severity: normal >>> >>> Dear Maintainer, >>> >>> I have been trying to fully automate installing debian on the SolidRun >>> Clearfog through a preseed file. >>> However I cannot seem to skip the first two questions: >>> [!!] Select a language --> English >>> [!!] Select your location --> United Kingdom >> [...] >> >> Depending on where the preseed file is, these questions may be asked >> before the installer is able to load it. >> >> You can put the answers to these two questions on the kernel command >> line. See >> <https://www.debian.org/releases/stable/amd64/ch05s03.html.en#preseed-args>. Didn't try this yet so idk if it helps. I find auto=true to be much more practical! > Alternatively, if you're providing the preseed via a url (and I think > for a least some of the other options for preseeding) you can specify > auto=true, which delays these questions until after the preseed file is > available, and thus makes your preseeding work -- this is the purpose of > the various "Automatic Install" options in the boot menus. They just add > "auto=true" to the default kernel command line. That piece is actually magic. Changing from plain auto to auto=true makes these first two questions go away as expected! Thank you very much for this pointer. I couldn't find any mention of this on the wiki, and as I am only hacking on arm devices of course I never got to see the boot menus. > > Cheers, Phil. br Josua
Bug#905965: preseed.cfg
# Localization d-i debian-installer/locale string en_US # Networking d-i netcfg/choose_interface select eth0 d-i netcfg/get_hostname string imx6 d-i netcfg/get_domain string unassigned-domain # Debian Mirror d-i mirror/country string manual d-i mirror/http/hostname string deb.debian.org d-i mirror/http/directory string /debian d-i mirror/http/proxy string # Users and Passwords d-i passwd/root-login boolean false d-i passwd/user-fullname string Debian User d-i passwd/username string debian d-i passwd/user-password password debian d-i passwd/user-password-again password debian # Time d-i clock-setup/utc boolean true d-i time/zone string Israel d-i clock-setup/ntp boolean true # Partitioning d-i partman-auto/disk string /dev/sda d-i partman-auto/method string regular d-i partman-auto/choose_recipe atomic d-i partman-lvm/device_remove_lvm boolean true d-i partman-md/device_remove_md boolean true d-i partman-partitioning/confirm_write_new_label boolean true d-i partman/choose_partition select finish d-i partman/confirm boolean true d-i partman/confirm_nooverwrite boolean true # Package Selection tasksel tasksel/first multiselect standard, ssh-server # Package Survey popularity-contest popularity-contest/participate boolean false # Exit Installer d-i finish-install/reboot_in_progress note
Bug#905965: debian-installer: preseeding language fails
Package: debian-installer Severity: normal Dear Maintainer, I have been trying to fully automate installing debian on the SolidRun Clearfog through a preseed file. However I cannot seem to skip the first two questions: [!!] Select a language --> English [!!] Select your location --> United Kingdom I looked at the sample at https://www.debian.org/releases/stable/example-preseed.txt To quote "# Preseeding only locale sets language, country and locale." So I put the line d-i debian-installer/locale string en_US but I still get to see the question after booting with setenv bootargs "auto file=/hd-media/preseed.cfg" For reference I have seen this problem with two versions of the debian installer for testing: http://ftp.nl.debian.org/debian/dists/testing/main/installer-armhf/current/images/hd-media/hd-media.tar.gz https://cdimage.debian.org/cdimage/buster_di_alpha3/armhf/iso-cd/debian-buster-DI-alpha3-armhf-netinst.iso and the daily snapshot of today (12/08/2018) https://d-i.debian.org/daily-images/armhf/daily/hd-media/hd-media.tar.gz https://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/armhf/iso-cd/debian-testing-armhf-netinst.iso Am I just doing it wrong? I have tried examining the output of debconf-get-selections --installer but I couldn't find something helpful there. Yours sincerely Josua Mayer -- System Information: Debian Release: 9.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: armhf (armv7l) Kernel: Linux 4.17.0-0.bpo.1-armmp (SMP w/1 CPU core) 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#905962: flash-kernel: Support HummingBoard variants HummingBoard 2 and SoM version 1.5
Package: flash-kernel Version: 3.93 Severity: normal Tags: patch Dear Maintainer, Please add machine entries for HummingBoard variants with SoM revision 1.5, and HummingBoard 2. HB2 was introduced to mainline with 4.16. I have provided the missing entries as a patch file. -- System Information: Debian Release: 9.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: armhf (armv7l) Kernel: Linux 4.17.0-0.bpo.1-armmp (SMP w/1 CPU core) 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) Versions of packages flash-kernel depends on: ii debconf [debconf-2.0] 1.5.61 ii devio 1.2-1.2+b1 ii initramfs-tools0.130 ii linux-base 4.5 ii mtd-utils 1:2.0.0-1 ii ucf3.0036 Versions of packages flash-kernel recommends: ii u-boot-tools 2016.11+dfsg1-4 flash-kernel suggests no packages. -- Configuration Files: /etc/flash-kernel/db changed [not included] -- debconf information excluded >From f0df9cb040862aec41052261680f2eb5038d6408 Mon Sep 17 00:00:00 2001 From: Josua Mayer Date: Sun, 12 Aug 2018 14:04:40 +0200 Subject: [PATCH] Add missing entries for HummingBoard variants As of linux 4.16 the DeviceTrees for HummingBoard 2 have landed. Also add the microsom revision 1.5 for the first HummingBoard. Signed-off-by: Josua Mayer --- db/all.db | 70 +++ 1 file changed, 70 insertions(+) diff --git a/db/all.db b/db/all.db index 04d38f2..c156539 100644 --- a/db/all.db +++ b/db/all.db @@ -590,6 +590,20 @@ Boot-Script-Path: /boot/boot.scr U-Boot-Script-Name: bootscr.uboot-generic Required-Packages: u-boot-tools +Machine: SolidRun HummingBoard Solo/DualLite (1.5som) +Kernel-Flavors: armmp +DTB-Id: imx6dl-hummingboard-som-v15.dtb +Boot-Script-Path: /boot/boot.scr +U-Boot-Script-Name: bootscr.uboot-generic +Required-Packages: u-boot-tools + +Machine: SolidRun HummingBoard Solo/DualLite (1.5som+emmc) +Kernel-Flavors: armmp +DTB-Id: imx6dl-hummingboard-emmc-som-v15.dtb +Boot-Script-Path: /boot/boot.scr +U-Boot-Script-Name: bootscr.uboot-generic +Required-Packages: u-boot-tools + Machine: SolidRun HummingBoard Dual/Quad Kernel-Flavors: armmp DTB-Id: imx6q-hummingboard.dtb @@ -597,6 +611,62 @@ Boot-Script-Path: /boot/boot.scr U-Boot-Script-Name: bootscr.uboot-generic Required-Packages: u-boot-tools +Machine: SolidRun HummingBoard Dual/Quad (1.5som) +Kernel-Flavors: armmp +DTB-Id: imx6q-hummingboard-som-v15.dtb +Boot-Script-Path: /boot/boot.scr +U-Boot-Script-Name: bootscr.uboot-generic +Required-Packages: u-boot-tools + +Machine: SolidRun HummingBoard Dual/Quad (1.5som+emmc) +Kernel-Flavors: armmp +DTB-Id: imx6q-hummingboard-emmc-som-v15.dtb +Boot-Script-Path: /boot/boot.scr +U-Boot-Script-Name: bootscr.uboot-generic +Required-Packages: u-boot-tools + +Machine: SolidRun HummingBoard2 Solo/DualLite +Kernel-Flavors: armmp +DTB-Id: imx6dl-hummingboard2.dtb +Boot-Script-Path: /boot/boot.scr +U-Boot-Script-Name: bootscr.uboot-generic +Required-Packages: u-boot-tools + +Machine: SolidRun HummingBoard2 Solo/DualLite (1.5som) +Kernel-Flavors: armmp +DTB-Id: imx6dl-hummingboard2-som-v15.dtb +Boot-Script-Path: /boot/boot.scr +U-Boot-Script-Name: bootscr.uboot-generic +Required-Packages: u-boot-tools + +Machine: SolidRun HummingBoard2 Solo/DualLite (1.5som+emmc) +Kernel-Flavors: armmp +DTB-Id: imx6dl-hummingboard2-emmc-som-v15.dtb +Boot-Script-Path: /boot/boot.scr +U-Boot-Script-Name: bootscr.uboot-generic +Required-Packages: u-boot-tools + +Machine: SolidRun HummingBoard2 Dual/Quad +Kernel-Flavors: armmp +DTB-Id: imx6q-hummingboard2.dtb +Boot-Script-Path: /boot/boot.scr +U-Boot-Script-Name: bootscr.uboot-generic +Required-Packages: u-boot-tools + +Machine: SolidRun HummingBoard2 Dual/Quad (1.5som) +Kernel-Flavors: armmp +DTB-Id: imx6q-hummingboard2-som-v15.dtb +Boot-Script-Path: /boot/boot.scr +U-Boot-Script-Name: bootscr.uboot-generic +Required-Packages: u-boot-tools + +Machine: SolidRun HummingBoard2 Dual/Quad (1.5som+emmc) +Kernel-Flavors: armmp +DTB-Id: imx6q-hummingboard2-emmc-som-v15.dtb +Boot-Script-Path: /boot/boot.scr +U-Boot-Script-Name: bootscr.uboot-generic +Required-Packages: u-boot-tools + Machine: I12 / Q5 / QT840A A20 tvbox Kernel-Flavors: armmp armmp-lpae Boot-Script-Path: /boot/boot.scr -- 2.18.0
Bug#871792: wait a little
Sorry for the quick addition: a secodn uncertainty lies in the name of the boot script. We currently search for a bootargs.scr which was supposed to let distros set a few boot options, and then return control back to the menu. So maybe the name should be boot.scr instead. I will update once this has been decided.
Bug#871792: u-boot environment
Dear Maintainers, I finally found the time to capture the u-boot environment variables when bootargs.scr is run by our vendor boot script. This did involve changing the first script to set a few variables, and I am submitting my few changes to the vendor. I will update this bug when the changes have been accepted. I have some uncertainties in my code changes, but not in the result. The goal is using the generic boot script, so I don't think waiting for the vendor blocks adding entries to the db. I have created the following 3 machine entries, and verified that the system comes up properly after running flash-kernel: Machine: Goldelico GTA04A3 Kernel-Flavors: armmp Boot-Script-Path: /boot/bootargs.scr DTB-Id: omap3-gta04a3.dtb U-Boot-Script-Name: bootscr.uboot-generic Required-Packages: u-boot-tools Machine: Goldelico GTA04A4 Kernel-Flavors: armmp Boot-Script-Path: /boot/bootargs.scr DTB-Id: omap3-gta04a4.dtb U-Boot-Script-Name: bootscr.uboot-generic Required-Packages: u-boot-tools Machine: Goldelico GTA04A5 Kernel-Flavors: armmp Boot-Script-Path: /boot/bootargs.scr DTB-Id: omap3-gta04a5.dtb U-Boot-Script-Name: bootscr.uboot-generic Required-Packages: u-boot-tools Please find attached a logfile for demonstration purposes showing that the current 4.16 kernel actually works as intended. Yours sincerely Josua Mayer U-Boot SPL 2016.11-00249-gc9d20fc (Dec 18 2017 - 17:41:57) Trying to boot from MMC1 pop_mfr = 00 pop_id = 00 reading u-boot.img spl: payload image: U-Boot 2016.11-00249-gc9d20fc fo load addr: 0x800fffc0 size: 388656 reading u-boot.img Jumping to U-Boot loaded - jumping to U-Boot... U-Boot 2016.11-00249-gc9d20fc (Dec 18 2017 - 17:41:57 +0100) OMAP36XX/37XX-GP ES1.2, CPU-OPP2, L3-200MHz, Max CPU Clock 1 Ghz GTA04 + LPDDR/OneNAND I2C: ready DRAM: 1 GiB NAND: 0 Bytes MMC: OMAP SD/MMC: 0 *** Warning - bad CRC, using default environment OMAP die ID: 58b29ff8015a988206017025 Found GTA04A5 Device Tree: omap3-gta04a5one.dtb Net: usb_ether Error: usb_ether address not set. 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 load - load binary file from a filesystem Usage: load [ [ [ [bytes [pos] - Load binary file 'filename' from partition 'part' on device type 'interface' instance 'dev' to address 'addr' in memory. 'bytes' gives the size to load in bytes. If 'bytes' is 0 or omitted, the file is read until the end. 'pos' gives the file byte position to start reading from. If 'pos' is 0 or omitted, the file is read from the start. ## Executing script at 8200 Wrong image format for "source" command SCRIPT FAILED: continuing... reading /omap3-gta04a5one.dtb 72305 bytes read in 22 ms (3.1 MiB/s) switch to partitions #0, OK mmc0 is current device gpio: pin 173 (gpio 173) value is 1 gpio: pin 7 (gpio 7) value is 1 SD/MMC found on device 0 reading user.txt ** Unable to read file user.txt ** reading boot.scr 14843 bytes read in 14 ms (1 MiB/s) Running bootscript from mmc0 ... ## Executing script at 8020 USB charger detected Main battery charge:4116 mV Battery temperature:39 C Backup battery voltage: 2738 mV AC charger voltage: 14 mV USB charger voltage:5206 mV Charging current: 9 mA Charger present : 1 *** if you boot from NAND don-t worry about error messages when U-Boot tries to read a non-existing MMC *** Setting bus to 0 did init LED driver for TCA6507 ## Resetting to default environment *** initializing GTA04 environment *** Unknown command 'nand' - try 'help' OneNAND read: total chip size (0x0) exceeded! can not flash - must always boot from SD card *** initializing LCM *** board_video_init() for JBT6K74-AS / TD028TTEC1 did backlight_init() on GPIO_57 did panel_reg_init() dss panel config dss enable did board_video_init() did jbt_init_regs() lcm backlight level set to 255 (0..255) *** loading splash from MMC *** Setting bus to 0 reading splash.rgb16 ** Unable to read file splash.rgb16 ** reading splash.rgb16z 39304 bytes read in 15 ms (2.5 MiB/s) Uncompressed size: 614400 = 0x96000 *** initializing TSC for boot menu *** did tsc2007_init() *** loading boot menu image *** Setting bus to 0 reading menu.rgb16 ** Unable to read file menu.rgb16 ** reading menu.rgb16z 247281 bytes read in 34 ms (6.9 MiB/s) Uncompressed size: 614400 = 0x96000 Choosing by waiting for touch. 1 2 3 4 5 6 7 8 9 Press touch or any key to stop did choose 2/0 -> 3 background color: 00ff55 *** MMC boot partition 1*** new boot order 3 4 1 2 Setting bus to 0 did set bootargs for false trying partitions 3 4 1 2 ** File not found uImage ** ** File not found /boot/uImage ** ** File not found bootargs.scr ** 88 bytes read in 24 ms (2.9 KiB/s) ## Executing script at 8080 PARTITION=3 PARTITIONTYPE=EXT arch=arm baudrate=115200 b
Bug#902432: flash-kernel: There is a typo in Clearfog Pro DTB name
Package: flash-kernel Version: 3.91 Severity: important Tags: patch Dear Maintainer, There is a typo in the clearfog pro DTB name: pre -> pro. Easy enough to fix, so please find the patch below: >From 1d19172e0326a2e2ee2a5d236bad13a99a8f88e1 Mon Sep 17 00:00:00 2001 From: Josua Mayer Date: Tue, 26 Jun 2018 16:40:30 +0200 Subject: [PATCH] Clearfog Pro: correct DTB name The DTB for Clearfog Pro is actually called armada-388-clearfog-pro.dtb Signed-off-by: Josua Mayer --- db/all.db | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/db/all.db b/db/all.db index 14b1bc8..8f93d02 100644 --- a/db/all.db +++ b/db/all.db @@ -325,7 +325,7 @@ Required-Packages: u-boot-tools Machine: SolidRun Clearfog Pro A1 Kernel-Flavors: armmp Boot-Script-Path: /boot/boot.scr -DTB-Id: armada-388-clearfog-pre.dtb +DTB-Id: armada-388-clearfog-pro.dtb U-Boot-Script-Name: bootscr.uboot-generic Required-Packages: u-boot-tools -- 2.16.4 -- System Information: Debian Release: 9.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-6-amd64 (SMP w/2 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#894849: debian-installer: support dove cubox
Package: debian-installer Severity: wishlist Tags: d-i Dear Maintainer, Lets figure out how install media can be created that works with the original Dove Cubox. Bug#876773 has added support for this device to flash-kernel; Bug#876774 is about adding support to linux-image-armmp. The goal of this bug is generating a debian-installer image for use with block storage such as sata, usb or microsd that will actually boot by itself. Ideally with at least some packages for doing an offline installation. So this is the boot process we are working with: preinstalled U-boot on SPI Flash looks for boot.scr on usb -> mmc -> sata, first in /boot, then /. This U-Boot is very old and needs u-boot wrapped uImage with appended DTB, and uInitrd. For reference, this is the boot-script in flash-kernel: https://anonscm.debian.org/git/d-i/flash-kernel.git/commit/?id=7d9106b7a89df0b697d048e03a3f94f167e2e0d0 It is usable for booting d-i as is, however I am a little unsure about the substitutions @@LINUX_KERNEL_CMDLINE_DEFAULTS@@ @@LINUX_KERNEL_CMDLINE@@ @@UBOOT_ENV_EXTRA@@ So we need: boot.scr uImage uInitrd These can manually be created by issueing cat vmlinuz dtbs/dove-cubox.dtb > vmlinuz-dtb mkimage -A arm -O linux -T kernel -C none -a 0x8000 -e 0x8000 -d vmlinuz-dtb uImage mkimage -A arm -O linux -T ramdisk -C none -a 0 -e 0 -d initrd.gz uInitrd I did manage to build debian-installer from source, using the patched kernel package; and I can say that it boots and has internet access. Installation gets as far as searchign for kernel module packages on the Debian servers. However I have no idea what is required to load drivers for usb, sdhc and sata from the install drive. Please let me know what can be done to ultimately achieve readily usable installer images, say of the next debian release. Yours sincerely Josua Mayer *** End of the template - remove these template lines *** -- System Information: Debian Release: 9.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: armhf (armv7l) Kernel: Linux 4.16.0-rc6-armmp (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#876774: tested with 4.16-rc6, patch
Greetings once again, I have now rebuilt the current kernel package from sid, with the necessary config changes. So far it boots, and network works. I haven't tested anything else yet. Please find attached the patch for enabling the missing options. br Josua Mayer >From b7411e73b05896e024f4059f7ae5c27ad2942992 Mon Sep 17 00:00:00 2001 From: Josua Mayer Date: Tue, 3 Apr 2018 23:40:53 +0200 Subject: [PATCH] enable support for dove cubox This enables CONFIG_MACH_DOVE, and a few device-specific drivers. Signed-off-by: Josua Mayer --- debian/config/armhf/config | 17 + 1 file changed, 17 insertions(+) diff --git a/debian/config/armhf/config b/debian/config/armhf/config index d54d43eee..16e65cceb 100644 --- a/debian/config/armhf/config +++ b/debian/config/armhf/config @@ -78,6 +78,7 @@ CONFIG_MACH_ARMADA_375=y CONFIG_MACH_ARMADA_38X=y CONFIG_MACH_ARMADA_39X=y CONFIG_MACH_ARMADA_XP=y +CONFIG_MACH_DOVE=y ## ## file: arch/arm/mach-omap1/Kconfig @@ -134,6 +135,7 @@ CONFIG_ARCH_WM8850=y ## file: arch/arm/mm/Kconfig ## CONFIG_ARM_THUMBEE=y +CONFIG_CACHE_TAUROS2=y ## ## file: arch/arm/plat-omap/Kconfig @@ -197,6 +199,7 @@ CONFIG_COMMON_CLK_MAX77686=m CONFIG_COMMON_CLK_RK808=m CONFIG_COMMON_CLK_S2MPS11=m CONFIG_CLK_TWL6040=m +CONFIG_COMMON_CLK_SI5351=m ## ## file: drivers/cpufreq/Kconfig @@ -438,6 +441,7 @@ CONFIG_I2C_MESON=m ## CONFIG_I2C_ARB_GPIO_CHALLENGE=m CONFIG_I2C_MUX_PCA954x=m +CONFIG_I2C_MUX_PINCTRL=m ## ## file: drivers/iio/Kconfig @@ -641,6 +645,7 @@ CONFIG_MMC_WMT=m CONFIG_MMC_SUNXI=m CONFIG_MMC_BCM2835=m CONFIG_MMC_MESON_MX_SDIO=m +CONFIG_MMC_SDHCI_DOVE=m ## ## file: drivers/mtd/Kconfig @@ -754,6 +759,7 @@ CONFIG_E100=m CONFIG_MVMDIO=m CONFIG_MVNETA=m CONFIG_MVPP2=m +CONFIG_MV643XX_ETH=m ## ## file: drivers/net/ethernet/microchip/Kconfig @@ -882,6 +888,11 @@ CONFIG_PHY_SUN4I_USB=m CONFIG_PHY_SUN9I_USB=m ## +## file: drivers/phy/marvell/Kconfig +## +CONFIG_PHY_MVEBU_SATA=m + +## ## file: drivers/phy/rockchip/Kconfig ## CONFIG_PHY_ROCKCHIP_DP=m @@ -1080,6 +1091,7 @@ CONFIG_SPI_MESON_SPIFC=m ## CONFIG_ROCKCHIP_THERMAL=m CONFIG_ARMADA_THERMAL=y +CONFIG_DOVE_THERMAL=m ## ## file: drivers/thermal/broadcom/Kconfig @@ -1335,6 +1347,11 @@ CONFIG_SND_SOC_IMX_MC13783=m CONFIG_SND_SIMPLE_CARD=m ## +## file: sound/soc/kirkwood/Kconfig +## +CONFIG_SND_KIRKWOOD_SOC=m + +## ## file: sound/soc/omap/Kconfig ## CONFIG_SND_OMAP_SOC=m -- 2.13.6
Bug#871792: flash-kernel: please add support for Golden Delicious GTA04 phone
Hi Vagrant, I believe that we should expect the generic boot-script to just work. If it doesn't that will be because of bugs in our boot menu script, and we can fix those outside of Debian. For the next two to 3 weeks I won't have time to acquire that environment, but maybe I can get someone else to post it. As to the models: Yes, those seem correct. So we will need an entry for each of them? Supported kernel flavors: armmp, no lpae. What I was asking before is if it is possible to have a wildcard entry for the device variants that would always copy a set of DTBs to /boot, to make moving the sdcard between devices easier. But this is just a wishlist item, if flash-kernel doesn't work that way, so be it. Also: is there a way to modify this later if we ever want to be able to install directly to nand flash(meaning kernel and rootfs) in such a way that people can choose during install if they want to use sdcard or nand? Such that when installed to sdcard, flash-kernel will never touch nand flash, and vice versa? Again, another wishlist item. br Josua Mayer
Bug#839595: news?
Hi everybody, Pinging this issue in case it fell off the table. If anything is preventing this from going forward that I can influence, please let me know! br Josua Mayer
Bug#876773: flash-kernel: Please add support for the original SolidRun CuBox (Dove)
Hi Vagrant,
thanks for your reply!
I have now come up with a revised script taking your comments into
consideration.
Am 25.09.2017 um 21:22 schrieb Vagrant Cascadian:
> On 2017-09-25, Josua Mayer wrote:
>> The SolidRun CuBox has very good support in Mainline Linux.
>> Thus it is a great candidate for supporting it in Debian.
> ...
>> I have come up with the database entry below, and this preliminary
>> boot-script:
>> setenv loadaddr 0x0200
>> setenv loadaddrrd 0x2000
>> setenv bootargs console=ttyS0,115200n8
>> ${fstype}load ${device_name} 0:${partition} ${loadaddr} /boot/uImage
>> ${fstype}load ${device_name} 0:${partition} ${loadaddrrd} /boot/uInitrd
>> bootm $loadaddr $loadaddrrd
> loaddr is already set in your environment, no need to set it again.
Yes. I just wanted to be verbose.
>
> If you use:
>
> setenv bootargs @@LINUX_KERNEL_CMDLINE_DEFAULTS@@ ${bootargs} ${console}
> @@LINUX_KERNEL_CMDLINE@@
>
> Then flash-kernel can be configured with options from
> /etc/default/flash-kernel.
Ack
>
> And have this before the load/bootm parts:
>
> @@UBOOT_ENV_EXTRA@@
>
> Then local environment overrides can be set from
> /etc/flash-kerenel/ubootenv.d or /usr/share/flash-kernel/ubootenv.d.
Ack
>
>
>> I am running U-Boot 2009.08-dirty (Mar 09 2013 - 18:15:45) Marvell version:
>> 5.4.4 NQ SR1.
>> It comes with a prepopulated bootcmd environment variable that tries out:
>> - usb sata(ide) mmc
>> - partitions 1,2
>> - directores / and /boot
>> to find a boot.scr.
>> At the time of loading it, these variables are set accordingly:
>> device_name, partition, directory, fstype
>> which can be used in our boot.scr.
> You also *might* want to emulate upstream u-boot conventions and use the
> variables consistant with other boot scripts, and set up a thin
> compatibility layer:
>
> setenv kernel_addr_r $loadaddr
> setenv ramdisk_addr_r 0x2000
> setenv devtype $device_name
> setenv devnum 0
> setenv bootpart $partition
> setenv distro_bootpart $partition
> setenv prefix $directory
>
> With that at the top of your file, you could probably copy the
> uboot-generic script and make minor modifications to get it working
> (change "load" to "${fstype}load" and "bootz" to "bootm", change "/boot"
> to "${prefix}"), and it would be more similar to the standard boot
> scripts, and it'd be easier to adapt if upstream u-boot support was
> later added with distro_bootcmd support.
True.
I decided to structure it very similar, but avoid the copy.
>
>
>> One important thing that is missing, is bootargs!
>> We need to set: console, root, rootfstype, rootwait
> Your bootscript already sets the console in bootargs, so I'm not sure
> what you mean...
That is what I meant.
It would be neat using just console=${console}, but the console variable
in u-boot is set to
console=console=ttyS0,115200useNandHal=single
which is not nice style.
So I hardcoded it now.
>
>> - rootfstype could be gathered from fstype
> I would not assume that the / fs and /boot fs are the same. But, you
> shouldn't need to set that if you're using an initrd that can detect the
> filesystem on it's own (e.g. initramfs-tools).
Ack
>
>> - any ideas how to generate the root= option?
>> Ideally we could use UUID= there!
>> Or does Bootloader-Sets-Incorrect-Root: yes help here?
> Again, with initramfs-tools, flash-kernel adds a root= entry based on
> fstab in the initrd, so that in that case, you don't need root= defined
> in the u-boot environment.
Ack.
After regenerating my initrd, I managed to boot with cmdline:
console=ttyS0,115200n8 quiet
>
>
> live well,
> vagrant
br
Josua Mayer
# Boot-Script for SolidRun CuBox (Dove)
# environment variables provided by the 2009.08* vendor U-Boot:
# device_name [usb,mmc,ide]
# partition [1,2]
# directory [/,/boot/]
# fstype [ext4,fat]
# set load-address for ramdisk image
setenv loadaddrrd 0x2000
# set up serial console as default
setenv console ttyS0,115200n8
# set bootargs
setenv bootargs @@LINUX_KERNEL_CMDLINE_DEFAULTS@@ console=${console}
@@LINUX_KERNEL_CMDLINE@@
# set up distr-boot-like variable names where possible
setenv devnum 0
setenv devtype ${device_name}
setenv distro_bootpart ${partition}
setenv kernel_addr_r ${loadaddr}
setenv prefix ${directory}
setenv ramdisk_addr_r ${loadaddrrd}
# allow overriding u-boot environment
@@UBOOT_ENV_EXTRA@@
# look for boot images where this script was loaded from
setenv partition ${distro_bootpart}
# Boot it
${fstype}load ${devtype} ${devnum}:${partition} ${kernel_addr_r} ${prefix}uImage
${fstype}load ${devtype} ${devnum}:${partition
Bug#876773: U-Boot environment
I am hereby providing the complete U-Boot environment:
CuBox>> printenv
baudrate=115200
loads_echo=0
rootpath=/mnt/ARM_FS/
netmask=255.255.255.0
console=console=ttyS0,115200 useNandHal=single
mtdids=nand0=dove-nand
mtdparts=mtdparts=dove-nand:4m(boot),-(rootfs)
arcNumber=3905
CASset=min
MALLOC_len=5
ethprime=egiga0
bootargs_root=root=/dev/nfs rw
bootargs_end=:::dove:eth0:none
image_name=uImage
tftpbootcmd=tftpboot 0x200 ${image_name}; setenv bootargs ${console}
${mtdparts} ${bootargs_root} nfsroot=${serverip}:${rootpath}
ip=${ipaddr}:${serverip}${bootargs_end} usb0Mode=${usb0Mode}
usb1Mode=${usb1Mode}
video=dovefb:lcd0:${lcd0_params},lcd1:${lcd1_params}
clcd.lcd0_enable=${lcd0_enable} clcd.lcd1_enable=${lcd1_enable}; bootm
0x200;
standalone=fsload 0x200 ${image_name};setenv bootargs ${console}
${mtdparts} root=/dev/mtdblock0 rw
ip=${ipaddr}:${serverip}${bootargs_end} usb0Mode=${usb0Mode}
usb1Mode=${usb1Mode}
video=dovefb:lcd0:${lcd0_params},lcd1:${lcd1_params}
clcd.lcd0_enable=${lcd0_enable} clcd.lcd1_enable=${lcd1_enable}; bootm
0x200;
disaMvPnp=no
usb0Mode=host
usb1Mode=host
yuk_ethaddr=00:00:00:EE:51:81
lcd0_enable=0
lcd1_enable=1
lcd0_params=1280x768-24@60
lcd1_params=640x480-16@60
ethact=egiga0
bootdelay=3
filesize=52FEC
ipaddr=192.168.15.223
serverip=192.168.15.100
stdin=serial
stdout=serial
stderr=serial
passDramInitTag=yes
mainlineLinux=yes
enaMonExt=no
pexMode=RC
disL2Cache=no
disL2Ecc=no
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
bootscript=boot.scr
loadaddr=0x0200
mmc_started=0
ide_started=0
usb_started=0
trydev=usb mmc ide
trypart=1 2
trydir=/ /boot/
tryfs=ext4 fat
bootcmd=for device_name in ${trydev} ; do for partition in ${trypart} ;
do for directory in ${trydir} ;do for fstype in ${tryfs}; do echo ===>
Executing ${fstype}load ${device_name} 0:${partition} ${loadaddr}
${directory}${bootscript};if itest.s $device_name -eq mmc; then if
itest.s $mmc_started -ne 1; then mmcinfo; setenv mmc_started
'1';fi;fi;if itest.s $device_name -eq usb; then if itest.s $usb_started
-ne 1; then usb start; setenv usb_started '1';fi;fi;if itest.s
$device_name -eq ide; then if itest.s $ide_started -ne 1; then ide
reset; setenv ide_started '1';fi;fi;if ${fstype}load ${device_name}
0:${partition} ${loadaddr} ${directory}${bootscript}; then source
${loadaddr};fi;if itest.s $device_name -eq usb; then echo ===> Executing
${fstype}load ${device_name} 1:${partition} ${loadaddr}
${directory}${bootscript};if ${fstype}load ${device_name} 1:${partition}
${loadaddr} ${directory}${bootscript}; then source
${loadaddr};fi;fi;done;done;done;done;tftp ${loadaddr}
${bootscript};source ${loadaddr};
ethaddr=d0:63:b4:00:04:5e
enaL2ExtraFeatures=yes
enaCpuStream=no
enaVpuPower=no
enaGpuPower=yes
Environment size: 2672/65532 bytes
Bug#876774: linux-image-4.9.0-3-armmp: please enable missing configuration options for dove cubox
Package: src:linux Version: 4.9.30-2+deb9u5 Severity: wishlist Tags: patch Dear Maintainer, Please enable the required config options for supporting the SolidRun CuBox (Dove). This machine is extremely well supported in Mainline and it would be great if it could become a first-class citizen of Debian. Note that not only the 4.9.0-armmp is affected, but also any later kernel package at this point. I'd be happy to test any version after enabling the missing options! But getting it into stretch would be supreme. I have collected these missing options: CONFIG_MACH_DOVE=y CONFIG_CACHE_TAUROS2=y CONFIG_CPU_PJ4=y CONFIG_DOVE_CLK=y CONFIG_DOVE_THERMAL=n CONFIG_MMC_SDHCI_DOVE=n CONFIG_ORION_IRQCHIP=y CONFIG_ORION_TIMER=y CONFIG_PHY_MVEBU_SATA=y CONFIG_PINCTRL_DOVE=y CONFIG_COMMON_CLK_SI5351=m CONFIG_I2C_MUX_PINCTRL=m CONFIG_MMC_SDHCI_DOVE=m CONFIG_MV643XX_ETH=m CONFIG_PHY_MVEBU_SATA=m CONFIG_SND_KIRKWOOD_SOC=m CONFIG_DOVE_THERMAL=m # This one is not needed, it is present on the SoC, but not exposed by the Cubox CONFIG_DRM_ARMADA=m I have built mainline 4.9.45 from the armmp .config, and above options to verify that it actually does work! Yours sincerely Josua Mayer -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information Hardware: Marvell Dove Revision: Device Tree model: SolidRun CuBox ** PCI devices: ** USB devices: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub -- System Information: Debian Release: 9.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: armhf (armv7l) Kernel: Linux 4.9.45-dove-cubox (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-image-4.9.0-3-armmp depends on: ii initramfs-tools [linux-initramfs-tool] 0.130 ii kmod23-2 ii linux-base 4.5 Versions of packages linux-image-4.9.0-3-armmp recommends: ii firmware-linux-free 3.4 ii irqbalance 1.1.0-2.3 Versions of packages linux-image-4.9.0-3-armmp suggests: pn debian-kernel-handbook pn linux-doc-4.9 Versions of packages linux-image-4.9.0-3-armmp is related to: pn firmware-amd-graphics pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x pn firmware-brcm80211 pn firmware-cavium pn firmware-intel-sound pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv pn firmware-iwlwifi pn firmware-libertas pn firmware-linux-nonfree pn firmware-misc-nonfree pn firmware-myricom pn firmware-netxen pn firmware-qlogic pn firmware-realtek pn firmware-samsung pn firmware-siano pn firmware-ti-connectivity pn xen-hypervisor -- no debconf information
Bug#876773: flash-kernel: Please add support for the original SolidRun CuBox (Dove)
Package: flash-kernel
Version: 3.79
Severity: wishlist
Tags: patch
Dear Maintainer,
The SolidRun CuBox has very good support in Mainline Linux.
Thus it is a great candidate for supporting it in Debian.
As I see it there are only 2 blockers right now:
- missing conifg options in the kernel package
- missing entry in flash-kernel
In this bug I'd like to solve the latter.
The board comes with a pretty old version of U-Boot that does support neither
bootz nor distro_boot.
This is why we need:
- a custom boot.scr
- uImage with appended DTB
- uInitrd
- a way to set root= cmdline option
I have come up with the database entry below, and this preliminary boot-script:
setenv loadaddr 0x0200
setenv loadaddrrd 0x2000
setenv bootargs console=ttyS0,115200n8
${fstype}load ${device_name} 0:${partition} ${loadaddr} /boot/uImage
${fstype}load ${device_name} 0:${partition} ${loadaddrrd} /boot/uInitrd
bootm $loadaddr $loadaddrrd
I am running U-Boot 2009.08-dirty (Mar 09 2013 - 18:15:45) Marvell version:
5.4.4 NQ SR1.
It comes with a prepopulated bootcmd environment variable that tries out:
- usb sata(ide) mmc
- partitions 1,2
- directores / and /boot
to find a boot.scr.
At the time of loading it, these variables are set accordingly:
device_name, partition, directory, fstype
which can be used in our boot.scr.
One important thing that is missing, is bootargs!
We need to set: console, root, rootfstype, rootwait
- rootfstype could be gathered from fstype
- any ideas how to generate the root= option?
Ideally we could use UUID= there!
Or does Bootloader-Sets-Incorrect-Root: yes help here?
Please let me know if I can provide any additional details, or if you have
something for me to test.
One note about testing: Can I get flash-kernel to work with a custom built
kernel, as long as the necessary config options are not enabled in -armmp?
Yours sincerely
Josua Mayer
-- System Information:
Debian Release: 9.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: armhf (armv7l)
Kernel: Linux 4.9.45-dove-cubox (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages flash-kernel depends on:
ii debconf [debconf-2.0] 1.5.61
ii devio 1.2-1.2+b1
ii initramfs-tools0.130
ii linux-base 4.5
ii mtd-utils 1:2.0.0-1
ii ucf3.0036
Versions of packages flash-kernel recommends:
ii u-boot-tools 2016.11+dfsg1-4
flash-kernel suggests no packages.
-- Configuration Files:
/etc/flash-kernel/db changed:
Machine: SolidRun CuBox
Kernel-Flavors: armmp
DTB-Id: dove-cubox.dtb
DTB-Append: yes
Boot-Kernel-Path: /boot/uImage
Boot-Initrd-Path: /boot/uInitrd
U-Boot-Kernel-Address: 0x8000
U-Boot-Initrd-Address: 0x0
Boot-Script-Path: /boot/boot.scr
U-Boot-Script-Name: bootscr.cubox
Required-Packages: u-boot-tools
Bootloader-Sets-Incorrect-Root: yes
Machine: SolidRun CuBox (Engineering Sample)
Kernel-Flavors: armmp
DTB-Id: dove-cubox-es.dtb
DTB-Append: yes
Boot-Kernel-Path: /boot/uImage
Boot-Initrd-Path: /boot/uInitrd
U-Boot-Kernel-Address: 0x8000
U-Boot-Initrd-Address: 0x0
Boot-Script-Path: /boot/boot.scr
U-Boot-Script-Name: bootscr.cubox
Required-Packages: u-boot-tools
Bootloader-Sets-Incorrect-Root: yes
-- debconf information excluded
Bug#772628: Use-Case
Hi everyone, I have once more come across this issue and would like to share with you why I think this feature should be enabled: I have several devices with small flash storage: Openmoko GTA02, Goldelico GTA04, Beaglebone and quite a few slow SD-Cards class-10, and devices that can't do UHS-1: Cubox, Cubox-i, RaspberryPi The first group would benefit by requiring less disk space for the Kernel. That is either a custom kernel where the vendor enables comrpessed modules, or in the future the Debian Kernel if maintainers can be persuaded to enable that feature (which obviously depends on this very issue). The second group will benefit from faster updates of kernels (with such compression enabled). Maintainers, please reconsider enabling this feature. Yours sincerely Josua Mayer
Bug#839595: Device-Tree naming and hardware variants
Hi there, Now it is time to raise a different problem: Hardware Variants. Right now we have the Clearfog Pro, and the Clearfog Base. The future might bring also introduce other CPU variants different from Armada-388 (but thats pure speculation). The Device-Tree was actually renamed in mainline with 712032aa65ae19a613488f8ce956e575cc5e1486, to armada-388-clearfog-pro.dts. That one sets the model field to "SolidRun Clearfog Pro A1". Then we have the "SolidRun Clearfog Base A1" in armada-388-clearfog-base.dts. How can these variants be mirrored in flash-kernel? And is there a way to allow moving SD-Cards between device variants? That would be a *really* useful feature! Either way, what can we do about this? br Josua Mayer
Bug#839595: tested
Hi again everybody, I finally got around to trying this out myself using a freshly debootstrapped stretch, and 2017.07-rc3 u-boot and these are my findings with the early posted db entry: The device-tree gets copied as expected boot.scr gets generated root= argument is not added to cmdline: That is actually fine! I still had some trouble with mounting the rootfs, because it turns out I used /dev/root short-hand in my fstab. This is a problem because flash-kernel picks that value up and stores it as conf/conf.d/default_root. Obviously passing root=/dev/root makes no sense to the kernel. I might even go as far as suggesting to not populate default_root if it is set to this magical value! Anyway after putting a UUID=... line in my fstab its all good! And now to question the Kernel-Flavors Line: Does anybody know if the Armada 388 supports lpae? I did not manage finding sufficient information. However I can tell you that the current linux-image-4.9.0-3-armmp-lpae does *not* boot! That means the serial console stays quiet after "Starting kernel ..." So I now have this database entry: Machine: SolidRun Clearfog A1 Kernel-Flavors: armmp Boot-Script-Path: /boot/boot.scr DTB-Id: armada-388-clearfog.dtb U-Boot-Script-Name: bootscr.uboot-generic Required-Packages: u-boot-tools br Josua Mayer
Bug#871792: flash-kernel: please add support for Golden Delicious GTA04 phone
Package: flash-kernel Severity: wishlist Dear Maintainer, Please add support for above mentioned phone. Since debian armmp kernel 4.9.13-1 the board is reasonably well supported, though charging isn't working, which is why I use a custom kernel here. It comes with a downstream u-boot variant based on 2016.11. For the sake of simplicity, it is reasonable to expect that there is a vendor-provided u-boot binary already installed in nand flash. It looks for a boot.scr on any MBR partition on the microSD card (there is a boot menu available), and executes it if found. I am pretty sure the current vendor boot-script does not set the expected distro_bootpart, and related variables but we can add the necessary pieces as they come up! The rootfs might also be on nand flash, but lets skip that for starters because the vendor boot-script could use some improvement in that area. It currently looks for a kernel uImage and bootm`s that without any initrd. More details: There are several iterations of the GTA04, and of its early prototypes. U-Boot auto-detects at least all those that were shipped to customers, and sets fdtfile variable as appropriate. This is the list of DTBs included with linux-image-4.9.0-3-armmp: /usr/lib/linux-image-4.9.0-3-armmp/omap3-gta04a3.dtb /usr/lib/linux-image-4.9.0-3-armmp/omap3-gta04a4.dtb /usr/lib/linux-image-4.9.0-3-armmp/omap3-gta04a5.dtb If you need any further details, let me know! Yours sincerely Josua Mayer -- System Information: Debian Release: 8.9 APT prefers oldoldstable APT policy: (500, 'oldoldstable'), (500, 'oldstable') Architecture: armhf (armv7l) Kernel: Linux 4.12.3-letux+ (SMP w/1 CPU core; PREEMPT) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init)
Bug#839595: flash-kernel: Please add support for SolidRun Clearfog
Hi Vagrant, thanks for the reply. On Sun, 23 Jul 2017 12:56:35 -0400 Vagrant Cascadian wrote: > On a related note, nobody has requested the clearfog target be enabled > in the u-boot packages in Debian: > > https://wiki.debian.org/U-boot/ > > If someone can offer to regularly test that, I'd be happy to enable it > in u-boot. I'd be happy to do that, what is the process? > > > I don't think that should be a blocker for including it into > flash-kernel, though. > > > live well, > vagrant
Bug#839595: Status
Hi there, Can anyone state the status here? If there is somethign missing, I'd be perfectly willing to conduct some tests on my board if necessary. br Josua Mayer
Bug#855472: (no subject)
This is about linux-image-4.9.0-1-armmp in stretch, armhf.
Bug#855472: display drivers missing for gta04 board
Package: src:linux Version: 4.9.6-3 Severity: normal Tags: upstream Dear Maintainers, Please enable following set of configs to support the display on GTA04 phone: CONFIG_DRM_OMAP_PANEL_TPO_TD028TTEC1=m CONFIG_PWM_OMAP_DMTIMER=m This enables the driver for the connected display, and the pwm driver that is used for backlight. br Josua Mayer
Bug#855174: catz: not found. Encountered while running make images.
Am 15.02.2017 um 00:40 schrieb Steve McIntyre: > On Wed, Feb 15, 2017 at 12:17:03AM +0100, Josua Mayer wrote: >> Package: debian-cd >> Version: 3.1.19 >> Severity: important >> >> Dear Maintainer, >> >> I am attempting to reproduce creating installer isos using debian-cd. >> Following the README I set up a mirror using debmirror, and then ran the >> mentioned mkae steps up to make images, where I encountered an error message >> concerning a command called catz (never heard of it). >> I suspect debian-cd is missing a runtime dependency. > No, catz is an internal helper script. Looks like I missed a path for > it in one place, now fixed. Thanks for that report. > >> This is the short log leading to the error: >> root@vm-stretch:/usr/share/debian-cd# make images >> Looking in /opt/debmirror/dists/stretch/ /opt/debmirror/dists/stretch/ >> Using MD5 sums from Packages files: >> /opt/debmirror/dists/stretch/contrib/binary-arm64/Packages.xz >> /opt/debmirror/dists/stretch/contrib/binary-arm64/Packages.gz >> /opt/debmirror/dists/stretch/main/binary-arm64/Packages.xz >> /opt/debmirror/dists/stretch/main/binary-arm64/Packages.gz >> /opt/debmirror/dists/stretch/main/debian-installer/binary-arm64/Packages.xz >> /opt/debmirror/dists/stretch/main/debian-installer/binary-arm64/Packages.gz >> /opt/debmirror/dists/stretch/non-free/binary-arm64/Packages.xz >> /opt/debmirror/dists/stretch/non-free/binary-arm64/Packages.gz >> /opt/debmirror/dists/stretch/contrib/binary-arm64/Packages.xz >> /opt/debmirror/dists/stretch/contrib/binary-arm64/Packages.gz >> /opt/debmirror/dists/stretch/main/binary-arm64/Packages.xz >> /opt/debmirror/dists/stretch/main/binary-arm64/Packages.gz >> /opt/debmirror/dists/stretch/main/debian-installer/binary-arm64/Packages.xz >> /opt/debmirror/dists/stretch/main/debian-installer/binary-arm64/Packages.gz >> /opt/debmirror/dists/stretch/non-free/binary-arm64/Packages.xz >> /opt/debmirror/dists/ >> stretch/non-free/binary-arm64/Packages.gz >> /usr/share/debian-cd/tools/grab_md5: 74: >> /usr/share/debian-cd/tools/grab_md5: catz: not found >> Generating the arm64 iso/jigdo images ... >> Last-minute updates: >>README.html >> md5sum: ./README.html: No such file or directory >> Makefile:479: recipe for target 'images' failed >> make: *** [images] Error 1 >> root@vm-stretch:/usr/share/debian-cd# > But the real reason for the stop here is the missing README.html > file. That should have been generated by the tools/add-bin-doc > script, and that's called each time a new temp disc tree is > started. Do you have logs going back further? > Attaching the logs of a fresh attempt (after syncing debmirror). This time every build step was a success, so I don't think we'll find in these logs what went wrong before. Updating task files... - copying task files from 'tasks/stretch/' - generating dynamic task files update_tasks: Using "gnome" as the default desktop, as specified by pool/main/t/tasksel/task-desktop_3.39_all.deb Missing package file for arm64/contrib. Generating a fake status file for apt-get and apt-cache... :> /srv/mirror/tmp/apt/status # Set up keyring so apt doesn't complain Setting up archive-keyring # Updating the apt database Get:1 file:/opt/debmirror stretch InRelease [184 kB] Get:1 file:/opt/debmirror stretch InRelease [184 kB] Get:2 file:/opt/debmirror stretch/main arm64 Packages [6,926 kB] Ign:2 file:/opt/debmirror stretch/main arm64 Packages Get:3 file:/opt/debmirror stretch/main arm64 Contents (deb) [31.0 MB] Ign:3 file:/opt/debmirror stretch/main arm64 Contents (deb) Get:4 file:/opt/debmirror stretch/contrib arm64 Packages [42.1 kB] Ign:4 file:/opt/debmirror stretch/contrib arm64 Packages Get:5 file:/opt/debmirror stretch/contrib arm64 Contents (deb) [94.6 kB] Ign:5 file:/opt/debmirror stretch/contrib arm64 Contents (deb) Get:6 file:/opt/debmirror stretch/main/debian-installer arm64 Packages [49.2 kB] Ign:6 file:/opt/debmirror stretch/main/debian-installer arm64 Packages Get:2 file:/opt/debmirror stretch/main arm64 Packages [6,926 kB] Get:3 file:/opt/debmirror stretch/main arm64 Contents (deb) [31.0 MB] Get:4 file:/opt/debmirror stretch/contrib arm64 Packages [42.1 kB] Get:5 file:/opt/debmirror stretch/contrib arm64 Contents (deb) [94.6 kB] Get:6 file:/opt/debmirror stretch/main/debian-installer arm64 Packages [49.2 kB] Reading package lists... W: Target Contents-deb-legacy (Contents-arm64) is configured multiple times in /srv/mirror/tmp/apt/stretch-arm64/apt/sources.list:1 and /srv/mirror/tmp/apt/stretch-arm64/apt/sources.list:2 W: Target Contents-deb-legacy (Contents-all) is configured multiple times in /srv/mirror/tmp/apt/stretch-arm64/apt/sourc
Bug#855174: catz: not found. Encountered while running make images.
Am 15.02.2017 um 00:40 schrieb Steve McIntyre: > On Wed, Feb 15, 2017 at 12:17:03AM +0100, Josua Mayer wrote: >> Package: debian-cd >> Version: 3.1.19 >> Severity: important >> >> Dear Maintainer, >> >> I am attempting to reproduce creating installer isos using debian-cd. >> Following the README I set up a mirror using debmirror, and then ran the >> mentioned mkae steps up to make images, where I encountered an error message >> concerning a command called catz (never heard of it). >> I suspect debian-cd is missing a runtime dependency. > No, catz is an internal helper script. Looks like I missed a path for > it in one place, now fixed. Thanks for that report. > >> This is the short log leading to the error: >> root@vm-stretch:/usr/share/debian-cd# make images >> Looking in /opt/debmirror/dists/stretch/ /opt/debmirror/dists/stretch/ >> Using MD5 sums from Packages files: >> /opt/debmirror/dists/stretch/contrib/binary-arm64/Packages.xz >> /opt/debmirror/dists/stretch/contrib/binary-arm64/Packages.gz >> /opt/debmirror/dists/stretch/main/binary-arm64/Packages.xz >> /opt/debmirror/dists/stretch/main/binary-arm64/Packages.gz >> /opt/debmirror/dists/stretch/main/debian-installer/binary-arm64/Packages.xz >> /opt/debmirror/dists/stretch/main/debian-installer/binary-arm64/Packages.gz >> /opt/debmirror/dists/stretch/non-free/binary-arm64/Packages.xz >> /opt/debmirror/dists/stretch/non-free/binary-arm64/Packages.gz >> /opt/debmirror/dists/stretch/contrib/binary-arm64/Packages.xz >> /opt/debmirror/dists/stretch/contrib/binary-arm64/Packages.gz >> /opt/debmirror/dists/stretch/main/binary-arm64/Packages.xz >> /opt/debmirror/dists/stretch/main/binary-arm64/Packages.gz >> /opt/debmirror/dists/stretch/main/debian-installer/binary-arm64/Packages.xz >> /opt/debmirror/dists/stretch/main/debian-installer/binary-arm64/Packages.gz >> /opt/debmirror/dists/stretch/non-free/binary-arm64/Packages.xz >> /opt/debmirror/dists/ >> stretch/non-free/binary-arm64/Packages.gz >> /usr/share/debian-cd/tools/grab_md5: 74: >> /usr/share/debian-cd/tools/grab_md5: catz: not found >> Generating the arm64 iso/jigdo images ... >> Last-minute updates: >>README.html >> md5sum: ./README.html: No such file or directory >> Makefile:479: recipe for target 'images' failed >> make: *** [images] Error 1 >> root@vm-stretch:/usr/share/debian-cd# > But the real reason for the stop here is the missing README.html > file. That should have been generated by the tools/add-bin-doc > script, and that's called each time a new temp disc tree is > started. Do you have logs going back further? Not at this time, but I can produce some tomorrow. At first attempt I didn't consider catching logs.
Bug#855174: catz: not found. Encountered while running make images.
Thanks a lot, that does the trick! Am 15.02.2017 um 00:30 schrieb James Clarke: > Control: tags -1 patch > > On Wed, Feb 15, 2017 at 12:17:03AM +0100, Josua Mayer wrote: >> I am attempting to reproduce creating installer isos using debian-cd. >> Following the README I set up a mirror using debmirror, and then ran the >> mentioned mkae steps up to make images, where I encountered an error message >> concerning a command called catz (never heard of it). >> I suspect debian-cd is missing a runtime dependency. > This is found in /usr/share/debian-cd/tools/catz. If you use build.sh, > it adds the directory to PATH, but not if you invoke make manually. The > attached patch fixes this like it is done elsewhere. > > Regards, > James > >> This is the short log leading to the error: >> root@vm-stretch:/usr/share/debian-cd# make images >> Looking in /opt/debmirror/dists/stretch/ /opt/debmirror/dists/stretch/ >> Using MD5 sums from Packages files: >> /opt/debmirror/dists/stretch/contrib/binary-arm64/Packages.xz >> /opt/debmirror/dists/stretch/contrib/binary-arm64/Packages.gz >> /opt/debmirror/dists/stretch/main/binary-arm64/Packages.xz >> /opt/debmirror/dists/stretch/main/binary-arm64/Packages.gz >> /opt/debmirror/dists/stretch/main/debian-installer/binary-arm64/Packages.xz >> /opt/debmirror/dists/stretch/main/debian-installer/binary-arm64/Packages.gz >> /opt/debmirror/dists/stretch/non-free/binary-arm64/Packages.xz >> /opt/debmirror/dists/stretch/non-free/binary-arm64/Packages.gz >> /opt/debmirror/dists/stretch/contrib/binary-arm64/Packages.xz >> /opt/debmirror/dists/stretch/contrib/binary-arm64/Packages.gz >> /opt/debmirror/dists/stretch/main/binary-arm64/Packages.xz >> /opt/debmirror/dists/stretch/main/binary-arm64/Packages.gz >> /opt/debmirror/dists/stretch/main/debian-installer/binary-arm64/Packages.xz >> /opt/debmirror/dists/stretch/main/debian-installer/binary-arm64/Packages.gz >> /opt/debmirror/dists/stretch/non-free/binary-arm64/Packages.xz >> /opt/debmirror/dists/stretch/non-free/binary-arm64/Packages.gz >> /usr/share/debian-cd/tools/grab_md5: 74: >> /usr/share/debian-cd/tools/grab_md5: catz: not found >> Generating the arm64 iso/jigdo images ... >> Last-minute updates: >> README.html >> md5sum: ./README.html: No such file or directory >> Makefile:479: recipe for target 'images' failed >> make: *** [images] Error 1 >> root@vm-stretch:/usr/share/debian-cd#
Bug#855174: catz: not found. Encountered while running make images.
Package: debian-cd Version: 3.1.19 Severity: important Dear Maintainer, I am attempting to reproduce creating installer isos using debian-cd. Following the README I set up a mirror using debmirror, and then ran the mentioned mkae steps up to make images, where I encountered an error message concerning a command called catz (never heard of it). I suspect debian-cd is missing a runtime dependency. This is the short log leading to the error: root@vm-stretch:/usr/share/debian-cd# make images Looking in /opt/debmirror/dists/stretch/ /opt/debmirror/dists/stretch/ Using MD5 sums from Packages files: /opt/debmirror/dists/stretch/contrib/binary-arm64/Packages.xz /opt/debmirror/dists/stretch/contrib/binary-arm64/Packages.gz /opt/debmirror/dists/stretch/main/binary-arm64/Packages.xz /opt/debmirror/dists/stretch/main/binary-arm64/Packages.gz /opt/debmirror/dists/stretch/main/debian-installer/binary-arm64/Packages.xz /opt/debmirror/dists/stretch/main/debian-installer/binary-arm64/Packages.gz /opt/debmirror/dists/stretch/non-free/binary-arm64/Packages.xz /opt/debmirror/dists/stretch/non-free/binary-arm64/Packages.gz /opt/debmirror/dists/stretch/contrib/binary-arm64/Packages.xz /opt/debmirror/dists/stretch/contrib/binary-arm64/Packages.gz /opt/debmirror/dists/stretch/main/binary-arm64/Packages.xz /opt/debmirror/dists/stretch/main/binary-arm64/Packages.gz /opt/debmirror/dists/stretch/main/debian-installer/binary-arm64/Packages.xz /opt/debmirror/dists/stretch/main/debian-installer/binary-arm64/Packages.gz /opt/debmirror/dists/stretch/non-free/binary-arm64/Packages.xz /opt/debmirror/dists/ stretch/non-free/binary-arm64/Packages.gz /usr/share/debian-cd/tools/grab_md5: 74: /usr/share/debian-cd/tools/grab_md5: catz: not found Generating the arm64 iso/jigdo images ... Last-minute updates: README.html md5sum: ./README.html: No such file or directory Makefile:479: recipe for target 'images' failed make: *** [images] Error 1 root@vm-stretch:/usr/share/debian-cd# -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing') Architecture: arm64 (aarch64) Kernel: Linux 4.9.0-1-arm64 (SMP w/3 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages debian-cd depends on: ii apt 1.4~rc1 ii bc1.06.95-9+b2 ii bzip2 1.0.6-8.1 ii cpp 4:6.3.0-1 ii curl 7.52.1-2 ii dctrl-tools [grep-dctrl] 2.24-2 ii dpkg-dev 1.18.22 ii genisoimage 9:1.1.11-3 pn libcompress-zlib-perl pn libdigest-md5-perl ii libdpkg-perl 1.18.22 ii libperl5.24 [libdigest-sha-perl] 5.24.1-1 ii lynx 2.8.9dev11-1 ii lynx-cur 2.8.9dev11-1 ii make 4.1-9 ii perl 5.24.1-1 ii tofrodos 1.7.13+ds-2 ii xorriso 1.4.6-1+b1 Versions of packages debian-cd recommends: ii dosfstools 4.1-1 ii hfsutils 3.2.6-13 ii isolinux 3:6.03+dfsg-14.1 ii mtools 4.0.18-2 ii netpbm 2:10.0-15.3+b1 ii syslinux-common 3:6.03+dfsg-14.1 pn syslinux-utils debian-cd suggests no packages. -- Configuration Files: /etc/debian-cd/conf.sh changed [not included] -- no debconf information
Bug#854606: ITP: libnfc-nci -- NFC stack for NCI based NFC Controllers by NXP
Am 08.02.2017 um 22:40 schrieb Ben Hutchings: > On Wed, 2017-02-08 at 11:28 -0500, Josua Mayer wrote: >> Package: wnpp >> Severity: wishlist >> Owner: Josua Mayer >> >> * Package name: libnfc-nci >> Version : 2.1 >> Upstream Author : NXP Semiconductors >> * URL : https://github.com/NXPNFCLinux/linux_libnfc-nci >> * License : Apache-2.0 >> Programming Lang: C >> Description : NFC stack for NCI based NFC Controllers by NXP >> >> This library provides an abstracted interface to NFC controllers in order >> to build applications that make use of nfc technology. >> Description to be revised! >> >> This library is provided by NFC to facilitate development of nfc enabled >> applications. >> It currently has support for the pn7120 and pn7150 chips. > This doesn't look suitable for Debian. Although it can be used with > GNU/Linux, it is clearly designed for Android. Hopefully this is not a showstopper. The library was originally designed for use with android, I see no reason why it can't be used on GNU/Linux. > Debian already > provides: > > - Linux kernel NFC stack and drivers, providing a socket interface > - libnfc, providing a generic interface to many (mostly USB-attached) > NFC controllers > > I don't see a lot of value in adding a third, vendor-specific stack > that's incompatible with anything else packaged in Debian. > > [...] >> However this library can be used with devices and nfc addon boards by other >> vendors providing they feature a supported nfc chip. >> Such it could benefit a much broader audience than just SR customers. > [...] > > Really? The documentation says it's specific to NXP PN5xx. I was referring to the host systems. As in . Anyone could connect one of the supported chips to anything. > > Ben. >
Bug#854606: ITP: libnfc-nci -- NFC stack for NCI based NFC Controllers by NXP
Package: wnpp Severity: wishlist Owner: Josua Mayer * Package name: libnfc-nci Version : 2.1 Upstream Author : NXP Semiconductors * URL : https://github.com/NXPNFCLinux/linux_libnfc-nci * License : Apache-2.0 Programming Lang: C Description : NFC stack for NCI based NFC Controllers by NXP This library provides an abstracted interface to NFC controllers in order to build applications that make use of nfc technology. Description to be revised! This library is provided by NFC to facilitate development of nfc enabled applications. It currently has support for the pn7120 and pn7150 chips. SolidRun Ltd is releasing a mikroBUS nfc board featuring the pn7120. The purpose of this package is to facilitate rapid development of applications utilizing this nfc module, by making it as easy as possible to use from Debian, or a debian-based rootfs. However this library can be used with devices and nfc addon boards by other vendors providing they feature a supported nfc chip. Such it could benefit a much broader audience than just SR customers. I volunteer to do the necessary packaging work, and handle any unexpected build failures in the future. I would like for this package to be maintained in a packaging team, however I have not been able to identify a single team that would fit perfectly. Is there a team that focuses on IoT, connectivity or low-level hardware development? And since I am not affiliated with Debian, I am also looking for a sponsor to take on this package.
Bug#847779: omap2-nand not auto-loaded on gta04
Package: linux-image-4.9.0-rc8-armmp-unsigned: src:linux Version: 4.9~rc8-1~exp1 Message-ID: <148146021121.356.16709761149479929183.reportbug@localhost> X-Mailer: reportbug 6.6.6 Date: Sun, 11 Dec 2016 12:43:31 + X-Debbugs-Cc: josua.maye...@gmail.com Severity: normal Dear Maintainer, While doing some more tests on the GTA04 board I found that the nand flash works just fine *after* manually loading omap2-nand. The kernel should know to load that module on its own, why it doesn't is still to be found. -- Package-specific info: ** Version: Linux version 4.9.0-rc8-armmp (debian-ker...@lists.debian.org) (gcc version 6.2.1 20161124 (Debian 6.2.1-5) ) #1 SMP Debian 4.9~rc8-1~exp1 (2016-12-05) ** Command line: console=ttyO2,115200n8 root=/dev/mmcblk0p1 rootfstype=ext2 rootwait ** Tainted: E (8192) * Unsigned module has been loaded. ** Kernel log: [ 11.949829] EXT4-fs error (device mmcblk0p1): ext4_mb_generate_buddy:758: group 6, block bitmap and bg descriptor inconsistent: 5945 vs 5947 free clusters [ 12.437194] EXT4-fs error (device mmcblk0p1): ext4_mb_generate_buddy:758: group 1, block bitmap and bg descriptor inconsistent: 26419 vs 26417 free clusters [ 12.556365] EXT4-fs error (device mmcblk0p1): ext4_mb_generate_buddy:758: group 2, block bitmap and bg descriptor inconsistent: 18241 vs 18243 free clusters [ 14.364379] 4805.dss supply vdda_video not found, using dummy regulator [ 14.476654] OMAP DSS rev 2.0 [ 14.514038] omapdss_dss 4805.dss: bound 48050400.dispc (ops dispc_component_ops [omapdss]) [ 14.592834] omapdss_dss 4805.dss: bound 48050c00.encoder (ops venc_component_ops [omapdss]) [ 14.893432] omap_ssi 48058000.ssi-controller: ssi controller 0 initialized (2 ports)! [ 14.959777] omap_ssi_port 4805a000.ssi-port: couldn't get cawake gpio (err=-2)! [ 15.034698] omap_ssi_port: probe of 4805a000.ssi-port failed with error -2 [ 15.130096] omap_ssi_port 4805b000.ssi-port: couldn't get cawake gpio (err=-2)! [ 15.185852] omap_ssi_port: probe of 4805b000.ssi-port failed with error -2 [ 15.261901] input: twl4030_pwrbutton as /devices/platform/6800.ocp/4807.i2c/i2c-0/0-0048/4807.i2c:twl@48:pwrbutton/input/input1 [ 15.357574] input: twl4030:vibrator as /devices/platform/6800.ocp/4807.i2c/i2c-0/0-0048/4807.i2c:twl@48:audio/twl4030-vibra/input/input2 [ 15.437683] 4807.i2c:twl@48:madc supply vusb3v1 not found, using dummy regulator [ 15.552154] twl4030_bci 4807.i2c:twl@48:bci: could not request vac iio channel [ 16.300292] Driver for 1-wire Dallas network protocol. [ 16.335479] input: TSC2007 Touchscreen as /devices/platform/6800.ocp/48072000.i2c/i2c-1/1-0048/input/input3 [ 16.499816] omap_hdq 480b2000.1w: OMAP HDQ Hardware Rev 0.5. Driver in Interrupt mode [ 16.508819] at24 1-0050: 8192 byte 24c64 EEPROM, writable, 1 bytes/write [ 16.631317] omap-sham 480c3000.sham: hw accel on OMAP rev 0.9 [ 17.195587] omap_wdt: OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec [ 17.245086] OF: graph: no port node found in /ocp@6800/isp@480bc000/ports [ 17.292327] 480bc000.isp supply vdd-csiphy1 not found, using dummy regulator [ 17.419189] 480bc000.isp supply vdd-csiphy2 not found, using dummy regulator [ 17.456146] backlight supply power not found, using dummy regulator [ 17.519348] omap3isp 480bc000.isp: Revision 15.0 found [ 17.547027] connector-analog-tv connector: failed to find video source [ 17.595306] iommu: Adding device 480bc000.isp to group 0 [ 17.671722] omap-iommu 480bd400.mmu: 480bd400.mmu: version 1.1 [ 17.753997] OF: ERROR: Bad of_node_put() on /ocp@6800/i2c@4807/twl@48/audio [ 17.762023] CPU: 0 PID: 230 Comm: systemd-udevd Tainted: G E 4.9.0-rc8-armmp #1 Debian 4.9~rc8-1~exp1 [ 17.772827] Hardware name: Generic OMAP36xx (Flattened Device Tree) [ 17.779418] [] (unwind_backtrace) from [] (show_stack+0x20/0x24) [ 17.787506] [] (show_stack) from [] (dump_stack+0x90/0xa4) [ 17.795074] [] (dump_stack) from [] (of_node_release+0xa0/0xa4) [ 17.803070] [] (of_node_release) from [] (kobject_put+0xc8/0x224) [ 17.811248] [] (kobject_put) from [] (of_node_put+0x24/0x28) [ 17.818969] [] (of_node_put) from [] (of_find_node_by_name+0x8c/0xdc) [ 17.827545] [] (of_find_node_by_name) from [] (twl4030_soc_probe+0x8c/0x438 [snd_soc_twl4030]) [ 17.838439] [] (twl4030_soc_probe [snd_soc_twl4030]) from [] (snd_soc_codec_drv_probe+0x28/0x2c [snd_soc_core]) [ 17.850860] [] (snd_soc_codec_drv_probe [snd_soc_core]) from [] (soc_probe_component+0x22c/0x374 [snd_soc_core]) [ 17.863342] [] (soc_probe_component [snd_soc_core]) from [] (snd_soc_register_card+0x4b8/0xe7c [snd_soc_core]) [ 17.875640] [] (snd_soc_register_card [snd_soc_core]) from [] (devm_snd_soc_register_card+0x48/0x80 [snd_soc_core]) [ 17.888397] [] (devm_snd_soc_register_card [snd_soc_core]) from [] (omap_twl4030_probe+0x130/0x1e4 [snd_soc_omap_twl4030]) [ 17.901763] [] (omap_twl4030_probe [snd_soc_omap_twl4030]
Bug#847775: solved in 4.9
With the current kernel in testing, namely 4.9.0-rc8-armmp, the omap-aes module is loading just fine. So when 4.9 hits testing, this bug should be done.
Bug#847775: promised serial console logfile
Forgot attaching the log to the report, so here goes nothing omap-aes.log Description: Binary data
Bug#847775: linux-image-4.8.0-2-armmp: kernel crashes while loading omap-aes module
Package: src:linux Version: 4.8.11-1 Severity: important Dear Maintainer, I booted latest debian unstable on my gta04 board and noticed that the system crashes as soon as omap-aes is loaded (which happens automatically unless blacklisted). The same crash also happens on 4.8.0-1, but I do not know when it started since I am only now bringing the armmp package to this board. Please find the serial log attached to this report. -- Package-specific info: ** Version: Linux version 4.8.0-2-armmp (debian-ker...@lists.debian.org) (gcc version 5.4.1 20161019 (Debian 5.4.1-3) ) #1 SMP Debian 4.8.11-1 (2016-12-02) ** Command line: console=ttyO2,115200n8 root=/dev/mmcblk0p1 rootfstype=ext2 rootwait ** Tainted: W (512) * Taint on warning. ** Kernel log: [ 17.647674] omap3isp 480bc000.isp: Entity type for entity OMAP3 ISP AF was not initialized! [ 17.739471] omap3isp 480bc000.isp: Entity type for entity OMAP3 ISP histogram was not initialized! [ 17.805541] iommu: Removing device 480bc000.isp from group 0 [ 17.852447] omap3isp: probe of 480bc000.isp failed with error -22 [ 17.865447] backlight supply power not found, using dummy regulator [ 18.646972] OF: ERROR: Bad of_node_put() on /ocp/i2c@4807/twl@48/audio [ 18.654174] CPU: 0 PID: 214 Comm: systemd-udevd Not tainted 4.8.0-2-armmp #1 Debian 4.8.11-1 [ 18.663024] Hardware name: Generic OMAP36xx (Flattened Device Tree) [ 18.669616] [] (unwind_backtrace) from [] (show_stack+0x20/0x24) [ 18.677734] [] (show_stack) from [] (dump_stack+0x98/0xac) [ 18.685302] [] (dump_stack) from [] (of_node_release+0xa0/0xa4) [ 18.693328] [] (of_node_release) from [] (kobject_put+0xe0/0x1ec) [ 18.701538] [] (kobject_put) from [] (of_node_put+0x24/0x28) [ 18.709289] [] (of_node_put) from [] (of_find_node_by_name+0x8c/0xdc) [ 18.717834] [] (of_find_node_by_name) from [] (twl4030_soc_probe+0x8c/0x424 [snd_soc_twl4030]) [ 18.728790] [] (twl4030_soc_probe [snd_soc_twl4030]) from [] (snd_soc_codec_drv_probe+0x28/0x2c [snd_soc_core]) [ 18.741210] [] (snd_soc_codec_drv_probe [snd_soc_core]) from [] (soc_probe_component+0x22c/0x370 [snd_soc_core]) [ 18.753723] [] (soc_probe_component [snd_soc_core]) from [] (snd_soc_register_card+0x4dc/0xe68 [snd_soc_core]) [ 18.766082] [] (snd_soc_register_card [snd_soc_core]) from [] (devm_snd_soc_register_card+0x48/0x80 [snd_soc_core]) [ 18.778839] [] (devm_snd_soc_register_card [snd_soc_core]) from [] (omap_twl4030_probe+0x138/0x1f0 [snd_soc_omap_twl4030]) [ 18.792266] [] (omap_twl4030_probe [snd_soc_omap_twl4030]) from [] (platform_drv_probe+0x5c/0xc0) [ 18.803375] [] (platform_drv_probe) from [] (driver_probe_device+0x238/0x43c) [ 18.812683] [] (driver_probe_device) from [] (__driver_attach+0x100/0x10c) [ 18.821685] [] (__driver_attach) from [] (bus_for_each_dev+0x8c/0xd0) [ 18.830291] [] (bus_for_each_dev) from [] (driver_attach+0x2c/0x30) [ 18.838653] [] (driver_attach) from [] (bus_add_driver+0x210/0x28c) [ 18.847045] [] (bus_add_driver) from [] (driver_register+0x88/0x108) [ 18.855529] [] (driver_register) from [] (__platform_driver_register+0x50/0x58) [ 18.864990] [] (__platform_driver_register) from [] (omap_twl4030_driver_init+0x1c/0x24 [snd_soc_omap_twl4030]) [ 18.877380] [] (omap_twl4030_driver_init [snd_soc_omap_twl4030]) from [] (do_one_initcall+0x60/0x1a4) [ 18.54] [] (do_one_initcall) from [] (do_init_module+0x74/0x1e4) [ 18.897338] [] (do_init_module) from [] (load_module+0x2064/0x2690) [ 18.905731] [] (load_module) from [] (SyS_finit_module+0xdc/0x110) [ 18.914062] [] (SyS_finit_module) from [] (__sys_trace_return+0x0/0x10) [ 18.932922] backlight supply power not found, using dummy regulator [ 18.965820] [ cut here ] [ 18.970703] WARNING: CPU: 0 PID: 6 at /build/linux-89XnL_/linux-4.8.11/include/linux/kref.h:46 kobject_get+0xac/0xb0 [ 18.981689] Modules linked in: joydev omapdrm(+) drm_kms_helper snd_soc_simple_card(+) snd_soc_simple_card_utils drm snd_soc_omap_twl4030(+) evdev connector_analog_tv pwm_bl cpufreq_dt snd_soc_omap_mcbsp omap3_isp snd_soc_omap w1_smem omap_wdt videobuf2_dma_contig snd_soc_twl4030 videobuf2_memops videobuf2_v4l2 omap_sham omap_hdq snd_soc_core videobuf2_core at24 wire nvmem_core tsc2007 snd_pcm_dmaengine spi_omap2_mcspi twl4030_wdt snd_pcm snd_timer snd twl4030_vibra soundcore twl4030_charger ff_memless twl4030_pwrbutton twl4030_madc pwm_twl pwm_twl_led industrialio omapdss omap_ssi hsi sunrpc ip_tables x_tables autofs4 ext4 crc16 jbd2 crc32c_generic fscrypto ecb mbcache phy_generic pbias_regulator ti_abb_regulator ohci_omap3 phy_twl4030_usb omap2430 omap_hsmmc phy_omap_control ehci_omap ohci_hcd [ 19.055664] musb_hdrc ehci_hcd udc_core usbcore usb_common [ 19.060150] CPU: 0 PID: 6 Comm: kworker/u2:0 Not tainted 4.8.0-2-armmp #1 Debian 4.8.11-1 [ 19.068695] Hardware name: Generic OMAP36xx (Flattened Device Tree) [ 19.075286] Workqueue: deferwq deferred_probe_work_func [ 19.080780] [] (unwind_b
Bug#847770: linux-image-4.8.0-1-armmp: tca-6507 driver missing - required to turn on wifi chip
Package: src:linux Version: 4.8.7-1 Severity: normal Tags: upstream Dear Maintainer, I started running the standard debian armmp kernel on the GTA04 and noticed that some driver are missing. For starters this bug is about wireless lan. The device features a Marvell 8686 module which is supported by the libertas driver. On this specific board, the wifi chip is switched on and off by a TCA 6507. Please consider enabling the driver for this chip in the armmp config: CONFIG_LEDS_TCA6507 -- Package-specific info: ** Version: Linux version 4.8.0-1-armmp (debian-ker...@lists.debian.org) (gcc version 5.4.1 20161019 (Debian 5.4.1-3) ) #1 SMP Debian 4.8.7-1 (2016-11-13) ** Command line: console=ttyO2,115200n8 root=/dev/mmcblk0p1 rootfstype=ext2 rootwait ** Tainted: W (512) * Taint on warning. ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information Hardware: Generic OMAP36xx (Flattened Device Tree) Revision: Device Tree model: Goldelico GTA04A4 ** Loaded modules: joydev omapdrm drm_kms_helper drm snd_soc_simple_card snd_soc_omap_twl4030 snd_soc_simple_card_utils evdev connector_analog_tv pwm_bl cpufreq_dt w1_smem snd_soc_omap_mcbsp omap3_isp snd_soc_omap snd_soc_twl4030 videobuf2_dma_contig omap_wdt videobuf2_memops videobuf2_v4l2 omap_hdq omap_sham videobuf2_core snd_soc_core wire at24 snd_pcm_dmaengine nvmem_core spi_omap2_mcspi tsc2007 snd_pcm twl4030_wdt snd_timer snd twl4030_charger twl4030_madc soundcore twl4030_pwrbutton twl4030_vibra ff_memless pwm_twl industrialio pwm_twl_led omapdss omap_ssi hsi sunrpc ip_tables x_tables autofs4 ext4 crc16 jbd2 crc32c_generic fscrypto ecb mbcache phy_generic pbias_regulator ti_abb_regulator omap2430 phy_omap_control ohci_omap3 phy_twl4030_usb omap_hsmmc ehci_omap musb_hdrc ohci_hcd udc_core ehci_hcd usbcore usb_common ** PCI devices: not available ** USB devices: not available -- 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/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-image-4.8.0-1-armmp depends on: ii initramfs-tools [linux-initramfs-tool] 0.125 ii kmod23-1 ii linux-base 4.5 Versions of packages linux-image-4.8.0-1-armmp recommends: ii firmware-linux-free 3.4 ii irqbalance 1.1.0-2 Versions of packages linux-image-4.8.0-1-armmp suggests: pn debian-kernel-handbook pn linux-doc-4.8 Versions of packages linux-image-4.8.0-1-armmp is related to: pn firmware-amd-graphics pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x pn firmware-brcm80211 pn firmware-cavium pn firmware-intel-sound pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv pn firmware-iwlwifi pn firmware-libertas pn firmware-linux-nonfree pn firmware-misc-nonfree pn firmware-myricom pn firmware-netxen pn firmware-qlogic pn firmware-realtek pn firmware-samsung pn firmware-siano pn firmware-ti-connectivity pn xen-hypervisor -- no debconf information
Bug#799939: chromium not available for armhf/arm64
Hi everyone, I just wanted to let you know that Riku`s latest patch is building and running on armhf perfectly. If I might ask you Riku, why are you disabling neon? Is it still not properly auto-detected at runtime? br Josua Mayer signature.asc Description: OpenPGP digital signature
Bug#815934: rfkill state not restored after reboot
Package: systemd Version: 215-17+deb8u3 Severity: normal Dear Maintainers, I noticed that rfkill state for both wifi and bluetooth is not restored on reboots on Hummingboard and Cubox-i. 1) Let me focus on wifi first: The behaviour I see is: it always starts up soft-blocked no matter if I unblocked it before rebooting, or not. In /var/lib/systemd/rfkill a state-file is created which shows 1 if wifi was blocked before last reboot, and 0 if it was unblocked. So I conclude that saving the state works fine. So I investigated the status of systemd-rfkill@rfkill0.service, and found that its reported to have exited without error. --> I guess that systemd tries to restore therfkill state too early, that is before the actual rfkill device / wifi device is properly initialized. (is this #809323 ?) There is still a ghost around here, as I got the state restored properly at least once now, without changing *anything* at all. 2) Bluetooth: There is no state-file created in /var/lib/systemd/rfkill for the bluetooth device. But I should add that this specific bluetooth chip requires manualy loading firmware from userspace, and only then it comes up. br Josua Mayer -- Package-specific info: -- System Information: Debian Release: 8.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: armhf (armv7l) Kernel: Linux 3.14.60-fslc-imx6-sr (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd depends on: ii acl 2.2.52-2 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-59 ii libacl1 2.2.52-2 ii libaudit1 1:2.4-1+b1 ii libblkid1 2.25.2-6 ii libc6 2.19-18+deb8u3 ii libcap2 1:2.24-8 ii libcap2-bin 1:2.24-8 ii libcryptsetup4 2:1.6.6-5 ii libgcrypt20 1.6.3-2+deb8u1 ii libkmod218-3 ii liblzma55.1.1alpha+20120614-2+b3 ii libpam0g1.1.8-3.1+deb8u1 ii libselinux1 2.3-2 ii libsystemd0 215-17+deb8u3 ii mount 2.25.2-6 ii sysv-rc 2.88dsf-59 ii udev215-17+deb8u3 ii util-linux 2.25.2-6 Versions of packages systemd recommends: ii dbus1.8.20-0+deb8u1 ii libpam-systemd 215-17+deb8u3 Versions of packages systemd suggests: pn systemd-ui -- no debconf information
Bug#799939: chromium: does not build / is not available for armhf
Hi everybody, How about at least getting the armhf part in somewhere? I tried to build this thing myself once more but I keep getting weird compile errors so I'd love to see it build on one of the debian buildbots. br Josua Mayer 2015-10-25 3:25 GMT+01:00 Michael Gilbert : > On Wed, Oct 21, 2015 at 9:21 AM, Riku Voipio wrote: >> Hi, >> >> Here's cleaned up patch against pkg-chromium git. I've now briefly tested the >> built chromium runs on armhf hw and a bit more extensively on arm64 hw. >> >> Michael, how would you feel about sending at test build at experimental? > > These changes are larger than I would like. Please upstream them > first, especially the assembly changes to openmax. > > Best wishes, > Mike
Bug#799939: chromium: does not build / is not available for armhf
Small update: Apparently those weird errors I was getting have been related to teh toolchain. The update to Jessie 8.2 (from 8.1) of my build-system made it go away. Instead, I am now presented with a new message: ../../media/base/audio_video_metadata_extractor.cc:116:17: error: use of undeclared identifier 'avcodec_get_name'; did you mean 'avcodec_get_type' I dont think this will be hard to work around (just wondering if it has surfaced when Riku tried to build). 2015-10-13 21:57 GMT+02:00 Josua Mayer : > I tried to build with Riku's patch, but I end up with a build error > that says error: '_Complex __int128' is invalid > I don't have a clue where that message comes from. Perhaps somebody > else can try building it on 32-bit arm hardware? > > I attached my logfile in case anybody wants to have a peek. > > 2015-10-13 15:43 GMT+02:00 Riku Voipio : >> On Tue, Oct 13, 2015 at 11:48:04AM +0300, Riku Voipio wrote: >>> Notice it needs a fix to objcopy/strip in binutils to handle stripping a > >>> 2GB file. >>> I'm still working on cleaning up that patch. >> >> The patch for binutils as attached to the upstream bug: >> >> https://sourceware.org/bugzilla/show_bug.cgi?id=19123 >> >> And resulted packages at: >> >> https://people.debian.org/~riku/chromium/ >> >> Riku
Bug#799939: chromium: does not build / is not available for armhf
Sadly I did not manage to produce any successful build yet.
Instead I am reliably running into this bug:
https://code.google.com/p/chromium/issues/detail?id=508897
So now I am retrying with this patchset:
https://codereview.chromium.org/1236863006/#ps160001
Hopefully it works; attaching the patch jsut in case somebody else wants
to give building a try.
--- a/chrome/browser/ui/views/profiles/profile_chooser_view.cc
+++ b/chrome/browser/ui/views/profiles/profile_chooser_view.cc
@@ -50,6 +50,7 @@
#include "ui/gfx/path.h"
#include "ui/gfx/skia_util.h"
#include "ui/gfx/text_elider.h"
+#include "ui/gfx/vector_icons_public.h"
#include "ui/native_theme/native_theme.h"
#include "ui/views/controls/button/blue_button.h"
#include "ui/views/controls/button/image_button.h"
--- a/chrome/chrome_browser_ui.gypi
+++ b/chrome/chrome_browser_ui.gypi
@@ -2921,6 +2921,9 @@
}],
['OS!="mac"', {
'sources': [ '<@(chrome_browser_ui_views_non_mac_sources)' ],
+ 'dependencies': [
+'../ui/gfx/gfx.gyp:gfx_vector_icons',
+ ],
'conditions': [
['enable_extensions==1', {
'sources': [ '<@(chrome_browser_ui_views_extensions_non_mac_sources)' ],
--- a/ui/gfx/gfx.gyp
+++ b/ui/gfx/gfx.gyp
@@ -408,41 +408,6 @@
'text_utils_skia.cc',
],
}, { # desktop platforms
- 'variables': {
-'vector_icons_cc_file': '<(INTERMEDIATE_DIR)/ui/gfx/vector_icons.cc',
-'vector_icons_public_h_file': '<(SHARED_INTERMEDIATE_DIR)/ui/gfx/vector_icons_public.h',
- },
- 'include_dirs': [
-'<(SHARED_INTERMEDIATE_DIR)',
- ],
- 'sources': [
-'<(vector_icons_cc_file)',
-'<(vector_icons_public_h_file)',
-
-'paint_vector_icon.cc',
-'paint_vector_icon.h',
-'vector_icons.h',
- ],
- 'actions': [
-{
- # GN version: //ui/gfx:aggregate_vector_icons
- 'action_name': 'aggregate_vector_icons',
- 'inputs': [
-'vector_icons/',
- ],
- 'outputs': [
-'<(vector_icons_cc_file)',
-'<(vector_icons_public_h_file)',
- ],
- 'action': [ 'python',
- 'vector_icons/aggregate_vector_icons.py',
- '--working_directory=vector_icons/',
- '--output_cc=<(vector_icons_cc_file)',
- '--output_h=<(vector_icons_public_h_file)',
- ],
- 'message': 'Aggregating vector resources.',
-},
- ],
}],
['use_x11==1', {
'dependencies': [
@@ -472,6 +437,55 @@
}],
],
},
+# Separate from gfx to limit the impact of the hard_dependency.
+{
+ 'target_name': 'gfx_vector_icons',
+ 'type': '<(component)',
+ 'dependencies': [
+'<(DEPTH)/base/base.gyp:base',
+'<(DEPTH)/skia/skia.gyp:skia',
+'gfx',
+'gfx_geometry',
+ ],
+ 'defines': [
+'GFX_IMPLEMENTATION',
+ ],
+ 'sources': [
+'paint_vector_icon.cc',
+'paint_vector_icon.h',
+'vector_icons.h',
+ ],
+ 'variables': {
+'vector_icons_cc_file': '<(INTERMEDIATE_DIR)/ui/gfx/vector_icons.cc',
+'vector_icons_public_h_file': '<(SHARED_INTERMEDIATE_DIR)/ui/gfx/vector_icons_public.h',
+ },
+ 'include_dirs': [
+'<(SHARED_INTERMEDIATE_DIR)',
+ ],
+ 'actions': [
+{
+ # GN version: //ui/gfx:aggregate_vector_icons
+ 'action_name': 'aggregate_vector_icons',
+ 'inputs': [
+'vector_icons/',
+ ],
+ 'outputs': [
+'<(vector_icons_cc_file)',
+'<(vector_icons_public_h_file)',
+ ],
+ 'action': [ 'python',
+ 'vector_icons/aggregate_vector_icons.py',
+ '--working_directory=vector_icons/',
+ '--output_cc=<(vector_icons_cc_file)',
+ '--output_h=<(vector_icons_public_h_file)',
+ ],
+ 'message': 'Aggregating vector resources.',
+ 'process_outputs_as_sources': 1,
+},
+ ],
+ # Export a hard dependency because of generated header files.
+ 'hard_dependency': 1,
+},
{
'target_name': 'gfx_test_support',
'type': 'static_library',
--- a/ui/views/controls/image_view.cc
+++ b/ui/views/controls/image_view.cc
@@ -11,6 +11,7 @@
#include "ui/gfx/canvas.h"
#include "ui/gfx/geometry/insets.h"
#include "ui/gfx/paint_vector_icon.h"
+#include "ui/gfx/vector_icons_public.h"
#include "ui/views/painter.h"
namespace views {
--- a/ui/views/controls/image_view.h
+++ b/ui/views/controls/image_view.h
@@ -7,11 +7,11 @@
#include "third_party/skia/include/c
Bug#799939: chromium: does not build / is not available for armhf
Please find the patch for armhf attached.
As of now it is still untested, as my buildbot is still busy building.
It should work for armel too, but I did not enable that in control yet.
diff -Naur chromium-browser-45.0.2454.85.orig/debian/control chromium-browser-45.0.2454.85/debian/control
--- chromium-browser-45.0.2454.85.orig/debian/control 2015-06-26 22:50:40.0 +0200
+++ chromium-browser-45.0.2454.85/debian/control 2015-09-24 16:07:46.665797443 +0200
@@ -86,7 +86,7 @@
Standards-Version: 3.9.6
Package: chromium
-Architecture: i386 amd64
+Architecture: i386 amd64 armhf
Depends:
${misc:Depends},
${shlibs:Depends},
@@ -105,7 +105,7 @@
This package contains the web browser component.
Package: chromium-dbg
-Architecture: i386 amd64
+Architecture: i386 amd64 armhf
Section: debug
Priority: extra
Depends:
@@ -149,7 +149,7 @@
elements of a web page at runtime (HTML, JavaScript, CSS, etc.).
Package: chromedriver
-Architecture: i386 amd64
+Architecture: i386 amd64 armhf
Depends:
${misc:Depends},
${shlibs:Depends},
diff -Naur chromium-browser-45.0.2454.85.orig/debian/rules chromium-browser-45.0.2454.85/debian/rules
--- chromium-browser-45.0.2454.85.orig/debian/rules 2015-04-19 20:30:39.0 +0200
+++ chromium-browser-45.0.2454.85/debian/rules 2015-09-24 16:22:44.81704 +0200
@@ -81,6 +81,15 @@
# can't use system nss since net/third_party/nss is heavily patched
# can't use system ots (open text *summarizer*) since that's not google's ots (open text *sanitizer*)
+# on armhf we need to tell gyp that this is a hardfloat system
+# chromium defaults to soft, so there is nothing to do when targeting armel
+ifeq (armhf,$(shell dpkg-architecture -qDEB_HOST_ARCH))
+defines+=arm_float_abi=hard
+endif
+
+# don't use a sysroot for build, ever. (when targeting arm, gyp default to yes)
+defines+=sysroot=
+
# make gyp a little more informative
options+=--check \
--debug=includes \
Bug#799939: chromium: does not build / is not available for armhf
Package: chromium Version: 45.0.2454.85-1~deb8u1 Severity: wishlist Dear Maintainer, While chromium itself works fine on ARM, as proven by the ChromeBooks, it is not available on Debian armhf (nor armel). There are 2 things required to get this working: a) add armhf to control for all those packages that are currently only built for i386 and amd64 b) enable a few special gyp defines in rules Both of these aren't hard, and I intend to provide a minimal patch for that as soon as I have a working build. Just reporting thos on a amd64 machine; but of course it affects armhf. -- System Information: Debian Release: 8.2 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.7-24-desktop (SMP w/4 CPU cores; PREEMPT) 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: unable to detect
