Page 5 of 17

Re: Openwrt 19.07 based Gargoyle

Posted: Tue Oct 15, 2019 9:14 am
by boldga
I downloaded the client config zip file from another R7800 also flashed 1.13.x gargoyle and set as openvpn server.

BTW, I tried uncompress the zip file, and used "individual configuraton files" option, same error appeared.

the zip file seems OK, because I can upload it after flashing the R7800 back to 1.11.x from this post:
viewtopic.php?f=14&t=11988

Re: Openwrt 19.07 based Gargoyle

Posted: Sun Oct 27, 2019 7:31 am
by Lantis
I've fixed the openvpn config uploading today. Thanks for reporting it.

Re: Openwrt 19.07 based Gargoyle

Posted: Sun Oct 27, 2019 5:29 pm
by ispyisail
Do I need to switch to this repo?

I been waiting for Eric to push an official build

Re: Openwrt 19.07 based Gargoyle

Posted: Sun Oct 27, 2019 7:57 pm
by Lantis
I'll merge it into Eric's repo soon, but I won't merge it into master without his say so (as we agreed).
It's his call on whether to do releases or not. I will prompt him when I think it is ready.

It might be nice to start doing beta builds soon, but there's a bit to be checked with upgrading to it (particularly ar71xx devices that have moved to ath79)

Maybe wait until it shows up in Eric's repo then I'll let you know. Thanks mate.

Re: Openwrt 19.07 based Gargoyle

Posted: Fri Nov 08, 2019 8:33 pm
by Lantis
I've made a testing 1.13.x build available here:
https://lantisproject.com/gargoyle_custom/
Based on the 19.07-rc1 Openwrt tag.

This is still considered experimental, and not well tested beyond the devices that I personally own.
Please provide any feedback or concerns if you do decide to use it.

Note: some ar71xx devices have been migrated to the ath79 target. If your device is one of these, you may need to force the sysupgrade at the command line. If you force the flash, please be careful you're using the correct image, and be familiar with failsafe procedures (and in extreme cases, serial recovery).

Do not preserve settings for any versions prior to 1.13. They are not compatible.

Re: Openwrt 19.07 based Gargoyle

Posted: Sat Nov 09, 2019 8:33 pm
by RomanHK
Hi @Lantis,
I'm trying to carry 1.13.X and ...

1. I have problems with router "Turris Omnia - https://lantisproject.com/gargoyle_custom/mvebu/" again - missing kernel packages (F2FS filesystem and support atheros 9k) see my post here: viewtopic.php?f=14&t=11829&p=51667#p51667

2. As you add kernel packages, can you add additional support for the switch and other things?

Code: Select all

kmod-switch-mvsw61xx
kmod-gpio-pca953x
kmod-eeprom-at24
3. The /etc/opkg/distfeeds.conf file is still omitted, the gpkg update command does not load the sources from the file (you cannot install the squid package) see my post here: viewtopic.php?f=14&t=12138&p=54478#p54478

I will only run other tests after correcting the above errors.

Re: Openwrt 19.07 based Gargoyle

Posted: Sun Nov 10, 2019 1:34 am
by Lantis
RomanHK wrote:Hi @Lantis,
I'm trying to carry 1.13.X and ...

1. I have problems with router "Turris Omnia - https://lantisproject.com/gargoyle_custom/mvebu/" again - missing kernel packages (F2FS filesystem and support atheros 9k) see my post here: viewtopic.php?f=14&t=11829&p=51667#p51667
I've added f2fs and ath9k back in. They are marked as default in the config but don't come across properly. I'll probably forget these many times, sorry!
RomanHK wrote: 2. As you add kernel packages, can you add additional support for the switch and other things?

Code: Select all

kmod-switch-mvsw61xx
kmod-gpio-pca953x
kmod-eeprom-at24
Everything i can find says that you don't need mvsw61xx? It also looks like you need pca954x, not 953x?
Why is the eeprom module needed?

At this stage i have added pca954x as per upstream. No other changes.
RomanHK wrote: 3. The /etc/opkg/distfeeds.conf file is still omitted, the gpkg update command does not load the sources from the file (you cannot install the squid package) see my post here: viewtopic.php?f=14&t=12138&p=54478#p54478
This isn't necessary.
From my own router:

Code: Select all

root@Gargoyle:~# cat /etc/opkg/distfeeds.conf
src/gz openwrt_core http://downloads.openwrt.org/releases/19.07.0-rc1/targets/ipq806x/generic/packages
src/gz openwrt_base http://downloads.openwrt.org/releases/19.07.0-rc1/packages/arm_cortex-a15_neon-vfpv4/base

Code: Select all

