[opensuse-support] lost vmlinuz for kernels in /usr/src
Hi-- I lost vmlinuz's for kernels in /usr/src/ so I can't boot the previous 5.7.11 kernel hence no VMware. Can I create the files necessary to boot the /usr/src/linux-5.7.11-1? Thanks Tom Tumbleweed up to date VERSION_ID="20200813" -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 16/08/2020 00.52, Tom wrote:
Hi-- I lost vmlinuz's for kernels in /usr/src/ so I can't boot the previous 5.7.11 kernel hence no VMware.
Can I create the files necessary to boot the /usr/src/linux-5.7.11-1?
Normally, mkinitrd does it, but the "kernels in /usr/src/" part has me baffled. You will have to explain what does that mean.
Tumbleweed up to date VERSION_ID="20200813"
-- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 8/15/20 7:14 PM, Carlos E. R. wrote:
On 16/08/2020 00.52, Tom wrote:
Hi-- I lost vmlinuz's for kernels in /usr/src/ so I can't boot the previous 5.7.11 kernel hence no VMware.
Can I create the files necessary to boot the /usr/src/linux-5.7.11-1?
Normally, mkinitrd does it, but the "kernels in /usr/src/" part has me baffled. You will have to explain what does that mean.
Tumbleweed up to date VERSION_ID="20200813"
Thanks Carlos- I mean there is a file /usr/src/linux-5.7.11-1 with others that have kernel names from recent updates. So, can that file be used to generate a bootable entry in grub2? Tom -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 16/08/2020 04.30, Tom Wekell wrote:
On 8/15/20 7:14 PM, Carlos E. R. wrote:
On 16/08/2020 00.52, Tom wrote:
Hi-- I lost vmlinuz's for kernels in /usr/src/ so I can't boot the previous 5.7.11 kernel hence no VMware.
Can I create the files necessary to boot the /usr/src/linux-5.7.11-1?
Normally, mkinitrd does it, but the "kernels in /usr/src/" part has me baffled. You will have to explain what does that mean.
Tumbleweed up to date VERSION_ID="20200813"
Thanks Carlos- I mean there is a file /usr/src/linux-5.7.11-1 with others that have kernel names from recent updates. So, can that file be used to generate a bootable entry in grub2?
No, vmlinuz is not generated from that. I thought you might have created your own kernel. Just run "mkinitrd" in a terminal as root. This has no relation at all to vmwware. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
Le 16/08/2020 à 00:52, Tom a écrit :
Hi-- I lost vmlinuz's for kernels in /usr/src/ so I can't boot the previous 5.7.11 kernel hence no VMware.
Can I create the files necessary to boot the /usr/src/linux-5.7.11-1? Tanks Tom
Tumbleweed up to date VERSION_ID="20200813"
I guess you didn't completely understand the problem... (anybody was like this at some point :-) For vmware or any application needing a kernel module to be compiled, you have to get the "kernel headers", installed with yast. Nothing to do with GRUB. for such application present in Yast (AKA virtualbox, for example), the module come pre-compiled, so no need. GRUB needs kernels in /boot, here lrap 15.1:
ll /boot/ total 69544 -rw-r--r-- 1 root root 1725 13 juil. 2019 boot.readme -rw-r--r-- 1 root root 200382 11 juin 09:16 config-4.12.14-lp151.28.52-default -rw-r--r-- 1 root root 200426 5 août 14:38 config-4.12.14-lp151.28.59-default drwxr-xr-x 3 root root 16384 1 janv. 1970 efi drwxr-xr-x 1 root root 142 8 août 20:28 grub2 lrwxrwxrwx 1 root root 34 6 août 14:52 initrd -> initrd-4.12.14-lp151.28.59-default -rw------- 1 root root 14450344 8 août 20:28 initrd-4.12.14-lp151.28.52-default -rw------- 1 root root 14452052 8 août 20:28 initrd-4.12.14-lp151.28.59-default -rw-r--r-- 1 root root 1182907 11 juin 09:26 symtypes-4.12.14-lp151.28.52-default.gz -rw-r--r-- 1 root root 1183023 5 août 15:50 symtypes-4.12.14-(...) (...) lrwxrwxrwx 1 root root 35 6 août 14:52 vmlinuz -> vmlinuz-4.12.14-lp151.28.59-default -rw-r--r-- 1 root root 7327856 11 juin 09:47 vmlinuz-4.12.14-lp151.28.52-default -rw-r--r-- 1 root root 7336064 5 août 17:03 vmlinuz-4.12.14-lp151.28.59-default
jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 8/15/20 3:52 PM, Tom wrote:
Hi-- I lost vmlinuz's for kernels in /usr/src/ so I can't boot the previous 5.7.11 kernel hence no VMware.
Tumbleweed up to date VERSION_ID="20200813" I will restate my problem - VMware will not run on kernel 5.8; as it connects it spontaneously re- boots the entire machine with no warning. - I need a previous kernel. Google shows no such for openSUSE - I could pause the boot and select such a kernel _ In my wisdom I removed kernel 5.8 with YaST but it removed all my previous kernels and left my with 4.13's where did they come from? - What are these files: ls -l /usr/src rwxr-xr-x 17 root root 4096 2020-07-22 16:08 kernel-modules lrwxrwxrwx 1 root root 13 2020-08-15 14:14 linux -> linux-5.8.0-1 drwxr-xr-x 23 root root 4096 2020-08-03 07:06 linux-5.7.11-1 drwxr-xr-x 3 root root 4096 2020-08-05 10:07 linux-5.7.11-1-obj drwxr-xr-x 23 root root 4096 2020-07-22 06:04 linux-5.7.9-1 drwxr-xr-x 3 root root 4096 2020-07-24 17:04 linux-5.7.9-1-obj drwxr-xr-x 23 root root 4096 2020-08-08 07:26 linux-5.8.0-1 drwxr-xr-x 3 root root 4096 2020-08-15 14:14 linux-5.8.0-1-obj drwxr-xr-x 3 root root 4096 2020-08-08 07:29 linux-obj drwxr-xr-x 8 root root 4096 2020-08-01 03:36 packages - Is there a recipe to make bootable kernels from these? Any help is appreciated. Tom -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 17/08/2020 21.30, Tom wrote:
On 8/15/20 3:52 PM, Tom wrote:
Hi-- I lost vmlinuz's for kernels in /usr/src/ so I can't boot the previous 5.7.11 kernel hence no VMware.
Tumbleweed up to date VERSION_ID="20200813"
I will restate my problem
- VMware will not run on kernel 5.8; as it connects it spontaneously re- boots the entire machine with no warning.
- I need a previous kernel. Google shows no such for openSUSE
- I could pause the boot and select such a kernel
_ In my wisdom I removed kernel 5.8 with YaST but it removed all my previous kernels and left my with 4.13's where did they come from?
You are lucky your machine still boots.
- What are these files: ls -l /usr/src rwxr-xr-x 17 root root 4096 2020-07-22 16:08 kernel-modules lrwxrwxrwx 1 root root 13 2020-08-15 14:14 linux -> linux-5.8.0-1 drwxr-xr-x 23 root root 4096 2020-08-03 07:06 linux-5.7.11-1 drwxr-xr-x 3 root root 4096 2020-08-05 10:07 linux-5.7.11-1-obj drwxr-xr-x 23 root root 4096 2020-07-22 06:04 linux-5.7.9-1 drwxr-xr-x 3 root root 4096 2020-07-24 17:04 linux-5.7.9-1-obj drwxr-xr-x 23 root root 4096 2020-08-08 07:26 linux-5.8.0-1 drwxr-xr-x 3 root root 4096 2020-08-15 14:14 linux-5.8.0-1-obj drwxr-xr-x 3 root root 4096 2020-08-08 07:29 linux-obj drwxr-xr-x 8 root root 4096 2020-08-01 03:36 packages
- Is there a recipe to make bootable kernels from these?
That's not the way to go. You have to look at boombatower. https://review.tumbleweed.boombatower.com/about.html You can install *some* previous version of Tumbleweed from here: http://download.opensuse.org/history/ -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 8/17/20 12:37 PM, Carlos E. R. wrote:
On 17/08/2020 21.30, Tom wrote:
On 8/15/20 3:52 PM, Tom wrote:
Hi-- I lost vmlinuz's for kernels in /usr/src/ so I can't boot the previous 5.7.11 kernel hence no VMware.
Tumbleweed up to date VERSION_ID="20200813"
I will restate my problem
- VMware will not run on kernel 5.8; as it connects it spontaneously re- boots the entire machine with no warning.
- I need a previous kernel. Google shows no such for openSUSE
You have to look at boombatower.
https://review.tumbleweed.boombatower.com/about.html
You can install *some* previous version of Tumbleweed from here:
Thanks Carlos-- I found a 5.7 kernel at http://download.opensuse.org/history/ Thanks Tom -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Le 17/08/2020 à 21:30, Tom a écrit :
On 8/15/20 3:52 PM, Tom wrote:
Hi-- I lost vmlinuz's for kernels in /usr/src/ so I can't boot the previous 5.7.11 kernel hence no VMware.
this is the *source* path, necessary to compile vmware modules, not to boot the system (except if you compile your kernel yourself) boot kernels are in /boot
- VMware will not run on kernel 5.8; as it connects it spontaneously re- boots the entire machine with no warning.
odd... but anyway to be able to compile any module, and use it, the source have to be the same than the booted kernel uname -a should give you the name of the running kernel.
- I need a previous kernel. Google shows no such for openSUSE
openSUSE is not android, no google here. look in yast, search for "kernel", I'm pretty sure you will have a choice. Check is "source" repo is present and load any and the source equivalent (installing the headers is enough)
_ In my wisdom I removed kernel 5.8 with YaST but it removed all my previous kernels and left my with 4.13's where did they come from?
you are probably looking in the *source* repo, not is the main one
- What are these files: ls -l /usr/src
you can remove them before going to yast, if needed they will be reinstalled, probably a remain of previous compilations, not is the removed package so left in place jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 8/17/20 11:54 PM, jdd@dodin.org wrote:
Le 17/08/2020 à 21:30, Tom a écrit :
On 8/15/20 3:52 PM, Tom wrote:
Hi-- I lost vmlinuz's for kernels in /usr/src/ so I can't boot the previous 5.7.11 kernel hence no VMware.
this is the *source* path, necessary to compile vmware modules, not to boot the system (except if you compile your kernel yourself)
boot kernels are in /boot
- VMware will not run on kernel 5.8; as it connects it spontaneously re- boots the entire machine with no warning.
odd...
JDD-- From http://rglinuxtech.com/?p=2774 VMware – Kernel 5.8 is a Serious Problem? Posted on July 19, 2020 by RG Since the release of Kernel 5.8-rc1, any attempt I made to run a VMware client on that host system has failed catastrophically. ( see http://rglinuxtech.com/?p=2753 ) and the problem still persists, with 5.8-rc6. I had posted brief details of the issue on the VMware forum some weeks ago, but there has been no useful response. https://communities.vmware.com/thread/638457 I have recently looked at the issue with other VM technologies, and found some rather alarming comments on the VirtualBox defect tracking site: https://www.virtualbox.org/ticket/19644 It is not encouraging, when their only solution seems to be to actually patch the Linux Kernel… One of the comments states”…From what I see, the kernel developers have effectively blocked all access to allocation of executable memory other than through the KVM mechanism. ” So… It appears that the current situation, is that both VMware and VirtualBox hosts are incompatible with Kernel 5.8….? I am now reading up on KVM etc, just in case…! Robert Gadsdon. July 19th 2020. Tom -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
participants (4)
-
Carlos E. R. -
jdd＠dodin.org -
Tom -
Tom Wekell