Instalação vmware fedora 6

[Patrick]

Olá,
Bom, eu tinha o vmware funcionando direitinho, depoix de atualizar o fc5 
pra o fc6 com o yum, dai somente fiz esse comando ali e volto a 
funciona, mas eu consegui o cd do fc 6 e botei pra atualiza pensando que 
poderia faze alguma diferença, e fez, desatualizo alguns pacotes e o 
kernel. Então atualizei tudo novamento com o yum e fui tenta faze 
funciona o vmware novamente e estou tento o seguinte erro:

[root@localhost ~]# vmware-config.pl -d
Making sure services for VMware Workstation are stopped.

Stopping VMware services:
Virtual machine monitor [ OK ]

Configuring fallback GTK+ 2.4 libraries.

In which directory do you want to install the mime type icons?
[/usr/share/icons]

What directory contains your desktop menu entry files? These files have a
.desktop file extension. [/usr/share/applications]

In which directory do you want to install the application's icon?
[/usr/share/pixmaps]

Trying to find a suitable vmmon module for your running kernel.

None of the pre-built vmmon modules for VMware Workstation is suitable 
for your
running kernel. Do you want this program to try to build the vmmon 
module for
your system (you need to have a C compiler installed on your system)? [yes]

Using compiler "/usr/bin/gcc". Use environment variable CC to override.

What is the location of the directory of C header files that match your 
running
kernel? [/usr/src/kernels/2.6.20-1.2933.fc6-i686/include]

Extracting the sources of the vmmon module.

Building the vmmon module.

Building for VMware Workstation 5.5.2 or 5.5.3.
Using 2.6.x kernel build system.
make: Entrando no diretório `/tmp/vmware-config13/vmmon-only'
make -C /usr/src/kernels/2.6.20-1.2933.fc6-i686/include/.. SUBDIRS=$PWD 
SRCROOT=$PWD/. modules
make[1]: Entrando no diretório `/usr/src/kernels/2.6.20-1.2933.fc6-i686'
CC [M] /tmp/vmware-config13/vmmon-only/linux/driver.o
CC [M] /tmp/vmware-config13/vmmon-only/linux/hostif.o
CC [M] /tmp/vmware-config13/vmmon-only/common/cpuid.o
CC [M] /tmp/vmware-config13/vmmon-only/common/hash.o
CC [M] /tmp/vmware-config13/vmmon-only/common/memtrack.o
CC [M] /tmp/vmware-config13/vmmon-only/common/phystrack.o
CC [M] /tmp/vmware-config13/vmmon-only/common/task.o
cc1plus: warning: command line option 
"-Werror-implicit-function-declaration" is valid for C/ObjC but not for C++
cc1plus: warning: command line option "-Wdeclaration-after-statement" is 
valid for C/ObjC but not for C++
cc1plus: warning: command line option "-Wno-pointer-sign" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
Ada/C/ObjC but not for C++
cc1plus: warning: command line option "-ffreestanding" is valid for 
C/ObjC but not for C++
/tmp/vmware-config13/vmmon-only/common/task_compat.h: In function ‘int 
Vmx86_RunVM(VMCrossPage*, VMDriver*) [with VMCrossPage = VMCrossPageV321]’:
/tmp/vmware-config13/vmmon-only/common/task_compat.h:1522: warning: 
‘sysenterState.SysenterStateV45::rsp’ is used uninitialized in this function
/tmp/vmware-config13/vmmon-only/common/task_compat.h:1523: warning: 
‘sysenterState.SysenterStateV45::rip’ is used uninitialized in this function
/tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning: 
‘sysenterState.SysenterStateV45::validEIP’ may be used uninitialized in 
this function
/tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning: 
‘sysenterState.SysenterStateV45::cs’ may be used uninitialized in this 
function
/tmp/vmware-config13/vmmon-only/common/task_compat.h: In function ‘int 
Vmx86_RunVM(VMCrossPage*, VMDriver*) [with VMCrossPage = VMCrossPageV3]’:
/tmp/vmware-config13/vmmon-only/common/task_compat.h:1522: warning: 
‘sysenterState.SysenterStateV45::rsp’ is used uninitialized in this function
/tmp/vmware-config13/vmmon-only/common/task_compat.h:1523: warning: 
‘sysenterState.SysenterStateV45::rip’ is used uninitialized in this function
/tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning: 
‘sysenterState.SysenterStateV45::validEIP’ may be used uninitialized in 
this function
/tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning: 
‘sysenterState.SysenterStateV45::cs’ may be used uninitialized in this 
function
/tmp/vmware-config13/vmmon-only/common/task_compat.h: In function ‘int 
Vmx86_RunVM(VMCrossPage*, VMDriver*) [with VMCrossPage = VMCrossPageGSX1]’:
/tmp/vmware-config13/vmmon-only/common/task_compat.h:1522: warning: 
‘sysenterState.SysenterStateV45::rsp’ is used uninitialized in this function
/tmp/vmware-config13/vmmon-only/common/task_compat.h:1523: warning: 
‘sysenterState.SysenterStateV45::rip’ is used uninitialized in this function
/tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning: 
‘sysenterState.SysenterStateV45::validEIP’ may be used uninitialized in 
this function
/tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning: 
‘sysenterState.SysenterStateV45::cs’ may be used uninitialized in this 
function
/tmp/vmware-config13/vmmon-only/common/task_compat.h: In function ‘int 
Vmx86_RunVM(VMCrossPage*, VMDriver*) [with VMCrossPage = VMCrossPageV2]’:
/tmp/vmware-config13/vmmon-only/common/task_compat.h:1522: warning: 
‘sysenterState.SysenterStateV45::rsp’ is used uninitialized in this function
/tmp/vmware-config13/vmmon-only/common/task_compat.h:1523: warning: 
‘sysenterState.SysenterStateV45::rip’ is used uninitialized in this function
/tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning: 
‘sysenterState.SysenterStateV45::validEIP’ may be used uninitialized in 
this function
/tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning: 
‘sysenterState.SysenterStateV45::cs’ may be used uninitialized in this 
function
/tmp/vmware-config13/vmmon-only/common/task_compat.h: In function ‘int 
Vmx86_RunVM_V4(VMDriver*, Vcpuid) [with VMCrossPage = VMCrossPageV4]’:
/tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning: 
‘sysenterState.SysenterStateV45::validEIP’ may be used uninitialized in 
this function
/tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning: 
‘sysenterState.SysenterStateV45::cs’ may be used uninitialized in this 
function
/tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning: 
‘sysenterState.SysenterStateV45::rsp’ may be used uninitialized in this 
function
/tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning: 
‘sysenterState.SysenterStateV45::rip’ may be used uninitialized in this 
function
/tmp/vmware-config13/vmmon-only/common/task_compat.h: In function ‘int 
Vmx86_RunVM(VMDriver*, Vcpuid)’:
/tmp/vmware-config13/vmmon-only/common/task_compat.h:1522: warning: 
‘sysenterState.SysenterStateV45::rsp’ is used uninitialized in this function
/tmp/vmware-config13/vmmon-only/common/task_compat.h:1523: warning: 
‘sysenterState.SysenterStateV45::rip’ is used uninitialized in this function
/tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning: 
‘sysenterState.SysenterStateV45::validEIP’ may be used uninitialized in 
this function
/tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning: 
‘sysenterState.SysenterStateV45::cs’ may be used uninitialized in this 
function
/tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning: 
‘sysenterState.SysenterStateV45::validEIP’ may be used uninitialized in 
this function
/tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning: 
‘sysenterState.SysenterStateV45::cs’ may be used uninitialized in this 
function
/tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning: 
‘sysenterState.SysenterStateV45::rsp’ may be used uninitialized in this 
function
/tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning: 
‘sysenterState.SysenterStateV45::rip’ may be used uninitialized in this 
function
/tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning: 
‘sysenterState.SysenterStateV45::validEIP’ may be used uninitialized in 
this function
/tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning: 
‘sysenterState.SysenterStateV45::cs’ may be used uninitialized in this 
function
/tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning: 
‘sysenterState.SysenterStateV45::rsp’ may be used uninitialized in this 
function
/tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning: 
‘sysenterState.SysenterStateV45::rip’ may be used uninitialized in this 
function
/tmp/vmware-config13/vmmon-only/common/task_compat.h: In function ‘void 
Task_Switch_V45(VMDriver*, Vcpuid)’:
/tmp/vmware-config13/vmmon-only/common/task_compat.h:1713: warning: 
‘sysenterState.SysenterStateV45::validEIP’ may be used uninitialized in 
this function
/tmp/vmware-config13/vmmon-only/common/task_compat.h:1713: warning: 
‘sysenterState.SysenterStateV45::cs’ may be used uninitialized in this 
function
/tmp/vmware-config13/vmmon-only/common/task_compat.h:1713: warning: 
‘sysenterState.SysenterStateV45::rsp’ may be used uninitialized in this 
function
/tmp/vmware-config13/vmmon-only/common/task_compat.h:1713: warning: 
‘sysenterState.SysenterStateV45::rip’ may be used uninitialized in this 
function
CC [M] /tmp/vmware-config13/vmmon-only/common/vmx86.o
CC [M] /tmp/vmware-config13/vmmon-only/vmcore/compat.o
CC [M] /tmp/vmware-config13/vmmon-only/vmcore/moduleloop.o
LD [M] /tmp/vmware-config13/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-config13/vmmon-only/vmmon.mod.o
LD [M] /tmp/vmware-config13/vmmon-only/vmmon.ko
make[1]: Saindo do diretório `/usr/src/kernels/2.6.20-1.2933.fc6-i686'
cp -f vmmon.ko ./../vmmon.o
make: Saindo do diretório `/tmp/vmware-config13/vmmon-only'
Unable to make a vmmon module that can be loaded in the running kernel:
insmod: error inserting '/tmp/vmware-config13/vmmon.o': -1 Invalid 
module format
There is probably a slight difference in the kernel configuration 
between the
set of C header files you specified and your running kernel. You may want to
rebuild a kernel based on that directory, or specify another directory.

For more information on how to troubleshoot module-related problems, please
visit our Web site at 
"http://www.vmware.com/download/modules/modules.html" and
"http://www.vmware.com/support/reference/linux/prebuilt_modules_linux.html".

Execution aborted.
[root@localhost ~]#

Eu já desintalei e instalei novamente mas continuo o mesmo problema!

Alguém poderia me ajudar?

PaTricK

[Robert Pereira]

Patrick.

Este trecho do erro de compilação lhe dá a resposta:

Unable to make a vmmon module that can be loaded in the running kernel:
insmod: error inserting '/tmp/vmware-config13/vmmon.o': -1 Invalid
module format
There is probably a slight difference in the kernel configuration
between the
set of C header files you specified and your running kernel.

Você possui o pacote kernel-devel-2.6.20-1.2933.fc6-i686 instalado, mas no
momento da compilação dos módulos do VMware você estava executando o kernel
com uma versão diferente.
Instale o kernel-2.6.20-1.2933.fc6-i686 e inicie o sistema usando ele, ai
sim execute novamente o comando vmware-config.pl.

2007/4/3, PaTricK :
> Olá,
> Bom, eu tinha o vmware funcionando direitinho, depoix de atualizar o fc5
> pra o fc6 com o yum, dai somente fiz esse comando ali e volto a
> funciona, mas eu consegui o cd do fc 6 e botei pra atualiza pensando que
> poderia faze alguma diferença, e fez, desatualizo alguns pacotes e o
> kernel. Então atualizei tudo novamento com o yum e fui tenta faze
> funciona o vmware novamente e estou tento o seguinte erro:
>
> [root@localhost ~]# vmware-config.pl -d
> Making sure services for VMware Workstation are stopped.
>
> Stopping VMware services:
> Virtual machine monitor [ OK ]
>
> Configuring fallback GTK+ 2.4 libraries.
>
> In which directory do you want to install the mime type icons?
> [/usr/share/icons]
>
> What directory contains your desktop menu entry files? These files have a
> .desktop file extension. [/usr/share/applications]
>
> In which directory do you want to install the application's icon?
> [/usr/share/pixmaps]
>
> Trying to find a suitable vmmon module for your running kernel.
>
> None of the pre-built vmmon modules for VMware Workstation is suitable
> for your
> running kernel. Do you want this program to try to build the vmmon
> module for
> your system (you need to have a C compiler installed on your system)?
> [yes]
>
> Using compiler "/usr/bin/gcc". Use environment variable CC to override.
>
> What is the location of the directory of C header files that match your
> running
> kernel? [/usr/src/kernels/2.6.20-1.2933.fc6-i686/include]
>
> Extracting the sources of the vmmon module.
>
> Building the vmmon module.
>
> Building for VMware Workstation 5.5.2 or 5.5.3.
> Using 2.6.x kernel build system.
> make: Entrando no diretório `/tmp/vmware-config13/vmmon-only'
> make -C /usr/src/kernels/2.6.20-1.2933.fc6-i686/include/.. SUBDIRS=$PWD
> SRCROOT=$PWD/. modules
> make[1]: Entrando no diretório `/usr/src/kernels/2.6.20-1.2933.fc6-i686'
> CC [M] /tmp/vmware-config13/vmmon-only/linux/driver.o
> CC [M] /tmp/vmware-config13/vmmon-only/linux/hostif.o
> CC [M] /tmp/vmware-config13/vmmon-only/common/cpuid.o
> CC [M] /tmp/vmware-config13/vmmon-only/common/hash.o
> CC [M] /tmp/vmware-config13/vmmon-only/common/memtrack.o
> CC [M] /tmp/vmware-config13/vmmon-only/common/phystrack.o
> CC [M] /tmp/vmware-config13/vmmon-only/common/task.o
> cc1plus: warning: command line option
> "-Werror-implicit-function-declaration" is valid for C/ObjC but not for
> C++
> cc1plus: warning: command line option "-Wdeclaration-after-statement" is
> valid for C/ObjC but not for C++
> cc1plus: warning: command line option "-Wno-pointer-sign" is valid for
> C/ObjC but not for C++
> cc1plus: warning: command line option "-Wstrict-prototypes" is valid for
> Ada/C/ObjC but not for C++
> cc1plus: warning: command line option "-ffreestanding" is valid for
> C/ObjC but not for C++
> /tmp/vmware-config13/vmmon-only/common/task_compat.h: In function 'int
> Vmx86_RunVM(VMCrossPage*, VMDriver*) [with VMCrossPage =
> VMCrossPageV321]':
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:1522: warning:
> 'sysenterState.SysenterStateV45::rsp' is used uninitialized in this
> function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:1523: warning:
> 'sysenterState.SysenterStateV45::rip' is used uninitialized in this
> function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> 'sysenterState.SysenterStateV45::validEIP' may be used uninitialized in
> this function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> 'sysenterState.SysenterStateV45::cs' may be used uninitialized in this
> function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h: In function 'int
> Vmx86_RunVM(VMCrossPage*, VMDriver*) [with VMCrossPage = VMCrossPageV3]':
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:1522: warning:
> 'sysenterState.SysenterStateV45::rsp' is used uninitialized in this
> function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:1523: warning:
> 'sysenterState.SysenterStateV45::rip' is used uninitialized in this
> function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> 'sysenterState.SysenterStateV45::validEIP' may be used uninitialized in
> this function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> 'sysenterState.SysenterStateV45::cs' may be used uninitialized in this
> function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h: In function 'int
> Vmx86_RunVM(VMCrossPage*, VMDriver*) [with VMCrossPage =
> VMCrossPageGSX1]':
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:1522: warning:
> 'sysenterState.SysenterStateV45::rsp' is used uninitialized in this
> function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:1523: warning:
> 'sysenterState.SysenterStateV45::rip' is used uninitialized in this
> function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> 'sysenterState.SysenterStateV45::validEIP' may be used uninitialized in
> this function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> 'sysenterState.SysenterStateV45::cs' may be used uninitialized in this
> function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h: In function 'int
> Vmx86_RunVM(VMCrossPage*, VMDriver*) [with VMCrossPage = VMCrossPageV2]':
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:1522: warning:
> 'sysenterState.SysenterStateV45::rsp' is used uninitialized in this
> function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:1523: warning:
> 'sysenterState.SysenterStateV45::rip' is used uninitialized in this
> function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> 'sysenterState.SysenterStateV45::validEIP' may be used uninitialized in
> this function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> 'sysenterState.SysenterStateV45::cs' may be used uninitialized in this
> function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h: In function 'int
> Vmx86_RunVM_V4(VMDriver*, Vcpuid) [with VMCrossPage = VMCrossPageV4]':
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> 'sysenterState.SysenterStateV45::validEIP' may be used uninitialized in
> this function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> 'sysenterState.SysenterStateV45::cs' may be used uninitialized in this
> function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> 'sysenterState.SysenterStateV45::rsp' may be used uninitialized in this
> function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> 'sysenterState.SysenterStateV45::rip' may be used uninitialized in this
> function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h: In function 'int
> Vmx86_RunVM(VMDriver*, Vcpuid)':
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:1522: warning:
> 'sysenterState.SysenterStateV45::rsp' is used uninitialized in this
> function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:1523: warning:
> 'sysenterState.SysenterStateV45::rip' is used uninitialized in this
> function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> 'sysenterState.SysenterStateV45::validEIP' may be used uninitialized in
> this function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> 'sysenterState.SysenterStateV45::cs' may be used uninitialized in this
> function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> 'sysenterState.SysenterStateV45::validEIP' may be used uninitialized in
> this function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> 'sysenterState.SysenterStateV45::cs' may be used uninitialized in this
> function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> 'sysenterState.SysenterStateV45::rsp' may be used uninitialized in this
> function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> 'sysenterState.SysenterStateV45::rip' may be used uninitialized in this
> function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> 'sysenterState.SysenterStateV45::validEIP' may be used uninitialized in
> this function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> 'sysenterState.SysenterStateV45::cs' may be used uninitialized in this
> function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> 'sysenterState.SysenterStateV45::rsp' may be used uninitialized in this
> function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> 'sysenterState.SysenterStateV45::rip' may be used uninitialized in this
> function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h: In function 'void
> Task_Switch_V45(VMDriver*, Vcpuid)':
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:1713: warning:
> 'sysenterState.SysenterStateV45::validEIP' may be used uninitialized in
> this function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:1713: warning:
> 'sysenterState.SysenterStateV45::cs' may be used uninitialized in this
> function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:1713: warning:
> 'sysenterState.SysenterStateV45::rsp' may be used uninitialized in this
> function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:1713: warning:
> 'sysenterState.SysenterStateV45::rip' may be used uninitialized in this
> function
> CC [M] /tmp/vmware-config13/vmmon-only/common/vmx86.o
> CC [M] /tmp/vmware-config13/vmmon-only/vmcore/compat.o
> CC [M] /tmp/vmware-config13/vmmon-only/vmcore/moduleloop.o
> LD [M] /tmp/vmware-config13/vmmon-only/vmmon.o
> Building modules, stage 2.
> MODPOST 1 modules
> CC /tmp/vmware-config13/vmmon-only/vmmon.mod.o
> LD [M] /tmp/vmware-config13/vmmon-only/vmmon.ko
> make[1]: Saindo do diretório `/usr/src/kernels/2.6.20-1.2933.fc6-i686'
> cp -f vmmon.ko ./../vmmon.o
> make: Saindo do diretório `/tmp/vmware-config13/vmmon-only'
> Unable to make a vmmon module that can be loaded in the running kernel:
> insmod: error inserting '/tmp/vmware-config13/vmmon.o': -1 Invalid
> module format
> There is probably a slight difference in the kernel configuration
> between the
> set of C header files you specified and your running kernel. You may want
> to
> rebuild a kernel based on that directory, or specify another directory.
>
> For more information on how to troubleshoot module-related problems,
> please
> visit our Web site at
> "http://www.vmware.com/download/modules/modules.html" and
> "http://www.vmware.com/support/reference/linux/prebuilt_modules_linux.html
> ".
>
> Execution aborted.
> [root@localhost ~]#
>
> Eu já desintalei e instalei novamente mas continuo o mesmo problema!
>
> Alguém poderia me ajudar?
>
> PaTricK
>
> --
> Fedora-users-br mailing list
> [e-mail]
> https://www.redhat.com/mailman/listinfo/fedora-users-br

[Patrick]

Olá,
Eu tenho essa versao do kernel instalada. mostra até nesse paremetro:

What is the location of the directory of C header files that match your
running
kernel? [/usr/src/kernels/2.6.20-1.2933.fc6-i686/include]

Robert Pereira escreveu:
> Patrick.
>
> Este trecho do erro de compilação lhe dá a resposta:
>
> Unable to make a vmmon module that can be loaded in the running kernel:
> insmod: error inserting '/tmp/vmware-config13/vmmon.o'
> : -1 Invalid
> module format
> There is probably a slight difference in the kernel configuration
> between the
> set of C header files you specified and your running kernel.
>
> Você possui o pacote kernel-devel-2.6.20-1.2933.fc6-i686 instalado, 
> mas no momento da compilação dos módulos do VMware você estava 
> executando o kernel com uma versão diferente.
> Instale o kernel-2.6.20-1.2933.fc6-i686 e inicie o sistema usando ele, 
> ai sim execute novamente o comando vmware-config.pl.
>
> 2007/4/3, PaTricK <[e-mail] 
> >:
> Olá,
> Bom, eu tinha o vmware funcionando direitinho, depoix de atualizar
> o fc5
> pra o fc6 com o yum, dai somente fiz esse comando ali e volto a
> funciona, mas eu consegui o cd do fc 6 e botei pra atualiza
> pensando que
> poderia faze alguma diferença, e fez, desatualizo alguns pacotes e o
> kernel. Então atualizei tudo novamento com o yum e fui tenta faze
> funciona o vmware novamente e estou tento o seguinte erro:
>
> [root@localhost ~]# vmware-config.pl -d
> Making sure services for VMware Workstation are stopped.
>
> Stopping VMware services:
> Virtual machine monitor [ OK ]
>
> Configuring fallback GTK+ 2.4 libraries.
>
> In which directory do you want to install the mime type icons?
> [/usr/share/icons]
>
> What directory contains your desktop menu entry files? These files
> have a
> .desktop file extension. [/usr/share/applications]
>
> In which directory do you want to install the application's icon?
> [/usr/share/pixmaps]
>
> Trying to find a suitable vmmon module for your running kernel.
>
> None of the pre-built vmmon modules for VMware Workstation is suitable
> for your
> running kernel. Do you want this program to try to build the vmmon
> module for
> your system (you need to have a C compiler installed on your
> system)? [yes]
>
> Using compiler "/usr/bin/gcc". Use environment variable CC to
> override.
>
> What is the location of the directory of C header files that match
> your
> running
> kernel? [/usr/src/kernels/2.6.20-1.2933.fc6-i686/include]
>
> Extracting the sources of the vmmon module.
>
> Building the vmmon module.
>
> Building for VMware Workstation 5.5.2 or 5.5.3.
> Using 2.6.x kernel build system.
> make: Entrando no diretório `/tmp/vmware-config13/vmmon-only'
> make -C /usr/src/kernels/2.6.20-1.2933.fc6-i686/include/..
> SUBDIRS=$PWD
> SRCROOT=$PWD/. modules
> make[1]: Entrando no diretório `/usr/src/kernels/2.6.20-
> 1.2933.fc6-i686'
> CC [M] /tmp/vmware-config13/vmmon-only/linux/driver.o
> CC [M] /tmp/vmware-config13/vmmon-only/linux/hostif.o
> CC [M] /tmp/vmware-config13/vmmon-only/common/cpuid.o
> CC [M] /tmp/vmware-config13/vmmon-only/common/hash.o
> CC [M] /tmp/vmware-config13/vmmon-only/common/memtrack.o
> CC [M] /tmp/vmware-config13/vmmon-only/common/phystrack.o
> CC [M] /tmp/vmware-config13/vmmon-only/common/task.o
> cc1plus: warning: command line option
> "-Werror-implicit-function-declaration" is valid for C/ObjC but
> not for C++
> cc1plus: warning: command line option
> "-Wdeclaration-after-statement" is
> valid for C/ObjC but not for C++
> cc1plus: warning: command line option "-Wno-pointer-sign" is valid
> for
> C/ObjC but not for C++
> cc1plus: warning: command line option "-Wstrict-prototypes" is
> valid for
> Ada/C/ObjC but not for C++
> cc1plus: warning: command line option "-ffreestanding" is valid for
> C/ObjC but not for C++
> /tmp/vmware-config13/vmmon-only/common/task_compat.h: In function 'int
> Vmx86_RunVM(VMCrossPage*, VMDriver*) [with VMCrossPage =
> VMCrossPageV321]':
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:1522: warning:
> 'sysenterState.SysenterStateV45::rsp' is used uninitialized in
> this function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:1523: warning:
> 'sysenterState.SysenterStateV45::rip' is used uninitialized in
> this function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> 'sysenterState.SysenterStateV45::validEIP' may be used
> uninitialized in
> this function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> 'sysenterState.SysenterStateV45::cs' may be used uninitialized in this
> function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h: In function 'int
> Vmx86_RunVM(VMCrossPage*, VMDriver*) [with VMCrossPage =
> VMCrossPageV3]':
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:1522: warning:
> 'sysenterState.SysenterStateV45::rsp' is used uninitialized in
> this function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:1523: warning:
> 'sysenterState.SysenterStateV45::rip' is used uninitialized in
> this function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> 'sysenterState.SysenterStateV45::validEIP' may be used
> uninitialized in
> this function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> 'sysenterState.SysenterStateV45::cs' may be used uninitialized in this
> function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h: In function
> 'int
> Vmx86_RunVM(VMCrossPage*, VMDriver*) [with VMCrossPage =
> VMCrossPageGSX1]':
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:1522: warning:
> 'sysenterState.SysenterStateV45::rsp' is used uninitialized in
> this function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:1523: warning:
> 'sysenterState.SysenterStateV45::rip' is used uninitialized in
> this function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> 'sysenterState.SysenterStateV45::validEIP' may be used
> uninitialized in
> this function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> 'sysenterState.SysenterStateV45::cs' may be used uninitialized in
> this
> function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h: In function 'int
> Vmx86_RunVM(VMCrossPage*, VMDriver*) [with VMCrossPage =
> VMCrossPageV2]':
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:1522: warning:
> 'sysenterState.SysenterStateV45::rsp' is used uninitialized in
> this function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:1523: warning:
> 'sysenterState.SysenterStateV45::rip' is used uninitialized in
> this function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> 'sysenterState.SysenterStateV45::validEIP' may be used
> uninitialized in
> this function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> 'sysenterState.SysenterStateV45::cs' may be used uninitialized in this
> function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h: In function 'int
> Vmx86_RunVM_V4(VMDriver*, Vcpuid) [with VMCrossPage =
> VMCrossPageV4]':
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> 'sysenterState.SysenterStateV45::validEIP' may be used
> uninitialized in
> this function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> 'sysenterState.SysenterStateV45::cs' may be used uninitialized in this
> function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> 'sysenterState.SysenterStateV45::rsp' may be used uninitialized in
> this
> function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> 'sysenterState.SysenterStateV45::rip' may be used uninitialized in
> this
> function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h: In function
> 'int
> Vmx86_RunVM(VMDriver*, Vcpuid)':
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:1522: warning:
> 'sysenterState.SysenterStateV45::rsp' is used uninitialized in
> this function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:1523: warning:
> 'sysenterState.SysenterStateV45::rip' is used uninitialized in
> this function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> 'sysenterState.SysenterStateV45::validEIP' may be used
> uninitialized in
> this function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> 'sysenterState.SysenterStateV45::cs' may be used uninitialized in this
> function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> 'sysenterState.SysenterStateV45::validEIP' may be used
> uninitialized in
> this function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> 'sysenterState.SysenterStateV45::cs' may be used uninitialized in
> this
> function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> 'sysenterState.SysenterStateV45::rsp' may be used uninitialized in
> this
> function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> 'sysenterState.SysenterStateV45::rip' may be used uninitialized in
> this
> function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> 'sysenterState.SysenterStateV45::validEIP' may be used
> uninitialized in
> this function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> 'sysenterState.SysenterStateV45::cs' may be used uninitialized in this
> function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> 'sysenterState.SysenterStateV45::rsp' may be used uninitialized in
> this
> function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> 'sysenterState.SysenterStateV45::rip' may be used uninitialized in
> this
> function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h: In function
> 'void
> Task_Switch_V45(VMDriver*, Vcpuid)':
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:1713: warning:
> 'sysenterState.SysenterStateV45::validEIP' may be used
> uninitialized in
> this function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:1713: warning:
> 'sysenterState.SysenterStateV45::cs' may be used uninitialized in this
> function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:1713: warning:
> 'sysenterState.SysenterStateV45::rsp' may be used uninitialized in
> this
> function
> /tmp/vmware-config13/vmmon-only/common/task_compat.h:1713: warning:
> 'sysenterState.SysenterStateV45::rip' may be used uninitialized in
> this
> function
> CC [M] /tmp/vmware-config13/vmmon-only/common/vmx86.o
> CC [M] /tmp/vmware-config13/vmmon-only/vmcore/compat.o
> CC [M] /tmp/vmware-config13/vmmon-only/vmcore/moduleloop.o
> LD [M] /tmp/vmware-config13/vmmon-only/vmmon.o
> Building modules, stage 2.
> MODPOST 1 modules
> CC /tmp/vmware-config13/vmmon-only/vmmon.mod.o
> LD [M] /tmp/vmware-config13/vmmon-only/vmmon.ko
> make[1]: Saindo do diretório
> `/usr/src/kernels/2.6.20-1.2933.fc6-i686 '
> cp -f vmmon.ko ./../vmmon.o
> make: Saindo do diretório `/tmp/vmware-config13/vmmon-only'
> Unable to make a vmmon module that can be loaded in the running
> kernel:
> insmod: error inserting '/tmp/vmware-config13/vmmon.o': -1 Invalid
> module format
> There is probably a slight difference in the kernel configuration
> between the
> set of C header files you specified and your running kernel. You
> may want to
> rebuild a kernel based on that directory, or specify another
> directory.
>
> For more information on how to troubleshoot module-related
> problems, please
> visit our Web site at
> "http://www.vmware.com/download/modules/modules.html
> <http://www.vmware.com/download/modules/modules.html>" and
> "http://www.vmware.com/support/reference/linux/prebuilt_modules_linux.html".
>
> Execution aborted.
> [root@localhost ~]#
>
> Eu já desintalei e instalei novamente mas continuo o mesmo problema!
>
> Alguém poderia me ajudar?
>
> PaTricK
>
>
> --
> Fedora-users-br mailing list
> [e-mail] <mailto:[e-mail]>
> https://www.redhat.com/mailman/listinfo/fedora-users-br
>
>
> --
> Fedora-users-br mailing list
> [e-mail]
> https://www.redhat.com/mailman/listinfo/fedora-users-br

[Otto Fuchshuber Filho]

Recentemente postei a solução, segue:

-------- Mensagem original --------
Assunto: kernel 2.6.20 x vmplayer
Data: Sat, 17 Mar 2007 16:15:36 -0300
De: Otto Fuchshuber Filho 
Para: Lista de discussão voltada para os usuários brasileiros do
Fedora

Para quem usa FC6 e vmplayer:

Fiz upgrade p/o kernel 2.6.20 e o vmplayer não compilou mais.

Segue abaixo a solução que funcionou:

# As root, cd to /usr/lib/vmware/modules/source
# untar vmmon.tar and then move vmmon.tar to vmmon.tar.orig (just
to be safe)
# edit ./vmmon-only/include/compat_kernel.h and comment out line
21 with 2 slashes: //static inline _syscall1(int, compat_exit,
int, exit_code);
# tar vmmon-only and rename resultant archive to vmmon.tar. (I
used nautilus "create archive")
# run vmplayer-config.pl

fonte:
http://forums.fedoraforum.org/showpost.php?p=761622&postcount=5

[Gustavo Picoloto]

Olá,

