Felix Miata composed on 2022-08-02 18:35 (UTC-0400):
> Adam Williamson composed on 2022-08-02 14:10 (UTC-0700):
>> On Tue, 2022-08-02 at 15:20 -0400, Felix Miata wrote:
>>> Adam Williamson composed on 2022-08-02 11:23 (UTC-0700):
>>>> On Mon, 2022-08-01 at 11:02 -0400, Felix Miata wrote:
>>>>> Is this normal procedure now in rawhide?
>>>>> I copied vmlinuz directly from the rpm to /boot/ and renamed it
>>>>> vmlinuz-5.19.0-0.rc8.20220729git6e2c0490769e.62.fc37.x86_64,
>>>>> though I could have symlinked its location in the /lib/modules tree. It
>>>>> works.
>>>> kernel is a metapackage that doesn't contain any files, the actual main
>>>> parts of the kernel are in kernel-core. Is that what you meant?
>>> I haven't installed "kernel" in over a year. I haven't been able to
>>> determine any purpose it serves that is actually needed. What I ran was:
>>> time rpm -ivh
>>> kernel-core-5.19.0-0.rc8.20220729git6e2c0490769e.62.fc37.x86_64
>>> kernel-modules-5.19.0-0.rc8.20220729git6e2c0490769e.62.fc37.x86_64
>> OK. Well, it should have wound up putting the file in place, I think. I
>> think it's not directly installed, but put in place by the %posttrans
>> script, which does this (from the current package):
>> rm -f /var/lib/rpm-state/kernel/installing_core_5.19.0-65.fc37.x86_64
>> /bin/kernel-install add 5.19.0-65.fc37.x86_64
>> /lib/modules/5.19.0-65.fc37.x86_64/vmlinuz || exit $?
>> did you get any scriptlet failures or anything?
> I don't remember seeing anything to indicate failure at the time. String
> vmlinuz
> does not appear in /var/log/messages from yesterday, or in last 6 iterations
> of
> journal. :p
Looks like my internal RAM failed. Different MBR host (fi965), newer kernel,
same errant behavior, but error messages did result:
# time rpm -ivh kernel-core-5.19.0-65.fc37.x86_64.rpm
kernel-modules-5.19.0-65.fc37.x86_64.rpm
Verifying... ################################# [100%]
Preparing... ################################# [100%]
Updating / installing...
1:kernel-core-5.19.0-65.fc37 ################################# [ 50%]
2:kernel-modules-5.19.0-65.fc37 ################################# [100%]
cp: cannot stat '/lib/modules/5.19.0-65.fc37.x86_64/bls.conf': No such file or
directory
sed: can't read
/boot/loader/entries/11352b14084942c18a21a5586db0b5b3-0-rescue.conf: No such
file or directory
warning: %posttrans(kernel-core-5.19.0-65.fc37.x86_64) scriptlet failed, exit
status 2
real 2m45.397s
user 2m25.506s
sys 0m26.617s
# ls -Gg /boot/*5.19*
-rw------- 1 15292124 Aug 3 03:57 /boot/initramfs-5.19.0-65.fc37.x86_64.img
<copy vmlinuz from /usr/lib/ tree; rename appropriately>
# ls -Gg /boot/*5.1*
-rw------- 1 6256078 Jul 22 10:21 /boot/System.map-5.18.13-200.fc36.x86_64
-rw-r--r-- 1 247453 Jul 22 10:21 /boot/config-5.18.13-200.fc36.x86_64
-rw------- 1 17206976 Aug 3 02:51 /boot/initramfs-5.18.13-200.fc36.x86_64.img
-rw------- 1 15292124 Aug 3 03:57 /boot/initramfs-5.19.0-65.fc37.x86_64.img
-rwxr-xr-x 1 12187888 Jul 22 10:21 /boot/vmlinuz-5.18.13-200.fc36.x86_64
-rwxr-xr-x 1 12261008 Aug 1 09:52 /boot/vmlinuz-5.19.0-65.fc37.x86_64
# efibootmgr
-bash: efibootmgr: command not found
#
So $SUMMARY isn't quite on target. Kernel installation with rpm only puts
an initrd in /boot/.
As before, with my manual adjusting done, 5.19 is working as expected.
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
_______________________________________________
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
