# Anyone have "gpm" working on the DevTerm

**URL:** <https://forum.clockworkpi.com/t/anyone-have-gpm-working-on-the-devterm/8871>\
**Category:** DevTerm\
**Tags:** console, r-01\
**Created:** [August 30, 2022, 7:43pm UTC](https://forum.clockworkpi.com/t/anyone-have-gpm-working-on-the-devterm/8871 "2022-08-30T19:43:13Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![ChipMaster](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/chipmaster/32/6412_2.png) [@ChipMaster](https://forum.clockworkpi.com/u/ChipMaster)\
**Post date:** [August 30, 2022, 7:43pm UTC](https://forum.clockworkpi.com/t/anyone-have-gpm-working-on-the-devterm/8871/1 "2022-08-30T19:43:13Z")

</div>

I’m building [TWIN](https://sourceforge.net/projects/twin/) on my DevTerm + R-01. It makes use of a mouse, so to make it work in _console_ mode I need `gpm` running. It says it can’t find `/dev/input/mice` when it tries to start. I’ve never really used `gpm` before. But when I’ve seen it launch in the past its been painless. I suspect this has to do with the way the trackball is wired in.

I thought I’d reach out and see if anyone has this working before I go for the _deep-dive_.

---

<div class="post-metadata">

**Author:** ![ChipMaster](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/chipmaster/32/6412_2.png) [@ChipMaster](https://forum.clockworkpi.com/u/ChipMaster)\
**Post date:** [August 31, 2022, 5:18pm UTC](https://forum.clockworkpi.com/t/anyone-have-gpm-working-on-the-devterm/8871/2 "2022-08-31T17:18:52Z")

</div>

A follow up for anyone looking or caring. I found that Xorg is using `/dev/input/event5` for the mouse device. It doesn’t mention what protocol its using. So I haven’t been able to get `gpm` to behave yet. Perhaps the DevTerm keyboard+mouse is doing its own thing, since `gpm` fails to understand the input with the most common mice types.

Hopefully I’ll get some time to nail it down…

---

<div class="post-metadata">

**Author:** ![ChipMaster](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/chipmaster/32/6412_2.png) [@ChipMaster](https://forum.clockworkpi.com/u/ChipMaster)\
**Post date:** [September 12, 2022, 5:30pm UTC](https://forum.clockworkpi.com/t/anyone-have-gpm-working-on-the-devterm/8871/3 "2022-09-12T17:30:38Z")

</div>

I must be the only one trying to run the DevTerm outside of X…

I’ve found the kernel does not have the `input mouse` (CONFIG\_INPUT\_MOUSE) driver enabled. `gpm` is not apparently compatible with the raw event interface. Or I just haven’t found the documentation for it. I’ll probably have to look into the source or figure out how to rebuild the kernel…

---

<div class="post-metadata">

**Author:** ![andypiper](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/andypiper/32/7970_2.png) [@andypiper](https://forum.clockworkpi.com/u/andypiper)\
**Post date:** [September 13, 2022, 9:23pm UTC](https://forum.clockworkpi.com/t/anyone-have-gpm-working-on-the-devterm/8871/4 "2022-09-13T21:23:49Z")

</div>

> [@ChipMaster](#):
>
> I must be the only one trying to run the DevTerm outside of X…

I’ve been back and forth on this - like you, super frustrated by the lack of `gpm` on the R01, but it works on the CM4, which is a lot more promising.

Good sleuthing on what could be behind the problem on the R01 - I need to try another kernel build or have another go at building a new OS image from scratch.

---

<div class="post-metadata">

**Author:** ![andypiper](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/andypiper/32/7970_2.png) [@andypiper](https://forum.clockworkpi.com/u/andypiper)\
**Post date:** [September 13, 2022, 9:26pm UTC](https://forum.clockworkpi.com/t/anyone-have-gpm-working-on-the-devterm/8871/5 "2022-09-13T21:26:25Z")

</div>

Have you applied the alternative keyboard firmware(s), by the way? I’m using @yatli firmware from [somewhere in this thread](https://forum.clockworkpi.com/t/devterm-keyboard-firmware-mod-hot-mode-switching-gear-switching/8431/).

---

<div class="post-metadata">

**Author:** ![ChipMaster](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/chipmaster/32/6412_2.png) [@ChipMaster](https://forum.clockworkpi.com/u/ChipMaster)\
**Post date:** [September 14, 2022, 12:04am UTC](https://forum.clockworkpi.com/t/anyone-have-gpm-working-on-the-devterm/8871/6 "2022-09-14T00:04:25Z")

</div>

> Have you applied the alternative keyboard firmware(s)

No, I have not. Sooo many things… Sooo little time. 😉 I have to figure out how to get access to the physical I2C bus so I can put in a DS3231 to keep it on track with time w/o iNet. That will get me the minimum hardware functionality I need to be able to use this on a daily basis. Then I have to rewrite a few programs in C++ since FreePascal (FPC) hasn’t got on board with RISC-V yet and I originally wrote them in FPC for my PocketCHIP.

Much to do.

Is there some compelling reason I should try to upgrade the firmware in my keyboard?

I think when I solve my _break out_ issue I might take a whack at patching the kernel sources together and enabling the mouse support. That should be another large time-suck. It will be nice if the driver can be supplied as a module. But I need to see the menu to know if that’s an option. I wonder how many days it will take to compile the whole kernel… 😉

---

<div class="post-metadata">

**Author:** ![garabik](https://avatars.discourse-cdn.com/v4/letter/g/5e9695/32.png) [@garabik](https://forum.clockworkpi.com/u/garabik)\
**Post date:** [October 5, 2022, 4:42pm UTC](https://forum.clockworkpi.com/t/anyone-have-gpm-working-on-the-devterm/8871/7 "2022-10-05T16:42:51Z")

</div>

For the record, I just installed `gpm` and it run fine with the default settings here (A06), with `/dev/input/mice`

---

<div class="post-metadata">

**Author:** ![ChipMaster](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/chipmaster/32/6412_2.png) [@ChipMaster](https://forum.clockworkpi.com/u/ChipMaster)\
**Post date:** [October 5, 2022, 5:05pm UTC](https://forum.clockworkpi.com/t/anyone-have-gpm-working-on-the-devterm/8871/8 "2022-10-05T17:05:20Z")

</div>

Thanks for this. This helps to confirm the issue is the RISC-V kernel is missing the appropriate driver. Maybe I can get some time this weekend to see about building a module…
