2.6.11-love2 (usb & genetic-as deplug. oops fix)

Message

Archangel1 · Post by **Archangel1** » Sat Mar 12, 2005 1:08 am

MyrddinEmrys: Looks like it's gotten confused with one of the parameters - maybe it's not optional in this release?
"make mrproper" will clean out your .config from memory - if not deleting .config should do it. Then go into menuconfig, device drivers, USB and put in a value for "USB HID Polling Interval" - 10's the default, 2's nicer if your mouse will handle it.
Or it may well be easier to edit .config, and find the USB_HID_MOUSE_POLLING_INTERVAL line, and change it to "CONFIG_USB_HID_MOUSE_POLLING_INTERVAL=2".

Lunchy: Note that it's the polling interval, not the polling rate. Hence a value of 2 gives 500Hz polling - when you entered 1000 it would have been checking once a second. Your mouse probably got totally bored/confused and stopped bothering at that point

DrWoland · Post by **DrWoland** » Sat Mar 12, 2005 3:22 am

MyrddinEmrys wrote:well... I was using the love1 version... I tought I should give this one a shot... emerged, set the configs... and when I his make && make modules_install I got some parse error...

the weird part is that now, I can't run make meuconfig

Code: Select all

HOSTCC  scripts/basic/fixdep
  HOSTCC  scripts/basic/split-include
  HOSTCC  scripts/basic/docproc
  SHIPPED scripts/kconfig/zconf.tab.h
  HOSTCC  scripts/kconfig/conf.o
  HOSTCC  scripts/kconfig/mconf.o
  SHIPPED scripts/kconfig/zconf.tab.c
  SHIPPED scripts/kconfig/lex.zconf.c
  HOSTCC  scripts/kconfig/zconf.tab.o
  HOSTLD  scripts/kconfig/mconf
  HOSTCC  scripts/lxdialog/checklist.o
  HOSTCC  scripts/lxdialog/inputbox.o
  HOSTCC  scripts/lxdialog/lxdialog.o
  HOSTCC  scripts/lxdialog/menubox.o
  HOSTCC  scripts/lxdialog/msgbox.o
  HOSTCC  scripts/lxdialog/textbox.o
  HOSTCC  scripts/lxdialog/util.o
  HOSTCC  scripts/lxdialog/yesno.o
  HOSTLD  scripts/lxdialog/lxdialog
scripts/kconfig/mconf arch/i386/Kconfig
arch/i386/Kconfig:923:warning: choice values currently only support a single prompt
arch/i386/Kconfig:926:warning: choice values currently only support a single prompt
arch/i386/Kconfig:929:warning: choice values currently only support a single prompt
arch/i386/Kconfig:932:warning: choice values currently only support a single prompt
init/Kconfig:196:warning: choice values currently only support a single prompt
init/Kconfig:199:warning: choice values currently only support a single prompt
init/Kconfig:202:warning: choice values currently only support a single prompt
init/Kconfig:205:warning: choice values currently only support a single prompt
drivers/video/Kconfig:494:warning: 'select' used by config symbol 'FB_NVIDIA' refer to undefined symbol 'FB_CFB_FILLRECT'
drivers/video/Kconfig:495:warning: 'select' used by config symbol 'FB_NVIDIA' refer to undefined symbol 'FB_CFB_COPYAREA'
drivers/video/Kconfig:496:warning: 'select' used by config symbol 'FB_NVIDIA' refer to undefined symbol 'FB_CFB_IMAGEBLIT'
drivers/video/Kconfig:497:warning: 'select' used by config symbol 'FB_NVIDIA' refer to undefined symbol 'FB_SOFT_CURSOR'
#
# using defaults found in .config
#
.config:1254: symbol value '' invalid for USB_HID_MOUSE_POLLING_INTERVAL
make[1]: *** [menuconfig] Error 1
make: *** [menuconfig] Error 2

any1 has a clue ? help will be apreciated =)

There are a ton of posts about this in both threads. You need to go in and set the polling interval. The easiest way to do this is nano -w .config, the hit Ctrl+W, then type in POLLING and set the value to something. If you have a USB MX anything, set it to 2, otherwise I don't know, look around.

borkdox · Post by **borkdox** » Sat Mar 12, 2005 6:20 am

I this kernel uncompatible with nvidia drivers 1.0.7167? I cant seem to get X started with nvidia-kernel 1.0.7167, it works fine with 1.0.6629.

rmh3093 · Post by **rmh3093** » Sat Mar 12, 2005 6:25 am

danm when did that version come out?

DrWoland · Post by **DrWoland** » Sat Mar 12, 2005 6:33 am

rmh3093 wrote:danm when did that version come out?

I certainly pooped myself when I saw that 7 at the beginning of the version number... guess i better do some research...

fallow · Post by **fallow** » Sat Mar 12, 2005 6:48 am

MyrddinEmrys wrote:
Code: Select all
#
# using defaults found in .config
#
.config:1254: symbol value '' invalid for USB_HID_MOUSE_POLLING_INTERVAL
make[1]: *** [menuconfig] Error 1
make: *** [menuconfig] Error 2
any1 has a clue ? help will be apreciated =)

Archangel1 wrote: Or it may well be easier to edit .config, and find the USB_HID_MOUSE_POLLING_INTERVAL line, and change it to "CONFIG_USB_HID_MOUSE_POLLING_INTERVAL=2".
Lunchy: Note that it's the polling interval, not the polling rate. Hence a value of 2 gives 500Hz polling - when you entered 1000 it would have been checking once a second. Your mouse probably got totally bored/confused and stopped bothering at that point

EXACTLY

