Installation of Ubuntu 16.04.2 LTS Error AMD Graphics CardHP Laptop AMD APU - Fail to Boot - Live linux cdUbuntu 16.04 and AMD RADEON HD 6750: The system is running in low-graphics modeTurn off LED logo on graphics card (AMD)Second monitor and graphics card (AMD) not detected in Ubuntu 12.04 (32-bit)Ubuntu 16.04 AMD Radeon HD 8770 Graphics DriverAMD graphics Ubuntu driver issueInstall 16.04 AMD R7 Graphics issueshow to install the amd graphic card driver?Ubuntu 18.04 Vulkan Problems (AMD HD7950 Graphics Card Tahiti)AMD Graphics card (R5 M430) driver for Ubuntu 18.04Ubuntu freeze and more installation problems
How difficult is it to simply disable/disengage the MCAS on Boeing 737 Max 8 & 9 Aircraft?
Is it true that good novels will automatically sell themselves on Amazon (and so on) and there is no need for one to waste time promoting?
How to use deus ex machina safely?
How to explain that I do not want to visit a country due to personal safety concern?
Are all passive ability checks floors for active ability checks?
Is it normal that my co-workers at a fitness company criticize my food choices?
Why one should not leave fingerprints on bulbs and plugs?
Why do passenger jet manufacturers design their planes with stall prevention systems?
compactness of a set where am I going wrong
Should we release the security issues we found in our product as CVE or we can just update those on weekly release notes?
Is it possible to upcast ritual spells?
Time travel from stationary position?
How do I hide Chekhov's Gun?
A Cautionary Suggestion
Why Choose Less Effective Armour Types?
What options are left, if Britain cannot decide?
Credit cards used everywhere in Singapore or Malaysia?
Are ETF trackers fundamentally better than individual stocks?
What did Alexander Pope mean by "Expletives their feeble Aid do join"?
Why did it take so long to abandon sail after steamships were demonstrated?
Employee lack of ownership
Are there verbs that are neither telic, or atelic?
Does someone need to be connected to my network to sniff HTTP requests?
Could the Saturn V actually have launched astronauts around Venus?
Installation of Ubuntu 16.04.2 LTS Error AMD Graphics Card
HP Laptop AMD APU - Fail to Boot - Live linux cdUbuntu 16.04 and AMD RADEON HD 6750: The system is running in low-graphics modeTurn off LED logo on graphics card (AMD)Second monitor and graphics card (AMD) not detected in Ubuntu 12.04 (32-bit)Ubuntu 16.04 AMD Radeon HD 8770 Graphics DriverAMD graphics Ubuntu driver issueInstall 16.04 AMD R7 Graphics issueshow to install the amd graphic card driver?Ubuntu 18.04 Vulkan Problems (AMD HD7950 Graphics Card Tahiti)AMD Graphics card (R5 M430) driver for Ubuntu 18.04Ubuntu freeze and more installation problems
I want to install Ubuntu 16.04.2 LTS on my HP Pavilion 15-AW009AX (256 GB SSD, 16GB RAM, AMD Radeon R7 M440 and an AMD 9600P Processor).
I followed the installation guidelines to install Ubuntu via a bootable USB flash drive and chose to "Install Ubuntu". The screen froze upon installation and after browsing through a few forums I found that replacing "quiet splash" with "nomodeset" within the "Install Ubuntu" command may be able to solve my problem. Ubuntu installed, however, I got stuck in a loop when logging in - the screen would basically go blank and then take me back to the login screen.
I then rebooted and loaded the GRUB terminal, entering the "Ubuntu" menu I added "radeon.modeset=0" to the end of the line starting with "linux" as my HP has an AMD graphics card and upon reboot I am getting the following error screen:
I have been through a few forums and I believe I am having problems due to the graphics card. If anyone could help I would really appreciate it.
EDIT
I have found another post on the ask ubuntu forums which lists a similar issue encountered when trying to boot ubuntu onto a HP laptop with similar specs: HP Laptop AMD APU - Fail to Boot - Live linux cd
The post mentioned above conatins a link to a patch which I believe may solve the issue. I am unsure how to go about applying the patch. Will I be required to patch and compile the source code for the kernal?
EDIT
Running fsck -y /dev/sda2at the initramfs prompt returns the following:
The AMD-Vi: Completion-Wait loop timed out appears to be addressed in the patch mentioned above.
boot 16.04 system-installation amd-graphics
asked Jun 24 '17 at 13:12
mroche1991mroche1991
613
bumped to the homepage by Community♦ 10 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I want to install Ubuntu 16.04.2 LTS on my HP Pavilion 15-AW009AX (256 GB SSD, 16GB RAM, AMD Radeon R7 M440 and an AMD 9600P Processor).
I followed the installation guidelines to install Ubuntu via a bootable USB flash drive and chose to "Install Ubuntu". The screen froze upon installation and after browsing through a few forums I found that replacing "quiet splash" with "nomodeset" within the "Install Ubuntu" command may be able to solve my problem. Ubuntu installed, however, I got stuck in a loop when logging in - the screen would basically go blank and then take me back to the login screen.
I then rebooted and loaded the GRUB terminal, entering the "Ubuntu" menu I added "radeon.modeset=0" to the end of the line starting with "linux" as my HP has an AMD graphics card and upon reboot I am getting the following error screen:
I have been through a few forums and I believe I am having problems due to the graphics card. If anyone could help I would really appreciate it.
EDIT
I have found another post on the ask ubuntu forums which lists a similar issue encountered when trying to boot ubuntu onto a HP laptop with similar specs: HP Laptop AMD APU - Fail to Boot - Live linux cd
The post mentioned above conatins a link to a patch which I believe may solve the issue. I am unsure how to go about applying the patch. Will I be required to patch and compile the source code for the kernal?
EDIT
Running fsck -y /dev/sda2at the initramfs prompt returns the following:
The AMD-Vi: Completion-Wait loop timed out appears to be addressed in the patch mentioned above.
boot 16.04 system-installation amd-graphics
asked Jun 24 '17 at 13:12
mroche1991mroche1991
613
bumped to the homepage by Community♦ 10 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I want to install Ubuntu 16.04.2 LTS on my HP Pavilion 15-AW009AX (256 GB SSD, 16GB RAM, AMD Radeon R7 M440 and an AMD 9600P Processor).
I followed the installation guidelines to install Ubuntu via a bootable USB flash drive and chose to "Install Ubuntu". The screen froze upon installation and after browsing through a few forums I found that replacing "quiet splash" with "nomodeset" within the "Install Ubuntu" command may be able to solve my problem. Ubuntu installed, however, I got stuck in a loop when logging in - the screen would basically go blank and then take me back to the login screen.
I then rebooted and loaded the GRUB terminal, entering the "Ubuntu" menu I added "radeon.modeset=0" to the end of the line starting with "linux" as my HP has an AMD graphics card and upon reboot I am getting the following error screen:
I have been through a few forums and I believe I am having problems due to the graphics card. If anyone could help I would really appreciate it.
EDIT
I have found another post on the ask ubuntu forums which lists a similar issue encountered when trying to boot ubuntu onto a HP laptop with similar specs: HP Laptop AMD APU - Fail to Boot - Live linux cd
The post mentioned above conatins a link to a patch which I believe may solve the issue. I am unsure how to go about applying the patch. Will I be required to patch and compile the source code for the kernal?
EDIT
Running fsck -y /dev/sda2at the initramfs prompt returns the following:
The AMD-Vi: Completion-Wait loop timed out appears to be addressed in the patch mentioned above.
boot 16.04 system-installation amd-graphics
asked Jun 24 '17 at 13:12
mroche1991mroche1991
613
I want to install Ubuntu 16.04.2 LTS on my HP Pavilion 15-AW009AX (256 GB SSD, 16GB RAM, AMD Radeon R7 M440 and an AMD 9600P Processor).
I followed the installation guidelines to install Ubuntu via a bootable USB flash drive and chose to "Install Ubuntu". The screen froze upon installation and after browsing through a few forums I found that replacing "quiet splash" with "nomodeset" within the "Install Ubuntu" command may be able to solve my problem. Ubuntu installed, however, I got stuck in a loop when logging in - the screen would basically go blank and then take me back to the login screen.
I then rebooted and loaded the GRUB terminal, entering the "Ubuntu" menu I added "radeon.modeset=0" to the end of the line starting with "linux" as my HP has an AMD graphics card and upon reboot I am getting the following error screen:
I have been through a few forums and I believe I am having problems due to the graphics card. If anyone could help I would really appreciate it.
EDIT
I have found another post on the ask ubuntu forums which lists a similar issue encountered when trying to boot ubuntu onto a HP laptop with similar specs: HP Laptop AMD APU - Fail to Boot - Live linux cd
The post mentioned above conatins a link to a patch which I believe may solve the issue. I am unsure how to go about applying the patch. Will I be required to patch and compile the source code for the kernal?
EDIT
Running fsck -y /dev/sda2at the initramfs prompt returns the following:
The AMD-Vi: Completion-Wait loop timed out appears to be addressed in the patch mentioned above.
boot 16.04 system-installation amd-graphics
boot 16.04 system-installation amd-graphics
asked Jun 24 '17 at 13:12
mroche1991mroche1991
613
asked Jun 24 '17 at 13:12
mroche1991mroche1991
613
edited Jun 28 '17 at 12:27
mroche1991
asked Jun 24 '17 at 13:12
mroche1991mroche1991
613
asked Jun 24 '17 at 13:12
mroche1991mroche1991
613
asked Jun 24 '17 at 13:12
mroche1991mroche1991
613
613
bumped to the homepage by Community♦ 10 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 10 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Fix the BusyBox screen by manually fixing the filesystem with this at the prompt:
(initramfs) fsck -y /dev/sda2
(In the above command, the initramfs is the prompt you're seeing. The text the follows is the command to type in.)
Fix the graphics problem by running this at a console prompt. First boot using the nomodeset grub parameter. You can get to a console by hitting this keyboard short cut: Alt+Ctrl>+F2.
Install Graphic Drivers from Commandline
Run this command to show the available drivers for your GPU:
$ ubuntu-drivers devices
You'll be safer by picking the one that the system identifies as recommended.
To install a driver from the list run this:
$ sudo apt-get install [drivername]
To see which driver is currently in use (most likely the one that is failing) run:
$ sudo lspci -nnk | grep -i vga -A3
answered Jun 27 '17 at 14:02
L. D. JamesL. D. James
18.7k43789
You're very welcome. Did you test the steps? I'm sure it'll resolve your issue. If it fails, I would like to know the type of error you get so that I can fix the answer and help with your resolution.
– L. D. James
Jun 28 '17 at 12:07
I ran the fsck command at the initramfs prompt as directed. This ended with a series of five lines of the form: [ XX.XXXXXX] AMD-Vi: Completion-Wait loop timed out. This is what was appearing after several attempts at logging in. I believe this issue is addressed in the patch mentioned in the EDIT above.
– mroche1991
Jun 28 '17 at 12:16
There are a number of ways to fix problems. Personally, I would try first using the default Operating system which usually works. The link in your question is different from the Busybox prompt that you have, with is very specifically a problem (separate from the Graphics card issue) to the integrity of your file system... partially/dev/sda2. That would have to be addressed before going further. It's very important not to interrupt thefsckprogram. If you don't interrupt it. It should fix that part of your problem. Are you still getting the same fix/dev/sdafilesystem?
– L. D. James
Jun 28 '17 at 12:24
As shown in the edit above running thefsckprogram appears to modify/dev/sda2file system. This is then followed by the AMD-Vi: Completion-Wait loop timed out issue.
– mroche1991
Jun 28 '17 at 12:54
Sorry. I didn't notice you had updated the question. I'll study the update and provide a resolution for the new screen... if you don't mind. The new screen is different. It appears to have cleaned the/dev/sdaproblem.
– L. D. James
Jun 28 '17 at 12:59
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%2f928744%2finstallation-of-ubuntu-16-04-2-lts-error-amd-graphics-card%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Fix the BusyBox screen by manually fixing the filesystem with this at the prompt:
(initramfs) fsck -y /dev/sda2
(In the above command, the initramfs is the prompt you're seeing. The text the follows is the command to type in.)
Fix the graphics problem by running this at a console prompt. First boot using the nomodeset grub parameter. You can get to a console by hitting this keyboard short cut: Alt+Ctrl>+F2.
Install Graphic Drivers from Commandline
Run this command to show the available drivers for your GPU:
$ ubuntu-drivers devices
You'll be safer by picking the one that the system identifies as recommended.
To install a driver from the list run this:
$ sudo apt-get install [drivername]
To see which driver is currently in use (most likely the one that is failing) run:
$ sudo lspci -nnk | grep -i vga -A3
answered Jun 27 '17 at 14:02
L. D. JamesL. D. James
18.7k43789
You're very welcome. Did you test the steps? I'm sure it'll resolve your issue. If it fails, I would like to know the type of error you get so that I can fix the answer and help with your resolution.
– L. D. James
Jun 28 '17 at 12:07
I ran the fsck command at the initramfs prompt as directed. This ended with a series of five lines of the form: [ XX.XXXXXX] AMD-Vi: Completion-Wait loop timed out. This is what was appearing after several attempts at logging in. I believe this issue is addressed in the patch mentioned in the EDIT above.
– mroche1991
Jun 28 '17 at 12:16
There are a number of ways to fix problems. Personally, I would try first using the default Operating system which usually works. The link in your question is different from the Busybox prompt that you have, with is very specifically a problem (separate from the Graphics card issue) to the integrity of your file system... partially/dev/sda2. That would have to be addressed before going further. It's very important not to interrupt thefsckprogram. If you don't interrupt it. It should fix that part of your problem. Are you still getting the same fix/dev/sdafilesystem?
– L. D. James
Jun 28 '17 at 12:24
As shown in the edit above running thefsckprogram appears to modify/dev/sda2file system. This is then followed by the AMD-Vi: Completion-Wait loop timed out issue.
– mroche1991
Jun 28 '17 at 12:54
Sorry. I didn't notice you had updated the question. I'll study the update and provide a resolution for the new screen... if you don't mind. The new screen is different. It appears to have cleaned the/dev/sdaproblem.
– L. D. James
Jun 28 '17 at 12:59
add a comment |
Fix the BusyBox screen by manually fixing the filesystem with this at the prompt:
(initramfs) fsck -y /dev/sda2
(In the above command, the initramfs is the prompt you're seeing. The text the follows is the command to type in.)
Fix the graphics problem by running this at a console prompt. First boot using the nomodeset grub parameter. You can get to a console by hitting this keyboard short cut: Alt+Ctrl>+F2.
Install Graphic Drivers from Commandline
Run this command to show the available drivers for your GPU:
$ ubuntu-drivers devices
You'll be safer by picking the one that the system identifies as recommended.
To install a driver from the list run this:
$ sudo apt-get install [drivername]
To see which driver is currently in use (most likely the one that is failing) run:
$ sudo lspci -nnk | grep -i vga -A3
answered Jun 27 '17 at 14:02
L. D. JamesL. D. James
18.7k43789
You're very welcome. Did you test the steps? I'm sure it'll resolve your issue. If it fails, I would like to know the type of error you get so that I can fix the answer and help with your resolution.
– L. D. James
Jun 28 '17 at 12:07
I ran the fsck command at the initramfs prompt as directed. This ended with a series of five lines of the form: [ XX.XXXXXX] AMD-Vi: Completion-Wait loop timed out. This is what was appearing after several attempts at logging in. I believe this issue is addressed in the patch mentioned in the EDIT above.
– mroche1991
Jun 28 '17 at 12:16
There are a number of ways to fix problems. Personally, I would try first using the default Operating system which usually works. The link in your question is different from the Busybox prompt that you have, with is very specifically a problem (separate from the Graphics card issue) to the integrity of your file system... partially/dev/sda2. That would have to be addressed before going further. It's very important not to interrupt thefsckprogram. If you don't interrupt it. It should fix that part of your problem. Are you still getting the same fix/dev/sdafilesystem?
– L. D. James
Jun 28 '17 at 12:24
As shown in the edit above running thefsckprogram appears to modify/dev/sda2file system. This is then followed by the AMD-Vi: Completion-Wait loop timed out issue.
– mroche1991
Jun 28 '17 at 12:54
Sorry. I didn't notice you had updated the question. I'll study the update and provide a resolution for the new screen... if you don't mind. The new screen is different. It appears to have cleaned the/dev/sdaproblem.
– L. D. James
Jun 28 '17 at 12:59
add a comment |
Fix the BusyBox screen by manually fixing the filesystem with this at the prompt:
(initramfs) fsck -y /dev/sda2
(In the above command, the initramfs is the prompt you're seeing. The text the follows is the command to type in.)
Fix the graphics problem by running this at a console prompt. First boot using the nomodeset grub parameter. You can get to a console by hitting this keyboard short cut: Alt+Ctrl>+F2.
Install Graphic Drivers from Commandline
Run this command to show the available drivers for your GPU:
$ ubuntu-drivers devices
You'll be safer by picking the one that the system identifies as recommended.
To install a driver from the list run this:
$ sudo apt-get install [drivername]
To see which driver is currently in use (most likely the one that is failing) run:
$ sudo lspci -nnk | grep -i vga -A3
answered Jun 27 '17 at 14:02
L. D. JamesL. D. James
18.7k43789
Fix the BusyBox screen by manually fixing the filesystem with this at the prompt:
(initramfs) fsck -y /dev/sda2
(In the above command, the initramfs is the prompt you're seeing. The text the follows is the command to type in.)
Fix the graphics problem by running this at a console prompt. First boot using the nomodeset grub parameter. You can get to a console by hitting this keyboard short cut: Alt+Ctrl>+F2.
Install Graphic Drivers from Commandline
Run this command to show the available drivers for your GPU:
$ ubuntu-drivers devices
You'll be safer by picking the one that the system identifies as recommended.
To install a driver from the list run this:
$ sudo apt-get install [drivername]
To see which driver is currently in use (most likely the one that is failing) run:
$ sudo lspci -nnk | grep -i vga -A3
answered Jun 27 '17 at 14:02
L. D. JamesL. D. James
18.7k43789
answered Jun 27 '17 at 14:02
L. D. JamesL. D. James
18.7k43789
answered Jun 27 '17 at 14:02
L. D. JamesL. D. James
18.7k43789
answered Jun 27 '17 at 14:02
L. D. JamesL. D. James
18.7k43789
18.7k43789
You're very welcome. Did you test the steps? I'm sure it'll resolve your issue. If it fails, I would like to know the type of error you get so that I can fix the answer and help with your resolution.
– L. D. James
Jun 28 '17 at 12:07
I ran the fsck command at the initramfs prompt as directed. This ended with a series of five lines of the form: [ XX.XXXXXX] AMD-Vi: Completion-Wait loop timed out. This is what was appearing after several attempts at logging in. I believe this issue is addressed in the patch mentioned in the EDIT above.
– mroche1991
Jun 28 '17 at 12:16
There are a number of ways to fix problems. Personally, I would try first using the default Operating system which usually works. The link in your question is different from the Busybox prompt that you have, with is very specifically a problem (separate from the Graphics card issue) to the integrity of your file system... partially/dev/sda2. That would have to be addressed before going further. It's very important not to interrupt thefsckprogram. If you don't interrupt it. It should fix that part of your problem. Are you still getting the same fix/dev/sdafilesystem?
– L. D. James
Jun 28 '17 at 12:24
As shown in the edit above running thefsckprogram appears to modify/dev/sda2file system. This is then followed by the AMD-Vi: Completion-Wait loop timed out issue.
– mroche1991
Jun 28 '17 at 12:54
Sorry. I didn't notice you had updated the question. I'll study the update and provide a resolution for the new screen... if you don't mind. The new screen is different. It appears to have cleaned the/dev/sdaproblem.
– L. D. James
Jun 28 '17 at 12:59
add a comment |
You're very welcome. Did you test the steps? I'm sure it'll resolve your issue. If it fails, I would like to know the type of error you get so that I can fix the answer and help with your resolution.
– L. D. James
Jun 28 '17 at 12:07
I ran the fsck command at the initramfs prompt as directed. This ended with a series of five lines of the form: [ XX.XXXXXX] AMD-Vi: Completion-Wait loop timed out. This is what was appearing after several attempts at logging in. I believe this issue is addressed in the patch mentioned in the EDIT above.
– mroche1991
Jun 28 '17 at 12:16
There are a number of ways to fix problems. Personally, I would try first using the default Operating system which usually works. The link in your question is different from the Busybox prompt that you have, with is very specifically a problem (separate from the Graphics card issue) to the integrity of your file system... partially/dev/sda2. That would have to be addressed before going further. It's very important not to interrupt thefsckprogram. If you don't interrupt it. It should fix that part of your problem. Are you still getting the same fix/dev/sdafilesystem?
– L. D. James
Jun 28 '17 at 12:24
As shown in the edit above running thefsckprogram appears to modify/dev/sda2file system. This is then followed by the AMD-Vi: Completion-Wait loop timed out issue.
– mroche1991
Jun 28 '17 at 12:54
Sorry. I didn't notice you had updated the question. I'll study the update and provide a resolution for the new screen... if you don't mind. The new screen is different. It appears to have cleaned the/dev/sdaproblem.
– L. D. James
Jun 28 '17 at 12:59
You're very welcome. Did you test the steps? I'm sure it'll resolve your issue. If it fails, I would like to know the type of error you get so that I can fix the answer and help with your resolution.
– L. D. James
Jun 28 '17 at 12:07
You're very welcome. Did you test the steps? I'm sure it'll resolve your issue. If it fails, I would like to know the type of error you get so that I can fix the answer and help with your resolution.
– L. D. James
Jun 28 '17 at 12:07
I ran the fsck command at the initramfs prompt as directed. This ended with a series of five lines of the form: [ XX.XXXXXX] AMD-Vi: Completion-Wait loop timed out. This is what was appearing after several attempts at logging in. I believe this issue is addressed in the patch mentioned in the EDIT above.
– mroche1991
Jun 28 '17 at 12:16
I ran the fsck command at the initramfs prompt as directed. This ended with a series of five lines of the form: [ XX.XXXXXX] AMD-Vi: Completion-Wait loop timed out. This is what was appearing after several attempts at logging in. I believe this issue is addressed in the patch mentioned in the EDIT above.
– mroche1991
Jun 28 '17 at 12:16
There are a number of ways to fix problems. Personally, I would try first using the default Operating system which usually works. The link in your question is different from the Busybox prompt that you have, with is very specifically a problem (separate from the Graphics card issue) to the integrity of your file system... partially
/dev/sda2. That would have to be addressed before going further. It's very important not to interrupt the fsck program. If you don't interrupt it. It should fix that part of your problem. Are you still getting the same fix /dev/sda filesystem?– L. D. James
Jun 28 '17 at 12:24
There are a number of ways to fix problems. Personally, I would try first using the default Operating system which usually works. The link in your question is different from the Busybox prompt that you have, with is very specifically a problem (separate from the Graphics card issue) to the integrity of your file system... partially
/dev/sda2. That would have to be addressed before going further. It's very important not to interrupt the fsck program. If you don't interrupt it. It should fix that part of your problem. Are you still getting the same fix /dev/sda filesystem?– L. D. James
Jun 28 '17 at 12:24
As shown in the edit above running the
fsck program appears to modify /dev/sda2 file system. This is then followed by the AMD-Vi: Completion-Wait loop timed out issue.– mroche1991
Jun 28 '17 at 12:54
As shown in the edit above running the
fsck program appears to modify /dev/sda2 file system. This is then followed by the AMD-Vi: Completion-Wait loop timed out issue.– mroche1991
Jun 28 '17 at 12:54
Sorry. I didn't notice you had updated the question. I'll study the update and provide a resolution for the new screen... if you don't mind. The new screen is different. It appears to have cleaned the
/dev/sda problem.– L. D. James
Jun 28 '17 at 12:59
Sorry. I didn't notice you had updated the question. I'll study the update and provide a resolution for the new screen... if you don't mind. The new screen is different. It appears to have cleaned the
/dev/sda problem.– L. D. James
Jun 28 '17 at 12:59
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.
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%2f928744%2finstallation-of-ubuntu-16-04-2-lts-error-amd-graphics-card%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
