[Ubuntu-x-swat] [Bug 1568449] [NEW] [Toshiba Satellite S55-C5247] ETPS/2 Elantech Touchpad not working

[Christopher M. Penalver]

Public bug reported:

After an update from the following batch, mouse icon shows for a couple seconds 
at login, then disappears. Moving finger on the touchpad or clicking does not 
make it reappear before or after logging in, nor does the OS react to these 
events:
Start-Date: 2016-04-09  14:40:48
Commandline: apt-get build-dep linux-image-4.4.0-15-generic
Requested-By: user (1000)
Install: tex-common:amd64 (6.04, automatic), python2.7-dev:amd64 (2.7.11-7, 
automatic), docbook-dsssl:amd64 (1.79-9, automatic), texlive-latex-base:amd64 
(2015.20160320-1, automatic), sp:amd64 (1.3.4-1.2.1-49ubuntu1, automatic), 
libpci-dev:amd64 (1:3.3.1-1.1ubuntu1), libdw1:amd64 (0.165-3ubuntu1, 
automatic), xmlto:amd64 (0.0.28-0.1), libelf-dev:amd64 (0.165-3ubuntu1), 
libunwind-dev:amd64 (1.1-4.1, automatic), libexpat1-dev:amd64 (2.1.0-7, 
automatic), transfig:amd64 (1:3.2.5.e-5), lynx-common:amd64 
(2.8.9dev8-4ubuntu1, automatic), openjade:amd64 (1.4devel1-21.1, automatic), 
libslang2-dev:amd64 (2.3.0-2ubuntu1, automatic), libpotrace0:amd64 (1.13-2, 
automatic), texlive-base:amd64 (2015.20160320-1, automatic), 
libsgmls-perl:amd64 (1.03ii-34, automatic), libptexenc1:amd64 
(2015.20160222.37495-1, automatic), gawk:amd64 (1:4.1.3+dfsg-0.1), 
texlive-generic-recommended:amd64 (2015.20160320-1, automatic), 
libpython2.7-dev:amd64 (2.7.11-7, automatic), zlib1g-dev:amd64 
(1:1.2.8.dfsg-2ubuntu4, a
 utomatic), lynx:amd64 (2.8.9dev8-4ubuntu1, automatic), 
texlive-fonts-recommended:amd64 (2015.20160320-1, automatic), libdw-dev:amd64 
(0.165-3ubuntu1), libunwind8-dev:amd64 (1.1-4.1), libpng12-dev:amd64 
(1.2.54-1ubuntu1, automatic), libbison-dev:amd64 (2:3.0.4.dfsg-1, automatic), 
libosp5:amd64 (1.5.2-13ubuntu1, automatic), libzzip-0-13:amd64 (0.13.62-3, 
automatic), libudev-dev:amd64 (229-4ubuntu1), makedumpfile:amd64 (1:1.5.9-5), 
libpython-dev:amd64 (2.7.11-1, automatic), dh-systemd:amd64 (1.29ubuntu1), 
libtexluajit2:amd64 (2015.20160222.37495-1, automatic), libnewt-dev:amd64 
(0.52.18-1ubuntu2), sharutils:amd64 (1:4.15.2-1), jadetex:amd64 (3.13-16, 
automatic), libssl-dev:amd64 (1.0.2g-1ubuntu2), python-dev:amd64 (2.7.11-1), 
uuid-dev:amd64 (2.27.1-6ubuntu2), libostyle1c2:amd64 (1.4devel1-21.1, 
automatic), asciidoc:amd64 (8.6.9-3), libiberty-dev:amd64 (20160215-1), 
libsynctex1:amd64 (2015.20160222.37495-1, automatic), tipa:amd64 (2:1.3-20, 
automatic), docbook-utils:amd64 (0.6.14-3ubunt
 u1), libaudit-dev:amd64 (1:2.4.5-1ubuntu2), texlive-binaries:amd64 
(2015.20160222.37495-1, automatic), flex:amd64 (2.6.0-11), bison:amd64 
(2:3.0.4.dfsg-1), kernel-wedge:amd64 (2.90ubuntu1), libsp1c2:amd64 
(1.3.4-1.2.1-49ubuntu1, automatic), xsltproc:amd64 (1.1.28-2.1, automatic), 
libtexlua52:amd64 (2015.20160222.37495-1, automatic), 
texlive-latex-recommended:amd64 (2015.20160320-1, automatic), libfl-dev:amd64 
(2.6.0-11, automatic), sgmlspl:amd64 (1.03ii-34, automatic)
End-Date: 2016-04-09  14:41:12

Rolling back to prior kernel versions where this was confirmed working
didn't change anything.

Toggling the touchpad on/off button doesn't change this behavior.

This works fine in Windows.

