https://wiki.archlinux.org/api.php?action=feedcontributions&user=Ajbw&feedformat=atomArchWiki - User contributions [en]2024-03-28T23:05:03ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Arch_Based_Distributions&diff=69020Arch Based Distributions2009-05-21T05:21:34Z<p>Ajbw: /* Shift Linux */</p>
<hr />
<div>{{stub}}<br />
<br />
==Shift Linux==<br />
Shift Linux was a work in progress that aims to be a desktop distro based on a solid Arch foundation.<br />
Since May 8th, 2009 it isn't developed anymore. Read more about here: http://shiftlinux.net/news/item/shift-placed-on-indefinite-hold<br />
<br />
"''Anyone interested in developing a Linux distro should consider helping out Firefly Linux. It's a great project that spawned from Shift.''"<br />
- Simon on shiftlinux.net<br />
<br />
===Links===<br />
*ShiftLinux Website: http://shiftlinux.net<br />
*ShiftLinux Forums: http://www.neowin.net/forum/index.php?showforum=182<br />
*ShiftLinux Development Team (open for anyone) on Launchpad: https://launchpad.net/~shiftlinux-devs<br />
*ShiftLinux Project on Launchpad: https://launchpad.net/shiftlinux<br />
<br />
==Chakra==<br />
"''Our goal with Chakra is to provide a operating system for desktops that is easy to use, but still has all the functionality, clarity, power and speediness of a KISS operating system. In the long term, we want to build an operating system based on Arch Linux that meets most requirements desktop users have today, like easy installation of software, graphical system administration, configuring power management on mobile devices or sharing an internet connection.''"<br />
<br />
The creators of the famous [[KDEmod]] project have put together a very polished distro, based on Arch and KDEMod (of course). Tools like [http://chakra-project.org/tools-shaman.html Shaman], [http://chakra-project.org/tools-arxin.html Arxin] show the gradual shift towards a more graphical UI oriented Arch derivative. Nonetheless, the project maintainst the KISS principle of Arch, even though the [http://chakra-project.org/tools-tribe.html Tribe installer] on the Live CD provides more of the 'you don't have to know what's inside' philosophy. The installed system however is a pure ArchLinux + KDE4 + Shaman with some artistic touches.<br />
<br />
===Links===<br />
*Homepage: http://www.chakra-project.org/<br />
*Forums: http://www.chakra-project.org/bbs/<br />
<br />
==Firefly Linux==<br />
<br />
Firefly Linux is an easy to use and friendly Linux distribution based on Arch Linux, with openness, size, and usability in mind. There are two versions of Firefly Linux: Firefly, and Float.<br />
<br />
Firefly Linux itself is bigger, with a full-er desktop based on Gnome, one of the most popular desktops on Linux. The download is 621MB, and it installs in 2.1GB.<br />
<br />
Float is a smaller Firefly, which uses XFCE, also a popular desktop for Linux. That’s just about the only difference you’ll notice between the two for now, but we plan to gear Float towards the fluffy Internet Clouds in the future, and create wonderful ways to work with the Cloud on tiny computers called “netbooks”. Floaty is a 385MB download and 1.3GB installation.<br />
<br />
===Links===<br />
*Homepage: http://fireflylinux.com/<br />
*Forums: http://fireflylinux.com/forum/index.php</div>Ajbwhttps://wiki.archlinux.org/index.php?title=Arch_Based_Distributions&diff=69019Arch Based Distributions2009-05-21T05:20:00Z<p>Ajbw: /* Chakra */ fix internal link</p>
<hr />
<div>{{stub}}<br />
<br />
==Shift Linux==<br />
Shift Linux was a work in progress that aims to be a desktop distro based on a solid Arch foundation.<br />
Since May 8th, 2009 it isn't developed anymore. Read more about here: http://shiftlinux.net/news/item/shift-placed-on-indefinite-hold<br />
<br />
"Anyone interested in developing a Linux distro should consider helping out Firefly Linux. It's a great project that spawned from Shift."<br />
- Simon on shiftlinux.net<br />
<br />
===Links===<br />
*ShiftLinux Website: http://shiftlinux.net<br />
*ShiftLinux Forums: http://www.neowin.net/forum/index.php?showforum=182<br />
*ShiftLinux Development Team (open for anyone) on Launchpad: https://launchpad.net/~shiftlinux-devs<br />
*ShiftLinux Project on Launchpad: https://launchpad.net/shiftlinux<br />
<br />
==Chakra==<br />
"''Our goal with Chakra is to provide a operating system for desktops that is easy to use, but still has all the functionality, clarity, power and speediness of a KISS operating system. In the long term, we want to build an operating system based on Arch Linux that meets most requirements desktop users have today, like easy installation of software, graphical system administration, configuring power management on mobile devices or sharing an internet connection.''"<br />
<br />
The creators of the famous [[KDEmod]] project have put together a very polished distro, based on Arch and KDEMod (of course). Tools like [http://chakra-project.org/tools-shaman.html Shaman], [http://chakra-project.org/tools-arxin.html Arxin] show the gradual shift towards a more graphical UI oriented Arch derivative. Nonetheless, the project maintainst the KISS principle of Arch, even though the [http://chakra-project.org/tools-tribe.html Tribe installer] on the Live CD provides more of the 'you don't have to know what's inside' philosophy. The installed system however is a pure ArchLinux + KDE4 + Shaman with some artistic touches.<br />
<br />
===Links===<br />
*Homepage: http://www.chakra-project.org/<br />
*Forums: http://www.chakra-project.org/bbs/<br />
<br />
==Firefly Linux==<br />
<br />
Firefly Linux is an easy to use and friendly Linux distribution based on Arch Linux, with openness, size, and usability in mind. There are two versions of Firefly Linux: Firefly, and Float.<br />
<br />
Firefly Linux itself is bigger, with a full-er desktop based on Gnome, one of the most popular desktops on Linux. The download is 621MB, and it installs in 2.1GB.<br />
<br />
Float is a smaller Firefly, which uses XFCE, also a popular desktop for Linux. That’s just about the only difference you’ll notice between the two for now, but we plan to gear Float towards the fluffy Internet Clouds in the future, and create wonderful ways to work with the Cloud on tiny computers called “netbooks”. Floaty is a 385MB download and 1.3GB installation.<br />
<br />
===Links===<br />
*Homepage: http://fireflylinux.com/<br />
*Forums: http://fireflylinux.com/forum/index.php</div>Ajbwhttps://wiki.archlinux.org/index.php?title=Arch_Based_Distributions&diff=69018Arch Based Distributions2009-05-21T05:19:10Z<p>Ajbw: /* Chakra */ fix broken links</p>
<hr />
<div>{{stub}}<br />
<br />
==Shift Linux==<br />
Shift Linux was a work in progress that aims to be a desktop distro based on a solid Arch foundation.<br />
Since May 8th, 2009 it isn't developed anymore. Read more about here: http://shiftlinux.net/news/item/shift-placed-on-indefinite-hold<br />
<br />
"Anyone interested in developing a Linux distro should consider helping out Firefly Linux. It's a great project that spawned from Shift."<br />
- Simon on shiftlinux.net<br />
<br />
===Links===<br />
*ShiftLinux Website: http://shiftlinux.net<br />
*ShiftLinux Forums: http://www.neowin.net/forum/index.php?showforum=182<br />
*ShiftLinux Development Team (open for anyone) on Launchpad: https://launchpad.net/~shiftlinux-devs<br />
*ShiftLinux Project on Launchpad: https://launchpad.net/shiftlinux<br />
<br />
==Chakra==<br />
"''Our goal with Chakra is to provide a operating system for desktops that is easy to use, but still has all the functionality, clarity, power and speediness of a KISS operating system. In the long term, we want to build an operating system based on Arch Linux that meets most requirements desktop users have today, like easy installation of software, graphical system administration, configuring power management on mobile devices or sharing an internet connection.''"<br />
<br />
The creators of the famous [KDEMod] project have put together a very polished distro, based on Arch and KDEMod (of course). Tools like [http://chakra-project.org/tools-shaman.html Shaman], [http://chakra-project.org/tools-arxin.html Arxin] show the gradual shift towards a more graphical UI oriented Arch derivative. Nonetheless, the project maintainst the KISS principle of Arch, even though the [http://chakra-project.org/tools-tribe.html Tribe installer] on the Live CD provides more of the 'you don't have to know what's inside' philosophy. The installed system however is a pure ArchLinux + KDE4 + Shaman with some artistic touches.<br />
<br />
===Links===<br />
*Homepage: http://www.chakra-project.org/<br />
*Forums: http://www.chakra-project.org/bbs/<br />
<br />
==Firefly Linux==<br />
<br />
Firefly Linux is an easy to use and friendly Linux distribution based on Arch Linux, with openness, size, and usability in mind. There are two versions of Firefly Linux: Firefly, and Float.<br />
<br />
Firefly Linux itself is bigger, with a full-er desktop based on Gnome, one of the most popular desktops on Linux. The download is 621MB, and it installs in 2.1GB.<br />
<br />
Float is a smaller Firefly, which uses XFCE, also a popular desktop for Linux. That’s just about the only difference you’ll notice between the two for now, but we plan to gear Float towards the fluffy Internet Clouds in the future, and create wonderful ways to work with the Cloud on tiny computers called “netbooks”. Floaty is a 385MB download and 1.3GB installation.<br />
<br />
===Links===<br />
*Homepage: http://fireflylinux.com/<br />
*Forums: http://fireflylinux.com/forum/index.php</div>Ajbwhttps://wiki.archlinux.org/index.php?title=Arch_Based_Distributions&diff=69017Arch Based Distributions2009-05-21T05:13:24Z<p>Ajbw: /* Links */ fix broken Chakra links</p>
<hr />
<div>{{stub}}<br />
<br />
==Shift Linux==<br />
Shift Linux was a work in progress that aims to be a desktop distro based on a solid Arch foundation.<br />
Since May 8th, 2009 it isn't developed anymore. Read more about here: http://shiftlinux.net/news/item/shift-placed-on-indefinite-hold<br />
<br />
"Anyone interested in developing a Linux distro should consider helping out Firefly Linux. It's a great project that spawned from Shift."<br />
- Simon on shiftlinux.net<br />
<br />
===Links===<br />
*ShiftLinux Website: http://shiftlinux.net<br />
*ShiftLinux Forums: http://www.neowin.net/forum/index.php?showforum=182<br />
*ShiftLinux Development Team (open for anyone) on Launchpad: https://launchpad.net/~shiftlinux-devs<br />
*ShiftLinux Project on Launchpad: https://launchpad.net/shiftlinux<br />
<br />
==Chakra==<br />
"''Our goal with Chakra is to provide a operating system for desktops that is easy to use, but still has all the functionality, clarity, power and speediness of a KISS operating system. In the long term, we want to build an operating system based on Arch Linux that meets most requirements desktop users have today, like easy installation of software, graphical system administration, configuring power management on mobile devices or sharing an internet connection.''"<br />
<br />
The creators of the famous [http://kdemod.ath.cx/download-kdemod.html KDEMod] project have put together a very polished distro, based on Arch and KDEMod (of course). Tools like [http://kdemod.ath.cx/tools-shaman.html Shaman], [http://kdemod.ath.cx/tools-arxin.html Arxin] show the gradual shift towards a more graphical UI oriented Arch derivative. Nonetheless, the project maintainst the KISS principle of Arch, even though the [http://kdemod.ath.cx/about-screenshots.html installer] on the Live CD provides more of the 'you don't have to know what's inside' philosophy. The installed system however is a pure ArchLinux + KDE4 + Shaman with some artistic touches.<br />
<br />
===Links===<br />
*Homepage: http://www.chakra-project.org/<br />
*Forums: http://www.chakra-project.org/bbs/<br />
<br />
==Firefly Linux==<br />
<br />
Firefly Linux is an easy to use and friendly Linux distribution based on Arch Linux, with openness, size, and usability in mind. There are two versions of Firefly Linux: Firefly, and Float.<br />
<br />
Firefly Linux itself is bigger, with a full-er desktop based on Gnome, one of the most popular desktops on Linux. The download is 621MB, and it installs in 2.1GB.<br />
<br />
Float is a smaller Firefly, which uses XFCE, also a popular desktop for Linux. That’s just about the only difference you’ll notice between the two for now, but we plan to gear Float towards the fluffy Internet Clouds in the future, and create wonderful ways to work with the Cloud on tiny computers called “netbooks”. Floaty is a 385MB download and 1.3GB installation.<br />
<br />
===Links===<br />
*Homepage: http://fireflylinux.com/<br />
*Forums: http://fireflylinux.com/forum/index.php</div>Ajbwhttps://wiki.archlinux.org/index.php?title=Kernel_Panics&diff=69016Kernel Panics2009-05-21T05:05:15Z<p>Ajbw: /* Troubleshooting */</p>
<hr />
<div>[[Category: System recovery (English)]]<br />
[[Category:HOWTOs (English)]]<br />
[[Category:Kernel (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|Česky|:Kernel Panics (Česky)}}<br />
{{i18n_entry|English|:Kernel Panics}}<br />
{{i18n_entry|Español|:Kernel Panics (Español)}}<br />
{{i18n_entry|Italiano|:Kernel Panics (Italiano)}}<br />
{{i18n_entry|简体中文|:Kernel Panics (简体中文)}}<br />
{{i18n_entry|Ελληνικά|:Kernel Panics (Ελληνικά)}}<br />
{{i18n_entry|Türkçe|:Çekirdek Hataları}}<br />
{{i18n_links_end}}<br />
<br />
This page describes how to repair a computer whose kernel panics at boot.<br />
<br />
==Troubleshooting==<br />
To make troubleshooting easier, ensure that the kernel is not in quiet mode. Remove 'quiet' from the kernel line in GRUB if it is. Upon boot, check the output immediately before the panic and decide whether there is any useful information. There are probably too many causes for a kernel panic to keep well-documented in this wiki. Make sure that your system's configuration in /boot is correct and that none of the computer's hardware is faulty - it is good idea to run memtest from the Arch install/rescue CD or another utility (red entries are bad). If you believe the configuration in /boot may be erroneous, try option 1. If you believe the kernel panic is the fault of the kernel itself, follow option 2 in order to install an earlier kernel.<br />
<br />
==Option 1: Check bootloader configuration==<br />
Another possibility is an error in the bootloader's configuration (e.g. <tt>/boot/grub/menu.lst</tt>). For example, repartitioning hard drives can change partitions' order. GRUB users may recall whether repartitioning has occurred recently and make sure the ''root'' and ''kernel'' lines match up with the new partitioning scheme. And examine the file for typos and extraneous characters. An extra space, or character in the wrong place will cause a kernel panic.<br />
<br />
==Option 2: Reinstall kernel==<br />
Reinstalling the kernel is probably the best bet when no other major system modifications have taken place recently.<br />
<br />
===Start from the installation CD===<br />
The first step is booting the installation CD. When started, type arch, like you would when installing arch.<br />
# arch<br />
<br />
===Chroot to your normal root===<br />
When booted, you are in a minimal but functional live GNU/Linux environment with some basic tools.<br />
Now, you have to mount your normal root disk to /mnt.<br />
# mount /dev/sdXY /mnt<br />
If you use a boot partition, don't forget to mount it<br />
# mount /dev/sdXZ /mnt/boot<br />
<br />
Newer kernels use an initial ramdisk to set up the kernel environment. When you reinstall a kernel, that initial ramdisk will be regenerated with mkinitcpio. One of mkinitcpio's features is that it does autodetection to find out what kernel modules are required for starting up your computer. For this autodetection to work, /dev, /sys and /proc need to mounted in your chroot:<br />
<br />
# mount -t proc none /mnt/proc<br />
# mount -t sysfs none /mnt/sys<br />
# mount --bind /dev /mnt/dev<br />
<br />
Now, we will chroot to this disk:<br />
# chroot /mnt<br />
<br />
===Roll back to previous kernel version===<br />
If you keep your downloaded pacman packages, you now can easily roll back. If you didn't keep them, you have to find a way to get a previous kernel version on your system now.<br />
<br />
Let's suppose you keep the previous versions. We will now install the last working one.<br />
# pacman -U /var/cache/pacman/pkg/kernel26-2.6.23.''xx-x''.pkg.tar.gz<br />
Of course, make sure that you adapt this line to your own kernel version.<br />
<br />
Otherwise, check the install CD for a package. For example, the version 2008.06 i686 CD contains addons/core-pkgs/kernel26-2.6.25.6-1-i686.pkg.tar.gz.<br />
<br />
==Reboot==<br />
Now is the time to reboot and see if the system modifications have stopped the panic.<br />
If reverting to an older kernel works, don't forget to check the arch-newspage to check what went wrong with the kernel build.</div>Ajbwhttps://wiki.archlinux.org/index.php?title=Skype&diff=68053Skype2009-05-01T23:53:15Z<p>Ajbw: Internal links, add sound category</p>
<hr />
<div>[[Category:Audio/Video (English)]]<br />
[[Category:Sound (English)]]<br />
[[Category:Internet and Email (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Skype}}<br />
{{i18n_entry|Česky|Skype (Česky)}}<br />
{{i18n_links_end}}<br />
<br />
===Installing Skype===<br />
To install skype, you need to have the community repository uncommented in /etc/pacman.conf<br />
<br />
#[community]<br />
# Add your preferred servers here, they will be used first<br />
#Include = /etc/pacman.d/mirrorlist<br />
<br />
becomes:<br />
[community]<br />
# Add your preferred servers here, they will be used first<br />
Include = /etc/pacman.d/mirrorlist<br />
<br />
Now use pacman to install Skype:<br />
# pacman -Sy skype<br />
<br />
====64-bit Installation====<br />
Because skype is only offered as a 32-bit binary, there is no official arch package for x86_64. However, you can install bin32-skype from AUR instead.<br />
<br />
===Skype Sound===<br />
Recent versions of Skype (2.0+) have native [[ALSA]] Support, ealier versions support only the deprecated [[OSS]].<br />
<br />
====Skype ALSA Sound (2.0+)====<br />
Sound should work out of the box, if not you can select a sound device to use in skype options.<br />
if you have problems with skype blocking your sound device, you only need to add the following to your ~/.asoundrc<br />
pcm.dmixout {<br />
# Just pass this on to the system dmix<br />
type plug<br />
slave {<br />
pcm "dmix"<br />
}<br />
}<br />
then you can start skype as normal, go to the audio options and select dmixout as your speaker- and ringingdevice.<br />
<br />
====Skype-OSS Sound (Pre-2.0)====<br />
if you have a recent version of skype, this will not work and is not needed, look at the "important notes" on start of this page.<br />
Option B is preferred over other options.<br />
With option B you can use skype AND let other programs play sound too.<br />
With option C you can do that too, but option B is way easier to set up.<br />
<br />
=====A. With OSS or Kernel OSS emulation for ALSA=====<br />
Start "skype" and make sure no other program is using your soundcard.<br />
If you want to use skype AND let another program play sound too, look at option B instead.<br />
<br />
=====B. Making ALSA + dMix work for Skype=====<br />
First of all, we need to install the alsa-oss package from pacman:<br />
# pacman -Sy alsa-oss<br />
<br />
Add the following to "~/.asoundrc" (the file ".asoundrc" in your home directory)<br />
If the file doesn't exist yet, just create it!<br />
<br />
Many thanks to Lorenzo Colitti for figuring this out!<br />
<br />
# .asoundrc to use skype at the same time as other audio apps like xmms<br />
#<br />
# Successfully tested on an IBM x40 with i810_audio using Linux 2.6.15 and<br />
# Debian unstable with skype 1.2.0.18-API. No sound daemons (asound, esd, etc.)<br />
# running. However, YMMV.<br />
#<br />
# For background, see:<br />
#<br />
# https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1228<br />
# https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1224<br />
#<br />
# (C) 2006-06-03 Lorenzo Colitti - http://www.colitti.com/lorenzo/<br />
# Licensed under the GPLv2 or later<br />
<br />
pcm.skype {<br />
type asym<br />
playback.pcm "skypeout"<br />
capture.pcm "skypein"<br />
}<br />
<br />
pcm.skypein {<br />
# Convert from 8-bit unsigned mono (default format set by aoss when<br />
# /dev/dsp is opened) to 16-bit signed stereo (expected by dsnoop)<br />
#<br />
# We can't just use a "plug" plugin because although the open will<br />
# succeed, the buffer sizes will be wrong and we'll hear no sound at<br />
# all.<br />
type route<br />
slave {<br />
pcm "skypedsnoop"<br />
format S16_LE<br />
}<br />
ttable {<br />
0 {0 0.5}<br />
1 {0 0.5}<br />
}<br />
}<br />
<br />
pcm.skypeout {<br />
# Just pass this on to the system dmix<br />
type plug<br />
slave {<br />
pcm "dmix"<br />
}<br />
}<br />
<br />
pcm.skypedsnoop {<br />
type dsnoop<br />
ipc_key 1133<br />
slave {<br />
# "Magic" buffer values to get skype audio to work<br />
# If these are not set, opening /dev/dsp succeeds but no sound<br />
# will be heard. According to the alsa developers this is due<br />
# to skype abusing the OSS API.<br />
pcm "hw:0,0"<br />
period_size 256<br />
periods 16<br />
buffer_size 16384<br />
}<br />
bindings {<br />
0 0<br />
}<br />
}<br />
<br />
If you get the error message :<br />
<br />
The dmix plugin supports only playback stream<br />
<br />
then add the following to .asoundrc :<br />
<br />
pcm.asymed {<br />
type asym<br />
playback.pcm "dmix"<br />
capture.pcm "dsnoop"<br />
}<br />
<br />
pcm.!default {<br />
type plug<br />
slave.pcm "asymed"<br />
}<br />
<br />
<br />
Now run skype in this way each time you want to use skype:<br />
ALSA_OSS_PCM_DEVICE="skype" aoss skype<br />
<br />
Optionally you can make a script to start skype:<br />
<br />
As root, create the file: '''/usr/bin/askype'''<br />
<br />
# Little script to run Skype correctly using the modified .asoundrc<br />
# See: http://wiki.archlinux.org/index.php/Skype for more information!<br />
#<br />
# Questions/Remarks: profox@debianbox.be<br />
<br />
ALSA_OSS_PCM_DEVICE="skype" aoss skype<br />
<br />
Now make sure every user is able to execute the file:<br />
# chmod a+x /usr/bin/askype<br />
<br />
You can also fix the menu entry so you can start Skype from the your window manager's menu:<br />
<br />
Edit the file: '''/usr/share/applications/skype.desktop'''<br />
<br />
[Desktop Entry]<br />
Name=Skype<br />
Comment=P2P software for high-quality voice communication<br />
Exec=askype<br />
Icon=skype.png<br />
Terminal=0<br />
Type=Application<br />
Encoding=UTF-8<br />
Categories=Network;Application;<br />
<br />
Sometimes it takes a while for Skype to start up,<br />
<br />
but once it's loaded it should work ok!<br />
<br />
=====C. Using OSS emulation with oss2jack=====<br />
oss2jack is another way to have OSS emulation without using ALSA directly. Instead, oss2jack creates a OSS device that forwards everything to JACK (JACK Audio Connection Kit), which in turn mixes, then outputs to the standard ALSA device. For more information on setting this up, please refer to [[Allow_multiple_programs_to_play_sound_at_once#ALSA_with_oss2jack]].<br />
<br />
<br />
===Problems===<br />
<br />
* I can receive multiple audio streams, but I can only send one:<br />
** for example: skype can send and receive audio, and I still hear other sounds playing from other applications, but I can't record my microphone with other applications. Skype or aoss blocks the audio input for itself<br />
<br />
* No video after the new kernel change with gspca.<br />
Instal libv4l, the userspace video for linux libary, and run skype with LD_PRELOAD=/usr/lib/libv4l/v4l1compat.so skype to start skype with v4l 1 compitability<br />
<br />
===Questions or Remarks===<br />
You are free to edit this wiki entry if you have anything to add or change, and for more questions or remarks you can mail me ([[User:ProfoX|profoX]]) at profox@debianbox.be</div>Ajbwhttps://wiki.archlinux.org/index.php?title=Adjusting_typematic_delay_and_rate&diff=67776Adjusting typematic delay and rate2009-04-28T04:34:49Z<p>Ajbw: typo</p>
<hr />
<div>==Introduction==<br />
<p>This article describes tuning of the automatic repeating process of characters when a key on your keyboard is pressed.<br><br />
The 'typematic delay' indicates the amount of time a key needs to be pressed in order for the repeating process to begin. (typically given in ms)<br><br />
After the repeating process has been triggered, the character will be repeated with at a rate which is governed by the 'typematic rate'. (typically given in Hz)<br />
<br />
==Tuning the typematic behavior in the tty==<br />
is done using the 'kbdrate' command. The syntax is:<br />
kbdrate [ -d delay ] [ -r rate ]<br />
if you wanted to set an typematic delay of 200ms and a repeating rate of 30Hz then you would issue this command as root:<br />
kbdrate -d 200 -r 30<br />
returning the typematic settings to their default value is done by issuing the command without arguments:<br />
kbdrate<br />
will return the typematic values to their respective defaults. (currently a delay of 250ms and a rate of 11Hz)<br />
==Tuning the typematic behavior in X==<br />
is done using the 'xset' command. The syntax adjusting the typematic rate and delay is:<br />
xset r rate delay [rate]<br />
if you wanted to set an typematic delay of 200ms and a repeating rate of 30Hz then you would include this command in your .xinitrc/.xsession:<br />
xset r rate 200 30<br />
returning the typematic settings to their default value is done by issuing the command without specifying the delay and rate:<br />
xset r rate<br />
will return the typematic values to their respective defaults. (currently a delay of 660ms and a rate of 25Hz)</div>Ajbwhttps://wiki.archlinux.org/index.php?title=Adjusting_typematic_delay_and_rate&diff=67775Adjusting typematic delay and rate2009-04-28T04:34:32Z<p>Ajbw: typo</p>
<hr />
<div>==Introduction==<br />
<p>This article describes tuning of the automatic repeating process of characters when a key on your keyboard is pressed.<br><br />
The 'typematic delay' indicates the amount of time a key needs to be pressed in order for the repeating process to begin. (typically given in ms)<br><br />
After the repeating process has been triggered, the character will be repeated with at a rate which is governed by the 'typomatic rate'. (typically given in Hz)<br />
<br />
==Tuning the typematic behavior in the tty==<br />
is done using the 'kbdrate' command. The syntax is:<br />
kbdrate [ -d delay ] [ -r rate ]<br />
if you wanted to set an typematic delay of 200ms and a repeating rate of 30Hz then you would issue this command as root:<br />
kbdrate -d 200 -r 30<br />
returning the typematic settings to their default value is done by issuing the command without arguments:<br />
kbdrate<br />
will return the typematic values to their respective defaults. (currently a delay of 250ms and a rate of 11Hz)<br />
==Tuning the typematic behavior in X==<br />
is done using the 'xset' command. The syntax adjusting the typematic rate and delay is:<br />
xset r rate delay [rate]<br />
if you wanted to set an typematic delay of 200ms and a repeating rate of 30Hz then you would include this command in your .xinitrc/.xsession:<br />
xset r rate 200 30<br />
returning the typematic settings to their default value is done by issuing the command without specifying the delay and rate:<br />
xset r rate<br />
will return the typematic values to their respective defaults. (currently a delay of 660ms and a rate of 25Hz)</div>Ajbwhttps://wiki.archlinux.org/index.php?title=Installing_VMware_Player&diff=67288Installing VMware Player2009-04-21T05:24:09Z<p>Ajbw: create fake directories so that installer doesn't complain about the system service runlevels directory not being an init directory</p>
<hr />
<div>[[Category:Emulators (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Installing_vmware_player}}<br />
{{i18n_entry|Русский|Installing_vmware_player (Русский)}}<br />
{{i18n_links_end}}<br />
<br />
== Introduction ==<br />
The quickest and easiest way I've found to install vmware player under Arch.<br />
<br />
This WIKI was done for vmwareplayer 1.03 with Kernel 2.6.20. The package names will change for later versions, please substitute the new names at that point.<br />
<br />
For this exercise download all files needed and place them in a directory called ~/pkgbuild. You don't need to download the vmware-player and kernel modules yourself, as the makepkg script will do that for itself.<br />
<br />
'''Tip:''' If you have already downloaded one/both of these 'large files', just place them into their respective directories, which will be referred to below as <code>~/pkgbuild/vmware-player-modules/</code> and <code>~/pkgbuild/vmware-player/</code>.<br />
<br />
== Setting up vmware-player-modules ==<br />
<br />
You will need to visit the vmware-player-modules page on the AUR site and download [http://aur.archlinux.org/packages/vmware-player-modules/vmware-player-modules.tar.gz vmware-player-modules.tar.gz].<br />
<br />
Extract them into ~/pkgbuild/vmware-player-modules/ and build the package:<br />
$ cd ~/pkgbuild/vmware-player-modules/<br />
$ makepkg<br />
<br />
This will download the files needed and make a file called something similar to:<br />
<br />
~/pkgbuild/vmware-player-modules/vmware-player-modules-1.0.3_34682-2.pkg.tar.gz<br />
<br />
This file will now be installed with pacman:<br />
# pacman -U ~/pkgbuild/vmware-player-modules/vmware-player-modules-1.0.3_34682-2.pkg.tar.gz<br />
<br />
If all went well the vmware kernel modules will now be installed.<br />
<br />
== Setting up vmware-player ==<br />
You will need to visit the vmware-player page on the AUR site and download [http://aur.archlinux.org/packages/vmware-player/vmware-player.tar.gz vmware-player.tar.gz].<br />
<br />
Extract them into ~/pkgbuild/vmware-player and build the package:<br />
$ cd ~/pkgbuild/vmware-player/<br />
$ makepkg<br />
<br />
This will download the files needed and make a file called something similar to:<br />
<br />
~/pkgbuild/vmware-player/vmware-player-1.0.3_34682-1.pkg.tar.gz<br />
<br />
This file will now be installed with pacman:<br />
# pacman -U ~/pkgbuild/vmware-player/vmware-player-1.0.3_34682-1.pkg.tar.gz<br />
<br />
If all went well the vmware player will now be installed.<br />
<br />
== Configuration ==<br />
You need to configure VMware Player by invoking /usr/bin/vmware-config.pl<br />
<br />
Also, you should add vmware to the DAEMONS array in /etc/rc.conf<br />
<br />
== Troubleshooting ==<br />
=== x86_64 ===<br />
In case you get this error when loading an .vmx file:<br />
/usr/lib/vmware/bin/vmware-vmx: error while loading shared libraries: libXtst.so.6: wrong ELF class: ELFCLASS64<br />
<br />
Make sure that lib32-libxtst [found in community repo] is installed.<br />
<br />
=== Future kernel updates ===<br />
<br />
If there is a kernel update in the future and vmwareplayer will not load, you will have to recompile the modules package. You don't need to download the vmware-player-modules.tar.gz again, only if it has changes. You can search at http://aur.archlinux.org/packages.php for vmware-player-modules. Then:<br />
$ cd ~/pkgbuild/vmware-player-modules/<br />
$ makepkg<br />
<br />
And install the package with pacman:<br />
# pacman -U ~/pkgbuild/vmware-player-modules/vmware-player-modules-1.0.3_34682-2.pkg.tar.gz<br />
<br />
Thanking pizzapunk who kindly helped me with my vmware-player installation.<br />
<br />
--[[User:Habtool|habtool]] 11:13, 20 February 2007 (EST)<br />
<br />
=== VMWare Player >= 2.5 ===<br />
<br />
Download the VMware-Player-xxx-xxx.<architecture>.bundle file from the VMWare Website and save it in any directory you like. Then, you need to create the same directories as you need installing VMWare Server. As root:<br />
<br />
# mkdir -p /etc/rc.d/vmware.d/rc{0,1,2,3,4,5,6}.d<br />
<br />
Then execute (as root) the installation binary:<br />
<br />
# ./VMware-Player-xxx-xxx.<architecture>.bundle<br />
<br />
When it promts for System Service Runlevels answer:<br />
<br />
/etc/rc.d/vmware.d/<br />
<br />
If you get told that "/etc/rc.d/vmware.d is not an init directory", create some dummy directories:<br />
<br />
cd /etc/rc.d/vmware.d<br />
mkdir rc0.d rc1.d rc2.d rc3.d rc4.d rc5.d rc6.d init.d<br />
<br />
For System Service Scripts use:<br />
<br />
/etc/rc.d<br />
<br />
You do not need to manually reconfigure the kernel modules each time you perform a kernel update. VMPlayer will do this for you when you start it up.<br />
<br />
Infact, vmware-config.pl is gone. If you need to manually reconfigure your kernel modules do (as root):<br />
<br />
/usr/bin/vmware-modconfig --console --install-all</div>Ajbwhttps://wiki.archlinux.org/index.php?title=VMware&diff=67287VMware2009-04-21T05:11:33Z<p>Ajbw: typo</p>
<hr />
<div>[[Category:Emulators (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Installing VMware}}<br />
{{i18n_entry|简体中文|安装VMWare}}<br />
{{i18n_entry|Italiano|Installing_VMware (Italiano)}}<br />
{{i18n_entry|Русский|Установка_VMware (Русский)}}<br />
{{i18n_links_end}}<br />
[http://www.vmware.com/ VMware] installs on [[Arch Linux]] pretty well, but its not totally straight forward.<br />
<br />
==VMware Workstation Installation==<br />
The following is from the VMWare Workstation AUR user comments, by user whompus. It describes how to install VMWare Workstation 6.5.x on either architecture.<br />
<br />
As a temp measure use this method to install 6.5. Note that it will '''not''' install with pacman, so the files installed will '''not''' be traceable/removable with pacman.<br />
<br />
To install Workstation on a Linux host using a bundle<br />
<br />
1. Download VMware-Workstation-6.5.xxxxxx.bundle. Replace xxxxx for whichever minor version & architecture.<br />
<br />
2. In a terminal cd to the directory where you downloaded the file.<br />
<br />
3. Become root to perform the initial installation steps:<br />
# mkdir -p /etc/rc.d/vmware.d/rc{0,1,2,3,4,5,6}.d<br />
# sh VMware-Workstation-6.5.xxxxxx.bundle --console --custom<br />
<br />
4. Read & accept the EULA to continue.<br />
<br />
5. Accept the default settings until it prompts for System service runlevels then set to:<br />
/etc/rc.d/vmware.d/<br />
If you get the error "/etc/rc.d/vmware.d is not an init directory", create the following in /etc/rc.d/vmware.d:<br />
cd /etc/rc.d/vmware.d<br />
mkdir rc0.d rc1.d rc2.d rc3.d rc4.d rc5.d rc6.d init.d<br />
<br />
6. For System service scripts set to:<br />
/etc/rc.d<br />
<br />
7. (Optional) Enter the directory path to the Integrated Virtual Debugger for Eclipse if Eclipse is installed.<br />
<br />
8. Mash enter to install. Note that if nothing happens at this point and you are returned to the prompt, try re-running the installation without the '--console' option.<br />
<br />
9. Open Workstation (<code>vmware</code> in the console) to configure & use!<br />
<br />
After launching vmware, if you experience an errors stating, "modinfo: could not find module vmmon" you may need to rebuild vmware's binary modules. Use the following commands:<br />
<br />
1. Make a backup (required before recompiling models):<br />
# sudo mv /usr/lib/vmware/modules/binary /usr/lib/vmware/modules/binary.old<br />
<br />
2. Recompile modules and load them into memory:<br />
# sudo vmware-modconfig --console --install-all<br />
<br />
==VMware Server Installation==<br />
'''NOTE''' I would highly recommend using VMWare Server 2 on 2.6.27 as it actually builds. It also does not appear to require a patch.<br />
<br />
You can use the [http://aur.archlinux.org/packages.php?do_Details=1&ID=6182&O=0&L=0&C=0&K=vmware&SB=n&SO=a&PP=25&do_MyPackages=0&do_Orphans=0&SeB=nd AUR] or manually install [http://www.vmware.com/download/server/ VMware Server] downloaded from [http://www.vmware.com/ VMware.com]. This guide shows you how to install the manually downloaded VMware server tarball, assuming you are running Voodoo or newer (Duke) with kernel version 2.6.20+ '''32-bit'''.<br />
<br />
===Requirements:===<br />
* Root access. Either 'sudo' or 'su'. For this guide, I will be using 'sudo'.<br />
* [http://archlinux.org/packages/search/?repo=all&category=all&q=xinetd&lastupdate=&limit=50 Xinetd] is installed, up and running.<br />
* The X-libraries libxtst, libxt and libxrender installed<br />
* [http://www.vmware.com/download/server/ VMware server tarball]; latest is 1.0.4 build 56528 as of this writing.<br />
* <strike>VMware server [http://www.vmware.com/community/thread.jspa?messageID=76957&tstart=0 any-to-any]" patch: [http://platan.vc.cvut.cz/ftp/pub/vmware mirror 1] and [ftp://ftp.cvut.cz/vmware mirror 2]. Note: For server 1.0.4 build 56528 you need patch vmware-any-any-update113.tar.bz2, which is on mirror 1 only.</strike><br />
* UPDATE: With 2.6.24 you need this [http://rtr.ca/vmware-2.6.24/ patch] (vmware-any-any-update115a.tgz)<br />
* UPDATE: With 2.6.25 you need also this [http://blog.creonfx.com/temp/vmware-any-any-update-117-very-ALPHA.tgz patch] (vmware-any-any-update-117-very-ALPHA)<br />
* Compatible with VMware Workstation >= 6.0.2 Build 59824 on Linux 2.6.25<br />
* UPDATE: With 2.6.26 you need this [http://vmkernelnewbies.googlegroups.com/web/vmware-any-any-update117d.tar.gz patch] (vmware-any-any-update117d.tar.gz), the VMware version 6.0.5 doesn't need the patch, the version for vmmon e.g. in 117d is even too old (168, need 169!)<br />
* UPDATE: With 2.6.26 and VMWare 6.5 _no_ patch is needed anymore (6.5.0 build-118166). The graphical installer works just fine and all the modules work out of the box. Follow the instructions below for the directory containing the init-scripts.<br />
<br />
===Instructions:===<br />
* Run '''''sudo mkdir -p /etc/rc.d/vmware.d/rc{0,1,2,3,4,5,6}.d''''' to create VMware runlevel directories.<br />
* Run '''''sudo ln -s /bin/lsmod /sbin/''''' to create symlink for lsmod.<br />
* Extract VMware server tarball somewhere... i.e. /tmp/.<br />
* Run '''''cd /tmp/vmware-server-distrib;sudo ./vmware-install.pl'''''. I used '''''/home/vmware/bin''''' for installation.<br />
* When it asks where the directories for ''rc0.d'' thru ''rc6.d'' are, use '''''/etc/rc.d/vmware.d'''''.<br />
* When it asks where the init directory is, use '''''/etc/rc.d'''''.<br />
* '''*QUIT*''' when it asks you if you want to run VMware configuration for the first time.<br />
* Extract VMware server any-to-any patch somewhere... i.e. /tmp/.<br />
* Run '''''cd /tmp/vmware-any-any-update*REV*;sudo ./runme.pl'''''. This will patch VMware server modules to allow Linux kernel 2.6.20 compilation.<br />
* For Linux 2.6.25 additionally to the previous patch115a or 116 you need to manually patch with 117_Alpha.<br />
* For 2.6.25 extract 117 to the location '''''tar xzf vmware-any-any-update-117-very-ALPHA.tgz -C /usr/lib/vmware/modules/source/<br />
* For 2.6.25 patch '''''cd /usr/lib/vmware/modules/source/''''' and run'''''./vmware-2.6.25.sh''''' and continue with next step.<br />
* Run '''''cd /home/vmware/bin;sudo ./vmware-config.pl''''' to compile VMware modules.<br />
<br />
== Running ==<br />
<br />
It's a possibility the first time you try to run Vmware server it'll throw an error stating something about "Unable to power virtual machine". Stop the VMware server and restart xinetd wtih '''''/etc/rc.d/vmware stop;wait;/etc/rc.d/xinetd restart'''''.<br />
<br />
Rerun '''''sudo /home/vmware/bin/vmware-config.pl''''' again. If this still fails, restart your computer and do the above again. It should be fixed.<br />
<br />
There is now a <code>vmware</code> init script in <code>/etc/rc.d</code>. You can add this to your daemons list if you want. I personally dont do this, but if you intend to use the vmware's network when not actually using vmware, then you will need to do this. You will need to start it before you can run vmware though.<br />
<br />
There is a problem with vmware unable to run correctly after a reboot. To fix this edit <code>/etc/rc.d/vmware</code>, find the text below<br />
case "$1" in<br />
start)<br />
and put<br />
rm /etc/vmware/not_configured<br />
immediately after that line.<br />
<br />
To start vmware, you just do <code>vmware</code> from a console window, or create a shortcut or menu item however you like.<br />
<br />
'''Some notes:'''<br />
<br />
Leave the <code>/etc/rc.d/vmware.d</code> directory there, because it is needed whenever you perform <code>vmware-config.pl</code>.<br />
<br />
Remember, if the kernel is changed or updated, you will need to run <code>vmware-config.pl</code> again.<br />
<br />
== Kernel 2.6 and udev ==<br />
<br />
Follow the steps above and then:<br />
<br />
'''1. Modify udev config'''<br />
<br />
Edit <code>/etc/udev/rules.d/00-myrules.rules</code> and add 2 lines:<br />
# tty devices<br />
KERNEL="tty<nowiki>[[0-9]]</nowiki>*", NAME="vc/%n", SYMLINK="%k"<br />
<br />
# floppy devices<br />
KERNEL="fd<nowiki>[[0-9]]</nowiki>*", NAME="floppy/%n" , SYMLINK="fd%n"<br />
<br />
'''2. Start/stop script'''<br />
<br />
It takes care of devices and starts vmware, also stops vmware and removes dev entries. Call it, for example, <code>mkvmdev</code>, chmod it <code>755</code> and put in <code>/etc/rc.d</code>:<br />
<br />
<pre><br />
#!/bin/sh<br />
<br />
. /etc/rc.conf<br />
. /etc/rc.d/functions<br />
<br />
case "$1" in<br />
start)<br />
stat_busy "Creating /dev entries and starting VMware"<br />
for i in `seq 0 9`; do<br />
mknod /dev/vmnet$i c 119 $i<br />
chmod 0600 /dev/vmnet$i<br />
done<br />
for i in `seq 0 3`; do<br />
mknod /dev/parport$i c 99 $i<br />
chmod 0600 /dev/parport$i<br />
done<br />
mknod /dev/vmmon c 10 165<br />
chmod 0660 /dev/vmmon<br />
/etc/rc.d/vmware start<br />
;;<br />
<br />
stop)<br />
stat_busy "Stopping VMware and removing /dev entries"<br />
/etc/rc.d/vmware stop<br />
rm /dev/vmmon<br />
for i in `seq 0 3`; do<br />
rm /dev/parport$i<br />
done<br />
for i in `seq 0 9`; do<br />
rm /dev/vmnet$i<br />
done<br />
;;<br />
<br />
restart)<br />
$0 stop<br />
$0 start<br />
;;<br />
<br />
*)<br />
echo "usage: $0 {start|stop|restart}"<br />
esac<br />
exit 0<br />
</pre><br />
<br />
'''3. Modify <code>/etc/rc.conf</code>.''' (*Note - this step is optional! See also the notes under the "Running" section above)<br />
<br />
Add <code>mkvmdev</code> to daemons in your <code>rc.conf</code>, and remember to remove <code>vmware</code> from <code>rc.conf</code>. Or if you prefer, you can delete the lines that launch vmware from <code>mkvmdev</code> and leave your original <code>vmware</code> in <code>rc.conf</code> - your choice.<br />
<br />
-----<br />
<br />
'''Comments:'''<br />
<br />
hi guys, a couple of quick questions:<br><br />
- why is /dev/vmmon chmod 0660, as opposed to the rest (0600)?<br><br />
- i suppose /dev/vmmon should be "rm"-ed as well in the "stop" section for the script above? (that line is missing) - FIXED<br />
<br />
== VMware and kernel 2.6.29 compile modules problem ==<br />
In Kernel 2.6.29 some internal data-structs were changed. Download this [http://communities.vmware.com/servlet/JiveServlet/download/2835-188410-1149089-18058/vmware-workstation-6.5.1.126130-2.6.29_x86_64.patch patch] and apply it to the vmware modules sources as follows:<br />
<br />
# cd /usr/lib/vmware/modules/source/<br />
# mkdir orig<br />
# cp *.tar orig/<br />
# for i in *.tar; do tar -xf $i; done<br />
# rm *.tar<br />
# patch -p1 -i /path/to/vmware-workstation-6.5.1.126130-2.6.29_x86_64.patch<br />
# for i in mblock mci mmon mnet mppuser sock; do tar -cf v$i.tar v$i-only; done<br />
# rm -r *-only<br />
<br />
{{Note | Modify <code>/path/to/vmware-workstation-6.5.1.126130-2.6.29_x86_64.patch</code> to match the path to the downloaded patch.}}<br />
<br />
{{Note | This stuff also works for VMWare Server 2 except that the "block" and "ppuser" modules are not present. Therefore patch complains about some missing files. Just let patch ignore this. Also ignore errors tar might give you if you copy and paste the lines above.}}<br />
<br />
Afterwards, build the modules manually or just start vmware, as it will start building the modules for you automatically (using the patched sources). For further information read this [http://communities.vmware.com/thread/192355 thread].<br />
<br />
== VMware and kernel 2.6.28 compile modules problem ==<br />
A tested solution is to [http://www.insecure.ws/warehouse/vmware-update-2.6.27-5.5.7-2.tar.gz fetch] the [http://www.insecure.ws/2008/10/20/vmware-specific-specific-55x-and-kernel-2627 patched modules] and replace them.<br />
To achieve this, you will need to extract the downloaded archive, and replace both vmmon.tar and vmnet.tar to /usr/lib/vmware/modules/source. <br />
After that, run /usr/bin/vmware-config.pl to rebuild the modules.<br />
<br />
== VMware and kernel 2.6.26 compile modules problem ==<br />
If after compiling the modules following the method for 2.6.25 you receive the "Version mismatch with vmmon module:" error when powering on a virtual machine you will need to take one additional step.<br />
<br />
$ cd /usr/lib/vmware/moduels/source/;<br />
$ sudo tar -xvf vmmon.tar;<br />
$ sudo vi vmmon-only/include/iocontrols.h;<br />
<br />
Find the line 48:<br />
#define VMMON_VERSION (161 << 16 | 0)<br />
and change it to:<br />
#define VMMON_VERSION (167 << 16 | 0)<br />
<br />
Save and exit.<br />
<br />
$ sudo tar -cf vmmon.tar vmmon-only;<br />
<br />
Finally, run vmware-config.pl.<br />
<br />
== VMware and kernel 2.6.25 compile modules problem ==<br />
There are extra steps required for Vmware WKS 6.0.3 build 80004, should be the same for VMware Server<br />
# Install and patch as described (use vmware-any-any-update-116.tgz)<br />
# Download the [http://blog.creonfx.com/temp/vmware-any-any-update-117-very-ALPHA.tgz patch117]vmware-any-any-update-117-very-ALPHA.tgz <br />
# Extract the archive in /usr/lib/vmware/modules/source <br />
# Run vmware-2.6.25.sh and then vmware-config.pl<br />
<br />
== VMware and kernel 2.6.24 compile modules problem ==<br />
May not work properly yet. Apply the patch from http://bio.artcradle.com/temp/vault/vmware-any-any-update-116.tgz (untar, run runme.pl script) Note: this is an '''ugly hack''', please don't put it into production systems. Some guest OS'es may have crashes and networking problems with this. '''Don't tell us that you haven't been warned'''<br />
<br />
== VMware and kernel 2.6.22 compile modules problem ==<br />
May not work properly yet. Apply the patch from http://knihovny.cvut.cz/ftp/pub/vmware/vmware-any-any-update112.tar.gz , replace vmnet.tar with http://npw.net/~phbaer/vmnet.tar and reinstall. Note: this is an '''ugly hack''', please dont put it into production systems. Some guest OS'es may have crashes and networking problems with this. '''Dont tell us that you havent been warned'''<br />
<br />
== VMware and kernel 2.6.20 compile modules problem ==<br />
Below is a solution for compiling the vmware modules on kernel 2.6.20.<br />
<br />
$ cd /usr/lib/vmware/modules/source/<br />
$ sudo tar -xvf vmmon.tar<br />
$ cd vmmon-only<br />
$ sudo vi include/compat_kernel.h<br />
<br />
Find this:<br />
#define __NR_compat_exit __NR_exit<br />
static inline _syscall1(int, compat_exit, int, exit_code);<br />
and change the <code>static inline .....</code> line to:<br />
int compat_exit(int exit_code);<br />
<br />
Then tar up the vmmon-only directory again:<br />
$ cd .. #go back to the source directory<br />
$ tar -cf vmmon.tar vmmon-only<br />
<br />
Finally, run vmware-config.pl<br />
<br />
== VMware and kernel 2.6.16 compile modules problem ==<br />
'''PROBLEM''': kernel 2.6.16-x - vmware or vmwareplayer complains that headers are incorect.<br><br />
'''FIX''': You need [http://knihovny.cvut.cz/ftp/pub/vmware/vmware-any-any-update101.tar.gz vmware-any-any-update] patch [ftp://ftp.cvut.cz/vmware/vmware-any-any-update101.tar.gz mirror here] [http://www.inarad.ro/soft/vmware/vmware-any-any-update101.tar.gz or here].<br> Just untar the archive and run ./runme.pl as root - and you-re happy again!<br />
<br />
== Slow networking between host and guest ==<br />
"Those oversized improperly checksummed packets are TCP Segmentation Offload packets. Use ''''ethtool -K eth0 tso off'''' to disable TSO on eth0 (or any other interface which you want to get bridged). At this moment vmnet does not understand TSO, and in addition to that it is silly to use TSO together with bridged networking as vmnet will have to split such packet anyway to pass it to the guest, so splitting will be done anyway, and in addition to it kernel will have to prepare metadata about TCP stream for hardware, so you'll probably get worse performance with TSO enabled than with disabled when you'll have some guest running."<br />
<br />
{{Note | <tt>ethtool</tt> is in extra packages.}}<br />
<br />
== Samba issues ==<br />
The guest os under vmware cannot see a samba share running on the linux host. To fix this problem, edit {{Filename|/etc/samba/smb.conf}} and make some changes under [global]. The following are suggested:<br />
workgroup = YOUR_WORKGROUP<br />
netbios name = YOUR_SERVER_NAME<br />
encrypt passwords = yes<br />
socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_RCVBUF=8192 SO_SNDBUF=8192<br />
interfaces = eth0 vmnet1 vmnet8<br />
sysv shm key=/dev/vmnet1<br />
bind interfaces only = true<br />
<br />
== Connecting Remotely ==<br />
If you setup a server that you would like to connect to remotely, please add the following to {{Filename|/etc/hosts.allow}}:<br />
vmware-authd: ALL<br />
This will enable '''xinetd''' to allow connections from a remote vmware client.<br />
<br />
If this condition is not met, you may see in your {{Filename|/var/log/everything.log}}:<br />
Feb 4 03:34:12 jeffc xinetd[7232]: libwrap refused connection to vmware-authd (libwrap=vmware-authd) from 192.168.1.1<br />
<br />
== Keycode issues ==<br />
# VMware console may mess up your keyboard mapping after VMware tools is installed, effectively making the host desktop unusable until you restart X.<br />
# If you have Windows guests, some/most keycodes might not be working within the guest (especially arrow-keys, ctrl, alt, windows-key, etc.).<br />
<br />
<br />
First solution, by forcing VMware to map keysyms instead of keycodes:<br />
Edit or create the file {{Filename|~/.vmware/config}} and add the following option:<br />
xkeymap.usekeycodeMap = true<br />
<br />
If the first solution still fails to bind certain keys, try the second solution:<br />
Edit or create the file {{Filename|~/.vmware/config}} and add the following keycode-mappings:<br />
<pre><br />
xkeymap.keycode.108 = 0x138 # Alt_R<br />
xkeymap.keycode.106 = 0x135 # KP_Divide<br />
xkeymap.keycode.104 = 0x11c # KP_Enter<br />
xkeymap.keycode.111 = 0x148 # Up<br />
xkeymap.keycode.116 = 0x150 # Down<br />
xkeymap.keycode.113 = 0x14b # Left<br />
xkeymap.keycode.114 = 0x14d # Right<br />
xkeymap.keycode.105 = 0x11d # Control_R<br />
xkeymap.keycode.118 = 0x152 # Insert<br />
xkeymap.keycode.119 = 0x153 # Delete<br />
xkeymap.keycode.110 = 0x147 # Home<br />
xkeymap.keycode.115 = 0x14f # End<br />
xkeymap.keycode.112 = 0x149 # Prior<br />
xkeymap.keycode.117 = 0x151 # Next<br />
xkeymap.keycode.78 = 0x46 # Scroll_Lock<br />
xkeymap.keycode.127 = 0x100 # Pause<br />
xkeymap.keycode.133 = 0x15b # Meta_L<br />
xkeymap.keycode.134 = 0x15c # Meta_R<br />
xkeymap.keycode.135 = 0x15d # Menu<br />
</pre><br />
<br />
==VMware 6.5 Fails to lunch vmware-modconfig==<br />
If vmware-modconfig crash at the first start, download and run this http://communities.vmware.com/servlet/JiveServlet/download/1088282-15379/vmware-build-modules<br />
See more here http://communities.vmware.com/thread/172023<br />
<br />
The above script will fail to compile vsock.so. To fix get vmware to work without it just run (as root):<br />
# depmod -a;<br />
# /etc/rc.d/vmware restart</div>Ajbwhttps://wiki.archlinux.org/index.php?title=VMware&diff=67286VMware2009-04-21T05:03:39Z<p>Ajbw: create fake directories so that VMware installer doesn't complain about the system service runlevels directory not being an init directory</p>
<hr />
<div>[[Category:Emulators (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Installing VMware}}<br />
{{i18n_entry|简体中文|安装VMWare}}<br />
{{i18n_entry|Italiano|Installing_VMware (Italiano)}}<br />
{{i18n_entry|Русский|Установка_VMware (Русский)}}<br />
{{i18n_links_end}}<br />
[http://www.vmware.com/ VMware] installs on [[Arch Linux]] pretty well, but its not totally straight forward.<br />
<br />
==VMware Workstation Installation==<br />
The following is from the VMWare Workstation AUR user comments, by user whompus. It describes how to install VMWare Workstation 6.5.x on either architecture.<br />
<br />
As a temp measure use this method to install 6.5. Note that it will '''not''' install with pacman, so the files installed will '''not''' be traceable/removable with pacman.<br />
<br />
To install Workstation on a Linux host using a bundle<br />
<br />
1. Download VMware-Workstation-6.5.xxxxxx.bundle. Replace xxxxx for whichever minor version & architecture.<br />
<br />
2. In a terminal cd to the directory where you downloaded the file.<br />
<br />
3. Become root to perform the initial installation steps:<br />
# mkdir -p /etc/rc.d/vmware.d/rc{0,1,2,3,4,5,6}.d<br />
# sh VMware-Workstation-6.5.xxxxxx.bundle --console --custom<br />
<br />
4. Read & accept the EULA to continue.<br />
<br />
5. Accept the default settings until it prompts for System service runlevels then set to:<br />
/etc/rc.d/vmware.d/<br />
If you get the error "/etc/rc.d/vmware.d is not an init directory", create the following in /etc/rc.d/vmware.d:<br />
cd /etc/rc.d/vmware.d<br />
mkdir rc0.d rc1.d rc2.d rc3.d rc4.d rc5.d rc6.d init.d<br />
<br />
6. For System service scripts set to:<br />
/etc/rc.d<br />
<br />
7. (Optional) Enter the directory path to the Integrated Virtual Debugger for Eclipse if Eclipse is installed.<br />
<br />
8. Mash enter to install. Note that if nothing happens at this point and you are returned to the prompt, try re-running the installation without the '--console' option.<br />
<br />
9. Open Workstation (<code>vmware</code> in the console) to configure & use!<br />
<br />
After launching vmware, if you experience an errors stating, "modinfo: could not find module vmmon" you may need to rebuild vmware's binary modules. Use the following commands:<br />
<br />
1. Make a backup (required before recompiling models):<br />
# sudo mv /usr/lib/vmware/modules/binary /usr/lib/vmware/modules/binary.old<br />
<br />
2. Recompile modules and load them into memory:<br />
# sudo vmware-modconfig --console --install-all<br />
<br />
==VMware Server Installation==<br />
'''NOTE''' I would highly recommend using VMWare Server 2 on 2.6.27 as it actually builds. It also does not appear to require a patch.<br />
<br />
You can use the [http://aur.archlinux.org/packages.php?do_Details=1&ID=6182&O=0&L=0&C=0&K=vmware&SB=n&SO=a&PP=25&do_MyPackages=0&do_Orphans=0&SeB=nd AUR] or manually install [http://www.vmware.com/download/server/ VMware Server] downloaded from [http://www.vmware.com/ VMware.com]. This guide shows you how to install the manually downloaded VMware server tarball, assuming you are running Voodoo or newer (Duke) with kernel version 2.6.20+ '''32-bit'''.<br />
<br />
===Requirements:===<br />
* Root access. Either 'sudo' or 'su'. For this guide, I will be using 'sudo'.<br />
* [http://archlinux.org/packages/search/?repo=all&category=all&q=xinetd&lastupdate=&limit=50 Xinetd] is installed, up and running.<br />
* The X-libraries libxtst, libxt and libxrender installed<br />
* [http://www.vmware.com/download/server/ VMware server tarball]; latest is 1.0.4 build 56528 as of this writing.<br />
* <strike>VMware server [http://www.vmware.com/community/thread.jspa?messageID=76957&tstart=0 any-to-any]" patch: [http://platan.vc.cvut.cz/ftp/pub/vmware mirror 1] and [ftp://ftp.cvut.cz/vmware mirror 2]. Note: For server 1.0.4 build 56528 you need patch vmware-any-any-update113.tar.bz2, which is on mirror 1 only.</strike><br />
* UPDATE: With 2.6.24 you need this [http://rtr.ca/vmware-2.6.24/ patch] (vmware-any-any-update115a.tgz)<br />
* UPDATE: With 2.6.25 you need also this [http://blog.creonfx.com/temp/vmware-any-any-update-117-very-ALPHA.tgz patch] (vmware-any-any-update-117-very-ALPHA)<br />
* Compatible with VMware Workstation >= 6.0.2 Build 59824 on Linux 2.6.25<br />
* UPDATE: With 2.6.26 you need this [http://vmkernelnewbies.googlegroups.com/web/vmware-any-any-update117d.tar.gz patch] (vmware-any-any-update117d.tar.gz), the VMware version 6.0.5 doesn't need the patch, the version for vmmon e.g. in 117d is even too old (168, need 169!)<br />
* UPDATE: With 2.6.26 and VMWare 6.5 _no_ patch is needed anymore (6.5.0 build-118166). The graphical installer works just fine and all the modules work out of the box. Follow the instructions below for the directory containing the init-scripts.<br />
<br />
===Instructions:===<br />
* Run '''''sudo mkdir -p /etc/rc.d/vmware.d/rc{0,1,2,3,4,5,6}.d''''' to create VMware runlevel directories.<br />
* Run '''''sudo ln -s /bin/lsmod /sbin/''''' to create symlink for lsmod.<br />
* Extract VMware server tarball somewhere... i.e. /tmp/.<br />
* Run '''''cd /tmp/vmware-server-distrib;sudo ./vmware-install.pl'''''. I used '''''/home/vmware/bin''''' for installation.<br />
* When it asks where the directories for ''rc0.d'' thru ''rc6.d'' are, use '''''/etc/rc.d/vmware.d'''''.<br />
* When it asks where the init directory is, use '''''/etc/rc.d'''''.<br />
* '''*QUIT*''' when it asks you if you want to run VMware configuration for the first time.<br />
* Extract VMware server any-to-any patch somewhere... i.e. /tmp/.<br />
* Run '''''cd /tmp/vmware-any-any-update*REV*;sudo ./runme.pl'''''. This will patch VMware server modules to allow Linux kernel 2.6.20 compilation.<br />
* For Linux 2.6.25 additionally to the previous patch115a or 116 you need to manually patch with 117_Alpha.<br />
* For 2.6.25 extract 117 to the location '''''tar xzf vmware-any-any-update-117-very-ALPHA.tgz -C /usr/lib/vmware/modules/source/<br />
* For 2.6.25 patch '''''cd /usr/lib/vmware/modules/source/''''' and run'''''./vmware-2.6.25.sh''''' and continue with next step.<br />
* Run '''''cd /home/vmware/bin;sudo ./vmware-config.pl''''' to compile VMware modules.<br />
<br />
== Running ==<br />
<br />
It's a possibility the first time you try to run Vmware server it'll throw an error stating something about "Unable to power virtual machine". Stop the VMware server and restart xinetd wtih '''''/etc/rc.d/vmware stop;wait;/etc/rc.d/xinetd restart'''''.<br />
<br />
Rerun '''''sudo /home/vmware/bin/vmware-config.pl''''' again. If this still fails, restart your computer and do the above again. It should be fixed.<br />
<br />
There is now a <code>vmware</code> init script in <code>/etc/rc.d</code>. You can add this to your daemons list if you want. I personally dont do this, but if you intend to use the vmware's network when not actually using vmware, then you will need to do this. You will need to start it before you can run vmware though.<br />
<br />
There is a problem with vmware unable to run correctly after a reboot. To fix this edit <code>/etc/rc.d/vmware</code>, find the text below<br />
case "$1" in<br />
start)<br />
and put<br />
rm /etc/vmware/not_configured<br />
immediately after that line.<br />
<br />
To start vmware, you just do <code>vmware</code> from a console window, or create a shortcut or menu item however you like.<br />
<br />
'''Some notes:'''<br />
<br />
Leave the <code>/etc/rc.d/vmware.d</code> directory there, because it is needed whenever you perform <code>vmware-config.pl</code>.<br />
<br />
Remember, if the kernel is changed or updated, you will need to run <code>vmware-config.pl</code> again.<br />
<br />
== Kernel 2.6 and udev ==<br />
<br />
Follow the steps above and then:<br />
<br />
'''1. Modify udev config'''<br />
<br />
Edit <code>/etc/udev/rules.d/00-myrules.rules</code> and add 2 lines:<br />
# tty devices<br />
KERNEL="tty<nowiki>[[0-9]]</nowiki>*", NAME="vc/%n", SYMLINK="%k"<br />
<br />
# floppy devices<br />
KERNEL="fd<nowiki>[[0-9]]</nowiki>*", NAME="floppy/%n" , SYMLINK="fd%n"<br />
<br />
'''2. Start/stop script'''<br />
<br />
It takes care of devices and starts vmware, also stops vmware and removes dev entries. Call it, for example, <code>mkvmdev</code>, chmod it <code>755</code> and put in <code>/etc/rc.d</code>:<br />
<br />
<pre><br />
#!/bin/sh<br />
<br />
. /etc/rc.conf<br />
. /etc/rc.d/functions<br />
<br />
case "$1" in<br />
start)<br />
stat_busy "Creating /dev entries and starting VMware"<br />
for i in `seq 0 9`; do<br />
mknod /dev/vmnet$i c 119 $i<br />
chmod 0600 /dev/vmnet$i<br />
done<br />
for i in `seq 0 3`; do<br />
mknod /dev/parport$i c 99 $i<br />
chmod 0600 /dev/parport$i<br />
done<br />
mknod /dev/vmmon c 10 165<br />
chmod 0660 /dev/vmmon<br />
/etc/rc.d/vmware start<br />
;;<br />
<br />
stop)<br />
stat_busy "Stopping VMware and removing /dev entries"<br />
/etc/rc.d/vmware stop<br />
rm /dev/vmmon<br />
for i in `seq 0 3`; do<br />
rm /dev/parport$i<br />
done<br />
for i in `seq 0 9`; do<br />
rm /dev/vmnet$i<br />
done<br />
;;<br />
<br />
restart)<br />
$0 stop<br />
$0 start<br />
;;<br />
<br />
*)<br />
echo "usage: $0 {start|stop|restart}"<br />
esac<br />
exit 0<br />
</pre><br />
<br />
'''3. Modify <code>/etc/rc.conf</code>.''' (*Note - this step is optional! See also the notes under the "Running" section above)<br />
<br />
Add <code>mkvmdev</code> to daemons in your <code>rc.conf</code>, and remember to remove <code>vmware</code> from <code>rc.conf</code>. Or if you prefer, you can delete the lines that launch vmware from <code>mkvmdev</code> and leave your original <code>vmware</code> in <code>rc.conf</code> - your choice.<br />
<br />
-----<br />
<br />
'''Comments:'''<br />
<br />
hi guys, a couple of quick questions:<br><br />
- why is /dev/vmmon chmod 0660, as opposed to the rest (0600)?<br><br />
- i suppose /dev/vmmon should be "rm"-ed as well in the "stop" section for the script above? (that line is missing) - FIXED<br />
<br />
== VMware and kernel 2.6.29 compile modules problem ==<br />
In Kernel 2.6.29 some internal data-structs were changed. Download this [http://communities.vmware.com/servlet/JiveServlet/download/2835-188410-1149089-18058/vmware-workstation-6.5.1.126130-2.6.29_x86_64.patch patch] and apply it to the vmware modules sources as follows:<br />
<br />
# cd /usr/lib/vmware/modules/source/<br />
# mkdir orig<br />
# cp *.tar orig/<br />
# for i in *.tar; do tar -xf $i; done<br />
# rm *.tar<br />
# patch -p1 -i /path/to/vmware-workstation-6.5.1.126130-2.6.29_x86_64.patch<br />
# for i in mblock mci mmon mnet mppuser sock; do tar -cf v$i.tar v$i-only; done<br />
# rm -r *-only<br />
<br />
{{Note | Modify <code>/path/to/vmware-workstation-6.5.1.126130-2.6.29_x86_64.patch</code> to match the path to the downloaded patch.}}<br />
<br />
{{Note | This stuff also works for VMWare Server 2 except that the "block" and "ppuser" modules are not present. Therefore patch complains about some missing files. Just let patch ignore this. Also ignore errors tar might give you if you coppy and paste the lines above.}}<br />
<br />
Afterwards, build the modules manually or just start vmware, as it will start building the modules for you automatically (using the patched sources). For further information read this [http://communities.vmware.com/thread/192355 thread].<br />
<br />
== VMware and kernel 2.6.28 compile modules problem ==<br />
A tested solution is to [http://www.insecure.ws/warehouse/vmware-update-2.6.27-5.5.7-2.tar.gz fetch] the [http://www.insecure.ws/2008/10/20/vmware-specific-specific-55x-and-kernel-2627 patched modules] and replace them.<br />
To achieve this, you will need to extract the downloaded archive, and replace both vmmon.tar and vmnet.tar to /usr/lib/vmware/modules/source. <br />
After that, run /usr/bin/vmware-config.pl to rebuild the modules.<br />
<br />
== VMware and kernel 2.6.26 compile modules problem ==<br />
If after compiling the modules following the method for 2.6.25 you receive the "Version mismatch with vmmon module:" error when powering on a virtual machine you will need to take one additional step.<br />
<br />
$ cd /usr/lib/vmware/moduels/source/;<br />
$ sudo tar -xvf vmmon.tar;<br />
$ sudo vi vmmon-only/include/iocontrols.h;<br />
<br />
Find the line 48:<br />
#define VMMON_VERSION (161 << 16 | 0)<br />
and change it to:<br />
#define VMMON_VERSION (167 << 16 | 0)<br />
<br />
Save and exit.<br />
<br />
$ sudo tar -cf vmmon.tar vmmon-only;<br />
<br />
Finally, run vmware-config.pl.<br />
<br />
== VMware and kernel 2.6.25 compile modules problem ==<br />
There are extra steps required for Vmware WKS 6.0.3 build 80004, should be the same for VMware Server<br />
# Install and patch as described (use vmware-any-any-update-116.tgz)<br />
# Download the [http://blog.creonfx.com/temp/vmware-any-any-update-117-very-ALPHA.tgz patch117]vmware-any-any-update-117-very-ALPHA.tgz <br />
# Extract the archive in /usr/lib/vmware/modules/source <br />
# Run vmware-2.6.25.sh and then vmware-config.pl<br />
<br />
== VMware and kernel 2.6.24 compile modules problem ==<br />
May not work properly yet. Apply the patch from http://bio.artcradle.com/temp/vault/vmware-any-any-update-116.tgz (untar, run runme.pl script) Note: this is an '''ugly hack''', please don't put it into production systems. Some guest OS'es may have crashes and networking problems with this. '''Don't tell us that you haven't been warned'''<br />
<br />
== VMware and kernel 2.6.22 compile modules problem ==<br />
May not work properly yet. Apply the patch from http://knihovny.cvut.cz/ftp/pub/vmware/vmware-any-any-update112.tar.gz , replace vmnet.tar with http://npw.net/~phbaer/vmnet.tar and reinstall. Note: this is an '''ugly hack''', please dont put it into production systems. Some guest OS'es may have crashes and networking problems with this. '''Dont tell us that you havent been warned'''<br />
<br />
== VMware and kernel 2.6.20 compile modules problem ==<br />
Below is a solution for compiling the vmware modules on kernel 2.6.20.<br />
<br />
$ cd /usr/lib/vmware/modules/source/<br />
$ sudo tar -xvf vmmon.tar<br />
$ cd vmmon-only<br />
$ sudo vi include/compat_kernel.h<br />
<br />
Find this:<br />
#define __NR_compat_exit __NR_exit<br />
static inline _syscall1(int, compat_exit, int, exit_code);<br />
and change the <code>static inline .....</code> line to:<br />
int compat_exit(int exit_code);<br />
<br />
Then tar up the vmmon-only directory again:<br />
$ cd .. #go back to the source directory<br />
$ tar -cf vmmon.tar vmmon-only<br />
<br />
Finally, run vmware-config.pl<br />
<br />
== VMware and kernel 2.6.16 compile modules problem ==<br />
'''PROBLEM''': kernel 2.6.16-x - vmware or vmwareplayer complains that headers are incorect.<br><br />
'''FIX''': You need [http://knihovny.cvut.cz/ftp/pub/vmware/vmware-any-any-update101.tar.gz vmware-any-any-update] patch [ftp://ftp.cvut.cz/vmware/vmware-any-any-update101.tar.gz mirror here] [http://www.inarad.ro/soft/vmware/vmware-any-any-update101.tar.gz or here].<br> Just untar the archive and run ./runme.pl as root - and you-re happy again!<br />
<br />
== Slow networking between host and guest ==<br />
"Those oversized improperly checksummed packets are TCP Segmentation Offload packets. Use ''''ethtool -K eth0 tso off'''' to disable TSO on eth0 (or any other interface which you want to get bridged). At this moment vmnet does not understand TSO, and in addition to that it is silly to use TSO together with bridged networking as vmnet will have to split such packet anyway to pass it to the guest, so splitting will be done anyway, and in addition to it kernel will have to prepare metadata about TCP stream for hardware, so you'll probably get worse performance with TSO enabled than with disabled when you'll have some guest running."<br />
<br />
{{Note | <tt>ethtool</tt> is in extra packages.}}<br />
<br />
== Samba issues ==<br />
The guest os under vmware cannot see a samba share running on the linux host. To fix this problem, edit {{Filename|/etc/samba/smb.conf}} and make some changes under [global]. The following are suggested:<br />
workgroup = YOUR_WORKGROUP<br />
netbios name = YOUR_SERVER_NAME<br />
encrypt passwords = yes<br />
socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_RCVBUF=8192 SO_SNDBUF=8192<br />
interfaces = eth0 vmnet1 vmnet8<br />
sysv shm key=/dev/vmnet1<br />
bind interfaces only = true<br />
<br />
== Connecting Remotely ==<br />
If you setup a server that you would like to connect to remotely, please add the following to {{Filename|/etc/hosts.allow}}:<br />
vmware-authd: ALL<br />
This will enable '''xinetd''' to allow connections from a remote vmware client.<br />
<br />
If this condition is not met, you may see in your {{Filename|/var/log/everything.log}}:<br />
Feb 4 03:34:12 jeffc xinetd[7232]: libwrap refused connection to vmware-authd (libwrap=vmware-authd) from 192.168.1.1<br />
<br />
== Keycode issues ==<br />
# VMware console may mess up your keyboard mapping after VMware tools is installed, effectively making the host desktop unusable until you restart X.<br />
# If you have Windows guests, some/most keycodes might not be working within the guest (especially arrow-keys, ctrl, alt, windows-key, etc.).<br />
<br />
<br />
First solution, by forcing VMware to map keysyms instead of keycodes:<br />
Edit or create the file {{Filename|~/.vmware/config}} and add the following option:<br />
xkeymap.usekeycodeMap = true<br />
<br />
If the first solution still fails to bind certain keys, try the second solution:<br />
Edit or create the file {{Filename|~/.vmware/config}} and add the following keycode-mappings:<br />
<pre><br />
xkeymap.keycode.108 = 0x138 # Alt_R<br />
xkeymap.keycode.106 = 0x135 # KP_Divide<br />
xkeymap.keycode.104 = 0x11c # KP_Enter<br />
xkeymap.keycode.111 = 0x148 # Up<br />
xkeymap.keycode.116 = 0x150 # Down<br />
xkeymap.keycode.113 = 0x14b # Left<br />
xkeymap.keycode.114 = 0x14d # Right<br />
xkeymap.keycode.105 = 0x11d # Control_R<br />
xkeymap.keycode.118 = 0x152 # Insert<br />
xkeymap.keycode.119 = 0x153 # Delete<br />
xkeymap.keycode.110 = 0x147 # Home<br />
xkeymap.keycode.115 = 0x14f # End<br />
xkeymap.keycode.112 = 0x149 # Prior<br />
xkeymap.keycode.117 = 0x151 # Next<br />
xkeymap.keycode.78 = 0x46 # Scroll_Lock<br />
xkeymap.keycode.127 = 0x100 # Pause<br />
xkeymap.keycode.133 = 0x15b # Meta_L<br />
xkeymap.keycode.134 = 0x15c # Meta_R<br />
xkeymap.keycode.135 = 0x15d # Menu<br />
</pre><br />
<br />
==VMware 6.5 Fails to lunch vmware-modconfig==<br />
If vmware-modconfig crash at the first start, download and run this http://communities.vmware.com/servlet/JiveServlet/download/1088282-15379/vmware-build-modules<br />
See more here http://communities.vmware.com/thread/172023<br />
<br />
The above script will fail to compile vsock.so. To fix get vmware to work without it just run (as root):<br />
# depmod -a;<br />
# /etc/rc.d/vmware restart</div>Ajbw