Kernel Modules: <not available>
Could not find map /boot/System.map, please specify a correct file with -M.
There was an error generating the initrd (9)
I’m scared to reboot my laptop. Is there anything I can try to repair?
The following package is going to be upgraded:
kernel-desktop
1 package to upgrade.
Overall download size: 40.4 MiB. After the operation, additional 3.2 KiB will be used.
Continue? [y/n/?] (y): y
Retrieving package kernel-desktop-3.6.6-1.1.x86_64 (1/1), 40.4 MiB (153.7 MiB unpacked)
Retrieving: kernel-desktop-3.6.6-1.1.x86_64.rpm ...........................[done (609.8 KiB/s)]
Installing: kernel-desktop-3.6.6-1.1 ....................................................[done]
Additional rpm output:
Kernel image: /boot/vmlinuz-3.6.6-1-desktop
Initrd image: /boot/initrd-3.6.6-1-desktop
Kernel Modules: <not available>
Could not find map /boot/System.map, please specify a correct file with -M.
There was an error generating the initrd (9)
Yes, you can compile and install a new kernel using SAKC and it does not mess with any kernels installed using YaST. I would surely give SAKC a try and then Grub 2 should have more than one kernel to select from. You could also install my Grub 2 utility before you try to reboot to actually look at your grub 2 menu:
Did you update mkinitrd from Kernel:stable? It does not work on 12.2 and below due to changed path to /sbin/get_kernel_version. As workaround use “ln -s /sbin/get_kernel_version /usr/bin”
> New update this morning for mkinitrd has solved my issue.
Nice to hear but still again the question is why they call this repo
stable. From my view it would more honest to change the name because
the stable times be a little bit away.
IMHO its no more unstable than other repo’s with the kernel updates in.
It all depends upon when you decide to update in the update cycle.
I was forced to wait a few days for all packages to be available before
updating from kernel-desktop-3.6.4-1.1.x86_64 to kernel-desktop-3.6.6-1.1.x86_64
The wait was worth it.
For my hardware kernel-desktop-3.6.4-9.1.x86_64 was a problem.
On Thu, 08 Nov 2012 18:30:24 GMT “dd” <dd@home.dk> wrote:
> how about “Intending to be stable, but humans make mistakes repo.”
No problem with mistakes and i’m thankfull for the work of the package
maintainer. But a mkinitrd which works not with <=12.2 is more a
untested version and i speak only for i686 where from my view the
intension to be stable is not so high.
Am 09.11.2012 06:41, schrieb Ferenginar:
> On Thu, 08 Nov 2012 18:30:24 GMT “dd” <dd@home.dk> wrote:
>
>> how about “Intending to be stable, but humans make mistakes repo.”
>
> No problem with mistakes and i’m thankfull for the work of the package
> maintainer. But a mkinitrd which works not with <=12.2 is more a
> untested version and i speak only for i686 where from my view the
> intension to be stable is not so high.
>
Maybe I am way off here, but as I understand the namings in that factory
repositories, kernel:stable refers to the latest stable version of the
kernel not that the repository content as such is stable.
–
PC: oS 12.2 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.8.5 | GeForce GT 420
ThinkPad E320: oS 12.2 x86_64 | i3@2.30GHz | 8GB | KDE 4.9.3 | HD 3000
eCAFE 800: oS 11.4 i586 | AMD Geode LX 800@500MHz | 512MB | lamp server
On Fri, 09 Nov 2012 13:48:11 GMT Martin Helm wrote:
> Maybe I am way off here, but as I understand the namings in that
> factory repositories, kernel:stable refers to the latest stable
> version of the kernel not that the repository content as such is
> stable.
Okay than all is fine because we have found the reason for the name
