Welcome!
Important information
-- Spectre and Meltdown vulnerabilities
-- Change in MX sources

News
-- MX Linux on social media: here
-- Mepis support still here

Current releases
-- MX-17.1 Final release info here
-- antiX-17 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

[solved] blender and proprietary amd/ati graphics driver

Feel free to talk about anything and everything in this board. Just don't post offensive topics that are meant to cause trouble with other members or are derogatory towards people of different genders, race, color, minors (this includes nudity and sex), politics or religion. Let's try to keep peace among the community and for visitors.

No spam on this or any other forums please! If you post advertisements on these forums, your account may be deleted.

Do not copy and paste entire or even up to half of someone else's words or articles into posts. Post only a few sentences or a paragraph and make sure to include a link back to original words or article. Otherwise it's copyright infringement.

You can talk about other distros here, but no MX bashing. You can email the developers of MX if you just want to say you dislike or hate MX.
Message
Author
User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 16550
Joined: Fri Dec 15, 2006 8:07 pm

Re: [solved] blender and proprietary amd/ati graphics driver

#11 Post by Stevo » Tue Dec 19, 2017 3:39 pm

Just a note that adding upstream Debian testing, sid, or experimental repositories to MX's stable base adds the very real possibility of breaking your system beyond repair. It's safer to download the deb from packages.debian.org and trying to install it with gdebi, since that will refuse to install incompatible packages, but our process of backporting them for our own repositories is the best method of all.

https://wiki.debian.org/DontBreakDebian

nubipengen
Forum Novice
Forum  Novice
Posts: 9
Joined: Mon Dec 18, 2017 11:25 am

Re: [solved] blender and proprietary amd/ati graphics driver

#12 Post by nubipengen » Wed Dec 20, 2017 12:07 am

noted that, thank you, sir. :)

nubipengen
Forum Novice
Forum  Novice
Posts: 9
Joined: Mon Dec 18, 2017 11:25 am

Re: [solved] blender and proprietary amd/ati graphics driver

#13 Post by nubipengen » Wed Dec 20, 2017 2:28 am

Stevo wrote:Just a note that adding upstream Debian testing, sid, or experimental repositories to MX's stable base adds the very real possibility of breaking your system beyond repair. It's safer to download the deb from packages.debian.org and trying to install it with gdebi, since that will refuse to install incompatible packages, but our process of backporting them for our own repositories is the best method of all.

https://wiki.debian.org/DontBreakDebian
one more curiosity, sir, is it possible not to break the system, if i limit the use of MX testing repo only for some specific end user applications, just to get their newest releases, in this case, blender, for example. the rest will still use MX stable repository.

User avatar
asqwerth
Forum Veteran
Forum Veteran
Posts: 3448
Joined: Sun May 27, 2007 5:37 am

Re: [solved] blender and proprietary amd/ati graphics driver

#14 Post by asqwerth » Wed Dec 20, 2017 3:41 am

MX Test Repo is NOT the same as Debian Testing.

In simple terms, Debian Testing and Sid (also called Unstable) Repos have packages that are built on different (newer) versions of the building blocks used in Debian Stretch (the current Debian Stable, which MX17 is on). Debian Testing and Sid are meant to be testing packages that will eventually make it to the next future version of Debian Stable in 1 or 2 years' time.

In contrast MX Test Repo is MX's own repo where the packages are actually compatible with Stretch. Debian Backports Repo is also compatible with Stretch. In these 2 repos, newer versions of packages from Debian Testing or Sid are adjusted so that the parts of the building blocks that will clash with Stretch are replaced with blocks that work with Stretch.

I think the very fact that you needed to ask your above question, shows that it might be safer for you for the moment, to use the MX Package Installer (MXPI) and install things from Stable, MX Test Repo or Debian Backports using the "Full Catalogue" Tab.

Learn to walk before you start running. Get more familiar with the system and Debian before jumping in. Unless of course you have a test partition to mess around with that you don't mind breaking if things go wrong.
Desktop: Intel i5-4460, 16GB RAM, Intel integrated graphics
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400

nubipengen
Forum Novice
Forum  Novice
Posts: 9
Joined: Mon Dec 18, 2017 11:25 am

Re: [solved] blender and proprietary amd/ati graphics driver

#15 Post by nubipengen » Wed Dec 20, 2017 6:25 am

thanks again for the insights, sir.

i am new to MX and debian.
blender 2.79 was added to MX test repo yesterday, so concluding from your explanation, i guess it is still safe to install it.

since this is a computer for client's daily production, i chose MX which is based on debian stable, to replace the previously installed sparky 5.1 (based on debian testing).

User avatar
timkb4cq
Forum Veteran
Forum Veteran
Posts: 4416
Joined: Wed Jul 12, 2006 4:05 pm

Re: [solved] blender and proprietary amd/ati graphics driver

#16 Post by timkb4cq » Wed Dec 20, 2017 4:49 pm

Yes. The reason we have an MX Testing repository is for those packages we have built to be safe for MX that work for the builder, but haven't had testing by others. Most are fine first try, but occasionally we find a missing dependency or other minor bug that we need to fix before moving it to the Main repo.

A good example of that was on the forums today. Cool-retro-term was built & put in the testing repo. A user installed it and found it wouldn't run from WhiskerMenu because his system was missing two required packages that had been present already on the builder's machine (so it worked fine for him), but which weren't brought in automatically by the package.
The package has been fixed to include those as dependencies and will be uploaded shortly.

Some packages never move out of testing because nobody gives any feedback on them - so if you install a package from MX Testing that works fine, please let us know!
MSI 970A-G43 MB, AMD FX-6300 (six core), 16GB RAM, GeForce 730, Samsung 850 EVO 250GB SSD, Seagate Barracuda XT 3TB

nubipengen
Forum Novice
Forum  Novice
Posts: 9
Joined: Mon Dec 18, 2017 11:25 am

Re: [solved] blender and proprietary amd/ati graphics driver

#17 Post by nubipengen » Thu Dec 21, 2017 7:21 am

certainly, sir, thank you so much for the insights. :)

User avatar
waqasjunaid
Forum Novice
Forum  Novice
Posts: 1
Joined: Fri May 04, 2018 2:39 am

linux device drivers 3rd edition pdf

#18 Post by waqasjunaid » Fri May 04, 2018 2:44 am


Post Reply

Return to “General”