Re: [LEDE-DEV] Failed to execute /usr/libexec/login.sh
On 16-05-11 06:08 PM, Alexey Brodkin wrote: > Hi Daniel, > > > breaks something for my boards (in particular arc770-based boards). > I'm unable to activate console now. That's what I'm getting > every time I press ENTER: > ->8- > Failed to execute /usr/libexec/login.sh > Please press Enter to activate this console. > Failed to execute /usr/libexec/login.sh > Please press Enter to activate this console. In your build tree build_dir/target-/root- can you verify bin/login bin/ash bin/sh all exist (they should be symlinks to busybox in bin/busybox which should also exist). also can you verify /usr/libexed/login.sh is exectuable? ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Failed to execute /usr/libexec/login.sh
On 16-05-11 06:08 PM, Alexey Brodkin wrote: > Hi Daniel, > > Looks like one recent commit: [snip] > > breaks something for my boards (in particular arc770-based boards). > I'm unable to activate console now. That's what I'm getting > every time I press ENTER: > ->8- > Failed to execute /usr/libexec/login.sh > Please press Enter to activate this console. > Failed to execute /usr/libexec/login.sh > Please press Enter to activate this console. > ->8- > > If I revert mentioned commit problem goes away. > > Any thoughts on what might be wrong here? > Probably something is missing in my board's init scripts etc? Hi, I will have to dig into the actual commit (it was modified from the patch I sent, so I have to review the details, to see if it's related to the changes, or something special about that board). Regards, Daniel ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] Maintaining LuCI
Hi All, Long time lurker, have a few out of tree patches mostly backporting stuff to older kernels... Question being: Is LuCI going to be maintained in LEDE? Or will some cheaper web front-end return similar to what these projects used to have? Reason being I feel OpenWRT has betrayed the community with their lua frontend by abandoning all of these older devices because of this architectural decision to go with a fancy web-frontend leaving most of the strict wireless G devices behind (looking at my WRT54GL, wl-520gu, etc). LuCI's great, but if you need an expensive device (I've since moved to the RT-N16, RT-N53, TL-WDR3600 and now the R7000) that kind of defeats the entire purpose of the project. Mainline, current, support for these devices is really my only goal. Any feedback would be absolutely appreciated. Kyle. ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Wiki for LEDE Project
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Bring it up at the next meeting? Who can edit the meeting agenda? -BEGIN PGP SIGNATURE- Version: APG v1.1.1 iQJRBAEBCgA7BQJXM+DONBxLdXNoYWwgSGFkYSAoZGV2ZWxvcGVyKSA8a3VzaGFs ZGV2ZWxvcGVyQGdtYWlsLmNvbT4ACgkQJsInd2b1xmOD1BAAtKDluafigaFg21VK 353YBoDfh2qjrCDIJ8MfAY4MuxsmENs7EW3n7BkIxYlYlopz7bgwvqsgrvM5CpuD kmnPavEI5CwLevF6rGPVG8zxXUEv67ql6OuYXf7vulaFzT924MPR+7jq3lZA1fo9 R5UUHAux5jfuwqAxg+9AtTWjhfnvl9hWoja9uS283t+O7D4H+nHc9F3Gng9Qr9lI jDfaiuof68TWJkc9E7DWguwrX4eBA9bnT9cEi684GKqVyLjj2OX5Vr5F5m44i1Vi Fac39x02c3O97qIGTLGH2CPqGd6ZSblIhjYb04L6xYSRt0KLPKIitzMN/HWhRwAR FqgO5IYro4/fmjMMMPBQ2XWVTxk6HyY60ht5JNqc/CPKtEHPXRMksMSubcJ8k/+Z SWBow+tWOcpVQuMMud4Rx7daPX9mWnmXEjHpMqznY/QKuAnaT9eViNwFQlf+GT7v sE8ot2PgfxI+D5Pi+4ic14Fk+pgiVSOPqhwYim/rphSNo+/WScIhLLSVczYFF9jY LX1NfnJTHG/I6Vb6v6CRWQ2ob84xLWx2dVdj8xIetse1hbIqPrAe8cyULxuNDgSQ VErXMe/kx/N38VyeGQ2NB6IuvSXkcqfjas9cj0KUnS8otARC+VbuY14KUKxXeLy1 OxJAalfc3ezb+LmNFHg+38PFymA= =8Tpa -END PGP SIGNATURE- ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Wiki for LEDE Project
Has anyone got this message at all ? Or it seems this topic isn't that important or necessary. Who is the person in charge of the infrastructure stuff for the project ? Fernando On 6 May 2016 at 00:25, Fernando Frediani wrote: > So is this on the list to be done ? > I am putting myself available to deploy, configure and perhaps add and > move some content into it. > If it´s the case whoever is looking after the infrastructure stuff may > contact me in private for arrangements. > > Thanks > Fernando > > On 5 May 2016 at 01:08, Kus wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA512 >> >> I love this idea. A wiki with pages for each router :D and people who have >> that particular machine can come in and write about the quirks about it. It >> will be great! >> -BEGIN PGP SIGNATURE- >> Version: APG v1.1.1 >> >> iQJRBAEBCgA7BQJXKscxNBxLdXNoYWwgSGFkYSAoZGV2ZWxvcGVyKSA8a3VzaGFs >> ZGV2ZWxvcGVyQGdtYWlsLmNvbT4ACgkQJsInd2b1xmOJgRAAplga7CkiFZm3XRs4 >> QMZBTedexBjNtEN5yabgv1y7CtMjd/1qQPRtZcxA7LmTkd4FJo/kW0EdoEmeYwWU >> cMP9Cty7VlGxBOuG3BESaDaOw54Rg4g7FHooXL653JrYSMOGDHvLAEbREY9FfV++ >> YX8PrfRYC+QYGBKPy13Zsrjk/M54sbpBBZbUFdCHYvFFMq7+iN3UTACb4xRJNgyr >> Dn1GD1zinhEGxVKZK6HBCGmXE2PJ9vtnOBRSR6WQo82Qjv7aQ7M6kWPL2vWDOyls >> 1RQa9eEH6qEHLJomHy64W3xcS94zVLg6//FG3fLC81S72xYgLKP3/Q0/T9qdaqzZ >> XwXZleKVKUEKbHlaZwN0gOn1iKSidBUkyFbcVBDLI1JE9UYUfm/qzhdY9Y98XZxh >> dgSNvLUhFmD+LvZosk1D3NRztOrytyhsAMNQ7dDqNtpdUL7UGMnKKJyQ7ft7/3dO >> 5ohlKKma5botXCoQcvxFXT/A6Ze03VVmqe7BbK3EQpbVqGdh8UFwHzZKc5H4RDUJ >> FT1aMlPLLE3b8CeTwEZLtlPrWPzLwTbXWHAZKYT9rNr5NSJz+/JdX6z48WbTI/Te >> jo0yQp0e3I6RoiliQ/pRhhrHS7SX6TrwhJKd+OQMuna5ciCukGUwsvZP1FoX8WJQ >> zXsgUD39qWF4INsEZ3olgmWXpSg= >> =DjaD >> -END PGP SIGNATURE- >> ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Wiki for LEDE Project
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 David, perhaps we can apply templates based on category? And then add or remove individual items to and from categories as things change? Just a thought. -BEGIN PGP SIGNATURE- Version: APG v1.1.1 iQJRBAEBCgA7BQJXM9fkNBxLdXNoYWwgSGFkYSAoZGV2ZWxvcGVyKSA8a3VzaGFs ZGV2ZWxvcGVyQGdtYWlsLmNvbT4ACgkQJsInd2b1xmOlNRAAkUkdh6WBHUZOLyda 5umiN0A0bQdXbWCP58ipjRe4oS1rQI79MbxNxSyCCNy2dOPUIXLyb01+BbpywbPl ZG5yJUXUGmsmnR5xIfgEY/U6P/HqaVSDgdrDzce9EGfgzBznxU68PzDn8WKq6iyR XWRu+gAbYgsaUydo6wkLsyg3pJkxAGgbEqTNdW6grNBptYQZOONL8ULS+0/o+T7d 8M8b4I219ivioN8c5evIjLFh8lFarvXOjv5cpMCHaWP8dN0zmKYoDvWYXm8U6iHP kmvR6rsiDeB3yqFj50Dp/uj3wDS+WkOBF4pNLUl74VeiWB3kpz+lkLAF9IZZbxqL HVQqm+05vqkL1tRGPcAKkIkAPXhNXvf9iOBjWurqhl4/UGGFNOTUoK3PIi3ue/Yz gm7MTeZy8/fTsOSGW21I+60xFO4GeZSnjB5fJjjp8J9NRGZYcEVuo+EC3NCfPp4H dmftd/NNJ5GWrsVeoDAvnRPxRRFEhidD15MGWIMOzKhxmmScQg43MT5zxuQkzqyU /BUcn6WQ+qa51gvNoX5I0rt04xz8yjua4+BEySL9jteZDXDAzII20WbQdUxgpVxb WGXvVcdS18GrJQd3mefAWo5CQeunQgiscp+ZNEdJfbkIMJj/cHyR9qqmlANfUr37 dndHlBGJmxMUZ9/2T5aMA/2HRcQ= =JsKE -END PGP SIGNATURE- ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Wiki for LEDE Project
On Thu, 5 May 2016, Kus wrote: I love this idea. A wiki with pages for each router :D and people who have that particular machine can come in and write about the quirks about it. It will be great! One thing that just came up on the wrt1900 support forum as we were talking about cleaning up the several pages for related routers. There is a lot of data that is critically important early on in the process, or when working to fix things when they are broken, that is not useful once the device is supported and everything is working fairly well. A lot of this information is also common across many different devices from the same manufacturer, but with different wiki pages there is a tendency to have some pages with the info, some without, and some with different versions of it. As such, I'd like to throw out the idea that this sort of info not be stored directly on the wiki page for each device, but instead be stored off in some out-of-the way hierarchy and referenced by the relavent pages. For example debricking processes flashing via serial flashing via bootp flashing via ftp tend to be the same for all devices from a given manufacturer (at least for everything manufactured within a given timeframe) Also bootlogs serial port pinouts (with pictures) tend to be critical early on, but almost never used after the support is solid. Other things to consider switch port assignments (for things like the wrt1900ac that have non-trivial port configs out of the box) thoughts? David Lang ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Script to gather system info for bug reports and similar.
On Wed, 11 May 2016, Bruno Randolf wrote: On 10/05/16 21:00, Ben Greear wrote: Here is an initial pass at a script to gather pertinent info about a LEDE (or similar) system. Suggestions for improvement are welcome. If someone could add a way to put the git commit ID(s) into the file system somewhere, I think that would be an excellent addition. And once the script is in place, a way to call it through the web UI would be most welcome. Some of these commands could be replaced by ubus calls. The benefit of this is could be that we get it structured as JSON so it's easier to parse and easy to upload to a webservice (e.g. for submitting test results or bug reports). I like, however I am a little concerned about leaking authentication info. Especially if you have more 'interesting' configs. I understand the need to have the basic interface config info, but do we really need the IP details and routing info? I can see some cases where they would matter, but most of the time they don't. I'm not arguing for security by obscurity, but I am willing to argue against providing info to attackers instead of making them work a little for it :-) David Lang ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] Failed to execute /usr/libexec/login.sh
Hi Daniel, Looks like one recent commit: ->8- commit a1860283b37c7a26f78c7387227a42219e8b4d4d Author: luka Date: Tue May 10 22:36:25 2016 + image / basefiles: make console password configurable Signed-off-by: Daniel Dickinson Signed-off-by: John Crispin git-svn-id: svn://svn.openwrt.org/openwrt/trunk@49325 3c298f89-4303-0410-b956-a3cf2f4a3e73 ->8- breaks something for my boards (in particular arc770-based boards). I'm unable to activate console now. That's what I'm getting every time I press ENTER: ->8- Failed to execute /usr/libexec/login.sh Please press Enter to activate this console. Failed to execute /usr/libexec/login.sh Please press Enter to activate this console. ->8- If I revert mentioned commit problem goes away. Any thoughts on what might be wrong here? Probably something is missing in my board's init scripts etc? -Alexey ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] tp-link archer c7 & cake & mac80211 fq_codel
looks like it can be easily flashed once again as 49217... https://wiki.openwrt.org/toh/tp-link/archer-c5-c7-wdr7500 but Arokh's comprehensive build (which includes sch_cake): https://forum.openwrt.org/viewtopic.php?id=50914 is a bit out of date... so I guess I should try lede for the first time via https://downloads.lede-project.org/snapshots/targets/ar71xx/generic/ and try cross compiling sch_cake for it. ... and if I feel really, really, really, really ambitious, try backporting one of michals lovely patchsets to 4.4. http://blog.cerowrt.org/post/fq_codel_on_ath10k/ https://github.com/kazikcz/linux/tree/fqmac-v4+dqlrfc+cpuregrfix But I don't feel that ambitious. It *will* be good to blow the dust off of the tp-link that made me go to Washington... here goes... -- Dave Täht Let's go make home routers and wifi faster! With better software! http://blog.cerowrt.org ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] What has been your experience with coverity?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Question to older members: What has been your experience with coverity and openwrt? Was it useful to you in the past? Is this something that we would like to continue to do going forward? Sincerely, -BEGIN PGP SIGNATURE- Version: APG v1.1.1 iQJRBAEBCgA7BQJXM6bCNBxLdXNoYWwgSGFkYSAoZGV2ZWxvcGVyKSA8a3VzaGFs ZGV2ZWxvcGVyQGdtYWlsLmNvbT4ACgkQJsInd2b1xmP7iQ/8D9XLiF+DAqlg8zp0 tGi26LACKywsGTRyGd+XH0fzTs3hCRUrujd4f5Iuzi7oSewNu2mWYBFHhizecM/5 5T4CXK3kRRhj6Z5/bpGgC5Gx1wNJ4T6pNfI6FlgBTHPTjrAXfqS286/Wgsi2ivpN rfSqexF8a2/dYXzvoiobsJcMs7Tcb8COl3VaWfR9XbihQQCzogRyAnW2s4+VcfRz SG69IvTlsJKP4EstzJkwYAY7t9wVAltHUeQFp9gaCd59BrfTQ+5vLsSsdO/OHS2l MtQM7o6eHuJtW1emG/OtiRITU0zY0Ifv9bprSqIpHXo1mpTo29GTUUOes/pAUYMP xmMZqJP+0yJIjexljYiQ8pAtddbZDg0uRS+yIt22+5FHOtT87kkO0fqKoaWfFI0t /Y82c8CD+1fTgCv7Edtv/dxpIB4TeVh8mu5ZRf/XcxV0Tpg8k3THCs7f9JSJFYr8 /VDVVbADI+cJhu9jEPPs5GXdLKv6OFiC6Wr6EZ9DpTAm8EdfZb7umGfqGD/UM0SF MIRddnPkHY8jB1hlcIT1dVq1z/fzziTmmyxLH0vCR12qziHJ0Ra0HBeCClo1hTu6 Qw7IW4SYN5j2fyYkO3WXRlW2ETVYgV4X3WgoGAp0loMI/uizFOPvvQ06ia5KvAAY TLu6dMURC7k+2TYhNux+MqugHIg= =NGLi -END PGP SIGNATURE- ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] raising rsync bwlimit ? was: LEDE mirror from RCS&RDS Romania
On Wed, 2016-05-11 at 02:17 +0300, Daniel Petre wrote: > On 05/06/2016 12:41 PM, Daniel Petre wrote: > > Hello, so per jow's last night's info i have rsynced the downloads part > > from LEDE to the RCS&RDS ( www.rcs-rds.ro ) mirroring server: > > > > http://mirrors.linux.ro/lede/ > > > > Two more questions please: > > > > 1. How often can we rsync? > > Seems i cannot resync so often since the original point has insufficient > bandwidth so far.. > I will try again when LEDE has a better connection, until then i will > rsync daily. Hi, I noticed rsync is about 750 kbyte/s whereas wget (on the same file) gets > 20 Mbyte/s so I assume there's a bwlimit on the rsync server that is not there on the web server, and that LEDE has a good connection. If I'm right I think it would be better to raise the rsync bwlimit. Sincerely, Laurent PS: thanks for having listed the mirrors :) https://www.lede-project.org/downloads.html We have now enabled rsync in addition to WWW. ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Script to gather system info for bug reports and similar.
On 05/11/2016 01:14 AM, Hannu Nyman wrote: On 10/05/16 21:00, Ben Greear wrote: If someone could add a way to put the git commit ID(s) into the file system somewhere, I think that would be an excellent addition. And once the script is in place, a way to call it through the web UI would be most welcome. I use the following script to fetch the basic version info, compilation time, commit info of the main source and three feeds, and to store that as a custom file into the built firmware: That looks good to me...maybe send a patch to include it for upstream, and logic to call it at build-time automatically? Thanks, Ben #!/bin/bash STATUSFILE=files/etc/Compile_info.txt OwVers=`grep RELEASE: include/toplevel.mk | cut -d "=" -f 2` echo LEDE $OwVers `scripts/getver.sh` / `date "+%F %H:%M"` > $STATUSFILE echo "---" >> $STATUSFILE echo "main "`(git show --format="%cd %h %s" --date=short | head -n 1 | cut -b1-60)` >> $STATUSFILE echo "luci "`(cd feeds/luci && git show --format="%cd %h %s" --date=short | head -n 1 | cut -b1-60)` >> $STATUSFILE echo "packages "`(cd feeds/packages && git show --format="%cd %h %s" --date=short | head -n 1 | cut -b1-60)` >> $STATUSFILE echo "routing "`(cd feeds/routing && git show --format="%cd %h %s" --date=short | head -n 1 | cut -b1-60)` >> $STATUSFILE That produces the following output for files/etc/Compile_info.txt (/etc/Compile_info.txt in the live router): LEDE Designated Driver r153 / 2016-05-11 11:06 --- main 2016-05-11 30d955a build: fix make clean, delete package dir luci 2016-05-10 650c031 Merge pull request #717 from Umeaboy/patc packages 2016-05-11 2339a82 libffi: bump to version 3.2.1 routing 2016-05-10 bec38bf Merge pull request #186 from stintel/bird ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev -- Ben Greear Candela Technologies Inc http://www.candelatech.com ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Script to gather system info for bug reports and similar.
On 05/11/2016 01:02 AM, Bruno Randolf wrote: On 10/05/16 21:00, Ben Greear wrote: Here is an initial pass at a script to gather pertinent info about a LEDE (or similar) system. Suggestions for improvement are welcome. If someone could add a way to put the git commit ID(s) into the file system somewhere, I think that would be an excellent addition. And once the script is in place, a way to call it through the web UI would be most welcome. Some of these commands could be replaced by ubus calls. The benefit of this is could be that we get it structured as JSON so it's easier to parse and easy to upload to a webservice (e.g. for submitting test results or bug reports). That looks good to me, though maybe include some of the more normal unix command output as well for humans reading the bug report. I don't know much about the LEDE build and package system..what is the best way to add this script to the system? Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH v2 01/10] include/image.mk: Add TP-Link image safe-loader defintion
> diff --git a/include/image.mk b/include/image.mk > index 9e342e0..aa12052 100644 > --- a/include/image.mk > +++ b/include/image.mk > @@ -325,6 +325,18 @@ define Build/netgear-dni > mv $@.new $@ > endef > > +define Build/tplink-safeloader Can you also remove the other version in target/linux/ar71xx/image/Makefile? best, lynxis -- Alexander Couzens mail: lyn...@fe80.eu jabber: lyn...@fe80.eu mobile: +4915123277221 gpg: 390D CF78 8BF9 AA50 4F8F F1E2 C29E 9DA6 A0DF 8604 pgparN58B2XQr.pgp Description: OpenPGP digital signature ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Cannot compile latest code.
On 2016-05-11 16:34, Dirk Neukirchen wrote: > Package dmesg is missing dependencies for the following libraries: > libtinfow.so.5 > > This happens with several other packages now with: > staging_dir/target-../usr/lib/libtinfow.so.5: error adding symbols: DSO > missing from command line > - fixing can involve adding LIBS="-ltinfo" to CONFIGURE_VARS (seems to > compile) or more > elaborate manipulation and patching of package build systems (to use > ncurses-config) Please try a clean build from the latest version - Felix ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Cannot compile latest code.
Package dmesg is missing dependencies for the following libraries: libtinfow.so.5 This happens with several other packages now with: staging_dir/target-../usr/lib/libtinfow.so.5: error adding symbols: DSO missing from command line - fixing can involve adding LIBS="-ltinfo" to CONFIGURE_VARS (seems to compile) or more elaborate manipulation and patching of package build systems (to use ncurses-config) diff --git a/package/utils/util-linux/Makefile b/package/utils/util-linux/Makefile index c128b48..8ee7c35 100644 --- a/package/utils/util-linux/Makefile +++ b/package/utils/util-linux/Makefile @@ -202,7 +202,7 @@ endef define Package/dmesg $(call Package/util-linux/Default) TITLE:=print or control the kernel ring buffer - DEPENDS:= +librt + DEPENDS:= +librt +libncursesw endef define Package/dmesg/description @@ -212,7 +212,7 @@ endef define Package/fdisk $(call Package/util-linux/Default) TITLE:=manipulate disk partition table - DEPENDS:= +libblkid +libsmartcols +libfdisk + DEPENDS:= +libblkid +libsmartcols +libfdisk +libncursesw SUBMENU=disc endef ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Script to gather system info for bug reports and similar.
On 10/05/16 21:00, Ben Greear wrote: If someone could add a way to put the git commit ID(s) into the file system somewhere, I think that would be an excellent addition. And once the script is in place, a way to call it through the web UI would be most welcome. I use the following script to fetch the basic version info, compilation time, commit info of the main source and three feeds, and to store that as a custom file into the built firmware: #!/bin/bash STATUSFILE=files/etc/Compile_info.txt OwVers=`grep RELEASE: include/toplevel.mk | cut -d "=" -f 2` echo LEDE $OwVers `scripts/getver.sh` / `date "+%F %H:%M"` > $STATUSFILE echo "---" >> $STATUSFILE echo "main "`(git show --format="%cd %h %s" --date=short | head -n 1 | cut -b1-60)` >> $STATUSFILE echo "luci "`(cd feeds/luci && git show --format="%cd %h %s" --date=short | head -n 1 | cut -b1-60)` >> $STATUSFILE echo "packages "`(cd feeds/packages && git show --format="%cd %h %s" --date=short | head -n 1 | cut -b1-60)` >> $STATUSFILE echo "routing "`(cd feeds/routing && git show --format="%cd %h %s" --date=short | head -n 1 | cut -b1-60)` >> $STATUSFILE That produces the following output for files/etc/Compile_info.txt (/etc/Compile_info.txt in the live router): LEDE Designated Driver r153 / 2016-05-11 11:06 --- main 2016-05-11 30d955a build: fix make clean, delete package dir luci 2016-05-10 650c031 Merge pull request #717 from Umeaboy/patc packages 2016-05-11 2339a82 libffi: bump to version 3.2.1 routing 2016-05-10 bec38bf Merge pull request #186 from stintel/bird ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Script to gather system info for bug reports and similar.
Hi Ben, Richard had created someting similar salready: https://github.com/richb-hanover/OpenWrtScripts/blob/master/getstats.sh which we occasionally used to debug/help sqm users with, maybe it contains some useful pointers… Best Regards M. > On May 10, 2016, at 22:00 , Ben Greear wrote: > > Here is an initial pass at a script to gather pertinent info about > a LEDE (or similar) system. Suggestions for improvement are welcome. > > If someone could add a way to put the git commit ID(s) into > the file system somewhere, I think that would be an excellent > addition. > > And once the script is in place, a way to call it through the web UI would > be most welcome. > > [root@ben-dt3 linux-wt.x64]# cat ~/verinfo.sh > #!/bin/sh > > echo "System Information" > uname -a > echo > echo "lspci:" > lspci > echo > echo "CPU Info" > cat /proc/cpuinfo > echo > echo "Banner:" > cat /etc/banner > echo > echo "Network Devices:" > ip addr show > echo > echo "Routing information:" > ip route show > echo > echo "Qdisc information:" > tc qdisc show > echo > echo "WiFi Information" > if [ -f /sys/class/net/wlan0/address ] > then > iw dev wlan0 info > fi > if [ -f /sys/class/net/wlan1/address ] > then >iw dev wlan1 info > fi > > echo > echo "dmesg output" > dmesg > > -- > Ben Greear > Candela Technologies Inc http://www.candelatech.com > > > ___ > Lede-dev mailing list > Lede-dev@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/lede-dev ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Script to gather system info for bug reports and similar.
On 10/05/16 21:00, Ben Greear wrote:
> Here is an initial pass at a script to gather pertinent info about
> a LEDE (or similar) system. Suggestions for improvement are welcome.
>
> If someone could add a way to put the git commit ID(s) into
> the file system somewhere, I think that would be an excellent
> addition.
>
> And once the script is in place, a way to call it through the web UI would
> be most welcome.
Some of these commands could be replaced by ubus calls. The benefit of
this is could be that we get it structured as JSON so it's easier to
parse and easy to upload to a webservice (e.g. for submitting test
results or bug reports).
> [root@ben-dt3 linux-wt.x64]# cat ~/verinfo.sh
> #!/bin/sh
>
> echo "System Information"
> uname -a
> echo
> echo "lspci:"
> lspci
No ubus equivalent yet.
lsusb would also be interesting.
> echo
> echo "CPU Info"
> cat /proc/cpuinfo
> echo
> echo "Banner:"
> cat /etc/banner
> echo
root@Rpi2:~# ubus call system board
{
"kernel": "3.18.29",
"hostname": "Rpi2",
"system": "ARMv7 Processor rev 5 (v7l)",
"model": "Raspberry Pi 2",
"release": {
"distribution": "OpenWrt",
"version": "Chaos Calmer",
"revision": "2016-04-21-140-ge1357c0",
"codename": "chaos_calmer",
"target": "brcm2708\/bcm2709",
"description": "OpenWrt Chaos Calmer
2016-04-21-140-ge1357c0"
}
}
root@Rpi2:~# ubus call system info
{
"uptime": 60,
"localtime": 1462952915,
"load": [
31264,
10560,
3648
],
"memory": {
"total": 976216064,
"free": 937431040,
"shared": 73728,
"buffered": 884736
},
"swap": {
"total": 0,
"free": 0
}
}
> echo "Network Devices:"
> ip addr show
> echo
root@Rpi2:~# ubus call network.device status
{
"eth0": {
"external": false,
"present": true,
"type": "Network device",
"up": true,
"carrier": true,
"link-advertising": [
"10H",
"10F",
"100H",
"100F"
],
"link-supported": [
"10H",
"10F",
"100H",
"100F"
],
"speed": "100F",
"mtu": 1500,
"mtu6": 1500,
"macaddr": "b8:27:eb:bb:b3:40",
"txqueuelen": 1000,
"ipv6": true,
"promisc": false,
"rpfilter": 0,
"acceptlocal": false,
"igmpversion": 0,
"mldversion": 0,
"neigh4reachabletime": 3,
"neigh6reachabletime": 3,
"dadtransmits": 1,
"statistics": {
"collisions": 0,
"rx_frame_errors": 0,
"tx_compressed": 0,
"multicast": 0,
"rx_length_errors": 0,
"tx_dropped": 0,
"rx_bytes": 433918,
"rx_missed_errors": 0,
"tx_errors": 0,
"rx_compressed": 0,
"rx_over_errors": 0,
"tx_fifo_errors": 0,
"rx_crc_errors": 0,
"rx_packets": 979,
"tx_heartbeat_errors": 0,
"rx_dropped": 0,
"tx_aborted_errors": 0,
"tx_packets": 1688,
"rx_errors": 0,
"tx_bytes": 388341,
"tx_window_errors": 0,
"rx_fifo_errors": 0,
"tx_carrier_errors": 0
}
},
"lo": {
"external": false,
"present": true,
"type": "Network device",
"up": true,
"carrier": true,
"mtu": 65536,
"mtu6": 65536,
"macaddr": "00:00:00:00:00:00",
"txqueuelen": 0,
"ipv6": true,
"promisc": false,
"rpfilter": 0,
"acceptlocal": false,
"igmpversion": 0,
"mldversion": 0,
"neigh4reachabletime": 3,
"neigh6reachabletime": 3,
"dadtransmits": 1,
"statistics": {
"collisions": 0,
"rx_frame_errors": 0,
"tx_compressed": 0,
"multicast": 0,
[LEDE-DEV] [PATCH 2/2] ar71xx: Add support for Ubiquiti UniFi AP AC PRO
From: P.Wassi
Add support for the Ubiquiti UniFi AP AC PRO
Signed-off-by: P.Wassi
---
The UniFi AP AC PRO has a built in switch and therefore needs
different Ethernet initialisation/setup. The patch below addresses this
and brings support for the mentioned device.
base-files/etc/board.d/02_network |5 +
base-files/etc/diag.sh |3
base-files/etc/hotplug.d/firmware/11-ath10k-caldata |3
base-files/lib/ar71xx.sh|3
base-files/lib/upgrade/platform.sh |1
files/arch/mips/ath79/Kconfig.openwrt |3
files/arch/mips/ath79/mach-ubnt-unifiac.c | 69
files/arch/mips/ath79/machtypes.h |1
generic/profiles/ubnt.mk| 11 +++
image/Makefile |8 ++
10 files changed, 103 insertions(+), 4 deletions(-)
diff -rupN a/target/linux/ar71xx/base-files/etc/board.d/02_network
b/target/linux/ar71xx/base-files/etc/board.d/02_network
--- a/target/linux/ar71xx/base-files/etc/board.d/02_network
+++ b/target/linux/ar71xx/base-files/etc/board.d/02_network
@@ -418,6 +418,11 @@ wpj344)
"0@eth0" "3:lan" "2:wan"
;;
+unifiac-pro)
+ ucidef_add_switch "switch0" \
+ "0@eth0" "2:lan" "3:wan"
+ ;;
+
wpj531)
ucidef_set_interfaces_lan_wan "eth0" "eth1"
;;
diff -rupN a/target/linux/ar71xx/base-files/etc/diag.sh
b/target/linux/ar71xx/base-files/etc/diag.sh
--- a/target/linux/ar71xx/base-files/etc/diag.sh
+++ b/target/linux/ar71xx/base-files/etc/diag.sh
@@ -355,7 +355,8 @@ get_status_led() {
status_led="ubnt:green:dome"
;;
uap-pro | \
- unifiac-lite)
+ unifiac-lite | \
+ unifiac-pro)
status_led="ubnt:white:dome"
;;
unifi-outdoor-plus)
diff -rupN
a/target/linux/ar71xx/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
b/target/linux/ar71xx/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
--- a/target/linux/ar71xx/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
+++ b/target/linux/ar71xx/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
@@ -76,7 +76,8 @@ case "$FIRMWARE" in
ath10kcal_extract "ART" 20480 2116
ath10kcal_patch_mac $(macaddr_add $(cat
/sys/class/net/eth0/address) +16)
;;
- unifiac-lite)
+ unifiac-lite | \
+ unifiac-pro)
ath10kcal_extract "EEPROM" 20480 2116
;;
esac
diff -rupN a/target/linux/ar71xx/base-files/lib/ar71xx.sh
b/target/linux/ar71xx/base-files/lib/ar71xx.sh
--- a/target/linux/ar71xx/base-files/lib/ar71xx.sh
+++ b/target/linux/ar71xx/base-files/lib/ar71xx.sh
@@ -952,6 +952,9 @@ ar71xx_board_detect() {
*"UniFi-AC-LITE")
name="unifiac-lite"
;;
+ *"UniFi-AC-PRO")
+ name="unifiac-pro"
+ ;;
*"UniFi AP Pro")
name="uap-pro"
;;
diff -rupN a/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
b/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
--- a/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
+++ b/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
@@ -269,6 +269,7 @@ platform_check_image() {
nbg460n_550n_550nh | \
unifi | \
unifiac-lite | \
+ unifiac-pro | \
unifi-outdoor | \
carambola2 | \
weio )
diff -rupN a/target/linux/ar71xx/files/arch/mips/ath79/Kconfig.openwrt
b/target/linux/ar71xx/files/arch/mips/ath79/Kconfig.openwrt
--- a/target/linux/ar71xx/files/arch/mips/ath79/Kconfig.openwrt
+++ b/target/linux/ar71xx/files/arch/mips/ath79/Kconfig.openwrt
@@ -1442,7 +1442,7 @@ config ATH79_MACH_UBNT
select ATH79_DEV_USB
config ATH79_MACH_UBNT_UNIFIAC
- bool "Ubiquiti UniFi AC (LITE/LR) support"
+ bool "Ubiquiti UniFi AC (LITE/LR/PRO) support"
select SOC_QCA956X
select ATH79_DEV_AP9X_PCI if PCI
select ATH79_DEV_ETH
@@ -1450,6 +1450,7 @@ config ATH79_MACH_UBNT_UNIFIAC
select ATH79_DEV_LEDS_GPIO
select ATH79_DEV_M25P80
select ATH79_DEV_WMAC
+ select ATH79_DEV_USB
config ATH79_MACH_WEIO
bool "WeIO board"
diff -rupN a/target/linux/ar71xx/files/arch/mips/ath79/machtypes.h
b/target/linux/ar71xx/files/arch/mips/ath79/machtypes.h
--- a/target/linux/ar71xx/files/arch/mips/ath79/machtypes.h
+++ b/target/linux/ar71xx/files/arch/mips/ath79/machtypes.h
@@ -220,6 +220,7 @@ enum ath79_mach_type {
ATH79_MACH_UBNT_UAP_PRO,/* Ubiquiti UniFi AP Pro */
ATH79_MACH_UBNT_UNIFI, /* Ubiquiti Unifi */
ATH79_MACH_UBNT_UNIFIAC_LITE, /* Ubiquiti Unifi AC LITE/LR */
+ ATH79_MACH_UBNT_UNIFIAC_PRO,/* Ubiquiti Unifi AC PRO */
ATH79_MACH_UBNT_UNIFI_OUTDOOR, /* Ubiquiti UnifiAP Outdoor */
ATH79_MACH_UBN
[LEDE-DEV] [PATCH 1/2] ar71xx: Rename unifiac to unifiac-lite
From: P.Wassi
To avoid confusion with different unifiac devices, rename existing target
"unifiac" to "unifiac-lite", before "unifiac-pro" is introduced.
Signed-off-by: P.Wassi
---
base-files/etc/board.d/02_network |2 -
base-files/etc/diag.sh |2 -
base-files/etc/hotplug.d/firmware/11-ath10k-caldata |2 -
base-files/lib/ar71xx.sh|4 +--
base-files/lib/upgrade/platform.sh |2 -
files/arch/mips/ath79/Kconfig.openwrt |2 -
files/arch/mips/ath79/mach-ubnt-unifiac.c | 14 ++---
files/arch/mips/ath79/machtypes.h |2 -
generic/profiles/ubnt.mk| 10 -
image/Makefile | 21
10 files changed, 33 insertions(+), 28 deletions(-)
diff -rupN a/target/linux/ar71xx/base-files/etc/board.d/02_network
b/target/linux/ar71xx/base-files/etc/board.d/02_network
--- a/target/linux/ar71xx/base-files/etc/board.d/02_network
+++ b/target/linux/ar71xx/base-files/etc/board.d/02_network
@@ -368,7 +368,7 @@ tl-wa901nd-v3 |\
tl-wa901nd-v4 |\
tl-wr703n |\
tube2h |\
-unifiac |\
+unifiac-lite |\
wndap360 |\
mynet-rext |\
wp543)
diff -rupN a/target/linux/ar71xx/base-files/etc/diag.sh
b/target/linux/ar71xx/base-files/etc/diag.sh
--- a/target/linux/ar71xx/base-files/etc/diag.sh
+++ b/target/linux/ar71xx/base-files/etc/diag.sh
@@ -355,7 +355,7 @@ get_status_led() {
status_led="ubnt:green:dome"
;;
uap-pro | \
- unifiac)
+ unifiac-lite)
status_led="ubnt:white:dome"
;;
unifi-outdoor-plus)
diff -rupN
a/target/linux/ar71xx/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
b/target/linux/ar71xx/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
--- a/target/linux/ar71xx/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
+++ b/target/linux/ar71xx/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
@@ -76,7 +76,7 @@ case "$FIRMWARE" in
ath10kcal_extract "ART" 20480 2116
ath10kcal_patch_mac $(macaddr_add $(cat
/sys/class/net/eth0/address) +16)
;;
- unifiac)
+ unifiac-lite)
ath10kcal_extract "EEPROM" 20480 2116
;;
esac
diff -rupN a/target/linux/ar71xx/base-files/lib/ar71xx.sh
b/target/linux/ar71xx/base-files/lib/ar71xx.sh
--- a/target/linux/ar71xx/base-files/lib/ar71xx.sh
+++ b/target/linux/ar71xx/base-files/lib/ar71xx.sh
@@ -949,8 +949,8 @@ ar71xx_board_detect() {
*UniFi)
name="unifi"
;;
- *"UniFi-AC")
- name="unifiac"
+ *"UniFi-AC-LITE")
+ name="unifiac-lite"
;;
*"UniFi AP Pro")
name="uap-pro"
diff -rupN a/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
b/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
--- a/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
+++ b/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
@@ -268,7 +268,7 @@ platform_check_image() {
wlae-ag300n | \
nbg460n_550n_550nh | \
unifi | \
- unifiac | \
+ unifiac-lite | \
unifi-outdoor | \
carambola2 | \
weio )
diff -rupN a/target/linux/ar71xx/files/arch/mips/ath79/Kconfig.openwrt
b/target/linux/ar71xx/files/arch/mips/ath79/Kconfig.openwrt
--- a/target/linux/ar71xx/files/arch/mips/ath79/Kconfig.openwrt
+++ b/target/linux/ar71xx/files/arch/mips/ath79/Kconfig.openwrt
@@ -1442,7 +1442,7 @@ config ATH79_MACH_UBNT
select ATH79_DEV_USB
config ATH79_MACH_UBNT_UNIFIAC
- bool "Ubiquiti UniFi AC (LITE) support"
+ bool "Ubiquiti UniFi AC (LITE/LR) support"
select SOC_QCA956X
select ATH79_DEV_AP9X_PCI if PCI
select ATH79_DEV_ETH
diff -rupN a/target/linux/ar71xx/files/arch/mips/ath79/machtypes.h
b/target/linux/ar71xx/files/arch/mips/ath79/machtypes.h
--- a/target/linux/ar71xx/files/arch/mips/ath79/machtypes.h
+++ b/target/linux/ar71xx/files/arch/mips/ath79/machtypes.h
@@ -219,7 +219,7 @@ enum ath79_mach_type {
ATH79_MACH_UBNT_RS, /* Ubiquiti RouterStation */
ATH79_MACH_UBNT_UAP_PRO,/* Ubiquiti UniFi AP Pro */
ATH79_MACH_UBNT_UNIFI, /* Ubiquiti Unifi */
- ATH79_MACH_UBNT_UNIFIAC,/* Ubiquiti Unifi AC */
+ ATH79_MACH_UBNT_UNIFIAC_LITE, /* Ubiquiti Unifi AC LITE/LR */
ATH79_MACH_UBNT_UNIFI_OUTDOOR, /* Ubiquiti UnifiAP Outdoor */
ATH79_MACH_UBNT_UNIFI_OUTDOOR_PLUS, /* Ubiquiti UnifiAP Outdoor+ */
ATH79_MACH_UBNT_XM, /* Ubiquiti Networks XM board rev 1.0 */
diff -rupN a/target/linux/ar71xx/files/arch/mips/ath79/mach-ubnt-unifiac.c
b/target/linux/ar71xx/files/arch/mips/ath79/mach-ubnt-unifiac.c
--- a/target/linux/ar71xx/files/arch/mips/ath79/mach-ubnt-unifiac.c
+++ b/target/linux/ar71xx/
[LEDE-DEV] [PATCH 0/2] ar71xx: Add support for Ubiquiti UniFi AP AC PRO
Hi, the following patches bring support for the Ubiquiti UniFi AP AC PRO. It turned out that the PRO has a different Ethernet setup (built-in switch). Therefore, the existing image can not be used - a new target is required. First, the existing target "unifiac" is renamed to "unifiac-lite", then a new target "unifiac-pro" is introduced. These targets then support the following devices: "unifiac-lite" = UniFi AP AC LITE, UniFi AP AC LR (Longrange) "unifiac-pro" = UniFi AP AC PRO (and possibly also -EDU, which is not available yet) Best regards, P. Wassi ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
