Sorry, I looked at the driver.c code in thelinux tree to see what I could do about making the buffer smaller etc.. Bad thing: A lot of work just to try and get this thing to work, good side: If one DID bother however, it seemed as one could in fact, hack it enough to make it work properly.
Anyway, I ditched it and got a Asus N66U, but not impressed with it at all, bloody shite actually but oh well. Will return it and go for a used router to slap open or tomato on hehe for half the price.
So, but to answer some tips on the compiling:
If i recall correctly do something like
initial:
git clone git repo
scripts/feeds update -a
scripts/feeds install -a
make menuconfig
#(choose target, subtarget n that}
#exit/save
make defconfig
make menuconfig
# Now choose whatevcer the fook you want, but try until you get used to the system to compiule stuff as M rather than *
# as M can be overriden and ignored whilst ocmpiling.
# How? Well, here is a tip to make things quicker, instead of just doing -j1:
time make -j12 V=s IGNORE_ERRORS=m BUILD_LOG=1 2> build.log
CHoose j to y9our liking , generally 1.5xthreads, or +1-2 people have diufferent ways of seein git. Do what tickles your scrotum.
Now, it will _probably_ fail, but now here comes the good parts:
IGNORE_ERRORS=m, means that the m modules won't break yoru build. SO if it still fails, it is due to something more fundamental:
(you can find the not so cruicial ones in e.g.) BUILD_LOG=1:
cat logs/packages/feeds/errors.text for example or so.
But the MAIN place to find those secretive erros, _without doing -1 [but NEEDS V=s still], is in
cat build.log
Thisi is WHERE you will find hints to what is wrong. In no time will you have stuff compiled.
Hope it helps.
About fixing the ring buffer and whatnot, it just is a bit too crap tbh. As scapi said, this thing wasn't build for speed.
It's not JUST wifi which breaks, it is also the lan. ANyway Scapi's method was to bring the wan port onto the switch.. this is NOT a working solution, as if the power goes down or a reboot, will leav eyour computer on the upstream network, aka WAN lol unless you manaually restart the dhcp server.. not good enough.
The solution is the ring issue, which drops packets.. fine if you don't care much I guess, not cool if you game or do other RT stuff.
But, I am gonna look into cutomising the stock firmware, as I do not care much for the usual backdoor stuff by companies, and so I might just rip out some of the services and install new ones in the stock and use that, if I can't get openwrt to work better with the onboard switch.
Laters.
)
)
