**** BEGIN LOGGING AT Sat Sep 29 02:59:56 2007 Sep 29 03:28:05 nbd * r9061 /trunk/include/quilt.mk: refactor quilt patching code Sep 29 03:39:58 nbd * r9062 /trunk/include/ (4 files): move a stampfile to make it easier to override the patch template Sep 29 04:29:14 nbd * r9063 /trunk/include/ (host-build.mk kernel-build.mk package.mk quilt.mk): fixes for refresh/update handling Sep 29 10:14:24 re Sep 29 11:35:53 nbd * r9064 /trunk/docs/ (openwrt.sty openwrt.tex): apply latex style patch posted on openwrt-devel@lists Sep 29 11:38:55 nbd: thanx docs update :-) Sep 29 11:44:05 glp_home: replied to your request about the feeds system as well Sep 29 11:44:07 :) Sep 29 11:49:50 nbd: when did you reply to my feeds question? Sep 29 11:50:10 mail says 13:42 Sep 29 11:51:44 nbd: hasn't found my mail-server yet :( Sep 29 11:52:09 glp_home: http://lists.openwrt.org/pipermail/openwrt-devel/2007-September/001239.html Sep 29 11:53:17 nbd: super :o) Sep 29 12:00:14 WIP-Day has now hit its beginning - and I hope it will 24 happy hours ;-) Sep 29 12:11:09 Big question of the weekend: Will 7.09 reach release? Sep 29 12:11:57 i hope so Sep 29 12:12:01 i'll upload new binaries for testing Sep 29 12:12:15 if we find some people for testing, i might release the current stuff tomorrow Sep 29 12:12:51 I better find a "piece" of hardware and be ready :-) Sep 29 12:19:56 nbd: it works fine for me on a fonera and wgt634u Sep 29 12:21:44 loswillios: which fonera version? Sep 29 12:21:48 hi glp_home Sep 29 12:21:54 blogic? Sep 29 12:22:04 glp_home: fon 2100 a/b/c Sep 29 12:22:20 blogic: hi ;-) Sep 29 12:22:26 wrt: wanna talk to lisa ? :-) Sep 29 12:22:33 loswillios: okie Sep 29 12:42:38 nico * r9065 /trunk/package/ (acx/Makefile acx-mac80211/Makefile): disable acx & acx-mac80211 on atheros, renable check for CONFIG_MAC80211 in KCONFIG in acx-mac80211 so that it does not get built on pre 2.6.22 Sep 29 12:48:42 Where are the pre 7.09 snapshots hosted ? Sep 29 12:49:01 http://nbd.openwrt.org/kamikaze/7.09/ Sep 29 12:51:13 rwhitby * r9066 /packages/utils/bluez-hcidump/ (. Makefile): bluez-hcidump: Bluetooth packet analyzer Sep 29 12:55:30 nbd: cheers Sep 29 12:58:47 rwhitby * r9067 /packages/utils/bluez-hcidump/Makefile: bluez-hcidump: --with-usb is irrelevant, cut and paste error. Sep 29 13:58:19 * glp_home is just updating firmware on the macbook Sep 29 14:27:59 juhosg * r9069 /trunk/ (107 files in 53 dirs): get rid of per-profile base-files Sep 29 15:50:11 blogic: how did you get your hands on the olpc (i suppose negroponte didn't call you and asking; would you like to try and subvert my biggest project ever?) Sep 29 15:50:41 glp_home: we got it from the debian developers :-) Sep 29 15:51:18 glp_home: and now that we got it booting with owrt we are going to send a mail tonight and see if we can get our own, cause we want to play with the meshing part Sep 29 15:52:36 blogic: you'll just end up building a better solution if they give you one :o) Sep 29 15:53:20 glp_home: yep Sep 29 15:53:22 :-) Sep 29 15:56:18 blogic: did you get all the hardware working? Sep 29 15:56:23 on the olpc Sep 29 15:57:02 glp_home: not the wifi and the camera, the rest is working Sep 29 15:57:12 glp_home: and we still have to make sugar work Sep 29 15:57:20 glp_home: sugar is the olpc software Sep 29 15:57:35 blogic: is the wifi still marvel? Sep 29 15:57:43 glp_home: but we boot in <20 seconds, the redhat bloat takes about 1 minute Sep 29 15:57:50 glp_home: yes and it is closed source Sep 29 15:58:06 glp_home: hence we wanna get our own and hgopefully access to the gpl sources Sep 29 15:58:12 s/gpl/nda/ Sep 29 15:58:55 blogic: nda is nasty Sep 29 15:59:06 marvell is worse Sep 29 16:01:41 glp_home: the wifi in the marvell is cool though, they have a hw ieee stack and the olpc can mesh, even if the device is in standby Sep 29 16:04:28 blogic: how does the thing keep working in standby, do you know? Sep 29 16:05:37 glp_home: no idea, hence i want access to the nda stuff :-) sounds really cool if you ask me Sep 29 16:09:08 blogic: maybe someone will suddently feel inspired to write a solution for openwrt :P Sep 29 16:09:29 glp_home: hmmz :-) Sep 29 16:09:57 glp_home: lets see what they say when i send my 'beg' mail to olpc Sep 29 16:10:04 i want 3 olpcs :-) Sep 29 16:11:03 blogic: you'r gonna be classified as an independent country ;-) Sep 29 16:11:15 glp_home: we already are :-) Sep 29 16:11:33 country of hack Sep 29 16:17:05 blogic: always a step ahead Sep 29 16:18:11 glp_home: :-) Sep 29 16:31:03 Linux version 2.4.17_mvl21-malta-mips_fp_le (root@Run-P4) (gcc version 2.95.3 20 Sep 29 16:31:03 010315 (release/MontaVista)) #8 Thu Jan 29 17:42:41 CST 2004 Sep 29 16:44:39 * glp_home thinks it is maté time Sep 29 17:00:37 The TableOfHardware is very useful. According to the Status Legend, there is no status to indicate that the device is supported both by White Russian and Kamikaze. Should there not be such a status? For example, wrt54gl is listed as "supported" which means that it works under White Russian (and by omission, not under kamikaze. Sep 29 17:01:35 devices supported under whiterussian are also supported under kamikaze Sep 29 17:02:00 dhr: the specific sub-page of wrt54gl should in principle inform you about such details Sep 29 17:02:02 ggp81: not really, the wireless of broadcom devices doesn't work well Sep 29 17:02:43 Then the Status Legend should be clearer about what "Supported" does and does not mean. Sep 29 17:02:46 (*under kamikaze atm) Sep 29 17:02:47 crazy_imp: broadcom wireless doesn't work with 2.6 kernel, but does with 2.4 Sep 29 17:03:09 dhr: i'm agree :) Sep 29 17:03:23 ggp81: true, i mainly think about 2.6 if you say kamikaze, my fault :D Sep 29 17:03:44 the problem of kamikaze wireless Sep 29 17:04:05 is that on 2.4 kernel there's a proprietary version of wireless driver (i think) Sep 29 17:04:15 yes Sep 29 17:04:21 on 2.6 there's another driver which is not yet supported Sep 29 17:04:31 i think when wireless will work on 2.6 Sep 29 17:04:39 2.4 target will be removed on kamikaze Sep 29 17:04:58 the 2.4 target won't be removed until alternatives are ready Sep 29 17:05:09 Does it make sense to allow more than one item in the status field and thus allow "White Russian", "Kamikaze2.4", and "Kamikaze2.6" to each be present? Sep 29 17:05:45 kamikaze2.4 and kamikaze2.6 it doesn't make sense Sep 29 17:05:54 exactly Sep 29 17:06:00 we have one 2.4 target and many 2.6 targets Sep 29 17:06:43 what is the one 2.4 target (for Kamikaze, I assume)? Anything with Broadcom wireless? Sep 29 17:06:54 of course broadcom Sep 29 17:06:57 with broadcom wireless Sep 29 17:07:03 everything else is 2.6 Sep 29 17:11:20 I have a Motorola WR850G. It uses a Broadcom wireless. The router is listed as "supported". The linked web page does not mention Kamikaze. What should I infer from this? Is Kamikaze-on-2.4 likely to work? Sep 29 17:12:27 your device supports both kamikaze and whiterussian Sep 29 17:12:36 if you have to use wireless install 2.4 firmware Sep 29 17:12:56 because you can install 2.6 kernel Sep 29 17:12:58 your router support it Sep 29 17:13:02 but wireless will not work Sep 29 17:13:20 so if you are planning to use wireless you have to install whiterussian or kamikaze 2.4 Sep 29 17:13:55 Good to know. Thanks. How can I tell this from the documentation? I ask because I'd like to help improve the documentation for newbies. Something I can do due to being one. Sep 29 17:14:21 dhr: add it as a comment to the wr850g page Sep 29 17:14:47 dhr: probably at the top of the page :-) Sep 29 17:15:07 about table of hardware Sep 29 17:15:11 there are many "?" Sep 29 17:15:25 on the status field Sep 29 17:16:59 maybe those fields could be more clear Sep 29 17:17:44 I'm editing the WR850G page... I'll telly you when I've committed. Then you can critique. Sep 29 17:18:22 :) Sep 29 17:25:03 Darn. When I go to commit, I get: 500 Internal Server Error (sorry - we're updating) Sep 29 17:26:19 Now it works. Please check section #2. of http://wiki.openwrt.org/OpenWrtDocs/Hardware/Motorola/WR850G#preview Sep 29 17:27:19 dhr: you should probably make it clear, when you refer to the brcm-driver, that this only concerns kamikaze? Sep 29 17:29:37 Are all versions of White Russian based on 2.4? Were there ever versions of OpenWRT based on 2.0 or 2.2? Sep 29 17:30:22 dhr: yes - but they are all in the past Sep 29 17:35:24 is there a good link to explain this kamikaze 2.4/2.6 thing? I imagine that entering this expanitory text in each router's page is redundant and therefore hard to maintain (say, when Broadcom is supported under 2.6). Sep 29 17:36:24 Here's my revised paragraph, before I commit it. Comments? The Broadcom wireless is not (yet?) supported by an open source driver. The proprietary driver is only available for Linux kernel 2.4. If you need to use wireless, you need to use a version of OpenWRT based on the 2.4 kernel. White Russian is based on the 2.4 kernel and there is a version of Kamikaze based on the 2.4 kernel. Beware: the main version Sep 29 17:36:24 of Kamikaze is based on the 2.6 kernel and does not support the Broadcom wireless. Sep 29 17:36:48 dhr: I think it is something which needs to be added to http://downloads.openwrt.org/kamikaze/docs/openwrt.html Sep 29 17:37:10 dhr: i'll put in on the list of things-to-be-done Sep 29 17:37:50 dhr: or you could write a patch and post it on the openwrt-devel mailing-list? Sep 29 17:38:37 my only submission to the mailing list (a revised version of motorola-bin) has been met with silence so far. Sep 29 17:40:14 dhr: silence is not always bad Sep 29 17:41:01 a bit of philosophy: you're only a newbie once. A project can gain a lot by discovering where newbies get into trouble. Newbies are often wrong, but it is interesting to figure out why they went wrong. Sep 29 17:42:42 dhr: it's often a question about priorities Sep 29 17:47:18 glp_home: of course it is a question of priorities, individual and project priorities. I have found that there antipathy to OpenWRT, for example, at linksysinfo.org. I don't understand it. One theory is that OpenWRT is hard to get into. I'm trying to reduce some of the trivial barriers to entry. I don't know for sure that it matters, but I think that it should. Sep 29 17:49:54 dhr: I think the whole linksysinfo aspect is quite complex - entry to openwrt is on the other hand is quite easy; you just ahve to begin using it (which can be difficult) Sep 29 17:52:01 dhr: i've spend a couple of years getting to where i'm at now - i'm not sure if i would have made a quicker progress with another 'project'. Sep 29 17:53:20 as far as I can tell, OpenWRT is meant for participants whereas the other projects are aimed at users. This is my current impression, even if it is wrong. Sep 29 17:53:57 dhr: i think you right about the participant aim Sep 29 17:54:11 i agree Sep 29 17:54:51 dhr: you can only declare that you belong (use) by participation Sep 29 17:54:56 we're not trying to build the firmware that has every freature and does everything by itself Sep 29 17:55:06 we're building something that is as easy as possible to adapt for any purpose Sep 29 17:55:24 ... and any platform Sep 29 17:55:56 nbd: + it's a damn good learning-tool Sep 29 17:56:24 yeah. i've learned much just by hacking on it and shaping it Sep 29 17:56:57 nbd: or bricking it ;-) Sep 29 17:57:09 i don't do that a lot Sep 29 17:57:10 ;) Sep 29 17:57:28 nbd: but i do :P Sep 29 17:57:57 but then again, for me something isn't a brick, if i can still connect over serial and upload stuff ;) Sep 29 17:58:13 nbd: auchh Sep 29 17:58:25 nbd: that's why I hate the term; overused and typically used out of ignorance of recovery proceedures. Sep 29 17:59:02 yep Sep 29 17:59:41 I have a high standard for documentation, perhaps not shared by the project. I want to be able to read the documentation and know what to do. I don't mean that it has to be tutorial, just that everything is documented and the documentation has links so that you can find what you need to know. I feel that the Motorola WR850G documentation has failed this test so I'm trying to chip away at the problems. Sep 29 18:00:09 I ask you questions but as payback, I try to capture the answers in documentation. Sep 29 18:00:22 that sounds good Sep 29 18:01:20 that reminds me, what the hell is going on with the wiki? It appears to be a lot more unstable than normal. Sep 29 18:01:35 no idea Sep 29 18:01:43 we really ought to replace it with something sane Sep 29 18:02:13 nbd: yeah, I'm going to be creating my own later today because I simply can't trust the OpenWrt wiki to work anymore. Sep 29 18:03:04 Bartman007: maybe ask kaloz about the sanity of the wiki? Sep 29 18:03:37 wikipedia has discussion page for each article. If you are changing wiki systems, I'd request that feature. Sep 29 18:03:41 glp_home: maybe... I realize I forgot to post my DocBook vs Latex idea to the mailing list also... Sep 29 18:04:15 dhr: mediawiki is prettynice Sep 29 18:04:37 Bartman007: it's never to late Sep 29 18:04:45 that was one of the main arguments for moinmoin, since it does have the "Render to DocBook" idea. Sep 29 18:05:48 Bartman007: yeah Sep 29 18:06:34 nbd: what's your thoughts on docbook? my primary issue with latex (that has come about over the past few weeks) is monolithic orientation of the rendered output. I really like being able to break the docs up, like in the wiki, and have meaningful links/pagenames (rather than node0001.html or the current numerical anchors in the latex docs) Sep 29 18:06:58 Bartman007: i have no experience with docbook Sep 29 18:08:07 ok, all the more reason to pose the question to the mailing list, it sounds like David Farning does have experience with it through his ties to Ubuntu. Sep 29 18:08:14 you could make an example Sep 29 18:08:17 so that i can see the structure Sep 29 18:08:38 maybe i'll like it. i don't really mind as long as it's easy enough to write and build Sep 29 18:08:53 nbd: ok, I'll get to that later today. Sep 29 18:10:29 * glp_home will just help with getting children into bed :-) Sep 29 18:23:51 nbd: it needs to be easy to write (and all the building should be automatic) Sep 29 18:23:59 yes Sep 29 18:24:08 with easy to built i meant light on dependencies and stuff Sep 29 18:25:14 nbd: yeah - and few human-hours involved Sep 29 18:29:01 in the actual build-process Sep 29 18:37:37 nico * r9072 /packages/net/peerguardian/ (Makefile files/peerguardian.init): peerguardian fixes: add dependency on queue netfilter module, run the actual daemon in the initcript (not the control program) and set exec perms on it Sep 29 19:20:39 I asked this on the list, but I'm impatient. Does the filename extension .trx signify anything in particular? It appears as if various routers' firmware want .trx but mean something different by it. Sep 29 19:24:18 nico * r9073 /packages/net/peerguardian/Makefile: really set exec perm on peerguardian initscript (thanks olli for noticing) Sep 29 19:28:55 dhr: as much as i remember; .trx is a particular file format Sep 29 19:31:51 dhr: anyway - this whole thing about .bin and .trx is only relevant when flashing a new device. after 7.06 you can only upgrade an existing kamikaze with the appropriate .trx file Sep 29 19:32:18 dhr: the system is no longr able to accept .bin files when upgrading Sep 29 19:33:51 dhr: on brcm hardware Sep 29 19:34:30 glp_home: it can still accept them via TFTP... Sep 29 19:35:00 Bartman007: but does it make a difference? Sep 29 19:35:47 I like the idea of being able to go back and forth between the original firmware and the OpenWRT firmware. On the Motorola wr850g, it seems as if there is a slight difference between the form that openwrt expects for flashing and the form that the motorola-provided firmware expects. Sep 29 19:36:16 dhr: why do you want to go back and forth? Sep 29 19:37:02 glp_home: I'm not quite sure what you mean. TFTP is a bootloader function, flashing Kamikaze does not mess with that. If it required a trx before it requires a trx now, same deal for a bin. Sep 29 19:37:17 so far, this is theoretical. I have only used Motorola's firmware. Before I jump into the water, I want to know how to get out again. Sep 29 19:38:01 Bartman007: point taken Sep 29 19:38:20 dhr: enable boot_wait and then you can alwaqys tftp Sep 29 19:38:28 the wiki page is not very clear about this so I'm considering fixing it. Sep 29 19:39:12 scary: the wiki page says that boot_wait has to be set each time: it doesn't stick. Sep 29 19:41:01 I assume that this is specific to the wr850g Sep 29 19:42:13 dhr: where does it say that boot_wait does not stick (just looking at the page and I can't find it)? Sep 29 19:44:03 glp_home: 5.1 in http://wiki.openwrt.org/OpenWrtDocs/Hardware/Motorola/WR850G Sep 29 19:46:30 dhr: i think this might be related to whiterussian install, which is based on nvram configuration - so, just to be sure it is recommended to check the boot_wait status before doing something foolish Sep 29 19:47:55 dhr: but i can really understand your problems with this page, it's just one big mess (and nobody has been taking care of it for a long time) Sep 29 19:48:26 I'll try to test this boot_wait thing ... Sep 29 19:50:07 dhr: i started this thread a while ago http://forum.openwrt.org/viewtopic.php?id=11451 Sep 29 19:50:57 I bought three of the Motorola WR850g's because they were very inexpensive and seemed to be supported by OpenWRT. So that page is my entre' into OpenWRT. It turns out that I haven't yet needed OpenWRT badly enough to work through setting it up. My goal is to set up Openswan on it. Sep 29 19:52:11 My "culture" is mailing list oriented, so I tend to miss things in fora. I'll go look at that thread. Sep 29 19:54:25 glp_home: if you know enough to make simple quick improvements to the wr850g page, please do so. I realize that structural fixes may be more work than they are worth to you. Sep 29 20:00:26 glp_home: I like your forum thread. Surely this belongs on a wiki page! Improvements/generalizations/whatever could evolve on the wiki. Sep 29 20:01:03 dhr: thanx :) Sep 29 20:14:44 glp_home: I performed the following experiment on motorola firmware 4.0.3. Set boot_wait; commit it; verify that it is on; reboot using "restart" button; observed that boot_wait is off. Sep 29 20:15:26 So: there really is a problem with boot_wait not being sticky, at least with Motorola firmware. I assume that OpenWRT would behave differently. Sep 29 20:19:34 dhr: unless the bootloader unsets it... Sep 29 20:21:18 Bartman007: could be - on the other hand, i suppose it's the cfe bootloader, and why would motorola change the default behaviour Sep 29 20:22:25 glp_home: I don't think you can apply logic to decisions made on embedded devices. :-P Sep 29 20:24:46 Bartman007: you'r probably right - as alternative; could it be a script in the firmware which resets to default values? Sep 29 20:26:08 Bartman007: if the wr850g behaves differently with openwrt it perhaps points away from the bootloader? Sep 29 20:27:08 glp_home: if it behaves differently with owrt installed then it was not the bootloader, guess we'll have to wait until he tests. Sep 29 20:30:26 Bartman007: guess so Sep 29 20:31:37 with your help, maybe I'll try that now. Take that as a warning. I'll spit out my problems as I encounter them. Shout "stop" if you think that I should stop. Sep 29 20:33:06 dhr: go ahead Sep 29 20:34:05 problem 1: the wr850g page doesn't say from where to get kamikaze (or White Russian). I think it should. Perhaps in the section I just added. So I'm going to the FAQ... Sep 29 20:36:18 problem 2: FAQ #1.3 "Which image should I use?" seems lost in details. Talks indecisively about SquashFS vs JFFS2, and nothing else! Seems bogus. (Don't help me yet, my wanderings may be useful) Sep 29 20:37:54 FAQ 1.4 "How do I install/flash OpenWrt?" talks only about White Russian, but punts to OpenWrtDocs/Installing so I'll go there. Sep 29 20:38:24 bingo: "This page does not exist yet. You can create a new empty page, or use one of the page templates." Sep 29 20:38:34 dhr: that page is broken, not sure why, and I can't fix it. Sep 29 20:38:44 supposedly it was deleted.... Sep 29 20:39:59 Bartman007: very odd with that page Sep 29 20:41:11 I tried to create a placeholder but when I saved, I got: 500 Internal Server Error (sorry - we're updating) Sep 29 20:41:30 dhr: yeah, it can't be edited... Sep 29 20:41:54 It would be nice if it told me that in some sensible way. Sep 29 20:42:13 see what fun it is to watch a newbie? Sep 29 20:42:14 dhr: it is my present experience that it will have done the edit if you do a refresh Sep 29 20:42:45 dhr: after having seen the: 500 Internal ...... Sep 29 20:43:03 glp_home: with the page in question it simply does not work Sep 29 20:43:07 I've tried many times... Sep 29 20:43:46 Bartman007: damn it Sep 29 20:44:13 how does one report this to the responsible authorities? trac, I assume. Can I leave that to one of you? Sep 29 20:46:21 dhr: I'll ask about it - have to admit i don't even know if things like these can be report via a trac ticket? Sep 29 20:46:45 OpenWrt/HelpOnInstalling is about installing MoinMoin. Another blind alley. But don't help me yet... Sep 29 20:47:46 Kaloz: ping. Sep 29 20:48:51 The list of howtos does not contain a name that jumps out at me... Sep 29 20:49:28 http://wiki.openwrt.org/OpenWrtDocs/Installing?action=recall&rev=238 Sep 29 20:50:26 bartman007: thanks. But you weren't supposed to help me yet :-) Sep 29 20:50:58 dhr: I'm only helping you because that is what should be at http://wiki.openwrt.org/OpenWrtDocs/Installing if it were not broken. Sep 29 20:51:27 fair enough. That's why I put in the smily Sep 29 20:52:39 dhr: i think i had similar problems a while ago and ended up working on this (whiterussian) http://wiki.x-wrt.org/index.php/Installation_Guide Sep 29 20:53:04 dhr: and for kamikaze http://wiki.x-wrt.org/index.php/Kamikaze_Installation Sep 29 20:53:09 that page just deals with White Russian (at least Kamikaze is never mentioned). My impression is the Kamikaze is now good enough to be recommended. Am I wrong? Sep 29 20:53:23 that page == http://wiki.openwrt.org/OpenWrtDocs/Installing?action=recall&rev=238 Sep 29 20:54:43 truth be told, I imagine that I'd like x-wrt. But I thought that it would add another level of complexity. Perhaps no wr850g user had tried it. Sep 29 20:55:02 dhr: kamikaze is very good - the whole thing about installtion is just complicated due to the many platforms Sep 29 20:55:14 dhr: the Installing section applies to Kamikaze also for all White Russian capable devices. Sep 29 20:55:50 Bartman007: not the "You can get the latest OpenWrt White Russian firmware images at: http://downloads.openwrt.org/whiterussian/newest/" Sep 29 20:56:56 note: I will now abandon openwrt proper and try http://wiki.x-wrt.org/index.php/Kamikaze_Installation Sep 29 20:57:35 dhr: common sense would indicate that Kamikaze would be at downloads.openwrt.org/kamikaze it is also linked to from www.openwrt.org Sep 29 20:58:04 Bartman007: this here wiki just keeps making loops and loops and loops and loops Sep 29 20:58:07 Bartman007: sure, but I'm trying to be a newbie. Sep 29 20:58:58 dhr: I realize that, I can't so go "here" for all the docs because Kamikaze simply does not have any such location. Sep 29 20:59:07 s/so go/say go/ Sep 29 20:59:47 Yeah, and we'd fix that page if we could edit it. Or even recreate it. Sep 29 21:00:28 Is there a reason that Kamikaze has no such location? Is it intended to share the page or have its own? Sep 29 21:00:47 dhr: good question? Sep 29 21:02:21 dhr: the Kamikaze docs are locationed at http://kamikaze.openwrt.org/docs/openwrt.html Sep 29 21:02:29 located* Sep 29 21:02:41 the install section simply doesn't exist. Sep 29 21:02:58 [mbm]: ping Sep 29 21:03:24 OK. I really like wiki pages for my current exercise because I get instant gratification when I can fix things. Sep 29 21:06:16 dhr: if I weren't doing three things at the same time right now, I'd be bringing my own wiki online so we could have a place to work; I simply don't trust the OpenWrt wiki in it's current state. Sep 29 21:07:38 I'm starting on http://wiki.x-wrt.org/index.php/Kamikaze_Installation . I want Kamikaze 7.07, I think (yell if you disagree). Sep 29 21:08:08 dhr: 7.09 should be released this weekend :-) Sep 29 21:09:11 http://downloads.x-wrt.org/xwrt/kamikaze/7.07/ has a bunch of subdirectories but I've not been given enough of a hint which I want. But I know that the ony one that can work (with wireless) is http://downloads.x-wrt.org/xwrt/kamikaze/7.07/brcm-2.4/ Sep 29 21:09:40 Within that, I see http://downloads.x-wrt.org/xwrt/kamikaze/7.07/brcm-2.4/openwrt-wr850g-squashfs.bin which looks really promising. Sep 29 21:10:24 dhr: well, http://downloads.openwrt.org/kamikaze/7.07/ has release.txt which discusses which platforms are which :-P Sep 29 21:10:47 glp_home: if I wait for 7.09, you guys will have disappeared and I'll be on my own. Or do you think that 7.07 is problematic and I should wait? Sep 29 21:11:09 dhr: 7.07 is jsut fine Sep 29 21:11:15 jsut = just Sep 29 21:12:04 dhr: as long as you remember to use the 2.4 kernel version (if you want wireless) Sep 29 21:13:34 glp_home: you can see the file that I have chosen. It does say 2.4 in the path (but not the filename itself -- possibly unfortunate). Sep 29 21:15:37 dhr: are you downloading from download.openwrt or from the x-wrt repository ? Sep 29 21:15:59 I find the section struction in http://wiki.x-wrt.org/index.php/Kamikaze_Installation hard to makeout. THe nesting gets lost in that long run of text. moinmoin makes the nesting explicit by numbering the sections. Sep 29 21:16:44 glp_home: see above. I'm intending to use http://downloads.x-wrt.org/xwrt/kamikaze/7.07/brcm-2.4/openwrt-wr850g-squashfs.bin Sep 29 21:17:44 I'm not sure if this has the header Motorola's firmware's loader requires. I will stare at it with od. Sep 29 21:17:55 dhr: should be the one Sep 29 21:18:23 as I understand it, the firmware is probably delivered without the header. Dunno. Sep 29 21:19:32 * glp_home will go and make a cup of coffee Sep 29 21:27:08 dhr: this wr850g device, does it have a firmware upgrade function in the original firmware (webif) Sep 29 21:43:37 florian * r9076 /trunk/target/linux/au1000/files/arch/ (5 files in 4 dirs): Use the gpio-led driver, but do not enable it until we move to 2.6.23 Sep 29 22:36:13 I've hacked on motorola-bin so that it can strip the motorola header off a .bin/.trx file. The advantage over dd is that it does a sanity check: that a proper header was there. Sep 29 22:37:12 It seems as if http://downloads.x-wrt.org/xwrt/kamikaze/7.07/brcm-2.4/openwrt-wr850g-squashfs.bin has that header. Seems odd because (I think) that means that it could not be flashed by openwrt as-is, only by motorola firmware. Sep 29 22:54:58 woot! My WR850G is now running x-wrt/Kamikaze 7.07! Sep 29 22:57:19 why would x-wrt's system information say "Trendware TEW411BRP+"? Sep 30 00:34:01 glp_home: sorry, missed your question. Yeah, the motorola firmware has an upgrade function. It worked. With the .bin I had downloaded (it had the Motorola-specific prefix). I had to rename the file .trx. Sep 30 01:54:15 my router type is detected incorrectly by Kamikaze 7.07. /proc/diag/model says "Trendware TEW411BRP+". This looks to be the same as https://dev.openwrt.org/ticket/1936 Sep 30 01:55:26 Since it was fixed 2007 July 8, should I expect it to be fixed in 7.09 (expected this weekend)? Sep 30 01:56:53 What are the consequences of this misidentification? I think that the lights are wrong, but I'm not sure. Will it affect flashing an upgrade or downgrade? Sep 30 02:24:38 I've found that this bug is only like 1936, but needs another clause added to the "if". I've posted to the openwrt-devel list (I don't know how to get a trac account). **** ENDING LOGGING AT Sun Sep 30 02:59:56 2007