Reinstall MESA driver
I'm new here and will be thankful if you help me in this case.
I dunno why, but somehow I did upgrade video driver and now I want to restore the original one for current system.
Is this safe and is it work if remove/purge libraries one by one, and then install them again with commands like that:
$sudo aptitude remove libegl-mesa0:amd64
$sudo aptitude install libegl-mesa0:amd64
So I want to remove these which are 18.3~git to the
18.0.5
> $ dpkg -l | grep mesa
> libegl-mesa0:amd64 18.3~git1810131930.b7397b~oibaf~b
> libegl1-mesa:amd64 18.3~git1810131930.b7397b~oibaf~b
> libegl1-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1
> libgl1-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1
> libgl1-mesa-dri:amd64 18.3~git1810131930.b7397b~oibaf~b
> libgl1-mesa-dri:i386 18.3~git1810131930.b7397b~oibaf~b
> libgl1-mesa-glx:amd64 18.3~git1810131930.b7397b~oibaf~b
> libgl1-mesa-glx:i386 18.3~git1810131930.b7397b~oibaf~b
> libglapi-mesa:amd64 18.3~git1810131930.b7397b~oibaf~b
> libglapi-mesa:i386 18.3~git1810131930.b7397b~oibaf~b
> libgles2-mesa:amd64 18.3~git1810131930.b7397b~oibaf~b
> libgles2-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1
> libglu1-mesa:amd64 9.0.0-2.1build1
> libglu1-mesa-dev:amd64 9.0.0-2.1build1
> libglx-mesa0:amd64 18.3~git1810131930.b7397b~oibaf~b
> libglx-mesa0:i386 18.3~git1810131930.b7397b~oibaf~b
> libwayland-egl1-mesa:amd64 18.0.5-0ubuntu0~18.04.1
> mesa-common-dev:amd64 18.0.5-0ubuntu0~18.04.1
> mesa-opencl-icd:i386 18.0.5-0ubuntu0~18.04.1
> mesa-utils 8.4.0-1
> mesa-va-drivers:amd64 18.3~git1810131930.b7397b~oibaf~b
> mesa-vdpau-drivers:amd64 18.3~git1810131930.b7397b~oibaf~b
mesa
asked Dec 16 '18 at 22:44
Плодомир Зеленчуков
183
add a comment |
I'm new here and will be thankful if you help me in this case.
I dunno why, but somehow I did upgrade video driver and now I want to restore the original one for current system.
Is this safe and is it work if remove/purge libraries one by one, and then install them again with commands like that:
$sudo aptitude remove libegl-mesa0:amd64
$sudo aptitude install libegl-mesa0:amd64
So I want to remove these which are 18.3~git to the
18.0.5
> $ dpkg -l | grep mesa
> libegl-mesa0:amd64 18.3~git1810131930.b7397b~oibaf~b
> libegl1-mesa:amd64 18.3~git1810131930.b7397b~oibaf~b
> libegl1-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1
> libgl1-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1
> libgl1-mesa-dri:amd64 18.3~git1810131930.b7397b~oibaf~b
> libgl1-mesa-dri:i386 18.3~git1810131930.b7397b~oibaf~b
> libgl1-mesa-glx:amd64 18.3~git1810131930.b7397b~oibaf~b
> libgl1-mesa-glx:i386 18.3~git1810131930.b7397b~oibaf~b
> libglapi-mesa:amd64 18.3~git1810131930.b7397b~oibaf~b
> libglapi-mesa:i386 18.3~git1810131930.b7397b~oibaf~b
> libgles2-mesa:amd64 18.3~git1810131930.b7397b~oibaf~b
> libgles2-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1
> libglu1-mesa:amd64 9.0.0-2.1build1
> libglu1-mesa-dev:amd64 9.0.0-2.1build1
> libglx-mesa0:amd64 18.3~git1810131930.b7397b~oibaf~b
> libglx-mesa0:i386 18.3~git1810131930.b7397b~oibaf~b
> libwayland-egl1-mesa:amd64 18.0.5-0ubuntu0~18.04.1
> mesa-common-dev:amd64 18.0.5-0ubuntu0~18.04.1
> mesa-opencl-icd:i386 18.0.5-0ubuntu0~18.04.1
> mesa-utils 8.4.0-1
> mesa-va-drivers:amd64 18.3~git1810131930.b7397b~oibaf~b
> mesa-vdpau-drivers:amd64 18.3~git1810131930.b7397b~oibaf~b
mesa
asked Dec 16 '18 at 22:44
Плодомир Зеленчуков
183
The following answer is somewhat related. However, the specific versions mentioned are different so the exact commands used will not work but you can get an idea on how safe or unsafe it may be based on how much work you want to do. askubuntu.com/questions/908064/…
– mchid
Dec 17 '18 at 0:38
add a comment |
I'm new here and will be thankful if you help me in this case.
I dunno why, but somehow I did upgrade video driver and now I want to restore the original one for current system.
Is this safe and is it work if remove/purge libraries one by one, and then install them again with commands like that:
$sudo aptitude remove libegl-mesa0:amd64
$sudo aptitude install libegl-mesa0:amd64
So I want to remove these which are 18.3~git to the
18.0.5
> $ dpkg -l | grep mesa
> libegl-mesa0:amd64 18.3~git1810131930.b7397b~oibaf~b
> libegl1-mesa:amd64 18.3~git1810131930.b7397b~oibaf~b
> libegl1-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1
> libgl1-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1
> libgl1-mesa-dri:amd64 18.3~git1810131930.b7397b~oibaf~b
> libgl1-mesa-dri:i386 18.3~git1810131930.b7397b~oibaf~b
> libgl1-mesa-glx:amd64 18.3~git1810131930.b7397b~oibaf~b
> libgl1-mesa-glx:i386 18.3~git1810131930.b7397b~oibaf~b
> libglapi-mesa:amd64 18.3~git1810131930.b7397b~oibaf~b
> libglapi-mesa:i386 18.3~git1810131930.b7397b~oibaf~b
> libgles2-mesa:amd64 18.3~git1810131930.b7397b~oibaf~b
> libgles2-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1
> libglu1-mesa:amd64 9.0.0-2.1build1
> libglu1-mesa-dev:amd64 9.0.0-2.1build1
> libglx-mesa0:amd64 18.3~git1810131930.b7397b~oibaf~b
> libglx-mesa0:i386 18.3~git1810131930.b7397b~oibaf~b
> libwayland-egl1-mesa:amd64 18.0.5-0ubuntu0~18.04.1
> mesa-common-dev:amd64 18.0.5-0ubuntu0~18.04.1
> mesa-opencl-icd:i386 18.0.5-0ubuntu0~18.04.1
> mesa-utils 8.4.0-1
> mesa-va-drivers:amd64 18.3~git1810131930.b7397b~oibaf~b
> mesa-vdpau-drivers:amd64 18.3~git1810131930.b7397b~oibaf~b
mesa
asked Dec 16 '18 at 22:44
Плодомир Зеленчуков
183
I'm new here and will be thankful if you help me in this case.
I dunno why, but somehow I did upgrade video driver and now I want to restore the original one for current system.
Is this safe and is it work if remove/purge libraries one by one, and then install them again with commands like that:
$sudo aptitude remove libegl-mesa0:amd64
$sudo aptitude install libegl-mesa0:amd64
So I want to remove these which are 18.3~git to the
18.0.5
> $ dpkg -l | grep mesa
> libegl-mesa0:amd64 18.3~git1810131930.b7397b~oibaf~b
> libegl1-mesa:amd64 18.3~git1810131930.b7397b~oibaf~b
> libegl1-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1
> libgl1-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1
> libgl1-mesa-dri:amd64 18.3~git1810131930.b7397b~oibaf~b
> libgl1-mesa-dri:i386 18.3~git1810131930.b7397b~oibaf~b
> libgl1-mesa-glx:amd64 18.3~git1810131930.b7397b~oibaf~b
> libgl1-mesa-glx:i386 18.3~git1810131930.b7397b~oibaf~b
> libglapi-mesa:amd64 18.3~git1810131930.b7397b~oibaf~b
> libglapi-mesa:i386 18.3~git1810131930.b7397b~oibaf~b
> libgles2-mesa:amd64 18.3~git1810131930.b7397b~oibaf~b
> libgles2-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1
> libglu1-mesa:amd64 9.0.0-2.1build1
> libglu1-mesa-dev:amd64 9.0.0-2.1build1
> libglx-mesa0:amd64 18.3~git1810131930.b7397b~oibaf~b
> libglx-mesa0:i386 18.3~git1810131930.b7397b~oibaf~b
> libwayland-egl1-mesa:amd64 18.0.5-0ubuntu0~18.04.1
> mesa-common-dev:amd64 18.0.5-0ubuntu0~18.04.1
> mesa-opencl-icd:i386 18.0.5-0ubuntu0~18.04.1
> mesa-utils 8.4.0-1
> mesa-va-drivers:amd64 18.3~git1810131930.b7397b~oibaf~b
> mesa-vdpau-drivers:amd64 18.3~git1810131930.b7397b~oibaf~b
mesa
mesa
asked Dec 16 '18 at 22:44
Плодомир Зеленчуков
183
asked Dec 16 '18 at 22:44
Плодомир Зеленчуков
183
asked Dec 16 '18 at 22:44
Плодомир Зеленчуков
183
asked Dec 16 '18 at 22:44
Плодомир Зеленчуков
183
asked Dec 16 '18 at 22:44
Плодомир Зеленчуков
183
183
The following answer is somewhat related. However, the specific versions mentioned are different so the exact commands used will not work but you can get an idea on how safe or unsafe it may be based on how much work you want to do. askubuntu.com/questions/908064/…
– mchid
Dec 17 '18 at 0:38
add a comment |
The following answer is somewhat related. However, the specific versions mentioned are different so the exact commands used will not work but you can get an idea on how safe or unsafe it may be based on how much work you want to do. askubuntu.com/questions/908064/…
– mchid
Dec 17 '18 at 0:38
The following answer is somewhat related. However, the specific versions mentioned are different so the exact commands used will not work but you can get an idea on how safe or unsafe it may be based on how much work you want to do. askubuntu.com/questions/908064/…
– mchid
Dec 17 '18 at 0:38
The following answer is somewhat related. However, the specific versions mentioned are different so the exact commands used will not work but you can get an idea on how safe or unsafe it may be based on how much work you want to do. askubuntu.com/questions/908064/…
– mchid
Dec 17 '18 at 0:38
add a comment |
2 Answers
2
active
oldest
votes
From the package names, or from something like apt-cache policy mesa-va-drivers | grep -C2 Version, we can see these packages come from the Oibaf repository.
To revert to the default packages you need to ppa-purge those repos.
sudo apt install ppa-purge
sudo ppa-purge ppa:oibaf/graphics-drivers
Should revert you to the default repos and install the default packages.
In my experience the Oibaf and PKPPA repos do go bad sometimes, but usually are back to being usable within a couple of days. If it's just the latest updates that have gone wrong then it's possible to backtrack to prior versions (GUI tool Synaptic, and CLI too Aptitude both are good for that).
answered Dec 16 '18 at 23:07
pbhj
1,319923
See here on how to revert after using ppa-purge: askubuntu.com/questions/112865/…
– mchid
Dec 17 '18 at 0:33
add a comment |
Thank you guys! It was helpful! This is what I've did:
First checks all packages contains oibaf
$ dpkg -l | grep oibaf
Then I checks for recommended version
$ apt policy <package-name>
And finally does install with specific version
$ sudo aptitude install <package-name>=version
Voiala, no more oibaf. My end goal was to upgrade system to 18.10 cosmic and it's done
answered Dec 17 '18 at 20:05
Плодомир Зеленчуков
183
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1102431%2freinstall-mesa-driver%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
From the package names, or from something like apt-cache policy mesa-va-drivers | grep -C2 Version, we can see these packages come from the Oibaf repository.
To revert to the default packages you need to ppa-purge those repos.
sudo apt install ppa-purge
sudo ppa-purge ppa:oibaf/graphics-drivers
Should revert you to the default repos and install the default packages.
In my experience the Oibaf and PKPPA repos do go bad sometimes, but usually are back to being usable within a couple of days. If it's just the latest updates that have gone wrong then it's possible to backtrack to prior versions (GUI tool Synaptic, and CLI too Aptitude both are good for that).
answered Dec 16 '18 at 23:07
pbhj
1,319923
See here on how to revert after using ppa-purge: askubuntu.com/questions/112865/…
– mchid
Dec 17 '18 at 0:33
add a comment |
From the package names, or from something like apt-cache policy mesa-va-drivers | grep -C2 Version, we can see these packages come from the Oibaf repository.
To revert to the default packages you need to ppa-purge those repos.
sudo apt install ppa-purge
sudo ppa-purge ppa:oibaf/graphics-drivers
Should revert you to the default repos and install the default packages.
In my experience the Oibaf and PKPPA repos do go bad sometimes, but usually are back to being usable within a couple of days. If it's just the latest updates that have gone wrong then it's possible to backtrack to prior versions (GUI tool Synaptic, and CLI too Aptitude both are good for that).
answered Dec 16 '18 at 23:07
pbhj
1,319923
See here on how to revert after using ppa-purge: askubuntu.com/questions/112865/…
– mchid
Dec 17 '18 at 0:33
add a comment |
From the package names, or from something like apt-cache policy mesa-va-drivers | grep -C2 Version, we can see these packages come from the Oibaf repository.
To revert to the default packages you need to ppa-purge those repos.
sudo apt install ppa-purge
sudo ppa-purge ppa:oibaf/graphics-drivers
Should revert you to the default repos and install the default packages.
In my experience the Oibaf and PKPPA repos do go bad sometimes, but usually are back to being usable within a couple of days. If it's just the latest updates that have gone wrong then it's possible to backtrack to prior versions (GUI tool Synaptic, and CLI too Aptitude both are good for that).
answered Dec 16 '18 at 23:07
pbhj
1,319923
From the package names, or from something like apt-cache policy mesa-va-drivers | grep -C2 Version, we can see these packages come from the Oibaf repository.
To revert to the default packages you need to ppa-purge those repos.
sudo apt install ppa-purge
sudo ppa-purge ppa:oibaf/graphics-drivers
Should revert you to the default repos and install the default packages.
In my experience the Oibaf and PKPPA repos do go bad sometimes, but usually are back to being usable within a couple of days. If it's just the latest updates that have gone wrong then it's possible to backtrack to prior versions (GUI tool Synaptic, and CLI too Aptitude both are good for that).
answered Dec 16 '18 at 23:07
pbhj
1,319923
answered Dec 16 '18 at 23:07
pbhj
1,319923
answered Dec 16 '18 at 23:07
pbhj
1,319923
answered Dec 16 '18 at 23:07
pbhj
1,319923
1,319923
See here on how to revert after using ppa-purge: askubuntu.com/questions/112865/…
– mchid
Dec 17 '18 at 0:33
add a comment |
See here on how to revert after using ppa-purge: askubuntu.com/questions/112865/…
– mchid
Dec 17 '18 at 0:33
See here on how to revert after using ppa-purge: askubuntu.com/questions/112865/…
– mchid
Dec 17 '18 at 0:33
See here on how to revert after using ppa-purge: askubuntu.com/questions/112865/…
– mchid
Dec 17 '18 at 0:33
add a comment |
Thank you guys! It was helpful! This is what I've did:
First checks all packages contains oibaf
$ dpkg -l | grep oibaf
Then I checks for recommended version
$ apt policy <package-name>
And finally does install with specific version
$ sudo aptitude install <package-name>=version
Voiala, no more oibaf. My end goal was to upgrade system to 18.10 cosmic and it's done
answered Dec 17 '18 at 20:05
Плодомир Зеленчуков
183
add a comment |
Thank you guys! It was helpful! This is what I've did:
First checks all packages contains oibaf
$ dpkg -l | grep oibaf
Then I checks for recommended version
$ apt policy <package-name>
And finally does install with specific version
$ sudo aptitude install <package-name>=version
Voiala, no more oibaf. My end goal was to upgrade system to 18.10 cosmic and it's done
answered Dec 17 '18 at 20:05
Плодомир Зеленчуков
183
add a comment |
Thank you guys! It was helpful! This is what I've did:
First checks all packages contains oibaf
$ dpkg -l | grep oibaf
Then I checks for recommended version
$ apt policy <package-name>
And finally does install with specific version
$ sudo aptitude install <package-name>=version
Voiala, no more oibaf. My end goal was to upgrade system to 18.10 cosmic and it's done
answered Dec 17 '18 at 20:05
Плодомир Зеленчуков
183
Thank you guys! It was helpful! This is what I've did:
First checks all packages contains oibaf
$ dpkg -l | grep oibaf
Then I checks for recommended version
$ apt policy <package-name>
And finally does install with specific version
$ sudo aptitude install <package-name>=version
Voiala, no more oibaf. My end goal was to upgrade system to 18.10 cosmic and it's done
answered Dec 17 '18 at 20:05
Плодомир Зеленчуков
183
answered Dec 17 '18 at 20:05
Плодомир Зеленчуков
183
answered Dec 17 '18 at 20:05
Плодомир Зеленчуков
183
answered Dec 17 '18 at 20:05
Плодомир Зеленчуков
183
183
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1102431%2freinstall-mesa-driver%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
The following answer is somewhat related. However, the specific versions mentioned are different so the exact commands used will not work but you can get an idea on how safe or unsafe it may be based on how much work you want to do. askubuntu.com/questions/908064/…
– mchid
Dec 17 '18 at 0:38