[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1013678: installation-reports: honeycomb lx2: partial success, network and issues with raid/lvm/grub



On Fri, Jun 24, 2022 at 02:10:44PM -0700, Vagrant Cascadian wrote:
> Package: installation-reports
> Severity: normal
> X-Debbugs-Cc: vagrant@debian.org
> 
> Boot method: network
> Image version: https://d-i.debian.org/daily-images/arm64/20220624-02:19/netboot/netboot.tar.gz
> Date: 2022-06-24 after breakfast but before lunch
> 
> Machine: Solidrun Honeycomb LX2
> Partitions:
> udev           devtmpfs  32513604       0  32513604   0% /dev
> tmpfs          tmpfs      6514616     744   6513872   1% /run
> /dev/sda3      ext4       9510080 1530260   7475144  17% /
> tmpfs          tmpfs     32573080       0  32573080   0% /dev/shm
> tmpfs          tmpfs         5120       0      5120   0% /run/lock
> /dev/sda1      vfat        389904    3536    386368   1% /boot/efi
> tmpfs          tmpfs      6514616       0   6514616   0% /run/user/1000
> 
> 
> Base System Installation Checklist:
> [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
> 
> Initial boot:           [O]
> Detect network card:    [E]
> Configure network:      [O]
> Detect media:           [O]
> Load installer modules: [O]
> Clock/timezone setup:   [O]
> User/password setup:    [O]
> Detect hard drives:     [O]
> Partition hard drives:  [O]
> Install base system:    [O]
> Install tasks:          [O]
> Install boot loader:    [E]
> Overall install:        [E]
> 
> Comments/Problems:
> 
> On-board ethernet is not detected in debian-installer or even once the
> system is installed. Worked around with a USB-ethernet adapter.
> 
> Boot loader would install successfully, but grub would not boot when I
> had a system with rootfs on lvm on raid1 (with degraded 1-disk
> array). I think this sort of configuration used to work, but it has
> been ages since I've tested. Will check another install if it works
> better with a not degraded array (e.g. raid1, two disks). Workaround
> was to use a plain partition with ext4 for rootfs.
> 
> FWIW, Same issues with bullseye's installer too, so at least it's
> not...  a regression? :)
> 
> 
> live well,
>   vagrant
> 
> -- Package-specific info:
> 
> ==============================================
> Installer lsb-release:
> ==============================================
> DISTRIB_ID=Debian
> DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
> DISTRIB_RELEASE="12 (bookworm) - installer build 20220624-02:01:58"
> X_INSTALLATION_MEDIUM=netboot
> 
> ==============================================
> Installer hardware-summary:
> ==============================================
> uname -a: Linux hclx2 5.18.0-2-arm64 #1 SMP Debian 5.18.5-1 (2022-06-16) aarch64 GNU/Linux
> lsmod: Module                  Size  Used by
> lsmod: fuse                  131072  0
> lsmod: nls_ascii              16384  1
> lsmod: nls_cp437              20480  1
> lsmod: efivarfs               20480  1
> lsmod: dm_mod                143360  6
> lsmod: dax                    36864  1 dm_mod
> lsmod: raid1                  57344  1
> lsmod: md_mod                167936  4 raid1
> lsmod: xfs                  1376256  0
> lsmod: jfs                   196608  0
> lsmod: btrfs                1466368  0
> lsmod: xor                    20480  1 btrfs
> lsmod: xor_neon               20480  1 xor
> lsmod: raid6_pq              106496  1 btrfs
> lsmod: zstd_compress         253952  1 btrfs
> lsmod: libcrc32c              16384  2 btrfs,xfs
> lsmod: vfat                   28672  1
> lsmod: fat                    81920  1 vfat
> lsmod: ext4                  761856  1
> lsmod: crc16                  16384  1 ext4
> lsmod: mbcache                24576  1 ext4
> lsmod: jbd2                  143360  1 ext4
> lsmod: crc32c_generic         16384  3
> lsmod: sd_mod                 57344  3
> lsmod: t10_pi                 20480  1 sd_mod
> lsmod: crc64_rocksoft         20480  1 t10_pi
> lsmod: crc64                  20480  1 crc64_rocksoft
> lsmod: crc_t10dif             20480  1 t10_pi
> lsmod: crct10dif_common       16384  1 crc_t10dif
> lsmod: ahci_qoriq             16384  0
> lsmod: ahci_platform          16384  3
> lsmod: libahci_platform       20480  2 ahci_platform,ahci_qoriq
> lsmod: libahci                40960  3 libahci_platform,ahci_platform,ahci_qoriq
> lsmod: libata                303104  4 libahci,libahci_platform,ahci_platform,ahci_qoriq
> lsmod: usb_storage            73728  0
> lsmod: scsi_mod              229376  3 sd_mod,usb_storage,libata
> lsmod: scsi_common            16384  3 scsi_mod,usb_storage,libata
> lsmod: cdc_ether              20480  0
> lsmod: usbnet                 45056  1 cdc_ether
> lsmod: r8152                 110592  0
> lsmod: mii                    20480  2 usbnet,r8152
> lsmod: xhci_plat_hcd          20480  0
> lsmod: xhci_hcd              253952  1 xhci_plat_hcd
> lsmod: at803x                 32768  0
> lsmod: xgmac_mdio             20480  0
> lsmod: acpi_mdio              16384  1 xgmac_mdio
> lsmod: mdio_devres            16384  1 xgmac_mdio
> lsmod: of_mdio                20480  2 mdio_devres,xgmac_mdio
> lsmod: usbcore               270336  6 xhci_hcd,usbnet,usb_storage,cdc_ether,xhci_plat_hcd,r8152
> lsmod: fixed_phy              16384  1 of_mdio
> lsmod: fwnode_mdio            20480  2 acpi_mdio,of_mdio
> lsmod: libphy                 98304  6 mdio_devres,acpi_mdio,fwnode_mdio,of_mdio,fixed_phy,at803x
> lsmod: usb_common             16384  3 xhci_hcd,usbcore,xhci_plat_hcd

Which of the many network ports?  The module list at least looks like
the modules the AR8035 10Gb copper port uses ought to be present.

The layerscape ports need to be configured for sure.  That stuff looks
weird and complicated.

What dtb is it using?

-- 
Len Sorensen


Reply to: