Unknown mailing list, 1.

Fedora Core 3 Test 3 under VMware Workstation 4.5.2

Submitted by keithmo
on October 20, 2004 - 11:10am

Fedora Core 3 Test 3 was recently released, and as usual, requires a slight bit of tweaking to run under VMware. So, here we go.

Host Configuration:

  • Toshiba Satellite Laptop
  • 512MB RAM
  • 40GB Internal HD
  • Windows XP Pro SP2 with all updates
  • VMware 4.5.2

Guest Configuration:

  • Fedora Core 3 Test 3 (downloaded .iso files)
  • "Other Linux 2.6.x Kernel"
  • 256MB RAM
  • 4GB HD (/dev/sda1 = /boot, /dev/sda2 = /)
  • 4GB HD (/dev/sdb1 = /usr)
  • 1GB HD (/dev/sdc1 = <swap>)

Installation:

  • Graphical install seems to work OK – no need for "retro" text-mode install.
  • Avoid the CD verification step. It works OK on disk 1, but the other disks generate the following VMware error dialog: Operation on file "D:\ISO\fc3t3\FC3-test3-i386-disc3.iso" failed (Reached the end of the file).
  • Install as usual; shuffle disks and finish the installation.
  • Boot – runlevel 3
  • Login as root.
  • Apply (optional) performance tweaks. Without these, FC3 runs extremely slow under VMware:
    • Run the supplied adjsvc script (with corresponding services.lst file) to remove unnecessary services.
    • Build and install minimal 2.6.9 kernel. See the supplied .config file for sample minimal kernel configuration.
    • Reboot – runlevel 3 again.
  • Extract, patch, and install the VMware Tools:
    • mount /dev/cdrom /mnt
    • tar zxf /mnt/vmware-linux-tools.tar.gz
    • umount /dev/cdrom
    • cd vmware-tools-distrib
    • patch –Np1 –i vmware-4.5.2-fedora-core3-test3.patch
    • ./vmware-install.pl
    • Answer the installation/configuration questions as usual.
  • Reboot, and enjoy.

Notes:

  • When booting FC3, if the VM doesn't have focus when the keyboard is initialized, the keyboard not be detected properly. If you try to login and the keyboard is unresponsive, press the left shift key twice. This will cause the kernel to reinitialize the keyboard.

vmware-4.5.2-fedora-core3-test3.patch

diff -ru vmware-tools-distrib.orig/bin/vmware-config-tools.pl vmware-tools-distrib/bin/vmware-config-tools.pl
--- vmware-tools-distrib.orig/bin/vmware-config-tools.pl	2004-06-11 02:52:10.000000000 +0200
+++ vmware-tools-distrib/bin/vmware-config-tools.pl	2004-10-18 20:24:01.966295392 +0200
@@ -2849,7 +2849,7 @@
 }
sub xserver4 { - return xserver_bin() . '/XFree86'; + return xserver_bin() . '/Xorg'; } sub xserver3 { @@ -3052,7 +3052,7 @@ # string. Maybe it will once it settles down. if ($xversionAll eq "0.0.0") { $xversionAll = direct_command(shell_string(xserver4()) . ' -version 2>&1') =~ - /X.org Foundation/ ? '4.4.0' : '0.0.0'; + /X.org Foundation/ ? '4.4.0' : '4.4.0'; } # This search order is issued from the XF86Config man page. @@ -3063,6 +3063,8 @@ file_name_exist('/usr/X11R6/etc/X11/' . $ENV{'XF86CONFIG'})) { $xconfig_path = '/usr/X11R6/etc/X11'; $xconfig_file_name = $ENV{'XF86CONFIG'}; + } elsif (file_name_exist($xconfig_path . '/xorg.conf')) { + $xconfig_file_name = 'xorg.conf'; } elsif (file_name_exist($xconfig_path . '/XF86Config-4')) { $xconfig_file_name = 'XF86Config-4'; } elsif (file_name_exist($xconfig_path . '/XF86Config')) { @@ -3435,7 +3437,7 @@ my $inSection = 0; my @currentSection; my $sectionLine; - my $keybRegex = 'driver\s+\"keyboard\"'; + my $keybRegex = 'driver\s+\"(keyboard|kbd)\"'; my $kbdIdentifier = 'Keyboard'; my ($line, $copy); @@ -3568,6 +3570,7 @@ if ($major == 4 && $minor >= 2 && file_name_exist($cX4MouseDriverFile)) { $line =~ s/%MOUSE_DRIVER%/vmmouse/g; + $line =~ s-/dev/mouse-/dev/input/mice-; } else { $line =~ s/%MOUSE_DRIVER%/mouse/g; }

adjsvc

#!/bin/bash

action=$1
if [ -z "$action" ]; then
	action=off
fi

for svc in $(< services.lst); do
	echo $svc
	chkconfig --level 35 $svc $action
done

services.lst

acpid
anacron
apmd
atd
autofs
cpuspeed
crond
cups
cups-config-daemon
iptables
irqbalance
isdn
kudzu
mdmonitor
mdmpd
mDNSResponder
messagebus
netfs
nfslock
pcmcia
portmap
readahead
readahead_early
rhnsd
rpcgssd
rpcidmapd
rpcsvcgssd
sendmail
smartd
sshd
xinetd

kernel-config-2.6.9

#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.9
# Tue Oct 19 14:30:31 2004
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y

#
# Code maturity level options
#
# CONFIG_EXPERIMENTAL is not set
CONFIG_CLEAN_COMPILE=y
CONFIG_BROKEN_ON_SMP=y

#
# General setup
#
CONFIG_LOCALVERSION=""
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_BSD_PROCESS_ACCT=y
# CONFIG_BSD_PROCESS_ACCT_V3 is not set
CONFIG_SYSCTL=y
# CONFIG_AUDIT is not set
CONFIG_LOG_BUF_SHIFT=14
# CONFIG_HOTPLUG is not set
# CONFIG_IKCONFIG is not set
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SHMEM=y
# CONFIG_TINY_SHMEM is not set

#
# Loadable module support
#
CONFIG_MODULES=y
# CONFIG_MODULE_UNLOAD is not set
CONFIG_OBSOLETE_MODPARM=y
# CONFIG_KMOD is not set

#
# Processor type and features
#
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
CONFIG_MPENTIUM4=y
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_X86_GENERIC is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=7
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
# CONFIG_HPET_TIMER is not set
# CONFIG_SMP is not set
# CONFIG_PREEMPT is not set
# CONFIG_X86_UP_APIC is not set
CONFIG_X86_TSC=y
# CONFIG_X86_MCE is not set
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set

#
# Firmware Drivers
#
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
# CONFIG_MATH_EMULATION is not set
# CONFIG_MTRR is not set

#
# Power management options (ACPI, APM)
#
CONFIG_PM=y
# CONFIG_PM_DEBUG is not set

#
# ACPI (Advanced Configuration and Power Interface) Support
#
# CONFIG_ACPI is not set
CONFIG_ACPI_BLACKLIST_YEAR=0

#
# APM (Advanced Power Management) BIOS Support
#
CONFIG_APM=y
# CONFIG_APM_IGNORE_USER_SUSPEND is not set
# CONFIG_APM_DO_ENABLE is not set
CONFIG_APM_CPU_IDLE=y
# CONFIG_APM_DISPLAY_BLANK is not set
# CONFIG_APM_RTC_IS_GMT is not set
# CONFIG_APM_ALLOW_INTS is not set
# CONFIG_APM_REAL_MODE_POWER_OFF is not set

#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set

#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_LEGACY_PROC=y
# CONFIG_PCI_NAMES is not set
# CONFIG_ISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set

#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_AOUT is not set
# CONFIG_BINFMT_MISC is not set

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Parallel port support
#
# CONFIG_PARPORT is not set

#
# Plug and Play support
#

#
# Block devices
#
CONFIG_BLK_DEV_FD=y
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
CONFIG_BLK_DEV_LOOP=y
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_SIZE=16384
CONFIG_BLK_DEV_INITRD=y
# CONFIG_LBD is not set

#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y

#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_IDE_SATA is not set
# CONFIG_BLK_DEV_HD_IDE is not set
# CONFIG_BLK_DEV_IDEDISK is not set
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_BLK_DEV_IDESCSI is not set
# CONFIG_IDE_TASK_IOCTL is not set

#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
# CONFIG_BLK_DEV_CMD640 is not set
CONFIG_BLK_DEV_IDEPCI=y
# CONFIG_IDEPCI_SHARE_IRQ is not set
# CONFIG_BLK_DEV_OFFBOARD is not set
# CONFIG_BLK_DEV_GENERIC is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_ATIIXP is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_SC1200 is not set
CONFIG_BLK_DEV_PIIX=y
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
# CONFIG_IDE_ARM is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_BLK_DEV_HD is not set

#
# SCSI device support
#
CONFIG_SCSI=y
CONFIG_SCSI_PROC_FS=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
# CONFIG_BLK_DEV_SR is not set
# CONFIG_CHR_DEV_SG is not set

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set

#
# SCSI Transport Attributes
#
# CONFIG_SCSI_SPI_ATTRS is not set
# CONFIG_SCSI_FC_ATTRS is not set

#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
CONFIG_SCSI_BUSLOGIC=y
CONFIG_SCSI_OMIT_FLASHPOINT=y
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_EATA_PIO is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_QLOGIC_ISP is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
CONFIG_SCSI_QLA2XXX=y

# CONFIG_SCSI_QLA21XX is not set
# CONFIG_SCSI_QLA22XX is not set
# CONFIG_SCSI_QLA2300 is not set
# CONFIG_SCSI_QLA2322 is not set
# CONFIG_SCSI_QLA6312 is not set
# CONFIG_SCSI_QLA6322 is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set


#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set

#
# Fusion MPT device support
#
# CONFIG_FUSION is not set

#
# IEEE 1394 (FireWire) support
#
# CONFIG_IEEE1394 is not set

#
# I2O device support
#
# CONFIG_I2O is not set

#
# Networking support
#
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
# CONFIG_NETLINK_DEV is not set
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_TUNNEL is not set
# CONFIG_NETFILTER is not set
# CONFIG_BRIDGE is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set

#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set
# CONFIG_NET_CLS_ROUTE is not set

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
# CONFIG_HAMRADIO is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
CONFIG_NETDEVICES=y
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set

#
# ARCnet devices
#
# CONFIG_ARCNET is not set

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_NET_VENDOR_3COM is not set

#
# Tulip family network device support
#
# CONFIG_NET_TULIP is not set
# CONFIG_HP100 is not set
CONFIG_NET_PCI=y
CONFIG_PCNET32=y
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_DGRS is not set
# CONFIG_EEPRO100 is not set
# CONFIG_E100 is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_8139TOO is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set
# CONFIG_VIA_VELOCITY is not set

#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_R8169 is not set
# CONFIG_SK98LIN is not set
# CONFIG_TIGON3 is not set

#
# Ethernet (10000 Mbit)
#
# CONFIG_IXGB is not set
# CONFIG_S2IO is not set

#
# Token Ring devices
#
# CONFIG_TR is not set

#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set

#
# Wan interfaces
#
# CONFIG_WAN is not set
# CONFIG_FDDI is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_NET_FC is not set

#
# ISDN subsystem
#
# CONFIG_ISDN is not set

#
# Telephony Support
#
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set

#
# Input I/O drivers
#
# CONFIG_GAMEPORT is not set
CONFIG_SOUND_GAMEPORT=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PCIPS2 is not set
# CONFIG_SERIO_RAW is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set

#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_SERIAL_8250_NR_UARTS=4
# CONFIG_SERIAL_8250_EXTENDED is not set

#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_UNIX98_PTYS=y
# CONFIG_LEGACY_PTYS is not set

#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set

#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_HW_RANDOM is not set
# CONFIG_NVRAM is not set
# CONFIG_RTC is not set
# CONFIG_GEN_RTC is not set
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set

#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
# CONFIG_AGP is not set
# CONFIG_DRM is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HANGCHECK_TIMER is not set

#
# I2C support
#
# CONFIG_I2C is not set

#
# Dallas's 1-wire bus
#
# CONFIG_W1 is not set

#
# Misc devices
#

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set

#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set

#
# Graphics support
#
# CONFIG_FB is not set
CONFIG_VIDEO_SELECT=y

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y

#
# Sound
#
# CONFIG_SOUND is not set

#
# USB support
#
# CONFIG_USB is not set

#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set

#
# File systems
#
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
CONFIG_EXT3_FS=y
# CONFIG_EXT3_FS_XATTR is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
# CONFIG_XFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
# CONFIG_ZISOFS is not set
# CONFIG_UDF_FS is not set

#
# DOS/FAT/NT Filesystems
#
# CONFIG_MSDOS_FS is not set
# CONFIG_VFAT_FS is not set
# CONFIG_NTFS_FS is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_SYSFS=y
# CONFIG_DEVPTS_FS_XATTR is not set
CONFIG_TMPFS=y
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y

#
# Miscellaneous filesystems
#
# CONFIG_HFSPLUS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set

#
# Network File Systems
#
# CONFIG_NFS_FS is not set
# CONFIG_NFSD is not set
# CONFIG_EXPORTFS is not set
# CONFIG_SMB_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y

#

# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="utf8"
CONFIG_NLS_CODEPAGE_437=y
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
CONFIG_NLS_ASCII=y
CONFIG_NLS_ISO8859_1=y
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
CONFIG_NLS_UTF8=y

#
# Kernel hacking
#
# CONFIG_DEBUG_KERNEL is not set
# CONFIG_FRAME_POINTER is not set
CONFIG_EARLY_PRINTK=y
CONFIG_4KSTACKS=y

#
# Security options
#
# CONFIG_SECURITY is not set

#
# Cryptographic options
#
# CONFIG_CRYPTO is not set

#
# Library routines
#
# CONFIG_CRC_CCITT is not set
CONFIG_CRC32=y
# CONFIG_LIBCRC32C is not set
CONFIG_X86_BIOS_REBOOT=y
CONFIG_PC=y
AttachmentSize
vmware-4.5.2-fedora-core3-test3.patch.txt1.71 KB
adjsvc.txt148 bytes
services.lst.txt258 bytes
kernel-config-2.6.9.txt15.53 KB

Thanks again ;)

