On 04/04/2018 03:09 PM, sean darcy wrote: > New install of F27, with Xfce. startx fails without an error on the > console. Xorg.0.log has: > > > .... > [ 2930.626] (II) modesetting: Driver for Modesetting Kernel Drivers: kms > [ 2930.626] (II) FBDEV: driver for framebuffer: fbdev > [ 2930.626] (II) VESA: driver for VESA chipsets: vesa > [ 2930.626] xf86EnableIOPorts: failed to set IOPL for I/O (Operation > not permitted) > [ 2930.626] (II) [KMS] Kernel modesetting enabled. > [ 2930.626] (WW) Falling back to old probe method for modesetting > [ 2930.626] (WW) Falling back to old probe method for fbdev > [ 2930.626] (II) Loading sub module "fbdevhw" > [ 2930.626] (II) LoadModule: "fbdevhw" > [ 2930.626] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so > [ 2930.626] (II) Module fbdevhw: vendor="X.Org Foundation" > [ 2930.626] compiled for 1.19.6, module version = 0.0.2 > [ 2930.626] ABI class: X.Org Video Driver, version 23.0 > [ 2930.626] (EE) open /dev/fb0: Permission denied > [ 2930.626] (WW) Falling back to old probe method for vesa > [ 2930.626] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card > support > [ 2930.626] (II) RADEON(0): Creating default Display subsection in > Screen section > ....... > > No other errors or warnings. Are you starting it as root or as your mortal self (unprivileged)? Try it as your mortal self and not root. It should work either way, but try it anyway. The "permission denied" error on /dev/fb0 is odd. You should check the permissions of /dev/fb0. It should be a character device, major 29, minor 0, owner "root", group "video" with permissions of "660" (rw-rw----): [root@golem4 bin]# ls -l /dev/fb0 crw-rw----. 1 root video 29, 0 Apr 2 09:43 /dev/fb0 I believe it's created at boot time (at least mine all seem to have the timestamp of the last machine boot). It also appears that you're using a Radeon (AMD) card. I don't have a lot of experience with them (mostly nVidia and Intel here), so perhaps you don't have the driver installed? Someone smarter than I would need to address that. The final thing I'd validate is that if you have an /etc/X11/xorg.conf file, rename or move it and let the system sort things out without the help of that file. > Xorg kept going finishing the display section and loading the mouse etc. > and just terminates: > > > [ 2930.990] (II) XINPUT: Adding extended input device "SynPS/2 > Synaptics TouchPad" (type: TOUCHPAD, id 11) > [ 2930.991] (**) Option "AccelerationScheme" "none" > [ 2930.991] (**) SynPS/2 Synaptics TouchPad: (accel) selected scheme > none/0 > [ 2930.991] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration > factor: 2.000 > [ 2930.991] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration > threshold: 4 > [ 2930.992] (II) event4 - SynPS/2 Synaptics TouchPad: is tagged by > udev as: Touchpad > [ 2930.992] (II) event4 - SynPS/2 Synaptics TouchPad: device is a > touchpad > [ 2930.993] (II) config/udev: Adding input device SynPS/2 Synaptics > TouchPad (/dev/input/mouse0) > [ 2930.993] (II) No input driver specified, ignoring this device. > [ 2930.993] (II) This device may have been added with another device file. > [ 2930.997] (II) config/udev: Adding input device Toshiba WMI hotkeys > (/dev/input/event7) > [ 2930.997] (II) No input driver specified, ignoring this device. > [ 2930.997] (II) This device may have been added with another device file. > [ 2931.474] (**) Option "fd" "24" > [ 2931.474] (II) event2 - Power Button: device removed > [ 2931.474] (**) Option "fd" "27" > [ 2931.474] (II) event5 - Video Bus: device removed > [ 2931.475] (**) Option "fd" "28" > [ 2931.475] (II) event1 - Power Button: device removed > [ 2931.475] (**) Option "fd" "29" > [ 2931.475] (II) event6 - TOSHIBA Web Camera - MP: TOSHIB: device removed > [ 2931.475] (**) Option "fd" "30" > [ 2931.475] (II) event3 - AT Translated Set 2 keyboard: device removed > [ 2931.475] (**) Option "fd" "31" > [ 2931.475] (II) event4 - SynPS/2 Synaptics TouchPad: device removed > [ 2931.478] (II) UnloadModule: "libinput" > [ 2931.478] (II) systemd-logind: releasing fd for 13:68 > [ 2931.495] (II) UnloadModule: "libinput" > [ 2931.495] (II) systemd-logind: releasing fd for 13:67 > [ 2931.502] (II) UnloadModule: "libinput" > [ 2931.502] (II) systemd-logind: releasing fd for 13:70 > [ 2931.517] (II) UnloadModule: "libinput" > [ 2931.517] (II) systemd-logind: releasing fd for 13:65 > [ 2931.529] (II) UnloadModule: "libinput" > [ 2931.529] (II) systemd-logind: releasing fd for 13:69 > [ 2931.550] (II) UnloadModule: "libinput" > [ 2931.550] (II) systemd-logind: releasing fd for 13:66 > [ 2931.589] (II) Server terminated successfully (0). Closing log file. Yeah, that's likely. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@xxxxxxxxxxxxxx - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - You can lead a horse to water, but if you can teach him to roll - - over and float on his back...you got something! - ---------------------------------------------------------------------- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
