@ Erick: many thanks for the suggestion, I'll create an account in
Ubuntu Forums as you suggested.

But I post also there the results of the last Ubuntu-based saturday,
when I did many installations and all of them affected by the
impossiblity to get a working x-server:

- 1st installation: Ubuntu 12.04.1 - i386 desktop version - the
installation is very slow, it freezes towards the end. The Livecd
session works very fine, correct maximum screen resolution, good
colours. Tried to install also from the Livecd session. Grub damaged.

- 2nd installation: Ubuntu 12.04.0 - i 386 desktop version - the
installation is quicker, but it freezes from livecd session (graphics
ok). In the direct installation it seizes up, but you can continue if
you continue to hold a key... at the end, grubs work (I can start XP
session and Ubuntu recovery mode), but during the loading, after a fast
appearing of the Ubuntu logo, it freezes in a dark screen... no way to
enter in a terminal. In the recovery  mode, I tried failsafeX session,
but after a while a "window" appears: the message says that it is
impossible to identify monitor and graphic card, then it returns to the
recovery menu without starting a low-resolution session

- 3rd installation: Kubuntu 12.04.1 - i386 desktop version - i don't try livecd 
session, I directly start with the installation. Also here I have to hold an 
any key to keep the installation ongoing, otherwise it freezes but it is 
sufficient to return to hold a key and it restarts. At the end, I have a 
working grub and it loads the system without freezing. At the beginning, all 
seems ok, the screen resolution is the correct WXGA and not the XGA that I had 
in the previous installation when I forced Kubuntu to use vesa drivers. 
After a little bit, the system begins to continuously crash, a message (I have 
been stupid not to literally write the contents, but I was quite tired...) 
appears and more or less says that 'probably a bad graphic driver is 
installed'. I try to reconfigure Xserver, but after about ten minutes the 
system becomes very slow, it's difficult to use it although the nice grapchic 
result... so I'm ready for...

- 4th installation: Ubuntu 12.04.0 - alternate version. Here the installation 
is very fast and smooth. When I restart, the Ubuntu logo appears but the 
loading freezes in the "usual dark" screen.  Then I did the same passage of 2nd 
installation with failsafeX and the same message that it's impossible to 
determine screen and graphic card... so I have created a xorg.conf file forcing 
to load openchrome as this: http://www.linlap.com/fujitsu_amilo_l7320gw
The system freezes during the loading, so in the 'usual' recovery mode I've 
modified the xorg.conf file replacing 'openchrome' with 'vesa' (sic!).

Ok, now the system starts, with the same problems of my first post here
(XGA resolution instead of WXGA, faded colours etc.)... am I correct if
I say that perhaps it's a bug of openchrome driver more than X-stack?

Excuse me if I've been a little bit talkative, but I desired only to be
clear... obviously now (with vesa) the system works also with 12.04.4
(after the updates).

@Erick: yes, the ram is 1gb, the cpu is that but later I'll create an
account for Ubuntu Forums as you said.

Thanks in advance.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-openchrome in
Ubuntu.
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” source package in Saucy:
  Won't Fix
Status in “xserver-xorg-video-openchrome” source package in Trusty:
  Fix Released

Bug description:
  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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to