Hi everybody,
Yesterday I arranged some time to look further in my problem, so I decided to
search for an answer to the mouse flickering problem since I could perfectly
live with the VESA module, at least for native video games.
So I came up to this page:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-fbdev/+bug/1034470
One of the comments had something related to the hardware and the software
cursor, so I decided that I would try that out, and so I found out that it's
possible to determine the type of cursor in the xorg.conf file, which I found
in /etc/X11.
So I decided to take some examples to find out in which section I should put
the "HWCursor" option. After doing so (setting the option to "true") I
removed the "nomodeset" kernel parameter and rebooted the system.
Unfortunately, it didn't change anything, so I removed the "HWCursor" option
and rebooted the system again.
Since I also have my favorite Trisquel version (which is 5.5, Brigantia) in
this computer, I decided to look after its xorg.conf, but I couldn't find it
under /etc/X11, so I decided to remove the xorg.conf from version 6.0, but
just to be in the safe side, I made a copy of it, which left me with the
files xorg.conf~ (this being my copy) and xorg.conf.vesa.
So I rebooted the system and, for my surprise, when I decided to test
Neverball, all went well, despite the fact that, under the detailed section
of the system configuration, my graphics are still recognized as unknown
(this also happens when using HardInfo, which is in the default
repositories).
As I said in my previews comments, according to the Nexuiz developers, it can
use the CPU power to help in the graphical process, if the CPU supports
something which I don't remember correctly. What I do remember is that when I
ran Nexuiz on a virtual terminal while the "nomodeset" kernel parameter was
kept, the game recognized my CPU capabilities and used Gallium3D over
something called lvmpipe.
This time, the situation is different. When I decided to run Nexuiz on a
virtual terminal, it used Gallium3D over NVC1 (which is indeed the family of
my video card).
In short, I solved two problems, despite knowing the risks:
- The problem which caused my system to return to the login screen when the
3D acceleration was used. Which could be fixed by setting the "nomodeset"
kernel parameter in the boot loader (in this case, GRUB).
- The problem with the mouse pointer, which flickered when certain actions
were made. Which was caused by the "nomodeset" kernel parameter.
As I said early, I kept a copy of the xorg.conf file which has been deleted.
So, just for those interested, it's available as an attachment.
Best regards, ADFENO.
Have a nice day.
Addendum: The forum renamed the attachment "Deleted xorg.conf.txt" to
"Deleted xorg.conf_.txt".
