Ubuntu will not boot. Only getting extremely fast scrolling text

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
0
down vote

favorite












I am only getting a flickering screen of writing going too fast to read. But they start with a green [ OK] and sometimes [failed]. This is after choosing to install or try from usb. I have done the md5checksums



Worth noting this isn't exclusive to ubuntu. I have mint installed and cannot boot unless I go through recovery mode and boot without hardware video accelerating if that helps.



Thanks










share|improve this question



















  • 1




    Recovery mode uses the nomodeset boot parameter, which is often required until you install a proprietary video driver. Most often with nVidia. What vidia card/chip do you have? What brand/model system? askubuntu.com/questions/162075/…
    – oldfred
    Mar 28 at 3:27






  • 1




    Setting nomodeset let's me boot into ubuntu. So what do you think the issue is?
    – neil
    Mar 28 at 3:44










  • Your video driver.
    – Organic Marble
    Mar 28 at 4:05










  • Problem was fixed with this script: iam.tj/prototype/enhancements/Windows-acpi_osi.html I don't understand exactly what it did, but it worked.
    – neil
    Mar 28 at 6:26






  • 3




    @neil, if the problem is fixed, feel free to add your own answer, don't put the solution in the question, otherwise your question will hold the unanswered state.
    – pim
    Mar 28 at 6:27















up vote
0
down vote

favorite












I am only getting a flickering screen of writing going too fast to read. But they start with a green [ OK] and sometimes [failed]. This is after choosing to install or try from usb. I have done the md5checksums



Worth noting this isn't exclusive to ubuntu. I have mint installed and cannot boot unless I go through recovery mode and boot without hardware video accelerating if that helps.



Thanks










share|improve this question



















  • 1




    Recovery mode uses the nomodeset boot parameter, which is often required until you install a proprietary video driver. Most often with nVidia. What vidia card/chip do you have? What brand/model system? askubuntu.com/questions/162075/…
    – oldfred
    Mar 28 at 3:27






  • 1




    Setting nomodeset let's me boot into ubuntu. So what do you think the issue is?
    – neil
    Mar 28 at 3:44










  • Your video driver.
    – Organic Marble
    Mar 28 at 4:05










  • Problem was fixed with this script: iam.tj/prototype/enhancements/Windows-acpi_osi.html I don't understand exactly what it did, but it worked.
    – neil
    Mar 28 at 6:26






  • 3




    @neil, if the problem is fixed, feel free to add your own answer, don't put the solution in the question, otherwise your question will hold the unanswered state.
    – pim
    Mar 28 at 6:27













up vote
0
down vote

favorite









up vote
0
down vote

favorite











I am only getting a flickering screen of writing going too fast to read. But they start with a green [ OK] and sometimes [failed]. This is after choosing to install or try from usb. I have done the md5checksums



Worth noting this isn't exclusive to ubuntu. I have mint installed and cannot boot unless I go through recovery mode and boot without hardware video accelerating if that helps.



Thanks










share|improve this question















I am only getting a flickering screen of writing going too fast to read. But they start with a green [ OK] and sometimes [failed]. This is after choosing to install or try from usb. I have done the md5checksums



Worth noting this isn't exclusive to ubuntu. I have mint installed and cannot boot unless I go through recovery mode and boot without hardware video accelerating if that helps.



Thanks







boot






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Mar 28 at 6:52

























asked Mar 28 at 3:13









neil

363




363







  • 1




    Recovery mode uses the nomodeset boot parameter, which is often required until you install a proprietary video driver. Most often with nVidia. What vidia card/chip do you have? What brand/model system? askubuntu.com/questions/162075/…
    – oldfred
    Mar 28 at 3:27






  • 1




    Setting nomodeset let's me boot into ubuntu. So what do you think the issue is?
    – neil
    Mar 28 at 3:44










  • Your video driver.
    – Organic Marble
    Mar 28 at 4:05










  • Problem was fixed with this script: iam.tj/prototype/enhancements/Windows-acpi_osi.html I don't understand exactly what it did, but it worked.
    – neil
    Mar 28 at 6:26






  • 3




    @neil, if the problem is fixed, feel free to add your own answer, don't put the solution in the question, otherwise your question will hold the unanswered state.
    – pim
    Mar 28 at 6:27













  • 1




    Recovery mode uses the nomodeset boot parameter, which is often required until you install a proprietary video driver. Most often with nVidia. What vidia card/chip do you have? What brand/model system? askubuntu.com/questions/162075/…
    – oldfred
    Mar 28 at 3:27






  • 1




    Setting nomodeset let's me boot into ubuntu. So what do you think the issue is?
    – neil
    Mar 28 at 3:44










  • Your video driver.
    – Organic Marble
    Mar 28 at 4:05










  • Problem was fixed with this script: iam.tj/prototype/enhancements/Windows-acpi_osi.html I don't understand exactly what it did, but it worked.
    – neil
    Mar 28 at 6:26






  • 3




    @neil, if the problem is fixed, feel free to add your own answer, don't put the solution in the question, otherwise your question will hold the unanswered state.
    – pim
    Mar 28 at 6:27








