Timeline for Stuck in console after console-boot due to script, how to force startup in GUI?
Current License: CC BY-SA 3.0
16 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:56 | history | edited | CommunityBot |
replaced http://raspberrypi.stackexchange.com/ with https://raspberrypi.stackexchange.com/
|
|
| Jan 12, 2014 at 13:31 | comment | added | Gerben | Pressing [ALT]+[F2] will open a separate console. Might help here. | |
| Jan 11, 2014 at 23:22 | answer | added | RPiAwesomeness | timeline score: 3 | |
| Jan 11, 2014 at 22:31 | history | edited | syb0rg | CC BY-SA 3.0 |
Better formatting.
|
| Jan 11, 2014 at 21:01 | comment | added | RPiAwesomeness | let us continue this discussion in chat | |
| Jan 11, 2014 at 20:58 | comment | added | Maarten Hartman | no :( only basic commands like cd and ls. And I can edit config.txt via the recovery mode, so that gives hope.. | |
| Jan 11, 2014 at 20:56 | comment | added | RPiAwesomeness |
Can you run raspi-config?
|
|
| Jan 11, 2014 at 20:41 | comment | added | Maarten Hartman | okay I got a bit further. I can now boot into emergency and I can edit the config.txt file. How can I use the config file to boot into the GUI? Or what command can I use to boot into the GUI from emergency mode? Sudo and nano for example are all unavailable. | |
| Jan 11, 2014 at 5:43 | history | tweeted | twitter.com/#!/StackRaspi/status/421880051953852416 | ||
| Jan 11, 2014 at 1:49 | comment | added | RPiAwesomeness | You can get to the recovery mode by holding shift during the boot. Should keep your script from executing, allowing you to boot and fix the issue to an extent. Read this question: raspberrypi.stackexchange.com/questions/1416/… that explains the difference between the kernels. You can boot the emergency kernel by renaming kernel.img to kernel.img and kernel_emergency.img to kernel.img. Should work the same as holding shift. | |
| Jan 11, 2014 at 1:46 | comment | added | RPiAwesomeness | I meant in recovery/emergency mode. You could also pop the SD card into your PC and then comment out the line in the bashrc file that starts the offending script. You can also pull some of the logs off the Pi and post them online so we can view them. | |
| Jan 11, 2014 at 0:37 | comment | added | Maarten Hartman | can't try it right now, but I think it won't work. The console won't respond to no commands after the custom startup script crashes. How can I make the console respond to my commands? Note: the script runs automatically on boot to console, can I abort the script it with ctrl + c or a other command? | |
| Jan 10, 2014 at 23:01 | comment | added | RPiAwesomeness |
You should be able to mount the SD card in the recovery mode and change the boot up script to not execute that script. Then the Pi would boot normally. Would have to run sudo mount to do it. Have you tried that?
|
|
| Jan 10, 2014 at 22:34 | history | edited | Maarten Hartman | CC BY-SA 3.0 |
deleted 1 characters in body
|
| Jan 10, 2014 at 22:25 | history | edited | Maarten Hartman | CC BY-SA 3.0 |
added 50 characters in body
|
| Jan 10, 2014 at 22:20 | history | asked | Maarten Hartman | CC BY-SA 3.0 |