about NVIDIA 7167 - I`m on it now - working fine with love2

(in portage).

cheers.

rmh3093 · Post by **rmh3093** » Sat Mar 12, 2005 6:49 am

i wonder if it will work with the bk-agp

ashtophet · Post by **ashtophet** » Sat Mar 12, 2005 8:45 am

elocal wrote:I this kernel uncompatible with nvidia drivers 1.0.7167? I cant seem to get X started with nvidia-kernel 1.0.7167, it works fine with 1.0.6629.

Here also working, with nvagp.

cheers

fallow · Post by **fallow** » Sat Mar 12, 2005 9:22 am

galiza_ceive wrote:
elocal wrote:I this kernel uncompatible with nvidia drivers 1.0.7167? I cant seem to get X started with nvidia-kernel 1.0.7167, it works fine with 1.0.6629.
Here also working, with nvagp.

cheers

yeap , here also with nvagp

Code: Select all

# cat /proc/driver/nvidia/version 
NVRM version: NVIDIA Linux x86 NVIDIA Kernel Module  1.0-7167  Fri Feb 25 09:08:22 PST 2005
GCC version:  gcc version 3.4.3 20050110 (Gentoo Linux 3.4.3.20050110, ssp-3.4.3.20050110-0, pie-8.7.7)

# cat /proc/driver/nvidia/agp/status 
Status:          Enabled
Driver:          NVIDIA
AGP Rate:        4x
Fast Writes:     Enabled
SBA:             Enabled

#cat /etc/X11/xorg.conf | grep NvAGP
    Option "NvAGP" "1"

cheers

WladyX · Post by **WladyX** » Sat Mar 12, 2005 11:08 am

make mrproper and it will work.

Naib · Post by **Naib** » Sat Mar 12, 2005 12:57 pm

mmm still laggy. I have re-compiled and turned things off.

Going back to r4-love1 for now

MyrddinEmrys · Post by **MyrddinEmrys** » Sat Mar 12, 2005 2:29 pm

I really seem to be having a bad Gentoo day... I compiled the kernel, edited lilo, rebooted... everything loaded fine, no errors... BUT...
X seems to simply freeze while starting... I just see a black screen and it goes nowhere from there on...

The weirdest part is that it now happens to both my kernels

(I kept the love1 just in case... yeah, right...)

any1 had a similar problem ? maybe some file got tempered with when it wasen't supposed to ?

Gentoonie · Post by **Gentoonie** » Sat Mar 12, 2005 2:37 pm

elocal wrote:I this kernel uncompatible with nvidia drivers 1.0.7167? I cant seem to get X started with nvidia-kernel 1.0.7167, it works fine with 1.0.6629.

I got it working with love2, so its not incompatible

mirko_3 · Post by **mirko_3** » Sat Mar 12, 2005 3:05 pm

Ok, I noticed one thing that changed since love1: when switching resolutions, my lcd has a 4-5 second delay, with the message "No Signal", before the image reappears. Any hints? Some change in -mm?

DrWoland · Post by **DrWoland** » Sat Mar 12, 2005 4:45 pm

Doing my emerge -uDv world now, nvidia 7*** is in there, we'll see how it works out.

dhaemon · Post by **dhaemon** » Sat Mar 12, 2005 5:32 pm

I've been testing love-sources a bit... To test it's stability I put it through everyday use: running "emerge world" along side a 700mb movie, with skype, |with apache2, mysql, postfix, courier-imap|(remotly used by my friends), with, amule, with firefox and on top of it all; cube...
And from what I see: On my Athlon 64 3500+(full 64bit environment) nothing crashed. The runnig speed was more than acceptable. Believe me!

I checked my /var/log/messages, nothing to report.

Linux-2.6.11-love2 is AMD64 friendly (to me).

dhaemon · Post by **dhaemon** » Sat Mar 12, 2005 5:45 pm

fallow wrote: Also update from gen4nicksched 0.02 to 0.03 is availabe here : http://vivid.dat.pl/fallow/pub/love-sou ... to-03.diff . You can now select range of Base_Timeslice . Std in love2 was a 4-256 , If You want better interactivity - choose 4-128 for example and thanks to RMH3093 for the idea of additional selection

I'm a bit confused...
Is switching to the new version(if it is) really beneficial?
Does increasing interactivity mean decreasing overall speed(as always)?

Thanks for reading

borkdox · Post by **borkdox** » Sat Mar 12, 2005 6:55 pm

Gentoonie wrote:
elocal wrote:I this kernel uncompatible with nvidia drivers 1.0.7167? I cant seem to get X started with nvidia-kernel 1.0.7167, it works fine with 1.0.6629.
I got it working with love2, so its not incompatible

I finally managed to get X started with it. But now I dont have AGP acceleration disabled. I disabled AGPGART in the kernel, so I am trying to use NVAGP.

Code: Select all

elocal@gentux64 ~ $ cat /proc/driver/nvidia/agp/status
Status:          Disabled

AGP initialization failed, please check the ouput
of the 'dmesg' command and/or your system log file
for additional information on this problem.

There is no error in dmesg or Xorg.0.log .

Any idea of what the problem is?

EDIT1:
just FYI I am running AMD64, 64bit mode, chipset is a VIA K8T800.

DrWoland · Post by **DrWoland** » Sat Mar 12, 2005 7:03 pm

elocal wrote:
Gentoonie wrote:
elocal wrote:I this kernel uncompatible with nvidia drivers 1.0.7167? I cant seem to get X started with nvidia-kernel 1.0.7167, it works fine with 1.0.6629.
I got it working with love2, so its not incompatible
I finally managed to get X started with it. But now I dont have AGP acceleration disabled. I disabled AGPGART in the kernel, so I am trying to use NVAGP.
Code: Select all
elocal@gentux64 ~ $ cat /proc/driver/nvidia/agp/status
Status:          Disabled

AGP initialization failed, please check the ouput
of the 'dmesg' command and/or your system log file
for additional information on this problem.
There is no error in dmesg or Xorg.0.log .

Any idea of what the problem is?

EDIT1:
just FYI I am running AMD64, 64bit mode, chipset is a VIA K8T800.

... do dmesg|less and scroll through there till you get to nvidia.
Hopefuly, you have a system logger enabled, so check /var/log/messages next.

borkdox · Post by **borkdox** » Sat Mar 12, 2005 7:15 pm

I just compiled AGPGART in the kernel, recompiled nvidia-kerne, and use AGPGART instead of NVAGP, its working.

I suppose there is no difference in performance between AGPGART and NVAGP, is there?

Because I am getting with these drivers, compared with the 6629, only a 10 fps increase in glxgears(dont laugh at this bech...).

My card is an 6600GT AGP8x I get 6515FPS in glxgears.

Regards.......

WladyX · Post by **WladyX** » Sat Mar 12, 2005 7:21 pm

There can be differences between the agp module used, i have the same card and it gives me around the same fps as yours.

Mafteah · Post by **Mafteah** » Sat Mar 12, 2005 10:33 pm

1) To fix oops with usb I need to unset CONFIG_GENETIC_IOSCHED_AS ?
2) What is better NVAGP or AGPGART ?

Legoguy · Post by **Legoguy** » Sun Mar 13, 2005 6:20 am

elocal wrote:I just compiled AGPGART in the kernel, recompiled nvidia-kerne, and use AGPGART instead of NVAGP, its working.

I suppose there is no difference in performance between AGPGART and NVAGP, is there?

Because I am getting with these drivers, compared with the 6629, only a 10 fps increase in glxgears(dont laugh at this bech...).

My card is an 6600GT AGP8x I get 6515FPS in glxgears.

Regards.......

Heh. Using 6629 drivers with a GeForce FX 5900, I get 6893.4 FPS.
Is it really possible that my card is faster than yours? Or is yours just bottlenecked by your CPU?

Checking with 7167 drivers now.

[edit]

Heh, cool - 7760.400 FPS with 7167.

fallow · Post by **fallow** » Sun Mar 13, 2005 12:36 pm

dhaemon wrote: I'm a bit confused...
Is switching to the new version(if it is) really beneficial?
Does increasing interactivity mean decreasing overall speed(as always)?
Thanks for reading

the lower base_timeslice benefit can be greater than other things decrese.
however with genetic nicksched base_timeslice is fluctuating all the time , so the different is less than with static timeslice. Now is possibility to choose, just try and then choose better range for U

I`m using 4-128 now.