1




1




Recovery mode uses the nomodeset boot parameter, which is often required until you install a proprietary video driver. Most often with nVidia. What vidia card/chip do you have? What brand/model system? askubuntu.com/questions/162075/…
– oldfred
Mar 28 at 3:27




Recovery mode uses the nomodeset boot parameter, which is often required until you install a proprietary video driver. Most often with nVidia. What vidia card/chip do you have? What brand/model system? askubuntu.com/questions/162075/…
– oldfred
Mar 28 at 3:27




1




1




Setting nomodeset let's me boot into ubuntu. So what do you think the issue is?
– neil
Mar 28 at 3:44




Setting nomodeset let's me boot into ubuntu. So what do you think the issue is?
– neil
Mar 28 at 3:44












Your video driver.
– Organic Marble
Mar 28 at 4:05




Your video driver.
– Organic Marble
Mar 28 at 4:05












Problem was fixed with this script: iam.tj/prototype/enhancements/Windows-acpi_osi.html I don't understand exactly what it did, but it worked.
– neil
Mar 28 at 6:26




Problem was fixed with this script: iam.tj/prototype/enhancements/Windows-acpi_osi.html I don't understand exactly what it did, but it worked.
– neil
Mar 28 at 6:26




3




3




@neil, if the problem is fixed, feel free to add your own answer, don't put the solution in the question, otherwise your question will hold the unanswered state.
– pim
Mar 28 at 6:27





@neil, if the problem is fixed, feel free to add your own answer, don't put the solution in the question, otherwise your question will hold the unanswered state.
– pim
Mar 28 at 6:27











1 Answer
1






active

oldest

votes

















up vote
0
down vote



accepted










Problem was fixed with this script: http://iam.tj/prototype/enhancements/Windows-acpi_osi.html



#!/bin/sh
VERSION="$(sudo strings /sys/firmware/acpi/tables/DSDT | grep -i 'windows ' | sort | tail -1)"
echo 'Linux kernel command-line options required: acpi_osi=! "acpi_osi='$VERSION'"'
read -p "Do you want to add this setting (y/n) ? " answer
if [ x$answer != xY -a x$answer != xy ]; then
exit 1
fi
echo "Existing Command Line: ` sed -n '/.*linux[[:space:]].*root=(.*)/s//BOOT_IMAGE=1/ p;q;' /boot/grub/grub.cfg `"
if grep -m 1 'acpi_osi=Windows' -q /etc/default/grub; then
echo "There is already an entry; please remove it from /etc/default/grub and redo 'sudo update-grub' then re-run this script"
exit 2
fi
sudo sed -i "s/^(GRUB_CMDLINE_LINUX=.*)"$/1 acpi_osi=! \\"acpi_osi=$VERSION\\""/" /etc/default/grub
echo "Modified Command Line: ` sed -n '/.*linux[[:space:]].*root=(.*)/s//BOOT_IMAGE=1/ p;q;' /boot/grub/grub.cfg `"
sudo update-grub


I don't understand exactly what it did, but it worked.






share|improve this answer


















  • 1




    Do not run scripts from random sites, unless you know exactly what it does. It could be dangerous. But, it added acpi_osi=$VERSION to grub. Not sure what $VERSION is on your system, but on mine it is a blank. I have seen some specific systems need acpi_osi=linux boot parameter. Better to just manually edit sudo -H gedit /etc/default/grub
    – oldfred
    Mar 28 at 13:49










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',
convertImagesToLinks: true,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1019832%2fubuntu-will-not-boot-only-getting-extremely-fast-scrolling-text%23new-answer', 'question_page');

);

