Bug ID 1226122
Summary TW installation leaves /boot empty
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware x86-64
OS Other
Status NEW
Severity Major
Priority P5 - None
Component Installation
Assignee yast2-maintainers@suse.de
Reporter mario_bz@mgtech.com
QA Contact jsrain@suse.com
Target Milestone ---
Found By ---
Blocker ---

Created attachment 875388 [details]
zypp log from installation

Installing TW from June 7 image. I select not to install any boot manager
because I use Refind on Mac. Note I have installed Opensuse and TW this way for
15 years on multiple macs, leaving Grub out. In all cases installation always
worked fine and booted, the last fresh TW install 2 years ago is still good. I
decided to do a clean install of TW to check on other problems I am having.
However, although the kernel is placed in /usr/lib/modules, the/boot directory
is left empty except for the kernel cleanup script. I tried:

1. Copying my working kernel from a TW to /boot and /usr/lib/modules. I was
able to boot that kernel. While booted I did a force installation of the kernel
in YAST, but again, nothing was put into /boot.

2. I reinstalled using both btrf which I normally use, and xfs to see if btrfs
was the issue. No change.

I searched for hours trying to find this issue and found someone had the same
thing after updating, that was a couple of years ago and they just added
symlinks. I my case, I could not do that because initrd modules were missing
which are not symlinks. Since I cant find anyone having this issue recently, I
am assuming it's related to the fact I selected not to install boot manager.

At this point I can't get a new install working. Some people really need to
install without a boot manager, Opensuse and TW made it easy. I assume it's not
a design change since it would make no sense to leave /boot empty.

If you want any logs, please let me know where they are, I could not find an
installation log.

I attached the zypp log I found. It does not have a reference to /boot
anywhere.


You are receiving this mail because: