[Model? / Solus OS - Arch] Install won't let X11 load, no errors

moore-bryan commented 3 years ago

After installing on Solus 4.3 and rebooting, there was no GUI and X11 appeared not to have started; additionally, there was no way to start it... It just refused.

Running sudo systemctl disable asus_touchpad_numpad.service allows everything to start appropriately.

Any ideas?

kawaegle commented 3 years ago

hey can you show me the output of

sudo systemctl status

with and without the asus_touchpad service?

thx

moore-bryan commented 3 years ago

asus_touchpad_numpad_service-enabled.txt asus_touchpad_numpad_service-disabled.txt Attached.

kawaegle commented 3 years ago

hello,

Have you try to change the type of the service ? by default I set it as idle (because something waiting to finish but never finish) maybe if you try to change it and set it to simple or dbus.

The wantedby is set by default with default.target maybe on your install the default target is not defined (pretty sure that's impossible to not set default but maybe)

hope that's help little I continue to investigate.

thx

moore-bryan commented 3 years ago

So I figured out to simply edit the .service file for the idle/simple/dbus piece; interestingly, the install script you have didn't set it as "idle," but as "simple." I tried both and neither worked; "dbus" wouldn't even let the service start, giving a random error.

Additionally, I looked into your default.target suggestion and found Solus's default is graphical.target; that is,

# systemctl get-default results in graphical.target,
# ls -l /usr/lib/systemd/system/default.target yields lrwxrwxrwx 1 root root 16 Aug 19 13:45 /usr/lib/systemd/system/default.target -> graphical.target, and
# runlevel gives me N 5.

Any other ideas?

moore-bryan commented 3 years ago

Just did and I have the same results; i.e., blank screen. dmseg contains nothing strange and I don't know enough about journalctl to use it nor do I know if it would even be useful.

If I manually start the service after logging in, everything functions properly, but if I don't manually disable it before logging out or shutting down, the laptop will be unusable at boot until I switch ttys and disable the service, which will let me reboot and login.

So, what I've tried so far:

Editing the service type to "dbus," "idle," and "simple" with no effect.
Adding "gdm.service" to the "After" unit line with no effect.
Editing the install "WantedBy" from "default.target" to "graphical.target" and even "multi-user.target," as suggested on the Solus support chat, without effect.

ilSant0 commented 3 years ago

I'm using Wayland instead of X11, but I have the same problem on Arch. It's needed a reboot with live iso and chroot to disable the service, in orderr to be able to boot my OS again. I confirm that if I manually start the service after logging in, all work fine. Strange :\

moore-bryan commented 3 years ago

Interesting... That would suggest it's not an X issue, but something else...

kawaegle commented 3 years ago

maybe it's an issue with the python file at start up with systemd (I mean an error in the service file) and so all the systemd init fail because of something

(but that really strange that append on your computer and not mine (I start and can use my numpad)

[Unit]
Description=Asus Touchpad to Numpad Handler

[Service]
Type=idle
ExecStart=/usr/share/asus_touchpad_numpad-driver/asus_touchpad.py m433ia 40
StandardInput=tty-force
TimeoutSec=5

[Install]
WantedBy=default.target

this is my services file. Maybe check if my version work ?

moore-bryan commented 3 years ago

No change here.

The only difference in the service files between the one you provide above and the one that was installed is that the one that installs via the script contains a After=sddm.service display-manager.service line in [Unit] and the number "6" rather than "40" on the ExecStart line.

kawaegle commented 3 years ago

The difference between 6 and 40 is QWERTY and AZERTY keyboard

I was guessing the after services made the services crash for waiting for a services that doesn't exist

I'll continue to investigate but that a strange issue maybe I'll install Solus os and try by my own

moore-bryan commented 3 years ago

That explains that, then... Thank you for your persistent help getting this working for us!

moore-bryan commented 3 years ago

Just to report back... For unrelated reasons I had to switch back to a Fedora install and this works fine there; the corner is a little "off"—that is, my finger has to "slide in" from the right into the very top of the touchpad, not where the symbol is—but that is a minor gripe. :-)

moore-bryan commented 3 years ago

Are you sure this should be closed @mohamed-badaoui; is it resolved/fixed?

mohamed-badaoui commented 3 years ago

Sorry reading your last comment, I thought it was resolved. So the problem still exists for Arch and Solus OS.

This issue is probably related to this one https://github.com/mohamed-badaoui/asus-touchpad-numpad-driver/issues/65

moore-bryan commented 3 years ago

Solus, for sure; I do not currently use Arch, so I don't know. I'm no longer on Solus at the moment, so I just wanted to let you know I have no way to further debug...

B.Moore

On Wed, Sep 15, 2021 at 1:52 PM Mohamed Badaoui @.***> wrote:

Sorry reading your last comment, I thought it was resolved? So the problem still exists for Arch and Solus OS.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/mohamed-badaoui/asus-touchpad-numpad-driver/issues/61#issuecomment-920241509, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB6KO7WSQL3WNODKNRZE4M3UCDMPRANCNFSM5C7JR25A . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

mohamed-badaoui commented 3 years ago

I think I have found the reason for this random boot failure on a few systems.

When starting the python script we try to find the correct i2c interface id .. and we only try it 5 times with 0.1 second between each try otherwise we exit with a SIGNAL HANGUP status (sys.exit(1) https://github.com/mohamed-badaoui/asus-touchpad-numpad-driver/blob/main/asus_touchpad.py#L64)

The solution therefore consists in increasing the number of tries or the time spent sleeping between each try.

@see https://github.com/mohamed-badaoui/asus-touchpad-numpad-driver/issues/65

moore-bryan commented 3 years ago

Interesting... I hope someone can check and make sure this works for them; @ilSant0?

mohamed-badaoui commented 3 years ago

For some distro, there is an issue with the service startup. It does not depend on the python script itself. At this moment, service fails mainly to start on Mint, Pop!Os, ElementaryOs, and SolusOs.

mohamed-badaoui / asus-touchpad-numpad-driver

[Model? / Solus OS - Arch] Install won't let X11 load, no errors #61

Solus, for sure; I do not currently use Arch, so I don't know. I'm no longer on Solus at the moment, so I just wanted to let you know I have no way to further debug...