@ Yannis T.
Please build latest Openchrome according to
https://help.ubuntu.com/community/OpenChrome
and apply patch which I attached
panel_pm800.patch
It is helps you?
** Attachment added: "panel_pm800.patch"
http://launchpadlibrarian.net/27011069/panel_pm800.patch
--
incorrect screen d
Unfortunately even the last trunk revision (747) does not fix this.
--
incorrect screen detection [openchrome]
https://bugs.launchpad.net/bugs/182778
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
** Changed in: openchrome
Status: Fix Released => New
--
incorrect screen detection [openchrome]
https://bugs.launchpad.net/bugs/182778
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
http://www.openchrome.org/trac/ticket/156
It is supposed to be in trunk.
--
incorrect screen detection [openchrome]
https://bugs.launchpad.net/bugs/182778
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubun
> Still not working. Is there anything we can do??
Flagging a patch would help. Given that there's 1 days until
FinalFreeze, there isn't much time for this being fixed for Jaunty
unless a patch already exists.
--
incorrect screen detection [openchrome]
https://bugs.launchpad.net/bugs/182778
You
There are no 16:9 or 16:10 resolutions reported by the driver, so there
is no matching with the monitor.
--
incorrect screen detection [openchrome]
https://bugs.launchpad.net/bugs/182778
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Still not working. Is there anything we can do??
--
incorrect screen detection [openchrome]
https://bugs.launchpad.net/bugs/182778
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
I can confirm that this bug is NOT fixed in the latest Jaunty version.
--
incorrect screen detection [openchrome]
https://bugs.launchpad.net/bugs/182778
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
I removed (i think it is not needed):
Modeline "1440x900" 103.97 1440 1496 1624 1856 900 900 902 933
I added:
Virtual 1440 900
but I cannot see what happens (I am using ssh), I'll see at Monday.
I would like to ask is there a way to see the resolution of the xserver (f
Please try it again by adding
Virtual 1440 900
to SubSection "Display"!
--
incorrect screen detection [openchrome]
https://bugs.launchpad.net/bugs/182778
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
The default is:
Section "Device"
Identifier "Configured Video Device"
EndSection
Section "Monitor"
Identifier "Configured Monitor"
EndSection
Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
Device "
Please attach your xorg.conf too!
--
incorrect screen detection [openchrome]
https://bugs.launchpad.net/bugs/182778
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.u
I have the same problem here. I tried to force 1440x900 but no luck :(.
I have removed the original monitor (it was broken) and I have tried
with 2 different monitors and I get a 1900x1200 (or so). I attach my
xorg log
** Attachment added: "Xorg.0.log"
http://launchpadlibrarian.net/24709908/Xor
With a fresh install of intrepid (8.10), your workaround works like a charm.
thank you
--
incorrect screen detection [openchrome]
https://bugs.launchpad.net/bugs/182778
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
I would like to confirm, that with a fresh installation of Hardy
(without update) the following workaround gave satisfactory results.
By modifying /etc/X11/xorg.conf with the following:
Section "Device"
Identifier "Configured Video Device"
Driver "openchrome"
Option "XaaNo
** Description changed:
Binary package hint: xserver-xorg-video-openchrome
I'm trying to run Hardy Alpha 3 on a Fujitsu/Siemens Amilo Li1705
laptop.
It has a (wide) screen of 1280x800 (according to Windows).
The live CD gives me a resolution of 1920x1200, which means that a lot
Updated package which is said to fix the bug is to be uploaded soon
** Changed in: xserver-xorg-video-openchrome (Ubuntu)
Status: Confirmed => In Progress
--
incorrect screen detection [openchrome]
https://bugs.launchpad.net/bugs/182778
You received this bug notification because you are a
** Changed in: openchrome
Status: New => Fix Released
--
incorrect screen detection [openchrome]
https://bugs.launchpad.net/bugs/182778
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
I tried the openchrome package at
https://launchpad.net/~atomo64/+archive and it seems to fix the
resolution problem with my HP 2133 when using the openchrome driver on
Ubuntu 8.10. I also had to add the following lines to to the device
section on /etc/X11/xorg.conf:
Option "XaaNoImageWriteRect"
O
I did some debugging on this yesterday. It appears that when the panel
is not supported it uses the function VBEValidateModes to choose the
resolution and virtual resolution. If you haven't any virtual sizes in
your xorg.conf file then the modeNames variable points to an empty
string. That causes t
Running with XaaNoImageWriteRect and svn599 packages I get correct
resolution only after system startup. If I log out, resolution is
broken.
And this is what I found, when I restarted X (X started with wrong resolution):
Oct 27 08:25:40 2133 kernel: [ 340.356792] Xorg[5166]: segfault at 0 ip
000
Rafał, can you post your /var/log/Xorg.0.log from a startup where screen
resolution detection fails?
--
incorrect screen detection [openchrome]
https://bugs.launchpad.net/bugs/182778
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
Okay, found screen lock up bug #274340. XaaNoImageWriteRect in display
section fixes that problem for my laptop.
I still get incorrect screen size detection as expected. And Raphael's
patch doesn't correct the problem for me as mine is K8M800.
--
incorrect screen detection [openchrome]
https://b
I've tried the packages from https://launchpad.net/~atomo64/+archive,
but X did not start until I put XaaNoImageWriteRect and "Display"
subsection with some modes into xorg.conf. It's a VIA P4M900 (Chrome 9
HC).
I'm on a clean Ibex (installed from the RC alternate cd and updated as
of October 25th
harrdydb, can you provide a copy of /var/log/Xorg.0.log after X fails to
configure properly? Without a log file it's impossible to say what's
going on for you.
Paul, please file a new bug about your crash. AFAICT it doesn't seem
related to screen size detection (which this bug is about).
Regardi
I'm having similar problems with an Acer 1362LC. Hardy incorrectly
guessed the screen size after install and I had to modify it manually.
With Intrepid RC I get a lock up after install. The only way in for me
now is to modify xorg.conf to use Driver "vesa".
@raphael, I tried your updated driver, s
but unfortunately it does not work. I tried the package on a cx700 and
it gives a maximum resolution of 1920x1200 while my monitor (LCD on the
DVI port) can handle only 1280x1024.
Btw I am also using VBEModes True because my panel otherwise does not
work, however it does give some scrambled/scroll
It's not my laptop and I can't play around with it unfortunately, so
somebody else will have to test your packages.
I actually did look at the code though, and there *is* convincingly-
looking detection code in there. I'm hopeful :-).
--
incorrect screen detection [openchrome]
https://bugs.laun
@Johan Walles: Xavier asked to *retry*, he didn't in any way imply that
it was fixed (although it might be :).
Could you please try the package at [1]? it is the latest revision by
upstream.
[1] https://launchpad.net/~atomo64/+archive
--
incorrect screen detection [openchrome]
https://bugs.laun
According to the upstream trac this is supposedly fixed in revision 594:
http://www.openchrome.org/trac/ticket/156
1:0.2.903-0ubuntu3 which is shipped in Intrepid right now is based on revision
588, which does not contain the fix:
http://www.openchrome.org/trac/browser/tags
Please upgrade the In
Same problem for me with Intrepid Ibex.
Here are the logs:
http://launchpadlibrarian.net/18049355/dmesg
http://launchpadlibrarian.net/18049330/Xorg.0.log
--
incorrect screen detection [openchrome]
https://bugs.launchpad.net/bugs/182778
You received this bug notification because you are a membe
I can confirm this with the 0 hz refres rate and have created another
bug report for the screen corruption under Bug 259389. I have also
reported it upstream. A confirmation would be great with information
about your exact graphic chipset.
--
incorrect screen detection [openchrome]
https://bugs.l
** Changed in: openchrome
Status: Unknown => New
--
incorrect screen detection [openchrome]
https://bugs.launchpad.net/bugs/182778
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.ubun
** Summary changed:
- Wrong resolution on Hardy
+ incorrect screen detection [openchrome]
--
incorrect screen detection [openchrome]
https://bugs.launchpad.net/bugs/182778
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
34 matches
Mail list logo