As per cat /proc/bus/input/devices :
I: Bus=0011 Vendor=0002 Product=000e Version=
N: Name="ETPS/2 Elantech Touchpad"
P: Phys=isa0060/serio2/input0
S: Sysfs=/devices/platform/i8042/serio2/input/input9
U: Uniq=
H: Handlers=mouse0 event5 
B: PROP=5
B: EV=b
B: KEY=e420 1 0 0 0 0
B: ABS=66180001103

Strangely:
synclient | grep TouchpadOff
TouchpadOff = 2

Change this to:
synclient TouchpadOff=0

Confirm this via:
synclient | grep TouchpadOff
TouchpadOff = 0

Then touch the touchpad and notice:
synclient | grep TouchpadOff
TouchpadOff = 2

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xserver-xorg-input-synaptics 1.8.2-1ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
Uname: Linux 4.4.0-18-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME-Flashback:Unity
Date: Sat Apr  9 23:29:29 2016
DistUpgraded: 2016-01-20 03:32:27,395 DEBUG enabling apt cron job
DistroCodename: xenial
DistroVariant: ubuntu
InstallationDate: Installed on 2015-12-18 (113 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: TOSHIBA Satellite S55-C
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-18-generic 
root=/dev/mapper/ubuntu--vg-root ro ipv6.disable=1 debug=y
SourcePackage: xserver-xorg-input-synaptics
UpgradeStatus: Upgraded to xenial on 2016-01-20 (80 days ago)
dmi.bios.date: 10/14/2015
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 5.10
dmi.board.name: 06F1
dmi.board.vendor: FF50
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis ManuFacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: 

[Ubuntu-x-swat] [Bug 1382462] Re: 10de:0dfa Desktop/windows painted incorrectly in dual monitor configuration

[Launchpad Bug Tracker]

[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

** Changed in: xorg (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1382462

Title:
  10de:0dfa Desktop/windows painted incorrectly in dual monitor
  configuration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1382462/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1511476] Re: Unstable unity session

[Launchpad Bug Tracker]

[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

** Changed in: xorg (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1511476

Title:
  Unstable unity session

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1511476/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1568429] [NEW] Radeon won't work with KMS enabled

[Charlie McMackin]

Public bug reported:

I have a Radeon HD 5770 GPU. After upgrading to Xenial today and
ensuring the xorg radeon driver was enabled, my machine will no longer
boot to a usable state. After selecting default Ubuntu option from GRUB
menu, both monitor lose signal input and the keyboard becomes
unresponsive. Sometimes the machine will reboot on its own, most of the
time I have to hard reset.

If I add `nomodeset` or `radeon.modeset=0` to kernel line in GRUB, the
machine will boot but the radeon driver will not load. Attempting to
load radeon driver with `sudo modprobe radeon modeset=1` after booting
with modesetting off results in the same fail state explained above.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
Uname: Linux 4.4.0-18-generic x86_64
.tmp.unity.support.test.1:
 
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,grid,mousepoll,widget,regex,vpswitch,resize,imgpng,place,gnomecompat,wall,move,animation,fade,snap,expo,scale,unitymtgrabhandles,ezoom,session,workarounds]
CompositorRunning: None
Date: Sat Apr  9 20:02:22 2016
DistUpgraded: 2016-04-09 16:49:55,340 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 vboxhost, 5.0.12, 4.2.0-35-generic, x86_64: installed
 vboxhost, 5.0.12, 4.4.0-18-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GpuHangFrequency: Continuously
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] 
(prog-if 00 [VGA controller])
   Subsystem: XFX Pine Group Inc. Juniper XT [Radeon HD 5770] [1682:2990]
InstallationDate: Installed on 2013-12-29 (832 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=e7310b2e-03b9-4e94-ba8a-d384330592cf ro quiet splash radeon.modeset=0
Renderer: Software
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to xenial on 2016-04-09 (0 days ago)
dmi.bios.date: 04/29/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0519
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5N7A-VM
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0519:bd04/29/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N7A-VM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.12.2+16.04.20160331-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sat Apr  9 19:49:46 2016
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.3-1ubuntu2

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug freeze kms radeon ubuntu xenial

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1568429

Title:
  Radeon won't work with KMS enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1568429/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1548845] Re: [FFe] mesa 11.2.0

[Mathew Hodson]

This bug was fixed in the package mesa - 11.2.0-1ubuntu1

---
mesa (11.2.0-1ubuntu1) xenial; urgency=medium

  * Merge from debian. (LP: #1481832, #1548845)

mesa (11.2.0-1) experimental; urgency=medium

  [ Andreas Boll ]
  * control: Fix vdpau-va-driver Breaks/Replaces for mesa-va-drivers
(Closes: #819655).
  * control: Bump Standards-Version to 3.9.7 (no changes).
  * watch: Update url to use https instead of ftp.

  [ Timo Aaltonen ]
  * New upstream release.
  * rules: Disable tests for now, most of them weren't run before anyway
and they cause unnecessary ftbfs on some archs.

mesa (11.2.0~rc4-1) experimental; urgency=medium

  * New upstream release candidate.

mesa (11.2.0~rc3-2) experimental; urgency=medium

  * mesa-va-drivers: Build gallium VA driver, and add symlinks for
nouveau, r600 and radeonsi.
  * control: Add vdpau-va-driver Breaks/Replaces for mesa-va-drivers.

mesa (11.2.0~rc3-1) experimental; urgency=medium

  * New upstream release candidate.
  * Drop upstreamed patches.
  * libgl1-mesa-glx.symbols: Remove dropped symbols.
  * rules,control: Drop -dbg packages, we have -dbgsym now.
  * rules, *.install.in, not-installed: Drop dri/-build prefix, we build
everything in one pass nowadays.
  * control: Bump libdrm-dev build-dep to 2.4.67 for freedreno.
  * rules: Migrate to dh.
  * control: Add dh-autoreconf to build-depends.

 -- Timo Aaltonen  Tue, 05 Apr 2016 10:19:51 +0300

** Changed in: mesa (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1548845

Title:
  [FFe] mesa 11.2.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1548845/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1562387] Re: digimend / wacom drivers do not recognize chinese clone

[Patola]

Jason,

The edits on 10-evdev.conf are not unnecessary. If general-purpose
drivers are loaded before the huion drivers, the huion drivers are not
loaded. The catch-all rule in 10-evdev.conf prevents the correct drivers
from being loaded.

I'll see if I file a bug report in linuxwacom to see if they can
integrate the huion entries. Thank you.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xf86-input-wacom in Ubuntu.
https://bugs.launchpad.net/bugs/1562387

Title:
  digimend / wacom drivers do not recognize chinese clone

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1562387/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1568243] Re: No video signal after OS load/APU Radeon 6530

[Foghrye4]

** Description changed:

  After recent package upgrade on Ubuntu Xenial Xerus 16.04 monitor stops 
receiving signal in a moment when login screen should appear. I still heard a 
sound of OS loaded (drums). I'm using AMD A6-3650 APU with Radeon(tm) HD 
Graphics × 4. Launching OS via safe mode works fine with video provided by 
"Gallium 0.4 on llvmpipe (LLVM 3.8, 128 bits)".
  Version of xserver-xorg-video-ati:
  1:7.7.0-1 amd64
  Also:
  - Purge and reinstalling xserver-xorg-video-ati package not helping.
  - Booting from "Live USB" with Ubuntu 16.04 beta2 results in same effect 
after choosing "Try Ubuntu" option.
+ Workaround:
+ - Install Ubuntu 15.10 or earlier.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/1568243

Title:
  No video signal after OS load/APU Radeon 6530

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1568243/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1507676] Re: Nvidia-Prime not switching from intel to nvidia leading to a black screen

[Piotr]

The above comments doesn't work. To be honest applying those
modification make things even worse. Now I even can't use ctrl+alt+F2 to
switch to text mode...

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1507676

Title:
  Nvidia-Prime not switching from intel to nvidia leading to a black
  screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1507676/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1568243] Re: No video signal after OS load/APU Radeon 6530

[Foghrye4]

** Description changed:

  After recent package upgrade on Ubuntu Xenial Xerus 16.04 monitor stops 
receiving signal in a moment when login screen should appear. I still heard a 
sound of OS loaded (drums). I'm using AMD A6-3650 APU with Radeon(tm) HD 
Graphics × 4. Launching OS via safe mode works fine with video provided by 
"Gallium 0.4 on llvmpipe (LLVM 3.8, 128 bits)".
- Version of xserver-xorg-video-ati: 
+ Version of xserver-xorg-video-ati:
  1:7.7.0-1 amd64
+ Also:
+ - Purge and reinstalling xserver-xorg-video-ati package not helping.
+ - Booting from "Live USB" with Ubuntu 16.04 beta2 results in same effect 
after choosing "Try Ubuntlu" option.

** Description changed:

  After recent package upgrade on Ubuntu Xenial Xerus 16.04 monitor stops 
receiving signal in a moment when login screen should appear. I still heard a 
sound of OS loaded (drums). I'm using AMD A6-3650 APU with Radeon(tm) HD 
Graphics × 4. Launching OS via safe mode works fine with video provided by 
"Gallium 0.4 on llvmpipe (LLVM 3.8, 128 bits)".
  Version of xserver-xorg-video-ati:
  1:7.7.0-1 amd64
  Also:
  - Purge and reinstalling xserver-xorg-video-ati package not helping.
- - Booting from "Live USB" with Ubuntu 16.04 beta2 results in same effect 
after choosing "Try Ubuntlu" option.
+ - Booting from "Live USB" with Ubuntu 16.04 beta2 results in same effect 
after choosing "Try Ubuntu" option.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/1568243

Title:
  No video signal after OS load/APU Radeon 6530

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1568243/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 899944] Re: package nvidia-173 173.14.22-0ubuntu11 failed to install/upgrade: nvidia-173 kernel module failed to build (FATAL: parse error in symbol dump file)

