2.6.3-love1 aka "Fuzzy Bunnies Of Crazy Doom"

[Jefklak]

Could someone finally explain to me what the heck those "love" sources are about? What's changed? What's good/bad about them? Why not taking the usual kernels?


Thanks, That would clear things up.

[Stu L Tissimus]

Basically, they have lots of patches, and lots of luuuuv.

[nervousfinger]

Hmmm, compiled 2 times and still doesn't work...

i've used my 2.6.3_rc1_love1 config and it stops while booting at "Floppy Drive(s) is fd(0) 1,44" or something like that...

is there a new setting i haven't used?

[Jefklak]

Basically, they have lots of patches, and lots of luuuuv.

I already understood that.
Now, details please? Patches aren't always good...
But luuuv is

[cpu]

What with nForce2 APIC problems ? Because there is no patch included for this problems...

They should have already been included in mm. I would also *highly* recommend updating your bios.

We'll see - have ABIT NF7-S 2.0...

[Pink]

@ Jefklak:
Reading the notes frome each realease will tell you what extar patches are in there (love is always based on the mm-sources as a start point)

It is usually faster than the stock kernels and includes a few other things to play with such as Reiser4 filesystem, extra security models, scheduler items, etc.

As to whether it is good or bad is up to you. I have had incredible results with some of the love releases (speed, stability, playfulness) and others I've never even been able to boot from.

If you want 'reliablly stable' but up-to-date stuff perhaps try the mm-sources. If you want the chance of an unstable system but a great chance to learn and a few patches to really tweak the system then love it up!

All I can really say is try it, reading the other threads will reveal many problems and sucesses of the love with previous releases.

[MadEgg]

It compiles fine here, but I can't boot it
Same as 2.6.3-rc3-love1 btw. 2.6.2-rc1-love1 works fine though...

It seems to get stuck somewhere at the IDE-driver. I get this message:

Code: Select all

IDE1 at 0x170-0x177,0x376 on IRQ 15
hda: max request size 128 KiB

A few lines above that, this message(at driver initialisation I suppose):

Code: Select all

VP_IDE VIA vt8233a (rev 00) IDE UDMA 133 at PCI0000:00:11.1

Any clue on what's causing this?

[Epyon]

You need to enable

Code: Select all

Processor type and features  --->
       [*] Local APIC support on uniprocessors
       [*]   IO-APIC support on uniprocessors

It's a new APIC thing

So we have to enable APIC even if we don't want it?

[steel300]

You need to enable

Code: Select all

Processor type and features  --->
       [*] Local APIC support on uniprocessors
       [*]   IO-APIC support on uniprocessors

It's a new APIC thing

So we have to enable APIC even if we don't want it?

You'er confusing APIC with ACPI. ACPI is the power interface, APIC is the interrupt controller. Every computer has the interrupt controller and it *MUST* be used. Before it was enabled by default, now it's now. I don't know why.

[FirechilD]

i get some errors during my compiling too

Code: Select all

  CC      arch/i386/kernel/acpi/boot.o
arch/i386/kernel/acpi/boot.c: In Funktion »acpi_apic_setup«:
arch/i386/kernel/acpi/boot.c:581: Warnung: implicit declaration of function `clustered_apic_check'
arch/i386/kernel/acpi/boot.c:460: Warnung: unused variable `result'
  LD      arch/i386/kernel/acpi/built-in.o

Code: Select all

  LD      .tmp_vmlinux1
arch/i386/kernel/built-in.o(.text+0xd108): In function `acpi_apic_setup':
: undefined reference to `smp_found_config'
arch/i386/kernel/built-in.o(.text+0xd111): In function `acpi_apic_setup':
: undefined reference to `clustered_apic_check'
make: *** [.tmp_vmlinux1] Fehler 1

this last one kills the compiling :/
seems to have something to do with acpi - but i dont have it activatet.

there are some more errors, but i dont want to blow up this post ^^
if you wanne see them send me an pm

EDIT: seems that i am too slow with my writing *g*

