Printable View
Hi All
I finally got around to downloading and HD installing the latest Knoppix 3.4 with the 2.6.6 kernel.
Obviously this is completely subjective, but somehow it does actually "feel" faster. In particular, the mouse seems much more responsive and moves faster than before.
Has anybody else noticed any difference?
tearinghairout,
Yes... I have...
Having GKrellm running on the desktop, I see lots of things that have changed with the new kernel - mostly, I never see the CPU go over 30 to 40% usage, on average, it never goes above 12 to 15%...
Programs tend to appear to run faster, even though the "window" pop-up seems to take a little longer - you get the "bouncing mouse cursor" a little longer than I felt in previous kernel releases...
But, noticable change is in XBoing - the program now goes so fast, the sound is unrecognizable, and the game is completely unplayable - due to excessive speed. I've tried to change the program "speed" to its slowest setting, a 1, and it is still unplayable because it runs too fast. XBoing being a "clone" game of BrickOut (r) - you need to maintain the ball by using your paddle to keep it "breaking up" the bricks in a pattern above you, the ball, paddle, and the bricks, go so fast, you can't keep up with it... I've just settled to not playing the game, because of this, and chocked it up to the speed of the kernel - since I played the game with my old kernel v2.4.22 and it was fine, sounds were fine, and the playing was at a game speed of say, 6...
Other than this, I think the speed is great... I am just worrying about it a little... Way back, in the days of ISA ( 8 bit cards ), if your processor ran too quickly, it could easilly "speed" by a card. It would send a communication to a card, but the speed was so quick, the card never "heard" a word, and thus, you would have device / communication problems. Not sure if this could be the "same" problem here, but, the speed could become an issue... ( just my thoughts )
Ms. Cuddles
Haven't been using 2.6; no built-in support for wheelmouse. I read somewhere of a workaround to get wheelmouse working but it's easier just to stick with the 2.4 kernel.Quote:
Originally Posted by tearinghairout
If I'm not mistaken thats just the KDE startup notification that is set by default for somethinhg like 30 seconds!Quote:
Originally Posted by Cuddles
I have the kernel 2.6.6, and a mouse with the scroll wheel, and it works fine... And I think the mouse is setup, from the install, as a generic mouse too...Quote:
Originally Posted by CrashedAgain
Not sure on "technology" things at the time, is a wheel-mouse what I am talking about, or is it something that has more than one scroll-wheel? A friend has one, it can scroll both up and down, and side to side - mine only has the vertical. But it works fine in the new kernel...
Clueless,
Ms. Cuddles
Wheelmice work fine as it is not kernel related. Have a look at /etc/X11/XF86Config-4. ;)Quote:
Originally Posted by CrashedAgain
This is for my USB mouse (with scrollwheel). :)
$ uname -aCode:Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "Emulate3Buttons" "true"
Option "ZAxisMapping" "4 5"
EndSection
Linux cromag 2.6.8-rc2 #2 Thu Jul 22 16:13:51 MDT 2004 i686 GNU/Linux
This thread is getting old, I should check more often!
What are you doing different than me? Here is my XF86Config-4:
When I boot with the 2.4 kernel, the scroll wheel works. When I boot with the 2.6 kernel, it does not. XFConfig is unchanged.Code:Section "InputDevice"
Identifier "PS/2 Mouse"
Driver "mouse"
Option "Protocol" "auto"
Option "ZAxisMapping" "4 5"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "true"
Option "Emulate3Timeout" "70"
Option "SendCoreEvents" "true"
EndSection
I have also tried the suggestions in these threads:
http://www.knoppix.net/forum/viewtop...ght=wheelmouse
http://www.knoppix.net/forum/viewtop...ght=wheelmouse
Mouse is a generic PS2 single scroll wheel mouse.
Here's my /etc/X11/XF86Config-4. The key is:
Option "Device" "/dev/input/mice"
Code:Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "Emulate3Buttons" "true"
Option "ZAxisMapping" "4 5"
EndSection
Hmmmm. OK, I tried:
Code:Section "InputDevice"
Identifier "PS/2 Mouse"
Driver "mouse"
Option "Protocol" "auto"
Option "ZAxisMapping" "4 5"
# Option "Device" "/dev/psaux"
Option "Device" "/dev/input/mice"
Option "Emulate3Buttons" "true"
Option "Emulate3Timeout" "70"
Option "SendCoreEvents" "true"
EndSection
Result: Still no scroll wheel function with the 2.6 kernel but now the mouse is very jumpy & needed to be reconfigured slower.
XF86Config already had:
but I'm using a PS2 connection not USB. I don't think you can use 'device=' option twiceCode:Section "InputDevice"
Identifier "USB Mouse"
Driver "mouse"
Option "Device" "/dev/input/mice"
Option "SendCoreEvents" "true"
Option "Protocol" "IMPS/2"
Option "ZAxisMapping" "4 5"
Option "Buttons" "5"
EndSection
ie not comment out the /dev/psaux line can you...maybe I'll try it, worst it can do is freeze up solid!
Didn't freeze up but still no scroll wheel either. It seems to be something with the 2.6 kernel; 2.4 works OK.
Methinks all you need to change is the Protocol and the above should work. IIRC 'auto' doesn't work w/ 2.6.*Quote:
Originally Posted by CrashedAgain
CrashedAgain,
Here is what I have for my PS/2 Mouse, which is a wheel mouse, connected to my PS/2 port connector, and its just a "generic" wheel mouse - It doesn't even say the manufacturer on the durn mouse, thats how "generic" it is - but I get scroll "up and down" in Konq., Mozilla, Spreadsheets, Word Processors, and mail... Here's my XF86Config-4 "snippet"
I've never touched a thing, from the hard drive install of kernel 2.6.6 w/ Knoppix v3.4 - so this is "un-tainted" code...Code:Section "InputDevice"
Identifier "PS/2 Mouse"
Driver "mouse"
Option "Protocol" "auto"
Option "ZAxisMapping" "4 5"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "true"
Option "Emulate3Timeout" "70"
Option "SendCoreEvents" "true"
EndSection
Hope this helps,
Ms. Cuddles
My impression of the 2.6 kernel is that it doesn't do the suspend to ram as good as the 2.4 kernel. That, the usb bug, and the memory epplet breakage are the chief reasons why I'm not using 2.6. I have a modified 2.4.26 with a modified xfree86 savage server running dri that enables my 2.4 kernel to run with nearly the same speed and responsiveness of the 2.6 kernel. Plus, it doesn't have the exploit bug that I tried to crash it with, so for now, this 2.4 kernel does it for me.
Got it working. The key is:
Option "Protocol" "IMPS/2"
Thanks for the help.
The 2.6 is certainly going though a fast development
cycle. The only quirk I've found is with s/w that
relys on the kernels system calls to query the
boot sectors table geometry, via the MBR. But then,
my bios is old, and only deals in 24 bit geometry,
aka, 255 heads.
It hasn't been a problem, but i had to update my
Lilo to the latest version to get it to update
it's table in 2.6.x smoothly... It would always
respond with a fatal warning about geometry
miss-matches :).
The whole system runs considerably faster though.
I use the "spirals" screen saver from the
xscreensaver collection... with the 2.4.x kernel
it was quite hypnotic, but with the 2.6.7 it runs
like a rocket. Very happy :).
The 2.6.x pre-empts and scheduals (sic) more
efficiently i believe. It is a development kernel
though, in spite of the even minor number. And so,
needs to be followed on that score.
Running knoppix v3.3, that i copied over directly
from a LiveCD to disk, and using the 2.6.7,
from another Linux (deb). There's been marked
improvement in performance.
I'm fascinated to know what you mean though by...
Durand Hicks wrote:
>>
My impression of the 2.6 kernel is that it doesn't do the suspend to ram as good as the 2.4 kernel. That, the usb bug, and the memory epplet breakage are the chief reasons why I'm not using 2.6.
>>
???
>>
I have a modified 2.4.26 with a modified xfree86 savage server running dri that enables my 2.4 kernel to run with nearly the same speed and responsiveness of the 2.6 kernel.
>>
Modifications... do you mean the pre-emptive patches
for 2.4.x. I have those, but possibly not
all. And the 2.4.24 is noticeably slower, though
faster than with out the patches.
>>
Plus, it doesn't have the exploit bug that I tried to crash it with, so for now, this 2.4 kernel does it for me.
>>
Maybe thats been fixed ???
jm