Re: [Bug 296437] Re: vesa doesn't let me set my LCD resolution

2008-11-28 Thread tz
On Fri, Nov 14, 2008 at 1:48 AM, Bryce Harrington
[EMAIL PROTECTED] wrote:
 [This is an automated message]

 Hi thomas-mich,


 Please attach the output of `lspci -vvnn`, and attach your 
 /var/log/Xorg.0.log file from after reproducing this issue.  If you've made 
 any customizations to your /etc/X11/xorg.conf please attach that as well.


 ** Changed in: xorg (Ubuntu)
   Status: New = Incomplete

 --
 vesa doesn't let me set my LCD resolution
 https://bugs.launchpad.net/bugs/296437
 You received this bug notification because you are a direct subscriber
 of the bug.



** Attachment added: lspci-vvnn.txt
   http://launchpadlibrarian.net/20041514/lspci-vvnn.txt

** Attachment added: Xorg.0.log
   http://launchpadlibrarian.net/20041515/Xorg.0.log

-- 
vesa doesn't let me set my LCD resolution
https://bugs.launchpad.net/bugs/296437
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


Re: [Bug 296437] Re: vesa doesn't let me set my LCD resolution

2008-11-14 Thread tz
I will do this later (my battery on the laptop now refuses to recharge
so I have to be careful) however I don't know what this has to do with
the complete inability to manually set the device.

To quote the original bug:

Vesa comes up in 800x600.  There is no official way in intrepid to set
it to the correct resolution of 1024x768.

THE BUG IS THAT INTREPID DELETED THE ABILITY TO MANUALLY SET THE
INFORMATION, not that you can't chase down every possible hardware
combination.

I DON'T WANT THIS PARTICULAR LAPTOP AND SCREEN SUPPORTED WITH A
ONE-OFF CHANGE.  Then if I get a new laptop I will be in the same
place with the same bug report and yet another PCI bus information
dump and will still have to find the displayconfig-gtk utility to make
it work.

I can appreciate that something is going wrong in the monitor
detection and probably should be fixed, but something which worked
under Hardy and back was REMOVED from Intrepid.  The via/chrome driver
barely worked in edgy, and has gotten worse with each new release.
But at least I had ways of getting around the brokenness.  Now
Intrepid has apparently removed any ability for me to fix it.

Before, if the detection was broken, the configuration could be set
manually in an easy fashion.  Now with intrepid, if the detection is
broken, you're stuck with a horrible failsafe mode that cannot be
corrected - and may not be corrected at all if you don't find
something in the hardware dump.

On Fri, Nov 14, 2008 at 1:48 AM, Bryce Harrington
[EMAIL PROTECTED] wrote:
 [This is an automated message]

 Hi thomas-mich,


 Please attach the output of `lspci -vvnn`, and attach your 
 /var/log/Xorg.0.log file from after reproducing this issue.  If you've made 
 any customizations to your /etc/X11/xorg.conf please attach that as well.


 ** Changed in: xorg (Ubuntu)
   Status: New = Incomplete

 --
 vesa doesn't let me set my LCD resolution
 https://bugs.launchpad.net/bugs/296437
 You received this bug notification because you are a direct subscriber
 of the bug.


-- 
vesa doesn't let me set my LCD resolution
https://bugs.launchpad.net/bugs/296437
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs