NetCube-Systems-Austria/kumquat-buildroot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

manual: (faq-boot-hang-after-starting) fix config entries

Browse Source 
Signed-off-by: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
This commit is contained in:
Vivien Didelot 2014-06-18 10:12:10 -04:00 committed by Thomas Petazzoni
parent 929180d1b8
commit 9ab109869f
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/manual/faq-troubleshooting.txt
View File

@ -19,11 +19,11 @@ Starting dropbear sshd: generating rsa key... generating dsa key... OK
then it means that your system is running, but didn't start a shell on then it means that your system is running, but didn't start a shell on
the serial console. In order to have the system start a shell on your the serial console. In order to have the system start a shell on your
serial console, you have to go into the Buildroot configuration, +System serial console, you have to go into the Buildroot configuration, in
configuration+, and modify +Port to run a getty (login prompt) on+ and +System configuration+, modify +Run a getty (login prompt) after boot+
+Baudrate to use+ as appropriate. This will automatically tune the and set the appropriate port and baud rate in the +getty options+
+/etc/inittab+ file of the generated system so that a shell starts on submenu. This will automatically tune the +/etc/inittab+ file of the
the correct serial port. generated system so that a shell starts on the correct serial port.
[[faq-no-compiler-on-target]] [[faq-no-compiler-on-target]]
== Why is there no compiler on the target? == Why is there no compiler on the target?