** Tags removed: verification-needed verification-needed-focal
verification-needed-jammy
** Tags added: verification-done verification-done-jammy
verification-needed-done
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-co
** Changed in: ubuntu-drivers-common (Ubuntu Jammy)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: ubuntu-drivers-common (Ubuntu Lunar)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: ubuntu-drivers-common (Ubuntu Lunar)
(Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-restricted-modules (Ubuntu)
Status: New => Triaged
** Changed in: linux-restricted-modules (Ubuntu)
Importance: Undecided => High
** Changed in: linux-restricted-modules (Ubuntu)
Assignee: (unassigned) =>
aphics-drivers-535 (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/2025538
Title:
Unrequest
n (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/2025538
Title:
Unrequested kernel update
Sta
1) On the firmware errors: they come from the open b43 driver, since the
firmware is not installed. This is something the b43-fwcutter package
can help with, if you want to use that.
2) As for the driver installation issue, I wonder if ubuntu-drivers is
confused, finding both bcmwl-kernel-source (
Uploaded. Thank you for your contribution.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to screen-resolution-extra in Ubuntu.
https://bugs.launchpad.net/bugs/2015777
Title:
Fix build for screen-resolution-extra 0.18.2 on Lunar
Status
@Brian: by default, the b43 driver won't override the bcma driver
(unless you force it to, of course).
As for ubuntu-drivers, it does things correctly, meaning that it lists
the compatible proprietary driver (broadcom-sta-dkms), without
recommending its installation (over the open driver).
The "A
@Brian: did you update the initramfs after blacklisting the module?
sudo update-initramfs -u
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/2013236
Title:
Failed to ins
** Changed in: ubuntu-drivers-common (Ubuntu)
Importance: Undecided => High
** Changed in: ubuntu-drivers-common (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscri
Hi Fox, can you try ubuntu-drivers 1:0.9.6.2~0.22.04.3 from proposed,
please?
The problem should be LP: #1993019
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/2019016
Ti
do so in the debian/rules file.
== Changelogs ==
=== Kinetic and Jammy ===
[ Alberto Milone ]
* New upstream release:
* UbuntuDrivers/detect.py:
- Make sure all -open drivers have a lower priority, regardless
of whether the --server parameter is passed in or not.
(Ubuntu Bionic)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: ubuntu-drivers-common (Ubuntu Focal)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: ubuntu-drivers-common (Ubuntu Jammy)
Assignee: (unassigned) => Alberto Milone (alber
I think we can safely remove this from -proposed, as I am going to
upload a new release, including this one and more fixes.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1
@Brian, no, there was a misunderstanding, and this was not meant for
Lunar. Please unsubscribe the Release team, as I can't seem to be able
to do it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https:/
Public bug reported:
Kinetic
[ Alberto Milone ]
* New upstream release:
* UbuntuDrivers/detect.py:
- Make sure all -open drivers have a lower priority, regardless
of whether the --server parameter is passed in or not.
- Update regex in nvidia_desktop_pre_installation_hook
ged in: ubuntu-drivers-common (Ubuntu Kinetic)
Status: New => In Progress
** Changed in: ubuntu-drivers-common (Ubuntu Jammy)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: ubuntu-drivers-common (Ubuntu Kinetic)
Assignee: (unassigned) => Al
** Description changed:
- Hello, we received a drive-by complaint about the ubuntu-drivers
- autoinstall tool:
+ == Changelogs ==
+
+ === Kinetic and Jammy ===
+
+ [ Alberto Milone ]
+ * debian/rules:
+ - Limit the tests to the selected architectures (amd64, arm64).
+ This
== Kinetic and Jammy ===
+
+ [ Alberto Milone ]
+ * New upstream release:
+ * UbuntuDrivers/detect.py:
+ - Make sure all -open drivers have a lower priority, regardless
+ of whether the --server parameter is passed in or not.
+ - Update regex in nvidia_desktop_pre_installation_
ones actually using ubuntu-drivers).
This was already the case with riscv, and we now have an easier way
to do so in the debian/rules file.
== Changelogs ==
=== Kinetic and Jammy ===
[ Alberto Milone ]
* New upstream release:
* UbuntuDrivers/detect.py:
- Make s
mmon (Ubuntu Jammy)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: ubuntu-drivers-common (Ubuntu Kinetic)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: Fix Committed => Fix Released
*
Hey Timo, unfortunately I had left an unused variable in Jammy and in
Kinetic, and that caused the test suite to trigger a FTBFS for both. The
unused variable is not there in Lunar.
Please accept my new uploads, so that we can proceed with the testing.
--
You received this bug notification becau
already the case with riscv, and we now have an easier way
to do so in the debian/rules file.
== Changelogs ==
=== Kinetic and Jammy ===
[ Alberto Milone ]
* New upstream release:
* UbuntuDrivers/detect.py:
- Make sure all -open drivers have a lower priority, re
Removing the alsa-utils package in Kinetic, I don't get the traceback
any more with the package in kinetic-proposed:
:~$ ubuntu-drivers list
ERROR:root:aplay command not found
nvidia-driver-515-open, (kernel modules provided by nvidia-dkms-515-open)
nvidia-driver-510, (kernel modules provided by
I did the same thing for Jammy, with the same results:
:~$ ubuntu-drivers list
ERROR:root:aplay command not found
nvidia-driver-525-open
nvidia-driver-515
nvidia-driver-510
nvidia-driver-470-server
nvidia-driver-470
nvidia-driver-525-server
nvidia-driver-515-server
nvidia-driver-525
nvidia-driver-
ctually using ubuntu-drivers).
This was already the case with riscv, and we now have an easier way
to do so in the debian/rules file.
== Changelogs ==
=== Kinetic and Jammy ===
[ Alberto Milone ]
* New upstream release:
* UbuntuDrivers/detect.py:
- Make sure
vers).
This was already the case with riscv, and we now have an easier way
to do so in the debian/rules file.
== Changelogs ==
=== Kinetic and Jammy ===
[ Alberto Milone ]
* New upstream release:
* UbuntuDrivers/detect.py:
- Make sure all -open drivers h
The problem here is that ubuntu-drivers-common in Focal is too old, and
does not include code to handle the -open driver series. This needs an
SRU.
** Also affects: ubuntu-drivers-common (Ubuntu)
Importance: Undecided
Status: New
** Also affects: ubuntu-drivers-common (Ubuntu Focal)
** Changed in: ubuntu-drivers-common (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: ubuntu-drivers-common (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Desktop
Packages, which is subscri
The "nogpumanager" parameter has been supported since ubuntu-drivers-
common 1:0.2.89 in 14.04. I'm not sure why that doesn't work for you.
Did you update the grub menu with "sudo update-grub" ?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribe
I can no longer reproduce the problem with either fglrx or with fglrx-
updates 2:15.200-0ubuntu0.3 in -proposed.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-
I'm going to backport the fix together with the 346 release and with the
340 release in 14.04. Sorry for the inconvenience.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331-updates in
Ubuntu.
https://bugs.launch
331 is the previous long term release. I plan to introduce 340 (the
legacy driver) to migrate users from 331 (so that hardware support is
the same), whereas 346 (the current long term release) will have to be
installed manually (if your hardware is supported).
--
You received this bug notificatio
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1410801
Title:
[AMD Richland + Topaz X
** Changed in: xserver-xorg-video-vmware (Ubuntu)
Assignee: Marco Trevisan (Treviño) (3v1n0) => Alberto Milone
(albertomilone)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-vmware in Ubuntu.
ht
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1126234
Title:
Does not show nvidia dr
Please try the package in precise-proposed. It already contains the fix.
** Changed in: nvidia-prime (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launch
** Description changed:
- As per the topic, this bug report is about enabling Kaveri APUs, and
- configurations where the APU is used together with a discrete card, in
- 12.04.4.
+ SRU request:
- This requires a small update to Jockey, a change in fglrx-pxpress and a
- new fglrx driver.
+ Pleas
what version of Xubuntu are you using?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1267442
Title:
Install nvidia-331 on Xubuntu results in unbootable machine
Status in “nvidi
The preinstallation script checks the default login manager by looking
at /etc/X11/default-display-manager. If lightdm is the default login
manager, then nvidia-prime creates (if no lightdm.conf exists) or edits
the configuration file.
In your case it should have just edited the file by adding or
** Changed in: nvidia-prime (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: nvidia-prime (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-pr
Ok, then I guess I'll have to find a more reliable way to tell what
system I'm dealing with. I'll use both Kubuntu and Xubunutu vms so that
I can see exactly how I can better detect the system in use.
--
You received this bug notification because you are a member of Desktop
Packages, which is sub
** Tags removed: verification-failed
** Tags added: bot-stop-nagging
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1259237
Title:
Hybrid graphics enablement in 12.04.4
Status in “bb
** Changed in: nvidia-prime (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1267442
Title:
Install nvidia-331 on X/K/Lubuntu resul
** Package changed: nvidia-graphics-drivers-319 (Ubuntu) => libvdpau
(Ubuntu)
** No longer affects: libvdpau (Ubuntu)
** Changed in: nvidia-graphics-drivers-331 (Ubuntu)
Status: New => Confirmed
** Changed in: nvidia-graphics-drivers-331 (Ubuntu)
Assignee: (unassigned) =>
** Also affects: nvidia-graphics-drivers-331-updates (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331-updates in
Ubuntu.
https://bugs.launchpad.net/bugs/12625
It seems to me that, despite what the website says, the driver doesn't
support that specific card:
(EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not
found)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-grap
** Changed in: nvidia-prime (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1268771
Title:
NVIDIA Prime fails with Linux 3.13
Sta
This is not the same bug then, as your card clearly belongs to the 0300
pci class.
Feel free to file a separate bug report for 12.04
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/
Good find nenon1ks!
So it seems that this is the commit that breaks it:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=3a83f992490f8235661b768e53bd5f14915420ac
If this is the case, I can stop bisecting the kernel and move on to
writing a patch to work around it.
--
Y
ics-drivers-331-updates (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu)
Importance: Undecided => High
** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu)
Status: New => In Progress
--
You recei
** Changed in: nvidia
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1126234
Title:
Does not show nvidia driver if intel card is active
St
I can confirm that the last two updates work correctly on my laptop:
Jockey detects the new drivers correctly:
~$ jockey-text -l
kmod:wl - Broadcom STA wireless driver (Proprietary, Disabled, Not in use)
[auto-install]
xorg:nvidia_331 - NVIDIA accelerated graphics driver (Proprietary, Disabled,
There are no regressions in the new package:
:~$ apt-cache policy nvidia-prime
nvidia-prime:
Installed: 0.5~hybrid0.0.2
Candidate: 0.5~hybrid0.0.2
Version table:
*** 0.5~hybrid0.0.2 0
400 http://archive.ubuntu.com/ubuntu/ precise-proposed/main amd64
Packages
100 /var/lib/dp
I can confirm that the new nvidia-prime works well here:
:~$ apt-cache policy nvidia-prime
nvidia-prime:
Installed: 0.5~hybrid0.0.2
Candidate: 0.5~hybrid0.0.2
Version table:
*** 0.5~hybrid0.0.2 0
400 http://archive.ubuntu.com/ubuntu/ precise-proposed/main amd64
Packages
100
The new nvidia-prime works fine here. The pci address is treated as
hexadecimal as expected.
:~$ apt-cache policy nvidia-prime
nvidia-prime:
Installed: 0.5~hybrid0.0.2
Candidate: 0.5~hybrid0.0.2
Version table:
*** 0.5~hybrid0.0.2 0
400 http://archive.ubuntu.com/ubuntu/ precise-propo
fglrx-experimental-13 builds and works correctly here:
:~$ dkms status
fglrx-experimental-13, 13.300, 3.11.0-15-generic, x86_64: installed
The driver is also correctly detected:
:~$ jockey-text --list
xorg:fglrx_experimental_13 - ATI/AMD proprietary FGLRX graphics driver
(**experimental** beta
all the drivers build and work correctly here:
:~$ dkms status
fglrx, 13.101, 3.11.0-15-generic, x86_64: installed
:~$ dkms status
fglrx-updates, 13.125, 3.11.0-15-generic, x86_64: installed
:~$ dkms status
fglrx-experimental-13, 13.300, 3.11.0-15-generic, x86_64: installed
:~$ apt-cache policy
are you using version 331.38-0ubuntu3?
Please attach the output of the following commands:
apt-cache policy nvidia-331
apt-cache policy nvidia-331-updates
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331-upda
This is a regression in the nvidia-prime package.
nvidia-prime 0.5.5 solves the problem.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331-updates in
Ubuntu.
https://bugs.launchpad.net/bugs/1268771
Title:
NVI
@Rabin: you might want to follow the instructions:
https://wiki.ubuntu.com/Testing/EnableProposed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1252667
Title:
package nvidia-pri
@Marcin: please attach the following files:
1) /var/log/nvidia-prime-upstart.log
2) /var/log/prime-offload.log
3) /var/log/prime-supported.log
4) /var/log/lightdm/lightdm.log
5) /var/log/lightdm/x-0.log
6) /var/log/lightdm/x-0.log.old
Note: if you can only use the terminal, you can install the "
-extra (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: nvidia-settings (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to screen-resolution-extra in U
it looks like a configuration problem:
"Error: alternatives are not set up properly"
what's the output of the following commands?
1) update-alternatives --display x86_64-linux-gnu_gl_conf
2) update-alternatives --display i386-linux-gnu_gl_conf
--
You received this bug notification because you
The fact that /var/log/prime-offload.log is missing, means that the
program that is supposed to tell the system to use prime is not being
used.
Please attach the following files:
1) /etc/lightdm/lightdm.conf
2) all the files in /etc/lightdm/lightdm.conf.d/
You can still use pastebin as you did b
Yes, that's exactly why I was asking about those files.
** Changed in: nvidia-prime (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bug
Apparently it's the i915 kernel module that fails when the system
suspends (as per the dmesg in nvidia-bug-report.log.gz):
[ 347.094378] [ cut here ]
[ 347.094404] WARNING: CPU: 5 PID: 2858 at
/build/buildd/linux-3.13.0/drivers/gpu/drm/i915/intel_uncore.c:125
gen6_gt_ch
ok, please try the following steps:
sudo apt-get --purge remove nvidia-331-updates nvidia-331
sudo apt-get install nvidia-331 nvidia-prime
sudo prime-select nvidia
Then reboot and you should be all set.
--
You received this bug notification because you are a member of Desktop
Packages, which
: Alberto Milone (albertomilone)
Status: Triaged
** Also affects: fglrx-pxpress (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: fglrx-pxpress (Ubuntu)
Status: New => Invalid
** Changed in: fglrx-pxpress (Ubuntu Precise)
Status: New => T
** Description changed:
- the amd-xconfig script gets stuck and keeps writing to the log in
- /var/log/upstart/amd-config.log
+ SRU request:
+
+ Please accept fglrx-pxpress 0.6~hybrid0.0.2 in precise-proposed.
+
+ [Rationale]
+ Because of a regression in 0.6~hybrid0.0.1, the amd-config upstart j
** Description changed:
SRU request:
Please accept fglrx-pxpress 0.6~hybrid0.0.2 in precise-proposed.
[Rationale]
Because of a regression in 0.6~hybrid0.0.1, the amd-config upstart job gets
stuck, and, as a result, /var/log/upstart/amd-config.log keeps growing
indefinitely
[Im
The fix in precise-proposed works correctly on my laptop:
:~$ ls /var/log/upstart/ | grep amd
:~$ sudo initctl status amd-config
amd-config stop/waiting
:~$ cat /var/log/amd-xconfig.log
hybrid intel+amd: no need to do anything
:~$ apt-cache policy fglrx-pxpress
fglrx-pxpress:
Installed: 0.6
it works on my multi-gpu desktop system too:
:~$ ls /var/log/upstart/ | grep amd
:~$ sudo initctl status amd-config
amd-config stop/waiting
:~$ cat /var/log/amd-xconfig.log
multi gpu system with amd(s) detected
:~$ apt-cache policy fglrx-pxpress
fglrx-pxpress:
Installed: 0.6~hybrid0.0.2
Ca
Can you still reproduce the problem?
** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331-updates in
Ubuntu.
https://bugs
It looks like a duplicate
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1264543
Title:
Trusty sometimes boots with inactive keyboard .
Status in “lightdm” package in Ubuntu:
@Giovanni: that works as expected. The "hybrid intel+amd: no need to do
anything" only means that it's all set.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-pxpress in Ubuntu.
https://bugs.launchpad.net/bugs/1277058
Title:
Pro
if it's a hybrid system (Intel+NVIDIA) then you'll definitely need
nvidia-prime
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331-updates in
Ubuntu.
https://bugs.launchpad.net/bugs/1262539
Title:
Driver for NV
you have too many drivers installed.
sudo apt-get --purge remove nvidia-304 nvidia-current
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1249067
Title:
nvidia prime causes free
also, please make sure to remove bumblebee
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1249067
Title:
nvidia prime causes freeze at start up
Status in “nvidia-prime” package
The bumblebee-nvidia package depends on the nvidia-packages.
sudo apt-get --purge remove bumblebee*
sudo apt-get install nvidia-331 nvidia-prime
sudo prime-select nvidia
The nvidia-prime package enables Optimus. There's no need to use bumblebee,
unless you prefer to use it (in which case you
@Eduard: please attach the output of the following command:
lspci -n
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1262238
Title:
[SRU] Add support for the lts-saucy stack
Apparently both the fglrx and the fglrx-updates package support your
card. I suggest that you remove fglrx-experimental-13 and install fglrx-
updates
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.
Please attach the output of the following command:
lspci -n
and the following files:
/var/log/prime-supported.log
/var/log/prime-offload.log
/var/log/nvidia-prime-upstart.log
/var/log/prime-switch.log
/var/log/prime-supported.log
If attaching the files is a problem, you can install the pastebinit
I've just checked AMD's website, and it seems that they support your
card only in their legacy driver which, however, doesn't support new
xservers.
http://support.amd.com/en-
us/download/desktop/legacy?product=Legacy2&os=Linux%20x86_64
That driver should work well with the kernel (Linux 3.2) and
Please attach the files that I requested (even though the problem seems
different to you).
** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidi
The errors in the logs should be marked as warnings, as the fglrx keeps
looking for the same library in different places. The log in comment #6
shows that the library was found in the end:
[19.166] (II) AIGLX: Loaded and initialized OpenGL driver(II) GLX:
Initialized DRI GL provider for screen
@Chih-Hsyuan Ho: can we get a working xorg.conf from those platforms,
please? This way I can make sure that gpu-manager does the right thing,
if that is the problem
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu
If calling "amdconfig --initial" instead of creating a xorg.conf from
scratch is desirable, I can make that change in gpu-manager. I'll need
testers though, as I don't own a unit with AMD+AMD.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
This looks like memory corruption in the open driver. Does installing
the 14.04.2 stack (lts-utopic) help?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/1330334
Title:
Does the driver work after a reboot?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jockey in Ubuntu.
https://bugs.launchpad.net/bugs/1247712
Title:
Unable to install Broadcom STA wireless driver on Precise 3.8 / 3.11 /
3.13 kernel
What Martin proposed in the Debian bug report would make my life as a
maintainer much easier.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-304-updates in
Ubuntu.
https://bugs.launchpad.net/bugs/1427924
Title:
@Po-Hsu: please attach the xorg.conf
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1417952
Title:
[HP Pavilion 23 AIO] Stuck on the ubuntu loading splashscreen with
fglrx i
Please follow these steps and report the results:
1) Boot using the "nogpumanager" parameter from the GRUB menu (this will make
sure that the xorg.conf is not overwritten)
2) Copy the attached to /etc/X11/xorg.conf
3) Log out and log back in
4) See if it solves the problem
** Attachment added: "
what happens if you follow the verification steps (using "amdconfig
--initial" this time, instead of my xorg.conf) and switch between the
two GPUs multiple times? Can you always see the switchable option in the
Catalyst Control Center?
--
You received this bug notification because you are a membe
What does this break, other than bumblebee? Does X fail to start? (if
so, please provide /var/log/Xorg.0.log)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1381175
Title:
** Changed in: fglrx-installer (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: fglrx-installer (Ubuntu)
Importance: Undecided => High
** Changed in: fglrx-installer (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug not
@John: that sounds like a bug in the intel driver then. Please attach
your /var/log/Xorg.0.log and /var/log/Xorg.0.log.old after reproducing
the problem.
@Keith: I think the main problem there is that we have to re-enable the
disabled GPU on shutdown in order to avoid problems with the BIOS. This
yes, the problem with fglrx is well known and I'm working on it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1424466
Title:
Devel package not installable in 14.04.2 (mesa-lts-utopic
s (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: fglrx
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs
Ok, thanks, I'll make the relevant changes in gpu-manager.
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.laun
1 - 100 of 1378 matches
Mail list logo
