Davidc502- wrt1200ac wrt1900acx wrt3200acm wrt32x builds

It hasn't happened to me in a while, but could happen at any time. Seems to very slowly be getting better over time.

Did you need to do something specific to get IOT's to work?

Disable WMM and revert to legacy b/g

1 Like

Does your browser accept the certificate from uHTTPd?

I don't think so? Does it work for anyone? I thought we were all just skipping it...

If the browser displays a certificate warning like in the screenshot,
photo_2019-07-10_09-17-26
Luci may not respond to page change and the only forced page refresh will help in this situation. You need to ensure the trust to certificate and then Luci will work correctly. Modern browsers, like IE and Chrome, require a certificate with a root certification authority, like one in the screenshot.
photo_2019-07-10_08-53-15
The root certificate should be added to the trusted ones. Opera may not have such strict requirements, but I don't use it. If you want to get such a self-signed certificate, I can make a small instruction.

Well the on-going PC build saga continues... Doesn't look like my new 3900x CPU will ship out until the 19th :).. Meaning I probably won't get it until the 22nd or 23rd.

It has been absolutely crazy just trying to get one on back-order. You would think with a roll-out of a new CPU AMD would have plenty in stock, but apparently they were not ready.

3 Likes

3900X is gonna be unbelievable for OpenWrt compiles. It took a $2,000 CPU to perform that kinda task as well just a year or two ago.

This article kind of sums it up. I'm going to be waiting a while.

EDIT

I just got an email and the processor just shipped out today, and I'll get it by end of day Saturday.

@ibex-are-goats - yes, please make a brief instructional. the openwrt docs seem needlessly conufusing.
thank yoi

Dear Dave,
All is well that ends well. Could not have happened to a nicer guy. And to quote Mark Twain : “Some of the worst things in my life never even happened” if you have some time for reading while you wait for your new PC / Processor - try this : http://mommyadventures.blogs.petaluma360.com/10019/“some-of-the-worst-things-in-my-life-never-even-happened”/
Peace

1 Like

Use this script
Original script here

  1. Edit script section "alt_names" for your router names and IP's
  2. Copy to router e.g., /tmp, check file permissions for execution, run script
    2.1. If error occurred, delete folder /tmp/tls and analyze errors
  3. Copy root cert /tmp/tls/ca.crt to PC/Smart/Tablet, add to trusted
  4. Сopy with replacement /tmp/tls/uhttpd.key and /tmp/tls/uhttpd.crt to /etc
  5. Restart uhttpd
2 Likes

Hi guys, I'm back!

Reinstalled Dave's build after 6 months of using the stock firmware ( don't even ask why :slight_smile: ) ... and ran again into the annoying error below when diagnosing that everything was being setup correctly with logread ...

