If a kernel change fixed it, it's probably not as much a valve issue than the rather.. Linux tends to change it's VM etc per every release, so I'm not surprised.
At 11:04 PM 7/24/2006, [EMAIL PROTECTED] wrote:
Greetings For everyone else who was affected by this problem some time ago: Changing the OS from Suse 10.0 to 10.1 (which has a nice and new kernel) solved it for me. I don't know how much cpu I would use with v29, but the cpu usage is so low now, that I can even run v35 without problems. And since valve wasn't very interested in fixing this bug anyway.. just update your kernel to the newest stable version, install a newer Version of your OS, or another OS. As said, Suse 10.1 works nice for me. bye _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
_______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
