dlezcano has quit [Ping timeout: 264 seconds]
<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
<steev> Wizzup: whenever you're up, it's the uh, chromeos kernel, 3.8
<_hc> steev: do you have that documented somewhere?
<steev> No... It's a symlink, there isn't much to document there
<_hc> how do you tell nv-uboot about it?
<steev> U boot expects the file to be vmlinux.uimg so I symlink vmlinux.uimg.chromeos to it, or I point the symlink at vmlinux.uimg.mainline?
<_hc> I guess Ubuntu/chrubuntu is doing something different. There are kernels in /boot
<_hc> and ot vmlinux.uimg
<_hc> nd not vmlinux.uimg
_hc has quit [Quit: Leaving.]
MrBIOS has joined #linux-exynos
MrBIOS has quit [Quit: MrBIOS]
tilmann has joined #linux-exynos
<javier__> for those interested in having a working display on snow, peach pit/pi
<javier__> just noticed that I missed CONFIG_DRM_PTN3460 (used on snow) so I posted a v2
dne has joined #linux-exynos
dlezcano has joined #linux-exynos
<suihkulokki> does anyone have a git tree with all the patches on top of 3.17-rc1 one might want to have?
<javier__> suihkulokki: samsung folks have rebased their changes on top of 3.17-rc1
<suihkulokki> javier__: thanks
<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.
liquidAcid has joined #linux-exynos
<javier__> _hc: according to http://packages.ubuntu.com/source/utopic/linux-exynos5 is an 3.13 kernel so pretty old
<javier__> _hc: also you have to be sure that support for your specific device is present, most likely is not
<_hc> yeah, its a 3.13
<_hc> ok, so I should stick with the specific kernel for my device then
<javier__> _hc: dunno, I don't use ubuntu so I don't know what is in that kernel nor that linux-chromebook package
<javier__> _hc: my point is that is quite device specific so you have to figure out if supports your device
<_hc> javier__: the linux-chromebook package is a build of the ChromeOS kernel, 3.4.0, so even older
<javier__> I see, latest stable ChromeOS kernel for Samsung Chromebooks (snow, spring, peach, etc) is 3.8 though
<_hc> yeah, I've built that, but not in the same way as the linux-chromebook package
<_hc> so I broke my bootloader... :-(
<_hc> I'm wondering if its worth packaging the 3.8.11 kernel for debian/ubuntu
<_hc> or just waiting until more stuff gets included in the mainline kernel
<si1v3r> 3.4 vs 3.17rc1 isn't even an age question, it's support question.
<si1v3r> 3.4 is going to support all of the hardware. 3.17 or 13 or whatever will not.
<_hc> I started this whole thing because using a newer xorg breaks on the 3.4 kernel
<si1v3r> samsung chromebook?
<_hc> yeah
<si1v3r> do you have the package xserver-xorg-video-modesetting?
<_hc> tried fbdev and armsoc, and different issues with both
<_hc> xserver-xorg-video-armsoc-exynos5
<Wizzup> si1v3r: does that actually work for you?
<si1v3r> For some reason that one made the fbdev driver flip out on me, just from being presenty.
<Wizzup> that never worked for me (modesetting)
<Wizzup> I use fbturbo only
<si1v3r> Yeah my "fix" was to make sure the modesetting package is not installed.
<si1v3r> at all.
<Wizzup> although newer chromeos kernels backporte some stupid
<si1v3r> I tested with about 2 dozen fresh debian installes.
<Wizzup> backported some patch that breaks fbturbo
<Wizzup> and any fbdev
<si1v3r> (was time consuming...)
<si1v3r> Speaking of, anyone else have all their sd cards marked as read only in 3.16/3.17?
<_hc> anyone have an opinion about whether Debian or ubuntu is better supported on the samsung chromebook?
<si1v3r> I'd like to get back to testing custom install scripts but I'm a bit blocked by that.
<_hc> I'm a DD so I'm partial to Debian, but Ubuntu was so much easier when I first installed
<si1v3r> _hc: Both are equally bad.
<si1v3r> but debian is easier to untagle so you can fix it.
<si1v3r> I've got a good template for a debian system if you want it.
<si1v3r> Script is a work in progress, but if you are running chrubuntu already you can probably use it.
<_hc> yes please
<si1v3r> I made that work for me, no one else has seen it work.
<si1v3r> but it drops you to a debian install that just works.
<si1v3r> xorg trackpad fix, dpms fix, sleep hacks, alsa adjustments, even sets up a wifi config.
<si1v3r> I ran it over and over about 2 dozen times at least until I had a usable desktop on first boot.
<si1v3r> but you have to run it ON the chromebook, not on a pc, so that's a bit limiting.
<_hc> si1v3r: (you should use https:// for software downloads, whenever possible, like with https://commondatastorage.googleapis.com)
<si1v3r> I don't care if someone sniffs my work while you download it.
<si1v3r> You use https if you like though. :)
<_hc> but they can easily insert different code
<si1v3r> ONOES
<si1v3r> likes I says, you go ahead and use it, I'll save on bandwidth.
<si1v3r> I actually read it over and over when debugging, so I'm not too worried.
<Wizzup> javier__: with that kernel, any chance on big.little?
<javier__> Wizzup: big.LITTLE is working on that kernel afaik although you probably want to use the big.LITTLE switcher
<Wizzup> what is 'the switcher'? (sorry for silly questions)
<Wizzup> I'd just like all cores enabled
<si1v3r> I thought the idea was to switch between them but not use all of them?
<si1v3r> AFAIK, linux likes the procs to be the same.
<Wizzup> no, I think you should be able to use big.little at the same time
<Wizzup> Depending on the hw, possibly
<Wizzup> but I am very use that it should be possible to use all of them at the asme time.
<Wizzup> I think only one of the first odroids with big.little could not use all
<liquidAcid> you need HMP for that
<liquidAcid> which doesn't need to be available on your exynos soc
<Wizzup> what do you mean, 'need'? :)
<si1v3r> required for a serial console?
<liquidAcid> to use all cores at the same time
<Wizzup> Interesting
<javier__> Wizzup: you could use all cores but since are not the same then it can be inefficient
<javier__> Wizzup: the linux scheduler is not power-aware (yet)
<javier__> Wizzup: so the switcher as si1v3r allows to switch between the two clusters (A15 and A7)
<javier__> Wizzup: so basically there are too many assumptions that is ok to load balance your workload between all cores since all are the same
<javier__> which is not true anymore with big.LITTLE
<javier__> leaving for today, bye!
<Wizzup> back
<Wizzup> javier__: thanks!!
<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.
<si1v3r> Kinda proud of this stupid thing still
<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
<si1v3r> hehehehehehe
<Wizzup> I think you're at the right place
<Wizzup> ;)
<si1v3r> Bah... fucked up my uboot scripts.
si1v3r has quit [Ping timeout: 246 seconds]
si1v3r has joined #linux-exynos
MrBIOS has quit [Quit: MrBIOS]
dlezcano has quit [Ping timeout: 264 seconds]
dlezcano has joined #linux-exynos