Mailinglist Archive: opensuse-bugs (6630 mails)

< Previous Next >
[Bug 527312] preload-kmp: FATAL: Could not open '/boot/': No such file or directory
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Thu, 13 Aug 2009 01:07:52 -0600
  • Message-id: <20090813070752.CE1C9CC7CD@xxxxxxxxxxxxxxxxxxxxxx>

User mmarek@xxxxxxxxxx added comment

Michal Marek <mmarek@xxxxxxxxxx> changed:

What |Removed |Added

--- Comment #6 from Michal Marek <mmarek@xxxxxxxxxx> 2009-08-13 01:07:51 MDT
(In reply to comment #5)
Conspiracy theory 1: is it possible this happens in case the running
kernel is different from the installed kernel (i.e., when as part of
the same zypper dup run we previously updated the kernel)?

Running kernel does not matter, the only uname call in the script is when you
run it with --add-kernel without an argument (maybe I should remove this).

Conspiracy theory 2: Or when there are several kernels installed?

Also should not matter and during each kernel update there are two kernels at
some point.

Conspiracy theory 3: Or when I have a symlink within /lib/modules
(which I _think_ was not the case here, but...)

Some havoc in /lib/modules might be the cause here, yes, but if you look at the
add_kmp() function, it only proceeds with given kernel release if there exists
/lib/modules/$krel and /boot/$krel. My private theory is some
scripting error that overwrites the $krel variable, but then it should fail
more deterministically. IOW I'm clueless here :-).

Should you hit it once more, please run
bash -x /usr/lib/module-init-tools/weak-modules2 --add-kmp $kmp

where $kmp is the name-version-release of the affected kmp. I'll also ask on
opensuse-factory if anyone has seen it.

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >