@ewr2san: the .old shows that the system was using software rendering.
As for the new log, I don't see anything wrong with it (the dmesg output
might help). Also, the packages are not available in the archive yet, so
I imagine you use a driver from a PPA.
--
You received this bug notification
Please accept nvidia-graphics-drivers-367_367.44-0ubuntu0.16.04.1 and
ubuntu-drivers-common_0.4.17.2 into xenial-proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1619306
Title:
SRU request:
*** This bug is a duplicate of bug 1619306 ***
https://bugs.launchpad.net/bugs/1619306
** This bug has been marked a duplicate of bug 1619306
SRU request: Include the 367 driver in Ubuntu 16.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
ubuntu-drivers-common (Ubuntu)
Status: Triaged => Fix Released
** Changed in: ubuntu-drivers-common (Ubuntu Xenial)
Assignee: (unassigned) => Alberto Milone (albertomilone)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
** Description changed:
- As per the subject, this bug report is about including the 367 driver in
- Ubuntu 16.04.
+ SRU Request:
- This also requires changes in ubuntu-drivers-common, as gpu-manager
- needs to be able to unload the nvidia-drm module in order to power down
- the dGPU in hybrid
-graphics-drivers-367 (Ubuntu)
Importance: High
Assignee: Alberto Milone (albertomilone)
Status: In Progress
** Affects: ubuntu-drivers-common (Ubuntu)
Importance: High
Assignee: Alberto Milone (albertomilone)
Status: In Progress
** Changed in: ubuntu-drivers
ded => Medium
** 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/1615058
Title:
gpu-mana
ommon (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/1610476
Title:
booting with nvidia drivers via nvidia-prime results in no disp
As for the tearing problem, that will be fixed in the near future.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1610476
Title:
booting with nvidia drivers via nvidia-prime results in no display in
** Changed in: bcmwl (Ubuntu)
Assignee: Alberto Milone (albertomilone) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097519
Title:
bcmwl-kernel-source_6.20 update bre
; High
** Changed in: nvidia-graphics-drivers-304-updates (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Summary changed:
- nvidia-304 can't be loaded with the lts-xenial kernel
+ SRU: nvidia-304 can't be loaded with the lts-xenial kernel
** Description changed:
- n
Public bug reported:
nvidia-304 doesn't work with the lts-xenial kernel, as it still relies
on mtrr_add mtrr_del.
** Affects: nvidia-graphics-drivers-304 (Ubuntu)
Importance: High
Assignee: Alberto Milone (albertomilone)
Status: In Progress
** Affects: nvidia-graphics-drivers
I suspect gdm is not calling gpu-manager, which would make it a bug in
gdm.
** Also affects: gdm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Hai: the problem described in this bug report is solved. If, for some
reason, things don't work for you, feel free to file a new bug report,
and attach the logs that I requested in #91
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: nvidia-prime (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: nvidia-prime (Ubuntu)
Importance: Undecided => Medium
** Changed in: nvidia-prime (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notificatio
Xenial)
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/1582439
Title:
nvidia-prime depends upon gdm instead of gdm3
To manage notificati
** Changed in: nvidia-prime (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: nvidia-prime (Ubuntu)
Importance: High => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: unity (Ubuntu)
Assignee: Alberto Milone (albertomilone) => (unassigned)
** Changed in: unity (Ubuntu)
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I spoke with Michael, and we are going to reject the patch for the
nvidia packages in xenial-proposed (already reverted in Yakkety), as he
has a better plan now (so that we don't run into LP: #1589006).
For this reason I am closing the tasks for the nvidia drivers for now.
** Changed in:
True, I got the link from Krita's release notes on the website, but that
pointed to the appstore:
https://krita.org/item/krita-3-0-released/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1588192
Just an update. I have written a workaround, so that users can disable
gestures from dconf. I have used it for a few days on my Macbook, and it
makes the problem go away.
I have proposed my branch for merging. You can follow the bug report
here: LP: #1589520
P.S. it's a separate bug report, as
Public bug reported:
Not an actual solution to LP: #1264795 (which should probably be fixed
in the driver), but a simply way for users to disable gestures in dconf.
** Affects: unity (Ubuntu)
Importance: Medium
Assignee: Alberto Milone (albertomilone)
Status: In Progress
** Description changed:
- Rather than calling drm directly, gpu-manager should simply check the
- outputs connector status by using the sysfs filesystem (e.g.
- /sys/class/drm/card0-HDMI-A-1/status, etc.), thus relying on data that
- is already available.
+ SRU request:
+
+ [Impact]
+ The
*** This bug is a duplicate of bug 1589006 ***
https://bugs.launchpad.net/bugs/1589006
This looks like a duplicate of LP: #1589006
Job for var-lib-snapd-lib-gl.mount failed. See "systemctl status var-
lib-snapd-lib-gl.mount" and "journalctl -xe" for details
** This bug has been marked a
Installing the snap from Krita's website, and using the 361 driver from
proposed works fine here. See the attached screenshot.
** Attachment added: "screenshot"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1588192/+attachment/4677998/+files/krita_works.png
--
I'll look into the problem and make sure it's fixed in 361 for good.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1588192
Title:
GL interfaces seem wedged for Krita on nvidia
To manage
@Mark: can you attach your /var/log/gpu-manager.log , please?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1588192
Title:
GL interfaces seem wedged for Krita on nvidia
To manage notifications
I have applied the changes to 361 and 340. The old 304 legacy driver is
the only one remaining, as it will require further changes (a switch
from cdbs to debhelper) in order to apply Michael's patch. I promise I
am going to fix 304 soon.
In the meantime we can proceed with the SRU for 361 and
@Mark: that means that either the system or (more likely) the app is
using software rendering. Maybe that is enough for the app, although it
should be a little slower. Soon this will be working with full
acceleration :)
@Michael: thanks for the patch! I made a little change, so that the
.mount
** Changed in: nvidia-graphics-drivers-361 (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: nvidia-graphics-drivers-361 (Ubuntu Xenial)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Also affects: nvidia-graphics-drivers-340 (
** Changed in: unity (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: unity (Ubuntu)
Importance: Undecided => Medium
** Changed in: unity (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are
I committed a fix in Yakkey but aptdaemon is currently broken (LP:
#1496292), so ubuntu-driver-common won't build.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1586933
Title:
gpu-manager's drm
ubuntu-drivers-common (Ubuntu Xenial)
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/1586933
Title:
gpu-manager's drm output detectio
I did a little profiling, and it seems that the call that gpu-manager
does to drm to get the connected outputs is quite expensive, and I think
there are better ways to check the connector status.
While certainly relevant to boot time, this is a separate problem (the
original one being caused by
intensive, especially
on boot.
The attached perf shows the problem in gpu-manager.
** Affects: ubuntu-drivers-common (Ubuntu)
Importance: High
Assignee: Alberto Milone (albertomilone)
Status: Triaged
** Attachment added: "Perf Output"
https://bugs.launchpad.net/bu
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579596
Title:
[amdgpu] System failed to resume from suspend with amdgpu
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1583888
Title:
Laptop crashes when trying to run discrete AMD GPUs commands with
@Jeremy @Bill - what is your system configuration (CPU/GPU)? Can you
attach the output of lspci -vvv and your /var/log/gpu-manager.log
please?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1307069
Public bug reported:
Pull in the amdgpu/radeon code from Linux 4.5.3.
** Affects: linux (Ubuntu)
Importance: High
Assignee: Alberto Milone (albertomilone)
Status: In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomil
** Description changed:
+ SRU Request:
+
+ [Impact]
+ The current code will prevent gpu-manager from getting the correct list of
alternatives. This breaks the detection system.
+
+ [Test Case]
+ Install the nvidia driver and check that gpu-manager reconfigures the system
properly. More
ubuntu-drivers-common (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: ubuntu-drivers-common (Ubuntu)
Importance: Critical => High
** Changed in: ubuntu-drivers-common (Ubuntu Xenial)
Assignee: (unassigned) => Alberto Milone (albertomilone)
--
You received this b
Rafał: thank you for spotting the problem. To be honest, I am a little
shocked too.
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: New => Triaged
** Changed in: ubuntu-drivers-common (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you
one minor correction: 364.19 is not open source.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1559576
Title:
Ubuntu GNOME boots to black screen when using proprietary Nvidia
drivers on a laptop
@virgosun: does 352 from the PPA work in 16.04? https://launchpad.net
/~graphics-drivers/+archive/ubuntu/ppa
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1559576
Title:
Ubuntu GNOME boots to black
the log in comment #10 looks good to me.
@Tim: yes, it could be a problem with permissions. I don't use Gnome,
so I didn't notice. I can certainly have a look at GDM.
@virgosun: that sounds like a different problem.
--
You received this bug notification because you are a member of Ubuntu
Does the hdmi audio work when the nvidia driver is not installed?
All I can see is the device from intel:
[ 14.115647] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0
[ 14.115670] snd_hda_intel :00:03.0: enabling device ( -> 0002)
[ 14.115769] HDA driver get
** Changed in: ubuntu-drivers-common (Ubuntu Trusty)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: ubuntu-drivers-common (Ubuntu Wily)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: ubuntu-drivers-common (Ubuntu Trusty)
Impo
Public bug reported:
Summary: After resume from S3, the Login page with blur screen. (FR:
2/10)
Steps:
1.Install X02 Manifest.
2.Boot to system.
3.Let system enter to S3.
4.Press power button to resume from S3.
Expected results: System resume from S3 completed.
Actual results: After resume
That is an alternate dependency i.e. nvidia-prime (>= 0.5) | bumblebee,
and it's only meant to allow users to choose between nvidia-prime and
bumblebee. We do not need or support bumblebee.
Note: nvidia-prime and bumblebee are mutually exclusive ways to deal
with hybrid graphics.
--
You
** Also affects: ubuntu-drivers-common (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: ubuntu-drivers-common (Ubuntu Wily)
Importance: Undecided
Status: New
** Changed in: ubuntu-drivers-common (Ubuntu Trusty)
Status: New => Triaged
** Changed in:
*** This bug is a duplicate of bug 1307069 ***
https://bugs.launchpad.net/bugs/1307069
** This bug has been marked a duplicate of bug 1307069
gpu-manager causing long startup delays
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
We provided that PPA because we could not include those drivers. This,
however, does not mean that 16.04 won't get a Vulkan driver after its
release.
When NVIDIA release a long term support driver that features support for
vulkan, we will include it.
As for AMD, we certainly have plans to keep
n (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: ubuntu-drivers-common (Ubuntu Trusty)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: ubuntu-drivers-common (Ubuntu Wily)
Assignee: (unassigned) => Alberto Milone (albertom
Hi Doug,
gpu-manager.log does not show any nvidia GPUs in your system. Maybe you
disabled the nvidia GPU?
Also, what is the output of the following command?
update-alternatives --display x86_64-linux-gnu_gl_conf
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I am attaching the output of the following command:
lsinitramfs /boot/initrd.img-`uname -r` | grep drm
** Attachment added: "initramfs_drm"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1561643/+attachment/4610107/+files/initramfs_drm
** Changed in: initramfs-tools (Ubuntu)
Public bug reported:
initramfs-tools ignores the FRAMEBUFFER option. This means that the
framebuffer hook will always include the drm modules, regardless of
whether it is dealing with an encrypted system or not.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: initramfs-tools 0.122ubuntu6
Public bug reported:
Reverting commit a83b349814dee660caff0a40a22ac2f166c94a8b fixes a
regression on AMD GPUs.
Here is the upstream commit with that fixes that (from linux-stable):
@Alberto: the "tainting kernel" message is expected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310406
Title:
[regression] Trusty kernel doesn't recognize GeForce 8600m GT nor with
nouveau or
** Changed in: xinit (Ubuntu)
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/1554303
Title:
xinit can't start
To manage notifications about this bug go to:
@HuaiDan: what do you mean by "failsafe values"?
@g hartog: if you think the problem described in this bug report is
still there, then please explain the situation, and attach your /var/log
/gpu-manager.log after reproducing the problem.
--
You received this bug notification because you are a
** Summary changed:
- Pull in upstream amdgpu code in Xenial
+ Pull in upstream AMD code in Xenial
** Description changed:
AMD have made a lot of progress on the amdgpu driver (especially in
- Linux 4.5), and the code will definitely benefit our HWE efforts.
+ Linux 4.5) and they have made a
** Description changed:
+ [Impact]
+ The lts-wily backported kernel introduces the amdgpu driver. Graphics cards
that use this driver need the render node (/dev/dri/renderD*) to be accessible
to users.
+
+ [Test Case]
+ Install the lts-wily kernel, and check whether /dev/dri/renderD* is
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: systemd (Ubuntu)
Status: New => Triaged
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member
Both packages work correctly here:
:~$ dkms status
fglrx-core, 15.201, 4.2.0-27-generic, i686: installed
:~$ apt-cache policy fglrx-core
fglrx-core:
Installed: 2:15.201-0ubuntu0.14.04.1
Candidate: 2:15.201-0ubuntu0.14.04.1
Version table:
*** 2:15.201-0ubuntu0.14.04.1 0
400
Public bug reported:
AMD have made a lot of progress on the amdgpu driver (especially in
Linux 4.5), and the code will definitely benefit our HWE efforts.
** Affects: linux (Ubuntu)
Importance: High
Assignee: Alberto Milone (albertomilone)
Status: In Progress
** Changed
*** This bug is a duplicate of bug 1511301 ***
https://bugs.launchpad.net/bugs/1511301
** This bug has been marked a duplicate of bug 1511301
Failed to upgrade fglrx from 14.502 to 15.200 on Trusty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Verification didn't fail in LP: #1539865
It seems to me that the error came from 2:15.200-0ubuntu0.5 but was
reported as coming from 2:15.200-0ubuntu0.6, since it was (probably) all
part of the same upgrade:
2016-01-30 18:25:56 configure fglrx-updates:amd64 2:15.200-0ubuntu0.5
2016-01-30
Yes, a backport is certainly possible. I'll create a new bug report 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/1361207
Title:
nvidia-graphics-drivers-* should recommend nvidia-modprobe
it.
We rejected the inclusion of the nvidia-modprobe tool over security
concerns, in favour of adopting a udev based solution, which this report
is about.
** Affects: nvidia-graphics-drivers-340 (Ubuntu)
Importance: Undecided
Assignee: Alberto Milone (albertomilone)
Status
here is the new bug report LP: #1540896
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1361207
Title:
nvidia-graphics-drivers-* should recommend nvidia-modprobe
To manage notifications about this
@Michael: no, there is no bug report for it yet. I am finally working on
it, so I expect to deliver a fix for 16.04 soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1361207
Title:
@Michael: the idea is to have all the modules loaded and all the devices
available on boot, even when starting a non graphical environment. This
way we do not need nvidia-modprobe at all.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
you can leave gpu-manager in place and simply boot with the
"nogpumanager" boot parameter.
I am closing this bug report since we do not support bumblebee.
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a
buntu Trusty)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: ubuntu-drivers-common (Ubuntu Wily)
Assignee: (unassigned) => Alberto Milone (albertomilone)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: ubuntu-drivers-common (Ubuntu)
Importance: Undecided => High
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: Confirmed => In Progress
** Changed in: ubuntu-drivers-common (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
--
You
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: Triaged => In Progress
--
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 causing long startup delays
To manage
@SRU team: please accept fglrx-installer and fglrx-updates
(2:15.201-0ubuntu0.14.04.1) in trusty-proposed.
** Description changed:
+ [Impact]
+ The lts-wily backported kernel and (the soon to be available) xserver in
Trusty make fglrx and fglrx-updates uninstallable, and make the DKMS module
** Description changed:
- We are seeing build failures for dkms packages on trusty + linux-lts-
- wily.
+ [Impact]
+ The lts-wily backported kernel in Trusty causes the DKMS module installed by
bcmwl-kernel-source to fail to build.
+
+ [Test Case]
+ Install the lts-wily kernel and check that
** Tags removed: verification-failed
** Tags added: bot-stop-nagging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1511301
Title:
Failed to upgrade fglrx from 14.502 to 15.200 on Trusty.
To manage
One minor correction:
sudo apt-get --purge remove
** Tags removed: trusty verification-failed
** Tags added: bot-stop-nagging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1511301
Title:
Failed
** Changed in: bcmwl (Ubuntu)
Status: New => Triaged
** Changed in: bcmwl (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1518956
Title:
bcmwl: dkms
** Changed in: fglrx-installer (Ubuntu)
Status: New => Triaged
** Changed in: fglrx-installer-updates (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: fglrx-installer-updates (Ubuntu)
Status: New => Triaged
** Changed in: fglrx-
** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: nvidia-graphics-drivers-352 (Ubuntu)
Status: Fix Committed => Fix Released
--
@serenity: the failure shows that you were upgrading to the
15.200-0ubuntu0.5 release, whereas the fix in this bug report is
included in 15.200-0ubuntu0.6. I am pretty sure the fix will help you.
I'm removing the verification-failed tag.
** Tags removed: verification-failed
--
You received
@Roger: that would be a problem with the restricted drivers manager. You
really need to remove the packages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510573
Title:
fglrx should blacklist
It certainly makes sense to simply set up things when the nvidia module
is loaded, although I plan to do it with a udev rule. This will make
nvidia-modprobe redundant on the desktop (i.e. where X is started by
default).
On the server (and on the desktop with Mir), however, X is not started,
and
Just an update: while we are not going to use nvidia-modprobe, we are
going to use a different tool I am working on, that will rely on udev
and will accomplish the same as nvidia-modprobe.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
On 11-11-15 13:58:08, Philip Gemmell wrote:
> After my update, I had my computer freezing after starting lightdm.
> Going through recovery, I purged lightdm and xorg, so I could at least
> get to work with a tty terminal.
>
> After having followed the instructions on adding wily-proposed to my
>
** Description changed:
- Note that the fglrx 14.502 package name is
- fglrx_14.502-0ubuntu1_amd64_UB_14.01.deb, which is from AMD's site, not
- from Ubuntu repository.
+ SRU Request:
+
+ [Impact]
+
+ Upgrading from the upstream fglrx driver packages to the packages in the
+ Ubuntu repository
** Changed in: fglrx-installer (Ubuntu Trusty)
Status: New => In Progress
** Changed in: fglrx-installer (Ubuntu Trusty)
Importance: Undecided => High
** Changed in: fglrx-installer (Ubuntu Trusty)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed
** Description changed:
- The fglrx packages should blacklist amdgpu so that the said driver does
- not prevent fglrx from loading.
+ SRU Request:
+
+ [Impact]
+
+ The fglrx driver can't be loaded unless the amdgpu driver is blacklisted
+ (as we already do with the radeon driver).
+
+ [Test
@SRU team: please accept fglrx-installer_15.200-0ubuntu0.6 and fglrx-
installer-updates_15.200-0ubuntu0.6 into 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/1511301
Title:
Failed
rivers-common (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/1500591
Title:
ubuntu-drivers-common should not care a
*** This bug is a duplicate of bug 1500591 ***
https://bugs.launchpad.net/bugs/1500591
@Jeff: this looks like a duplicate of LP: #1500591 (which I fixed in
16.04)
This is the modalias on your system:
pci:v14E4d43A0sv106Bsd0117bc02sc80i00
and this is what the driver package
On 29-10-15 07:52:37, Martin Pitt wrote:
> The PCI device will exist whether or not the module was loaded; so you
> can just iterate over /sys/bus/pci/devices/* (* expands to the PCI bus
> IDs) and check the attributes in each directory; e. g. you probably want
> to pick out the ones with class ==
** Also affects: fglrx-installer (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1511301
Title:
Failed to upgrade fglrx from 14.502 to
** Package changed: ubuntu-drivers-common (Ubuntu) => fglrx-installer
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1511429
Title:
Monitor attached to integrated intel graphics not
On 29-10-15 17:00:28, xpris wrote:
> I have question. If I install this fglrx from Wily proposed repo, I can
> install also without patching new kernel like 4.3 or I need make some
> patch?
>
I haven't looked into adding support for Linux 4.3 to the driver, so the
package might fail to build (I
nvidia-graphics-drivers-352 (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/1511272
Title:
[4.3] patch to avoid dkms issue
701 - 800 of 4210 matches
Mail list logo