libv has quit [Ping timeout: 260 seconds]
afaerber_ has joined #linux-exynos
afaerber has quit [Ping timeout: 240 seconds]
libv has joined #linux-exynos
Wizzup has quit [Ping timeout: 252 seconds]
ssvb has quit [Ping timeout: 240 seconds]
ssvb has joined #linux-exynos
<swabbles> WarheadsSE: no, I am using the MicroSD slot.
<swabbles> And yes, they have, but none of them work :P.
<swabbles> Oh, and the links are different now btw.
<swabbles> But no kpart, and the updater shell scripts won't work on my Chromebook 2 because of a version mismatch.
<swabbles> So I am probably going to set up the chromiumos dev stuff when I am at the university (in the train atm, and the internet is crappy).
<swabbles> Then again, I am quite sure I am not supposed to use those shell scripts anyway.
Wizzup_ has joined #linux-exynos
afaerber_ has quit [Quit: Verlassend]
<Wizzup_> swabbles: yes, I noticed the links were different too
<Wizzup_> there's now pi firmware too
<Wizzup_> instead of 'pit' twice
<swabbles> I have tried the pi firmware was well, but I am not sure what I am supposed to do with the nv u-boot binary.
<Wizzup_> do you mean, where do 'place' it?
<swabbles> Like the shell scripts are probably meant to update the firmware on the Flash ROM (I am not mistaken).
<Wizzup_> to*
<swabbles> if*
<swabbles> Well, no, like you normally need a kpart file, not a binary.
* Wizzup_ will need to re-read stuffs
<swabbles> Because the binary is what you use to bundle it all together with the ec firmware and some other stuff.
<swabbles> Which is something you can't do without the System.map and BL1/BL2 files.
<swabbles> Unless I am misunderstanding something.
<swabbles> Hmm, let's see.
<swabbles> OK, I think I know how to create the kpart file now.
<swabbles> Going to test it out in a few.
<swabbles> Pff.
<Wizzup_> hm?
<WarheadsSE> now if only we could just build it in-tree with the cros_sdk ..
<swabbles> WarheadsSE: I have a working kpart now.
<WarheadsSE> !? WOO
<swabbles> For Peach Pi (I am not sure where to find the vboot keys for Peach Pit, otherwise I can create a kpart for that one as well).
<WarheadsSE> hmm
<WarheadsSE> swabbles: you will have to document how you got that.
<WarheadsSE> Since the the "official" documentation I have found does not result in usefulness, just yet
<Wizzup_> swabbles: \o/
<Wizzup_> I'll buy you a mate sometime soon ;-)
<Wizzup_> swabbles: I'd like to help with a good guide, might give the wiki a nice boost too
<WarheadsSE> I've got Arch users clamoring to get this puppy running
<WarheadsSE> Not to mention myself, of course
<Wizzup_> gentoo and arch users unite ;-)
<WarheadsSE> Anyone know of anyone heading to South East Linux Fest?
<WarheadsSE> NC, US, June 20-22
* Wizzup_ does not
* WarheadsSE shrug
<WarheadsSE> figured I would check
<WarheadsSE> swabbles: I currently have my uSD slot occupied by a UHS card so I have a working chroot I can build on
<swabbles> OK, I am back.
<WarheadsSE> wb then
<swabbles> Will put instructions up in a few, bit busy.
<WarheadsSE> np
Wizzup has joined #linux-exynos
afaerber has joined #linux-exynos
Wizzup_ is now known as Wizzup___
<WarheadsSE> progress
<swabbles> For pit, it should be the same (except everything should be named pit instead of pi).
<WarheadsSE> yeah
<swabbles> I have a working kpart for pi, but can't upload it to linux-exynos.org yet (I can upload it to another web server in the meanwhile).
<swabbles> And the keys are important (because when I did this on snow, u-boot rejected my nv u-boot image).
<swabbles> But yes, progress \o/
<WarheadsSE> interestingly enough
<WarheadsSE> My nv-uboot for snow is not rejected
<WarheadsSE> it just black screens
<WarheadsSE> (as should)
<swabbles> I might have the wrong keys on Snow, that could be a problem as well.
<swabbles> Because I am using whatever came with the vbutils package on Gentoo.
<swabbles> @snow
<swabbles> http://www.synkhronix.com/static/nv_uboot-peach-pi.kpart (will upload it to linux-exynos later today)
<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
luka has quit [*.net *.split]
luka has joined #linux-exynos
luka is now known as Guest89741
Guest89741 is now known as luka
luka has quit [Changing host]
luka has joined #linux-exynos
cmuller__ has quit [Ping timeout: 245 seconds]