On 06/15/2017 12:57 PM, Karsten Merker wrote: > Cyril Brulebois wrote: >> On Thu, Jun 15, 2017 at 10:43:18AM +0100, Ben Hutchings wrote: >>> Control: tag -1 moreinfo >>> >>> On Thu, 2017-06-15 at 08:34 +0200, Heinrich Schuchardt wrote: >>>> Package: debian-installer >>>> Version: stretch >>>> Severity: normal >>>> >>>> Dear Maintainer, >>>> >>>> the Lamobo R1 is an Arm system based on the Amlogic A20. >>>> The network interface of the A20 is connected to a switch. >>>> If the switch is not configured there is no external >>>> network access and subsequently a network install fails. >>>> >>>> On an installed system it is sufficient to have a line >>>> in /etc/modules: >>>> b53_mdio >>>> >>>> I suggest the following corrections to the installer: >>>> >>>> The initrd.img should include the b53_mdio module and its >>>> prerequisites b53_common and dsa_core plus aforementioned >>>> file /etc/modules. >>>> >>>> The installer should compare the content of >>>> /proc/device-tree/model >>>> to the string >>>> Lamobo R1 >>>> >>>> If this string is found, the file /etc/modules should be >>>> appended with b53_mdio on the installed system. >>> >>> Why is this necessary? It should load automatically. >> >> Because of missing i2c? Lamobo R1 is listed here: >> https://bugs.debian.org/864536#15 >> >> (Didn't check the recursive list of dependencies though.) > > If I understood the original submitter correctly, the problem > also exists in the installed system, not only in d-i. The > i2c-modules udeb issue (or other modules unavailable in the udebs > but available in the regular kernel deb) would explain problems > inside d-i, but not in the installed system. > > Heinrich, can you clarify on that? > > Regards, > Karsten >
Yes, the problems exists both in the installer and in an installed system. I set up the installed system via debootstrap: https://github.com/xypron/debian-image-lamobo-r1/commit/8fa1b7cb3a0cc2bfd44475d0c9972115ffb82e15 Best regards Heinrich Schuchardt