Anonymous
on
October 24, 2004 - 6:14pm

You got us used to come here looking for vmware-fedora issues :)
Please keep up the good work, and of course thanks again!

Also .. do you know if fedora will ever run normally (not slow) after an install without the need to take out services and tweak the kernel? In other words ... do you have any idea if either fedora or vmware or both have the intention to look into and fix this?

Cheers

No Clue

on
October 24, 2004 - 6:26pm

I have no idea if either VMWare or the Fedora team are interested in these performance problems. If ever I have gobs of time to spare, I'll try to narrow down the exact kernel config option(s) that cause the problem.

One thing I've noticed: With a "stock" Fedora-supplied kernel, the VMware Win32 process constantly pegs the CPU meter at 100%. With my minimal kernel, CPU usage seems more reasonable. I suspect the problem is due to the Fedora kernel's use of the 4G/4G feature, but that's just a total WAG at this point.

Oh yes, one other thing: Thanks for the kind words.

Some Clue

edan idzerda (not verified)
on
December 17, 2004 - 12:45pm

First, thanks for this page. The vmware-any-any* info I've seen other places hasn't helped me; I never even get /dev/vm* classes :-)

The minimal kernel is *MUCH* faster for me. The original 2.6.9-1.667smp kernel took 5 seconds to `ls /usr/lib | wc -l`! The update 2.6.9-681_FC3 was snappier, but it still took 1.0 seconds. The minimal kernel takes 0.02 secs :-)

