[prev in list] [next in list] [prev in thread] [next in thread]
List: freedesktop-xorg
Subject: Re: Bringing up a raspi in a machine shop environment.
From: Peter Hutterer <peter.hutterer () who-t ! net>
Date: 2016-12-07 21:47:22
Message-ID: 20161207214722.GA20676 () jelly
[Download RAW message or body]
On Wed, Dec 07, 2016 at 01:22:26PM -0500, Gene Heskett wrote:
> Greetings folks;
>
> From the current Xorg.0.log:
> ===========
> [ 10.932] (II) AIGLX: Screen 0 is not DRI2 capable
> [ 10.932] (EE) AIGLX: reverting to software rendering
> [ 11.824] (II) AIGLX: Loaded and initialized swrast
> [ 11.824] (II) GLX: Initialized DRISWRAST GL provider for screen 0
> ===========
> Is this normal on a raspi-3b, or do I need to install a better driver?
>
> And:
> ====================
> [ 12.144] (II) config/udev: Adding input device MOSART Semi. 2.4G RF
> Keyboard & Mouse (/dev/input/event1)
> [ 12.144] (**) MOSART Semi. 2.4G RF Keyboard & Mouse: Applying
> InputClass "evdev pointer catchall"
> [ 12.144] (**) MOSART Semi. 2.4G RF Keyboard & Mouse: Applying
> InputClass "evdev keyboard catchall"
> [ 12.144] (II) Using input driver 'evdev' for 'MOSART Semi. 2.4G RF
> Keyboard & Mouse'
> [ 12.144] (**) MOSART Semi. 2.4G RF Keyboard & Mouse: always reports
> core events
> [ 12.144] (**) evdev: MOSART Semi. 2.4G RF Keyboard & Mouse:
> Device: "/dev/input/event1"
> [ 12.144] (--) evdev: MOSART Semi. 2.4G RF Keyboard & Mouse: Vendor
> 0x3938 Product 0x1032
> [ 12.145] (--) evdev: MOSART Semi. 2.4G RF Keyboard & Mouse: Found 9
> mouse buttons
> [ 12.145] (--) evdev: MOSART Semi. 2.4G RF Keyboard & Mouse: Found
> scroll wheel(s)
> [ 12.145] (--) evdev: MOSART Semi. 2.4G RF Keyboard & Mouse: Found
> relative axes
> [ 12.145] (--) evdev: MOSART Semi. 2.4G RF Keyboard & Mouse: Found x
> and y relative axes
> [ 12.145] (--) evdev: MOSART Semi. 2.4G RF Keyboard & Mouse: Found
> absolute axes
> [ 12.145] (II) evdev: MOSART Semi. 2.4G RF Keyboard & Mouse: Forcing
> absolute x/y axes to exist.
> [ 12.145] (--) evdev: MOSART Semi. 2.4G RF Keyboard & Mouse: Found
> keys
> [ 12.145] (II) evdev: MOSART Semi. 2.4G RF Keyboard & Mouse:
> Configuring as mouse
> [ 12.145] (II) evdev: MOSART Semi. 2.4G RF Keyboard & Mouse:
> Configuring as keyboard
> [ 12.145] (II) evdev: MOSART Semi. 2.4G RF Keyboard & Mouse: Adding
> scrollwheel support
> [ 12.145] (**) evdev: MOSART Semi. 2.4G RF Keyboard & Mouse:
> YAxisMapping: buttons 4 and 5
> [ 12.145] (**) evdev: MOSART Semi. 2.4G RF Keyboard & Mouse:
> EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
> [ 12.145] (**)
> Option "config_info" \
> "udev:/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2.1/1-1.2.1:1.1/0003:3938:1032.0002/input/input1/event1"
> [ 12.145] (II) XINPUT: Adding extended input device "MOSART Semi. 2.4G
> RF Keyboard & Mouse" (type: KEYBOARD, id 7)
> [ 12.145] (**) Option "xkb_rules" "evdev"
> [ 12.145] (**) Option "xkb_model" "pc105"
> [ 12.145] (**) Option "xkb_layout" "gb"
> [ 12.146] (II) evdev: MOSART Semi. 2.4G RF Keyboard & Mouse:
> initialized for relative axes.
> [ 12.146] (WW) evdev: MOSART Semi. 2.4G RF Keyboard & Mouse: ignoring
> absolute axes.
> [ 12.146] (**) MOSART Semi. 2.4G RF Keyboard & Mouse: (accel) keeping
> acceleration scheme 1
> [ 12.146] (**) MOSART Semi. 2.4G RF Keyboard & Mouse: (accel)
> acceleration profile 0
> [ 12.146] (**) MOSART Semi. 2.4G RF Keyboard & Mouse: (accel)
> acceleration factor: 2.000
> [ 12.147] (**) MOSART Semi. 2.4G RF Keyboard & Mouse: (accel)
> acceleration threshold: 4
> [ 12.148] (II) config/udev: Adding input device MOSART Semi. 2.4G RF
> Keyboard & Mouse (/dev/input/mouse0)
> [ 12.148] (II) No input driver specified, ignoring this device.
> [ 12.148] (II) This device may have been added with another device
> file.
> ===========================
> this is I believe, a touchpad and is part of the cheap keyboard, and
> located where ones right little finger often touches it as I'm typing
> and causes tons of miss-fires, focus stealing and other hate and
> discontent. Can this PITA be disabled/ignored? It seems to be slow for
> a mouse, but very sensitive to a touch, so I am not convinced that a
> sheet of lexan glued above it would disable the touch functions.
see this section here:
https://fedoraproject.org/wiki/Input_device_configuration#Blacklisting_a_device
Cheers,
Peter
_______________________________________________
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic