[06:03] <seismic__> hey, are ubuntu-ports armhf binaries compiled for armv7+VFP?
[06:03] <lilstevie> seismic__, that is what hardfloat is :p
[06:04] <seismic__> lilstevie: cool, just to be sure ;)
[06:04] <lilstevie> :)
[06:06] <lilstevie> seismic__, armhf is armv7 using vfp for floating points, the only major thing armhf doesn't cover is neon
[06:06] <lilstevie> and that is due to some armv7 cores out there not supporting neon
[06:10] <seismic__> lilstevie: ok, i see
[09:26] <ogra_> rsalveti, do you know if https://launchpad.net/ubuntu/quantal/+source/xbmc/2:11.0~git20120510.82388d5-1ubuntu2 could also build for arm ? or is it missing patches ... ?
[09:27] <ogra_> rsalveti, oh, ignore me, i'm blind
[09:27] <ogra_> (somehow my brain was looking for armel in the archiers list)
[09:27] <ogra_> *arches
[10:24] <int_ua> I'm constantly getting a couple of "Buffer I/O error on device loop1, logical block 494320" while mounting/working with 12.04 OMAP preinstalled image. Can anyone suggest what's the problem?
[10:25] <ogra_> int_ua, well, what did you loop mount ?
[10:30] <int_ua> sudo mount -o "loop,offset=75497472" -t auto ubuntu-12.04-preinstalled-desktop-armhf+omap.img /mn
[10:30] <int_ua> ogra_: ^
[10:31] <ogra_> ohm, i thought you meant when running it :)
[10:31] <int_ua> ogra_: doesn't it mean that the image FS is broken?
[10:32] <ogra_> might be, it doesnt stay like that since on first boot the SD gets re-partitioned and the FS gets adjusted to the SD
[10:33] <ogra_> i havent loop mounted an image in quite a while i must admit
[10:33] <int_ua> Where should I report it?
[10:33] <ogra_> (and preinstalled is dead from 12.10 on)
[10:34] <ogra_> you could report it against debian-cd i guess but dont expect it to be fixed, loop mounting the images is a corner case and arm wasnt even rebuilt for 12.04.1
[10:34] <ogra_> and as said, this image type is dead
[10:35] <int_ua> orga_: What's the proposed replacement if it's dead? Ubuntu Core?
[10:35] <ogra_> well, for omap there is still ubuntu-server
[10:36] <ogra_> beyond trhat all images are now simple live/alternate images like on x86
[10:36] <ogra_> the preinstalled hackery is gone
[10:37] <int_ua> ok, thanks
[10:38] <ogra_> ubuntu core isnt an image
[10:38] <ogra_> it is a base for building images
[10:39] <ogra_> (or a cheap way of getting a chroot)
[10:48] <int_ua> The same thing for Kubuntu, just different logical blocks
[10:49] <Heradon> good morning
[11:02] <Heradon> I have a question and that is responsible for the uboot you can load a image from MMC or does boot.axf?
[11:03] <hrw> boot.axf?
[11:03] <LetoThe2nd> sounds like armcc. bah.
[11:04] <Heradon> on my gooseberry (android) is an nanda/boot.axf i think this is the firmware
[11:06] <Heradon> i have build sucessfully a new u-boot.bin but boot from mmc is not possible
[11:08] <Heradon> but the android boots without a problem ^^
[12:37] <ogra_> damned ... i cant get the console up with more recent kernels on the zatab
[12:51]  * ogra_ doesnt get that
[13:08] <ogra_> sigh
[13:21] <ogra_> yay, at least i see 1G now
[13:21] <ogra_> (well, 900+M )
[13:24] <ogra_> oha, we used the totally wrong kernel branch for allwinner it seems
[13:24] <ogra_> there is apparently a branch based on 3.0.42
[13:25]  * ogra_ clones 
[16:42] <hrw> ogra_: allwinner? does it hurts badly?
[16:42] <ogra_> well, so so
[16:42] <ogra_> i have a kernel that has a working console now and that allocates the full 1G if i use mem=
[16:43] <ogra_> no success with the mmc ot touchscreen drivers yet
[16:43] <ogra_> *or
[16:44]  * xnox ponders if the way I wrote lvm support in ubiquity increased memory usage
[16:44] <xnox> and if it did, whether it was significant....
[16:44] <ogra_> who uses lvm anyway :)
[16:45]  * xnox does
[16:45] <xnox> :P
[16:45] <xnox> who uses arm anyway ;)
[16:47] <ogra_> xnox, everyone using a mobilephone ;)
[16:48] <sauerbraten> using the precise ubuntu core rootfs on a pandaboard I can't use my keyboard. at no point is there any power (i.e. the lock leds never light up). known bug / not a bug?
[16:48] <hrw> ogra_: there are !arm mobilephones ;)
[16:48] <sauerbraten> pandaboard A2 btw
[16:48] <ogra_> hrw, rarely :)
[16:49]  * hrw -> off
[16:49] <ogra_> sauerbraten, kernel issue i would say, and no, not known (works fine here)
[16:50] <ogra_> sauerbraten, do you have a proper power supply attached (3A or bigger)
[16:50] <sauerbraten> mhm... I only untared the rootfs to the second partition and put MLO, u-boot.bin and uImage onto the boot partition from http://ports.ubuntu.com/ubuntu-ports/dists/precise/main/installer-armhf/current/images/omap4/netboot/
[16:51] <sauerbraten> it worked with arch linux for arm, for example, so I guess. let me check though
[16:51] <sauerbraten> 2.5A
[16:51] <ogra_> no usb disk ?
[16:51] <sauerbraten> nothing but the keyboard
[16:52] <ogra_> then 2.5A should eb fine
[16:52] <ogra_> *be
[16:52] <ogra_> where did you get the required initrd ?
[16:52] <sauerbraten> I didn't get one. do I need one? ooops
[16:52] <ogra_> (or how did you produce it)
[16:53] <ogra_> ah, well, i think the HID stuff is modules :)
[16:53] <sauerbraten> I followed http://www.omappedia.com/wiki/OMAP_Ubuntu_Core and there was no mention of it
[16:53] <ogra_> do you have an ubuntu PC around ?
[16:54] <sauerbraten> I'm on xubuntu right now, installing xubuntu-desktop to the SD card, to see if xorg gets my keyboard
[16:55] <ogra_> nah, wait
[16:55] <ogra_> first install linux-omap4
[16:55] <ogra_> so you get the modules
[16:56] <sauerbraten> mhm, you're too late, but I'll do that when xubuntu finishes :)
[16:56] <ogra_> any reason why you started off so compicated ?
[16:56] <ogra_> nothing will be in sync with the defaults of an ubuntu system that way
[16:57] <sauerbraten> I read https://wiki.ubuntu.com/Core/InstallationExample where it says to install a kernel and the dependencies, but I couldn't find linux-image for arm so I left that out
[16:57] <sauerbraten> so it's named linux-omap4?
[16:57] <ogra_> yes
[16:57] <ogra_> why do you actually use core ... its not really designed for this
[16:58] <sauerbraten> I used ubuntu for arm but it was really slow
[16:58] <ogra_> ??
[16:59] <sauerbraten> what?
[16:59] <sauerbraten> I mean the UI
[16:59] <ogra_> ubuntu for arm ... what do you mean
[16:59] <sauerbraten> the normal ubuntu build for omap4
[16:59] <ogra_> well, still core is to build images on top of it
[16:59] <sauerbraten> https://wiki.ubuntu.com/ARM/OMAP
[17:00] <ogra_> all the required installer bits arent there
[17:00] <ogra_> and core is for use as a chroot
[17:00] <ogra_> you shouldnt try to roll a normel system based on it if you dont exactly knwo which bits and pieces need to be touched
[17:00] <ogra_> for xubuntu desktop installs just use the server image
[17:01] <ogra_> it offers you all installable tasks, ubuntu-dekstop or xubuntu-desktop are among them
[17:01] <sauerbraten> sounds reasonable. well I'll see what I get now and if it fails again I'll try server
[17:01] <ogra_> and you end up with a properly set up system that doesnt fall over all the time on package upgrades
[17:02] <sauerbraten> core does?
[17:02] <ogra_> it will, i,.e. the kernel relies on a properly configured bootloader setup
[17:36] <sauerbraten> ogra_: will the server image offer a login prompt on hdmi or only serial?
[17:37] <ogra_> it defaults to run the installer on serial, once installed it will show ttys on all consoles (so on hdmi too)
[17:47] <sauerbraten> do I have to interact with the installer?
[17:47] <ogra_> yes
[17:48] <ogra_> you can rebuild the boot.scr on the first SD partition and drop the console= arg as well as the debian-installer/framebiffer option
[17:49] <ogra_> that should give you the installer on HDMI by default
[17:49] <ogra_> (in 12.10 we actually ship a second bootloader config that you can just cp in place if needed)
[17:50] <ogra_> but 12.10 expects to install to a USB target device by default
[18:16] <sauerbraten> ogra_: mhm that's bad, I don't have my serial cable with me atm :/ I booted it anyway and the screen got activated, I don't have any prompt though. sure there is an installer on there? it's already 630MB and it's named preinstalled, so...
[20:08] <GrueMaster> sauerbraten: The installer is oem-config.  It only prompts for localization (username/password, language, timezone, etc).  It is not the full installer.
[20:10] <sauerbraten> GrueMaster: ok, I had to let go though. I'm now using a minimal biuld from http://rcn-ee.net/deb/rootfs/precise/ which does it's job quite good until now
[20:12] <GrueMaster> Ok.  I can also help with the preinstalled server image if you want.  The rcn-ee images are a bit customized, and asside from the apps, you won't get much help here.
[20:21] <sauerbraten> GrueMaster: well I would have to have my serial cable which is about 150km away from where I am :) the repos should be the same as for the original ubuntu though, right? so I will eventually be able to get the graphics to work?
[20:24] <sauerbraten> I was actually running ubuntu server before I think, but couldn't get X to work properly. I had a nifty little autoupdate config though which I plan on using again
[20:28] <GrueMaster> sauerbraten: I can help you get around the serial console issue.  It is a simple edit of the boot.scr file.
[20:30] <sauerbraten> GrueMaster: oooh! well, it's kind of too late now. wanna tell me anyway so I can save a boot.script file in case I switch back to server?
[20:31] <GrueMaster> Are you using a Linux PC or a Windows system?  You will need to edit the boot.scr on the 1st partition.
[20:37] <GrueMaster> Give me a second.  looking up the alternate names for boot.scr.  There is a way to edit it and save it as plain text without the u-boot crc header.
[20:41] <GrueMaster> I actually had this documented on the ubuntu wiki at one point.  Now it is all gone.  sigh.
[20:47] <GrueMaster> Ok, figured it out.  Edit the boot.scr, remove the binary crap at the beginning, and replace the bootargs with "bootargs=vram=40M mem=456M@0x80000000 mem=512M@0xA0000000 root=/dev/mmcblk0p2 fixrtc quiet splash"
[20:47] <GrueMaster> And that should work.
[20:48] <GrueMaster> Save the file as preEnv.txt (delete boot.scr).
[21:14] <sauerbraten> ok, wrote that down. thanks GrueMaster
[21:14] <GrueMaster> No problem.  I just wish it had stayed on the wiki.
[21:21] <sauerbraten> so, after "apt-get install linux-omap4" rendered the system unusable again (no login prompt, no X, though that worked before) I'm now actually gonna use your method, GrueMaster :)
[21:23] <GrueMaster> Ok.  Let me know how it goes.
[21:24] <sauerbraten> can you tell me what the bootargs mean? I've used so many different boot.src's now, would be good to know what I'm actually putting in there
[21:25] <GrueMaster> These are the parameters that uboot passes to the kernel.  They are the kernel boot arguments.
[21:25] <GrueMaster> Just a different syntax than, say, grub or lilo.
[21:27] <sauerbraten> but for example  mem=456M@0x80000000 mem=512M@0xA0000000 look like it tells the kernel where to allocate memory or something? why twice?
[21:27] <sauerbraten> also fixrtc?
[21:29] <GrueMaster> The mem= lines map memory holes in system memory.  These holes are used for the video decoder.  If you aren't running the omap4 powervr drivers (i.e. stock FB) then you don't need these lines.
[21:29] <GrueMaster> The fixrtc runs a script that essentially sets the time to the last filesystem write time.
[21:29] <GrueMaster> Since there is no battery backed RTC in the system.
[21:32] <GrueMaster> Quiet tells the kernel to quit yapping, and splash will run Plymouth splash screen.
[21:33] <GrueMaster> Not sure on the vram, but it is omap specific.
[21:33] <GrueMaster> I think it is for Video Ram.
[21:34] <GrueMaster> to allocate shared memory as video memory.
[21:34] <sauerbraten> ok, I will hopefully use the powervr driver :) when you said "remove that binary crap", you meant I can delete the whole file? cause there's nothing in there besides weird bytes
[21:35] <GrueMaster> It should have had other stuff as well (like the bootargs).
[21:36] <sauerbraten> doesn't, not in a standard text editor at least
[21:36] <GrueMaster> What are you editing with?
[21:36] <sauerbraten> leafpad
[21:36] <sauerbraten> now checking with cat
[21:36] <sauerbraten> ok cat shows more
[21:36] <GrueMaster> Hmm.  Never used that one.
[21:36] <sauerbraten> I'll try nano
[21:37] <sauerbraten> yes that works
[21:37] <GrueMaster> The first 72 bytes are the CRC.
[21:38] <sauerbraten> this is what's in there besides the CRC bytes http://pastie.org/4793694
[21:38] <sauerbraten> looks good? now edit the bootargs how you said?
[21:39] <sauerbraten> actually, this is the whole bootargs line: bootargs vram=40M mem=456M@0x80000000 mem=512M@0xA0000000   root=/dev/mmcblk0p2 fixrtc quiet splash debian-installer/framebuffer=false console=ttyO2,115200n8
[21:39] <GrueMaster> yes, only just edit the way it looks in the boot.scr (i.e. remove the console= and the debian-installer stuff).
[21:39] <sauerbraten> ok
[21:40] <GrueMaster> Yea, so just remove everything after the splash.
[21:40] <sauerbraten> and the CRC, cause that will be wrong now?
[21:40] <GrueMaster> Right.
[21:40] <GrueMaster> Are you on a linux system while editing?
[21:41] <sauerbraten> yep
[21:41] <sauerbraten> so, save that as boot.scr or preEnv.txt now?
[21:41] <GrueMaster> Then you can re-add the crc with mkimage.
[21:41] <GrueMaster> Save it as boot.script.
[21:42] <sauerbraten> done
[21:42] <sauerbraten> now mkimage -A arm -O linux -T script -C none -a 0 -e 0 -n "ubuntu server boot script" -d boot.script boot.scr ?
[21:42] <GrueMaster> then type "mkimage -A arm -O linux -T script -C none -n boot.scr boot.script"
[21:42] <GrueMaster> Or what you said.
[21:43] <sauerbraten> yours gave me segfault o.O
[21:43] <GrueMaster> (I had -n and -d confused).
[21:43] <sauerbraten> oh ok
[21:43] <sauerbraten> well, let's try this!
[21:43] <GrueMaster> I haven't done this since April.
[21:44] <GrueMaster> Now that you have boot.scr, copy it back to the first partition of the SD and boot in a panda.
[21:45] <sauerbraten> I always had it on the first partition, was too lazy to even copy it away from there :)
[21:45] <GrueMaster> That works too.
[21:45] <sauerbraten> mhm, nothing happening yet, only both LEDs on
[21:45] <GrueMaster> I used to do this (and many other edits) on a more than daily basis, so I wrote a script.
[21:46] <GrueMaster> Hmmm.
[21:46] <GrueMaster> It may be doing the first stage filesystem expansion.  Give it about 5 minutes.
[21:47] <GrueMaster> The preinstalled images will boot once to expand the rootfs to fill the SD, then reboot into oem-config.
[21:47] <GrueMaster> And that stage is only visible without quiet & splash in the bootargs.
[21:48] <GrueMaster> But iirc, one LED should shut off as soon as it loads the kernel.
[21:49] <sauerbraten> yeah I remember that. we'll see. I also think I remember the SD LED to blink once or twice while it booted ./
[21:49] <GrueMaster> How did you write the image to the SD?
[21:49] <sauerbraten> dd and bs=4M
[21:49] <sauerbraten> it said 1M, but hey
[21:50] <GrueMaster> ok
[21:50] <sauerbraten> plus sudo sync, so that shoul have worked
[21:51] <GrueMaster> Is this a precise image?  img.gz?
[21:51] <sauerbraten> yes. but wait, I just realized I left the empty preEnv.txt on there
[21:51] <sauerbraten> maybe the bootloader is confused
[21:51] <GrueMaster> could be.
[21:52] <GrueMaster> I need to step out for ~15 minutes.  biab.
[21:56] <sauerbraten> mhm, I checked my boot.scr and boot.script again and it seems something got messed up (or I did) well, the boot.scr didn't contain anything but the CRC (probably from getting an empty preEnv.txt the first time?) and boot.script was completely erased. I'll copy the original boot.scr now and edit it again, this time making sure to not mess up
[22:16] <sauerbraten> works now, I even see the resizing splash on HDMI
[22:16] <GrueMaster> Cool.
[22:17] <GrueMaster> Should be fairly straight-forward from here.