| 1 |
On 26-Apr-13 18:41, Alan McKinnon wrote: |
| 2 |
> On 26/04/2013 18:37, Jarry wrote: |
| 3 |
>> On 26-Apr-13 18:11, Tanstaafl wrote: |
| 4 |
>>> compile fails with lots of |
| 5 |
>>> |
| 6 |
>>> "...error "No Module support in this kernel. Please configure with |
| 7 |
>>> CONFIG_MODULES" |
| 8 |
>>> |
| 9 |
>>> Please tell me that I'm not going to have to enable modules just so I |
| 10 |
>>> can use the vmware tools?? |
| 11 |
>> |
| 12 |
>> Yes you are. If you want to use vm-tools ("open" or "vmware"), |
| 13 |
>> you have to enable kernel modules. And also some strange options |
| 14 |
>> (i.e. vmware-graphics). And as I told you previously, updating |
| 15 |
>> to new kernel is really pain in a**. That's why I got rid of |
| 16 |
>> the whole vm-stuff and I'm happy without it... |
| 17 |
> |
| 18 |
> Are you aware of "module-rebuild rebuild"? |
| 19 |
|
| 20 |
Yes I am. Believe me or not, but this did not work. |
| 21 |
|
| 22 |
> Nice little scriplet that reduces all that pain to running one single |
| 23 |
> command after installing a new built kernel. |
| 24 |
|
| 25 |
I mean there is a problem with new kernel version. Not sure |
| 26 |
but I suppose open-vm-tools sources are installed into kernel |
| 27 |
sources tree. And if you install new kernel, open-vm-tools |
| 28 |
sources are not moved to the new kernel-sources tree. |
| 29 |
Whenever I installed new kernel-sources and re-created link |
| 30 |
/usr/src/linux pointing to the new sources, I had to re-emerge |
| 31 |
open-vm-tools too... |
| 32 |
|
| 33 |
Jarry |
| 34 |
-- |
| 35 |
_______________________________________________________________ |
| 36 |
This mailbox accepts e-mails only from selected mailing-lists! |
| 37 |
Everything else is considered to be spam and therefore deleted. |
Archives