fedup 20 -> 21 -> xinit -> KDE -> open /dev/fb0: No such file or directory

[Rich Emberson]

Still no mouse or keyboard. Don't know if this is the problem.

from /var/log/Xorg.0.log
START
[    96.019] (II) Loading sub module "fb"
[    96.019] (II) LoadModule: "fb"
[    96.020] (II) Loading /usr/lib64/xorg/modules/libfb.so
[    96.030] (II) Module fb: vendor="X.Org Foundation"
[    96.030]    compiled for 1.17.2, module version = 1.0.0
[    96.030]    ABI class: X.Org ANSI C Emulation, version 0.4
[    96.030] (WW) Unresolved symbol: fbGetGCPrivateKey
[    96.030] (II) Loading sub module "wfb"
[    96.030] (II) LoadModule: "wfb"
[    96.030] (II) Loading /usr/lib64/xorg/modules/libwfb.so
[    96.041] (II) Module wfb: vendor="X.Org Foundation"
[    96.041]    compiled for 1.17.2, module version = 1.0.0
[    96.041]    ABI class: X.Org ANSI C Emulation, version 0.4
[    96.041] (II) Loading sub module "ramdac"
[    96.041] (II) LoadModule: "ramdac"
[    96.041] (II) Module "ramdac" already built-in
[    96.068] (WW) Falling back to old probe method for modesetting
[    96.068] (WW) Falling back to old probe method for fbdev
[    96.068] (II) Loading sub module "fbdevhw"
[    96.068] (II) LoadModule: "fbdevhw"
[    96.068] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
[    96.082] (II) Module fbdevhw: vendor="X.Org Foundation"
[    96.082]    compiled for 1.17.2, module version = 0.0.2
[    96.082]    ABI class: X.Org Video Driver, version 19.0
[    96.082] (EE) open /dev/fb0: No such file or directory
[    96.082] (WW) Falling back to old probe method for vesa
[    96.082] (II) NVIDIA(0): Creating default Display subsection in Screen
section
        "Default Screen Section" for depth/fbbpp 24/32
[    96.082] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[    96.082] (==) NVIDIA(0): RGB weight 888
[    96.082] (==) NVIDIA(0): Default visual is TrueColor
......
END

Thanks
Richard

[Ed Greshko]

On 07/27/15 08:00, Rich Emberson wrote:
> Still no mouse or keyboard. Don't know if this is the problem.
>
> from /var/log/Xorg.0.log
> START
> [    96.019] (II) Loading sub module "fb"
> [    96.019] (II) LoadModule: "fb"
> [    96.020] (II) Loading /usr/lib64/xorg/modules/libfb.so
> [    96.030] (II) Module fb: vendor="X.Org Foundation"
> [    96.030]    compiled for 1.17.2, module version = 1.0.0
> [    96.030]    ABI class: X.Org ANSI C Emulation, version 0.4
> [    96.030] (WW) Unresolved symbol: fbGetGCPrivateKey
> [    96.030] (II) Loading sub module "wfb"
> [    96.030] (II) LoadModule: "wfb"
> [    96.030] (II) Loading /usr/lib64/xorg/modules/libwfb.so
> [    96.041] (II) Module wfb: vendor="X.Org Foundation"
> [    96.041]    compiled for 1.17.2, module version = 1.0.0
> [    96.041]    ABI class: X.Org ANSI C Emulation, version 0.4
> [    96.041] (II) Loading sub module "ramdac"
> [    96.041] (II) LoadModule: "ramdac"
> [    96.041] (II) Module "ramdac" already built-in
> [    96.068] (WW) Falling back to old probe method for modesetting
> [    96.068] (WW) Falling back to old probe method for fbdev
> [    96.068] (II) Loading sub module "fbdevhw"
> [    96.068] (II) LoadModule: "fbdevhw"
> [    96.068] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
> [    96.082] (II) Module fbdevhw: vendor="X.Org Foundation"
> [    96.082]    compiled for 1.17.2, module version = 0.0.2
> [    96.082]    ABI class: X.Org Video Driver, version 19.0
> [    96.082] (EE) open /dev/fb0: No such file or directory
> [    96.082] (WW) Falling back to old probe method for vesa
> [    96.082] (II) NVIDIA(0): Creating default Display subsection in Screen section
>         "Default Screen Section" for depth/fbbpp 24/32
> [    96.082] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
> [    96.082] (==) NVIDIA(0): RGB weight 888
> [    96.082] (==) NVIDIA(0): Default visual is TrueColor

Oh, I see you are using the nVidia drivers.  From rpmfusion?  Using the akmod-nvidia package as well?

If you are, you need to be aware that currently there is a problem with dnf keeping the rpmdb locked when the kmod-nvidia package for the new kernels are built.  This will also result in them not being built during fedup.

Check the log file /var/cache/akmods/akmods.log for errors.

A common way to fix the problem is to run this command as root....

/usr/sbin/akmods --force   and then reboot.

[Ed Greshko]

On 07/27/15 08:00, Rich Emberson wrote:
> Still no mouse or keyboard. Don't know if this is the problem.
>
> from /var/log/Xorg.0.log

Well, the /dev/fb0 is not related to your keyboard/mouse problem since that device is a "frame buffer" which is related to video.  My reason for suggesting what I did is that I only see this error on my systems when the nVidia drivers are not installed.

What type of keyboard/mouse do you have?  PS2, USB, Bluetooth?

If you

grep "input device" /var/log/Xorg.0.log | grep XINPUT

what do you get?

On one system I have a USB keyboard/mouse combination and I see...

[egreshko@meimei log]$ grep "input device" Xorg.0.log | grep XINPUT
[338349.680] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[338349.680] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[338349.682] (II) XINPUT: Adding extended input device "Logitech M310" (type: MOUSE, id 8)
[338349.683] (II) XINPUT: Adding extended input device "Logitech K520" (type: KEYBOARD, id 9)

While on my laptop I see....

[egreshko@acer log]$  grep "input device" Xorg.0.log | grep XINPUT
[    64.585] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[    64.594] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[    64.606] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 8)
[    64.615] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 9)
[    64.627] (II) XINPUT: Adding extended input device "Acer CrystalEye webcam" (type: KEYBOARD, id 10)
[    64.695] (II) XINPUT: Adding extended input device "Logitech Optical USB Mouse" (type: MOUSE, id 11)
[    64.759] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 12)
[    64.777] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 13)
[    64.795] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 14)

But, rather than picking out bits and pieces of your Xorg log file, maybe post it somewhere for everyone to see?