Re: d-i on Firefly-rk3288. Solved missing mmc and eth
- To: Diego Roversi <diegor@tiscali.it>
- Cc: Philip Hands <phil@hands.com>, Luke Kenneth Casson Leighton <lkcl@lkcl.net>, debian-arm@lists.debian.org
- Subject: Re: d-i on Firefly-rk3288. Solved missing mmc and eth
- From: Diego Roversi <diegor@tiscali.it>
- Date: Sun, 1 Jan 2017 20:34:23 +0100
- Message-id: <[🔎] 20170101203423.d62de02f799de10fad5a64b8@tiscali.it>
- In-reply-to: <20161220211250.b5c6efb2426884b5ef82114c@tiscali.it>
- References: <20161209213137.c46956d72a2e5bfe372867d3@tiscali.it> <87oa0kstdu.fsf@aikidev.net> <20161210222842.3cbdc13e8829687454373d82@tiscali.it> <CAPweEDyidHuK0fwqjE4DjSKVd09++1ifLA1oS+NJ8sD-JfR-2g@mail.gmail.com> <20161211201450.7b4d688acf00e898c58f90d1@tiscali.it> <CAPweEDzYbBMkMOH4TR0X66q2CxPXTNWHT11WW28gOY66h28Xjw@mail.gmail.com> <20161212211109.50d67a7564a050918918d852@tiscali.it> <CAPweEDx-8GioLX7Y7NNjntkxh10BpkmG9Z9C7jQV8tmn6Ygc3g@mail.gmail.com> <87y3zkn2v2.fsf@whist.hands.com> <20161220211250.b5c6efb2426884b5ef82114c@tiscali.it>
On Tue, 20 Dec 2016 21:12:50 +0100
Diego Roversi <diegor@tiscali.it> wrote:
>
> Ok, now I'm trying to create a d-i with custom kernel...
>
> > Here are some (slighted rotted) docs: https://wiki.debian.org/DebianInstaller/Modify/CustomKernel
>
> I've compiled my custom kernel, and created .deb file, using make-kpkg. But I don't find how to create the .udeb file. The page suggests to use kernel-wedge, but I don't really understand how.
>
> I've seen that there is a README for kernel-wedge, but it's quite criptic to me. Does it exists some example?
I couldn't build a new kernel for d-i with kernel-wedge, but I've modified the sd-card image, with a custom kernel. The installation went flawlessly. And the debian installed kernel worked fine (recognized mmc and ethernet), even if they are the same version (4.8.11).
Comparing the list of loaded modules (d-i kernel versus standard debian kernel), I've found out that phy regulator is missing, because there is a missing module in the initrd.gz of the d-i: i2c_rk3x.
--
Diego Roversi <diegor@tiscali.it>
Reply to: