| 2006-02-17 23:21:23 |
Ricardo Pérez López |
bug |
|
|
added bug |
| 2006-02-17 23:23:22 |
Ricardo Pérez López |
bug |
|
|
added attachment 'lspci.gz' ("lspci" output) |
| 2006-02-17 23:23:55 |
Ricardo Pérez López |
bug |
|
|
added attachment 'lspci-n.gz' ("lspci -n" output) |
| 2006-02-17 23:24:45 |
Ricardo Pérez López |
bug |
|
|
added attachment 'Xorg.0.log.gz' (The /var/log/Xorg.0.log file) |
| 2006-02-17 23:25:28 |
Ricardo Pérez López |
bug |
|
|
added attachment 'xorg.conf.gz' (The /etc/X11/xorg.conf file) |
| 2006-02-17 23:29:32 |
Ricardo Pérez López |
bug |
|
|
added attachment 'xorg.conf.good.gz' (The /etc/X11/xorg.conf file generated by "sudo dpkg-reconfigure xserver-xorg") |
| 2006-04-06 15:03:20 |
Henrik Nilsen Omma |
xorg: status |
Unconfirmed |
Confirmed |
|
| 2006-04-06 15:03:20 |
Henrik Nilsen Omma |
xorg: statusexplanation |
|
I'm setting tge status to confirmed since several people agree.
Has anyone with this hardware also performed a standard install? If so, is it detected on install or do you have to run 'dpkg-reconfigure' after install?
Thanks. |
|
| 2006-04-10 16:15:57 |
Henrik Nilsen Omma |
xorg: status |
Confirmed |
Needs Info |
|
| 2006-04-10 16:15:57 |
Henrik Nilsen Omma |
xorg: statusexplanation |
I'm setting tge status to confirmed since several people agree.
Has anyone with this hardware also performed a standard install? If so, is it detected on install or do you have to run 'dpkg-reconfigure' after install?
Thanks. |
Hello,
Could eeither of you please try running the following two commands on the live CD (or standard version if you have it installed):
wget http://www.ubuntulinux.nl/files/pastebin
python pastebin --debug-x
That will first download a debugging script from ubuntulinux.nl. Running it will in turn gather all the log files and output we should need and paste it to a URL at http://paste.ubuntu-nl.org
If you then just paste that URL into a new comment here we should have what we need. Thanks! You can see a sample of what is collected here: http://paste.ubuntu-nl.org/11955
|
|
| 2006-05-26 17:51:36 |
Matthew Lange |
xorg: status |
Needs Info |
Confirmed |
|
| 2006-05-26 17:51:36 |
Matthew Lange |
xorg: statusexplanation |
Hello,
Could eeither of you please try running the following two commands on the live CD (or standard version if you have it installed):
wget http://www.ubuntulinux.nl/files/pastebin
python pastebin --debug-x
That will first download a debugging script from ubuntulinux.nl. Running it will in turn gather all the log files and output we should need and paste it to a URL at http://paste.ubuntu-nl.org
If you then just paste that URL into a new comment here we should have what we need. Thanks! You can see a sample of what is collected here: http://paste.ubuntu-nl.org/11955
|
Similar to Bug #5801?
Set to confirmed, package: xserver-xorg |
|
| 2007-03-05 14:40:09 |
didier |
None: statusexplanation |
Similar to Bug #5801?
Set to confirmed, package: xserver-xorg |
|
|
| 2007-03-30 09:00:01 |
Tollef Fog Heen |
casper: status |
Confirmed |
Fix Committed |
|
| 2007-03-30 09:00:01 |
Tollef Fog Heen |
casper: statusexplanation |
|
I have just committed a fix which I believe solves this problem now; please test tomorrow's daily CDs to verify. |
|
| 2007-03-30 10:49:16 |
Tollef Fog Heen |
casper: status |
Fix Committed |
Fix Released |
|
| 2007-03-30 10:49:16 |
Tollef Fog Heen |
casper: statusexplanation |
I have just committed a fix which I believe solves this problem now; please test tomorrow's daily CDs to verify. |
|
|
| 2007-04-20 07:17:53 |
David Taylor |
casper: status |
Fix Released |
Confirmed |
|
| 2007-04-20 07:17:53 |
David Taylor |
casper: statusexplanation |
|
I have moved the status back to confirmed as the fix released has not worked, does anyone else wish to confirm this with their system set-up. |
|
| 2009-01-06 16:38:34 |
Colin Watson |
casper: bugtargetdisplayname |
casper (Ubuntu) |
xorg (Ubuntu) |
|
| 2009-01-06 16:38:34 |
Colin Watson |
casper: bugtargetname |
casper (Ubuntu) |
xorg (Ubuntu) |
|
| 2009-01-06 16:38:34 |
Colin Watson |
casper: statusexplanation |
I have moved the status back to confirmed as the fix released has not worked, does anyone else wish to confirm this with their system set-up. |
|
|
| 2009-01-06 16:38:34 |
Colin Watson |
casper: title |
Bug #31830 in casper (Ubuntu): "Incorrect screen resolution in Dapper LiveCD" |
Bug #31830 in xorg (Ubuntu): "Incorrect screen resolution in Dapper LiveCD" |
|
| 2009-01-06 17:43:55 |
Bryce Harrington |
description |
The screen resolution in X is not correct. It appears in 640x480, 24 bit color. In "System -> Preferences -> Screen resolution" I can't change the resolution to another one (only appears "640x480", 60 Hz).
I have a MSI K7N2G-ILSR motherboard (3 years, more or less), with nVidia nForce2 chipset. I use the internal graphics card. Breezy works perfectly for me (installed and LiveCD). |
The screen resolution in X is not correct. It appears in 640x480, 24 bit color. In "System -> Preferences -> Screen resolution" I can't change the resolution to another one (only appears "640x480", 60 Hz).
I have a MSI K7N2G-ILSR motherboard (3 years, more or less), with nVidia nForce2 chipset. I use the internal graphics card. Breezy works perfectly for me (installed and LiveCD).
0000:03:00.0 VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX - nForce GPU] (rev a3)
0000:03:00.0 0300: 10de:01f0 (rev a3) |
|
| 2009-01-06 17:43:55 |
Bryce Harrington |
title |
Incorrect screen resolution in Dapper LiveCD |
Incorrect screen resolution in Dapper LiveCD unless HorizSync and VertRefresh specified |
|
| 2009-01-06 17:44:28 |
Bryce Harrington |
description |
The screen resolution in X is not correct. It appears in 640x480, 24 bit color. In "System -> Preferences -> Screen resolution" I can't change the resolution to another one (only appears "640x480", 60 Hz).
I have a MSI K7N2G-ILSR motherboard (3 years, more or less), with nVidia nForce2 chipset. I use the internal graphics card. Breezy works perfectly for me (installed and LiveCD).
0000:03:00.0 VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX - nForce GPU] (rev a3)
0000:03:00.0 0300: 10de:01f0 (rev a3) |
The screen resolution in X is not correct. It appears in 640x480, 24 bit color. In "System -> Preferences -> Screen resolution" I can't change the resolution to another one (only appears "640x480", 60 Hz).
I have a MSI K7N2G-ILSR motherboard (3 years, more or less), with nVidia nForce2 chipset. I use the internal graphics card. Breezy works perfectly for me (installed and LiveCD).
0000:03:00.0 VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX - nForce GPU] (rev a3)
0000:03:00.0 0300: 10de:01f0 (rev a3)
[Workaround]
Add the following HorizSync and VertRefresh settings:
Section "Monitor"
Identifier "Monitor genérico"
Option "DPMS"
HorizSync 30-70
VertRefresh 50-160
EndSection |
|
| 2009-01-06 17:51:30 |
Bryce Harrington |
title |
Incorrect screen resolution in Dapper LiveCD unless HorizSync and VertRefresh specified |
Incorrect screen resolution on Samtron 75E in Dapper LiveCD unless HorizSync and VertRefresh specified |
|
| 2009-01-06 17:58:15 |
Bryce Harrington |
xorg: status |
Confirmed |
Fix Released |
|
| 2009-01-06 17:58:15 |
Bryce Harrington |
xorg: importance |
Medium |
High |
|
| 2009-01-06 17:58:15 |
Bryce Harrington |
xorg: statusexplanation |
|
This is long since fixed in X. Resolution handling has been completely revamped since this bug was first reported.
The original issue was just that for some monitors it used to be that you had to manually specify H/V rates in order for the X to work because the install-time config generator wasn't able to detect that properly. But today those scripts are eliminated, and now X does all the resolution detection internally, which works like 99% of the time. (There are cases where it still fails, see https://bugs.edge.launchpad.net/ubuntu/+source/xorg-server/+bug/194760 as the main example, but these are rare corner cases now.)
Ricardo's last comment was in early 2007 which iirc was before much of this new stuff hit. I'm going to go ahead and make a guess that with the new resolution autodetection code, his problem went away, and will close the bug.
Other commenters on this bug have indicated their issues were solved by this change. Anyone else still having resolution detection problems - please report as a new bug, don't re-open this one. |
|
