Re: Using quirks to fix incorrect Monitor physical size

Re: Using quirks to fix incorrect Monitor physical size

[Nasa]

----- "Nasa" <nasa01@comcast.net> wrote:

> Hi,
> 
> Is there a way to tell the driver to use DisplaySize to pass the
> correct dimensions to
> the i915 driver?  from my searches, I saw the following note:
> 
> News: xf86-video-intel only supports KMS now
> 2010-02-11 - Jan de Groot
> 
> With the move of xf86-video-intel 2.10.0 to extra, support for UMS has
> been removed from the intel driver. This means that KMS is a
> requirement now.
> 
> 
> Does this mean that there's no way to override incorrect (or in my
> case) missing EDID info?  I am assuming so, 
> which is why I am asking about quirks.  Thanks in advance,
> 
So...

Given the lack of a response, I am guessing this means the drivers don't
support this capability.  Is there a reason for limiting user capabilities?  
Removing users ability to work around hardware issues just seems like the 
wrong way to go.  At least in my humble opinion.

Nasa

Re: Using quirks to fix incorrect Monitor physical size

[Felix Miata]

On 2010/09/13 10:10 (GMT) Nasa composed:

>> Is there a way to tell the driver to use DisplaySize to pass the
>> correct dimensions to
>> the i915 driver?  from my searches, I saw the following note:

>> News: xf86-video-intel only supports KMS now
>> 2010-02-11 - Jan de Groot

>> With the move of xf86-video-intel 2.10.0 to extra, support for UMS has
>> been removed from the intel driver. This means that KMS is a
>> requirement now.

>> Does this mean that there's no way to override incorrect (or in my
>> case) missing EDID info?  I am assuming so, 
>> which is why I am asking about quirks.  Thanks in advance,

> So...

> Given the lack of a response, I am guessing this means the drivers don't
> support this capability.  Is there a reason for limiting user capabilities?  
> Removing users ability to work around hardware issues just seems like the 
> wrong way to go.  At least in my humble opinion.

I'm not implying what you're asking for is unreasonable or too much to ask,
but have you tried Meego's vesa or fbdev drivers with KMS disabled? If those
don't cut it for you, maybe you just need to wait a while longer for the
Intel devs to replace more of what got discarded when UMS got dumped from its
driver. Maybe you need to file an xorg bug to help that along.

What was on the laptop when you bought it? You'd think the vendor would have
shipped something works with its hardware. I can't tell from
http://lists.freedesktop.org/archives/intel-gfx/2010-August/007907.html what
it was you bought.
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409

Felix Miata  ***  http://fm.no-ip.com/

Re: Using quirks to fix incorrect Monitor physical size

[Nasa]

----- "Felix Miata" <mrmazda@earthlink.net> wrote:

> On 2010/09/13 10:10 (GMT) Nasa composed:
> 
> >> Is there a way to tell the driver to use DisplaySize to pass the
> >> correct dimensions to
> >> the i915 driver?  from my searches, I saw the following note:
> 
> >> News: xf86-video-intel only supports KMS now
> >> 2010-02-11 - Jan de Groot
> 
> >> With the move of xf86-video-intel 2.10.0 to extra, support for UMS
> has
> >> been removed from the intel driver. This means that KMS is a
> >> requirement now.
> 
> >> Does this mean that there's no way to override incorrect (or in my
> >> case) missing EDID info?  I am assuming so, 
> >> which is why I am asking about quirks.  Thanks in advance,
> 
> > So...
> 
> > Given the lack of a response, I am guessing this means the drivers
> don't
> > support this capability.  Is there a reason for limiting user
> capabilities?  
> > Removing users ability to work around hardware issues just seems
> like the 
> > wrong way to go.  At least in my humble opinion.
> 
> I'm not implying what you're asking for is unreasonable or too much to
> ask,
> but have you tried Meego's vesa or fbdev drivers with KMS disabled? If
> those
> don't cut it for you, maybe you just need to wait a while longer for
> the
> Intel devs to replace more of what got discarded when UMS got dumped
> from its
> driver. Maybe you need to file an xorg bug to help that along.
> 
> What was on the laptop when you bought it? You'd think the vendor
> would have
> shipped something works with its hardware. I can't tell from
> http://lists.freedesktop.org/archives/intel-gfx/2010-August/007907.html
> what
> it was you bought.
> -- 
Actually,

This isn't a laptop.  It's a 7" monitor (http://www.lilliput.cn/EBY701-NP.html),
that I am using in my carpc.  I am presently try this with the IVI 
version of meego (with it's own issues).  Lilliput does provided drivers
for Windows, but nothing directly for Linux.  I have also verified that the 
monitor doesn't provide EDID data as the file size (I found were it's dump to, 
just can't recall right now) was 0.  Talking to Lilliput themselves hasn't 
been very helpful (I don't speak a 2nd language, and neither did the rep I
tried to talk too).

Nasa

BTW: thanks for the reply.

Re: Using quirks to fix incorrect Monitor physical size

[Felix Miata]

On 2010/09/13 11:42 (GMT) Nasa composed:

> This isn't a laptop.  It's a 7" monitor (http://www.lilliput.cn/EBY701-NP.html),
> that I am using in my carpc.  I am presently try this with the IVI 
> version of meego (with it's own issues).  Lilliput does provided drivers
> for Windows, but nothing directly for Linux.  I have also verified that the 
> monitor doesn't provide EDID data as the file size (I found were it's dump to, 
> just can't recall right now) was 0.  Talking to Lilliput themselves hasn't 
> been very helpful (I don't speak a 2nd language, and neither did the rep I
> tried to talk too).

Anything that is neither a standard format (4:3, 16:10 or 16:9) nor provides
valid EDID is just plain broken. I'd return it. If it's too late for free
return, maybe the vendor would allow exchange. If not, then try warranty
repair. Maybe a Lilliput support manager can authorize an attempt to get it
to output valid EDID either with a firmware update or otherwise.

Again, what about VESA or FBDEV drivers? No help?
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409

Felix Miata  ***  http://fm.no-ip.com/

Re: Using quirks to fix incorrect Monitor physical size

[The Fungi]

On Mon, Sep 13, 2010 at 11:42:22AM +0000, Nasa wrote:
[...]
> I have also verified that the monitor doesn't provide EDID data as
> the file size (I found were it's dump to, just can't recall right
> now) was 0.
[...]

You checked the size of the /sys/devices/*/*/drm/*/*/edid structure
(remember to cat it and redirect or pipe that through something,
since it's not a real file)?

   fungi@hastur:~$ cat '/sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-HDMI Type A-1/edid' | wc -c
   256

If memory serves, there was a commit to the driver a kernel rev or
two after KMS went in allowing explicit mode timings to be supplied
on as a kernel/driver parameter, though I'm having trouble digging
up the details now (I could also be misremembering and it just
allows you to pick among the additional non-preferred modes detected
by the driver).

For a while, I was stuck editing the kernel source and hacking the
default display timings to match my monitor, which was ugly but
definitely worked.

If you're using Xorg and can survive with no visible display until
after it starts (using a mode your driver supports but your monitor
does not), xrandr can be used to manually insert additional
modelines and switch to those (I used to do that in my ~/.xinitrc
until mode detection for my HDTV's HDMI input improved).
-- 
{ IRL(Jeremy_Stanley); PGP(97AE496FC02DEC9FC353B2E748F9961143495829);
SMTP(fungi@yuggoth.org); IRC(fungi@irc.yuggoth.org#ccl); ICQ(114362511);
AIM(dreadazathoth); YAHOO(crawlingchaoslabs); FINGER(fungi@yuggoth.org);
MUD(kinrui@katarsis.mudpy.org:6669); WWW(http://fungi.yuggoth.org/); }

Re: Using quirks to fix incorrect Monitor physical size

[Nasa]

----- "Felix Miata" <mrmazda@earthlink.net> wrote:

> On 2010/09/13 22:42 (GMT) Nasa composed:
> 
> > Felix Miata wrote:
> 
> >> Does Meego have /etc/sysconfig/videobios? I just discovered it on
> >> openSUSE
> 
> >> that file does not exist.
> 
> I've since discovered that was made obsolete nearly two years ago.
> 
> > Checked the meego install and no that file doesn't exist -- good
> suggestion
> > though.
> 
> > I also tried the VESA driver, which just ended up giving me a black
> screen.
> 
> What about the fbdev driver? What about the intellegacy driver? I
> don't see
> intellegacy in the Meego repo, but openSUSE 11.3 has it, so maybe if
> Meego
> doesn't have it incorporated in some larger package you can boot some
> live CD
> or DVD that does have it to see if it can make your display work
> properly.
> 
> Hmmm, IIRC a new quarterly Intel driver release is due RSN. Maybe that
> will
> be your answer.
> -- 
Felix,

I *really* appreciate you taking an interest in my issue.  You are correct in
that meego itself doesn't have the legacy driver available.  So the idea of 
using a live cd (or usb for me) is a resonable -- I will give it a go and 
give a report back.

Nasa

Re: Using quirks to fix incorrect Monitor physical size

[Nasa]

----- "Felix Miata" <mrmazda@earthlink.net> wrote:

> On 2010/09/13 11:42 (GMT) Nasa composed:
> 
> > This isn't a laptop.  It's a 7" monitor
> (http://www.lilliput.cn/EBY701-NP.html),
> > that I am using in my carpc.  I am presently try this with the IVI 
> > version of meego (with it's own issues).  Lilliput does provided
> drivers
> > for Windows, but nothing directly for Linux.  I have also verified
> that the 
> > monitor doesn't provide EDID data as the file size (I found were
> it's dump to, 
> > just can't recall right now) was 0.  Talking to Lilliput themselves
> hasn't 
> > been very helpful (I don't speak a 2nd language, and neither did the
> rep I
> > tried to talk too).
> 
> Anything that is neither a standard format (4:3, 16:10 or 16:9) nor
> provides
> valid EDID is just plain broken. I'd return it. If it's too late for
> free
> return, maybe the vendor would allow exchange. If not, then try
> warranty
> repair. Maybe a Lilliput support manager can authorize an attempt to
> get it
> to output valid EDID either with a firmware update or otherwise.
> 
> Again, what about VESA or FBDEV drivers? No help?
> -- 

I haven't tried those drivers yet (have to do it after work).  I'll have
to make sure these drivers will work with meego.  And I can't really return/
warranty exchange this monitor as it's been *modified* (ie removed from 
case) so that it fits nicely in my car.

Nasa

Re: Using quirks to fix incorrect Monitor physical size

[Felix Miata]

Does Meego have /etc/sysconfig/videobios? I just discovered it on openSUSE
11.4. It contains:
## Path:        System/Hardware/Graphicscard
## Description: Additional options for graphics cards
## Type:        yesno
## Default:     no
#
# Should the Intel(R) video BIOS be patched to let the X Server run with
# resolutions unknown to the BIOS? Warning, this is potentially dangerous,
# read the documentation in /usr/share/doc/packages/915resolution.
#
VIDEOBIOS_PATCH="no"

## Type:        string
## Default:
#
# The options passed to 915resolution, usually 3 numbers:
# the video mode to patch, X and Y resolution.
#
VIDEOBIOS_PARAMETERS=""

Note /usr/share/doc/packages/915resolution on the i845G system where I found
that file does not exist.
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409

Felix Miata  ***  http://fm.no-ip.com/

Re: Using quirks to fix incorrect Monitor physical size

[Nasa]

----- "Felix Miata" <mrmazda@earthlink.net> wrote:

> Does Meego have /etc/sysconfig/videobios? I just discovered it on
> openSUSE
> 11.4. It contains:
> ## Path:        System/Hardware/Graphicscard
> ## Description: Additional options for graphics cards
> ## Type:        yesno
> ## Default:     no
> #
> # Should the Intel(R) video BIOS be patched to let the X Server run
> with
> # resolutions unknown to the BIOS? Warning, this is potentially
> dangerous,
> # read the documentation in /usr/share/doc/packages/915resolution.
> #
> VIDEOBIOS_PATCH="no"
> 
> ## Type:        string
> ## Default:
> #
> # The options passed to 915resolution, usually 3 numbers:
> # the video mode to patch, X and Y resolution.
> #
> VIDEOBIOS_PARAMETERS=""
> 
> Note /usr/share/doc/packages/915resolution on the i845G system where I
> found
> that file does not exist.

Checked the meego install and no that file doesn't exist -- good suggestion
though.

I also tried the VESA driver, which just ended up giving me a black screen.
In fact, I had to blindly type in the terminal (after ctrl-alt-f1) to remove
the xorg.conf file so I could get things back :{

Re: Using quirks to fix incorrect Monitor physical size

[Felix Miata]

On 2010/09/13 22:42 (GMT) Nasa composed:

> Felix Miata wrote:

>> Does Meego have /etc/sysconfig/videobios? I just discovered it on
>> openSUSE

>> that file does not exist.

I've since discovered that was made obsolete nearly two years ago.

> Checked the meego install and no that file doesn't exist -- good suggestion
> though.

> I also tried the VESA driver, which just ended up giving me a black screen.

What about the fbdev driver? What about the intellegacy driver? I don't see
intellegacy in the Meego repo, but openSUSE 11.3 has it, so maybe if Meego
doesn't have it incorporated in some larger package you can boot some live CD
or DVD that does have it to see if it can make your display work properly.

Hmmm, IIRC a new quarterly Intel driver release is due RSN. Maybe that will
be your answer.
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409

Felix Miata  ***  http://fm.no-ip.com/

Using quirks to fix incorrect Monitor physical size

[Nasa]

Hi,

Is there a way to tell the driver to use DisplaySize to pass the correct dimensions to
the i915 driver?  from my searches, I saw the following note:

News: xf86-video-intel only supports KMS now
2010-02-11 - Jan de Groot

With the move of xf86-video-intel 2.10.0 to extra, support for UMS has been removed from the intel driver. This means that KMS is a requirement now.


Does this mean that there's no way to override incorrect (or in my case) missing EDID info?  I am assuming so, 
which is why I am asking about quirks.  Thanks in advance,

Nasa