Startup failure :Started WPA Supplicant
Clash Royale CLAN TAG#URR8PPP
Why does my system boot stop at "Started WPA Supplicant"?
When I try to startup up my ArchLinux it pauses at "Started WPA supplicant" I had other problems which I solved like SDDM failure. And now everything shows OK. However the startup doesn't continue.
I've tried updating the system but it always fails.
arch-linux startup
asked Mar 12 '17 at 3:33
Charlie PlettCharlie Plett
287
|
show 1 more comment
Why does my system boot stop at "Started WPA Supplicant"?
When I try to startup up my ArchLinux it pauses at "Started WPA supplicant" I had other problems which I solved like SDDM failure. And now everything shows OK. However the startup doesn't continue.
I've tried updating the system but it always fails.
arch-linux startup
asked Mar 12 '17 at 3:33
Charlie PlettCharlie Plett
287
Now I updated wpa_supplicant and it says The /etc/wpa_supplicant/wpa_supplicant.conf is file no longer managed by pacman and if it was modified, it has been renamed to wpa_supplicant.conf.pacsave. Move it to the original location of needed.
– Charlie Plett
Mar 12 '17 at 4:04
The startup screen also says failed to start Load/Save screen.
– Charlie Plett
Mar 12 '17 at 4:05
1
If everything shows OK, including that the machine started WPA supplicant, then your diagnosis that WPA Supplicant is faulty is clearly wrong. You need, as has already been said, to describe your system's actions more accurately than this. "it fails" is woefully inadequate, not least because there are two possible antecedents for the pronoun. People are not telepathic.
– JdeBP
Mar 12 '17 at 6:49
After running yaourt -Syua it shows error: failed to commit transaction (conflicting files) ttf-dejavu: /etc/fonts/conf.d/20-unhint-small-dejavu-sans-mono.conf exists in filesystem.
– Charlie Plett
Mar 12 '17 at 14:14
Now I removed ttf-dejavu and I will retry update.
– Charlie Plett
Mar 12 '17 at 14:17
|
show 1 more comment
Why does my system boot stop at "Started WPA Supplicant"?
When I try to startup up my ArchLinux it pauses at "Started WPA supplicant" I had other problems which I solved like SDDM failure. And now everything shows OK. However the startup doesn't continue.
I've tried updating the system but it always fails.
arch-linux startup
asked Mar 12 '17 at 3:33
Charlie PlettCharlie Plett
287
Why does my system boot stop at "Started WPA Supplicant"?
When I try to startup up my ArchLinux it pauses at "Started WPA supplicant" I had other problems which I solved like SDDM failure. And now everything shows OK. However the startup doesn't continue.
I've tried updating the system but it always fails.
arch-linux startup
arch-linux startup
asked Mar 12 '17 at 3:33
Charlie PlettCharlie Plett
287
asked Mar 12 '17 at 3:33
Charlie PlettCharlie Plett
287
edited Mar 12 '17 at 3:55
Charlie Plett
asked Mar 12 '17 at 3:33
Charlie PlettCharlie Plett
287
asked Mar 12 '17 at 3:33
Charlie PlettCharlie Plett
287
asked Mar 12 '17 at 3:33
Charlie PlettCharlie Plett
287
287
Now I updated wpa_supplicant and it says The /etc/wpa_supplicant/wpa_supplicant.conf is file no longer managed by pacman and if it was modified, it has been renamed to wpa_supplicant.conf.pacsave. Move it to the original location of needed.
– Charlie Plett
Mar 12 '17 at 4:04
The startup screen also says failed to start Load/Save screen.
– Charlie Plett
Mar 12 '17 at 4:05
1
If everything shows OK, including that the machine started WPA supplicant, then your diagnosis that WPA Supplicant is faulty is clearly wrong. You need, as has already been said, to describe your system's actions more accurately than this. "it fails" is woefully inadequate, not least because there are two possible antecedents for the pronoun. People are not telepathic.
– JdeBP
Mar 12 '17 at 6:49
After running yaourt -Syua it shows error: failed to commit transaction (conflicting files) ttf-dejavu: /etc/fonts/conf.d/20-unhint-small-dejavu-sans-mono.conf exists in filesystem.
– Charlie Plett
Mar 12 '17 at 14:14
Now I removed ttf-dejavu and I will retry update.
– Charlie Plett
Mar 12 '17 at 14:17
|
show 1 more comment
Now I updated wpa_supplicant and it says The /etc/wpa_supplicant/wpa_supplicant.conf is file no longer managed by pacman and if it was modified, it has been renamed to wpa_supplicant.conf.pacsave. Move it to the original location of needed.
– Charlie Plett
Mar 12 '17 at 4:04
The startup screen also says failed to start Load/Save screen.
– Charlie Plett
Mar 12 '17 at 4:05
1
If everything shows OK, including that the machine started WPA supplicant, then your diagnosis that WPA Supplicant is faulty is clearly wrong. You need, as has already been said, to describe your system's actions more accurately than this. "it fails" is woefully inadequate, not least because there are two possible antecedents for the pronoun. People are not telepathic.
– JdeBP
Mar 12 '17 at 6:49
After running yaourt -Syua it shows error: failed to commit transaction (conflicting files) ttf-dejavu: /etc/fonts/conf.d/20-unhint-small-dejavu-sans-mono.conf exists in filesystem.
– Charlie Plett
Mar 12 '17 at 14:14
Now I removed ttf-dejavu and I will retry update.
– Charlie Plett
Mar 12 '17 at 14:17
Now I updated wpa_supplicant and it says The /etc/wpa_supplicant/wpa_supplicant.conf is file no longer managed by pacman and if it was modified, it has been renamed to wpa_supplicant.conf.pacsave. Move it to the original location of needed.
– Charlie Plett
Mar 12 '17 at 4:04
Now I updated wpa_supplicant and it says The /etc/wpa_supplicant/wpa_supplicant.conf is file no longer managed by pacman and if it was modified, it has been renamed to wpa_supplicant.conf.pacsave. Move it to the original location of needed.
– Charlie Plett
Mar 12 '17 at 4:04
The startup screen also says failed to start Load/Save screen.
– Charlie Plett
Mar 12 '17 at 4:05
The startup screen also says failed to start Load/Save screen.
– Charlie Plett
Mar 12 '17 at 4:05
1
1
If everything shows OK, including that the machine started WPA supplicant, then your diagnosis that WPA Supplicant is faulty is clearly wrong. You need, as has already been said, to describe your system's actions more accurately than this. "it fails" is woefully inadequate, not least because there are two possible antecedents for the pronoun. People are not telepathic.
– JdeBP
Mar 12 '17 at 6:49
If everything shows OK, including that the machine started WPA supplicant, then your diagnosis that WPA Supplicant is faulty is clearly wrong. You need, as has already been said, to describe your system's actions more accurately than this. "it fails" is woefully inadequate, not least because there are two possible antecedents for the pronoun. People are not telepathic.
– JdeBP
Mar 12 '17 at 6:49
After running yaourt -Syua it shows error: failed to commit transaction (conflicting files) ttf-dejavu: /etc/fonts/conf.d/20-unhint-small-dejavu-sans-mono.conf exists in filesystem.
– Charlie Plett
Mar 12 '17 at 14:14
After running yaourt -Syua it shows error: failed to commit transaction (conflicting files) ttf-dejavu: /etc/fonts/conf.d/20-unhint-small-dejavu-sans-mono.conf exists in filesystem.
– Charlie Plett
Mar 12 '17 at 14:14
Now I removed ttf-dejavu and I will retry update.
– Charlie Plett
Mar 12 '17 at 14:17
Now I removed ttf-dejavu and I will retry update.
– Charlie Plett
Mar 12 '17 at 14:17
|
show 1 more comment
1 Answer
1
active
oldest
votes
A little more information would help a lot actually..
Did you recently install the wpa_supplicant package?
Did you update your system recently?
Is this a fresh install?
Have you auto enabled a wifi profile lately? May something be wrong with that profile?
How long have you waited since the output on the screen says "Started WPA Supplicant" and did it actually go "success" and says "started" or "starting".. Is it still like that or did you turn it off?
Based on your other recent question here i assume you are running Arch Linux, would you be able to boot with the installation medium of Arch and chroot and disable/remove wpa_supplicant, and then try to boot your system again? Might be a broken package.. Have you checked bug tracker @ arch website?
Also, you could try to diagnose the hardware, (RAM and HDD) with Memtest and gsmartcontrol(smartmontools) (long shot, but still possible..)
I won't apologize for asking more questions than i replied with answers since your question is extremely vague.
answered Mar 12 '17 at 3:48
SlckrSlckr
11
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2funix.stackexchange.com%2fquestions%2f350849%2fstartup-failure-started-wpa-supplicant%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
A little more information would help a lot actually..
Did you recently install the wpa_supplicant package?
Did you update your system recently?
Is this a fresh install?
Have you auto enabled a wifi profile lately? May something be wrong with that profile?
How long have you waited since the output on the screen says "Started WPA Supplicant" and did it actually go "success" and says "started" or "starting".. Is it still like that or did you turn it off?
Based on your other recent question here i assume you are running Arch Linux, would you be able to boot with the installation medium of Arch and chroot and disable/remove wpa_supplicant, and then try to boot your system again? Might be a broken package.. Have you checked bug tracker @ arch website?
Also, you could try to diagnose the hardware, (RAM and HDD) with Memtest and gsmartcontrol(smartmontools) (long shot, but still possible..)
I won't apologize for asking more questions than i replied with answers since your question is extremely vague.
answered Mar 12 '17 at 3:48
SlckrSlckr
11
add a comment |
A little more information would help a lot actually..
Did you recently install the wpa_supplicant package?
Did you update your system recently?
Is this a fresh install?
Have you auto enabled a wifi profile lately? May something be wrong with that profile?
How long have you waited since the output on the screen says "Started WPA Supplicant" and did it actually go "success" and says "started" or "starting".. Is it still like that or did you turn it off?
Based on your other recent question here i assume you are running Arch Linux, would you be able to boot with the installation medium of Arch and chroot and disable/remove wpa_supplicant, and then try to boot your system again? Might be a broken package.. Have you checked bug tracker @ arch website?
Also, you could try to diagnose the hardware, (RAM and HDD) with Memtest and gsmartcontrol(smartmontools) (long shot, but still possible..)
I won't apologize for asking more questions than i replied with answers since your question is extremely vague.
answered Mar 12 '17 at 3:48
SlckrSlckr
11
add a comment |
A little more information would help a lot actually..
Did you recently install the wpa_supplicant package?
Did you update your system recently?
Is this a fresh install?
Have you auto enabled a wifi profile lately? May something be wrong with that profile?
How long have you waited since the output on the screen says "Started WPA Supplicant" and did it actually go "success" and says "started" or "starting".. Is it still like that or did you turn it off?
Based on your other recent question here i assume you are running Arch Linux, would you be able to boot with the installation medium of Arch and chroot and disable/remove wpa_supplicant, and then try to boot your system again? Might be a broken package.. Have you checked bug tracker @ arch website?
Also, you could try to diagnose the hardware, (RAM and HDD) with Memtest and gsmartcontrol(smartmontools) (long shot, but still possible..)
I won't apologize for asking more questions than i replied with answers since your question is extremely vague.
answered Mar 12 '17 at 3:48
SlckrSlckr
11
A little more information would help a lot actually..
Did you recently install the wpa_supplicant package?
Did you update your system recently?
Is this a fresh install?
Have you auto enabled a wifi profile lately? May something be wrong with that profile?
How long have you waited since the output on the screen says "Started WPA Supplicant" and did it actually go "success" and says "started" or "starting".. Is it still like that or did you turn it off?
Based on your other recent question here i assume you are running Arch Linux, would you be able to boot with the installation medium of Arch and chroot and disable/remove wpa_supplicant, and then try to boot your system again? Might be a broken package.. Have you checked bug tracker @ arch website?
Also, you could try to diagnose the hardware, (RAM and HDD) with Memtest and gsmartcontrol(smartmontools) (long shot, but still possible..)
I won't apologize for asking more questions than i replied with answers since your question is extremely vague.
answered Mar 12 '17 at 3:48
SlckrSlckr
11
answered Mar 12 '17 at 3:48
SlckrSlckr
11
answered Mar 12 '17 at 3:48
SlckrSlckr
11
answered Mar 12 '17 at 3:48
SlckrSlckr
11
11
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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%2funix.stackexchange.com%2fquestions%2f350849%2fstartup-failure-started-wpa-supplicant%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
Now I updated wpa_supplicant and it says The /etc/wpa_supplicant/wpa_supplicant.conf is file no longer managed by pacman and if it was modified, it has been renamed to wpa_supplicant.conf.pacsave. Move it to the original location of needed.
– Charlie Plett
Mar 12 '17 at 4:04
The startup screen also says failed to start Load/Save screen.
– Charlie Plett
Mar 12 '17 at 4:05
1
If everything shows OK, including that the machine started WPA supplicant, then your diagnosis that WPA Supplicant is faulty is clearly wrong. You need, as has already been said, to describe your system's actions more accurately than this. "it fails" is woefully inadequate, not least because there are two possible antecedents for the pronoun. People are not telepathic.
– JdeBP
Mar 12 '17 at 6:49
After running yaourt -Syua it shows error: failed to commit transaction (conflicting files) ttf-dejavu: /etc/fonts/conf.d/20-unhint-small-dejavu-sans-mono.conf exists in filesystem.
– Charlie Plett
Mar 12 '17 at 14:14
Now I removed ttf-dejavu and I will retry update.
– Charlie Plett
Mar 12 '17 at 14:17