I have been using the nitro sources for a while and I think that they are very cool. I have a question though. Has there been any discussion over whether nitro sources should go into portage, or whether there should be a svn site or a rsync site to download it?

I guess it will never make it to portage, just like love-sources never will. Custom kernel patchsets like nitro-sources and love-sources are just way too risky and unstable to make it to the portage tree._________________nitro-sources, because between stable and experimental there exists only speed

While I don't remember this type of discussion about nitro-sources, there has been an extensive one about love-sources, and the general consensus is that patchets of this type are way too experimental for portage.

fs/reiser4/repacker.c:400: warning: 'wait_repacker_completion' defined but notused
fs/reiser4/repacker.c:595: warning: 'init_repacker_sysfs_interface' defined but not used
fs/reiser4/repacker.c:612: warning: 'done_repacker_sysfs_interface' defined but not used

Nice. Latency is at least as good as rc3-nitro2 was (which is pretty damn good), and I enabled preempt, though I'm not seeing many effects whether positive or negative.
Also, vesafb-tng *finally* works. Is there any way I can find out what resolution it's using once I have it running, other than by looking at it? The reason I ask is I have a suspicion for what's causing the problem with nVidia drivers where if you switch to a different console after you've started X once, the screen blacks out/powers down. You see, previously it did this, but now that both the consoles and X are (theoretically, which is why I'd like some way to confirm it) running at the same settings (1024x768-32@85), it doesn't. So my theory is basically that the bug in the nVidia drivers is somehow related to switching resolutions when switching to consoles, and if you don't have to switch resolutions it doesn't surface.

EDIT - one problem though is that on the consoles, the text starts 0.5-1cm (~1char) to the left of where the screen does, meaning I can't see it. Any way to change this?_________________Work is punishment for failing to procrastinate effectively.
last.fm

Also, vesafb-tng *finally* works. Is there any way I can find out what resolution it's using once I have it running, other than by looking at it? The reason I ask is I have a suspicion for what's causing the problem with nVidia drivers where if you switch to a different console after you've started X once, the screen blacks out/powers down. You see, previously it did this, but now that both the consoles and X are (theoretically, which is why I'd like some way to confirm it) running at the same settings (1024x768-32@85), it doesn't. So my theory is basically that the bug in the nVidia drivers is somehow related to switching resolutions when switching to consoles, and if you don't have to switch resolutions it doesn't surface.

Update: I rebooted, and now it's buggy again. vesafb-tng seems to be working still, but can't switch from X to a console without the screen powering down. So, I'm puzzled. The amount of things that have changed between when it worked and when it doesn't is approximately zero. _________________Work is punishment for failing to procrastinate effectively.
last.fm

Here it also randomly locks up, switching back to 2.6.8-r6 once more...
Too bad the nitros are so unstable most of the time

You're pushing things to the limit with these experimental kernels , dont expect it to always works out of the box. Maybe you need to try a different scheduler or something.

By my experience and most posts here seppe has done a great job on this release.

I#ve just rebuild half my system and only had one glitch during qt build . That was NOT due to nitro . I had just pushed my o/c a knotch higher than my "summer" settings and it looks like a it was a tad too far.

I pulled the FSB back from 180 to 178 and all went beautifully.

Hat's off to seppe!

Cant get gensplash to work, but it never has, that's another story. _________________Linux, because I'd rather own a free OS than steal one that's not worth paying for.
Gentoo because I'm a masochist

I guess it will never make it to portage, just like love-sources never will. Custom kernel patchsets like nitro-sources and love-sources are just way too risky and unstable to make it to the portage tree.