I could use some help and don't tell me to look here:

https://www.thinkwiki.org/wiki/Problem_ … tch_noises

Tried this already...

First solution:

doas usermod -aG input [USERNAME]

$ doas nano  /etc/X11/xorg.conf.d/00-touchpad.conf

ection "InputClass"
        Identifier      "laplet touchpad"
        MatchIsTouchpad "yes"
        Driver          "synaptics"
        Option          "ClickPad"              "yes"
#       Option          "Device"                "/dev/input/event19"
        Option          "HorizEdgeScroll"       "yes"
        Option          "LockedDrags"           "no"
        Option          "PalmDetect"            "yes"
        Option          "PalmMinWidth"          "8"
        Option          "PalmMinZ"              "100"
        Option          "Protocol"              "auto-dev"
        Option          "TapButton1"            "1"
        Option          "TapButton2"            "3"
        Option          "TapButton3"            "2"
        Option          "TouchpadOff"           "0"
        Option          "VertEdgeScroll"        "yes"
EndSection

Second solution:

doas usermod -aG input [USERNAME]

Solved. Just had to set it up.

    Touchpad Synaptics - ArchWiki https://wiki.archlinux.org/title/Touchpad_Synaptics

$ doas nano /etc/X11/xorg.conf.d/70-synaptics.conf

Section "InputClass"
        Identifier      "touchpad"
        Driver          "synaptics"
        MatchIsTouchpad "on"
EndSection

Do I need to download drivers xenocara-input-synaptics ? Or is this configuration sufficient?

The question is: Are you using Trisquel WITH GNU/Linux-libre kernel or with its default kernel? In its default Trisquel is NOT using GNU/Linux-libre and therefore I highly doubt that entry from h-node and its outcome. Perhaps I'm not right, but with the current information there is not much more to be done for the moment. You can perhaps also tryout to use a different software-package instead of simple-scan. If this is not working, we need to remove it.

But that point stands: Trisquel is not using GNU/Linux-libre so far and therefore is also not really comparable with other systems.

$sane-find-scanner
....
found USB scanner (vendor=0x04b8, product=0x0160 [Epson DS-70]) at libusb:001:014
....

$groups
sys wheel network video audio optical storage scanner input power users

$pacman -Ss sane 
extra/perl-common-sense 3.75-1
    Implements some sane defaults for Perl programs
extra/perl-file-slurp-tiny 0.004-1
    A simple, sane and efficient file slurper
extra/sane 1.0.31-2 [installed]
    Scanner Access Now Easy
extra/xsane 0.999-2
    A GTK-based X11 frontend for SANE and plugin for Gimp.
extra/xsane-gimp 0.999-2
    XSane Gimp plugin

The problem is that scanner is not found using simple-scan.

Aditional info:
Scanner is working with Linux-libre kernel: https://h-node.org/scanners/view/en/2362/DS-70 by installing libsane
Scanner is listed working with complete support at: http://www.sane-project.org/sane-mfgs.html

I am using a librebooted x200, so as described here, I need to install powertop and start it at boot.

As the instructions given in the site doesn't apply to an alternative init system like openrc, I needed to find another method.

Furthermore, I have to disable the use of powertop in two external usb devices, so the commands I need to run in boot time are:

/usr/sbin/powertop --auto-tune
echo 'on' > '/sys/bus/usb/devices/1-2.2/power/control';
echo 'on' > '/sys/bus/usb/devices/1-2.5/power/control';

I tried to add them in cron like this:

@reboot /usr/sbin/powertop --auto-tune
@reboot echo on | doas /sys/bus/usb/devices/1-2.2/power/control
@reboot echo on | doas /sys/bus/usb/devices/1-2.5/power/control

but although powertop starts, the 2nd and 3d command don't work. (Also I have tried more compinations with or without doas.)

What I ended up doing, and it worked, was to add the commands to ~/.xinitrc and also adjusting the /etc/doas.conf accordingly. I don't like messing with doas.conf though, and maybe there is something new for me to learn, so my question is if there is a better (more secure?) alternative for this.

The keyboard that I am currently trying to replace is for a desktop, but I suppose the same questions may apply to laptop keyboards.  The aspect that particularly concerns me, and which I think I lack some understanding is the difference between older systems that use PS2 and newer systems that use USB.  Is there any kind of security risk with USB keyboards?  How would I know if the firmware in such a keyboard is one that can be trusted?  Is it better or safer to use a PS2 keyboard?  Is there any difference between PS2 and USB in the operating system?  I am guessing that in Hyperbola I am using only free drivers for a keyboard device, so does that make me safer against potentially getting exposed to a malicious firmware?

Also with many of the USB keyboards, especially the gaming keyboards, there appears to be a set of opensource tools for programming the keyboard firmware, I am not sure if these are totally freedom respecting.  They refer to these as QMK and VIA.  QMK (quantum mechanical keyboard) is a software project that allows users to build their own firmware and load them into the keyboard.  VIA I think enables commands to be sent to the keyboard firmware, but what scares me with this is that it is meant to work through the web browser (Chrome mostly).  Good or bad?  What are the pros and cons of these tools?

In the end I like Hyperbola and the philosophy to keep the system simple to the degree where I can have understanding and control over what it does for me.  For instance when using a USB memory device, I have come to like mounting it myself just using the 'doas mount' command, that way I only connect to a device I have some knowledge about where it comes from.  I used to automount, but now I have concerns.  Though I suppose USB memory and the firmware on USB devices is a related topic, usb hard drives too.  And the firmware in any USB device I suppose could pretend to be a keyboard, so wondering a little how to gain control over preventing or minimizing those situations?  Is there anything special I should be doing to secure the keyboard connection in configuration of Hyperbola?

Maybe I don't know all the right questions to ask here.  Maybe also some questions are pretty basic and just lack of knowledge on my side, though I suspect others might have some gaps they would like filled in on too.  So definetly would be interested to hear any insights on this from the community.

I cannot flash any libreboot roms onto my system.

Its very annoying... is this a kernel issue or flashrom issue?

Or is it something else...?

we think it is about time to clear up this point: HyperbolaBSD will be ONLY supporting the x86-platform!
Even though right from the start we first will even go with x86_64 (64bit) for further implementation and enhancments. 32bit can get there later on.

Nevertheless overall here in the forums people write down wishes for other CPU-architectures and more. So we make this clear: This won't be there at a point without further financial support and donations. Please respect that we are only a small team and we cannot work full-time on so many different architectures. It took a long time even to get towards the point we are for now with porting and we won't make any kind of further tryout to get this bigger as we can manage.

So again: No further CPU-architectures are planned for HyperbolaBSD!
You want more? You have time to support us implementing and testing? Feel welcome. But please no further illusions and dreamcastle-constructions with hearsaying about possible platforms. And remember that Hyperbola is free and libre software: So you can always take the code and startup with poring-efforts. For more CPU-architectures there is also hardware needed.

Thank you!

https://libreboot.org/news/libreboot20220710.html