Did you use an ebuild to get the vanilla or mm? They both change the top level Makefile ever so slightly and that could cause adding the EXTRAVERSION to break.

The first time I built love1 was with an ebuild to test out the new patch. The second build was made later after you went to sleep. I untared linux-2.6.4.tar.bz2 by hand, applied -mm1, then -love1. That is when I noticed the warning, looked for the .rej and found none. The love1-fixes.patch was then applied on top of that, diff'ed, then bunzip2'd and I moded the ebuild to make love1.

Quote:

That'd also explain the fact that there's no .rej file, the ebuild moves the original Makefile out of the way to Makefile.orig

I believe that the patch applies correctly, but the code itself might be out of date. I'm unfortunatly at work still, so I'll be another 2.5 hours until I can look at it.

I emerged with the ebuild and compiled just fine. Weird thing is though that not all my hardware sensors are working. I have w83781d loaded as a module, but it doesn't seem to do anything. Gkrellm2 (re-emerged just to make sure) recognizes only the lm75 module - which gives me my temps, but not my fan and voltages. w83781d used to work just fine in 2.6.4-rc1-love3...

I emerged with the ebuild and compiled just fine. Weird thing is though that not all my hardware sensors are working. I have w83781d loaded as a module, but it doesn't seem to do anything. Gkrellm2 (re-emerged just to make sure) recognizes only the lm75 module - which gives me my temps, but not my fan and voltages. w83781d used to work just fine in 2.6.4-rc1-love3...

yngwin,

That is the driver also used for the ASB100-A on my mobo. I'll check it when I get home, but I havn't noticed any thing out of the ordinary (the temps are natively off by a factor of 10 since the 2.6.1 kernel release). I normally compile that in as well so I'll test it as a module for you.

You're right. On closer inspection they arn't functioning. As are many other drivers paired with 2.6.4 "stable". There have been quite a few deep changes made in this kernel release which break things in -mm1 and -love1 (loops, packetwriting, au8820, reiser4, and quite a few others including the lm sensors we both use).

You're right. On closer inspection they arn't functioning. As are many other drivers paired with 2.6.4 "stable". There have been quite a few deep changes made in this kernel release which break things in -mm1 and -love1 (loops, packetwriting, au8820, reiser4, and quite a few others including the lm sensors we both use).

We'll keep working on it

Thanks for confirming that. I still think it's weird that this changed between rc1 and release, but so be it. Anyway, now I know it's not me. This is not critical for me, at least I get the temps from lm75.

On the other hand I can confirm this kernel compile works with my custom CFLAGS, although that was labeled experimental. I added "-march=athlon-xp -falign-jumps=4 -falign-loops=4 -falign-functions=64" - nothing too aggressive, but some nice optimizations for my processor.

I too had a problem with 2.6.4-mm1 (mm1 applied manually to kernel.org 2.6.4), but no problem applying the ck1 from the Con Kolivas home page, with the CFQ scheduler selected. Works great, but I don't select the supermount option. If you can't get Love sources to work, ck1 might be an alternative some might like, until Love is working.

The core problem with this release is not the pagecache and friends code, not the interface change in some kernel internals, or the half-done work in the bk trees to update all the drivers. The problem is these all happened at once. A lot of the more common drivers received all the necessary changes by the mm1 release, but a lot of other drivers didn't.

This is kind of a sore spot on the love release. I ask that anyone with a broken driver to wait for the next release of either mainline or mm upstream to hopefully sort out some of these changes, and then I'll take another close look at the patches introduced in love if I have to (note that this would be a great time to see if the authors of those patches have an updated release).

If love works now, great, go about your daily business. If not, sit tight for one release, a lot of things should be cleaned up soon._________________Website - All sorts of nonsense (some of it actually Linux related)

I don't know if anyone has experienced this but when trying to use the anticipatory scheduler the boot process hangs... looks like it's looking for the root partition... it's really strange... when using the cfq though everything is great...

Alrighty, I've been working on love2. I want to see if I can get some of the drivers we introduce that are broken working again. Those concerned about a driver that we add, it would be most appreciated if you could see if there's an update from where ever you originally got the patch. I have about a dozen options in a make allyesconfig that fail, and as much as I enjoy digging around code, I'd rather not if there are updated drivers.

Thanks. I hope to have a release for you within 24 hours._________________Website - All sorts of nonsense (some of it actually Linux related)

i think that the au88x0 drivers were updated in the latest bk snapshot patch for alsa, i'm not sure if its in mm2 or not though._________________This post has been over explained for newb-informing purposes.