Gargoyle bleeding edge build (OpenWRT 36307, debugfs)

[Slacker]

USE AT YOUR OWN RISK!

This flash may cause bricks, cancer, erectile dysfunction, blindness and insanity!

ar7xx ONLY compile, with kernel debugfs enabled in a copy of usb_large. No other changes.

Openwrt 36307 - EDIT: This is a Barrier Breaker Frankenstein build, so beware. I recommend waiting for the next new AA build or sticking with 32089.
Gargoyle df33941

Not a lot of ath9k changes, but what the hell, the 32089 build has been working so well (with disable_ani on) that I'm feeling adventurous.

Openwrt changes since my last compile (32089):
https://dev.openwrt.org/log/?action=sto ... sfph_mail=

I've split the flashes to save time/bandwidth:
https://www.dropbox.com/s/xcyze3ayiucgw ... 3941-1.zip = All images except starting with "W"
(Example: gargoyle_1.5.x-ar71xx-generic-Tl-wr1043nd-v1, etc)

https://www.dropbox.com/s/840v09lafbint ... 3941-2.zip = Images starting with "W"
(Example: gargoyle_1.5.x-ar71xx-generic-Wndr3700, etc)

I've built this primarily to see if the latest ath9k fixes take care of the "clients drop to 1Mbit, wifi flaky, even on just B/G" issue I, and others, have been dealing with.

Flashed on a 1043ND 1.7 and basic functionality verified. I'm using it as we speak, but I do not use tor or Openvpn.

To use disable_ani:

Code: Select all

echo 1 >/sys/kernel/debug/ieee80211/phy0/ath9k/disable_ani
wifi

To keep disable_ani enabled across reboots:

add to /etc/rc.local:

Code: Select all

echo 1 >/sys/kernel/debug/ieee80211/phy0/ath9k/disable_ani

EDIT: Fixed dropbox link for file 2

[BashfulBladder]

Can you post the output of 'cat /etc/banner'?

[Slacker]

Not sure why Openwrt is showing just an R... Maybe something got changed and the gargolye build script isn't picking the string up?
EDIT: Next build, I'll specify the openwrt version, instead of blanking it out (for latest) in the build sh file.

------------------------------------------------------------------
| _____ _ |
| | __ \ | | |
| | | \/ __ _ _ __ __ _ ___ _ _| | ___ |
| | | __ / _` | '__/ _` |/ _ \| | | | |/ _ \ |
| | |_\ \ (_| | | | (_| | (_) | |_| | | __/ |
| \____/\__,_|_| \__, |\___/ \__, |_|\___| |
| __/ | __/ | |
| |___/ |___/ |
| |
|----------------------------------------------------------------|
| Gargoyle version 1.5.X | OpenWrt Attitude Adjustment branch |
| Gargoyle revision df33941 | OpenWrt revision r |
| Built April 10, 2013 | Target ar71xx/debugfs_usb_large |
------------------------------------------------------------------

[BashfulBladder]

The build script(s) (build.sh & rebuild.sh) are tuned to work on the Attitude Adjustment branch. By tuned, I mean, the source, the folder structure, the packages, the config files.

https://dev.openwrt.org/log/branches/at ... adjustment

Nothing in 3 weeks.
------------------
Building OpenWrt's trunk (aka Barrier Breaker) is no harder to build than Attitude Adjustment - but the Gargoyle scripts aren't set up to build Barrier Breaker.

You were pointing to logs from trunk, and I know its not just "I'll just change this number".

[jchapman007]

I would like to do some testing on ubiquiti devices using a more up to date openwrt and I don't have time to build gargoyle myself. Do you mind including ubiquiti builds when you build your images. I would be happy to test on the rocket m and air router. Thanks again for building these images. I just don't have any hardware for the images you have built.

[Slacker]

BashfulBladder: You know, I completely forgot about BB!
It looks like the structure is still similar enough to work, because I use everything on the Gargoyle end, except USB printing, routing, quotas and restrictions.
The guest SSID workaround also works, but I reckon there will be a point wen the divergence will be so great that something noticeable will break, or Gargoyle will move to it.

I always test the image om my router, since I have the serial console for debrick, so if I get a broken image, it'll not be posted.

jchapman007: Sure thing, I'll include them as long as there aren't flaming hoops and you're aware of both, the above and that I don't have the hardware to test it.

[Slacker]

BashfulBladder: I did some playing around with it and I see what you mean, because when I specify BB in build.sh, it breaks the build process.
I haven't used many packages, but nano, transmission and pptp(needs --force-deps) all work. I do fully expect a brick, or things exploding very soon!

jchapman007:
Here's 32089, which is the latest AA on the latest gargoyle. I did a clean build on a new directory, so it should be "by the book".

If you want, or need BB for newer hardware, I can build atheros along with ar7xxx(mine) on this weird "shouldn't even be working" BB/gargoyle setup I've blundered on, provided it even works next build.
Those boxes of yours are debrickable, right?

https://www.dropbox.com/s/lmp5gysmzjpwo ... -32089.zip

[nebbia88]

https://www.dropbox.com/s/lmp5gysmzjpwo ... -32089.zip

Nothing Here
The file you're looking for has been deleted or moved.