<Somasis>
I'm on mainline 3.18.1, using the default kernel config as prescribed by the wiki's page on building mainline, and ethernet keeps dropping after a while. is there a patch to fix this or a workaround of any sort?
zombu2 has quit [Ping timeout: 244 seconds]
zombu2 has joined #radxa
<Somasis>
never mind, found it in irc logs
Astralix has joined #radxa
Astralix1 has quit [Ping timeout: 250 seconds]
<Somasis>
on a different topic, is there any way to upgrade the kernel from the system itself, without putting it into loader mode?
hipboi_ has joined #radxa
hipboi has quit [Ping timeout: 255 seconds]
<naobsd>
Somasis: you can write any image except loader
npcomp has quit [Ping timeout: 245 seconds]
npcomp has joined #radxa
<Somasis>
where would I write the boot.img to, then?
<Somasis>
I saw the stuff on the page about writing an image to the rock, and the section about doing it from the rock itself, but it sounds like that's assuming that you're using the default kernel, not mainline, and like it's for writing an image over the entire nand, not just the boot section
<naobsd>
NAND is not supported on mainline
<Somasis>
mm, alright, I wasn't sure if boot was stored on nand or something different. that makes sense.
<naobsd>
?
<naobsd>
it depends on where you flashed
<naobsd>
you said nand
<naobsd>
you can use sd (sd is only usable media for RR Lite)
<Somasis>
I have the boot parameter set to boot from my sd card
<naobsd>
Somasis: where did you write boot.img?
<Somasis>
to the nand
<naobsd>
Somasis: which media (nand or sd) are you using to boot? (I'm not asking about how did you modify parameter file)
<naobsd>
I see, nand
<Somasis>
boot is on nand, root is on sd
<naobsd>
then it's very clear where boot.img is stored
<Somasis>
the wiki is less clear :)
<naobsd>
I'm asking "what you did"
<naobsd>
"boot is on nand" is not true for people who uses sd
<naobsd>
not wiki issue
<Somasis>
maybe I'm not explaining this right
<Somasis>
what I did, was mkbootimg after compiling the kernel, and then I wrote it using upgrade_tool, to the boot partition of the nand
<Somasis>
the kernel is on the nand, that's correct
<Somasis>
the parameter is on the nand as well
<naobsd>
write new image to boot partition on nand from running system on RR is possible if "running system on RR" support NAND
<Somasis>
I understand that now
<naobsd>
write new image to boot (and any other partitions) ...
<Somasis>
okay
<naobsd>
same for SD
<naobsd>
... if "running system on RR" support SD
<Somasis>
alright then
CosmicDuck_ has quit [Remote host closed the connection]
CosmicDuck_ has joined #radxa
CosmicDuck has joined #radxa
CosmicDuck_ has quit [Ping timeout: 272 seconds]
CosmicDuck_ has joined #radxa
CosmicDuck has quit [Ping timeout: 272 seconds]
CosmicDuck has joined #radxa
CosmicDuck_ has quit [Ping timeout: 272 seconds]
CosmicDuck has quit [Remote host closed the connection]
CosmicDuck has joined #radxa
CosmicDuck has quit [Ping timeout: 272 seconds]
CosmicDuck has joined #radxa
CosmicDuck has quit [Read error: Connection reset by peer]