This bug is fixed in 14.10 (I cannot guarantee for packages coming from
PPAs though).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1369398
Title:
package nvidia-331 331.89-0ubuntu4 failed to
I'm not familiar with bumblebee but I'm pretty sure nvidia-prime per se
is not the problem here. All the heavy lifting is done by the gpu-
manager binary in the ubuntu-driver-common package. If you give me an
easy way to check if bumblebee is in use (e.g. checking the existence of
a file, etc.),
** Changed in: fglrx-installer-updates (Ubuntu)
Assignee: (unassigned) = Alberto Milone (albertomilone)
** Changed in: fglrx-installer-updates (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: bcmwl (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/1358966
Title:
bcmwl-kernel-source 6.30.223.248+bdcom
I've just fixed this in fglrx-installer (2:14.201-0ubuntu3) and fglrx-
installer-updates (2:14.201-0ubuntu3) in Vivid. Linux 3.17 is not yet
supported in Ubuntu 14.10.
** Changed in: fglrx-installer-updates (Ubuntu)
Status: In Progress = Fix Released
--
You received this bug notification
and your /var/log/gpu-manager.log
** Changed in: nvidia-graphics-drivers-331 (Ubuntu)
Status: Triaged = Incomplete
** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu)
Status: Triaged = Incomplete
--
You received this bug notification because you are a member of Ubuntu
@Ferhat: please attach your /var/lib/dkms/bbswitch/kernel-$(uname
-r)-$(uname -i)/log/make.log
If anybody else is missing the nvidia kernel module, please post your
/var/lib/dkms/bbswitch/kernel-$(uname -r)-$(uname -i)/log/make.log too.
--
You received this bug notification because you are a
@Jean: please attach your /var/log/gpu-manager.log
** Changed in: ubuntu-drivers-common (Ubuntu Trusty)
Importance: Undecided = Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1262068
@Alistair: if the gpu-manager detected only one GPU, it means that the
other one was probably powered down (or it hadn't been powered on yet?).
Either way, you can work around the problem by passing the
nogpumanager kernel parameter on boot. This will disable the
gpu-manager. If that helps, 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/1376966
Title:
gpu-manager treats all files in /etc/modprobe.d as
** Changed in: nvidia-prime (Ubuntu Precise)
Status: In Progress = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1296020
Title:
[Asus U36JC] Non-existent display detected in both
yes, as Scott already pointed out, I didn't say that you would get the
fix when 15.04 is released. The archive for the development release
(15.04) is now open, so I'll get the fix there first, and then I'll
backport it to 14.10, as this is the standard procedure for SRUs.
--
You received this
** Also affects: alsa-plugins (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: ubuntu-drivers-common (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: alsa-plugins (Ubuntu Trusty)
Status: New = Invalid
** Changed in:
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1181651
Title:
ldconfig problem with 64-bit nvidia driver packages
On 23-10-14 06:29:51, Mark Duncan wrote:
This bug is still affecting me. I have a desktop with two nVidia cards
in an SLI configuration. I need a custom xorg.conf to support my 1440p
monitor, but my xorg.conf gets renamed to xorg.conf.mmdd almost
every reboot.
That's a separate case.
On 22-10-14 20:34:24, Joakim wrote:
According to that page, it should be rated as high importance.
* Has a severe impact on a small portion of Ubuntu users (estimated)
Yes, all users who wants to use fglrx and wine.
* A problem with an essential hardware component (disk controller, built-in
This problem is fixed. Feel free to file a separate bug report by using
the following command:
ubuntu-bug nvidia-331 (or nvidia-331-updates, if that is what you use).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
nvidia-prime doesn't support systemd yet. This will require a systemd
equivalent.
** Changed in: nvidia-prime (Ubuntu)
Assignee: (unassigned) = Alberto Milone (albertomilone)
** Changed in: nvidia-prime (Ubuntu)
Importance: Undecided = Medium
** Changed in: nvidia-graphics-drivers-331
@Alistair: please also include your /var/log/gpu-manager.log after your
xorg.conf is overwritten.
--
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
@Alistair: the gpu-manager detected a change in the number of the
available graphics cards:
How many cards? 1
The number of cards has changed!
It detects the following card:
Vendor/Device Id: 10de:1004
BusID PCI:1@0:0:0
The gpu-manager reconfigures your xorg.conf when you physically remove,
Driver packages are not multi-arch. The 64 bit package provides both 64
bit and 32 bit libraries. The empty alternative is meant to avoid that,
when nvidia is installed, users end up using nvidia's 64 bit libraries
and mesa's 32 bit libraries.
As for the NVIDIA Optimus case, when in power saving
On 22-10-14 10:28:15, Bruno Nova wrote:
As I don't have a working computer with NVIDIA only, I can't test this
myself.
But the bug reporter and another commenter are/were affected. There are also
several people marked as affected.
And I can see other people in the Web using an NVIDIA card
Thank you for reporting the problem. I'll review the patch, and
hopefully include the fix soon.
** 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
@l0j1k: that is definitely a separate issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1365695
Title:
No longer able to use GUI after update
To manage notifications about this bug go to:
Public bug reported:
This package is needed as a dependency of nvidia-graphics-drivers-331
and of nvidia-graphics-drivers-331-updates (main), so that the open
source OpenCL loader is used over the proprietary one. This helps
avoiding symbols mismatches when building OpenCL applications that are
Public bug reported:
This package is needed as a dependency of ocl-icd, which is pending a
MIR (LP: #1382086).
Report:
https://wiki.ubuntu.com/MainInclusionReportKhronosOpenclHeaders
** Affects: khronos-opencl-headers (Ubuntu)
Importance: High
Assignee: MIR approval team (ubuntu-mir)
** Changed in: khronos-opencl-headers (Ubuntu)
Assignee: (unassigned) = MIR approval team (ubuntu-mir)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1382091
Title:
[MIR] Main inclusion request
** Changed in: ocl-icd (Ubuntu)
Assignee: (unassigned) = MIR approval team (ubuntu-mir)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1382086
Title:
[MIR] Main inclusion request for ocl-icd
** Changed in: fglrx-installer-updates (Ubuntu Precise)
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/1355041
Title:
[SRU] fglrx dependencies had
** Changed in: fglrx-installer (Ubuntu)
Importance: Undecided = Medium
** Changed in: fglrx-installer (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can't reproduce the problem in 14.10 using the default kernel (custom
kernels are not supported)
uname -r
3.13.0-37-generic
# dkms status
bbswitch, 0.7, 3.16.0-22-generic, x86_64: installed
nvidia-331-updates-uvm, 331.89, 3.16.0-22-generic, x86_64: installed
nvidia-331-updates, 331.89,
Unless somebody tests the package that Maarten Lankhorst asked to test
in #93, there won't be a proper fix in 14.04.
Please help us test that package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
And this is what I get in 14.04
# uname -r
3.13.0-37-generic
# dkms status
bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed
nvidia-331-updates, 331.38, 3.13.0-24-generic, x86_64: installed
I suspect you're either using custom kernels or an obsolete driver
release (make sure to enable the
@Ivo: yes, please install the intel package, regardless of the version
of ubuntu-drivers-common that you have, as it's really a bug in the
intel driver.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@steveb:
Please follow these steps:
sudo add-apt-repository ppa:canonical-x/x-staging
(say yes to the all the questions)
sudo apt-get update
sudo apt-get install xserver-xorg-video-intel
Remove nvidia:
sudo apt-get --purge remove nvidia-331 (or nvidia-331-updates, according to
what 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/1374126
Title:
mac is not installing bcmwl even though 3rd party
** Changed in: fglrx-installer (Ubuntu)
Status: Confirmed = Triaged
** Changed in: fglrx-installer (Ubuntu)
Assignee: (unassigned) = Alberto Milone (albertomilone)
** Changed in: fglrx-installer-updates (Ubuntu)
Assignee: (unassigned) = Alberto Milone (albertomilone)
--
You
@Daniele: no, the system is not supposed to shut down as you described.
It could be a different problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1365695
Title:
No longer able to use GUI after
On 02-10-14 19:27:22, Brian Murray wrote:
The fglrx-installer-updates upload in the precise proposed queue makes
an incorrect modification to the debian/changelog.
I had rebased my work against the wrong git branch. I've just fixed it
and reuploaded.
--
You received this bug notification
On 06-10-14 16:32:22, Martin Pitt wrote:
So I suppose we should drop bcmwl from the images and instead put linux-
firmware-nonfree on it? And mark that for auto-install instead?
I wish it were that simple. Apparently there are licensing issues with
linux-firmware-nonfree. This means we'll
I'll need at least the following files (after you reproduce the error)
to see what's going on:
1) /var/log/Xorg.0.log
2) /var/log/gpu-manager.log
3) the output of dmesg (the attached dmesg shows only nouveau)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Changed in: ubuntu-drivers-common (Ubuntu)
Assignee: (unassigned) = Alberto Milone (albertomilone)
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: New = Triaged
** Changed in: ubuntu-drivers-common (Ubuntu)
Importance: Undecided = Critical
--
You received this bug
/X11/xorg.conf
xserver.devices:
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.16.0-1ubuntu1
xserver.video_driver: fglrx
** Affects: fglrx-installer (Ubuntu)
Importance: Undecided
Assignee: Alberto Milone (albertomilone)
Status: Triaged
** Affects: xserver-xorg
@Fabio: ok, that's good news. While I can't predict for sure what
systems will work well with Intel/SNA and what won't (i.e. this is
really a bug in Intel's SNA), I can add that workaround for now. Thanks
for testing.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
sohel: ok, then please remove nogpumanager and try what I suggested in
comment #66
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1365695
Title:
No longer able to use GUI after update
To manage
** Also affects: ubuntu-drivers-common (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-304-updates (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-331 (Ubuntu Trusty)
Importance:
/ppa?field.series_filter=trusty
--
Alberto Milone
Software Engineer
Hardware Enablement Team
Professional and Engineering Services
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1365695
Title
@Tryfon: you're probably missing the kernel module for nvidia. Make sure
the headers for the kernel that you're using are installed and then
reinstall the nvidia driver.
** Also affects: xserver-xorg-video-intel (Ubuntu)
Importance: Undecided
Status: New
** Changed in:
I tried to reproduce the problem using a Xubuntu 14.04 image and
everything worked as expected:
http://people.canonical.com/~amilone/xubuntu-output.log
The main problem is that systems older than 14.04 might still have a
/etc/lightdm/lightdm.conf that was altered by older nvidia-prime
releases.
@Tryfon: you can boot in Recovery mode from the Grub menu and remove the
relevant packages from the command line.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1365695
Title:
No longer able to use
@Dimitrios: hybrid graphics won't work with nvidia-304 (nvidia-current
and nvidia-current-updates are transitional packages to it).
Please try installing nvidia-331 instead
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Fabio: please try waubuntu-drivers-common 0.2.91.8 that you can find
here (pick the one that matches your architecture i.e. amd64 for 64 bit
or i386 for 32 bit):
http://people.canonical.com/~amilone/lp1365695/
Then edit /etc/default/grub with root privileges and add
thegpumanager_modesetting
@Fabio: there's no trace of my change in either log. You don't seem to
have passed the gpumanager_modesetting boot parameter (I can't see it
in either Xorg log). Maybe you forgot to update grub?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
-graphics-drivers-331 (Ubuntu)
Assignee: (unassigned) = Alberto Milone (albertomilone)
** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu)
Assignee: (unassigned) = Alberto Milone (albertomilone)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
@Fabio: the new logs show that you're using power saving mode (where
only Intel is enabled, and SNA is expected to be used). I'm going to
need a log where both intel and nvidia are enabled.
Please try with sudo prime-select nvidia and restart X or reboot.
--
You received this bug notification
@Tryfon: please follow my suggestions in comment #33
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1365695
Title:
No longer able to use GUI after update
To manage notifications about this bug go
This is now fixed in 14.04
** Changed in: nvidia-graphics-drivers-331 (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1254994
Title:
[kernel 3.13 rc1]
@Fabio: ok, that makes sense. You're using the modesetting driver, as
expected.
I'll provide a package with a workaround for testing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1365695
Title:
Taihsiang has shown that, thanks to the new ubuntu-drivers-common, it is
now possible to use the nvidia driver in an Optimus system even when
bbswitch is not available. This was the point of the SRU.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug
** Changed in: nvidia-graphics-drivers-331 (Ubuntu)
Assignee: (unassigned) = Alberto Milone (albertomilone)
** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu)
Assignee: (unassigned) = Alberto Milone (albertomilone)
** Changed in: nvidia-graphics-drivers-331 (Ubuntu
** Changed in: nvidia-graphics-drivers-331 (Ubuntu)
Status: Triaged = In Progress
** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1310489 ***
https://bugs.launchpad.net/bugs/1310489
** This bug has been marked a duplicate of bug 1310489
xorg.conf overwritten by booting system
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: nvidia-graphics-drivers-304 (Ubuntu Precise)
Status: Triaged = In Progress
** Changed in: nvidia-graphics-drivers-304-updates (Ubuntu Precise)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
On 14-09-14 21:07:54, Fabio wrote:
Here you are. Xorg.0.log from the working system (currently with version
4).
** Attachment added: Xorg.0.log
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304-updates/+bug/1365695/+attachment/4204011/+files/Xorg.0.log
Fabio: I'm
@Tryfon: if you're using bumblebee, you'll have to disable the
gpu-manager by passing the nogpumanager parameter on boot.
The logs show that you're using nvidia 304, which is not expected to
work with Nvidia Optimus, at least not the way we enable it in Ubuntu
(I'm not sure about bumblebee).
--
@sohel: I can see from dmesg that bumblebeed is in use. You should
either remove bumblebee (and all of its packages) or disable the
gpumanager (by passing nogpumanager as a boot parameter).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@Fabio: can you attach a /var/log/Xorg.0.log from your working system,
please? (the one that uses the old release of ubuntu-drivers-common).
I'm wondering if what you're experiencing is actually an issue in the
switch to Intel/SNA. If so, I can work around it.
--
Alberto Milone
Software Engineer
-common (Ubuntu)
Importance: Undecided = Critical
** 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
accordingly for fglrx
and nvidia.
Thanks for the update.
--
Alberto Milone
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1365336
Title:
Lightdm update=No desktop
To manage notifications about this bug
@Fabio: what's the output of the following command? (after reproducing
the problem)
DISPLAY=:0 xrandr --listproviders
The logs look fine, by the way.
@Tryfon: then it must be a different problem. Please attach the following files
(you can ssh into the machine and use the pastebin command line
you can file a bug report by typing the following command:
ubuntu-bug fglrx (or fglrx-updates, according to the package you're
using).
This will attach most of the relevant logs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Please reproduce the problem and attach the dmesg output.
Also, I don't see anything wrong in /var/log/gpu-manager.log. Was it
collected after reproducing the problem? If not, please do so.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
On 08-09-14 08:27:54, Philipp Commans wrote:
Hallo Alberto!
I found the time do delete the Catalyst drivers (AMD installer) and reinstall
fglrx from the repositories.
I also reinstalled ubuntu-drivers-common from the proposed-archive just to
make sure.
Some testing showed the
On 08-09-14 11:15:07, Philipp Commans wrote:
The last fix I committed in 14.10 should fix this.
Does your fix affect the gpu-manager?
In this case I would still have to get it started.
Yes,
Could I start it manually with a start-script as a workaround?
Sure, whatever works best for
Please accept fglrx-installer and fglrx-installer-updates into precise-
proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1355041
Title:
[SRU] fglrx dependencies had conflicts in
@Uwe: please attach the following files:
1) /var/log/gpu-manager.log
2) /var/log/Xorg.0.log
3) /etc/X11/xorg.conf (the one generated by the gpu-manager)
4)/etc/X11/xorg.conf (the one generated by amdconfig)
5) the dmesg output
--
You received this bug notification because you are a member of
@Abhijit: I don't think the xorg.conf that gpu-manager generates is
causing your problem (I don't see anything wrong in the X log) but let's
see what happens when the gpu-manager is disabled. Please follow these
steps:
1) sudo nano -w /etc/default/grub
2) Add nogpumanager in the following line
In the mean time I have committed a fix in 14.10 so that we are more
tolerant with xorg.confs in general. I included Abhijit's xorg.conf in
the test suite, and the new test shows that the xorg.conf is no longer
being removed. I'll backport the fix to 14.04.
--
You received this bug notification
@Uwe: ok, the fix that I committed today should solve your problem. I'll
backport it soon.
--
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
@Abhijit: you can use pastebinit to upload text files from the command
line:
Install pastebinit:
sudo apt-get install pastebinit
Upload the files:
pastebinit /var/log/Xorg.0.log
pastebinit /etc/X11/xorg.conf
Post the links that pastebinit will give you.
--
You received this bug notification
@Abhijit: as I suspected, your problem is not being caused by the gpu-
manager but it's probably a bug in the fglrx driver. You might want to
file a separate bug report against the fglrx package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Does the driver in trusty-proposed work for you (as per LP: #1310489) ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1365695
Title:
No longer able to use GUI after update
To manage notifications
Abhijit: the log looks fine. It says that fglrx is enabled and in use.
Please attach the following files:
1) /var/log/Xorg.0.log
2) the output of the dmesg command
3) your current xorg.conf
4) the xorg.conf that the gpu-manager keeps overwriting (you can try generating
a new one using the
@Philipp: even if the gpu-manager started on boot, it wouldn't solve
your problem. Here's why (as your log shows):
Proprietary driver installer detected
I assume you installed fglrx from the AMD installer without generating
the deb packages. By doing so, you probably broke your system.
Also, I
@Abhijit: please download the attached file and type the following commands:
cd path_to_the_downloaded_xorg_conf
sudo mv -f xorg.conf /etc/X11/
Then restart your computer, see how it goes, and finally attach your
/var/log/gpu-manager.log and /var/log/Xorg.0.log
** Attachment added: xorg.conf
The error that you see in the log was caused by this code:
if (is_disabled_in_cmdline()) {
fprintf(log_handle, Disabled by kernel parameter \%s\\n,
KERN_PARAM);
goto end;
}
That simply parses /proc/cmdline.
A few more things to try:
1) Maybe what you see is an old log. Try
changed: nvidia-graphics-drivers (Ubuntu) = nvidia-graphics-
drivers-331-updates (Ubuntu)
** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu)
Status: Confirmed = Triaged
** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu)
Assignee: (unassigned) = Alberto Milone (albertomilone
** Changed in: nvidia-graphics-drivers-331 (Ubuntu)
Assignee: (unassigned) = Alberto Milone (albertomilone)
** Changed in: fglrx-installer-updates (Ubuntu)
Assignee: (unassigned) = Alberto Milone (albertomilone)
** Changed in: fglrx-installer (Ubuntu)
Assignee: (unassigned
** Changed in: nvidia-graphics-drivers-331 (Ubuntu)
Status: Triaged = In Progress
** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu)
Status: Triaged = In Progress
** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
Status: Triaged = In Progress
** Changed in:
Thank you for reporting the problem and for debugging it, and thank you,
Laércio, for providing a solution.
I have just uploaded a fix for the relevant nvidia drivers. An update
for fglrx will follow soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
-updates (Ubuntu)
Status: In Progress = Invalid
** Changed in: fglrx-installer-updates (Ubuntu Precise)
Importance: Undecided = Critical
** Changed in: fglrx-installer-updates (Ubuntu Precise)
Assignee: (unassigned) = Alberto Milone (albertomilone)
** Changed in: fglrx-installer
The log attached by Po-Hsu shows that fglrx was correctly enabled on a
system with hybrid graphics.
@Yu Ning: that is ok. If there is no switching option in amdcccle, that
is a bug in the amdcccle binary (nothing I can do about it). The gpu-
manager worked correctly by enabling both AMD GPUs with
@Philipp: no, I've never disabled the gpu-manager in the package (or
anywhere else).
What's the output of the following command?
cat /proc/cmdline
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
please also attach your /etc/init/gpu-manager.conf
--
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
** Description changed:
Description: Ubuntu 14.04 LTS
Release: 14.04
+
+
+
+
+ SRU Request
+
+ There is a regression in the gpu-manager that causes it to revert user
+ changes right before the first reboot after enabling the fglrx driver or
+ the nvidia driver on a
I'll be tracking this as part of LP: #1310489
** No longer affects: ubuntu-drivers-common (Ubuntu Trusty)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1337357
Title:
gpu-manager searches for a
** Description changed:
+ SRU Request
+
+ While bbswitch may fail on some hybrid systems (e.g. on the desktop or
+ when the bbswitch module fails to build), this is not a good reason to
+ prevent the system from offloading rendering to the NVIDIA GPU.
+
+ [Impact]
+ * This problem makes it
LP: #1333569 was filed on 2014-06-24, when FWTS was still using pm-utils
instead of logind.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1364716
Title:
grub menu show up everytime after the second
** Changed in: fglrx-installer (Ubuntu Precise)
Status: New = In Progress
** Changed in: fglrx-installer (Ubuntu Precise)
Importance: Undecided = Critical
** Changed in: fglrx-installer (Ubuntu Precise)
Assignee: (unassigned) = Alberto Milone (albertomilone)
** Changed in: fglrx
** Description changed:
Description: Ubuntu 14.04 LTS
Release: 14.04
== SRU Request ==
There is a regression in the gpu-manager that causes it to revert user
changes right before the first reboot after enabling the fglrx driver or
the nvidia driver on
1001 - 1100 of 4210 matches
Mail list logo
