**** BEGIN LOGGING AT Sun Feb 19 02:59:58 2012 Feb 19 03:06:14 ok f. it. that thing is 100% useless Feb 19 03:06:19 error after error Feb 19 05:17:20 build #114 of xburst is complete: Failure [failed compile_10] Build details are at http://buildbot.openwrt.org:8010/builders/xburst/builds/114 Feb 19 05:56:26 build #114 of ixp4xx is complete: Failure [failed compile_10] Build details are at http://buildbot.openwrt.org:8010/builders/ixp4xx/builds/114 Feb 19 06:29:12 jow_laptop: ping Feb 19 08:54:17 philipp64|laptop ping Feb 19 08:54:54 you didn't get it working? Feb 19 08:55:06 I'll build you an image... Feb 19 09:17:00 no i didnt, i am building an image again with current trunk, with everything default.. Feb 19 09:17:32 i was to ask if there is a way that you could share your working image, just to test if it works here. maybe my build system is not correct.. Feb 19 09:17:58 thank for that :) Feb 19 09:29:57 crow: ftp://ftp.redfish-solutions.com/pub/openwrt-x86-alix2-combined-squashfs.img Feb 19 09:36:23 philipp64|laptop user and pass? Feb 19 09:38:09 Logging in as anonymous ... Login incorrect. Feb 19 09:55:11 looking... Feb 19 09:59:40 crow: not sure why it's failing. might be an rDNS problem with you IP address. Feb 19 10:02:51 hmm i am not sure to, but it fails. i dont have an sandbox to test it from somewhere else.. Feb 19 10:29:33 crow: well, if you have an FTP drop box, I can put it there. Feb 19 10:36:29 build #112 of kirkwood is complete: Failure [failed shell] Build details are at http://buildbot.openwrt.org:8010/builders/kirkwood/builds/112 Feb 19 10:39:02 build #144 of brcm63xx is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/brcm63xx/builds/144 Feb 19 11:00:09 when i compile for x86 alix i see in dmesg these unknown cmds http://paste.pocoo.org/show/z4g63pT9RfFCfqLciW0x/ Feb 19 11:10:35 philipp64|laptop maybe these ^^ are the reason why the image i build dont boot.. (but maybe) Feb 19 12:36:39 crow: yes grub fails Feb 19 12:36:59 but where is it spittoung out those messages ? Feb 19 12:37:06 looks like syslog output Feb 19 12:37:17 if syslog then it has booted Feb 19 12:39:21 WillieNL its when i compile a x86 image for my alix board, and yes in syslog, actualy the image i dd to CF doesn boot so am i trying boot it actually, and on build maching I did dmesg and saw these in log Feb 19 12:40:03 ok also i wonder wich toolchain do you use for building your own image ? Feb 19 12:40:24 outdated binutils + current gcc + unknown-libc -> fail Feb 19 12:40:44 my last builds grub just as it is in trunk simply worked flawless Feb 19 12:40:44 WillieNL checkout trunk, make menuconfig x86, alix2 ; make .. Feb 19 12:41:08 ahh eglibc or uclibc :) Feb 19 12:41:21 whatever default is. Feb 19 12:41:24 have you checked the bug reports if it is known ? Feb 19 12:42:04 but i gues uclibc: /alix.3d3/build_dir/target-i386_uClibc-0.9.33/root-x86 -v 2>&1 1>/dev/null | awk '/^.+$/' Feb 19 12:42:46 WillieNL actually i am waiting that philipp64|laptop upload his image so i can try and see if its my build system fubared or not Feb 19 12:43:19 hmmzz. Feb 19 12:43:33 are you trying to overwrite the alix image on a live running system btw ? Feb 19 12:43:43 <- just awake and waiting for coffee machine to finish Feb 19 12:44:24 WillieNL no i am not, i took CF to build system, and dd image to it. after inserting back, i see grub and it start to boot openwrt, but there is notting after "Booting the kernel". Feb 19 12:45:07 yes while think those ioctl messages are from the build system. Feb 19 12:45:27 when do they apear ? right afther removing the cf card when your shell prompt returns ? Feb 19 12:45:38 when i compile the image Feb 19 12:45:49 disk is not full ? Feb 19 12:45:51 i think at the end of compile, when it start to prepare image Feb 19 12:46:00 df -h Feb 19 12:46:14 no it isnt: build sys: rootfs 28G 12G 15G 45% / Feb 19 12:47:17 hmm sorry but right now no clue Feb 19 12:47:42 do you run make V=99 ? if so can you paste the last 45 lines from the build output ? Feb 19 12:49:08 i do make with V=99 and no errors there Feb 19 12:49:23 this is what happens when i put CF in alix.3d3 back and try to boot: http://www.abload.de/img/openwrt01rnux5.jpg Feb 19 12:50:53 looks like a incomplete image :0 Feb 19 12:50:54 :) Feb 19 12:51:13 WillieNL doesnt look like there was an error in build: http://paste.pocoo.org/show/hjmbZGDeG1HgDyn53b8p/ (except these in syslog) Feb 19 12:51:14 also your errors from the build machine are not normal Feb 19 12:52:56 WillieNL yea looks like an incomplete image, but i am not sure what to try or where to try, my build system is an archlinux x86_64 with mutlilib and uptodate as of yesterday. Feb 19 12:53:32 and regarding openwrt trunk also from today: r30641 Feb 19 12:55:59 hmm Feb 19 12:56:14 not sure about it Feb 19 12:56:30 multilib ? Feb 19 12:56:33 ehm... Feb 19 12:56:39 not tested that :) Feb 19 12:56:55 with arch i686 in vm works without errors Feb 19 12:58:04 i have an x86_64 for htpc, and compiling image there, i needed to install these in order to build for x86: http://dpaste.com/705169/ Feb 19 12:58:47 this error started afther your distro update ? else i think about one of the tools in your wrt build tree failed during build Feb 19 12:59:06 this error started when i try to build an x86 image, Feb 19 12:59:15 also theire is no need for multilib from x86_64 Feb 19 12:59:17 an wndr3700 build doesnt produce these Feb 19 12:59:37 thats the great deal about crosscompiling anyway.. Feb 19 12:59:51 WillieNL well make menuconfig prompted for mutlilib on my first x86 build try Feb 19 13:00:06 have you tested with that disabled ? Feb 19 13:00:20 since i do not remember multilib in wrt :) Feb 19 13:00:55 i cant compile openwrt image without it, thats reason i installed them Feb 19 13:01:02 wait let me remove them and try without.. Feb 19 13:03:06 crow: also if you wait a while possible some of the other people have a idea or know this problem Feb 19 13:04:42 hi Feb 19 13:05:18 <- coffea and breakfast :) Feb 19 13:05:25 same Feb 19 13:06:54 hmm 1.5TB sata drive was abiout 70 euro.. they still are +100~140 :S Feb 19 13:07:18 im askig all the other embedded distros about bcm47xx and ip8k ubicom32 v5 Feb 19 13:07:21 lol Feb 19 13:07:36 CcSsNET: other ? Feb 19 13:07:40 we all know linux is known for excessive fragmentation Feb 19 13:08:11 hmm ubicom nothing your on your own.. if you sucseed make people happy Feb 19 13:08:28 eh. openembedded, buildroot, yocto, angstrom, linaro, crosstool-ng, sbox2, ptxdist, many others Feb 19 13:08:46 heh, you won't find any of those with *proper* support for either of those two platforms Feb 19 13:08:47 and bcm47xx enough info known about those http://www.linux-mips.org/wiki/Broadcom_SOCs Feb 19 13:09:09 nbd most likely. but worth asking around Feb 19 13:09:10 but diy hacky :) Feb 19 13:09:30 CcSsNET: i know most of these distros, and i know that they don't properly support such devices Feb 19 13:09:45 nbd: are theire any people that ever did get theire ubicom routers stable ? Feb 19 13:09:46 ah Feb 19 13:10:06 as long i do not hear any non bug report about device lockups they are not worth the time anyway Feb 19 13:10:30 lol Feb 19 13:10:31 WillieNL: not many people working on ubicom stuff, in openwrt it's unmaintained Feb 19 13:10:45 nbd: jup and mmuless for my ip7k :( Feb 19 13:10:48 ok. so whats the best supported usb router? Feb 19 13:11:01 best for what? Feb 19 13:11:05 usb Feb 19 13:11:07 CcSsNET: openrd ? Feb 19 13:11:11 lol Feb 19 13:11:14 :) Feb 19 13:11:17 fast and usb Feb 19 13:11:25 widely supported by now Feb 19 13:11:30 like dockstar arm devices Feb 19 13:11:54 openrd is nnot a router Feb 19 13:12:04 stick a usb wifi dongle in it and tada Feb 19 13:12:15 i dont use wifi Feb 19 13:12:59 CcSsNET: but your soundling almosth like me 2 years ago :) Feb 19 13:13:09 make a list what do you wanna do and what do you need todo just that. Feb 19 13:13:24 then look for supported devices and afther all that start shopping Feb 19 13:13:34 meh Feb 19 13:14:09 i guess ill try working from the rt-n16 since i got it. Feb 19 13:14:18 ill just have to work from dd-wrt Feb 19 13:14:25 nbd: is mikrotik not something for CcSsNET ? atheros gbit switch Feb 19 13:14:47 mikrotik is slow is it not? Feb 19 13:14:51 lol Feb 19 13:15:24 ehh embedded is always not like lamborgini :) Feb 19 13:15:30 * CcSsNET pokes around openwrt menuconfig and tries to specify his own kernel Feb 19 13:15:32 CcSsNET: he didn't even say which device :P Feb 19 13:15:38 lol Feb 19 13:15:40 nbd: indeed Feb 19 13:15:47 ya but its a proprietary company as well Feb 19 13:15:57 its actually got linux support? Feb 19 13:16:10 they are one of the first i think Feb 19 13:16:23 are you guys actually trying to talk specifics, or are you just throwing random keywords around? Feb 19 13:16:38 nbd: i try to make sense but i don't get it :p Feb 19 13:16:44 CcSsNET: example s Feb 19 13:16:45 ? Feb 19 13:16:49 paste fail Feb 19 13:16:55 http://routerboard.com/RB751U-2HnD Feb 19 13:17:07 meh. why ask me for examples. ur the one that suggested them... Feb 19 13:17:18 runs at 400mhz yes.. but theire is no need for 2.8ghz on that :) Feb 19 13:17:32 some old cisco fancy routers where hardly running 266mhz on ppc :) Feb 19 13:17:41 ya i look at bogomips now a days anyway Feb 19 13:17:43 not mhz Feb 19 13:17:45 bad choice for usb stuff, imho Feb 19 13:17:54 bogomips -> nothing proofed at all Feb 19 13:18:08 still better then looking at mhz... Feb 19 13:18:17 disagree :) Feb 19 13:18:28 meh Feb 19 13:18:35 think as u wish Feb 19 13:19:15 bogomips with a anlaysis of cpu l2 cache size and u got a basis for performance review in a semi standardized way Feb 19 13:19:40 nbd: for usb dunno wat will be best choise togo. personal think about those kirkwood devices that mosthly come with 4 usb2.0 ports and 256mb ram Feb 19 13:19:59 ooo that sounds nice Feb 19 13:20:11 i'd say get some cheap x86 atom board or something if you need high throughput for usb Feb 19 13:20:11 4usb, 256mb. which devices are those? Feb 19 13:20:42 WillieNL reason for mutlilib on x86_64 and archlinux http://dpaste.com/705177/ Feb 19 13:20:49 CcSsNET: marvell kirkwood -> pogoplig/dockstar/openrd board Feb 19 13:20:57 k Feb 19 13:21:42 ahh ok so using vmware/vbox for i686 was not a time whaste :) Feb 19 13:21:43 WillieNL so yes they are needed. Feb 19 13:21:48 crow: thanks Feb 19 13:22:57 WillieNL np, still is the question if these errors in syslog can fubar an image.. Feb 19 13:23:36 nbd do you have maybe any suggestion for this: http://paste.pocoo.org/show/z4g63pT9RfFCfqLciW0x/ Feb 19 13:24:33 crow: yeah, just ignore it Feb 19 13:24:59 lol Feb 19 13:25:41 crow: grub thinks it's installing to a disk, so it does all kinds of weird ioctl crap, which the kernel will happily ignore Feb 19 13:30:21 nbd so these are safe to ignore? as after i do "dd" this x86 to CF and plug into alix.3d3 i get only this: http://www.abload.de/img/openwrt01rnux5.jpg Feb 19 13:31:16 what kind of device? Feb 19 13:31:30 ALIX.3D3 Feb 19 13:32:07 have you tried connecting something to the serial port Feb 19 13:32:10 http://pcengines.ch/alix3d3.htm Feb 19 13:32:49 nbd no as i dont have that hw jet, i ordered an "nokia" cable for old asus wl-500gpv1, but i am not sure if it would work with alix serial port to Feb 19 13:33:04 for the alix you use a normal nullmodem cable Feb 19 13:33:06 the nokia cable method works nicely Feb 19 13:33:09 not one of those 3.3v things Feb 19 13:33:13 iirc Feb 19 13:33:21 but you need to verifly target device is 3.3v Feb 19 13:33:34 -l Feb 19 13:33:36 alix is normal pc hardware Feb 19 13:33:44 with a normal serial port Feb 19 13:33:53 o Feb 19 13:34:34 nbd so just to plug normal "null modem kabel" and use putty or something like that to get info? Feb 19 13:34:58 yeah, just to see if the kernel is printing some early stuff when it's not booting Feb 19 13:35:18 ehh nokia pl2303 sticks can run 3.3v and 5v if it is a 2303hx Feb 19 13:35:30 they can also auto sense if you modify them Feb 19 13:35:48 WillieNL: it's still unsuitable for crow's purposes Feb 19 13:36:06 nbd: yes if it have a real rs232 then he need nullmodem :) Feb 19 13:36:24 ahh Warning: Pin 4 of PL-2303HX cannot support 5V (Only 1.8 to 3.3V). Feb 19 13:36:50 from datasheet Feb 19 13:36:59 nbd will take a while to find my null modem cabel i used, Feb 19 13:51:52 nbd: do you know if anyone ever did get those allied data copperjet adsl modems working ? bcm43 and bcm6xxx devices ? Feb 19 13:54:54 no idea what 'those allied data copperjet adsl modems' are Feb 19 13:55:51 ehh ancient adsl and adsl2 modems Feb 19 13:56:13 they still can be used as a rs232 over lan or i2c Feb 19 13:56:32 no idea Feb 19 13:56:46 hauke * r30642 /trunk/package/mac80211/Makefile: Feb 19 13:56:46 mac80211: fix directory of mwl8k firmware Feb 19 13:56:46 Thank you Eugene San for the patch Feb 19 13:57:32 ok Feb 19 13:59:01 Hi. I want to customize my kernel options. But this does not seem to work: http://wiki.openwrt.org/doc/techref/buildroot#customizing.the.kernel.options Feb 19 14:03:52 My changes seem to get overwritten on make Feb 19 14:29:12 olistudent_: no idea who added that part of the wiki, but it's completely wrong Feb 19 14:29:26 :-) Feb 19 14:29:47 nbd: Is there another way than overwriting the defaults for generic and special arch? Feb 19 14:29:58 do you want the changes to be made to the existing files in the tree, or do you want them to be stored separately? Feb 19 14:31:44 heh, this wiki page is funny Feb 19 14:31:52 it seems that >90% of that page are wrong Feb 19 14:31:56 i should probably delete the whole thing Feb 19 14:32:33 I'm trying to get an openwrt image running on an unsupported device with different mtd layout. So I need a quick and simple way to change some config options like cmdline and so on... Feb 19 14:34:49 olistudent_: if you're not using ./scripts/env yet, simply call ./scripts/env new to ensure that ./env/ is created Feb 19 14:34:58 then run make kernel_menuconfig CONFIG_TARGET=env Feb 19 14:35:11 it will store your kernel config changes in an overlay file in env/ without touching files under version control Feb 19 14:35:28 hauke * r30643 /trunk/package/ (4 files in 3 dirs): Feb 19 14:35:28 mac80211: add brcmsmac driver Feb 19 14:35:28 brcmsmac does not work on bcm47xx based devices or has AP mode support for now. Feb 19 14:35:40 Hm, not document anywhere in the wiki? :-) Feb 19 14:36:30 btw Thank you for this samba36 multicall binary. I have been looking for this for years... We took it over already to Freetz. ;-) Feb 19 14:38:18 :) Feb 19 14:38:45 i haven't really looked at the wiki structure a lot, so not sure where this information fits there Feb 19 14:39:03 i deleted the page that you linked to, so that it doesn't confuse more people Feb 19 14:42:27 nbd: Okay. This seemed to work. How do I build this new configuration? Feb 19 14:42:34 just run maek Feb 19 14:42:35 make Feb 19 14:42:48 Ah, it symlinked TOPDIR/.config. Feb 19 14:43:07 scripts/env symlinks .config and files/ Feb 19 14:43:49 the kernel config changes are in env/kernel-config afterwards Feb 19 14:43:55 but only the changes, not the full config Feb 19 14:44:14 And the changes do get merged with the defaults? Feb 19 14:46:28 yeah, the build system always creates the final .config by merging different files anyway Feb 19 14:47:14 the order is Feb 19 14:47:18 nice Feb 19 14:47:25 module selection is autogenerated based on the kmod-* packages that you select Feb 19 14:47:44 and with the kconfig.pl script that it uses, it can not only merge configs, but also split them Feb 19 14:48:08 the CONFIG_TARGET variable also supports 'platform' and 'subtarget' Feb 19 14:48:12 to select what config you want to make changes to Feb 19 14:51:09 I do have a rt3052 devices which gives me strange squashfs read errors and failures when reading/writing from/to jffs2. So I wanted to try if it's hardware related or software (ralink sdk vs. openwrt)... Feb 19 14:51:33 hauke * r30644 /trunk/package/mac80211/patches/880-brcmsmac_suspend_signature.patch: mac80211: brcmsmac: fix a build warning, till we update bcma Feb 19 14:53:08 i highly suggest avoiding using jffs2 as a safe solution to anything Feb 19 14:53:17 but thats my opinion Feb 19 14:53:31 Hm, what fs do you suggest on kernel 2.6.21? ;-) Feb 19 14:53:51 squashfs with a ramdisk Feb 19 14:54:01 its more reliable even if u need to keep backups Feb 19 14:54:14 Very reliable in case of powerloss... Feb 19 14:54:31 nice sarcasm Feb 19 14:54:37 * CcSsNET points at backup Feb 19 14:55:26 jffs2 is very good at dealing with power loss Feb 19 14:55:48 i think in large parts because it's a log structured filesystem (unlike what the name implies) Feb 19 14:56:36 yes it may solve the power loss problem but it introduces the oops i acidently bricked it problem for people that use ssh more then webui Feb 19 14:59:22 considering i dont use a webui at all. i have bricked 2 devices accidently because of the way jffs2 works Feb 19 14:59:57 remount it readonly if you are playing. Feb 19 15:00:06 they didnt cost much though. wrtu54g-tm Feb 19 15:00:12 yea i guess Feb 19 15:00:51 i may attempt to jtag them at some point. use them as the teach myself jtag devices Feb 19 15:00:53 lol Feb 19 15:00:54 CcSsNET: how did you brick the devices? Feb 19 15:01:04 just editing files Feb 19 15:01:23 yeah, openwrt doesn't protect against users shooting themselves in the foot Feb 19 15:01:26 acidently didnt change directory once when wgeting something on the other Feb 19 15:01:45 at least in recent versions, wget doesn't overwrite by default Feb 19 15:01:54 so it's hard to break something that way Feb 19 15:01:55 yea but i just highly suggest avoiding jffs2 if u use ssh more then webui Feb 19 15:02:05 just do ramdisk for sanity sake Feb 19 15:02:37 i think that's unnecessary Feb 19 15:02:38 and a cheap battery backup Feb 19 15:03:18 i'd say ramdisk is easier to screw up Feb 19 15:03:21 you think so, but i think its not a good pair for ssh users Feb 19 15:03:26 because it's easy to forget to write your changes to flash Feb 19 15:03:35 and then on a reboot they're suddenly lost Feb 19 15:03:45 duh... common sense Feb 19 15:04:04 id rather have a common sense issue then a woops i bricked it issue Feb 19 15:04:17 well, not bricking your device is also a common sense issue Feb 19 15:04:23 not really Feb 19 15:04:29 if you know what you're doing, it is Feb 19 15:04:32 ;) Feb 19 15:04:39 jffs2 from that perspective is a must learn as you go type of scenario Feb 19 15:04:49 your almost garanteed to brick one first time Feb 19 15:05:13 i don't consider a messed up file in jffs2 a brick Feb 19 15:05:16 as long as failsafe works Feb 19 15:05:27 from that perspective, it's actually quite hard to brick your device Feb 19 15:05:30 accidentally Feb 19 15:05:36 which on wrtu54g-tm doesnt have as far as i know Feb 19 15:05:55 what platform is that? Feb 19 15:06:04 infineon adm8668 Feb 19 15:06:14 64mb ram, 8mb flash Feb 19 15:06:18 mipsel Feb 19 15:06:30 so somebody should add button support to make failsafe work Feb 19 15:07:13 it might have been done already. just havent looked into it Feb 19 15:07:19 wiki.scottn.us Feb 19 15:11:03 but no. im not using his firmware so if it is implimented by him. its not on my device most likely :) Feb 19 15:11:35 bbl Feb 19 15:29:45 CcSsNET: in 1.5 year i have not bricked a single device :) Feb 19 15:29:50 read then do ;-) Feb 19 15:30:07 always double check how to rescue and wat never todo Feb 19 15:30:57 nbd: can u-boots default webif based failsafe not be used ? Feb 19 15:31:06 nbd: like on those dlink ubicom devices for example :) Feb 19 15:31:14 uboots default? Feb 19 15:31:18 what's that supposed to mean? Feb 19 15:31:21 yes theire is a httpd in uboot Feb 19 15:31:30 ok, it's not a uboot defaut, it's d-link specific stuff Feb 19 15:31:34 and that's not failsafe Feb 19 15:31:39 that's just a method for reflashing Feb 19 15:31:48 second method for flashing yes. Feb 19 15:31:51 with failsafe you can actually mount your rootfs overlay and fix things Feb 19 15:31:52 aka recovery Feb 19 15:31:55 instead of nuking everything Feb 19 15:32:03 right then i'm wrong indeed Feb 19 15:32:53 nbd: since i had my dlink a few times semi bricked pressed 15 sec on reset during powerup and tada device runs a diffrent webif Feb 19 15:33:08 but the 15sec press do flush the flash Feb 19 15:34:00 handy for people without rs232 debugging Feb 19 15:37:55 nbd: something wrong with latest bison changes. Feb 19 15:38:04 bison: cannot open file `/home/peter/Candi/openwrt/staging_dir/host/share/bison/m4sugar/m4sugar.m4': No such file or directory Feb 19 15:38:28 http://pastebin.com/Ee1kBfmt Feb 19 16:00:59 WillieNL: i honestly didnt put any effort into trying to debrick them for all i know the bootloader will allow me a simple tftp reflash. like in the rt-n16 does Feb 19 16:01:30 as long your still able to manage u-boot yes Feb 19 16:01:38 thats what i like about such systems Feb 19 16:02:08 at first boot though i havent been seeing serial output and i just basically walked away from them lol Feb 19 17:15:01 juhosg * r30645 /trunk/target/linux/ramips/ (14 files in 10 dirs): (log message trimmed) Feb 19 17:15:01 ramips: rt305x: add support for the Skyline SL-R7205 Wireless 3G router Feb 19 17:15:01 [juhosg: Feb 19 17:15:01 - don't switch back to 2.6.39 Feb 19 17:15:01 - update config-3.2 Feb 19 17:15:01 - change machine id to SL-R7205 Feb 19 17:15:01 - reorder case entries in platform scripts Feb 19 17:31:27 jow * r30646 /branches/backfire/target/linux/generic-2.4/patches/ (6 files): [backfire] generic-2.4: rebase netfilter patches after RTSP removal Feb 19 18:01:54 luka12345: I assume you haven't seen http://git.nico-and-co.net/?p=nico/openwrt.git;a=shortlog;h=refs/heads/proposed-updates Feb 19 18:11:23 swalker * r30647 /packages/net/bind/Makefile: [packages] bind: disable gssapi (#10997, thanks Cybjit) Feb 19 18:17:00 hm Feb 19 18:17:19 anybody else noticed issues with building bash? Feb 19 18:17:34 it seems to fail if a libreadline is in staging_dir Feb 19 18:22:22 juhosg * r30648 /trunk/target/linux/ramips/image/Makefile: ramips: build sysupgrade image for the V11ST-FE board Feb 19 18:22:23 juhosg * r30649 /trunk/target/linux/ramips/ (5 files in 2 dirs): ramips: rt288x: nuke built-in MTD partition maps Feb 19 18:22:27 juhosg * r30650 /trunk/target/linux/ramips/files/arch/mips/ralink/rt305x/ (23 files): ramips: rt305x: nuke built-in MTD partition maps Feb 19 18:22:31 juhosg * r30651 /trunk/target/linux/ramips/ (4 files in 4 dirs): ramips: nuke 2.6.39 support Feb 19 18:22:34 juhosg * r30652 /trunk/target/linux/ramips/ (2 files in 2 dirs): ramips: merge 3.2 fixes Feb 19 18:25:06 jow_laptop: built fine for me yesterday (x86) Feb 19 18:26:35 swalker: was the libreadline package also enabled? Feb 19 18:26:48 I see this problem in a full build of backfire for rdc Feb 19 18:27:16 apparently OS X has a similar problem where -lreadline prefers the system wide libreadline.so over the internal libreadline.a Feb 19 18:27:46 the system wide one lacks symbols which are present in the internal version Feb 19 18:28:16 jow_laptop: no, iirc, but a previous builds files are still in my staging_dir Feb 19 18:30:40 hm Feb 19 18:30:47 can you try this patch: Feb 19 18:30:55 http://openwrt.linux-appliance.net/bash.patch Feb 19 18:31:12 it shouldn't change anything in the working case Feb 19 18:32:33 maybe the problem is rdc/x86 specific Feb 19 18:33:25 because I don't see the same compile issue with mips or arm stuff Feb 19 18:53:10 jow_laptop: (still) worksforme Feb 19 19:03:37 jow * r30653 /packages/utils/bash/ (3 files in 2 dirs): [packages] bash: force linking against internal libreadline.a, fixes Backfire build on CentOS 5.6 Feb 19 19:06:00 jow_laptop: #7066, missing luci-app-samba postinst? Feb 19 19:06:41 swalker: hm maybe Feb 19 19:07:15 jow * r30654 /branches/packages_10.03.2/utils/bash/ (3 files in 2 dirs): [packages_10.03.2] bash: merge r30653 Feb 19 19:10:09 jow_laptop: has there ever been a luci about page? the bootstrap footer links to one Feb 19 19:10:28 swalker: yes Feb 19 19:10:33 but it has been removed Feb 19 19:10:56 thanks for the hint, I'll make it link to the trac isntead Feb 19 19:11:35 ah Feb 19 19:15:43 updated openwrt/upstream, https://home.comcast.net/~sdwalker/uscan/index.html Feb 19 19:22:46 jow_laptop: is luci #64 done given luci-app-{asterisk,pbx*}? Feb 19 19:23:37 yes indeed Feb 19 19:27:12 jow_laptop: luci #379 looks to be a feature Feb 19 19:27:58 it is Feb 19 19:28:06 but I'm too lazy to decide it Feb 19 19:28:18 so it remains open, its not a blocker after all Feb 19 19:33:44 jow_laptop: luci #327 missing olsrd dependency? Feb 19 19:40:54 swalker: recursive deps Feb 19 19:41:05 never managed to track this one down Feb 19 19:54:11 hello :) Feb 19 19:54:34 does somebody know what is the "noise" level range in wpa supplicant ? Feb 19 19:54:50 im implementing than for android (tiwlan) Feb 19 19:54:54 that* Feb 19 19:55:12 V/wifi ( 2267): CMD [SIGNAL_POLL]: Feb 19 19:55:14 V/wifi ( 2267): OK [RSSI=-39 Feb 19 19:55:16 V/wifi ( 2267): LINKSPEED=54 Feb 19 19:55:18 V/wifi ( 2267): NOISE=6 Feb 19 19:55:20 V/wifi ( 2267): FREQUENCY=2412] Feb 19 19:55:40 ive made rssi_beacon - rssi_data to get the noise... Feb 19 19:55:55 not sure what the range should be, negative or not... Feb 19 20:02:24 jow_laptop: luci #372, only seeing an error for the rules tab - http://pastebin.com/raw.php?i=kgt5UTJY Feb 19 20:10:48 juhosg * r30655 /trunk/target/linux/ramips/files/arch/mips/ralink/rt3883/ (devices.c devices.h): ramips: rt3883: make rt3883_nand_data visible Feb 19 20:18:10 swalker: ok, I see why it can happen Feb 19 20:30:47 jow_laptop: was everything added in r8077 & r8263 for #332? Feb 19 20:31:31 maybe Feb 19 20:31:45 there's two chinese groups battling over whos translatiosn are the right ones Feb 19 20:42:36 i think we really need some people that can do a proper review of our wiki contents Feb 19 20:42:57 today i found a 'buildroot technical reference' page that was almost entirely wrong Feb 19 20:43:27 jow_laptop: #318 is the same as #335 Feb 19 20:44:45 nbd: futile Feb 19 20:59:45 I'm progressing with pppoe-server. have the hhv3 connecting to OpenWRT. now i need to NAT the packets I guess? e.g. i'm seeing ntp requests, but they are not being answered... Feb 19 21:05:31 philipp64|laptop ping Feb 19 22:49:22 build #106 of iop32x is complete: Failure [failed compile_10] Build details are at http://buildbot.openwrt.org:8010/builders/iop32x/builds/106 Feb 19 23:48:37 build #138 of at91 is complete: Failure [failed compile_4] Build details are at http://buildbot.openwrt.org:8010/builders/at91/builds/138 Feb 20 00:19:50 build #136 of ubicom32 is complete: Failure [failed compile_1] Build details are at http://buildbot.openwrt.org:8010/builders/ubicom32/builds/136 **** ENDING LOGGING AT Mon Feb 20 03:00:00 2012