root@Gargoyle:~# cat /etc/opkg.conf
src/gz openwrt_19.07.0-rc1_base http://downloads.openwrt.org/releases/19.07.0-rc1/packages/arm_cortex-a15_neon-vfpv4/base
src/gz openwrt_19.07.0-rc1_packages http://downloads.openwrt.org/releases/19.07.0-rc1/packages/arm_cortex-a15_neon-vfpv4/packages
src/gz openwrt_19.07.0-rc1_routing http://downloads.openwrt.org/releases/19.07.0-rc1/packages/arm_cortex-a15_neon-vfpv4/routing
src/gz openwrt_19.07.0-rc1_telephony http://downloads.openwrt.org/releases/19.07.0-rc1/packages/arm_cortex-a15_neon-vfpv4/telephony

src/gz gargoyle http://www.gargoyle-router.com/packages/gargoyle-1.14/ipq806x/default
src/gz gargoyle_kernel_specific http://www.gargoyle-router.com/packages/gargoyle-1.14/ipq806x/default_kernelspecific

dest root /
dest ram /tmp
dest plugin_root /plugin_root
lists_dir ext /var/opkg-lists
option overlay_root /overlay
src/gz lantisipq806x https://lantisproject.com/gargoyle_custom/ipq806x/default
src/gz lantisipq806xkernel https://lantisproject.com/gargoyle_custom/ipq806x/default_kernelspecific
We already include "openwrt_base" as "openwrt_19.07.0-rc1_base".
"openwrt_core" contains mostly kernel modules, which will all be incompatible with the Gargoyle kernel (because they were compiled with different options), so there's not much point in adding this.
As per all community builds, the gargoyle packages and kernel specific packages (replaces "openwrt_core") are included as directories which you can either upload files to your router from, or in the case of the builds that i host, you just need to add them as sources, as per the last 2 lines in my /etc/opkg.conf above.


I've just refreshed the mvebu/turris profile for you, you can try to flash again if you like.

Re: Openwrt 19.07 based Gargoyle

Posted: Sun Nov 10, 2019 6:05 am
by RomanHK
Ok, perfect, thank you very much ...
Here you have a link to the detailed scheme of the router Turris Omnia - This is really very rare and not all manufacturers like to provide a detailed scheme: https://doc.turris.cz/doc/_media/rtrom01-schema.pdf :shock:
Lantis wrote: Everything i can find says that you don't need mvsw61xx? It also looks like you need pca954x, not 953x?
Why is the eeprom module needed?

At this stage i have added pca954x as per upstream. No other changes.
- kmod-switch-mvsw61xx: I don't need it right now, but it's important to get VLAN up - it needs to be configured manually, nic.cz has requested a DSA fix, it should be fixed in the future.

- kmod-gpio-pca953x: it looks like it uses both (PCA9547BS page 15 of the manual, PCA9538PWR page 5 of the manual).

- kmod-eeprom-at24: should be a cripto chip, but I'm not sure. You can find it in the manual (ATSHA204A page 15). Maybe this link helps: https://lists.denx.de/pipermail/u-boot/ ... 88868.html

P.S. all of these kernel modules are included with the OEM TurrisOS firmware.

I will fix the package sources manually ;) , but I wasn't sure why gpkg was bypassing the /etc/opkg/* directory.

Re: Openwrt 19.07 based Gargoyle

Posted: Sun Nov 10, 2019 6:37 am
by RomanHK
What I have noticed is that the Linksys router shows both CPU and WiFi temperatures - for Omnia, temperatures are not displayed. But we'll try to deal with that later, if you help me with it, I'll provide the information you need.

Re: Openwrt 19.07 based Gargoyle

Posted: Sun Nov 10, 2019 1:57 pm
by RomanHK
After upgrading to the latest version I get error messages:
1. NFSD - I don't use, it doesn't bother me so much:

Code: Select all

Sun Nov 10 16:26:09 2019 daemon.notice procd: /etc/rc.d/S60nfsd: exportfs: could not open /var/lib/nfs/.etab.lock for locking: errno 2 (No such file or directory)
Sun Nov 10 16:26:09 2019 daemon.notice procd: /etc/rc.d/S60nfsd: exportfs: can't lock /var/lib/nfs/etab for writing
Sun Nov 10 16:26:09 2019 daemon.notice procd: /etc/rc.d/S60nfsd: Command failed: Not found
2. WebMon - sometimes after restart does not start WebMon = same characteristics as once in IMQ/NAT:

Code: Select all

Sun Nov 10 16:26:12 2019 daemon.notice procd: /etc/rc.d/S85webmon_gargoyle: Another app is currently holding the xtables lock. Perhaps you want to use the -w option?
3. Helpers - often displayed in the kernel dump:

Code: Select all

Sun Nov 10 16:26:40 2019 kern.info kernel: [   62.098033] xt_CT: No such helper "rtsp"