**** BEGIN LOGGING AT Mon Sep 24 02:59:59 2012
Sep 24 06:03:23 <seismic__> hey, are ubuntu-ports armhf binaries compiled for armv7+VFP?
Sep 24 06:03:42 <lilstevie> seismic__, that is what hardfloat is :p
Sep 24 06:04:25 <seismic__> lilstevie: cool, just to be sure ;)
Sep 24 06:04:30 <lilstevie> :)
Sep 24 06:06:04 <lilstevie> seismic__, armhf is armv7 using vfp for floating points, the only major thing armhf doesn't cover is neon
Sep 24 06:06:20 <lilstevie> and that is due to some armv7 cores out there not supporting neon
Sep 24 06:10:38 <seismic__> lilstevie: ok, i see
Sep 24 09:26:08 <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 ... ?
Sep 24 09:27:12 <ogra_> rsalveti, oh, ignore me, i'm blind
Sep 24 09:27:51 <ogra_> (somehow my brain was looking for armel in the archiers list)
Sep 24 09:27:57 <ogra_> *arches
Sep 24 10:24:45 <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?
Sep 24 10:25:50 <ogra_> int_ua, well, what did you loop mount ?
Sep 24 10:30:22 <int_ua> sudo mount -o "loop,offset=75497472" -t auto ubuntu-12.04-preinstalled-desktop-armhf+omap.img /mn
Sep 24 10:30:35 <int_ua> ogra_: ^
Sep 24 10:31:15 <ogra_> ohm, i thought you meant when running it :)
Sep 24 10:31:51 <int_ua> ogra_: doesn't it mean that the image FS is broken?
Sep 24 10:32:39 <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
Sep 24 10:33:06 <ogra_> i havent loop mounted an image in quite a while i must admit
Sep 24 10:33:35 <int_ua> Where should I report it?
Sep 24 10:33:38 <ogra_> (and preinstalled is dead from 12.10 on)
Sep 24 10:34:24 <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
Sep 24 10:34:46 <ogra_> and as said, this image type is dead
Sep 24 10:35:06 <int_ua> orga_: What's the proposed replacement if it's dead? Ubuntu Core?
Sep 24 10:35:42 <ogra_> well, for omap there is still ubuntu-server
Sep 24 10:36:06 <ogra_> beyond trhat all images are now simple live/alternate images like on x86
Sep 24 10:36:19 <ogra_> the preinstalled hackery is gone
Sep 24 10:38:00 <int_ua> ok, thanks
Sep 24 10:38:22 <ogra_> ubuntu core isnt an image
Sep 24 10:38:29 <ogra_> it is a base for building images
Sep 24 10:39:05 <ogra_> (or a cheap way of getting a chroot)
Sep 24 10:48:48 <int_ua> The same thing for Kubuntu, just different logical blocks
Sep 24 10:49:48 <Heradon> good morning
Sep 24 11:02:03 <Heradon> I have a question and that is responsible for the uboot you can load a image from MMC or does boot.axf?
Sep 24 11:03:49 <hrw> boot.axf?
Sep 24 11:03:58 <LetoThe2nd> sounds like armcc. bah.
Sep 24 11:04:30 <Heradon> on my gooseberry (android) is an nanda/boot.axf i think this is the firmware
Sep 24 11:06:43 <Heradon> i have build sucessfully a new u-boot.bin but boot from mmc is not possible
Sep 24 11:08:27 <Heradon> but the android boots without a problem ^^
Sep 24 12:37:26 <ogra_> damned ... i cant get the console up with more recent kernels on the zatab
Sep 24 12:51:19 * ogra_ doesnt get that
Sep 24 13:08:34 <ogra_> sigh
Sep 24 13:21:10 <ogra_> yay, at least i see 1G now
Sep 24 13:21:37 <ogra_> (well, 900+M )
Sep 24 13:24:17 <ogra_> oha, we used the totally wrong kernel branch for allwinner it seems
Sep 24 13:24:35 <ogra_> there is apparently a branch based on 3.0.42
Sep 24 13:25:15 * ogra_ clones 
Sep 24 16:42:05 <hrw> ogra_: allwinner? does it hurts badly?
Sep 24 16:42:15 <ogra_> well, so so
Sep 24 16:42:51 <ogra_> i have a kernel that has a working console now and that allocates the full 1G if i use mem=
Sep 24 16:43:10 <ogra_> no success with the mmc ot touchscreen drivers yet
Sep 24 16:43:14 <ogra_> *or
Sep 24 16:44:23 * xnox ponders if the way I wrote lvm support in ubiquity increased memory usage
Sep 24 16:44:36 <xnox> and if it did, whether it was significant....
Sep 24 16:44:53 <ogra_> who uses lvm anyway :)
Sep 24 16:45:09 * xnox does
Sep 24 16:45:15 <xnox> :P
Sep 24 16:45:25 <xnox> who uses arm anyway ;)
Sep 24 16:47:15 <ogra_> xnox, everyone using a mobilephone ;)
Sep 24 16:48:10 <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?
Sep 24 16:48:20 <hrw> ogra_: there are !arm mobilephones ;)
Sep 24 16:48:25 <sauerbraten> pandaboard A2 btw
Sep 24 16:48:36 <ogra_> hrw, rarely :)
Sep 24 16:49:04 * hrw -> off
Sep 24 16:49:32 <ogra_> sauerbraten, kernel issue i would say, and no, not known (works fine here)
Sep 24 16:50:45 <ogra_> sauerbraten, do you have a proper power supply attached (3A or bigger)
Sep 24 16:50:46 <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/
Sep 24 16:51:09 <sauerbraten> it worked with arch linux for arm, for example, so I guess. let me check though
Sep 24 16:51:34 <sauerbraten> 2.5A
Sep 24 16:51:49 <ogra_> no usb disk ?
Sep 24 16:51:56 <sauerbraten> nothing but the keyboard
Sep 24 16:52:04 <ogra_> then 2.5A should eb fine
Sep 24 16:52:06 <ogra_> *be
Sep 24 16:52:27 <ogra_> where did you get the required initrd ?
Sep 24 16:52:49 <sauerbraten> I didn't get one. do I need one? ooops
Sep 24 16:52:50 <ogra_> (or how did you produce it)
Sep 24 16:53:04 <ogra_> ah, well, i think the HID stuff is modules :)
Sep 24 16:53:13 <sauerbraten> I followed http://www.omappedia.com/wiki/OMAP_Ubuntu_Core and there was no mention of it
Sep 24 16:53:29 <ogra_> do you have an ubuntu PC around ?
Sep 24 16:54:10 <sauerbraten> I'm on xubuntu right now, installing xubuntu-desktop to the SD card, to see if xorg gets my keyboard
Sep 24 16:55:12 <ogra_> nah, wait
Sep 24 16:55:23 <ogra_> first install linux-omap4
Sep 24 16:55:34 <ogra_> so you get the modules
Sep 24 16:56:00 <sauerbraten> mhm, you're too late, but I'll do that when xubuntu finishes :)
Sep 24 16:56:28 <ogra_> any reason why you started off so compicated ?
Sep 24 16:56:57 <ogra_> nothing will be in sync with the defaults of an ubuntu system that way
Sep 24 16:57:30 <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
Sep 24 16:57:41 <sauerbraten> so it's named linux-omap4?
Sep 24 16:57:45 <ogra_> yes
Sep 24 16:58:00 <ogra_> why do you actually use core ... its not really designed for this
Sep 24 16:58:40 <sauerbraten> I used ubuntu for arm but it was really slow
Sep 24 16:58:54 <ogra_> ??
Sep 24 16:59:22 <sauerbraten> what?
Sep 24 16:59:30 <sauerbraten> I mean the UI
Sep 24 16:59:31 <ogra_> ubuntu for arm ... what do you mean
Sep 24 16:59:41 <sauerbraten> the normal ubuntu build for omap4
Sep 24 16:59:54 <ogra_> well, still core is to build images on top of it
Sep 24 16:59:56 <sauerbraten> https://wiki.ubuntu.com/ARM/OMAP
Sep 24 17:00:03 <ogra_> all the required installer bits arent there
Sep 24 17:00:18 <ogra_> and core is for use as a chroot
Sep 24 17:00:44 <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
Sep 24 17:00:58 <ogra_> for xubuntu desktop installs just use the server image
Sep 24 17:01:31 <ogra_> it offers you all installable tasks, ubuntu-dekstop or xubuntu-desktop are among them
Sep 24 17:01:46 <sauerbraten> sounds reasonable. well I'll see what I get now and if it fails again I'll try server
Sep 24 17:01:53 <ogra_> and you end up with a properly set up system that doesnt fall over all the time on package upgrades
Sep 24 17:02:04 <sauerbraten> core does?
Sep 24 17:02:29 <ogra_> it will, i,.e. the kernel relies on a properly configured bootloader setup
Sep 24 17:36:57 <sauerbraten> ogra_: will the server image offer a login prompt on hdmi or only serial?
Sep 24 17:37:44 <ogra_> it defaults to run the installer on serial, once installed it will show ttys on all consoles (so on hdmi too)
Sep 24 17:47:44 <sauerbraten> do I have to interact with the installer?
Sep 24 17:47:53 <ogra_> yes
Sep 24 17:48: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
Sep 24 17:49:11 <ogra_> that should give you the installer on HDMI by default
Sep 24 17:49:42 <ogra_> (in 12.10 we actually ship a second bootloader config that you can just cp in place if needed)
Sep 24 17:50:14 <ogra_> but 12.10 expects to install to a USB target device by default
Sep 24 18:16:25 <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...
Sep 24 20:08:55 <GrueMaster> sauerbraten: The installer is oem-config.  It only prompts for localization (username/password, language, timezone, etc).  It is not the full installer.
Sep 24 20:10: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
Sep 24 20:12: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.
Sep 24 20:21:14 <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?
Sep 24 20:24:54 <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
Sep 24 20:28:50 <GrueMaster> sauerbraten: I can help you get around the serial console issue.  It is a simple edit of the boot.scr file.
Sep 24 20:30:59 <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?
Sep 24 20:31:54 <GrueMaster> Are you using a Linux PC or a Windows system?  You will need to edit the boot.scr on the 1st partition.
Sep 24 20:37:06 <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.
Sep 24 20:41:22 <GrueMaster> I actually had this documented on the ubuntu wiki at one point.  Now it is all gone.  sigh.
Sep 24 20:47:42 <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"
Sep 24 20:47:52 <GrueMaster> And that should work.
Sep 24 20:48:26 <GrueMaster> Save the file as preEnv.txt (delete boot.scr).
Sep 24 21:14:22 <sauerbraten> ok, wrote that down. thanks GrueMaster
Sep 24 21:14:56 <GrueMaster> No problem.  I just wish it had stayed on the wiki.
Sep 24 21:21:58 <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 :)
Sep 24 21:23:28 <GrueMaster> Ok.  Let me know how it goes.
Sep 24 21:24:45 <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
Sep 24 21:25:32 <GrueMaster> These are the parameters that uboot passes to the kernel.  They are the kernel boot arguments.
Sep 24 21:25:50 <GrueMaster> Just a different syntax than, say, grub or lilo.
Sep 24 21:27:00 <sauerbraten> but for example  mem=456M@0x80000000 mem=512M@0xA0000000 look like it tells the kernel where to allocate memory or something? why twice?
Sep 24 21:27:57 <sauerbraten> also fixrtc?
Sep 24 21:29:12 <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.
Sep 24 21:29:39 <GrueMaster> The fixrtc runs a script that essentially sets the time to the last filesystem write time.
Sep 24 21:29:53 <GrueMaster> Since there is no battery backed RTC in the system.
Sep 24 21:32:53 <GrueMaster> Quiet tells the kernel to quit yapping, and splash will run Plymouth splash screen.
Sep 24 21:33:36 <GrueMaster> Not sure on the vram, but it is omap specific.
Sep 24 21:33:47 <GrueMaster> I think it is for Video Ram.
Sep 24 21:34:10 <GrueMaster> to allocate shared memory as video memory.
Sep 24 21:34:11 <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
Sep 24 21:35:57 <GrueMaster> It should have had other stuff as well (like the bootargs).
Sep 24 21:36:14 <sauerbraten> doesn't, not in a standard text editor at least
Sep 24 21:36:33 <GrueMaster> What are you editing with?
Sep 24 21:36:39 <sauerbraten> leafpad
Sep 24 21:36:43 <sauerbraten> now checking with cat
Sep 24 21:36:54 <sauerbraten> ok cat shows more
Sep 24 21:36:56 <GrueMaster> Hmm.  Never used that one.
Sep 24 21:36:56 <sauerbraten> I'll try nano
Sep 24 21:37:10 <sauerbraten> yes that works
Sep 24 21:37:19 <GrueMaster> The first 72 bytes are the CRC.
Sep 24 21:38:05 <sauerbraten> this is what's in there besides the CRC bytes http://pastie.org/4793694
Sep 24 21:38:16 <sauerbraten> looks good? now edit the bootargs how you said?
Sep 24 21:39:27 <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
Sep 24 21:39:36 <GrueMaster> yes, only just edit the way it looks in the boot.scr (i.e. remove the console= and the debian-installer stuff).
Sep 24 21:39:45 <sauerbraten> ok
Sep 24 21:40:01 <GrueMaster> Yea, so just remove everything after the splash.
Sep 24 21:40:31 <sauerbraten> and the CRC, cause that will be wrong now?
Sep 24 21:40:43 <GrueMaster> Right.
Sep 24 21:40:59 <GrueMaster> Are you on a linux system while editing?
Sep 24 21:41:02 <sauerbraten> yep
Sep 24 21:41:18 <sauerbraten> so, save that as boot.scr or preEnv.txt now?
Sep 24 21:41:33 <GrueMaster> Then you can re-add the crc with mkimage.
Sep 24 21:41:46 <GrueMaster> Save it as boot.script.
Sep 24 21:42:05 <sauerbraten> done
Sep 24 21:42:31 <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 ?
Sep 24 21:42:36 <GrueMaster> then type "mkimage -A arm -O linux -T script -C none -n boot.scr boot.script"
Sep 24 21:42:54 <GrueMaster> Or what you said.
Sep 24 21:43:15 <sauerbraten> yours gave me segfault o.O
Sep 24 21:43:34 <GrueMaster> (I had -n and -d confused).
Sep 24 21:43:43 <sauerbraten> oh ok
Sep 24 21:43:48 <sauerbraten> well, let's try this!
Sep 24 21:43:58 <GrueMaster> I haven't done this since April.
Sep 24 21:44:20 <GrueMaster> Now that you have boot.scr, copy it back to the first partition of the SD and boot in a panda.
Sep 24 21:45:05 <sauerbraten> I always had it on the first partition, was too lazy to even copy it away from there :)
Sep 24 21:45:24 <GrueMaster> That works too.
Sep 24 21:45:32 <sauerbraten> mhm, nothing happening yet, only both LEDs on
Sep 24 21:45:57 <GrueMaster> I used to do this (and many other edits) on a more than daily basis, so I wrote a script.
Sep 24 21:46:00 <GrueMaster> Hmmm.
Sep 24 21:46:28 <GrueMaster> It may be doing the first stage filesystem expansion.  Give it about 5 minutes.
Sep 24 21:47:04 <GrueMaster> The preinstalled images will boot once to expand the rootfs to fill the SD, then reboot into oem-config.
Sep 24 21:47:44 <GrueMaster> And that stage is only visible without quiet & splash in the bootargs.
Sep 24 21:48:33 <GrueMaster> But iirc, one LED should shut off as soon as it loads the kernel.
Sep 24 21:49:11 <sauerbraten> yeah I remember that. we'll see. I also think I remember the SD LED to blink once or twice while it booted ./
Sep 24 21:49:22 <GrueMaster> How did you write the image to the SD?
Sep 24 21:49:48 <sauerbraten> dd and bs=4M
Sep 24 21:49:56 <sauerbraten> it said 1M, but hey
Sep 24 21:50:03 <GrueMaster> ok
Sep 24 21:50:06 <sauerbraten> plus sudo sync, so that shoul have worked
Sep 24 21:51:07 <GrueMaster> Is this a precise image?  img.gz?
Sep 24 21:51:32 <sauerbraten> yes. but wait, I just realized I left the empty preEnv.txt on there
Sep 24 21:51:38 <sauerbraten> maybe the bootloader is confused
Sep 24 21:51:56 <GrueMaster> could be.
Sep 24 21:52:24 <GrueMaster> I need to step out for ~15 minutes.  biab.
Sep 24 21:56:39 <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
Sep 24 22:16:15 <sauerbraten> works now, I even see the resizing splash on HDMI
Sep 24 22:16:56 <GrueMaster> Cool.
Sep 24 22:17:35 <GrueMaster> Should be fairly straight-forward from here.
**** ENDING LOGGING AT Tue Sep 25 02:59:58 2012