[05:41] <AdamOutler> hello!
[05:42] <AdamOutler> I was wondering if there was a guide somewhere which can lead me through obtaining Ubuntu/linux sources and compiling it into a boot.img?
[05:42] <AdamOutler> and a bootable drive.
[05:42] <twb> For what hardware?
[05:42] <AdamOutler> I am using a blaze-tabet based piece of equipment.
[05:43] <AdamOutler> Texas Instruments OMAP 4430, blaze tablet.
[05:43] <twb> There are prebuilt omap4 images
[05:43] <AdamOutler> It's a production version though and I have to recompile sources.
[05:43] <twb> Why?
[05:43] <AdamOutler> because the drivers are different.
[05:44] <twb> Uh, so just compile the drivers
[05:45] <AdamOutler> well, there's a caviet...  it's a device based on blaze, it's actually a Nook Tablet...  I located a security hole and it will only work for boot.img files.  I need to use my own kernel on it.
[05:45] <AdamOutler> so, I'd like to find a guide on compiling a kernel from scratch and making a boot.img.
[05:46] <twb> I don't know what you mean by boot.img
[05:46] <AdamOutler> boot.img is Android standard..   basically it has to authenticate with the bootloader before it can be loaded.
[05:46] <twb> OK, a blobtools boot.img
[05:46] <twb> Er, I mean abootimg
[05:46] <AdamOutler> kinda.
[05:47] <AdamOutler> mkbootimg
[05:47] <twb> The tool I have seen that builds those is called "abootimg", apt-get install it
[05:47] <AdamOutler> I need some sort of guide though.
[05:48] <AdamOutler> ah ha!  abootimg is a good tool
[05:48] <twb> To build the kernel, get an environment that can compile for your target architecture, then do "make zImage" or "make deb-pkg" to taste
[05:48] <twb> It would be a good idea to start with the stock ubuntu kernel and its omap4 .config
[05:48] <AdamOutler> twb,  and abootimg handles zImage files?
[05:48] <twb> AdamOutler: I don't remember offhand
[05:48] <AdamOutler> ok, twb, what is a uImage?
[05:49] <twb> Different flavour of zImage, it's for u-boot
[05:49] <twb> If you are using the android bootloader (which takes abootimg boot.img files), then you don't want uImage.
[05:50] <AdamOutler> I have uImage and uInitrd..  they need to get into a boot img...  I found a program that converts uImage to zImage, and now I need to convert uInitrd to initrd I guess.
[05:50] <twb> You probably want to prepare an Ubuntu rootfs, generate a kernel .deb, install the latter into the former, then run abootimg on the resulting kernel and ramdisk from /boot
[05:50] <twb> AdamOutler: if you already have a uImage why are you asking about kernel compilation?
[05:50] <AdamOutler> twb.  you're opening my eyes.
[05:51] <AdamOutler> :)
[05:51] <AdamOutler> twb.. I've been compiling non-stop for a few days,  I have several test images to work with in various formats.
[05:51] <twb> What hardware are you compiling on?
[05:51] <AdamOutler> stupid boot.img is tearing me up.
[05:52] <AdamOutler> twb, I'm cross-compiling from a i5 quad core for ARM arch
[05:52] <twb> That should compile in deciminutes, not days
[05:52] <AdamOutler> twb, it's operator error... this is why I asked for a guide when I came in ;)
[05:52] <twb> Try turning off the debugging symbols
[05:53] <twb> AdamOutler: it would be a good idea for you to get comfortable building normal x86 kernels first
[05:53] <AdamOutler> twb I am comfortable building 86_64
[05:53] <twb> AdamOutler: that way you will have a solid foundation when you try to get a handle on the arm randomness
[05:54] <AdamOutler> twb, I've been operating several linux boxes in my home for years.  I've compiled several for my media center alone.
[05:55] <AdamOutler> I'd just like some knoledge about all these formats and everything..  On my Samsung, I could just flash a zImage to my device and I was done..  This boot.img format is crazy.
[05:55] <twb> IIUC samsungs use u-boot and are generally on the "less stupid" side of ARM'd spectrum of idiocy
[05:55] <AdamOutler> zImage has Ramdisk+kernel.   For some reason Boot.img has zImage + ramdisk, + android headers?
[05:56] <twb> zImage does not normally include the ramdisk
[05:56] <twb> The kernel has support for tacking a ramdisk onto itself -- this should work in both cases
[05:56] <twb> Normally the ramdisk is a separate file.
[05:57] <AdamOutler> ok, and what is the point of a ramdisk when the files are already on the root of the storage medium?
[05:57] <twb> To generate a boot.img using abootimg, you need a kernel, a ramdisk (optional), and a config file that basically consists of the options passed at the boot: prompt
[05:57] <twb> AdamOutler: the primary reason to use a ramdisk, is so you can build a small portable kernel and then include device-specific drivers to *get to* the root fliesystem, in the ramdisk
[05:57] <twb> That is how e.g. Ubuntu x86 servers all share the same kernel despite having different SATA controllers and video cards
[05:58] <twb> You can also put various other clever code in the ramdisk, e.g. this is how live CDs are made to look writable
[05:59] <twb> There is probably a paper somewhere that describes the linux boot process in detail; I don't have one handy to recommend.
[05:59] <AdamOutler> I think this is what I need.
[05:59] <AdamOutler> the paper describing the Uboot/Linux boot process.  I really need to sort out these formats.
[06:00] <AdamOutler> you're making me much smarter though twb.  I appreciate it.
[06:00] <AdamOutler> may I ask what you do for a living?
[06:01] <twb> http://prisonpc.com/
[06:06] <AdamOutler> thanks for your help.
[06:09] <AdamOutler> twb..  one more thing before I go..  On the pre-compiled version, the touchscreen is 90 degrees off, and the wifi is totally inop.   Any suggestions before I go trying to mix and match and recompile a few more things?
[06:09] <AdamOutler> https://plus.google.com/u/0/104711040110222472212/posts
[06:09] <twb> xrandr may help the latter if you are using X
[06:09] <twb> Er, the former
[06:09] <twb> wifi will probably be a missing firmware blob or soemthing
[06:10] <twb> http://openbsd.org/lyrics.html#39
[06:13] <twb> You'll need to find someone who knows about your hw
[06:14] <AdamOutler> ok..  I found out about the xrandr thing, but I'm having a problem getting getty to work.  I have a UART console hooked up, but I can't get shell access no matter what I do.
[06:14] <AdamOutler> I think it may have to do with the kernel being compiled with ttyS2 instead of ttyO2 for the default?
[06:14] <AdamOutler> I'm monitoring on ttyO2
[06:14] <twb> Never heard of ttyO2
[06:15] <twb> I've only seen ttyACM0 or so, plus the usual tty1 and ttyS0
[06:15] <AdamOutler> /dev/ttyO2 is Texas Instrument's serial administration console.
[06:15] <twb> ok
[06:15] <AdamOutler> On samsung devices it's /dev/ttySAC2
[06:15] <twb> Well, you can just pass console=/dev/ttyO2
[06:16] <twb> On the boot: prompt
[06:16] <AdamOutler> I can make this device and get output from it.. I just can't seem to send any input.  this would solve about 99% of my problems.
[06:16] <twb> Also in /etc/init/ there is a ttyN.conf you need to make one for O2
[06:16] <AdamOutler> I can't pass arguments.
[06:16] <twb> What output are you seeing?  The linux kernel boot messages?  A tty login prompt?  Both?
[06:18] <AdamOutler> I'm only getting kernel boot messages.   I have tried several things including creating a S80StartConsole in /etc/RCS.d, creating my device on the /dev/ folder with the proper chmod params, and creating a /etc/init/ttyO2.conf
[06:19] <twb> you probably got ttyO2.conf wrong, pastebin it
[06:20] <AdamOutler> http://pastebin.ubuntu.com/805911/
[06:20] <twb> Assuming the baud rate is right, looks OK to me.
[06:20] <AdamOutler> I've tried with those params and a -L instead of 8n
[06:20] <twb> Oh, and "rc RUNLEVEL=..." looks wrong.
[06:21] <twb> Never mind, it looks like that's the style used for other getty .conf
[06:21] <twb> I'm used to "start on runlevel [2345]" and "stop on runlevel [^2345]"
[06:21] <twb> I'm used to "start on runlevel [2345]" and "stop on runlevel [!2345]" (braino)
[06:22] <AdamOutler> I'll try that.
[06:22] <AdamOutler> next time.
[06:23] <AdamOutler> my s80StartConsole contains "start ttyO2" and a bunch of other things.  I have determined it is run as root so I have a way to make things happen, I just don't know what needs to happen.
[12:30] <S0NiC> hi
[12:31] <S0NiC> hmm is it possoible to play on a pandaboard any mp4 video? is this supported?
[12:32] <taruti> S0NiC: just use mplayer?
[12:33] <ogra_> only supported in totem
[12:33] <LetoThe2nd> ogra_: depends on the desired playback speed ;)
[12:34] <ogra_> mplayer would only try to do it in sw ... all gstreamer based players can use the hw acceleration of the panda (if you have the codecs installed=
[12:34] <S0NiC> ogra_: wich codecs would that be?
[12:34] <ogra_> LetoThe2nd, indeed, i should have said that mplayer is great for turning mp4 movies into slideshows instead :)
[12:35] <ogra_> S0NiC, just install the ubuntu-omap4-extras or the ubuntu-omap4-multimedia packages after you enabled the PPA
[12:35] <LetoThe2nd> S0NiC: maybe have a good look at http://rsalveti.wordpress.com/2012/01/06/hw-video-decode-and-xbmc-ubuntu-linaro/
[12:35] <LetoThe2nd> ogra_: cool use case that is ;)
[12:35] <ogra_> (they get installed by default after you clicked the TI desktop item on the images)
[12:36] <ogra_> LetoThe2nd, well, ubuntu-tv extensively makes use of xbmc ;)
[12:36] <S0NiC> thx
[12:36] <LetoThe2nd> ogra_: havent gotten round to try it yet :/
[12:36] <S0NiC> hmm wich kind of video works out of the box?
[12:36] <S0NiC> *codec
[12:39] <S0NiC> does anybody know?
[12:40] <LetoThe2nd> S0NiC: any video works out of the box, but none with hw accel. thats why the ppa is there.
[12:40] <S0NiC> LetoThe2nd: ok that means i have to enable hw acceleration. what means ppa in this case?
[12:41] <LetoThe2nd> S0NiC: basically http://omappedia.org/wiki/PandaBoard_Ubuntu_PPA, no idea how uptodate the instructions are.
[12:43] <ndec> the codecs which are h/w accelerated on OMAP4 are MPEG2, MPEG4, H263, H264, VC1 (WMV)
[12:43] <S0NiC> LetoThe2nd: but i think your link http://rsalveti.wordpress.com/2012/01/06/hw-video-decode-and-xbmc-ubuntu-linaro/ is good. but i have to create a new image...
[12:43] <ndec> just start with the default 11.10, upgrade it, reboot, and install the TI adds on.
[12:43] <ndec> that should be a good start.
[12:44] <S0NiC> ndec: mom
[12:45] <S0NiC> ndec: ok, iam using 10.10 at the moment...
[12:45] <ndec> ouch...
[12:45] <LetoThe2nd> urgh
[12:45] <ndec> any good reason to stick to 10.10?
[12:45] <LetoThe2nd> "ancient technologies and wisdom of the olde"?
[12:46] <S0NiC> ndec: no
[12:46] <S0NiC> ok, dann i update,
[12:46] <ndec> 11.10 has better OMAP support, and more codecs. and is maintained in case you face an issue
[12:46] <S0NiC> what is ment by the "ti adds"
[12:46] <S0NiC> ?
[12:46] <ndec> hum, my advice is to restart from scratch, don't dist-upgrade a 10.10 system into 11.10.
[12:46] <LetoThe2nd> S0NiC: the ti addons for hw accel
[12:47] <ndec> once you install 11.10 image, there will be an icon to install the TI 'addons' on the desktop. just click
[12:47] <S0NiC> i get them with apt-get....?
[12:47] <ndec> yes you can too.
[12:47] <S0NiC> ndec: ah cool
[12:47] <LetoThe2nd> S0NiC: have you actuelly read the links?
[12:47] <S0NiC> thanks guys
[12:47] <S0NiC> LetoThe2nd: only your link
[12:47] <S0NiC> now i have a lot to do ;D
[12:47] <ndec> but make sure that you run apt-get update & apt-get dist-upgrade before you install the TI stuff. some people have reported that there are issues otherwise
[12:48] <LetoThe2nd> S0NiC: i doubt it, because then you would know how to install them ;)
[12:50] <LetoThe2nd> one could also aim directly for the tv release that ricardo pointed to...
[12:51] <S0NiC> ok
[12:51] <S0NiC> thx
[12:52] <S0NiC> ok i have to leave cya later...
[12:52] <S0NiC> thx bye
[12:54] <LetoThe2nd> side note: his original question was in #ubuntu-de why 'apt-cache search vlc' did not yield any results :)
[12:54] <ogra_> oh, it should
[12:55] <LetoThe2nd> ogra_: on ancient 10.10, and a user that doesn't know how to handle a ppa? ;)
[12:55]  * ogra_ gets more than a terminal page 
[12:55] <ogra_> doesnt matter, vlc is in universe, he should even have seen it on 10.10
[12:56] <ndec> i guess he didn't enable universe
[12:56] <ogra_> yeah, smells like
[12:56] <ogra_> and 10.10 had a bug with the default sources.list iirc
[12:56] <ogra_> which we fixed in an update
[12:56] <LetoThe2nd> smells like nirvana... erm, teen spirit ;)
[12:56] <ogra_> hehe
[12:57]  * ogra_ had totally forgotten ubuntu-de ... i used to be resident there ... but i find IRC in german weird and have probs to not write half my sentences in english
[12:58] <LetoThe2nd> ogra_: the traffic there receded quite a bit over the last 3 or 4 years, after we enforced more and more to stay on topic, and in the meantime rejected to support weird offshoots/derivates/whatevers ;)
[12:59] <ogra_> yeah, i remember that kind of discuaaions
[12:59] <LetoThe2nd> ogra_: you wouldn't believe how many people come there bit***ing around when you reject to support mint or debian.
[12:59] <ogra_> oh, i would :) i see the same bitching in bugs ...
[13:00] <LetoThe2nd> ogra_: hehe
[13:00] <ogra_> rarely debian, but often mint users freak out that we dont support their ubiquity bugs for the hacked up mint installer
[13:00] <LetoThe2nd> ogra_: it has emerged that when the slightest doubts arise we ask for lsb_release -a and uname -a.
[13:00] <ogra_> and mint does serious bad things when customizing the distro
[13:01] <LetoThe2nd> ogra_: yeah, thats why we reject to support it.
[13:01] <ogra_> like disabling security updates for things like X11, kernel, dbus etc
[13:01] <ogra_> (or bootloaders)
[13:02] <ogra_> s/security updates/all updates/
[13:02] <LetoThe2nd> ogra_: hehe
[13:03] <LetoThe2nd> lets be glad they don't have an arm port yet.
[16:03] <hrw> heartbeat led trigger is not in kernel in 3.2.0/omap4
[16:13] <rsalveti> hrw: config issue I believE?
[16:18] <hrw> yes - it is a module now
[16:18] <hrw> I was surprised when one of my pandas stopped blinking
[16:20] <GrueMaster> It's a module?  figures.  Hard to track when I have 4 pandas in a tower.
[16:21] <hrw> ledtrig-heartbeat
[17:37] <S0NiC> re guys
[17:37] <S0NiC> so i installed ubuntu 11.10 and doing an apt-get update /dist upgrade
[17:37] <S0NiC> but there is no icon with Ti stuff... i only have installOAMP4addons...
[17:37] <S0NiC> is taht the same=?
[17:38] <ndec> yes
[17:41] <S0NiC> ndec: thx
[18:27] <vani> hello what's the arm ports repo for precise
[18:31] <vani> how can I point to the repos, I want to use live-build
[18:32] <rbasak> deb http://ports.ubuntu.com/ubuntu-ports precise main
[18:34] <vani> thank you.
[18:58] <NotJimCarrey> how do you add eabi support?
[20:19] <AdamOutler> HI!
[20:20] <AdamOutler> I've sucessfully created a boot.img that apparently works, however I am running into an error.   "Unrecognized/unsupported machine ID"..
[20:20] <AdamOutler> Is there a way to change this in my kernel?
[20:20] <AdamOutler> I'm using precompiled binaries
[20:20] <AdamOutler> Here is the pastebin: http://pastebin.com/7cBB05KF
 sorry I cannot help you on this as I'm new to ARM ports. But, I'm trying to piggy back on you.
