[Ubuntu-x-swat] [Bug 1267742] Re: Screen artifacts appear after restart and cold boot

2016-02-11 Thread Mélodie
PS: I want to check next in Trusty if the newer kernel 3.13.0-77 is less
friendly than the former one, 3.13.0-76 in this situation, with that one
hardware (the town on which I installed yesterday : I'll have it back to
run tests on it). So I'll report the full specs to help debug this
issue.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1267742

Title:
  Screen artifacts appear after restart and cold boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1267742/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1267742] Re: Screen artifacts appear after restart and cold boot

2016-02-11 Thread Mélodie
Hello,

I installed Ubuntu Trusty on an old tower yesterday, which has an
integrated nvidia Geforce 7* so this is "nouveau" running on that
machine, and after a while, when clicking on some menu the mouse
suddenly freezes, and there is this strange look on the screen, looking
a lot like what Elfy describes.

This happened after the distro was installed and updated. I have been
able to install a few packages, but then it froze again. I could not use
the SysRQ, it didn't work.

This morning on my own tower, which now runs Xenial I hit the same issue : 
which never happened before! But my tower has the same kind of nvidia internal 
GPU, an old Geforce 7, and I can't use the nvidia driver because it's now 
unable to display the resolution properly. So I thought the fault must be the 
nouveau driver (or firmware? I can't know that).
I also tried to ssh my tower using my laptop, but the frozen machine was 
unreachable.

I don't know why I can't attach more than one file here (using Firefox
44.0.1 but never could before). So I paste down here the 80 last lines
of the most relevant syslog I could find, the one that has the timestamp
from just before it froze, there is a part related to nouveau in it:

*
Feb 11 10:33:40 bento64 ntpd[1696]: peers refreshed
Feb 11 10:33:40 bento64 ntpd[1696]: Listening on routing socket on fd #23 for 
interface updates
Feb 11 10:33:40 bento64 ntp[1684]: ...done.
Feb 11 10:33:46 bento64 systemd[1]: Stopping LSB: Start NTP daemon...
Feb 11 10:33:46 bento64 ntp[1721]: * Stopping NTP server ntpd
Feb 11 10:33:46 bento64 ntpd[1696]: ntpd exiting on signal 15
Feb 11 10:33:46 bento64 ntp[1721]: ...done.
Feb 11 10:33:46 bento64 systemd[1]: Stopped LSB: Start NTP daemon.
Feb 11 10:33:56 bento64 ntpdate[1734]: adjust time server 178.33.227.201 offset 
-0.289198 sec
Feb 11 10:33:56 bento64 systemd[1]: Starting LSB: Start NTP daemon...
Feb 11 10:33:56 bento64 ntp[1765]: * Starting NTP server ntpd
Feb 11 10:33:56 bento64 ntpd[1776]: ntpd 4.2.6p5@1.2349-o Mon Dec  7 13:51:58 
UTC 2015 (1)
Feb 11 10:33:56 bento64 ntpd[1777]: proto: precision = 0.116 usec
Feb 11 10:33:56 bento64 systemd[1]: Started LSB: Start NTP daemon.
Feb 11 10:33:56 bento64 ntpd[1777]: ntp_io: estimated max descriptors: 1024, 
initial socket boundary: 16
Feb 11 10:33:56 bento64 ntpd[1777]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 
123
Feb 11 10:33:56 bento64 ntp[1765]: ...done.
Feb 11 10:33:56 bento64 ntpd[1777]: Listen and drop on 1 v6wildcard :: UDP 123
Feb 11 10:33:56 bento64 ntpd[1777]: Listen normally on 2 lo 127.0.0.1 UDP 123
Feb 11 10:33:56 bento64 ntpd[1777]: Listen normally on 3 eth0 192.168.1.5 UDP 
123
Feb 11 10:33:56 bento64 ntpd[1777]: Listen normally on 4 virbr0 192.168.122.1 
UDP 123
Feb 11 10:33:56 bento64 ntpd[1777]: Listen normally on 5 lo ::1 UDP 123
Feb 11 10:33:56 bento64 ntpd[1777]: Listen normally on 6 eth0 
fe80::6e62:6dff:fef5:1334 UDP 123
Feb 11 10:33:56 bento64 ntpd[1777]: peers refreshed
Feb 11 10:33:56 bento64 ntpd[1777]: Listening on routing socket on fd #23 for 
interface updates
Feb 11 10:34:04 bento64 systemd[1]: Starting Stop ureadahead data collection...
Feb 11 10:34:04 bento64 systemd[1]: Stopped Read required files in advance.
Feb 11 10:34:04 bento64 systemd[1]: Started Stop ureadahead data collection.
Feb 11 10:37:14 bento64 systemd[1206]: Time has been changed
Feb 11 10:37:14 bento64 systemd[1]: Time has been changed
Feb 11 10:37:59 bento64 anacron[688]: Job `cron.daily' started
Feb 11 10:37:59 bento64 anacron[1790]: Updated timestamp for job `cron.daily' 
to 2016-02-11
Feb 11 10:46:24 bento64 org.gtk.vfs.Daemon[1220]: A connection to the bus can't 
be made
Feb 11 10:46:24 bento64 systemd[1]: Created slice User Slice of melodie.
Feb 11 10:46:24 bento64 systemd[1]: Starting User Manager for UID 1000...
Feb 11 10:46:24 bento64 systemd[1]: Started Session c2 of user melodie.
Feb 11 10:46:24 bento64 systemd[1835]: Reached target Sockets.
Feb 11 10:46:24 bento64 systemd[1835]: Reached target Timers.
Feb 11 10:46:24 bento64 systemd[1835]: Reached target Paths.
Feb 11 10:46:24 bento64 systemd[1835]: Reached target Basic System.
Feb 11 10:46:24 bento64 systemd[1835]: Reached target Default.
Feb 11 10:46:24 bento64 systemd[1835]: Startup finished in 104ms.
Feb 11 10:46:24 bento64 systemd[1]: Started User Manager for UID 1000.
Feb 11 10:46:25 bento64 systemd[1]: Stopping User Manager for UID 104...
Feb 11 10:46:25 bento64 systemd[1206]: Reached target Shutdown.
Feb 11 10:46:25 bento64 systemd[1206]: Starting Exit the Session...
Feb 11 10:46:25 bento64 systemd[1206]: Stopped target Default.
Feb 11 10:46:25 bento64 systemd[1206]: Stopped target Basic System.
Feb 11 10:46:25 bento64 systemd[1206]: Stopped target Paths.
Feb 11 10:46:25 bento64 systemd[1206]: Stopped target Timers.
Feb 11 10:46:25 bento64 systemd[1206]: Stopped target Sockets.
Feb 11 10:46:25 bento64 systemd[1206]: Received SIGRTMIN+24 from PID 1848 
(kill).
Feb 11 10:46:25 bento64 systemd[1]: Stopped User Manager for 

[Ubuntu-x-swat] [Bug 1378940] Re: Video to slow

2015-10-24 Thread Mélodie
Hi,

>From your XorgConf.txt file: the Driver in use is VESA! How can you ask
for the driver not loaded to boost the Matrox card? It's mga which
should be loaded.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-mga in Ubuntu.
https://bugs.launchpad.net/bugs/1378940

Title:
  Video to slow

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp