**** BEGIN LOGGING AT Sun Sep 18 02:59:57 2011
Sep 18 03:01:24 <twb> I mean I run the binary the "make" compils
Sep 18 03:01:30 <twb> *compiles
Sep 18 03:08:30 <lilstevie> how are you "running" it, the binary that make compiles is a bootloader, not a userland executable
Sep 18 03:09:16 <twb> file said it was an ELF executable
Sep 18 03:10:12 <twb> It also made a u-boot.bin or so, which I presume is the actual bootloader
Sep 18 03:14:57 <lilstevie> well yeah of course it is an elf
Sep 18 03:15:06 <lilstevie> then it gets stripped
Sep 18 03:16:14 <lilstevie> u-boot the elf is the base, which then gets stripped to become u-boot.bin, and what ever moto requirements are to become u-boot.srec
Sep 18 03:16:32 <twb> oh, ok
Sep 18 03:17:08 <twb> I am used to extlinux where e.g. there is a program extlinux that helps install the bootloader
Sep 18 03:25:20 <twb> 18:25 <twb> So now that I have a kernel and a rootfs and u-boot, how do I actually get u-boot onto the device?
Sep 18 03:30:26 <Martyn> twb : Which device?
Sep 18 03:30:33 <Martyn> u-boot installs differently onto different hardware
Sep 18 03:30:47 <twb> Martyn: tf101
Sep 18 03:31:14 <Martyn> Asus transformer?
Sep 18 03:31:22 <twb> yes
Sep 18 03:31:36 <Martyn> http://androidroot.mobi/technical/asus-eee-pad-transformer-tf101-root-cwm-recovery/
Sep 18 03:31:49 * twb reads
Sep 18 03:32:04 <Martyn> To install/reflash the tf101, you need to use it's own recovery tools
Sep 18 03:32:17 <twb> I'm already using nvflash
Sep 18 03:32:21 <Martyn> which involves flashing u-boot using MMC
Sep 18 03:32:28 <twb> http://cyber.com.au/~twb/doc/tf101.txt <– my notes
Sep 18 03:33:11 <Martyn> This is the other guide you wil need:
Sep 18 03:33:12 <Martyn> http://technoreview.net/2011/06/asus-transformer-ubuntu.html
Sep 18 03:33:52 <twb> Note that android is long gone
Sep 18 03:34:04 <twb> I already have ubuntu booting, but using the crappy asus bootloader
Sep 18 03:35:17 <Martyn> have you already ported u-boot for the asus transformer?
Sep 18 03:35:35 <Martyn> I'm not aware of board support for the asus at the moment in u-boot
Sep 18 03:39:04 <twb> I'm using a fork from muromec to support it
Sep 18 03:44:28 <Martyn> You may have to jtag it into place
Sep 18 03:44:40 <Martyn> because I don't know of any generic tool that can flash u-boot into place on the tf101
Sep 18 03:45:02 <twb> Hum
Sep 18 03:45:11 <twb> I know it's possible, at least, lilstevie is using it
Sep 18 03:46:02 <lilstevie> nvflash
Sep 18 03:46:14 <twb> lilstevie: do i just write it to the EBT partition?
Sep 18 03:46:38 <lilstevie> twb, you will need to make a few small edits
Sep 18 03:46:53 <lilstevie> MBR needs to be at a certain spot
Sep 18 03:47:15 <lilstevie> and you should edit include/configs/ventana.h to reflect different partition numbers
Sep 18 03:50:43 <twb> Also where do I tell it to try booting from microsd first?
Sep 18 04:02:20 <lilstevie> I told you about that
Sep 18 04:02:26 <lilstevie> one of the limitations with u-boot
Sep 18 04:02:31 <lilstevie> no microsd
Sep 18 04:08:01 <twb> Sorry, I must've forgotten
Sep 18 04:08:11 <twb> SD or USB, then
Sep 18 04:10:28 <lilstevie> then that is the default action
Sep 18 04:11:00 <lilstevie> SD/USB/eMMC
Sep 18 04:11:56 <twb> Good-o
Sep 19 00:12:53 <brokencodes> hello...
Sep 19 00:13:03 <brokencodes> still persuing login prompt... http://paste.ubuntu.com/692648/
Sep 19 00:13:20 <brokencodes> it stops RIGHT there, next action suppose to be getty, never gets there
Sep 19 00:13:22 <brokencodes> or
Sep 19 00:13:26 <brokencodes> getty dies?
Sep 19 00:34:46 <brokencodes> it boots fine in qemu-system-arm, with its kernel, but not with the target kernel for this board, and they are the same processor / variant
Sep 19 00:34:51 <brokencodes> only getty seems to fail
Sep 19 00:37:05 <tmzt> qemu won't boot your board's kernel unles you add support to qemu for your hardware
Sep 19 00:37:18 <brokencodes> you thinking backwards
Sep 19 00:37:23 <brokencodes> qemu boots fine
Sep 19 00:37:29 <brokencodes> board stops at getty
Sep 19 00:38:15 <phh> you're sure you're not just doing getty at the wrong place ? :D
Sep 19 00:38:22 <phh> i mean wrong serial port
Sep 19 00:39:24 <brokencodes> how to redirect getty?
Sep 19 00:39:28 <phh> ????
Sep 19 00:39:30 <phh> wat ?
Sep 19 00:39:47 <brokencodes> kernel bootargs includes console=/dev/ttyS0 115200n81
Sep 19 00:40:29 <phh> ah i forgot ubuntu no longer uses inittab for getty ...
Sep 19 00:40:47 <brokencodes> debian does same damn thing
Sep 19 00:40:53 <brokencodes> stops at getty
Sep 19 00:41:10 <phh> brokencodes: well what's the getty command line on debian ?
Sep 19 00:41:49 <brokencodes> I dont know
Sep 19 00:41:53 <phh> OKAY
Sep 19 00:41:55 <mikejf> brokencodes: What does the 'exec' line of '/etc/init/ttyS0.conf' say?
Sep 19 00:41:59 <phh> how do you know if it ever tries to start ?
Sep 19 00:42:02 <brokencodes> I would have to trace the initscripts
Sep 19 00:42:36 <tmzt> it's upstart isn't it?
Sep 19 00:42:42 <brokencodes> give me a min, I go back inside, hook up the devboard, we can investigate it...
Sep 19 00:42:43 <phh> mikejf: /etc/init ? http://doc.ubuntu-fr.org/console_serie is saying /etc/event.d :(
Sep 19 00:43:01 <phh> tmzt: that's why i meant it's easier on debian :p
Sep 19 00:43:24 <phh> good old inittab ..
Sep 19 00:43:41 <brokencodes> ok, then we will stick with debian for now
Sep 19 00:44:16 <phh> brokencodes: mikejf just gave you the path for ubuntu ...
Sep 19 00:44:16 <brokencodes> hooking upthe debian drive,and reloading the kernel image over tftp, saving to nand
Sep 19 00:49:09 <brokencodes> added another line to inittab... waiting to see result
Sep 19 00:49:42 <brokencodes> rebooting
Sep 19 00:51:38 <brokencodes> I have a login prompt!
Sep 19 00:51:39 <brokencodes> YAY
Sep 19 00:51:44 <brokencodes> thank you
Sep 19 00:54:01 <phh> .
Sep 19 00:59:05 <brokencodes> what is " . "
Sep 19 00:59:06 <brokencodes> ?
**** ENDING LOGGING AT Mon Sep 19 02:59:57 2011