[02:56] <twb`> Is there an easy way to determine which /usr/bin/qemu-X-static corresponds  to a "debian --print-architecture" architecture string?  e.g. armhf -> arm, amd64 -> x86_64
[02:57] <twb`> Plan B is just to copy in qemu-*-static and hope for the best.
[03:08] <tmzt> twb`: wouldn't it be -cpu as a command line option
[03:25] <twb`> Well, I'm not actually on armhf at the time, so I don't think I can ask dpkg
[03:32] <infinity> twb`: Perhaps dpkg-architecture -qDEB_BUILD_GNU_CPU?
[03:33] <infinity> twb`: Although, if you want to know without being able to run the native arm dpkg, that could be more entertaining.
[03:39] <twb`> Let me show you the actual code...
[03:40] <twb`> http://paste.debian.net/129496/  (the QemuUserEmulation bit)
[03:40] <twb`> IOW I want to know before I can execute arm code
[03:52] <infinity> twb`: dpkg-architecture -aarmhf -qDEB_HOST_GNU_CPU
[03:52] <infinity> twb`: And might want to 2>/dev/null to ignore the whining about gcc mismatches.
[03:53] <infinity> twb`: Assuming that qemu-$arch-static matches the GNU CPU types, that should do it for you.
[03:55] <twb`> Ah, thanks
[05:45] <travalas> so running ubuntu 11.04, my beagle board doesn't turn on the usb bus.  but this works fine with angstrom. thoughs?
[05:47] <infinity> travalas: Try the latest oneiric kernel.  I vaguely recall some known issues surrounding USB on beagle.
[05:48] <travalas> where would I look for that kernel?
[05:53] <infinity> travalas: http://ports.ubuntu.com/ubuntu-ports/pool/main/l/linux/linux-image-3.0.0-11-omap_3.0.0-11.17_armel.deb
[05:58] <travalas> thanks
[06:15] <twb`> lilstevie: what happens if you do "make localyesconfig" and "make localmodconfig" from inside a running TF101?
[06:16] <lilstevie> twb`: hmm
[06:16] <lilstevie> twb`: I have only done make uImage from inside a running TF101
[06:17] <twb`> You don't have to actually build the image there, that just generates the .config
[06:17] <lilstevie> hmm
[06:17] <lilstevie> well IDK
[06:17] <twb`> I do it on x86_64 and it's handy for getting mostly-right localized/hw-specific .config
[06:17] <twb`> I'd check myself but I left the TF101 at home
[06:22] <twb`> Why is both MACH_PICASSO and MACH_TF101 set?
[06:37] <lilstevie> in the 2.6.38.3 kernel it is set because the guy who did it wove tf101 stuff into picasso
[06:38] <lilstevie> not only that is it is common place on these tegra devices
[06:38] <lilstevie> the asus defconfig has both MACH_HARMONY and MACH_VENTANA set
[06:39] <twb`> Hum.
[06:39] <twb`> Kernel config is pretty overwhelming these days
[06:39] <twb`> I end up doing things like grep -r --include Kconfig
[06:39] <lilstevie> yeah
[06:39] <lilstevie> heh
[07:42] <twb> lilstevie: remind me; what doesn't work when booting via u-boot?
[07:44] <lilstevie> in the boot process or after boot
[07:45] <twb`> Whatever you were saying was needed to boot your CrOS kernel
[07:46] <lilstevie> no I mean, what is broken of u-boot or once you are in userland :p
[07:47] <twb`> either
[07:47] <twb`> both
[07:47] <lilstevie> ok, most of the u-boot env is broken
[07:47] <twb`> "What's the downside of using CrOS + u-boot"
[07:47] <lilstevie> without attaching to the serial port you have 0 interactivity with u-boot apart from boot.scr
[07:47] <lilstevie> you must use an MBR layout on the emmc
[07:48] <lilstevie> and the MBR part must start at a set address
[07:48] <twb`> That's not so bad considering I have no interaction with the default bootloader except "use LNX" vs "use SOS"
[07:48] <lilstevie> yeah well it is less
[07:48] <lilstevie> :p
[07:48] <lilstevie> cause you don't even have that
[07:48] <lilstevie> well, I mean you can run a cascase boot
[07:48] <lilstevie> so like test dock usb, dock SD emmc
[07:49] <lilstevie> µSD is broken too
[07:49] <lilstevie> u-boot does not see the card
[07:49] <lilstevie> so that is u-boots limitations set out
[07:49] <lilstevie> as for the kernel, it is mostly fine
[07:49] <lilstevie> wifi works with network manager
[07:49] <twb`> "connect serial port" as in open the case and connect to to a jumper header, or like the USB to 40-pin cable?
[07:50] <lilstevie> well I haven't traced out the serial port yet
[07:50] <lilstevie> I am certain it plumbs out on the 40pin connector somewhere
[07:50] <lilstevie> just no idea where
[07:51] <twb`> So it would mean getting a 40-pin plug and wiring that up to a 9-ping serial port?
[07:51] <twb`> *9-pin
[07:51] <lilstevie> well just 3 pins are needed
[07:51] <lilstevie> tx, rx and common ground
[07:51] <lilstevie> when I say serial, I mean UART :)
[07:51] <twb`> k
[07:52] <twb`> I could live with that if I could tell uboot to try booting off the dock's SD card first, and then fall back to the eMMC
[07:52] <twb`> That way, I could put a complete kernel and rootfs rescue image on an SD card
[07:52] <lilstevie> yeah, just build it in to your scripting
[07:52] <lilstevie> I have a small patch which uses some space on emmc for environment variables too :)
[07:52] <twb`> I've used systems that have u-boot preinstalled, I haven't installed it before tho
[07:53] <lilstevie> heh
[07:53] <twb`> Do you build a uboot image and then nvflash --download it to the EBT partition?
[07:53] <lilstevie> no
[07:53] <lilstevie> it can only be placed in with a --create
[07:53] <lilstevie> nvflash will not write EBT at any other time
[07:53] <twb`> Because nvflash is retarded?
[07:53] <lilstevie> probably
[07:54] <lilstevie> Don't know if mini/updater prevent it
[07:54] <lilstevie> or if it is just some retardation from nvflash
[07:55] <lilstevie> anyway, back to  kernel
[07:55] <lilstevie> with the u-boot kernel most things work
[07:55] <lilstevie> in fact nearly everything works
[07:55] <lilstevie> except the TSP is inverted
[07:55] <lilstevie> and clocking is a little off
[07:56] <lilstevie> so from time to time the framebuffer corrupts when using acceleration
[07:56] <lilstevie> and unexplained slowdowns occur
[07:57] <twb`> What determines if a kernel is u-boot compatible vs. ASUS(?) compatible?
[07:58] <lilstevie> it seems to be a memory map issue
[07:58] <lilstevie> I have been far too busy with uni to properly track it down
[08:06] <twb`> What are you studying?
[08:06] <lilstevie> education
[08:07] <twb`> Man, that's a gruelling career
[08:07] <lilstevie> heh
[09:21] <ogra_> janimo, back from vacation ?
[09:27] <janimo> ogra_, hello, back
[09:27] <janimo> looking into the mx53 scripts now
[09:28] <ogra_> janimo, do we have anything for mx5 already ?
[09:28] <ogra_> bah i type to slow :)
[09:28] <janimo> I'll send you a post-boot script for debian-cd later today
[09:28] <ogra_> cool
[09:28] <ogra_> that should be all we need
[09:29] <janimo> later some changes to jasper as resize needs to deal with the partitioning that is not like on omap
[09:29] <ogra_> k
[09:29] <janimo> but I still need to check as linaro media create and the factory image that came with the board have slightly different partition layouts
[09:30] <ogra_> k, we need to get it in today (and working)
[09:30] <ogra_> freeze starts later today
[10:12] <lilstevie> ogra_: do you know where persia id hiding?
[10:13] <lilstevie> is even
[10:27] <ogra_> lilstevie, at home i guess, not sure
[10:27] <lilstevie> heh
[10:27] <lilstevie> haven't seen him lately
[11:31] <ogra_> diwic, do you know any good spectrum analyzer SW in the archive (i got that new set of speakers and want to get all the room related issues fixed)
[12:13] <diwic> ogra_, hmm, no I'm afraid not - I mean, audacity sure has one if you just want to see the frequency spectrum of a recorded wave file
[12:13] <diwic> ogra_, but maybe you're after something more sofisticated?
[12:13] <ogra_> nah, i need something that takes a mic and outputs a sweep through my speakers
[12:14] <ogra_> and generates the frequency spectrum from that ... so i can see wheer the speakers are lacking
[12:14] <ogra_> and adjust accordingly
[12:14] <ogra_> i can do that with my ears, but only to a certain level :)
[12:15] <diwic> ogra_, hmm, haven't heard of such an app. My receiver has one built in, so I've just used that.
[12:16] <ogra_> yeah, mine too ... but that doesnt work well for the subwoofer and base frequencies
[12:17] <ogra_> finding the right position in the room for it to eleminate resonances etc
[12:17] <gildean> if you happen to find such a software, i'm interested in hearing how it works out
[12:17] <ogra_> i have a very bad room here and i think there are some bad peaks around 30Hz
[12:18] <gildean> i also have some ypao-crap built in the amplifier
[12:18] <ogra_> if i try to fix that "by ear" i will never stop to experiment :)
[12:18] <ogra_> ah, you got a yamaha then
[12:18] <gildean> yeah
[12:19]  * ogra_ is planning to upgrade the amp too ... are you satisfied with yamaha ?
[12:19] <gildean> yes
[12:19] <gildean> i've had it for the past 6 years now
[12:19] <gildean> still working perfectly
[12:19] <ogra_> i'm considering the a810 ... but i'm undecided, there are also some good marantz ones in that area
[12:19] <ogra_> and they look a lot better :)
[12:19] <gildean> the sound is balanced and works nicely with my b&w speakers
[12:20] <ogra_> the onkyo 508b i have atm is really disappointing since i have speakers that are bigger than plastic cups
[12:21] <ogra_> it doesnt really manage to replicate the details properly unless i turn very loud
[12:23] <gildean> you should also check out the denon models in the pricerange too
[12:23] <gildean> ah, and one important point is phono-in
[12:23] <ogra_> none of them gets above 100W
[12:23] <gildean> as in if you need one, most amps don't have one anymore
[12:23] <ogra_> and i dont need phono in, my LPs are all turned into flac already
[12:24] <ogra_> and i also have a pretty good hifi system (i rarely use) i could use to lead my luxman pre-amp through to the surround amp if needed
[12:25] <hrw> ogra_: with ac100 you are using nvflash to flash it?
[12:25] <ogra_> hrw, for the first flashing operation, yeah, later (with teh flashed kernel booted) you can flash locally
[12:25] <lilstevie> ogra_: so same as me for the tf
[12:26] <ogra_> would be cool if someone would write an android installer :)
[12:26] <lilstevie> would be
[12:26] <lilstevie> but meh
[12:26] <lilstevie> not going to happen on my device
[12:26] <ogra_> something that just grabs the boot.img and goes into flash mode
[12:26] <ogra_> same here
[12:26] <lilstevie> I need to modify the flash layout
[12:27] <ogra_> why is that ?
[12:27] <lilstevie> because the original layout is a pita
[12:27] <ogra_> should be possible though, there are howtos for the ac100
[12:27] <lilstevie> boot.img and recovery.img are not within the fs per se
[12:28] <hrw> ogra_: on device flashing is via mtd subsystem?
[12:28] <lilstevie> like the partition table covers a certain portion and boot and recovery are not within it
[12:28] <ogra_> hrw, eMMC
[12:28] <ogra_> its juts a partition
[12:29] <hrw> ah
[12:30] <ogra_> and you can just dd an image you created with abootimg to it
[12:30] <lilstevie> yeah I cant
[12:30] <lilstevie> I need to package into an nvidia blob
[12:30] <lilstevie> dd to a staging partition
[12:31] <lilstevie> then run through a reboot which flashes it into the correct place
[12:32] <ogra_> phew, why ?
[12:32] <ogra_> there is code that enables you to see the LNX and SOS partitions from the kernel
[12:33] <lilstevie> becuase of how asus implemented the flash layout
[12:33] <lilstevie> and our device does not use tegraparts
[12:34] <ogra_> not at all ?
[12:34] <ogra_> i thought all tegras use the partition table offset in the tegra sd code
[12:34] <ogra_> tegrapart is just to make them visible afaik, theoretically you should have all bits in the kernel already
[12:36] <lilstevie> they use tegra parts for the very minimum
[12:37] <lilstevie> but there is certainly nothing in the kernel to make any of it visable
[12:37] <lilstevie> or to use it
[12:38] <lilstevie> because at a kernel level everything the kernel needs is within the GPT
[12:47] <lilstevie> ogra_: anyway it is a pain of an implementation
[12:48] <lilstevie> I move the kernels, and tack on my partition for ubuntu
[12:49] <lilstevie> which gnu parted cant do (work on the partitions that is)
[14:14] <rbasak> I want to mess with the initrd on the pandaboard, eg. move the root filesystem around. On a normal system I'd run update-initramfs and maybe update-grub as necessary. What do I need to do here to cope with u-boot, to update the u-boot partition with the new initrd?
[14:35] <ogra_> rbasak, the same minus update-grub
[14:35] <ogra_> rbasak, though, do you want to actually change the initrd content ?
[14:35] <ogra_> or just the cmdline
[14:36] <rbasak> ogra_: I want to change the fstab entry for the root partition, so I think that needs to get duplicated into the initrd
[14:36] <ogra_> no
[14:36] <ogra_> initrds dont use fstab internally
[14:37] <ogra_> you want your root= setting on the cmdline to point to the right uuid
[14:37] <rbasak> oh, just the kernel cmdline?
[14:37] <ogra_> thats all you need to change
[14:37] <ogra_> there should be a /boot/boot.script file, edit it and just run sudo flash-kernel
[14:38] <ogra_> (you could run update-initrsamfs toon it calls flash-kernel in the end, if you only want to memorize one command ;) )
[14:47] <rbasak> aha
[14:47] <rbasak> ok, I know why I want to update the initrd
[14:48] <rbasak> It's for /conf/conf.d/cryptroot
[14:48] <rbasak> (I always assumed that fstab and crypttab were copied to the initrd, but it looks like update-initramfs generates /conf/conf.d/cryptroot instead)
[14:49] <rbasak> so flash-kernel will update the FAT initrd file with the one in /boot?
[15:05] <ogra_> right
[15:05] <ogra_> as well as vmlinuz and boot.script
[15:10] <GrueMaster> rbasak: Morning.  Anything I can do to help?
[15:11] <rbasak> hi GrueMaster
[15:12] <rbasak> I'm poking with LUKS right now
[15:12] <rbasak> It seems to work for non-system partition stuff just fine
[15:13] <GrueMaster> afaik, the easiest way to configure it is at install time.
[15:13] <GrueMaster> Which means using the netinstall image.
[15:13] <rbasak> Only note is that if using /etc/crypttab and /etc/fstab to mount something on boot, then the prompt for the passphrase isn't very clean over serial (it echoes the passphrase in plaintext and kernel messages appear async over the top)
[15:13] <GrueMaster> And installing to USB.
[15:14] <rbasak> Ah OK, I'll switch to the netinst image then
[15:14] <GrueMaster> oops.  That's not good.
[15:14] <GrueMaster> Although at least it is harder to hack.  Hard to get a man in the middle with a serial console.
[15:14] <ogra_> heh
[15:14] <rbasak> :-)
[15:15] <rbasak> What will be the recommended/supported boot method? Serial only? Or via USB keyboard + monitor or something?
[15:15] <rbasak> (or both?)
[15:15] <ogra_> we default to serial atm iirc
[15:16] <GrueMaster> For server, serial console.  For desktop, KVM.
[15:16] <rbasak> Also I think GrueMaster just answered this - I was going to ask whether we would support encrypted root via the installer or not, since the pre-installed image didn't give me an option. But I think the answer is to use netboot :)
[15:16] <ogra_> you would need to modify the cmdline before first boot to change that to monitor
[15:18] <rbasak> It doesn't need a man in the middle at the moment, just a man over the shoulder :-P
[15:20] <rbasak> I've been using http://cdimage.ubuntu.com/ubuntu-server/daily-preinstalled/current/ so far - where do I get the netinst image from?
[15:20]  * rbasak has just hunted through ubuntu-server/
[15:20] <ogra_> well, a good over-the-sholder-man doesnt need to see the cleartext, he can guess from the keys you press ;)
[15:21] <rbasak> For server I made a keyscript that required a USB key to be inserted (back in Hardy)
[15:22] <rbasak> Never got round to contributing it though :-/
[15:22] <GrueMaster> The netinstall images are here:  http://ports.ubuntu.com/dists/oneiric/main/installer-armel/current/images/omap4/netboot/
[15:23] <GrueMaster> However, if you use them I recommend a different approach than using the img file for now.
[15:23] <ogra_> DYO image :)
[15:23] <GrueMaster> bug 806751 will prevent you from finishing.
[15:23] <ubot2`> Launchpad bug 806751 in debian-installer "Boot partition on SD is too small on omap/omap4" [Medium,New] https://launchpad.net/bugs/806751
[15:24] <ogra_> luckily NCommander is back today to work on that :)
[15:25] <GrueMaster> So you need to download these files (in order) to an SD with a fat partition >30M:  MLO, u-boot.bin, uImage, uInitrd, boot.scr-serial (rename to boot.scr).
[15:25] <GrueMaster> Yes, he should have it fixed this week.
[15:26] <rbasak> In order?
[15:26] <GrueMaster> Well, MLO needs to be first.
[15:26] <GrueMaster> Specifically.
[15:27] <rbasak> First on a fresh FAT partition so it ends up at the beginning?
[15:27] <GrueMaster> Bug in the boot rom and how it looks at the fat table.
[15:27] <GrueMaster> yes.
[15:27] <rbasak> OK, understood
[15:27]  * rbasak hopes that the vfat driver is deterministic in this regard :-P
[15:28] <GrueMaster> So if you have an SD with server preinstalled already on it, just run "sudo mkfs.vfat -F 32 <SD Part 1>"
[15:28] <GrueMaster> Then mount and copy the files, MLO being first.
[15:32] <rbasak> OK I've done that. Before I try booting this, I'd like to remove the second partition on SD now and install to a USB disk instead - will that work?
[15:35]  * rbasak tries it
[15:37] <GrueMaster> Don't worry about the second partition.  It will be ignored.
[15:42] <rbasak> It booted, installing now
[15:45] <rbasak> Does anyone else's pandaboard whistle?
[15:45] <rbasak> Actually it appears to be the PSU
[15:45] <GrueMaster> interesting.
[15:46] <rbasak> I once had a cheap replacement laptop PSU that did that and it made the touchpad not work properly when using it
[15:46]  * rbasak wonders if he has a dodgy PSU
[15:50] <prpplague> rbasak: many cheap "wall-warts" are nothing more than a rectifier, cheap transformer, and a 7805
[15:52] <prpplague> rbasak: without proper impedence matching and filtering you can get a audible frequency Oscillation
[15:52]  * GrueMaster is using an old AT power supply with something like 30A on the  5V rail.  No problems so far.
[15:52] <ogra_> stop welding your pandas dude !
[15:54] <GrueMaster> Heh.  I've even thought of installing a solar panel outside to run my panda stack from.
[15:54] <GrueMaster> (living in Oregon has pretty much dashed that thought, though.
[15:55] <ogra_> well, if you accidentially shorten the right pins with a screwdriver, you might need a new screwdriver in such a setup :)
[15:55] <hrw> GrueMaster: I recently burnt old ATX psu
[15:56] <GrueMaster> ATX power supplies are easy to fry.  They usually melt down in order to protect the $1 fuse they have built in.
[15:57] <GrueMaster> Plus a lot of them require a fair load on the 12v rail for the 5v rail to be stable.
[16:07] <rbasak> The install worked, but on reboot nothing after "Uncompressing Linux... done, booting the kernel." - at a guess it's not configured for console output?
[16:07] <gildean> also AT-powers have a real power-switch
[16:09] <rbasak> GrueMaster: yeah the original boot.scr-serial had a console=ttyO2... line in it, the installer has replaced it and put nothing. I could fix this manually by replacing the file I suppose?
[16:10] <GrueMaster> That is only usefull if you want to see the kernel boot messages.  It should still boot with a login prompt on serial.
[16:13] <rbasak> I see nothing after two minutes. I'd like to see the kernel boot message to see what's up.
[16:14] <rbasak> The USB disk keeps powering down. It does that when on my laptop as well - evidently by default the power save is quite aggressive. I hope that's not affecting it.
[16:14] <GrueMaster> Try hitting enter on the serial console.  Sometimes I have to do that to get a login.
[16:15] <rbasak> No joy
[16:15] <rbasak> It's not really been hitting the USB disk enough to convince me that it's even booting
[16:15] <GrueMaster> If that fails, you will need to manually edit the boot.scr on the SD from your desktop.  I'll walk you through it.
[16:15] <GrueMaster> (and bear with me.  I have an IRC lag from my overloaded server).
[16:16] <GrueMaster> Is your usb drive powered separately, or from the panda?
[16:16] <rbasak> Powered separately
[16:16] <rbasak> I've got the SD mounted on my desktop. boot.scr is binary, though I can edit the ascii part with vim
[16:17] <GrueMaster> Hmmm.  Ok, lets edit the boot.scr.  First, do "dd bs=1 skip=72 if=boot.scr of=boot.script.
[16:17] <rbasak> OK, boot.script now looks like http://paste.ubuntu.com/687735/
[16:18] <GrueMaster> Then you can edit boot.script to add "console=ttyO2,115200" and "earlyprintk=ttyO2,115200".
[16:18] <GrueMaster> Delete "quiet splash".
[16:19] <rbasak> OK done
[16:19] <rbasak> Now stick those 72 bytes at the front again I suppose?
[16:19] <GrueMaster> Save and exit.
[16:20] <GrueMaster> Yes.  Use "mkimage -A arm -O linux -T script -C none -d boot.script boot.scr"
[16:20] <GrueMaster> If you don't have mkimage installed, install u-boot-mkimage.
[16:21] <GrueMaster> That's it.
[16:22] <rbasak> It wanted u-boot-tools rather than u-boot-mkimage, but working now
[16:22] <rbasak> and...aha!
[16:22] <rbasak> I got the kernel output
[16:23] <rbasak> Of course it was asking for the passphrase :-)
[16:23] <GrueMaster> ok
[16:23] <GrueMaster> heh
[16:25] <rbasak> No plaintext echo problem this time. I need to see if that's a initrd vs. normal init prompt thing or a netinst-fixes-it thing
[16:28] <GrueMaster> Cool.  Also, you might try removing early printk, and adding quiet & splash to see how much you need for it to still come up.  If all we need is a console= line, then we can add that.
[16:31] <rbasak> It seems to die when my usb drive powers down. Looks like a separate issue I better tackle first, as I only get about a minute at a login otherwise
[16:32] <rbasak> I'll work out what the minimum required is for the passphrase prompt after that
[16:58] <NCommander> ogra_: indeed, I'm working on it (and did some work on it on Sunday). I already can feel the madness setting in
[17:48] <rbasak> GrueMaster: OK, it works with quiet spash and no early_printk - ie. only console= is required. For a full disk encrypted from the installer, apart from that it works including using *s for echoing the passphrase as it is entered. If I manually add a non-root partition to crypttab and fstab, then it works but echoes the plaintext bad and generally pollutes the console during passphrase input.
[17:48] <ppisati> can anyone check what's going on with actinidiaceae?
[17:49] <ppisati> buildlog has not been updated for a while
[17:49] <rbasak> GrueMaster: so that's basic functionality. Any need for stress/benchmarking? I presume I need to write this up and automate the testing?
[17:51] <GrueMaster> rbasak: Thanks, good work.  For now, if you can just write up the steps to get it enabled, we will be working on automation between Beta 2 and UDS-P (possibly unitl P-A1).
[17:51] <GrueMaster> Goal for now is to do a once through and flush out any issues (like the console=).
[17:52] <GrueMaster> File a bug against debian-installer that states that console= line needs to be added when doing a serial console install.
[17:53] <rbasak> OK, writeup at https://wiki.ubuntu.com/ARM/QA/Server I assume?
[17:54] <GrueMaster> I wonder if it needs to be there regardless.  Did yhe passphrase prompt come up on the monitor at all?  (If you didn't test it, no worries).
[17:54] <rbasak> I didn't test it. I don't have the the right lead to hook up a monitor
[17:54] <GrueMaster> yes, that is the correct link, thanks.
[17:55] <rbasak> I suspect it asks on whatever the console is
[17:56] <GrueMaster> I'll test it further after Beta 2 with a KVM enabled system to verify.  Might require a different cmdline to enable monitor out.
[18:07] <GrueMaster> rbasak: I marked the Test LUKS under server-o-arm-image-qa as done per your results.  Thanks again for the help.
[18:28] <rbasak> GrueMaster: No problem, pleased to get into something arm server related. I'm off now, I'll write up the results and file the bug against debian-installer in the morning.
[20:17] <SysTom> Is there an ubuntu-server build I can get hold of? (Pandaboard)
[21:04] <GrueMaster> SysTom: The official latest release is Oneiric Beta 1, found here:http://cdimage.ubuntu.com/releases/oneiric/beta-1/  Daily builds are at http://cdimage.ubuntu.com/ubuntu-server/daily-preinstalled/.  You can also do a netinstall from http://ports.ubuntu.com/dists/oneiric/main/installer-armel/current/images/omap4/netboot/, but be aware of bug 806751.  netinstall is for installing to either USB or iSCSI (both have been tested, iSCSI still has a
[21:04] <GrueMaster> post-install bug).
[21:04] <ubot2`> Launchpad bug 806751 in debian-installer "Boot partition on SD is too small on omap/omap4" [Medium,New] https://launchpad.net/bugs/806751
[21:05] <GrueMaster> iSCSI bug is 838809.
[21:06] <GrueMaster> sigh.  Bug 838809
[21:06] <ubot2`> Launchpad bug 838809 in Ubuntu Oneiric "authenticated and unauthenicated iscsi clients fails to complete boot" [High,Confirmed] https://launchpad.net/bugs/838809
[21:16] <SysTom> GrueMaster: thanks :)
[21:17] <SysTom> GrueMaster: How's it looking, I assume it's a lot light on resources?
[21:17] <GrueMaster> Well, imagine running a server instance on your cell phone.
[21:18] <GrueMaster> Other than the lack of SATA, it really isn't bad.
[21:18] <GrueMaster> What type of server are you planning?
[21:20] <SysTom> Just having a play at this time tbh
[21:24] <GrueMaster> If you just want to see what it feels like, download the preinstalled image and boot it from SD.  If you are doing anything that involves more disk i/o, you need a usb drive (much faster).
[21:40] <SysTom> Interesting
[21:40] <SysTom> I have a spare USB drive here
[21:42] <SysTom> What's the method for preparing a USB stick for the netboot edition (http://ports.ubuntu.com/dists/oneiric/main/installer-armel/current/images/omap4/netboot/)
[21:43] <GrueMaster> The netboot edition still boots from SD, but the rootfs can be installed on USB.  You need an SD with a primary fat 32 (LBA) partition marked bootable.  The first file should be MLO from the netboot directory.
[21:44] <GrueMaster> The next files should be: u-boot.bin, uImage, uInitrd, and boot.scr-serial (for serial console) or boot.scr-fb (for keyboard/monitor installation) renamed to boot.scr.
[21:45] <GrueMaster> Unfortunately, there is a bug in the installer (see above) that prevents you from using the boot.img files.
[21:45] <SysTom> Ah ok, thanks for the info- certainly something to look into
[21:46] <GrueMaster> Also, be aware that it pulls a lot of files across the internet.  Depending on your network connection, the ports.ubuntu.com mirror may be a big bottleneck, and there are no mirrors (unless you have your own).
[21:49] <GrueMaster> Let me know if you run into issues.  I have been doing netinstalls since Alpha 2.
[21:49] <SysTom> Thanks GrueMaster
[22:01] <NCommander> GrueMaster: ogra_ infinity need a sanity check before I upload http://paste.ubuntu.com/687934/
[22:03] <GrueMaster> From what I can tell, this looks sane.
[22:48] <NCommander> GrueMaster: uploading then
[22:48] <GrueMaster> Will test first thing in the morning.