Sempre apliquei o patch vmware-any-any-update
(http://ftp.cvut.cz/vmware/vmware-any-any-update108.tar.gz) e
funcionou de boa.

Basta fazer o download, descompactar e executar o "runme.pl" que tem
dentro do diretório que foi descompactado. Alias, se não me engano, o
que este patch faz basicamente são as modificações sugeridas no email
abaixo.

[]'s
Gustavo Picoloto

2007/4/4, Otto Fuchshuber Filho :
> Recentemente postei a solução, segue:
>
> -------- Mensagem original --------
> Assunto: kernel 2.6.20 x vmplayer
> Data: Sat, 17 Mar 2007 16:15:36 -0300
> De: Otto Fuchshuber Filho 
> Para: Lista de discussão voltada para os usuários brasileiros do
> Fedora
>
> Para quem usa FC6 e vmplayer:
>
> Fiz upgrade p/o kernel 2.6.20 e o vmplayer não compilou mais.
>
> Segue abaixo a solução que funcionou:
>
> # As root, cd to /usr/lib/vmware/modules/source
> # untar vmmon.tar and then move vmmon.tar to vmmon.tar.orig (just
> to be safe)
> # edit ./vmmon-only/include/compat_kernel.h and comment out line
> 21 with 2 slashes: //static inline _syscall1(int, compat_exit,
> int, exit_code);
> # tar vmmon-only and rename resultant archive to vmmon.tar. (I
> used nautilus "create archive")
> # run vmplayer-config.pl
>
> fonte:
> http://forums.fedoraforum.org/showpost.php?p=761622&postcount=5
>
> --
> Saudações,
> Otto Fuchshuber Filho
> [e-mail]
>
> 2007/4/3, PaTricK :
> > Olá,
> > Bom, eu tinha o vmware funcionando direitinho, depoix de atualizar o fc5
> > pra o fc6 com o yum, dai somente fiz esse comando ali e volto a
> > funciona, mas eu consegui o cd do fc 6 e botei pra atualiza pensando que
> > poderia faze alguma diferença, e fez, desatualizo alguns pacotes e o
> > kernel. Então atualizei tudo novamento com o yum e fui tenta faze
> > funciona o vmware novamente e estou tento o seguinte erro:
> >
> > [root@localhost ~]# vmware-config.pl -d
> > Making sure services for VMware Workstation are stopped.
> >
> > Stopping VMware services:
> > Virtual machine monitor [ OK ]
> >
> > Configuring fallback GTK+ 2.4 libraries.
> >
> > In which directory do you want to install the mime type icons?
> > [/usr/share/icons]
> >
> > What directory contains your desktop menu entry files? These files have a
> > .desktop file extension. [/usr/share/applications]
> >
> > In which directory do you want to install the application's icon?
> > [/usr/share/pixmaps]
> >
> > Trying to find a suitable vmmon module for your running kernel.
> >
> > None of the pre-built vmmon modules for VMware Workstation is suitable
> > for your
> > running kernel. Do you want this program to try to build the vmmon
> > module for
> > your system (you need to have a C compiler installed on your system)? [yes]
> >
> > Using compiler "/usr/bin/gcc". Use environment variable CC to override.
> >
> > What is the location of the directory of C header files that match your
> > running
> > kernel? [/usr/src/kernels/2.6.20-1.2933.fc6-i686/include]
> >
> > Extracting the sources of the vmmon module.
> >
> > Building the vmmon module.
> >
> > Building for VMware Workstation 5.5.2 or 5.5.3.
> > Using 2.6.x kernel build system.
> > make: Entrando no diretório `/tmp/vmware-config13/vmmon-only'
> > make -C /usr/src/kernels/2.6.20-1.2933.fc6-i686/include/.. SUBDIRS=$PWD
> > SRCROOT=$PWD/. modules
> > make[1]: Entrando no diretório `/usr/src/kernels/2.6.20-1.2933.fc6-i686'
> > CC [M] /tmp/vmware-config13/vmmon-only/linux/driver.o
> > CC [M] /tmp/vmware-config13/vmmon-only/linux/hostif.o
> > CC [M] /tmp/vmware-config13/vmmon-only/common/cpuid.o
> > CC [M] /tmp/vmware-config13/vmmon-only/common/hash.o
> > CC [M] /tmp/vmware-config13/vmmon-only/common/memtrack.o
> > CC [M] /tmp/vmware-config13/vmmon-only/common/phystrack.o
> > CC [M] /tmp/vmware-config13/vmmon-only/common/task.o
> > cc1plus: warning: command line option
> > "-Werror-implicit-function-declaration" is valid for C/ObjC but not for C++
> > cc1plus: warning: command line option "-Wdeclaration-after-statement" is
> > valid for C/ObjC but not for C++
> > cc1plus: warning: command line option "-Wno-pointer-sign" is valid for
> > C/ObjC but not for C++
> > cc1plus: warning: command line option "-Wstrict-prototypes" is valid for
> > Ada/C/ObjC but not for C++
> > cc1plus: warning: command line option "-ffreestanding" is valid for
> > C/ObjC but not for C++
> > /tmp/vmware-config13/vmmon-only/common/task_compat.h: In function 'int
> > Vmx86_RunVM(VMCrossPage*, VMDriver*) [with VMCrossPage = VMCrossPageV321]':
> > /tmp/vmware-config13/vmmon-only/common/task_compat.h:1522: warning:
> > 'sysenterState.SysenterStateV45::rsp' is used uninitialized in this function
> > /tmp/vmware-config13/vmmon-only/common/task_compat.h:1523: warning:
> > 'sysenterState.SysenterStateV45::rip' is used uninitialized in this function
> > /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> > 'sysenterState.SysenterStateV45::validEIP' may be used uninitialized in
> > this function
> > /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> > 'sysenterState.SysenterStateV45::cs' may be used uninitialized in this
> > function
> > /tmp/vmware-config13/vmmon-only/common/task_compat.h: In function 'int
> > Vmx86_RunVM(VMCrossPage*, VMDriver*) [with VMCrossPage = VMCrossPageV3]':
> > /tmp/vmware-config13/vmmon-only/common/task_compat.h:1522: warning:
> > 'sysenterState.SysenterStateV45::rsp' is used uninitialized in this function
> > /tmp/vmware-config13/vmmon-only/common/task_compat.h:1523: warning:
> > 'sysenterState.SysenterStateV45::rip' is used uninitialized in this function
> > /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> > 'sysenterState.SysenterStateV45::validEIP' may be used uninitialized in
> > this function
> > /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> > 'sysenterState.SysenterStateV45::cs' may be used uninitialized in this
> > function
> > /tmp/vmware-config13/vmmon-only/common/task_compat.h: In function 'int
> > Vmx86_RunVM(VMCrossPage*, VMDriver*) [with VMCrossPage = VMCrossPageGSX1]':
> > /tmp/vmware-config13/vmmon-only/common/task_compat.h:1522: warning:
> > 'sysenterState.SysenterStateV45::rsp' is used uninitialized in this function
> > /tmp/vmware-config13/vmmon-only/common/task_compat.h:1523: warning:
> > 'sysenterState.SysenterStateV45::rip' is used uninitialized in this function
> > /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> > 'sysenterState.SysenterStateV45::validEIP' may be used uninitialized in
> > this function
> > /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> > 'sysenterState.SysenterStateV45::cs' may be used uninitialized in this
> > function
> > /tmp/vmware-config13/vmmon-only/common/task_compat.h: In function 'int
> > Vmx86_RunVM(VMCrossPage*, VMDriver*) [with VMCrossPage = VMCrossPageV2]':
> > /tmp/vmware-config13/vmmon-only/common/task_compat.h:1522: warning:
> > 'sysenterState.SysenterStateV45::rsp' is used uninitialized in this function
> > /tmp/vmware-config13/vmmon-only/common/task_compat.h:1523: warning:
> > 'sysenterState.SysenterStateV45::rip' is used uninitialized in this function
> > /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> > 'sysenterState.SysenterStateV45::validEIP' may be used uninitialized in
> > this function
> > /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> > 'sysenterState.SysenterStateV45::cs' may be used uninitialized in this
> > function
> > /tmp/vmware-config13/vmmon-only/common/task_compat.h: In function 'int
> > Vmx86_RunVM_V4(VMDriver*, Vcpuid) [with VMCrossPage = VMCrossPageV4]':
> > /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> > 'sysenterState.SysenterStateV45::validEIP' may be used uninitialized in
> > this function
> > /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> > 'sysenterState.SysenterStateV45::cs' may be used uninitialized in this
> > function
> > /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> > 'sysenterState.SysenterStateV45::rsp' may be used uninitialized in this
> > function
> > /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> > 'sysenterState.SysenterStateV45::rip' may be used uninitialized in this
> > function
> > /tmp/vmware-config13/vmmon-only/common/task_compat.h: In function 'int
> > Vmx86_RunVM(VMDriver*, Vcpuid)':
> > /tmp/vmware-config13/vmmon-only/common/task_compat.h:1522: warning:
> > 'sysenterState.SysenterStateV45::rsp' is used uninitialized in this function
> > /tmp/vmware-config13/vmmon-only/common/task_compat.h:1523: warning:
> > 'sysenterState.SysenterStateV45::rip' is used uninitialized in this function
> > /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> > 'sysenterState.SysenterStateV45::validEIP' may be used uninitialized in
> > this function
> > /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> > 'sysenterState.SysenterStateV45::cs' may be used uninitialized in this
> > function
> > /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> > 'sysenterState.SysenterStateV45::validEIP' may be used uninitialized in
> > this function
> > /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> > 'sysenterState.SysenterStateV45::cs' may be used uninitialized in this
> > function
> > /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> > 'sysenterState.SysenterStateV45::rsp' may be used uninitialized in this
> > function
> > /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> > 'sysenterState.SysenterStateV45::rip' may be used uninitialized in this
> > function
> > /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> > 'sysenterState.SysenterStateV45::validEIP' may be used uninitialized in
> > this function
> > /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> > 'sysenterState.SysenterStateV45::cs' may be used uninitialized in this
> > function
> > /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> > 'sysenterState.SysenterStateV45::rsp' may be used uninitialized in this
> > function
> > /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> > 'sysenterState.SysenterStateV45::rip' may be used uninitialized in this
> > function
> > /tmp/vmware-config13/vmmon-only/common/task_compat.h: In function 'void
> > Task_Switch_V45(VMDriver*, Vcpuid)':
> > /tmp/vmware-config13/vmmon-only/common/task_compat.h:1713: warning:
> > 'sysenterState.SysenterStateV45::validEIP' may be used uninitialized in
> > this function
> > /tmp/vmware-config13/vmmon-only/common/task_compat.h:1713: warning:
> > 'sysenterState.SysenterStateV45::cs' may be used uninitialized in this
> > function
> > /tmp/vmware-config13/vmmon-only/common/task_compat.h:1713: warning:
> > 'sysenterState.SysenterStateV45::rsp' may be used uninitialized in this
> > function
> > /tmp/vmware-config13/vmmon-only/common/task_compat.h:1713: warning:
> > 'sysenterState.SysenterStateV45::rip' may be used uninitialized in this
> > function
> > CC [M] /tmp/vmware-config13/vmmon-only/common/vmx86.o
> > CC [M] /tmp/vmware-config13/vmmon-only/vmcore/compat.o
> > CC [M] /tmp/vmware-config13/vmmon-only/vmcore/moduleloop.o
> > LD [M] /tmp/vmware-config13/vmmon-only/vmmon.o
> > Building modules, stage 2.
> > MODPOST 1 modules
> > CC /tmp/vmware-config13/vmmon-only/vmmon.mod.o
> > LD [M] /tmp/vmware-config13/vmmon-only/vmmon.ko
> > make[1]: Saindo do diretório `/usr/src/kernels/2.6.20-1.2933.fc6-i686'
> > cp -f vmmon.ko ./../vmmon.o
> > make: Saindo do diretório `/tmp/vmware-config13/vmmon-only'
> > Unable to make a vmmon module that can be loaded in the running kernel:
> > insmod: error inserting '/tmp/vmware-config13/vmmon.o': -1 Invalid
> > module format
> > There is probably a slight difference in the kernel configuration
> > between the
> > set of C header files you specified and your running kernel. You may want to
> > rebuild a kernel based on that directory, or specify another directory.
> >
> > For more information on how to troubleshoot module-related problems, please
> > visit our Web site at
> > "http://www.vmware.com/download/modules/modules.html" and
> > "http://www.vmware.com/support/reference/linux/prebuilt_modules_linux.html".
> >
> > Execution aborted.
> > [root@localhost ~]#
> >
> > Eu já desintalei e instalei novamente mas continuo o mesmo problema!
> >
> > Alguém poderia me ajudar?
> >
> > PaTricK
> >
> > --
> > Fedora-users-br mailing list
> > [e-mail]
> > https://www.redhat.com/mailman/listinfo/fedora-users-br
>
> --
> Fedora-users-br mailing list
> [e-mail]
> https://www.redhat.com/mailman/listinfo/fedora-users-br

[Patrick]

Já executei esse path, e ele vai faze a config e acontece esse mesmo erro

PaTricK