[dino99]

Closing that outdated report as EOL has been reached long time ago

** Changed in: nvidia-graphics-drivers-173 (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-173 in Ubuntu.
https://bugs.launchpad.net/bugs/899944

Title:
  package nvidia-173 173.14.22-0ubuntu11 failed to install/upgrade:
  nvidia-173 kernel module failed to build (FATAL: parse error in symbol
  dump file)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-173/+bug/899944/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1568243] [NEW] No video signal after OS load/APU Radeon 6530

[Foghrye4]

Public bug reported:

After recent package upgrade on Ubuntu Xenial Xerus 16.04 monitor stops 
receiving signal in a moment when login screen should appear. I still heard a 
sound of OS loaded (drums). I'm using AMD A6-3650 APU with Radeon(tm) HD 
Graphics × 4. Launching OS via safe mode works fine with video provided by 
"Gallium 0.4 on llvmpipe (LLVM 3.8, 128 bits)".
Version of xserver-xorg-video-ati: 
1:7.7.0-1 amd64

** Affects: xserver-xorg-video-ati (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/1568243

Title:
  No video signal after OS load/APU Radeon 6530

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1568243/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1568233] [NEW] BOINC doesn't recognize AMD/ATI GPU in 16.04 despite sudo /etc/init.d/boinc-client restart

