Yes, I just confirmed that displaying ath1 crashes httpd and it doesn't show up in ps. I not using (and have never setup) WDS. This happens when my 5GHz radio is disabled, and it also happens when I set the channel width to 80MHz as I think that setting is effectively the same as disabling that radio because there is no signal output.
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Sat Apr 09, 2016 23:14 Post subject:
well that build works..dont know why it bricked. u can go from kong <-> brainslayer builds fine, i do it every time kong gives a new build just for checking if any issues are fixed there.
if it fails to boot it will try 3 times to boot then give up & load the fw on the other flash partition. how long did u let it boot loop for? _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Sun Apr 10, 2016 2:58 Post subject:
dont know then sorry. i havent fully bricked mine yet so i have no clue what the recovery procedure is, going to have to wait for kong to give u instructions. ill send him/her a message to check this thread. _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Sun Apr 10, 2016 21:41 Post subject:
kong's response
It is pretty simple, setup a tftp server e.g. on 192.168.1.2, in the root dir of the tftp goes the firmware, run flashimg flashes to first part run flashimg2 to second part. Attach serial at boot just hit a key, then it jumps to uboot prompt where you set it up.
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Sun Apr 17, 2016 2:55 Post subject:
we dont need to double flash anymore, at least on bs builds. after unbricking from a broken nightly build i noticed that if boot_part is on 2, a single flash flashes both parts at once (even though on reboot itll still switch to part 1). but if boot_part is on 1, then u have to flash twice. flashing from boot_part 1 seems to do nothing, its like the flash never happened. once on 2, fw flashes to both in 1 try.
u can do ubootenv set boot_part 2 when its running, then flash a new build after it. no need to reboot after changing it. _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
I got the .bin file off of Kong's site yesterday to update to 29510M. Today I noticed it's been updated again (24-Apr-2016 08:52) so I flashed that one. No matter what I do it stays at 29510M though. Not sure what's going on
I got the .bin file off of Kong's site yesterday to update to 29510M. Today I noticed it's been updated again (24-Apr-2016 08:52) so I flashed that one. No matter what I do it stays at 29510M though. Not sure what's going on
I got the .bin file off of Kong's site yesterday to update to 29510M. Today I noticed it's been updated again (24-Apr-2016 08:52) so I flashed that one. No matter what I do it stays at 29510M though. Not sure what's going on
The revision was not bumped, but added a little fix for the log spam.
Thanks, I just noticed the build date is different