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

Ed Greshko ed.greshko at greshko.com
Tue Jul 28 07:52:37 UTC 2015


On 07/28/15 11:41, richard emberson wrote:
> ]# journalctl -b 0 | grep -i mouse
> Jul 27 19:52:02 localhost.localdomain kernel: mousedev: PS/2 mouse device common for all mice
> Jul 27 19:52:02 localhost.localdomain kernel: usb 7-1: Product: USB Optical Mouse
> Jul 27 19:52:02 localhost.localdomain kernel: input: PixArt USB Optical Mouse as /devices/pci0000:00/0000:00:1d.1/usb7/7-1/7-1:1.0/0003:093A:2510.0001/input/input6
> Jul 27 19:52:02 localhost.localdomain kernel: hid-generic 0003:093A:2510.0001: input,hidraw0: USB HID v1.11 Mouse [PixArt USB Optical Mouse] on usb-0000:00:1d.1-1/input0
> Jul 27 19:52:02 localhost.localdomain kernel: psmouse serio1: synaptics: Touchpad model: 1, fw: 6.2, id: 0x81a0b1, caps: 0xa04711/0x200000/0x0, board id: 0, fw id: 496485
> Jul 27 19:52:49 localhost.localdomain kernel: input: MCE IR Keyboard/Mouse (ene_ir) as /devices/virtual/input/input10
> Jul 27 19:52:49 localhost.localdomain kernel: IR MCE Keyboard/mouse protocol handler initialized
> # journalctl -b 0 | grep -i keyb
> Jul 27 19:52:02 localhost.localdomain kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3
> Jul 27 19:52:49 localhost.localdomain kernel: input: MCE IR Keyboard/Mouse (ene_ir) as /devices/virtual/input/input10
> Jul 27 19:52:49 localhost.localdomain kernel: IR MCE Keyboard/mouse protocol handler initialized
>
> I appreciate the help. I've been downloading the fedora 22
> workstation and server dvds just in case.
> Re-installing my laptops is not much of a problem, its my home
> servers where I want to be sure prior to going from fedora x to x+1.
> Also, I'd like to keep using KDE, but, at least for this laptop,
> that may not be possible. 

Well, that all looks in order.

So, you are able to boot and you do get a graphical login screen, but you don't get a cursor and you can't type a password.

You looked in the fedup log, located in /var/log, and see no errors.

I'm fairly sure the lack of XINPUT lines in the Xorg log is telling....just have no idea what could be the issue.

I've not had a failure in fedup such as this and I've been using it for the past several releases.


-- 
If I wanted a blog or social media I'd go elsewhere


More information about the users mailing list