2.6.5-love4 aka "Dum Diddly Doo"

Message

steel300 · Post by **steel300** » Sun Apr 11, 2004 9:58 pm

Here you go. Check the notes.

Patch Name:                         Description:
2.6.5-mm4                           Latest MM
acerhk                              Acer Hotkeys support
acx100-0.2.0pre7-linux2.6.2         acx100 drivers
bootsplash-3.1.4-2.6.5              bootsplash support
cflags-selection.patch              Select the cflags for your kernel
config_hz.patch                     Change internal timer frequency
ipw2100-2.6.4-0.40-pre-patch        Centrino drivers
layer7-kernelpatch-nf-0.4.0         Layer7 Packet classifier
linux-2.6.0.dxr3.20031229           dxr3/H+ Support
love_ppm.patch                      Love boot logo
lufs-0.9.7-2.6.0-test9              LUFS support
menuconfig-NAME-v1.0                Do something with NAME
move-__this_module-to-modpost       For Nvidia
orinoco-0.13e-patch                 Monitor Mode
patch-2.4.x-vesafb-rrc              Vesafb hack
patch-2.6.4-am9                     Autoswappiness
patch-2.6.4-amd76x_pm               AMD Power Management
sii-3512-update.patch               Silicon Image updates
sis_agpgart_support                 Sis agp support
supermount-2.0.4-2.6.5-love1        Supermount
v30b                                Nick's scheduler
via-v4l-1.4a-drm                    Via DRM support
viafb_0                             Viafb support

I lost a lot of patches that were sent to me, so I'm sorry if I missed something. If there's something you want in, that I lost (GigaRaid), please email me the patch again. steel300 at gentoo dot org

http://www.public.iastate.edu/~jpcox

Zviratko · Post by **Zviratko** » Sun Apr 11, 2004 10:18 pm

Centrino wireless driver could get updated to 0.40-pre2 (around for a while, see ipw2100.sf.net)

Another thing - I'm not quite sure whether it's in your patch or even vanilla kernel, but turning CONFIG_X86_SPEEDSTEP_CENTRINO_ACPI on crashes the kernel on startup (at least on my lappy) - this is true since the first release having this option.

Also, I've had performance issue with Nick's scheduler && Preempt - kernel without Nick's scheduler runs fine with and without preempt, kernel with Nick's patch only runs fine when preempt is off... (for example compiling kernel on background with web surfing/mp3 takes twice the time to complete, heavy disk load gets the machine to its knees...)

anyway, great work :) I haven't used a vanilla kernel for a loong loooooong time... :)

Robe · Post by **Robe** » Sun Apr 11, 2004 10:27 pm

Just snaged and compiled the latest love 4. Works great ! Just have 2 questions

1.)cflags-selection.patch. Is anyone using it ? And if so, which flags are you using.

2)Do i need to do anything special to use nicks scheduler, or is it automatic.

And one again great work steel !

Lews_Therin · Post by **Lews_Therin** » Sun Apr 11, 2004 10:32 pm

I haven't upgraded since around 2.6.3-love6 (for shame

), and I noticed that the orinocco drivers aren't in this one. Are they default or something?

steel300 · Post by **steel300** » Sun Apr 11, 2004 10:43 pm

Lews_Therin wrote:I haven't upgraded since around 2.6.3-love6 (for shame ), and I noticed that the orinocco drivers aren't in this one. Are they default or something?

The orinoco drivers are in there. Check the notes again.

steel300 · Post by **steel300** » Sun Apr 11, 2004 10:44 pm

Robe wrote:Just snaged and compiled the latest love 4. Works great ! Just have 2 questions

1.)cflags-selection.patch. Is anyone using it ? And if so, which flags are you using.

2)Do i need to do anything special to use nicks scheduler, or is it automatic.

And one again great work steel !

I don't use custom cflags, but I would like to know who uses what.

Nick's scheduler is "on" by default. There's no way to turn it off.

discomfitor · Post by **discomfitor** » Sun Apr 11, 2004 11:02 pm

Working great here! For a while I used some pretty aggressive cflags on the kernel, but since I never noticed any speed gains, I figured that there was more risk than benefit and stopped. I'm considering trying a new set soon though.

thedumbkid · Post by **thedumbkid** » Sun Apr 11, 2004 11:19 pm

haha
o man, and I just installed love3 this afternoon...

time to do it again I guess

thanks!

snakattak3 · Post by **snakattak3** » Sun Apr 11, 2004 11:26 pm

When I patch, I get Hunk failures on a dry run. Are we supposed to just patch the previous love-sources? Its going against a vanilla kernel tree.

Robe · Post by **Robe** » Sun Apr 11, 2004 11:31 pm

