Re: [OpenWrt-Devel] [PATCH] Make kernel version configurable for developers
Regarding the problem of users playing with config options and not mentioning it, part of the solution could be to require users to submit their .config files when reporting issues. In such a case, having the kernel version in there too would actually be better than relying on users mentioning the fact that they edited their Makefiles... Board platform and driver files/patches *depends* on a specific kernel version so kernel version configuration as you proposed would depend on luck for the users unless we provide the required patches for every kernel version. OTOH your idea could work if all boards supported by OpenWRT reside on the upstream kernel so we don't need to test and patch for every kernel release. -- Otto ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] What is the configuration file for wireless(ath9k driver)?
On Tue, Apr 17, 2012 at 09:50:56PM +0900, 马进 wrote: Hi all, Where could I find the configuration file for wireless based on ath9k driver? I want to know how to configure the beacon time, beacon time interval and so on. Is it hostapd.conf? Add your needed options in /etc/config/wireless: option dtim_period '2' option beacon_int '100' option ... -- Otto ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Bridge filtering on WRT160NL (ar71xx) not working
On Thu, Mar 29, 2012 at 05:47:03PM +0300, Felix Fietkau wrote: On 2012-03-29 1:51 PM, Felix Fietkau wrote: On 2012-03-29 11:50 AM, Florian Fainelli wrote: Le 03/28/12 00:49, Otto Solares Cabrera a écrit : On Tue, Mar 27, 2012 at 03:49:04PM +0200, Florian Fainelli wrote: Hello, Le 03/27/12 15:43, Otto Solares Cabrera a écrit : Hi! I have a WRT160NL with the 3 interfaces (eth0, eth1, wlan0) on a single bridge (br-lan) and I was normally doing filtering between them but now all the packets are unconditionally bridged to all the interfaces despite the ebtables rules. ebtables doesn't report hits on rules. My last working image was based on r30676 with 3.2.7 kernel, I'm pretty sure is not an upstream kernel problem as I tried latest trunk with kernels 3.2.7, 3.2.12, 3.2.13 and 3.3 and the same problem. Does some default changed recently? You might want to revert changeset r30954 and see if that changes something for you. Reverting that changeset fixes my problem, thank you! Felix, do you have any idea why this does not work for Otto? I think I need a new sysctl for passing packets through ebtables but not iptables. As a workaround you can probably simply set the sysctl field net.bridge.bridge-nf-call-arptables to 1. I'll make the new sysctl default to =1 as long as ebtables is loaded. Fix is in, please try the new version. New version works fine, thank you!! -- Otto ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Bridge filtering on WRT160NL (ar71xx) not working
Hi! I have a WRT160NL with the 3 interfaces (eth0, eth1, wlan0) on a single bridge (br-lan) and I was normally doing filtering between them but now all the packets are unconditionally bridged to all the interfaces despite the ebtables rules. ebtables doesn't report hits on rules. My last working image was based on r30676 with 3.2.7 kernel, I'm pretty sure is not an upstream kernel problem as I tried latest trunk with kernels 3.2.7, 3.2.12, 3.2.13 and 3.3 and the same problem. Does some default changed recently? -- Otto ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Bridge filtering on WRT160NL (ar71xx) not working
On Tue, Mar 27, 2012 at 03:49:04PM +0200, Florian Fainelli wrote: Hello, Le 03/27/12 15:43, Otto Solares Cabrera a écrit : Hi! I have a WRT160NL with the 3 interfaces (eth0, eth1, wlan0) on a single bridge (br-lan) and I was normally doing filtering between them but now all the packets are unconditionally bridged to all the interfaces despite the ebtables rules. ebtables doesn't report hits on rules. My last working image was based on r30676 with 3.2.7 kernel, I'm pretty sure is not an upstream kernel problem as I tried latest trunk with kernels 3.2.7, 3.2.12, 3.2.13 and 3.3 and the same problem. Does some default changed recently? You might want to revert changeset r30954 and see if that changes something for you. Reverting that changeset fixes my problem, thank you! -- Otto ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] hostapd issue maybe between 30952 - 31118
On Tue, Mar 27, 2012 at 05:03:24PM -0700, Dave Taht wrote: however my issue is that hostapd isn't coming up for ap mode. Yeah in 3.3 the mon.wlan0 i/f is not being setup but I didn't investigate further. OTOH is just me or do you note too that the compressed firmware image with the 3.3 kernel is like 0.25MB bigger than 3.2? It seems too much kernelbloat* to me :( *any similarity with bufferbloat is pure coincidence... :) -- Otto ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] 2012.02 Linaro 4.6
On Sat, Feb 11, 2012 at 01:34:58PM -0500, jonsm...@gmail.com wrote: Updating to Linaro 4.6 2012.02 has fixed those code generation bugs I was hitting. 2012.02 can also compile openssl for ARMv5 again (some Cortex changes had broken it). JFYI 2012.02 works fine for me on all my targets, thanks. -- Otto ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH V2] ar71xx: support for kernel 3.1
On Wed, Jan 18, 2012 at 10:19:45AM +0100, Gabor Juhos wrote: 2012.01.18. 4:42 keltezéssel, Otto Solares Cabrera írta: On Thu, Dec 08, 2011 at 11:57:46PM +0100, Hartmut Knaack wrote: juhosg was working quite hard to get us out of sync, with decent support of nbd ;-) It took me a while, but we're finally back on the track. Minimum kernel version is probably still 3.1.1. Successfully tested with kernel 3.1.4 on a WR1043ND. Kernel version in the Makefile still needs to be adjusted manually. Any comments appreciated. Enjoy. Hi Harmut, do you have something for 3.2? I don't want to duplicate efforts :=) I'm working on that. Great! if you need help with testing let me know. Thank you. -- Otto ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH V2] ar71xx: support for kernel 3.1
On Thu, Dec 08, 2011 at 11:57:46PM +0100, Hartmut Knaack wrote: juhosg was working quite hard to get us out of sync, with decent support of nbd ;-) It took me a while, but we're finally back on the track. Minimum kernel version is probably still 3.1.1. Successfully tested with kernel 3.1.4 on a WR1043ND. Kernel version in the Makefile still needs to be adjusted manually. Any comments appreciated. Enjoy. Hi Harmut, do you have something for 3.2? I don't want to duplicate efforts :=) -- Otto ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH v2 0/3] ar71xx: Add support for Linux-3.0
On Sat, Nov 26, 2011 at 07:27:44AM -0500, Outback Dingo wrote: On Sat, Nov 26, 2011 at 5:49 AM, Outback Dingo outbackdi...@gmail.com wrote: On Sat, Nov 26, 2011 at 4:12 AM, Otto Estuardo Solares Cabrera so...@guug.org wrote: This patch series adds Linux-3.0 kernel support to the ar71xx target in OpenWRT trunk. Tested with Linux-3.0.9. This doesn't switch the default kernel version for ar71xx targets yet. I edited target/linux/ar71xx/Makefile Added # LINUX_VERSION:=2.6.39.4 LINUX_VERSION:=3.0.9 Please disregard the prior email - the kernel tree patching does work attempting to build now Great! let me know if you have any problem, thank you for testing! -- Otto ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] mac80211: read eeprom from platform data
On Sun, Oct 23, 2011 at 06:51:19PM -0600, Philip Prindeville wrote: Personally I would have submitted these two patches separately so that one doesn't hold up the other, especially since they're not visibly related in any way. +1 On 10/23/11 6:22 PM, Andrej Vlašić wrote: This enables eeprom and mac addr. to be read from boards with eeprom stored in platfrom data on flash (it was removed for some reason in rev. 26744) Also it adds pci id ff16, so that sx76x boards can use ath5k. Signed-off-by: Andrej Vlašić andrej.vlasic0 (at) gmail dot com ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] Update mjpeg-streamer package
On Tue, Sep 13, 2011 at 08:20:45AM +0200, Roberto Riggio wrote: It is the output of svn diff. Rev 150 was from the experimental branch so I was not sure how stable it was (considering the mjpeg streamer is pretty volatile). Just FYI I was having problems in many cams with stable and experimental r150 coupled with Linux 2.6.39 or 3.0 fixed my problems in ar71xx devices so IMO is worth a shot if you have issues. - Otto ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] Update mjpeg-streamer package
On Thu, Sep 08, 2011 at 10:31:31AM +0200, Roberto Riggio wrote: This patch upgrades the mjpeg-streamer package to the latest svn revision. It also closes track entry #9896 in the the newer version moved to v4l2. This patch it doesn't apply. mjpg-streamer r150 works for me too. - Otto ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] replace CONFIG_PREEMPT_NONE with CONFIG_PREEMPT
On Fri, Sep 02, 2011 at 12:39:38PM +0200, Luka Perkov wrote: Please look at the kernel config file above. You will see that CONFIG_PREEMPT should be used on embedded systems... Doesn't CONFIG_PREEMPT will add userspace scheduling overhead which in turn harm kernelspace workloads such as packet routing, firewalling, NAT, etc.? I had done some tests in the past with the scheduling priority of the hostapd daemon (with nice and schedtools) but never spot a gain in bandwith or latency with iperf. - Otto ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] Updated versions of NaCl and Quicktun
On Thu, Mar 31, 2011 at 09:40:35PM +0200, Matthias Schiffer wrote: Hi, this updates NaCl to version 20110221 and Quicktun to 2.1.6. Also I improved the Quicktun init script so it doesn't fail when Quicktun takes more than 1 second to start. Hey, this package is excellent, thank you! - Otto (solca) Solares Cabrera ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Developers needed - OpenWrt, Linux kernel, C, networking, etc.
Hello Erik, please see my answers between lines and don't hesitate in
asking me further.
On Mon, Mar 28, 2011 at 11:01:16AM -0400, Erik Levinson wrote:
Caneris is looking for some additional development help at the PS group (one
new position at this time).
Details and requirements:
-Strong C and shell scripting skills
Not to look presumptuous but I can program in C since my 12 years old,
I'm now almost 35 so I have a good deal of C experience plus my
prefered scripting language is Bourne shell as interpreted in busybox
or bash.
-General Linux systems administration and specific knowledge of Debian
Currently I work as {net,sys}admin on a University in Guatemala where I
just use Debian, too I administer servers for a French company with Debian
too. In total I administer like 20 servers plus like 5 VMs plus 125
OpenWRT APs.
-Linux kernel development experience with a focus on networking, particularly
PPP, L2TP, and Ethernet drivers
I just have a few commits to the kernel but I understand it well and
can modify it accordingly to our needs or integrate/backport patches.
I had good deal of Linux networking experience specially in TCP sender
side mods (Vegas, etc.), modified CWND, buffer sizes for NIC Tx ring
and Linux TX queue length, all this with focus in low latency and
buffer debloating (I'm member of the Bufferbloat community).
-Embedded systems development experience, particularly with OpenWrt
In the Whiterussian times I had a very popular patch which fixes the
worst instabilities on Broadcom devices:
http://forum.openwrt.org/viewtopic.php?id=10519
I had deployed commercially this embedded devices (with OpenWRT):
WRT54G/WRT54GL (MIPS)
WRT160NL (MIPS)
SheevaPlug (ARM)
GuruPlug Server Plus (ARM)
Soekris boards (x86)
BeagleBoard (ARM)
LeopardBoard 365 (ARM) (Arago distro)
N810 Nokia Internet Tablet (ARM)
Geos (x86)
Too I was of the firsts to port Android (kernel and userspace) to a real device
(N810)
when Google publish originally the source code, I called my project NITdroid:
http://guug.org/nit/nitdroid/
-Preferably some userspace development experience with OpenL2TP, pppd, and
Quagga
Now that BIRD is better than anything else (additionally it supports
multiple kernel routing tables) I send some fixes to Debian and to
upstream all accepted.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=462341
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=462344
(Some patches were accepted upstream in the mailing list).
-Excellent English verbal and written communication skills and reading
comprehension
Just with verbal English I honestly have a little problem here but I'm
pretty sure others can understand me.
-Self-motivated with ability to work independently and as part of a team
without supervision
I tend to work many hours a day (I fall sleep until 3AM).
-Contract, part-time
Perfect.
-Telecommute with preference given to Canadian residents (though others are
never excluded solely on the basis of being located outside Canada)
I'm in Guatemala so telecommute is perfect for me altough I can travel
at any time. I have USA Visa if that helps too.
-Compensation negotiable
More than excellent!
Please e-mail me if you wish to apply.
Too please check my simple contributions to Free/OSS:
http://home.galileo.edu/~solca/contrib
If you want to discuss something in specific please let me know so I
can expand if I know about it or learn (if I don't know) in the
process.
Thanks for your consideration.
-
Otto (solca) Solares Cabrera
Thanks
Erik
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Developers needed - OpenWrt, Linux kernel, C, networking, etc.
I meant to send this offlist, I'm very sorry. :)
-
Otto
On Mon, Mar 28, 2011 at 12:23:42PM -0600, Otto Solares wrote:
Hello Erik, please see my answers between lines and don't hesitate in
asking me further.
On Mon, Mar 28, 2011 at 11:01:16AM -0400, Erik Levinson wrote:
Caneris is looking for some additional development help at the PS group
(one new position at this time).
Details and requirements:
-Strong C and shell scripting skills
Not to look presumptuous but I can program in C since my 12 years old,
I'm now almost 35 so I have a good deal of C experience plus my
prefered scripting language is Bourne shell as interpreted in busybox
or bash.
-General Linux systems administration and specific knowledge of Debian
Currently I work as {net,sys}admin on a University in Guatemala where I
just use Debian, too I administer servers for a French company with Debian
too. In total I administer like 20 servers plus like 5 VMs plus 125
OpenWRT APs.
-Linux kernel development experience with a focus on networking,
particularly PPP, L2TP, and Ethernet drivers
I just have a few commits to the kernel but I understand it well and
can modify it accordingly to our needs or integrate/backport patches.
I had good deal of Linux networking experience specially in TCP sender
side mods (Vegas, etc.), modified CWND, buffer sizes for NIC Tx ring
and Linux TX queue length, all this with focus in low latency and
buffer debloating (I'm member of the Bufferbloat community).
-Embedded systems development experience, particularly with OpenWrt
In the Whiterussian times I had a very popular patch which fixes the
worst instabilities on Broadcom devices:
http://forum.openwrt.org/viewtopic.php?id=10519
I had deployed commercially this embedded devices (with OpenWRT):
WRT54G/WRT54GL (MIPS)
WRT160NL (MIPS)
SheevaPlug (ARM)
GuruPlug Server Plus (ARM)
Soekris boards (x86)
BeagleBoard (ARM)
LeopardBoard 365 (ARM) (Arago distro)
N810 Nokia Internet Tablet (ARM)
Geos (x86)
Too I was of the firsts to port Android (kernel and userspace) to a real
device (N810)
when Google publish originally the source code, I called my project NITdroid:
http://guug.org/nit/nitdroid/
-Preferably some userspace development experience with OpenL2TP, pppd, and
Quagga
Now that BIRD is better than anything else (additionally it supports
multiple kernel routing tables) I send some fixes to Debian and to
upstream all accepted.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=462341
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=462344
(Some patches were accepted upstream in the mailing list).
-Excellent English verbal and written communication skills and reading
comprehension
Just with verbal English I honestly have a little problem here but I'm
pretty sure others can understand me.
-Self-motivated with ability to work independently and as part of a team
without supervision
I tend to work many hours a day (I fall sleep until 3AM).
-Contract, part-time
Perfect.
-Telecommute with preference given to Canadian residents (though others are
never excluded solely on the basis of being located outside Canada)
I'm in Guatemala so telecommute is perfect for me altough I can travel
at any time. I have USA Visa if that helps too.
-Compensation negotiable
More than excellent!
Please e-mail me if you wish to apply.
Too please check my simple contributions to Free/OSS:
http://home.galileo.edu/~solca/contrib
If you want to discuss something in specific please let me know so I
can expand if I know about it or learn (if I don't know) in the
process.
Thanks for your consideration.
-
Otto (solca) Solares Cabrera
Thanks
Erik
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Developers needed - OpenWrt, Linux kernel, C, networking, etc.
On Mon, Mar 28, 2011 at 01:47:09PM -0500, Larry Vaden wrote: On Mon, Mar 28, 2011 at 1:28 PM, Otto Solares so...@guug.org wrote: I meant to send this offlist, I'm very sorry. :) I'm thinking many in the audience are quite impressed. Thank you for your kind words! I would love to work exclusively on embedded stuff and OpenWRT. - Otto (solca) Solares Cabrera ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] /etc/config/wireless empty
Better first check as the others if your ART partition is empty, then if that's the case I'll help you. - Otto On Tue, Apr 13, 2010 at 09:12:50PM +0200, Thierry MUSEUX - www.fwt.fr - wrote: I have exactly the same problem. could you tell us howto restore if we have only one device ? What is the procedure with one working device ? Thierry -Message d'origine- De : openwrt-devel-boun...@lists.openwrt.org [mailto:openwrt-devel-boun...@lists.openwrt.org] De la part de so...@guug.org Envoyé : mardi 13 avril 2010 19:05 À : OpenWrt Development List Objet : Re: [OpenWrt-Devel] /etc/config/wireless empty On Tue, Apr 13, 2010 at 09:42:12AM +0100, Nuno Gonçalves wrote: [20777] breaks wireless, /etc/config/wireless is empty on install on a wrt160nl. r...@openwrt:/# dmesg | grep ath9k ath9k ath9k: failed to initialize device ath9k: probe of ath9k failed with error -5 revision: r20835(latest) logread: http://pastebin.com/Yt8eUrC1 dmesg: http://pastebin.com/144KEgJ5 I'm running r20791 on 75 WRT160NLs without problems. By your dmesg output it seems you screw your ART flash partition which will not let you operate the wireless interface if it's missing. It happens to me too some time ago, first check it's empty and if it is you can use this patch to restore from a working device: http://home.galileo.edu/~solca/openwrt/wrt160nl-forfixeeprom.patch Regards, - solca ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] /etc/config/wireless empty
On Tue, Apr 13, 2010 at 09:54:14PM +0100, Nuno Gonçalves wrote: SOLCA: Your patch is nevertheless interesting. Why isn't it merged on trunk? Because it's dangerous, normally you should not mess with a r/w ART partition. Also, I had some problems a few weeks ago were firstboot wasn't reseting the device to flash default. Do you think it have something to do with this? Don't think so as that was fixed for WRT160NL with new bootloaders a few weeks ago. - Otto ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Backfire 10.03-rc1
On Thu, Mar 25, 2010 at 11:59:56PM +0100, Matthias Buecher / Germany wrote:
If 2.6.32.10 will be *the* desired version, then Orion can be just
switched to it.
My WRT350Nv2 is really running fine with it.
File: target/linux/orion/Makefile
No need to rebase any patches.
Same for target/linux/ar71xx/Makefile on WRT160NL working fine since
last week.
-
Otto
Maddes
On 25.03.2010 22:57, Nico wrote:
It seems 2.6.32.10 applies on all targets at 2.6.32.9, so I have no
problem switching to 2.6.32.10. Ideally, it would be great if all
targets at 2.6.32.x could be switched to the same version (coherency)
and such updates be committed before Friday evening.
--
-{Nico}
On 25/03/10 22:44, Matthias Buecher / Germany wrote:
Sorry, a typo, meant 2.6._32_.10 not .30.10.
On 25.03.2010 22:15, Matthias Buecher / Germany wrote:
Do I understand correctly that kernel 2.6.32.9 is one of the preferred
kernels for Backfire, and not 2.6.30.10?
(see https://dev.openwrt.org/changeset/20410 and Nico's [2])
Just want to make sure.
Maddes
P.S.:
Will install it onto my LinkSys WRT350Nv2 this weekend if time permits.
On 24.03.2010 18:15, Nico wrote:
Backfire 10.03-rc1 is still based on trunk @ 20254. In Backfire
10.03-rc1 milestone in Trac [1], you can find the diff used attached
[2] at the end of the page.
1. https://dev.openwrt.org/milestone/Backfire%2010.03-rc1
2.
https://dev.openwrt.org/attachment/milestone/Backfire%2010.03-rc1/backfire-10.03-rc1-trunk-r20254.diff
Regards,
--
-{Nico}
Bruno Wolff III wrote:
On Wed, Mar 24, 2010 at 17:10:25 +0100,
Nico n...@openwrt.org wrote:
*** Release Candidate 1 ***
The OpenWrt Team would like to announce a release candidate (RC1) of
the
next major release, codenamed Backfire. Testing of this build will help
refine the code in preparation of the final release.
Binaries can be downloaded at
http://downloads.openwrt.org/backfire/10.03-rc1/
Is there a separate branch for backfire or is it trunk?
(I want some extra things built in, and so am interested in doing builds
that use the same code as backfire but with a couple of different build
options.)
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] WRT160NL new bootloader fix
On Wed, Mar 24, 2010 at 02:39:51PM +0100, Bernhard Loos wrote:
After a suggestion from xMff, I dedicded to use a uci-defaults script,
as this should fit the needs. Use it instead of the firstboot script
in the original patch.
I can't test it, as I don't have the device with me right now, but it's
trivial.
Based on others ar71xx uci-defaults scripts and yours I think the
attached patch is a little better.
Tested successfully with your original patch in both pure jffs2 and
squashfs and it works fine.
-
Otto
Index: target/linux/ar71xx/base-files/etc/uci-defaults/wrt160nl
===
--- target/linux/ar71xx/base-files/etc/uci-defaults/wrt160nl (revision 0)
+++ target/linux/ar71xx/base-files/etc/uci-defaults/wrt160nl (revision 0)
@@ -0,0 +1,16 @@
+#!/bin/sh
+#
+# Copyright (C) 2010 OpenWrt.org
+#
+
+. /lib/ar71xx.sh
+
+board=$(ar71xx_board_name)
+
+wrt160nl_fixtrx() {
+ mtd -o 32 fixtrx firmware
+}
+
+if [ ${board} == wrt160nl ]; then
+ wrt160nl_fixtrx
+fi
Property changes on: target/linux/ar71xx/base-files/etc/uci-defaults/wrt160nl
___
Added: svn:executable
+ *
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] WRT160NL new bootloader fix
On Sat, Mar 20, 2010 at 01:38:58PM +0100, Matthias Buecher / Germany wrote: Is the script set to executable (+x) in the image? This is typical for scripts that are presebt but not running, and often overlooked. Scripts in /lib/firstboot are not executable as they are sourced and not executed directly so that's not the problem here. - Otto ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] WRT160NL new bootloader fix
On Sat, Mar 20, 2010 at 06:14:08PM +0100, Jo-Philipp Wich wrote: I think the real issue is that the preinit hook used by the fix script is not executed on jffs2-only images. Exactly, this script is added to the switch2jffs hooks which aren't executed on a pure jffs2 image. It seems there are just 2 hooks: switch2jffs and jffs2reset, neither seems appropiate for this kind of scripts. It would be nice to have another independent of filesystems hook but I'm not a preinit expert as it seems to me a little overcomplicated, hopefully someone who knows can give the OP advice as his fix is necesary. Thank you! - Otto ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] WRT160NL new bootloader fix
On Fri, Mar 19, 2010 at 04:53:34PM +0100, Bernhard Loos wrote: Does this happen directly after flashing or only after a reboot? After the first reboot. If openwrt does come up at least once, could you run mtd -o 32 fixtrx firmware and give me the output? Yes, it comes up once and for the next reboot/power-cycle it lose the firmware and waits for a TFTP firmware. I'm not near this new WRT160NL so I'll send you the output later. Thank you for looking into this! - Otto 2010/3/19 Otto Solares so...@guug.org: On Wed, Mar 17, 2010 at 05:34:33PM +0100, Bernhard Loos wrote: Hello I forgot to svn add the firstboot script, that actually calls mtd to fix the trx, sorry about that. Here is the complete patch again. Bernhard Hello Bernhard, FYI I try your patch on my newer WRT160NL but it lost again the new firmware on boot and just sits waiting for a TFTP put from the network. - Otto ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] WRT160NL new bootloader fix
On Fri, Mar 19, 2010 at 11:25:40AM -0600, Otto Solares wrote: On Fri, Mar 19, 2010 at 04:53:34PM +0100, Bernhard Loos wrote: Does this happen directly after flashing or only after a reboot? After the first reboot. If openwrt does come up at least once, could you run mtd -o 32 fixtrx firmware and give me the output? Yes, it comes up once and for the next reboot/power-cycle it lose the firmware and waits for a TFTP firmware. I'm not near this new WRT160NL so I'll send you the output later. r...@openwrt:~# mtd -o 32 fixtrx firmware Trying to fix trx header in firmware at 0x20... New crc32: 0x73ea777a, rewriting block Done. - Otto ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] WRT160NL new bootloader fix
On Fri, Mar 19, 2010 at 06:34:03PM -0600, Otto Solares wrote: On Fri, Mar 19, 2010 at 11:25:40AM -0600, Otto Solares wrote: On Fri, Mar 19, 2010 at 04:53:34PM +0100, Bernhard Loos wrote: Does this happen directly after flashing or only after a reboot? After the first reboot. If openwrt does come up at least once, could you run mtd -o 32 fixtrx firmware and give me the output? Yes, it comes up once and for the next reboot/power-cycle it lose the firmware and waits for a TFTP firmware. I'm not near this new WRT160NL so I'll send you the output later. r...@openwrt:~# mtd -o 32 fixtrx firmware Trying to fix trx header in firmware at 0x20... New crc32: 0x73ea777a, rewriting block Done. FYI after this command it always boots fine now. - Otto ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] WRT160NL new bootloader fix
Rechecked and yes, I'm using your latest patch and at boot the file /lib/firstboot/25_fixtrx is there but next boot lose the firmware. BTW I'm just using pure jffs2 image, will test squashfs and let you know. - Otto On Sat, Mar 20, 2010 at 02:27:29AM +0100, Bernhard Loos wrote: Are you really sure, you used the second patch I posted and the firstboot script is included in the image? 2010/3/20 Otto Solares so...@guug.org: On Fri, Mar 19, 2010 at 06:34:03PM -0600, Otto Solares wrote: On Fri, Mar 19, 2010 at 11:25:40AM -0600, Otto Solares wrote: On Fri, Mar 19, 2010 at 04:53:34PM +0100, Bernhard Loos wrote: Does this happen directly after flashing or only after a reboot? After the first reboot. If openwrt does come up at least once, could you run mtd -o 32 fixtrx firmware and give me the output? Yes, it comes up once and for the next reboot/power-cycle it lose the firmware and waits for a TFTP firmware. I'm not near this new WRT160NL so I'll send you the output later. r...@openwrt:~# mtd -o 32 fixtrx firmware Trying to fix trx header in firmware at 0x20... New crc32: 0x73ea777a, rewriting block Done. FYI after this command it always boots fine now. - Otto ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] WRT160NL new bootloader fix
It works on squashfs but didn't on pure jffs2 which I pressume was our only environment difference. The logcat diff between jffs2 and squashfs seems to be: +user.info sysinit: Trying to fix trx header in firmware at 0x20... +user.info sysinit: New crc32: 0x407d9371, rewriting block +user.info sysinit: Done. +user.warn kernel: jffs2_scan_eraseblock(): End of filesystem marker found at 0x0 +user.warn kernel: jffs2_build_filesystem(): unlocking the mtd device... done. +user.warn kernel: jffs2_build_filesystem(): erasing all blocks after the end marker... done. +user.info sysinit: copying files ... done +user.info kernel: mini_fo: using base directory: / +user.info kernel: mini_fo: using storage directory: /jffs Obviously it's not running on pure jffs2 images but it seems to me a bug in the firstboot scripts unrelated to your patch... - Otto On Fri, Mar 19, 2010 at 08:12:24PM -0600, Otto Solares wrote: Rechecked and yes, I'm using your latest patch and at boot the file /lib/firstboot/25_fixtrx is there but next boot lose the firmware. BTW I'm just using pure jffs2 image, will test squashfs and let you know. - Otto On Sat, Mar 20, 2010 at 02:27:29AM +0100, Bernhard Loos wrote: Are you really sure, you used the second patch I posted and the firstboot script is included in the image? 2010/3/20 Otto Solares so...@guug.org: On Fri, Mar 19, 2010 at 06:34:03PM -0600, Otto Solares wrote: On Fri, Mar 19, 2010 at 11:25:40AM -0600, Otto Solares wrote: On Fri, Mar 19, 2010 at 04:53:34PM +0100, Bernhard Loos wrote: Does this happen directly after flashing or only after a reboot? After the first reboot. If openwrt does come up at least once, could you run mtd -o 32 fixtrx firmware and give me the output? Yes, it comes up once and for the next reboot/power-cycle it lose the firmware and waits for a TFTP firmware. I'm not near this new WRT160NL so I'll send you the output later. r...@openwrt:~# mtd -o 32 fixtrx firmware Trying to fix trx header in firmware at 0x20... New crc32: 0x73ea777a, rewriting block Done. FYI after this command it always boots fine now. - Otto ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] WRT160NL new bootloader fix
On Wed, Mar 17, 2010 at 05:34:33PM +0100, Bernhard Loos wrote: Hello I forgot to svn add the firstboot script, that actually calls mtd to fix the trx, sorry about that. Here is the complete patch again. Bernhard Hello Bernhard, FYI I try your patch on my newer WRT160NL but it lost again the new firmware on boot and just sits waiting for a TFTP put from the network. - Otto ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] WRT160NL new bootloader fix
On Tue, Mar 16, 2010 at 12:21:14PM +0100, Bernhard Loos wrote: Hello The WRT160NL gets shipped with a new bootloader since some time, which actually checks the checksum in the trx image header. As the checksummed area includes the jffs2 start marker, this will blow up after first boot. This patch fixes this by adding a new funktion to mtd (fixtrx) which is called in firstboot. It also gets rid of the unneeded padding of 65kB. Bernhard Excellent! I just received a new WRT160NL with this new check thank you! - Otto PS. Your patch have ugly ^M ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] ath9k in openwrt
On Mon, Feb 08, 2010 at 04:24:34PM +0800, Michael Geddes wrote: The drivers work pretty well.. .though not entirely stable. Every few days I have to run a script that will ifdown wlan, rmmod the modules, insert the modules back and ifup wlan... and every now and again, the server reboots itself, I believe because of ath9k drivers.. and even rarer, I get a crashed kernel on occasions. Same here, just that in many cases a simple 'wifi' command will reset and fix the situation but rarely I have to rmmod and insmod the ath9k driver as you said. - Otto ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Preinit fixes
On Tue, Jan 26, 2010 at 07:28:18AM -0800, Marc Abrams wrote: See, http://cshore.is-a-geek.com/openwrt/preinit_mount.html It's fully documented along with an example. Hi Marc, I read the following: Preinit 3. Initializes device tree (/dev) Does that takes into account the new devtmpfs on 2.6.32+? My WRT160NL with OpenWRT, 2.6.32 kernel and trunk before your code's commit reads: devtmpfs on /dev type devtmpfs (rw,size=14692k,nr_inodes=3673) I think it was mounted automagically by the kernel himself like old devfs. Regards, - Otto ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Preinit fixes
On Tue, Jan 26, 2010 at 10:59:53AM -0800, Marc Abrams wrote: Otto: I don't think so currently, but it should be pretty easy to add. Currently the main development branch for brcm63xx uses 2.6.30.10. marc. Ok, hopefully all platforms will switch to 2.6.32 as it is a long term release by the stable kernel maintainer. Your, - Otto On Tue, Jan 26, 2010 at 10:54 AM, Otto Solares so...@guug.org wrote: On Tue, Jan 26, 2010 at 07:28:18AM -0800, Marc Abrams wrote: See, http://cshore.is-a-geek.com/openwrt/preinit_mount.html It's fully documented along with an example. Hi Marc, I read the following: Preinit 3. Initializes device tree (/dev) Does that takes into account the new devtmpfs on 2.6.32+? My WRT160NL with OpenWRT, 2.6.32 kernel and trunk before your code's commit reads: devtmpfs on /dev type devtmpfs (rw,size=14692k,nr_inodes=3673) I think it was mounted automagically by the kernel himself like old devfs. Regards, - Otto ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] mac80211: correct application of the rts threshold config
Signed-off-by: Otto Solares so...@guug.org
---
Index: package/mac80211/files/lib/wifi/mac80211.sh
===
--- package/mac80211/files/lib/wifi/mac80211.sh (revisión: 18444)
+++ package/mac80211/files/lib/wifi/mac80211.sh (copia de trabajo)
@@ -207,7 +207,7 @@
config_get rts $vif rts
if [ -n $rts ]; then
- iw phy $phy set rts ${frag%%.*}
+ iw phy $phy set rts ${rts%%.*}
fi
ifconfig $ifname up
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
