Sitsofe,
I am running the final release of Fiesty, just installed it today. I still
had to manually enter my H & V settings into xorg.conf but other than that
this is the best Linux I have ever tried. Other than that short visit to the
command line I have been able to configured and install all ne
This looks similar to Bug #91292 .
--
Feisty Gnome Xorg Resolution
https://bugs.launchpad.net/bugs/99022
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[EMAIL PROTECTED]
https://lists.ubuntu.com/mailma
Gordo:
Could you attach the output of
sudo xresprobe nvidia
However, from what you are saying (with regard to fixing up HorizSync
and VertRefresh) it sounds more and more like your monitor is giving
back incorrect information. Looking at your logs your monitor claims to
have a HorizSync of 30.00-7
Here are the requested files...
FYI, after manually adding my monitor's HorizSync and VertRefresh
settings I was able to use the correct resolution settings. Also after
the latest round of updates the Restricted Drivers Manager is showing my
Nvidia driver as "In Use"...
Thanks,
Gordo
** Attachm
I will send you mine when I get home from work tonight...
Gordo
On 4/12/07, Sitsofe Wheeler <[EMAIL PROTECTED]> wrote:
>
> This could be down to your monitor lying about what it can actually do
> or incorrect settings in xorg.conf ...
>
> Timo, Gordo, Marcel:
> Could you each attach your
> /var/
I have attached my Xorg logging and config files
- Xorg.0.NOK.log -> incorrect resolution of 800x600
- Xorg.0.OK.log -> correct resolution of 1280x1024
- xorg.NOK.conf -> incorrect resolution of 800x600
- xorg.OK.conf -> correct resolution of 1280x1024
I have a Philips 190S monitor connected t
This could be down to your monitor lying about what it can actually do
or incorrect settings in xorg.conf ...
Timo, Gordo, Marcel:
Could you each attach your
/var/log/Xorg.0.log
and
/etc/X11/xorg.conf
files to this bug report?
--
Feisty Gnome Xorg Resolution
https://bugs.launchpad.net/bugs/99022
Update: I just noticed that in the restricted drivers manager under the
status column it next to the NVIDIA driver line it always says "Needs
computer restart". No matter how many times I restart, this message
never goes away. But, interestingly the 3D support appears to be working
fine. If I could
I also had a problem with nvidia-glx-legacy driver not getting higher than
800x600.
See https://bugs.launchpad.net/bugs/91292 (same issue?)
--
Feisty Gnome Xorg Resolution
https://bugs.launchpad.net/bugs/99022
You received this bug notification because you are a member of Ubuntu
Bugs, which is
using nvidia-glx-legacy
** Changed in: linux-restricted-modules-2.6.20 (Ubuntu)
Sourcepackagename: xorg => linux-restricted-modules-2.6.20
--
Feisty Gnome Xorg Resolution
https://launchpad.net/bugs/99022
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/
Cesare,
Ya, I know about all that. The restricted drivers utility did actually
install the legacy driver. I am using the legacy driver in Edgy with my
little card and it works flawlessly. I am able to run the 3D OpenGL
screensavers and UT and Quake 3 all without any problems.
Thanks,
Gord
On 3/
I don't have an NVIDIA myself, so I might be totally wrong, but I read that the
most recent NVIDIA proprietary drivers do not support very well (if at all)
some old cards like the GeForce4 440 MX.
For these, the nvidia-legacy driver should be used.
--
Feisty Gnome Xorg Resolution
https://launch
** Summary changed:
- Fiesty Gnome Xorg Resolution
+ Feisty Gnome Xorg Resolution
** Changed in: Ubuntu
Sourcepackagename: None => xorg
--
Feisty Gnome Xorg Resolution
https://launchpad.net/bugs/99022
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/li
13 matches
Mail list logo
