Ask Your Question
0

After upgrade to kernel 4.3 fc23 No screen after login

asked 2016-01-16 01:18:20 -0600

Arttalbert gravatar image

updated 2016-01-17 14:06:55 -0600

After I log in on the new kernel-4.3 fc23, I get a blank screen. I tried to go to tty2, but it won't go there. I can go to tty3. I then called for an dnf upgrade, but this hasn't helped. I then rebooted back to kernel 4.2, and it works the same as always. Is this a bug that can be corrected? hw Memory: 3.6 Gib Processor: AMD Processor model unknown × 6 Graphics : Gallium 0.4 on NV4C Gnome: Version 3.18.2

My video board has always been a problem, I've had to work with it on all upgrades to different versions. This time, I don't know what happened, its not a black screen at login, its a blank screen after login, I hit ctrl, alt, F1 and it goes back to login screen from the blank screen. Then, I try tty2, and nothing happens, then tty3 and the screen goes to tty3. Strange, I think, can't find anything in the logs, so nothing is being reported except login as normal. I just can't get the GUI to work. It still works in the Kernel 4.2..

lspci -vnn |grep VGA -A 14 00:0d.0 VGA compatible controller [0300]: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:83a4] Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 22 Memory at de000000 (32-bit, non-prefetchable) [size=16M] Memory at c0000000 (64-bit, prefetchable) [size=256M] Memory at dd000000 (64-bit, non-prefetchable) [size=16M] Expansion ROM at dffc0000 [disabled] [size=128K] Capabilities: [48] Power Management version 2 Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+ Kernel driver in use: nouveau Kernel modules: nouveau

00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 10h Processor HyperTransport Configuration [1022:1200] Flags: fast devsel Capabilities: [80] HyperTransport: Host or Secondary Interface

Ok, this is parts of my logs that I get to read. Sorry for the boring reading, but here goes the information:

This is a part of the journal on Kernel 4.2 after boot

Jan 17 11:13:46 localhost.localdomain audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 ms Jan 17 11:13:44 localhost.localdomain /usr/libexec/gdm-x-session[1964]: Successfully activated service 'org.gnome.GConf' Jan 17 11:13:44 localhost.localdomain /usr/libexec/gdm-x-session[1964]: Activating service name='org.gnome.GConf' Jan 17 11:13:43 localhost.localdomain audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 ms Jan 17 11:13:40 localhost.localdomain kernel: nouveau E[ PBUS][0000:00:0d.0] MMIO write of 0x00000000 FAULT at 0x00b030 Jan 17 11:13:40 localhost.localdomain kernel: nouveau E[ PBUS][0000:00:0d.0] MMIO write of 0x06950001 FAULT at 0x00b030 Jan 17 11:13:37 localhost.localdomain gnome-shell.desktop[2194]: Gjs-Message: JS LOG: The property vignette_sharpness doesn ... (more)

edit retag flag offensive close merge delete

Comments

Can you provide more details about your hw? Would be greatly helpful. Without details, only with issue reported it's not gonna solve anything. Thank you.

zoltanh721 gravatar imagezoltanh721 ( 2016-01-16 05:02:31 -0600 )edit

I have the same problem. My laptop is an old 2006 model.

Dell E1705 GeForce Go 7900 GS 4Gb RAM BIOS v. A10 T2600 processor upgrade Solid State HD upgrade

Graphics Drivers are proprietary as follows in the following guide: http://www.if-not-true-then-false.com...

SeVaS gravatar imageSeVaS ( 2016-01-17 18:22:15 -0600 )edit

Thanks SeVaS, that was what I had to do to get it to work when I upgraded to fc20. It work after Intel drivers, but quit on fc22. Nouveau is working now on fc23 kernel 4.2, but something is locking up the driver in kernel 4.3.

Arttalbert gravatar imageArttalbert ( 2016-01-18 01:55:48 -0600 )edit

4 Answers

Sort by » oldest newest most voted
0

answered 2016-01-18 01:41:58 -0600

Arttalbert gravatar image

I found the answer to my problem, but I don't know how to solve it. The problem is that the VT is switched on for Virtual Box to work. After the login this is where it begins and ends: reading in reverse log

Jan 17 12:35:25 localhost.localdomain /usr/libexec/gdm-x-session[1899]: (II) systemd-logind: got pause for 13:66 Jan 17 12:35:25 localhost.localdomain /usr/libexec/gdm-x-session[1899]: (II) systemd-logind: got pause for 13:64 Jan 17 12:35:25 localhost.localdomain /usr/libexec/gdm-x-session[1899]: (II) systemd-logind: got pause for 13:65 Jan 17 12:35:25 localhost.localdomain /usr/libexec/gdm-x-session[1899]: (II) systemd-logind: got pause for 226:0 Jan 17 12:35:25 localhost.localdomain /usr/libexec/gdm-x-session[1899]: (II) systemd-logind: got pause for 13:67 Jan 17 12:35:25 localhost.localdomain /usr/libexec/gdm-x-session[1899]: (II) NOUVEAU(0): NVLeaveVT is called. Jan 17 12:35:25 localhost.localdomain /usr/libexec/gdm-x-session[1899]: (II) AIGLX: Suspending AIGLX clients for VT switch

Now, with out turning off the VT in the bios, how do I solve this?

edit flag offensive delete link more

Comments

I turned off the VT switch and it didn't solve the problem. Still waiting for another upgrade on the kernel.

Arttalbert gravatar imageArttalbert ( 2016-01-20 10:48:20 -0600 )edit
1

Solved, new update on the kernel 4.3 solved the problem. Atta boy Fedora!

Arttalbert gravatar imageArttalbert ( 2016-01-21 12:03:06 -0600 )edit
0

answered 2016-01-16 14:11:04 -0600

jalalsfs gravatar image

What is your graphical card? Do you use the proprietary driver or the free driver?

edit flag offensive delete link more
0

answered 2018-12-26 16:57:02 -0600

DirkHoffmann gravatar image

I had a similar problem with fc22 / kernel 4.4.14-200. NVIDIA long term support is a problem in Fedora/RedHat, unfortunately. Like the fc23 referenced in the OP, all this is quite old stuff now, but in case someone needs to run archeological systems, I post this hint.

I recovered my graphical display manager (gnome 3) by removing xorg-x11-drv-nvidia-:358.16.-1.fc22, opencl-utils-0-14.svn16.fc22, kmod-nvidia-4.4.14-200.fc22. I had installed them "accidentally" while testing some code using GPU for calculation.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

2 followers

Stats

Asked: 2016-01-16 01:18:20 -0600

Seen: 522 times

Last updated: Dec 26 '18