I believe the 4G/4G feature is at fault, as the time to compile 2.6.9 kernel (based on the kernel-2.6.9-1.681_FC3.src.rpm) with 681_FC3 was 15 minutes. Under the "small" kernel it was 5 minutes, easily repeatable. I changed the small config by adding "4GB kernel-space" and "High Memory 4GB" in processor type and features. Under this "small4G_46" rebuilding the kernel took 16 minutes again. (NOTE: THe compile failed with just CONFIG_X86_4G; it worked when I added CONFIG_HIMEM4G too.)

The CONFIG_X86_4G notes say the overhead might be 20-30%, but this seems to indicate pretty strongly that you do not want to enable this on VMWare systems. The 681_FC3 update *significantly* improved things, but with 4G support off my FC3 VM may be about the same speed as my Redhat 7.2 VM with 2.4.7 :-)

As 681 did seem to be improved, I may try again when a new kernel update is available, but for now I'm sticking with 4G off!

Thanks again.

- edan

Re: some clue

edan idzerda (not verified)
on
December 20, 2004 - 4:51pm

Just FYI. I re-compiled the 2.6.9_681_FC3 kernel with the RPM supplied config and just setting only 686 optimization and 4G/4G and HIMEM4G turned off, and my performance (filesystem, mysql queries) appears to be the same as the minimal kernel, which seems to really point at 4G support as the culprit in VMWare.

Cheers.

- edan

How do I recompile kernel?

quinthar (not verified)
on
June 1, 2005 - 11:19pm

This sounds great. How do I do it? I've installed FC2, and would love to recompile the kernel as you recommend, but I don't know where to start. What are the commands?

Thanks!

-david

Kernel tuning

Anonymous
on
November 3, 2004 - 9:29am

Hi,
Hope you'll post some more info on howto
apply the kernel-config-2.6.9

regads

linux user

doesn't work here...

Anonymous
on
November 3, 2004 - 11:10am

I tried FC3T3 with VMWare 4.5.2 build 8848 using the DVD iso image. Installation seems to go fine. But after first reboot I get the following (as last line);

Kernel panic - not syncing....

Can't help much here cause I'm new to Linux... What I can see (I think) is that during boot sda is not found (?) and so no volume groups are found.

I hope to get this running - I'll try some other Linux distris also.

Regards.

FC3T3

Anonymous
on
November 4, 2004 - 3:05am

Hi,
your problem migth be automatically partition of your disk.
Did let the installation program automatically partition your disks ?
You should do that by yourselves.

you need:
/boot # about 250 Mbyte
/swap # about 2* your memory size
/ # whatever space you have left on your disk

hope this will help u.

FC3T3

Anonymous
on
November 5, 2004 - 5:33am

Indeed. I let it do its thing. I'll try what you proposed.

Thx.

It works...

Anonymous
on
November 8, 2004 - 8:33am

It works... thanks a lot. If you have the time it would be great to add some more specific info on how to upload the patch and how to reboot in level 3. I'll try to find this myself, but it would be great to have ;-)..

Thx.

Run level 3

Anonymous
on
November 10, 2004 - 10:15pm

Instead of booting to runlevel 3, once you are signed in you can hit:
Shift+Ctrl+space, let go of space then hit f1.

A text based window will open.

Jim

Run level 3

Anonymous
on
November 12, 2004 - 5:33pm

It doesn't work that way for me, instead you should press
Ctrl + Alt + F1 to get into runlevel 3, apply the patch, cd /usr/bin and run ./vmware-tools-config.pl answer all the questions with yes except the one with the vmhgs story.

vmware tools don't install

on
November 19, 2004 - 1:29am

Hello All,

I'm new on Fedora, I currecntly using Red hat 9 guest with netware 4.5.2 on an host xp and all work fine. I installed fedora 3 guest and the system works very well. When I try to install the vmware tools I check inside /dev/cdrom, but I cannot found any cdrom entry. Using the same procedurwe on RedHat9 works fine.
I need that in order to see shared folder between Fedora guest and XP host.
(FTP works fine but sharing is faster...:-)

Anyone could help me?
Thanks a lot
Gianka

cdrom

on
November 19, 2004 - 4:52pm

On my Fedora Core 3 system, /dev/cdrom no longer exists -- /dev/hdc is now the cdrom. You might try that (or some other /dev/hdX device).

Also, /mnt/cdrom is no longer the officially blessed mount point for cdroms, but /media/cdrom is. This is for compliance with the Filesystem Hierarchy Standard 2.3.

Extremely useful comment!

Frederic (not verified)
on
February 15, 2005 - 3:53pm

Thank you for your Extremely Useful comment :)

I'm brand new to my own linux system having used University supplied ones, and I was experimenting with vmware and having alot of trouble with this specific issue :)

FC3T3

Anonymous
on
December 6, 2004 - 1:22am

Setting my disks manually for the partition didn't help in my case. I still get the following error message on reboot:

Red Hat nash version 4.1.18 starting
Kernel panic - not syncing: Attempted to kill init!

Can you give me a clue how to build customized kernel in Fedora?

Anonymous
on
November 12, 2004 - 9:24pm

First of all, I would like to thank you for every effort you've done to a guy like me to be able to install/play FC3 on VMWare.

However, could you kindly give me a clue how to build customized kernel in Fedora in more details or a link I can refer to?

Thanks in advance!

To build a kernel you can fol

Anonymous
on
November 14, 2004 - 1:07pm

To build a kernel you can follow the instructions at:
http://acd.ucar.edu/~fredrick/linux/fedorakernel/

Broken link...

Orlando Barron (not verified)
on
September 2, 2006 - 1:31pm

That link is NO MORE!!!

Is there any blog or method l

Anonymous
on
November 13, 2004 - 3:46pm

Is there any blog or method like this for getting SUSE 9.2 to run/install properly under VMWARE 4.5.2?

I have a Win XP Pro host, VMWARE 4.5.2 and SUSE 9.2. The install goes very well, but getting the VMTOOLS to install and work just screws everything up!!!

Any help or tips would be appreciated...
sbj400 at yahoo

Thank you

Anonymous
on
November 21, 2004 - 5:15pm

Fantastic! Thank you for the article. fc3 runs at a blistering pace with vmware 4.5.2 on my guest O/S fc2.

