**** BEGIN LOGGING AT Fri Oct 07 02:59:58 2011
Oct 07 13:27:04 <voyo> hey, Im haveing trouble with using extroot. I noticed that package/block-extroot/ is empty, its current owrt trunk (At revision 28377). is that OK ?
Oct 07 13:27:37 <jow_laptop> yeah, its part of block-mount
Oct 07 13:27:44 <jow_laptop> and its all edxplained in the wiki
Oct 07 13:30:23 <voyo> oki, got it
Oct 07 13:30:44 <voyo> Note: If the overlay mount fails it will appear on /tmp/overlay-disabled instead of becoming the rootfs.
Oct 07 13:31:14 <voyo> thats my issue, and /dev/mtdblock3 is still /overlay.  any particular reason  for that ?
Oct 07 13:31:44 <jow_laptop> yeah, your overlay probably holds on old md5sum
Oct 07 13:32:34 <voyo> http://pastebin.com/vJKWwukZ
Oct 07 13:32:42 <jow_laptop> there is /etc/init.d/fstab enable-overlay
Oct 07 13:37:47 <voyo> ok, tnx. fixed that. (by remove sda7/etc/*md5*  )
Oct 07 13:38:00 <voyo> any reason why this could happen ? how to prevent
Oct 07 13:38:58 <voyo> btw, Im getting many such errors:   overlayfs: ERROR - failed to whiteout  'file'
Oct 07 13:39:15 <voyo> but it seems working ok...
Oct 07 13:39:57 <jow_laptop> failed to whiteout errors occur because your overlayfs has no xattr support
Oct 07 13:40:08 <jow_laptop> the disabling of overlay happens after a system upgrade
Oct 07 13:40:25 <jow_laptop> its done to prevent crashes due to binary incompatible modules on overlay loaded against a newer system
Oct 07 13:41:28 <voyo> okI see
Oct 07 13:42:51 <voyo> xattr is used by owrt for some reson, or its safe to not have it ? (for me - its not needed).
Oct 07 13:43:11 <jow_laptop> no its not safe to not have it
Oct 07 13:43:20 <jow_laptop> it *is* needed
Oct 07 13:43:25 <voyo> oh ?
Oct 07 13:43:35 <jow_laptop> overlayfs stores the information "this stuff has been deleted" in extended attributes
Oct 07 13:43:44 <jow_laptop> if you have no xattr support, you cannot delete files
Oct 07 13:43:50 <voyo> oki.
Oct 07 13:43:57 <voyo> I'll enable then.
Oct 07 13:44:20 <voyo> tnx
Oct 07 13:44:23 <jow_laptop> np
Oct 07 15:30:14 <builder_> build #84 of pxcab is complete: Failure [failed compile_10]  Build details are at http://buildbot.openwrt.org:8010/builders/pxcab/builds/84
Oct 07 15:55:40 <builder_> build #79 of ppc44x is complete: Failure [failed compile_4]  Build details are at http://buildbot.openwrt.org:8010/builders/ppc44x/builds/79
Oct 07 16:06:12 <CIA-73> florian * r28378 /trunk/package/iproute2/ (5 files in 2 dirs):
Oct 07 16:06:12 <CIA-73> [package] iproute2: update to 2.6.39
Oct 07 16:06:12 <CIA-73> Signed-off-by: Daniel Mierswa <impulze@impulze.org>
Oct 07 16:36:15 <__trine> Trunk is not compiling  because of >>> http://dpaste.com/629716/
Oct 07 16:40:55 <nbd> __trine: try again, should work now
Oct 07 16:41:06 <__trine> ok
Oct 07 16:42:43 <__trine> it seems to be ok now
Oct 07 16:42:48 <__trine> ta
Oct 07 16:59:28 <idl0r> hey guys, any ideas why flashing via mtd / tftp fails while the integrated recovery/flasher works fine? http://dpaste.com/629590/ http://qasl.de/~idl0r/flash.log
Oct 07 17:03:14 <Chocky> telling us the hardware and the software version you're trying to use would be a good start
Oct 07 17:03:54 <idl0r> WRT610Nv2, trunk/28369
Oct 07 17:12:25 <slonopotamus> mb__: ping
Oct 07 17:12:51 <mb__> hey
Oct 07 17:15:37 <slonopotamus> mb__: i'm currently in the state where tsc2301 driver compiles. luckily, it required only minor fixes to its sources. now the question is how to plug it into board file. maemo kernel had separate board files and just returned different arrays of devices connected to SPI. should i duplicate array in board-n8x0.c (changing touchscreen for n800) and use if (machine_is_n800()) to decide which one to use or there's some way to handle that without c
Oct 07 17:15:37 <slonopotamus> opypasting hw info that is common for both n8x0?
Oct 07 17:17:10 <mb__> Oh I really don't remember this
Oct 07 17:17:24 <mb__> It's been quite some time since I worked on that stuff
Oct 07 17:17:50 <slonopotamus> btw, tsc* drivers are very similar. maybe (if my thingie works) we should merge them into a single driver
Oct 07 17:17:54 <mb__> two arrays and then if(800) 800-array else 810-array; seems fine
Oct 07 17:18:24 <slonopotamus> mb__: i just don't like copypasting
Oct 07 17:19:24 <mb__> well, how big is it?
Oct 07 17:22:00 <slonopotamus> two common items currently - wifi and screen
Oct 07 17:23:33 <mb__> Maybe it's possible to define the structs standalone and then only do a pointer array.
Oct 07 17:23:50 <mb__> But having two struct arrays really seems to be OK for the time being.
Oct 07 17:24:11 <slonopotamus> okay
Oct 07 17:26:47 <slonopotamus> funny chip btw - touchscreen, keypad and... sound
Oct 07 17:29:49 <mb__> I think this is to save power
Oct 07 17:30:42 <slonopotamus> if you'll be messing with sound, remember than n810 has different chip
Oct 07 17:57:04 <swalker> [florian]: can you remove the obsolete 007-version_includes iproute2 patch?
Oct 07 18:07:58 <swalker> thepeople, Kaloz: have any of the maintainers that are lacking commit access to their package(s) gotten access?
Oct 07 18:10:21 <karlp> I sent thepeople an email with ssh details a while ago, but never heard back...
Oct 07 18:10:33 <karlp> no stress on my part,
Oct 07 19:03:07 <CIA-73> nbd * r28379 /trunk/package/mac80211/patches/ (2 files): ath9k: disable phy error reporting on the rx queue to improve stability under noisy conditions
**** ENDING LOGGING AT Sat Oct 08 02:59:57 2011