[Bug 1205643] Re: VIA P4M800 graphics broken in Lubuntu/Xubuntu Saucy & 12.04.4 candidate

[Alberto Jovito]

This function is only for source compatibility with old drivers. source:
http://lists.x.org/archives/xorg-devel/2012-August/033405.html

 Not only these drivers was removed this call..
http://lists.x.org/archives/xorg-devel/2012-November/034541.html
https://build.opensuse.org/package/view_file/openSUSE:13.1/xf86-video-
siliconmotion/U_Remove-miInitializeBackingStore.patch?expand=1

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1205643

Title:
  VIA P4M800 graphics broken in Lubuntu/Xubuntu Saucy & 12.04.4
  candidate

Status in “xserver-xorg-video-openchrome” package in Ubuntu:
  Fix Released
Status in “xserver-xorg-video-openchrome-lts-saucy” package in Ubuntu:
  Incomplete
Status in “xserver-xorg-video-openchrome” source package in Saucy:
  Fix Released
Status in “xserver-xorg-video-openchrome” source package in Trusty:
  Fix Released

Bug description:
  * Impact:
  - the driver doesn't work with the X.org version in 12.04 with the Saucy hardware enablement stack.

  * Test case:
  - try using 12.04 with the Saucy hardware enablement stack on a machine needing the openchrome driver.

  * regression potential:
  - check that xorg sessions work as they should. The patches have received testing in Debian/Trusty/Saucy and upstream, so presumably should be fairly safe. The number of people using openchrome is relatively small compared to the main X drivers, so the scope of risk is rather small here.

  ----------
  Saucy Hardware Enablement Stack:

  https://wiki.ubuntu.com/Kernel/LTSEnablementStack

  -------

  Please bear with me and read all of this. Since I can't get a working
  display in Saucy with that graphics chip I need to use this method to
  file the initial bug report, but I can provide info using a chroot or
  replacing the "quiet splash" boot parameter with "text" which takes me
  to a tty interface.

  I hope using the tty interface provided by using the "text" boot
  parameter I can use "apport-collect" to collect the info needed from
  an installed Lubuntu 13.10 but I won't do so until asked by a dev in
  case some "switch" needs to be set to collect the appropriate info.

  I also want to say that I'm fully aware that graphics chip is not
  supported by Ubuntu/compiz itself, or even GNOME's mutter window
  manager, but I think it should still work with the openbox, metacity,
  and Xfwm window managers ...... at least I hope so :^)

  So onto what actually happens. When I try to boot either Lubuntu or
  Xubuntu Saucy Alpha 2, either the live image or an installed version,
  I just get a frozen progress bar. So it's just 5 frozen dots on the
  screen. If I try booting through the recovery mode or otherwise trying
  to "startx" or "'sudo service lightdm start' I just get a blank
  screen. I can see the backlight is working but that's all.

  This is the specific hardware:

  VIA C7 CPU @ 1500MHz
  VIA CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] (rev 01)
  VIA VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
  Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78)
  1GB DDR2 RAM

  I did take a pic of the live image boot process while dealing with an
  unrelated d-i bug during Lubuntu Alpha 2 testing process:

  https://launchpadlibrarian.net/145894508/P4M800_xfreeze.JPG

  Now I'm wondering what else to say ............... the same Saucy
  images and installs work with two other totally different sets of
  hardware.

  I'm ready to roll up my sleeves to help gather any needed info. Thanks
  in advance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-openchrome/+bug/1205643/+subscriptions