10:02 a.m.
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.
--
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
1:23 p.m.
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?
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
2:20 p.m.
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 do
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
--
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
4:10 p.m.
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 do
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?
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
5:35 p.m.
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
--
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
3:20 a.m.
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
12:46 p.m.
On Wed, 2022-08-03 at 04:20 -0400, Felix Miata wrote:
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.
So basically kernel-install is failing on your system for some reason.
We'd have to pick through all its logic to figure out why. I've done
this several times before and can probably take a look and try to guess
some possible causes on Monday.
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
3:06 a.m.
New subject: rpm -ivh kernel installation put no vmlinuz* in /boot/ WFM
Felix Miata composed on 2022-08-03 04:20 (UTC-0400):
# 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
Repeated on another host. Error messages differed, and so did end result - no
unexpected absences in /boot. Errors were about depmod unknown sound symbols:
...kunit_do_failed_assertion
...__kunit_test_suites_exit
...__kunit_test_suites_init
...kunit_binary_assert_format
As before, with my manual adjusting done, 5.19 is working as
expected.
No need to adjust /boot this time.
I have more PCs left on which to upgrade a 36 to 37 if more need for this thread.
--
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
1:41 a.m.
New subject: rpm -ivh kernel installation put no vmlinuz* in /boot/ WFM-not
Felix Miata composed on 2022-08-07 04:06 (UTC-0400):
Felix Miata composed on 2022-08-03 04:20 (UTC-0400):
> # 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
...
> As before, with my manual adjusting done, 5.19 is working as
expected.
...
I have more PCs left on which to upgrade a 36 to 37 if more need for
this thread.
Another fresh system-upgrade from 36 to 37 resulted in no new kernel in /boot/,
just like in the OP, on yet another host:
# inxi -SMC --vs
inxi 3.3.20-00 (2022-07-27)
System:
Host: ara88 Kernel: 5.19.0-65.fc37.x86_64 arch: x86_64 bits: 64
Console: pty pts/0 Distro: Fedora release 37 (Thirty Seven)
Machine:
Type: Desktop Mobo: ASRock model: FM2A88X Extreme6+ serial: E80-38024200616
UEFI: American Megatrends v: P4.20 date: 01/13/2016
CPU:
Info: quad core model: AMD A10-7850K Radeon R7 12 Compute Cores 4C+8G
bits: 64 type: MT MCP cache: L2: 4 MiB
Speed (MHz): avg: 1700 min/max: 1700/3700 cores: 1: 1700 2: 1700 3: 1700
4: 1700
--
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
11:44 a.m.
Felix Miata composed on 2022-08-12 02:41 (UTC-0400):
Felix Miata composed on 2022-08-07 04:06 (UTC-0400):
> Felix Miata composed on 2022-08-03 04:20 (UTC-0400):
>> # 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
...
>> As before, with my manual adjusting done, 5.19 is working as expected.
...
> I have more PCs left on which to upgrade a 36 to 37 if more need for this thread.
Another fresh system-upgrade from 36 to 37 resulted in no new kernel
in /boot/,
just like in the OP, on yet another host:
# inxi -SMC --vs
inxi 3.3.20-00 (2022-07-27)
System:
Host: ara88 Kernel: 5.19.0-65.fc37.x86_64 arch: x86_64 bits: 64
Console: pty pts/0 Distro: Fedora release 37 (Thirty Seven)
Machine:
Type: Desktop Mobo: ASRock model: FM2A88X Extreme6+ serial: E80-38024200616
UEFI: American Megatrends v: P4.20 date: 01/13/2016
CPU:
Info: quad core model: AMD A10-7850K Radeon R7 12 Compute Cores 4C+8G
bits: 64 type: MT MCP cache: L2: 4 MiB
Speed (MHz): avg: 1700 min/max: 1700/3700 cores: 1: 1700 2: 1700 3: 1700
4: 1700
And another:
# inxi -SMC --vs
inxi 3.3.20-00 (2022-07-27)
System:
Host: ab85m Kernel: 5.19.0-65.fc37.x86_64 arch: x86_64 bits: 64
Desktop: KDE Plasma v: 5.25.4 Distro: Fedora release 37 (Thirty Seven)
Machine:
Type: Desktop System: ASUS product: All Series v: N/A serial: N/A
Mobo: ASUSTeK model: B85M-E v: Rev X.0x serial: MB-1234567890
UEFI: American Megatrends v: 3602 date: 04/04/2018
CPU:
Info: dual core model: Intel Pentium G3220 bits: 64 type: MCP cache:
L2: 512 KiB
Speed (MHz): avg: 952 min/max: 800/3000 cores: 1: 1104 2: 800
rpm kernel installation doesn't put anything in /boot/ except for initramfs:
# ls -gG /boot/*5.19*
-rw------- 1 21049097 Aug 19 12:28 /boot/initramfs-5.19.0-65.fc37.x86_64.img
-rwxr-xr-x 1 12261008 Aug 1 09:52 /boot/vmlinuz-5.19.0-65.fc37.x86_64
--
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
677
days inactive
695
days old
9 comments
2 participants
participants (2)
-
Adam Williamson -
Felix Miata