**** BEGIN LOGGING AT Thu Jan 06 02:59:58 2011 Jan 06 04:54:44 swalker * r24916 /packages/net/nbd/Makefile: [packages] nbd: update to 2.9.18, add kmod-nbd dependency, use PKG_INSTALL Jan 06 04:55:31 swalker * r24917 /packages/utils/dosfstools/Makefile: [packages] dosfstools: update to 3.0.11 Jan 06 04:56:08 swalker * r24918 /packages/mail/msmtp/Makefile: [packages] msmtp: update to 1.4.22 Jan 06 04:57:36 swalker * r24919 /packages/mail/fetchmail/Makefile: [packages] fetchmail: update to 6.3.19, add ssl/nossl variants Jan 06 08:44:01 hi, could anybody give me reasons why kernel 2.6.33 support was removed from the trunk? i did the OnRISC Alekto platform port based on that kernel Jan 06 09:10:46 qecko: because it is old and was not used by any supported target Jan 06 09:10:53 you wil need to update your port Jan 06 09:21:33 blogic: when i did the port there were other targets using 2.6.33... whatever, i think i'll do the patches for 2.6.35 then Jan 06 09:23:24 but when i do the patches for 2.6.35 now, will the support for this kernel remain? Jan 06 09:29:28 qecko: its like with upstream linux, as soon as stuff gets included ppl try to maintain it over updates, until it falls apart due to lack of work or knowledge on it, then its scrapped Jan 06 09:30:20 though openwrt never removed a target yet except brcm-2.4 Jan 06 09:33:10 xMff: oh, that one is gone for good? ;) Jan 06 09:33:51 yeah, I think so Jan 06 09:34:09 hooray! Jan 06 09:34:18 in trunk that is Jan 06 09:37:26 no mode development on brcm-2.4, but its has releases u can compile like 10.03 Jan 06 09:37:35 so what would be the best choise now 2.6.35, 2.6.36 or 2.6.37? which kernel has the best chances to stay maintained? Jan 06 09:37:37 no more Jan 06 09:38:31 i mean, i don't want to do the patches for 2.6.37 now and at the end it gets dropped again Jan 06 09:40:38 .35 is declared longterm, .36 is likely to stay for a while Jan 06 09:40:56 qrcko: .35 is a longterm maybe a good choice, but .37 will bring many improvments and probably will be the most used in future Jan 06 09:41:06 grep LINUX_VERSION:=target/linux/*/Makefile Jan 06 09:41:12 grep LINUX_VERSION:= target/linux/*/Makefile Jan 06 09:48:54 xMff: is b43 finally ready for prime time? Jan 06 09:49:07 nope, imo not Jan 06 09:57:47 in ad-hoc it seems to work nice Jan 06 10:01:44 jow * r24920 /packages/net/xtables-addons/patches/002-fix-kernel-version-detection.patch: Jan 06 10:01:44 [packages] xtables-addons: the configure first calls "make kernelrelease" which then triggers a silentoldconfig of the tree Jan 06 10:01:44 for the sole purpose of adding the localversion which is then stripped anyway. Let it call "make kernelversion" instead Jan 06 10:01:44 which does not have such issues. This patch should fix #8535. Jan 06 10:03:55 problem is that we still get reports of it dying in ap mode Jan 06 10:04:19 and really mixed outcomes, for some it is faster than the blob, for others it performs really bad Jan 06 10:18:39 xMff: sorry, no news yet about the ld.so Jan 06 10:37:05 strange Jan 06 12:40:32 build #55 of ppc44x is complete: Success [build successful] Build details are at http://tksite.gotdns.org:8010/builders/ppc44x/builds/55 Jan 06 14:44:49 build #50 of x86 is complete: Success [build successful] Build details are at http://tksite.gotdns.org:8010/builders/x86/builds/50 Jan 06 15:15:42 build #60 of s3c24xx is complete: Failure [failed shell_9] Build details are at http://tksite.gotdns.org:8010/builders/s3c24xx/builds/60 Jan 06 15:21:15 build #54 of ramips is complete: Failure [failed shell_9] Build details are at http://tksite.gotdns.org:8010/builders/ramips/builds/54 Jan 06 15:48:56 larsc: Is is possible to use the OpenWRT u-boot (compiled for a Seagate DockStar) as a one-stage bootloader replacing the original/factory u-boot on mtd0? Jan 06 15:53:39 mazilo: in theory yes Jan 06 15:54:32 larsc: Thanks. Do I need a special address location if I want to use the OpenWRT u-boot to replace the original one? Jan 06 15:55:07 build #59 of ppc40x is complete: Success [build successful] Build details are at http://tksite.gotdns.org:8010/builders/ppc40x/builds/59 Jan 06 15:56:45 larsc: The OpenWRT wiki only has a section on how to install the OpenWRT u-boot as a 2-stage bootloader. I sure would appreciate if you can provide instructions on how to install the OpenWRT u-boot for a Seagate DockStar as a 1-stage bootloader. Jan 06 16:01:27 mazilo: in theory it's the same, just use 0x0 instead of 0x100000 for base address. but i'm not sure right now if you don't have to adjust some offset in the image as well. Jan 06 16:03:25 ah, right now i remember. you need the .kwb image for the first stage bootloader Jan 06 16:07:29 larsc: Thanks. Jan 06 16:09:29 larsc: So, if I flash the OpenWRT .kwb image (perhaps also need to adjust the arcNumber), then perhaps I don't need to replace the original/factory u-boot? Jan 06 16:11:45 larsc: The reason I asked these questions is I just want to get rid off the original Pogo OS, consolidate mtd2 + mtd3 into a new mtd2, and put a bigger OpenWRT into the new mtd2 partition. This way, I can create a new OpenWRT firmware with more built-in packages and use an external USB partition to hold data. Jan 06 16:14:01 larsc: I am hoping your and/or kaloz who pioneered in this can revise the OpenWRT configurations for a Seagate DockStar to support 1-stage bootloader + to consolidate the existing mtd2 & mtd3 into a single mtd2 partition. Jan 06 16:14:23 larsc: Perhaps, make it as an option. Jan 06 16:30:41 mazilo: mtd2 is the kernel, right? Jan 06 16:42:55 larsc: I believe it is mtd1 where the uImage is located and mtd2 is the Pogo OS. Jan 06 16:43:28 larsc: Jan 06 16:43:29 Pogoplug:~$ cat /proc/mtd Jan 06 16:43:31 dev: size erasesize name Jan 06 16:43:32 mtd0: 00100000 00020000 "u-boot" Jan 06 16:43:33 mtd1: 00400000 00020000 "uImage" Jan 06 16:43:35 mtd2: 02000000 00020000 "root" Jan 06 16:43:37 mtd3: 0db00000 00020000 "data" Jan 06 16:45:15 ok, so you want to join the root and data partition Jan 06 16:53:58 larsc: Yup. Jan 06 16:57:14 you can do that with the 2-stage loader Jan 06 16:58:49 i don't want to keep you from using the openwrt uboot as the first stage loader, but i do not recommend it, unless you have a jtag adapter Jan 06 17:01:33 larsc: Thanks. Jan 06 17:02:45 larsc: If I use the 2-stage bootloader, it will occupied mtd1, won't it? Jan 06 17:04:57 it will, but the openwrt layout uses 1MB for mtd1 and 3MB for mtd2, while the original layout uses 4MB for mtd1. Jan 06 17:05:25 larsc: IC. Jan 06 17:05:35 so openwrts mtd3 and mtd4 are equivalent to the originals mtd2 and mtd3 Jan 06 17:05:57 larsc: IC. Jan 06 17:06:54 larsc: I am thinking to leave mtd1 intact with uImage and consolidate mtd2 & mtd3 into a big chunck of partition as mtd2. Jan 06 17:28:50 build #53 of rb532 is complete: Exception [exception failed slave lost shell_13 compile_12] Build details are at http://tksite.gotdns.org:8010/builders/rb532/builds/53 Jan 06 17:28:51 build #48 of uml is complete: Exception [exception failed slave lost shell_13 compile_12] Build details are at http://tksite.gotdns.org:8010/builders/uml/builds/48 Jan 06 17:28:53 build #46 of etrax is complete: Exception [exception failed slave lost shell_13 compile_12] Build details are at http://tksite.gotdns.org:8010/builders/etrax/builds/46 Jan 06 17:28:56 build #46 of ep93xx is complete: Exception [exception failed slave lost shell_13 compile_12] Build details are at http://tksite.gotdns.org:8010/builders/ep93xx/builds/46 Jan 06 17:52:20 build #47 of etrax is complete: Failure [failed compile_3] Build details are at http://tksite.gotdns.org:8010/builders/etrax/builds/47 Jan 07 01:35:40 build #48 of ixp4xx is complete: Success [build successful] Build details are at http://tksite.gotdns.org:8010/builders/ixp4xx/builds/48 **** ENDING LOGGING AT Fri Jan 07 02:59:58 2011