2.6.12-nitro2 [__DEPRECATED__]

Tiger683 · Last edited by Tiger683 on Wed Jul 13, 2005 1:52 pm; edited 1 time in total

2.6.12-nitro2 "Six in the morning"

READ THIS FIRST
Nitro-sources is an experimental kernel patchset which is NOT supported by the Gentoo devs. If you have problems with something, see if the problem persists with a kernel supported by Gentoo. If you still have the same problem with a kernel supported by Gentoo (like vanilla-sources), then file a bug report at h**p://bugs.gentoo.org . If you only had the problem with 2.6.12-nitro2, and not with a vanilla kernel, then bug us in this thread.

Best Kernel ive had since quite a long time, and getting even better

DO NOT POST ABOUT GCC4 PROBLEMS, ATI/NVIDIA MODULES OR REISER4, UNLESS YOU
WANT OTHER USERS TO HELP YOU, BECAUSE I WONT, I ONLY CAN HELP WITH IN-KERNEL __AND__
NOT-BROKEN-BY-DESIGN STUFF

This kernel Patchset is unsupported on 64BIT Architectures, we can only try to help with compile-errors
on x86_64 and thelike

Phlogiston · Posted: Thu Jun 30, 2005 3:59 pm Post subject:

Thanks tiger, works perfectly here

ToeiRei · Veteran Joined: 03 Jan 2005 Posts: 1191 Location: Austria

Just punching in the emerge command, having my fingers crossed.

Rei
_________________
Please stand by - The mailer daemon is busy burning your messages in hell...

John5788 · Posted: Thu Jun 30, 2005 5:35 pm Post subject:

so, how do i switch from anticipatory to genetic anticipatory?

[edit]
nevermind, i just enable it in kernel and i guess it works automatically.

Zephyrus · Apprentice Joined: 01 Sep 2004 Posts: 204

As always i make you my sincere congratulations for your hard work.

About the nF4 problems: at least for me, they are not resolved

*sigh*

radr · Posted: Thu Jun 30, 2005 6:19 pm Post subject: SWEET!!

yesterday i built the nitro1, had a slight stuttering problem when under load (note emerge blah = GUI stuttering)

built up this baby used genetig-anticipatory sched..
no issues - thus far.

if i was happy before now im positively BEAMING!!

kudos on this rev tiger!! keep em rolling in.
_________________
Dual Opteron 280/1M (dual core = 4 procs) , 16G reg ECC ram, 4TB disc, NvIDIA GF 6800 PCI-E, SB X-FI
=Theres NO Substitute for Horsepower=

massimo · Veteran Joined: 22 Jun 2003 Posts: 1226

Nvidia doesn't work here as it didn't with the previous nitro release. I tried the nvidia driver from x86 and ~x86 both don't work. The log only says: Failed to initialize the NVIDIA kernel module! Do I need to have AGPGART support from Kernel? I use to have NVAgp=1 in my xorg.conf.

Thanks,
_________________
Hello 911? How are you?

Tiger683 · Posted: Thu Jun 30, 2005 7:29 pm Post subject:

I have no idea what's wrong, you are also the first nvidia user with problems....

anyone a clue?

you might also want to post dmesg right after trying to insmod nvidia

cheers

T
_________________
Retired gentoo user

Phlogiston · Posted: Thu Jun 30, 2005 7:38 pm Post subject:

b3cks · Posted: Thu Jun 30, 2005 7:40 pm Post subject:

Kernel works, but same problems as with the nitro1.
I'll tinker on it at the weekend...
_________________
I am /root and if you see me laughing you better have a backup.

massimo · Veteran Joined: 22 Jun 2003 Posts: 1226

Well, the problem was in front of the linux box

. I didn't emerge the ~x86 nvidia-glx package, thus nvidia-kernel from ~x86 and nvidia-glx from x86 were installed. Now I've got both nvidia-kernel and nvidia-glx from ~x86 emerged and everything is running just fine.

Thank you,
_________________
Hello 911? How are you?

Koala Kid · Guru Joined: 09 May 2003 Posts: 382

The compiling fails with the following error:

m0p · Apprentice Joined: 20 Jun 2005 Posts: 205 Location: en_GB

emerge'ing it out now. I've always stuck with ck-sources usually, since I've had experimental patchsets cause all sorts of problems before. 2.6.11-cko5 had extreme scheduler problems for me, but nitro has been getting alot of good feedback so I think I will try it

EDIT: Using it now. fglrx has this error:

