Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I recently began seeing a raft of error messages when booting, although there is nothing apparently wrong
during normal operation that I can detect.
/var/log/boot.log has the following four lines near the beginning:
OK Started Braille Device Support.
Starting Apply Kernel Variables...
FAILED Failed to start Apply Kernel Variables.
See 'systemctl status systemd-sysctl.service' for details.
Running systemctl status systemd-sysctl.service gives the following (some fluff deleted):
● systemd-sysctl.service - Apply Kernel Variables
Loaded: loaded (/lib/systemd/system/systemd-sysctl.service; static; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2016-10-04 08:17:52 CDT; 2h 21min ago
Process: 544 ExecStart=/lib/systemd/systemd-sysctl (code=exited, status=1/FAILURE)
Main PID: 544 (code=exited, status=1/FAILURE)
08:17:52 systemd: Starting Apply Kernel Variables...
08:17:52 systemd: systemd-sysctl.service: Main process exited, code=exited, status=1/FAILURE
08:17:52 systemd: Failed to start Apply Kernel Variables.
08:17:52 systemd: systemd-sysctl.service: Unit entered failed state.
08:17:52 systemd: systemd-sysctl.service: Failed with result 'exit-code'.
1) Does the "Starting Apply Kernel Variables..." message have anything to do with the "Braille
Device Support" in the line above? Or is that just coincidence? For the record, I was unaware
that I had any support for Braille devices and don't need them, so:
2) Should I take any steps to find and eliminate Braille device support?
3) The information resulting from the "systemctl status systemd-sysctl.service" command means
absolutely nothing to me. The only thing I'm aware of that I use which needs to load kernel
module(s) is VirtualBox, and that seems to be working just fine.
4) /var/log/kern.log has the following lines that I would like to understand (some fluff deleted):
08:17:54 kernel: [ 0.000000] AGP: Your BIOS doesn't leave an aperture memory hole
08:17:54 kernel: [ 0.000000] AGP: Please enable the IOMMU option in the BIOS setup
08:17:54 kernel: [ 0.000000] AGP: This costs you 64MB of RAM
I certainly don't wish to "give up" 64MB of RAM, but I can't locate anything in the BIOS setup
that sounds like it might be an IOMMU setting; my BIOS is several years old, though, so maybe it
just doesn't have such a thing ... Google suggests that IOMMU is a generic name for AMD's IOV, but I
found nothing like "IOV" in my BIOS either (my processor is an AMD Athlon(tm) II X4 640 Processor.
5) Another series of lines in /var/log/kern.log is the following:
08:17:54 kernel: [ 4.694148] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
08:17:54 kernel: [ 4.714659] ACPI Warning: SystemIO range 0x0B00-0x00B07 conflicts with OpRegion 0x0B00-0x0B0F (\SOR1) (20150930/utaddress-254)
08:17:54 kernel: [ 4.714666] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
This machine is a desktop and I don't use (or think I need) power management; is this memory conflict
something I should care about eliminating or just leave well enough alone?
Thanks very much for any advice, education, or enlightenment anyone can offer.