My bug #118681 has just been marked a duplicate of this bug. That's fine
of course - but I probably could have marked it myself if the
description was clearer. I haven't changed it because I'm not 100% sure
I understand it, but I think the description should be "xresprobe sets
resolution to second
I like solution of Vedran Rodic very much. Juse use Xorg feature instead
of out-of-date tools. Generate monitor settings in xorg.conf like this:
Section "Monitor"
Identifier "minitor0"
Option "DPMS"
EndSection
I suppose it'll cause problems only with very old screen devices. And these
problem
I see that the
http://people.ubuntu.com/~bryce/Uploads/xresprobe_0.4.24ubuntu5.tar.gz
has not maid it into the daily builds yet..I had assumed it was. I also
see you have a specific line to have intel cards ddc probe. But really
the behavior should be:
1) First try to ddcprobe
2) If you do not hav
Oh forgot...while it's broken for my laptop .. it does not work
correctly for the Samsung 243T LCD.
--
Problems with xresprobe & Samsung 243T LCD
https://bugs.launchpad.net/bugs/27667
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ub
Yes version xresprobe 0.4.24 is BROKEN. So the function "doprobe()" is
totally .. utterly broken! It probably shouldn't even be used at all. I
can't even figure out what the hack of script that is lcdsize.sh
actually supposed to be doing correctly. Now replacing the call from
"doprobe()" with "dodd
ok something broke. When I try the daily live CD (9/28/07) with my Thinkpad
T61 with intel x3100 graphics. It defaults to 1024x768 as opposed to 1400x900.
Now interesting is when I run xresprobe as root I get the following output:
# xrespobe intel
id:
res: 1024x768
freq:
disptype: lcd/lvds
So b
xresprobe (0.4.24ubuntu5) gutsy; urgency=low
* xorg.conf: Fix xprobe.sh failure caused by missing type1 module;
this was dropped by Debian for xserver 1.3 since it's obsolete and
has some security issues. (Addresses portion of fix for 127008)
* xresprobe: Fix issue in alternate instal
I absolutely agree. With the post-install giving too low a resolution
it would def. give a bad impression of Ubuntu, esp. on an LCD where a
lower resolution (ie non-native) tends to make fonts and such a much
poorer readibility. I'm very happy w/ the work being done in Gutsy w/
the new GUI tool t
Jerone, I've taken over the X maintainership from daniels. I am of the
opinion that you are correct on this bug. Dropping the highest
resolution was a bad design decision; the real problem here is that the
code is using poor logic to tell the difference between an lcd and a
crt, and as a result i
For upload:
http://people.ubuntu.com/~bryce/Uploads/xresprobe_0.4.24ubuntu5*
** Changed in: xresprobe (Ubuntu)
Importance: Medium => High
Target: None => ubuntu-7.10-rc
--
Problems with xresprobe & Samsung 243T LCD
https://bugs.launchpad.net/bugs/27667
You received this bug notificati
** Changed in: xresprobe (Ubuntu)
Status: Unconfirmed => Confirmed
--
Problems with xresprobe & Samsung 243T LCD
https://bugs.launchpad.net/bugs/27667
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubu
Actually that time I didn't :-O . But I just tried it commenting out the
mode lines with the Nvidia (Proprietary) driver. Worked like a charm
automatically come up at 1900x1200 . Acutally this is how Fedora Core
does there X configurations. They list no mode lines for resolution and
just read off t
Yeah, the goal is that X can do this by itself, and I guess other
distros are using "get-edid|parse-edid" or something similar to make
this happen. Since your get-edid output is similar to the one I get on
my samsung syncmaster 900NF monitor, I guess that X discards your
monitors edid information t
Nvidia driver & NV driver seem to read the edid just fine. Also on other
distros things are fine...but when I run get-edid under Feisty I get
this:
[EMAIL PROTECTED]:~# get-edid
get-edid: get-edid version 1.4.1
Performing real mode VBE call
Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0
Jerone, I share your emotions about fixing this bug, because I''ve seen
a lot of instances of ubuntu showing the wrong resolution for both CRT
and LCD displays. Other debian based linux distributions (such as
knoppix) actually used get-edit|parse-edid to generate X configuration
Monitor section, wh
Edgy still suffers from this problem. Noone has as of yet to address
this.
--
Problems with xresprobe & Samsung 243T LCD
https://launchpad.net/bugs/27667
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Can anyone test this out with a Feisty nightly and/or a currently
updated Edgy so we can see if this bug still exists?
--
Problems with xresprobe & Samsung 243T LCD
https://launchpad.net/bugs/27667
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinf
17 matches
Mail list logo
