Booting up to black screen - Log included

Greetings,

I previously posted that since a fedup to fedora 21, I intermittently 
boot up to a blank screen. I'm using akmod-nvidia-340xx, but reverting 
back to nouveau did not solve the issue. One out of every 3 boot results 
in the problem. I pressed ctrl+alt+F2 and logged in and attempted the 
startx command. The resulting error message said to check xorg.1.log.

The nvidia console ( nvidia xserver settings ) clearly indicates my 
screen type ( Ancor communications Asus VH196. Would the "no screens 
found" be the possible source of my headache?

This is the error log from /var/log/Xorg.1.log:

[   359.396] (II) FBDEV: driver for framebuffer: fbdev
[   359.396] (II) VESA: driver for VESA chipsets: vesa
[   359.396] (++) using VT number 2

[   359.396] (WW) Falling back to old probe method for modesetting
[   359.396] (II) Loading sub module "fbdevhw"
[   359.396] (II) LoadModule: "fbdevhw"
[   359.396] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
[   359.397] (II) Module fbdevhw: vendor="X.Org Foundation"
[   359.397] 	compiled for 1.16.3, module version = 0.0.2
[   359.397] 	ABI class: X.Org Video Driver, version 18.0
[   359.397] (EE) open /dev/fb0: No such file or directory
[   359.397] (WW) Falling back to old probe method for fbdev
[   359.397] (II) Loading sub module "fbdevhw"
[   359.397] (II) LoadModule: "fbdevhw"
[   359.397] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
[   359.397] (II) Module fbdevhw: vendor="X.Org Foundation"
[   359.397] 	compiled for 1.16.3, module version = 0.0.2
[   359.397] 	ABI class: X.Org Video Driver, version 18.0
[   359.397] (EE) open /dev/fb0: No such file or directory
[   359.397] vesa: Ignoring device with a bound kernel driver
[   359.397] (WW) Falling back to old probe method for vesa
[   359.397] (EE) Screen 0 deleted because of no matching config section.
[   359.397] (II) UnloadModule: "modesetting"
[   359.397] (EE) Screen 0 deleted because of no matching config section.
[   359.397] (II) UnloadModule: "fbdev"
[   359.397] (II) UnloadSubModule: "fbdevhw"
[   359.397] (EE) Screen 0 deleted because of no matching config section.
[   359.397] (II) UnloadModule: "vesa"
[   359.397] (EE) Device(s) detected, but none match those in the config 
file.
[   359.397] (EE)
Fatal server error:
[   359.397] (EE) no screens found(EE)
[   359.397] (EE)
Please consult the Fedora Project support
     at http://wiki.x.org
  for help.
[   359.397] (EE) Please also check the log file at 
"/var/log/Xorg.1.log" for additional information.
[   359.397] (EE)
[   359.398] (EE) Server terminated with error (1). Closing log file.

[poma]

On 07.03.2015 13:45, [e-mail] wrote:

...
> boot up to a blank screen. I'm using akmod-nvidia-340xx, but reverting 
> back to nouveau did not solve the issue.

...

NOUVEAU TEST:

Part I

# yum erase *nvidia*
# dracut -f
# systemctl set-default multi-user.target
# systemctl reboot

Part II

Paste here the output of the following commands:
$ lspci -knn -s $(lspci | grep VGA | awk '{print $1}')
$ grep -P '(?=.*^blacklist)(?=.*nouveau)' /etc/modprobe.d/*.conf
$ grep 'nouveau|modeset' /proc/cmdline
$ modinfo nouveau -n
$ lsmod | grep ^nouveau
$ systemctl show display-manager -p Id

Part III

Follows, if the results of the above are satisfactory.

[Martin Cigorraga]

Hello, it's a GPU modules issue, by all means; I experienced the very same
the first time I booted into the live environment to install Fedora.
You need to find a workaround, maybe by adding the needed parameters in
your kernel boot line.
Regards.

On Sat, Mar 7, 2015 at 9:45 AM,  wrote:
> Greetings,
>
> I previously posted that since a fedup to fedora 21, I intermittently boot
> up to a blank screen. I'm using akmod-nvidia-340xx, but reverting back to
> nouveau did not solve the issue. One out of every 3 boot results in the
> problem. I pressed ctrl+alt+F2 and logged in and attempted the startx
> command. The resulting error message said to check xorg.1.log.
>
> The nvidia console ( nvidia xserver settings ) clearly indicates my screen
> type ( Ancor communications Asus VH196. Would the "no screens found" be the
> possible source of my headache?
>
> This is the error log from /var/log/Xorg.1.log:
>
> [   359.396] (II) FBDEV: driver for framebuffer: fbdev
> [   359.396] (II) VESA: driver for VESA chipsets: vesa
> [   359.396] (++) using VT number 2
>
> [   359.396] (WW) Falling back to old probe method for modesetting
> [   359.396] (II) Loading sub module "fbdevhw"
> [   359.396] (II) LoadModule: "fbdevhw"
> [   359.396] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
> [   359.397] (II) Module fbdevhw: vendor="X.Org Foundation"
> [   359.397]    compiled for 1.16.3, module version = 0.0.2
> [   359.397]    ABI class: X.Org Video Driver, version 18.0
> [   359.397] (EE) open /dev/fb0: No such file or directory
> [   359.397] (WW) Falling back to old probe method for fbdev
> [   359.397] (II) Loading sub module "fbdevhw"
> [   359.397] (II) LoadModule: "fbdevhw"
> [   359.397] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
> [   359.397] (II) Module fbdevhw: vendor="X.Org Foundation"
> [   359.397]    compiled for 1.16.3, module version = 0.0.2
> [   359.397]    ABI class: X.Org Video Driver, version 18.0
> [   359.397] (EE) open /dev/fb0: No such file or directory
> [   359.397] vesa: Ignoring device with a bound kernel driver
> [   359.397] (WW) Falling back to old probe method for vesa
> [   359.397] (EE) Screen 0 deleted because of no matching config section.
> [   359.397] (II) UnloadModule: "modesetting"
> [   359.397] (EE) Screen 0 deleted because of no matching config section.
> [   359.397] (II) UnloadModule: "fbdev"
> [   359.397] (II) UnloadSubModule: "fbdevhw"
> [   359.397] (EE) Screen 0 deleted because of no matching config section.
> [   359.397] (II) UnloadModule: "vesa"
> [   359.397] (EE) Device(s) detected, but none match those in the config
> file.
> [   359.397] (EE)
> Fatal server error:
> [   359.397] (EE) no screens found(EE)
> [   359.397] (EE)
> Please consult the Fedora Project support
>          at http://wiki.x.org
>  for help.
> [   359.397] (EE) Please also check the log file at "/var/log/Xorg.1.log"
> for additional information.
> [   359.397] (EE)
> [   359.398] (EE) Server terminated with error (1). Closing log file.
> --
> users mailing list
> [e-mail]
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org

I googled about and saw something somebody else tried. I renamed 
nvidia-xorg.conf to xorg.conf and thus far this seems to have resolved 
the issue...

On 03/07/2015 07:23 PM, Martin Cigorraga wrote:
> Hello, it's a GPU modules issue, by all means; I experienced the very
> same the first time I booted into the live environment to install Fedora.
> You need to find a workaround, maybe by adding the needed parameters in
> your kernel boot line.
> Regards.
>
> On Sat, Mar 7, 2015 at 9:45 AM, <[e-mail]
> > wrote:
> Greetings,
>
> I previously posted that since a fedup to fedora 21, I
> intermittently boot up to a blank screen. I'm using
> akmod-nvidia-340xx, but reverting back to nouveau did not solve the
> issue. One out of every 3 boot results in the problem. I pressed
> ctrl+alt+F2 and logged in and attempted the startx command. The
> resulting error message said to check xorg.1.log.
>
> The nvidia console ( nvidia xserver settings ) clearly indicates my
> screen type ( Ancor communications Asus VH196. Would the "no screens
> found" be the possible source of my headache?
>
> This is the error log from /var/log/Xorg.1.log:
>
> [   359.396] (II) FBDEV: driver for framebuffer: fbdev
> [   359.396] (II) VESA: driver for VESA chipsets: vesa
> [   359.396] (++) using VT number 2
>
> [   359.396] (WW) Falling back to old probe method for modesetting
> [   359.396] (II) Loading sub module "fbdevhw"
> [   359.396] (II) LoadModule: "fbdevhw"
> [   359.396] (II) Loading /usr/lib64/xorg/modules/__libfbdevhw.so
> [   359.397] (II) Module fbdevhw: vendor="X.Org Foundation"
> [   359.397]    compiled for 1.16.3, module version = 0.0.2
> [   359.397]    ABI class: X.Org Video Driver, version 18.0
> [   359.397] (EE) open /dev/fb0: No such file or directory
> [   359.397] (WW) Falling back to old probe method for fbdev
> [   359.397] (II) Loading sub module "fbdevhw"
> [   359.397] (II) LoadModule: "fbdevhw"
> [   359.397] (II) Loading /usr/lib64/xorg/modules/__libfbdevhw.so
> [   359.397] (II) Module fbdevhw: vendor="X.Org Foundation"
> [   359.397]    compiled for 1.16.3, module version = 0.0.2
> [   359.397]    ABI class: X.Org Video Driver, version 18.0
> [   359.397] (EE) open /dev/fb0: No such file or directory
> [   359.397] vesa: Ignoring device with a bound kernel driver
> [   359.397] (WW) Falling back to old probe method for vesa
> [   359.397] (EE) Screen 0 deleted because of no matching config
> section.
> [   359.397] (II) UnloadModule: "modesetting"
> [   359.397] (EE) Screen 0 deleted because of no matching config
> section.
> [   359.397] (II) UnloadModule: "fbdev"
> [   359.397] (II) UnloadSubModule: "fbdevhw"
> [   359.397] (EE) Screen 0 deleted because of no matching config
> section.
> [   359.397] (II) UnloadModule: "vesa"
> [   359.397] (EE) Device(s) detected, but none match those in the
> config file.
> [   359.397] (EE)
> Fatal server error:
> [   359.397] (EE) no screens found(EE)
> [   359.397] (EE)
> Please consult the Fedora Project support
>           at http://wiki.x.org
>   for help.
> [   359.397] (EE) Please also check the log file at
> "/var/log/Xorg.1.log" for additional information.
> [   359.397] (EE)
> [   359.398] (EE) Server terminated with error (1). Closing log file.
> --
> users mailing list
> [e-mail] <mailto:[e-mail]>
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.__org/mailman/listinfo/users
> <https://admin.fedoraproject.org/mailman/listinfo/users>
> Fedora Code of Conduct: http://fedoraproject.org/code-__of-conduct
> <http://fedoraproject.org/code-of-conduct>
> Guidelines: http://fedoraproject.org/wiki/__Mailing_list_guidelines
> <http://fedoraproject.org/wiki/Mailing_list_guidelines>
> Have a question? Ask away: http://ask.fedoraproject.org
>
>
>
>
> --
> -Martin