**** BEGIN LOGGING AT Fri Dec 09 02:59:58 2011
Dec 09 03:07:47 <lilstevie> I always call the other scripts with source 0.o
Dec 09 03:11:25 <twb> OK my fault then
Dec 09 03:16:03 <twb> Also when flashing it gets to "Device needs to be put back into APX mode" but doesn't pause
Dec 09 03:43:01 <lilstevie> odd
Dec 09 03:43:03 <lilstevie> it should
Dec 09 03:49:45 <twb> Why does linux.cfg say USP instead of UBT?
Dec 09 03:49:56 <twb> nm, UBT is further up
Dec 09 03:51:22 <twb> When I boot it, it coms up with the eeepad/asus/nvidia logos, and just sits at that screen
Dec 09 03:53:01 <twb> I am using your olife prime edition, maybe the asus bootloader that ships with that is wrong for the 32G
Dec 09 03:54:42 <lilstevie> no
Dec 09 03:54:45 <lilstevie> there is one bootloader
Dec 09 03:56:39 <twb> OK
Dec 09 03:57:10 <twb> I asked because now when I do boot+voldn, it gives me only "wipe data" and no second icon, last time IIRC there were two icons and volup switched between them
Dec 09 03:58:20 <lilstevie> newer versions doesn't
Dec 09 03:58:28 <lilstevie> don't*
Dec 09 03:58:46 <twb> ah ok
Dec 09 03:59:22 <lilstevie> you may need to put the kernel in recovery position and write recovery-boot to msc
Dec 09 04:01:06 <twb> ./bins/nvflash --bct ./images/transformer.bct --setbct --configfile ./configs/linux.cfg --create --bl ./images/bootloader.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --go
Dec 09 04:01:06 <twb> ./bins/nvflash --bct ./images/transformer.bct --setbct --configfile ./configs/linux.cfg.cfg --bl ./images/bootloader.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --sync && ./bins/nvflash -r --download 8 ./images/ubuntu.img
Dec 09 04:01:12 <twb> ...those were the commands that ran
Dec 09 04:01:32 <lilstevie> yeah
Dec 09 04:01:54 <lilstevie> there has been some wierd condition though with decompressing the initrd
Dec 09 04:01:57 <lilstevie> in main boot
Dec 09 04:02:19 <lilstevie> where quite frankly, it dies on its ass and has a kernel panic
Dec 09 04:02:39 <twb> I don't think that's what's happening to me
Dec 09 04:02:58 <lilstevie> what is happening to you
Dec 09 04:03:06 <twb> 14:47 <twb> When I boot it, it coms up with the eeepad/asus/nvidia logos, and just sits at that screen
Dec 09 04:03:22 <twb> If it was oopsing in the ramdisk I would expect it to say so onscreen
Dec 09 04:03:35 <lilstevie> yeah it does
Dec 09 04:03:43 <lilstevie> incomplete write
Dec 09 04:09:29 <lilstevie> ./bins/nvflash --bct ./images/transformer.bct --setbct --configfile ./configs/linux.cfg --bl ./images/bootloader.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --sync && ./bins/abootimg-$(uname -m) --create ./tmp/linux.img -f ./boot/purelinux.cfg -k ./kernels/2636-zImage -r ./kernels/initrd-2.6.36.img && ./bins/nvflash -r --download 6 ./tmp/linux.img
Dec 09 04:09:54 <twb> 6 not 8 ?
Dec 09 04:10:10 <lilstevie> why would you write the kernel over the rootfs :p
Dec 09 04:10:26 <twb> Well because 8 is what you're doing in olife script
Dec 09 04:10:36 <lilstevie> yeah but that is writing the rootfs
Dec 09 04:10:47 <twb> oh right
Dec 09 04:13:26 <twb> That didn't seem to help
Dec 09 04:14:11 <lilstevie> what happened
Dec 09 04:14:21 <lilstevie> same thing, or something else
Dec 09 04:14:56 <twb> same thing
Dec 09 04:15:28 <lilstevie> hm
Dec 09 04:22:25 <lilstevie> do it to 5 and boot recovert
Dec 09 04:22:28 <lilstevie> recovery*
Dec 09 04:22:31 <twb> wtf I hit reboot and it just displayed linux for a second
Dec 09 04:22:51 <twb> So it had booted the kernel but not drawn anything onscreen
Dec 09 04:23:16 <twb> yeah, it was oopsing
Dec 09 04:23:22 <lilstevie> ah
Dec 09 04:23:24 <lilstevie> ^^
Dec 09 04:24:30 <twb> somethign about not syncing VFS
Dec 09 04:25:22 <twb> unable to mount root filesystem
Dec 09 04:37:27 <twb> if I pick dualboot and ubuntu default, then I get the thing you described where linux starts and oopses onscreen
Dec 09 04:38:36 <twb> Then if I bounce it again it comes up normally, and resize2fs's and everything
Dec 09 04:38:45 <lilstevie> hm
Dec 09 04:39:33 <twb> my guess is config/linux.cfg and boot/purelinux.cfg don't line up somehwere
Dec 09 04:39:38 <TheMuso> I wonder whether Linux would still boot if some of the fat was trimmed from the initramfs when in the default boot configuration.
Dec 09 04:40:10 <twb> TheMuso: strictly the ramdisk isn't needed at all
Dec 09 04:40:20 <TheMuso> twb: I know that.
Dec 09 04:40:41 <TheMuso> twb: But the initramfs sets up framebuffer stuff, runs jasper bits, etc.
Dec 09 04:42:17 <twb> haha, it's been in D for >120 seconds, the kernel guard just said
Dec 09 04:42:34 <twb> "kinteractiveup" has
Dec 09 04:43:39 <lilstevie> TheMuso: have you written anything up yet for that blueprint
Dec 09 04:44:15 <twb> TheMuso: if you want to remove plymouth from ramdisk I won't object ;-)
Dec 09 04:46:35 <twb> lilstevie: during oem, what is the username and password?  It used to be oem/oem, but this doesn't appear to be the case here
Dec 09 04:46:51 <lilstevie> stuffed if I know
Dec 09 04:46:57 <twb> (I need to know so I can run "ip a" and find out the wifi MAC address, since wifi here pegs PSKs to MACs)
Dec 09 04:47:02 <twb> hum
Dec 09 04:47:07 <lilstevie> ubiquity is autorun
Dec 09 04:48:01 <twb> yeah but ubiquity prompts for a PSK without telling me what the MAC address is, so I can't give it the PSK
Dec 09 04:48:33 <twb> I just skipped wifi for now
Dec 09 04:48:40 <lilstevie> well then do wifi once booted :p
Dec 09 04:48:58 <lilstevie> like post ubiquity
Dec 09 04:49:08 <twb> I'm used to network installs where you can't :-)
Dec 09 04:59:51 <TheMuso> lilstevie: Beyond actually adding the blueprint, not yet. Hopefully this weekend. Why whats up?
Dec 09 05:08:32 <lilstevie> was just wondering :p
Dec 09 05:42:54 <twb> lilstevie: how do you get keyboard repeat working?
Dec 09 06:01:25 <twb> lilstevie: ok, excitingly even though I was happily running ubuntu and did ubiquity and rebooted and such, after I switched into prime and back, ubuntu kernel detected the ramdisk was an incomplete write, and then oopsed
Dec 09 06:01:57 <twb> lilstevie: THAT makes me think that maybe the ramdisk is wider than the partition its on, but it happens to work until you run android which overwrites some of the overlapping blocks.  or something.
Dec 09 06:08:28 <lilstevie> no
Dec 09 06:08:35 <lilstevie> it is bootloader space
Dec 09 06:08:56 <lilstevie> it works if kernel is in recovery position but not in main
Dec 09 07:28:01 <twb> That hurts my brain
Dec 09 08:01:38 <twb> If I pick the first option (dual boot, prime default), jasper seems to want to resize the root filesystem *every* boot
Dec 09 08:41:45 <twb> lilstevie: I'm going home now.  I'm a hard-code bash-fu weenie, so feel free to ping me if you want someone to wangle those olife scripts
Dec 09 12:41:31 <ogra_> doko, someone in #ac100 just complained that python2.7 segfaults on armhf, is that known ?
Dec 09 12:44:13 <doko> ogra_, extension or core code?
Dec 09 12:44:35 <ogra_> he claims the package cant execute bytecode compilation from its postinst
Dec 09 12:44:44 <ogra_> seems core code
Dec 09 12:45:06 <ogra_> he said that 1.5h ago, i only saw it now, i pinged him
Dec 09 12:45:46 <ogra_> i'm also not sure if he doesnt use a chroot or if thats the hf ac100 image
Dec 09 12:46:44 <ogra_> (hf chroots seem to behave weird if /proc is mounted ... )
Dec 09 12:51:49 <infinity> Err.
Dec 09 12:51:50 <infinity> No.
Dec 09 12:51:54 <infinity> They don't.
Dec 09 12:52:08 <ogra_> they did here
Dec 09 12:52:12 <ogra_> several times
Dec 09 12:52:26 <infinity> You mean procps upgrades killing your system?
Dec 09 12:52:36 <infinity> That's not "hf chroots misbehaving with proc mounted".
Dec 09 12:52:42 <ogra_> that too, i had two other incidents where it affectzed the host
Dec 09 12:52:55 <infinity> Well, any chroot can affect the host through proc.
Dec 09 12:53:02 <infinity> Not an hf thing.
Dec 09 12:53:10 <ogra_> sure, but usually that doesnt mean i need to reboot :)
Dec 09 12:53:43 <infinity> The procps thing is not hf-specific either, I suspect.
Dec 09 12:53:48 <infinity> I just haven't cared to look at it.
Dec 09 12:54:29 <ogra_> well, i have never seen that on other setups
Dec 09 12:55:00 <infinity> Anyhow, python not being able to execute its postinst is pretty clearly not true, since it happens on nearly every build on the buildds..
Dec 09 12:55:11 <infinity> So, there's something more subtle going on there.
Dec 09 12:55:13 <ogra_> for 2.7 ?
Dec 09 12:55:20 <infinity> 2.7 is our default python.
Dec 09 12:55:21 <infinity> So, yeah.
Dec 09 12:55:44 <ogra_> hmm, intresting
Dec 09 12:55:45 <infinity> Any package that build-deps on python (which is, well, lots of them), python2.7 gets installed.
Dec 09 12:56:03 <ogra_> well, then i guess that guy simply has a broken setup or some such
Dec 09 12:56:09 <ogra_> i asked him to file a bug
Dec 09 12:56:12 <infinity> Or a dying machine.
Dec 09 12:56:29 <infinity> If he can reproduce the same segv every time, then it's worth looking into.
Dec 09 12:56:39 <infinity> But still might be something with the ac100 kernel or some such.
Dec 09 12:57:26 <ogra_> well, i installed ubiquity b-deps yesterday in my chroot ... that should definitely install 2.7 alongside then
Dec 09 12:57:31 <ogra_> and i had no errors
Dec 09 12:57:55 <ogra_> its likely that he uses one of the early -core tarballs or some such
Dec 09 12:58:07 <ogra_> and didnt upgrade
Dec 09 13:10:07 <infinity> Should have been fine back then too.
Dec 09 13:10:17 <infinity> If python had been broken at any point in the bootstrap, I would have known.
Dec 09 13:10:21 <infinity> Well, broken to that extent.
Dec 09 13:10:22 <ogra_> k
Dec 09 13:10:28 <infinity> I'm sure it's slightly broken somewhere. ;)
Dec 09 13:10:34 <infinity> All software is.
Dec 09 13:10:39 <ogra_> well, we'll see what he says (if he answers or writes the bug)
Dec 09 18:07:17 <MMlosh> How does one use the USB OTG   port on ubuntu oneiric?  (device mode)
Dec 09 18:09:33 <jjardon> Hi, I have problems compiling eglibc in my ARM board. This is the error message: http://paste.ubuntu.com/765163/
Dec 09 18:10:11 <jjardon> I already set CFLAGS="-fno-stack-protector -U_FORTIFY_SOURCE" Any another idea?
Dec 09 18:14:12 <infinity> jjardon: I suppose asking why you don't use the packaged version would be a stupid question?
Dec 09 18:14:51 <infinity> jjardon: (And your CFLAGS pretty clearly aren't making it there)
Dec 09 18:18:10 <jjardon> infinity: mmm, strange, I export the CFLAGS environment var and I get the same result
Dec 09 18:18:54 <infinity> I assume they're being reset by the Makefiles.
Dec 09 18:19:10 <infinity> Still, why are you building eglibc at all?
Dec 09 18:20:25 <jjardon> infinity: playing with lfs
Dec 09 18:21:01 <infinity> Ahh, so not really an Ubuntu question. ;)
Dec 09 18:21:26 <infinity> Anyhow, in the eglibc packages, we work around the upstream Makefiles being draconian about CFLAGS by cheating.
Dec 09 18:22:11 <infinity> We set CC="gcc-4.6 -fno-stack-protector -U_FORTIFY_SOURCE" CXX="g++-4.6 -fno-stack-protector -U_FORTIFY_SOURCE"
Dec 09 18:22:21 <jjardon> infinity: no, not really ;) . I was wondering if the ubuntu-linaro compiler was setting any special flag or something
Dec 09 18:22:26 <infinity> (ie: passing the flags as part of the compiler name instead)
Dec 09 18:22:58 <jjardon> oo, I'll try that
Dec 09 18:24:16 <ogra_> janimo, could you take a look if we could get teh fix for bug 861296 into the ac100 oneiric package ?
Dec 09 18:24:20 <ubot2> Launchpad bug 861296 in linux-ti-omap4 "mmap fails to allocate 2030Mb heap on ARM" [Undecided,Fix committed] https://launchpad.net/bugs/861296
Dec 09 18:25:53 <shadeslayer> lilstevie: no luck on getting ubuntu to boot on the transformer? :(
Dec 09 18:26:00 <shadeslayer> ( SBK v2 )
Dec 09 18:32:49 <MMlosh> How does one use the pandaboard's USB OTG   port on ubuntu oneiric?  (device mode)  Loading g_ether does not seem to be enough
Dec 09 18:38:29 <GrueMaster> infinity: Any progress onlibc6
Dec 09 18:38:58 <infinity> GrueMaster: The netisnt issue?  Haven't had a chance to test yet.
Dec 09 18:39:27 <GrueMaster> well, last build still failed libc6-udeb
Dec 09 18:39:43 <GrueMaster> uInitrd was fine though.
Dec 09 18:39:44 <infinity> Yeah, I know.  Getting to it.
Dec 09 18:48:58 <doko> infinity, did you see my message about happy being unhappy?
Dec 09 18:49:36 <infinity> doko: Yeahp, it's building.
Dec 09 18:51:05 <doko> thanks
Dec 09 18:56:51 <infinity> GrueMaster: Oh, FFS.
Dec 09 18:57:10 <GrueMaster> ?
Dec 09 18:57:12 * infinity looks...
Dec 09 18:58:15 <infinity> -rw-r--r-- root/root     93484 2011-12-06 16:45 ./lib/arm-linux-gnueabihf/ld-2.13.so
Dec 09 18:58:28 <infinity> Lack of executable bits.
Dec 09 18:59:38 <infinity> I could just back out my path change from eglibc, since I fixed that in d-i anyway...
Dec 09 19:03:31 <parin1> i just got a pandaboard what should be the status of LED1 and LED2 when you boot?
Dec 09 19:03:34 * infinity tries to sort out how that's happening...
Dec 09 19:03:46 <parin1> i am not getting anything on console neither on display
Dec 09 19:04:11 <parin1> SD card booting from ubuntu 11/05 netbook prebuilt image
Dec 09 19:04:19 <parin1> 11.04
Dec 09 19:04:23 <infinity> parin1: Nothing on serial?  Wiggle the card or try another.
Dec 09 19:04:42 <infinity> parin1: It very unhelpfully does precisely nothing if it doesn't think there's an SD in the slot.
Dec 09 19:04:49 <parin1> nope nothing on serial
Dec 09 19:05:15 <parin1> i am using eclipse Terminal plugin not the minicom
Dec 09 19:05:24 <parin1> whish should not matter i think
Dec 09 19:05:50 <parin1> i am trying other card
Dec 09 19:06:16 <parin1> but what should be the stutus of LEDs in a normal situation?
Dec 09 19:09:31 <infinity> I don't recall what they do initially on boot.
Dec 09 19:09:43 <infinity> Looks like both come on.
Dec 09 19:10:02 <infinity> If there's no card in, only 2 comes on.
Dec 09 19:12:18 <parin1> ok now i insetred the card, plugged the power in and pressed the power on button but still nothing
Dec 09 19:12:39 <parin1> LED2 comes on and goes off
Dec 09 19:13:01 <parin1> LED1 isnt turning on
Dec 09 19:13:56 <parin1> i pressed power button one more time no LED2 is on
Dec 09 19:14:02 <parin1> LED1 is off
Dec 09 19:14:09 <parin1> but not getting anything
Dec 09 19:14:14 <parin1> any idea?
Dec 09 19:19:17 <infinity> You don't even need to press the power button.  Just card then plug is enough.
Dec 09 19:19:36 <infinity> If LED2 is blinking out like that, I suspect it thinks there's nothing worth looking at on the card.
Dec 09 19:19:45 <janimo> ogra_, we do not have it yet, I pinged upstream about it too
Dec 09 19:20:10 <infinity> janimo: Locally patch it into your upcoming 3.x release? :)
Dec 09 19:20:13 <janimo> I think we only need it for precise though?
Dec 09 19:20:26 <janimo> infinity, that too if upstream does not put it in their 3.0 tree :)
Dec 09 19:20:38 <infinity> janimo: I don't think it's dreadfully necessary to backport it for a "community" kernel, but we did do so for all the supported ones.
Dec 09 19:22:23 <janimo> infinity,I figured it is not that important a bug to have another oneiric upload for it
Dec 09 19:23:00 <infinity> janimo: No, but maybe queue it up if there are other things that need SRUing.
Dec 09 19:23:18 <infinity> janimo: But, really, I supect you're not even doing security support on that kernel, so...
Dec 09 19:23:26 <janimo> I not so secretly hope we no longer upload SRU for ac100 kernel, unless critical security issues
Dec 09 19:23:40 <janimo> it works ok so far and people are not complainig
Dec 09 19:23:56 <janimo> the thing which do not work are minor (headphone mic etc) but those are not working upstream either yet
Dec 09 19:24:38 <janimo> the last SRU did not get even one tester even though there was a call or two asking for it, so I think people are ok with what they have and not falling over to get new hotness
Dec 09 19:26:03 <infinity> I don't much care, as long as things kinda work.
Dec 09 19:26:17 <infinity> Security support would be nice, but I also plan to replace oneiric on my ac100 with precise really soon now.
Dec 09 19:26:27 <infinity> So... Will I get security support from you on precise? ;)
Dec 09 19:28:29 <janimo> infinity, heh, let me think before I decide if this is a trap question or not ok?
Dec 09 19:28:39 <infinity> (It is)
Dec 09 19:28:56 <janimo> if we get the port in good shape to be more than a community thing, we should probably have SRUs for it
Dec 09 19:29:19 <infinity> "More than a community thing" meaning?
Dec 09 19:29:25 <infinity> It'll never be more than a community thing. :P
Dec 09 19:29:42 <janimo> although since this is a space of arm/netbook tablets where the ac100 will look stone age in 2 years I am not sure people will care about updates for too long
Dec 09 19:29:55 <infinity> Canonical's not gong to put any official support behind a subarch aimed at hardware that isn't available.
Dec 09 19:30:01 <infinity> Although.
Dec 09 19:30:14 <janimo> well, more than it is now, a bit more poliesh and with more users, in that regard
Dec 09 19:30:29 <infinity> lilstevie and I were saying the other day that changing the ac100 subarch to a tegra subarch might not be an awful idea, if we can make the same kernel boot on a few devices.
Dec 09 19:30:42 <janimo> that would indeed make a lot of sense
Dec 09 19:31:01 <infinity> (Might be limited to tegra2, which still makes it DOA, but just maybe a unified tegra2/3 thing is possible?)
Dec 09 19:31:29 <janimo> the 'One ARM kernel to boot them all' is still far away I guess. Not sure what subarchs linaro is targetting with that (if still the plan indeed)
Dec 09 19:31:44 <infinity> Well, it relies on two things.
Dec 09 19:31:56 <infinity> The first being Devicetree/ACPI on all target devices.
Dec 09 19:32:01 <janimo> no idea how the tegra3 differs from t2 for such a kernel to be possible. Would be nice of course
Dec 09 19:32:09 <infinity> The second being no more driver conflicts between all the source trees. :P
Dec 09 19:32:16 <infinity> (ie: so you can have one source tree)
Dec 09 19:32:47 <infinity> Given nvidia's engineering practices with GPUs, I'd be shocked if tegra3 couldn't boot on tegra2 kernels.
Dec 09 19:32:55 <infinity> But then again, it's probably a whole different set of engineers.
Dec 09 19:33:16 <infinity> (I still love that the same drivers work from Riva TNT all the way to GeForce FancyPants 2011)
Dec 09 19:33:26 <infinity> Well, except for bitrot.
Dec 09 19:34:13 <janimo> infinity, same drivers? I thought there were about 3 deb packages for different eras of NV chipsets? But as usual I may misremember
Dec 09 19:35:38 <infinity> janimo: There are, but that's only because they drop "official" support for old GPUs every once in a while so they don't have to keep testing and tweaking for dead hardware they don't care about.
Dec 09 19:36:21 <infinity> janimo: The oldest driver will still init the newest card (if you jam in the PCI IDs), just won't know all the extensions, and the newest driver will still drive the oldest card, it just might be buggy due to bitrot and lack of testing/caring.
Dec 09 19:36:56 <janimo> I'd like to think  the lack of love for L4T is because they work on tegra3 support and will release together, and not just because they couldn't care less for linux
Dec 09 19:37:14 <janimo> infinity, that is impressive if so, had no idea
Dec 09 19:37:28 <janimo> but I do not want to image how that code must look like
Dec 09 19:37:34 <janimo> imagine
Dec 09 19:37:51 <infinity> The code's reasonable, except for the TNT compat (which they did actually drop completely at one point).
Dec 09 19:37:58 <MMlosh> ogra_,  I am not sure if you're the right one to ask..   who might know how to use the pandaboard as a usb device?  loading g_ether is not enough.  and I apologize again for the highlight..
Dec 09 19:38:06 <infinity> So, I suppose I should say GeForce GTS -> GeForce now (but that's still 11 years of GPUs?)
Dec 09 19:39:30 <infinity> janimo: When they come up with shiny new ways to do old things, they often toss in a bit of a translation layer in microcode instead of in the drivers.  One of the things that happens when they drop support for old GPUs is dropping support for those translation interfaces and writing to the newer instructions.
Dec 09 19:39:53 <infinity> janimo: But, like I said, the core ISA never changes much.  Think of it like x86-for-graphics (which actually isn't far off, sadly).
Dec 09 19:40:05 <infinity> janimo: Stupidly complex, very extensible, and remarkably backward-compatible.
Dec 09 19:40:20 <janimo> hmm, they do not change the core ISA even with such changes in hw? impressive too
Dec 09 19:45:41 <infinity> janimo: They took a very Intel approach to the whole thing.  Think of the Riva128 and RivaTNT as the 8088 and 80286 (ish).  The GeForce was their "80386", and much like Intel, they decided that was good enough, and just kept extending the ISA after that instead of breaking it.
Dec 09 19:46:35 <infinity> janimo: Which was pretty different from how most other video chip vendors were doing things at the time.  And probably led to their rapid iterations and World Domination(tm) in the space for a while until ATI caught on and started doing similar things.
Dec 09 19:51:15 <infinity> GrueMaster: Found and fixing your bug.  Needs yet another eglibc upload.  FML.
Dec 09 19:51:49 <GrueMaster> Figrues.  Thanks.  Let me know when it goes through.
Dec 09 19:52:23 <GrueMaster> I thought it might have something to do with the udeb change you had made earlier.
Dec 09 19:53:28 <infinity> Sort of, yeah.  All passes do a find | chmod +x run to make sure ld.so is excutable.
Dec 09 19:53:44 <infinity> For the normal passes, that find was fixed to scan subdirectories.  For udebs, no one made that change.
Dec 09 19:53:49 <infinity> So, no +x on ld.so.
Dec 09 20:02:22 <infinity> GrueMaster: Fixing a couple of other eglibc bugs while I'm in there.  And it takes forever to build anyway, so you wouldn't have it by EOD even if I uploaded now.  But you should have working netinst by Monday.
Dec 09 20:03:08 <GrueMaster> Ok.  Cool.
Dec 09 20:49:14 <mksh> hi, can someone who has precise/arm{el,hf} run a test for me?
Dec 09 20:49:34 <mksh> i've read the mksh build logs and am not fully sure about the regression testsuite results
Dec 09 20:49:42 <mksh> (or just gimme a shell)
Dec 09 20:54:17 <mksh> or if there’s something like debian’s porterboxen, tell me where ☺
Dec 09 21:50:50 <infinity> lynx: The test suite seemed to have run fine...?
Dec 09 21:51:41 <infinity> lynx: Anyhow, I can help a bit later today.  I'm in the middle of fixing my clutch right now. :P
Dec 09 22:05:20 <lynx> it actually did not run at all, for mksh-static
Dec 09 22:05:34 <lynx> thanks, if I'm still around later tell me
Dec 09 23:50:51 <lilstevie> janimo: Tegra2 and Tegra3 are very similar at a core level, just the Tegra3 has 4 of them,
Dec 10 01:19:16 <infinity> lynx: I'm back, if you're still needing help.
Dec 10 01:58:30 <Netham45> Anyone know what the username/pass is for the AC100 images?
Dec 10 01:58:50 <Netham45> (https://wiki.ubuntu.com/ARM/TEGRA/AC100)
Dec 10 02:03:16 <infinity> Netham45: There isn't one unti you've booted the installer.
Dec 10 02:04:05 <infinity> Netham45: If you follow the instructions on the page, on first boot, you'll end up (eventually) in a graphical installer that asks you to create a users.
Dec 10 02:04:08 <infinity> s/users/user/
Dec 10 02:04:25 <Netham45> I'm not on an AC100 but another tegra device
Dec 10 02:04:48 <infinity> Okay... And?
Dec 10 02:04:53 <infinity> That image is an installer image.
Dec 10 02:05:13 <infinity> If you just want a rootfs, try ubuntu-core.
Dec 10 02:05:33 <infinity> (which you'll have to manually configure as you want, but it at least won't have an installer in it that you won't be running)
Dec 10 02:08:51 <Netham45> There's an alternate installer image that'd normally install this one, apparantly.
Dec 10 02:09:30 <Netham45> Okay, I'll just make an acc't on my laptop for the image before I reflash it.
Dec 10 02:11:01 <Netham45> I'm being really confusing, aren't I.
Dec 10 02:11:18 <infinity> Perhaps, but that's alright. :P
Dec 10 02:11:42 <Netham45> http://cdimage.ubuntu.com/releases/11.10/release/ubuntu-11.10-preinstalled-desktop-armel+ac100.tar.gz < Downloaded that and flashed to my tablet, an Acer Iconia A500. That's meant to be installed through that installer, but I just extracted so it got flashed w/o any accounts.
Dec 10 02:12:07 <Netham45> So I need to mount my image on my PC and make an acc't and put the wifi drivers on and it should all be good
Dec 10 02:12:15 <infinity> Yeah, as I said, the instructions on the page point to needing the actual boot image as well.
Dec 10 02:12:43 <Netham45> I have it booting, it just only has a 'Guest' user that obviously has no root access.
Dec 10 02:12:48 <infinity> That said, you could run oem-config on that image on first boot and have it properly "install".
Dec 10 02:13:36 <infinity> Just touch "/var/lib/oem-config/run" in that image before you flash it.
Dec 10 02:13:43 <infinity> And on first boot, you should get the installer running.
Dec 10 02:13:58 <Netham45> Okay. That installer won't muck with my partitions, will it
Dec 10 02:13:59 <infinity> Which will set up a user "correctly", among other things.
Dec 10 02:14:00 <Netham45> ?
Dec 10 02:14:12 <Netham45> heh, I was just going to chroot and adduser
Dec 10 02:14:17 <Netham45> (or is it useradd)
Dec 10 02:14:21 <infinity> adduser.
Dec 10 02:14:27 <infinity> useradd is the lower-level utility.
Dec 10 02:14:44 <infinity> But you'll need to also add yourself to a few groups if you want to mimic what the installer does.
Dec 10 02:15:04 <Netham45> adduser, add to admin group, right?
Dec 10 02:15:15 <Netham45> (or whatever the default sudoers group is)
Dec 10 02:15:30 <Netham45> y'know, the installer sounds easier, I'ma just use that.
Dec 10 02:15:33 <infinity> adm, dialout, cdrom, plugdev, lpadmin, admin.
Dec 10 02:15:57 <infinity> The installer might fail due to you not actually using the ac100 kerel (at least, I assume you're not?)
Dec 10 02:16:01 <infinity> But I guess we'll see.
Dec 10 02:16:16 <Netham45> No, I'm not.
Dec 10 02:20:07 <Netham45> Installer started.
Dec 10 02:21:30 <infinity> It may well die if it tries to do anything kernel-related.
Dec 10 02:21:44 <infinity> Unless you removed linux-\* from the image first.
Dec 10 02:21:51 <infinity> Which I probably should have mentioned. :P
Dec 10 02:22:11 <infinity> (I'm not sure what the installer will do with no kernel packages installed, but I'm hoping the answer is "nothing").
Dec 10 02:22:26 <infinity> It may not break anyway, though.
Dec 10 02:22:53 <Netham45> Worst-case if it tries to overwrite one of the kernels I'll have another to boot to.
**** ENDING LOGGING AT Sat Dec 10 02:59:56 2011