Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#982270: installation-reports: Installing Debian Bullseye on Cubox-i4 - installer finds no ethernet
103 views
Skip to first unread message
Rick Thomas
Feb 7, 2021, 7:40:03 PM2/7/21
to
Package: installation-reports
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
-- Package-specific info:
Boot method: Followed the instruction in the README file
Image version:
https://d-i.debian.org/daily-images/armhf/daily/netboot/SD-card-images/
dated 2021-01-30 (also tried 2021-02-06)
Date: 2021-02-06
Machine: Cubox-i4P
Partitions: Didn't get that far in the installation
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot: [ok]
Detect network card: [failed] could not proceed
Overall install: [failed ]
Comments/Problems:
I downloaded the two-part image from [1] dated 2021-01-30 and tried to
install it on my Cubox-i4.
It booted fine but when it got to the "Detect network hardware" phase,
it failed and said:
> No Ethernet card was detected. If you know the name of the driver
> needed by your Ethernet card, you can select it from the list.
> Driver needed by your Ethernet card:
and gave a long list of available ethernet drivers, none of which seemed to be relevant.
I tried it again, this time with the components dated 2021-02-06.
I was hoping that the problem was transient and might have been fixed in
the intervening week, but I still got the same result: "No Ethernet card was detected."
Vagrant says:
> Pretty sure it is a kernel bug, since I can make it go away on a similar
> system by downgrading to linux 5.9.x. Please CC me on the report and
> I'll try to contribute what I can!
--
Log files attached to this report are from a successful Buster installation on the same hardware,
in hopes they might be some help...
Once you have filled out this report, mail it to sub...@bugs.debian.org.
==============================================
Installer lsb-release:
==============================================
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="10 (buster) - installer build 20190702+deb10u7"
X_INSTALLATION_MEDIUM=netboot
==============================================
Installer hardware-summary:
==============================================
uname -a: Linux cube 4.19.0-13-armmp #1 SMP Debian 4.19.160-2 (2020-11-28) armv7l GNU/Linux
usb-list:
usb-list: Bus 01 Device 01: EHCI Host Controller [1d6b:0002]
usb-list: Level 00 Parent 00 Port 00 Class 09(hub ) Subclass 00 Protocol 01
usb-list: Manufacturer: Linux 4.19.0-13-armmp ehci_hcd
usb-list: Interface 00: Class 09(hub ) Subclass 00 Protocol 00 Driver hub
usb-list:
usb-list: Bus 02 Device 01: EHCI Host Controller [1d6b:0002]
usb-list: Level 00 Parent 00 Port 00 Class 09(hub ) Subclass 00 Protocol 01
usb-list: Manufacturer: Linux 4.19.0-13-armmp ehci_hcd
usb-list: Interface 00: Class 09(hub ) Subclass 00 Protocol 00 Driver hub
lsmod: Module Size Used by
lsmod: dm_mod 122880 9
lsmod: md_mod 143360 0
lsmod: jfs 184320 0
lsmod: btrfs 1241088 0
lsmod: libcrc32c 16384 1 btrfs
lsmod: xor 16384 1 btrfs
lsmod: zstd_decompress 61440 1 btrfs
lsmod: zstd_compress 159744 1 btrfs
lsmod: xxhash 20480 2 zstd_compress,zstd_decompress
lsmod: zlib_deflate 28672 1 btrfs
lsmod: raid6_pq 98304 1 btrfs
lsmod: vfat 24576 0
lsmod: fat 73728 1 vfat
lsmod: ext4 618496 3
lsmod: crc16 16384 1 ext4
lsmod: mbcache 16384 1 ext4
lsmod: jbd2 102400 1 ext4
lsmod: crc32c_generic 16384 6
lsmod: fscrypto 28672 1 ext4
lsmod: ecb 16384 0
lsmod: brcmfmac 253952 0
lsmod: brcmutil 16384 1 brcmfmac
lsmod: cfg80211 548864 1 brcmfmac
lsmod: rfkill 28672 1 cfg80211
lsmod: usb_storage 53248 0
lsmod: sd_mod 49152 3
lsmod: ahci_imx 20480 2
lsmod: libahci_platform 20480 1 ahci_imx
lsmod: libahci 32768 2 libahci_platform,ahci_imx
lsmod: libata 208896 3 libahci_platform,libahci,ahci_imx
lsmod: scsi_mod 196608 3 sd_mod,usb_storage,libata
lsmod: sdhci_esdhc_imx 24576 0
lsmod: sdhci_pltfm 16384 1 sdhci_esdhc_imx
lsmod: sdhci 53248 2 sdhci_pltfm,sdhci_esdhc_imx
lsmod: ci_hdrc_imx 16384 0
lsmod: ci_hdrc 45056 1 ci_hdrc_imx
lsmod: ulpi 16384 1 ci_hdrc
lsmod: ehci_hcd 77824 1 ci_hdrc
lsmod: udc_core 36864 1 ci_hdrc
lsmod: usbcore 221184 4 usb_storage,ehci_hcd,brcmfmac,ci_hdrc
lsmod: usbmisc_imx 16384 1 ci_hdrc_imx
lsmod: imxdrm 28672 0
lsmod: anatop_regulator 16384 1
lsmod: phy_mxs_usb 16384 2
lsmod: dw_hdmi_imx 16384 0
lsmod: dw_hdmi 36864 1 dw_hdmi_imx
lsmod: imx_ipu_v3 94208 1 imxdrm
lsmod: cec 49152 1 dw_hdmi
lsmod: drm_kms_helper 147456 2 dw_hdmi,imxdrm
lsmod: drm 356352 5 imx_ipu_v3,dw_hdmi,dw_hdmi_imx,imxdrm,drm_kms_helper
lsmod: at803x 16384 1
df: Filesystem 1K-blocks Used Available Use% Mounted on
df: none 206276 56 206220 0% /run
df: devtmpfs 1010736 0 1010736 0% /dev
df: /dev/mapper/ncube--vg-root
df: 19092136 769744 17329524 4% /target
df: /dev/sda1 482922 31992 425996 7% /target/boot
df: /dev/mapper/ncube--vg-home
df: 459206776 74516 435736116 0% /target/home
df: /dev/mapper/ncube--vg-root
df: 19092136 769744 17329524 4% /dev/.static/dev
df: devtmpfs 1010736 0 1010736 0% /target/dev
free: total used free shared buff/cache available
free: Mem: 2062756 146340 976244 108440 940172 1809220
free: Swap: 999420 0 999420
/proc/cmdline: console=ttymxc0,115200
/proc/cpuinfo: processor : 0
/proc/cpuinfo: model name : ARMv7 Processor rev 10 (v7l)
/proc/cpuinfo: BogoMIPS : 6.00
/proc/cpuinfo: Features : half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpd32
/proc/cpuinfo: CPU implementer : 0x41
/proc/cpuinfo: CPU architecture: 7
/proc/cpuinfo: CPU variant : 0x2
/proc/cpuinfo: CPU part : 0xc09
/proc/cpuinfo: CPU revision : 10
/proc/cpuinfo:
/proc/cpuinfo: processor : 1
/proc/cpuinfo: model name : ARMv7 Processor rev 10 (v7l)
/proc/cpuinfo: BogoMIPS : 6.00
/proc/cpuinfo: Features : half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpd32
/proc/cpuinfo: CPU implementer : 0x41
/proc/cpuinfo: CPU architecture: 7
/proc/cpuinfo: CPU variant : 0x2
/proc/cpuinfo: CPU part : 0xc09
/proc/cpuinfo: CPU revision : 10
/proc/cpuinfo:
/proc/cpuinfo: processor : 2
/proc/cpuinfo: model name : ARMv7 Processor rev 10 (v7l)
/proc/cpuinfo: BogoMIPS : 6.00
/proc/cpuinfo: Features : half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpd32
/proc/cpuinfo: CPU implementer : 0x41
/proc/cpuinfo: CPU architecture: 7
/proc/cpuinfo: CPU variant : 0x2
/proc/cpuinfo: CPU part : 0xc09
/proc/cpuinfo: CPU revision : 10
/proc/cpuinfo:
/proc/cpuinfo: processor : 3
/proc/cpuinfo: model name : ARMv7 Processor rev 10 (v7l)
/proc/cpuinfo: BogoMIPS : 6.00
/proc/cpuinfo: Features : half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpd32
/proc/cpuinfo: CPU implementer : 0x41
/proc/cpuinfo: CPU architecture: 7
/proc/cpuinfo: CPU variant : 0x2
/proc/cpuinfo: CPU part : 0xc09
/proc/cpuinfo: CPU revision : 10
/proc/cpuinfo:
/proc/cpuinfo: Hardware : Freescale i.MX6 Quad/DualLite (Device Tree)
/proc/cpuinfo: Revision : 0000
/proc/cpuinfo: Serial : 0000000000000000
/proc/device-tree/model: SolidRun Cubox-i Dual/Quad�€/proc/iomem: 00110000-00111fff : dma-apbh@110000
/proc/iomem: 00900000-0093ffff : 900000.sram
/proc/iomem: 02020000-02023fff : serial@2020000
/proc/iomem: 0209c000-0209ffff : gpio@209c000
/proc/iomem: 020a0000-020a3fff : gpio@20a0000
/proc/iomem: 020a4000-020a7fff : gpio@20a4000
/proc/iomem: 020a8000-020abfff : gpio@20a8000
/proc/iomem: 020ac000-020affff : gpio@20ac000
/proc/iomem: 020b0000-020b3fff : gpio@20b0000
/proc/iomem: 020b4000-020b7fff : gpio@20b4000
/proc/iomem: 020c9000-020c9fff : usbphy@20c9000
/proc/iomem: 020ca000-020cafff : usbphy@20ca000
/proc/iomem: 020dc000-020dffff : gpc@20dc000
/proc/iomem: 020e0000-020e3fff : iomuxc@20e0000
/proc/iomem: 020ec000-020effff : sdma@20ec000
/proc/iomem: 02184000-021841ff : usb@2184000
/proc/iomem: 02184000-021841ff : usb@2184000
/proc/iomem: 02184200-021843ff : usb@2184200
/proc/iomem: 02184200-021843ff : usb@2184200
/proc/iomem: 02184800-021849ff : usbmisc@2184800
/proc/iomem: 02188000-0218bfff : ethernet@2188000
/proc/iomem: 02190000-02193fff : usdhc@2190000
/proc/iomem: 02194000-02197fff : usdhc@2194000
/proc/iomem: 021f0000-021f3fff : serial@21f0000
/proc/iomem: 02200000-02203fff : sata@2200000
/proc/iomem: 10000000-8fffffff : System RAM
/proc/iomem: 10208000-10ffffff : Kernel code
/proc/iomem: 11200000-11364d6f : Kernel data
/proc/interrupts: CPU0 CPU1 CPU2 CPU3
/proc/interrupts: 16: 183268 191266 201319 188753 GIC-0 29 Edge twd
/proc/interrupts: 17: 0 0 0 0 GPC 55 Level i.MX Timer Tick
/proc/interrupts: 19: 0 0 0 0 GPC 94 Level arm-pmu
/proc/interrupts: 26: 7762 0 0 0 GPC 26 Level 2020000.serial
/proc/interrupts: 50: 0 0 0 0 GPC 19 Level rtc alarm
/proc/interrupts: 56: 0 0 0 0 GPC 2 Level sdma
/proc/interrupts: 57: 1323 0 0 0 GPC 43 Level 2184000.usb
/proc/interrupts: 58: 1321 0 0 0 GPC 40 Level 2184200.usb
/proc/interrupts: 59: 101120 0 0 0 GPC 118 Level 2188000.ethernet
/proc/interrupts: 60: 0 0 0 0 GPC 119 Level 2188000.ethernet
/proc/interrupts: 61: 890 0 0 0 GPC 22 Level mmc0
/proc/interrupts: 62: 5576 0 0 0 GPC 23 Level mmc1
/proc/interrupts: 66: 0 0 0 0 GPC 29 Level 21f0000.serial
/proc/interrupts: 69: 100595 0 0 0 GPC 39 Level ahci-imx[2200000.sata]
/proc/interrupts: 77: 0 0 0 0 gpio-mxc 4 Edge 2194000.usdhc cd
/proc/interrupts: 145: 0 0 0 0 gpio-mxc 8 Edge Button 0
/proc/interrupts: IPI0: 0 0 0 0 CPU wakeup interrupts
/proc/interrupts: IPI1: 0 0 0 0 Timer broadcast interrupts
/proc/interrupts: IPI2: 96559 108944 112712 91367 Rescheduling interrupts
/proc/interrupts: IPI3: 34 14824 29232 32584 Function call interrupts
/proc/interrupts: IPI4: 0 0 0 0 CPU stop interrupts
/proc/interrupts: IPI5: 0 0 0 0 IRQ work interrupts
/proc/interrupts: IPI6: 0 0 0 0 completion interrupts
/proc/interrupts: Err: 0
/proc/meminfo: MemTotal: 2062756 kB
/proc/meminfo: MemFree: 976244 kB
/proc/meminfo: MemAvailable: 1809220 kB
/proc/meminfo: Buffers: 88644 kB
/proc/meminfo: Cached: 851528 kB
/proc/meminfo: SwapCached: 0 kB
/proc/meminfo: Active: 381924 kB
/proc/meminfo: Inactive: 595844 kB
/proc/meminfo: Active(anon): 104244 kB
/proc/meminfo: Inactive(anon): 41784 kB
/proc/meminfo: Active(file): 277680 kB
/proc/meminfo: Inactive(file): 554060 kB
/proc/meminfo: Unevictable: 0 kB
/proc/meminfo: Mlocked: 0 kB
/proc/meminfo: HighTotal: 1310720 kB
/proc/meminfo: HighFree: 405500 kB
/proc/meminfo: LowTotal: 752036 kB
/proc/meminfo: LowFree: 570744 kB
/proc/meminfo: SwapTotal: 999420 kB
/proc/meminfo: SwapFree: 999420 kB
/proc/meminfo: Dirty: 768 kB
/proc/meminfo: Writeback: 0 kB
/proc/meminfo: AnonPages: 37668 kB
/proc/meminfo: Mapped: 5296 kB
/proc/meminfo: Shmem: 108440 kB
/proc/meminfo: Slab: 79328 kB
/proc/meminfo: SReclaimable: 63628 kB
/proc/meminfo: SUnreclaim: 15700 kB
/proc/meminfo: KernelStack: 992 kB
/proc/meminfo: PageTables: 928 kB
/proc/meminfo: NFS_Unstable: 0 kB
/proc/meminfo: Bounce: 0 kB
/proc/meminfo: WritebackTmp: 0 kB
/proc/meminfo: CommitLimit: 2030796 kB
/proc/meminfo: Committed_AS: 161296 kB
/proc/meminfo: VmallocTotal: 245760 kB
/proc/meminfo: VmallocUsed: 0 kB
/proc/meminfo: VmallocChunk: 0 kB
/proc/meminfo: Percpu: 368 kB
/proc/meminfo: CmaTotal: 16384 kB
/proc/meminfo: CmaFree: 15900 kB
/proc/bus/input/devices: I: Bus=0019 Vendor=0001 Product=0001 Version=0100
/proc/bus/input/devices: N: Name="gpio-keys"
/proc/bus/input/devices: P: Phys=gpio-keys/input0
/proc/bus/input/devices: S: Sysfs=/devices/soc0/gpio-keys/input/input0
/proc/bus/input/devices: U: Uniq=
/proc/bus/input/devices: H: Handlers=
/proc/bus/input/devices: B: PROP=0
/proc/bus/input/devices: B: EV=3
/proc/bus/input/devices: B: KEY=1 0 0 0 0 0 0 0 0
/proc/bus/input/devices:
-- System Information:
Debian Release: 10.8
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: armhf (armv7l)
Kernel: Linux 4.19.0-14-armmp (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
-- Package-specific info:
Boot method: Followed the instruction in the README file
Image version:
https://d-i.debian.org/daily-images/armhf/daily/netboot/SD-card-images/
dated 2021-01-30 (also tried 2021-02-06)
Date: 2021-02-06
Machine: Cubox-i4P
Partitions: Didn't get that far in the installation
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot: [ok]
Detect network card: [failed] could not proceed
Overall install: [failed ]
Comments/Problems:
I downloaded the two-part image from [1] dated 2021-01-30 and tried to
install it on my Cubox-i4.
It booted fine but when it got to the "Detect network hardware" phase,
it failed and said:
> No Ethernet card was detected. If you know the name of the driver
> needed by your Ethernet card, you can select it from the list.
> Driver needed by your Ethernet card:
and gave a long list of available ethernet drivers, none of which seemed to be relevant.
I tried it again, this time with the components dated 2021-02-06.
I was hoping that the problem was transient and might have been fixed in
the intervening week, but I still got the same result: "No Ethernet card was detected."
Vagrant says:
> Pretty sure it is a kernel bug, since I can make it go away on a similar
> system by downgrading to linux 5.9.x. Please CC me on the report and
> I'll try to contribute what I can!
--
Log files attached to this report are from a successful Buster installation on the same hardware,
in hopes they might be some help...
Once you have filled out this report, mail it to sub...@bugs.debian.org.
==============================================
Installer lsb-release:
==============================================
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="10 (buster) - installer build 20190702+deb10u7"
X_INSTALLATION_MEDIUM=netboot
==============================================
Installer hardware-summary:
==============================================
uname -a: Linux cube 4.19.0-13-armmp #1 SMP Debian 4.19.160-2 (2020-11-28) armv7l GNU/Linux
usb-list:
usb-list: Bus 01 Device 01: EHCI Host Controller [1d6b:0002]
usb-list: Level 00 Parent 00 Port 00 Class 09(hub ) Subclass 00 Protocol 01
usb-list: Manufacturer: Linux 4.19.0-13-armmp ehci_hcd
usb-list: Interface 00: Class 09(hub ) Subclass 00 Protocol 00 Driver hub
usb-list:
usb-list: Bus 02 Device 01: EHCI Host Controller [1d6b:0002]
usb-list: Level 00 Parent 00 Port 00 Class 09(hub ) Subclass 00 Protocol 01
usb-list: Manufacturer: Linux 4.19.0-13-armmp ehci_hcd
usb-list: Interface 00: Class 09(hub ) Subclass 00 Protocol 00 Driver hub
lsmod: Module Size Used by
lsmod: dm_mod 122880 9
lsmod: md_mod 143360 0
lsmod: jfs 184320 0
lsmod: btrfs 1241088 0
lsmod: libcrc32c 16384 1 btrfs
lsmod: xor 16384 1 btrfs
lsmod: zstd_decompress 61440 1 btrfs
lsmod: zstd_compress 159744 1 btrfs
lsmod: xxhash 20480 2 zstd_compress,zstd_decompress
lsmod: zlib_deflate 28672 1 btrfs
lsmod: raid6_pq 98304 1 btrfs
lsmod: vfat 24576 0
lsmod: fat 73728 1 vfat
lsmod: ext4 618496 3
lsmod: crc16 16384 1 ext4
lsmod: mbcache 16384 1 ext4
lsmod: jbd2 102400 1 ext4
lsmod: crc32c_generic 16384 6
lsmod: fscrypto 28672 1 ext4
lsmod: ecb 16384 0
lsmod: brcmfmac 253952 0
lsmod: brcmutil 16384 1 brcmfmac
lsmod: cfg80211 548864 1 brcmfmac
lsmod: rfkill 28672 1 cfg80211
lsmod: usb_storage 53248 0
lsmod: sd_mod 49152 3
lsmod: ahci_imx 20480 2
lsmod: libahci_platform 20480 1 ahci_imx
lsmod: libahci 32768 2 libahci_platform,ahci_imx
lsmod: libata 208896 3 libahci_platform,libahci,ahci_imx
lsmod: scsi_mod 196608 3 sd_mod,usb_storage,libata
lsmod: sdhci_esdhc_imx 24576 0
lsmod: sdhci_pltfm 16384 1 sdhci_esdhc_imx
lsmod: sdhci 53248 2 sdhci_pltfm,sdhci_esdhc_imx
lsmod: ci_hdrc_imx 16384 0
lsmod: ci_hdrc 45056 1 ci_hdrc_imx
lsmod: ulpi 16384 1 ci_hdrc
lsmod: ehci_hcd 77824 1 ci_hdrc
lsmod: udc_core 36864 1 ci_hdrc
lsmod: usbcore 221184 4 usb_storage,ehci_hcd,brcmfmac,ci_hdrc
lsmod: usbmisc_imx 16384 1 ci_hdrc_imx
lsmod: imxdrm 28672 0
lsmod: anatop_regulator 16384 1
lsmod: phy_mxs_usb 16384 2
lsmod: dw_hdmi_imx 16384 0
lsmod: dw_hdmi 36864 1 dw_hdmi_imx
lsmod: imx_ipu_v3 94208 1 imxdrm
lsmod: cec 49152 1 dw_hdmi
lsmod: drm_kms_helper 147456 2 dw_hdmi,imxdrm
lsmod: drm 356352 5 imx_ipu_v3,dw_hdmi,dw_hdmi_imx,imxdrm,drm_kms_helper
lsmod: at803x 16384 1
df: Filesystem 1K-blocks Used Available Use% Mounted on
df: none 206276 56 206220 0% /run
df: devtmpfs 1010736 0 1010736 0% /dev
df: /dev/mapper/ncube--vg-root
df: 19092136 769744 17329524 4% /target
df: /dev/sda1 482922 31992 425996 7% /target/boot
df: /dev/mapper/ncube--vg-home
df: 459206776 74516 435736116 0% /target/home
df: /dev/mapper/ncube--vg-root
df: 19092136 769744 17329524 4% /dev/.static/dev
df: devtmpfs 1010736 0 1010736 0% /target/dev
free: total used free shared buff/cache available
free: Mem: 2062756 146340 976244 108440 940172 1809220
free: Swap: 999420 0 999420
/proc/cmdline: console=ttymxc0,115200
/proc/cpuinfo: processor : 0
/proc/cpuinfo: model name : ARMv7 Processor rev 10 (v7l)
/proc/cpuinfo: BogoMIPS : 6.00
/proc/cpuinfo: Features : half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpd32
/proc/cpuinfo: CPU implementer : 0x41
/proc/cpuinfo: CPU architecture: 7
/proc/cpuinfo: CPU variant : 0x2
/proc/cpuinfo: CPU part : 0xc09
/proc/cpuinfo: CPU revision : 10
/proc/cpuinfo:
/proc/cpuinfo: processor : 1
/proc/cpuinfo: model name : ARMv7 Processor rev 10 (v7l)
/proc/cpuinfo: BogoMIPS : 6.00
/proc/cpuinfo: Features : half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpd32
/proc/cpuinfo: CPU implementer : 0x41
/proc/cpuinfo: CPU architecture: 7
/proc/cpuinfo: CPU variant : 0x2
/proc/cpuinfo: CPU part : 0xc09
/proc/cpuinfo: CPU revision : 10
/proc/cpuinfo:
/proc/cpuinfo: processor : 2
/proc/cpuinfo: model name : ARMv7 Processor rev 10 (v7l)
/proc/cpuinfo: BogoMIPS : 6.00
/proc/cpuinfo: Features : half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpd32
/proc/cpuinfo: CPU implementer : 0x41
/proc/cpuinfo: CPU architecture: 7
/proc/cpuinfo: CPU variant : 0x2
/proc/cpuinfo: CPU part : 0xc09
/proc/cpuinfo: CPU revision : 10
/proc/cpuinfo:
/proc/cpuinfo: processor : 3
/proc/cpuinfo: model name : ARMv7 Processor rev 10 (v7l)
/proc/cpuinfo: BogoMIPS : 6.00
/proc/cpuinfo: Features : half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpd32
/proc/cpuinfo: CPU implementer : 0x41
/proc/cpuinfo: CPU architecture: 7
/proc/cpuinfo: CPU variant : 0x2
/proc/cpuinfo: CPU part : 0xc09
/proc/cpuinfo: CPU revision : 10
/proc/cpuinfo:
/proc/cpuinfo: Hardware : Freescale i.MX6 Quad/DualLite (Device Tree)
/proc/cpuinfo: Revision : 0000
/proc/cpuinfo: Serial : 0000000000000000
/proc/device-tree/model: SolidRun Cubox-i Dual/Quad�€/proc/iomem: 00110000-00111fff : dma-apbh@110000
/proc/iomem: 00900000-0093ffff : 900000.sram
/proc/iomem: 02020000-02023fff : serial@2020000
/proc/iomem: 0209c000-0209ffff : gpio@209c000
/proc/iomem: 020a0000-020a3fff : gpio@20a0000
/proc/iomem: 020a4000-020a7fff : gpio@20a4000
/proc/iomem: 020a8000-020abfff : gpio@20a8000
/proc/iomem: 020ac000-020affff : gpio@20ac000
/proc/iomem: 020b0000-020b3fff : gpio@20b0000
/proc/iomem: 020b4000-020b7fff : gpio@20b4000
/proc/iomem: 020c9000-020c9fff : usbphy@20c9000
/proc/iomem: 020ca000-020cafff : usbphy@20ca000
/proc/iomem: 020dc000-020dffff : gpc@20dc000
/proc/iomem: 020e0000-020e3fff : iomuxc@20e0000
/proc/iomem: 020ec000-020effff : sdma@20ec000
/proc/iomem: 02184000-021841ff : usb@2184000
/proc/iomem: 02184000-021841ff : usb@2184000
/proc/iomem: 02184200-021843ff : usb@2184200
/proc/iomem: 02184200-021843ff : usb@2184200
/proc/iomem: 02184800-021849ff : usbmisc@2184800
/proc/iomem: 02188000-0218bfff : ethernet@2188000
/proc/iomem: 02190000-02193fff : usdhc@2190000
/proc/iomem: 02194000-02197fff : usdhc@2194000
/proc/iomem: 021f0000-021f3fff : serial@21f0000
/proc/iomem: 02200000-02203fff : sata@2200000
/proc/iomem: 10000000-8fffffff : System RAM
/proc/iomem: 10208000-10ffffff : Kernel code
/proc/iomem: 11200000-11364d6f : Kernel data
/proc/interrupts: CPU0 CPU1 CPU2 CPU3
/proc/interrupts: 16: 183268 191266 201319 188753 GIC-0 29 Edge twd
/proc/interrupts: 17: 0 0 0 0 GPC 55 Level i.MX Timer Tick
/proc/interrupts: 19: 0 0 0 0 GPC 94 Level arm-pmu
/proc/interrupts: 26: 7762 0 0 0 GPC 26 Level 2020000.serial
/proc/interrupts: 50: 0 0 0 0 GPC 19 Level rtc alarm
/proc/interrupts: 56: 0 0 0 0 GPC 2 Level sdma
/proc/interrupts: 57: 1323 0 0 0 GPC 43 Level 2184000.usb
/proc/interrupts: 58: 1321 0 0 0 GPC 40 Level 2184200.usb
/proc/interrupts: 59: 101120 0 0 0 GPC 118 Level 2188000.ethernet
/proc/interrupts: 60: 0 0 0 0 GPC 119 Level 2188000.ethernet
/proc/interrupts: 61: 890 0 0 0 GPC 22 Level mmc0
/proc/interrupts: 62: 5576 0 0 0 GPC 23 Level mmc1
/proc/interrupts: 66: 0 0 0 0 GPC 29 Level 21f0000.serial
/proc/interrupts: 69: 100595 0 0 0 GPC 39 Level ahci-imx[2200000.sata]
/proc/interrupts: 77: 0 0 0 0 gpio-mxc 4 Edge 2194000.usdhc cd
/proc/interrupts: 145: 0 0 0 0 gpio-mxc 8 Edge Button 0
/proc/interrupts: IPI0: 0 0 0 0 CPU wakeup interrupts
/proc/interrupts: IPI1: 0 0 0 0 Timer broadcast interrupts
/proc/interrupts: IPI2: 96559 108944 112712 91367 Rescheduling interrupts
/proc/interrupts: IPI3: 34 14824 29232 32584 Function call interrupts
/proc/interrupts: IPI4: 0 0 0 0 CPU stop interrupts
/proc/interrupts: IPI5: 0 0 0 0 IRQ work interrupts
/proc/interrupts: IPI6: 0 0 0 0 completion interrupts
/proc/interrupts: Err: 0
/proc/meminfo: MemTotal: 2062756 kB
/proc/meminfo: MemFree: 976244 kB
/proc/meminfo: MemAvailable: 1809220 kB
/proc/meminfo: Buffers: 88644 kB
/proc/meminfo: Cached: 851528 kB
/proc/meminfo: SwapCached: 0 kB
/proc/meminfo: Active: 381924 kB
/proc/meminfo: Inactive: 595844 kB
/proc/meminfo: Active(anon): 104244 kB
/proc/meminfo: Inactive(anon): 41784 kB
/proc/meminfo: Active(file): 277680 kB
/proc/meminfo: Inactive(file): 554060 kB
/proc/meminfo: Unevictable: 0 kB
/proc/meminfo: Mlocked: 0 kB
/proc/meminfo: HighTotal: 1310720 kB
/proc/meminfo: HighFree: 405500 kB
/proc/meminfo: LowTotal: 752036 kB
/proc/meminfo: LowFree: 570744 kB
/proc/meminfo: SwapTotal: 999420 kB
/proc/meminfo: SwapFree: 999420 kB
/proc/meminfo: Dirty: 768 kB
/proc/meminfo: Writeback: 0 kB
/proc/meminfo: AnonPages: 37668 kB
/proc/meminfo: Mapped: 5296 kB
/proc/meminfo: Shmem: 108440 kB
/proc/meminfo: Slab: 79328 kB
/proc/meminfo: SReclaimable: 63628 kB
/proc/meminfo: SUnreclaim: 15700 kB
/proc/meminfo: KernelStack: 992 kB
/proc/meminfo: PageTables: 928 kB
/proc/meminfo: NFS_Unstable: 0 kB
/proc/meminfo: Bounce: 0 kB
/proc/meminfo: WritebackTmp: 0 kB
/proc/meminfo: CommitLimit: 2030796 kB
/proc/meminfo: Committed_AS: 161296 kB
/proc/meminfo: VmallocTotal: 245760 kB
/proc/meminfo: VmallocUsed: 0 kB
/proc/meminfo: VmallocChunk: 0 kB
/proc/meminfo: Percpu: 368 kB
/proc/meminfo: CmaTotal: 16384 kB
/proc/meminfo: CmaFree: 15900 kB
/proc/bus/input/devices: I: Bus=0019 Vendor=0001 Product=0001 Version=0100
/proc/bus/input/devices: N: Name="gpio-keys"
/proc/bus/input/devices: P: Phys=gpio-keys/input0
/proc/bus/input/devices: S: Sysfs=/devices/soc0/gpio-keys/input/input0
/proc/bus/input/devices: U: Uniq=
/proc/bus/input/devices: H: Handlers=
/proc/bus/input/devices: B: PROP=0
/proc/bus/input/devices: B: EV=3
/proc/bus/input/devices: B: KEY=1 0 0 0 0 0 0 0 0
/proc/bus/input/devices:
-- System Information:
Debian Release: 10.8
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: armhf (armv7l)
Kernel: Linux 4.19.0-14-armmp (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Vagrant Cascadian
Feb 11, 2021, 2:00:04 PM2/11/21
to
Control: reassign 982270 linux
Control: retitle 982270 linux: [armhf] several imx6 systems unable to detect ethernet
Control: found 982270 5.10.13-1
On 2021-02-07, Rick Thomas wrote:
> It booted fine but when it got to the "Detect network hardware" phase,
> it failed and said:
>
>> No Ethernet card was detected. If you know the name of the driver
>> needed by your Ethernet card, you can select it from the list.
>> Driver needed by your Ethernet card:
I can confirm this is an issue on hummingboard-i2ex, cubox-i4x4 and
wandboard quad, all of which are similar imx6 systems, and all of which
use the SoC's gigabit ethernet interface.
I've had better luck with linux 5.9.x and 4.19.x versions, although
possibly backported patches on the stable branches may also trigger
similar issues, just not consistantly. 5.10.x seems to consistantly
result in no working ethernet interface.
Marked as found in 5.10.13-1, but I believe this affects all 5.10.x
versions I have seen.
Possibly related to changes to the mdio interface infrastructure, but
this pretty much needs someone to able take the time to git bisect and
boot test the issue...
live well,
vagrant
> /proc/device-tree/model: SolidRun Cubox-i Dual/Quad/proc/iomem: 00110000-00111fff : dma-apbh@110000
Control: retitle 982270 linux: [armhf] several imx6 systems unable to detect ethernet
Control: found 982270 5.10.13-1
On 2021-02-07, Rick Thomas wrote:
> It booted fine but when it got to the "Detect network hardware" phase,
> it failed and said:
>
>> No Ethernet card was detected. If you know the name of the driver
>> needed by your Ethernet card, you can select it from the list.
>> Driver needed by your Ethernet card:
wandboard quad, all of which are similar imx6 systems, and all of which
use the SoC's gigabit ethernet interface.
I've had better luck with linux 5.9.x and 4.19.x versions, although
possibly backported patches on the stable branches may also trigger
similar issues, just not consistantly. 5.10.x seems to consistantly
result in no working ethernet interface.
Marked as found in 5.10.13-1, but I believe this affects all 5.10.x
versions I have seen.
Possibly related to changes to the mdio interface infrastructure, but
this pretty much needs someone to able take the time to git bisect and
boot test the issue...
live well,
vagrant
Vagrant Cascadian
May 17, 2021, 5:50:03 PM5/17/21
to
On 2021-02-11, Vagrant Cascadian wrote:
> Control: reassign 982270 linux
> Control: retitle 982270 linux: [armhf] several imx6 systems unable to detect ethernet
> Control: found 982270 5.10.13-1
>
> On 2021-02-07, Rick Thomas wrote:
>> It booted fine but when it got to the "Detect network hardware" phase,
>> it failed and said:
>>
>>> No Ethernet card was detected. If you know the name of the driver
>>> needed by your Ethernet card, you can select it from the list.
>>> Driver needed by your Ethernet card:
>
> I can confirm this is an issue on hummingboard-i2ex, cubox-i4x4 and
> wandboard quad, all of which are similar imx6 systems, and all of which
> use the SoC's gigabit ethernet interface.
>
> I've had better luck with linux 5.9.x and 4.19.x versions, although
> possibly backported patches on the stable branches may also trigger
> similar issues, just not consistantly. 5.10.x seems to consistantly
> result in no working ethernet interface.
>
> Marked as found in 5.10.13-1, but I believe this affects all 5.10.x
> versions I have seen.
>
> Possibly related to changes to the mdio interface infrastructure, but
> this pretty much needs someone to able take the time to git bisect and
> boot test the issue...
I'm also experiencing periodic issues on 4.19.x:
> Control: reassign 982270 linux
> Control: retitle 982270 linux: [armhf] several imx6 systems unable to detect ethernet
> Control: found 982270 5.10.13-1
>
> On 2021-02-07, Rick Thomas wrote:
>> It booted fine but when it got to the "Detect network hardware" phase,
>> it failed and said:
>>
>>> No Ethernet card was detected. If you know the name of the driver
>>> needed by your Ethernet card, you can select it from the list.
>>> Driver needed by your Ethernet card:
>
> I can confirm this is an issue on hummingboard-i2ex, cubox-i4x4 and
> wandboard quad, all of which are similar imx6 systems, and all of which
> use the SoC's gigabit ethernet interface.
>
> I've had better luck with linux 5.9.x and 4.19.x versions, although
> possibly backported patches on the stable branches may also trigger
> similar issues, just not consistantly. 5.10.x seems to consistantly
> result in no working ethernet interface.
>
> Marked as found in 5.10.13-1, but I believe this affects all 5.10.x
> versions I have seen.
>
> Possibly related to changes to the mdio interface infrastructure, but
> this pretty much needs someone to able take the time to git bisect and
> boot test the issue...
fec 2188000.ethernet eth0: MDIO read timeout
Not sure if that is related or a separate issue... there the ethernet
interface is present, but periodically becomes unusable, and bringing
the interface down and up again "fixes" the problem:
$ ip a
...
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
state DOWN group default qlen 1000
link/ether 12:4f:47:94:87:e1 brd ff:ff:ff:ff:ff:ff
inet 10.0.0.56/24 brd 10.0.0.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::104f:47ff:fe94:87e1/64 scope link
valid_lft forever preferred_lft forever
$ ping 10.0.0.1
PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data.
^C
--- 10.0.0.1 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
$ sudo ifdown eth0 ; sudo ifup eth0
$ ping 10.0.0.1
PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data.
From 10.0.0.56 icmp_seq=1 Destination Host Unreachable
64 bytes from 10.0.0.1: icmp_seq=2 ttl=64 time=0.265 ms
64 bytes from 10.0.0.1: icmp_seq=3 ttl=64 time=0.452 ms
^C
--- 10.0.0.1 ping statistics ---
3 packets transmitted, 2 received, +1 errors, 33.3333% packet loss,
time 2024ms
live well,
vagrant
Michael Jeanson
May 20, 2021, 4:10:03 PM5/20/21
to
This looks to be fixed in '5.10.38-1', at least on the single Wandboard
Quad (rev C1) I tested, networking works at boot. I'll update the kernel
on the boards that are CI workers and report back in a couple days if
the network is stable.
Quad (rev C1) I tested, networking works at boot. I'll update the kernel
on the boards that are CI workers and report back in a couple days if
the network is stable.
Rick Thomas
May 30, 2021, 8:00:04 PM5/30/21
to
I just tried this using the two-part uSD-card image at [1]. The problem is still present. Can anyone suggest which of the ethernet drivers to try in the long list it says is available?
Thanks!
Rick
[1] https://d-i.debian.org/daily-images/armhf/daily/netboot/SD-card-images/
date: 2021-05-30 00:09
> Attachments:
> * signature.asc
Thanks!
Rick
[1] https://d-i.debian.org/daily-images/armhf/daily/netboot/SD-card-images/
date: 2021-05-30 00:09
> * signature.asc
Rick Thomas
May 31, 2021, 1:00:04 AM5/31/21
to
I neglected to mention that my test machine here is a SolidRun CuBox i4Pro (2 GB RAM) model # I4P-300D .
What can I do to help debug this?
And again: Can anyone suggest which of the ethernet drivers to try in the long list it says is available?
Thanks,
Rick
What can I do to help debug this?
And again: Can anyone suggest which of the ethernet drivers to try in the long list it says is available?
Thanks,
Rick
Rick Thomas
Jun 1, 2021, 11:10:03 PM6/1/21
to
Hi!
Is there any estimate of when the assumed fix (linux/5.10.40-1) will show up in the installer at [1] ? I'd love to test it!
Failing that, is there some other place I can get an installer SDcard image with that fix?
Is there any estimate of when the assumed fix (linux/5.10.40-1) will show up in the installer at [1] ? I'd love to test it!
Failing that, is there some other place I can get an installer SDcard image with that fix?
Vagrant Cascadian
Jun 2, 2021, 2:10:04 AM6/2/21
to
On 2021-06-01, Rick Thomas wrote:
> Is there any estimate of when the assumed fix (linux/5.10.40-1) will
> show up in the installer at [1] ? I'd love to test it!
...
> Is there any estimate of when the assumed fix (linux/5.10.40-1) will
> show up in the installer at [1] ? I'd love to test it!
> [1] https://d-i.debian.org/daily-images/armhf/daily/netboot/SD-card-images/
It should already be there kernel version 5.10.38-1 had it, 5.10.40-1
should also have it.
I only tested it outside of debian-installer (e.g. upgrading kernel on
an already installed system), so it is also possible that more modules
are needed in one of the kernel udebs used by the installer, or that
you're experiencing a different issue from the one that was fixed. I'll
try to test debian-installer on Cubox-i4pro to see if I still have an
issue.
live well,
vagrant
Salvatore Bonaccorso
Jun 2, 2021, 11:40:04 AM6/2/21
to
Hi,
On Tue, Jun 01, 2021 at 07:46:34PM -0700, Rick Thomas wrote:
> Hi!
> Is there any estimate of when the assumed fix (linux/5.10.40-1) will
> show up in the installer at [1] ? I'd love to test it!
Should be "soon", cf. #988442.
Regards,
Salvatore
On Tue, Jun 01, 2021 at 07:46:34PM -0700, Rick Thomas wrote:
> Hi!
> Is there any estimate of when the assumed fix (linux/5.10.40-1) will
> show up in the installer at [1] ? I'd love to test it!
Regards,
Salvatore
Vagrant Cascadian
Jun 18, 2021, 7:00:05 PM6/18/21
to
Control: tags 982270 confirmed
Just tested d-i daily[1] on a Cubox-I4pro, and it definitely fails to
find the network card.
Same hardware, same kernel finds it just fine on an already installed
system... so this most likely means we need to add more modules to one
of the kernel .udebs.
[1] https://d-i.debian.org/daily-images/armhf/20210618-00:15/netboot/SD-card-images/
live well,
vagrant
find the network card.
Same hardware, same kernel finds it just fine on an already installed
system... so this most likely means we need to add more modules to one
of the kernel .udebs.
[1] https://d-i.debian.org/daily-images/armhf/20210618-00:15/netboot/SD-card-images/
live well,
vagrant
Vagrant Cascadian
Jun 18, 2021, 9:10:03 PM6/18/21
to
Control: tags 982270 pending
On 2021-06-18, Vagrant Cascadian wrote:
> On 2021-06-01, Vagrant Cascadian wrote:
>> On 2021-06-01, Rick Thomas wrote:
>>> Is there any estimate of when the assumed fix (linux/5.10.40-1) will
>>> show up in the installer at [1] ? I'd love to test it!
>> ...
>>> [1] https://d-i.debian.org/daily-images/armhf/daily/netboot/SD-card-images/
>>
>> It should already be there kernel version 5.10.38-1 had it, 5.10.40-1
>> should also have it.
>>
>> I only tested it outside of debian-installer (e.g. upgrading kernel on
>> an already installed system), so it is also possible that more modules
>> are needed in one of the kernel udebs used by the installer, or that
>> you're experiencing a different issue from the one that was fixed. I'll
>> try to test debian-installer on Cubox-i4pro to see if I still have an
>> issue.
>
> Just tested d-i daily[1] on a Cubox-I4pro, and it definitely fails to
> find the network card.
And same behavior on a wandboard quad...
> Same hardware, same kernel finds it just fine on an already installed
> system... so this most likely means we need to add more modules to one
> of the kernel .udebs.
What's more confusing, is the ethernet is CONFIG_FEC which is enabled as
a built-in, but still needs gpio-mxc to actually function!
Pushed a fix to git:
https://salsa.debian.org/kernel-team/linux/-/commit/f952b94621847732b3ed96a74babb89b6a1862f6
live well,
vagrant
On 2021-06-18, Vagrant Cascadian wrote:
> On 2021-06-01, Vagrant Cascadian wrote:
>> On 2021-06-01, Rick Thomas wrote:
>>> Is there any estimate of when the assumed fix (linux/5.10.40-1) will
>>> show up in the installer at [1] ? I'd love to test it!
>> ...
>>> [1] https://d-i.debian.org/daily-images/armhf/daily/netboot/SD-card-images/
>>
>> It should already be there kernel version 5.10.38-1 had it, 5.10.40-1
>> should also have it.
>>
>> I only tested it outside of debian-installer (e.g. upgrading kernel on
>> an already installed system), so it is also possible that more modules
>> are needed in one of the kernel udebs used by the installer, or that
>> you're experiencing a different issue from the one that was fixed. I'll
>> try to test debian-installer on Cubox-i4pro to see if I still have an
>> issue.
>
> Just tested d-i daily[1] on a Cubox-I4pro, and it definitely fails to
> find the network card.
> Same hardware, same kernel finds it just fine on an already installed
> system... so this most likely means we need to add more modules to one
> of the kernel .udebs.
a built-in, but still needs gpio-mxc to actually function!
Pushed a fix to git:
https://salsa.debian.org/kernel-team/linux/-/commit/f952b94621847732b3ed96a74babb89b6a1862f6
live well,
vagrant
Rick Thomas
Jun 21, 2021, 8:00:03 AM6/21/21
to
> Pushed a fix to git:
>
> https://salsa.debian.org/kernel-team/linux/-/commit/f952b94621847732b3ed96a74babb89b6a1862f6
Wow! Thanks! At least I now know I'm not crazy... Any idea how long it will be before the fix is in something I can download and install with?
>
> https://salsa.debian.org/kernel-team/linux/-/commit/f952b94621847732b3ed96a74babb89b6a1862f6
Enjoy!
Rick
0 new messages