** Attachment added: lspci.txt
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1439786/+attachment/4366631/+files/lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1439786
Title:
Christopher you were absolutely right. The nouveau-firmware package was
not installed.
But even now after installing it, adding an initramfs hook and creating
a new initrd the driver does not seem to load correctly.
Attached I added the new dmesg and lspci -vvv output.
** Attachment added:
Just started Ubuntu live CD to see if the problem is also there. Using the live
CD I can see a different xrandr output:
ubuntu@ubuntu:~$ xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
LVDS-1 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected
Finally the problem was coming from passing nomodeset to the kernel
command line.
Now I have full screen resolution but there is still an issue refreshing
the screen sometimes.
When switching between windows, scrolling, moving the mouse and just
writing some text the screen gets scrumbled. None
Public bug reported:
As requested in https://bugs.launchpad.net/nvidia-drivers-
ubuntu/+bug/1314367 I open a new bug for my system.
After a fresh installation of Vivid I only have a resolution of
1024x768.
Using xrandr and a custom xorg.conf file I might be able to get a bigger
resolution (not
Yesterday I uninstalled the nvidia driver and tried to get the nouveau
to work. As the nouveau does not recognize the proper resolution I have
to use xrandr to create and add a new one.
As a lack of time I have not completely solved this issue yesterday. At
least with the default (and maximal
On the 02.03 I installed the 15.04 development version from scatch. With
nouveau I never had a resolution available wich was more than 1024x768
unless using xrandr after installation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yes that is exactly what they said.
Mail from support:
The bug looks bad and we would love to fix it.
But I discussed this with our product manager, and was informed that
there are no updates planned to the 340 driver branch and that this
older tesla generation graphics card will only be
I opened a bug at Nvidia. Short answer: no fix :-(
So I am left alone with an almost useless notebook
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1314367
Title:
10de:0cbc [HP EliteBook 8540w]
I'm using the nvidia driver which is included in the 15.04 version:
340.76-0ubuntu1
ii nvidia-340 340.76-0ubuntu1
amd64NVIDIA binary driver - version 340.76
ii nvidia-340-uvm
Finally I could not wait and installed the new version of Ubuntu today.
Even installing all the updates did not change anything. The flickering
is still there and none of the described workarounds are working.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I'm afraid I can't install it on my laptop for now. How do I use the
nvidia driver from the live cd? By default the nouveau driver is loaded.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1314367
I already installed the latest BIOS long time ago.
dmidecode -s bios-version
68CVD Ver. F.50
dmidecode -s bios-release-date
07/08/2014
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1314367
Title:
Still no success. Freshly installed Ubuntu 14.10 with Nvidia driver
331.89-0ubuntu5.
CCSM workaround mentioned above in this thresd still does not solve the
issue.
The system is completely useless with this flickering.
--
You received this bug notification because you are a member of Ubuntu
Still for me there is no workaround. Even if the above mentioned
workaround seems to be working for some it does not for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1314367
Title:
Flickering
Still no luck. All workarounds don't help in my case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1314367
Title:
Flickering with Ubuntu 14.04 and nvidia card reappeared
To manage notifications
Also this workaround does not solve the issue for me. I hope there will
be a solution soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1314367
Title:
Flickering with Ubuntu 14.04 and nvidia card
Thanks, but also this workaround does not help in my case. It improves
the situation a little bit, but the flickering is still there.
Especially when switching between multiple windows.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Unfortunately I can't confirm this workaround. In my case it just
doesn't flicker directly after starting the computer. After a short
moment using it the flickering reappears.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yes it is not updating correctly. Especially when switching between
different aplications.
The Gmail thin I have never noticed so far. But I'm rarely using it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
As requested in Bug #1310633 I'm opening a new bug.
With a previous version of Ubuntu I already had this flickering. With
additional options for the kernel module I was able to fix the
flickering.
options nvidia NVreg_RegistryDwords=PerfLevelSrc=0x NVreg_Mobile=3
After upgrading to 14.04 I also have this flickering problem again. It seems
that the old line in options.conf:
options nvidia NVreg_RegistryDwords=PerfLevelSrc=0x NVreg_Mobile=3
NVreg_ModifyDeviceFiles=0
is not read anymore (I found this somewhere in the net and it solved the
issue on
Me too I can confirm that this patch solves the issue.
--
stickynotes_applet crashed with SIGSEGV
https://bugs.launchpad.net/bugs/422110
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
Whenever I attach my Western Digital My Book to my HP EliteBook 8530w I
get a Kernel OOps. When using it in this state I get a corrupted
filesystem (ext3).
I never see this problem on an older HP nc6120 notebook running Ubuntu
9.04 when attaching the same disk.
ProblemType:
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/32004551/AlsaDevices.txt
** Attachment added: BootDmesg.gz
http://launchpadlibrarian.net/32004552/BootDmesg.gz
** Attachment added: Card0.Amixer.values.txt
http://launchpadlibrarian.net/32004553/Card0.Amixer.values.txt
With the latest version of libapache2-svn everything is ok again.
Bug can be closed now.
--
Apache2 mod_dav_svn.so cannot be loaded anymore
https://bugs.launchpad.net/bugs/242886
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Public bug reported:
Binary package hint: libapache2-svn
Today I upgraded my Intrepid system. The upgrade installed apache2
2.2.9-1
Since then I cannot start my Apache server due to undefined symbols in
libapache2-svn.
When starting Apache 2 I get the following error.
apache2: Syntax error on
At this time I used the intel driver. Currently I'm using FBDev.
After changing to the default ubuntu splash the problem disappeared.
Only when using a customized usplash theme I don't have any visible
fonts in xorg.
As it is a long time ago I don't know, if the problem still persists. I
think I
Attached is a part of the term.log showing which packages have been
installed today
** Attachment added: term.txt
http://launchpadlibrarian.net/10726768/term.txt
--
xorg 7.3 no font
https://bugs.launchpad.net/bugs/173920
You received this bug notification because you are a member of Ubuntu
Public bug reported:
I'm running Hardy since Gutsy was finally released. So far there was no
problem because I really carefully upgraded.
Before upgrading essential packages on my base installation I upgrade
them in a virtual machine to see if everything is working fine.
Now I did the same
I made some more testing. It seems that there is something wrong with
usplash which results in fonts not being displayed in X.
I started my Ubuntu notebook into recovery mode and from there I changed
the runlevel. After doing this I was able to work as usual.
So I created a new entry in menu.lst
I have the same problem on my fujitsu-siemens e8410 with a dual core
cpu. It is just blocked at 800 MHz.
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 Duo CPU T7100 @ 1.80GHz
stepping: 13
cpu MHz
According cpufreq-info the cpu is known correctly, but it seems, that a
policy is blocking the speed between 800 and 800 MHz
What looks cpufrequtils 002: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to [EMAIL PROTECTED], please.
analyzing CPU 0:
driver: acpi-cpufreq
33 matches
Mail list logo
