I want to recompile my kernel just as it is right now. This will place the needed things in place to do a vmware install. I am looking for instructions how to do this on suse 9.0. I am looking for the .config file that suse used to create the kernel that suse installed. Is it posted somewhere? or is it on my system somewhere? Is it possible to create a .config from a kernel sitting in my /boot folder? My kernel is listed as vmlinuz-2.4.21-99-athlon dated 9/23/2003
Hi Go to /usr/src/linux, and do "make cloneconfig" Then You have a "copy" of the running kernel configuration... Ps. Make sure You have kernel-sources installed... Jaska.
I want to recompile my kernel just as it is right now. This will place the needed things in place to do a vmware install.
Is it possible to create a .config from a kernel sitting in my /boot folder?
-----Original Message-----
From: Jaakko Tamminen
Hi
Go to /usr/src/linux, and do "make cloneconfig" Then You have a "copy" of the running kernel configuration...
Ps. Make sure You have kernel-sources installed...
Jaska.
I want to recompile my kernel just as it is right now. This will place the needed things in place to do a vmware install.
And speaking of a VMware install.. Why were the VMware modules left -out- of the .166 kernel update?! The km_vmware piece of shit doesn't work and neither does the module complilation from VMware themselves. Going back to the .144 kernel till 2.6 becomes stable. Ken
On Monday 05 January 2004 19:46, Ken Schneider wrote:
And speaking of a VMware install..
Why were the VMware modules left -out- of the .166 kernel update?!
The km_vmware piece of shit doesn't work and neither does the module complilation from VMware themselves. Going back to the .144 kernel till 2.6 becomes stable.
What problems are you encountering? I've been running VMware-gsx-2.5.1-5336 on 2.4.21-166-smp4G (for a whopping 30 minutes or so) with no problems. I did find that the vmware-config.pl compiled _and_ installed vmmon and vmnet modules, so I'm not using any pre-supplied ones. The -99 and -144 kernel versions included these modules, and I thought I had used the SuSE-supplied ones by telling the vmware-config.pl script to not install its own, but I was not presented with that option with the -166 kernel installed.
On Tue, 2004-01-06 at 09:45, Gary Gapinski wrote:
On Monday 05 January 2004 19:46, Ken Schneider wrote:
And speaking of a VMware install..
Why were the VMware modules left -out- of the .166 kernel update?!
The km_vmware piece of shit doesn't work and neither does the module complilation from VMware themselves. Going back to the .144 kernel till 2.6 becomes stable.
What problems are you encountering?
I've been running VMware-gsx-2.5.1-5336 on 2.4.21-166-smp4G (for a whopping 30 minutes or so) with no problems.
I did find that the vmware-config.pl compiled _and_ installed vmmon and vmnet modules, so I'm not using any pre-supplied ones. The -99 and -144 kernel versions included these modules, and I thought I had used the SuSE-supplied ones by telling the vmware-config.pl script to not install its own, but I was not presented with that option with the -166 kernel installed.
The -166 kernel did not come with pre-compiled modules hence you would not get a prompt to overwrite files that do not exist. I have only performed the update at home and when I use vmware-config to create the modules I get a kernel oops when starting vmware (4.0.5 workstation on 9.0 pro). If I try to use the km_vmware addon to create the modules vmware will not start as it cannot load all of the modules. -- Ken Schneider unix user since 1989 linux user since 1994 SuSE user since 1998 (5.2)
imo 9.0 is still not ready for prime time regarding vmware. or the other way around. i guess i will stay with 8.2 /vm 4.05 a bit longer. d. On Tuesday 06 January 2004 05:38, Kenneth Schneider wrote:
On Tue, 2004-01-06 at 09:45, Gary Gapinski wrote:
On Monday 05 January 2004 19:46, Ken Schneider wrote:
And speaking of a VMware install..
Why were the VMware modules left -out- of the .166 kernel update?!
The km_vmware piece of shit doesn't work and neither does the module complilation from VMware themselves. Going back to the .144 kernel till 2.6 becomes stable.
What problems are you encountering?
I've been running VMware-gsx-2.5.1-5336 on 2.4.21-166-smp4G (for a whopping 30 minutes or so) with no problems.
I did find that the vmware-config.pl compiled _and_ installed vmmon and vmnet modules, so I'm not using any pre-supplied ones. The -99 and -144 kernel versions included these modules, and I thought I had used the SuSE-supplied ones by telling the vmware-config.pl script to not install its own, but I was not presented with that option with the -166 kernel installed.
The -166 kernel did not come with pre-compiled modules hence you would not get a prompt to overwrite files that do not exist.
I have only performed the update at home and when I use vmware-config to create the modules I get a kernel oops when starting vmware (4.0.5 workstation on 9.0 pro). If I try to use the km_vmware addon to create the modules vmware will not start as it cannot load all of the modules.
-- Ken Schneider unix user since 1989 linux user since 1994 SuSE user since 1998 (5.2)
On Tuesday 06 January 2004 16:38, Kenneth Schneider wrote:
On Tue, 2004-01-06 at 09:45, Gary Gapinski wrote:
On Monday 05 January 2004 19:46, Ken Schneider wrote:
And speaking of a VMware install..
Why were the VMware modules left -out- of the .166 kernel update?!
The km_vmware piece of shit doesn't work and neither does the module complilation from VMware themselves. Going back to the .144 kernel till 2.6 becomes stable.
What problems are you encountering?
I've been running VMware-gsx-2.5.1-5336 on 2.4.21-166-smp4G (for a whopping 30 minutes or so) with no problems.
I did find that the vmware-config.pl compiled _and_ installed vmmon and vmnet modules, so I'm not using any pre-supplied ones. The -99 and -144 kernel versions included these modules, and I thought I had used the SuSE-supplied ones by telling the vmware-config.pl script to not install its own, but I was not presented with that option with the -166 kernel installed.
The -166 kernel did not come with pre-compiled modules hence you would not get a prompt to overwrite files that do not exist.
I have only performed the update at home and when I use vmware-config to create the modules I get a kernel oops when starting vmware (4.0.5 workstation on 9.0 pro). If I try to use the km_vmware addon to create the modules vmware will not start as it cannot load all of the modules.
[snip] Same problem here, after the kernel upgrade vmware would not start. I ran vmware-config and new modules were created. These gave a kernel oops when I got to the login screen of my XP instance. I then tried to reinstall km_vmware and are still getting a kernel oops. *sigh* I really hope to fix this soon or I'll end up getting fired ;-). Where can I find the previous kernel (.144 I believe) so that I can downgrade? -- Med vennlig hilsen / Kind regards (( Torkild Ulvøy Resheim, Senior Systemutvikler / Software Engineer )) Emma EDB AS, Trondheim, Norway. http://www.emmaedb.no |----|_ "Any sufficiently advanced bug is indistinguishable | | ) from a feature." |____|´
--Boundary-02=_hf++/6zr2e6833k Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Description: signed data Content-Disposition: inline On Wednesday 07 January 2004 09:44, Torkild Ulv=F8y Resheim wrote:
On Tuesday 06 January 2004 16:38, Kenneth Schneider wrote:
On Tue, 2004-01-06 at 09:45, Gary Gapinski wrote:
On Monday 05 January 2004 19:46, Ken Schneider wrote:
And speaking of a VMware install..
Why were the VMware modules left -out- of the .166 kernel update?!
The km_vmware piece of shit doesn't work and neither does the module complilation from VMware themselves. Going back to the .144 kernel till 2.6 becomes stable.
What problems are you encountering?
I've been running VMware-gsx-2.5.1-5336 on 2.4.21-166-smp4G (for a whopping 30 minutes or so) with no problems.
I did find that the vmware-config.pl compiled _and_ installed vmmon a= nd vmnet modules, so I'm not using any pre-supplied ones. The -99 and -1= 44 kernel versions included these modules, and I thought I had used the SuSE-supplied ones by telling the vmware-config.pl script to not install its own, but I was not presented with that option with the -1= 66 kernel installed.
The -166 kernel did not come with pre-compiled modules hence you would not get a prompt to overwrite files that do not exist.
I have only performed the update at home and when I use vmware-config to create the modules I get a kernel oops when starting vmware (4.0.5 workstation on 9.0 pro). If I try to use the km_vmware addon to create the modules vmware will not start as it cannot load all of the modules.
[snip]
Same problem here, after the kernel upgrade vmware would not start. I ran vmware-config and new modules were created. These gave a kernel oops when= I got to the login screen of my XP instance. I then tried to reinstall km_vmware and are still getting a kernel oops. *sigh* I really hope to fix this soon or I'll end up getting fired ;-). Where can I find the previous kernel (.144 I believe) so that I can downgrade? Never mind... I found it (and vmware works again). =2D-=20 Med vennlig hilsen / Kind regards (( Torkild Ulv=F8y Resheim, Senior Systemutvikler / Software Engineer )) Emma EDB AS, Trondheim, Norway. http://www.emmaedb.no |----|_ "Any sufficiently advanced bug is indistinguishable | | ) from a feature." |____|=B4
--Boundary-02=_hf++/6zr2e6833k Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQA/++fhr6G1rOJkYu4RAp+bAKCmThYbY7UuV5dqntBi83T4kXzZlQCeND9l sz+tOJelJ0njiXV6iuHViJQ= =Dquc -----END PGP SIGNATURE----- --Boundary-02=_hf++/6zr2e6833k--
On Wed, 2004-01-07 at 03:44, Torkild Ulvøy Resheim wrote:
Same problem here, after the kernel upgrade vmware would not start. I ran vmware-config and new modules were created. These gave a kernel oops when I got to the login screen of my XP instance. I then tried to reinstall km_vmware and are still getting a kernel oops. *sigh* I really hope to fix this soon or I'll end up getting fired ;-). Where can I find the previous kernel (.144 I believe) so that I can downgrade?
If you upgraded using YaST you should find them here /var/lib/YaST2/you/mnt/i386/update/9.0/rpm/i586/ Unless of course you delete the patches after install. -- Ken Schneider unix user since 1989 linux user since 1994 SuSE user since 1998 (5.2)
participants (7)
-
David Gleba -
Gary Gapinski -
Jaakko Tamminen -
Ken Schneider -
Kenneth Schneider
-
plain -
Torkild Ulvøy Resheim