<Wizzup> Perhaps one of the people using mainline on their ODROID U3 can fill in/update http://linux-exynos.org/wiki/Hardkernel_ODROID-U3
prometheanfire has quit [Quit: leaving]
mkatic has joined #linux-exynos
<mkatic> hi al
<mkatic> anyone running chromeos-3.8.11 kernel on a XE303C12?
<mkatic> my setup is as follows:
<mkatic> nv-uboot running straight from spi flash
<mkatic> chromeos completely wiped out and replaced with ubuntu trusty
<mkatic> and i've been running chromeos 3.8.11 for a while now
<mkatic> got some problems with it, mainly random and quite common hangs that were probably related to wifi
<mkatic> also, it took forever for wifi to connect to any ap
<mkatic> yesterday i pulled from 3.8.11 repo and tried it out
<mkatic> seems like wifi is more stable, connects instantly
<mkatic> it also seems like it doesn't hang anymore
<mkatic> but i've got no sound, i used to have perfect sound
<mkatic> dmesg|grep max9 says:
<mkatic> [ 0.999253] max98090 7-0010: Failed to reset codec: -6
<mkatic> [ 1.004910] max98090 7-0010: Failed to read device revision: -1
<mkatic> [ 1.012449] max98090 7-0010: ASoC: failed to probe CODEC -1
<mkatic> [ 1.014350] daisy-snd-max98095 sound.8: ASoC: failed to instantiate card -1
<mkatic> [ 1.016253] daisy-snd-max98095 sound.8: snd_soc_register_card failed (-1)
<mkatic> [ 1.018153] daisy-snd-max98095: probe of sound.8 failed with error -1
<mkatic> [ 0.999253] max98090 7-0010: Failed to reset codec: -6
<mkatic> [ 1.004910] max98090 7-0010: Failed to read device revision: -1
<mkatic> [ 1.012449] max98090 7-0010: ASoC: failed to probe CODEC -1
<mkatic> [ 1.014350] daisy-snd-max98095 sound.8: ASoC: failed to instantiate card -1
<mkatic> [ 1.016253] daisy-snd-max98095 sound.8: snd_soc_register_card failed (-1)
<mkatic> [ 1.018153] daisy-snd-max98095: probe of sound.8 failed with error -1
<mkatic> oops, accidentaly pasted it twice
<mkatic> anyone has the same problem?
<mkatic> i did notice that there were some changes in the dtb files
<mkatic> dts files that is
<mkatic> seems like there are two snow revisions out there, rev4 and rev5?
<mkatic> each has a separate dts file now
<mkatic> hm
<mkatic> seems like the default exynos_config has alsa support completely disabled?
<Wizzup> hiya
<mkatic> greetings
<Wizzup> the wifi problems may be due to improper firmware
<Wizzup> Some work better than others, iirc
<Wizzup> I don't know what the error is that you're getting though, wrt sound
<Wizzup> I haven't booted my snow in a bit
<Wizzup> mostly using peach-pi
<mkatic> i have just now realised that alsa support is completely turned off in default exynos_defconfig
<mkatic> that's probably it
<Wizzup> I don't think you want to use exynos_defconfig on the chromeos kernel, let me check.
<Wizzup> uf, I thought we had a chromeos kernel guide on the wiki
<Wizzup> apparently not
<Wizzup> iirc there's a config for each define
<Wizzup> device*
<mkatic> is there a better config file for 3.8.11 than exynos_defconfig?
<Wizzup> I think so, uf. Let me see.
<mkatic> yeah, the default one won't compile
<Wizzup> You could also consider trying an mainline branch
<mkatic> i tried the latest one, but nv-uboot complains about something in the dtb file and it just resets
<mkatic> first i want to get 3.8.11 going as i feel that this is the most stable kernel for snow atm
<Wizzup> ok
<mkatic> oh, and i got another really weird problem that i think is not kernel related
<Wizzup> anyway, how did you build the previous kernel?
<mkatic> maybe a hardware fault? u-boot problem? i cant really say
<mkatic> basically, my XE303C12 turns on all by itself
<Wizzup> I see on my build server that I have branch chromeos-3.8 from https://chromium.googlesource.com/chromiumos/third_party/kernel-next.git ; but it's most likely outdated
<Wizzup> pressing buttons is probably enough, if it's in sleep at least
<Wizzup> I have to go again, I am going to try the dp-integ branch on snow this weekend (hopefully), so I'll let you know
<mkatic> i'll try dp-integ now and mainline again and report back
<Wizzup> you may also want to ping javier__ if you run into problems
<Wizzup> and keep some notes please, I want to make a wiki article about it soon
<mkatic> back to my "XE303C12 turns on by itself" problem
<mkatic> i do not put it to sleep, ever
<mkatic> i tried turning it off by holding the power button
<Wizzup> just opening the lid will boot the chromebook
<Wizzup> by design
<mkatic> i know that
<mkatic> but very often i would take it out of my bag and it is completely
<mkatic> empty
<mkatic> and sometimes i would open it and it would be already on, just idling in the uboot console
<Wizzup> what I noticed is that when I shut it down / put it to sleep, I had to make sure it was already closed
<Wizzup> otherwise the act of closing it would start it again
<mkatic> basically i made a workaround with an initscript
<Wizzup> also maybe your bag is too tight
<mkatic> if it is booting and the lid is closed, just turn it off
<mkatic> solved my problem
<Wizzup> I have to go
<mkatic> still, quite a stupid issue
<mkatic> ok, see you later
afaerber_ has joined #linux-exynos
afaerber__ has quit [Ping timeout: 255 seconds]
LanDi has joined #linux-exynos
prometheanfire has joined #linux-exynos
<mkatic> sound init problem solved by using *snow-rev4 dts
mkatic has quit [Quit: http://www.kiwiirc.com/ - A hand crafted IRC client]
mkatic has joined #linux-exynos
LanDi has quit [Ping timeout: 256 seconds]
mkatic has quit [Quit: http://www.kiwiirc.com/ - A hand crafted IRC client]
LanDi has joined #linux-exynos
mkatic has joined #linux-exynos
<mkatic> Wizzup: i tried running a kernel built from the collabora tree
<Wizzup> and?
<mkatic> u-boot won't even start it, just like the mainline kernel
<mkatic> ## Booting kernel from FIT Image at 42000000 ...
<mkatic> Using 'conf@1' configuration
<mkatic> Trying 'kernel@1' kernel subimage
<mkatic> Description: kernel
<mkatic> Type: Kernel Image (no loading done)
<mkatic> Compression: uncompressed
<mkatic> Data Start: 0x420000dc
<mkatic> Data Size: 3696248 Bytes = 3.5 MiB
<mkatic> Verifying Hash Integrity ... OK
<mkatic> ## Flattened Device Tree from FIT Image at 42000000
<mkatic> Using 'conf@1' configuration
<mkatic> Trying 'fdt@1' FDT blob subimage
<mkatic> i doubt that this has to do with the kernel
<mkatic> more like a problem with nv-uboot, or device tree
Wizzup has quit [Quit: brb]
<mkatic> oops
<mkatic> sorry, i pasted the wrong output
<mkatic> just a sec
<mkatic> here's the correct one: http://paste.debian.net/139069/
Wizzup has joined #linux-exynos
Wizzup has quit [Client Quit]
Wizzup has joined #linux-exynos
<Wizzup> [back]
LanDi has quit [Quit: fui !]
<Wizzup> mkatic: Well I definitely got some mainline kernel booting some time ago
<Wizzup> So it's definitely possible :)
<Wizzup> It's just a bit tedious I think :)
<mkatic> i'll have to check the nv-uboot source to see why it fails to load the dtb
<mkatic> to see what FDT_ERR_NOTFOUND exactly is
<mkatic> but i think i googled that a while ago
<mkatic> all i could find that there is possibly something missing in the device tree
<mkatic> but hey, i got the latest 3.8.11 chromeos going just fine
<mkatic> and it seems that this revision is more stable than whatever 3.8.11 revision i had before
<mkatic> it seems like i don't get random hangs with this revision
<mkatic> but i'll know for sure in a few days, too early to say anyhing now
<mkatic> the only thing missing now is opengl
<mkatic> gotta go, see you later
mkatic has quit [Quit: http://www.kiwiirc.com/ - A hand crafted IRC client]