Thanks for the info steel. Drakness, can u post which flags you where using, I know that I'd probably miss a few I really need if I only used the standard pentium4 ones.

CaribbeanKnight · Post by **CaribbeanKnight** » Sun Apr 11, 2004 11:42 pm

hmmm, failing compilation with this error:

Code: Select all

.....
  CC      init/main.o
  CHK     include/linux/compile.h
  UPD     include/linux/compile.h
  CC      init/version.o
  CC      init/do_mounts.o
  LD      init/mounts.o
  CC      init/initramfs.o
  LD      init/built-in.o
  HOSTCC  usr/gen_init_cpio
  CPIO    usr/initramfs_data.cpio
  GZIP    usr/initramfs_data.cpio.gz
  AS      usr/initramfs_data.o
  LD      usr/built-in.o
  CC      arch/i386/kernel/process.o
  CC      arch/i386/kernel/semaphore.o
  CC      arch/i386/kernel/signal.o
  AS      arch/i386/kernel/entry.o
arch/i386/kernel/entry.S: Assembler messages:
arch/i386/kernel/entry.S:93: Error: missing ')'
arch/i386/kernel/entry.S:93: Warning: rest of line ignored; first ignored character is `0'
arch/i386/kernel/entry.S:522: Error: bad expression
arch/i386/kernel/entry.S:522: Error: missing ')'
arch/i386/kernel/entry.S:522: Error: junk `8)' after expression
arch/i386/kernel/entry.S:522: Error: junk `8)' after expression
arch/i386/kernel/entry.S:522: Error: bad expression
arch/i386/kernel/entry.S:522: Error: missing ')'
arch/i386/kernel/entry.S:522: Error: junk `8)' after expression
arch/i386/kernel/entry.S:561: Error: bad expression
arch/i386/kernel/entry.S:561: Error: missing ')'
arch/i386/kernel/entry.S:561: Error: junk `8)' after expression
arch/i386/kernel/entry.S:561: Error: bad expression
arch/i386/kernel/entry.S:561: Error: missing ')'
arch/i386/kernel/entry.S:561: Error: junk `8)' after expression
arch/i386/kernel/entry.S:564: Error: bad expression
arch/i386/kernel/entry.S:564: Error: missing ')'
arch/i386/kernel/entry.S:564: Error: junk `8)' after expression
arch/i386/kernel/entry.S:566: Warning: missing operand; zero assumed
arch/i386/kernel/entry.S:566: Error: junk `1' after expression
arch/i386/kernel/entry.S:571: Error: bad expression
arch/i386/kernel/entry.S:571: Error: missing ')'
arch/i386/kernel/entry.S:571: Error: junk `8)' after expression
arch/i386/kernel/entry.S:571: Error: bad expression
arch/i386/kernel/entry.S:571: Error: missing ')'
arch/i386/kernel/entry.S:571: Error: junk `8)' after expression
make[1]: *** [arch/i386/kernel/entry.o] Error 1
make: *** [arch/i386/kernel] Error 2
StardusT linux #

something going wrong there, anyone knows what this could mean..?

ktech · Post by **ktech** » Sun Apr 11, 2004 11:43 pm

snakattak3 wrote:When I patch, I get Hunk failures on a dry run. Are we supposed to just patch the previous love-sources? Its going against a vanilla kernel tree.

It's against mm4.

ktech · Post by **ktech** » Sun Apr 11, 2004 11:45 pm

I'm getting things like that when compiling modules for this kernel (no problems for love3):

make: Entering directory `/usr/src/linux-2.6.5-love4'
CC [M] /var/tmp/portage/ati-drivers-3.7.6-r1/work/lib/modules/fglrx/build_mod/agp3.o
CC [M] /var/tmp/portage/ati-drivers-3.7.6-r1/work/lib/modules/fglrx/build_mod/nvidia-agp.o
CC [M] /var/tmp/portage/ati-drivers-3.7.6-r1/work/lib/modules/fglrx/build_mod/agpgart_be.o
CC [M] /var/tmp/portage/ati-drivers-3.7.6-r1/work/lib/modules/fglrx/build_mod/i7505-agp.o
CC [M] /var/tmp/portage/ati-drivers-3.7.6-r1/work/lib/modules/fglrx/build_mod/firegl_public.o
/var/tmp/portage/ati-drivers-3.7.6-r1/work/lib/modules/fglrx/build_mod/firegl_public.c

aviso: inicializaci?n de tipo de puntero incompatible
/var/tmp/portage/ati-drivers-3.7.6-r1/work/lib/modules/fglrx/build_mod/firegl_public.c

aviso: inicializaci?n de tipo de puntero incompatible
LD [M] /var/tmp/portage/ati-drivers-3.7.6-r1/work/lib/modules/fglrx/build_mod/fglrx.o
/bin/sh: line 1: /var/tmp/portage/ati-drivers-3.7.6-r1/work/lib/modules/fglrx/build_mod/.tmp_versions/fglrx.mod: No existe el fichero o el directorio

The latest says that the modules(fglrx.mod) doesn't exist. It happens with another different module but hasn't happened to me never before this.

Any tip?

Zviratko · Post by **Zviratko** » Mon Apr 12, 2004 12:17 am

I am unable to compile *any* out of tree drivers... It worked with -love3 but it does not even when I revert from love4.

VMWare fails with:

CC [M] /tmp/vmware-config2/vmmon-only/common/task.o
LD [M] /tmp/vmware-config2/vmmon-only/vmmon.o
/bin/sh: line 1: /tmp/vmware-config2/vmmon-only/.tmp_versions/vmmon.mod: No such file or directory
Building modules, stage 2.
make[1]: Leaving directory `/usr/src/linux-2.6.5-love4'
cp -f vmmon.ko ./../vmmon.o
cp: cannot stat `vmmon.ko': No such file or directory
make: *** [auto-build] Error 1
make: Leaving directory `/tmp/vmware-config2/vmmon-only'
Unable to build the vmmon module.

