After quite a long gap I have finally got around to changing from the nVidia
drivers to the vesa ones. I did try to use the Nouveau ones but they were
excluded by default and when I allowed the kernel module to be loaded my system
froze at boot just as the warning comment said.
(From my
Of course... now I have the vesa drivers running I might have some fun getting
a Dual Output nVidia card to work in dual-head mode and if I cannot get two
monitors working it will be hard to check for the problem.
Any suggestions on where to look for vesa multi-monitor help?
Tom - BlueArc
Package: xorg
Version: 1:7.5+8
Severity: normal
Same problem as before, I have not moved over to the non-nvidia drivers
but I shall look to do so soon.
-- Package-specific info:
X server symlink status:
lrwxrwxrwx 1 root root 13 Oct 27 2010 /etc/X11/X - /usr/bin/Xorg
Package: xorg
Version: 1:7.5+8
Severity: normal
After having updated to the latest nvidia-driver the problem still seems
to be present. I will investigate switching to the non-nvidia
alternative as suggested previously.
-- Package-specific info:
X server symlink status:
Well I feel slightly foolish but plenty of searching has not provided an asnwer
I am confident in yet.
What is the cleanest way for me to update my nvidia driver to the one in
testing? At present the most clear instructions I can find are at
http://wiki.debian.org/NvidiaGraphicsDrivers but
Did you reboot after updating the driver? Or manually stop Xorg, unload
the old nvidia kernel module and restart X?
There should have been a debconf notice explaining this.
I did keep an eye out for anything asking me to restart X or similar as I was
expect it. I have not done that yet so I
Slight problem with my setup not matching our local Debian mirror but not that
is fixed I updated to the unstable version easily using
sudo apt-get -t unstable install nvidia-glx
I can even confirm that the Nvidia settings panel thinks I am using the updated
driver.
I will set a reminder
) to 280.13-1 (unstable). If
I don't see anything for a couple of months after the driver update I will try
to post an update to this bug.
Tom - BlueArc Corporation
-Original Message-
From: Andreas Beckmann [mailto:deb...@abeckmann.de]
Sent: 29 August 2011 10:15
Cc: Thomas Thorne; 625
Package: xorg
Version: 1:7.5+8
Severity: normal
Reoccurrence this morning, just the same as before but I am now using
Synergy to share my keyboard with my windows machine instead. Just as
before my mouse pointer between the two screen and only responds to
mouse movments in a limited way. Only a
I was advised by someone that the work around for this is to specify separate
profiles for each instance of iceweasel by using the -P profile option. It
seems that only one instance of iceweasel can have read/write access to the
profile at a time and starting a second instance will either fail
Package: Xorg
Version: 1:7.5+8
Severity: important
When I get in after leaving my machine runnin overnight and clear the
screen saver by moving the mouse the Xorg progress sometimes locks up.
I have a system with two displays attached and it seems that this may be
caused by moving the mouse from
My xorg.conf:
# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings: version 1.0 (pbuilder@c203) Tue May 18 07:56:38 UTC 2010
Section ServerLayout
Identifier Layout0
Screen 0 Screen0 0 0
Screen 1 Screen1 1600 460
InputDevice
Now that I have got an xsession back I can confirm that me screen saver is set
to Blank Screen, Regard the computer as idel after 9min, activate screensaver
when computer is idel, Lock screen when screensaver is active and in power
management my computer is set to never go to sleep and to put
I have just spotted that bug
#576183http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576183 looks a lot
like this bug apart from the fact that this one only occurs after the screen
has been powered off after beind idle but #576183 sounds like it happens all
the time. The symptoms sound very
I may have just raised a bug very much like this one; I missed it when I was
filing the report with reportbug. My new bug is
625813http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625813. I only
experience a problem like the one described here when I wake up my screen after
it as entered the
This means that the -display option is ineffective on it's own, but no mention
is made of using -no-remote in the man page.
It also seems that I cannot have two window instances using the same profile,
even if they are on the same screen, using the -no-profile option. What seems
to work well
would be using them in a variety of ways.
-Original Message-
From: Mike Hommey [mailto:m...@glandium.org]
Sent: 08 February 2011 08:41
To: Thomas Thorne; 612...@bugs.debian.org
Subject: Re: Bug#612304: How many new profiles
On Tue, Feb 08, 2011 at 08:26:08AM +, Thomas Thorne wrote
Hommey [mailto:m...@glandium.org]
Sent: 08 February 2011 09:58
To: Thomas Thorne; 612...@bugs.debian.org
Subject: Re: Bug#612304: How many new profiles
On Tue, Feb 08, 2011 at 09:15:47AM +, Thomas Thorne wrote:
The problem is that using different profiles is not really what most
people would
Package: epiphany-browser
Version: 2.30.6-1
Severity: normal
It was noted that this behaviour was targeted for fixing before v1 but I have
just seen the same behaviour in v2.30.6. Not that many people were using
multi-head displays 8 years ago when this bug first surfaced but it is now
becoming
19 matches
Mail list logo
