Re: [[newbie] message repeats]
Bob Jackson [EMAIL PROTECTED] wrote: Has anyone else got a repeat on saturday's messages? I got a couple of dozen repeats. Bob J. Ditto! ++ Michael Scottaline COL 2.2 Linux 2.2.5 * * * * * * * * * * * It's a fresh wind that Blows Against the Empire Get your own FREE, personal Netscape WebMail account today at http://webmail.netscape.com.
Re: [[newbie] message repeats]
Hi there. I have recently tried to re-install vmware (the new beta version), to see if I can finally get it to work. However, I get the following message during the install: "None of VMware's pre-built vmmon modules is suitable for your running kernel. Do you want this script to try to build the vmmon module for your system (you need to have a C compiler installed on your system)? [yes] What is the location of the directory of C header files that match your running kernel? [/usr/src/linux/include] The directory of kernel headers (version 2.2.9-19mdk) does not match your running kernel (version 2.2.9-27mdk). Consequently, even if the compilation of the module was successful, the module would not load into the running kernel." I answer the defaults to both questions - I assume that I have installed a C compiler because I selected everything when I installed linux originally (stop laughing - I wasn't to know any better :) ). As you can see, I have compiled a new kernel (I think it worked - I don't get any error messages during boot-up). Can someone tell me (in simple terms) how I might be able to fix this error? If you require further info please ask, as I still have little to no idea what I am doing in linux. Thanks, Chris.
Re: [[newbie] message repeats]
"Chris" == Chris Smallhorne [EMAIL PROTECTED] writes: [snip] Chris The directory of kernel headers (version 2.2.9-19mdk) does Chris not match your running kernel (version Chris 2.2.9-27mdk). Consequently, even if the compilation of the Chris module was successful, the module would not load into the Chris running kernel." [snip] Chris messages during boot-up). Can someone tell me (in simple Chris terms) how I might be able to fix this error? If you [snip] Upgrade kernel-headers to 2.2.9-27mdk. But, you might want to check the VMware pages, since I believe vmware doesn't work with 2.2.9-27. It does work with other kernel versions. -- Mike Fieschko, West Orange, NJ, USA X-Mailer: XEmacs 21.1, VM 6.71 and random-sig.el X-Face header is me! http://www.cs.indiana.edu/picons/ftp/faq.html Kernel 2.2.13-7mdk mailto:[EMAIL PROTECTED] http://www.viconet.com/fieschko/home.htm Sep 21 St Matthew "Truth is sacred; and if you tell the truth too often nobody will believe it." - [G.K. Chesterton, in ILN, 2/24/06]
Re: [newbie] message repeats
On Mon, 20 Sep 1999, you wrote: Has anyone else got a repeat on saturday's messages? I got a couple of dozen repeats. YES I sent a message to Axalon asking him to pass it along to the Majordomo "owner." John
Re: [[newbie] message repeats]
Thanks for the info Mike, I went to the VMware site to check it out - here is what it said: Software requirements 1.VMware host operating system requirements glibc2 to glibc6 (glibc1 does not work) Linux kernel 2.0.32 to 36 Linux kernel 2.2.0 and higher for SMP systems VMware will not run on systems that do not meet these requirements. Does this mean that I need to find a copy of kernel version 2.0.32 to 36, or should it work with 2.2.9-19mdk? If I only need to go back to 2.2.9-19mdk, is it easier to do an "upgrade" install to go back to this kernel version, or won't this work and will I be stuck with doing an install from scratch? I don't think I made a backup of the old kernel - if I did, I don't know where I put it. Is there any way to find out? BTW, what does the -19mdk mean? Thanks, Chris. Mike Fieschko wrote: "Chris" == Chris Smallhorne [EMAIL PROTECTED] writes: [snip] Chris The directory of kernel headers (version 2.2.9-19mdk) does Chris not match your running kernel (version Chris 2.2.9-27mdk). Consequently, even if the compilation of the Chris module was successful, the module would not load into the Chris running kernel." [snip] Chris messages during boot-up). Can someone tell me (in simple Chris terms) how I might be able to fix this error? If you [snip] Upgrade kernel-headers to 2.2.9-27mdk. But, you might want to check the VMware pages, since I believe vmware doesn't work with 2.2.9-27. It does work with other kernel versions. -- Mike Fieschko, West Orange, NJ, USA X-Mailer: XEmacs 21.1, VM 6.71 and random-sig.el X-Face header is me! http://www.cs.indiana.edu/picons/ftp/faq.html Kernel 2.2.13-7mdk mailto:[EMAIL PROTECTED] http://www.viconet.com/fieschko/home.htm Sep 21 St Matthew "Truth is sacred; and if you tell the truth too often nobody will believe it." - [G.K. Chesterton, in ILN, 2/24/06]
Re: [[newbie] message repeats]
"Chris" == Chris Smallhorne [EMAIL PROTECTED] writes: [snip] Chris Software requirements Chris 1.VMware host operating system Chris requirements glibc2 to glibc6 (glibc1 does not work) Linux Chris kernel 2.0.32 to 36 Linux kernel 2.2.0 and higher for SMP Chris systems ChrisVMware will not run on systems that do Chris not meet these requirements. Chris Does this mean that I need to find a copy of kernel version Chris 2.0.32 to 36, or should it work with 2.2.9-19mdk? If I It works with 2.2.9-19mdk. I've used it and I have only one CPU. (I've also used it with 2.2.13-7 from the 6.1 release.) Chris only need to go back to 2.2.9-19mdk, is it easier to do an Chris "upgrade" install to go back to this kernel version, or Chris won't this work and will I be stuck with doing an install Chris from scratch? I don't think I made a backup of the old Chris kernel - if I did, I don't know where I put it. Is there Chris any way to find out? Install or upgrade? from man rpm: rpm -U [install-options] package_file+ This upgrades or installs the package currently installed to the version in the new RPM. This is the same as install, except all other version of the package are removed from the system. Since upgrade removes other versions of the package, you want install. BUT: * watch out for symlinks in /boot and /lib/modules ** You ought to rm the symlinks, so when you install, the existing vmlinuz, module-info, and System.map in /boot and /lib/modules isn't overwritten. Where's your old kernel (was it -19?)? It ought to be in /boot, if it wasn't overwritten when you put in -27 What does ls /boot/ show? Here is mine: $ls /boot/ System.map@ bzImage os2_d.b System.map-2.2.13-5mdk chain.b vmlinuz@ System.map-2.2.13-5mdkBOOT core vmlinuz-2.2.13-5mdk System.map-2.2.13-7mdk initrd-2.2.9-19mdk.img vmlinuz-2.2.13-5mdkBOOT System.map-2.2.9-27mdk map vmlinuz-2.2.13-7mdk System.map-2.2.9-27mdkfbmodule-info@ vmlinuz-2.2.9-27mdk boot.0300 module-info-2.2.13-5mdk vmlinuz-2.2.9-27mdkfb boot.0341 module-info-2.2.13-7mdk boot.b module-info-2.2.9-27mdk $ The symlinks are to the 2.2.13-7 stuff. Chris BTW, what does the -19mdk mean? Probably that it's from a Mandrake distribution. -- Mike Fieschko, West Orange, NJ, USA X-Mailer: XEmacs 21.1, VM 6.71 and random-sig.el X-Face header is me! http://www.cs.indiana.edu/picons/ftp/faq.html Kernel 2.2.13-7mdk mailto:[EMAIL PROTECTED] http://www.viconet.com/fieschko/home.htm Sep 21 St Matthew "Civilization has run on ahead of the soul of man, and is producing faster than he can think and give thanks." - [G.K. Chesterton, in Daily News, 2/21/02]
