2.6.10-nitro4: The Kernel Formerly Known As Hercules

[discomfitor]

REISER4 PEOPLE: DISABLE 4K STACKS!!!!!!!!!!!

[bMd]

hmmmm, anyone getting following when emerge nitro-source?

[Moloch]

I haven't tried nitro4 yet. But hdparm has no problems on nitro3 for me.

And yes it's running as "rc-update add hdparm default"
_________________
Understanding is a three-edged sword: your side, their side, and the truth. --Kosh
1010011010

[discomfitor]

bMd: try deleting and redownloading the linux-2.6.10.tar.bz2 file.

Moloch: maybe it's just me then...
_________________
There is no substitute for experience.
Imperfection indicates a lack of effort.

[EricHsu]

Using it to post this!

Everything works perfectly, however, I have the following error msgs since 2.6.10-nitro3 (no problem with 2.6.9-nitro4):

[amorpheus]

new nitros *drools*
_________________
#!/usr/bin/amorpheus

[ashtophet]

Great!!! Compiled fine, booted as a rocket and by now is working smoothly!! Thanks a lot for yr. wonderful job, Darckness

[Cagnulein]

problem here:

[catalinux]

copy /char/drm/i830* from nitro3 over nitro4
intelfbdrv is broken too nitro3 is good

[Cagnulein]

copy that...

it works great. Thx

[thecrazyperson_ws]

dangit! i just downloaded and compiled nitro3 not even 6 hrs ago. after xorg, i guess it's kernel rebuild time again... to nitro4.

EDIT: nitro3 works beautifully... thanks for the great work, darckness. let's hope 4 is better/faster!
_________________
Bevelle: Dual Athlon MP 2000+, 1.25G ram, 120G HD, Gentoo 2005.1-r1, Kernel 2.6.15-gentoo-r5

Gagazet: Pentium 2-266, 288M ram, 240G HD, currently installing gentoo

Besaid: p-150, 80M ram, win2k pro

[()]

How come you've started including -mm? I originally opted for nitro-sources as an alternative to to mm (too unstable for my liking).
_________________
to be concerned is good

[peterk0]

[Pink]

[discomfitor]

I'm not including all of mm. Just the patches that I feel work nicely. If people don't like mm because it's too unstable, then why hasn't anyone else complained about the fact that I use the latest bk snapshots?

I suppose if it's a real big issue for people I'll stop including mm from now on. If you feel that way, post now. It's not really a big deal since it just means less work for me anyway .

I'll work on offering two different ebuilds/patches for this release.

EDIT: Just about done here...

EDIT: Done.
_________________
There is no substitute for experience.
Imperfection indicates a lack of effort.

[()]

[discomfitor]

(): Pure genius. Just...pure genius. I think that's the way I'll handle it from now on unless someone else has a better idea?
_________________
There is no substitute for experience.
Imperfection indicates a lack of effort.

[()]

Software modularization in general is a very nice concept, although USE flags are a bit messy (with the current, global, system anyway).
_________________
to be concerned is good

[SysOP XXL]

The new nitro works fine here! Good job, once again

I've spent 20 minutes dealing with the hdparm script though, it made my box freeze completely. I've found out that the '-d1' parameter freezes, removing it from the config fixed it. It doesn't have any drawbacks here, DMA is enabled without this option too (YMMV).

[discomfitor]

Alright, I've uploaded new patches and ebuilds which make the mm/bk patches completely optional. Check the first post for more info. The only difference besides that in the mm patch is that it actually downgrades the ac patch a bit (regular nitro4 uses ac7 now, while nitro4-mm is back on ac4). I don't think it's a huge difference, but who knows?

I hope that will make everyone happier!
_________________
There is no substitute for experience.
Imperfection indicates a lack of effort.

[Tiger683]

There is an error, which is caused probably by an option that noone else but me activated:

the block :

+ while(ide_unregister_hwif(hwif) < 0) {
+ hwif_removed_ops(hwif);
+ msleep(1000);

should be:

+ while(ide_unregister_hwif(hwif) < 0) {
+ removed_hwif_iops(hwif);
+ msleep(1000);

or else this breaks the build.....


EDIT:
UMMM, oh yeah, this is from regular nitro4, so ac7

where did the "hwif_removed_ops" come from???????

[()]

Great, merging nitro4 now :]
_________________
to be concerned is good

[discomfitor]

Tiger683: I'm assuming you meant the block in ide-pnp? I just fixed it and reuploaded the patches. I'm not going to punch you; frankly I'm impressed that nitro has become that widespread! And distro wars do suck. Your CFLAGS remind me of when I used to do that on love-sources back in the day. Then I realized that there was too much of a chance to segfault with not a lot of gain .

(): Glad to hear it.
_________________
There is no substitute for experience.
Imperfection indicates a lack of effort.

[Tiger683]

yepp

it was breaking my build the whole afternoon... )))
PS: You may punch me, but I'm running nitro on suse.......*runaway*

You never know, distro wars and stuff, been there , seen that..... :[

now building with
CONFIG_CFLAGS_STRING="-O3 -march=athlon-xp -mcpu=athlon-xp -mmmx -msse -mfpmath=sse -pipe -funroll-loops -frerun-cse-after-loop -frerun-loop-opt -falign-functions=4 -maccumulate-outgoing-args -ffast-math -fprefetch-loop-arrays -fomit-frame-pointer"
and regparm

lets see what f***up comes out...... --fforce-addr did mess asm-stuff at prepare stage....

hehe, i wil be glad when hes not going to chicken...(ehm, panic ),then it probably wont break my neck i guess...

Just curious: what bad things happen with CONFIG_IOPRIO_WRITE=y ?

[Archangel1]

Anyone else had issues with -want-mm? It goes beserk on here, just about everything fails. Makes me think I've done something wrong, except there's not a lot of scope for that in