View previous topic :: View next topic |
Author |
Message |
jse86 n00b
![n00b n00b](/images/ranks/rank_rect_0.gif)
![](images/avatars/gallery/The Matrix/movie_the_matrix_neo_2.gif)
Joined: 13 Aug 2004 Posts: 51 Location: Longview, TX
|
Posted: Mon Aug 16, 2004 1:00 am Post subject: |
|
|
what the heck is a nitro patched source? |
|
Back to top |
|
![](templates/gentoo/images/spacer.gif) |
butters Guru
![Guru Guru](/images/ranks/rank_rect_3.gif)
![](images/avatars/gallery/Southpark/avatar13.gif)
Joined: 13 May 2002 Posts: 427 Location: Poughkeepsie, NY
|
Posted: Mon Aug 16, 2004 1:24 am Post subject: |
|
|
To those confused about the purpose of the nitro patchset, or any of the others (love, xx, mm, ck, etc.):
As you can see on the first post in this thread, this kernel is kernel.org's vanilla 2.6.8 kernel, with a bunch of patches applied that make changes to the kernel source code. Some of these patches enable support for features not available in the mainline kernel:
reiser4, win4lin, supermount, squashfs, BadRAM workaround, lirc remote controls
And some of these patches are improvements on existing kernel technologies:
CFQ i/o scheduler, vesafb-tng, gensplash, staircase process scheduler
But the majority are patches to reduce latency (response time) for desktop users. This patchset is by far the fastest kernel I have ever used, in terms of the snappy response and general interactivity.
The hidden purpose of these patchsets is to allow many users to use and test new technologies that will one day make it to the mainline kernel. For example, reiser4 will soon become a standard filesystem option in the vanilla kernel. The testing made possible by nitro-sources and other reiser4-enabled patchsets helps developers iron out any wrinkles that remain so that the general release will go smoothly.
A word of advice is to always keep a backup kernel in your /boot partition that you know will boot your system. Although most of the problems I've had with various patchsets are minor stability problems, somtimes they won't boot at all for one reason or another. So make sure to keep your trusty stable kernel in your bootloader menu just in case. _________________ If tugboats were bigger, they'd be the ones getting tugged. |
|
Back to top |
|
![](templates/gentoo/images/spacer.gif) |
jj11888 n00b
![n00b n00b](/images/ranks/rank_rect_0.gif)
Joined: 28 Apr 2004 Posts: 36
|
Posted: Mon Aug 16, 2004 3:07 am Post subject: |
|
|
butters wrote: |
1. I've been blessed with hardware that NEVER works with vesafb, or any other type of framebuffer, while everyone else's hardware I've set up does framebuffer just fine. Needless to say I haven't been paying attention to the posts about vesa-tng, since I don't use framebuffer. So, is the normal VESA framebuffer option in the graphics section actually the vesa-tng you speak of? I think I'll give it a try and see if anything drastic has changed to make either my i810e or Intel Extreme (sigh) i855GM work... after all they should be VESA compliant. |
I dont no about the i855gm, but the i810e i can help you with
vesa and vesafb and vesa-tng is NOT compatable with intel cards, dont even waste your time tring
Theres a i810fb driver that you can use, look at Documentation/fb/i810.txt, i use this in my grub.conf:
Code: | kernel (hd0,2)/boot/bzImage root=/dev/hda3 dev=/dev/hdc video=i810fb:vram:2,xres:1024,yres:768,bpp:16,hsync1:30,hsync2:66,vsync1:50,vsync2:130 gentoo=nodevfs elevator=cfq splash=verbose,theme:EvenNewerTux
|
|
|
Back to top |
|
![](templates/gentoo/images/spacer.gif) |
pleusicles n00b
![n00b n00b](/images/ranks/rank_rect_0.gif)
Joined: 26 May 2004 Posts: 44
|
Posted: Mon Aug 16, 2004 7:46 am Post subject: |
|
|
seppe: thanks for the barriers patch ![Smile :)](images/smiles/icon_smile.gif) |
|
Back to top |
|
![](templates/gentoo/images/spacer.gif) |
Archangel1 Veteran
![Veteran Veteran](/images/ranks/rank_rect_5_vet.gif)
![](images/avatars/10640655464313fa93b48a7.png)
Joined: 21 Apr 2004 Posts: 1212 Location: Work
|
Posted: Mon Aug 16, 2004 8:39 am Post subject: |
|
|
jj11888 wrote: |
vesa and vesafb and vesa-tng is NOT compatable with intel cards, dont even waste your time tring
|
That's a bit of a generalisation.... framebuffer & bootsplash are working absolutely fine on my i830 notebook. Admittedly it's been _really_ weird with vesafb-tng so far, but none of those kernels have worked terribly well on my machine yet anyway. |
|
Back to top |
|
![](templates/gentoo/images/spacer.gif) |
kos n00b
![n00b n00b](/images/ranks/rank_rect_0.gif)
Joined: 28 May 2003 Posts: 71 Location: Mountain View, CA
|
Posted: Mon Aug 16, 2004 10:32 am Post subject: |
|
|
raku wrote: | kos:
i've got the same starting from 2.6.8-rc3-nitro1, but it was with 4k stacks on
whenever i started to compile anything, i got system crush (only hard reset helped).
i switched 4k off just a minute ago (new 2.6.8-nitro1) and kdelibs is compiling for almost half an hour (not possible before) |
4k stacks is a known r4 problem, they aren't supported yet. Tried lots of kernels in attempt to find one that won't fail on compilation before found out this fact. But 2.6.8-nitro1 oopses even with 8k stacks. Rolled back to 2.6.8-rc3-nitro1 for now, had no problems with it for several weeks. _________________ /KoS |
|
Back to top |
|
![](templates/gentoo/images/spacer.gif) |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|