Ubuntu
xserver-xorg-video-openchrome package

[P4M900] Chrome9 doesn't display fullscreen-mode correctly

Bug #163405 reported by Jonas H on 2007-11-17

This bug affects 1 person

	Status	Importance	Assigned to
Xorg Xserver VESA	Fix Released	Undecided	Unassigned
xserver-xorg-video-openchrome (Ubuntu)	Fix Released	High	Unassigned
xserver-xorg-video-vesa (Ubuntu)	Fix Released	Undecided	Unassigned

Bug Description

Hello,
i've got a VN896-VIA-Unichrome9 Chipset.
The problem is that everytime a game or an application wants to change to fullscreen-mode, the Xserver displays only colourfull stripes so I cannot work on and have to restart the X.
I'm using the vesa-driver in 1280x800 resultion.
This bug is there since i'm using Ubuntu Gutsy, with Feisty i hadn't got this problem.

Tags:

Revision history for this message

Adam Niedling (krychek) wrote on 2008-08-23:

I have the same graphic chipset, there is still no decent driver for it. However I don't have the problem you're describing. Has it been resolved in Hardy maybe?

Revision history for this message

Jonas H (jonash) wrote on 2008-08-24:

No - for me, it hasn't.

Revision history for this message

Timo Aaltonen (tjaalton) wrote on 2008-09-25:

you can't be using the vesa driver with that resolution, since it only supports 4:3 modes.

Please try 8.10.

Changed in xorg:
status:	New → Incomplete

Revision history for this message

Jonas H (jonash) wrote on 2008-09-25:

@Timo Aaltonen: That's rubbish, I'm using it with a 1280x800 resolution every day.
See here: http://daui.lophus.org/shots/various/xorg.conf_geany.png

Cheers :D

Revision history for this message

Timo Aaltonen (tjaalton) wrote on 2008-09-25:

well, attach your /var/log/Xorg.0.log to be sure. I'll bet that it's using the openchrome driver ;)

Revision history for this message

Jonas H (jonash) wrote on 2008-09-26:

Xorg.0.log Edit (59.3 KiB, text/plain)

See attachment.

$ cat /var/log/Xorg.0.log | grep openchrome

$ cat /var/log/Xorg.0.log | grep vesa
(II) LoadModule: "vesa"
(II) Loading /usr/lib/xorg/modules/drivers//vesa_drv.so
(II) Module vesa: vendor="X.Org Foundation"
(II) VESA: driver for VESA chipsets: vesa
(--) Chipset vesa found

Michael Nagel (nailor) on 2008-11-02

Changed in xserver-xorg-video-openchrome:
status:	Incomplete → New

Revision history for this message

Michael Nagel (nailor) wrote on 2008-12-29:

is this still an issue with intrepid/jaunty. if yes, please set to confirmed as it really seems to be a bug, then.

Changed in xserver-xorg-video-openchrome:
status:	New → Incomplete

Revision history for this message

Bryce Harrington (bryce) wrote on 2009-01-31:

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.

Changed in xserver-xorg-video-openchrome:
status:	Incomplete → Invalid

Revision history for this message

Jonas H (jonash) wrote on 2009-01-31:

Oh, dammit - I forgot. I'm not able to test this using intrepid nor jaunty. In Intrepid, X doesn't even start (it displays a black screen). In Jaunty, after logging in via gdm (which works fine [ignoring wrong display resolutions]), X doesn't change the picture anymore (even not mouse-moving or stuff like that).

Changed in xserver-xorg-video-openchrome:
status:	Invalid → Incomplete

Michael Nagel (nailor) on 2009-03-02

Changed in xserver-xorg-video-openchrome:
status:	Incomplete → New

Revision history for this message

Bartosz Kosiorek (gang65) wrote on 2009-03-30:

#10

I think this error was resolved in the latest version of the openchrome.

See:
http://www.openchrome.org/trac/ticket/260

Build and install the latest openchrome driver according to:
https://help.ubuntu.com/community/OpenChrome

Bartosz Kosiorek (gang65) on 2009-05-06

Changed in xserver-xorg-video-openchrome (Ubuntu):
status:	New → Invalid

Revision history for this message

Bartosz Kosiorek (gang65) wrote on 2009-07-08:

#11

Attach the output of `lspci -vvnn` command.

Revision history for this message

Bartosz Kosiorek (gang65) wrote on 2009-07-08:

#12

Please attach also Xorg.0.log file from Jaunty.

After start gdm (or X) try to switch to terminal by pressing CTRL+ALT+F1 and attach your Xorg.0.log file.
It is located at /var/log/Xorg.0.log

Next build/install the latest openchrome driver and enable debug mode.
The detail instruction is available at:
https://help.ubuntu.com/community/OpenChrome

Changed in xserver-xorg-video-openchrome (Ubuntu):
status:	Invalid → Incomplete
importance:	Undecided → High

Revision history for this message

Jonas H (jonash) wrote on 2009-07-08:

#13

I'd like to test wether fullscreen support is provided in jaunty (which I got installed and working after some long nights).

Can you suggest an application that uses "true" fullscreen mode but not 3d graphics (which aren't working with that chip)?

Revision history for this message

Bartosz Kosiorek (gang65) wrote on 2009-07-22:

#14

To use fullscreen mode, you can download Diablo 2 Demo and run it under wine.

Could you attach your Xorg.0.log file?
It is necessary to resolve this bug.

Bartosz Kosiorek (gang65) on 2009-07-22

summary:

- vesa: Chrome9 doesn't display fullscreen-mode correctly
+ [P4M900] Chrome9 doesn't display fullscreen-mode correctly

Revision history for this message

Jonas H (jonash) wrote on 2009-07-23:

#15

Xorg.0.log Edit (74.0 KiB, text/plain)

Just tried diablo 2 and it seems like fullscreen mode works. If you still need my Xorg.o.log, see attachments.

Revision history for this message

Timo Aaltonen (tjaalton) wrote on 2009-07-29:

#16

seems like it's fixed for openchrome, which you are using according to the logfile.

Changed in xserver-xorg-video-openchrome (Ubuntu):
status:	Incomplete → Fix Released

Revision history for this message

Bryce Harrington (bryce) wrote on 2009-11-27:

#17

Hi dauerbaustelle,

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with the latest development release of Ubuntu? (ISO CD images are available from http://cdimage.ubuntu.com/releases/)

If it remains an issue, could you also attach a new /var/log/Xorg.0.log?
Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags:	added: needs-verification
Changed in xserver-xorg-video-vesa (Ubuntu):
status:	New → Incomplete

Revision history for this message

Jonas H (jonash) wrote on 2009-11-29:

#18

Bryce, I think this has been fixed in Karmic.

Revision history for this message

Bryce Harrington (bryce) wrote on 2010-05-13:

#19

[This is an automatic notification.]

Hi dauerbaustelle,

This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?

Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal support channels, please see:

http://www.ubuntu.com/support

If you are the original reporter and can still reproduce the issue on
Lucid, please run the following command to refresh the report:

apport-collect 163405

If you are not the original reporter, please file a new bug report, so
we can work with you as the original reporter instead (you can reference
bug 163405 in your report if you think it may be related):

ubuntu-bug xorg

If by chance you can no longer reproduce the issue on Lucid or if you
feel it is no longer relevant, please mark the bug report 'Fix Released'
or 'Invalid' as appropriate, at the following URL:

https://bugs.launchpad.net/ubuntu/+bug/163405