Post as a guest






























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
0
down vote



accepted










Problem was fixed with this script: http://iam.tj/prototype/enhancements/Windows-acpi_osi.html



#!/bin/sh
VERSION="$(sudo strings /sys/firmware/acpi/tables/DSDT | grep -i 'windows ' | sort | tail -1)"
echo 'Linux kernel command-line options required: acpi_osi=! "acpi_osi='$VERSION'"'
read -p "Do you want to add this setting (y/n) ? " answer
if [ x$answer != xY -a x$answer != xy ]; then
exit 1
fi
echo "Existing Command Line: ` sed -n '/.*linux[[:space:]].*root=(.*)/s//BOOT_IMAGE=1/ p;q;' /boot/grub/grub.cfg `"
if grep -m 1 'acpi_osi=Windows' -q /etc/default/grub; then
echo "There is already an entry; please remove it from /etc/default/grub and redo 'sudo update-grub' then re-run this script"
exit 2
fi
sudo sed -i "s/^(GRUB_CMDLINE_LINUX=.*)"$/1 acpi_osi=! \\"acpi_osi=$VERSION\\""/" /etc/default/grub
echo "Modified Command Line: ` sed -n '/.*linux[[:space:]].*root=(.*)/s//BOOT_IMAGE=1/ p;q;' /boot/grub/grub.cfg `"
sudo update-grub


I don't understand exactly what it did, but it worked.






share|improve this answer


















  • 1




    Do not run scripts from random sites, unless you know exactly what it does. It could be dangerous. But, it added acpi_osi=$VERSION to grub. Not sure what $VERSION is on your system, but on mine it is a blank. I have seen some specific systems need acpi_osi=linux boot parameter. Better to just manually edit sudo -H gedit /etc/default/grub
    – oldfred
    Mar 28 at 13:49














up vote
0
down vote



accepted










Problem was fixed with this script: http://iam.tj/prototype/enhancements/Windows-acpi_osi.html



#!/bin/sh
VERSION="$(sudo strings /sys/firmware/acpi/tables/DSDT | grep -i 'windows ' | sort | tail -1)"
echo 'Linux kernel command-line options required: acpi_osi=! "acpi_osi='$VERSION'"'
read -p "Do you want to add this setting (y/n) ? " answer
if [ x$answer != xY -a x$answer != xy ]; then
exit 1
fi
echo "Existing Command Line: ` sed -n '/.*linux[[:space:]].*root=(.*)/s//BOOT_IMAGE=1/ p;q;' /boot/grub/grub.cfg `"
if grep -m 1 'acpi_osi=Windows' -q /etc/default/grub; then
echo "There is already an entry; please remove it from /etc/default/grub and redo 'sudo update-grub' then re-run this script"
exit 2
fi
sudo sed -i "s/^(GRUB_CMDLINE_LINUX=.*)"$/1 acpi_osi=! \\"acpi_osi=$VERSION\\""/" /etc/default/grub
echo "Modified Command Line: ` sed -n '/.*linux[[:space:]].*root=(.*)/s//BOOT_IMAGE=1/ p;q;' /boot/grub/grub.cfg `"
sudo update-grub


I don't understand exactly what it did, but it worked.






share|improve this answer


















  • 1




    Do not run scripts from random sites, unless you know exactly what it does. It could be dangerous. But, it added acpi_osi=$VERSION to grub. Not sure what $VERSION is on your system, but on mine it is a blank. I have seen some specific systems need acpi_osi=linux boot parameter. Better to just manually edit sudo -H gedit /etc/default/grub
    – oldfred
    Mar 28 at 13:49












up vote
0
down vote



accepted







up vote
0
down vote



accepted






Problem was fixed with this script: http://iam.tj/prototype/enhancements/Windows-acpi_osi.html



