Re: d-i on Firefly-rk3288

[Diego Roversi <diegor@tiscali.it>]

On Mon, 12 Dec 2016 22:26:43 +0000
Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:

> On 12/12/16, Diego Roversi <diegor@tiscali.it> wrote:
> > On Mon, 12 Dec 2016 05:35:01 +0000
> > Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> >
> >> add console=ttyS2 to the kernel parameters, also earlyprintk is really
> >> helpful (but you have to have the right options compiled in the kernel
> >> to use it).
> >>
> >
> > Ok, I retried with this, and now the serial console works (thanks):
> 
>  great!  ok so now you have a feedback loop to monitor issues until success.
> 
> > Except the ethernet doesn't works. There are errors in dmesg:
> 
>  ok.  right.  so the next questions are: how flexible are you prepared
> to be to get this working, and do you *absolutely* need to use
> debian-installer to get this up-and-running?  i,e, do you have some
> hard requirement that *forces* you to use debian-installer or did you
> choose it because you'd heard it was the "normal" way to install
> debian?
> 

It's not a hard requirement, but I thing it would be nice to have a working debian-installer, so it will be more easy to install linux on the firefly.

And having a debian kernel means I don't have to upgrade manually the kernel, but I just do a "apt upgrade".

>  instead, i've resorted - reluctantly - to using either debootstrap or
> qemu-arm to carry out the root filesystem preparation... then copied
> that over.

I used debootstrap too, the first time with allwinner boards. 
 


> 
>  you could look for a debian-testing "weekly build" version of
> debian-installer (which should have a more recent kernel)
> 
It was just the latest I've found.

> 
>  you could ask around to see if someone else has a working (older or
> newer) debian-installer from debian/testing or sid that is known to
> work and they can provide a copy online for you.

I hoped to found someone on the mailing list, but no luck... Anyway, I think that il follow to path in parallel. I will open a bug, and try a custom kernel.

Thanks,
  Diego.

-- 
Diego Roversi <diegor@tiscali.it>