[21:20] <vani> How did you create the boot.img...
[21:20] <vani> any notes or references...I'm having a board with ARMv7
[21:21] <vani> trying to build a custom image for it...
[21:25] <LetoThe2nd> the machine ID refers to the ID that the first/second stage bootloader passes to the kernel. the kernel uses this ID to decide which board file to use.
[21:25] <LetoThe2nd> if the kernel doesn't know about the ID, it will not boot. so make sure kernel and bootloader (u-boot in most cases) match.
[22:16] <LetoThe2nd> the machine ID refers to the ID that the first/second stage bootloader passes to the kernel. the kernel uses this ID to decide which board file to use.
[22:16] <LetoThe2nd> if the kernel doesn't know about the ID, it will not boot. so make sure kernel and bootloader (u-boot in most cases) match.
[22:16] <LetoThe2nd> AdamOutler: ^^^^^^^^^^
[22:17] <AdamOutler> oh
[22:17] <AdamOutler> hi
[22:17] <LetoThe2nd> concerning your question from some time ago.
[22:17] <AdamOutler> ok... so can I spoof this from U-Boot prompt somehow?
[22:17] <LetoThe2nd> hopefully not.
[22:18] <AdamOutler> LetoThe2nd, this is a Blaze Tablet based device.
[22:18] <AdamOutler> LetoThe2nd, I'm pretty sure I should be able to get something from the device by spoofing the id
[22:19] <LetoThe2nd> AdamOutler: its three parts altogether 1) get/register the machine ID at arm.linux.co.uk 2) make sure the bootloader passes this ID 3) make sure the kernel contains a board support file bound to this id.
[22:51] <AdamOutler> LetoThe2nd, the link you provided is bad.
[22:51] <LetoThe2nd> AdamOutler: the link was just from memory please google the correct site.
[23:12] <rsalveti> hrw: it should be built-in to work during boot I
[23:12] <rsalveti> something to ping ppisati to change
[23:23] <mythos> register what?
[23:39] <mythos> is it possible to start a dovel-kernel with qemu?
[23:43] <GrueMaster> mythos: A which kernel?  I think qemu wants a versatile kernel only.
[23:45] <mythos> yes, versatile runs perfectly. are you sure, that those dove-kernels don't run with qemu - i speak from those in maverick
[23:45] <mythos> 10.10
[23:45] <mythos> and btw thanks for your response, GrueMaster =)
[23:45] <GrueMaster> The dove kernels are specifically for Marvell hardware.
[23:46] <GrueMaster> Same as the omap4 kernels are for TI omap4 processors.
[23:46] <mythos> hmm... ok, i see
[23:46] <mythos> good to know why qemu pretends to stay black =)
[23:46] <GrueMaster> And the Marvell kernel for Maverick was a bit of a mess anyways.  It was the same as the Lucid kernel, just built with the Maverick tool chain.
[23:47] <mythos> i have a hp device here, which uses a maverick-debootstrab
[23:48] <mythos> it has marvell-hardware in it, so that fits
[23:48] <GrueMaster> Is it using a marvel soc?
[23:48] <GrueMaster> Cool.
[23:48]  * NCommander screams in horror
[23:49] <GrueMaster> heh
[23:49] <NCommander> mythos: is that a thinclient by any chance?
[23:49] <mythos> NCommander, yes
[23:49] <mythos> a hp 5335z
[23:49] <NCommander> mythos: ....
[23:49] <mythos> i broke yesterday one
[23:50] <mythos> was not able to boot up anymore, after i zeroed /dev/sda
[23:50] <mythos> ^^"
[23:51] <GrueMaster> Yea, that would be a bad thing.
[23:52] <NCommander> mythos: I loathe to say this, but that thing is based around a Marvell Dove board. If they took my patches wholesale, it *might* boot with an Ubuntu maverick dove image off USB
[23:52] <mythos> no, it should boot up from a usb-device. but it simply did not
[23:52] <NCommander> mythos: open it up and find the serial header to get uboot access :-)
[23:52] <NCommander> mythos: what image did you try?
[23:53] <mythos> NCommander, i only messed around with the the image, which is downloadable from hp
[23:53]  * GrueMaster watches NCommander's version of the crying game, laughing hysterically.
[23:53] <NCommander> mythos: http://cdimage.ubuntu.com/ubuntu-netbook/ports/releases/maverick/release/
[23:54] <NCommander> try one of the dove images, and see if it boots
[23:54] <NCommander> instructions are ... somewhere
[23:54] <NCommander> ^- GrueMaster
[23:55] <mythos> NCommander, i'm going to try that =)
[23:55] <NCommander> mythos: if it works, please don't call me ;.;
[23:55]  * NCommander horrorifically flashs back to China
[23:55] <mythos> don't?
[23:56] <NCommander> mythos: I was assigned to Antartica^W China for a month to do that image
[23:56] <mythos> ok, i won't
[23:56] <NCommander> I'm still scared from the experience
[23:56] <mythos> omg ^^"
[23:56] <NCommander> mythos: (actually, feel free to ping me, but what support I can give is limited)
[23:57] <mythos> my plan was to use the hp-image as skeleton
[23:57] <NCommander> mythos: alternatively, you might need to open it up, pop the HDD, and then do some creative repartitioning
[23:57] <mythos> hdd? there is no hdd inside them ^^"
[23:57] <NCommander> what compelled you to zero sda though?
[23:58] <NCommander> oh good, they fixed that 'bug'
[23:58] <mythos> omg xD
[23:59] <NCommander> mythos: so depending on how they smacked uboot, the thing will either try and load an image off USB, or try and TFTP a blob off somewhere (you'll probably need to use ethereal to see where its trying to get a blob)
[23:59] <twb> NCommander: why did you need to go to .cn to make an ISO9660?
[23:59] <mythos> even though it is limited, that offer is very nice, NCommander =)
[23:59] <twb> ethereal is called wireshark these days btw