[OpenWrt-Devel] /etc/ethers and sysupgrade
I've noticed that /etc/ethers is not preserved over sysupgrades but /etc/hosts is I can fix this with /etc/sysupgrade.conf but I think it should be part of the default set of kept files -- Tim Fletcher t...@night-shade.org.uk ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] [kirkwood] Enable eSATA sheevaplug
I would love to see eSATA Sheevaplug supported by standard OpenWRT kirkwood images. Since standard Sheevaplug is already supported, the CONFIG_MACH_ESATA_SHEEVAPLUG option just adds a little MACHINE_START definition and we have support for eSATA Sheevaplug and the kernel image is only enlarged by 56 bytes. Signed-off-by: Unai Uribarri una...@gmail.com diff --git a/target/linux/kirkwood/config-3.3 b/target/linux/kirkwood/config-3.3 index 7dd154d..a32e150 100644 --- a/target/linux/kirkwood/config-3.3 +++ b/target/linux/kirkwood/config-3.3 @@ -101,7 +101,7 @@ CONFIG_LEGACY_PTY_COUNT=256 CONFIG_MACH_DOCKSTAR=y CONFIG_MACH_GOFLEXNET=y CONFIG_MACH_GOFLEXHOME=y -# CONFIG_MACH_ESATA_SHEEVAPLUG is not set +CONFIG_MACH_ESATA_SHEEVAPLUG=y # CONFIG_MACH_GURUPLUG is not set CONFIG_MACH_ICONNECT=y # CONFIG_MACH_INETSPACE_V2 is not set ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] [kirkwood] Enable eSATA sheevaplug
On 24/08/12 13:20, Unai Uribarri wrote: I would love to see eSATA Sheevaplug supported by standard OpenWRT kirkwood images. Since standard Sheevaplug is already supported, the CONFIG_MACH_ESATA_SHEEVAPLUG option just adds a little MACHINE_START definition and we have support for eSATA Sheevaplug and the kernel image is only enlarged by 56 bytes. Signed-off-by: Unai Uribarri una...@gmail.com diff --git a/target/linux/kirkwood/config-3.3 b/target/linux/kirkwood/config-3.3 index 7dd154d..a32e150 100644 --- a/target/linux/kirkwood/config-3.3 +++ b/target/linux/kirkwood/config-3.3 @@ -101,7 +101,7 @@ CONFIG_LEGACY_PTY_COUNT=256 CONFIG_MACH_DOCKSTAR=y CONFIG_MACH_GOFLEXNET=y CONFIG_MACH_GOFLEXHOME=y -# CONFIG_MACH_ESATA_SHEEVAPLUG is not set +CONFIG_MACH_ESATA_SHEEVAPLUG=y # CONFIG_MACH_GURUPLUG is not set CONFIG_MACH_ICONNECT=y # CONFIG_MACH_INETSPACE_V2 is not set ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel you mailed this patch 3 days ago already... it was merged earlier today ... did you feel like increasing the traffic on the ML ? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] Keep /etc/nginx on sysupgrade
Jo-Philipp Wich wrote: It looks like conffiles can only save files, not entire directories. /etc/nginx is a directory. Should conffiles be fixed to work with directories too? It works fine with directories, see include/package-ipkg.mk, the code below ifneq ($$(KEEP_$(1)),) I see. The existing feeds/packages/net/nginx/Makefile already lists the files under /etc/nginx that ship in the package in its conffiles definition, but this doesn't result in a keep file in the package because include/package-ipkg.mk will only add entries to a keep file when they aren't present as files in the package. Is this intentional? The net effect is that changes to conffiles aren't preserved across sysupgrade when default conffiles are present in a package. If that's the case, what's the point of even listing these files in conffiles? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] Keep /etc/nginx on sysupgrade
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I see. The existing feeds/packages/net/nginx/Makefile already lists the files under /etc/nginx that ship in the package in its conffiles definition, but this doesn't result in a keep file in the package because include/package-ipkg.mk will only add entries to a keep file when they aren't present as files in the package. ... or when the entry is a directory. But they will get recorded by opkg, which is another source sysupgrade uses to assemble the list of files to get backed up. The sysupgrade list is the distinct union of find -type f $(cat /etc/sysupgrade.conf) find -type f $(cat /lib/upgrade/keep.d/*) opkg list-changed-conffiles Is this intentional? Yey. The net effect is that changes to conffiles aren't preserved across sysupgrade when default conffiles are present in a package. Huh? If that's the case, what's the point of even listing these files in conffiles? The point is: - - Existing file entries in conffiles are tracked by opkg, and opkg list-changed-conffiles is used to only back up actually modified configs during a sysupgrade - - Directory or not existing file entries are added to the keep list so that they're unconditionally backed up during sysupgrade I agree that adding /etc/nginx will overrule the opkg tracking (means files are *always* backed up, even if unchanged, but that is such a minor problem that neither needs fixing nor much discussion about. In any case, simply add /etc/nginx/ to conffiles, it will work as intended and you do not need to ship a custom keep file. ~ Jow -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlA3d/cACgkQdputYINPTPMmdwCfZcvNtg1ogFC2W4haYjYEv4lI 5N0An3egffwxDtaXlo6/1c50OJW/CoZT =BxMq -END PGP SIGNATURE- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] Keep /etc/nginx on sysupgrade
Jo-Philipp Wich wrote: But they will get recorded by opkg, which is another source sysupgrade uses to assemble the list of files to get backed up. This is the part I was missing. Thanks for the explanation. I've submitted a v2 patch in case it's thought to be generally useful, otherwise I'll just carry it locally. I also submitted a patch to upgrade nginx 1.2.3 separately a few days ago. That shouldn't be controversial at all. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH v2] Keep /etc/nginx/ on sysupgrade
This allows additional files in /etc/nginx/, such as SSL certificates, tobe saved on sysupgrade. Signed-off-by: Mark Mentovai m...@moxienet.com --- Index: packages/net/nginx/Makefile === --- packages/net/nginx/Makefile (revision 33213) +++ packages/net/nginx/Makefile (working copy) @@ -48,12 +48,7 @@ config_files=nginx.conf mime.types fastcgi_params koi-utf koi-win win-utf define Package/nginx/conffiles -/etc/nginx/nginx.conf -/etc/nginx/mime.types -/etc/nginx/fastcgi_params -/etc/nginx/koi-utf -/etc/nginx/koi-win -/etc/nginx/win-utf +/etc/nginx/ endef ADDITIONAL_MODULES:= ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] base-files: add config option for log rotation in syslogd
Signed-off-by: Petr Štetiar yn...@true.cz
---
package/base-files/files/etc/init.d/boot |5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/package/base-files/files/etc/init.d/boot
b/package/base-files/files/etc/init.d/boot
index 43837a8..54afbb8 100755
--- a/package/base-files/files/etc/init.d/boot
+++ b/package/base-files/files/etc/init.d/boot
@@ -26,15 +26,16 @@ system_config() {
date -k
if [ -x /sbin/syslogd ]; then
- local args log_ip log_size log_port log_type log_file
+ local args log_ip log_size log_port log_type log_file log_rotate
config_get log_ip $cfg log_ip
config_get log_size $cfg log_size 16
config_get log_port $cfg log_port 514
config_get log_type $cfg log_type circular
config_get log_file $cfg log_file /var/log/messages
+ config_get log_rotate $cfg log_rotate 1
args=${log_ip:+-L -R ${log_ip}:${log_port}} ${conloglevel:+-l
$conloglevel}
if [ $log_type = file ]; then
- args=$args -s $log_size -O $log_file -S
+ args=$args -s $log_size -O $log_file -S -b
${log_rotate}
else
args=$args -C${log_size}
fi
--
1.7.9.5
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Need to hire a person for Creating a Custom Luci menu for a new SOC port.
Hello Everyone, I need a custom Luci menu for a new soc port we are working on. We would like some one that is an expert with Luci since we are on a time crunch. We have 3 weeks to do it, and I will start the offer at 1000 usd OBO. We want a style similar to the FON 2.0n. Best Regards, Jason ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH v2] Keep /etc/nginx/ on sysupgrade
On 24/08/12 15:14, Mark Mentovai wrote: This allows additional files in /etc/nginx/, such as SSL certificates, tobe saved on sysupgrade. Signed-off-by: Mark Mentovai m...@moxienet.com after not reading the 100 mails leading up to this patch i expected something big ;) Thanks, applied in r33271 John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] ath5k and txpower
My problem is likely unrelated, but could you (Tobias) say precisely what revision of trunk you are using? Freshly compiled trunk r33202 w/ default config does not appear to boot at all on my OM1P (ar2315 chipset), i.e. no response on eth0. However, I don't think the bugs mentioned w/ compat-wireless in this thread could cause that. On Sat, Aug 4, 2012 at 7:34 PM, Tobias Diedrich ranma+open...@tdiedrich.de wrote: Compiling OpenWRT from trunk, I've found that there are issues with setting txpower on AR2417: - No txpower setting in LuCI gui - iw phy phy0 info shows 0dBm for all channels regardless of regdomain [9.332000] cfg80211: Calling CRDA to update world regulatory domain [9.34] cfg80211: World regulatory domain updated: [9.344000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [9.352000] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [9.36] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [9.364000] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [9.372000] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm) [9.38] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm) root@OpenWrt:/# iw phy phy0 info Wiphy phy0 Band 1: Frequencies: * 2412 MHz [1] (0.0 dBm) * 2417 MHz [2] (0.0 dBm) * 2422 MHz [3] (0.0 dBm) * 2427 MHz [4] (0.0 dBm) * 2432 MHz [5] (0.0 dBm) * 2437 MHz [6] (0.0 dBm) * 2442 MHz [7] (0.0 dBm) * 2447 MHz [8] (0.0 dBm) * 2452 MHz [9] (0.0 dBm) * 2457 MHz [10] (0.0 dBm) * 2462 MHz [11] (0.0 dBm) * 2467 MHz [12] (0.0 dBm) * 2472 MHz [13] (0.0 dBm) * 2484 MHz [14] (disabled) One issue seems to be fallout from http://git.kernel.org/?p=linux/kernel/git/linville/wireless-next.git;a=commitdiff;h=eccc068e8e84c8fe997115629925e0422a98e4de AFAICS max_power for the channels is never set and thus min(chan-max_power, chan-max_reg_power) is 0. This patch tries to fix this (but is probably wrong :)) After applying this patch iw phy phy0 info looks good, but WiFi Analyzer on my phone still shows a very weak signal for the AP. Until I do this: root@OpenWrt:/# iw phy phy0 set txpower fixed 0 root@OpenWrt:/# iw phy phy0 set txpower auto And then the signal strength is good. iw phy phy0 set txpower fixed|limit still doesn't accept values above 0 for some reason though. Index: compat-wireless-2012-07-16/drivers/net/wireless/ath/ath5k/base.c === --- compat-wireless-2012-07-16.orig/drivers/net/wireless/ath/ath5k/base.c 2012-08-05 01:42:19.141413438 +0200 +++ compat-wireless-2012-07-16/drivers/net/wireless/ath/ath5k/base.c 2012-08-05 01:44:19.957568271 +0200 @@ -325,6 +325,8 @@ if (!ath5k_is_standard_channel(ch, band)) continue; + channels[count].max_power = AR5K_TUNE_MAX_TXPOWER; + count++; } -- Tobias PGP: http://8ef7ddba.uguu.de ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel -- Ben West http://gowasabi.net b...@gowasabi.net ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] WRT54g / b43 / mac802.11 BREAKTHROUGH
Do you have any info whether the failure occurs with the change from OFDM to CCK, or vice versa? I am wondering if the radio needs a dummy i cannot answer this question - interesting idea. i like to test your patch, simply do a dummy tx in both cases. bye, bastian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] ath5k and txpower
When I rebuilt the other day my ar2315 would not boot due to jffs2 errors. I haven't checked to see if it was something in my tree, but just thought i'd let you know. I can rebuilt with a clean true today and watch serial to see if the issue persists. On 08/24/2012 01:02 PM, Ben West wrote: My problem is likely unrelated, but could you (Tobias) say precisely what revision of trunk you are using? Freshly compiled trunk r33202 w/ default config does not appear to boot at all on my OM1P (ar2315 chipset), i.e. no response on eth0. However, I don't think the bugs mentioned w/ compat-wireless in this thread could cause that. On Sat, Aug 4, 2012 at 7:34 PM, Tobias Diedrich ranma+open...@tdiedrich.de wrote: Compiling OpenWRT from trunk, I've found that there are issues with setting txpower on AR2417: - No txpower setting in LuCI gui - iw phy phy0 info shows 0dBm for all channels regardless of regdomain [9.332000] cfg80211: Calling CRDA to update world regulatory domain [9.34] cfg80211: World regulatory domain updated: [9.344000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [9.352000] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [9.36] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [9.364000] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [9.372000] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm) [9.38] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm) root@OpenWrt:/# iw phy phy0 info Wiphy phy0 Band 1: Frequencies: * 2412 MHz [1] (0.0 dBm) * 2417 MHz [2] (0.0 dBm) * 2422 MHz [3] (0.0 dBm) * 2427 MHz [4] (0.0 dBm) * 2432 MHz [5] (0.0 dBm) * 2437 MHz [6] (0.0 dBm) * 2442 MHz [7] (0.0 dBm) * 2447 MHz [8] (0.0 dBm) * 2452 MHz [9] (0.0 dBm) * 2457 MHz [10] (0.0 dBm) * 2462 MHz [11] (0.0 dBm) * 2467 MHz [12] (0.0 dBm) * 2472 MHz [13] (0.0 dBm) * 2484 MHz [14] (disabled) One issue seems to be fallout from http://git.kernel.org/?p=linux/kernel/git/linville/wireless-next.git;a=commitdiff;h=eccc068e8e84c8fe997115629925e0422a98e4de AFAICS max_power for the channels is never set and thus min(chan-max_power, chan-max_reg_power) is 0. This patch tries to fix this (but is probably wrong :)) After applying this patch iw phy phy0 info looks good, but WiFi Analyzer on my phone still shows a very weak signal for the AP. Until I do this: root@OpenWrt:/# iw phy phy0 set txpower fixed 0 root@OpenWrt:/# iw phy phy0 set txpower auto And then the signal strength is good. iw phy phy0 set txpower fixed|limit still doesn't accept values above 0 for some reason though. Index: compat-wireless-2012-07-16/drivers/net/wireless/ath/ath5k/base.c === --- compat-wireless-2012-07-16.orig/drivers/net/wireless/ath/ath5k/base.c 2012-08-05 01:42:19.141413438 +0200 +++ compat-wireless-2012-07-16/drivers/net/wireless/ath/ath5k/base.c 2012-08-05 01:44:19.957568271 +0200 @@ -325,6 +325,8 @@ if (!ath5k_is_standard_channel(ch, band)) continue; + channels[count].max_power = AR5K_TUNE_MAX_TXPOWER; + count++; } -- Tobias PGP: http://8ef7ddba.uguu.de ___ 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] WRT54g / b43 / mac802.11 BREAKTHROUGH
How do I monitor this particular channel with an other wifi card to get most of the packages, with aircrack I am unable to set the channel? the simple approach is installing horst on another router or your pc. ofcourse you get a full dump with wireshark sniffing on your monitor-interface. bye, bastian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] ath5k and txpower
Thank you, Jonathan. I should note that r33202 boots fine for me on ar71xx, if that helps narrow down a root cause. On Fri, Aug 24, 2012 at 12:15 PM, Jonathan Bither jonbit...@gmail.com wrote: When I rebuilt the other day my ar2315 would not boot due to jffs2 errors. I haven't checked to see if it was something in my tree, but just thought i'd let you know. I can rebuilt with a clean true today and watch serial to see if the issue persists. On 08/24/2012 01:02 PM, Ben West wrote: My problem is likely unrelated, but could you (Tobias) say precisely what revision of trunk you are using? Freshly compiled trunk r33202 w/ default config does not appear to boot at all on my OM1P (ar2315 chipset), i.e. no response on eth0. However, I don't think the bugs mentioned w/ compat-wireless in this thread could cause that. On Sat, Aug 4, 2012 at 7:34 PM, Tobias Diedrich ranma+open...@tdiedrich.de wrote: Compiling OpenWRT from trunk, I've found that there are issues with setting txpower on AR2417: - No txpower setting in LuCI gui - iw phy phy0 info shows 0dBm for all channels regardless of regdomain [9.332000] cfg80211: Calling CRDA to update world regulatory domain [9.34] cfg80211: World regulatory domain updated: [9.344000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [9.352000] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [9.36] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [9.364000] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [9.372000] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm) [9.38] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm) root@OpenWrt:/# iw phy phy0 info Wiphy phy0 Band 1: Frequencies: * 2412 MHz [1] (0.0 dBm) * 2417 MHz [2] (0.0 dBm) * 2422 MHz [3] (0.0 dBm) * 2427 MHz [4] (0.0 dBm) * 2432 MHz [5] (0.0 dBm) * 2437 MHz [6] (0.0 dBm) * 2442 MHz [7] (0.0 dBm) * 2447 MHz [8] (0.0 dBm) * 2452 MHz [9] (0.0 dBm) * 2457 MHz [10] (0.0 dBm) * 2462 MHz [11] (0.0 dBm) * 2467 MHz [12] (0.0 dBm) * 2472 MHz [13] (0.0 dBm) * 2484 MHz [14] (disabled) One issue seems to be fallout from http://git.kernel.org/?p=linux/kernel/git/linville/wireless-next.git;a=commitdiff;h=eccc068e8e84c8fe997115629925e0422a98e4de AFAICS max_power for the channels is never set and thus min(chan-max_power, chan-max_reg_power) is 0. This patch tries to fix this (but is probably wrong :)) After applying this patch iw phy phy0 info looks good, but WiFi Analyzer on my phone still shows a very weak signal for the AP. Until I do this: root@OpenWrt:/# iw phy phy0 set txpower fixed 0 root@OpenWrt:/# iw phy phy0 set txpower auto And then the signal strength is good. iw phy phy0 set txpower fixed|limit still doesn't accept values above 0 for some reason though. Index: compat-wireless-2012-07-16/drivers/net/wireless/ath/ath5k/base.c === --- compat-wireless-2012-07-16.orig/drivers/net/wireless/ath/ath5k/base.c 2012-08-05 01:42:19.141413438 +0200 +++ compat-wireless-2012-07-16/drivers/net/wireless/ath/ath5k/base.c 2012-08-05 01:44:19.957568271 +0200 @@ -325,6 +325,8 @@ if (!ath5k_is_standard_channel(ch, band)) continue; + channels[count].max_power = AR5K_TUNE_MAX_TXPOWER; + count++; } -- Tobias PGP: http://8ef7ddba.uguu.de ___ 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 -- Ben West http://gowasabi.net b...@gowasabi.net ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH v2] Keep /etc/nginx/ on sysupgrade
John Crispin wrote: On 24/08/12 15:14, Mark Mentovai wrote: This allows additional files in /etc/nginx/, such as SSL certificates, tobe saved on sysupgrade. Signed-off-by: Mark Mentovai m...@moxienet.com after not reading the 100 mails leading up to this patch i expected something big ;) Yeah, I had misunderstood a couple of things, it's way easier than I was making it. Thanks, applied in r33271 Thanks, John. Can you take the nginx 1.2.3 upgrade I sent in a few days ago too? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH v2] Keep /etc/nginx/ on sysupgrade
Thanks, applied in r33271 Thanks, John. Can you take the nginx 1.2.3 upgrade I sent in a few days ago too? not merging any new stuff and/or updates atm ... -- https://lists.openwrt.org/pipermail/openwrt-devel/2012-August/016411.html is there a specific reason, such as a security fix or is it just a feature update ? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] dev.openwrt.org throwing 502 Bad Gateway errors
dev.openwrt.ort seems to be throwing 502 errors, at least for the past hour or so. https://dev.openwrt.org/browser/trunk https://dev.openwrt.org/browser/branches -- Ben West http://gowasabi.net b...@gowasabi.net ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Unable to mount squashfs, no real error returned (Invalid argument)
Hey, I have original firmware installed on my (unsupported) router and I'm booting ELF image using tftp. My purpose is to get correct partitions layout and access to them. Linux correctly detects mtds, I get: 0x001c-0x001416a4 : linux 0x001416a4-0x007ba000 : rootfs # cat /proc/mtd dev:size erasesize name mtd0: 001e boot mtd1: 0001 board_data mtd2: 0001 nvram mtd3: 00141688 0002 linux mtd4: 0067895c 0002 rootfs So the mtd I'm interested in is mtd4. # head /dev/mtd4 | hexdump -C 73 68 73 71 2b 03 00 00 00 00 00 54 03 00 00 d8 |shsq+..T| # head /dev/mtdblock4 | hexdump -C head: /: Input/output error 3d 3d 3e 20 2f 20 3c 3d 3d 0a 0a 3d 3d 3e 20 64 |== / ==..== d| 0010 65 76 2f 6d 74 64 62 6c 6f 63 6b 34 20 3c 3d 3d |ev/mtdblock4 ==| 0020 0a 73 68 73 71 2b 03 00 00 00 00 00 54 03 00 00 |.shsq+..T...| Again... # head /dev/mtdblock4 | hexdump -C 73 68 73 71 2b 03 00 00 00 00 00 54 03 00 00 d8 |shsq+..T| Now the most interesting part: # mount -t squashfs /dev/mtdblock4 /mnt/ mount: mounting /dev/mtdblock4 on /mnt/ failed: Invalid argument Can someone explain to me, what does it mean? Is there something wrong with my mtdblock4? I don't get anything interesting in dmesg. Is that possible squashfs used by original firmware is somehow malformed and requires original-vendor-hacked squashfs support? -- Rafał ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Unable to mount squashfs, no real error returned (Invalid argument)
Hi Rafał, On 24 August 2012 23:09, Rafał Miłecki zaj...@gmail.com wrote: (...) # head /dev/mtd4 | hexdump -C 73 68 73 71 2b 03 00 00 00 00 00 54 03 00 00 d8 |shsq+..T| (...) Can someone explain to me, what does it mean? Is there something wrong with my mtdblock4? I don't get anything interesting in dmesg. The problem is that Broadcom uses its own squashfs with lzma-magic. The standard squashfs magic is sqsh or hsqs (depending on endianess), and Broadcom chose to use a different one (since squashfs3 does not support storing the compressor type). There is a patch adding support for unsquashfs in the repo (so you should be able to just throw a copy of the image at it), but the in-kernel squashfs only accepts standard squashfs magics. Jonas ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Unable to mount squashfs, no real error returned (Invalid argument)
2012/8/24 Jonas Gorski jonas.gorski+open...@gmail.com: Hi Rafał, On 24 August 2012 23:09, Rafał Miłecki zaj...@gmail.com wrote: (...) # head /dev/mtd4 | hexdump -C 73 68 73 71 2b 03 00 00 00 00 00 54 03 00 00 d8 |shsq+..T| (...) Can someone explain to me, what does it mean? Is there something wrong with my mtdblock4? I don't get anything interesting in dmesg. The problem is that Broadcom uses its own squashfs with lzma-magic. The standard squashfs magic is sqsh or hsqs (depending on endianess), and Broadcom chose to use a different one (since squashfs3 does not support storing the compressor type). There is a patch adding support for unsquashfs in the repo (so you should be able to just throw a copy of the image at it), but the in-kernel squashfs only accepts standard squashfs magics. Ah, OK, thanks a lot! I've managed to track where mounting fails. It's fs/squashfs/super.c::squashfs_fill_super. As you said, it fails at: if (sb-s_magic != SQUASHFS_MAGIC) Unfortunately error wasn't displayed to me, because flag MS_SILENT was set. Backtrace after I put WARN_ON(1): [ 33.984000] [ cut here ] [ 33.988000] WARNING: at fs/squashfs/super.c:126 squashfs_fill_super+0x1a0/0x84c() [ 33.996000] Modules linked in: [ 34.00] Call Trace: [ 34.004000] [8025ce80] dump_stack+0x8/0x34 [ 34.008000] [80023780] warn_slowpath_common+0x78/0xa4 [ 34.012000] [800237c4] warn_slowpath_null+0x18/0x24 [ 34.016000] [80103640] squashfs_fill_super+0x1a0/0x84c [ 34.024000] [800a7c0c] mount_bdev+0x14c/0x1cc [ 34.028000] [801033b0] squashfs_mount+0x18/0x24 [ 34.032000] [800a856c] mount_fs+0x20/0xe4 [ 34.036000] [800bfaf4] vfs_kern_mount+0x64/0xe8 [ 34.04] [800bfda0] do_kern_mount+0x48/0xf4 [ 34.048000] [800c1cc0] do_mount+0x67c/0x6fc [ 34.052000] [800c1dcc] sys_mount+0x8c/0xf0 [ 34.056000] [8000d1d0] stack_done+0x20/0x40 [ 34.06] [ 34.06] ---[ end trace 088bd3492332a7b0 ]--- -- Rafał ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Time Division Multiple Access (TDMA)
i have interesting. 2012/8/22 Adrian Chadd adr...@freebsd.org On 13 July 2012 06:24, Jonathan Bither jonbit...@gmail.com wrote: Nico, I too have been interested in experimenting with TDMA. When I looked a while ago the most helpful information that I saw was that TDMA support is apparently included in freebsd. You may want to take a look at how it is implemented over there. http://fxr.watson.org/fxr/source/net80211/ieee80211_tdma.c I'm about to start working out the kinks. It broke some time after FreeBSD-7.x. Luckily I have all of the pre-11n atheros hardware here so I can setup a working environment and then figure out which commits/changes broke things. I'll post updates to FreeBSD-wireless once I figure it out. Thanks, Adrian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel -- DDNAS系列！ http://ddnas.openmobilefree.net/ adam.huang ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] EP93xx compile problem
Folks, Not sure how to resolve this: while compiling mklibs, got the following: make[7]: Entering directory `/var/storage/src/trunk-arm/build_dir/host/mklibs/src/mklibs-readelf' x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I../.. -O2 -I/var/storage/src/trunk-arm/staging_dir/host/include -I/var/storage/src/trunk-arm/tools/mklibs/include -g -O2 -MT elf.o -MD -MP -MF .deps/elf.Tpo -c -o elf.o elf.cpp elf.cpp: In static member function 'static Elf::file* Elf::file::open(const char*)': elf.cpp:68:5: error: '::close' has not been declared make[7]: *** [elf.o] Error 1 any ideas how to fix? Thanx, David A. Bandel -- Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe. -- Albert Einstein Visit my web page at: http://david.bandel.us/ ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
