Project

General

Profile

Actions

Bug #837

closed

VideoFE not working with 5.10.y kernel

Added by Hammel over 3 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Immediate
Assignee:
Category:
Configuration
Start date:
17 Apr 2021
Due date:
% Done:

100%

Estimated time:
Severity:
01 - Critical

Description

The interface via the touchscreen is not working. Touch is not enabled (or shouldn't be) in videofe. So the keyboard should be the only controller. But the arrow keys don't work. Typing in a video name does. But if you touch the screen then things go really bad really fast.

The keyboard arrow keys should be an easy fix. See the related issues for help on the keys.

I need to run xev on an 4.19.y build and see what those keys map to.
Then do the same on 5.10.y.


Files

keys-4.19.y.txt (2.5 KB) keys-4.19.y.txt Hammel, 17 Apr 2021 14:40
keys-5.10.y.txt (2.25 KB) keys-5.10.y.txt Hammel, 17 Apr 2021 14:40

Related issues

Related to PiBox - Action Item #629: Verify Rii mini X1 keyboard worksClosedHammel18 May 2018

Actions
Actions #1

Updated by Hammel over 3 years ago

  • Description updated (diff)
Actions #2

Updated by Hammel over 3 years ago

Attached are the two key mappings from xev. They show that the 4.19.y kernel has proper keysyms for the keyboard, but the 5.10.y do not. However, both kernels provide the same keycodes since those likely come directly from the keyboard.

FAVI keyboard is mapped using xmodmap in /etc/X11/xinitrc:

# If using the Favi keyboard, adjust mouse acceleration
# and remap Arrow Keys to KeyPad arrow keys
# This remap only works on PiBox/RaspberryPi cuz the keycodes
# are different on other distributions.
if [ -f /etc/init.d/data/usb.list ]
then
    FAVI=`grep 1997:2433 /etc/init.d/data/usb.list`
    if [ "$FAVI" != "" ]
    then
        xinput --set-prop 6 'Device Accel Constant Deceleration' 2
        xmodmap -e 'keycode 198=KP_Up'
        xmodmap -e 'keycode 200=KP_Left'
        xmodmap -e 'keycode 201=KP_Right'
        xmodmap -e 'keycode 204=KP_Down'
    else
        xinput --set-prop 6 'Device Accel Constant Deceleration' 3
    fi
else
    xinput --set-prop 6 'Device Accel Constant Deceleration' 3
fi

This means that the FAVI is not being seen in the usb.list. A quick check of usb.list shows that it does NOT have the FAVI in it, though if you run lsusb manually it shows up. So the lsusb that generates the usb.list is run before the keyboard is found.

The fix is to run lsusb in xinitrc manually instead of relying on usb.list, since usb.list is generated before all drivers are loaded.

Actions #3

Updated by Hammel over 3 years ago

  • Status changed from In Progress to Closed
  • % Done changed from 50 to 100

That fix worked. The fix went into pmsui, which contains the xinitrc used or the media player (and other) systems.

Tested, committed and pushed.

Closing issue.

Actions

Also available in: Atom PDF