[00:03] <brokencodes> ok, so me asking again, how do i get a login prompt in ubuntu maveric (--seed build-essential, git, automake) in qemu-system-arm?
[00:04] <brokencodes> should I be attempting an ssh conection, or could I use the qemu console instead?
[00:04] <brokencodes> I don't understand why the login prompt never shown in the qemu console...
[00:05] <tmzt> what are you trying to do?
[00:06] <brokencodes> get to where it asks login: < insert blinky cursor here
[00:06] <tmzt> an?
[00:07] <tmzt> no, why are you booting the image in qemu, just looking for some context
[00:07] <brokencodes> and type in the username, then the password, then use qemu, as if I were actually using an arm board,
[00:07] <tmzt> okay
[00:07] <tmzt> you have to have a kernel that matches the machine you select with -M ? in qemu
[00:07] <brokencodes> because my RV926 board has an issue, where it doesn't function, probably related to the hole in the center
[00:07] <brokencodes> es
[00:07] <brokencodes> yes
[00:08] <brokencodes> I get way past the kernel loading
[00:10] <brokencodes> i used rootstock, to build ubuntu maverick, --seed build-essential, automake
[00:11] <brokencodes> last line to come up in qemu console, is init:plymouth-log main process (238) terminated with status 1
[00:11] <brokencodes> then cpu usage drops to 0, and qemu-system-arm is then a sleeping process
[00:11] <brokencodes> blinky blinky blinky blinky blinky.....
[00:12] <brokencodes> qemu started like so...
[00:13] <brokencodes> qemu-system-arm -M versatilepb -kernel vmlinuz -hda ubuntu-arm.img -m 256 -append "root=/dev/sda mem=256M ro" -cpu cortex-a9
[00:13] <brokencodes> kernel compiled for arm7l with neon / ThumbEE
[00:14] <brokencodes> tmzt, did you catch all that?
[00:15] <tmzt> yeah
[00:15] <brokencodes> So, should I repeat the question? or am I barking in the wrong tree, at the wrong room?
[00:16] <tmzt> hmm
[00:16] <tmzt> plymouth doesn't seem to like the fbdev
[00:16] <tmzt> and you aren't getting to the getty
[00:16] <brokencodes> i would guess so
[00:16] <tmzt> first thing to try is init=/bin/sh
[00:16] <tmzt> that should work
[00:16] <brokencodes> ok
[00:16] <brokencodes> brb
[00:16] <tmzt> the disable plymouth
[00:16] <tmzt> or actually
[00:17] <arcaico> hello, "/init: line 61: can't open /r/dev/console: no such file"  , Can anyone help-me?
[00:17] <tmzt> nosplash noquiet
[00:17] <tmzt> what is /r?
[00:17] <tmzt> you aren't pivoting correctly
[00:17] <tmzt> tmzt@ubuntu:~$ ls -lh /dev/console
[00:17] <tmzt> crw------- 1 root root 5, 1 2011-09-17 15:39 /dev/console
[00:18] <brokencodes> how to remove plymouth?
[00:18] <brokencodes> do I have to reseed, from rootstock?
[00:53] <dev_> thank you tmzt, got my login prompt
[02:44] <twb> lilstevie: ./u-boot segfaults both when compiled in Debian armhf chroot, and in the ubuntu armel host environment.  I wonder if the problem is that I used dtc from git instead of 1.3.0 release proper?  Oh, and strace says it segfaults before doing any syscalls at all
[02:51] <lilstevie> how would you know that u-boot segfaults 0.o
[03:00] <twb> I mean I run the binary the "make" compils
[03:00] <twb> *compiles
[03:07] <lilstevie> how are you "running" it, the binary that make compiles is a bootloader, not a userland executable
[03:08] <twb> file said it was an ELF executable
[03:09] <twb> It also made a u-boot.bin or so, which I presume is the actual bootloader
[03:14] <lilstevie> well yeah of course it is an elf
[03:14] <lilstevie> then it gets stripped
[03:15] <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
[03:16] <twb> oh, ok
[03:16] <twb> I am used to extlinux where e.g. there is a program extlinux that helps install the bootloader
[03:24] <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?
[03:29] <Martyn> twb : Which device?
[03:30] <Martyn> u-boot installs differently onto different hardware
[03:30] <twb> Martyn: tf101
[03:30] <Martyn> Asus transformer?
[03:30] <twb> yes
[03:31] <Martyn> http://androidroot.mobi/technical/asus-eee-pad-transformer-tf101-root-cwm-recovery/
[03:31]  * twb reads
[03:31] <Martyn> To install/reflash the tf101, you need to use it's own recovery tools
[03:31] <twb> I'm already using nvflash
[03:31] <Martyn> which involves flashing u-boot using MMC
[03:31] <twb> http://cyber.com.au/~twb/doc/tf101.txt <– my notes
[03:32] <Martyn> This is the other guide you wil need:
[03:32] <Martyn> http://technoreview.net/2011/06/asus-transformer-ubuntu.html
[03:33] <twb> Note that android is long gone
[03:33] <twb> I already have ubuntu booting, but using the crappy asus bootloader
[03:34] <Martyn> have you already ported u-boot for the asus transformer?
[03:35] <Martyn> I'm not aware of board support for the asus at the moment in u-boot
[03:38] <twb> I'm using a fork from muromec to support it
[03:43] <Martyn> You may have to jtag it into place
[03:44] <Martyn> because I don't know of any generic tool that can flash u-boot into place on the tf101
[03:44] <twb> Hum
[03:44] <twb> I know it's possible, at least, lilstevie is using it
[03:45] <lilstevie> nvflash
[03:45] <twb> lilstevie: do i just write it to the EBT partition?
[03:46] <lilstevie> twb, you will need to make a few small edits
[03:46] <lilstevie> MBR needs to be at a certain spot
[03:46] <lilstevie> and you should edit include/configs/ventana.h to reflect different partition numbers
[03:50] <twb> Also where do I tell it to try booting from microsd first?
[04:01] <lilstevie> I told you about that
[04:01] <lilstevie> one of the limitations with u-boot
[04:01] <lilstevie> no microsd
[04:07] <twb> Sorry, I must've forgotten
[04:07] <twb> SD or USB, then
[04:09] <lilstevie> then that is the default action
[04:10] <lilstevie> SD/USB/eMMC
[04:11] <twb> Good-o