ubuntu 18.04 shutdown problemUbuntu 11.10 restart and shutdown not working fullyAttempting to dual boot...
LaTeX closing $ signs makes cursor jump
How is the claim "I am in New York only if I am in America" the same as "If I am in New York, then I am in America?
What does it mean to describe someone as a butt steak?
How to find program name(s) of an installed package?
How much RAM could one put in a typical 80386 setup?
Collect Fourier series terms
Why doesn't Newton's third law mean a person bounces back to where they started when they hit the ground?
Why are 150k or 200k jobs considered good when there are 300k+ births a month?
Risk of getting Chronic Wasting Disease (CWD) in the United States?
Smoothness of finite-dimensional functional calculus
Can an x86 CPU running in real mode be considered to be basically an 8086 CPU?
Why do falling prices hurt debtors?
Why, historically, did Gödel think CH was false?
To string or not to string
Characters won't fit in table
Why are electrically insulating heatsinks so rare? Is it just cost?
String Manipulation Interpreter
Can a Warlock become Neutral Good?
Minkowski space
Can I ask the recruiters in my resume to put the reason why I am rejected?
Font hinting is lost in Chrome-like browsers (for some languages )
What do the dots in this tr command do: tr .............A-Z A-ZA-Z <<< "JVPQBOV" (with 13 dots)
Which models of the Boeing 737 are still in production?
Why don't electron-positron collisions release infinite energy?
ubuntu 18.04 shutdown problem
Ubuntu 11.10 restart and shutdown not working fullyAttempting to dual boot Ubuntu and Windows 7 on Sony Vaio with Insyde H2O BIOSUbuntu won't shutdownInstall EFI-mode GRUB2 on Ubuntu booted from legacy-modeMixing Legacy and UEFI boot - WIndows 7 and Ubuntu 13.10Dual Boot / Grub 2 issues (Ubuntu/Windows)Shutdown ProblemUbuntu WiFi problem installation problem shutdown restart problemUbuntu 16.04 Network Problem & Shutdown ProblemSOLVED msi laptop install Ubuntu 17.10 on pendrive
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
To add to the many causes/solutions already discussed about this.
I am adding mine to hopefully provide a smarter person with some extra insight that might lead to an actual solution to the core of the problem.(if it hasn't been determined already)... if so, maybe this will help someone in some other way. (and to pose a question or two)
Here is the background information.... the solution I had will be closer to the bottom if you don't care to read this.
I was installing Ubuntu 18.04 from a thumb drive on a dell 7010 thin-client.. fresh 16GB hardrive, 8GB of memory...
After toying with a bunch of things that were prohibiting the install, I finally got it running.
I customized it the way I like, gnome flashback, background pics, etc., and finally KODI(the purpose)... I had done a bunch of reboots up to that point. But when I was finally done I went to do an actual "shutdown" and it froze at the "power down" stage, as everyone else is describing on the internet.
I spent 2 days with it doing every solution on the web on every forum I could find... acpi=off acpi=force, apm=power_off, acpi_osi=this,that,and the next... pci=this,that,and the next.... none of it worked.
Since all searches were leading to hardware/driver/BIOS related solutions, I decided to remove the EFI partition that I had to build while I was "toying with a bunch of things that were prohibiting the install".....
.....so now more background info is needed.
-while I was still ignorant, I could not get ubuntu to install on the drive, as I kept getting the the "grub-efi-amd64-signed failed installation" error....(I like to manually make my partitions) I was not creating the EFI partition necessary for the install. After I did, and everything installed.
-the DELL 7010 thin-client does not have EFI.. it just has legacy bios. (at least as far as I can tell, but there really isn't much as far as options in this particular BIOS, so I am almost sure about that).
SOOOOO... screwing around and testing removing the partitions I pretty much bricked the device, which was fine, I was ready to start over anyway because of something I discovered in all of the searches. I did not know that there were two modes of install (LEGACY, EFI)... legacy = purple boot screen, EFI = black boot screen.
I was getting the black screen. And there was nothing I could do anywhere to get the thin client to boot the install into "Legacy mode". I even tried a usb DVD boot install instead, it still booted into "EFI mode".
solution (for this case)
SOOOO... Being convinced that this was my problem. I popped the drive out and put it into a very old (2008-ish) ASUS box I have. I even took the same 18.04 install thumb drive and booted it into the ASUS box and it instantly comes up with the purple screen (legacy mode)... So I did my install there without a hitch..... And I even did a shutdown there just to make sure, and it worked.
I moved the newly installed drive back into the Dell thin-client, booted it up just fine.... shut down, just fine.
I added all of my customizations just incase they may have been the problem... shut down, just fine.
Problem solved for me... BUT
My question(s) now, is :
what is forcing the thin client to report itself as EFI... or what is making install read the BIOS as EFI?
and what about configuration when it was installed "wrong", caused the shutdown to not work?
If I knew that, I might have been able to come up with a tweaking solution rather than a rebuild.
@$%@#$!!!! new info
Rather than edit this before the submit button I will just let you see what has transpired while typing this....
So I was going to get some information to provide about the bios:
(Phoenix SecureCore Tiano Setup)
(Bios Version 3.0)
(Bios date 9/3/15)
Come to find out, IT IS UEFI!!! BUT, there is no where I can see on any menu to disable it... But to that point, I shouldn't need to! So the only takeaway now is that the shutdown problem existed when installed with UEFI.
I now wonder if the same problem will persist if I let the install automatically partition the drive? I plan to get my hands on another thin-client, I will update.... gottdammit!!!
... hope this helps someone with at least another place to look...
uefi shutdown
asked 6 mins ago
WU-TANGWU-TANG
11
New contributor
WU-TANG is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
To add to the many causes/solutions already discussed about this.
I am adding mine to hopefully provide a smarter person with some extra insight that might lead to an actual solution to the core of the problem.(if it hasn't been determined already)... if so, maybe this will help someone in some other way. (and to pose a question or two)
Here is the background information.... the solution I had will be closer to the bottom if you don't care to read this.
I was installing Ubuntu 18.04 from a thumb drive on a dell 7010 thin-client.. fresh 16GB hardrive, 8GB of memory...
After toying with a bunch of things that were prohibiting the install, I finally got it running.
I customized it the way I like, gnome flashback, background pics, etc., and finally KODI(the purpose)... I had done a bunch of reboots up to that point. But when I was finally done I went to do an actual "shutdown" and it froze at the "power down" stage, as everyone else is describing on the internet.
I spent 2 days with it doing every solution on the web on every forum I could find... acpi=off acpi=force, apm=power_off, acpi_osi=this,that,and the next... pci=this,that,and the next.... none of it worked.
Since all searches were leading to hardware/driver/BIOS related solutions, I decided to remove the EFI partition that I had to build while I was "toying with a bunch of things that were prohibiting the install".....
.....so now more background info is needed.
-while I was still ignorant, I could not get ubuntu to install on the drive, as I kept getting the the "grub-efi-amd64-signed failed installation" error....(I like to manually make my partitions) I was not creating the EFI partition necessary for the install. After I did, and everything installed.
-the DELL 7010 thin-client does not have EFI.. it just has legacy bios. (at least as far as I can tell, but there really isn't much as far as options in this particular BIOS, so I am almost sure about that).
SOOOOO... screwing around and testing removing the partitions I pretty much bricked the device, which was fine, I was ready to start over anyway because of something I discovered in all of the searches. I did not know that there were two modes of install (LEGACY, EFI)... legacy = purple boot screen, EFI = black boot screen.
I was getting the black screen. And there was nothing I could do anywhere to get the thin client to boot the install into "Legacy mode". I even tried a usb DVD boot install instead, it still booted into "EFI mode".
solution (for this case)
SOOOO... Being convinced that this was my problem. I popped the drive out and put it into a very old (2008-ish) ASUS box I have. I even took the same 18.04 install thumb drive and booted it into the ASUS box and it instantly comes up with the purple screen (legacy mode)... So I did my install there without a hitch..... And I even did a shutdown there just to make sure, and it worked.
I moved the newly installed drive back into the Dell thin-client, booted it up just fine.... shut down, just fine.
I added all of my customizations just incase they may have been the problem... shut down, just fine.
Problem solved for me... BUT
My question(s) now, is :
what is forcing the thin client to report itself as EFI... or what is making install read the BIOS as EFI?
and what about configuration when it was installed "wrong", caused the shutdown to not work?
If I knew that, I might have been able to come up with a tweaking solution rather than a rebuild.
@$%@#$!!!! new info
Rather than edit this before the submit button I will just let you see what has transpired while typing this....
So I was going to get some information to provide about the bios:
(Phoenix SecureCore Tiano Setup)
(Bios Version 3.0)
(Bios date 9/3/15)
Come to find out, IT IS UEFI!!! BUT, there is no where I can see on any menu to disable it... But to that point, I shouldn't need to! So the only takeaway now is that the shutdown problem existed when installed with UEFI.
I now wonder if the same problem will persist if I let the install automatically partition the drive? I plan to get my hands on another thin-client, I will update.... gottdammit!!!
... hope this helps someone with at least another place to look...
uefi shutdown
asked 6 mins ago
WU-TANGWU-TANG
11
New contributor
WU-TANG is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Welcome to Ask Ubuntu. This is a question answer site. Please don't put the answer inside the question. You are welcome to answer your own question. Put your answer in the "Your Answer" box below. Edit the question and remove the "solution".
– user68186
2 mins ago
add a comment |
To add to the many causes/solutions already discussed about this.
I am adding mine to hopefully provide a smarter person with some extra insight that might lead to an actual solution to the core of the problem.(if it hasn't been determined already)... if so, maybe this will help someone in some other way. (and to pose a question or two)
Here is the background information.... the solution I had will be closer to the bottom if you don't care to read this.
I was installing Ubuntu 18.04 from a thumb drive on a dell 7010 thin-client.. fresh 16GB hardrive, 8GB of memory...
After toying with a bunch of things that were prohibiting the install, I finally got it running.
I customized it the way I like, gnome flashback, background pics, etc., and finally KODI(the purpose)... I had done a bunch of reboots up to that point. But when I was finally done I went to do an actual "shutdown" and it froze at the "power down" stage, as everyone else is describing on the internet.
I spent 2 days with it doing every solution on the web on every forum I could find... acpi=off acpi=force, apm=power_off, acpi_osi=this,that,and the next... pci=this,that,and the next.... none of it worked.
Since all searches were leading to hardware/driver/BIOS related solutions, I decided to remove the EFI partition that I had to build while I was "toying with a bunch of things that were prohibiting the install".....
.....so now more background info is needed.
-while I was still ignorant, I could not get ubuntu to install on the drive, as I kept getting the the "grub-efi-amd64-signed failed installation" error....(I like to manually make my partitions) I was not creating the EFI partition necessary for the install. After I did, and everything installed.
-the DELL 7010 thin-client does not have EFI.. it just has legacy bios. (at least as far as I can tell, but there really isn't much as far as options in this particular BIOS, so I am almost sure about that).
SOOOOO... screwing around and testing removing the partitions I pretty much bricked the device, which was fine, I was ready to start over anyway because of something I discovered in all of the searches. I did not know that there were two modes of install (LEGACY, EFI)... legacy = purple boot screen, EFI = black boot screen.
I was getting the black screen. And there was nothing I could do anywhere to get the thin client to boot the install into "Legacy mode". I even tried a usb DVD boot install instead, it still booted into "EFI mode".
solution (for this case)
SOOOO... Being convinced that this was my problem. I popped the drive out and put it into a very old (2008-ish) ASUS box I have. I even took the same 18.04 install thumb drive and booted it into the ASUS box and it instantly comes up with the purple screen (legacy mode)... So I did my install there without a hitch..... And I even did a shutdown there just to make sure, and it worked.
I moved the newly installed drive back into the Dell thin-client, booted it up just fine.... shut down, just fine.
I added all of my customizations just incase they may have been the problem... shut down, just fine.
Problem solved for me... BUT
My question(s) now, is :
what is forcing the thin client to report itself as EFI... or what is making install read the BIOS as EFI?
and what about configuration when it was installed "wrong", caused the shutdown to not work?
If I knew that, I might have been able to come up with a tweaking solution rather than a rebuild.
@$%@#$!!!! new info
Rather than edit this before the submit button I will just let you see what has transpired while typing this....
So I was going to get some information to provide about the bios:
(Phoenix SecureCore Tiano Setup)
(Bios Version 3.0)
(Bios date 9/3/15)
Come to find out, IT IS UEFI!!! BUT, there is no where I can see on any menu to disable it... But to that point, I shouldn't need to! So the only takeaway now is that the shutdown problem existed when installed with UEFI.
I now wonder if the same problem will persist if I let the install automatically partition the drive? I plan to get my hands on another thin-client, I will update.... gottdammit!!!
... hope this helps someone with at least another place to look...
uefi shutdown
asked 6 mins ago
WU-TANGWU-TANG
11
New contributor
WU-TANG is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
To add to the many causes/solutions already discussed about this.
I am adding mine to hopefully provide a smarter person with some extra insight that might lead to an actual solution to the core of the problem.(if it hasn't been determined already)... if so, maybe this will help someone in some other way. (and to pose a question or two)
Here is the background information.... the solution I had will be closer to the bottom if you don't care to read this.
I was installing Ubuntu 18.04 from a thumb drive on a dell 7010 thin-client.. fresh 16GB hardrive, 8GB of memory...
After toying with a bunch of things that were prohibiting the install, I finally got it running.
I customized it the way I like, gnome flashback, background pics, etc., and finally KODI(the purpose)... I had done a bunch of reboots up to that point. But when I was finally done I went to do an actual "shutdown" and it froze at the "power down" stage, as everyone else is describing on the internet.
I spent 2 days with it doing every solution on the web on every forum I could find... acpi=off acpi=force, apm=power_off, acpi_osi=this,that,and the next... pci=this,that,and the next.... none of it worked.
Since all searches were leading to hardware/driver/BIOS related solutions, I decided to remove the EFI partition that I had to build while I was "toying with a bunch of things that were prohibiting the install".....
.....so now more background info is needed.
-while I was still ignorant, I could not get ubuntu to install on the drive, as I kept getting the the "grub-efi-amd64-signed failed installation" error....(I like to manually make my partitions) I was not creating the EFI partition necessary for the install. After I did, and everything installed.
-the DELL 7010 thin-client does not have EFI.. it just has legacy bios. (at least as far as I can tell, but there really isn't much as far as options in this particular BIOS, so I am almost sure about that).
SOOOOO... screwing around and testing removing the partitions I pretty much bricked the device, which was fine, I was ready to start over anyway because of something I discovered in all of the searches. I did not know that there were two modes of install (LEGACY, EFI)... legacy = purple boot screen, EFI = black boot screen.
I was getting the black screen. And there was nothing I could do anywhere to get the thin client to boot the install into "Legacy mode". I even tried a usb DVD boot install instead, it still booted into "EFI mode".
solution (for this case)
SOOOO... Being convinced that this was my problem. I popped the drive out and put it into a very old (2008-ish) ASUS box I have. I even took the same 18.04 install thumb drive and booted it into the ASUS box and it instantly comes up with the purple screen (legacy mode)... So I did my install there without a hitch..... And I even did a shutdown there just to make sure, and it worked.
I moved the newly installed drive back into the Dell thin-client, booted it up just fine.... shut down, just fine.
I added all of my customizations just incase they may have been the problem... shut down, just fine.
Problem solved for me... BUT
My question(s) now, is :
what is forcing the thin client to report itself as EFI... or what is making install read the BIOS as EFI?
and what about configuration when it was installed "wrong", caused the shutdown to not work?
If I knew that, I might have been able to come up with a tweaking solution rather than a rebuild.
@$%@#$!!!! new info
Rather than edit this before the submit button I will just let you see what has transpired while typing this....
So I was going to get some information to provide about the bios:
(Phoenix SecureCore Tiano Setup)
(Bios Version 3.0)
(Bios date 9/3/15)
Come to find out, IT IS UEFI!!! BUT, there is no where I can see on any menu to disable it... But to that point, I shouldn't need to! So the only takeaway now is that the shutdown problem existed when installed with UEFI.
I now wonder if the same problem will persist if I let the install automatically partition the drive? I plan to get my hands on another thin-client, I will update.... gottdammit!!!
... hope this helps someone with at least another place to look...
uefi shutdown
uefi shutdown
asked 6 mins ago
WU-TANGWU-TANG
11
New contributor
WU-TANG is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 6 mins ago
WU-TANGWU-TANG
11
New contributor
WU-TANG is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 6 mins ago
WU-TANGWU-TANG
11
New contributor
WU-TANG is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 6 mins ago
WU-TANGWU-TANG
11
asked 6 mins ago
WU-TANGWU-TANG
11
11
New contributor
WU-TANG is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
WU-TANG is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
WU-TANG is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Welcome to Ask Ubuntu. This is a question answer site. Please don't put the answer inside the question. You are welcome to answer your own question. Put your answer in the "Your Answer" box below. Edit the question and remove the "solution".
– user68186
2 mins ago
add a comment |
Welcome to Ask Ubuntu. This is a question answer site. Please don't put the answer inside the question. You are welcome to answer your own question. Put your answer in the "Your Answer" box below. Edit the question and remove the "solution".
– user68186
2 mins ago
Welcome to Ask Ubuntu. This is a question answer site. Please don't put the answer inside the question. You are welcome to answer your own question. Put your answer in the "Your Answer" box below. Edit the question and remove the "solution".
– user68186
2 mins ago
Welcome to Ask Ubuntu. This is a question answer site. Please don't put the answer inside the question. You are welcome to answer your own question. Put your answer in the "Your Answer" box below. Edit the question and remove the "solution".
– user68186
2 mins ago
add a comment |
0
active
oldest
votes
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
});
}
});
WU-TANG is a new contributor. Be nice, and check out our Code of Conduct.
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%2f1131757%2fubuntu-18-04-shutdown-problem%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
WU-TANG is a new contributor. Be nice, and check out our Code of Conduct.
WU-TANG is a new contributor. Be nice, and check out our Code of Conduct.
WU-TANG is a new contributor. Be nice, and check out our Code of Conduct.
WU-TANG is a new contributor. Be nice, and check out our Code of Conduct.
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%2f1131757%2fubuntu-18-04-shutdown-problem%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
Welcome to Ask Ubuntu. This is a question answer site. Please don't put the answer inside the question. You are welcome to answer your own question. Put your answer in the "Your Answer" box below. Edit the question and remove the "solution".
– user68186
2 mins ago