-
-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: installation not persistant on reboot up5401ea #78
Comments
Hello there, |
If you see a Vendor preset: Disabled, it means when the service first installs it will be disabled on start-up and will have to be manually started. |
@d4nkIot Arch python pip3 package name (that error) should be fixed in master, thank you :) |
@d4nkIot What is your output for the command |
@ldrahnik good morning. regarding the preset: disabled on the service, I guess this should have no impact on this scenario. Is it not normal behavior for all services to default to this statue in Arch, due to the 99-default.preset file set to *disable ? e.g., the other asus drivers work function normally on start with same preset (as well as all other services like NetworkManager, SDDM, etc): |
@d4nkIot You're right. Preset is not used/ignored in arch distro. Helped adding sleep to file
|
@d4nkIot Look at systemd log file and attach result here please. Should be there all attempts of service start in case start failed. |
@ldrahnik adding sleep did not work unfortunately |
@d4nkIot For example like this
|
@d4nkIot Could you please try an attempt with reinstalled the driver with non-xorg-11 service. Do a change in Co we could exclude a problem with different type |
okay, let me check it in a moment |
@d4nkIot Why is on the last screenshot in the last non-yellow row written |
@ldrahnik apologies, my last message was very confusing even for myself -- i deleted it :) I reinstalled, changed line 13 as you suggested, and uncommented ExecStartPre=/bin/sleep 2 Same behavior as before, only works with forced starting in session. As for your question regarding why the previous screenshot is missing an 'e', i checked and it was indeed an autocomplete, sorry for the confusions. It did indeed start the .service ultimately. |
@d4nkIot No problem, unfortunately, I have no more ideas atm. Is weird that other asus services have no problem with starting after boot. |
@d4nkIot Please attach log file |
asus-touchpad_numpad-driver-error.log |
@d4nkIot Here we go:
|
here from logfile is result from restarting service to get it to work
|
@ldrahnik hello. find 4 log cases here:
when it doesn't work after reboot, the device is touchpad device ... input/input10 |
@d4nkIot Nice clear report, thank you. Attempts have been done using |
@d4nkIot About input id's do not worry, when is driver started every time is created new input device for sending characters/numbers from NumberPad. Creating these devices like touchpad, mouse, touchscreen etc is done asynchronously, so sometimes is input higher, sometimes lower. Who comes first have better number.. |
@ldrahnik correct, X11 on KDE with SDDM. |
@d4nkIot Summary: It still looks like the driver is just starting too early, nothing else. 2 reasons, the first is
I have no exp it could be a problem, I use The second problem is when we try not to check the status! but when we are trying listening touchpad device it says does not exist:
What we could test more? I would like to confirm or refute that the second problem is connected to |
@ldrahnik firstly --> 2 cases with foobar.log
|
@ldrahnik I appreciate the help trying to troubleshoot this!! Maybe there might be another way to make the driver load later, once X11 is running -- or automate the manual starting of service later at some point before SDDM loads session. I will dig around some internet.. |
@d4nkIot Please, could you try again? Please pull master. What's bothering me is keyboard device is loaded, every time, and touchpad device is at the same moment not found, it can be because adding input device consumes more time, for example, I do not know. So I added printing entire list of devices at that moment |
@d4nkIot Could you please try it now? I pushed to master change - I added a line to the service unit |
@ldrahnik sure thing! |
@d4nkIot Could you please try branch |
@ldrahnik here it is |
@d4nkIot And this version of
I am only interested if is printed |
@d4nkIot Badly described, of course, is necessary to edit file |
ah gotcha.. |
|
@d4nkIot Please again git pull branch, reinstall, restart and this time again attach entire log, I added to service line: |
@ldrahnik I will try again. Do you think this is related (I use KDE - SDDM) since the previous logs were also throwing the similar errors mentioned?
|
@d4nkIot Did you test that service proposal from mentioned git issue? Important to test is I think adding to
|
@ldrahnik Here are the only 5 lines in log, from the updated branch. Same failed status as above as well.
I have not tested out what was suggested on the git issue, I will have more time later tonight to try. |
@d4nkIot Please let me know about any progress. |
@ldrahnik Hi, sorry been quite busy last few days. |
@ldrahnik Hi. FYI, I just had some time to test things out today... actually I got the lasted updated master, reinstalled, and now it works as intended! Issues are gone :) |
Describe the bug
There are 2 scenarios where everything works perfectly on my Vivobook S 14 Flip (TP3402ZA)
The issue is, if I restart the laptop, it stops working (nothing happens when touching the numpad numlock).
Then, when I either re-run installation or troubleshoot (start LOG=DEBUG), it starts working normally.
However if I close the debug in terminal, then the numpad stops working again.
Even more strange, if I stop debug while the backlight is lit up, actually it stays lit up permanently. The backlight will even be lit after a reboot, however nothing works (numbers, or numpad numlock).
Any idea what I am doing wrong?
Expected behavior
After installation, stays persistent through reboot.
Relevant log output
No response
Desktop
The text was updated successfully, but these errors were encountered: