Pipeline workaround on Eee Box incorrectly configures screens with DVI>VGA converter

Please attach logs separately rather than in a tarball, as it makes linking to them in upstream bug reports easier.

Can you describe your setup in more detail? Are you trying to do a dual screen setup with LVDS and a VGA monitor?

Ah nevermind, found some photos online, I understand.

Attached separately as requested.
Launchpad really needs mulitple file upload capabilities.

@Bryce Harrington
     > Can you describe your setup in more detail?
     Eee Box is directly connected to a Philips 170B LCD monitor via the DVI port.
     When the DVI>VGA converter is used, it's attached to the Eee Box and an analogue VGA cable is then connected to it and the VGA port on the monitor.

     > Are you trying to do a dual screen setup with LVDS and a VGA monitor?
     No, single screen as shown in the "no converter used" screen shot.

On Thu, Sep 11, 2008 at 11:57:39PM -0000, Caysho wrote:
> Launchpad really needs mulitple file upload capabilities.

Yeah I know. :-/

I did put a request for this directly to kiko when we met in London, so
I'm hopeful it will come soon.

Meanwhile, I have added xorg support to apport, so you can file bugs
against X using 'ubuntu-bug', and it will automatically attach all the
required files. Probably wouldn't have been applicable in this
particular case, but might be useful for future bug reports.

Bryce

have you tried xorg-xserver-video-intel patch?

@Lorenzo Z.
I don't want to test this on my main box, but what are the steps to do so ?

Only intrepid applies this patch. If you are using intrepid upgrade your system and remove the x.org workaround

Sorry for the double post but I've noticed that also Windows XP (SP3) doesn't choose the correct resolution (1280x720).

@Lorenzo Z.
I'm on hardy (8.04.1).

I tried booth alpha 5 and 6 of INtrepid on my B202. With alpha 5 Xorg did not work, with slightly before alpha 6 the Intel driver was changed, and now X starts and the 1600x1200 resolution is correctly detected on my monitor (I connected B202 to my monitor using a DVI to VGA adapter, since DVI on the monitor is used by my primary PC). The Alpha 6 live CD works fine too.
There might still be some problems since although the connected monitor works fine, two monitors are detected by X, this seems not to be a problem, but I am not sure that it does not unnecessarily drain system resources.

Please ask if you need any details, I am going to test most prereleases of Intrepid on the B202.

IzI

On this forum there are some other B202 owners:
http://forum.eeeuser.com/viewtopic.php?id=39698

IzI

I'm sorry for the offtopic, but lzl, have you found any issue with alpha6? I
suppose that Asus EEE Box have a GigaBit Intel Ethernet Adapter, so Ubuntu
Intrepid alpha 6 should have destroyed your ethernet adapter...

On Mon, Sep 22, 2008 at 10:42 AM, IzI <email address hidden> wrote:

> On this forum there are some other B202 owners:
> http://forum.eeeuser.com/viewtopic.php?id=39698
>
> IzI
>
> --
> Pipeline workaround on Eee Box incorrectly configures screens with DVI>VGA
> converter
> https://bugs.launchpad.net/bugs/268529
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Ciao Lorenzo,

The question is not out of topic, the problem should be researched and
commented on the forum, since there are not many B202 owners yet, such
problems could halt the testing.

I know there are firmware problems with recent kernel versions on many
distributions, but they did not manifest on my hardware, at least not with
the early alpha 6. But it is possible the guilty kernel version was an
update that came after 18. September.

Somebody should check the the B202 chip and compare it to the list of
affected chips.

IzI

On Sat, Sep 27, 2008 at 3:59 PM, Lorenzo Zolfanelli
<email address hidden>wrote:

> I'm sorry for the offtopic, but lzl, have you found any issue with alpha6?
> I
> suppose that Asus EEE Box have a GigaBit Intel Ethernet Adapter, so Ubuntu
> Intrepid alpha 6 should have destroyed your ethernet adapter...
>
> On Mon, Sep 22, 2008 at 10:42 AM, IzI <email address hidden> wrote:
>
> > On this forum there are some other B202 owners:
> > http://forum.eeeuser.com/viewtopic.php?id=39698
> >
> > IzI
> >
> > --
> > Pipeline workaround on Eee Box incorrectly configures screens with
> DVI>VGA
> > converter
> > https://bugs.launchpad.net/bugs/268529
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
>
> --
> Pipeline workaround on Eee Box incorrectly configures screens with DVI>VGA
> converter
> https://bugs.launchpad.net/bugs/268529
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "xserver-xorg-video-intel" source package in Ubuntu: Triaged
>
> Bug description:
> Binary package hint: xserver-xorg-video-intel
>
> I have an Asus Eee Box B202, and it has the pipeline issue described at
>
> https://bugs.launchpad.net/ubuntu/intrepid/+source/xserver-xorg-video-intel/+bug/233787
>
> caysho@minipc:~$ lsb_release -rd
> Description: Ubuntu 8.04.1
> Release: 8.04
>
> When checking the workaround with the DVI>VGA converter in response to
> Lorenzo Z's comment, the display does work but the correct resolution for my
> monitor (1280x1024) is not chosen.
>
> I have attached an tar.gz archive containing the following files:
>
> xorg_with_pipeline_workaround.conf [my working xorg.conf]
>
> xorg_with_workaround_no_vga_converter.log [xorg log with no VGA
> converter]
> xrandr_with_workaround_no_vga_converter.txt [xrandr verbose output with
> no VGA converter]
> ubuntu_resolution_utility_with_workaround_no_vga_converter.png [screenshot
> of ubuntu resolution utility, no VGA converter]
>
> xorg_with_workaround_and_vga_converter.log [xorg log with VGA converter]
> xrandr_with_workaround_and_vga_converter.txt [xrandr verbose output with
> VGA converter]
> ubuntu_resolution_utility_with_workaround_no_vga_converter.png [screenshot
> of ubuntu resolution utility with VGA converter]
>

I've moved to Ubuntu 8.10, and the resolution is selected correctly.
However, there is a weird artifact when using the Monitor Resolution Settings utility.
I'm attaching three screenshots.
The first is without the DVI > VGA converter (ie direct DVI connection). Mirror is not available for selection.
The second is with the converter, with the mirror tick box selected; the dialogue box has this set when the utility is first run.
The third is with the converter, without the tick box selected.

This is the third item.
Sorry, they're quite large; I didn't realise until I uploaded them. The second two files have been resized to 75% original size.
The quirk created for bug 233787 does select the correct resolution with the DVI > VGA converter, but it shows two screens available for selection. Looks like both pipelines are being detected when the converter is used.
The artifact I referred to above is present both with or without the converter - take note of the green rectangle in the top left hand corner with the text "Philips 17"".

Thanks for the screenshots. However in this case we also need the `xrandr --verbose` command line output for each case. This helps us determine whether the issue is in Xorg or the Screen Resolution tool.

I've attached the xrandr output for both configurations.
Has anyone else reported the artifact I'm seeing with the resolution utility ?

[This is an automatic notice.]

We'd like to forward your bug upstream, however upstream requires
that you first test it against their newer driver code.

To save you the effort of building the driver from source, we've built
packages for the driver and its new dependencies.

So you have a couple options:

 1. Download and test .debs for intrepid, from:
     https://edge.launchpad.net/~intel-gfx-testing/+archive

 -or-

 2. Download and test the Jaunty alpha-2 (or newer) Live CD,
     (which includes a beta of the new xserver 1.6 as well).
     See http://cdimage.ubuntu.com/releases/9.04/ for ISOs

Thanks ahead of time! You can simply reply to this email to report your
findings.

P.S., if you wish to forward your bug upstream yourself, please follow
these directions to do so:
  http://intellinuxgraphics.org/how_to_report_bug.html

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

I am attaching two xrandr --verbose logs, with and without the converter.
I used the 9.04 (alpha 3) iso.

Hardy has seen the end of its life and is no longer receiving any updates. Marking the Hardy task for this ticket as "Won't Fix".