What's new?
- Lot's of stuff is out
- Software Suspend 2 is updated to latest version
- Reiser4 patch is updated to the version from 2.6.9-mm1
- I was so kind this time to give a broken-out directory with all individual patches applied, see in "Download" section

If you really want some patch is that isn't in anymore (like orinocco, acx, iteraid, ...), please let me know.

Add on patches
Get them here!
To apply them
1. Download them
2. cd /usr/src/linux
3. patch -p1 < /path/to/name_of_the_addon_patch.diff

Have fun with it!_________________nitro-sources, because between stable and experimental there exists only speed

As far as I know, inotify is indeed something related to Gnome's hal+dbus implementation, so maybe I should add it next time.

Btw, you should do 'make oldconfig' first when you've copied over your old .config file to this new kernel, then you won't get messages like these anymore because make oldconfig alters your .config to match the features of your new kernel._________________nitro-sources, because between stable and experimental there exists only speed

Compiles and boots fine, but I cannot install the ivtv drivers on it...

Code:

/var/tmp/portage/ivtv-0.2.0_rc2/work/ivtv-0.2.0-rc2f/driver/ivtv-driver.c:427:59: macro "create_workqueue" requires 2 arguments, but only 1 given
/var/tmp/portage/ivtv-0.2.0_rc2/work/ivtv-0.2.0-rc2f/driver/ivtv-driver.c: In function `ivtv_init_struct':
/var/tmp/portage/ivtv-0.2.0_rc2/work/ivtv-0.2.0-rc2f/driver/ivtv-driver.c:427: error: `create_workqueue' undeclared (first use in this function)
/var/tmp/portage/ivtv-0.2.0_rc2/work/ivtv-0.2.0-rc2f/driver/ivtv-driver.c:427: error: (Each undeclared identifier is reported only once
/var/tmp/portage/ivtv-0.2.0_rc2/work/ivtv-0.2.0-rc2f/driver/ivtv-driver.c:427: error: for each function it appears in.)
/var/tmp/portage/ivtv-0.2.0_rc2/work/ivtv-0.2.0-rc2f/driver/ivtv-driver.c:432:57: macro "create_workqueue" requires 2 arguments, but only 1 given

Anyway, do you have somewhere that supermount-ng patch that you used before? I am using it ATM and I do not have enough time to setup the alternate method of automatic un/mounting. I will not ask you to put it on nitro tough, I only would want the patch itself, I plan to apply it on my setup.

PS: what switches do I have to apply when patching with the supermount diff? p0, p1...?_________________.:c0p0n:.

Well after messing around myself with some kernel patches, most of them are in nitro sources. So why bothering with -klak sources? Good question. I don't have time anymore to re-create the whole thing and re-apply all patches when a new kernel version is released. Conclusion: horrah for nitro Horrah for us Belgium linux users, gnehe
Watch my sig change!_________________{Linux User #333296}Kernel 2.6.9-nitro4! << hurrah

Compiles and boots fine, but I cannot install the ivtv drivers on it...

Code:

/var/tmp/portage/ivtv-0.2.0_rc2/work/ivtv-0.2.0-rc2f/driver/ivtv-driver.c:427:59: macro "create_workqueue" requires 2 arguments, but only 1 given
/var/tmp/portage/ivtv-0.2.0_rc2/work/ivtv-0.2.0-rc2f/driver/ivtv-driver.c: In function `ivtv_init_struct':
/var/tmp/portage/ivtv-0.2.0_rc2/work/ivtv-0.2.0-rc2f/driver/ivtv-driver.c:427: error: `create_workqueue' undeclared (first use in this function)
/var/tmp/portage/ivtv-0.2.0_rc2/work/ivtv-0.2.0-rc2f/driver/ivtv-driver.c:427: error: (Each undeclared identifier is reported only once
/var/tmp/portage/ivtv-0.2.0_rc2/work/ivtv-0.2.0-rc2f/driver/ivtv-driver.c:427: error: for each function it appears in.)
/var/tmp/portage/ivtv-0.2.0_rc2/work/ivtv-0.2.0-rc2f/driver/ivtv-driver.c:432:57: macro "create_workqueue" requires 2 arguments, but only 1 given

Go to the /var/tmp/portage/ivtv-0.2.0_rc2/work/ivtv-0.2.0-rc2f/driver directory, than open that file (ivtv-driver.c) and change line number 427 from this :

Code:

itv->vbi_work_queues = create_workqueue("ivtv_vbi");

to this :

Code:

itv->vbi_work_queues = create_workqueue("ivtv_vbi", PF_SYNCTHREAD);

, than change line 432 too from this :

Code:

itv->fw_work_queues = create_workqueue("ivtv_fw");

to this :

Code:

itv->fw_work_queues = create_workqueue("ivtv_fw", PF_SYNCTHREAD);

and than try to compile (now you can't do emerge ..., but you have to use `ebuild /path/to/that/ebuild merge`).

Anyway, do you have somewhere that supermount-ng patch that you used before? I am using it ATM and I do not have enough time to setup the alternate method of automatic un/mounting. I will not ask you to put it on nitro tough, I only would want the patch itself, I plan to apply it on my setup.

PS: what switches do I have to apply when patching with the supermount diff? p0, p1...?

1. Download http://ck.kolivas.org/patches/2.6/2.6.9/2.6.9-ck3/patches/supermount-ng207.diff
2. cd /usr/src/linux (which should point to /usr/src/linux-2.6.9-nitro4)
3. patch -p1 < /path/to/supermount-ng207.diff
If you get failed hunks, let me know.. I'll fix them (and I will someday write a full tutorial on 'how to create patches and patch sets" _________________nitro-sources, because between stable and experimental there exists only speed