=== Guest74361 is now known as Martyn [08:16] hi [08:17] did ubuntu support s3c6410 ? [08:19] think it's armv5 capable [08:39] yes [09:00] whats the s3c6410 [09:13] joshzhao: You need to build your own kernel and any integration bits, but the userland should work, it's ARM11 [09:19] NCommander: 10:11 < lool> NCommander: What are you looking into ATM? Could you take that? [09:19] 10:12 < lool> NCommander: Also, kexec-tools was finally added to P-a-s, do you think you could try it out? it built on armel [09:19] NCommander: "that" being d-i [09:20] Been working on that already [09:20] * NCommander learns how d-i goes together, but I'm making no headway on ARM [09:20] The last kernel upload made my board completely unreliable, and with it getting files at the speed of dial up .... [09:21] Same thing goes for kexec (that being said, I used the 2.0.0 release of kexec-tools on Babbage, and got nothing, so unless we're carrying patches ...) [09:22] NCommander: Please try the ubuntu kernels [09:22] NCommander: If there are bugs, file them [09:23] NCommander: Perhaps compare the exact same scenario in qemu/i386 and qemu/armel? [09:24] lool, it doesn't work in qemu/armel with our kernel as of the last time I tried it, I'm building a new qemu/armel image now so I can work on d-i, I'll test it once it finishes installing. [09:34] NCommander: Where's the bug report? [09:34] NCommander: the same test case passes on i386? [09:35] lool, I dunno if I filed a bug on this in Ubuntu, I did bring it upstream; no ping reply. [09:37] i don't know what kind of Ubuntu Kernel tree support 6410? [09:38] s3c6410 is based on arm11 [09:38] samsung [09:40] NCommander: Are you waiting for me to ask you to file one or will you file one now? :-) [09:40] lool, I'll file once I rerun the tests, filing bugs based on old data is a bad thing. [09:42] lool: do you know what kind of Ubuntu Kernel tree support 6410? [09:43] joshzhao: No [09:43] joshzhao: The Ubuntu kernel tree is close to the upstream one [09:56] thanks lool [10:01] lool, if you have a few minutes, would you like to process one of the outstanding MIRs on RedBoot or ecosconfig? === Nicke_ is now known as Nicke [10:28] mcasadevall: I'm queueing it up, but don't consider it assigned to me yet; I'm afraid I have a bunch of urgent stuff which is landing on my plate these days [10:28] lool, no problem. [10:30] amitk, meh, FTBFS on imx51 [10:30] Building modules, stage 2. [10:30] MODPOST 739 modules [10:30] ERROR: "cpufreq_gov_performance" [arch/arm/plat-mxc/cpufreq.ko] undefined! [10:30] ERROR: "get_cpu_wp" [arch/arm/plat-mxc/cpufreq.ko] undefined! [10:30] ERROR: "dvfs_core_is_active" [arch/arm/plat-mxc/cpufreq.ko] undefined! [10:30] ERROR: "cpu_wp_nr" [arch/arm/plat-mxc/cpufreq.ko] undefined! [10:30] make[3]: *** [__modpost] Error 1 [10:30] make[2]: *** [modules] Error 2 [10:30] make[1]: *** [sub-make] Error 2 [10:30] amitk, throw cpufreq out, it has no use on the babbage anyway [10:30] It looks like you need to turn on these configs for the imx51 cpufreq backends [10:31] Hmm they are [10:32] waht for ? [10:32] ogra: I know, working on it [10:32] ah, good [10:33] intresting that it didnt fail in the PPA build [11:03] ogra: could you test -11.35 (FINAL). It has AA and aufs, cpufreq solved. This might be our last chance before beta to fix this issue. [11:03] amitk, after the meeting [11:03] ogra: sure [11:03] (i'll try to do i aside the meeting if really urgent though) [11:04] naah.. I still have to work on the d-i bits. So anytime in the next 2-3hrs is good [11:04] oh, wait, my inner clock is off one hour [11:04] i can do it now [11:04] did we change time? [11:04] no, its 12 UTC [11:13] * ogra smiles, a working NIC makes everything so much easier [11:14] no more plugging around of USB keys to transfer kernels and initramfs [11:14] ogra: make sure you get this http://people.ubuntu.com/~amitk/linux-image-FINAL-2.6.28-11-imx51_2.6.28-11.35_armel.deb [11:15] yes, thats what i just installed and copied to my desktop [11:15] now i'm doing a dist-upgrade to get new procps etc ... then i'll reboot and xmodem the kernel and initramfs over [11:16] ogra or amitk: I need /proc/cpuinfo on babbage with CONFIG_NEON=y (probably on the kernels you're running) and with the NEON hwacps merged in 2.6.28-10.33 [11:34] amitk, AA oops :( [11:35] ogra: that is underinvestigation. just disable in on the cmdline [11:36] same [11:36] apparmor.enable=0 ... still oopses [11:38] grmbl [11:39] that costed me my working setup [11:40] * ogra needs to rebot after upgrade ... [11:40] *reboot [11:46] ogra: are you capturing the oops? [11:46] Would really appreciate a /proc/cpuinfo [11:46] * ogra cant give a /proc/cpuinfo without getting into the system [11:46] amitk, one sec [11:47] lool: I'll have to build a new kernel with NEON enabled again [11:47] Is there a working babbage kernel I can run right now which has NEON support? [11:47] is the ubuntu one working for instance? [11:48] lool: try the original ubuntu one, or one from http://people.ubuntu.com/~amitk/ [11:48] amitk, http://paste.ubuntu.com/133579/ [11:49] Will either boot without initramfs? [11:49] __aa_find_profile it seems [11:49] ogra: same oops [11:49] lool, yes, but you need rootdelay [11:49] and no uuid root= line [11:56] ogra: I'm compiling another one with AA turned off by default [11:56] thanks === mcasadevall is now known as NCommander [12:14] ogra: same 'FINAL' .deb with AA compiled in but turned off by default [12:14] back from lunch [12:15] * NCommander sighs [12:15] THere is a max initrd size it seems on the Babbage [12:15] or something crazy ... [12:15] how big did you b'koat yours ? [12:15] *bloat [12:15] up to 4.5M worked fine here [12:16] 2.5MB, I'm getting incomplete write, which suggests its too large [12:16] funny [12:16] i'm using a 4.2M one atm [12:16] and had a 4.5 one before [12:25] ogra, its I'm an idiot problem :-) === rwhitby` is now known as rwhitby [13:23] amitk, hmm, lost all my input capabilities again with the latest build [13:23] amitk, did you remover the compiled in usb host drivers again ? [13:23] *remove [13:24] amitk, hrm, and i get compcache by default [13:26] amitk, additionally the rest of the usb stack doesnt get loaded either [13:26] amitk, and i dont see an indication of a kernel event happening [13:27] aha, loading ehci-hcd helps [13:27] ogra: I haven't touched anything else, you can check the config file [13:27] weird [13:28] my rootfs doesnt mount, ehci-hcd should be compiled in [13:29] there is no trace of usb-storage in my initramfs [13:29] ogra: it is [13:29] (initramfs) ls /lib/modules/2.6.28-11-imx51/kernel/drivers/usb/ [13:29] host [13:29] (initramfs) ls /lib/modules/2.6.28-11-imx51/kernel/drivers/usb/host/ [13:29] ehci-hcd.ko [13:29] thats all i have [13:29] (initramfs) uname -a [13:29] Linux (none) 2.6.28-11-imx51 #35 Thu Mar 19 12:38:40 EET 2009 armv7l unknown [13:30] * amitk checks again [13:31] ogra: shoot me, you are right. EHCI_HCD is a module [13:31] (initramfs) cat conf/initramfs.conf |grep MODULES [13:31] # MODULES: [ most | netboot | dep | list ] [13:31] MODULES=most [13:32] so usb-storage should be there actually [13:32] hmm [13:33] ogra: storage is compiled in, so is USB_HID (for keyboard), but i left EHCI as a module for some reason [13:33] ah [13:33] that expleins it [13:33] *explains [13:33] that config file is swimming in front of me now [13:33] ok [13:33] i dont get why it uses compcache though [13:34] ogra: because it is a module [13:34] do you want it removed? [13:34] it should only be included if there are less than 256M ram [13:34] no, keep it [13:34] but the script shouldnt fire [13:35] (initramfs) cat /proc/meminfo [13:35] MemTotal: 482808 kB [13:35] there is definately more than 256M [13:35] It is only a module [13:36] argh [13:36] TOTAL_RAM=$( grep MemTotal /proc/meminfo |tr -d ': [A-Z][a-z]') [13:36] # Do not use compcache on the liveCD if we have more than 512M [13:36] if [ "${BOOT}" = "casper" ]; then [13:36] if [ "${TOTAL_RAM}" -gt 524288 ]; then [13:36] exit 0 [13:36] fi [13:36] fi [13:36] thats bad [13:37] hehe [13:39] i mean it works, but its pointless to have on babbage [13:47] The distro kernel doesn't boot for me [13:47] Uncompressing Linux............................................................. [13:47] And nothing more [13:48] amitk, oh, does compcache get autoloaded if its there ? (it should never load alone) [13:48] Can someone hand me a recent kernel build with the NEON hwcaps patch? [13:49] http://people.ubuntu.com/~amitk/linux-image-NO-AA-AUFS-USB-COMPILED-2.6.28-10-imx51_2.6.28-10.32_armel.deb not sure about neon [13:49] but thats definately a working one [13:49] Thanks [13:49] lool: grab the .deb from my p.u.c and grep the config. [13:49] amitk: It's not a config [13:50] lool: you want the patch AND the CONFIG_NEON configured in, right? [13:50] amitk: Correct [13:50] But CONFIG_NEON has been set since forever [13:51] * ogra wonders how long forever is for an unfinished kernel :) [13:52] if [ "${BOOT}" = "casper" ]; then [13:52] if [ "${TOTAL_RAM}" -gt 524288 ]; then [13:52] exit 0 [13:52] fi [13:52] fi [13:52] modprobe -q --ignore-install compcache compcache_size_kbytes="$(($(sed -nre 's/^MemTotal:\s*([0-9]+) kB$/\1/p' /proc/meminfo) * 25 / 100))" [13:52] ARGH [13:53] so if i boot with boot=casper and the system has 512M it will exit ... if the system has no 512M *and* i dont boot with casper compcache will load in *any* case [13:53] thats so wrong ... [13:54] i guess that needs an else condition ... [13:54] oh, my, what was i smoking when i wrote that code [13:55] * ogra takes a break ... thats so embrassing [13:55] good stuff? :) [13:56] ogra: new 'FINAL' uploaded. Hopefully the real FINAL :-/ [14:02] The above kernel doesn't work for me either [14:02] Does it need an initramfs to output anything? [14:07] GRR [14:07] screen doesn't like too long commands [14:15] Ok, the kernel loaded over ymodem at least says "done, booting the kernel." but nothing more [14:15] ogra: is there serial console in the kernel you mentionned as working? [14:23] ogra: I definitely get zero output from the kernel with the .deb you pointed me at, only up to "done, booting the kernel.", even with console=ttymxc0,115200 console=tty0 on serial and VGA output [14:26] And the same thing with the FINAL .deb above [14:29] I'm booting with RedBoot> exec -c "console=ttymxc0,115200 console=tty0 root=/dev/mmcblk0p2 ro debug noinitrd rootdelay=2" [14:31] I confirmed that the way I upload kernels works as if I reload zImage_DVI it works [14:32] BTW I'm now updating the SD card directly [14:32] With dd and fis [14:35] amitk: Can you confirm the above kernels will work *without* initrd? [14:39] lool: dunno. I have an initramfs [14:40] amitk: Could you show me fis list and/or a boot log so that I can use the proper fis create command here? [14:40] hello. does anyone know when we might see usable Ubuntu netbooks on ARM? [14:40] I also need the cmdline with initramfs, so far I only have without [14:41] FlimFlamMan: No final date yet [14:42] lool: thanks. what's the best place to keep track of how things are progressing, and what the shape of the final product will be? will the "experience" basically be the same as on x86? [14:43] FlimFlamMan: The images Ubuntu will release for arm devices match images which exist for i386 already [14:44] FlimFlamMan: Following Ubuntu news channels should be enough to get the news [14:47] lool: Thanks for the information. (I'm trying to judge whether i should hold off on a netbook purchase or buy an interim unit.) [14:47] lool, yes, works fine for me [14:49] ogra: without initrd? [14:49] ogra: I'm using dpkg -x, replacing the kernel with the file in boot/vmlinuz-foo exactly in the same way as zImage_DVI, and it doesn't boot; while zImage_DVI works [14:49] I'm really confused [14:51] i use dpkg -x on my laptop, boot into redboot serial, do xmodem, load the kernel and run a similar exec line to yours [14:51] ogra: what exact line are you currently running? [14:51] might it be the dd/fis combo you use ? [14:51] it could be [14:51] I'm not using the default sizes for the fis partitions [14:52] currently i'm using the lates kernel *with* initramfs ... [14:52] (initramfs) cat /proc/cmdline [14:52] console=ttymxc0,115200 root=UUID=ae90832f-ba0d-4164-b710-0402041ab8ed [14:52] ogra: Ah *with* initramfs [14:52] right [14:52] I suspect that's the problem [14:52] but it works fine without initramfs using yours [14:52] no [14:53] ogra: I put the new kernel on p.u.c [14:53] amitk, thanks, trying [14:53] lool, drop the "noinitrd" [14:53] and the debug [14:53] amitk: http://people.ubuntu.com/~amitk/linux-image-FINAL-2.6.28-11-imx51_2.6.28-11.35_armel.deb ? [14:53] yes [14:53] exec -c "console=ttymxc0,115200 console=tty0 root=/dev/mmcblk0p2 rootdelay=2" should work [14:54] (for me exec -c "console=ttymxc0,115200 console=tty0 root=/dev/sdb1 rootdelay=2" definately does if amitk doesnt play with USB modularization ;) ) [14:55] ogra: hopefully this time I don't have my head up you-know-where :) [14:55] heh [14:55] ogra: no difference, it stops after "done, booting the kernel." [14:55] strange [14:55] works fine here [14:55] ogra: Can you show your fis commands? [14:55] Or your xmodem load rather [14:55] RedBoot says before booting: [14:55] entry=0x90008000, target=0x90008000 [14:55] Using base address 0x00100000 and length 0x002144c0 [14:56] load -m xmodem -b 0x100000 -r [14:56] fis create kernel [14:56] thats what o do [14:56] RedBoot> e -r 0x1000000 -s 4020573 -c "console=ttymxc0,115200 console=tty1 root=UUID=ae90832f-ba0d-4164-b710-0402041ab8ed quiet" [14:56] entry=0x90008000, target=0x90008000 [14:56] Using base address 0x00100000 and length 0x0021020c [14:56] ogra: Do you have fis list or boot output? [14:57] RedBoot> fis list [14:57] ... Read from 0x1fee0000-0x1feff000 at 0x00040000: . [14:57] Name FLASH addr Mem addr Length Entry point [14:57] RedBoot 0x00000000 0x00000000 0x00040000 0x00000000 [14:57] FIS directory 0x00040000 0x00040000 0x0001F000 0x00000000 [14:57] RedBoot config 0x0005F000 0x0005F000 0x00001000 0x00000000 [14:57] initramfs 0x00060000 0x01000000 0x00400000 0x01000000 [14:57] kernel 0x00460000 0x00100000 0x00220000 0x00100000 [14:57] RedBoot> [14:59] ogra: and fis list -d? [14:59] RedBoot> fis list -d [14:59] ... Read from 0x1fee0000-0x1feff000 at 0x00040000: . [14:59] Name FLASH addr Mem addr Datalen Entry point [14:59] RedBoot 0x00000000 0x00000000 0x00000000 0x00000000 [14:59] FIS directory 0x00040000 0x00040000 0x00000000 0x00000000 [14:59] RedBoot config 0x0005F000 0x0005F000 0x00000000 0x00000000 [14:59] initramfs 0x00060000 0x01000000 0x003D595D 0x01000000 [14:59] kernel 0x00460000 0x00100000 0x0021020C 0x00100000 [15:00] My datalen is 0x002144C0 [15:00] lool, i'm about to xmodem again, if you need anything else, say it now :) [15:01] ogra: I don't, unless you can be tempted to try my way of updating with fis [15:01] i do, but only after i have a working initramfs again [15:01] which takes a bit [15:01] ogra: How do you create the initramfs? by installing the package? [15:01] right [15:01] ogra: Hwo do you load it? [15:01] installing the package and scp'ing to my laptop [15:01] then i reboot and xmodem it over serial [15:02] load -m xmodem... wihch args [15:02] load -m xmodem -b 0x1000000 -r [15:02] fis create initramfs [15:02] load -m xmodem -b 0x100000 -r [15:02] fis create kernel [15:02] exec -r 0x1000000 -s *size* -c *command line* [15:03] where *size* is the output of ls -l [15:03] for the initramfs file [15:03] sillyness of the week, its not in hex [15:03] while everything else is [15:04] I really don't get why it doesn't work for me [15:04] try serial [15:04] ogra: Can you show me the messages before loading linux on the next boot? [15:04] ogra: I did [15:04] check if that changes it [15:04] i will [15:04] Will try serial again [15:04] xmodem running now ... takes a while [15:10] lool, http://paste.ubuntu.com/133688/ [15:11] its intresting how noisy it is even though i use quiet [15:12] ogra: no explosions yet? [15:12] not yet and i was even brave and just re-used the old initramfs from the former build [15:12] rolling a fresh one now to make sure [15:12] ogra: same thing with xmodem [15:13] weird [15:13] http://paste.ubuntu.com/133690/ [15:13] But without initramfs [15:13] It's depressing [15:13] hmm, i'm not sure the -b 0x100000 is right without initramfs [15:14] look on the wiki [15:15] It's the same I used in the past and that I use for zImage_DVI [15:15] hmm [15:16] wiki says RedBoot> load -m ymodem -b 0x01000000 -r though [15:16] shouldnt differ [15:16] oh, wait [15:16] 0x01000000 != 0x100000 [15:16] 0x01000000 is the address used for the initramfs [15:17] which needs to be loaded first [15:17] ogra: Yes, but the wiki mentions that for "an image" [15:17] I think it's wrong though [15:17] so its likely that 0x01000000 gets copied into ram first [15:17] Anyway, it works fine with other kernels with 0x100000 and you use 0x100000 for kernel as well [15:17] Oh I know [15:18] yes [15:18] * lool bangs head [15:18] PFF [15:18] ogra: RedBoot version [15:18] *again* [15:18] oh [15:18] indeed i use NCommanders [15:18] All makes sense now [15:18] ogra: You need 2.6.28 redboot for 2.6.28 kernel and I was running 2.6.26 with its redboot still [15:18] indeed [15:18] Two times I kill almost a day because of redboot version [15:18] you said zImage_DVI [15:19] * ogra killed a day because he didnt have lrzsz installed on the host [15:19] *that* was silly [15:20] having a wrong redboot version is rather in the middle of sillyness in taht light imho ... not on the edge [15:20] ogra: you're not complaining yet. I am getting worried... [15:20] amitk, xmodem*ing initramfs atm [15:20] let me reboot [15:20] and then hammer the system a bit [15:27] amitk, cross your fingers, booting now [15:27] * amitk crosses fingers, hands, legs [15:27] boot looks fine for a start [15:28] gdm is up ... [15:29] oh, usb errors in demsg [15:29] *dmesg [15:29] [42949494.010000] usb-storage: -- transfer complete [15:29] [42949494.010000] usb-storage: Bulk command transfer result=0 [15:29] [42949494.010000] usb-storage: usb_stor_bulk_transfer_sglist: xfer 4096 bytes, 1 entries [15:29] [42949494.010000] usb-storage: Status code 0; transferred 4096/4096 [15:29] [42949494.010000] usb-storage: -- transfer complete [15:29] [42949494.010000] usb-storage: Bulk data transfer result 0x0 [15:29] [42949494.010000] usb-storage: Attempting to get CSW... [15:29] [42949494.010000] usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes [15:29] [42949494.010000] usb-storage: Status code 0; transferred 13/13 [15:29] [42949494.010000] usb-storage: -- transfer complete [15:29] [42949494.010000] usb-storage: Bulk status result = 0 [15:29] [42949494.010000] usb-storage: Bulk Status S 0x53425355 T 0x176e R 0 Stat 0x0 [15:29] [42949494.010000] usb-storage: scsi cmd done, result=0x0 [15:29] [42949494.010000] usb-storage: *** thread sleeping. [15:29] over and over [15:29] sounds like issues with their usb driver [15:30] sounds like NCommanders issue [15:31] mcasadevall: could you file a bug regarding your usb errors and tag it arm? [15:31] ogra: does it prevent us from going further? [15:31] let me see if it survives [15:31] amitk, sure, I think its a issue with my network adapter, since the USB storage seems to be okish [15:32] i seem to be able to run a dist-upgrade getting 30M [15:32] tail -f /var/log/messages doesnt show any probs atm [15:33] hmm, now i see a bunch of usb-storage related messages [15:33] hi...what is default window manager in ubuntu-arm port? [15:33] giedz, any WM you like ... the architecture has noting to do with the CPU [15:33] s/architecture/desktop/ [15:34] ok but is there any prefered? [15:34] amitk, i see a ton of messages, but the package installation seems to work regardless [15:34] amitk, will capture it for you once the dist-upgrade finished [15:34] afternoon ogra [15:34] hey Martyn [15:35] I'm going to have to wait for your drop :) I have a usb network adapter, but no way to use it until there are some kernel modules to load. *chuckle* [15:35] Martyn, http://people.ubuntu.com/~amitk/linux-image-FINAL-2.6.28-11-imx51_2.6.28-11.35_armel.deb [15:36] that seems to be relatively good (just testing it here) [15:41] ARGH [15:41] * ogra wasnt aware DPMS works on babbage ... [15:41] i just thought my X crashed [15:41] :P [15:42] Heh [15:43] DPMS works great in babbage [15:43] I've come to a blank console :) [15:43] apparently [15:44] Now .. if we could only coax DVI to work :) [15:44] not without a public driver [15:45] * Starting AppArmor [15:45] * Loading AppArmor module... [15:45] ...fail! [15:45] pffft [15:45] good [15:45] the exclamation mark is really overreaction [15:46] * ogra grabs the source and adds ...fail! (omg, OMG !!!!) to make it look more scary :P [15:49] amitk, still not died, but /var/log/messages looks really worrying [15:51] amitk, http://paste.ubuntu.com/133715/ [15:52] amitk, and /var/log/messages grew from 10 to 408k since i started the dist-upgrade, its completely filled with these messages [15:53] ogra: I'm not too worried. It seems to be restricted to their storage driver. Fixable at a later date. [15:54] apart from the fact that we will try to do installs to a USB device with beta i tend to agree [15:56] ogra: So yeah, it was definitely redboot and only that [15:56] I'm booting into my system just fine now [15:57] cool [15:57] With VGA and all [15:57] i just had a reboot notification after dist-upgrade :) [15:57] so that works as well :) [15:57] do you have a binary for fis ? [15:57] so i can try to update my SD from the running system [15:59] ogra : I've got errors loading the modules, I'm afraid [15:59] ogra : 'invalid module format' [16:00] ogra: Sure [16:00] ogra: I'm mostly running it from my desktop though [16:00] then your initramfs isnt in sync with your kernel [16:00] ogra: Let me write a flash-kernel alike script [16:00] lool, oh, so no armel build ? [16:00] oh snap [16:00] ogra: I have one as well, but am not using it much now [16:01] sure, that makes sense [16:01] ogra: http://people.ubuntu.com/~lool/fis-armel [16:01] ogra: I updated redboot and kernel with fis on my desktop to boot into 2.6.28 [16:02] Works fine [16:02] but no initramfs yet, right ? [16:02] No [16:02] ogra: Needed a working system first [16:02] ogra: But that's *easy* ;-) [16:02] indeed, like me [16:02] ogra: would making the various filesystems (ext2, 3, fat, vfat) as modules cause your problems? [16:02] ogra: Will write a flash-kernel alike script now [16:02] Unless you like to [16:03] ogra: from perspective of updating an image [16:03] amitk, once lool has the script ready he just talks about it wonmt [16:03] lool, no, feel free [16:03] * amitk will leave them compiled-in for a little more then [16:03] i'll go on poking on my image creation tool [16:03] amitk: Why make them modules? [16:03] amitk, though arent ext2/3 in the normal ubuntu kernels as well now ? [16:04] amitk: it's going ot be harder to boot without initramfs, and I don't think it's what we do on i386 [16:04] i thought Keybuk had pulled them in for boot speedup [16:04] Yes [16:04] right, our kernel should be as close to the distro kernel as possible [16:04] oh "system has a crash report detected" ... [16:05] seems apport works too [16:06] lool, do you also have the prob that the vga picture is slightly shifted to the top on the screen ? [16:06] it swallows the upper third of the top panel here and i cant get it moved down [16:06] ogra: My LCD autoadjust [16:06] ogra: I'm running console ATM [16:06] (under X) [16:07] ah [16:07] console is fine here [16:07] ogra : Are you running from flash, or USB? [16:07] SD or USB I should say... [16:07] its just the desktop ... about 5-6px shifted to the top [16:07] Martyn, usb atm [16:07] console is fine here too [16:07] I'm using SD [16:08] both should work fine [16:22] mcasadevall, so you just copied the iso to a USB key ? [16:23] ogra, pretty much. cdrom-detector didn't find it, but I manually mounted it [16:23] what means "pretty much" ? [16:23] But its stuck ATM ... I dunno, I think the USB stack on my board leaves something to be desired w.r.t. to stability [16:24] mount usb key, loop mount iso ... cp iso/* usb-key/ ?? [16:24] or what exactly did you do ? [16:24] No, I did that [16:24] But once in the installer environment [16:24] mount /dev/sda1 /cdrom [16:24] "Load Installer Compontents from CD" [16:24] │ This partitioner doesn't have information about the default type of │ [16:24] ┌│ the partition tables on your architecture. Please send an e-mail │ [16:24] ││ message to debian-boot@lists.debian.org with information. │ [16:24] heh :-) [16:24] so far so good [16:24] how did you get *in the installer environment* [16:25] would be nice to have an alternate build you can just dd to SD [16:25] i.e. with the right boot mechanism in place [16:25] ogra, oh, loaded the RAMdisk from RedBoot [16:25] right [16:26] thats what i mean, we should have an alternate image that has redboot, kernel and initramfs ready to dd it to SD [16:26] That's the idea [16:26] Its easy to do extactly that. [16:26] so you just need to grab the iso/img file [16:26] But I wanted to see if the damn thing would work :-) [16:27] partman is going to need some work [16:28] talk to cjwatson for that [16:29] we'll likely need that for ubiquity too [16:29] damn it [16:29] "Failed to determine toe codename of the release" [16:29] So there are a few bugs to work out. [16:30] Actually [16:30] We got an anonyingly large issue [16:30] "Unknown armel subarchitecture: unknown" [16:30] Obviously thats something in the filesystem MIA [16:36] ogra, so libdebian-installer requires re-education :-) [16:40] right the subarch thing is somethng i talked with colin about before but didnt file a bug yet and didnt approach him further about [16:40] ogra: btw, are you using aufs now or unionfs? [16:41] amitk, heh, neither, i'll test that soon [16:41] my usb disk is ext3 [16:41] ogra : Ah! So you did a full install... [16:41] (sorry, i'm in a short 1:1 meeting atm) [16:41] I'm building a rootfs right now [16:42] ogra : no worries. [16:42] Martyn, right i built a rootfs using my script and untarred it to a usb HD [16:42] lool : Do you have a matching initrd to go with that kernel? [16:42] and use an SD to boot that [16:43] I'm doing much the same, but using a usb enclosure with a 7200 rpm drive. [16:44] me too [16:44] :) [16:44] Martyn: will soon [16:44] a kernel compile takes less than 1h with all modules :) [16:44] on that fast disk [16:46] *nod* [16:46] I tried a 10k RPM drive, but the enclosure was just too frigging loud [16:46] It sounded like a small airplane about to take off [16:46] heh [16:46] So I switch it out for a WD eco-drive/green drive. 1Tb, 7200rpm, 32mb cache [16:47] most of the time it sits idle, and that's perfect [16:47] heh, i have the same setup, but a maxctor drive [16:47] *maxtor [16:47] ogra : Hey, I just rebuilt the initrd, and still have the module format error. *grump* [16:47] did you transfer it to the SD ? [16:47] yep [16:48] weird [16:48] Can I borrow yours and compare? [16:48] I must be doing something wrong [16:48] * ogra looks for an envelope to send his [16:48] :P [16:48] *groan* [16:48] oh, you mean the initramfs [16:48] No, not the SD .. the initramfs [16:48] i thought my SD [16:48] yep :) [16:49] and if I wanted to borrow your sd, all you'd have to do is dd of=myfile anyway :) [16:49] ogra, so I'm pushing my branch to LP now, and I'll have to start looking at libdebian-installer ;.; [16:49] mcasadevall : It doesn't fail gracefully eh? unknown subarchitecture causes a crit fail? [16:50] mcasadevall, make sure do coordinate with #ubuntu-installer [16:50] ogra, I am. I'm popping back and forth between the two channels. [16:50] Martyn, http://people.ubuntu.com/~ogra/arm/babbage/initrd.img-2.6.28-11-imx51 and http://people.ubuntu.com/~ogra/arm/babbage/vmlinuz-2.6.28-11-imx51 [16:51] * ogra goes for a break [16:52] ogra : Got 'em [17:49] amitk, aufs looks ok so far, i need to wait for tomorrows build to actually test it since i need the updated procps in the squashfs [17:50] ogra: ok. I've pushed the changes to git and build-tested. rtg has done the same. So we might have a good kernel tomorrow. [17:51] yay [17:51] and with the fixed procps even a live image that can be used [17:53] ogra: is imx51 live image created automatically now? [17:53] not yet, no [17:53] still some missing bits and pieces, i have the skeleton work done to rolla partitioned image and copy the livefs in [17:54] tomorrow evening i sould have a working script [17:54] creating one manually on top of my old image is easy though [17:55] just copy the latest livecd image content into the second partition, pull vmlinuz and initramfs from http://people.ubuntu.com/~ogra/arm/babbage/ and replace them via serial [17:56] ogra: would be nice to have an installable image [17:56] eventually [17:56] yeah, indeed [17:56] that might only happen post beta though [17:57] we dont know how ubiquity behaves yet [17:57] and its a bit tricky since you will need an usb SD cardreader to install to, or we need to trash the install media [18:15] even if we don't have an installer, the rootfs builder provides a system that is just about the same when finished [18:15] So short term, you end up with a working desktop [18:16] (well, working-ish) [18:16] indeed, but release target is an installable image [18:16] preferably a live image [18:16] abolutely! [18:16] I'll take what I can get though. [18:16] Thank you for the initrd + kernel .. that helped a lot [18:16] great [18:35] root@babbage:~# flash-kernel [18:35] Flashing kernel... done. [18:35] Flashing initramfs... done. [18:36] Ok, system still boots without initramfs [18:36] Now let's see with a proper boot script [18:38] lool : Did you just compile in all the drivers needed to get to console? [18:38] Martyn: I used the .debs provided above [18:40] mm [18:43] ogra: What do you put on your initrd aware command line? [18:43] exec line [18:43] I mean in the -c part [18:43] Ah wait, you mentionned cmdline [18:43] 15:52 < ogra> console=ttymxc0,115200 root=UUID=ae90832f-ba0d-4164-b710-0402041ab8ed [18:43] nothing [18:44] e -r 0x1000000 -s 3927720 -c "console=ttymxc0,115200 console=tty1 boot=casper LIVEMEDIA=/dev/mmcblk0p1" [18:44] RedBoot> fis load initrd [18:44] for the live image [18:44] ... Read from 0x1fee0000-0x1feff000 at 0x00040000: . [18:44] Not a loadable image - try using -b ADDRESS option [18:44] Hmm [18:44] fis load initramfs [18:44] ogra: did you manage to put it in fis? [18:44] Martyn: it is called initrd [18:44] in fis list [18:44] ah [18:44] Martyn: Probably I used wrong params, happy to hear what I should use [18:44] RedBoot> fis list [18:44] Name FLASH addr Mem addr Length Entry point [18:45] initrd 0x00460000 0xFFFFFFFF 0x00940000 0x00100000 [18:45] RedBoot> fis list -d [18:45] Name FLASH addr Mem addr Datalen Entry point [18:45] initrd 0x00460000 0xFFFFFFFF 0x002A8EE7 0x00100000 [18:46] lool, do you use 0x1000000 as base address for it when dumping it into place ? [18:47] ogra: Ah no, I see what's wrong now [18:47] mem addr and entry point are reversed [18:47] I should have entry point == 0xffffff and not mem addr [18:48] yeah [18:48] initramfs 0x00060000 0x01000000 0x00400000 0x01000000 [18:48] thats what i have [18:50] what's the RedBoot command to load in something from serial, so you can flash it? [18:51] load -m xmodem -b 0x1000000 -r [18:51] fis create initramfs [18:51] Unfortunately, I can't get the ram address / load address from the fis command [18:51] load -m xmodem -b 0x100000 -r [18:51] I have hardcoded it for now [18:51] Need to extend the command [18:51] fis create kernel [18:51] Ok, fis load initrd works now [18:51] ah! xmodem :) [18:51] thanks [18:51] Now let's get the initrd to be picked up [18:52] thats tricky [18:52] since you need the size in the exec cmd [18:52] so with each initramfs update we have toi touch the cmdline [18:52] ogra: Well I think we shouldn't need the size in the exec command [18:53] I'd rather *not* touch the cmdline that'd be awful :-/ [18:53] you have to [18:53] it wont boot without [18:53] ogra: my thecus doesn't need that and uses redboot [18:53] we can use padding and fill up initrd with zeroes [18:53] nopt the FSL redboot [18:53] I can do that [18:53] (padding) [18:54] with padding the size can always be the sanme and we can use a fixed parameter in exec [18:54] ogra: even with padding, it doesn't set the address on the cmdline in the exec command [18:54] exec -c "console=ttyS0,115200 root=/dev/ram0 initrd=0xa0f00000,42M mem" [18:54] is all there is [18:54] Sorry, that's cut [18:54] exec -c "console=ttyS0,115200 root=/dev/ram0 initrd=0xa0f00000,42M mem=128M@0xa0000000" [18:54] That's a full line from the boot_script_data [18:55] right, but with debian kernel and initramfs [18:55] Well with any [18:55] * ogra tries to boot without -s parameter [18:56] [42949379.640000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0) [18:56] nope [18:57] ogra: It worked better for me [18:57] ogra: I can actually boot with exec -r 0x1000000 -c ... but it prints an error during boot and ignores initramfs [18:57] heh [18:57] let me switch console to serial to copy paste it [18:58] RAMDISK: Compressed image found at block 0 [18:58] RAMDISK: incomplete write (-28 != 32768) 4194304 [18:58] right [18:59] oop [18:59] that's bad [18:59] thats what you get if exec doesnt get the size handed over [18:59] You think that's solved by padding? [18:59] padding to 5000000 [18:59] and using exec -r 0x1000000 -s 5000000 [18:59] i *assume* that fixes it [18:59] well, at least then the boot script will be consistent [18:59] I'll try it. [19:00] ogra: I'd liket to avoid the size part [19:00] yu wont [19:00] I'm uploading a ramdisk now, so it's just a little extra work to overlay the initrd onto a blank file made with dd if=/dev/zero of=initrd.template bs=1k count=5000 [19:00] else we need to fix the redboot we have now [19:01] According to the redboot manual, -s is mandatory [19:01] I wish the RedBoot supported zmodem. (I switched to ymodem) [19:02] Too bad, I wish redboot would be clever just like for fis create after a load [19:02] what happens if you lie to redboot? [19:02] just tell it -s is 5000000 [19:02] even if the ramdisk is smaller... [19:02] right and pad [19:02] without padding [19:02] all it will do is load garbage bytes [19:02] oh, that *might* work [19:03] * ogra tries [19:03] <-- lazy [19:03] * Martyn so badly wants to try to bump the serial port up to 230k ... it takes forever to load things at 115k [19:04] [42949378.620000] RAMDISK: Compressed image found at block 0 [19:04] [42949378.900000] RAMDISK: incomplete write (-28 != 32768) 4194304 [19:04] :( [19:04] i guess we need the padding [19:10] blocksize seems to be 32768 [19:11] so 524288 should be a proper number for padding [19:11] (16 blocks) [19:13] is it really that bad to have to put in the length of the image when doing fis create? [19:15] fis create can take a lenght ? [19:15] oh, right [19:15] does that make -s not mandatory anymore ? [19:16] good question [19:16] I haven't tried it [19:17] it take ~4-5m for me to load the initrd via ymodem [19:17] I really wish the onboard NIC was working :) [19:17] yeah [19:17] then I could load via network, and bim-boom-bam :) [19:18] almost done with the upload [19:24] fis create is broken [19:24] it's not setting the length, I think [19:26] * ogra tries something [19:33] [42949379.550000] Please append a correct "root=" boot option; here are the available partitions: [19:33] [42949379.570000] b300 1956352 mmcblk0 driver: mmcblk [19:33] [42949379.580000] b301 714892 mmcblk0p1 [19:33] heh, so much for mounting a root filesystem from the mmc [19:34] RedBoot> fis create initramfs [19:34] ... Read from 0x1fee0000-0x1feff000 at 0x00040000: . [19:34] ... Read from 0x1fee0000-0x1feff000 at 0x00040000: . [19:34] Invalid FLASH image size/length combination [19:34] so much for padded initramfs [19:36] * ogra tries a smaller one [19:36] btw .. I booted just fine now [19:36] i'm stuck in the initramfs [19:36] but I did get a boot :) [19:37] with the padded intiramfs ? [19:37] no padding [19:37] but ? [19:37] what did you do ? [19:39] oh, nm [19:39] I forgot to write the fconfig [19:39] So I tried with padding and failed [19:39] it reverted to using your commandline [19:39] me too [19:39] But hex addresses are support for -s just fine [19:39] how big did you make it ? [19:39] I checked the source code and -s is required [19:39] ogra: 0x00940000 [19:39] 4980736 bytes [19:39] is what i'm trying atm [19:39] okay, so after the upload, every time, you have to check the size of the initrd then [19:39] using the pad script from d-i [19:40] ogra: I used the same padding as for N2100 [19:40] Martyn, right, and thats what we try to get around atm [19:40] Now searching for kernel stuff [19:41] i tried 5013504 before but seems redboot finds that to big [19:42] [42949379.550000] Please append a correct "root=" boot option; here are the available partitions: [19:42] [42949379.570000] b300 1956352 mmcblk0 driver: mmcblk [19:42] [42949379.580000] b301 714892 mmcblk0p1 [19:42] Oh perhaps my ramdisk is too big [19:42] oops, wrong one [19:42] [42949378.130000] RAMDISK: Compressed image found at block 0 [19:42] [42949378.180000] RAMDISK: ran out of compressed data [19:42] [42949378.190000] invalid compressed format (err=1) [19:42] Martyn, right, thats what you get if you give a to big size [19:42] crap [19:43] (bigger than the actual initramfs) [19:43] I'm trying to locate the ramdisk decompression code, the ATAG parsing one can't help us [19:43] The size I gave was only 0x003e000 [19:43] init/do_mounts_rd.c [19:43] so we're attacking from two sides now :) [19:44] So >-------printk(KERN_ERR "RAMDISK: incomplete write (%d != %d) %ld\n", [19:44] >------- written, outcnt, bytes_out); [19:45] written = sys_write(crd_outfd, window, outcnt); [19:45] => -28 is an error [19:45] yes [19:45] ENOSPC [19:46] window = kmalloc(WSIZE, GFP_KERNEL); [19:47] RedBoot> fis create initramfs [19:47] ... Read from 0x1fee0000-0x1feff000 at 0x00040000: . [19:47] ... Read from 0x1fee0000-0x1feff000 at 0x00040000: . [19:47] Invalid FLASH image size/length combination [19:47] GRRR ! [19:47] I got the same [19:47] WSIZE is 0x8000 [19:48] out_fd = sys_open("/dev/ram", O_RDWR, 0); [19:48] Eh PPC and S390 have a spinner when loading the ramdisk [19:49] yep [19:49] it's just so unfair :) [19:49] I say we make a cooler, better progress loading bar, and show 'em [19:49] -snicker- [19:50] ( We hacked the cobalt kernels, back in 2.4, to output to a parallel LCD panel, and show a graphical loading bar .. it was silly as all hell ) [19:50] lool, do we really want to get stuck on that now ? [19:50] ogra : no :) [19:50] lets just rewrite fconfig [19:50] -laugh- [19:51] i know you would like to get around it, but thats the way that waorks atm [19:51] *works [19:51] ogra : It's not really worth it, is it? We're not going to be using redboot forever, right? [19:51] just until u-boot gets ported and mature. [19:51] hopefully not ... [19:51] ugh [19:52] we have to run fconfig anyway to get the UUID in [19:52] I can't get the initrd to load [19:52] I tried specifying the -precise- -s length [19:52] okay, something's funny [19:52] make sure to load it first [19:54] I did [19:54] loads fine [19:54] but when the kernel boots, it's not there [19:55] or at least, I'm getting a vfs error [19:55] whats your current exec line ? [19:56] e -r 0x1000000 -s 4001525 -c "console=ttymxc0,115200 console=tty1 root=/dev/sda1 text" [19:56] 4001525 ? [19:57] right, thats proper [19:57] root=/dev/sda1 might be wrong though [19:57] try sdb1 [19:57] what would be taking up /dev/sda? the media card is mmcblk0p1 [19:57] and eventually use the UUID [19:57] nothing, sdX are no guaranteed names anymore [19:58] use UUID [19:58] root=UUID= [19:58] Which means I'll need to write a disklabel with the UUID :) [19:58] no [19:58] you have a uuid already [19:58] its created if you format the partition [19:59] at the initramfs prompt: ls -l /dev/disk/by-uuid/ [20:00] ogra: Updating the config is really painful [20:00] lool, we have to do it anyway [20:00] ogra: Why so? [20:00] got it [20:00] mxc_ipu mxc_ipu: VSyncPre occurred before DI1 disable [20:00] to get the device uuid into the append string after install [20:01] lool, thats your display being switched on and off [20:01] ogra: indeed [20:01] i would propose we concentrate on a better way to write fconfig [20:02] ogra: Ok; it's enough for me for today though [20:02] instead of trying to hack the current working boot methor [20:02] *d [20:02] lool, same here [20:02] ogra: I don't think it's hack if we get it to work sanely [20:02] I consider changing the size on each upgrade dangerous [20:02] i doubt we can [20:02] we will only end up with a hardcoded size or something i suspect [20:02] I don't think it's as bad as it could kill the flash, but it's risky [20:02] which isnt better [20:03] ogra: i don't mind a hardcoded size [20:03] It's not pretty, but it's not risky on upgrades [20:03] i would neither if it was easy ... i.e. through padding [20:03] but that apparently doesnt work [20:04] so we would have to dive deeply into redboot [20:04] and hack it up [20:04] i honestly prefer to rather find a sane way to update fconfig [20:04] ogra: I dived into redboot *already* [20:04] ok [20:04] We can't do anything with stock redboot [20:04] Unless we change it [20:04] I'm looking at the kernel now [20:05] My hope is that I can find a magic byte which stops the decompression [20:05] -s is very, very nonoptional [20:05] Another thing which would be worth trying is whether we can limit the initrd size at another level [20:05] booted to console, went with busybox rather than ubuntu rootfs [20:05] Martyn: I checked the redboot sources and it's not optional [20:05] we could fill up with zeros *before* compressing [20:05] packages/hal/arm/arch/current/src/redboot_linux_exec.c [20:05] search for ramdisk_size [20:06] ogra : They would be compressed away [20:06] And that's why I can assure you it supports hex, and hex worked for me [20:06] lool, nonoptional == not optional ;) [20:06] hex works for me just fine as well [20:06] sure [20:06] but what does hex gain us here [20:06] nothing really [20:06] right [20:06] ogra: I know, I said it earlier as well; I'm just repeating it because you seem to be doing the same research [20:07] no, i researched padding [20:07] I'm surprised, though, that it doesn't simply scan or set the length of the ramdisk image somewhere [20:07] rather than forcing the user to set it manually. There must be a reason... [20:07] ogra: hex> just replying to the fact that it was said to be broken, and it's not [20:07] fis has all the smarts to load it, and stuff the value somewhere... [20:07] the thing is, if we fill the cramfs with zeros before zipping it it might probably work [20:07] Martyn: Yes, that's why I checked as well; but it has not [20:07] not sure, but possible [20:07] We could implement it, but I don't want to rely on our redboot to be present [20:08] ogra: I did that already [20:08] Well, then we have to write the config each time, and there's no getting around it [20:08] lool, padding during compression ? [20:08] ogra: I created a 0x00940000 file with intiramfs contents + zeroes, checksummed that [20:08] every time the initrd and kernels are updated, the fconfig boot script likewise has to be updated [20:08] UNLESS [20:08] you want to do the two-kernel tango like they do in beowulf [20:08] load a kernel, that chainloads the new kernel and initrd from disk [20:09] ogra: Ah no, I didn't understand what you meant; I don't see how you'll get exactly the good size though [20:09] lool, right, but you likely padded zeros to the end of the already compressed file [20:09] lots of math ... [20:09] you only need to know the two values ... before and after [20:09] then pad cramfs to a certain size ... after gzip you should have the right final size [20:09] I think it might be enough to pass the initrd size to the kernel to stop decompression at EOG [20:09] EOF [20:10] in the -c command you mean ? [20:10] Yes [20:10] but that still means we need to run fconfig [20:11] No, I think it works with a zero padded initrd if we pass its size [20:11] I don't think you can get away from that one [20:11] no matter where you have to add the exact size in exec ... you have to submit it [20:13] ogra: it's just a cut size [20:13] That's my N2100 exec line: [20:13] exec -c "root=/dev/ram0 rw rootfstype=ext2 initrd=0x01000000,10M noirqdebug mem=32M@0x00000000 console=ttyS0,115200n8" 0x01d00000 [20:13] The 10M is just to stop the unzip I think [20:17] right, but exec still doesnt know what to do [20:17] ? [20:18] the -s tells it to load initramfs, no ? [20:19] Yes [20:19] so how do you tell exec what to do ? [20:19] Oh I still need the -s for bababge [20:19] I was pointing at initrd=0x01000000,10M [20:20] right [20:21] ogra, lool's command line works! [20:21] I just did it [20:21] no -f, no -s [20:21] just -c [20:21] Err 0x01d00000 is in the initrd [20:21] How come [20:21] Martyn: With the 0x01d00000? [20:21] no, without it [20:21] Ok [20:21] my line was -> [20:22] Martyn: For me it works, but the initrd isn't run [20:22] e -c "console=ttymxc0,115200 initrd=0x1000000,10M console=tty1 root=/dev/sdb1 text" [20:23] hmmm [20:23] [ 0.000000] Memory policy: ECC disabled, Data cache writeback [20:23] [ 0.000000] INITRD: 0x01000000+0x00a00000 extends beyond physical memory - disabling initrd [20:23] Interesting, I get the same message [20:23] I think you need to pass mem [20:23] what's the appended 0x01d00000? [20:24] It's the kernel entry point for N2100 [20:24] 0x00a00000 us lel start [20:25] is mem start [20:26] setting the mem= parameter had no impact [20:27] It hangs for me if I set mem [20:27] here too [20:28] it doesnt uncompress [20:28] I did mem=512M, and skipped the @ [20:28] though i assume we overwrite something [20:28] is initrd=0x01000000 REALLY what we mean? [20:28] that's where fis put it on the flash, but that's not where it got reloaded in ram, right? [20:29] right [20:29] In the case of my thecus it matches [20:30] anyway, i'm really exhausted [20:30] me too [20:30] You can't set mem alone without setting the start address [20:30] start = memparse(*p, p); [20:30] if (**p == ',') { [20:30] size = memparse((*p) + 1, p); [20:30] phys_initrd_start = start; [20:30] phys_initrd_size = size; [20:30] lool : Um, I do that all the time on the x86 platform... [20:30] heh [20:31] but not to define initrd size [20:31] Martyn: that's arm specific though [20:32] linux/arch/arm/mm/init.c [20:32] http://clug.open2space.com/node/10 [20:33] oops, sorry [20:35] * ogra calls it a day [20:35] my brain hurts and i dont see us getting anywhere by poking in the dark [20:36] nope. I'll look at redboot tonight, now that I've unpacked the fsl-redboot source [20:36] * ogra thinks its better to attack that after a relaxing night of sleep [20:36] I'm a few hours behind you, so I'm fresher [20:36] it's 15:30 here [20:36] note that we ise redboot-mxc from the archive [20:36] *use [20:36] oh! [20:36] is it downloadable? [20:37] (which actually is the same) [20:37] indeed [20:37] URI? [20:37] its in universe atm [20:37] apt-get source redboot-mxc [20:37] ports, universe? [20:37] gotcha [20:37] err [20:37] redboot-imx [20:38] sorry, to tired [20:38] no worries [20:38] downloading, and I'll take a read in a bit [20:38] you need to build it on the babbage though [20:38] I have a working-ish boot now, I can probably do it [20:39] but really, I should start poking through the source and understanding the exec code [20:39] and the load code [20:44] * ogra wonders what packages/redboot/current/src/fs/e2fs.c is :P [20:46] ogra: I told you rebdoot supported filesystems! :) [20:47] lets look at that tomorrow :) [20:48] ogra: Well I don't think our version has it [20:48] Unless it's a new drop, could be [20:48] Ah ours has e2fs but not fat [20:49] right [20:50] * lool & [20:50] i just pulled michales packge and found packages/redboot/current/src/fs/e2fs.c [20:50] sleep tight lool [20:50] * ogra is off as well now ... finally [20:51] http://people.ubuntu.com/~lool/flash-kernel [20:51] has the padding ATM [20:54] bah, you break my naming scheme [20:55] error "Cannot find FIS partition 'initrd'" [22:15] ogra: what did you use? [22:15] We could support multiple names easily in this place === Guest74361 is now known as Martyn