krejler wrote:The old one incorporated a module parameter too, although, it didn't have a sysfs entry for it (which, for instance, the patches above provides). It would use value set in Kconfig as the default, and use the value provided by the parameter, if a parameter was actually passed.
The patches I posted above should work like I just described. It only uses the value fron the config as a last resort.
Anyway, it's up to you.

Ok, thanks for the head-up. I'll include your updated "total" patch in the next release. Oh, and thanks also for your work on it
m0sia wrote:great work! it works great!
btw anybody know how to use swsusp2 with fbsplah?
You mean fbsplash turning on and showing progress-bar when hibernating? It is in the TODO list of the devs, can't say when it will be implemented though.
Robin79 wrote:The alsa still dosent show any sign of the azx driver in the kernel config and that sucks
It seems that the azx driver is not ready for prime time yet. I'm sorry to say that you'll have to wait
mayday147 wrote:You're right. It did the trick. Thanks.
But isn't 4k stacks supposed to be a good thing? What happened?
Reiser4 used to have problems with 4k stacks on. Now these problems seems to be resolved, and I'm running ok with reiser4+4stacks at the moment. I may remove this limitation in the next morph release.
I'm working on -morph11. The highlights are:
- the cfq-ioprio patches by Jens Axboe, which now promise full io priority support also for writes (check the -ck mailing list archives for details). This means yet more system responsivity under high io-loads, yay!
- the update to -ac6, with many bugfixes with respect to the vanilla kernel;
- an up-to-date reiser4 patch from 2.6.10-mm2;
- more sofware-suspend fixes.
Thanks to all who are testing morph and helping in ironing out the issues they find. I really appreciate it
Cheers!