and ndiswrapper fails with:

CC [M] /var/tmp/portage/ndiswrapper-0.6-r1/work/ndiswrapper-0.6/driver/divdi3 .o
LD [M] /var/tmp/portage/ndiswrapper-0.6-r1/work/ndiswrapper-0.6/driver/ndiswr apper.o
/bin/sh: line 1: /var/tmp/portage/ndiswrapper-0.6-r1/work/ndiswrapper-0.6/driver /.tmp_versions/ndiswrapper.mod: No such file or directory

It is possible that the error is not in love-sources... but I haven't emerged anything significant (just afterstep, efax-gtk...)

snakattak3 · Post by **snakattak3** » Mon Apr 12, 2004 12:24 am

ktech wrote:
snakattak3 wrote:When I patch, I get Hunk failures on a dry run. Are we supposed to just patch the previous love-sources? Its going against a vanilla kernel tree.
It's against mm4.

Thanks

ktech · Post by **ktech** » Mon Apr 12, 2004 12:25 am

I have not emerged nothing really important into my system.

So the problem is mm4 or love4

I've been looking into lkml for problems like this but nobody seems to have it. I'll have a look tomorrow.

Bye!

pixie · Post by **pixie** » Mon Apr 12, 2004 1:39 am

I have the same ati-drivers problem. It won't build the module for this kernel.

secondshadow · Post by **secondshadow** » Mon Apr 12, 2004 2:06 am

I get this during 'make bzImage'. I'm compiling using the ebuild found on the link in Steel300's sig

CC arch/x86_64/lib/bitstr.o
AS arch/x86_64/lib/clear_page.o
AS arch/x86_64/lib/copy_page.o
AS arch/x86_64/lib/copy_user.o
AS arch/x86_64/lib/csum-copy.o
CC arch/x86_64/lib/csum-partial.o
CC arch/x86_64/lib/csum-wrappers.o
CC arch/x86_64/lib/dec_and_lock.o
CC arch/x86_64/lib/delay.o
AS arch/x86_64/lib/getuser.o
CC arch/x86_64/lib/io.o
AS arch/x86_64/lib/memcpy.o
CC arch/x86_64/lib/memmove.o
AS arch/x86_64/lib/memset.o
AS arch/x86_64/lib/putuser.o
AS arch/x86_64/lib/thunk.o
CC arch/x86_64/lib/usercopy.o
AR arch/x86_64/lib/lib.a
GEN .version
CHK include/linux/compile.h
UPD include/linux/compile.h
CC init/version.o
LD init/built-in.o
LD .tmp_vmlinux1
kernel/built-in.o(.text+0x1e59): In function `rebalance_tick':
: undefined reference to `MSEC_TO_JIFFIES'
make: *** [.tmp_vmlinux1] Error 1

sindre · Post by **sindre** » Mon Apr 12, 2004 2:09 am

I'm not sure why, but this kernel feels smoother than the last one. I might be imagining things though. Only things I changed was disabling preempt and actually enabling 4k-stack-whatever since I don't use nvidia-drivers anyway.

As for cflags-hacking, I usually change -O2 to -O3 and add -ffast-math.

zerojay · Post by **zerojay** » Mon Apr 12, 2004 3:09 am

I can't use the ebuild to emerge the sources.

[/usr/local/portage/sys-kernel/love-sources] > emerge love-sources-2.6.5-r4.ebuild
Calculating dependencies ...done!
>>> emerge (1 of 1) sys-kernel/love-sources-2.6.5-r4 to /
>>> md5 src_uri

