**** BEGIN LOGGING AT Thu Dec 08 02:59:57 2011
Dec 08 03:26:00 <twb> lilstevie: my btrfs netbook decided to become corrupt with warning this morning, so I think I will be fast-tracking my TF101 now :-P
Dec 08 03:33:51 <lilstevie> lol
Dec 08 03:37:38 <twb> At least the notes were copied to another box
Dec 08 03:58:35 <GrueMaster> Grrr.  Looks like hunspell-en-us has clobbered all arm desktop images.
Dec 08 04:51:10 <Xase> lilstevie: oh @ evdev, rollup.
Dec 08 05:00:01 <twb> lilstevie: what's the URL for your latest tarball of stuff?
Dec 08 05:00:09 <twb> IIRC you changed its name and suchlike
Dec 08 05:05:43 <twb> Ah, "OLiFE"
Dec 08 09:50:37 <ogra_> hmm, where does that second omap4 armhf image build come from
Dec 08 09:52:20 <ogra_> infinity, was that you ?
Dec 08 09:52:36 * ogra_ definitely didnt trigger a second build 
Dec 08 11:06:06 <infinity> ogra_: Eh?  What second build?
Dec 08 11:06:29 <infinity> ogra_: Oh, cdimage?  I've been asleep.  So, not me.
Dec 08 11:06:39 <ogra_> k
Dec 08 11:06:55 <ogra_> i'll add the SUDO_USER stuff today then :P
Dec 08 11:07:14 <ogra_> but first i would love to know why ubiquity is broken :(
Dec 08 11:07:28 <infinity> The build, you mean?
Dec 08 11:07:34 * ogra_ sees no valid reason for it not finding flash-kernel-installer
Dec 08 11:07:37 <infinity> I was going to look at that today.
Dec 08 11:07:52 <infinity> After I get this mklibs hackery committed for netboot.
Dec 08 11:07:52 <ogra_> it complains about f-k-i missing in its source tree
Dec 08 11:08:01 <infinity> Yeah, I saw that.  Made little sense.
Dec 08 11:08:18 <infinity> Ooo, my bootstrap build of ghc finished.
Dec 08 11:08:18 <ogra_> but f-k-i definitely built for hf and the last ubiquity upload calims it pulled it in in the changelog
Dec 08 11:08:22 <infinity> Time to get the archive building it.
Dec 08 11:09:26 <ogra_> hmm, though it claims it can not create the target in the build log
Dec 08 11:09:41 <ogra_> not that the source file isnt there
Dec 08 11:09:54 <ogra_> i wonder if there is just a mkdir missing
Dec 08 11:10:34 <ogra_> (or -d for the install command)
Dec 08 11:10:45 <infinity> But it works on armel.
Dec 08 11:10:49 <infinity> Should be the same code.
Dec 08 11:10:50 <ogra_> yes
Dec 08 11:10:51 <infinity> Looking, though.
Dec 08 11:11:31 <ogra_> well, colin claims in the changelog that he adapted links for hf or some such
Dec 08 11:11:39 * ogra_ checks for the exacrt wording
Dec 08 11:12:05 <ogra_> hmm, no, that was d-i
Dec 08 11:12:11 <ogra_> ubiquity only has * Add armhf support.
Dec 08 11:12:40 * ogra_ doesnt really get it 
Dec 08 11:13:40 <infinity> lrwxrwxrwx 1 adconrad adconrad  15 2011-12-08 04:06 armhf -> d-i/lists/armel
Dec 08 11:13:49 <infinity> That could be the problem.
Dec 08 11:13:52 <ogra_> hmm
Dec 08 11:13:59 <infinity> That should be a link to the same directory.
Dec 08 11:14:30 <ogra_> geez, unpacking the xz takes my ac100 close to a halt
Dec 08 11:14:46 <ogra_> still running
Dec 08 11:15:18 <ogra_> fun
Dec 08 11:16:59 <ogra_> infinity, to the same file you mean
Dec 08 11:18:17 <infinity> Well, to the file in the same directory, yes.
Dec 08 11:18:30 <ogra_> yup
Dec 08 11:18:56 <infinity> Same problem in debian/
Dec 08 11:19:34 <ogra_> you mean the .install file ? yeah
Dec 08 11:19:44 <infinity> And that's probably your missing target.
Dec 08 11:19:59 <ogra_> and .dirs as well it seems
Dec 08 11:20:07 * infinity is also curious why ./d-i/source/base-installer/kernel/armhf.sh is different from ./d-i/source/base-installer/kernel/armel.sh
Dec 08 11:20:20 <infinity> But I'm also not entirely convinced that's used.
Dec 08 11:21:31 <ogra_> i doubt it, but it will surely caquse d-i issues since it originates there i think
Dec 08 11:24:54 <infinity> Well, let's see if fixing those symlinks makes ubiquity happy.
Dec 08 11:25:02 <infinity> To test build or not to test build...
Dec 08 11:25:07 <ogra_> pfft
Dec 08 11:25:09 <ogra_> just upload
Dec 08 11:25:43 <ogra_> will just waste 1h of your day to do a testbuilt, if it fails we can upload again
Dec 08 11:25:51 <ogra_> *testbuild
Dec 08 11:26:34 <ogra_> testbuilds are for freezes :P
Dec 08 11:29:02 * ogra_ wonders why gcc-4.5 is in the core seed
Dec 08 11:29:17 <ogra_> arent we using 4.6 since a while ?
Dec 08 11:30:07 <infinity> 4.4 is still in main too.
Dec 08 11:30:16 <ogra_> main, sure
Dec 08 11:30:21 <ogra_> but core ?
Dec 08 11:30:24 <infinity> Eh?
Dec 08 11:30:31 <infinity> "core" is just an upload packageset.
Dec 08 11:30:42 <infinity> I don't ever want any version of GCC living outside core, do you?
Dec 08 11:30:59 <ogra_> i want the default one in core ...
Dec 08 11:31:00 <infinity> Packagesets != Seeds.
Dec 08 11:31:09 <ogra_> why would i want the fallback there
Dec 08 11:31:26 <infinity> You want MOTU updating every compiler other than the primary one?
Dec 08 11:31:37 <infinity> Possibly accidentally dropping vital patches and breaking them? :)
Dec 08 11:31:56 <ogra_> well, -snapshot is in universe as well
Dec 08 11:32:06 <infinity> Yeah, because we don't build packages with snapshot.
Dec 08 11:32:07 <ogra_> afaik at least
Dec 08 11:32:15 <infinity> Sometimes we fall back to building packages with older versions of gcc.
Dec 08 11:32:23 <infinity> (MySQL is built with 4.5, for instance)
Dec 08 11:32:26 <ogra_> ah, k
Dec 08 11:32:36 <ogra_> i thought we fobid that a while ago
Dec 08 11:32:41 <ogra_> *forbid
Dec 08 11:32:44 <infinity> We can't, really.
Dec 08 11:33:00 <infinity> If a new compiler is broken for some chunk of code, what do we do?
Dec 08 11:33:06 <ogra_> fix it :)
Dec 08 11:33:09 <infinity> Just say "well, we can't ship MySQL unless the compiler is fixed"?
Dec 08 11:33:16 <ogra_> scream and shout to linaro ...
Dec 08 11:33:21 <infinity> That sort of thing doesn't work well with time-based releases. :P
Dec 08 11:33:26 <ogra_> heh
Dec 08 13:11:52 <doko> infinity, hmm, what is wrong with https://buildd.debian.org/status/package.php?p=gcc-4.4&suite=sid ?
Dec 08 13:11:55 <doko> armel
Dec 08 13:13:34 <infinity> doko: You forget to backport your -mfloat-abi=softfp change from 4.6 to earlier versions?
Dec 08 13:13:53 <infinity> doko: (The one where you explicitly set that for the Debian/armel build)
Dec 08 13:14:10 <infinity> s/forget/forgot/
Dec 08 13:15:21 <infinity>   else
Dec 08 13:15:21 <infinity>     # Debian armel
Dec 08 13:15:21 <infinity>     CONFARGS += --with-arch=armv4t --with-float=$(float_abi)
Dec 08 13:15:21 <infinity>   endif
Dec 08 13:15:28 <infinity> doko: ^-- That?
Dec 08 13:19:09 <doko> infinity, it's the default anyway, and 4.4 doesn't know about hard-float yet. it's just 4.4 linaro. so I assume I just back out this change for debian
Dec 08 13:19:54 <infinity> doko: Eh?  softfp wasn't the default, that's why you had to add it to 4.6...
Dec 08 13:20:15 <infinity> (Or, rather, the switch wasn't SET by default)
Dec 08 13:22:57 <infinity> doko: --with-float=$(float_abi) only happens in the ifeq Ubuntu block, so no float bits set for debian/armel.
Dec 08 13:23:04 <doko> infinity, Debian armel is soft, not softfp
Dec 08 13:23:20 <infinity> Well, whatever it was. :P
Dec 08 13:23:39 <infinity> I was just copying your else..endif from 4.6 up there.
Dec 08 13:23:49 <infinity> Anyhow.  You could just revert and not build on armhf at all.
Dec 08 13:23:59 <infinity> Or just make rules2's arm* block match 4.6
Dec 08 13:25:25 <infinity> 4.5 is in the same boat, I imagine.
Dec 08 13:49:37 <doko> infinity, ahh, no -mfloat-abi= parameter passed at all, which breaks the patch :-/
Dec 08 13:50:58 <doko> I know I dislike this default stuffing of config parameters
Dec 08 13:52:06 <infinity> I'm sure we can work up a more elegant patch later.  But this "works".
Dec 08 13:53:54 <infinity> doko: ghc is building on the buildds now, BTW.
Dec 08 13:54:15 <infinity> Local build took forever.  Silly haskell.
Dec 08 14:16:16 <ogra_> hmm
Dec 08 14:16:50 <ogra_> what i wonder is why did ubiquity 2.9.5 build flawless on armhf ... it shuld have had the same issues as .9.6
Dec 08 14:17:08 * ogra_ just noticed there is a binary
Dec 08 14:47:27 <IamTrying> I was using Ubuntu-ARM in my Eee pad transformer, now i get this: http://i.imgur.com/6lY5H.png  . How can i restore to Android using OLiFE.sh ? 1. Backup 2. Flash 3. Inject
Dec 08 14:49:26 * ogra_ would suggest to ask that in a transformer channel ... i doubt anyone here knows OLiFE.sh (apart from lilstevie probably)
Dec 08 14:56:41 <IamTrying> Fixed, with OLiFE.sh > Menu update > 1. Android kernel
Dec 08 14:56:56 <IamTrying> But i want to go back to Ubuntu again and see what caused it?
Dec 08 14:59:01 <lilstevie> IamTrying: sec
Dec 08 14:59:14 <lilstevie> wow
Dec 08 14:59:17 <lilstevie> wtf did you do
Dec 08 14:59:18 <lilstevie> 0.o
Dec 08 15:00:11 <IamTrying> Yea i was also thinking what i did. I actually Ubuntu-ARM but it does not auto boot
Dec 08 15:00:22 <IamTrying> So i needed to press always Vol+ to boot
Dec 08 15:00:32 <lilstevie> yeah, but that framebuffer connection is... just not normal
Dec 08 15:00:39 <IamTrying> Then i decided to re-install Ubuntu-ARM again so that auto it boots
Dec 08 15:00:44 <lilstevie> and yeah, that is normal if android is set as default boot
Dec 08 15:00:55 <lilstevie> ok, still doesn't really answer the question
Dec 08 15:01:07 <lilstevie> if you try running it as the recovery boot does it do the same
Dec 08 15:02:16 <ogra_> probably the antenna is just mis-adjusted :P
Dec 08 15:02:37 <IamTrying> I used this OLiFE.sh script to restore to Android ( https://gist.github.com/1447187 ) and it caused this > http://i.imgur.com/6lY5H.png
Dec 08 15:03:10 <lilstevie> that isn't what I asked
Dec 08 15:03:13 <lilstevie> ogra_: lol
Dec 08 15:03:35 <lilstevie> ogra_: that is like total fb corruption; I don't understand it in the slightest
Dec 08 15:03:48 <ogra_> bootloader probably
Dec 08 15:04:17 <lilstevie> ogra_: shouldn't be, bootloader goes with the OLiFE scripts
Dec 08 15:04:34 <lilstevie> purposely done so I don't have to deal with bootloader issues
Dec 08 15:04:43 <ogra_> isnt the frambuffer initialized by the bootloader on the transformer ?
Dec 08 15:04:49 <ogra_> like on the ac100
Dec 08 15:05:03 <lilstevie> yeah, but corruption like that would be kernel level
Dec 08 15:05:30 <lilstevie> or above
Dec 08 15:05:36 <IamTrying> Let me freshly install the Ubunt-ARM using OLiFE.sh. But it does not boot auto.
Dec 08 15:05:37 <lilstevie> maybe something done to xorg
Dec 08 15:05:37 <ogra_> on ac100 we dont re-initialize the fb ... so such a thing cant happen here
Dec 08 15:05:51 <IamTrying> I did always need to press vol+ to boot. and finally today it was failing to boot.
Dec 08 15:05:52 <ogra_> do you re-init it in the transformer kernel =
Dec 08 15:05:54 <ogra_> ?
Dec 08 15:06:04 <lilstevie> no, which is why I don't understand
Dec 08 15:06:12 <ogra_> yeah, weird
Dec 08 15:06:38 <lilstevie> also IamTrying yes, that means you set ubuntu to be secondary boot
Dec 08 15:06:39 <IamTrying> I did those steps and it fixed it now and i am back to Android PRime
Dec 08 15:06:40 <IamTrying> https://gist.github.com/1447187
Dec 08 15:06:44 <lilstevie> AKA; it is meant to do that
Dec 08 15:06:58 <lilstevie> as I said last time we had this little conversation
Dec 08 15:08:25 <IamTrying> Yes, when i try to setup for option 2, its very odd, it shows a loop of ASUS Screen and Linux unless i press manually down and then up button.  1. Turn device on or 2. Hold vol-down then press vol-up
Dec 08 15:16:25 <lilstevie> IamTrying: all I can really suggest is post in the QandA thread on XDA developers, maybe someone has come across your condition before and can help
Dec 08 15:17:41 <IamTrying> lilstevie, Yes sure, OLiFE.sh is excellent its genius, its working actually, saved my Android device. I just want to install the Ubuntu-Arm as power-on default boot, but optionally if requires i want to go back like now i did.
Dec 08 15:18:31 <lilstevie> default boot can be a little flakey tbh
Dec 08 15:18:39 <lilstevie> the mem carveout is not nice
Dec 08 15:19:41 <IamTrying> Ok, still fine, but There was a strange crash today. I pressed vol-down, i got the choice then i press vol-up to boot in my Ubuntu-Arm, but it shows lots of error and then nothing just happened. So then i decided to go back to Android.
Dec 08 15:45:18 <IamTrying> I just re-installed Ubuntu-Arm using OLiFE.sh just like Day 1. And i have the same crash everytime when i boot e.g: http://i.imgur.com/AGSzH.png
Dec 08 15:45:24 <IamTrying> Any idea?
Dec 08 15:58:11 <infinity> doko_: I'll fix qtmobility right after my next meeting.
Dec 09 01:18:55 <twb> lilstevie: hey, you around?
Dec 09 01:19:33 <twb> lilstevie: I'm trying to use your menu doodad from OLiFE 1.2, it isn't happy about something
Dec 09 01:19:56 <twb> nvflash configuration file error: partition/ filesystem_type invalid
Dec 09 01:25:37 <twb> lilstevie: it gets farther if I pick dualboot, so I think there's a typo in your configs/linux.cfg, investigating now
Dec 09 02:08:04 <lilstevie> yeah, there is :p
Dec 09 02:08:16 <lilstevie> twb: I need to fix it but there is a misplaced c
Dec 09 02:08:57 <lilstevie> sed -i 's/ext3c/ext3/g' ./configs/*
Dec 09 02:15:09 <twb> Ah, I saw that and thought it looked suspicious :-)
Dec 09 02:22:36 <lilstevie> yeah, was a typo, but haven't really gotten around to fixing it because I cbf, I don't want that script to be around for much longer
Dec 09 02:22:56 <lilstevie> and the more I fiddle around with trying to fix it the less time I have to work on the gui
Dec 09 02:23:45 <lilstevie> oh btw, interesting thing, someone else came across the same issue you were having with u-boot
Dec 09 02:29:40 <twb> Hooray
Dec 09 02:29:47 <twb> Did they fix it?
Dec 09 02:30:02 <lilstevie> well,
Dec 09 02:30:03 <lilstevie> no
Dec 09 02:30:04 <lilstevie> I did
Dec 09 02:30:11 <lilstevie> they were a little more helpful
Dec 09 02:30:18 * twb looks guilty
Dec 09 02:30:23 <lilstevie> turns out; not following instructions to the letter doesn't work
Dec 09 02:30:45 <twb> What did I fuck up?
Dec 09 02:30:49 <lilstevie> did you apply ARCH=arm on the same command line, or were you doing it from env vars
Dec 09 02:31:05 <twb> IIRC no because I was compiling on the device itself
Dec 09 02:31:12 <lilstevie> ok
Dec 09 02:31:36 <lilstevie> well the guy who also had the problem; if ARCH=arm was not supplied, it produced the same non working image you had
Dec 09 02:31:38 <twb> I've lost most of that when my netbook exploded yesterday
Dec 09 02:31:47 <lilstevie> fair enough
Dec 09 02:32:00 <twb> Interesting and annoying, tho
Dec 09 02:32:07 <twb> Do you know if he was cross-compiling?
Dec 09 02:32:08 <lilstevie> yeah
Dec 09 02:32:21 <twb> k
Dec 09 02:32:25 <lilstevie> he was, but I supply ARCH=arm when I compile on device
Dec 09 02:32:37 <twb> Hum
Dec 09 02:33:01 <lilstevie> cause I use the same script to build
Dec 09 02:33:15 <lilstevie> and supply the cross compiler in envvars
Dec 09 02:50:43 <twb> scripts/flash.sh: line 108: return: can only `return' from a function or sourced script
Dec 09 02:54:10 <twb> FYI you also appear to have done + ./bins/nvflash --bct ./images/transformer.bct --setbct --configfile ./configs/linux.cfg.cfg --bl ./images/bootloader.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --sync
**** ENDING LOGGING AT Fri Dec 09 02:59:58 2011