Sfdwhf

How to deal with taxi scam when on vacation?

Do I need life insurance if I can cover my own funeral costs?

Is it normal that my co-workers at a fitness company criticize my food choices?

What's the meaning of “spike” in the context of “adrenaline spike”?

Is a party consisting of only a bard, a cleric, and a warlock functional long-term?

Why Choose Less Effective Armour Types?

Does Mathematica reuse previous computations?

How to change two letters closest to a string and one letter immediately after a string using notepad++

How to create the Curved texte?

What exactly is this small puffer fish doing and how did it manage to accomplish such a feat?

Is it possible to upcast ritual spells?

Identifying the interval from A♭ to D♯

Recruiter wants very extensive technical details about all of my previous work

In a future war, an old lady is trying to raise a boy but one of the weapons has made everyone deaf

Are ETF trackers fundamentally better than individual stocks?

Why do Australian milk farmers need to protest supermarkets' milk price?

How Could an Airship Be Repaired Mid-Flight

Gravity magic - How does it work?

Is there a data structure that only stores hash codes and not the actual objects?

How to use deus ex machina safely?

Combining an idiom with a metonymy

How to simplify this time periods definition interface?

SOQL: Populate a Literal List in WHERE IN Clause

How could a scammer know the apps on my phone / iTunes account?

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

1

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

share|improve this question

edited Jun 28 '17 at 12:27

mroche1991

asked Jun 24 '17 at 13:12

mroche1991mroche1991

613

bumped to the homepage by Community♦ 8 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 | 

1

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

share|improve this question

edited Jun 28 '17 at 12:27

mroche1991

asked Jun 24 '17 at 13:12

mroche1991mroche1991

613

bumped to the homepage by Community♦ 8 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

share|improve this question

edited Jun 28 '17 at 12:27

mroche1991

asked Jun 24 '17 at 13:12

mroche1991mroche1991

613

share|improve this question

edited Jun 28 '17 at 12:27

mroche1991

asked Jun 24 '17 at 13:12

mroche1991mroche1991

613

share|improve this question

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

1 Answer
1

active

oldest

votes

0

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

share|improve this answer

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 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
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  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 | 

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
});


}
});

draft saved

draft discarded

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

Name

Email

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

Name

Email

Required, but never shown

0

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

share|improve this answer

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 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
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  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 | 

0

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

share|improve this answer

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 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
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  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 | 

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

share|improve this answer

answered Jun 27 '17 at 14:02

L. D. JamesL. D. James

18.7k43789

(initramfs) fsck -y /dev/sda2

$ ubuntu-drivers devices

$ sudo apt-get install [drivername]

$ sudo lspci -nnk | grep -i vga -A3

share|improve this answer

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