linux-2.6.5.tar.bz2
>>> md5 src_uri

2.6.5-mm4.bz2
>>> md5 src_uri

2.6.5-love4.bz2
>>> Preparing to unpack...
>>> Unpacking source...
>>> Unpacking linux-2.6.5.tar.bz2 to /var/tmp/portage/love-sources-2.6.5-r4/work
* Applying 2.6.5-mm4.patch...
patch: pch.c:614: intuit_diff_type: Assertion `i0 != NONE' failed.
patch: pch.c:614: intuit_diff_type: Assertion `i0 != NONE' failed. [ !! ]

* Please attach /var/tmp/portage/love-sources-2.6.5-r4/temp/2.6.5-mm4.err to any bug you may post.

!!! ERROR: sys-kernel/love-sources-2.6.5-r4 failed.
!!! Function unipatch, Line 443, Exitcode 0
!!! Unable to dry-run patch.

-- 2.6.5-mm4.err -> http://darkstalker.servebeer.com/~darks ... eerror.log

steel300 · Post by **steel300** » Mon Apr 12, 2004 3:17 am

DarkStalker wrote:I can't use the ebuild to emerge the sources.

[/usr/local/portage/sys-kernel/love-sources] > emerge love-sources-2.6.5-r4.ebuild
Calculating dependencies ...done!
>>> emerge (1 of 1) sys-kernel/love-sources-2.6.5-r4 to /
>>> md5 src_uri linux-2.6.5.tar.bz2
>>> md5 src_uri 2.6.5-mm4.bz2
>>> md5 src_uri 2.6.5-love4.bz2
>>> Preparing to unpack...
>>> Unpacking source...
>>> Unpacking linux-2.6.5.tar.bz2 to /var/tmp/portage/love-sources-2.6.5-r4/work
* Applying 2.6.5-mm4.patch...
patch: pch.c:614: intuit_diff_type: Assertion `i0 != NONE' failed.
patch: pch.c:614: intuit_diff_type: Assertion `i0 != NONE' failed. [ !! ]

* Please attach /var/tmp/portage/love-sources-2.6.5-r4/temp/2.6.5-mm4.err to any bug you may post.

!!! ERROR: sys-kernel/love-sources-2.6.5-r4 failed.
!!! Function unipatch, Line 443, Exitcode 0
!!! Unable to dry-run patch.

-- 2.6.5-mm4.err -> http://darkstalker.servebeer.com/~darks ... eerror.log

I've seen this error before. I have no idea what causes though. There's a bug on it at bugs.gentoo.org, can't remember the bug number though. Can you patch it by hand?

zerojay · Post by **zerojay** » Mon Apr 12, 2004 3:20 am

Yeah, it looks like patching it went okay. I'll see if it compiles though. I've never had that error before.

steel300 · Post by **steel300** » Mon Apr 12, 2004 3:28 am

DarkStalker wrote:Yeah, it looks like patching it went okay. I'll see if it compiles though. I've never had that error before.

I'm still trying to track this one down. It's really crazy. Could you try emerging mm-sources and then unmerging them to see if it can patch them?

zerojay · Post by **zerojay** » Mon Apr 12, 2004 3:46 am

23:38:52 (348.91 KB/s) - `/usr/portage/distfiles/2.6.5-mm1-gentoo1.bz2' saved [1295483/1295483]

>>> md5 src_uri

linux-2.6.5.tar.bz2
>>> md5 src_uri

2.6.5-mm1-gentoo1.bz2
>>> Preparing to unpack...
>>> Unpacking source...
>>> Unpacking linux-2.6.5.tar.bz2 to /var/tmp/portage/mm-sources-2.6.5-r1/work
RUNNING FROM extra_functions.sh
* Applying 2.6.5-mm1-gentoo1.bz2...

* Failed Patch: 2.6.5-mm1-gentoo1.bz2!
*
* Include in your bugreport the contents of:
*
* /var/tmp/portage/mm-sources-2.6.5-r1/temp/2.6.5-mm1-gentoo1.bz2-23838.out

!!! ERROR: sys-kernel/mm-sources-2.6.5-r1 failed.
!!! Function epatch, Line 360, Exitcode 0
!!! Failed Patch: 2.6.5-mm1-gentoo1.bz2!

2.6.5-mm1-gentoo1.bz2-23838.out -> http://darkstalker.servebeer.com/~darks ... merror.log

Steel, you let me know if there's anything at all I can do to help out. If you would like, contact me through one of the IMs in my profile.

kevmille · Post by **kevmille** » Mon Apr 12, 2004 5:42 am

Kernel works like a charm. Thanks

2.6.5-love4 aka "Dum Diddly Doo"

2.6.5-love4 aka "Dum Diddly Doo"

Updates...

cflags

Re: cflags