4:49 p.m.
Good afternoon,
I upgraded from f25 to f26 this afternoon. I didn't see any error messages, but a lot
of messages went by very fast. After the verification step was done, the system
automatically rebooted. After the three rectangles separately brightened and faded, the
screen went blank. After over 15 minutes, still nothing. I did a hard reset. Same
behavior. This is a dual-boot system; I am able to log in to windows-7.
I'm a home user, not a sys.admin. I do have f25 on a usb stick.
Please help.
Thank-you in advance.
Bill.
10:28 p.m.
On 10/19/2017 02:49 PM, William Mattison wrote:
I upgraded from f25 to f26 this afternoon. I didn't see any
error messages, but a lot of messages went by very fast. After the verification step was
done, the system automatically rebooted. After the three rectangles separately brightened
and faded, the screen went blank. After over 15 minutes, still nothing. I did a hard
reset. Same behavior. This is a dual-boot system; I am able to log in to windows-7.
Did you have those rectangles in F25 or did you have the Fedora logo
filling up? It sounds like there's a graphics problem, do you have
NVidia graphics? What desktop are you using? Gnome, KDE, something else?
11:36 p.m.
On 10/20/17 11:28, Samuel Sieb wrote:
On 10/19/2017 02:49 PM, William Mattison wrote:
> I upgraded from f25 to f26 this afternoon. I didn't see any error messages, but
a
> lot of messages went by very fast. After the verification step was done, the
> system automatically rebooted. After the three rectangles separately brightened
> and faded, the screen went blank. After over 15 minutes, still nothing. I did a
> hard reset. Same behavior. This is a dual-boot system; I am able to log in to
> windows-7.
Did you have those rectangles in F25 or did you have the Fedora logo filling up?Â
It sounds like there's a graphics problem, do you have NVidia graphics? What
desktop are you using? Gnome, KDE, something else?
Odd that the original message didn't show up in either of my subscribed addresses....
Anyway, along with the graphics HW it would be good to know if he is using nVidia he
is using nouveau or nVidia drivers.
--
Fedora Users List - The place to go to speculate endlessly
12:12 a.m.
Could your "Odd..." have something to do with my submitting the message through
the fedora HYPERKITTY web site rather than e-mailing it through Thunderbird?
I know I wrestled with the graphics card driver some 4 years ago, but I don't recall
whether I switched from nouveau to nVidia or from nVidia to nouveau.
I hope the log I will include in my reply to Samuel's second message might answer
that. I'm not clear on what it's saying.
thanks,
Bill.
3:31 a.m.
Could your "Odd..." have something to do with my submitting
the message through
the fedora HYPERKITTY web site rather than e-mailing it through Thunderbird?
Possibly. I'm replying in Hyperkitty to check this.
FWIW, I agree with Samuel that you've probably not waited long enough for the nVidia
drivers to be rebuilt. This takes a bit longer than usual at the end of an upgrade. You
should also check /var/cache to see if you have an akmods directory. If you do, look in
that directory and there should be a log file telling you what was going on around the
times you were booting.
5:06 p.m.
Hi Ed,
The f25 to f26 upgrade was done using the instructions here:
"https://fedoraproject.org/wiki/DNF_system_upgrade".
The boot that seemed to fail (or never finish) was the one that should happen
automatically at the end of step 7. I waited for that boot to finish over 15 minutes
after the 3 rectangles disappeared before doing the hard reset. The screen was blank that
whole time.
Question: When during the upgrade process does the building of the nvidia drivers happen?
(I would have guessed that it happens during the long process triggered by my dnf command
in step 6, but before the automatic reboot that occurs at the end of step 7 (after
thousands of installing, clean-up, and verifying messages).
Question: How long should I have waited?
Question: I did not run dnf after 2200. Who or what did? (not a complaint; rather,
I'm curious)
The log file you point to does exist. The relevant part is at the bottom of this message,
between the lines of '='. I gather from that log extract, and from what Samuel
said overnight, that whatever the problem was has somehow fixed itself. Also, things seem
to be behaving better today.
Thank-you for your help.
Bill.
======================================================================
2017/10/19 12:08:05 akmods: Checking kmods exist for 4.12.14-200.fc25.x86_64
2017/10/19 12:23:10 akmods: Checking kmods exist for 4.13.5-100.fc25.x86_64
2017/10/19 12:23:10 akmods: Building and installing nvidia-kmod
2017/10/19 12:23:10 akmods: Building RPM using the command '/sbin/akmodsbuild --target
x86_64 --kernels 4.13.5-100.fc25.x86_64 /usr/src/akmods/nvidia-kmod.latest'
2017/10/19 12:23:33 akmods: Installing newly built rpms
2017/10/19 12:23:33 akmods: DNF detected
2017/10/19 12:23:39 akmods: Successful.
2017/10/19 12:23:56 akmods: Checking kmods exist for 4.12.13-200.fc25.x86_64
2017/10/19 12:23:57 akmods: Checking kmods exist for 4.12.14-200.fc25.x86_64
2017/10/19 12:23:57 akmods: Checking kmods exist for 4.13.5-100.fc25.x86_64
2017/10/19 12:25:20 akmods: Checking kmods exist for 4.13.5-100.fc25.x86_64
2017/10/19 12:50:49 akmods: Checking kmods exist for 4.12.13-200.fc25.x86_64
2017/10/19 12:50:49 akmods: Checking kmods exist for 4.12.14-200.fc25.x86_64
2017/10/19 12:50:49 akmods: Checking kmods exist for 4.13.5-100.fc25.x86_64
2017/10/19 14:35:49 akmods: Checking kmods exist for 4.13.5-200.fc26.x86_64
2017/10/19 14:35:49 akmods: Building and installing nvidia-kmod
2017/10/19 14:35:49 akmods: Building RPM using the command '/sbin/akmodsbuild --target
x86_64 --kernels 4.13.5-200.fc26.x86_64 /usr/src/akmods/nvidia-kmod.latest'
2017/10/19 14:36:16 akmods: Installing newly built rpms
2017/10/19 14:36:16 akmods: DNF detected
2017/10/19 14:36:16 akmods: Could not install newly built RPMs. You can find them and the
logfile
2017/10/19 14:36:16 akmods: 375.66-3-for-4.13.5-200.fc26.x86_64.failed.log in
/var/cache/akmods/nvidia/
2017/10/19 14:36:16 akmods: Checking kmods exist for 4.13.5-100.fc25.x86_64
2017/10/19 14:36:17 akmods: Building and installing nvidia-kmod
2017/10/19 14:36:17 akmods: Building RPM using the command '/sbin/akmodsbuild --target
x86_64 --kernels 4.13.5-100.fc25.x86_64 /usr/src/akmods/nvidia-kmod.latest'
2017/10/19 14:36:39 akmods: Installing newly built rpms
2017/10/19 14:36:39 akmods: DNF detected
2017/10/19 14:36:39 akmods: Could not install newly built RPMs. You can find them and the
logfile
2017/10/19 14:36:39 akmods: 375.66-3-for-4.13.5-100.fc25.x86_64.failed.log in
/var/cache/akmods/nvidia/
2017/10/19 14:48:20 akmods: Checking kmods exist for 4.13.5-200.fc26.x86_64
2017/10/19 14:48:26 akmods: Ignoring nvidia-kmod as it failed earlier
2017/10/19 14:48:26 akmods: Hint: Some kmods were ignored or failed to build or install.
2017/10/19 14:48:26 akmods: You can try to rebuild and install them by by calling
2017/10/19 14:48:26 akmods: '/usr/sbin/akmods --force' as root.
2017/10/19 15:19:48 akmods: Checking kmods exist for 4.13.5-200.fc26.x86_64
2017/10/19 15:19:54 akmods: Ignoring nvidia-kmod as it failed earlier
2017/10/19 15:19:54 akmods: Hint: Some kmods were ignored or failed to build or install.
2017/10/19 15:19:54 akmods: You can try to rebuild and install them by by calling
2017/10/19 15:19:54 akmods: '/usr/sbin/akmods --force' as root.
2017/10/19 22:07:58 akmods: Checking kmods exist for 4.13.5-200.fc26.x86_64
2017/10/19 22:08:06 akmods: Ignoring nvidia-kmod as it failed earlier
2017/10/19 22:08:06 akmods: Hint: Some kmods were ignored or failed to build or install.
2017/10/19 22:08:06 akmods: You can try to rebuild and install them by by calling
2017/10/19 22:08:06 akmods: '/usr/sbin/akmods --force' as root.
2017/10/19 22:19:49 akmods: Checking kmods exist for 4.12.14-200.fc25.x86_64
2017/10/19 22:19:52 akmods: Checking kmods exist for 4.13.5-100.fc25.x86_64
2017/10/19 22:19:52 akmods: Checking kmods exist for 4.13.5-200.fc26.x86_64
2017/10/19 22:19:52 akmods: Building and installing nvidia-kmod
2017/10/19 22:19:52 akmods: Building RPM using the command '/sbin/akmodsbuild --target
x86_64 --kernels 4.13.5-200.fc26.x86_64 /usr/src/akmods/nvidia-kmod.latest'
2017/10/19 22:20:18 akmods: Installing newly built rpms
2017/10/19 22:20:18 akmods: DNF detected
2017/10/19 22:21:01 akmods: Successful.
2017/10/19 22:22:21 akmods: Checking kmods exist for 4.13.5-200.fc26.x86_64
2017/10/19 22:38:47 akmods: Checking kmods exist for 4.12.14-200.fc25.x86_64
2017/10/19 22:38:47 akmods: Checking kmods exist for 4.13.5-100.fc25.x86_64
2017/10/19 22:38:47 akmods: Checking kmods exist for 4.13.5-200.fc26.x86_64
======================================================================
8:53 p.m.
Hi Ed,
The f25 to f26 upgrade was done using the instructions here:
"https://fedoraproject.org/wiki/DNF_system_upgrade".
The boot that seemed to fail (or never finish) was the one that should happen
automatically at the end of step 7. I waited for that boot to finish over 15 minutes
after the 3 rectangles disappeared before doing the hard reset. The screen was blank
that
whole time.
Question: When during the upgrade process does the building of the nvidia drivers happen?
(I would have guessed that it happens during the long process triggered by my dnf
command
in step 6, but before the automatic reboot that occurs at the end of step 7 (after
thousands of installing, clean-up, and verifying messages).
If I remember correctly, and that is a big if, the process that builds the new drivers is
kicked off between the "clean-up" and "verify" phase of the dnf
process.
The problem is if the clean-up process lasts too long and the verify process doesn't
complete by the time akmod tries to install the new rpm it built it is locked out and
fails. This can also happen during a normal update if a large number of packages and a
new kernel are being updated.
Question: How long should I have waited?
There is no set time since it is a variable depending on CPU and disk performance.
After an upgrade I am often left with a blinking cursor. I just walk away and come back
later to find the login screen.
When, if, you find yourself in the same situation you should just bring up a console and
check the log file to see what is happening.
Question: I did not run dnf after 2200. Who or what did? (not a complaint; rather,
I'm curious)
But when did you reboot? akmod will check for a working nVidia driver on each boot.
2017/10/19 14:36:16 akmods: Could not install newly built RPMs. You
can find them and the
logfile
The above indicated that the rpm was built, but could not be installed. Most likely due
to the dnf command still having the rpm database locked.
(Odd that I don't get messages you post here....but I get my response via email that I
post on hyperkitty) Oh, well.
11:01 p.m.
On 10/20/2017 06:53 PM, Ed Greshko wrote:
If I remember correctly, and that is a big if, the process that
builds the new drivers is kicked off between the "clean-up" and
"verify" phase of the dnf process.
I think it generally doesn't work at that point even if it does try.
> Question: How long should I have waited?
There is no set time since it is a variable depending on CPU and disk performance.
After an upgrade I am often left with a blinking cursor. I just walk away and come back
later to find the login screen.
At the end of the upgrade process there are a lot of scripts and stuff
that run, sometimes for a long time depending on the speed of the computer.
When, if, you find yourself in the same situation you should just
bring up a console and check the log file to see what is happening.
I'm not clear if this happened at the end of the upgrade process or on
the first reboot. If it's at the end of the upgrade, then there are no
other consoles. On the reboot, if it's made it far enough, then there
will be.
> Question: I did not run dnf after 2200. Who or what did? (not a
complaint; rather,
> I'm curious)
But when did you reboot? akmod will check for a working nVidia driver on each boot.
And akmods runs dnf to install the rpm it builds.
> 2017/10/19 14:36:16 akmods: Could not install newly built RPMs.
You can find them and the
> logfile
The above indicated that the rpm was built, but could not be installed. Most likely due
to the dnf command still having the rpm database locked.
Right, so the next reboot will be able to do the install.
5:03 a.m.
On Fri, 2017-10-20 at 21:01 -0700, Samuel Sieb wrote:
> The above indicated that the rpm was built, but could not be
installed. Most likely due to the dnf command still having the rpm database locked.
Right, so the next reboot will be able to do the install.
You can also just run 'dnf install' directly on the rpm that akmod
produces. That's what I generally do when this happens. You still need
to reboot of course.
poc
10:28 a.m.
(replying to Ed, Samuel, and Patrick)
The upgrade phase (step 7) generated a line of output for each package(?) being upgraded.
The clean-up phase (step 7) generated a line of output for each upgraded package(?).
The verify phase (step 7) generated a line of output for each upgraded package(?).
Then came the automatic reboot. After the grub menu disappeared,...
The left rectangle brightened, then dimmed.
Then the middle rectangle brightened, then dimmed.
Then the right rectangle brightened, then dimmed.
A bunch of error messages (ACPI errors, addressed in a prior thread, back in May) flew
by.
Then 15+ minutes of nothing but black screen with slowly blinking cursor.
I have a 3+ gigahertz quad-core chip, and 16 gb memory. I don't know the speed rating
of the hard drive, but it has plenty of empty space. 15+ minutes of black screen with one
slowly blinking cursor had me thinking something was "stuck", caught in a loop,
aborted, crashed, or something else nasty. Processes that take a while should generate
output somehow indicating progress, as does
* dnf's download, upgrade, clean-up, and verification phases;
* file browsers when copying large amounts of files to a usb stick (a growing percent done
bar, or a pie chart gradually filling in).
* k3b when copying stuff to a cd/dvd/blu-ray;
* (many other examples).
Question: If I were to submit an enhancement request bugzilla on this, would it likely get
done (preferably in time for Fedora 28)?
If yes, then
Question: Which bugzilla (or other tracking system) should I use (please provide url)?
Endif.
Ed: When I had fedora HYPERKITTY issues in early July, Kevin Fenzi referred me to the
Fedora infrastructure site:
"https://pagure.io/fedora-infrastructure/issues"
to report the issues. I submitted issue #6146 in response.
Thank-you.
Bill.
10:10 p.m.
Question: If I were to submit an enhancement request bugzilla on
this, would it likely get
done (preferably in time for Fedora 28)?
If yes, then
Question: Which bugzilla (or other tracking system) should I use (please provide url)?
There would be no action taken on any fedora bugzilla you submit on this issue since it
isn't a "fedora" issue. It is related to the rpmfusion packages.
Since you did see the slowly blinking cursor on the reboot could have opened a console
window to check the progress. Also, if you have a disk activity light you should have
seen activity.
I guess, you could always file a bugzilla on rpmfusion asking for akmod to display a
message when rebuilding nVidia drivers. I have no idea how easy that would be for them to
implement.
10:39 a.m.
New subject: no login screen after f25 to f26 upgrade. [SOLVED]
Good morning,
In the RPM Fusion Bugzilla, I submitted bug #4690 to request that simple
progress logging be added to the nvidia driver patching and upgrading.
The worst RPM Fusion can do is reject the request. If they accept and
implement it, it would be helpful to non-pro's like me and other
(probably scarce) "home users" of Fedora, and maybe even to the pro's.
Samuel, Ed, and Patrick: I thank you for all your help on this. I've
marked this "SOLVED".
Bill.
12:11 a.m.
I saw those same rectangles in f-25.
I have an NVidia graphics card.
I usually use Gnome, but since the upgrade, I don't even get to the login screen.
I'll answer your second message separately.
thanks,
Bill.
10:29 p.m.
On 10/19/2017 02:49 PM, William Mattison wrote:
I upgraded from f25 to f26 this afternoon. I didn't see any
error messages, but a lot of messages went by very fast. After the verification step was
done, the system automatically rebooted. After the three rectangles separately brightened
and faded, the screen went blank. After over 15 minutes, still nothing. I did a hard
reset. Same behavior. This is a dual-boot system; I am able to log in to windows-7.
Something to try is pressing CTRL-ALT-F3 and see if you get a console.
If you do, try logging in and run "startx".
12:12 a.m.
The CTRL-ALT3-F3 got me a basic black-and-white login prompt. I logged in as root, and
typed in "startx". I got a bunch of messages, ending with "Please also
check the log file at "/var/log/Xorg.0.log" for additional information.".
I shut down. I booted up. I got ***no*** screen with the option to enter and edit bios.
I got ***no*** grub menu. But I got a bunch of long thick white lines in seemingly random
places, and of seemingly random length. I eventually got winter lake scene with a login
gui. I was able to log in as root, launch Thunderbird, and mail the Xorg log to myself.
Since I haven't yet done the post-upgrade tasks, I then shut down, and booted back
into windows-7, where I am now.
I did also see strange display behavior in windows this evening, but only within Firefox:
blocks of black.
The Xorg log is below, beneath the line of '='.
Is there a simple way to test the graphics card, either from Fedora or from windows-7?
Thank-you, Sam and Ed.
Bill.
==================================================================================================================
[ 171.530]
X.Org X Server 1.19.3
Release Date: 2017-03-15
[ 171.530] X Protocol Version 11, Revision 0
[ 171.530] Build Operating System: 4.10.6-200.fc25.x86_64
[ 171.531] Current Operating System: Linux {sysname} 4.13.5-200.fc26.x86_64 #1 SMP Thu
Oct 5 16:53:13 UTC 2017 x86_64
[ 171.531] Kernel command line: BOOT_IMAGE=/vmlinuz-4.13.5-200.fc26.x86_64
root=UUID=45e553d2-fa0c-4eae-95f6-7bf9086ab74c ro rd.md=0 rd.lvm=0 rd.dm=0 rd.luks=0
vconsole.keymap=us rhgb quiet nouveau.modeset=0 rd.driver.blacklist=nouveau video=vesa:on
modprobe.blacklist=nouveau LANG=en_US.UTF-8
[ 171.531] Build Date: 23 April 2017 11:51:31PM
[ 171.533] Build ID: xorg-x11-server 1.19.3-4.fc26
[ 171.533] Current version of pixman: 0.34.0
[ 171.533] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 171.533] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 171.534] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Oct 19 22:10:29
2017
[ 171.534] (==) Using config file: "/etc/X11/xorg.conf"
[ 171.534] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 171.534] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 171.535] (==) No Layout section. Using the first Screen section.
[ 171.535] (==) No screen section available. Using defaults.
[ 171.535] (**) |-->Screen "Default Screen Section" (0)
[ 171.535] (**) | |-->Monitor "<default monitor>"
[ 171.535] (==) No device specified for screen "Default Screen Section".
Using the first device section listed.
[ 171.535] (**) | |-->Device "Videocard0"
[ 171.535] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 171.535] (==) Automatically adding devices
[ 171.535] (==) Automatically enabling devices
[ 171.535] (==) Automatically adding GPU devices
[ 171.535] (==) Automatically binding GPU devices
[ 171.535] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 171.535] (==) FontPath set to:
catalogue:/etc/X11/fontpath.d,
built-ins
[ 171.535] (**) ModulePath set to
"/usr/lib64/nvidia/xorg,/usr/lib64/xorg/modules"
[ 171.535] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 171.535] (II) Loader magic: 0x823e00
[ 171.535] (II) Module ABI versions:
[ 171.535] X.Org ANSI C Emulation: 0.4
[ 171.535] X.Org Video Driver: 23.0
[ 171.535] X.Org XInput driver : 24.1
[ 171.535] X.Org Server Extension : 10.0
[ 171.537] (++) using VT number 3
[ 171.544] (II) systemd-logind: took control of session
/org/freedesktop/login1/session/_31
[ 171.546] (--) PCI:*(0:1:0:0) 10de:11c0:3842:2662 rev 161, Mem @ 0xf6000000/16777216,
0xe8000000/134217728, 0xf0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/131072
[ 171.546] (WW) "glamoregl" will not be loaded unless you've specified it
to be loaded elsewhere.
[ 171.546] (II) "glx" will be loaded by default.
[ 171.546] (II) LoadModule: "glx"
[ 171.546] (II) Loading /usr/lib64/nvidia/xorg/libglx.so
[ 171.550] (II) Module glx: vendor="NVIDIA Corporation"
[ 171.550] compiled for 4.0.2, module version = 1.0.0
[ 171.550] Module class: X.Org Server Extension
[ 171.550] (II) NVIDIA GLX Module 375.66 Mon May 1 14:28:39 PDT 2017
[ 171.550] (II) LoadModule: "nvidia"
[ 171.550] (II) Loading /usr/lib64/xorg/modules/drivers/nvidia_drv.so
[ 171.551] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 171.551] compiled for 4.0.2, module version = 1.0.0
[ 171.551] Module class: X.Org Video Driver
[ 171.551] (II) NVIDIA dlloader X Driver 375.66 Mon May 1 14:03:26 PDT 2017
[ 171.551] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 171.551] (II) Loading sub module "fb"
[ 171.551] (II) LoadModule: "fb"
[ 171.551] (II) Loading /usr/lib64/xorg/modules/libfb.so
[ 171.551] (II) Module fb: vendor="X.Org Foundation"
[ 171.551] compiled for 1.19.3, module version = 1.0.0
[ 171.551] ABI class: X.Org ANSI C Emulation, version 0.4
[ 171.551] (II) Loading sub module "wfb"
[ 171.551] (II) LoadModule: "wfb"
[ 171.551] (II) Loading /usr/lib64/xorg/modules/libwfb.so
[ 171.551] (II) Module wfb: vendor="X.Org Foundation"
[ 171.552] compiled for 1.19.3, module version = 1.0.0
[ 171.552] ABI class: X.Org ANSI C Emulation, version 0.4
[ 171.552] (II) Loading sub module "ramdac"
[ 171.552] (II) LoadModule: "ramdac"
[ 171.552] (II) Module "ramdac" already built-in
[ 171.561] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the
[ 171.561] (EE) NVIDIA: system's kernel log for additional error messages and
[ 171.561] (EE) NVIDIA: consult the NVIDIA README for details.
[ 171.561] (EE) No devices detected.
[ 171.561] (EE)
Fatal server error:
[ 171.561] (EE) no screens found(EE)
[ 171.561] (EE)
Please consult the Fedora Project support
at http://wiki.x.org
for help.
[ 171.562] (EE) Please also check the log file at "/var/log/Xorg.0.log" for
additional information.
[ 171.562] (EE)
[ 171.564] (EE) Server terminated with error (1). Closing log file.
==================================================================================================================
2:16 a.m.
On 10/19/2017 10:12 PM, William Mattison wrote:
The CTRL-ALT3-F3 got me a basic black-and-white login prompt. I
logged in as root, and typed in "startx". I got a bunch of messages, ending
with "Please also check the log file at "/var/log/Xorg.0.log" for
additional information.". I shut down. I booted up. I got ***no*** screen with the
option to enter and edit bios. I got ***no*** grub menu. But I got a bunch of long thick
white lines in seemingly random places, and of seemingly random length. I eventually got
winter lake scene with a login gui. I was able to log in as root, launch Thunderbird, and
mail the Xorg log to myself. Since I haven't yet done the post-upgrade tasks, I then
shut down, and booted back into windows-7, where I am now.
That's a little confusing, but it sounds like you did end up eventually
getting the proper login screen. What do you mean by "post-upgrade tasks"?
[ 171.550] (II) LoadModule: "nvidia"
[ 171.550] (II) Loading /usr/lib64/xorg/modules/drivers/nvidia_drv.so
You are using the proprietary NVidia driver.
[ 171.561] (EE) NVIDIA: Failed to initialize the NVIDIA kernel
module. Please see the
[ 171.561] (EE) NVIDIA: system's kernel log for additional error messages and
[ 171.561] (EE) NVIDIA: consult the NVIDIA README for details.
But it was unable to load the NVidia kernel module. I suspect that
somewhere in the reboot cycles you did, the NVidia kernel module ended
up getting rebuilt by akmod. So it will probably work now, which is
supported by you getting that login screen.
5:07 p.m.
Hi Samuel,
The f25 to f26 upgrade was done using the instructions here:
"https://fedoraproject.org/wiki/DNF_system_upgrade".
The "post-upgrade tasks" are the ones in the "Optional post-upgrade
tasks" section and the "Resolving post-upgrade issues" section of those
instructions. I completed those today, along with "rkhunter --propupd".
The problem does seem to have fixed itself. The system does seem to be behaving better
today. For my (and others) education, please see the questions in my reply to Ed's
last post on this thread.
Thank-you.
Bill.
2377
days inactive
2381
days old
16 comments
6 participants
participants (6)
-
Ed Greshko -
Ed Greshko -
Patrick O'Callaghan -
Samuel Sieb -
William -
William Mattison