On 06/07/15 04:12 PM, William Bulley wrote: > According to Connor Behan <[email protected]> on Sat, 07/04/15 at 15:57: >> Can you post the Intel Xorg.0.log as well? > See attached. > > When I attempt to invoke an Xorg session (see below) with the VESA section > commented out and the Intel section uncommented, the "Fatal server error" was: > > (EE) no screens found(EE) > >> That's what happens when X starts without input or window managers. Try >> typing the exec line of your favourite window manager in xinitrc. To >> make sure input works, make sure you have udev and xf86-input-evdev >> installed. Also make sure the evdev kernel module is loaded. If you >> don't want to go that route, you'll have to install the older mouse and >> keyboard drivers and make corresponding sections for those in xorg.conf. > I have these two ports built and installed on this laptop: > > xf86-input-keyboard-1.8.0_7 > xf86-input-mouse-1.9.1 > > and I have these two sections in my /etc/X11/xorg.conf file: > > Section "InputDevice" > Identifier "Keyboard0" > Driver "kbd" > EndSection > > Section "InputDevice" > Identifier "Mouse0" > Driver "mouse" > Option "Protocol" "auto" > Option "Device" "/dev/sysmouse" > Option "ZAxisMapping" "4 5 6 7" > EndSection > > This is how I invoke my Xorg session (and have been doing so for over > ten years IIRC): > > % /usr/local/bin/xinit -- /usr/local/bin/Xorg -nolisten tcp -retro -bs > -ar1 350 -ar2 30 > > The last line in my .xinitrc file is this: > > /usr/local/bin/mwm 2>&1 /dev/null I don't know any firm reasons why that wouldn't work, but I can just suggest some tweaks that work for me. Do things change if you run "startx -- -nolisten tcp ..." instead of explicitly calling xinit? And do things change if you add "exec" in front of the mwm line? I would put Option "CoreKeyboard" in the keyboard section. I also have:
InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" in my ServerLayout section. Lastly, /dev/sysmouse looks new to me. If it's a valid device that's fine, but I find out what the device nodes are from looking at /proc/bus/input/devices. > I have looked high and low for anything like the "evdev kernel module" > and the xf86-input-evdev port. There is no evdev in the output of > sysctl(8), and no mention of evdev in the GENERIC kernel config file. > There is nothing starting with "ev..." in the /boot/kernel directory. If "modprobe evdev" works, you have the module, otherwise you don't. With evdev, the devices all look like "/dev/input/event*" and you don't need sections for them. You just need udev to be running. That is, "udev" should show up in ps -e output. > Here are some command line results: > > unix% locate evdev | grep '\<evdev\>$' > /usr/local/share/X11/xkb/keycodes/evdev > /usr/local/share/X11/xkb/rules/evdev > /usr/ports/devel/dbus-qt5/work/qtbase-opensource-src-5.4.1/config.tests/unix/evdev > /usr/ports/devel/dbus-qt5/work/qtbase-opensource-src-5.4.1/config.tests/unix/evdev/evdev > /usr/ports/devel/qmake5/work/qtbase-opensource-src-5.4.1/config.tests/unix/evdev > /usr/ports/devel/qt5-buildtools/work/qtbase-opensource-src-5.4.1/config.tests/unix/evdev > /usr/ports/devel/qt5-buildtools/work/qtbase-opensource-src-5.4.1/config.tests/unix/evdev/evdev > /usr/ports/devel/qt5-core/work/qtbase-opensource-src-5.4.1/config.tests/unix/evdev > /usr/ports/x11/libxkbcommon/work/libxkbcommon-0.5.0/test/data/keycodes/evdev > /usr/ports/x11/libxkbcommon/work/libxkbcommon-0.5.0/test/data/rules/evdev > /usr/ports/x11/xkeyboard-config/work/stage/usr/local/share/X11/xkb/keycodes/evdev > /usr/ports/x11/xkeyboard-config/work/stage/usr/local/share/X11/xkb/rules/evdev > /usr/ports/x11/xkeyboard-config/work/xkeyboard-config-2.14/keycodes/evdev > /usr/ports/x11/xkeyboard-config/work/xkeyboard-config-2.14/rules/evdev > /usr/ports/x11-toolkits/qt5-gui/work/qtbase-opensource-src-5.4.1/config.tests/unix/evdev > /usr/ports/x11-toolkits/qt5-widgets/work/qtbase-opensource-src-5.4.1/config.tests/unix/evdev > /usr/ports/x11-toolkits/qt5-widgets/work/qtbase-opensource-src-5.4.1/config.tests/unix/evdev/evdev > > t550% locate udev | grep '\<udev\>' > /compat/linux/etc/udev > /compat/linux/etc/udev/rules.d > /compat/linux/etc/udev/rules.d/60-raw.rules > /compat/linux/lib/udev > /compat/linux/lib/udev/rules.d > /compat/linux/lib/udev/rules.d/91-drm-modeset.rules > /usr/ports/emulators/linux_base-c6/work/etc/udev > /usr/ports/emulators/linux_base-c6/work/etc/udev/rules.d > /usr/ports/emulators/linux_base-c6/work/etc/udev/rules.d/60-raw.rules > /usr/ports/emulators/linux_base-c6/work/stage/compat/linux/etc/udev > /usr/ports/emulators/linux_base-c6/work/stage/compat/linux/etc/udev/rules.d > /usr/ports/emulators/linux_base-c6/work/stage/compat/linux/etc/udev/rules.d/60-raw.rules > /usr/ports/graphics/linux-c6-dri/work/lib/udev > /usr/ports/graphics/linux-c6-dri/work/lib/udev/rules.d > /usr/ports/graphics/linux-c6-dri/work/lib/udev/rules.d/91-drm-modeset.rules > /usr/ports/graphics/linux-c6-dri/work/stage/compat/linux/lib/udev > /usr/ports/graphics/linux-c6-dri/work/stage/compat/linux/lib/udev/rules.d > /usr/ports/graphics/linux-c6-dri/work/stage/compat/linux/lib/udev/rules.d/91-drm-modeset.rules > > unix% which evdev > evdev: Command not found. > unix% whereis evdev > evdev: > /usr/ports/devel/dbus-qt5/work/qtbase-opensource-src-5.4.1/config.tests/unix/evdev > unix% which udev > udev: Command not found. > unix% whereis udev > udev: /usr/ports/emulators/linux_base-c6/work/etc/udev > unix% pkg info | grep evdev > unix% pkg info | grep udev > unix% pwd > /usr/ports > unix% ls -ald */xf86-input-evdev > ls: No match. > unix% ls -ald */*evdev* > ls: No match. > > unix% pkg info | grep hal > hal-0.5.14_28 Hardware Abstraction Layer for simplifying > device access > unix% pkg info | grep dbus > dbus-1.8.16 Message bus system for inter-application > communication > dbus-glib-0.104 GLib bindings for the D-BUS messaging system > unix% ps agxuww | egrep hal | egrep -v egrep > unix% ps agxuww | egrep dbus | egrep -v egrep > unix% > > (that is, I am not running either dbus, or hal) > > It sure would be nice to get to the bottom of this (I would like to run > Xorg on this laptop)! :-) > > Regards, > > web... >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ [email protected]: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
