Re: kernel org: 2.6.36 is stable
Hugo Vanwoerkom wrote:
Hugo Vanwoerkom wrote:
Hugo Vanwoerkom wrote:
Hi,
Kernel org has 2.6.36 as stable.
Anybody tried that?
I tried it, with success ;-)
Had to install Nvidia driver 260.19.12 instead of 195.36.24 because
the latter gets an error.
and VMware-Player-3.1.2-301548 does not compile. Of course not.
This is stupid of course. The error I got was:
/tmp/vmware-root/modules/vmmon-only/linux/hostif.c: In function
'HostIFDoIoctl':
/tmp/vmware-root/modules/vmmon-only/linux/hostif.c:3706: error: 'const
struct file_operations' has no member named 'ioctl'
/tmp/vmware-root/modules/vmmon-only/linux/hostif.c:3710: error: 'const
struct file_operations' has no member named 'ioctl'
Well, in /usr/lib/vmware/modules/source I do: 'tar xf vmmon.tar'
and in /usr/lib/vmware/modules/source/vmmon-only/linux/hostif.c line
#3677 the error is bracketed by an '#ifndef VMMON_USE_HIGH_RES_TIMERS'
and that 'VMMON_USE_HIGH_RES_TIMERS' is set when CONFIG_HIGH_RES_TIMERS
is set.
That is the kernel option in 'processor type and features' -> High
Resolution Timer Support.
I don't have that set. Why not? I don't recall and my system
installation blog doesn't have anything about that.
So I set it and recompile the kernel. Then I redo:
vmware-modconfig --console --install-all
and the error goes away... ;-)
This brings up 2 items: I wished I had the history of my kernel options,
why are things set or not set? Let's see what other sideeffects are
caused by CONFIG_HIGH_RES_TIMERS=y
Secondly vmware, come on boys, I have to do this mickey mouse to get
your products to work?
Hugo
Reply to: