<steev>
Wizzup: hm, so i'm building the kernel, and using exynos5422-peach-pi.dtb in the FIT image - is this incorrect? I'm getting some things about missing PPMU and it just sorta sits there
<Wizzup>
mainline? chromeos?
_hc has joined #linux-exynos
<_hc>
I'm running a Ubuntu 13.04 on a Samsung Chromebook for a while. I just upgraded to 14.04 and can't get the graphics to work. I did get the graphics working with 14.04 using the ARM development setup with 14.04. But I'd like to use Ubuntu's linux-exynos5 kernel. I installed that, and now I get a kernel panic on boot
<_hc>
there seems to be very little info about this on the web
<_hc>
I originally installed my first install using chrubuntu
<_hc>
mine is the Samsung Chromebook XE303C12
<Wizzup>
do you have a log of the panic?
<Wizzup>
(also: I have to go now - get some sleep)
<_hc>
hmm... how would I get that log?
<Wizzup>
or at least a hint of what goes wrong
<_hc>
I hit Ctrl-U on dev BIOS
<_hc>
screen goes black for a bit
<_hc>
then I get the panic
<_hc>
give me 10 seconds, I'll bring it up again
<_hc>
all I did to install the new kernel was `apt-get install linux-exynos5`
<_hc>
doh
<_hc>
it worked this time
<_hc>
strange
<_hc>
but it didn't fix my graphics problem.
<_hc>
the screen shows up perfectly for like 2 seconds, then goes black and there is just the mouse pointer
<_hc>
ah, it booted my old kernel 3.4.0-5-chromebook
<Wizzup>
last remark before I go to bed: check which x driver you have
<_hc>
I've tried both fbdev and armsoc
<_hc>
this is armsoc
<Wizzup>
and fbdev is no good?
<_hc>
it gets further
<_hc>
fbdev crashed for me
<Wizzup>
try fbturbo maybe
<_hc>
I gotta figure out how to select a kernel with this nv-uboot thing
<_hc>
it ain't grub ;)
<Wizzup>
well.. ext2load, etc
<Wizzup>
see the exynos wiki as well
<_hc>
yeah, looking at it now
<Wizzup>
afk
<Wizzup>
gl
<_hc>
sleep weel
<steev>
_hc: i use symlinks to switch between the various kernels
<afaerber>
javier__, cool, didn't know about that tree yet
<javier__>
afaerber: that branch is pretty recent, from yesterday afaik
<suihkulokki>
doesn't get much more bleeding edge
_hc has joined #linux-exynos
afaerber_ has joined #linux-exynos
afaerber has quit [Ping timeout: 260 seconds]
_hc has quit [Quit: Leaving.]
dlezcano has quit [Ping timeout: 240 seconds]
_hc has joined #linux-exynos
dlezcano has joined #linux-exynos
afaerber_ has quit [Quit: Verlassend]
sjoerd has quit [Ping timeout: 260 seconds]
afaerber has joined #linux-exynos
sjoerd has joined #linux-exynos
dlezcano has quit [Ping timeout: 260 seconds]
_hc1 has joined #linux-exynos
_hc has quit [Disconnected by services]
MrBIOS has joined #linux-exynos
_hc has joined #linux-exynos
_hc1 has quit [Ping timeout: 260 seconds]
<si1v3r>
Oooh... that tree looks fun.
<_hc>
anyone know anything about the linux-exynos5 kernel included in Ubuntu ARM port? it seems to be completely undocumented anywhere. I'm trying to use it on a Samsung Chromebook, since it seems like its meant to replace the linux-chromebook kernel that chrubuntu installed.
<Wizzup>
javier__: don't care too much about inefficiency
<Wizzup>
:)
si1v3r has quit [Ping timeout: 260 seconds]
<Wizzup>
javier__: right, so I'm probably more interested in HPM ;-)
si1v3r has joined #linux-exynos
plazmonii has quit [Ping timeout: 260 seconds]
plazmonii has joined #linux-exynos
tilmann has quit [Quit: leaving]
<si1v3r>
stupid ip changes
liquidAcid has quit [Quit: Leaving]
afaerber has quit [Quit: Verlassend]
jpantoja has joined #linux-exynos
afaerber has joined #linux-exynos
<steev>
si1v3r: if you specify 1 xf86-video-* package, it won't install all of them, just an fyi for your script (i see you install all, then remove all and modesetting)
<si1v3r>
It pulls in all no matter what I do. :/ easier to just go with it and remove the bad one later.
<si1v3r>
feel free to try to improve on it. It does make a perfectly decent end product.
<Wizzup>
si1v3r: why not set xorg.conf to load the proper driver?
<Wizzup>
(and thus ignore bad ones)
<si1v3r>
Doesn't work
<si1v3r>
I tried quite a few different ways and just went with a shit one that works.
<si1v3r>
I was never able to figure out why it broke things, but no matter what I did I couldn't get x to start with fbdev if the modesetting package was installed
dlezcano has joined #linux-exynos
<jpantoja>
si1v3r: which mainline kernel are you testing right now?
<si1v3r>
3.17rc1
<jpantoja>
si1v3r: have you tried without the simplefb u-boot?
<si1v3r>
not since 3.16
<si1v3r>
that never worked for me though.
<jpantoja>
si1v3r: I'm asking because I am under the impression that the exynos drm was not working correctly, and thus the simplefb was needed as workaround
<jpantoja>
but perhaps, if it is working (more or less) now, we may skip it
<jpantoja>
in fact, I would like to try upstream u-boot, but I don't feel like capable yet
<si1v3r>
chainload it from an sd card and you don't have to worry about breakage.
<jpantoja>
I was thinking more on the compilation, I have never compiled upstream u-boot
<jpantoja>
I have a broken snow to do testing
<steev>
si1v3r: i already have scripts that i use for kali (based on wheezy) - it works for us to specify xf86-video-fbdev, not sure why you're getting all of them :(
<si1v3r>
steev: alcohol may have been a factor
<steev>
heh
<si1v3r>
but, it works!
<si1v3r>
from arch. Not sure if it will work from chromeos. heh
<steev>
it should
<steev>
i mean, thats' what their kernel is based on
<steev>
i think, leming could correct me if i'm wrong
<si1v3r>
Uh.... heh......
<si1v3r>
I've got a lot of binary deps.
<si1v3r>
does cros come with parted?
<si1v3r>
bah. I should just restore my chromebook and start over. Then my scripts would actually be useful to people.
jpantoja has quit [Quit: Konversation terminated!]
<leming>
eh?
<si1v3r>
eh??
<leming>
kernels are all based on rainbows and butterflies
<Wizzup>
the more useful answer is: yes, they use chromeos
<Wizzup>
kernel
<leming>
only one real option at this point if you want things to work
<Wizzup>
well
<Wizzup>
I am not so sure about that
<Wizzup>
unless you specifically refer to mali
<leming>
mainline still has a bit of patching to go
* Wizzup
is going to try the 3.17-rc1 with patches soon
<si1v3r>
The samsung one?
<Wizzup>
ues
<Wizzup>
yes
<si1v3r>
Think wifi and sleep will work?
<Wizzup>
I guess, yeah
* Wizzup
mostly doesn't even use sleep
<Wizzup>
it lasts so long regardless
<Wizzup>
wifi - we'll see
<si1v3r>
I move around a lot. Sleep is good for that.
<si1v3r>
Anyway I'll give it a go
<Wizzup>
I sometimes forget to make it sleep and lose about 4% battery in 50 minutes
<Wizzup>
and it doesn't even get hot
<si1v3r>
there needs to be a chromebook circlejerk channel