ChanServ changed the topic of #linux-rockchip to: Rockchip development discussion | IRC log http://irclog.whitequark.org/linux-rockchip | Community GH https://github.com/linux-rockchip | Rockchip GH https://github.com/rockchip-linux | ML https://groups.google.com/group/linux-rockchip
tllim has quit [Read error: Connection reset by peer]
vagrantc has quit [Quit: leaving]
tllim has joined #linux-rockchip
tllim has quit [Client Quit]
Kamikaze84 has joined #linux-rockchip
<Kamikaze84> Hi
<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?
kaspter has joined #linux-rockchip
nighty- has joined #linux-rockchip
kaspter has quit [Remote host closed the connection]
kaspter has joined #linux-rockchip
<Kamikaze84> Anyone have any tips?
<stdint> Kamikaze84, you can clean the original data
<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.
<stdint> Kamikaze84, well it is impossible, the mainline doesn't support the rockchip's partition table
cnxsoft has joined #linux-rockchip
<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?
<Kamikaze84> or is it that mainline doesn't have drivers for the eMMC itself?
<stdint> Kamikaze84, I said the mainline doesn't support the rockchip's partition table
<Kamikaze84> stdint: ok, then is there a guide for booting from SDCard or USB?
<stdint> You can boot from usb to erase the emmc http://opensource.rock-chips.com/wiki_Boot_option#Boot_from_eMMC
<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...
Kamikaze84 has quit [Quit: Page closed]
ayufan3 has quit [Remote host closed the connection]
ayufan has joined #linux-rockchip
lurchi_ is now known as lurchi__
<levd1> t/ip
kaspter has quit [Remote host closed the connection]
kaspter has joined #linux-rockchip
anarsoul has joined #linux-rockchip
lurchi_ has joined #linux-rockchip
lurchi__ has quit [Ping timeout: 255 seconds]
PoueT has quit [Ping timeout: 248 seconds]
vstehle has joined #linux-rockchip
kaspter has quit [Ping timeout: 256 seconds]
PoueT has joined #linux-rockchip
cnxsoft1 has joined #linux-rockchip
cnxsoft has quit [Ping timeout: 248 seconds]
cnxsoft1 is now known as cnxsoft
kaspter has joined #linux-rockchip
nighty- has quit [Quit: Disappears in a puff of smoke]
nighty- has joined #linux-rockchip
matthias_bgg has joined #linux-rockchip
ckeepax has quit [Ping timeout: 255 seconds]
ckeepax has joined #linux-rockchip
kloczek has quit [Quit: kloczek]
kloczek has joined #linux-rockchip
nighty- has quit [Quit: Disappears in a puff of smoke]
ayaka has quit [Ping timeout: 240 seconds]
ayaka has joined #linux-rockchip
kaspter1 has joined #linux-rockchip
kaspter has quit [Ping timeout: 240 seconds]
kaspter1 is now known as kaspter
chewitt has joined #linux-rockchip
nighty- has joined #linux-rockchip
nighty- has quit [Max SendQ exceeded]
nighty- has joined #linux-rockchip
matthias_bgg has quit [Ping timeout: 264 seconds]
ayaka has quit [Ping timeout: 276 seconds]
ayaka has joined #linux-rockchip
ayaka has quit [Quit: byte]
ayaka has joined #linux-rockchip
lurchi_ is now known as lurchi__
diego71_ is now known as diego71
afaerber has quit [Quit: Leaving]
cnxsoft has quit [Quit: cnxsoft]
afaerber has joined #linux-rockchip
kaspter has quit [Ping timeout: 240 seconds]
JohnDoe_71Rus has joined #linux-rockchip
matthias_bgg has joined #linux-rockchip
focus has joined #linux-rockchip
aalm| has joined #linux-rockchip
aalm has quit [Ping timeout: 264 seconds]
aalm| has quit [Client Quit]
aalm has joined #linux-rockchip
vagrantc has joined #linux-rockchip
mrfixit2001 has joined #linux-rockchip
anarsoul|2 has quit [Ping timeout: 260 seconds]
Easyfab has joined #linux-rockchip
mrfixit2001 has quit [Remote host closed the connection]
mrfixit2001 has joined #linux-rockchip
anarsoul|2 has joined #linux-rockchip
fischerm has quit [Quit: ZNC 1.6.2 - http://znc.in]
fischerm has joined #linux-rockchip
mrfixit2001 has quit [Quit: Mutter: www.mutterirc.com]
afaerber has quit [Quit: Leaving]
focus has quit [Quit: Leaving]
LargePrime has joined #linux-rockchip
JohnDoe_71Rus has quit [Quit: KVIrc 4.9.3 Aria http://www.kvirc.net/]
matthias_bgg has quit [Ping timeout: 240 seconds]
matthias_bgg has joined #linux-rockchip
Easyfab has quit [Quit: Leaving]
sphalerite has joined #linux-rockchip
<sphalerite> Hi folks. I've got quite a high rate of file corruption on the SD card on my C201. What might cause this?
<ramcq> does it happen with every SD card, or just one?
<ramcq> all SD cards die eventually, especially if you are using general-purpose filesystems like ext4 which just write/rewrite the same blocks
<ramcq> cheap SD cards die sooner
<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
<ramcq> if you see something happening bizzarely quickly with every SD card and maybe it's something more sinister like timing etc
<ramcq> I'd swap out the SD card and assume it's bad. it's the easiest and usually the correct explanation
<sphalerite> It's a sandisk extreme card, fairly new, so if it is the card it's not an old age thing
<ramcq> that can be more suspicious indeed
<ramcq> compatibility problems can happen
<sphalerite> I am indeed using ext4 on it, and there are 8 broken paths I've been able to detect
<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
<ramcq> actually the most informative is to try another of the same kind of SD card, in the C201
<ramcq> well, maybe all three
<ramcq> this card somewhere else can tell you: is it this card
<ramcq> different one in the C201 can tell you: is it the C201
<ramcq> another one of the same model in the C201 can tell you: is it the combination of this type with the C201
<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
<sphalerite> alright, I'll try that stuff tomorrow. Need to sleep for now, thanks for the advice!
lkcl has quit [Ping timeout: 260 seconds]
lkcl has joined #linux-rockchip
matthias_bgg has quit [Remote host closed the connection]
<vagrantc> i've occasionally had bad SD cards new; once got a pack of 5, 3 were bad.
<vagrantc> never buying kingston again
anarsoul has quit [Ping timeout: 264 seconds]
lurchi__ is now known as lurchi_
anarsoul has joined #linux-rockchip
anarsoul|2 has quit [Remote host closed the connection]
anarsoul|2 has joined #linux-rockchip