The main problem at the moment is that I cannot set up KMail because I can't get at the bottom of the window. :-(
It is the first time that I have used dvi-d and the Iiyama Prolite E431S has heretofore been recognised well in VGA.
I obviously need an x-org file, but am not sure how to achieve this at this stage.
TDE 3.5.13.2 on Squeeze, just finished installing and am trying to set it up.
NVIDIA GTX 650Ti 1GB Graphics Card. Nouveau is installed.
As a pro-tem measure, can anyone remind me how to move a window above the top of the monitor so that I can get at the bottom and click "apply"? :-(
Thanks, Lisi
Am Donnerstag, 3. Januar 2013, 14:33:31 schrieb Lisi Reisz:
The main problem at the moment is that I cannot set up KMail because I can't get at the bottom of the window.
you can always move windows which are too big for the given resolution by just pressing alt+left mouse button down
HTH Werner
On Thursday 03 January 2013 14:38:56 Werner Joss wrote:
Am Donnerstag, 3. Januar 2013, 14:33:31 schrieb Lisi Reisz:
The main problem at the moment is that I cannot set up KMail because I can't get at the bottom of the window.
you can always move windows which are too big for the given resolution by just pressing alt+left mouse button down
HTH
It certainly did! It was a lifesaver. 700 emails downloading as I type! Now I can relax and solve the other problems more calmly!
Thanks! :-)
As I have said before, you are a lovely lot.
Lisi
On Thursday 03 of January 2013 15:38:56 Werner Joss wrote:
Am Donnerstag, 3. Januar 2013, 14:33:31 schrieb Lisi Reisz:
The main problem at the moment is that I cannot set up KMail because I can't get at the bottom of the window.
you can always move windows which are too big for the given resolution by just pressing alt+left mouse button down
HTH Werner
Hint: I'm changing 'Meta' key from 'Alt' to 'Win'. The main reason is that some programs have for 'Alt' + mouse's own behavior (such as GIMP). And then, that fits very nicely 'Win' + mouse => manipulating with windows (left for move, right for resizing).
Slavek --
On 2013-01-03 18:00 (GMT+0100) Slávek Banko composed:
Hint: I'm changing 'Meta' key from 'Alt' to 'Win'. The main reason is that some programs have for 'Alt' + mouse's own behavior (such as GIMP). And then, that fits very nicely 'Win' + mouse => manipulating with windows (left for move, right for resizing).
Changing where, SVN? None of the keyboards I use routinely have such keys. The last sanely priced keyboards with function keys where they belong were made last century, before keyboards with WIN keys were introduced, when mine were made.
On Thursday 03 of January 2013 18:27:16 Felix Miata wrote:
On 2013-01-03 18:00 (GMT+0100) Slávek Banko composed:
Hint: I'm changing 'Meta' key from 'Alt' to 'Win'. The main reason is that some programs have for 'Alt' + mouse's own behavior (such as GIMP). And then, that fits very nicely 'Win' + mouse => manipulating with windows (left for move, right for resizing).
Changing where, SVN? None of the keyboards I use routinely have such keys. The last sanely priced keyboards with function keys where they belong were made last century, before keyboards with WIN keys were introduced, when mine were made.
In Control Center / Desktop / Window Behavior / Window Actions / Modifier key. When I change from 'Alt' to 'Meta', then action working with the 'Win' key.
Slavek --
Quoth Sl�vek Banko.....
On Thursday 03 of January 2013 18:27:16 Felix Miata wrote:
On 2013-01-03 18:00 (GMT+0100) Sl?vek Banko composed:
Hint: I'm changing 'Meta' key from 'Alt' to 'Win'. The main reason is that some programs have for 'Alt' + mouse's own behavior (such as GIMP). And then, that fits very nicely 'Win' + mouse => manipulating with windows (left for move, right for resizing).
In Control Center / Desktop / Window Behavior / Window Actions / Modifier key. When I change from 'Alt' to 'Meta', then action working with the 'Win' key.
FWIW, if I'm right in that you're saying you are going to change the default for Trinity, then I think this is a bad idea.
Alt has been the normal Meta key for decades and anyone that's used to using it will be annoyed by this change.
Most online references will (arguably incorrectly) reference the Alt key and not the Meta key.
Anyone who doesn't know about the Alt key won't appreciate that you've changed it anyway.
Not every keyboard has the 'Windows' keys on it.
On Thursday 03 of January 2013 19:16:00 Russell Brown wrote:
Quoth Slávek Banko.....
On Thursday 03 of January 2013 18:27:16 Felix Miata wrote:
On 2013-01-03 18:00 (GMT+0100) Sl?vek Banko composed:
Hint: I'm changing 'Meta' key from 'Alt' to 'Win'. The main reason is that some programs have for 'Alt' + mouse's own behavior (such as GIMP). And then, that fits very nicely 'Win' + mouse => manipulating with windows (left for move, right for resizing).
In Control Center / Desktop / Window Behavior / Window Actions / Modifier key. When I change from 'Alt' to 'Meta', then action working with the 'Win' key.
FWIW, if I'm right in that you're saying you are going to change the default for Trinity, then I think this is a bad idea.
Alt has been the normal Meta key for decades and anyone that's used to using it will be annoyed by this change.
Most online references will (arguably incorrectly) reference the Alt key and not the Meta key.
Anyone who doesn't know about the Alt key won't appreciate that you've changed it anyway.
Not every keyboard has the 'Windows' keys on it.
You do not have to fear - I do not intend to change the default settings. I only recommended this change to those who have the Win key.
Slavek --
On 01/03/2013 11:07 AM, Slávek Banko wrote:
You do not have to fear - I do not intend to change the default settings. I only recommended this change to those who have the Win key.
The language barrier strikes again. :) We native English speakers thought you meant that you were going to change the default setting.
On Thursday 03 of January 2013 20:15:04 Dan Youngquist wrote:
On 01/03/2013 11:07 AM, Slávek Banko wrote:
You do not have to fear - I do not intend to change the default settings. I only recommended this change to those who have the Win key.
The language barrier strikes again. :) We native English speakers thought you meant that you were going to change the default setting.
No, I'm sorry for scaring :)
Slavek --
On 2013-01-03 20:07 (GMT+0100) Slávek Banko composed:
Russell Brown wrote:
Quoth Slávek Banko.....
Felix Miata wrote:
On 2013-01-03 18:00 (GMT+0100) Sl?vek Banko composed:
Hint: I'm changing 'Meta' key from 'Alt' to 'Win'.
In Control Center / Desktop / Window Behavior / Window Actions / Modifier key. When I change from 'Alt' to 'Meta', then action working with the 'Win' key.
Not every keyboard has the 'Windows' keys on it.
You do not have to fear - I do not intend to change the default settings. I only recommended this change to those who have the Win key.
Your grammar "I'm changing 'Meta' key from 'Alt' to 'Win'" made it look like you were _intending_ to make such change, which would lead readers to believe to change the source and RPMs, rather than on your own system(s), where likely you had already _made_ the change described. The way you wrote, it looked nothing like a mere recommendation. This is why I asked "where" (and not how).
From: lisi.reisz@gmail.com To: trinity-users@lists.pearsoncomputing.net Date: Thu, 3 Jan 2013 14:33:31 +0000 Subject: [trinity-users] settings for a 1024x768 monitor that Trinity insists on recognising as 800x600.
The main problem at the moment is that I cannot set up KMail because I can't get at the bottom of the window. :-(
It is the first time that I have used dvi-d and the Iiyama Prolite E431S has heretofore been recognised well in VGA.
I obviously need an x-org file, but am not sure how to achieve this at this stage.
TDE 3.5.13.2 on Squeeze, just finished installing and am trying to set it up.
NVIDIA GTX 650Ti 1GB Graphics Card. Nouveau is installed.> --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
As a pro-tem measure, can anyone remind me how to move a window above the top of the monitor so that I can get at the bottom and click "apply"? :-(
Thanks, Lisi
Hi Lisi, Press and keep pressed the ''Alt'' button and drag the window you want as you wish! I use it all the time on my Asus EEE (first gen), because it has a screen resolution of 800x480
-Alexandre
On Thursday 03 January 2013 15:33:16 Alexandre Couture wrote:
Press and keep pressed the ''Alt'' button and drag the window you want as you wish! I use it all the time on my Asus EEE (first gen), because it has a screen resolution of 800x480
Thanks, Alexandre! I knew it was possible in some way, and tried my hand, but didn't get there.
:-) Lisi
On Thursday 03 of January 2013 15:33:31 Lisi Reisz wrote:
The main problem at the moment is that I cannot set up KMail because I can't get at the bottom of the window. :-(
It is the first time that I have used dvi-d and the Iiyama Prolite E431S has heretofore been recognised well in VGA.
I obviously need an x-org file, but am not sure how to achieve this at this stage.
TDE 3.5.13.2 on Squeeze, just finished installing and am trying to set it up.
NVIDIA GTX 650Ti 1GB Graphics Card. Nouveau is installed.
As a pro-tem measure, can anyone remind me how to move a window above the top of the monitor so that I can get at the bottom and click "apply"? :-(
Thanks, Lisi
First of all - I suggest a kernel and xorg from backports. For me it solved several problems.
Can you send your /var/log/Xorg.0.log? There should be to see if the monitor parameters were successfully detected.
Slavek --
On Thursday 03 January 2013 17:05:36 Slávek Banko wrote:
On Thursday 03 of January 2013 15:33:31 Lisi Reisz wrote:
The main problem at the moment is that I cannot set up KMail because I can't get at the bottom of the window. :-(
It is the first time that I have used dvi-d and the Iiyama Prolite E431S has heretofore been recognised well in VGA.
I obviously need an x-org file, but am not sure how to achieve this at this stage.
TDE 3.5.13.2 on Squeeze, just finished installing and am trying to set it up.
NVIDIA GTX 650Ti 1GB Graphics Card. Nouveau is installed.
As a pro-tem measure, can anyone remind me how to move a window above the top of the monitor so that I can get at the bottom and click "apply"? :-(
Thanks, Lisi
First of all - I suggest a kernel and xorg from backports. For me it solved several problems.
Can you send your /var/log/Xorg.0.log? There should be to see if the monitor parameters were successfully detected.
Thanks, Slávek! You can be relied on for helpful suggestions! I am litterally on my way out . :-( But I shall see to this as soon as I get back. I already have a kernel from Backports, 3.2.0, so I'll get a backported xorg as soon as I can get to the keyboard again, and I'll send the log.
Lisi
On Thursday 03 January 2013 17:05:36 Slávek Banko wrote:
First of all - I suggest a kernel and xorg from backports. For me it solved several problems.
Slávek, I could hug you! Luckily for you, I can't reach. ;-) I installed the xorg from backports - and the monitor resolution problem is solved!!
Now that I can just about bear to look at the thing, I can get on with the configuration and setting up. I'll have a look at that log you recommended, but I have to go off again now.
Thank you! Lisi
On Thursday 03 January 2013 17:05:36 Slávek Banko wrote:
Can you send your /var/log/Xorg.0.log? There should be to see if the monitor parameters were successfully detected.
I was so delighted that the monitor was usable that I just jumped for joy and got on with configuring.
But it still wasn't right. As I say, it gets recognised in VGA, so I haven't had to do anything for ages. 800x600 was ghastly, and 1024x768 was dredged from my memory.
It was only when I used it that I realised that, hugely improved as it was, and usable as it was, it still wasn't right.
So I did what I should have done in the first place, and read the manual. (What was that that someone said about RTFM? :-( ) The optimum resolution is 1280x1024.
Here is my /var/log/Xorg.0.log: http://paste.ubuntu.com/1495223/
It says near the beginning that /usr/share/X11/xorg.conf.d was consulted, and didn't have the necessary information, so it is using the default monitor. That presumably is at least part of the problem. So "all" I have to do now is put the necessary information into xorg.conf.d? And I will sail off into the rainbow? Or is there in fact a lot more that I ought to do?
I shall Google for xorg.conf.d and see what Google advises.
Thanks again, Slávek, for telling me which log to look at, and for all your help.
Lisi
Dne pá 4. ledna 2013 Lisi Reisz napsal(a):
On Thursday 03 January 2013 17:05:36 Slávek Banko wrote:
Can you send your /var/log/Xorg.0.log? There should be to see if the monitor parameters were successfully detected.
I was so delighted that the monitor was usable that I just jumped for joy and got on with configuring.
But it still wasn't right. As I say, it gets recognised in VGA, so I haven't had to do anything for ages. 800x600 was ghastly, and 1024x768 was dredged from my memory.
It was only when I used it that I realised that, hugely improved as it was, and usable as it was, it still wasn't right.
So I did what I should have done in the first place, and read the manual. (What was that that someone said about RTFM? :-( ) The optimum resolution is 1280x1024.
Here is my /var/log/Xorg.0.log: http://paste.ubuntu.com/1495223/
It says near the beginning that /usr/share/X11/xorg.conf.d was consulted, and didn't have the necessary information, so it is using the default monitor. That presumably is at least part of the problem. So "all" I have to do now is put the necessary information into xorg.conf.d? And I will sail off into the rainbow? Or is there in fact a lot more that I ought to do?
I shall Google for xorg.conf.d and see what Google advises.
Thanks again, Slávek, for telling me which log to look at, and for all your help.
Lisi
Please, you have updated to backports version also packages libdrm*? From the log I see that instead of nouveau is used vesa. It is not good.
Slavek --
On Friday 04 January 2013 14:03:19 Slávek Banko wrote:
Please, you have updated to backports version also packages libdrm*?
It would seem so. (see below *.)
From the log I see that instead of nouveau is used vesa. It is not good.
Yes, I noticed that but thought it was related to teh fact that it was using teh default monitor.
I'm running out of ways to say thank you. Thank you itself is becoming clichéd. Lisi
* peter@Nyx:~$ aptitude search libdrm p libdrm-dev - Userspace interface to kernel DRM services -- devel i A libdrm-intel1 - Userspace interface to intel-specific kernel DRM se p libdrm-intel1-dbg - Userspace interface to intel-specific kernel DRM se c libdrm-nouveau1 - Userspace interface to nouveau-specific kernel DRM p libdrm-nouveau1-dbg - Userspace interface to nouveau-specific kernel DRM i A libdrm-nouveau1a - Userspace interface to nouveau-specific kernel DRM p libdrm-nouveau1a-dbg - Userspace interface to nouveau-specific kernel DRM i A libdrm-radeon1 - Userspace interface to radeon-specific kernel DRM s p libdrm-radeon1-dbg - Userspace interface to radeon-specific kernel DRM s i A libdrm2 - Userspace interface to kernel DRM services -- runti p libdrm2-dbg - Userspace interface to kernel DRM services -- debug p libdrmaa-dev - Distributed resource management Application API lib p libdrmaa-java - Distributed resource management Application API lib p libdrmaa1.0 - Distributed resource management Application API lib peter@Nyx:~$ aptitude -t squeeze-backports search libdrm p libdrm-dev - Userspace interface to kernel DRM services -- devel i A libdrm-intel1 - Userspace interface to intel-specific kernel DRM se p libdrm-intel1-dbg - Userspace interface to intel-specific kernel DRM se c libdrm-nouveau1 - Userspace interface to nouveau-specific kernel DRM p libdrm-nouveau1-dbg - Userspace interface to nouveau-specific kernel DRM i A libdrm-nouveau1a - Userspace interface to nouveau-specific kernel DRM p libdrm-nouveau1a-dbg - Userspace interface to nouveau-specific kernel DRM i A libdrm-radeon1 - Userspace interface to radeon-specific kernel DRM s p libdrm-radeon1-dbg - Userspace interface to radeon-specific kernel DRM s i A libdrm2 - Userspace interface to kernel DRM services -- runti p libdrm2-dbg - Userspace interface to kernel DRM services -- debug p libdrmaa-dev - Distributed resource management Application API lib p libdrmaa-java - Distributed resource management Application API lib p libdrmaa1.0 - Distributed resource management Application API lib peter@Nyx:~$
root@Nyx:/home/peter# aptitude -t squeeze-backports install libdrm-nouveau1 libdrm-nouveau1a The following NEW packages will be installed: libdrm-nouveau1 0 packages upgraded, 1 newly installed, 0 to remove and 43 not upgraded. Need to get 0 B/408 kB of archives. After unpacking 487 kB will be used. The following packages have unmet dependencies: libdrm-nouveau1a: Conflicts: libdrm-nouveau1 but 2.4.21-1~squeeze3 is to be installed. The following actions will resolve these dependencies:
Remove the following packages: 1) libdrm-nouveau1a 2) xserver-xorg-video-nouveau
Accept this solution? [Y/n/q/?] q Abandoning all efforts to resolve these dependencies. Abort. root@Nyx:/home/peter# aptitude -t squeeze-backports install libdrm-nouveau1a No packages will be installed, upgraded, or removed. 0 packages upgraded, 0 newly installed, 0 to remove and 43 not upgraded. Need to get 0 B of archives. After unpacking 0 B will be used.
root@Nyx:/home/peter#
Dne pá 4. ledna 2013 Lisi Reisz napsal(a):
On Friday 04 January 2013 14:03:19 Slávek Banko wrote:
Please, you have updated to backports version also packages libdrm*?
It would seem so. (see below *.)
From the log I see that instead of nouveau is used vesa. It is not good.
Yes, I noticed that but thought it was related to teh fact that it was using teh default monitor.
I'm running out of ways to say thank you. Thank you itself is becoming clichéd. Lisi
peter@Nyx:~$ aptitude search libdrm p libdrm-dev - Userspace interface to kernel DRM services -- devel i A libdrm-intel1 - Userspace interface to intel-specific kernel DRM se p libdrm-intel1-dbg - Userspace interface to intel-specific kernel DRM se c libdrm-nouveau1 - Userspace interface to nouveau-specific kernel DRM p libdrm-nouveau1-dbg - Userspace interface to nouveau-specific kernel DRM i A libdrm-nouveau1a - Userspace interface to nouveau-specific kernel DRM p libdrm-nouveau1a-dbg - Userspace interface to nouveau-specific kernel DRM i A libdrm-radeon1 - Userspace interface to radeon-specific kernel DRM s p libdrm-radeon1-dbg - Userspace interface to radeon-specific kernel DRM s i A libdrm2 - Userspace interface to kernel DRM services -- runti p libdrm2-dbg - Userspace interface to kernel DRM services -- debug p libdrmaa-dev - Distributed resource management Application API lib p libdrmaa-java - Distributed resource management Application API lib p libdrmaa1.0 - Distributed resource management Application API lib peter@Nyx:~$ aptitude -t squeeze-backports search libdrm p libdrm-dev - Userspace interface to kernel DRM services -- devel i A libdrm-intel1 - Userspace interface to intel-specific kernel DRM se p libdrm-intel1-dbg - Userspace interface to intel-specific kernel DRM se c libdrm-nouveau1 - Userspace interface to nouveau-specific kernel DRM p libdrm-nouveau1-dbg - Userspace interface to nouveau-specific kernel DRM i A libdrm-nouveau1a - Userspace interface to nouveau-specific kernel DRM p libdrm-nouveau1a-dbg - Userspace interface to nouveau-specific kernel DRM i A libdrm-radeon1 - Userspace interface to radeon-specific kernel DRM s p libdrm-radeon1-dbg - Userspace interface to radeon-specific kernel DRM s i A libdrm2 - Userspace interface to kernel DRM services -- runti p libdrm2-dbg - Userspace interface to kernel DRM services -- debug p libdrmaa-dev - Distributed resource management Application API lib p libdrmaa-java - Distributed resource management Application API lib p libdrmaa1.0 - Distributed resource management Application API lib peter@Nyx:~$
root@Nyx:/home/peter# aptitude -t squeeze-backports install libdrm-nouveau1 libdrm-nouveau1a The following NEW packages will be installed: libdrm-nouveau1 0 packages upgraded, 1 newly installed, 0 to remove and 43 not upgraded. Need to get 0 B/408 kB of archives. After unpacking 487 kB will be used. The following packages have unmet dependencies: libdrm-nouveau1a: Conflicts: libdrm-nouveau1 but 2.4.21-1~squeeze3 is to be installed. The following actions will resolve these dependencies:
Remove the following packages:
libdrm-nouveau1axserver-xorg-video-nouveauAccept this solution? [Y/n/q/?] q Abandoning all efforts to resolve these dependencies. Abort. root@Nyx:/home/peter# aptitude -t squeeze-backports install libdrm-nouveau1a No packages will be installed, upgraded, or removed. 0 packages upgraded, 0 newly installed, 0 to remove and 43 not upgraded. Need to get 0 B of archives. After unpacking 0 B will be used.
root@Nyx:/home/peter#
According to this commit, support for nvidia GK106 is not yet available in nouveau. I guess the only chance is to use the (ugly) binary drivers.
http://cgit.freedesktop.org/nouveau/linux-2.6/commit/?id=15dd5a6044cfbc259d0...
Slávek --
On Friday 04 January 2013 16:23:24 Slávek Banko wrote:
Dne pá 4. ledna 2013 Lisi Reisz napsal(a):
On Friday 04 January 2013 14:03:19 Slávek Banko wrote:
Please, you have updated to backports version also packages libdrm*?
It would seem so. (see below *.)
From the log I see that instead of nouveau is used vesa. It is not good.
Yes, I noticed that but thought it was related to teh fact that it was using teh default monitor.
I'm running out of ways to say thank you. Thank you itself is becoming clichéd. Lisi
peter@Nyx:~$ aptitude search libdrm p libdrm-dev - Userspace interface to kernel DRM services -- devel i A libdrm-intel1 - Userspace interface to intel-specific kernel DRM se p libdrm-intel1-dbg - Userspace interface to intel-specific kernel DRM se c libdrm-nouveau1 - Userspace interface to nouveau-specific kernel DRM p libdrm-nouveau1-dbg - Userspace interface to nouveau-specific kernel DRM i A libdrm-nouveau1a - Userspace interface to nouveau-specific kernel DRM p libdrm-nouveau1a-dbg - Userspace interface to nouveau-specific kernel DRM i A libdrm-radeon1 - Userspace interface to radeon-specific kernel DRM s p libdrm-radeon1-dbg - Userspace interface to radeon-specific kernel DRM s i A libdrm2 - Userspace interface to kernel DRM services -- runti p libdrm2-dbg - Userspace interface to kernel DRM services -- debug p libdrmaa-dev - Distributed resource management Application API lib p libdrmaa-java - Distributed resource management Application API lib p libdrmaa1.0 - Distributed resource management Application API lib peter@Nyx:~$ aptitude -t squeeze-backports search libdrm p libdrm-dev - Userspace interface to kernel DRM services -- devel i A libdrm-intel1 - Userspace interface to intel-specific kernel DRM se p libdrm-intel1-dbg - Userspace interface to intel-specific kernel DRM se c libdrm-nouveau1 - Userspace interface to nouveau-specific kernel DRM p libdrm-nouveau1-dbg - Userspace interface to nouveau-specific kernel DRM i A libdrm-nouveau1a - Userspace interface to nouveau-specific kernel DRM p libdrm-nouveau1a-dbg - Userspace interface to nouveau-specific kernel DRM i A libdrm-radeon1 - Userspace interface to radeon-specific kernel DRM s p libdrm-radeon1-dbg - Userspace interface to radeon-specific kernel DRM s i A libdrm2 - Userspace interface to kernel DRM services -- runti p libdrm2-dbg - Userspace interface to kernel DRM services -- debug p libdrmaa-dev - Distributed resource management Application API lib p libdrmaa-java - Distributed resource management Application API lib p libdrmaa1.0 - Distributed resource management Application API lib peter@Nyx:~$
root@Nyx:/home/peter# aptitude -t squeeze-backports install libdrm-nouveau1 libdrm-nouveau1a The following NEW packages will be installed: libdrm-nouveau1 0 packages upgraded, 1 newly installed, 0 to remove and 43 not upgraded. Need to get 0 B/408 kB of archives. After unpacking 487 kB will be used. The following packages have unmet dependencies: libdrm-nouveau1a: Conflicts: libdrm-nouveau1 but 2.4.21-1~squeeze3 is to be installed. The following actions will resolve these dependencies:
Remove the following packages:
libdrm-nouveau1axserver-xorg-video-nouveauAccept this solution? [Y/n/q/?] q Abandoning all efforts to resolve these dependencies. Abort. root@Nyx:/home/peter# aptitude -t squeeze-backports install libdrm-nouveau1a No packages will be installed, upgraded, or removed. 0 packages upgraded, 0 newly installed, 0 to remove and 43 not upgraded. Need to get 0 B of archives. After unpacking 0 B will be used.
root@Nyx:/home/peter#
According to this commit, support for nvidia GK106 is not yet available in nouveau. I guess the only chance is to use the (ugly) binary drivers.
http://cgit.freedesktop.org/nouveau/linux-2.6/commit/?id=15dd5a6044cfbc259d 03cdd1d3f5f71a41a7d933
Thanks so much, Slávek. I ought to have known how to get that information for myself, but I'm afraid that I didn't. I also ought to have Googled to try and get that information. I did, after all, know that it is a NVIDIA card. But following this list and the Debian users list had left me with the obviously erroneous impression that nouveau is fine so long as you don't need 3d.
It is my husband's new computer. He seems happy with it as it is. I could do with its being a little clearer! But I'll see whether just giving nouveau time to catch up, gets it better before he starts to have problems.
Lisi
-
Alexandre Couture -
Dan Youngquist -
Felix Miata -
Lisi Reisz -
russell＠lls.lls.com -
Slávek Banko -
Werner Joss