@Luciano: it seems to me that you have a dual AMD system. I don't see
any signs of the problem mentioned in this bug report. Maybe it's a
different problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: nvidia-graphics-drivers-352 (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1511272
Title:
[4.3] patch to avoid dkms issue
To
Unfortunately fglrx does not support RandR 1.4. The only solution, in
your case, would be to use multiple xscreens which I think Kubuntu
supports but Ubuntu doesn't (because of Compiz). Unfortunately we do not
support this use case. If you do decide to go down this path, you will
probably want to
ti 2>/dev/null
+ rm -rf /etc/ati 2>/dev/null
# Finally move ati into /etc
mv /etc/ati.dpkg-bak /etc/ati 2>/dev/null || true
** Changed in: fglrx-installer (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: fglrx-installer (Ubunt
On 28-10-15 06:31:17, Martin Pitt wrote:
> So, let's try this again: What is this grepping of syslogs trying to do?
> Can we replace this with checking for presence/absence of
> /sys/module/?
>
The module can be loaded on boot and then it can (automatically) be
unloaded (at some point) if the GPU
On 28-10-15 13:56:42, Martin Pitt wrote:
> > The module can be loaded on boot and then it can (automatically) be
> unloaded (at some point) if the GPU is disabled in a hybrid system.
>
> Then I suggest to install an udev rule like
>
> ACTION=="remove", SUBSYSTEM=="module", DEVPATH=="*/nvidia",
** Changed in: fglrx-installer (Ubuntu)
Importance: Undecided => High
** Changed in: fglrx-installer-updates (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry, the actual versions are fglrx-installer_15.201-0ubuntu2~15.10.1
and fglrx-installer-updates_15.201-0ubuntu2~15.10.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1493888
Title:
FGLRX
** Description changed:
+ SRU Request:
+
+ [Impact]
+
+ The fglrx driver is not compatible with gcc 5.x. This causes the kernel
+ module to crash on initialisation. As a result, users will boot into a
+ black screen, as X will fail (except on Intel+AMD hybrid systems, where
+ intel is used).
+
@SRU team: please accept fglrx-installer_15.201-0ubuntu1~15.10.1 and
fglrx-installer-updates_15.201-0ubuntu1~15.10.1 in wily-proposed.
@all: please wait for the update. We are going to need testers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I'm reopening the bug report, as more can definitely be done to solve
the problem.
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On 27-10-15 10:42:01, Luca Weiss wrote:
> @Timo Aaltonen, #88 works for me on HD7970. I think these are the same
> packages?
>
Yes, they are the same packages (only with a slightly different
revision) but we need users to test the packages in wily-proposed (it's
the standard procedure)
--
You
Public bug reported:
The fglrx packages should blacklist amdgpu so that the said driver does
not prevent fglrx from loading.
** Affects: fglrx-installer (Ubuntu)
Importance: High
Assignee: Alberto Milone (albertomilone)
Status: In Progress
** Affects: fglrx-installer-updates
@Luciano: can you reproduce the problem and attach the following files
please?
1) the dmesg ouput
2) /var/log/gpu-manager.log
3) /var/log/Xorg.0.log
** Changed in: fglrx-installer (Ubuntu Wily)
Status: Fix Released => In Progress
** Changed in: fglrx-installer (Ubuntu Wily)
On 27-10-15 18:11:26, Flavio Elawi wrote:
> TESTED on R9 285 and it works.
> i had to manually do #1510573 to blacklist amdgpu and add the nomodeset flag
> for the kernel.
>
Good point. That would be LP: #1510573
It should be fixed in Xenial (fglrx 2:15.201-0ubuntu3). I am working to
SRU that
On 27-10-15 17:47:55, Roger Barrett wrote:
> It both works and doesn't work for me.
>
> The kernel module is fine, the X Server loads and seems to open the device
> correctly, but the screens stay blank, then turn off.
> The attached tar file has dmesg output and the Xorg and gpu-manager log
>
Also, please keep in mind that there is no journalctl in 14.04. It's
probably worth adding a check for it in the code.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1307069
Title:
gpu-manager
On 27-10-15 15:19:39, Bryan Quigley wrote:
> I tried to moving some of the syslogs to journalctl again.. much better
> results. - http://pastebin.ubuntu.com/12980242/
>
> Should I just propose merges to the wily branch or is there an upstream
> for this project?
>
Please use our git branch:
u Wily)
Importance: Undecided => High
** Changed in: fglrx-installer (Ubuntu Wily)
Assignee: (unassigned) => Alberto Milone (albertomilone)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/14
I have just uploaded the workaround in Xenial (16.04). If you see the
main task marked as fix released, that refers to 16.04. An SRU for 15.10
will follow.
Note: the packages for 16.04 will also work on 15.10, if you can't wait
for the official update.
** Summary changed:
- FGLRX incompatible
I am going to test the workaround here, and request an SRU for it. I
will also involve AMD to see if we can get an actual fix for it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1493888
Title:
On 24-10-15 18:37:06, Nerdknight wrote:
> The patch in #29 also works for me, with a 6700M card. If you install
> fglrx you must uninstall radeon drivers
>
That is already dealt with by the package. I imagine gpu-manager
disabled fglrx when it failed.
--
You received this bug notification
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: New => Triaged
** Changed in: ubuntu-drivers-common (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Good point. The current code (i.e. fnmatch.fnmatch()) is case sensitive
because the OS is.
** Changed in: ubuntu-drivers-common (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
I've just committed a fix in our git branch. The first step would be to
upload this to xenial.
It seems to me that we need to backport the fix to Wily. If so, are
there any bugs triggered by this problem?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: nvidia-graphics-drivers-352 (Ubuntu)
Status: New => Triaged
** Changed in: nvidia-graphics-drivers-352-updates (Ubuntu)
Status: New => Triaged
** Changed in: nvidia-graphics-drivers-352-updates (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albe
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1500591
Title:
ubuntu-drivers-common should not care about
On 22-10-15 17:44:52, xpris wrote:
> Very strange. I use Ubuntu 15.04 and I install kernel 4.2.0 from ubuntu ppa
> kernel team and use kolasa patch https://github.com/kolasa/fglrx-core-15.201
> and kernel and fglrx driver works fine.
Maybe there is something that we are missing in our patches
On 20-10-15 22:34:49, Doug McMahon wrote:
> A "regression in the intel driver" doesn't seem to explain why this was not
> an issue in a gnome session, nor to the fact that -
> xset dpms force off
> xset dpms force on
> returned display both in greeter & session
> (and nvidia driver loaded &
On 20-10-15 15:01:27, Bryan Quigley wrote:
> Find seems to be the other big time culprit:
> - "find /lib/modules/$(uname -r) -name '%s*.ko' -print",
> + "find /lib/modules/$(uname -r)/updates/dkms -name '%s*.ko'
> -print",
>
> Do we always know that the modules will be
@Paolo: not yet. We are going to fix this ASAP.
I have added an entry in the release notes for now.
Sorry for the inconvenience.
** Changed in: ubuntu-release-notes
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: ubuntu-release-notes
Status: Confirmed =&g
** Changed in: ubuntu-release-notes
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1493888
Title:
FGLRX incompatible with kernel 4.2
To manage notifications about
-video-intel (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1507676
Title:
Nvidia-Prime not switching from intel to nvidi
** Changed in: fglrx-installer (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1493888
Title:
FGLRX incompatible with kernel
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: Triaged => In Progress
** Changed in: ubuntu-drivers-common (Ubuntu)
Importance: Medium => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: ubuntu-drivers-common (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: ubuntu-drivers-common (Ubuntu)
Importance: Undecided => Medium
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: Confirmed => Triaged
--
You
** Also affects: xserver-xorg-video-intel (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: xserver-xorg-video-intel-lts-vivid (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: xserver-xorg-video-intel (Ubuntu Vivid)
Importance: Undecided
@Alistair: the system didn't really change in your case. It's just that
when you first run gpu-manager, it will have no records on any previous
runs (comparing "last cards number = 0" with "How many cards? 1"), so it
will try to configure your system. It should only happen the first time,
unless
Please remove and reinstall the drivers, then attach your /var/log/gpu-
manager.log . The kernel module doesn't seem to be there.
** Changed in: nvidia-graphics-drivers-352 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This is not really a bug in ubuntu-drivers-common. Those are just
debugging messages (no actual error there). I can probably get rid of
them but still that doesn't explain why a second xserver was started.
Maybe another user logged into the system from lightdm? Or maybe lightdm
is acting funny for
@sru-team: my code should be in trusty-proposed now. Please approve it
for testing.
P.S. the code is also in wily-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1471708
Title:
SRU: For
** Changed in: ubuntu-drivers-common (Ubuntu)
Assignee: (unassigned) = Alberto Milone (albertomilone)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1454642
Title:
my xorg.conf gets renamed
I can build the same code in a vivid chroot without seeing any failures.
My guess is that something else (python-apt? python-aptdaemon?) changed
in the archive.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: ubuntu-drivers-common (Ubuntu)
Assignee: (unassigned) = Alberto Milone (albertomilone)
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: New = Confirmed
** Changed in: ubuntu-drivers-common (Ubuntu)
Importance: Undecided = High
--
You received this bug
I can confirm that the updates solve the problem here. The amdcccle
panel can be launched correctly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1471661
Title:
[SRU] Regressions in the -core
** Description changed:
+ [Impact]
+ An update to the lts-vivid backported kernel (3.19.0-26) pulled in a commit
that made pci_ignore_hotplug() GPL only. As a result, the DKMS module fails.
+
+ [Test Case]
+ Install the new packages and check that DKMS doesn't fail.
+
+ [Regression Potential]
gpu-manager.log shows two cards being available at the following
addresses:
Vendor/Device Id: 8086:412
BusID PCI:0@0:2:0
Is boot vga? yes
Vendor/Device Id: 10de:1184
BusID PCI:1@0:0:0
Also, no nvidia driver seems to be available (strangely enough the
kernel module is available):
Error: no
** Changed in: ubuntu-drivers-common (Ubuntu)
Importance: Low = Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096363
Title:
Add '--help' to hybrid-detect
To manage notifications about
you might want to try again with the latest ubuntu-drivers-common, which
now comes with better support for dual AMD powerxpress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1417952
Title:
[HP
** Changed in: hwe-next
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1410801
Title:
[AMD Richland + Topaz XT ] gpu-manager generated xorg.conf is not
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1298693
Title:
gpu-manager crashed with SIGSEGV in
On 14-08-15 10:52:23, teo1978 wrote:
This, while unfortunate, is not a bug,
Yes it is. You are only giving a diagnosis of the exact cause of the bug
(which by the way I already knew), but that doesn't make it less of a
bug.
The alternatives switched back to automatic mode, and in automatic
On 13-08-15 16:50:40, teo1978 wrote:
By design a driver will be enabled if you install it.
However, if it is disable when you UPGRADE the driver, it shouldn't be
reenabled.
Right, that usually doesn't happen when you upgrade to a new version of
the same driver (for example upgrading
On 13-08-15 16:45:47, teo1978 wrote:
2) Optimus is supported by the NVIDIA driver.
That's not what NVidia told me. I asked for support and they told me it's
officially unsupported on Linux.
And what I can tell for sure is that it doesn't work. The screen switching
issue is well known.
please reproduce the problem and attach the following files:
/var/log/Xorg.0.log
/var/log/Xorg.0.log.old
/var/log/kern.log
/var/log/gpu-manager.log
** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a
On 14-08-15 13:24:50, teo1978 wrote:
Such work is not necessary, as yours is really an unsupported corner
case. If you insist on keeping the nvidia driver installed and disabled,
against what we recommend, that is your problem.
And how was I supposed to know what you recommend?
Back in
Just to clarify:
1) Do not install the driver unless you want to use it. Uninstalling the
driver will not break your system. By design a driver will be enabled if
you install it. We keep an option to disable the driver but that's only
to be used by gpu-manager (which is part of
Another update: yesterday I submitted my new code for a review
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1471708
Title:
SRU: For skylake system, u-s-d cause a black screen when resume from
S3
On 11-08-15 22:45:43, teo1978 wrote:
So, will my 331 drivers be automagically replaced with 340, or with
whatever version fixes the bug? (or perhaps they have already?) Because
otherwise, the bug is not fixed for me nor for the millions of people
having ubuntu 14.04 with 331 drivers. Anyway,
On 12-08-15 13:33:31, teo1978 wrote:
Yes, 331 will be replaced by 340 through a system update.
Nice, but is it possible that it not only replaces 331 by 340 but ALSO
ENABLES THEM?
Because I'm under the impression that that just happened to me, and
that's a bug.
Ages ago, when I first
@ciro: that could be caused by a number of things. If you can ssh into
the machine, or VT switch by pressing CTRL+ALT+F2, please collect the
following data:
1) the output of dkms status
2) the dmesg output
3) /var/log/Xorg.0.log
4) /var/log/gpu-manager.log
--
You received this bug notification
** Changed in: fglrx-installer (Ubuntu)
Assignee: (unassigned) = Alberto Milone (albertomilone)
** Changed in: fglrx-installer-updates (Ubuntu)
Assignee: (unassigned) = Alberto Milone (albertomilone)
** Also affects: fglrx-installer (Ubuntu Trusty)
Importance: Undecided
Just to make it clear, the status of this bug report was marked as Fix
released because the fix was actually released, and it's available to
you as long as you have the trusty-updates repositories enabled (which
should be enabled by default).
--
You received this bug notification because you are
On 31-05-15 03:23:09, KennoVO wrote:
Nice! Will this work with the 3.13 kernel in 14.04 ? Also, do you have
any idea when it will be available to end-users?
Yes, the update is available in 14.04, and works with the kernels 14.04
ships with.
--
You received this bug notification because you
I wrote a fix, the Desktop team reviewed it, and they requested some changes
before they merge my code, as you can see in the following code review:
https://code.launchpad.net/~albertomilone/unity-settings-daemon/non-blocking-touch-mapping-wily/+merge/266248
I am still working to adjust my code
I've just managed to reproduce the error. It happens when gpu-manager
tries to write to a log it doesn't have write access to. I'm surprised
there's no check for that.
** Changed in: ubuntu-drivers-common (Ubuntu)
Assignee: (unassigned) = Alberto Milone (albertomilone)
** Changed in: ubuntu
-drivers-common (Ubuntu Trusty)
Assignee: (unassigned) = Alberto Milone (albertomilone)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1298693
Title:
gpu-manager crashed with SIGSEGV
Correct, as long as the trusty-updates repository is enabled, both 340
and 346 will be available.
I recommend installing 346 (the system will upgrade to 340 from 331),
since 340 is a legacy driver.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Branch linked: lp:~albertomilone/unity-settings-daemon/non-blocking-
touch-mapping-wily
** Branch linked: lp:~albertomilone/unity-settings-daemon/non-blocking-
touch-mapping-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Mike: the system doesn't seem to be configured properly. You appear to
be using mesa, whereas only nvidia or nvidia-prime alternatives are
supported. If you attach the following files after reproducing the
problem, maybe I can help:
1) /var/log/gpu-manager.log
2) /var/log/Xorg.0.log
3)
I'm working on it, and I hope to have something available for testing
soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1471708
Title:
SRU: For skylake system, u-s-d cause a black screen when
Public bug reported:
As per the topic, kernel 4.2rc2 panics in Wily. This is probably caused
by CONFIG_OF, which is now enabled on X86_64.
:~$ apt-cache policy linux-image-4.2.0-040200rc2-generic
linux-image-4.2.0-040200rc2-generic:
Installed: 4.2.0-040200rc2.201507121935
Candidate:
** Attachment added: A screenshot of the kernel panic
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1474447/+attachment/4428865/+files/IMG_20150714_173935.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On 31-05-15 13:51:33, Andrey wrote:
Affected this bug on
Asus Transformer Flip TP500LN
Intel HD 4600, Nvidia GeForce 840m, Ubuntu 14.04 x64
sudo prime-select nvidia
Error: alternatives are not set up properly
Error: nvidia mode can't be enabled
Can you attach the output of the following
Iain Lane added some feedback. They won't merge the patch as is:
https://code.launchpad.net/~timchen119/unity-settings-daemon/unity-
settings-daemon.1471708.trusty/+merge/264163
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
OEM LP private bug: https://bugs.launchpad.net/bugs/1466441
Title: Sometimes system turns a black screen when resume from S3 via Lid
Close
[Impact]
Sometimes system turns a black screen when resume from S3 via Lid Close
It only has cursor on screen but
@Jeremy: what do you mean by settings?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310489
Title:
xorg.conf overwritten by booting system
To manage notifications about this bug go to:
** Changed in: unity-settings-daemon (Ubuntu)
Status: New = Triaged
** Changed in: unity-settings-daemon (Ubuntu)
Importance: Undecided = High
** Changed in: unity-settings-daemon (Ubuntu)
Assignee: (unassigned) = Alberto Milone (albertomilone)
--
You received this bug
I created a merge request of Tim's branch into the 14.04 branch.
** Changed in: unity-settings-daemon (Ubuntu)
Status: Triaged = In Progress
** Description changed:
OEM LP private bug: https://bugs.launchpad.net/bugs/1466441
Title: Sometimes system turns a black screen when resume
nvidia-graphics-drivers-346, nvidia-graphics-drivers-346-updates,
nvidia-graphics-drivers-340, nvidia-graphics-drivers-340-updates are
still in (trusty-proposed) NEW, pending approval. Can an admin take care
of this, please?
--
You received this bug notification because you are a member of
** Description changed:
As per the topic, a couple of regressions were introduced as part of the
work on the core package split. This can cause build issues with the
packages missing files.
- The problem is fixed upstream and in wily.
+ The problem is fixed upstream.
--
You received
** Summary changed:
- Remove the extra dones from for loops in debian/rules
+ Regressions in the -core packages split
** Description changed:
- As per the topic, three extra dones were introduced as part of the
+ As per the topic, a couple of regressions were introduced as part of the
work on
Assignee: Alberto Milone (albertomilone)
Status: Fix Released
** Affects: fglrx-installer (Ubuntu Trusty)
Importance: High
Assignee: Alberto Milone (albertomilone)
Status: In Progress
** Affects: fglrx-installer (Ubuntu Vivid)
Importance: High
Assignee: Alberto
** Description changed:
- As per the topic, a couple of regressions were introduced as part of the
- work on the core package split. This can cause build issues with the
- packages missing files.
+ [Impact]
+ As per the topic, a couple of regressions were introduced as part of the work
on the
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1469895
Title:
no alternatives for x86_64-linux-gnu_gfxcore_conf
To manage
It's not really an error, more of a warning, which suggests that there
is a problem only if you are using the fglrx driver (on AMD GPUs). There
is no need for you to fix anything.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
- Deliver new upstream releases of the nvidia binary drivers for 14.04.3
+ SRU Request:
+
+ [Impact]
+ The nvidia packages in Ubuntu 14.04 do not support the backported kernel from
15.04.
+
+ [Test Case]
+ 1) Enable the trusty-proposed repository, and install the
Just an update. I filed an SRU, and uploaded all the new nvidia packages
(that will also fix this problem) in LP: #1465706 . The SRU team will
review it and make it available for testing. You might want to keep an
eye on it, and provide feedback when the packages are approved and
available for
yes, your gpu-manager.log says that the nvidia driver is enabled. I'm
glad things work now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1362098
Title:
No proprietary driver available for nVidia
by reproducing the problem, I meant installing the nvidia-331 package
(do not use the installer from NVIDIA's website), letting the system
crash, and collecting the logs for me.
Also, please do not try to blacklist nouveau. It's all done
automatically. Simply type the following and reboot:
sudo
: New = In Progress
** Changed in: nvidia-settings (Ubuntu Trusty)
Milestone: None = ubuntu-14.04.3
** Changed in: nvidia-settings (Ubuntu Trusty)
Assignee: (unassigned) = Alberto Milone (albertomilone)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Michele: can you reproduce the problem and attach the dmesg output, your
/var/log/Xorg.0.log, /var/log/Xorg.0.log.old , and /var/log/gpu-
manager.log , please?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Chris: I've just re-uploaded the package. Let's keep the testing and
any further comments in LP: #1410801
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1376966
Title:
gpu-manager treats all files
Please accept ubuntu-drivers-common (1:0.2.91.10) in trusty-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1410801
Title:
[AMD Richland + Topaz XT ] gpu-manager generated xorg.conf is not
Public bug reported:
Deliver new upstream releases of the nvidia binary drivers for 14.04.3
** Affects: nvidia-graphics-drivers-304 (Ubuntu)
Importance: High
Assignee: Alberto Milone (albertomilone)
Status: Invalid
** Affects: nvidia-graphics-drivers-304-updates (Ubuntu
I am already working on it (I've been busy with other work). There's no
need to make this any more complicated than it needs to be.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431753
Title:
@Chris: I re-uploaded ubuntu-drivers-common to fix another issue. In the
meantime the old release was approved. If you reject the package in the
queue, I'll reupload, as per the SRU in LP: #1410801
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I'm going to introduce nvidia-340 and nvidia-346. At least the former seems to
support your GPU:
http://us.download.nvidia.com/XFree86/Linux-x86_64/340.76/README/supportedchips.html
That should solve your problem.
Sorry for the inconvenience.
--
You received this bug notification because you
The only error I see is the following:
[14.583] (II) fglrx(0): initializing int10
[14.583] (EE) fglrx(0): Cannot read int vect
[14.583] (WW) fglrx(0): GetVBEMode failed
This looks like LP: #1432899 , only it seems to come from fglrx, hence I
can't fix it myself.
--
You received
Hey Jammy, can you please have a look at this problem?
It looks like a regression in the driver for 15.04.
NOTE: this is a public bug report
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1450089
801 - 900 of 4210 matches
Mail list logo
