I suppose that the only "new" thing in this release is tux. Everything you would expect in a nitro is here, and it runs fantastically.

Nvidia drivers DO work with this kernel. If you're having issues, try using kernel agpgart and/or downloading the linked nvidia-kernel directory (goes in your $PORTDIR_OVERLAY/media-video) and using the newest ebuild in there that I made. It adjusts some stuff that's new since rc2 and avoids this:

Con Kolivas wrote:

Nvidia is completely borked with 2.6.11-rc2. The number of changes required to get it going is getting ridiculous so unless someone can send me a patch to do it all in one go there is not much hope of getting compatibility working.

I wonder if I he knows that nitro has accounted for this...

Insane stack users: Here is basically how it works (unless I'm completely mistaken). The smaller the stack size, the less memory stuff will use. The larger the stack size, the more memory it will use AND the faster stuff will work (to an extent I suppose). I'm not sure how noticible it would be and I'm sticking to 4k stacks myself. No guarantees that everything will work with stack sizes other than 4k and 8k!

fbsplash should work now. Genetic scheduling is out again and probably isn't coming back.

SEMI-NEW:
This kernel bears the "Darckness Gaming Seal Of Approval". This means that it's a kernel that I can play World of Warcraft and other intense games without issues on. Of course I test it for other stuff as well, but I remember always being frustrated when I couldn't find a good fps-guaranteed kernel. From now on, I will put the seal of approval on any nitros (or other kernels if people really want me to...) that I deem worthy of my use in various gaming worlds. For those of you wondering why I think I'm qualified to have my own Seal Of Approval, check out my awesome World Of Warcraft Howto. I'll probably be posting a couple other gaming howtos in the near future as well.

Also be sure to check out my ideas on genkernel. Anyone who can contribute to realizing some of the ideas in that thread would be most appreciated.

NEW!
Behold in all of its glory, we have here something wild and untamed. Something to set your teeth on edge. Straight from my logs we have:
THE NITRO-DEV FILES!_________________There is no substitute for experience.
Imperfection indicates a lack of effort.

Last edited by discomfitor on Tue Feb 08, 2005 9:19 pm; edited 4 times in total

Rainmaker: 2 means to use kernel agpgart. The nvidia agpgart is broken since rc2. In the kernel you can find agpgart in Character Devices._________________There is no substitute for experience.
Imperfection indicates a lack of effort.

well, I seem to be lucky then, because it works without agp support enabled in my kernel and with nvagp=1 in xorg.conf_________________If you can't dazzle them with brilliance, baffle them with bullshit.

HazarT: I never mark any of them ~amd64 because I have no way of testing them on that architecture. I think I'll be getting a couple machines of that variant to play with soon, so this may change in the near future._________________There is no substitute for experience.
Imperfection indicates a lack of effort.

http://www.evil-sources.org/fix-x86_64-asm-offsets.patch, that fixes it for me and it doesn't seem to have any negative side-effects, ignore the -mm base of this patch because it only adds an ifdef around the offending code._________________This post has been over explained for newb-informing purposes.

Even with this release and the new Nvidia driver, X freezes with ~100% CPU usage. I can ssh in and sigkill it, but I would like to have a stable kernel above 2.6.10 Very interesting for me is that the crashes very often happen during high disk activity (merging to / , or using locate or find)

I have to chime in here to say me too! I mistakingly assumed I was using agpgart from the kernel as I had made the xorg.conf change to force agpgart over nvagp. To my surprise I discovered only today that I don't even have agpgart support enabled in the kernel. I have not been having any issues either.

On another note, I do need to report that swsusp2 is not working. At least resume doesn't work -- just get a black screen on resume. I think I saw mention of some kernel panics and I will check for that to confirm it.

I've really worked myself into a corner now. The last nitro, would lock up on me randomly, this one doesn't compile. I built my system with reiserfs4, so I need a state of the art kernel (or at least one with reiser4 and works with nvidia)