Activity log for bug #91222

Date Who What changed Old value New value Message
2007-03-10 19:59:39 Andris Sprūds bug added bug
2007-03-10 20:00:12 Andris Sprūds bug added attachment 'dmesg.log' (dmesg.log)
2007-03-10 20:00:30 Andris Sprūds bug added attachment 'lspci-vvnn.log' (lspci-vvnn)
2007-03-10 20:00:59 Andris Sprūds bug added attachment 'uname.log' (uname -a)
2007-03-10 20:01:42 Andris Sprūds bug added attachment 'xorg.conf' (xorg.conf)
2007-03-10 20:02:45 Andris Sprūds description The highest resolution supported by Feisty is 1024x768, although my monitor's, Samsung SyncMaster 913n native resolution is 1280x1024. The highest resolution supported by Feisty is 1024x768, although my monitor's, Samsung SyncMaster 913n native resolution is 1280x1024. It seems that xorg.conf actually contains the correct resolution, but somehow System->Preferences->Display resolution applet won't show it in the list of available resolutions.
2007-03-10 20:03:32 Andris Sprūds description The highest resolution supported by Feisty is 1024x768, although my monitor's, Samsung SyncMaster 913n native resolution is 1280x1024. It seems that xorg.conf actually contains the correct resolution, but somehow System->Preferences->Display resolution applet won't show it in the list of available resolutions. The highest resolution supported by Feisty is 1024x768, although my monitor's, Samsung SyncMaster 913n native resolution is 1280x1024. It seems that xorg.conf actually contains the correct resolution, but somehow System->Preferences->Display resolution applet won't show it in the list of available resolutions. I have the latest Feisty (including all updates). Edgy detects the correct resolution without any problems.
2007-03-10 22:40:50 magilus None: status Unconfirmed Needs Info
2007-03-10 22:40:50 magilus None: statusexplanation Xorg is using the vesa driver because it does not support your video card (or autodetection fails). Which video card do you use?
2007-03-11 00:42:06 magilus xorg: status Needs Info Confirmed
2007-03-11 00:42:06 magilus xorg: statusexplanation Xorg is using the vesa driver because it does not support your video card (or autodetection fails). Which video card do you use? Okay, so auto detection fails with Feisty. Just a work around for you: In xorg.conf replace Driver "vesa" with Driver "nv"
2007-03-11 00:43:51 magilus description The highest resolution supported by Feisty is 1024x768, although my monitor's, Samsung SyncMaster 913n native resolution is 1280x1024. It seems that xorg.conf actually contains the correct resolution, but somehow System->Preferences->Display resolution applet won't show it in the list of available resolutions. I have the latest Feisty (including all updates). Edgy detects the correct resolution without any problems. The NVIDIA GeForce2 MX-400 is not being autodetected on Feisty. Instead, Ubuntu uses the ugly vesa driver. The autodetection (nv should be used) worked on releases prior to Feisty.
2007-03-11 00:43:51 magilus title 1280x1024 screen resolution not supported in Feisty NVIDIA GeForce2 MX-400 not autodetected on Feisty
2007-03-14 06:07:28 Timo Aaltonen xorg: status Confirmed Fix Released
2007-03-14 06:07:28 Timo Aaltonen xorg: statusexplanation Okay, so auto detection fails with Feisty. Just a work around for you: In xorg.conf replace Driver "vesa" with Driver "nv" The newest discover-data release should fix this. Please retry with a daily livecd-snapshot or the beta which is released next week, and reopen if it still fails.
2007-03-17 16:11:47 magilus discover-data: status Fix Released Confirmed
2007-03-17 16:11:47 magilus discover-data: statusexplanation The newest discover-data release should fix this. Please retry with a daily livecd-snapshot or the beta which is released next week, and reopen if it still fails. Reopening then.
2007-06-27 15:09:58 Kyle McMartin title NVIDIA GeForce2 MX-400 not autodetected on Feisty NVIDIA GeForce2 MX-400 not autodetected
2007-06-27 15:10:10 Kyle McMartin discover-data: status Confirmed Fix Released
2007-06-27 15:10:10 Kyle McMartin discover-data: statusexplanation Reopening then. Fixed in gutsy discover-data.