I've recently installed the new version of Trisquel (6.0, toutalis), having
5.5 (Brigantia) in a separated partition.
I could only test and install the live operating system when adding the
startup option "nomodeset".
After installation I also had to add the "nomodeset" kernal parameter in the
boot loader, otherwise I wouldn't be able to login using conventional
methods, only using terminal (however, I haven't tried logging in trough it
then starting the X server, if I can call it this way).
During the process of setting my new operating system, I noticed that Compiz
was installed, so I removed it, and the associated packages, and decided to
try the system without the "nomodeset" kernel parameter.
And so I finally passed the login screen. Since the version 5.5 of Trisquel
recognizes my video card (using the latest Linux-libre kerel, of course) and
has Gallium3D support for it, I checked if the standard kernel does the same,
so I went to the system configuration menu and to the detailed section and
came to the conclusion that the standard kernel doesn't.
So I decided to install the Linux-libre kernel, just as I did with my other
Trisquel partition. It gave me no results, the system continues to not
recognize my video card.
Then I reverted to the standard kernel (and so removed all the Linux-libre
repositories) and decided to do some graphical tests, I started with Nexuiz,
which turned my screen black for some seconds and then, I was back to the
login screen.
I checked the output from dmesg, and noticed this:
[ 15.742451] [drm] nouveau 0000:01:00.0: PMFB0_SUBP0: 0x037f0000
[ 15.742455] [drm] nouveau 0000:01:00.0: PMFB0_SUBP1: 0x037f0040
[ 15.744047] [drm] nouveau 0000:01:00.0: PMFB0_SUBP0: 0x037f0000
[ 15.744050] [drm] nouveau 0000:01:00.0: PMFB0_SUBP1: 0x037f0040
[ 15.744063] [drm] nouveau 0000:01:00.0: PMFB0_SUBP0: 0x037f0040
[ 15.744065] [drm] nouveau 0000:01:00.0: PMFB0_SUBP1: 0x037f0000
[ 16.248735] usblp0: removed
[ 16.250418] usblp0: USB Bidirectional printer dev 5 if 0 alt 0 proto 2 vid
0x03F0 pid 0x7904
[ 25.407113] eth0: no IPv6 routers present
[ 64.819350] [drm] nouveau 0000:01:00.0: PMFB0_SUBP0: 0x037f0000
[ 64.819354] [drm] nouveau 0000:01:00.0: PMFB0_SUBP1: 0x037f0040
[ 64.819373] [drm] nouveau 0000:01:00.0: PMFB0_SUBP0: 0x037f0000
[ 64.819377] [drm] nouveau 0000:01:00.0: PMFB0_SUBP1: 0x037f0040
[ 64.819396] [drm] nouveau 0000:01:00.0: PMFB0_SUBP0: 0x037f0040
[ 64.819399] [drm] nouveau 0000:01:00.0: PMFB0_SUBP1: 0x037f0000
[ 64.819457] [drm] nouveau 0000:01:00.0: PMFB0_SUBP0: 0x037f0000
[ 64.819460] [drm] nouveau 0000:01:00.0: PMFB0_SUBP1: 0x037f0040
[ 64.819507] [drm] nouveau 0000:01:00.0: PMFB0_SUBP0: 0x037f0040
[ 64.819510] [drm] nouveau 0000:01:00.0: PMFB0_SUBP1: 0x037f0000
[ 64.819568] [drm] nouveau 0000:01:00.0: PMFB0_SUBP0: 0x037f0040
[ 64.819571] [drm] nouveau 0000:01:00.0: PMFB0_SUBP1: 0x037f0000
[ 64.819583] [drm] nouveau 0000:01:00.0: PMFB0_SUBP0: 0x037f0040
[ 64.819586] [drm] nouveau 0000:01:00.0: PMFB0_SUBP1: 0x037f0000
[ 64.819598] [drm] nouveau 0000:01:00.0: PMFB0_SUBP0: 0x037f0000
[ 64.819601] [drm] nouveau 0000:01:00.0: PMFB0_SUBP1: 0x037f0040
[ 64.819626] [drm] nouveau 0000:01:00.0: PMFB0_SUBP0: 0x037f0000
[ 64.819629] [drm] nouveau 0000:01:00.0: PMFB0_SUBP1: 0x037f0040
[ 64.819640] [drm] nouveau 0000:01:00.0: PMFB0_SUBP0: 0x037f0000
[ 64.819643] [drm] nouveau 0000:01:00.0: PMFB0_SUBP1: 0x037f0040
[ 64.819654] [drm] nouveau 0000:01:00.0: PMFB0_SUBP0: 0x037f0040
[ 64.819657] [drm] nouveau 0000:01:00.0: PMFB0_SUBP1: 0x037f0000
[ 64.819694] [drm] nouveau 0000:01:00.0: PMFB0_SUBP0: 0x037f0040
[ 64.819697] [drm] nouveau 0000:01:00.0: PMFB0_SUBP1: 0x037f0000
[ 64.819708] [drm] nouveau 0000:01:00.0: PMFB0_SUBP0: 0x037f0000
[ 64.819711] [drm] nouveau 0000:01:00.0: PMFB0_SUBP1: 0x037f0040
[ 64.819724] [drm] nouveau 0000:01:00.0: PMFB0_SUBP0: 0x037f0000
[ 64.819727] [drm] nouveau 0000:01:00.0: PMFB0_SUBP1: 0x037f0040
[ 64.819752] [drm] nouveau 0000:01:00.0: PMFB0_SUBP0: 0x037f0000
[ 64.819755] [drm] nouveau 0000:01:00.0: PMFB0_SUBP1: 0x037f0040
[ 105.899273] init: tty1 main process ended, respawning
[ 483.647197] [drm] nouveau 0000:01:00.0: PMFB0_SUBP0: 0x037f0040
[ 483.647200] [drm] nouveau 0000:01:00.0: PMFB0_SUBP1: 0x037f0040
[ 488.129630] [drm] nouveau 0000:01:00.0: PMFB0_SUBP0: 0x037f0040
[ 488.129635] [drm] nouveau 0000:01:00.0: PMFB0_SUBP1: 0x037f0040
[ 488.321182] [drm] nouveau 0000:01:00.0: PMFB0_SUBP0: 0x037f0040
[ 488.321188] [drm] nouveau 0000:01:00.0: PMFB0_SUBP1: 0x037f0040
Note: there might have some unnecessary stuff, but I decided not to change it
for the sake of transparency.
So I went back to the basic trick of adding the "nomodeset" kernel parameter
to the bot loader. And this time, the system recognizes my video card in the
detailed section of the system configuration menu, and gives me this
information:
VESA: GF108 Board - 1071v0p1.
Then, I decided to test Nexuiz again, and it worked almost smothly, except
for the fact that every time an enemy appears in the screen, the game freezes
for a second, and the CPU usage goes way up.
Searching in the Internet, I found out that the developers of Nexuiz made it
possible for those with high CPU powers to use it (the CPU powers). They did
so by using Gallium3D over something called llvmpipe, which I don't know what
it is.
So I tried a more valid test, this time with PCSX-R, and everything went ok,
the games could be emulated fine.
Notes:
- All the programs were run with minimal-and-yet-playable configuration in
windowed mode;
- The output of lspci gives the correct video card name in all the cases,
that is:
01:00.0 VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 430]
(rev a1)
But this is not the main problem.
I noticed that whenever I do an action with the mouse pointer (other than
moving it), it disappears and only comes back when I move it.
For daily use it's not a big problem, but when it comes to productivity tasks
like image and vector graphics manipulation, it's extremely hard to see the
mouse pointer.
Notes:
- The mouse pointer problem only appears when the "nomodeset" kernel
parameter is added to the boot loader;
- When going to the system configuration menu, under display configuration
(without the "nomodeset" kernel parameter), my monitor is detected as a GSM,
and I have more resolutions available. In the other case, it's detected as a
laptop display and has just 1024x768 and 800x600 available. This is not a
problem for me because I just use 1024x768.
So... Is it possible to fix the mouse pointer problem, or even better, the
other problem mentioned in the beginning of this post.
Best regards, ADFENO.
Have a nice day.
Addendum: I can provide more information, if you wish.