@davidc502 and @eduperez, can you get to an agreement to compile the build with the kern.debug kernel messages debug output disabled ( as per the last message in this post https://github.com/kaloz/mwlwifi/issues/347 , it's enabled ) ?

Sat Jul 13 13:38:06 2019 kern.debug kernel: [ 6348.306568] ieee80211 phy1: Mac80211 start BA 74:8d:08:9f:95:4e
Sat Jul 13 13:38:06 2019 kern.debug kernel: [ 6348.366578] ieee80211 phy1: Mac80211 start BA 74:8d:08:9f:95:4e
Sat Jul 13 13:38:06 2019 kern.debug kernel: [ 6348.431198] ieee80211 phy1: Mac80211 start BA 74:8d:08:9f:95:4e
Sat Jul 13 13:38:06 2019 kern.debug kernel: [ 6348.486593] ieee80211 phy1: Mac80211 start BA 74:8d:08:9f:95:4e
Sat Jul 13 13:38:06 2019 kern.debug kernel: [ 6348.536556] ieee80211 phy1: Mac80211 start BA 74:8d:08:9f:95:4e
Sat Jul 13 13:38:06 2019 kern.debug kernel: [ 6348.637920] ieee80211 phy1: Mac80211 start BA 74:8d:08:9f:95:4e
Sat Jul 13 13:38:06 2019 kern.debug kernel: [ 6348.686500] ieee80211 phy1: Mac80211 start BA 74:8d:08:9f:95:4e
Sat Jul 13 13:38:06 2019 kern.debug kernel: [ 6348.746852] ieee80211 phy1: Mac80211 start BA 74:8d:08:9f:95:4e

Thanks in advance! The size and readability of our logs will appreciate it! :slight_smile:
Regards,
Mariano

Hi,
Just upgraded my already great r8373 to latest r10307 and so far so good.
Unfortunately I use ffmpeg with libffmeg-full to transcode the audio track of a video stream from MP2 to mp3 for my camera server and noticed that libffmpeg-full still has no SSL (https which is basically what every serious server uses now) support. I had to recompile it manually with openssl support AND libshine support (it's a mp3 encoder optimized for embedded systems with no float acceleration) but was a real pain cause I'm basically a newbie and took much time. So my request to DavidC: If it's not a issue can you enable openssl support and libshine for the whole ffmpeg package in the next-ish release?
Also I read somewhere that wrt3200acm has NEON acceleration support which if enabled should be great for transcoding. Is that true? If so can it be enabled somehow?

This is what I basically need (plus NEON support if possible should be amazing):

root@LEDE:~# ffmpeg 
ffmpeg version 3.2.10 Copyright (c) 2000-2018 the FFmpeg developers
  built with gcc 7.3.0 (OpenWrt GCC 7.3.0 r6880-aadca03)
  configuration: --enable-cross-compile --cross-prefix=arm-openwrt-linux-muslgnueabi- --arch=arm --target-os=linux --prefix=/usr --pkg-config=pkg-config --enable-shared --enable-static --enable-pthreads --enable-zlib --disable-doc --disable-debug --disable-lzma --disable-vaapi --disable-vdpau --disable-outdevs --disable-runtime-cpudetect --enable-lto --enable-vfp --disable-neon --disable-yasm --enable-avresample --enable-libopus --enable-small --enable-libmp3lame --enable-gpl --enable-libx264 --enable-libshine --enable-encoder=libshine --enable-openssl --enable-nonfree
  libavutil      55. 34.101 / 55. 34.101
  libavcodec     57. 64.101 / 57. 64.101
  libavformat    57. 56.101 / 57. 56.101
  libavdevice    57.  1.100 / 57.  1.100
  libavfilter     6. 65.100 /  6. 65.100
  libavresample   3.  1.  0 /  3.  1.  0
  libswscale      4.  2.100 /  4.  2.100
  libswresample   2.  3.100 /  2.  3.100
  libpostproc    54.  1.100 / 54.  1.100
Hyper fast Audio and Video encoder
usage: ffmpeg [options] [[infile options] -i infile]... {[outfile options] outfile}...

Regards and thanks for your amazing work.
Pino.

@puppinoo

I've searched the configuration up and down for ffmpeg-custom and doesn't exist. When I do a search for all available packages, according to it, ffmpgeg custom should be next to -mini and -full, but it doesn't exist. This may be a situation where another package has to be turned on before it shows up. However, I have no idea what that package would be. I'm still looking though.

I'm searching for -custom because it contains libshine and probably ssl support.

You need to patch the source of OpenWrt first to make the toolchain "neon aware", then you most likely want to get ffmpeg 4.X as 3.2 is "very old" by todays standards.

https://github.com/diizzyy/openwrt/commit/472fff28781a06305d6c6c34d59628dc3424bab7 (this will break compatibility with Armada XP platforms such as first gen of WRT1900AC.


Works but needs some tweaking due to changes in OpenWrt's toolchain, I'm slowly moving stuff to another distro so updates will most likely not be very frequent.

I did do a PR about it way back but I lost interest trying to convice people when there's little to no interest despite others also wanting this change and showing nice improvements. https://github.com/lede-project/source/pull/1211

Feel free to resubmit it if you want, I wish you the best of luck.

1 Like

You need to first turn ffmpeg-custom on under Libraries to be able to select; if you seach on the string, first turn on 2, then you should have 1 as being selectable. But as diizzy stated, without neon enabled its usage is questionable, but that breaks the mamba; but that is somewhat addressable by using the per-device rootfs functionality

That's what I was saying... I searched already by string and under libraries.

And then there is neon..........

The WRT3200ACM does have a SoC that supports NEON instructions (Armada 385) however neither (lib)shine or LAME uses it for encoding however ffmpeg does use it for resampling in some cases. If you're looking for performance you're probably better off using AAC which is available via the fdk-aac library.

Edit:
You'd also see quite a performance boost by just applying https://github.com/openwrt/openwrt/pull/1950 not to forget additionally enabling the optimization options for LAME (also available for fdk-aac).
https://github.com/openwrt/packages/pull/5048#issuecomment-341163032

2 Likes

Thanks a lot guys for trying. I'd send the .config I used to compile mine but it was a very dirty hack giving errors which I had to correct at every step and probably doesn't even work anymore. If it can be useful just let me know though. I have saved it just in case I need to recompile.

Pino.