[Ubuntu-x-swat] [Bug 353208] Re: screen resolution badly detected on FujitsuSiemens Amilo Pro V2010

2009-05-27 Thread Bartosz
Please attach Xorg.0.log from openchrome with applyied patch. Try use CTRL+ALT+F1, or just attach Xorg.log.old after reboot. This information will be useful in adding panel support for your chipset. -- screen resolution badly detected on FujitsuSiemens Amilo Pro V2010 https://bugs.launchpad.ne

[Ubuntu-x-swat] [Bug 353208] Re: screen resolution badly detected on FujitsuSiemens Amilo Pro V2010

2009-05-22 Thread qaculda
I tried to build openchrome with your patch, but I can't conform if it works, because on my screen was just grey fog(but computer reacted normally). I've had to reinstall xserver-xorg-video-openchrome package from repository. Editing of /etc/X11/xorg.cong(the Display subsection) worked. ** Attach

[Ubuntu-x-swat] [Bug 353208] Re: screen resolution badly detected on FujitsuSiemens Amilo Pro V2010

2009-05-21 Thread Bartosz
Please build, install the latest openchrome version according to: https://help.ubuntu.com/community/OpenChrome apply patch: panel_pm800.patch and check if its helps. Attach your Xorg.log ** Attachment added: "panel_pm800.patch" http://launchpadlibrarian.net/27010492/panel_pm800.patch ** C

[Ubuntu-x-swat] [Bug 353208] Re: screen resolution badly detected on FujitsuSiemens Amilo Pro V2010

2009-05-21 Thread Bartosz
In the Xorg.log, there is a message: (WW) CHROME(0): Panel on K8M800, PM800 and VM800 is currently not supported. (WW) CHROME(0): Using VBE to set modes to work around this. And this is a problem. Please try workaround this bug by add to xorg.conf in Section "Screen", following lines: SubSecti

[Ubuntu-x-swat] [Bug 353208] Re: screen resolution badly detected on FujitsuSiemens Amilo Pro V2010

2009-05-19 Thread Martin Olsson
** Package changed: xorg (Ubuntu) => xserver-xorg-video-openchrome (Ubuntu) ** Changed in: xserver-xorg-video-openchrome (Ubuntu) Status: Incomplete => New -- screen resolution badly detected on FujitsuSiemens Amilo Pro V2010 https://bugs.launchpad.net/bugs/353208 You received this bug no