<WarheadsSE>
Yeah, I think I am just using the pre-made nv-uboot for snow
<swabbles>
Nice, I found a kernel that may work :).
<swabbles>
I should have jotted the version stuff down earlier today when I was working on the Chromebook 2 (because I've set it to dev channel, but there is actually no reason to do that).
* swabbles
switches it back.
<swabbles>
I am currently running R37-5899.4.0.
<WarheadsSE>
I think other than being in dev mode, I am still on stable
<swabbles>
Yes, I am reverting it atm.
<swabbles>
I am currently looking at: kernel-next (R35-5712.B-chromeos-3.8).
<swabbles>
But I am not sure which one it is currently running on stable (other than 3.8.11).
<WarheadsSE>
hrm
<swabbles>
I reverted to stable R35-5712.61.0 (seems to match).
<swabbles>
Nice :).
<WarheadsSE>
Yeah, I can't tell what I am in, directly
<swabbles>
I am using "chrome://version" in the Google Chrome browser for that.
<swabbles>
Or cat /etc/lsb_release
<swabbles>
That's what most of the shell utils use.
<WarheadsSE>
mh, right, forgot that was there, been dealing too much with systemd and root vs initrd :P
* Wizzup___
hugs openrc
<WarheadsSE>
to each their own
<swabbles>
Hmm...
<swabbles>
I am trying to boot the kernel I just compiled, which works up to the point where I am simply getting a blank screen.
<Wizzup___>
wait for 5 minutes? :D
<tgall_foo>
swabbles, what board ?
<swabbles>
Samsung Chromebook 2 a.k.a. Peach Pi.
<swabbles>
Or well, the one I have is called Peach Pi.
<swabbles>
There also is Peach Pit.
<WarheadsSE>
he has the 13" w/ the "5800" 5422
<Wizzup___>
like all of us
<Wizzup___>
:D
<tgall_foo>
swabbles, ah! yeah that's the same that I was putting some time into last week
<tgall_foo>
yeah I've got the 13" as well
* WarheadsSE
calls me-fwee
<tgall_foo>
haven't gotten a successful boot with my own build kernel yet either
<swabbles>
I can try create a FIT image from my current Linux kernel, then see if u-boot wants to boot that.
<swabbles>
The pre-compiled u-boot image reminds me somewhat of the simplefb version.
<swabbles>
OK, that works and gets me a kernel trace.
<WarheadsSE>
progress
<tgall_foo>
good to hear
cmuller__ has joined #linux-exynos
Wizzup___ has quit [Quit: leaving]
<Wizzup>
So we made some progress, but we're still stuck at a trace
<Wizzup>
but that is likely due it it not finding a rootfs...
<Wizzup>
we can fix that with nv-uboot, probably..
<WarheadsSE>
IDK, haven't seen the trace
afaerber has quit [Quit: Verlassend]
<Wizzup>
I also tried a few different kernels but the most promising one didn't even ... compile
<WarheadsSE>
boo
<Wizzup>
It's kind of a mess with the chrome people
<Wizzup>
they have some old git repos that apparently are not to be used anymore
<Wizzup>
but they still have them
<Wizzup>
etc..
<Wizzup>
we'll get there
<swabbles>
You know what's the most amazing thing?
<swabbles>
They have many tools for the same job.
<swabbles>
And they are all equally poorly documented imo.
<Wizzup>
documentation lacks unfortunately
<Wizzup>
would be nice to find a friendly dev from their team maybe
<swabbles>
Well, I am trying something, because I have realised something on my path back home.
<swabbles>
If I am not mistaken they let you create an entire flash image with BL1, BL2, U-Boot, SPL, FDT, etc.
<swabbles>
To later just extract the U-Boot part, and just use that for nv u-boot.
<WarheadsSE>
makes sense, since those images are 4M