#$!@

[Cyber Source]

Not sure about Debian but we needed to run the script  vmware-any-any 
updates. If you need that, I can send it to you.

JJ Neff wrote:

>I did try it and it failed at the 2 modules that VMware needs.  (vmnet and
>vmmod or whatever). I was able to get the modules to compile with a gcc 3.3.6
>compiled kernel and a 3.3.5 gcc installed (or vice versa).  It warned me it was
>different but compiled anyway. I had t change the gcc and the gcc-bug symlinks
>to point from gcc4 to gcc3.3.x binaries.
>
>JJ
>
>--- Jesse Jarzynka <denisesballs at thecybersource.com> wrote:
>
>  
>
>>JJ Neff wrote:
>>
>>    
>>
>>>Unfortunately as hinted at before this is not Fedora specific.  I did as
>>>      
>>>
>>much
>>    
>>
>>>screaming at my monitor trying to get a wireless nic to run on a laptop
>>>      
>>>
>>under
>>    
>>
>>>Debian.  Everytime I tried to compile or install the source it didn't match
>>>      
>>>
>>my
>>    
>>
>>>kernel by one character.  Then I'd find out that the version of kernel (from
>>>deb package) had no installable source (running testing).  I then couldn't
>>>      
>>>
>>get
>>    
>>
>>>VMware to run due to kernel version being slightly different than source and
>>>then don't get me started on version of GCC.  Seems the kernel I was running
>>>had been compiled with gcc3.6 but I was running gcc 4 (default gcc in
>>>      
>>>
>>testing).
>>    
>>
>>>Then I finally found a kernel that had been compiled with 3.3.5 and the gcc
>>>3.3.6 I was able to trick my machine into using (changing enough symlinks)
>>>      
>>>
>>was
>>    
>>
>>>close enough. Now I'm practically afraid to reboot :-)  OK I made the change
>>>      
>>>
>>in
>>    
>>
>>>Grub to boor old kernel by default.  I don't need cutting edge when there
>>>      
>>>
>>are
>>    
>>
>>>bills to pay.  A couple folks on the #debian IRC make a very strong argument
>>>for sticking with 2.4 and I may do that.
>>>
>>>I no longer want to compile kernels (thanks to a certain BOB M. on the list
>>>      
>>>
>>who
>>    
>>
>>>got me used to using plain old kernels from packages- that just worked).
>>>
>>>JJN
>>> 
>>>
>>>      
>>>
>>By the way, we got that gcc error when putting it on our Core 4 dump. 
>>Same thing about gcc being a different version than the kernel was 
>>compiled with. You have the option to do it anyways, which we did, and 
>>it seems to work just fine. You could try that if you want.
>>-- 
>>Jesse Jarzynka
>>Cyber Source
>>http://www.jessejoe.com/
>>http://www.thecybersource.com/
>>
>>    
>>
>
>
>
>	
>		
>______________________________________________________
>Click here to donate to the Hurricane Katrina relief effort.
>http://store.yahoo.com/redcross-donate3/
>
>  
>