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