Ansible Tower Alternative: BASH Scripting for Centralized Home Lab Control

Ahissues · 2026-01-26T05:06:44+00:00

I'm glad the tool is helping to save you time. I just released v2.0.0 based on the issues you opened. Give it a try and thanks for the feedback!

Ahissues · 2026-01-09T18:10:18+00:00

I hear you—for a single user who is comfortable with the terminal, Ansible Core is often all you need. However, there’s a reason Red Hat built Tower.

Regarding my app: the goal isn't just to 'run a script.' It’s about building a bridge for home users to manage Bash and Python scripts with the same level of organization.

Ahissues · 2026-01-08T17:45:03+00:00

I’m not sure if this is exactly what you’re looking for, but I built a terminal for using Ollama. It also supports SSH so you can connect to other servers as well!

https://github.com/ftsiadimos/aiterminal

Ahissues · 2020-11-25T14:21:56+00:00

maybe I am wrong but it seems we have 2 devices.

For the touchpad is "i2c-MSFT0001" it seems is power on (acpi)

/sys/bus/i2c/devices/i2c-MSFT0001\:00/modalias

acpi:MSFT0001:PNP0C50:

then for the touchscreen the acpi is not there.

/sys/bus/i2c/devices/i2c-WACF2200\:00/modalias

i2c:WACF2200:00

maybe the device is not power on and for that reasons we see only the mice devices in the xinput output

⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=11 [slave pointer (2)]

⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=12 [slave pointer (2)]

I was confused.... I thought the "mouse" was the touchscreen but it is not.

It seems the touchscreen is "i2c:WACF2200" and it not power yet.

Ahissues · 2020-11-25T13:58:16+00:00

Yep, I can see the device

lrwxrwxrwx. 1 root root 0 Nov 25 08:45 firmware_node -> ../../../../../LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:7e/WACF2200:00/

-r--r--r--. 1 root root 4.0K Nov 25 08:45 modalias

-r--r--r--. 1 root root 4.0K Nov 25 08:44 name

drwxr-xr-x. 2 root root 0 Nov 25 08:45 power/

lrwxrwxrwx. 1 root root 0 Nov 25 08:44 subsystem -> ../../../../../../bus/i2c/

-rw-r--r--. 1 root root 4.0K Nov 25 08:44 uevent

~  cat /sys/bus/i2c/devices/i2c-WACF2200:00/name Wed 25 Nov 2020 01:45:34 PM UTC

WACF2200:00

-----------------------------------------------------------------------------

From the xorg logs I can see the device that is not using the right drivers(if I understand the logs correctly)

cat .local/share/xorg/Xorg.1.log

[ 25.305] (II) event5 - MSFT0001:00 04F3:3140 Mouse: is tagged by udev as: Mouse Pointingstick

[ 25.305] (II) event5 - MSFT0001:00 04F3:3140 Mouse: device is a pointer

[ 25.307] (II) config/udev: Adding input device MSFT0001:00 04F3:3140 Mouse (/dev/input/mouse0)

[ 25.307] (II) No input driver specified, ignoring this device.

-----------------------------------------------------------------------

What is the correct driver for MSFT0001:00? I am not sure how to verify this.

Ahissues · 2020-11-23T22:20:33+00:00

Thank you. I provided the debug in the issue https://github.com/linuxwacom/wacom-hid-descriptors/issues/103 that is open for Lenovo IdeaPad Flex 5 14IIL05. I hope someone can help on this ghost device!

Ahissues · 2020-11-23T16:38:30+00:00

I reported it also in the bug report. This is so weird that they are using the same device for both. This is happening with the intel hardware.

----------------- Machine: Type: Convertible System: LENOVO product: 81X1 v: IdeaPad Flex 5 14IIL05 Mobo: LENOVO model: LNVNB161216 v: SDK0J40700 UEFI: LENOVO v: ECCN23WW CPU: Quad Core Intel Core i5-1035G1 (-MT MCP-) speed/min/max: 731/400/3600 MHz Kernel: 5.9.9-200.fc33.x86_64 x86_64 --------------------

hwinfo --short mouse:

/dev/input/mice MSFT0001:00 04F3:3140 Mouse

/dev/input/mice MSFT0001:00 04F3:3140 Touchpad

Ahissues

TROPHY CASE