liminix

Unnamed repository; edit this file 'description' to name the repository.
Log | Files | Refs | README | LICENSE

commit a0b36be5e46978d022d8dbf6b0880f673c867715
parent 9bc9a077e372ab6de01187e03b4414e28b72bf25
Author: Daniel Barlow <dan@telent.net>
Date:   Sun,  6 Apr 2025 23:53:03 +0100

randomly proofread small sections

Diffstat:
Mdoc/configuration.adoc | 4++--
Mdoc/installation.adoc | 6++++--
Mdoc/tutorial.adoc | 6+++---
3 files changed, 9 insertions(+), 7 deletions(-)

diff --git a/doc/configuration.adoc b/doc/configuration.adoc @@ -1,7 +1,7 @@ == Configuration -There are many things you can specify in a configuration, but these are -the ones you most commonly need to change: +There are many things you can specify in a configuration, but most +commonly you need to change: * which services (processes) to run * what packages to install diff --git a/doc/installation.adoc b/doc/installation.adoc @@ -55,7 +55,7 @@ early boot, the risk of "bricking" is substantially reduced and you have options for recovering if you misstep or flash a bad image. [[serial]] -==== U-Boot and serial shenanigans +==== Serial connections Every device that we have so far encountered in Liminix uses https://docs.u-boot.org/en/latest/[U-Boot&#44; the "Universal Boot @@ -97,7 +97,9 @@ When you turn the router on you should be greeted with some messages from U-Boot, followed by the instruction to hit some key to stop autoboot. Do this and you will get to the prompt. If you didn't see anything, the strong likelihood is that TX and RX are the wrong way -around. If you see garbage, try a different speed. +around, or your computer is expecting flow control which the 3 wire +connection does not provide. . If you see garbage, try a different +speed. Interesting commands to try first in U-Boot are `+help+` and `+printenv+`. diff --git a/doc/tutorial.adoc b/doc/tutorial.adoc @@ -136,12 +136,12 @@ to attach serial cables to (soldering not required), so it is lower-risk than some devices. Using some other Liminix-supported MIPS hardware device also _ought_ to work here, but you accept the slightly greater bricking risk if it doesn't. -==== See <<_supported_hardware>> for device support status. +==== -You may want to read and inwardly digest the section about <<serial>> -connections when you start working with Liminix on real hardware. You +You may want to read and inwardly digest the section on <<serial>> +when you start working with Liminix on real hardware. You won't _need_ serial access for this example, assuming it works, but it allows you to see the boot monitor and kernel messages, and to login directly to the device if for some reason it doesn't bring its network