Is it possible to install Slackware 9.0 on WMware 4?
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I just installed Slacware 9 on VMWare 4.0.2. I did notice right away the default SCSI virtual disk and changed it to IDE. It was out of instinct I guess. Now I just have to get the vmware tools installed.
UPDATE: I got the vmware-tools installed by going through the following instructions found on this site:
I am also having the same problem. I followed the advice here, and changed to IDE mode in the Guest OS Setup wizard, then installed slackware 9.1, everything went fine, up until after the install,when you reboot, I get the black screen with the underscore in the top left everyone talks about. I made the partition bootable, so im stuck as to what else to do.
* boot: scsi.s
* fdisk /dev/sda
* select 'n' followed by 'p' then selected the defaults
* select 'w' which saves the settings
* cfdisk
* make sure sda has boot selected
* setup
* addswap
* selected the packages
* I chose the menu install
* Select a kernel from CDROM and choose the 'scsi.s/bzImage' kernel.
* skip a bootdisk
* no modem
* enable hotplug
* install simple lilo
* install LILO in the MBR
You will get a few more options which are self explanatory like choosing a window manager.
Fixed my install by setting lilo up in MBR, I guess I used something else in the past.
FYI: You can setup the VM with IDE by using the linux option, on the last screen there is an advanced button which will let you pick wether to use IDE or SCSI (instead of using a Windows OS option).
I have installed slackware12.1 on vmware. I did kernel recompiling for vmware device drivers, after new kernel compilation, there is no modules listed on lsmod.
Desktop : windows xp
Vmware Server console 1.0.1
Guest OS : slackware 12.1
This thread is from 2003 with a completely different VMware version together with a completely different version of Slackware. Slackware 9.0 and 12.1 are TOTALLY different. 9.0 uses the 2.4 kernel, while 12.1 uses the 2.6 kernel. VMware is also probably a lot different now. In addition, you already have a thread about the same problem here where people have tried to help you, but you're not helping us help you.
May I ask WHY you need to recompile the kernel? I would think it should work just fine in VMware without the need to recompile. If you're just recompiling the kernel for the learning experience, that's perfectly fine and I will help you with it. However, if you're just trying to get it to work in the first place, I don't think a recompile is even needed.
As for the missing modules, I already responded in the other thread, but you felt the need to start posting in a new thread instead of responding in that one. For a good guide on compiling the kernel, see here. You haven't told us what you have done in this thread or the other one, so it's literally impossible to help you. Help us help you. My guess would be that when you compiled the kernel, you missed out the `make modules_install` step (or maybe the `make modules` step...it's hard to tell with so little information) or maybe if you're compiling the same kernel version as the default kernel that comes with Slackware you've half-overwritten the /lib/modules/2.6.24.5 directory -- but I can't be sure. When I asked you what kernel version you are compiling, you gave an answer which was then different in a subsequent post, and I'm not sure if you're compiling the same version that ships with Slackware or not. You should post the output of `uname -a` and `ls -l /lib/modules/$(uname -r)` if you want help.
Also, do you know for sure that VMware uses the PCnet32 driver for networking, for example? I haven't used VMware, but I would assume that it presents a fake ethernet card to the guest OS, so it wouldn't matter what card you have in YOUR system but instead which card VMware emulates. The PCnet32 driver is compiled as a module in the default kernel anyway, so I'm still confused as to why you need to compile a kernel.
Your missing modules trouble *may* be as simple as running `depmod -a`, but not knowing what you've done prevents me from saying that conclusively.
make mrproper
make menuconfig
make -j3 bzImage
make -j3 modules
make modules_install
cp System.map /boot/System.mapnew
cp .config /boot/confignew
cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuznew
mv /boot/vmlinuz /boot/vmlinuz-old
I was explained my kernel recompiling error clearly on the last thread, but i didnt get any solution, so that i have posted new thread.. I have installed guest OS ie Slackware 12.1 on vmware, some of the vmware device drivers havent set so i tried to recompile the same kernel version for vmware drivers while getting from lspci command I am not updating the kernel version, just recompile the same kernel version. I think so, compiling the same kernel version as the default kernel that comes with Slackware you've half-overwritten the /lib/modules/2.6.24.5 directory. Can you suggest me, if we recompile the same kernel need extra configuration? I am new to kernel compilation and slackware os too.. Please help me
Here is the output before recompiling the kernel,
root@ang189:~# uname -a
Linux ang189 2.6.24.5 #2 Wed Apr 30 14:13:52 CDT 2008 i686 Intel(R) Core(TM)2 CPU 4400 @ 2.00GHz GenuineIntel GNU/Linux
Your `uname -a` output suggests that you're using the huge kernel and not the huge-smp kernel. I would recommend trying out the huge-smp kernel instead, since it is generally more supported. I can't verify whether everything works or not in VMware since I haven't used it, but I would still recommend trying out the huge-smp kernel anyway. Edit your /etc/lilo.conf and add the following stanza:
Then see how well it works (after running /sbin/lilo, of course). Since you are recompiling the same kernel version included with Slackware, you may have overwritten /lib/modules/2.6.24.5 (or /lib/modules/2.6.24.5-smp). I would recommend reinstalling the kernel modules packages. Mount the install media or download kernel-modules-2.6.24.5-i486-2.tgz and kernel-modules-smp-2.6.24.5_smp-i686-2.tgz from a mirror (they are located in the a/ series). Then, you should boot into runlevel 1 by typing `telinit 1`. This disables most services that may impact the reinstallation of the package. Then login as root and type the following:
Then return to runlevel 3 by typing `telinit 3`. Your system will now be restored to its original form. You should probably reboot the system at this point, and reboot into the HugeSMP kernel. If you're lucky, everything will work. Likely it won't, but at least you'll know the state of your system. The reason I recommend the SMP kernel over the non-SMP kernel is because the existing kernel sources are built around the SMP kernel, and require a patch to be set up for the non-SMP kernel. Although this can be done as well, the SMP kernel generally supports more hardware (and I would assume that means virtual hardware as well), and so it's probably a better choice.
Your kernel compilation steps look fine. One thing I will mention though -- since you're compiling the same kernel version that ships with Slackware, /lib/modules/2.6.24.5 (or /lib/modules/2.6.24.5-smp, depending on the configuration file you use) may get overwritten. To prevent this, you should set the LOCALVERSION option to "custom" (or another tag, as long as it isn't smp). This way, /lib/modules/2.6.24.5-custom will be created when you run `make modules_install`, and so you won't have to worry about overwriting anything.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.