The only modification made to the kernel-config was to include "Multi-device support > Device mapper support" and make the BusLogic module.

Cheers,
Rich

Xen is good for running Linux on Linux

Quinton Hoole (not verified)
on
January 30, 2005 - 3:20pm

Hi

While VMWare is great, particularly for running a Linux VM on Windows, or vice verse, if you're running a Linux VM on Linux, Xen may be a better option for you. See http://www.cl.cam.ac.uk/Research/SRG/netos/xen/.

Benefits include substantial speed improvements, and it's free and open source. The essential difference between xen and vmware is that Xen does not do "full virtualisation", which mean that the OS kernel needs to be ported (or "xenified"). But the benefit of this is that you don't carry the major performance penalty of full virtualisation, which vmware does. The good news is that most of the linux kernels you might be interested in have already been ported. So for example I installed Fedora FC 3 on the provided 2.6 ported kernel, out of the box. There is also a ported 2.4 kernel, for older distros.

Give it a whizz...

Q

Xen

on
January 31, 2005 - 5:58pm

Xen is near the top of my "cool things to investigate Real Soon Now" list. It looks like it will be included as an optional (or maybe even standard?) component of Fedora Core 4.

So where is the link for the xen ports?

coreman (not verified)
on
July 8, 2005 - 7:52am

You wouldn't care to share a link or few for the xen ports whould you?

How is this accomplished, as

Rich2 (not verified)
on
February 22, 2005 - 7:22pm

How is this accomplished, as follows?

CONFIG_MD=y
CONFIG_BLK_DEV_DM=y

How does one go about "making the BusLogic module" ?

performance lack FC and VMware

Anonymous
on
November 28, 2004 - 6:59pm

Probably the same reason like in GSX Server Environment:

The HZ settings in param.h (switch from 1000 to 100) could fix it.

Please check the *complete* following thread:

http://www.vmware.com/community/thread.jspa?threadID=4254&messageID=73938

P.S. Thanx for straightforward anonymous access.

Amas

More tweaks needed for FC3 guest on GSX Server 3.1

Anonymous (not verified)
on
February 21, 2005 - 2:08pm

Thanks to the excellent information, and the various scripts provided here, I was able to get the official FC3 up and running on VMWare GSX 3.1 running on XP host after making some more tweaks.

In addition to keithmo's original post (for FC3 T3), I need to apply more changes:
1. Make the one-line mod on bin/vmware-config-tools.pl script after the patch (explained in the comments).
2. Change the HZ definition in include/asm/param.h from 1000 to 100.
3. Add clock=pit kernel boot parameter in grub.conf.
4. Disable haldaemon service.

The haldaemon appears to be added to the official release after T3. It throws off the the system clock big time (like 10% slower). I only nailed it down after recompile 2.6.10 under FC2 to make sure the kernel wasn't the cause.

Calvin

My problems...

on
December 5, 2004 - 5:34pm

Running VMWare 4.5.2 with Fedora Core 3 (obviously) on an Inspirion 600m. Everything runs smooth up until I get to configuring and installing vmware tools. The code runs without any errors, but once I try booting up into gdm, X complains it can find my mouse. Attempts to run the mouse configuration program fail to have any results here.

Anyone else see this problem or have suggestions?

Mouse problem

Anonymous
on
December 6, 2004 - 12:42pm

change the entry in /etc/XF86Config from /dev/mouse to either /dev/mouse0 or /dev/input/mice. That should be all you need to do. Once it comes up, let me know if your mouse grab/ungrab works without needing Ctrl-Alt. I am running FC3 as a guest on a windows xp host and can't seem to fiugre out why the mouse isn't working. I have no problems using RH9 or FC2, but FC3 is not functioning correctly.

Worked like a charm.

on
December 6, 2004 - 2:40pm

Incidentally, I am running FC3 on Windows XP. Haven't had any problems aside from the mouse issue.

The same proplem here

Anonymous
on
December 8, 2004 - 11:19pm

well, i didn't have that mouse proplem when i first installed FC3
but after installing VMWare Tools, the proplem started to appear

I use FC3 as a guest on a windows XP SP2 (Media Center) host..

I hope i can find a solution for this.. (yeah, I came here through google) :D

That's exactly the problem I

on
December 8, 2004 - 11:29pm

That's exactly the problem I had. It only cropped up after installing VMWare Tools. Use the solution that was suggested above, go into /etc/XF86Config and change the /dev/mouse reference to /dev/mouse0.

It worked!!

Anonymous
on
December 9, 2004 - 12:08am