Mafteah wrote:1) To fix oops with usb I need to unset CONFIG_GENETIC_IOSCHED_AS ?
2) What is better NVAGP or AGPGART ?

ad1) EXACTLY

, Genetic Nicksched is safe.
ad2) With 6629 I don`t saw the difference beetwen agpgart and nvagp ( also with benchmarks) with 7167 without fixes NVAGP is better , but with latest fixes ( r1 from portage ) I also don`t see the difference. However I backed to the 6629 because I have freezes with 7167 and composite. with 6629 everything is ok . I have nv answer that my card can be ...too old

-> Geforce 2 GTS ...

cheers.

Mafteah · Post by **Mafteah** » Sun Mar 13, 2005 1:14 pm

Code: Select all

$ uname -a
Linux noisy 2.6.11-love2 #1 Sun Mar 13 15:05:25 IST 2005 i686 AMD Athlon(tm)  AuthenticAMD GNU/Linux

$ cat /proc/driver/nvidia/version
NVRM version: NVIDIA Linux x86 NVIDIA Kernel Module  1.0-7167  Fri Feb 25 09:08:22 PST 2005
GCC version:  gcc version 3.4.3-20050110 (Gentoo Linux 3.4.3.20050110, ssp-3.4.3.20050110-0, pie-8.7.7)

$ cat /proc/driver/nvidia/agp/status
Status:          Enabled
Driver:          NVIDIA
AGP Rate:        4x
Fast Writes:     Disabled
SBA:             Disabled

$ glxgears
9421 frames in 5.0 seconds = 1884.200 FPS
10780 frames in 5.0 seconds = 2156.000 FPS
10780 frames in 5.0 seconds = 2156.000 FPS
10716 frames in 5.0 seconds = 2143.200 FPS

2.6.11-love2 (usb & genetic-as deplug. oops fix)

Love-sources AMD64 Friendly

Re: 2.6.11-love2 aka "The Time is Now"