priestjim · Posted: Thu Jun 30, 2005 11:38 pm Post subject:

For the ALSA problems : it happens sometimes. The developers seem to change the mixer settings strings from version to version (not always) to better reflect the particular setting. What happens is that what you've saved in the mixer before doesn't work as the old names have been changed. An alsamixer && alsactl store will correct the problem.
_________________
My soul is my antenna, I am the instrument + the guitar is my amplifier.
-- Ottmar Liebert

m0p · Apprentice Joined: 20 Jun 2005 Posts: 205 Location: en_GB

Ok. Also, removing the genetic I/O scheduler improved the system load problems. I've still got the Genetic lib routines enabled with no problems though

I'll try fixing my graphics stuff now.

SchAmane · Tux's lil' helper Joined: 11 Sep 2004 Posts: 107

so far everything work(nvidia,alsa,reiser4), thanks for new release

m0p · Apprentice Joined: 20 Jun 2005 Posts: 205 Location: en_GB

Although, one small thing. With the genetic scheduler disabled, the overall system response feels slower, at the gain of some free RAM.

EDIT: And I still can't get the ATi driver working.

EDIT 2: Another wierd thing, when I try to log out of gnome, GDM appears briefly, tty1 appears briefly then the system locks up. Could this be related to the fglrx issue? It's such ashame, cause apart from that, the works great.

Robin79 · Posted: Fri Jul 01, 2005 12:31 am Post subject:

Will try it now i hope my alsa problems is gone

_________________
Gentoo 2005.0
ASUS P5AD2 Deluxe MB
Intel P4 3.2GHz
PCI-E Nvidia Geforce PCX 5750
--------------------

Registered Linux User Nr # 319050 http://counter.li.org

Robin79 · Posted: Fri Jul 01, 2005 1:09 am Post subject:

Damm same issues as on last one cant use alsa in the kenrle or in portage

crap...
_________________
Gentoo 2005.0
ASUS P5AD2 Deluxe MB
Intel P4 3.2GHz
PCI-E Nvidia Geforce PCX 5750
--------------------

Registered Linux User Nr # 319050 http://counter.li.org

m0p · Apprentice Joined: 20 Jun 2005 Posts: 205 Location: en_GB

Hmm, works fine for me. What soundcard?

m0p · Apprentice Joined: 20 Jun 2005 Posts: 205 Location: en_GB

Wait a sec, according to someone on the IRC channel, the ati drivers don't yet support 2.6.12. So, that could be causing the acceleration problems. Not sure about the locking up problems though. Could they be related to an incompatible module?

ToeiRei · Veteran Joined: 03 Jan 2005 Posts: 1191 Location: Austria

Kernel working - "chicks dig it" - quoting one of the past versions (at least I do)
alsa glitches resolved

Rei
_________________
Please stand by - The mailer daemon is busy burning your messages in hell...

babykart · Guru Joined: 08 Oct 2004 Posts: 415

Gentree · Posted: Fri Jul 01, 2005 8:18 am Post subject:

Hi Tiger,

no gazzz on this one Im afraid.

media-video/nvidia-kernel-1.0.6629-r4

rebuild for the new kernel but fails to find a screen. :cry:

_________________
Linux, because I'd rather own a free OS than steal one that's not worth paying for.
Gentoo because I'm a masochist
AthlonXP-M on A7N8X. Portage ~x86

Tiger683 · Posted: Fri Jul 01, 2005 8:59 am Post subject:

ok, lets start from the beginning:

The problem with unresolved symbols is caused by something enabled as a module
which should be a builtin. this happens when the wonderful kernel devs decide to
remove the EXPORT_SYMBOL()s from the tree (probably to prevent proprietary and/or binary modules from using
these symbols). Try enabling all crypto stuff as builtin ( <*> )

fglrx: this is correct, ati sucks rocks in terms of up-to-date linux support

nvidia + Gentree: sorry, this kernel works perfectly with the newest ~x86 drivers,
the 6xxx ones dont work on my NV 6600GT, so i cant even test them....

Robin79: Alsa in the kernel is newer than the one in portage, so dont try emerging alsa-driver, it sucks

Other than that i have built EVERY driver as module as well as builtin, and all went well, so please
check your config once again. Some drivers depend on seemingly unrelated hardware support in other Kconfig sections.
When having problems with loading alsa in-kernel modules, compile them as builtin, might also be the unresolved-symbol issue.

b3cks: You mentioned that compiling of something failed at your side with something like "structure has no field name"
GregKH introduced a change to the api lately. according to it we have a change from: