I have TLP installed to extend battery life. I have a Lenovo T440s and I have Fedora 26 installed. When I run TLP it recommends the installation of the acpi-call kernel. When I follow directions here it "works" until the final step(s) of: dnf install akmod-tp_smapi akmod-acpi_call kernel-devel. At which point I get the errors:
No package akmod-tp_smapi available.
No package akmod-acpi_call available.
Per , I was seeing tons of audit messages listed in logwatch reports.
(My patch fixes that, btw.) My actual question is why I wasn't seeing
those messages in my old (old) F20 logwatch reports, but did see:
--------------------- Kernel Audit Begin ------------------------
instead. Is this your experience, that some upgrade started giving
tons of audit messages?
I think that previously, when logwatch looked at the logfiles, it was
misconfigured to not use /var/log/audit/audit.log, but instead:
LogFile = modsecurity2/modsec_audit.log
and what I saw came from /var/log/messages (not sure why). Now
logwatch looks at the journal (that's the format of the lines I see)
and is actually able to report audit issues.
I was just wondering. Are there any plans on having an upstream project for Redhat Satellite 6? Or even satellite 7?
I mean, if you want to practice and test new features the only real option I've found that you have is putting together the components of 6 or running spacewalk. But that isn't what I'm looking for, I think.
Any other related tips would of course be appreciated as well.
Online Fedora documentation seems to be intentionally broken. The site
has been redesigned and all links fail. Every link redirects to the site
main page and the main page does not include any search function.
Specifically, the RPM guide (a document which has been in "draft" status
for a long time but is extremely useful nonetheless), is nowhere to be
found. It was at
"Age is a very high price to pay for maturity." -- Tom Stoppard
For anyone else with the misfortune to have a laptop with the RTL8723BE
wifi chipset, be cautious about upgrading the kernel to 4.12 or later.
It might still work if you use antenna 2, but I can't verify that. In
my case with ant_sel=1, the wifi can't see anything with the 4.12 kernel
I've filed https://bugzilla.redhat.com/show_bug.cgi?id=1486463 if anyone
else wants to follow it. There was a patch related to ant_sel not
working that was applied to 4.13, but it was reverted due to a null
system is Fedora 26, all current updates
I'm running raid1, two identical 500GB disks partitioned as follows:
/dev/sda1 2048 789501951 789499904 376.5G fd Linux raid
/dev/sda2 789501952 948973567 159471616 76G fd Linux raid
/dev/sda3 948973568 975749119 26775552 12.8G fd Linux raid
/dev/sda4 975749120 976773119 1024000 500M 5 Extended
/dev/sda5 * 975751168 976773119 1021952 499M fd Linux raid
Personalities : [raid1]
md124 : active raid1 sdb1 sda1
394617856 blocks super 1.2 [2/2] [UU]
bitmap: 0/3 pages [0KB], 65536KB chunk
md125 : active raid1 sda5 sdb5
510656 blocks super 1.2 [2/2] [UU]
bitmap: 0/1 pages [0KB], 65536KB chunk
md126 : active raid1 sda2 sdb2
79670272 blocks super 1.2 [2/2] [UU]
bitmap: 1/1 pages [4KB], 65536KB chunk
md127 : active (auto-read-only) raid1 sda3 sdb3
13379584 blocks super 1.2 [2/2] [UU]
unused devices: <none>
/dev/md126 79631372 5608820 74022552 8% /
/dev/md124 388294468 23798252 344748940 7% /home
/dev/md125 486308 283858 172822 63% /boot
md127 is swap
I get the following error in logwatch:
mdadm: cannot open /dev/md/boot: No such file or directory
mdadm: cannot open /dev/md/root: No such file or directory
mdadm: cannot open /dev/md/swap: No such file or directory
and I see that /dev/md contains the following:
# ls -l /dev/md
lrwxrwxrwx 1 root root 8 Aug 24 16:14 home -> ../md124
lrwxrwxrwx 1 root root 8 Aug 24 16:14 xyzzy2.bubble.org:boot -> ../md125
lrwxrwxrwx 1 root root 8 Aug 24 16:14 xyzzy2.bubble.org:root -> ../md126
lrwxrwxrwx 1 root root 8 Aug 24 16:14 xyzzy2.bubble.org:swap -> ../md127
the entries in /etc/mdadm.conf are:
AUTO +imsm +1.x -all
ARRAY /dev/md/boot level=raid1 num-devices=2
ARRAY /dev/md/home level=raid1 num-devices=2
ARRAY /dev/md/root level=raid1 num-devices=2
ARRAY /dev/md/swap level=raid1 num-devices=2
I have verified that the UUID numbers do match the respective volume names.
so obviously the reason for the error is boot, root, and swap don't
exist, if I create a symbolic links the error will go away until the
next reboot. The question is what triggers making the symbolic links at
boot time, is it /etc/mdadm.conf and do I simply rebuild it? and how can
I change them from the hostname to be root, boot, and swap or change the
mdadm command to look for the hostname entry?
If I run "mdadm --detail --scan" I get the following;
ARRAY /dev/md/xyzzy2.bubble.org:swap metadata=1.2
ARRAY /dev/md/xyzzy2.bubble.org:root metadata=1.2
ARRAY /dev/md/xyzzy2.bubble.org:boot metadata=1.2
ARRAY /dev/md/home metadata=1.2 name=xyzzy2.bubble.org:home
the array names are changed to match what is actually in /dev/md,
however before I change the entries in mdadm.conf I want to make sure
I'm not going to cause myself grief and have to log directly on the
console of the system which is about 30 min and a phone call or two away.
I just ran a dnf update on my fedora 26 box and the build
and install of the nvidia akmod failed:
2017/08/28 07:28:04 akmods: Installing newly built rpms
2017/08/28 07:28:04 akmods: DNF detected
error: db5 error(-30969) from dbenv->open: BDB0091 DB_VERSION_MISMATCH: Database environment version mismatch
error: cannot open Packages index using db5 - (-30969)
error: cannot open Packages database in /var/lib/rpm
Error: Error: rpmdb open failed
2017/08/28 07:28:04 akmods: Could not install newly built RPMs. You can find them and the logfile
2017/08/28 07:28:04 akmods: 375.66-3-for-4.12.8-300.fc26.x86_64.failed.log in /var/cache/akmods/nvidia/
After getting the system back up, I manually
installed the rpm it built via dnf install and
it seemed to install fine.
What the heck happened during the initial dnf update?
I tried to upgrade one of my systems to F26 according to the
I did the download and everything went fine. I then did
sudo dnf system-upgrade reboot
and here is where things went weird, there was no output at all on the
monitor. The disk light was flashing, so something was going on, but
nothing showed up on the monitor. After a while the disk light stopped
flashing, and I assumed it was time to reboot. I rebooted, but nothing
happened, the system did not boot. I tried several times with the same
result. That was yesterday. Today I downloaded the F26 Workstation
DVD, burned to a disk and placed it in the DVD drive of the what
appeared to be a dead system. This time the system booted, but there
was no F26 kernel, only F25 kernels. However, there are f26 packages
installed. I was going to redo the download and upgrade, but when I run
dnf I get this:
[pgaltieri@caseyjones ~]$ dnf
Traceback (most recent call last):
File "/usr/bin/dnf", line 57, in <module>
from dnf.cli import main
ModuleNotFoundError: No module named 'dnf'
Anyone know what I need to do to fix this system? There are 2 other
systems I want to upgrade, but after this experience I'm hesitant to go
ahead with the others. This system is my test system so there's nothing
important on it.
Any help is appreciated.
Over the last week I have observed several problems with how F25 runs on
Issue 1: The system does not suspend on lid closed. I have an external
monitor attached to it and I can continue working on the system despite
the lid being closed. When I run gnome-tweak-tool and indicates the
system should suspend on lid closed. I have attached the png image of
the gnome-tweak-tool screen.
Issue 2: Back in the F24 days and even prior to that I filed a bug
(1389019) which states that when I boot my laptop on battery and login
the power status applet is not displayed in the MATE top menu bar. It
does show up when I plug the AC cord in. This problem has now gotten
worse. The power applet is no longer displayed regardless of what I
try. I have had to re-open this bug since it was without it ever being
Issue 3: I run the MATE desktop and so I also run the
mate-screensaver. This is configured to display pictures from my
Pictures directory. Under the the "Power Management" screen it is
configured to suspend on lid closed and to put the display to sleep
after 5 minutes. After 5 minutes the display is not put to sleep, the
pictures from the Pictures directory continue to be displayed.
Issue 4: If I close the lid prior to the screen saver kicking in, wait
a minute and then lift the lid my session resumes without being asked to
enter a password. This to me is a serious security issue.
I have installed updates as of 8/15/2017
None of these issues existed a couple of months ago, except for maybe
the suspend issue. It has been a recurring problem getting the system
to suspend on lid closed. Sometimes it works other times it doesn't and
I've made no changes :-(
Has anyone else seen these issues?
As a side note why is there no equivalent to gnome-tweak-tool for the
MATE desktop? When I run gnome-tweak-tool under MATE I get these errors:
[pgaltieri@terrapin ~]$ gnome-tweak-tool
WARNING : Shell not installed or running
WARNING : Shell not running
WARNING : Error detecting shell
Traceback (most recent call last):
line 275, in __init__
raise Exception("Shell not running or DBus service not available")
Exception: Shell not running or DBus service not available
Of these issues Issue 2 is probably the most critical. If I'm running
on battery I want to see how much time I have left before the battery
power is consumed. I know I can use the upower command to find this
out, but that is not a satisfactory solution.
Any help is appreciated.