**** BEGIN LOGGING AT Sat Apr 21 03:00:00 2012 Apr 21 04:47:14 i was going to suggest he add rootwait to his bootargs Apr 21 04:47:25 some mmc devices are rather slow Apr 21 09:31:41 I get this while booting kernel 3.3.1: "EXT3-fs (mmcblk0p2): error: couldn't mount because of unsupported optional features (240)" Apr 21 09:31:45 then "EXT4-fs (mmcblk0p2): warning: maximal mount count reached, running e2fsck is recommended" Apr 21 09:31:59 and then "EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)" Apr 21 09:32:18 and last "VFS: Mounted root (ext4 filesystem) on device 179:2." Apr 21 09:32:33 the partition is a ext2 partition, but still it seems ext4 mounts it Apr 21 09:33:01 the last line in the log is "Freeing init memory: 248K", but I still don't get any login console Apr 21 09:33:06 should I? Apr 21 09:34:37 you sure the recomended fsck isnt running? Apr 21 09:35:35 no. how do I know? Apr 21 09:36:20 no idea unless you have disk activity light Apr 21 09:36:51 also not sure which ubuntu versions give a console prompt and which just go to desktop with nothing on serial Apr 21 09:37:04 I don't think I do. It's a small ARM system (Cubox). But the partition is only 4 GB, so I figured it would be done by now if so Apr 21 09:37:21 I'm running Ubuntu Core 12.04 beta2, there's no desktop to go to Apr 21 09:38:07 you could try fscking the card on a PC Apr 21 09:38:26 it may have got stuck with an unrecoverable error or something Apr 21 09:38:36 but thats all I can think off Apr 21 09:38:38 good idea. Would it be enough to just reformat the partition? Apr 21 09:39:18 I always try and recover before getting drastic Apr 21 09:39:26 just to try and understand what happened Apr 21 09:39:52 ok, I'll try that Apr 21 09:44:08 it found some errors, fixed them, recreated the lost+found and the error message "EXT4-fs (mmcblk0p2): warning: maximal mount count reached, running e2fsck is recommended" disappeared Apr 21 09:44:11 so it did something :) Apr 21 09:44:26 still it cannot mount the filesystem using ext2, even if it is an ext2 filesystem. it mounts it using ext4 Apr 21 09:44:37 and still no login console Apr 21 09:44:43 at some point in time you mounted it as ext4 and wrote a file Apr 21 09:44:57 hmm Apr 21 09:45:16 perhaps if ubuntu did it automatically when I inserted the SD card in another computer? Apr 21 09:45:22 possibly Apr 21 09:45:57 but as to why its not booting no idea Apr 21 09:46:00 ubuntu doesnt do such stuff, does your kernel have ext2 support ? Apr 21 09:46:17 yes, its compiled into the kernel Apr 21 09:46:20 if not, it will indeed try different FS drivers Apr 21 09:46:45 also does your fstab have a proper entry for it pointing to ext2 Apr 21 09:48:00 no, it does not. that file is just empty Apr 21 09:48:07 (heh) Apr 21 09:48:35 well, that means you leave it to the kernel to do guesswork :) Apr 21 09:49:16 (ubuntu-core is seriously not thought as a rootfs if you dont know how to configure it and do all bits the installer would do ...) Apr 21 09:49:35 I am having a freezing problem :/ after "init: unreadahead main process (105) terminated with status 5" it hardlocks Apr 21 09:50:06 are you sure it hardlocks or does it just not display anything ? Apr 21 09:50:07 well, I am learning. I had Ubuntu Core running on qemu arm, and the only modification I did to get a login prompt was to setup a root password there. Apr 21 09:50:14 yeah it hardlocks Apr 21 09:50:21 weird Apr 21 09:50:36 ceck your boot.log ;) Apr 21 09:50:40 *check Apr 21 09:50:42 I have an image on sdcard that should just go to console login rather than starting x Apr 21 09:50:49 and also logs are not written to Apr 21 09:51:10 you dont have the SD locked to readonly, do you ? Apr 21 09:51:21 this is both emmc and microsd Apr 21 09:51:28 hmm Apr 21 09:51:31 on transformer prime Apr 21 09:51:51 we think it is probably the kernel, just don't know why, and seriously lacking some debugging options Apr 21 09:51:52 your kernel has all necessary bits ? Apr 21 09:51:57 yes Apr 21 09:54:39 http://paste.ubuntu.com/939433/ <-- my config Apr 21 09:54:50 just incase you do see something I may have missed Apr 21 09:54:55 bug 936667 came to mind, but you should at least see error messages Apr 21 09:54:57 Launchpad bug 936667 in upstart "Upstart early job logging causes boot failure for systems with no initramfs (error is "No available ptys")" [High,Fix released] https://launchpad.net/bugs/936667 Apr 21 09:55:47 well I do have a different error when running noinitrd Apr 21 09:55:58 but it still ends up in the same lockup Apr 21 09:56:00 hmm, you have legacy pyts on Apr 21 09:56:33 not sure if that can get in your way, but the latest upstart is picky about kernel options at times Apr 21 09:56:47 oh that was me trying to work around failed to create pty with noinitrd Apr 21 09:56:55 I had this problem without legacy ptys Apr 21 09:57:36 wow, why do you compile loopdevice support into the kernel ? Apr 21 09:57:47 8instead of making it modular) Apr 21 09:58:02 cause that is how it is for android Apr 21 09:58:23 I haven't finished with the kernel yet Apr 21 09:58:33 wow, and also DM Apr 21 09:58:37 your kernel must be huge Apr 21 09:58:43 3.5MB Apr 21 09:59:57 this is just how things are in the default android config that I haven Apr 21 10:00:01 ogra_: do you know any place I can find the minimum configuration I need to do in order to get ubuntu core up and running? Apr 21 10:00:05 haven't bothered changing yet Apr 21 10:00:22 wowhmm your wlan driver is also hard compiled in and has a hardcoded firmware part ... Apr 21 10:00:54 yeah, that is bcmdhd Apr 21 10:01:21 jeinor, http://omapedia.org/wiki/OMAP_Ubuntu_Core has some hints Apr 21 10:01:37 thanks Apr 21 10:01:42 the firmware part is hardcoded cause I needed to rearrange some things :) Apr 21 10:01:45 lilstevie, i would make a lot stuff in your kernel modular Apr 21 10:02:00 as a first step Apr 21 10:02:01 bcmdhd does not work, at least on android without being compiled in Apr 21 10:02:33 this is a very early 3.1.10 port, a lot of the asus stuff is still horribly intertwined Apr 21 10:04:54 well, if you are sure it is locked up hard ... hard to say what it is ... if you wouldnt be sure about that i would just have guessed for a worng console= arg on the cmdline Apr 21 10:05:30 the commandline is certainly correct Apr 21 10:05:35 (the ureadahead message is usually the last bit you see before the userspace console kicks in) Apr 21 10:05:55 and this kernel will boot android with its config differences too Apr 21 10:06:01 and yeah I know Apr 21 10:06:19 well, that it boots android has nothing to say :) Apr 21 10:06:40 thats why I was wondering if there was something extra for a more verbose output Apr 21 10:07:03 and haha yeah .39 boots android too, but has a horribly broken framebuffer in ubuntu Apr 21 10:07:12 since you seem to properly get through the initrd i would boot with something like break=top or break=premount or so in your cmdline Apr 21 10:07:27 that will drop you into the initrd shell for further debugging Apr 21 10:07:43 ok Apr 21 10:08:08 (and indeed make sure to not have "quiet" set ;) ) Apr 21 10:09:52 jeinor, note that the above url refers to pandaboards, so dont pick up things like bootloader4 config etc from there since this is HW specific Apr 21 10:10:26 yeah I only have root= at the moment Apr 21 10:10:42 ogra_: got it. I used it for configuring network and root user so far Apr 21 10:11:11 I also recreated the filesystem using mkfs.ext3 and reuntared ubuntu core to it Apr 21 10:11:17 let's see what happens... :) Apr 21 10:11:19 lilstevie, right, try break=top ... that should get you the initrd prompt right after uncompressing Apr 21 10:14:32 ogra_: that removed all error messages on the filesystem. it now properly detects the filesystem as ext3 and mounts it without any error messages. Apr 21 10:14:43 good Apr 21 10:15:22 ogra_: i still get no login console, but I'm starting to believe there's a problem with the graphics driver. I see no output whatsoever on the monitor connected via HDMI during the boot process Apr 21 10:15:42 well, do you see anything on the serial console ? Apr 21 10:16:28 I don't think I have setup a serial console. Learned yesterday how to connect through putty to be able to view the output to ttyS0 Apr 21 10:16:52 so I see all kernel messages in the putty console window Apr 21 10:16:59 but I don't think I can do anything from there Apr 21 10:17:06 well, see the hints on the webpage for setting up serial login then Apr 21 10:17:11 right Apr 21 10:25:01 ogra_: testing with break=top now Apr 21 10:25:07 good Apr 21 10:25:35 ogra_: how do I connect to my new serial console? do I use putty? Apr 21 10:25:52 do you use windows on your host PC ? Apr 21 10:25:57 no Apr 21 10:25:58 ubuntu Apr 21 10:26:10 why do you use putty then and not a sane terminal program ? Apr 21 10:26:38 putty is a windows terminal emulator (that happens to have been ported to linux) Apr 21 10:26:42 the guide from the Cubox wiki contained instructions for using putty Apr 21 10:26:46 I see Apr 21 10:27:02 what is a sane terminal program? Apr 21 10:27:08 try screen ... Apr 21 10:27:13 i.e.: Apr 21 10:27:23 screen /dev/ttyUSB0 115200 Apr 21 10:27:36 that should get you a serial console in the terminal you run it in Apr 21 10:28:21 (see man screen for the commands to attach/detach from that session etc) Apr 21 10:28:27 that gave me a flashing prompt. Would I need to switch tty using ctrl+alt+fX? Apr 21 10:28:54 no Apr 21 10:29:07 ok. that SHOULD have given me a login prompt then, right? Apr 21 10:29:15 it talks directly to your serial port and will exactly output what the cubox sends to the serial port Apr 21 10:29:58 (you should see boot messages (and possible errors) if you reset the cubox) Apr 21 10:31:30 yep, that gives me the same output as putty did before (but nicer in a normal terminal window) Apr 21 10:31:35 thanks for the tip Apr 21 10:31:38 interesting Apr 21 10:32:02 ogra_: it boots when exiting from the initramfs shell Apr 21 10:32:06 but if I had succeeded in configuring the serial-console, I should have gotten a login prompt here, correct? Apr 21 10:32:14 lilstevie, race then ... Apr 21 10:32:24 heh fun Apr 21 10:32:29 jeinor, not if there were errors during boot Apr 21 10:32:48 ogra_: what do you suggest Apr 21 10:32:50 jeinor, reset the cubox and see if you see any boot errors now Apr 21 10:32:58 lilstevie, debugging :P Apr 21 10:33:01 heh Apr 21 10:33:35 try break=premount next ... that drops you into the console a bit later Apr 21 10:33:54 if that works too, try =bottom ... that gives you the console after it mounted the rootfs Apr 21 10:34:15 ogra_: same output as before, ends with "Mounted root (ext3 filesystem) on device 179:2", "devtmpfs: mounted" and last "Freeing init memory: 248K" Apr 21 10:34:23 ok Apr 21 10:34:24 I'll check earlier in the log Apr 21 10:34:46 jeinor, whats your kernel commandline ? Apr 21 10:35:00 i.e. what does the bootloader tell the kernel when it loads it Apr 21 10:35:08 "console=tty0 console=ttyS0,115200n8 vmalloc=384M root=/dev/mmcblk0p2 rootdelay=2 clcd.lcd0_enable=1 clcd.lcd1_enable=0 --no-log --verbose" Apr 21 10:35:58 are you sure you need the clcd bits in there ? Apr 21 10:36:26 no, I'm not sure what they do. I copied them from the stock kernel command line Apr 21 10:36:39 Tried to google that, didn't find anything so I figured I'd better leave them as is Apr 21 10:36:47 well, i guess the device has two lcd ports on borad Apr 21 10:37:25 LCD = HDMI/DVI/VGA? Apr 21 10:37:39 no idea how marvell defined them :) Apr 21 10:37:55 ok :) I'll try removing them Apr 21 10:38:06 one could be attached to the hdmi port and one to an internal socket that gets used in other devices for touchscreens etc Apr 21 10:38:39 makes sense, there is one HDMI port on the Cubox, no VGA/DVI Apr 21 10:40:20 btw, are you using the armel or armhf tarball ? Apr 21 10:41:04 currently the armel Apr 21 10:41:13 eek, Apr 21 10:41:14 k Apr 21 10:41:23 not using to your full potential! Apr 21 10:41:24 that should be on the safe side then Apr 21 10:41:42 not using at any potential right now... :) Apr 21 10:41:45 jeinor, you know you can always use multiarch to install armel packages if you have problems right? Apr 21 10:41:49 right, but it will make sure he wont be hit by any floating point issues for now Apr 21 10:42:16 getting a first boot up is the current focus ;) Apr 21 10:42:38 ogra_, kernel could still be compiled with VFP support, but that kernel floating point but a few revs back only affected x86-32 Apr 21 10:42:44 *bug Apr 21 10:42:50 the kernel doesnt care Apr 21 10:43:01 ogra_, it actually has a VFP option Apr 21 10:43:10 scientes: didn't know that. Will try the armhf as soon as I got an armel up and running Apr 21 10:43:17 (wouldn't make much of a speed diff as there is *very* little fp in the kernel) Apr 21 10:45:12 how do I scroll in screen? the --verbose option gives lots of output Apr 21 10:45:23 jeinor, pipe it to less? Apr 21 10:45:25 | less Apr 21 10:45:31 man screen (in a second terminal you put next to it) Apr 21 10:45:49 scientes, wont help much with dmesg from a serial port :) Apr 21 10:46:27 ogra_, well if you have that you can just turn on infinite back scrolling in your terminal emulator Apr 21 10:48:37 uhm... feeling a bit stupid here... what does "C-a" mean? what key is that? Apr 21 10:48:57 C means control Apr 21 10:49:01 a means a :) Apr 21 10:52:14 ^ Apr 21 10:52:39 :) thanks. entered copy mode, and now I can scroll in the buffer Apr 21 10:52:51 init is doing a whole lot of work here Apr 21 10:53:29 but there are no error messages, just a lot of "Handling start event" Apr 21 10:54:11 I must have done something wrong when configuring that serial console. everything looks fine Apr 21 10:56:49 anything on the monitor btw ? Apr 21 10:56:57 8since you dropped the lcd args) Apr 21 11:01:57 testing now Apr 21 11:04:10 no, still nothing there. And still no login terminal. Apr 21 11:04:17 hmm Apr 21 11:04:46 perhaps that serial-console script on the web page parses my first console= line, thus missing the correct options for the ttyS0 Apr 21 11:05:03 I have two, console=tty0 console=ttyS0,etc Apr 21 11:05:17 the first console line defines the console the kernel dumps dmesg to ... Apr 21 11:05:25 the second one defines whats used for userspace Apr 21 11:05:46 oh Apr 21 11:05:53 the first one is console=tty0, so it should dump dmesg to the screen then Apr 21 11:05:58 your second one say console=ttyS0 ? Apr 21 11:06:22 console=ttyS0,115200n8 Apr 21 11:06:27 * ogra_ wonders if the armada actually defines the serial console as S0 Apr 21 11:06:39 try dopping *all* console args for a test Apr 21 11:06:40 hm Apr 21 11:06:43 ok Apr 21 11:06:49 and see what happens :) Apr 21 11:08:36 though looking at the cubox wiki they all seem to use a single console arg defined as console=ttyS0,115200n8 Apr 21 11:09:03 yeah, that's where I got it from Apr 21 11:09:40 but you're right, perhaps I should drop the first console at least (trying without all now) Apr 21 11:10:13 ok, so removing all made screen stop receiving output after "Uncompressing Linux... done, booting the kernel." Apr 21 11:10:30 I'll try just the first one, console=ttyS0,115200n8 now Apr 21 11:11:04 right, but did you see anything on the monitor ? Apr 21 11:11:36 no, I checked that too. tried to switch tty as well (ctrl+alt+fX) Apr 21 11:11:38 (and make sure to wait for a while, it might take a bit to get to the login prompt, giv it time) Apr 21 11:12:07 ... that I didn't do. will redo that attempt after trying the single console= Apr 21 11:12:09 its an 800MHz system booting off slow media after all Apr 21 11:12:19 true Apr 21 11:13:55 "After a while (it takes a bit) a framebuffer console will appear, hiding the boot messages. Don't be scared, and wait for a few minutes. The login prompt will finally appear. " Apr 21 11:14:02 from the wiki :) Apr 21 11:14:30 this is why us old school guys like out console messages, gives us hope :-D Apr 21 11:14:41 yeah Apr 21 11:14:41 :) Apr 21 11:15:20 well, I think the framebuffer console won't appear here, this is not the stock kernel. The 2.6 kernel had graphic drivers and used a second command line arg, video= with resolution and stuff Apr 21 11:15:40 what kernel is it then ? Apr 21 11:15:45 3.3.1 Apr 21 11:15:52 and are you 100% sure that kernel is supposed to work at all Apr 21 11:15:59 (with ubuntu) Apr 21 11:16:04 compiled by me, config from forum post where they said it booted fine Apr 21 11:16:12 on ubuntu ? Apr 21 11:16:28 they had Debian Apr 21 11:16:34 perhaps it just wont work? Apr 21 11:16:48 well, the debian kernel should tehoretically work Apr 21 11:17:21 http://www.solid-run.com/phpbb/viewtopic.php?f=9&t=493 Apr 21 11:17:41 this is the link where this user (which doesn't respond back) says he got it working with stock 3.3.1 kernel Apr 21 11:17:46 and Debian 6 Apr 21 11:17:55 so I figured Ubuntu Core would work with that kernel as well Apr 21 11:18:18 first tried booting Ubuntu Core with kernel 2.6, but got looping error messages from dmesg complaining about missing functionality Apr 21 11:19:31 the kernel I used is downloaded from www.kernel.org Apr 21 11:19:49 ogra_: all three work top, premount and bottom Apr 21 11:20:16 lilstevie, well, then blame usersapce or some kernel option the userspace needs Apr 21 11:20:33 heh Apr 21 11:20:42 but I'm still in no better position to debug :/ Apr 21 11:20:43 but if the serial-console would have been working, I should have been given a login prompt in my screen session to /dev/ttyUSB0, correct? Apr 21 11:20:59 "Also note that currently, the "make modules" fails, there is some sort of compile error for the framebuffer modules. I just ignored them at initial testing...." Apr 21 11:21:10 so why would you expect anything on your monitor at all ? Apr 21 11:21:43 ogra_: yeah, I've read that. I figured that was the framebuffer module (with support for higher resolution and such), and that it would fallback to just displaying the console using some basic graphics drivers Apr 21 11:22:01 but perhaps you're right, perhaps it just doesn't work at all Apr 21 11:22:11 but I still should get a login console on the serial-console Apr 21 11:23:12 true Apr 21 11:24:37 can you pastebin your full output from the screen session ? Apr 21 11:26:14 (from one boot attempt indeed) Apr 21 11:26:51 hmm, trying to get the whole screen buffer Apr 21 11:26:57 hardcopy gives me the current window Apr 21 11:28:13 I'm on it Apr 21 11:32:51 where do screen logs go with the -L option? Apr 21 11:33:52 C-a H (log) Begins/ends logging of the current window to the file "screenlog.n". Apr 21 11:36:28 http://pastebin.com/NqfgpiCT Apr 21 11:39:26 ogra_: I have to leave for a few hours, will be back here later. I am really grateful for your help, I've been stuck on this problem for some days now and it's frustrating when I don't know even where to start looking Apr 21 11:39:43 yep Apr 21 11:39:58 i might not be around though (i usually dont work on weekends :) ) Apr 21 11:40:49 i wonder what /etc/init,conf is supposed to be Apr 21 11:41:06 the /etc/init.conf in the rootfs? Apr 21 11:41:29 they don't mention that one in the OMAP guide Apr 21 11:41:56 well, it usually doesnt exist on ubuntu systems Apr 21 11:42:10 but seems ot be read on yours Apr 21 11:42:35 hmm.. something specific to ubuntu core perhaps? Apr 21 11:43:21 maybe upstart doesn't properly start my serial-console script because of some errors with /etc/init or /etc/init.conf Apr 21 11:43:43 as i said, /etc/init.conf shouldnt exist Apr 21 11:44:15 and it seems the boot stops at upstart-udev-bridge Apr 21 11:44:42 probably soemthing you should take to our upstart maintainer on monday Apr 21 11:44:51 (he is jodh in #ubuntu-devel) Apr 21 11:44:59 actually, when I mount the root partion on another computer and look in /etc/ the file isn't there (init.conf) Apr 21 11:45:20 yes, as its supposed to be, not sure why there is that message in your dmesg Apr 21 11:45:42 true, maybe to notify me that if the file had been there, it should have been read Apr 21 11:46:08 I do have the --verbose option on Apr 21 11:46:11 yeah, likely Apr 21 11:46:50 in any case it doesnt seem to even get to fire up a getty process Apr 21 11:47:18 either a kernel misconfiguration or some issue with upstart Apr 21 11:47:24 ok Apr 21 11:47:31 then I have a pointer on where to continue next Apr 21 11:47:42 thanks a lot for all your help! Apr 21 11:47:49 np :) Apr 21 11:47:52 I'll report back here on how it goes :) Apr 21 11:48:20 really appreciate your help, worth a lot for me. take care! Apr 21 12:15:08 ok ogra_ I can trace it to something in bottom Apr 21 12:15:27 I get a panic some boots with break=bottom Apr 21 12:46:15 Are there no mirrors of Ubuntu ports? Apr 21 14:42:29 ogra_, you here? Apr 21 14:51:38 ogra_: I got it working!!! the reason I didn't get a console was that I had accidentally placed the serial-auto-detect-console.conf in /etc/, not in /etc/init Apr 21 14:51:39 !!! Apr 21 14:52:02 thanks again for all your help! now that I have a root console, I'm in my safe place again :) Apr 21 18:37:25 ogra_: in case anyone else comes in asking questions about kernel 3.3.1 and ubuntu core :) http://www.solid-run.com/phpbb/viewtopic.php?f=4&t=544 Apr 21 18:54:00 jeinor: Not that it matters for kernels that are ABI-agnostic, but if you're going to recommend people install an ARM cross-compiler, recommend they install gnueabihf, please. Apr 21 18:54:21 We really want to encourage people to switch to armhf completely. Apr 21 18:55:16 jeinor: Err, and same for core itself, you tell people to use armel, again, they'll be much happier with armhf. Apr 21 19:21:34 Il Apr 21 19:21:38 wops, I'll change that Apr 21 19:21:44 infinity, what is ABI-agnostic? Apr 21 19:22:10 to run a ubuntu core armhf, will I need to recompile kernel using the gnueabihf cross compiler? Apr 21 19:24:18 more importantly, will it make any performance difference? Apr 21 19:24:59 jeinor: No, the kernel doesn't care what ABI your userspace is at all. Apr 21 19:25:09 jeinor: Using either compiler will get you an identical kernel. Apr 21 19:25:34 jeinor: I'd just prefer we encourage people to use hf in all cases. Apr 21 19:32:46 I'll test that for my install and if everything works as before I'll change it in the post Apr 21 19:32:49 thanks for pointing it out Apr 21 19:41:07 hmm, what happens to all the armel-packages out there? in apt repositories for example? can I run armel compiled binaries on armhf systems? Apr 21 19:41:48 With multiarch, you might be able to. Apr 21 19:41:56 But generally, you should compile things for armhf. Apr 21 19:42:03 They're ABI-incompatible. Apr 21 19:42:36 The question is basically the same as "can I run i386 binaries on amd64", to which the answer is "sometimes". Apr 21 19:43:05 I see. What about the packages in apt repositories? Are most armhf or armel nowadays? Apr 21 19:43:31 openjdk, for example? Apr 21 19:47:35 i think, there are two ports. one for armel and one for armhf Apr 21 19:52:17 and as far as i know, the armhf port was completely rebuild (some weeks ago?). openjdk is also in the armhf-universe-repo of precise Apr 21 19:53:09 ok, thanks Apr 21 19:55:13 when you're saying "the armhf port was completely rebuilt", do you mean all packages in the official ubuntu repo were rebuilt for precise? Apr 21 19:55:55 for armhf in generell, i think Apr 21 19:59:35 sounds promising, I'll see what packages are there when I begin to setup my system Apr 21 20:01:19 it's quite eays to geht the package-information: download http://ports.ubuntu.com/dists/precise/universe/binary-armhf/Packages.gz for main/restricted/universe/multiverse and grep for the "Package: " Apr 21 20:02:27 * row Apr 21 20:04:04 nice, thanks for the tip Apr 21 20:04:27 np, you are welcome Apr 21 20:06:03 jesus, my grammar is bad today Apr 21 20:58:34 jeinor: There are two different prices ports. armhf and armel. armhf is the one we're supporting. Apr 21 22:04:21 jeinor, http://packages.ubuntu.com Apr 21 22:44:31 scientes, there is only i386, amd64 and powerpc selectable Apr 21 22:45:07 oh yeah ubuntu has an ugly split unlike debian Apr 21 22:45:14 there is another site, but i forget where it is **** ENDING LOGGING AT Sun Apr 22 03:00:00 2012