Comment # 21 on bug 1226122 from Mario Guzman
I finally got it to boot but there is obviously something missing in the
installation that leaves /boot empty. Just a guess, but I think it's related to
a missing suse-module-tools-scriptlets. I looked at Yast and found
system-modules-tools is installed but not system-module-tools-scriplets.

I needed your dracut command to create the initrd. I thought it would create
all /boot modules but it only creates one file per kernel. None of the
symlinks.

In the logs above I noticed the my manually added links from /boot to
/usr/lib/modules were wrong. These symlinks were the ones I manually added
since the install left /boot empty. Once I fixed them, along with the new
dracut generated file, it booted.

What I am concerned about  is if a kernel update will process correctly. I
don't think so because it would not create one when I did a force update in
Yast.

Let me know what you would like next. Thank you.


You are receiving this mail because: