WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: No keyboard in X  (Read 7009 times)

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 11590
Re: No keyboard in X
« Reply #15 on: January 05, 2019, 07:17:03 PM »
Hi julspower
Quote
what gets created when I put my other dongle in?
Possibly a driver that the non-working one needs? Try running:
Code: [Select]
lsmod > badmouse.txtwith it not working. Then plug in the other dongle so the mouse works and run:
Code: [Select]
lsmod > goodmouse.txtCompare the two files to see if anything new was loaded.

julspower

  • Guest
Re: No keyboard in X
« Reply #16 on: January 05, 2019, 07:28:22 PM »
thanks for pointing that
evdev wasn't loaded when its not working
If I get a console in ssh and I modprobe evdev everything is fine
A possible workaround is make it load with the .xsession script

Offline gatorback

  • Newbie
  • *
  • Posts: 17
Re: No keyboard in X
« Reply #17 on: February 16, 2020, 11:31:31 AM »
Code: [Select]
sudo modprobe evdev
Enables the K400 keyboard and trackpad in the PiCore GUI, however, despite:

filetool.sh -b

does not survive reboot. To overcome the reboot hurdle add the instruction:

Code: [Select]
echo "sudo modprobe evdev" >> /opt/bootlocal.sh
save the instruction to survive reboot:

Code: [Select]
filetool.sh -b
Raspberry Pi Zero W

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 11590
Re: No keyboard in X
« Reply #18 on: February 16, 2020, 11:57:12 AM »
Hi gatorback
Code: [Select]
sudo modprobe evdev
Enables the K400 keyboard and trackpad in the PiCore GUI, however, despite:

filetool.sh -b

does not survive reboot.
...
That's because you can't backup the memory that a driver was loaded into. The  filetool.sh  command only backs up files. I don't think
a driver that you  modprobe  manually would survive a reboot in any Linux.