0 Members and 8 Guests are viewing this topic.
cat /etc/llverLinux Lite 3.0p5qlinux@p5qlinux-Desk:~
sudo apt-get upgradeReading package lists... DoneBuilding dependency tree Reading state information... DoneCalculating upgrade... Done0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
sudo apt-get dist-upgradeReading package lists... DoneBuilding dependency tree Reading state information... DoneCalculating upgrade... Done0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
As the Spanish say..."no problemo"
Canonical will not be supporting the fglrx/Catalyst Linux driver in their archive beginning with Ubuntu 16.04 Xenial Xerus. There's nothing stopping anyone from downloading the latest release from AMD.com and installing the driver directly or generating the Debian packages from that -- assuming upstream Linux kernel and xorg-server compatibility -- but it's not being supported by upstream Ubuntu.For most users, the open-source Radeon graphics stack is "good enough" particularly if you just care about desktop use-cases, video playback, and light gaming. However, currently the open-source Radeon Linux graphics stack only supports OpenGL 4.1 rather than OpenGL 4.5, the open-source OpenCL compute stack leaves a lot to be desired, and there are other current open-source AMD driver limitations that for some users will make switching to the open-source driver a regression in experience and performance.
Quote from: Hans on November 03, 2016, 06:12:37 AM... I couldn't find any mention of the upstream issues with AMD/ATI and the 16.04 LTS... Does this version of LL still have those?I have never had any problems but I am using ADM Radeon HD (integrated).
... I couldn't find any mention of the upstream issues with AMD/ATI and the 16.04 LTS... Does this version of LL still have those?
ATTENTION ALL WHO UPGRADED:There was a bug in Lite Upgrade. This is now fixed. Please run:Menu, Favorites, Install UpdatesMenu, Settings, Lite UpgradeI know this is pain for some to run this again, but if I don't fix this properly now, we will have this bug every upgrade.
... There was a bug in Lite Upgrade. ...