00:59 <Kamikaze84> Hi

01:01 <Kamikaze84> I've purchased a Firefly RK3399 2G/16G. I would like to run a mainline linux kernel on it, but am having some trouble figuring out the necessary steps after kernel compilation. In particular, the existing eMMC seems to have an android style boot image in mmcblk1p13. Are there any steps/guides/howtos on turning a kernel Image into the appropriate format?

01:50 <Kamikaze84> Anyone have any tips?

01:56 <stdint> Kamikaze84, you can clean the original data

01:57 <Kamikaze84> stdint: Sorry I'm not sure exactly what you mean. Do you mean I can overwrite the existing image? If so, yes, I'm trying to do that, but only for the linux kernel on the eMMC at present.

01:58 <stdint> Kamikaze84, well it is impossible, the mainline doesn't support the rockchip's partition table

02:00 <Kamikaze84> stdint: so, mainline would start booting through the u-boot already on there, but then it wouldn't be able to find any rootfs as it doesn't understand the partition format of the eMMC? What format is it in? Is there no kernel config option to enable support for it?

02:00 <Kamikaze84> or is it that mainline doesn't have drivers for the eMMC itself?

02:00 <stdint> Kamikaze84, I said the mainline doesn't support the rockchip's partition table

02:02 <Kamikaze84> stdint: ok, then is there a guide for booting from SDCard or USB?

02:04 <stdint> You can boot from usb to erase the emmc http://opensource.rock-chips.com/wiki_Boot_option#Boot_from_eMMC

02:08 <Kamikaze84> stdint: Thanks for the help, that looks a lot more useful than the other guides I'd seen. I'll try and figure it out from there, if I get too stuck I might be back at some point asking for further help...

03:25 <levd1> t/ip

21:23 <sphalerite> Hi folks. I've got quite a high rate of file corruption on the SD card on my C201. What might cause this?

21:26 <ramcq> does it happen with every SD card, or just one?

21:26 <ramcq> all SD cards die eventually, especially if you are using general-purpose filesystems like ext4 which just write/rewrite the same blocks

21:26 <ramcq> cheap SD cards die sooner

21:26 <sphalerite> I don't know, it's the first time I've seen this issue, so I've only seen it with the one card so far

21:27 <ramcq> if you see something happening bizzarely quickly with every SD card and maybe it's something more sinister like timing etc

21:27 <ramcq> I'd swap out the SD card and assume it's bad. it's the easiest and usually the correct explanation

21:27 <sphalerite> It's a sandisk extreme card, fairly new, so if it is the card it's not an old age thing

21:28 <ramcq> that can be more suspicious indeed

21:28 <ramcq> compatibility problems can happen

21:29 <sphalerite> I am indeed using ext4 on it, and there are 8 broken paths I've been able to detect

21:31 <sphalerite> OK so to do: try this SD card in my big laptop to see if it's any better; and try a different one in the C201

21:36 <ramcq> actually the most informative is to try another of the same kind of SD card, in the C201

21:36 <ramcq> well, maybe all three

21:36 <ramcq> this card somewhere else can tell you: is it this card

21:37 <ramcq> different one in the C201 can tell you: is it the C201

21:37 <ramcq> another one of the same model in the C201 can tell you: is it the combination of this type with the C201

21:38 <ramcq> I think this card is most likely, this card together w/ C201 can happen sometimes, both are more likely than C201 is just bad

21:39 <sphalerite> alright, I'll try that stuff tomorrow. Need to sleep for now, thanks for the advice!

22:34 <vagrantc> i've occasionally had bad SD cards new; once got a pack of 5, 3 were bad.

22:34 <vagrantc> never buying kingston again