When i changed the /etc/XF86Config to "/dev/mouse0" (after 1 hour spent in understanding the vim editor) :D

thanks for the help!

mouse to mouse0

Anonymous (not verified)
on
March 14, 2005 - 1:42pm

thanks!!!!

can not install VMwareTool

Anonymous (not verified)
on
December 20, 2004 - 3:45am

Hello All,

I'm english was very poor.Sorry for that.
And,I need some help.
I'm new on Linux.
I have try to install Fedora Core 3 on VMware Workstaion 4.5.2.
Host os is XP Pro sp1.
Installation was finished without error.
reboot finish,it work on Graphical Mode.
I try to use "telinit 3" to run in the text mode,
but it stop at
starting anacron: [OK]

It look like stop respond.
How should I run text mode?
------
I try to install VMwareTool in Graphical Mode.
when Install finished,I try to config the VMwareTool.
It said i can't run it in X mode.
Faint!
How should I make it work?

Hi, I had the same problem,

Jeppo (not verified)
on
February 26, 2005 - 12:06pm

Hi,
I had the same problem, and I solved it, trying to change terminal (in my case pressing CTRL+ALT+F1 to pass from a Graphic Terminal to a Text Terminal, because I have set my hotkey combination as CTRL+ALT+SHIFT, so it works)...

I don't know what was the cause of this hanging...

Cannot aplyy patch

Anonymous (not verified)
on
December 20, 2004 - 11:42am

Hi!

I'm with problems applying the patch.
I've got this error:

patch: *** malformed patch at line 11: sub xserver4 {

Anyone knows what i've to do?

Thanks in advance.

hello all. I've got the er

Anonymous (not verified)
on
December 21, 2004 - 7:21am

hello all.

I've got the error.

patch: **** malformad patch at line 11: @@ -3052,7 +3052,7 @@

Anyone knows what i've to do?

I got the same problem

chrisg (not verified)
on
December 23, 2004 - 9:22pm

Hi ,
I got the same problem trying to patch ,
what is missing there ?

OK, I think I've found the pr

on
December 24, 2004 - 7:44am

OK, I think I've found the problem (finally!)

The blog software seems to be munging one of the first lines of the patch. There should be a line, consisting of a single space, after the " }" on line 5 and the "sub xserver4 {" (which should be line 7). This is all formatted as a "pre" section, so line breaks, etc should be preserved. They appear to be for other lines.

I've used the new file attachment feature to attach the patch (and other files mentioned in this blog entry). Note that I had to add ".txt" extensions to the files -- you'll need to remove these when you save them. (The blog software doesn't seem to like ".patch", ".lst", and other extensions.)

Try again, and sorry for the confusion!

oops it does not work for me

chrisg (not verified)
on
December 27, 2004 - 11:12pm

oops it does not work for me ...
I download the patch, here is what I done and the output I have.

patch -Np1 -i vmware-4.5.2-fedora-core3-test3.patch
patching file bin/vmware-config-tools.pl
Hunk #2 FAILED at 3052.
Hunk #5 succeeded at 3570 with fuzz 1.
1 out of 5 hunks FAILED -- saving rejects to file bin/vmware-config-tools.pl.rej

Here is what I got in bin/vmware-config-tools.pl.rej

***************
*** 3052,3058 ****
# string. Maybe it will once it settles down.
if ($xversionAll eq "0.0.0") {
$xversionAll = direct_command(shell_string(xserver4()) . ' -version 2>&1') =~
- /X.org Foundation/ ? '4.4.0' : '0.0.0';
}

# This search order is issued from the XF86Config man page.
--- 3052,3058 ----
# string. Maybe it will once it settles down.
if ($xversionAll eq "0.0.0") {
$xversionAll = direct_command(shell_string(xserver4()) . ' -version 2>&1') =~
+ /X.org Foundation/ ? '4.4.0' : '4.4.0';
}

# This search order is issued from the XF86Config man page.

thank for your help

BTW , since my network was working I upgrade fc3 prior to install vmware tools, but I don't know if its related to my patch problem !?

Chris

Does not work for me either...

Anonymous (not verified)
on
December 28, 2004 - 12:42am

I get the exact same errors as chrisg. I did not update my FC3 however yet. Does anyone have any idea...? Help is appreciated.

manually edit the file

Anonymous (not verified)
on
December 28, 2004 - 2:00am

Just manually edit the file (bin/vmware-config-tools.pl) and change the line

/X.org Foundation/ ? '4.4.0' : '0.0.0';

to

/X.org Foundation/ ? '4.4.0' : '4.4.0';

Thanks it worked like a charm

Anonymous (not verified)
on
February 26, 2005 - 4:24am

Thanks it worked like a charm ....

add a "-l" (or "--ignore-whitespace") to the patch command

Dusty Bottoms (not verified)
on
March 13, 2005 - 9:06pm

After looking and looking at the patch file for a fix to the "Hunk #2 FAILED at 3052." problem, I gave up and used the "--ignore-whitespace" switch (aka "-l") and that seems to work just fine, ie:

patch –lNp1 –i vmware-4.5.2-fedora-core3-test3.patch

Just my 2 pesos...

another thanks

Anonymous (not verified)
on
December 25, 2004 - 12:11pm

Thanks! I wouldn't have got vmware-tools working without this! :-)

All is good, but shared drives...

Anonymous (not verified)
on
December 29, 2004 - 4:58am

Hello,

OK, I got everything working ;-} (well... almost). I got the kernel from kernel.org and am using version 10 without 4G and it's pretty fast. I updated everything using yum. I used the fix above to get VMware tools to run. After running the patch I got the hunk errors. I then changed this (as above) :

vmware-config-tools.pl) and change the line