[Spawn of Lovechild]

BEST KERNEL NAME. EVER.

[steel300]

BEST KERNEL NAME. EVER.

[neenee]

the name reminds me of the ending
of doom 1, where a decapitated bunny
is shown.

[mcoulman]

Code: Select all

Uncompressing linux ...Ok, booting kernel.

...and there she hangs. :(

I'm running 2.6.3 rc1 love1 now, so I think this is just a matter of the config being hosed. I copied the config from 2.6.3 rc1 love1 to 2.6.3 love1 and did 'make oldconfig.'

FYI dual CPU Intel Pentium III (Katmai) stepping 03
SMP enabled.

Suggestions welcomed, TIA.

[buckoven]

as always, mirrored here: http://buckoven.silent-server.de/lovepa ... -r2.ebuild

[steel300]

Code: Select all

Uncompressing linux ...Ok, booting kernel.

...and there she hangs.

I'm running 2.6.3 rc1 love1 now, so I think this is just a matter of the config being hosed. I copied the config from 2.6.3 rc1 love1 to 2.6.3 love1 and did 'make oldconfig.'

FYI dual CPU Intel Pentium III (Katmai) stepping 03
SMP enabled.

Suggestions welcomed, TIA.

I have the same issue. I'm still working a solution, but I'll let you know when I find one.

I'm also running dual PIII's (Coppermine)

[_Adik_]

Code: Select all

drivers/built-in.o(.text+0x6dfa3): In function `rivafb_cursor':
: undefined reference to `move_buf_aligned'
drivers/built-in.o(.text+0x6dfcd): In function `rivafb_cursor':
: undefined reference to `move_buf_aligned'
make: *** [.tmp_vmlinux1] Error 1

oops, it stops compiling... steel300, WTF?

[steel300]

Code: Select all

drivers/built-in.o(.text+0x6dfa3): In function `rivafb_cursor':
: undefined reference to `move_buf_aligned'
drivers/built-in.o(.text+0x6dfcd): In function `rivafb_cursor':
: undefined reference to `move_buf_aligned'
make: *** [.tmp_vmlinux1] Error 1

oops, it stops compiling... steel300, WTF?

Could you post your .config for me? Preferably on an off site link.

[_Adik_]

Code: Select all

drivers/built-in.o(.text+0x6dfa3): In function `rivafb_cursor':
: undefined reference to `move_buf_aligned'
drivers/built-in.o(.text+0x6dfcd): In function `rivafb_cursor':
: undefined reference to `move_buf_aligned'
make: *** [.tmp_vmlinux1] Error 1

oops, it stops compiling... steel300, WTF?

Could you post your .config for me? Preferably on an off site link.

here it is:
http://80.53.208.138/~adik/.config

[steel300]

Code: Select all

drivers/built-in.o(.text+0x6dfa3): In function `rivafb_cursor':
: undefined reference to `move_buf_aligned'
drivers/built-in.o(.text+0x6dfcd): In function `rivafb_cursor':
: undefined reference to `move_buf_aligned'
make: *** [.tmp_vmlinux1] Error 1

oops, it stops compiling... steel300, WTF?

Could you post your .config for me? Preferably on an off site link.

here it is:
http://80.53.208.138/~adik/.config

I'm looking at it now. Thanks

EDIT: I have no idea what it's doing. move_buf_aligned isn't defined anywhere. Try going back to vesafb.

[GentooBox]

Code: Select all

Calculating dependencies ...done!
>>> emerge (1 of 1) sys-kernel/love-sources-2.6.3-r1 to /
>>> md5 src_uri ;-) linux-2.6.3.tar.bz2
>>> md5 src_uri ;-) 2.6.3-love1.patch.bz2
>>> Unpacking source...
>>> Unpacking linux-2.6.3.tar.bz2 to /var/tmp/portage/love-sources-2.6.3-r1/work

bzip2: Compressed file ends unexpectedly;
        perhaps it is corrupted?  *Possible* reason follows.
bzip2: Success
        Input file = /usr/portage/distfiles/linux-2.6.3.tar.bz2, output file = (stdout)

It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.

You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.

>>> Unpacking 2.6.3-love1.patch.bz2 to /var/tmp/portage/love-sources-2.6.3-r1/work
mv: cannot stat `linux-2.6.3': No such file or directory
/usr/sbin/ebuild.sh: line 38: cd: /var/tmp/portage/love-sources-2.6.3-r1/work/linux-2.6.3-love1: No such file or directory
can't find file to patch at input line 4
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff -urN linux-2.6.3/Documentation/Changes linux-2.6.3-love1/Documentation/Changes
|--- linux-2.6.3/Documentation/Changes  2004-02-17 21:59:28.000000000 -0600
|+++ linux-2.6.3-love1/Documentation/Changes    2004-02-18 07:44:42.000000000 -0600
--------------------------
File to patch:

Thats what i get when i emerge love-sources.

[steel300]

Code: Select all

Calculating dependencies ...done!
>>> emerge (1 of 1) sys-kernel/love-sources-2.6.3-r1 to /
>>> md5 src_uri ;-) linux-2.6.3.tar.bz2
>>> md5 src_uri ;-) 2.6.3-love1.patch.bz2
>>> Unpacking source...
>>> Unpacking linux-2.6.3.tar.bz2 to /var/tmp/portage/love-sources-2.6.3-r1/work

bzip2: Compressed file ends unexpectedly;
        perhaps it is corrupted?  *Possible* reason follows.
bzip2: Success
        Input file = /usr/portage/distfiles/linux-2.6.3.tar.bz2, output file = (stdout)

It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.

You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.

>>> Unpacking 2.6.3-love1.patch.bz2 to /var/tmp/portage/love-sources-2.6.3-r1/work
mv: cannot stat `linux-2.6.3': No such file or directory
/usr/sbin/ebuild.sh: line 38: cd: /var/tmp/portage/love-sources-2.6.3-r1/work/linux-2.6.3-love1: No such file or directory
can't find file to patch at input line 4
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff -urN linux-2.6.3/Documentation/Changes linux-2.6.3-love1/Documentation/Changes
|--- linux-2.6.3/Documentation/Changes  2004-02-17 21:59:28.000000000 -0600
|+++ linux-2.6.3-love1/Documentation/Changes    2004-02-18 07:44:42.000000000 -0600
--------------------------
File to patch:

Thats what i get when i emerge love-sources.

Clear out distfiles and the files folder, then redigest and try again.

[snekiepete]

mcoulman wrote:
Code:
Uncompressing linux ...Ok, booting kernel.

...and there she hangs.

I'm running 2.6.3 rc1 love1 now, so I think this is just a matter of the config being hosed. I copied the config from 2.6.3 rc1 love1 to 2.6.3 love1 and did 'make oldconfig.'

FYI dual CPU Intel Pentium III (Katmai) stepping 03
SMP enabled.

Suggestions welcomed, TIA.

I have the same issue. I'm still working a solution, but I'll let you know when I find one.

I'm also running dual PIII's (Coppermine)


Same problem here, but with p4 single processor with HT. i have SMp and SMT enabled in the kernel. This did boot with the last 2.6.3-rc3-love2, but i had initrd(bootsplash problems) with that kernel

[nephros]

"WTF?" I went when:

Code: Select all

scourge linux # ls /usr/src/linux-2.6.3-love1/
COPYING
Makefile
... blablabla....
au88x0_a3d.c
au88x0_a3d.h

Ok, those obviously don't belong here, but where do I move them to? From the code I can glimpse it's some sort of driver, and "a3d" hints to audio, but it's completely undocumented...

[mafe]

Hmmm, compiled 2 times and still doesn't work...

i've used my 2.6.3_rc1_love1 config and it stops while booting at "Floppy Drive(s) is fd(0) 1,44" or something like that...

is there a new setting i haven't used?

still same problem here... i had the same in rc3 too, if i remove floppy support from the kernel it hangs at the ide part.