#!/bin/sh
VERSION="$(sudo strings /sys/firmware/acpi/tables/DSDT | grep -i 'windows ' | sort | tail -1)"
echo 'Linux kernel command-line options required: acpi_osi=! "acpi_osi='$VERSION'"'
read -p "Do you want to add this setting (y/n) ? " answer
if [ x$answer != xY -a x$answer != xy ]; then
exit 1
fi
echo "Existing Command Line: ` sed -n '/.*linux[[:space:]].*root=(.*)/s//BOOT_IMAGE=1/ p;q;' /boot/grub/grub.cfg `"
if grep -m 1 'acpi_osi=Windows' -q /etc/default/grub; then
echo "There is already an entry; please remove it from /etc/default/grub and redo 'sudo update-grub' then re-run this script"
exit 2
fi
sudo sed -i "s/^(GRUB_CMDLINE_LINUX=.*)"$/1 acpi_osi=! \\"acpi_osi=$VERSION\\""/" /etc/default/grub
echo "Modified Command Line: ` sed -n '/.*linux[[:space:]].*root=(.*)/s//BOOT_IMAGE=1/ p;q;' /boot/grub/grub.cfg `"
sudo update-grub


I don't understand exactly what it did, but it worked.






share|improve this answer














Problem was fixed with this script: http://iam.tj/prototype/enhancements/Windows-acpi_osi.html



#!/bin/sh
VERSION="$(sudo strings /sys/firmware/acpi/tables/DSDT | grep -i 'windows ' | sort | tail -1)"
echo 'Linux kernel command-line options required: acpi_osi=! "acpi_osi='$VERSION'"'
read -p "Do you want to add this setting (y/n) ? " answer
if [ x$answer != xY -a x$answer != xy ]; then
exit 1
fi
echo "Existing Command Line: ` sed -n '/.*linux[[:space:]].*root=(.*)/s//BOOT_IMAGE=1/ p;q;' /boot/grub/grub.cfg `"
if grep -m 1 'acpi_osi=Windows' -q /etc/default/grub; then
echo "There is already an entry; please remove it from /etc/default/grub and redo 'sudo update-grub' then re-run this script"
exit 2
fi
sudo sed -i "s/^(GRUB_CMDLINE_LINUX=.*)"$/1 acpi_osi=! \\"acpi_osi=$VERSION\\""/" /etc/default/grub
echo "Modified Command Line: ` sed -n '/.*linux[[:space:]].*root=(.*)/s//BOOT_IMAGE=1/ p;q;' /boot/grub/grub.cfg `"
sudo update-grub


I don't understand exactly what it did, but it worked.







share|improve this answer














share|improve this answer



share|improve this answer








edited Mar 28 at 6:55









karel

50.7k11107127




50.7k11107127










answered Mar 28 at 6:51









neil

363




363







  • 1




    Do not run scripts from random sites, unless you know exactly what it does. It could be dangerous. But, it added acpi_osi=$VERSION to grub. Not sure what $VERSION is on your system, but on mine it is a blank. I have seen some specific systems need acpi_osi=linux boot parameter. Better to just manually edit sudo -H gedit /etc/default/grub
    – oldfred
    Mar 28 at 13:49












  • 1




    Do not run scripts from random sites, unless you know exactly what it does. It could be dangerous. But, it added acpi_osi=$VERSION to grub. Not sure what $VERSION is on your system, but on mine it is a blank. I have seen some specific systems need acpi_osi=linux boot parameter. Better to just manually edit sudo -H gedit /etc/default/grub
    – oldfred
    Mar 28 at 13:49







1




1




Do not run scripts from random sites, unless you know exactly what it does. It could be dangerous. But, it added acpi_osi=$VERSION to grub. Not sure what $VERSION is on your system, but on mine it is a blank. I have seen some specific systems need acpi_osi=linux boot parameter. Better to just manually edit sudo -H gedit /etc/default/grub
– oldfred
Mar 28 at 13:49




Do not run scripts from random sites, unless you know exactly what it does. It could be dangerous. But, it added acpi_osi=$VERSION to grub. Not sure what $VERSION is on your system, but on mine it is a blank. I have seen some specific systems need acpi_osi=linux boot parameter. Better to just manually edit sudo -H gedit /etc/default/grub
– oldfred
Mar 28 at 13:49

















 

draft saved


draft discarded















































 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1019832%2fubuntu-will-not-boot-only-getting-extremely-fast-scrolling-text%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

pylint3 and pip3 broken

Missing snmpget and snmpwalk

How to enroll fingerprints to Ubuntu 17.10 with VFS491