Gargoyle Forum

heilbronn wrote: ↑

Sun Feb 19, 2023 6:22 am

However, according to top the usbmuxd daemon is taking 50% CPU time (with a load of 1) although I haven't attached anything to the USB port! Is this normal?

Seems it's an issue for OpenWrt builds too - discussed here.

Intel i350 is not available - i think it's because of missing drivers. Looks like i350 requires the igb driver which isn't currently built. Re the Realtek NICs: 1) while you're running a speed test through the device, ssh into it and use top to monitor CPU stats - looking to see whether there might...

This build has been superceded by a 1.15.x build.

Download archive: download from Github The archives contain the images and packages generated from experimental bcm27xx (aka RaspberryPi) target configurations for Gargoyle 1.15.x. The source was from Gargoyle's git repository base_on_openwrt_2203 branch at commit 1bd0d80a. In order to pick up rece...

Firstly this discussion probably should be in it's own thread because it's not about x86 - mods, can this be split off into a new thread? It's disappointing that flashing Gargoyle as a sysupgrade didn't appear to go anywhere, but that sometimes even happens with a successful flash in my experience. ...

As an experiment, try installing Openwrt from scratch then do a sysupgrade (i.e. upgrade through OpenWrt's web UI using the Gargoyle sysupgrade image) to see whether that behaves any better. NOTE: don't keep settings!

Not necessarily a desirable solution, but you might be able to mitigate Pi-hole's stability problem with regular scheduled reboots?

Thanks for the feedback!

If you can't install the Gargoyle "factory" image via the OEM interface, I would suggest trying to install the OpenWrt "factory" image, and then install the Gargoyle "sysupgrade" image from OpenWrt (don't keep settings though). If you can't install OpenWrt via the OEM i...

So which of the 2 files did you try and install: the "factory" or "sysupgrade"?