[05:15] <lilstevie> gildean, you about?
[08:43] <sefo> hi
[08:43] <sefo> anyone have a hercules ecafe slim with ubuntu installed?
[08:43] <sefo> Its netbook have a modified ubuntu thats i dont like
[08:43] <sefo> this use uboot for boot kernel but i dont know how works it for install new ubuntu
[09:41] <IamTrying> System is crashed??? ASUS Eee pad transformer i have (in tried to install Ubuntu).  e.g: http://i.imgur.com/E9o16.png
[09:42] <IamTrying> I copied also the file rootfs.ext2 but why its showing that?
[09:42] <lilstevie> IamTrying: which install is that
[09:43] <lilstevie> clearly the outdated one from jhinta actually
[09:43] <lilstevie> IamTrying: m.xda-developers.com/showthread.php?p=19731842
[09:43] <lilstevie> hm
[09:43] <lilstevie> http://forum.xda-developers.com/showthread.php?p=19731842 even
[09:44] <IamTrying> lilstevie, i did this one, i have splash screen but not booting to ubuntu http://eeepadhacks.net/transformer-hacks/how-to-install-native-ubuntu-on-eeepad-transformer/
[09:45] <IamTrying> Once i boot > I see the splash penguin icons > And then i get > http://i.imgur.com/E9o16.png
[09:45] <lilstevie> that information is outdated
[09:47] <IamTrying> lilstevie, should i be doing then OLiFE? But is that same way?
[09:47] <lilstevie> OLiFE is not quite the same, it uses the internal emmc
[09:48] <IamTrying> OLiFE.tar.gz , OLiFE-Prime-Edition.tar.gz , Ubuntu.img.gz (3 files it got).
[09:49] <lilstevie> OLiFE-Prime-Edition has a rom included
[09:49] <lilstevie> OLiFE.tar.gz requires you to supply a rom, and the ubuntu.img.gz
[09:50] <IamTrying> What confusing me is that. I use nvflash but i do not have any external MicroSD cards will Olife do that?
[09:50] <IamTrying> Using SSHDroid i included the rootfs.exe2 files in /sdcard/Ubuntu/rootfs.ext2
[09:51] <IamTrying> nvflash if i can tell to look into that directory i think it should work.
[09:51] <lilstevie> not the same
[09:52] <lilstevie> using olife it reflashes the entire emmc, including /sdcard
[09:52] <lilstevie> and reparitions it so ubuntu has its own partition
[09:52] <lilstevie> also, with that kit you used, it requires an external SDcard
[09:52] <lilstevie> that is why you are getting that error
[09:53] <IamTrying> I got it, but i do not have MicroSD card, i want to do it what i got now like not wait for SD card to buy etc.
[09:53] <IamTrying> If i use Olife
[09:53] <IamTrying> Can i at-least go back like i did with restore.sh?
[09:53] <gildean> lilstevie: just woke up, why
[09:54] <lilstevie> IamTrying: you can restore yes
[09:54] <lilstevie> gildean: I saw in the logs you upgraded compulabs modified natty to oneiric on the trimslice
[09:55] <gildean> yeah
[09:55] <lilstevie> was just wondering what you did, cause every time I try it dies horribly
[09:56] <gildean> i think it was just mostly using apt in apt the wrong way and changing the distro in sources.list
[09:56] <IamTrying> lilstevie, that is great. Just to make sure before i make mistake 1) i followed this link http://forum.xda-developers.com/showthread.php?t=1191141  2) I downloaded OLiFE-Prime-Edition.tar.gz 3) Does it have the latest Ubuntu ARM or its old?
[09:56] <gildean> then multiple upgrades and dist-upgrades
[09:57] <gildean> first upgrade, then dist-upgrade, then dist-upgrade again and then upgrade && dist-upgrade
[09:57] <gildean> iirc
[09:57] <lilstevie> fair enough
[09:57] <lilstevie> using do-dist-upgrade fails
[09:57] <lilstevie> IamTrying: it is oneiric
[09:58] <gildean> i did apt-get upgrade && apt-get dist-upgrade
[09:58] <gildean> the first upgrade and dist-upgrade fail
[09:58] <lilstevie> gildean: cool
[09:58] <lilstevie> gildean: will try it in an hour or so :)
[09:59] <lilstevie> gildean: tbh I have been considering getting a generic image running on it
[09:59] <gildean> then the second dist-upgrade worked and then the last upgrade && dist-upgrade fixed the broken ones
[09:59] <gildean> yeah, me too
[09:59] <IamTrying> Ok, that is very latest to test with.
[09:59] <lilstevie> IamTrying: I maintain that image, and installer
[09:59] <gildean> actually i made a site for it already, just haven't had time to start the project in more depth
[09:59] <lilstevie> fair enough
[09:59] <gildean> http://julkinen.salaliitto.com/trimslice/
[10:00] <lilstevie> hah I saw that the other day
[10:00] <lilstevie> pretty cool
[10:00] <IamTrying> Wow
[10:00] <lilstevie> gildean: actually I would be interested in adding trimslice support to my image for the tf
[10:00] <IamTrying> lilstevie, you are Genius
[10:01] <lilstevie> IamTrying: not really
[10:01] <IamTrying> :)
[11:41] <IamTrying> lilstevie.... , I installed the OLiFE-Prime-Edition but now its doing a loop auto reboot 1) http://i.imgur.com/gmLrs.png  2) http://i.imgur.com/4ISkR.png  without stop its like loop.
[11:42] <IamTrying> This is the steps i took https://gist.github.com/1397454
[11:46] <lilstevie> ok yeah, sorry about that, can you switch the boot order
[11:46] <lilstevie> you can do that without reflashing
[11:47] <lilstevie> by going into the update menu
[11:47] <lilstevie> there is an issue in the current kernel that doesn't allow ubuntu to be default
[11:47] <lilstevie> only secondary
[11:48] <IamTrying> lilstevie, https://gist.github.com/1397454    So i go to APX mode and reinstall and choose secondary?
[11:49] <lilstevie> or go into the update menu
[11:49] <IamTrying> Yes i am now in Update menu> its saying 2. Ubuntu/Linux kernel 4. Ubuntu Rootfs
[11:49] <IamTrying> Should i take 2?
[11:49] <lilstevie> so yeah
[11:50] <lilstevie> option 1 and 2
[11:50]  * infinity is tempted to buy a TrimSlice...
[11:50] <infinity> Because my desk isn't littered with enough little ARM devices...
[11:50] <lilstevie> infinity: heh
[11:50] <IamTrying> Applied 2 asking 1. Turn device on or 2. Hold vol-down then press vol-up  ?
[11:51] <lilstevie> press 2
[11:52] <IamTrying> lilstevie, i have black screen now : https://gist.github.com/1397463
[11:53] <lilstevie> ok,
[11:53] <lilstevie> reboot the device hold vol-
[11:53] <IamTrying> Now i started. And its again those loop
[11:54] <lilstevie> and press vol+ when asked
[11:54] <IamTrying> After power-on i have same loop again: 1) http://i.imgur.com/gmLrs.png 2) http://i.imgur.com/4ISkR.png  (auto restart and loop)
[11:55] <infinity> lilstevie: Do you know off the top of your head what the odds are of us being able to do a generic tegra2 kernel that supports, say, AC100, TF101, and TrimSlice?
[11:55] <infinity> lilstevie: The idea of shipping a different kernel image for every device is really off-putting.
[11:55] <lilstevie> IamTrying: you didn't follow the instruction I just gave
[11:56] <IamTrying> i did vol+ yes
[11:56] <lilstevie> infinity: I was actually going to suggest something like that
[11:56] <lilstevie> IamTrying: you wouldn't have had that pic
[11:56] <IamTrying> lilstevie, i applied vol+ but still the same
[11:56] <lilstevie> pressing vol- white writing would have appeared
[11:56] <lilstevie> then you press vol+
[11:56] <infinity> lilstevie: Suggest away.  Better yet, give me something based on our AC100 source that works on your TF101, I'll verify that it still works on my AC100, and we'll call it good. :P
[11:57] <lilstevie> infinity: it would require patching device bootloaders though
[11:57] <infinity> lilstevie: (Lather, rinse, repeat for TS)
[11:57] <lilstevie> except for trimslice
[11:57] <infinity> lilstevie: Oh, that sounds less pleasant (the bootloader hackery).
[11:57] <lilstevie> to report a boardID
[11:57] <infinity> lilstevie: Due to AC100 and TF101 using messed-up Android boot/partition semantics, I'm assuming?
[11:57] <infinity> Oh, or just boardID?
[11:57] <lilstevie> because all tegra2 tablets seem to report ventana as the board identifier
[11:58] <infinity> We could perhaps fudge that heuristically.
[11:58] <lilstevie> maybe
[11:58] <lilstevie> that would be more plesant
[11:58] <lilstevie> infinity: using in kernel pt hacks are probably a little bit better
[11:58] <IamTrying> lilstevie,  I have first this screen 1) http://i.imgur.com/gmLrs.png  > Pressing vol- / + or vol + or only vol - just not responding its doing the same loop over and over.
[11:58] <lilstevie> the TF101 uses GPT
[11:58] <infinity> It does?
[11:59] <infinity> Curious.
[11:59] <lilstevie> IamTrying: you are still not following
[11:59] <lilstevie> infinity: yeah
[11:59] <lilstevie> GPT + forcing GPT on the commandline
[11:59] <lilstevie> IamTrying: white writing will appear on screen telling you to press volume up to boot RCK
[12:00] <lilstevie> you need to hold volume down while pushing power until that writing appears
[12:00] <infinity> Well, assuming we're dealing with factory PT schemes, then, we could just assume nvflash+MBR is ac100, nvflash+GPT is TF101, and uBoot is TrimSlice.  That all falls apart when people do fun things like install uBoot on their AC100, though. ;)
[12:00] <lilstevie> then press volume up
[12:00] <infinity> I'm sure we can come up with saner ways to gently probe.
[12:00] <infinity> Or something.
[12:00] <lilstevie> heh
[12:00] <infinity> I dunno.  Something to toss around anyway.
[12:00] <lilstevie> well personally I am moving to u-boot as soon as it is more stable on the tf101
[12:00] <infinity> Three kernel images won't kill us either.  At the very least, we should generate them from the same source, so it's a bit more maintainable.
[12:01] <lilstevie> at the moment though u-boot is small enough to put the MBR at the start of "rest of flash" as per swarrens brain dump
[12:01] <lilstevie> the tf101 does a similar thing with boot blocks on emmc
[12:01] <infinity> Yeah.
[12:01] <lilstevie> that take up the first 0x38000000
[12:02] <infinity> I'd like to fast forward ~5 year to when most ARM devices boot with a sane and standardised method.
[12:02] <lilstevie> yeah
[12:02] <infinity> s/year/years/
[12:02] <lilstevie> I actually am an advocate for standardising the boot process on arm
[12:03] <infinity> I think almost everyone is.
[12:03] <infinity> But getting people to agree on what should be the standard has been a nightmare.
[12:03] <lilstevie> I am also wanting to have a minimal kernel core
[12:03] <infinity> Oddly enough, I think our largest competitor may help a lot there.
[12:03] <infinity> Cause Microsoft (quite rightly, and I wish we had the balls to do this) just refuses to work with people who don't all boot shit the same way.
[12:03] <lilstevie> that gives us room for a reasonably large kernel but most of it being modular
[12:03] <lilstevie> yeah
[12:04] <lilstevie> tbh I would be happy even if it were u-boot
[12:05] <infinity> I'd die laughing if uBoot became the standard first-stage BIOS/firmware that chained into Windows8 on ARM.
[12:05] <infinity> Given that uBoot is 95% cargo-culted linux kernel code.
[12:05] <lilstevie> heh
[12:05] <lilstevie> well I know come win8 it will be UEFI
[12:05] <lilstevie> but that is not going to be feasable for current devices
[12:05] <IamTrying> lilstevie, i did by following the screen it was saying what you mentioned. But after that now i have this screen nothing happening: http://i.imgur.com/xzy6n.png
[12:06] <infinity> Well, yes, but UEFI is a spec, not an implementation.  What actually implements it is still up in the air.
[12:06] <lilstevie> IamTrying: just wait a moment with that, it is resizing the filesystem to fit the partition
[12:06] <lilstevie> infinity: heh
[12:08] <IamTrying> WOW, lilstevie yea it works, thanks a lot Guru.
[12:13] <lilstevie> infinity: anyway, I would like to see a universal arm kernel
[12:13] <lilstevie> for more than just tegra2 as well
[12:13] <infinity> That's much further down the road.
[12:13] <lilstevie> yeah of course
[12:13] <infinity> But ACPI and/or DT will get us there some day.
[12:14] <lilstevie> solving just one cpu type is going to be enough
[12:15] <IamTrying> I do not have Keyboard, for this Device. Is there any way System configuration i can skip my username/password i can not type, and its not showing any virtual keyboard.
[12:16] <lilstevie> IamTrying: there is an option for that
[12:16] <IamTrying> I mean here: http://i.imgur.com/Imqim.png
[12:16] <lilstevie> in the menu
[12:17] <lilstevie> yeah as I said
[12:17] <lilstevie> menu option in OLiFE
[12:17] <lilstevie> activates onscreen keyboard via usb
[12:18] <IamTrying> Aha, wow i must have to, is this in the OLiFE.sh?
[12:18] <lilstevie> yes
[12:18] <IamTrying> Oh yea got it
[12:20] <IamTrying> Thanks got it. 1) https://gist.github.com/1397487 2) http://i.imgur.com/enL8j.png
[12:23] <lilstevie> just don't disconnect until you have finished initial setup
[12:24] <IamTrying> Sure, Touch keyboard is it normal? When i press wireless password: 14788 it just keeps one typing more
[12:24] <IamTrying> s/one/on
[12:24] <lilstevie> ldm and unity allow you to invoke it, but ubiquity doesn't
[12:25] <lilstevie> um, yea I have noticed that, I don't know why it happens
[12:25] <IamTrying> Maybe because i made the keyboard bigger? My finger is large and the default layout was very tiny.
[12:26] <lilstevie> no, it is random, no matter what size the keyboard is
[12:26] <lilstevie> I personally do not undock my tf101
[12:27] <IamTrying> This is horrible keyboard. I am typing username: sun and its typing suuuuuuuuuuuuuuuuuuuuuuuuuuuuuu
[12:27] <lilstevie> yeah it happens sometimes
[12:28] <lilstevie> infinity: actaully the other thing I wouldn't mind setting up is a preinstall image like what panda and beagle have, but for tegra
[13:00] <IamTrying> After installation. 1) ./adb shell 2) export DISPLAY=:0.0 && xterm ;  does not open anything is it normal?
[13:00] <IamTrying> "xterm Xt error: Can't open display: %s"
[13:01] <IamTrying> Ok it works, i needed to su s
[13:03] <lilstevie> why would you need to do that?
[13:04] <lilstevie> you can launch onboard from unity
[13:04] <IamTrying> lilstevie, i am searching a keyboard lol i dont find anymore and OLiFE is not after installation not loading that virtual keyboard.
[13:05] <lilstevie> it is called onboard
[13:05] <IamTrying> Aha wow its there, thank you.
[13:20] <IamTrying> It is almost impossible to use onboard to put the password for my Wifi: 14788. Is there any command line way i can configure this? I still can not make the internet connection because of the onBoad is randomly putting invalid numbers.
[18:38] <IamTrying> This is second boot and now its not booting anymore e.g: http://i.imgur.com/SURhE.png
[18:38] <IamTrying> How to resolve this?
[20:18] <Xase> Question... building a kernel for an omap3621 on the Nook Color, would using the default config file for the board suffice, or are there any other changes I should make, to make sure Ubuntu runs correctly?
[22:09] <robclark> btw, anyone know if there is a way to get debuild to recompile something (ie. not a clean from-scratch build)?