System booting in VGA and giving “A start job is running…” errors [closed]
Clash Royale CLAN TAG#URR8PPP
I have an arch linux system that is not booting properly. It starts in VGA mode with big text, which is unusual. Then, as it boots, it is giving multiple "A start job is runing..." errors. Also, startup text messages have highlighted "?" characters where letters should be. Eventually the system starts, albeit in VGA mode, and presents a login prompt.
When I use journalctl -b command I get the following errors in the listing:
ACPI BIOS Error (bug): Could not resolve [_SB.PCIO.SAT0.PRT1._GTF.DDP], AE_NOT_FOUND (20180810/psargs-330)
ACPI Error: Method parse/execution failed _SB.PCIO.SAT0.PRT1._GTF.DDP], AE_NOT_FOUND (20180810/psparse-516)
....
Timed out waiting for device sys-subsystem-net-d (rest unreadable)
Since the screen is in VGA mode the text is cutoff (how do you scroll right in a virtual terminal?)
The only thing that changed since my last boot which was normal is that I enabled the network and did a package database update.
UPDATE
The module for the network is apparently not getting loaded because the boot kernel is now different than the installed kernel somehow? I don't understand exactly what this means.
arch-linux boot troubleshooting
asked Jan 7 at 22:33
Tyler DurdenTyler Durden
1,59242050
closed as unclear what you're asking by jasonwryan, Mr Shunz, msp9011, nwildner, Christopher Jan 10 at 13:41
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
|
show 1 more comment
I have an arch linux system that is not booting properly. It starts in VGA mode with big text, which is unusual. Then, as it boots, it is giving multiple "A start job is runing..." errors. Also, startup text messages have highlighted "?" characters where letters should be. Eventually the system starts, albeit in VGA mode, and presents a login prompt.
When I use journalctl -b command I get the following errors in the listing:
ACPI BIOS Error (bug): Could not resolve [_SB.PCIO.SAT0.PRT1._GTF.DDP], AE_NOT_FOUND (20180810/psargs-330)
ACPI Error: Method parse/execution failed _SB.PCIO.SAT0.PRT1._GTF.DDP], AE_NOT_FOUND (20180810/psparse-516)
....
Timed out waiting for device sys-subsystem-net-d (rest unreadable)
Since the screen is in VGA mode the text is cutoff (how do you scroll right in a virtual terminal?)
The only thing that changed since my last boot which was normal is that I enabled the network and did a package database update.
UPDATE
The module for the network is apparently not getting loaded because the boot kernel is now different than the installed kernel somehow? I don't understand exactly what this means.
arch-linux boot troubleshooting
asked Jan 7 at 22:33
Tyler DurdenTyler Durden
1,59242050
closed as unclear what you're asking by jasonwryan, Mr Shunz, msp9011, nwildner, Christopher Jan 10 at 13:41
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
From a chroot, read the actual error "sys-subsystem-net..." and then fix your misconfigured network service.
– jasonwryan
Jan 7 at 22:44
@jasonwryan I don't understand your instruction.
– Tyler Durden
Jan 7 at 22:49
What part do you not understand? You really are using the wrong distro.
– jasonwryan
Jan 7 at 22:52
@jasonwryan What is the "actual error"? Do you mean the rest of the error which is unreadable? When I use dmesg I can see the whole errors because the errors wrap. But when I use journalctl, it has each entry on its own line and they have line continuation triangles at the end of the line, so it suggests I can scroll the terminal somehow, but I don't know how. As far as chroot is concerned, I guess I don't understand what directory I should be "chroot'ing" into and how that would help me to understand the error.
– Tyler Durden
Jan 7 at 22:56
Read the wiki entry on filtering output, especially the tip about truncated lines. The error is telling you about a misconfigured network device: fix it (either from a chroot or change your default target at boot - both options are documented in the wiki).
– jasonwryan
Jan 7 at 23:00
|
show 1 more comment
I have an arch linux system that is not booting properly. It starts in VGA mode with big text, which is unusual. Then, as it boots, it is giving multiple "A start job is runing..." errors. Also, startup text messages have highlighted "?" characters where letters should be. Eventually the system starts, albeit in VGA mode, and presents a login prompt.
When I use journalctl -b command I get the following errors in the listing:
ACPI BIOS Error (bug): Could not resolve [_SB.PCIO.SAT0.PRT1._GTF.DDP], AE_NOT_FOUND (20180810/psargs-330)
ACPI Error: Method parse/execution failed _SB.PCIO.SAT0.PRT1._GTF.DDP], AE_NOT_FOUND (20180810/psparse-516)
....
Timed out waiting for device sys-subsystem-net-d (rest unreadable)
Since the screen is in VGA mode the text is cutoff (how do you scroll right in a virtual terminal?)
The only thing that changed since my last boot which was normal is that I enabled the network and did a package database update.
UPDATE
The module for the network is apparently not getting loaded because the boot kernel is now different than the installed kernel somehow? I don't understand exactly what this means.
arch-linux boot troubleshooting
asked Jan 7 at 22:33
Tyler DurdenTyler Durden
1,59242050
I have an arch linux system that is not booting properly. It starts in VGA mode with big text, which is unusual. Then, as it boots, it is giving multiple "A start job is runing..." errors. Also, startup text messages have highlighted "?" characters where letters should be. Eventually the system starts, albeit in VGA mode, and presents a login prompt.
When I use journalctl -b command I get the following errors in the listing:
ACPI BIOS Error (bug): Could not resolve [_SB.PCIO.SAT0.PRT1._GTF.DDP], AE_NOT_FOUND (20180810/psargs-330)
ACPI Error: Method parse/execution failed _SB.PCIO.SAT0.PRT1._GTF.DDP], AE_NOT_FOUND (20180810/psparse-516)
....
Timed out waiting for device sys-subsystem-net-d (rest unreadable)
Since the screen is in VGA mode the text is cutoff (how do you scroll right in a virtual terminal?)
The only thing that changed since my last boot which was normal is that I enabled the network and did a package database update.
UPDATE
The module for the network is apparently not getting loaded because the boot kernel is now different than the installed kernel somehow? I don't understand exactly what this means.
arch-linux boot troubleshooting
arch-linux boot troubleshooting
asked Jan 7 at 22:33
Tyler DurdenTyler Durden
1,59242050
asked Jan 7 at 22:33
Tyler DurdenTyler Durden
1,59242050
edited Jan 8 at 0:42
Tyler Durden
asked Jan 7 at 22:33
Tyler DurdenTyler Durden
1,59242050
asked Jan 7 at 22:33
Tyler DurdenTyler Durden
1,59242050
asked Jan 7 at 22:33
Tyler DurdenTyler Durden
1,59242050
1,59242050
closed as unclear what you're asking by jasonwryan, Mr Shunz, msp9011, nwildner, Christopher Jan 10 at 13:41
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
closed as unclear what you're asking by jasonwryan, Mr Shunz, msp9011, nwildner, Christopher Jan 10 at 13:41
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
From a chroot, read the actual error "sys-subsystem-net..." and then fix your misconfigured network service.
– jasonwryan
Jan 7 at 22:44
@jasonwryan I don't understand your instruction.
– Tyler Durden
Jan 7 at 22:49
What part do you not understand? You really are using the wrong distro.
– jasonwryan
Jan 7 at 22:52
@jasonwryan What is the "actual error"? Do you mean the rest of the error which is unreadable? When I use dmesg I can see the whole errors because the errors wrap. But when I use journalctl, it has each entry on its own line and they have line continuation triangles at the end of the line, so it suggests I can scroll the terminal somehow, but I don't know how. As far as chroot is concerned, I guess I don't understand what directory I should be "chroot'ing" into and how that would help me to understand the error.
– Tyler Durden
Jan 7 at 22:56
Read the wiki entry on filtering output, especially the tip about truncated lines. The error is telling you about a misconfigured network device: fix it (either from a chroot or change your default target at boot - both options are documented in the wiki).
– jasonwryan
Jan 7 at 23:00
|
show 1 more comment
From a chroot, read the actual error "sys-subsystem-net..." and then fix your misconfigured network service.
– jasonwryan
Jan 7 at 22:44
@jasonwryan I don't understand your instruction.
– Tyler Durden
Jan 7 at 22:49
What part do you not understand? You really are using the wrong distro.
– jasonwryan
Jan 7 at 22:52
@jasonwryan What is the "actual error"? Do you mean the rest of the error which is unreadable? When I use dmesg I can see the whole errors because the errors wrap. But when I use journalctl, it has each entry on its own line and they have line continuation triangles at the end of the line, so it suggests I can scroll the terminal somehow, but I don't know how. As far as chroot is concerned, I guess I don't understand what directory I should be "chroot'ing" into and how that would help me to understand the error.
– Tyler Durden
Jan 7 at 22:56
Read the wiki entry on filtering output, especially the tip about truncated lines. The error is telling you about a misconfigured network device: fix it (either from a chroot or change your default target at boot - both options are documented in the wiki).
– jasonwryan
Jan 7 at 23:00
From a chroot, read the actual error "sys-subsystem-net..." and then fix your misconfigured network service.
– jasonwryan
Jan 7 at 22:44
From a chroot, read the actual error "sys-subsystem-net..." and then fix your misconfigured network service.
– jasonwryan
Jan 7 at 22:44
@jasonwryan I don't understand your instruction.
– Tyler Durden
Jan 7 at 22:49
@jasonwryan I don't understand your instruction.
– Tyler Durden
Jan 7 at 22:49
What part do you not understand? You really are using the wrong distro.
– jasonwryan
Jan 7 at 22:52
What part do you not understand? You really are using the wrong distro.
– jasonwryan
Jan 7 at 22:52
@jasonwryan What is the "actual error"? Do you mean the rest of the error which is unreadable? When I use dmesg I can see the whole errors because the errors wrap. But when I use journalctl, it has each entry on its own line and they have line continuation triangles at the end of the line, so it suggests I can scroll the terminal somehow, but I don't know how. As far as chroot is concerned, I guess I don't understand what directory I should be "chroot'ing" into and how that would help me to understand the error.
– Tyler Durden
Jan 7 at 22:56
@jasonwryan What is the "actual error"? Do you mean the rest of the error which is unreadable? When I use dmesg I can see the whole errors because the errors wrap. But when I use journalctl, it has each entry on its own line and they have line continuation triangles at the end of the line, so it suggests I can scroll the terminal somehow, but I don't know how. As far as chroot is concerned, I guess I don't understand what directory I should be "chroot'ing" into and how that would help me to understand the error.
– Tyler Durden
Jan 7 at 22:56
Read the wiki entry on filtering output, especially the tip about truncated lines. The error is telling you about a misconfigured network device: fix it (either from a chroot or change your default target at boot - both options are documented in the wiki).
– jasonwryan
Jan 7 at 23:00
Read the wiki entry on filtering output, especially the tip about truncated lines. The error is telling you about a misconfigured network device: fix it (either from a chroot or change your default target at boot - both options are documented in the wiki).
– jasonwryan
Jan 7 at 23:00
|
show 1 more comment
0
active
oldest
votes
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
From a chroot, read the actual error "sys-subsystem-net..." and then fix your misconfigured network service.
– jasonwryan
Jan 7 at 22:44
@jasonwryan I don't understand your instruction.
– Tyler Durden
Jan 7 at 22:49
What part do you not understand? You really are using the wrong distro.
– jasonwryan
Jan 7 at 22:52
@jasonwryan What is the "actual error"? Do you mean the rest of the error which is unreadable? When I use dmesg I can see the whole errors because the errors wrap. But when I use journalctl, it has each entry on its own line and they have line continuation triangles at the end of the line, so it suggests I can scroll the terminal somehow, but I don't know how. As far as chroot is concerned, I guess I don't understand what directory I should be "chroot'ing" into and how that would help me to understand the error.
– Tyler Durden
Jan 7 at 22:56
Read the wiki entry on filtering output, especially the tip about truncated lines. The error is telling you about a misconfigured network device: fix it (either from a chroot or change your default target at boot - both options are documented in the wiki).
– jasonwryan
Jan 7 at 23:00