**** BEGIN LOGGING AT Sun May 22 02:59:58 2011 May 22 09:06:02 anyone about? May 22 09:06:11 i'm tryign to boot natty on my beagleboardxm May 22 09:06:21 it gets to a busybox terminal... May 22 09:07:01 but I don't know how to boot into X/gnome May 22 09:10:12 Which image are you using? May 22 09:11:22 ubuntu-11.04-preinstalled-netbook-armel+omap.img.gz May 22 09:12:09 That *should* (eventually) launch X. Do you have any errors in the busybox shell? What are you using for console? May 22 09:12:50 I jst have it plugged into my tv. May 22 09:13:00 (console is coming oup on tv) May 22 09:18:04 on boot it goes: caching vfat content, re-writing vfat partition, checking filesystem before resizing. then drops to busybox with: No init found. Try passing init= bootarg May 22 09:18:20 window 25 May 22 09:23:43 Hrm. May 22 09:24:03 How did you write the SD card? May 22 09:26:01 from my laptop with guzip -c | dd May 22 09:27:16 I haven't seen it done that way before, but I can't imagine why it wouldn't work :) Nice optimisation. May 22 09:27:38 uh' what other way would you do it? May 22 09:27:42 It looks like there's some issue resizing the filesystem for initial boot. May 22 09:27:55 Most folk use two steps: 1) uncompress, 2) copy to SD. May 22 09:28:04 There are, of course, N methods to achieve either 1) or 2). May 22 09:28:19 And, like I said, doing it all in one line should make no difference. May 22 09:28:46 For some hardware, attempting to write with `cat` rather than `dd` seems to cause issues (but for some people it works). May 22 09:29:04 Anyway, that's just me asking common questions to try to apply a known solution to an unknown problem :) May 22 09:31:10 So, if I had your symptoms, I'd probably try rewriting the SD (cosmic ray protection), then trying fsck in the busybox shell, and attempting to manually step through the initramfs scripts to get a more interesting error. May 22 09:31:15 I was going off https://wiki.ubuntu.com/ARM/OmapNetbook anyway :P May 22 09:32:30 Heh. Last time I saw that page it recommended `zcat > ${DEVICE_NAME}`. I'm glad to see that it's getting better :) May 22 09:52:50 so what file do I change? May 22 09:52:53 * daurnimator pokes persia May 22 09:56:10 I've no idea what file to change to "make it work". As I said before, I'd start with cosmic-ray-paranoia, then an fsck in the busybox shell, than attempting to manually process the initramfs scripts. May 22 09:57:37 well I'm looking at the uboot partition now... May 22 09:57:49 something in boot.scr? May 22 09:58:27 If you reached the message you posted at :16, uboot is working fine for you. The issue is happening inside the initramfs. May 22 09:59:02 I was imagining boot.scr was passing bad paramteres or something May 22 09:59:17 And that's really hard to debug *except* from inside. Were I in that situation, I'd leave the VFAT partition alone. May 22 09:59:56 Potentially, but if you hadn't previously modified it, the chances are fairly low (or there would be many people complaining) May 22 10:00:47 so; what do I do :P ? May 22 10:01:17 Well, did you try rewriting the SD card? May 22 10:01:38 If so, have you tried running fsck from the busybox prompt when you get the error? May 22 10:01:52 not yet: use same method? May 22 10:02:12 May as well: it's a reasonable one. May 22 10:07:56 does the blocksize matter/ May 22 10:08:14 Yes, but. May 22 10:09:19 You want to pick a blocksize that is larger than the allocation unit of the storage medium, or you may end up requiring more allocation units than you would otherwise expect for naive implementations of storage allocation algorithms (unchangeable: built into the MMC implementation on the SD card) May 22 10:09:20 but? May 22 10:10:46 You want to pick a blocksize that is smaller than any potential overflow buffer in the delivery pipeline. Ideally, there aren't any, but using e.g. blocksizes larger than available RAM may cause issues in certain circumstances. May 22 10:11:20 right. May 22 10:11:35 So, in practice, for relatively sane values of blocksize, it doesn't matter. I usually use 1M or 4M, but there's lots of working values. May 22 10:15:08 don May 22 10:15:21 I don't suppose theres any issue with using an 8gb SDHC card? May 22 10:23:22 ah turns out my download is corrupt May 22 10:33:43 Shouldn't be any issues with size: I've seen folk with 4, 8, 16. Ah, excellent: the issue is identified. May 22 12:39:54 gah May 22 12:40:00 this download is corrupt too May 22 12:40:08 anyone have a torrent or something? May 22 12:40:39 the zsync thing also failed. downloaded the hole thing then aborted cause of a gzip error or something May 22 12:40:47 *whole May 22 12:43:33 Ugh. May 22 12:44:06 I generally use rsync: in cases where I've had issues in the past, sometimes multiple runs sorts it. May 22 12:47:05 persia: flail. May 22 12:47:54 Yep :) Sorry I don't have any more constructive ideas. **** ENDING LOGGING AT Mon May 23 02:59:58 2011