Anonymous
Well, Xecure, these are the news: we have made progress.
I have followed some guidelines that you have raised.
Instead of suspending the system with the cover of the notebook, I did it with the sequence that you indicate and I also run out of mouse, but here is the burena news, there is no longer a black screen dominating the system, but everything is there and i can work antiX with keyboard. This led me to try modifying grub.cfg with the lines: gfxmode = 1024 × 600 and video = 1024 x 600. But here I was struck by the fact that from the graphical environment (nor with geany, leafpad, nano) it could not do it despite being as root. So I opened a console and edited grub.cfg with VIM and launched a reboot (thanks to Pat’s Slackware, for this knowledge). However, the issue of suspending from the menu again after the grub file changes and restarting remained unchanged.
At this point, I took a look at the link you sent me about a similar bug in the Ubuntu distro. Although it has no answers and is currently unsolvable (and that practically 8 years have passed !!), there was one detail that aroused my attention: the word “modules” in two lines. Although it does not allude to our problem in question, it gave me an idea: “What would happen if I downloaded and reloaded the mouse module?”
Okay. I rebooted the system to make it clean. I suspended antiX from the Logout menu. I woke up the system, of course, as I said without a mouse, but with video and keyboard. I accessed a terminal and ran the following: [modprobe -r psmouse] to disable the mousepad and then [modprobe -i psmouse] to reactivate it and “voila”, I had video, keyboard and mouse, as if nothing had happened.
I think this is far from an optimal solution, but it works. We would have to find a way to solve it in a more elegant way, don’t you think?
Regarding the possibility of updating the kernel, I do not know if it is viable if I am working from a USB memory. On the other hand, in the link that you indicate the user says to work with a 3.5.0 kernel and currently I am working with a 4.9.212 kernel. Or maybe you mean, not the version but the type of kernel?
Anyway, I’ve been thinking that maybe the lack of hard disk and a swap partition could be a problem for antiX to work optimally and this is the origin of the problem when suspending the system. However, I am happy with this solution that I have found and that you have selflessly helped. Although perhaps a better solution appears, it has been a great advance, don’t you think?
I attach the log file that you indicate, in case it is useful.
Thanks for your great help.
A cordial greeting.
Slickowl.
VIM (Vi IMproved)