/X.org Foundation/ ? '4.4.0' : '0.0.0';

to

/X.org Foundation/ ? '4.4.0' : '4.4.0';

Then I ran the vmware tools install... Everything was great. I compiled the stuff needed for the new kernel (when the vmware installer) asks me. Now I shared some drives... I look under /mnt and see hgfs. However under that there is no shared drives.

Does anyone have any idea if this works or how to get it to work? Aslo, I am not able to browse the network enymore for networked shared drives.

I also tried sharing the drives and then re-running the installer. That did not work.

Thanks!

FC3 and starting X - vmware_drv.o seems to hang display & guest

on
December 31, 2004 - 6:12pm

Thanks for these instructions.

I'm on a T41 (Pentium M) laptop with an Nvidia driver running XP SP1 as host and FC3 as guest. I am still having trouble getting X to start. I boot to init 3 but when I try to startx, the X server start up hangs although I am still able to login with ssh. After awhile, the host vmware process starts consuming most of the CPU and I have to power the guest off. I have tried all of the vmware_drv.o that are in the vmware tarball but all of them show this behavior. I did get it work for a few days under the vmware_drv 4.x.0 driver but then it stopped working with no other config changes that I am aware of!

Any thoughts? I have also tried different screen depths but no luck. The X log file indicates that the vmware_drv was the last driver loaded but no error messages or messages after it loads the vmware driver.

I also had to fix the vmhgfs driver as indicated in another post since it would continuously append the same file to itself over and over again. The network worked fine once I had turned off the Cisco vpn client's always on stateful inspection feature.

Perhaps one of the updates from up2date?

upgrage kernel

Kenzo (not verified)
on
January 1, 2005 - 10:43pm

Hi,
First thank u, keithmo for this tutorial
Im a beginer in Linux... Can anyone explain for me how to upgrage the kernel to the keithmo's config plz.
Thanks

Piece-O-Cake. Ensure you

on
January 2, 2005 - 1:33pm

Piece-O-Cake.

  • Ensure you have all of the necessary development tools installed. At a minimum, you'll need make, gcc, and possibly a few others. If something is missing, the kernel build will complain. Loudly.
  • Download your kernel of choice from kernel.org or one of its mirrors. Version 2.6.10 appears to be pretty stable.
  • Unpack the archive: tar jxf linux-2.6.10.tar.bz2
  • You may want to edit the linux-2.6.10/Makefile and edit the "EXTRAVERSION=" line. Anything you place here will become part of the new kernel's "name" -- I usually use "-ckm" (my initials).
  • Copy the config file listed above to the linux-2.6.10 directory. Ensure you copy it as .config -- the leading "." is critical.
  • Execute make oldconfig to update the .config file with any new additions. IIRC, there were a few config parameters added to 2.6.10, so this step will prompt you. Just press [enter] to accept the default for each.
  • Execute make all to build the kernel. This may take a while.
  • Execute su to logon (temporarily) as root.
  • Execute make modules_install to install any modules, then make install to install the kernel.
  • Reboot, select your new kernel from the Grub boot menu, and see if it works :)
  • After rebooting, you'll need to reconfigure VMware tools. You don't need to reinstall, just logon as root and execute vmware-config-tools.pl and answer the questions.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.