Gustavo Picoloto escreveu:
> Olá,
>
> Sempre apliquei o patch vmware-any-any-update
> (http://ftp.cvut.cz/vmware/vmware-any-any-update108.tar.gz) e
> funcionou de boa.
>
> Basta fazer o download, descompactar e executar o "runme.pl" que tem
> dentro do diretório que foi descompactado. Alias, se não me engano, o
> que este patch faz basicamente são as modificações sugeridas no email
> abaixo.
>
> []'s
> Gustavo Picoloto
>
> 2007/4/4, Otto Fuchshuber Filho :
> > Recentemente postei a solução, segue:
> >
> > -------- Mensagem original --------
> > Assunto: kernel 2.6.20 x vmplayer
> > Data: Sat, 17 Mar 2007 16:15:36 -0300
> > De: Otto Fuchshuber Filho 
> > Para: Lista de discussão voltada para os usuários brasileiros do
> > Fedora
> >
> > Para quem usa FC6 e vmplayer:
> >
> > Fiz upgrade p/o kernel 2.6.20 e o vmplayer não compilou mais.
> >
> > Segue abaixo a solução que funcionou:
> >
> > # As root, cd to /usr/lib/vmware/modules/source
> > # untar vmmon.tar and then move vmmon.tar to vmmon.tar.orig (just
> > to be safe)
> > # edit ./vmmon-only/include/compat_kernel.h and comment out line
> > 21 with 2 slashes: //static inline _syscall1(int, compat_exit,
> > int, exit_code);
> > # tar vmmon-only and rename resultant archive to vmmon.tar. (I
> > used nautilus "create archive")
> > # run vmplayer-config.pl
> >
> > fonte:
> > http://forums.fedoraforum.org/showpost.php?p=761622&postcount=5
> >
> > -- 
> > Saudações,
> > Otto Fuchshuber Filho
> > [e-mail]
> >
> > 2007/4/3, PaTricK :
> > > Olá,
> > > Bom, eu tinha o vmware funcionando direitinho, depoix de atualizar
> >
> > o fc5
> > > pra o fc6 com o yum, dai somente fiz esse comando ali e volto a
> > > funciona, mas eu consegui o cd do fc 6 e botei pra atualiza
> >
> > pensando que
> > > poderia faze alguma diferença, e fez, desatualizo alguns pacotes e o
> > > kernel. Então atualizei tudo novamento com o yum e fui tenta faze
> > > funciona o vmware novamente e estou tento o seguinte erro:
> > >
> > > [root@localhost ~]# vmware-config.pl -d
> > > Making sure services for VMware Workstation are stopped.
> > >
> > > Stopping VMware services:
> > > Virtual machine monitor [ OK ]
> > >
> > > Configuring fallback GTK+ 2.4 libraries.
> > >
> > > In which directory do you want to install the mime type icons?
> > > [/usr/share/icons]
> > >
> > > What directory contains your desktop menu entry files? These files
> >
> > have a
> > > .desktop file extension. [/usr/share/applications]
> > >
> > > In which directory do you want to install the application's icon?
> > > [/usr/share/pixmaps]
> > >
> > > Trying to find a suitable vmmon module for your running kernel.
> > >
> > > None of the pre-built vmmon modules for VMware Workstation is suitable
> > > for your
> > > running kernel. Do you want this program to try to build the vmmon
> > > module for
> > > your system (you need to have a C compiler installed on your
> >
> > system)? [yes]
> > > Using compiler "/usr/bin/gcc". Use environment variable CC to
> >
> > override.
> > > What is the location of the directory of C header files that match
> >
> > your
> > > running
> > > kernel? [/usr/src/kernels/2.6.20-1.2933.fc6-i686/include]
> > >
> > > Extracting the sources of the vmmon module.
> > >
> > > Building the vmmon module.
> > >
> > > Building for VMware Workstation 5.5.2 or 5.5.3.
> > > Using 2.6.x kernel build system.
> > > make: Entrando no diretório `/tmp/vmware-config13/vmmon-only'
> > > make -C /usr/src/kernels/2.6.20-1.2933.fc6-i686/include/..
> >
> > SUBDIRS=$PWD
> > > SRCROOT=$PWD/. modules
> > > make[1]: Entrando no diretório
> >
> > `/usr/src/kernels/2.6.20-1.2933.fc6-i686'
> > > CC [M] /tmp/vmware-config13/vmmon-only/linux/driver.o
> > > CC [M] /tmp/vmware-config13/vmmon-only/linux/hostif.o
> > > CC [M] /tmp/vmware-config13/vmmon-only/common/cpuid.o
> > > CC [M] /tmp/vmware-config13/vmmon-only/common/hash.o
> > > CC [M] /tmp/vmware-config13/vmmon-only/common/memtrack.o
> > > CC [M] /tmp/vmware-config13/vmmon-only/common/phystrack.o
> > > CC [M] /tmp/vmware-config13/vmmon-only/common/task.o
> > > cc1plus: warning: command line option
> > > "-Werror-implicit-function-declaration" is valid for C/ObjC but not
> >
> > for C++
> > > cc1plus: warning: command line option
> >
> > "-Wdeclaration-after-statement" is
> > > valid for C/ObjC but not for C++
> > > cc1plus: warning: command line option "-Wno-pointer-sign" is valid for
> > > C/ObjC but not for C++
> > > cc1plus: warning: command line option "-Wstrict-prototypes" is
> >
> > valid for
> > > Ada/C/ObjC but not for C++
> > > cc1plus: warning: command line option "-ffreestanding" is valid for
> > > C/ObjC but not for C++
> > > /tmp/vmware-config13/vmmon-only/common/task_compat.h: In function 'int
> > > Vmx86_RunVM(VMCrossPage*, VMDriver*) [with VMCrossPage =
> >
> > VMCrossPageV321]':
> > > /tmp/vmware-config13/vmmon-only/common/task_compat.h:1522: warning:
> > > 'sysenterState.SysenterStateV45::rsp' is used uninitialized in this
> >
> > function
> > > /tmp/vmware-config13/vmmon-only/common/task_compat.h:1523: warning:
> > > 'sysenterState.SysenterStateV45::rip' is used uninitialized in this
> >
> > function
> > > /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> > > 'sysenterState.SysenterStateV45::validEIP' may be used
> >
> > uninitialized in
> > > this function
> > > /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> > > 'sysenterState.SysenterStateV45::cs' may be used uninitialized in this
> > > function
> > > /tmp/vmware-config13/vmmon-only/common/task_compat.h: In function 'int
> > > Vmx86_RunVM(VMCrossPage*, VMDriver*) [with VMCrossPage =
> >
> > VMCrossPageV3]':
> > > /tmp/vmware-config13/vmmon-only/common/task_compat.h:1522: warning:
> > > 'sysenterState.SysenterStateV45::rsp' is used uninitialized in this
> >
> > function
> > > /tmp/vmware-config13/vmmon-only/common/task_compat.h:1523: warning:
> > > 'sysenterState.SysenterStateV45::rip' is used uninitialized in this
> >
> > function
> > > /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> > > 'sysenterState.SysenterStateV45::validEIP' may be used
> >
> > uninitialized in
> > > this function
> > > /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> > > 'sysenterState.SysenterStateV45::cs' may be used uninitialized in this
> > > function
> > > /tmp/vmware-config13/vmmon-only/common/task_compat.h: In function 'int
> > > Vmx86_RunVM(VMCrossPage*, VMDriver*) [with VMCrossPage =
> >
> > VMCrossPageGSX1]':
> > > /tmp/vmware-config13/vmmon-only/common/task_compat.h:1522: warning:
> > > 'sysenterState.SysenterStateV45::rsp' is used uninitialized in this
> >
> > function
> > > /tmp/vmware-config13/vmmon-only/common/task_compat.h:1523: warning:
> > > 'sysenterState.SysenterStateV45::rip' is used uninitialized in this
> >
> > function
> > > /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> > > 'sysenterState.SysenterStateV45::validEIP' may be used
> >
> > uninitialized in
> > > this function
> > > /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> > > 'sysenterState.SysenterStateV45::cs' may be used uninitialized in this
> > > function
> > > /tmp/vmware-config13/vmmon-only/common/task_compat.h: In function 'int
> > > Vmx86_RunVM(VMCrossPage*, VMDriver*) [with VMCrossPage =
> >
> > VMCrossPageV2]':
> > > /tmp/vmware-config13/vmmon-only/common/task_compat.h:1522: warning:
> > > 'sysenterState.SysenterStateV45::rsp' is used uninitialized in this
> >
> > function
> > > /tmp/vmware-config13/vmmon-only/common/task_compat.h:1523: warning:
> > > 'sysenterState.SysenterStateV45::rip' is used uninitialized in this
> >
> > function
> > > /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> > > 'sysenterState.SysenterStateV45::validEIP' may be used
> >
> > uninitialized in
> > > this function
> > > /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> > > 'sysenterState.SysenterStateV45::cs' may be used uninitialized in this
> > > function
> > > /tmp/vmware-config13/vmmon-only/common/task_compat.h: In function 'int
> > > Vmx86_RunVM_V4(VMDriver*, Vcpuid) [with VMCrossPage = VMCrossPageV4]':
> > > /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> > > 'sysenterState.SysenterStateV45::validEIP' may be used
> >
> > uninitialized in
> > > this function
> > > /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> > > 'sysenterState.SysenterStateV45::cs' may be used uninitialized in this
> > > function
> > > /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> > > 'sysenterState.SysenterStateV45::rsp' may be used uninitialized in
> >
> > this
> > > function
> > > /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> > > 'sysenterState.SysenterStateV45::rip' may be used uninitialized in
> >
> > this
> > > function
> > > /tmp/vmware-config13/vmmon-only/common/task_compat.h: In function 'int
> > > Vmx86_RunVM(VMDriver*, Vcpuid)':
> > > /tmp/vmware-config13/vmmon-only/common/task_compat.h:1522: warning:
> > > 'sysenterState.SysenterStateV45::rsp' is used uninitialized in this
> >
> > function
> > > /tmp/vmware-config13/vmmon-only/common/task_compat.h:1523: warning:
> > > 'sysenterState.SysenterStateV45::rip' is used uninitialized in this
> >
> > function
> > > /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> > > 'sysenterState.SysenterStateV45::validEIP' may be used
> >
> > uninitialized in
> > > this function
> > > /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> > > 'sysenterState.SysenterStateV45::cs' may be used uninitialized in this
> > > function
> > > /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> > > 'sysenterState.SysenterStateV45::validEIP' may be used
> >
> > uninitialized in
> > > this function
> > > /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> > > 'sysenterState.SysenterStateV45::cs' may be used uninitialized in this
> > > function
> > > /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> > > 'sysenterState.SysenterStateV45::rsp' may be used uninitialized in
> >
> > this
> > > function
> > > /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> > > 'sysenterState.SysenterStateV45::rip' may be used uninitialized in
> >
> > this
> > > function
> > > /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> > > 'sysenterState.SysenterStateV45::validEIP' may be used
> >
> > uninitialized in
> > > this function
> > > /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> > > 'sysenterState.SysenterStateV45::cs' may be used uninitialized in this
> > > function
> > > /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> > > 'sysenterState.SysenterStateV45::rsp' may be used uninitialized in
> >
> > this
> > > function
> > > /tmp/vmware-config13/vmmon-only/common/task_compat.h:2073: warning:
> > > 'sysenterState.SysenterStateV45::rip' may be used uninitialized in
> >
> > this
> > > function
> > > /tmp/vmware-config13/vmmon-only/common/task_compat.h: In function
> >
> > 'void
> > > Task_Switch_V45(VMDriver*, Vcpuid)':
> > > /tmp/vmware-config13/vmmon-only/common/task_compat.h:1713: warning:
> > > 'sysenterState.SysenterStateV45::validEIP' may be used
> >
> > uninitialized in
> > > this function
> > > /tmp/vmware-config13/vmmon-only/common/task_compat.h:1713: warning:
> > > 'sysenterState.SysenterStateV45::cs' may be used uninitialized in this
> > > function
> > > /tmp/vmware-config13/vmmon-only/common/task_compat.h:1713: warning:
> > > 'sysenterState.SysenterStateV45::rsp' may be used uninitialized in
> >
> > this
> > > function
> > > /tmp/vmware-config13/vmmon-only/common/task_compat.h:1713: warning:
> > > 'sysenterState.SysenterStateV45::rip' may be used uninitialized in
> >
> > this
> > > function
> > > CC [M] /tmp/vmware-config13/vmmon-only/common/vmx86.o
> > > CC [M] /tmp/vmware-config13/vmmon-only/vmcore/compat.o
> > > CC [M] /tmp/vmware-config13/vmmon-only/vmcore/moduleloop.o
> > > LD [M] /tmp/vmware-config13/vmmon-only/vmmon.o
> > > Building modules, stage 2.
> > > MODPOST 1 modules
> > > CC /tmp/vmware-config13/vmmon-only/vmmon.mod.o
> > > LD [M] /tmp/vmware-config13/vmmon-only/vmmon.ko
> > > make[1]: Saindo do diretório `/usr/src/kernels/2.6.20-1.2933.fc6-i686'
> > > cp -f vmmon.ko ./../vmmon.o
> > > make: Saindo do diretório `/tmp/vmware-config13/vmmon-only'
> > > Unable to make a vmmon module that can be loaded in the running
> >
> > kernel:
> > > insmod: error inserting '/tmp/vmware-config13/vmmon.o': -1 Invalid
> > > module format
> > > There is probably a slight difference in the kernel configuration
> > > between the
> > > set of C header files you specified and your running kernel. You
> >
> > may want to
> > > rebuild a kernel based on that directory, or specify another
> >
> > directory.
> > > For more information on how to troubleshoot module-related
> >
> > problems, please
> > > visit our Web site at
> > > "http://www.vmware.com/download/modules/modules.html" and
> >
> > "http://www.vmware.com/support/reference/linux/prebuilt_modules_linux.html".
> > > Execution aborted.
> > > [root@localhost ~]#
> > >
> > > Eu já desintalei e instalei novamente mas continuo o mesmo problema!
> > >
> > > Alguém poderia me ajudar?
> > >
> > > PaTricK
> > >
> > > --
> > > Fedora-users-br mailing list
> > > [e-mail]
> > > https://www.redhat.com/mailman/listinfo/fedora-users-br
> >
> > -- 
> > Fedora-users-br mailing list
> > [e-mail]
> > https://www.redhat.com/mailman/listinfo/fedora-users-br

[Patrick]

Eu comentei a linha e fiz fiz o vmmon.tar novamente mas continua o mesmo 
erro
fiz alguma coisa errada?

/*
 * compat_exit() provides an access to the exit() function. It must
 * be named compat_exit(), as exit() (with different signature) is
 * provided by x86-64, arm and other (but not by i386).
 */
#define __NR_compat_exit __NR_exit
#static inline _syscall1(int, compat_exit, int, exit_code);   "linha que 
comentei"

Otto Fuchshuber Filho escreveu:
> Recentemente postei a solução, segue:
>
> -------- Mensagem original --------
> Assunto: kernel 2.6.20 x vmplayer
> Data: Sat, 17 Mar 2007 16:15:36 -0300
> De: Otto Fuchshuber Filho 
> Para: Lista de discussão voltada para os usuários brasileiros do
> Fedora
>
> Para quem usa FC6 e vmplayer:
>
> Fiz upgrade p/o kernel 2.6.20 e o vmplayer não compilou mais.
>
> Segue abaixo a solução que funcionou:
>
> # As root, cd to /usr/lib/vmware/modules/source
> # untar vmmon.tar and then move vmmon.tar to vmmon.tar.orig (just
> to be safe)
> # edit ./vmmon-only/include/compat_kernel.h and comment out line
> 21 with 2 slashes: //static inline _syscall1(int, compat_exit,
> int, exit_code);
> # tar vmmon-only and rename resultant archive to vmmon.tar. (I
> used nautilus "create archive")
> # run vmplayer-config.pl
>
> fonte:
> http://forums.fedoraforum.org/showpost.php?p=761622&postcount=5

[Gustavo Picoloto]

Olá,

Execute esses dois comandos e nos envie a saída:
$ rpm -qa|grep kernel
$ uname -r

[]'s
Gustavo Picoloto

Em 04/04/07, PaTricK escreveu:
> Eu comentei a linha e fiz fiz o vmmon.tar novamente mas continua o mesmo
> erro
> fiz alguma coisa errada?
>
> /*
> compat_exit() provides an access to the exit() function. It must
> be named compat_exit(), as exit() (with different signature) is
> provided by x86-64, arm and other (but not by i386).
>
> */
> #define __NR_compat_exit __NR_exit
> #static inline _syscall1(int, compat_exit, int, exit_code);   "linha que
> comentei"
>
> Otto Fuchshuber Filho escreveu:
> > Recentemente postei a solução, segue:
> >
> > -------- Mensagem original --------
> > Assunto: kernel 2.6.20 x vmplayer
> > Data: Sat, 17 Mar 2007 16:15:36 -0300
> > De: Otto Fuchshuber Filho 
> > Para: Lista de discussão voltada para os usuários brasileiros do
> > Fedora
> >
> > Para quem usa FC6 e vmplayer:
> >
> > Fiz upgrade p/o kernel 2.6.20 e o vmplayer não compilou mais.
> >
> > Segue abaixo a solução que funcionou:
> >
> > # As root, cd to /usr/lib/vmware/modules/source
> > # untar vmmon.tar and then move vmmon.tar to vmmon.tar.orig (just
> > to be safe)
> > # edit ./vmmon-only/include/compat_kernel.h and comment out line
> > 21 with 2 slashes: //static inline _syscall1(int, compat_exit,
> > int, exit_code);
> > # tar vmmon-only and rename resultant archive to vmmon.tar. (I
> > used nautilus "create archive")
> > # run vmplayer-config.pl
> >
> > fonte:
> > http://forums.fedoraforum.org/showpost.php?p=761622&postcount=5
>
> --
> Fedora-users-br mailing list
> [e-mail]
> https://www.redhat.com/mailman/listinfo/fedora-users-br

[Patrick]

Ta aí o resultado dos comandos:

[root@localhost vmware-any-any-update108]# rpm -qa|grep kernel
kernel-2.6.20-1.2933.fc6
kernel-headers-2.6.20-1.2933.fc6
kernel-devel-2.6.20-1.2933.fc6
[root@localhost vmware-any-any-update108]# uname -a
Linux localhost.localdomain 2.6.20-1.2933.fc6 #1 SMP Mon Mar 19 10:42:48 
EDT 2007 i686 athlon i386 GNU/Linux
[root@localhost vmware-any-any-update108]#

PaTricK

Gustavo Picoloto escreveu:
> Olá,
>
> Execute esses dois comandos e nos envie a saída:
> $ rpm -qa|grep kernel
> $ uname -r
>
> []'s
> Gustavo Picoloto
>
> Em 04/04/07, PaTricK escreveu:
> > Eu comentei a linha e fiz fiz o vmmon.tar novamente mas continua o mesmo
> > erro
> > fiz alguma coisa errada?
> >
> > /*
> > compat_exit() provides an access to the exit() function. It must
> > be named compat_exit(), as exit() (with different signature) is
> > provided by x86-64, arm and other (but not by i386).
> >
> > */
> > #define __NR_compat_exit __NR_exit
> > #static inline _syscall1(int, compat_exit, int, exit_code);   "linha que
> > comentei"
> >
> > Otto Fuchshuber Filho escreveu:
> > > Recentemente postei a solução, segue:
> > >
> > > -------- Mensagem original --------
> > > Assunto: kernel 2.6.20 x vmplayer
> > > Data: Sat, 17 Mar 2007 16:15:36 -0300
> > > De: Otto Fuchshuber Filho 
> > > Para: Lista de discussão voltada para os usuários brasileiros do
> > > Fedora
> > >
> > > Para quem usa FC6 e vmplayer:
> > >
> > > Fiz upgrade p/o kernel 2.6.20 e o vmplayer não compilou mais.
> > >
> > > Segue abaixo a solução que funcionou:
> > >
> > > # As root, cd to /usr/lib/vmware/modules/source
> > > # untar vmmon.tar and then move vmmon.tar to vmmon.tar.orig (just
> > > to be safe)
> > > # edit ./vmmon-only/include/compat_kernel.h and comment out line
> > > 21 with 2 slashes: //static inline _syscall1(int, compat_exit,
> > > int, exit_code);
> > > # tar vmmon-only and rename resultant archive to vmmon.tar. (I
> > > used nautilus "create archive")
> > > # run vmplayer-config.pl
> > >
> > > fonte:
> > > http://forums.fedoraforum.org/showpost.php?p=761622&postcount=5
> >
> > -- 
> > Fedora-users-br mailing list
> > [e-mail]
> > https://www.redhat.com/mailman/listinfo/fedora-users-br

[Patrick]

Alguém pode dá uma ajudinha aí?

PaTricK

PaTricK escreveu:
> Ta aí o resultado dos comandos:
>
> [root@localhost vmware-any-any-update108]# rpm -qa|grep kernel
> kernel-2.6.20-1.2933.fc6
> kernel-headers-2.6.20-1.2933.fc6
> kernel-devel-2.6.20-1.2933.fc6
> [root@localhost vmware-any-any-update108]# uname -a
> Linux localhost.localdomain 2.6.20-1.2933.fc6 #1 SMP Mon Mar 19 
> 10:42:48 EDT 2007 i686 athlon i386 GNU/Linux
> [root@localhost vmware-any-any-update108]#
>
> PaTricK
>
> Gustavo Picoloto escreveu:
> > Olá,
> >
> > Execute esses dois comandos e nos envie a saída:
> > $ rpm -qa|grep kernel
> > $ uname -r
> >
> > []'s
> > Gustavo Picoloto
> >
> > Em 04/04/07, PaTricK escreveu:
> > > Eu comentei a linha e fiz fiz o vmmon.tar novamente mas continua o 
> > > mesmo
> > > erro
> > > fiz alguma coisa errada?
> > >
> > > /*
> > > compat_exit() provides an access to the exit() function. It must
> > > be named compat_exit(), as exit() (with different signature) is
> > > provided by x86-64, arm and other (but not by i386).
> > >
> > > */
> > > #define __NR_compat_exit __NR_exit
> > > #static inline _syscall1(int, compat_exit, int, exit_code);   "linha 
> > > que
> > > comentei"
> > >
> > > Otto Fuchshuber Filho escreveu:
> > > > Recentemente postei a solução, segue:
> > > >
> > > > -------- Mensagem original --------
> > > > Assunto: kernel 2.6.20 x vmplayer
> > > > Data: Sat, 17 Mar 2007 16:15:36 -0300
> > > > De: Otto Fuchshuber Filho 
> > > > Para: Lista de discussão voltada para os usuários brasileiros do
> > > > Fedora
> > > >
> > > > Para quem usa FC6 e vmplayer:
> > > >
> > > > Fiz upgrade p/o kernel 2.6.20 e o vmplayer não compilou mais.
> > > >
> > > > Segue abaixo a solução que funcionou:
> > > >
> > > > # As root, cd to /usr/lib/vmware/modules/source
> > > > # untar vmmon.tar and then move vmmon.tar to vmmon.tar.orig (just
> > > > to be safe)
> > > > # edit ./vmmon-only/include/compat_kernel.h and comment out line
> > > > 21 with 2 slashes: //static inline _syscall1(int, compat_exit,
> > > > int, exit_code);
> > > > # tar vmmon-only and rename resultant archive to vmmon.tar. (I
> > > > used nautilus "create archive")
> > > > # run vmplayer-config.pl
> > > >
> > > > fonte:
> > > > http://forums.fedoraforum.org/showpost.php?p=761622&postcount=5
> > >
> > > -- 
> > > Fedora-users-br mailing list
> > > [e-mail]
> > > https://www.redhat.com/mailman/listinfo/fedora-users-br
>
> -- 
> Fedora-users-br mailing list
> [e-mail]
> https://www.redhat.com/mailman/listinfo/fedora-users-br

[Otto Fuchshuber Filho]

Você não prestou atenção na instrução:
..and comment out line 21 with 2 slashes: //static inline 
_syscall1(int, compat_exit, int, exit_code);

Isto é, é para comentar a linha com 2 barras (slashes).  Você 
comentou com #.

Saudações,
Otto Fuchshuber Filho
[e-mail]

PaTricK escreveu, Em 10-04-2007 03:03:
> Alguém pode dá uma ajudinha aí?
>
> PaTricK
>
> PaTricK escreveu:
> > Ta aí o resultado dos comandos:
> >
> > [root@localhost vmware-any-any-update108]# rpm -qa|grep kernel
> > kernel-2.6.20-1.2933.fc6
> > kernel-headers-2.6.20-1.2933.fc6
> > kernel-devel-2.6.20-1.2933.fc6
> > [root@localhost vmware-any-any-update108]# uname -a
> > Linux localhost.localdomain 2.6.20-1.2933.fc6 #1 SMP Mon Mar 19 
> > 10:42:48 EDT 2007 i686 athlon i386 GNU/Linux
> > [root@localhost vmware-any-any-update108]#     
> > PaTricK
> >
> > Gustavo Picoloto escreveu:
> > > Olá,
> > >
> > > Execute esses dois comandos e nos envie a saída:
> > > $ rpm -qa|grep kernel
> > > $ uname -r
> > >
> > > []'s
> > > Gustavo Picoloto
> > >
> > > Em 04/04/07, PaTricK escreveu:
> > > > Eu comentei a linha e fiz fiz o vmmon.tar novamente mas continua o 
> > > > mesmo
> > > > erro
> > > > fiz alguma coisa errada?
> > > >
> > > > /*
> > > > compat_exit() provides an access to the exit() function. It must
> > > > be named compat_exit(), as exit() (with different signature) is
> > > > provided by x86-64, arm and other (but not by i386).
> > > >
> > > > */
> > > > #define __NR_compat_exit __NR_exit
> > > > #static inline _syscall1(int, compat_exit, int, exit_code);   "linha 
> > > > que
> > > > comentei"
> > > >
> > > > Otto Fuchshuber Filho escreveu:
> > > > > Recentemente postei a solução, segue:
> > > > >
> > > > > -------- Mensagem original --------
> > > > > Assunto: kernel 2.6.20 x vmplayer
> > > > > Data: Sat, 17 Mar 2007 16:15:36 -0300
> > > > > De: Otto Fuchshuber Filho 
> > > > > Para: Lista de discussão voltada para os usuários brasileiros do
> > > > > Fedora
> > > > >
> > > > > Para quem usa FC6 e vmplayer:
> > > > >
> > > > > Fiz upgrade p/o kernel 2.6.20 e o vmplayer não compilou mais.
> > > > >
> > > > > Segue abaixo a solução que funcionou:
> > > > >
> > > > > # As root, cd to /usr/lib/vmware/modules/source
> > > > > # untar vmmon.tar and then move vmmon.tar to vmmon.tar.orig (just
> > > > > to be safe)
> > > > > # edit ./vmmon-only/include/compat_kernel.h and comment out line
> > > > > 21 with 2 slashes: //static inline _syscall1(int, compat_exit,
> > > > > int, exit_code);
> > > > > # tar vmmon-only and rename resultant archive to vmmon.tar. (I
> > > > > used nautilus "create archive")
> > > > > # run vmplayer-config.pl
> > > > >
> > > > > fonte:
> > > > > http://forums.fedoraforum.org/showpost.php?p=761622&postcount=5
> > > >
> > > > -- 
> > > > Fedora-users-br mailing list
> > > > [e-mail]
> > > > https://www.redhat.com/mailman/listinfo/fedora-users-br
> >
> > -- 
> > Fedora-users-br mailing list
> > [e-mail]
> > https://www.redhat.com/mailman/listinfo/fedora-users-br
>
> -- 
> Fedora-users-br mailing list
> [e-mail]
> https://www.redhat.com/mailman/listinfo/fedora-users-br

[Patrick]

É que fiz dos dois jeitos e mesmo assim nao foi... continua o mesmo erro

/*
 * compat_exit() provides an access to the exit() function. It must
 * be named compat_exit(), as exit() (with different signature) is
 * provided by x86-64, arm and other (but not by i386).
 */
#define __NR_compat_exit __NR_exit
//static inline _syscall1(int, compat_exit, int, exit_code);   "linha que
comentei"

PaTricK

Otto Fuchshuber Filho escreveu:
> Você não prestou atenção na instrução:
> ..and comment out line 21 with 2 slashes: //static inline 
> _syscall1(int, compat_exit, int, exit_code);
>
> Isto é, é para comentar a linha com 2 barras (slashes).  Você comentou 
> com #.
>
> Saudações,
> Otto Fuchshuber Filho
> [e-mail]
>
> PaTricK escreveu, Em 10-04-2007 03:03:
> > Alguém pode dá uma ajudinha aí?
> >
> > PaTricK
> >
> > PaTricK escreveu:
> > > Ta aí o resultado dos comandos:
> > >
> > > [root@localhost vmware-any-any-update108]# rpm -qa|grep kernel
> > > kernel-2.6.20-1.2933.fc6
> > > kernel-headers-2.6.20-1.2933.fc6
> > > kernel-devel-2.6.20-1.2933.fc6
> > > [root@localhost vmware-any-any-update108]# uname -a
> > > Linux localhost.localdomain 2.6.20-1.2933.fc6 #1 SMP Mon Mar 19 
> > > 10:42:48 EDT 2007 i686 athlon i386 GNU/Linux
> > > [root@localhost vmware-any-any-update108]#     PaTricK
> > >
> > > Gustavo Picoloto escreveu:
> > > > Olá,
> > > >
> > > > Execute esses dois comandos e nos envie a saída:
> > > > $ rpm -qa|grep kernel
> > > > $ uname -r
> > > >
> > > > []'s
> > > > Gustavo Picoloto
> > > >
> > > > Em 04/04/07, PaTricK escreveu:
> > > > > Eu comentei a linha e fiz fiz o vmmon.tar novamente mas continua o 
> > > > > mesmo
> > > > > erro
> > > > > fiz alguma coisa errada?
> > > > >
> > > > > /*
> > > > > compat_exit() provides an access to the exit() function. It must
> > > > > be named compat_exit(), as exit() (with different signature) is
> > > > > provided by x86-64, arm and other (but not by i386).
> > > > >
> > > > > */
> > > > > #define __NR_compat_exit __NR_exit
> > > > > #static inline _syscall1(int, compat_exit, int, exit_code);   
> > > > > "linha que
> > > > > comentei"
> > > > >
> > > > > Otto Fuchshuber Filho escreveu:
> > > > > > Recentemente postei a solução, segue:
> > > > > >
> > > > > > -------- Mensagem original --------
> > > > > > Assunto: kernel 2.6.20 x vmplayer
> > > > > > Data: Sat, 17 Mar 2007 16:15:36 -0300
> > > > > > De: Otto Fuchshuber Filho 
> > > > > > Para: Lista de discussão voltada para os usuários brasileiros do
> > > > > > Fedora
> > > > > >
> > > > > > Para quem usa FC6 e vmplayer:
> > > > > >
> > > > > > Fiz upgrade p/o kernel 2.6.20 e o vmplayer não compilou mais.
> > > > > >
> > > > > > Segue abaixo a solução que funcionou:
> > > > > >
> > > > > > # As root, cd to /usr/lib/vmware/modules/source
> > > > > > # untar vmmon.tar and then move vmmon.tar to vmmon.tar.orig (just
> > > > > > to be safe)
> > > > > > # edit ./vmmon-only/include/compat_kernel.h and comment out line
> > > > > > 21 with 2 slashes: //static inline _syscall1(int, compat_exit,
> > > > > > int, exit_code);
> > > > > > # tar vmmon-only and rename resultant archive to vmmon.tar. (I
> > > > > > used nautilus "create archive")
> > > > > > # run vmplayer-config.pl
> > > > > >
> > > > > > fonte:
> > > > > > http://forums.fedoraforum.org/showpost.php?p=761622&postcount=5
> > > > >
> > > > > -- 
> > > > > Fedora-users-br mailing list
> > > > > [e-mail]
> > > > > https://www.redhat.com/mailman/listinfo/fedora-users-br
> > >
> > > -- 
> > > Fedora-users-br mailing list
> > > [e-mail]
> > > https://www.redhat.com/mailman/listinfo/fedora-users-br
> >
> > -- 
> > Fedora-users-br mailing list
> > [e-mail]
> > https://www.redhat.com/mailman/listinfo/fedora-users-br
>
> -- 
> Fedora-users-br mailing list
> [e-mail]
> https://www.redhat.com/mailman/listinfo/fedora-users-br

[André Felício]

A Wednesday 04 April 2007 12:17:56, PaTricK escreveu:
> Ta aí o resultado dos comandos:
>
> [root@localhost vmware-any-any-update108]# rpm -qa|grep kernel
> kernel-2.6.20-1.2933.fc6
> kernel-headers-2.6.20-1.2933.fc6
> kernel-devel-2.6.20-1.2933.fc6
> [root@localhost vmware-any-any-update108]# uname -a
> Linux localhost.localdomain 2.6.20-1.2933.fc6 #1 SMP Mon Mar 19 10:42:48
> EDT 2007 i686 athlon i386 GNU/Linux
> [root@localhost vmware-any-any-update108]#

Mande o rpm a saida rpm de outro modo:

# rpm --qf '%{name}-%{version}-%{release}.%{arch}\n' -qa |grep kernel

Ok?

[André Felício]

Rau,
> Mande o rpm a saida rpm de outro modo:
>
> # rpm --qf '%{name}-%{version}-%{release}.%{arch}\n' -qa |grep kernel

Esqueci de explicar o motivo.
A pouco tempo instalei um FC6 e quando fui instalar o vmware, estava dando o 
mesmo erro.

Para minha surpresa a maquina estava usando um kernel i586 em um pentium 4. 
Pior, quando mandei instalar pelo yum o kernel-devel instalado foi o i686.

Só percebi este possível *BUG* quando fui instalar o vmware.

[Patrick]

Olá,
  tá aí o comando:

root@localhost ~]# rpm --qf '%{name}-%{version}-%{release}.%{arch}\n' -qa |grep kernel
kernel-2.6.20-1.2933.fc6.i586
kernel-headers-2.6.20-1.2933.fc6.i386
kernel-devel-2.6.20-1.2933.fc6.i686

André Felício  escreveu:
  Rau,
> Mande o rpm a saida rpm de outro modo:
>
> # rpm --qf '%{name}-%{version}-%{release}.%{arch}\n' -qa |grep kernel

Esqueci de explicar o motivo.
A pouco tempo instalei um FC6 e quando fui instalar o vmware, estava dando o 
mesmo erro.

Para minha surpresa a maquina estava usando um kernel i586 em um pentium 4. 
Pior, quando mandei instalar pelo yum o kernel-devel instalado foi o i686.

Só percebi este possível *BUG* quando fui instalar o vmware.

[Otto Fuchshuber Filho]

Justamente o que o André Felício suspeitava.  Você está com o 
kernel i586 e o kernel-devel i686.
Troque um dos dois para que ambos fiquem com a mesma versão.

Saudações,
Otto Fuchshuber Filho
[e-mail]

PaTricK escreveu, Em 10-04-2007 21:31:
> Olá,
> tá aí o comando:
>
> root@localhost ~]# rpm --qf '%{name}-%{version}-%{release}.%{arch}\n' 
> -qa |grep kernel
> kernel-2.6.20-1.2933.fc6.i586
> kernel-headers-2.6.20-1.2933.fc6.i386
> kernel-devel-2.6.20-1.2933.fc6.i686
>
> */André Felício /* escreveu:
> Rau,
>
>  > Mande o rpm a saida rpm de outro modo:
>  >
>  > # rpm --qf '%{name}-%{version}-%{release}.%{arch}\n' -qa |grep kernel
>
> Esqueci de explicar o motivo.
> A pouco tempo instalei um FC6 e quando fui instalar o vmware, estava
> dando o
> mesmo erro.
>
> Para minha surpresa a maquina estava usando um kernel i586 em um
> pentium 4.
> Pior, quando mandei instalar pelo yum o kernel-devel instalado foi o
> i686.
>
> Só percebi este possível *BUG* quando fui instalar o vmware.
>
> -- 
> Att,
>
> André Felício
> http://www.felicio.com.br
>
> He is considered a most graceful speaker who can say nothing in the
> most
> words.
> --
> Fedora-users-br mailing list
> [e-mail]
> https://www.redhat.com/mailman/listinfo/fedora-users-br
>
>
> Fale com seus amigos de graça com o novo Yahoo! Messenger
> http://br.messenger.yahoo.com/
>
> --
> Fedora-users-br mailing list
> [e-mail]
> https://www.redhat.com/mailman/listinfo/fedora-users-br

[Cristiano Furtado]

Não seir amias pratico dar o comando uname -a e rpm -qa |grep kernel???

Em 10/04/07, Otto Fuchshuber Filho  escreveu:
> Justamente o que o André Felício suspeitava.  Você está com o
> kernel i586 e o kernel-devel i686.
> Troque um dos dois para que ambos fiquem com a mesma versão.
>
> Saudações,
> Otto Fuchshuber Filho
> [e-mail]
>
> PaTricK escreveu, Em 10-04-2007 21:31:
> > Olá,
> > tá aí o comando:
> >
> > root@localhost ~]# rpm --qf '%{name}-%{version}-%{release}.%{arch}\n'
> > -qa |grep kernel
> > kernel-2.6.20-1.2933.fc6.i586
> > kernel-headers-2.6.20-1.2933.fc6.i386
> > kernel-devel-2.6.20-1.2933.fc6.i686
> >
> > */André Felício /* escreveu:
> > Rau,
> >
> >  > Mande o rpm a saida rpm de outro modo:
> >  >
> >  > # rpm --qf '%{name}-%{version}-%{release}.%{arch}\n' -qa |grep
>
> kernel
> > Esqueci de explicar o motivo.
> > A pouco tempo instalei um FC6 e quando fui instalar o vmware, estava
> > dando o
> > mesmo erro.
> >
> > Para minha surpresa a maquina estava usando um kernel i586 em um
> > pentium 4.
> > Pior, quando mandei instalar pelo yum o kernel-devel instalado foi o
> > i686.
> >
> > Só percebi este possível *BUG* quando fui instalar o vmware.
> >
> > --
> > Att,
> >
> > André Felício
> > http://www.felicio.com.br
> >
> > He is considered a most graceful speaker who can say nothing in the
> > most
> > words.
> > --
> > Fedora-users-br mailing list
> > [e-mail]
> > https://www.redhat.com/mailman/listinfo/fedora-users-br
> >
> >
> > Fale com seus amigos de graça com o novo Yahoo! Messenger
> > http://br.messenger.yahoo.com/
> >
> > --
> > Fedora-users-br mailing list
> > [e-mail]
> > https://www.redhat.com/mailman/listinfo/fedora-users-br
>
> --
> Fedora-users-br mailing list
> [e-mail]
> https://www.redhat.com/mailman/listinfo/fedora-users-br

[Otto Fuchshuber Filho]

Você não consegue ver a arquitetura com estes comandos

Saudações,
Otto Fuchshuber Filho
[e-mail]

Cristiano Furtado escreveu, Em 10-04-2007 22:03:
> Não seir amias pratico dar o comando uname -a e rpm -qa |grep kernel???
>
> Em 10/04/07, *Otto Fuchshuber Filho* <[e-mail] 
> > escreveu:
> Justamente o que o André Felício suspeitava.  Você está com o
> kernel i586 e o kernel-devel i686.
> Troque um dos dois para que ambos fiquem com a mesma versão.
>
> Saudações,
> Otto Fuchshuber Filho
> [e-mail] <mailto:[e-mail]>
>
> PaTricK escreveu, Em 10-04-2007 21:31:
>  > Olá,
>  > tá aí o comando:
>  >
>  > root@localhost ~]# rpm --qf '%{name}-%{version}-%{release}.%{arch}\n'
>  > -qa |grep kernel
>  > kernel-2.6.20-1.2933.fc6.i586
>  > kernel-headers-2.6.20-1.2933.fc6.i386
>  > kernel-devel-2.6.20-1.2933.fc6.i686
>  >
>  >
>  > */André Felício <[e-mail]
> <mailto:[e-mail]>>/* escreveu:
>  >
>  >     Rau,
>  >
>  >      > Mande o rpm a saida rpm de outro modo:
>  >      >
>  >      > # rpm --qf '%{name}-%{version}-%{release}.%{arch}\n' -qa
> |grep kernel
>  >
>  >     Esqueci de explicar o motivo.
>  >     A pouco tempo instalei um FC6 e quando fui instalar o vmware,
> estava
>  >     dando o
>  >     mesmo erro.
>  >
>  >     Para minha surpresa a maquina estava usando um kernel i586 em um
>  >     pentium 4.
>  >     Pior, quando mandei instalar pelo yum o kernel-devel
> instalado foi o
>  >     i686.
>  >
>  >     Só percebi este possível *BUG* quando fui instalar o vmware.
>  >
>  >     --
>  >     Att,
>  >
>  >     André Felício
>  >     http://www.felicio.com.br
>  >
>  >     He is considered a most graceful speaker who can say nothing
> in the
>  >     most
>  >     words.
>  >     --
>  >     Fedora-users-br mailing list
>  >     [e-mail] <mailto:[e-mail]>
>  >     https://www.redhat.com/mailman/listinfo/fedora-users-br
>  >
>  >
>  > __________________________________________________
>  > Fale com seus amigos de graça com o novo Yahoo! Messenger
>  > http://br.messenger.yahoo.com/
>  >
>  >
>  >
> ------------------------------------------------------------------------
>  >
>  > --
>  > Fedora-users-br mailing list
>  > [e-mail] <mailto:[e-mail]>
>  > https://www.redhat.com/mailman/listinfo/fedora-users-br
>
> --
> Fedora-users-br mailing list
> [e-mail] <mailto:[e-mail]>
> https://www.redhat.com/mailman/listinfo/fedora-users-br
>
>
>
>
> -- 
> Cristiano Furtado dos Santos
> Gerente de TI - Projetos de Software Livre
> http://jasonnfedora.eti.br
> http://fedora.org.br
>
> --
> Fedora-users-br mailing list
> [e-mail]
> https://www.redhat.com/mailman/listinfo/fedora-users-br

[Cristiano Furtado]

[root@fbrasil ~]# uname -a
Linux fbrasil 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:37:32 EDT 2006 i686
i686 i3
86 GNU/Linux

Não???

Em 10/04/07, Otto Fuchshuber Filho  escreveu:
> Você não consegue ver a arquitetura com estes comandos
>
> Saudações,
> Otto Fuchshuber Filho
> [e-mail]
>
> Cristiano Furtado escreveu, Em 10-04-2007 22:03:
> > Não seir amias pratico dar o comando uname -a e rpm -qa |grep kernel???
> >
> > Em 10/04/07, *Otto Fuchshuber Filho* <[e-mail]
> > > escreveu:
> > Justamente o que o André Felício suspeitava.  Você está com o
> > kernel i586 e o kernel-devel i686.
> > Troque um dos dois para que ambos fiquem com a mesma versão.
> >
> > Saudações,
> > Otto Fuchshuber Filho
> > [e-mail] <mailto:[e-mail]>
> >
> > PaTricK escreveu, Em 10-04-2007 21:31:
> >  > Olá,
> >  > tá aí o comando:
> >  >
> >  > root@localhost ~]# rpm --qf
>
> '%{name}-%{version}-%{release}.%{arch}\n'
> >  > -qa |grep kernel
> >  > kernel-2.6.20-1.2933.fc6.i586
> >  > kernel-headers-2.6.20-1.2933.fc6.i386
> >  > kernel-devel-2.6.20-1.2933.fc6.i686
> >  >
> >  >
> >  > */André Felício <[e-mail]
> > <mailto:[e-mail]>>/* escreveu:
> >  >
> >  >     Rau,
> >  >
> >  >      > Mande o rpm a saida rpm de outro modo:
> >  >      >
> >  >      > # rpm --qf '%{name}-%{version}-%{release}.%{arch}\n' -qa
> > |grep kernel
> >  >
> >  >     Esqueci de explicar o motivo.
> >  >     A pouco tempo instalei um FC6 e quando fui instalar o vmware,
> > estava
> >  >     dando o
> >  >     mesmo erro.
> >  >
> >  >     Para minha surpresa a maquina estava usando um kernel i586 em
>
> um
> >  >     pentium 4.
> >  >     Pior, quando mandei instalar pelo yum o kernel-devel
> > instalado foi o
> >  >     i686.
> >  >
> >  >     Só percebi este possível *BUG* quando fui instalar o vmware.
> >  >
> >  >     --
> >  >     Att,
> >  >
> >  >     André Felício
> >  >     http://www.felicio.com.br
> >  >
> >  >     He is considered a most graceful speaker who can say nothing
> > in the
> >  >     most
> >  >     words.
> >  >     --
> >  >     Fedora-users-br mailing list
> >  >     [e-mail] <mailto:[e-mail]
> >
> >  >     https://www.redhat.com/mailman/listinfo/fedora-users-br
> >  >
> >  >
> >  > __________________________________________________
> >  > Fale com seus amigos de graça com o novo Yahoo! Messenger
> >  > http://br.messenger.yahoo.com/
> >  >
> >  >
> >  >
> >  >
> >  > --
> >  > Fedora-users-br mailing list
> >  > [e-mail] <mailto:[e-mail]>
> >  > https://www.redhat.com/mailman/listinfo/fedora-users-br
> >
> > --
> > Fedora-users-br mailing list
> > [e-mail] <mailto:[e-mail]>
> > https://www.redhat.com/mailman/listinfo/fedora-users-br
> >
> >
> >
> >
> > --
> > Cristiano Furtado dos Santos
> > Gerente de TI - Projetos de Software Livre
> > http://jasonnfedora.eti.br
> > http://fedora.org.br
> >
> > --
> > Fedora-users-br mailing list
> > [e-mail]
> > https://www.redhat.com/mailman/listinfo/fedora-users-br
>
> --
> Fedora-users-br mailing list
> [e-mail]
> https://www.redhat.com/mailman/listinfo/fedora-users-br

[Otto Fuchshuber Filho]

E a arquitetura do kernel-devel?

Saudações,
Otto Fuchshuber Filho
[e-mail]

Cristiano Furtado escreveu, Em 10-04-2007 22:07:
> [root@fbrasil ~]# uname -a
> Linux fbrasil 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:37:32 EDT 2006 i686 
> i686 i3
> 86 GNU/Linux
>
> Não???
>
> Em 10/04/07, *Otto Fuchshuber Filho * <[e-mail] 
> > escreveu:
> Você não consegue ver a arquitetura com estes comandos
>
> Saudações,
> Otto Fuchshuber Filho
> [e-mail] <mailto:[e-mail]>
>
> Cristiano Furtado escreveu, Em 10-04-2007 22:03:
>  > Não seir amias pratico dar o comando uname -a e rpm -qa |grep
> kernel???
>  >
>  > Em 10/04/07, *Otto Fuchshuber Filho* <[e-mail]
> <mailto:[e-mail]>
>  > <mailto:[e-mail] <mailto:[e-mail]>>> escreveu:
>  >
>  >     Justamente o que o André Felício suspeitava.  Você está com o
>  >     kernel i586 e o kernel-devel i686.
>  >     Troque um dos dois para que ambos fiquem com a mesma versão.
>  >
>  >     Saudações,
>  >     Otto Fuchshuber Filho
>  >     [e-mail] <mailto:[e-mail]>
> <mailto:[e-mail] <mailto:[e-mail]>>
>  >
>  >     PaTricK escreveu, Em 10-04-2007 21:31:
>  >      > Olá,
>  >      > tá aí o comando:
>  >      >
>  >      > root@localhost ~]# rpm --qf
> '%{name}-%{version}-%{release}.%{arch}\n'
>  >      > -qa |grep kernel
>  >      > kernel-2.6.20-1.2933.fc6.i586
>  >      > kernel-headers-2.6.20-1.2933.fc6.i386
>  >      > kernel-devel-2.6.20-1.2933.fc6.i686
>  >      >
>  >      >
>  >      > */André Felício <[e-mail]
> <mailto:[e-mail]>
>  >     <mailto: [e-mail]
> <mailto:[e-mail]>>>/* escreveu:
>  >      >
>  >      >     Rau,
>  >      >
>  >      >      > Mande o rpm a saida rpm de outro modo:
>  >      >      >
>  >      >      > # rpm --qf
> '%{name}-%{version}-%{release}.%{arch}\n' -qa
>  >     |grep kernel
>  >      >
>  >      >     Esqueci de explicar o motivo.
>  >      >     A pouco tempo instalei um FC6 e quando fui instalar o
> vmware,
>  >     estava
>  >      >     dando o
>  >      >     mesmo erro.
>  >      >
>  >      >     Para minha surpresa a maquina estava usando um kernel
> i586 em um
>  >      >     pentium 4.
>  >      >     Pior, quando mandei instalar pelo yum o kernel-devel
>  >     instalado foi o
>  >      >     i686.
>  >      >
>  >      >     Só percebi este possível *BUG* quando fui instalar o
> vmware.
>  >      >
>  >      >     --
>  >      >     Att,
>  >      >
>  >      >     André Felício
>  >      >     http://www.felicio.com.br
>  >      >
>  >      >     He is considered a most graceful speaker who can say
> nothing
>  >     in the
>  >      >     most
>  >      >     words.
>  >      >     --
>  >      >     Fedora-users-br mailing list
>  >      >     [e-mail]
> <mailto:[e-mail]>
> <mailto:[e-mail] <mailto:[e-mail]>>
>  >      >    
> https://www.redhat.com/mailman/listinfo/fedora-users-br
> <https://www.redhat.com/mailman/listinfo/fedora-users-br>
>  >      >
>  >      >
>  >      > __________________________________________________
>  >      > Fale com seus amigos de graça com o novo Yahoo! Messenger
>  >      > http://br.messenger.yahoo.com/
>  >      >
>  >      >
>  >      >
>  >    
> ------------------------------------------------------------------------
>  >      >
>  >      > --
>  >      > Fedora-users-br mailing list
>  >      > [e-mail]
> <mailto:[e-mail]>
> <mailto:[e-mail] <mailto:[e-mail]>>
>  >      > https://www.redhat.com/mailman/listinfo/fedora-users-br
>  >
>  >     --
>  >     Fedora-users-br mailing list
>  >     [e-mail]
> <mailto:[e-mail]> <mailto:
> [e-mail] <mailto:[e-mail]>>
>  >     https://www.redhat.com/mailman/listinfo/fedora-users-br
>  >
>  >
>  >
>  >
>  > --
>  > Cristiano Furtado dos Santos
>  > Gerente de TI - Projetos de Software Livre
>  > http://jasonnfedora.eti.br
>  > http://fedora.org.br
>  >
>  >
>  >
> ------------------------------------------------------------------------
>  >
>  > --
>  > Fedora-users-br mailing list
>  > [e-mail] <mailto:[e-mail]>
>  > https://www.redhat.com/mailman/listinfo/fedora-users-br
>
> --
> Fedora-users-br mailing list
> [e-mail] <mailto:[e-mail]>
> https://www.redhat.com/mailman/listinfo/fedora-users-br
>
>
>
>
> -- 
> Cristiano Furtado dos Santos
> Gerente de TI - Projetos de Software Livre
> http://jasonnfedora.eti.br
> http://fedora.org.br
>
> --
> Fedora-users-br mailing list
> [e-mail]
> https://www.redhat.com/mailman/listinfo/fedora-users-br

[Cristiano Furtado]

Bom pelo que sei se ele esta usando um kernel provavelmente é o mesmo :)
Manda dar ae um yum install kernel e quero ver ele instalar de outro :)

Em 10/04/07, Otto Fuchshuber Filho  escreveu:
> E a arquitetura do kernel-devel?
>
> Saudações,
> Otto Fuchshuber Filho
> [e-mail]
>
> Cristiano Furtado escreveu, Em 10-04-2007 22:07:
> > [root@fbrasil ~]# uname -a
> > Linux fbrasil 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:37:32 EDT 2006 i686
> > i686 i3
> > 86 GNU/Linux
> >
> > Não???
> >
> > Em 10/04/07, *Otto Fuchshuber Filho * <[e-mail]
> > > escreveu:
> > Você não consegue ver a arquitetura com estes comandos
> >
> > Saudações,
> > Otto Fuchshuber Filho
> > [e-mail] <mailto:[e-mail]>
> >
> > Cristiano Furtado escreveu, Em 10-04-2007 22:03:
> >  > Não seir amias pratico dar o comando uname -a e rpm -qa |grep
> > kernel???
> >  >
> >  > Em 10/04/07, *Otto Fuchshuber Filho* <[e-mail]
> > <mailto:[e-mail]>
> >  > <mailto:[e-mail] <mailto:[e-mail]>>> escreveu:
> >  >
> >  >     Justamente o que o André Felício suspeitava.  Você está com o
> >  >     kernel i586 e o kernel-devel i686.
> >  >     Troque um dos dois para que ambos fiquem com a mesma versão.
> >  >
> >  >     Saudações,
> >  >     Otto Fuchshuber Filho
> >  >     [e-mail] <mailto:[e-mail]>
> > <mailto:[e-mail] <mailto:[e-mail]>>
> >  >
> >  >     PaTricK escreveu, Em 10-04-2007 21:31:
> >  >      > Olá,
> >  >      > tá aí o comando:
> >  >      >
> >  >      > root@localhost ~]# rpm --qf
> > '%{name}-%{version}-%{release}.%{arch}\n'
> >  >      > -qa |grep kernel
> >  >      > kernel-2.6.20-1.2933.fc6.i586
> >  >      > kernel-headers-2.6.20-1.2933.fc6.i386
> >  >      > kernel-devel-2.6.20-1.2933.fc6.i686
> >  >      >
> >  >      >
> >  >      > */André Felício <[e-mail]
> > <mailto:[e-mail]>
> >  >     <mailto: [e-mail]
> > <mailto:[e-mail]>>>/* escreveu:
> >  >      >
> >  >      >     Rau,
> >  >      >
> >  >      >      > Mande o rpm a saida rpm de outro modo:
> >  >      >      >
> >  >      >      > # rpm --qf
> > '%{name}-%{version}-%{release}.%{arch}\n' -qa
> >  >     |grep kernel
> >  >      >
> >  >      >     Esqueci de explicar o motivo.
> >  >      >     A pouco tempo instalei um FC6 e quando fui instalar o
> > vmware,
> >  >     estava
> >  >      >     dando o
> >  >      >     mesmo erro.
> >  >      >
> >  >      >     Para minha surpresa a maquina estava usando um kernel
> > i586 em um
> >  >      >     pentium 4.
> >  >      >     Pior, quando mandei instalar pelo yum o kernel-devel
> >  >     instalado foi o
> >  >      >     i686.
> >  >      >
> >  >      >     Só percebi este possível *BUG* quando fui instalar o
> > vmware.
> >  >      >
> >  >      >     --
> >  >      >     Att,
> >  >      >
> >  >      >     André Felício
> >  >      >     http://www.felicio.com.br
> >  >      >
> >  >      >     He is considered a most graceful speaker who can say
> > nothing
> >  >     in the
> >  >      >     most
> >  >      >     words.
> >  >      >     --
> >  >      >     Fedora-users-br mailing list
> >  >      >     [e-mail]
> > <mailto:[e-mail]>
> > <mailto:[e-mail] <mailto:
>
> [e-mail]>>
> >  >      >
> > https://www.redhat.com/mailman/listinfo/fedora-users-br
> > <https://www.redhat.com/mailman/listinfo/fedora-users-br>
> >  >      >
> >  >      >
> >  >      > __________________________________________________
> >  >      > Fale com seus amigos de graça com o novo Yahoo! Messenger
> >  >      > http://br.messenger.yahoo.com/
> >  >      >
> >  >      >
> >  >      >
> >  >
> >  >      >
> >  >      > --
> >  >      > Fedora-users-br mailing list
> >  >      > [e-mail]
> > <mailto:[e-mail]>
> > <mailto:[e-mail] <mailto:
>
> [e-mail]>>
> >  >      > https://www.redhat.com/mailman/listinfo/fedora-users-br
> >  >
> >  >     --
> >  >     Fedora-users-br mailing list
> >  >     [e-mail]
> > <mailto:[e-mail]> <mailto:
> > [e-mail] <mailto:[e-mail]>>
> >  >     https://www.redhat.com/mailman/listinfo/fedora-users-br
> >  >
> >  >
> >  >
> >  >
> >  > --
> >  > Cristiano Furtado dos Santos
> >  > Gerente de TI - Projetos de Software Livre
> >  > http://jasonnfedora.eti.br
> >  > http://fedora.org.br
> >  >
> >  >
> >  >
> >  >
> >  > --
> >  > Fedora-users-br mailing list
> >  > [e-mail] <mailto:[e-mail]>
> >  > https://www.redhat.com/mailman/listinfo/fedora-users-br
> >
> > --
> > Fedora-users-br mailing list
> > [e-mail] <mailto:[e-mail]>
> > https://www.redhat.com/mailman/listinfo/fedora-users-br
> >
> >
> >
> >
> > --
> > Cristiano Furtado dos Santos
> > Gerente de TI - Projetos de Software Livre
> > http://jasonnfedora.eti.br
> > http://fedora.org.br
> >
> > --
> > Fedora-users-br mailing list
> > [e-mail]
> > https://www.redhat.com/mailman/listinfo/fedora-users-br
>
> --
> Fedora-users-br mailing list
> [e-mail]
> https://www.redhat.com/mailman/listinfo/fedora-users-br

[Otto Fuchshuber Filho]

Olha pela reposta do PaTricK que não é:
kernel-2.6.20-1.2933.fc6.i586
kernel-devel-2.6.20-1.2933.fc6.i686

É um bug de instalação (já vi documentado em algum lugar, não 
lembro onde).  Quando instalei o FC6 no meu notebook aconteceu 
exatamente isto, kernel e kernel-devel com arquiteturas diferentes.

Saudações,
Otto Fuchshuber Filho
[e-mail]

Cristiano Furtado escreveu, Em 10-04-2007 22:14:
> Bom pelo que sei se ele esta usando um kernel provavelmente é o mesmo :)
> Manda dar ae um yum install kernel e quero ver ele instalar de outro :)
>
> Em 10/04/07, * Otto Fuchshuber Filho* <[e-mail] 
> > escreveu:
> E a arquitetura do kernel-devel?
>
> Saudações,
> Otto Fuchshuber Filho
> [e-mail] <mailto:[e-mail]>
>
> Cristiano Furtado escreveu, Em 10-04-2007 22:07:
>  > [root@fbrasil ~]# uname -a
>  > Linux fbrasil 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:37:32 EDT
> 2006 i686
>  > i686 i3
>  > 86 GNU/Linux
>  >
>  > Não???
>  >
>  > Em 10/04/07, *Otto Fuchshuber Filho * < [e-mail]
> <mailto:[e-mail]>
>  > <mailto:[e-mail] <mailto:[e-mail]>>> escreveu:
>  >
>  >     Você não consegue ver a arquitetura com estes comandos
>  >
>  >     Saudações,
>  >     Otto Fuchshuber Filho
>  >     [e-mail] <mailto:[e-mail]>
> <mailto:[e-mail] <mailto:[e-mail]>>
>  >
>  >     Cristiano Furtado escreveu, Em 10-04-2007 22:03:
>  >      > Não seir amias pratico dar o comando uname -a e rpm -qa |grep
>  >     kernel???
>  >      >
>  >      > Em 10/04/07, *Otto Fuchshuber Filho* <[e-mail]
> <mailto:[e-mail]>
>  >     <mailto:[e-mail] <mailto:[e-mail]>>
>  >      > <mailto:[e-mail] <mailto:[e-mail]>
> <mailto:[e-mail] <mailto:[e-mail]>>>> escreveu:
>  >      >
>  >      >     Justamente o que o André Felício suspeitava.  Você
> está com o
>  >      >     kernel i586 e o kernel-devel i686.
>  >      >     Troque um dos dois para que ambos fiquem com a mesma
> versão.
>  >      >
>  >      >     Saudações,
>  >      >     Otto Fuchshuber Filho
>  >      >     [e-mail] <mailto:[e-mail]>
> <mailto:[e-mail] <mailto:[e-mail]>>
>  >     <mailto:[e-mail] <mailto:[e-mail]>
> <mailto:[e-mail] <mailto:[e-mail]>>>
>  >      >
>  >      >     PaTricK escreveu, Em 10-04-2007 21:31:
>  >      >      > Olá,
>  >      >      > tá aí o comando:
>  >      >      >
>  >      >      > root@localhost ~]# rpm --qf
>  >     '%{name}-%{version}-%{release}.%{arch}\n'
>  >      >      > -qa |grep kernel
>  >      >      > kernel-2.6.20-1.2933.fc6.i586
>  >      >      > kernel-headers-2.6.20-1.2933.fc6.i386
>  >      >      > kernel-devel-2.6.20-1.2933.fc6.i686
>  >      >      >
>  >      >      >
>  >      >      > */André Felício <[e-mail]
> <mailto:[e-mail]>
>  >     <mailto: [e-mail] <mailto:[e-mail]>>
>  >      >     <mailto: [e-mail]
> <mailto:[e-mail]>
>  >     <mailto:[e-mail]
> <mailto:[e-mail]>>>>/* escreveu:
>  >      >      >
>  >      >      >     Rau,
>  >      >      >
>  >      >      >      > Mande o rpm a saida rpm de outro modo:
>  >      >      >      >
>  >      >      >      > # rpm --qf
>  >     '%{name}-%{version}-%{release}.%{arch}\n' -qa
>  >      >     |grep kernel
>  >      >      >
>  >      >      >     Esqueci de explicar o motivo.
>  >      >      >     A pouco tempo instalei um FC6 e quando fui
> instalar o
>  >     vmware,
>  >      >     estava
>  >      >      >     dando o
>  >      >      >     mesmo erro.
>  >      >      >
>  >      >      >     Para minha surpresa a maquina estava usando um
> kernel
>  >     i586 em um
>  >      >      >     pentium 4.
>  >      >      >     Pior, quando mandei instalar pelo yum o
> kernel-devel
>  >      >     instalado foi o
>  >      >      >     i686.
>  >      >      >
>  >      >      >     Só percebi este possível *BUG* quando fui
> instalar o
>  >     vmware.
>  >      >      >
>  >      >      >     --
>  >      >      >     Att,
>  >      >      >
>  >      >      >     André Felício
>  >      >      >     http://www.felicio.com.br
>  >      >      >
>  >      >      >     He is considered a most graceful speaker who
> can say
>  >     nothing
>  >      >     in the
>  >      >      >     most
>  >      >      >     words.
>  >      >      >     --
>  >      >      >     Fedora-users-br mailing list
>  >      >      >     [e-mail]
> <mailto:[e-mail]>
>  >     <mailto:[e-mail]
> <mailto:[e-mail]>>
>  >     <mailto: [e-mail]
> <mailto:[e-mail]>
> <mailto:[e-mail] <mailto:[e-mail]>>>
>  >      >      >
>  >     https://www.redhat.com/mailman/listinfo/fedora-users-br
>  >     <https://www.redhat.com/mailman/listinfo/fedora-users-br>
>  >      >      >
>  >      >      >
>  >      >      > __________________________________________________
>  >      >      > Fale com seus amigos de graça com o novo Yahoo!
> Messenger
>  >      >      > http://br.messenger.yahoo.com/
>  >      >      >
>  >      >      >
>  >      >      >
>  >      >
>  >    
> ------------------------------------------------------------------------
>
>  >      >      >
>  >      >      > --
>  >      >      > Fedora-users-br mailing list
>  >      >      > [e-mail]
> <mailto:[e-mail]>
>  >     <mailto:[e-mail]
> <mailto:[e-mail]>>
>  >     <mailto:[e-mail]
> <mailto:[e-mail]> <mailto:
> [e-mail] <mailto:[e-mail]>>>
>  >      >      > https://www.redhat.com/mailman/listinfo/fedora-users-br
>  >      >
>  >      >     --
>  >      >     Fedora-users-br mailing list
>  >      >     [e-mail]
> <mailto:[e-mail]>
>  >     <mailto:[e-mail]
> <mailto:[e-mail]>> <mailto:
>  >     [e-mail]
> <mailto:[e-mail]>
> <mailto:[e-mail] <mailto:[e-mail]>>>
>  >      >     https://www.redhat.com/mailman/listinfo/fedora-users-br
>  >      >
>  >      >
>  >      >
>  >      >
>  >      > --
>  >      > Cristiano Furtado dos Santos
>  >      > Gerente de TI - Projetos de Software Livre
>  >      > http://jasonnfedora.eti.br
>  >      > http://fedora.org.br
>  >      >
>  >      >
>  >      >
>  >    
> ------------------------------------------------------------------------
>  >      >
>  >      > --
>  >      > Fedora-users-br mailing list
>  >      > [e-mail]
> <mailto:[e-mail]>
> <mailto:[e-mail] <mailto:[e-mail]>>
>  >      > https://www.redhat.com/mailman/listinfo/fedora-users-br
>  >
>  >     --
>  >     Fedora-users-br mailing list
>  >     [e-mail]
> <mailto:[e-mail]> <mailto:
> [e-mail] <mailto:[e-mail]>>
>  >     https://www.redhat.com/mailman/listinfo/fedora-users-br
>  >
>  >
>  >
>  >
>  > --
>  > Cristiano Furtado dos Santos
>  > Gerente de TI - Projetos de Software Livre
>  > http://jasonnfedora.eti.br
>  > http://fedora.org.br
>  >
>  >
>  >
> ------------------------------------------------------------------------
>  >
>  > --
>  > Fedora-users-br mailing list
>  > [e-mail] <mailto:[e-mail]>
>  > https://www.redhat.com/mailman/listinfo/fedora-users-br
>
> --
> Fedora-users-br mailing list
> [e-mail] <mailto:[e-mail]>
> https://www.redhat.com/mailman/listinfo/fedora-users-br
>
>
>
>
> -- 
> Cristiano Furtado dos Santos
> Gerente de TI - Projetos de Software Livre
> http://jasonnfedora.eti.br
> http://fedora.org.br
>
> --
> Fedora-users-br mailing list
> [e-mail]
> https://www.redhat.com/mailman/listinfo/fedora-users-br

[Cristiano Furtado]

Bom isso pode realmente acontecer. Espero que seja corrido no F7.

Em 10/04/07, Otto Fuchshuber Filho  escreveu:
> Olha pela reposta do PaTricK que não é:
> kernel-2.6.20-1.2933.fc6.i586
> kernel-devel-2.6.20-1.2933.fc6.i686
>
> É um bug de instalação (já vi documentado em algum lugar, não
> lembro onde).  Quando instalei o FC6 no meu notebook aconteceu
> exatamente isto, kernel e kernel-devel com arquiteturas diferentes.
>
> Saudações,
> Otto Fuchshuber Filho
> [e-mail]
>
> Cristiano Furtado escreveu, Em 10-04-2007 22:14:
> > Bom pelo que sei se ele esta usando um kernel provavelmente é o mesmo :)
> > Manda dar ae um yum install kernel e quero ver ele instalar de outro :)
> >
> > Em 10/04/07, * Otto Fuchshuber Filho* <[e-mail]
> > > escreveu:
> > E a arquitetura do kernel-devel?
> >
> > Saudações,
> > Otto Fuchshuber Filho
> > [e-mail] <mailto:[e-mail]>
> >
> > Cristiano Furtado escreveu, Em 10-04-2007 22:07:
> >  > [root@fbrasil ~]# uname -a
> >  > Linux fbrasil 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:37:32 EDT
> > 2006 i686
> >  > i686 i3
> >  > 86 GNU/Linux
> >  >
> >  > Não???
> >  >
> >  > Em 10/04/07, *Otto Fuchshuber Filho * < [e-mail]
> > <mailto:[e-mail]>
> >  > <mailto:[e-mail] <mailto:[e-mail]>>> escreveu:
> >  >
> >  >     Você não consegue ver a arquitetura com estes comandos
> >  >
> >  >     Saudações,
> >  >     Otto Fuchshuber Filho
> >  >     [e-mail] <mailto:[e-mail]>
> > <mailto:[e-mail] <mailto:[e-mail]>>
> >  >
> >  >     Cristiano Furtado escreveu, Em 10-04-2007 22:03:
> >  >      > Não seir amias pratico dar o comando uname -a e rpm -qa
>
> |grep
> >  >     kernel???
> >  >      >
> >  >      > Em 10/04/07, *Otto Fuchshuber Filho* <[e-mail]
> > <mailto:[e-mail]>
> >  >     <mailto:[e-mail] <mailto:[e-mail]>>
> >  >      > <mailto:[e-mail] <mailto:[e-mail]>
> > <mailto:[e-mail] <mailto:[e-mail]>>>> escreveu:
> >  >      >
> >  >      >     Justamente o que o André Felício suspeitava.  Você
> > está com o
> >  >      >     kernel i586 e o kernel-devel i686.
> >  >      >     Troque um dos dois para que ambos fiquem com a mesma
> > versão.
> >  >      >
> >  >      >     Saudações,
> >  >      >     Otto Fuchshuber Filho
> >  >      >     [e-mail] <mailto:[e-mail]>
> > <mailto:[e-mail] <mailto:[e-mail]>>
> >  >     <mailto:[e-mail] <mailto:[e-mail]>
> > <mailto:[e-mail] <mailto:[e-mail]>>>
> >  >      >
> >  >      >     PaTricK escreveu, Em 10-04-2007 21:31:
> >  >      >      > Olá,
> >  >      >      > tá aí o comando:
> >  >      >      >
> >  >      >      > root@localhost ~]# rpm --qf
> >  >     '%{name}-%{version}-%{release}.%{arch}\n'
> >  >      >      > -qa |grep kernel
> >  >      >      > kernel-2.6.20-1.2933.fc6.i586
> >  >      >      > kernel-headers-2.6.20-1.2933.fc6.i386
> >  >      >      > kernel-devel-2.6.20-1.2933.fc6.i686
> >  >      >      >
> >  >      >      >
> >  >      >      > */André Felício <[e-mail]
> > <mailto:[e-mail]>
> >  >     <mailto: [e-mail] <mailto:[e-mail]>>
> >  >      >     <mailto: [e-mail]
> > <mailto:[e-mail]>
> >  >     <mailto:[e-mail]
> > <mailto:[e-mail]>>>>/* escreveu:
> >  >      >      >
> >  >      >      >     Rau,
> >  >      >      >
> >  >      >      >      > Mande o rpm a saida rpm de outro modo:
> >  >      >      >      >
> >  >      >      >      > # rpm --qf
> >  >     '%{name}-%{version}-%{release}.%{arch}\n' -qa
> >  >      >     |grep kernel
> >  >      >      >
> >  >      >      >     Esqueci de explicar o motivo.
> >  >      >      >     A pouco tempo instalei um FC6 e quando fui
> > instalar o
> >  >     vmware,
> >  >      >     estava
> >  >      >      >     dando o
> >  >      >      >     mesmo erro.
> >  >      >      >
> >  >      >      >     Para minha surpresa a maquina estava usando um
> > kernel
> >  >     i586 em um
> >  >      >      >     pentium 4.
> >  >      >      >     Pior, quando mandei instalar pelo yum o
> > kernel-devel
> >  >      >     instalado foi o
> >  >      >      >     i686.
> >  >      >      >
> >  >      >      >     Só percebi este possível *BUG* quando fui
> > instalar o
> >  >     vmware.
> >  >      >      >
> >  >      >      >     --
> >  >      >      >     Att,
> >  >      >      >
> >  >      >      >     André Felício
> >  >      >      >     http://www.felicio.com.br
> >  >      >      >
> >  >      >      >     He is considered a most graceful speaker who
> > can say
> >  >     nothing
> >  >      >     in the
> >  >      >      >     most
> >  >      >      >     words.
> >  >      >      >     --
> >  >      >      >     Fedora-users-br mailing list
> >  >      >      >     [e-mail]
> > <mailto:[e-mail]>
> >  >     <mailto:[e-mail]
> > <mailto:[e-mail]>>
> >  >     <mailto: [e-mail]
> > <mailto:[e-mail]>
> > <mailto:[e-mail] <mailto:
>
> [e-mail]>>>
> >  >      >      >
> >  >     https://www.redhat.com/mailman/listinfo/fedora-users-br
> >  >     <https://www.redhat.com/mailman/listinfo/fedora-users-br>
> >  >      >      >
> >  >      >      >
> >  >      >      > __________________________________________________
> >  >      >      > Fale com seus amigos de graça com o novo Yahoo!
> > Messenger
> >  >      >      > http://br.messenger.yahoo.com/
> >  >      >      >
> >  >      >      >
> >  >      >      >
> >  >      >
> >  >
> >  >      >      >
> >  >      >      > --
> >  >      >      > Fedora-users-br mailing list
> >  >      >      > [e-mail]
> > <mailto:[e-mail]>
> >  >     <mailto:[e-mail]
> > <mailto:[e-mail]>>
> >  >     <mailto:[e-mail]
> > <mailto:[e-mail]> <mailto:
> > [e-mail] <mailto:[e-mail]>>>
> >  >      >      >
>
> https://www.redhat.com/mailman/listinfo/fedora-users-br
> >  >      >
> >  >      >     --
> >  >      >     Fedora-users-br mailing list
> >  >      >     [e-mail]
> > <mailto:[e-mail]>
> >  >     <mailto:[e-mail]
> > <mailto:[e-mail]>> <mailto:
> >  >     [e-mail]
> > <mailto:[e-mail]>
> > <mailto:[e-mail] <mailto:
>
> [e-mail]>>>
> >  >      >
>
> https://www.redhat.com/mailman/listinfo/fedora-users-br
> >  >      >
> >  >      >
> >  >      >
> >  >      >
> >  >      > --
> >  >      > Cristiano Furtado dos Santos
> >  >      > Gerente de TI - Projetos de Software Livre
> >  >      > http://jasonnfedora.eti.br
> >  >      > http://fedora.org.br
> >  >      >
> >  >      >
> >  >      >
> >  >
> >  >      >
> >  >      > --
> >  >      > Fedora-users-br mailing list
> >  >      > [e-mail]
> > <mailto:[e-mail]>
> > <mailto:[e-mail] <mailto:
>
> [e-mail]>>
> >  >      > https://www.redhat.com/mailman/listinfo/fedora-users-br
> >  >
> >  >     --
> >  >     Fedora-users-br mailing list
> >  >     [e-mail]
> > <mailto:[e-mail]> <mailto:
> > [e-mail] <mailto:[e-mail]>>
> >  >     https://www.redhat.com/mailman/listinfo/fedora-users-br
> >  >
> >  >
> >  >
> >  >
> >  > --
> >  > Cristiano Furtado dos Santos
> >  > Gerente de TI - Projetos de Software Livre
> >  > http://jasonnfedora.eti.br
> >  > http://fedora.org.br
> >  >
> >  >
> >  >
> >  >
> >  > --
> >  > Fedora-users-br mailing list
> >  > [e-mail] <mailto:[e-mail]>
> >  > https://www.redhat.com/mailman/listinfo/fedora-users-br
> >
> > --
> > Fedora-users-br mailing list
> > [e-mail] <mailto:[e-mail]>
> > https://www.redhat.com/mailman/listinfo/fedora-users-br
> >
> >
> >
> >
> > --
> > Cristiano Furtado dos Santos
> > Gerente de TI - Projetos de Software Livre
> > http://jasonnfedora.eti.br
> > http://fedora.org.br
> >
> > --
> > Fedora-users-br mailing list
> > [e-mail]
> > https://www.redhat.com/mailman/listinfo/fedora-users-br
>
> --
> Fedora-users-br mailing list
> [e-mail]
> https://www.redhat.com/mailman/listinfo/fedora-users-br

[Patrick]

olá
está aí!

[root@localhost include]# uname -a
Linux localhost.localdomain 2.6.20-1.2933.fc6 #1 SMP Mon Mar 19 10:42:48 
EDT 2007 i686 athlon i386 GNU/Linux

Cristiano Furtado escreveu:
> Não seir amias pratico dar o comando uname -a e rpm -qa |grep kernel???
>
> Em 10/04/07, *Otto Fuchshuber Filho* <[e-mail] 
> > escreveu:
> Justamente o que o André Felício suspeitava.  Você está com o
> kernel i586 e o kernel-devel i686.
> Troque um dos dois para que ambos fiquem com a mesma versão.
>
> Saudações,
> Otto Fuchshuber Filho
> [e-mail] <mailto:[e-mail]>
>
> PaTricK escreveu, Em 10-04-2007 21:31:
> > Olá,
> > tá aí o comando:
> >
> > root@localhost ~]# rpm --qf
> '%{name}-%{version}-%{release}.%{arch}\n'
> > -qa |grep kernel
> > kernel-2.6.20-1.2933.fc6.i586
> > kernel-headers-2.6.20-1.2933.fc6.i386
> > kernel-devel-2.6.20-1.2933.fc6.i686
> >
> >
> > */André Felício <[e-mail]
> <mailto:[e-mail]>>/* escreveu:
> >
> >     Rau,
> >
> >      > Mande o rpm a saida rpm de outro modo:
> >      >
> >      > # rpm --qf '%{name}-%{version}-%{release}.%{arch}\n' -qa
> |grep kernel
> >
> >     Esqueci de explicar o motivo.
> >     A pouco tempo instalei um FC6 e quando fui instalar o
> vmware, estava
> >     dando o
> >     mesmo erro.
> >
> >     Para minha surpresa a maquina estava usando um kernel i586 em um
> >     pentium 4.
> >     Pior, quando mandei instalar pelo yum o kernel-devel
> instalado foi o
> >     i686.
> >
> >     Só percebi este possível *BUG* quando fui instalar o vmware.
> >
> >     --
> >     Att,
> >
> >     André Felício
> >     http://www.felicio.com.br
> >
> >     He is considered a most graceful speaker who can say nothing
> in the
> >     most
> >     words.
> >     --
> >     Fedora-users-br mailing list
> >     [e-mail] <mailto:[e-mail]>
> >     https://www.redhat.com/mailman/listinfo/fedora-users-br
> >
> >
> > __________________________________________________
> > Fale com seus amigos de graça com o novo Yahoo! Messenger
> > http://br.messenger.yahoo.com/
> >
> >
> >
> ------------------------------------------------------------------------
> >
> > --
> > Fedora-users-br mailing list
> > [e-mail] <mailto:[e-mail]>
> > https://www.redhat.com/mailman/listinfo/fedora-users-br
>
> --
> Fedora-users-br mailing list
> [e-mail] <mailto:[e-mail]>
> https://www.redhat.com/mailman/listinfo/fedora-users-br
>
>
>
>
> -- 
> Cristiano Furtado dos Santos
> Gerente de TI - Projetos de Software Livre
> http://jasonnfedora.eti.br
> http://fedora.org.br
>
> --
> Fedora-users-br mailing list
> [e-mail]
> https://www.redhat.com/mailman/listinfo/fedora-users-br

[Patrick]

Olá,
Agora deu certo... eu não ia percebe esse problema tão cedo. Muito 
obrigado pela ajuda!

PaTricK

PaTricK escreveu:
> olá
> está aí!
>
> [root@localhost include]# uname -a
> Linux localhost.localdomain 2.6.20-1.2933.fc6 #1 SMP Mon Mar 19 
> 10:42:48 EDT 2007 i686 athlon i386 GNU/Linux
>
> Cristiano Furtado escreveu:
> > Não seir amias pratico dar o comando uname -a e rpm -qa |grep kernel???
> >
> > Em 10/04/07, *Otto Fuchshuber Filho* <[e-mail] 
> > > escreveu:
> > Justamente o que o André Felício suspeitava.  Você está com o
> > kernel i586 e o kernel-devel i686.
> > Troque um dos dois para que ambos fiquem com a mesma versão.
> >
> > Saudações,
> > Otto Fuchshuber Filho
> > [e-mail] <mailto:[e-mail]>
> >
> > PaTricK escreveu, Em 10-04-2007 21:31:
> > > Olá,
> > > tá aí o comando:
> > >
> > > root@localhost ~]# rpm --qf
> > '%{name}-%{version}-%{release}.%{arch}\n'
> > > -qa |grep kernel
> > > kernel-2.6.20-1.2933.fc6.i586
> > > kernel-headers-2.6.20-1.2933.fc6.i386
> > > kernel-devel-2.6.20-1.2933.fc6.i686
> > >
> > >
> > > */André Felício <[e-mail]
> > <mailto:[e-mail]>>/* escreveu:
> > >
> > >     Rau,
> > >
> > >      > Mande o rpm a saida rpm de outro modo:
> > >      >
> > >      > # rpm --qf '%{name}-%{version}-%{release}.%{arch}\n' -qa
> > |grep kernel
> > >
> > >     Esqueci de explicar o motivo.
> > >     A pouco tempo instalei um FC6 e quando fui instalar o
> > vmware, estava
> > >     dando o
> > >     mesmo erro.
> > >
> > >     Para minha surpresa a maquina estava usando um kernel i586 
> >
> > em um
> >     >     pentium 4.
> >     >     Pior, quando mandei instalar pelo yum o kernel-devel
> >     instalado foi o
> >     >     i686.
> >     >
> >     >     Só percebi este possível *BUG* quando fui instalar o vmware.
> >     >
> >     >     --
> >     >     Att,
> >     >
> >     >     André Felício
> >     >     http://www.felicio.com.br
> >     >
> >     >     He is considered a most graceful speaker who can say nothing
> >     in the
> >     >     most
> >     >     words.
> >     >     --
> >     >     Fedora-users-br mailing list
> >     >     [e-mail] 
> >     >     https://www.redhat.com/mailman/listinfo/fedora-users-br
> >     >
> >     >
> >     > __________________________________________________
> >     > Fale com seus amigos de graça com o novo Yahoo! Messenger
> >     > http://br.messenger.yahoo.com/
> >     >
> >     >
> >     >
> > >
> > > --
> > > Fedora-users-br mailing list
> > > [e-mail] <mailto:[e-mail]>
> > > https://www.redhat.com/mailman/listinfo/fedora-users-br
> >
> > --
> > Fedora-users-br mailing list
> > [e-mail] <mailto:[e-mail]>
> > https://www.redhat.com/mailman/listinfo/fedora-users-br
> >
> >
> >
> >
> > -- 
> > Cristiano Furtado dos Santos
> > Gerente de TI - Projetos de Software Livre
> > http://jasonnfedora.eti.br
> > http://fedora.org.br
> >
> > -- 
> > Fedora-users-br mailing list
> > [e-mail]
> > https://www.redhat.com/mailman/listinfo/fedora-users-br
>
> -- 
> Fedora-users-br mailing list
> [e-mail]
> https://www.redhat.com/mailman/listinfo/fedora-users-br