Month: June 2009

Debian Lenny locales problem

Recently I bumped in a Debian Lenny locales problem,  on some amd64 cluster inside the cloud, during apt-get operations the system complains continuously about wrong or missing locales with messages like this:

perl: warning: Setting locale failed.perl: warning: Please check that your locale settings:LANGUAGE = (unset),LC_ALL = (unset),LANG = “en_US.UTF-8″are supported and installed on your system.

or like this:

manconv: can’t set the locale; make sure $LC_* and $LANG are correct

The issue was fixed using this method,  reinstalling and regenerating the locales on the system, to avoid dependencies I used the following packages as a “bridge”:

~# apt-get install belocs-locales-bin belocs-locales-data~# locale-gen~# dpkg-reconfigure locales

After issuing the command dpkg-reconfigure locales select the locales you need from the list and you should be done.

Vmware 2.0.x build problem

If you get this error during the Vmware module compilation:

Unable to make a vsock module that can be loaded in the running kernel:insmod: error inserting ‘/tmp/vmware-config1/vsock.o’: -1 Unknown symbol in module

What you need to do is the following:

untar vmci.tar (in /usr/lib/vmware/modules/source)build the module with ‘make’untar vsock.tar and copy the “Modules.symvers” file resulting from the previous compilation into the “vsock-only” directory. Rebuild the vsock.tar file and run “”.

Speaking in bash language:

cd /usr/lib/vmware/modules/source/tar xvfp vmci.tartar xvfp vsock.tar cd vmci-only/makecp -av Module.symvers ../vsock-only/cd ..tar -f vsock.tar -cv vsock-only/

Now it should compile just fine.Thanks to Javier, I got this solution from