- This topic has 134 replies, 17 voices, and was last updated Dec 2-5:14 pm by Brian Masinick.
- Posts
PPC
@anticapitalista – installing xserver-xorg-input-synaptics and logging off and back on solved all my touchpad problems, on my netbook.
I just retested, audio works perfectly one the netbook. Pulseaudio problems (solved by toggling it off and back on) happen only on my desktop (that’s a bit quirky, with the log on problem)The package is tiny, some 200kb, so if it avoids touchpad problems, I think it would be worth being included in antix 23.1…
Xunzi_23
CMST cannot communicate with Connman on dbus
comes up all too often on my main machine which is always wired to ethernet.I did not notice the issue with older versions but that may or may not be init related or due to hardware changes,
The 2012 Device has a fast SSD for the OS, an NVME which I may take out again as it is running too cool to be reliable.I only recently fully switched to runit. Device boots from SSD very fast once the grub screens are left,
One reboot sometimes two has up to now sufficed to get a network connection.Startup and startup related setup is pure antiX which is the only system on the device. I have not played around
with wait states as no other user I support has to date asked for help with network and I have no idea where to put
waits in this case that is. All but one user wired connection at least most of the time.
Rarely TP Link dongles are used, they are, in my experience extremely reliable, exactly the opposite to often fitted
internal broadcom crap which is a pain. Pretty much any of the RaLink chipped devices is good, the ones with external
aerials vastly superior to internal hardware especially if on a USB extension cable and placed in free space..Ralink also provides GNU General Public License-licensed (GPL) drivers for the Linux kernel. Which is why I recommend.
- This reply was modified 3 weeks, 2 days ago by Xunzi_23.
anticapitalista@anticapitalista – installing xserver-xorg-input-synaptics and logging off and back on solved all my touchpad problems, on my netbook.
I just retested, audio works perfectly one the netbook. Pulseaudio problems (solved by toggling it off and back on) happen only on my desktop (that’s a bit quirky, with the log on problem)The package is tiny, some 200kb, so if it avoids touchpad problems, I think it would be worth being included in antix 23.1…
It has caused a problem -see this thread
https://www.antixforum.com/forums/reply/117794/
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
It has caused a problem
I did not remember that post, sorry.
I did try creating the entry D.O. suggested:but it might be nice to have a default libinput.conf file with some options, particularly for enabling tap-to-click.
/etc/X11/xorg.conf.d/30-touchpad-libinput.conf
Section “InputClass”
Identifier “touchpad”
Driver “libinput”
MatchIsTouchpad “on”
Option “Tapping” “on”
EndSectionOn antiX 23.1 v2 Live (I have not installed it), that had the unexpected effect of putting antiX, when closing or opening the OS, on an endless cycle, always repeating the same X message. I had to re-burn the ISO to the USB pen-drive to be able to boot from it, after trying that change.
IMPORTANT NOTE: The real problem with my netbook’s touch-pad is that, in antiX 23.1 v2, the “Tap to left click” is disabled. I noticed that the left click button on the touch-pad is physically damaged (i.e. not working), I’m so used to just tapping the touch-pad that I only noticed that when tapping failed to work AND the left button also failed.Any idea on what caused the loop and why it persisted after reboot (I don’t have persistence configured)? I just did:
cd /etc/X11/xorg.conf.d/ sudo geany 30-touchpad-libinput.confand pasted D.O.’s suggested content for the file. Saved the file and tried to log off and back on… That was when I got stuck on a loop.
P
- This reply was modified 3 weeks, 2 days ago by PPC.
abc-nix
It has caused a problem -see this thread
I think this is related to systems without slimski. When using slimski, the package xserver-xorg-input-synaptics should not be problematic.
As antiX full uses slimski, I think this package should be included.If I am mistaken, please ignore this message.
anticapitalistaxserver-xorg-input-synaptics is included on antiX-23 (the released one) and @PPC reported issues so it must be something else.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
dolphin_oraclelibinput is the new standard, synaptics being no longer developed. newer hardware, including some late model thinkpads, won’t work with synaptics, and conversly libinput works on my old 32 bit netbooks still.
maybe there is some artifact from the cut-and-paste. I’m attaching the file directly.
- This reply was modified 3 weeks, 1 day ago by dolphin_oracle.
blur13Usually with EFI you can choose what OS to boot if you have more than one OS installed.
Is there a way to reliably control the EFI boot options and the boot order of these from the software side? On my system there are no UEFI options in the BIOS, and pressing F10 on startup to access the boot options produces a menu that contains old operating systems no longer installed, and in a seemingly random order. I installed REfind and running that a couple of times, by sheer luck (as far as I could tell) managed to get the antiX install to the top of the boot priority so that it auto-boots on startup. I dread the day I install antiX 25 and have to go through this process again. As it stands, its almost worth keeping antiX 23 since its now the default EFI boot and use grub in antiX 23 to access other installed operating systems.
Robin
Have you tried efibootmgr?
sudo apt-get install efibootmgrIts -o command line option allows you to change the boot order on efi systems.
Windows is like a submarine. Open a window and serious problems will start.
techoreYou can also use ‘efibootmgr’ to list, then for each entry you want to remove, use ‘-B’. My preference is to select based on the boot entry number which is done using ‘-b’. For example if Windows 10 is boot entry 0000, then
efibootmgr -B -b 0000- This reply was modified 3 weeks ago by techore.
xserver-xorg-input-synaptics is included on antiX-23 (the released one) and @PPC reported issues so it must be something else.
Ok.
As dolphin_oracle said, libinput is the future. It is also the only method for wayland. As time goes by, other xserver-xorg-input options will all meld into libinput.
- This reply was modified 3 weeks ago by abc-nix.
blur13@Robin @techore
Thank you! That worked like a charm. When I was struggeling with this back in august I had no clue about EFI, boot order, boot entries, so I lacked the terminology to even conduct internet searches effectively. I made the connection that the “F10: boot menu” presented at startup must be the EFI boot entries when reading this thread. This has been added to my collection of useful linux tips.
techoreGlad I could help.
maybe there is some artifact from the cut-and-paste. I’m attaching the file directly.
Many thanks, D.O. – I just now tested your config file on my netbook – tap to clip now works perfectly!
Almost perfect – still missing: the “scroll bar” part of the touch-pad just acts as normal touch-pad space (i.e. – moves the mouse pointer, but does not “scroll” anything. Is there any setting that can be added to that config file to solve that? I’m currently searching on-line…P.
Ok, found it:
30-touchpad-libinput.conf requires this line:Option "ScrollMethod" "edge"Without it, I found out the touch-pad still works… with a 2 fingers gesture – that I didn’t even know this crappy old netbook supported: hold a finger in the middle of the touch-pad, drag another vertically or horizontally – it’s cool, but too much work…
With this changes, antiX 23.1 works perfectly on this netbook (on the desktop, pipewire only works after being toggled off and back on, and the problem of auto-log in not working is present on this version, and was not present in the first one- it’s not a big deal, I’m used to it, but I know that strange bug has a solution because antiX 23.1 v1 worked perfectly on that hardware).
Not perfect, but, with the correct touch-pad config file, this version is pretty good!
P.
- You must be logged in to reply to this topic.