There's some blocker bugs, read all about it here
https://lists.fedoraproject.org/arch...4L3Q7CKXBC3H5/
There's some blocker bugs, read all about it here
https://lists.fedoraproject.org/arch...4L3Q7CKXBC3H5/
Hello AntiKerbera,
I can confirm: there are lot of problems with Fedora 26, as it appears to be the current state of affairs.
I experienced few of them:
[1] http://www.forums.fedoraforum.org/sh...d.php?t=314337
[2] While upgrading 24 hours ago, I had very hard crash at the very end (while deleting old packages). It came just short (to the end) out of 6 packages to delete, and crashed!
As outcome of this crash [2], the following "feature" emerged from my newly re-installed Fedora 26. As usual, my CLI follows:
In other words: kernel 4.11.2-300.fc26 IS (indeed) INSTALLED, but DOES NOT appear as entry in GRUB2???[user@localhost Video-BIOS-Table-parser-assembler]$ cd /boot
[user@localhost boot]$ pwd
/boot
[user@localhost boot]$ ls -al
total 124864
dr-xr-xr-x. 8 root root 4096 May 26 12:01 .
dr-xr-xr-x. 18 root root 4096 Mar 29 21:20 ..
drwxr-xr-x. 4 root root 4096 May 19 06:16 5a76d41d758649feb94e3abdbfa7157f
-rw-r--r--. 1 root root 185335 May 9 17:42 config-4.11.0-2.fc26.x86_64
-rw-r--r--. 1 root root 185337 May 15 21:46 config-4.11.1-300.fc26.x86_64
drwxr-xr-x. 3 root root 4096 Mar 29 21:23 dbed1a205afe4fd3b60050c0e205222f
drwx------. 4 root root 4096 Mar 29 21:23 efi
-rw-r--r--. 1 root root 184380 Feb 11 06:58 elf-memtest86+-5.01
drwxr-xr-x. 2 root root 4096 Mar 29 21:21 extlinux
drwxr-xr-x. 6 root root 4096 May 26 12:01 grub2
-rw-------. 1 root root 56980221 May 14 19:54 initramfs-0-rescue-5a76d41d758649feb94e3abdbfa7157f.img
-rw-------. 1 root root 20565189 May 14 20:13 initramfs-4.11.0-2.fc26.x86_64.img
-rw-------. 1 root root 20564580 May 19 06:16 initramfs-4.11.1-300.fc26.x86_64.img
drwx------. 2 root root 16384 May 14 19:50 lost+found
-rw-r--r--. 1 root root 182704 Feb 11 06:58 memtest86+-5.01
-rw-------. 1 root root 3548950 May 9 17:42 System.map-4.11.0-2.fc26.x86_64
-rw-------. 1 root root 3549198 May 15 21:46 System.map-4.11.1-300.fc26.x86_64
-rwxr-xr-x. 1 root root 7262808 May 14 19:54 vmlinuz-0-rescue-5a76d41d758649feb94e3abdbfa7157f
-rwxr-xr-x. 1 root root 7282776 May 9 17:43 vmlinuz-4.11.0-2.fc26.x86_64
-rw-r--r--. 1 root root 165 May 9 17:35 .vmlinuz-4.11.0-2.fc26.x86_64.hmac
-rwxr-xr-x. 1 root root 7282776 May 15 21:46 vmlinuz-4.11.1-300.fc26.x86_64
-rw-r--r--. 1 root root 167 May 15 21:40 .vmlinuz-4.11.1-300.fc26.x86_64.hmac
[user@localhost boot]$ uname -a
Linux localhost.localdomain 4.11.1-300.fc26.x86_64 #1 SMP Mon May 15 19:28:32 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
[user@localhost boot]$ cd /usr/src/kernels/
[user@localhost kernels]$ ls -al
total 20
drwxr-xr-x. 5 root root 4096 May 26 11:59 .
drwxr-xr-x. 5 root root 4096 May 15 22:00 ..
drwxr-xr-x. 23 root root 4096 May 15 10:27 4.11.0-2.fc26.x86_64
drwxr-xr-x. 23 root root 4096 May 19 06:15 4.11.1-300.fc26.x86_64
drwxr-xr-x. 23 root root 4096 May 26 11:59 4.11.2-300.fc26.x86_64
[user@localhost kernels]$ cd /lib/modules
[user@localhost modules]$ ls -al
total 20
drwxr-xr-x. 5 root root 4096 May 26 12:01 .
dr-xr-xr-x. 59 root root 4096 May 19 06:15 ..
drwxr-xr-x. 6 root root 4096 May 22 09:37 4.11.0-2.fc26.x86_64
drwxr-xr-x. 6 root root 4096 May 22 13:28 4.11.1-300.fc26.x86_64
drwxr-xr-x. 6 root root 4096 May 26 12:00 4.11.2-300.fc26.x86_64
[user@localhost modules]$ su -m
Password:
[root@localhost modules]# dnf list installed | grep kernel
abrt-addon-kerneloops.x86_64 2.10.2-2.fc26 @updates-testing
kernel.x86_64 4.11.0-2.fc26 @updates-testing
kernel.x86_64 4.11.1-300.fc26 @updates-testing
kernel.x86_64 4.11.2-300.fc26 @updates-testing
kernel-core.x86_64 4.11.0-2.fc26 @updates-testing
kernel-core.x86_64 4.11.1-300.fc26 @updates-testing
kernel-core.x86_64 4.11.2-300.fc26 @System
kernel-devel.x86_64 4.11.0-2.fc26 @updates-testing
kernel-devel.x86_64 4.11.1-300.fc26 @updates-testing
kernel-devel.x86_64 4.11.2-300.fc26 @System
kernel-headers.x86_64 4.11.2-300.fc26 @System
kernel-modules.x86_64 4.11.0-2.fc26 @updates-testing
kernel-modules.x86_64 4.11.1-300.fc26 @updates-testing
kernel-modules.x86_64 4.11.2-300.fc26 @System
kernel-modules-extra.x86_64 4.11.0-2.fc26 @updates-testing
kernel-modules-extra.x86_64 4.11.1-300.fc26 @updates-testing
kernel-modules-extra.x86_64 4.11.2-300.fc26 @System
libreport-plugin-kerneloops.x86_64 2.9.1-2.fc26 @updates-testing
[root@localhost modules]#
_nobody_
Verify that you have grubby and systemd-udev installed.
Yes, I do.[root@localhost kernels]# dnf install grubby systemd-udev
Last metadata expiration check: 1:49:27 ago on Sat May 27 09:39:36 2017 CEST.
Package grubby-8.40-4.fc26.x86_64 is already installed, skipping.
Package systemd-udev-233-3.fc26.x86_64 is already installed, skipping.
Dependencies resolved.
Nothing to do.
Complete!
[root@localhost kernels]#
_nobody_
You know who does not have his new kernel updated? Nobody![]()
Verify that you have indeed a new kernel in /boot, and also look for grub2 configuration file. new-kernel-pkg determines which file to upgrade based on a link in /etc .
Code:$ file /etc/grub2{,-efi}.cfg
Well... Nobody is perfect, and I am a _nobody_, thus/therefore I am absolutely _PERFECT_!
I did upgrade few hours ago, after posting to you previous message. Here it is:
I am VERY lazy to back-track it, srak... But I made note/flag in my brain. Really, I did![root@localhost kernels]# dnf list installed | grep kernel
abrt-addon-kerneloops.x86_64 2.10.2-2.fc26 @updates-testing
kernel.x86_64 4.11.1-300.fc26 @updates-testing
kernel.x86_64 4.11.2-300.fc26 @updates-testing
kernel.x86_64 4.11.3-300.fc26 @updates-testing
kernel-core.x86_64 4.11.1-300.fc26 @updates-testing
kernel-core.x86_64 4.11.2-300.fc26 @System
kernel-core.x86_64 4.11.3-300.fc26 @updates-testing
kernel-devel.x86_64 4.11.1-300.fc26 @updates-testing
kernel-devel.x86_64 4.11.2-300.fc26 @System
kernel-devel.x86_64 4.11.3-300.fc26 @updates-testing
kernel-headers.x86_64 4.11.3-300.fc26 @updates-testing
kernel-modules.x86_64 4.11.1-300.fc26 @updates-testing
kernel-modules.x86_64 4.11.2-300.fc26 @System
kernel-modules.x86_64 4.11.3-300.fc26 @updates-testing
kernel-modules-extra.x86_64 4.11.1-300.fc26 @updates-testing
kernel-modules-extra.x86_64 4.11.2-300.fc26 @System
kernel-modules-extra.x86_64 4.11.3-300.fc26 @updates-testing
libreport-plugin-kerneloops.x86_64 2.9.1-2.fc26 @updates-testing
[root@localhost kernels]# uname -a
Linux localhost.localdomain 4.11.3-300.fc26.x86_64 #1 SMP Thu May 25 18:43:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
[root@localhost kernels]#
_nobody_
Hello srak (& AntiKerbera),
Now I have more evidences to report, as I have promised. After installing the new kernel.
Here is whai I do have in my /etc/dnf/dnf.conf :
So, I have default configuration of last 3 kernels to keep.Originally Posted by /etc/dnf/dnf.conf
Here is what I have in /boot:
I have currently latest two of them in /boot (with rescue one):Originally Posted by /boot
4.11.3-302.fc26.x86_64
4.11.3-300.fc26.x86_64
The system de-installed my 4.11.1-300.fc26.x86_64 kernel, the very first kernel I had with Fedora 26 from scratch (few weeks ago).
This was the third one from behind (oldest of 3), and it seems that system SOMEWHERE (NOT in grub.cfg) keeps track of these kernels, since the one in the middle (4.11.2-300.fc26.x86_64) was installed as bogus one and NEVER showed in neither /boot, neither grub.cfg???
So, I am facing very irregular situation: last 3 kernels kept are:
4.11.3-302.fc26.x86_64
4.11.3-300.fc26.x86_64
4.11.2-300.fc26.x86_64<<=== INVISIBLE (some entity keeps track of it)???
4.11.1-300.fc26.x86_64 <<=== DEINSTALLED!
In other words, I have still ONLY two kernels in GRUB2 menu!
The question is: which kernel entity keeps last three kernels (not /boot, not grub.cfg)???
Thank you,
_nobody_
Beta 1-4 is the beta to be released.
@Nobody have problems with kernels. Maybe rpm database. Did you look at what you have installed according to dnf/rpm? dnf in the end decides what kernels to keep and what to erase according to its setting.
P.S. You can't just delete files manually to remove a kernel you need to use a package manager![]()
https://bugzilla.redhat.com/show_bug.cgi?id=1446782
SDDM issue will be fixed soon, so that's 2 blockers down(?)...
Fedora 26 LXQt here we come!
https://github,com/truboxl
Jesus Christ, U R right!
Let me investigate further!Code:[root@localhost log]# dnf list installed | grep kernel abrt-addon-kerneloops.x86_64 2.10.2-2.fc26 @updates-testing kernel.x86_64 4.11.2-300.fc26 @updates-testing kernel.x86_64 4.11.3-300.fc26 @updates-testing kernel.x86_64 4.11.3-302.fc26 @updates-testing kernel-core.x86_64 4.11.2-300.fc26 @System kernel-core.x86_64 4.11.3-300.fc26 @updates-testing kernel-core.x86_64 4.11.3-302.fc26 @updates-testing kernel-devel.x86_64 4.11.2-300.fc26 @System kernel-devel.x86_64 4.11.3-300.fc26 @updates-testing kernel-devel.x86_64 4.11.3-302.fc26 @updates-testing kernel-headers.x86_64 4.11.3-302.fc26 @updates-testing kernel-modules.x86_64 4.11.2-300.fc26 @System kernel-modules.x86_64 4.11.3-300.fc26 @updates-testing kernel-modules.x86_64 4.11.3-302.fc26 @updates-testing kernel-modules-extra.x86_64 4.11.2-300.fc26 @System kernel-modules-extra.x86_64 4.11.3-300.fc26 @updates-testing kernel-modules-extra.x86_64 4.11.3-302.fc26 @updates-testing libreport-plugin-kerneloops.x86_64 2.9.1-2.fc26 @updates-testing [root@localhost log]#![]()
_______
After manually removing all the packages from the kernel 4.11.2-300.fc26.x86_64, I have the following:
Well, the last trick I need to discover: where is, the heck, kept local rmp database (which is, obvious to me, in some compressed format), which directory, and which file it is?Code:[root@localhost /]# dnf list installed | grep kernel abrt-addon-kerneloops.x86_64 2.10.2-2.fc26 @updates-testing kernel.x86_64 4.11.3-300.fc26 @updates-testing kernel.x86_64 4.11.3-302.fc26 @updates-testing kernel-core.x86_64 4.11.3-300.fc26 @updates-testing kernel-core.x86_64 4.11.3-302.fc26 @updates-testing kernel-devel.x86_64 4.11.3-300.fc26 @updates-testing kernel-devel.x86_64 4.11.3-302.fc26 @updates-testing kernel-headers.x86_64 4.11.3-302.fc26 @updates-testing kernel-modules.x86_64 4.11.3-300.fc26 @updates-testing kernel-modules.x86_64 4.11.3-302.fc26 @updates-testing kernel-modules-extra.x86_64 4.11.3-300.fc26 @updates-testing kernel-modules-extra.x86_64 4.11.3-302.fc26 @updates-testing libreport-plugin-kerneloops.x86_64 2.9.1-2.fc26 @updates-testing [root@localhost /]# rpm -qa | grep kernel kernel-core-4.11.3-302.fc26.x86_64 kernel-devel-4.11.3-300.fc26.x86_64 kernel-4.11.3-302.fc26.x86_64 kernel-headers-4.11.3-302.fc26.x86_64 libreport-plugin-kerneloops-2.9.1-2.fc26.x86_64 kernel-4.11.3-300.fc26.x86_64 kernel-modules-extra-4.11.3-300.fc26.x86_64 kernel-modules-extra-4.11.3-302.fc26.x86_64 kernel-core-4.11.3-300.fc26.x86_64 kernel-modules-4.11.3-300.fc26.x86_64 kernel-devel-4.11.3-302.fc26.x86_64 abrt-addon-kerneloops-2.10.2-2.fc26.x86_64 kernel-modules-4.11.3-302.fc26.x86_64 [root@localhost /]#
_______
Ahhhh... Here we go!
_nobody_[root@localhost yum]# ls /var/lib/rpm
Basenames __db.002 Enhancename Installtid Packages Requirename Suggestname Triggername
Conflictname __db.003 Filetriggername Name Providename Sha1header Supplementname
__db.001 Dirnames Group Obsoletename Recommendname Sigmd5 Transfiletriggername
[root@localhost yum]# ls -al /var/lib/rpm
total 136616
drwxr-xr-x. 2 root root 4096 Jun 7 23:52 .
drwxr-xr-x. 70 root root 4096 May 16 06:44 ..
-rw-r--r--. 1 root root 12431360 Jun 9 19:08 Basenames
-rw-r--r--. 1 root root 16384 Jun 9 19:07 Conflictname
-rw-r--r--. 1 root root 311296 Jun 9 19:08 __db.001
-rw-r--r--. 1 root root 90112 Jun 9 19:08 __db.002
-rw-r--r--. 1 root root 1318912 Jun 9 19:08 __db.003
-rw-r--r--. 1 root root 0 Mar 29 21:20 .dbenv.lock
-rw-r--r--. 1 root root 6520832 Jun 9 19:08 Dirnames
-rw-r--r--. 1 root root 8192 Mar 29 21:20 Enhancename
-rw-r--r--. 1 root root 8192 May 14 20:12 Filetriggername
-rw-r--r--. 1 root root 40960 Jun 9 19:08 Group
-rw-r--r--. 1 root root 53248 Jun 9 19:08 Installtid
-rw-r--r--. 1 root root 135168 Jun 9 19:08 Name
-rw-r--r--. 1 root root 49152 Jun 7 06:26 Obsoletename
-rw-r--r--. 1 root root 115847168 Jun 9 19:08 Packages
-rw-r--r--. 1 root root 1863680 Jun 9 19:08 Providename
-rw-r--r--. 1 root root 8192 Jun 7 06:26 Recommendname
-rw-r--r--. 1 root root 888832 Jun 9 19:08 Requirename
-rw-r--r--. 1 root root 0 Mar 29 21:20 .rpm.lock
-rw-r--r--. 1 root root 229376 Jun 9 19:08 Sha1header
-rw-r--r--. 1 root root 143360 Jun 9 19:08 Sigmd5
-rw-r--r--. 1 root root 8192 Jun 7 06:26 Suggestname
-rw-r--r--. 1 root root 8192 Jun 7 06:26 Supplementname
-rw-r--r--. 1 root root 8192 May 26 12:01 Transfiletriggername
-rw-r--r--. 1 root root 16384 Jun 5 11:56 Triggername
[root@localhost yum]#
Last edited by nobody; 9th June 2017 at 06:29 PM. Reason: Additional quick and dirty investigation ran by _nobody_!?
I can tell, today is Beta D Day, but me being Linus, Linux, Unix... I would postpone Fedora 26 beta release to 2017-07-04. At minimum!Code:2017-05-09 2017-05-16 2017-05-23 2017-05-30 2017-06-062017-06-13 Beta Release
_nobody_
What's all the fuss? Work it. Use it. Enjoy it. If its broken fix it.