I've got vesafb-tng working in nitro3 right now, and am even posting this using "links -g -driver fb".

DocSavage wrote:

I notice that there are 2 files I can download for this kernel -- the ebuild and the .bz2. Do I need both of these? Or is it optional which one I use.

chunderbunny wrote:

Yeah, you'll need both files since the patch files aren't actually in portage and will therefore not be found on the portage mirrors. The patch file needs to be saved in /usr/portage/distfiles.

I've never needed to manually download the nitro-sources bz2 (nitro2 or nitro3), since a download location is included in the ebuild (which you do need to download). However, because of the way mirroring works in portage, portage will try to download the file from several regular portage mirrors before the download location in the ebuild is used, so manually downloading the bz2 is probably a good idea.

--Arek75
(james@verge-rpg.com)

p.s. I can't fully vouch for nitro's performance yet (I don't have X installed yet), but it seems to be a great kernel so far - keep it up, seppe!

[...]
ck-sources is Con Kolivas's kernel patch set. This kernel is HIGHLY tuned for desktop performance at the expense of throughput and some of the scheduler's ability to prioritize applications.
[...]

Is this the reason why I see that the write buffer of my burning program drops down to frightening low levels comparing to the stable 100% I get when using a stock kernel?

In other words:
* Can Nitro-sources do harm to my cd burning projects while stressing the PC?
* Do I have to pay for these performance improvements?_________________Alle dingen moeten onzin zijn.

[...]
ck-sources is Con Kolivas's kernel patch set. This kernel is HIGHLY tuned for desktop performance at the expense of throughput and some of the scheduler's ability to prioritize applications.
[...]

Is this the reason why I see that the write buffer of my burning program drops down to frightening low levels comparing to the stable 100% I get when using a stock kernel?

In other words:
* Can Nitro-sources do harm to my cd burning projects while stressing the PC?
* Do I have to pay for these performance improvements?

That is a tragically wrong description! -ck is used on many servers and improves throughput! If you're having buffer problems they are unrelated to the cpu scheduler.

2rusxaker : We already have "i2c_clientname", it is defined as "msp34xx". The trouble is with new 3rd parameter (added for swsusp2), not 4th
look at macro kthread_run and comments in include/linux/kthread.h

Code:

...
/**
* kthread_run: create and wake a thread.
* @threadfn: the function to run until signal_pending(current).
* @data: data ptr for @threadfn.
* @freezer_flags: process flags that should be used for freezing.
* PF_SYNCTHREAD if needed for syncing data to disk.
* PF_NOFREEZE if also needed for writing the image.
* 0 otherwise.
* @namefmt: printf-style name for the thread.
...

Just installed the new kernel on a new Reiser4 partition and everything is woriking great. Haven't gotten around to fixing the /dev/nvidia* stuff yet, but when I had chmod'd them I got around 800 frames using an nForce2 with 64MBs of ram. With this kernel and Reiser4 I'm definitlly experiencing a lot of speed improvements, with portage most noticeably. Even emerge syncs are going faster. I have been noticing a slight problem I didn't have before. The system overall slows down more than it did when I'm compiling two or more programs, glxgears goes down to 10 fps, but most apps remain pretty responsive. No problems at all. Will be testing win4lin soon.

Any anyone know what that kexec is all about? Do I really now have the ability to install kernel updates without having to look at my bios screen ever again?

That is a tragically wrong description! -ck is used on many servers and improves throughput! If you're having buffer problems they are unrelated to the cpu scheduler.

Why does a stock kernel work better for me when burning cd's? You are saying no without saying why.

Having just had a load avg. of ~8.00 burning a .cue under nitro3, I can sympathize! What I don't know is whether this is CK related or something in the mainline kernel. The last cd burning I did was on 2.6.8.1, IIRC, so it could be either.

Anyone else having burning problems? Anyone solved them?

edit: Heavy disk usage (e.g. BT hash checking) also leads to high load. I think I'll go back to nitro2 for now :/

I get this error on the emerge of ndiswrapper. First time I am runing nitro source is there some thing I am missing patch/switch? What I noticed right away is the clipping/hitch on data load is gone. Loading tons of textures like in doom 3 is smooth no data pulling hitching. Would really like to run these sources .