On Tue, 20 Dec 2016 21:12:50 +0100
Diego Roversi 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
On Sat, 10 Dec 2016 21:02:18 +
Luke Kenneth Casson Leighton wrote:
>
> wtf? a sub-16k loader basically a few hundred lines of code in total
> and they couldn't be bothered to make sure it has interoperable
> chainloading?? there'd better be a *really* good reason for that.
>
Small chanc
On Tue, 13 Dec 2016 00:29:05 +0100
Philip Hands wrote:
> As I said, I'm pretty sure you just need to produce kernel udebs, and
> dump them in the build/localudebs directory -- the thing that normally
> trips me up is forgetting to bump the version so that the local udeb is
> a higher version than
On Mon, 12 Dec 2016 22:26:43 +
Luke Kenneth Casson Leighton wrote:
> On 12/12/16, Diego Roversi wrote:
> > On Mon, 12 Dec 2016 05:35:01 +
> > Luke Kenneth Casson Leighton wrote:
> >
> >> add console=ttyS2 to the kernel parameters, also earlyprintk is really
> >> helpful (but you have to
On 2016-12-12 at 22:26:43 +, Luke Kenneth Casson Leighton wrote:
> 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?
> [...]
> the reason i ask is because the la
Luke Kenneth Casson Leighton writes:
> On 12/12/16, Diego Roversi wrote:
>> On Mon, 12 Dec 2016 05:35:01 +
>> Luke Kenneth Casson Leighton wrote:
>>
>>> add console=ttyS2 to the kernel parameters, also earlyprintk is really
>>> helpful (but you have to have the right options compiled in the
On 12/12/16, Diego Roversi wrote:
> On Mon, 12 Dec 2016 05:35:01 +
> Luke Kenneth Casson Leighton 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 wi
On Mon, 12 Dec 2016 05:35:01 +
Luke Kenneth Casson Leighton 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 (tha
... you're doing ok, btw - progressing really quickly. took me
several days to get this right and i had to bother a lot of people,
including valgrind, stdint, mmind0 and nvm on #linux-rockchip :)
l.
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).
you could really do with adding the options to boot.cmd then running
the (well-known?) mkimage command that turns them into boot.scr... ok
adapt
On Sun, 11 Dec 2016 08:21:12 +
Luke Kenneth Casson Leighton wrote:
> make sure you wipe out at least 150mb (so as to trash *all* the
> partitions) - i had some segfaults occur with the default 3.10 kernels
> by not erasing enough data. i only erased 10mb and it left
> half-set-up partitions
On 12/10/16, Diego Roversi wrote:
> On Fri, 09 Dec 2016 23:08:13 +0200
> Vagrant Cascadian wrote:
>
>> > U-Boot 2014.10-RK3288-02 (Nov 26 2014 - 09:28:44)
>>
>> This u-boot version is not coming from the SD card; probably from the
>> on-board eMMC. You may need to zero out of first few MB on the
On Fri, 09 Dec 2016 23:08:13 +0200
Vagrant Cascadian wrote:
> > U-Boot 2014.10-RK3288-02 (Nov 26 2014 - 09:28:44)
>
> This u-boot version is not coming from the SD card; probably from the
> on-board eMMC. You may need to zero out of first few MB on the
> eMMC. This will obviously render the OS o
On 12/10/16, Diego Roversi wrote:
> On Sat, 10 Dec 2016 04:42:19 +
> Luke Kenneth Casson Leighton wrote:
>
>
>> yep - this is the recommended method [for now] because the default
>> hardware boot order is something like eMMC microsd USB. the technical
>> reference manual is available, some
On Sat, 10 Dec 2016 04:42:19 +
Luke Kenneth Casson Leighton wrote:
> yep - this is the recommended method [for now] because the default
> hardware boot order is something like eMMC microsd USB. the technical
> reference manual is available, some references here
> http://rhombus-tech.net/r
On 12/9/16, Vagrant Cascadian wrote:
> On 2016-12-09, Diego Roversi wrote:
>> I'm trying to install debian stretch on a firefly-rk3288, using debian
>> installer. I downloaded the firmware from:
>>
>>
>> http://ftp.nl.debian.org/debian/dists/testing/main/installer-armhf/current/images/netboot/SD
On 2016-12-09, Diego Roversi wrote:
> I'm trying to install debian stretch on a firefly-rk3288, using debian
> installer. I downloaded the firmware from:
>
>
> http://ftp.nl.debian.org/debian/dists/testing/main/installer-armhf/current/images/netboot/SD-card-images/
>
> Then I wrote the inst
Hello,
I'm trying to install debian stretch on a firefly-rk3288, using debian
installer. I downloaded the firmware from:
http://ftp.nl.debian.org/debian/dists/testing/main/installer-armhf/current/images/netboot/SD-card-images/
Then I wrote the installer on a sd:
zcat firmware.Firefly-
18 matches
Mail list logo