[EliasAlucard]

Public bug reported:

Back on 14.04 and also 12.04, all you had to do to get BOINC to use the
GPU(s), was to install AMD's proprietary fglrx driver, and then type in
terminal:

sudo /etc/init.d/boinc-client restart

You had to type that like every time you (re)started Ubuntu for BOINC to
recognize your graphics card, but it worked to fix the GPU recognition
with AMD cards (not sure about Nvidia cards though, since I don't have
any). Now however, in 16.04, AMD's Catalyst drivers have been
deprecated, and while the switch to AMD's improved open source GPU
drivers is a good move, for some reason, this command line no longer
works to recognize AMD graphics cards. And since we can no longer
install fglrx/Catalyst on Xenial, I hope AMD's work on their open source
drivers gets a BOINC optimization ASAP.

** Affects: fglrx-installer (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd ati boinc drivers gpu xenial

** Description changed:

  Back on 14.04 and also 12.04, all you had to do to get BOINC to use the
  GPU(s), was to install AMD's proprietary fglrx driver, and then type in
  terminal:
  
  sudo /etc/init.d/boinc-client restart
  
  You had to type that like every time you (re)started Ubuntu for BOINC to
  recognize your graphics card, but it worked to fix the GPU recognition
  with AMD cards (not sure about Nvidia cards though, since I don't have
  any). Now however, in 16.04, AMD's Catalyst drivers have been
- deprecated, and while the switch to AMD's open source GPU drivers is a
- good move, for some reason, this command line no longer works to
- recognize AMD graphics cards. And since we can't install Catalyst on
- Xenial, I hope AMD's work on their open source drivers gets a BOINC
- optimization ASAP.
+ deprecated, and while the switch to AMD's improved open source GPU
+ drivers is a good move, for some reason, this command line no longer
+ works to recognize AMD graphics cards. And since we can no longer
+ install Catalyst on Xenial, I hope AMD's work on their open source
+ drivers gets a BOINC optimization ASAP.

** Description changed:

  Back on 14.04 and also 12.04, all you had to do to get BOINC to use the
  GPU(s), was to install AMD's proprietary fglrx driver, and then type in
  terminal:
  
  sudo /etc/init.d/boinc-client restart
  
  You had to type that like every time you (re)started Ubuntu for BOINC to
  recognize your graphics card, but it worked to fix the GPU recognition
  with AMD cards (not sure about Nvidia cards though, since I don't have
  any). Now however, in 16.04, AMD's Catalyst drivers have been
  deprecated, and while the switch to AMD's improved open source GPU
  drivers is a good move, for some reason, this command line no longer
  works to recognize AMD graphics cards. And since we can no longer
- install Catalyst on Xenial, I hope AMD's work on their open source
+ install fglrx/Catalyst on Xenial, I hope AMD's work on their open source
  drivers gets a BOINC optimization ASAP.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1568233

Title:
  BOINC doesn't recognize AMD/ATI GPU in 16.04 despite sudo /etc/init.d
  /boinc-client restart

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1568233/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp