Chained serial connections to Linux machines with picocom and screen issues
I am connecting via serial terminal (picocom) to a Linux machine which at the same time has several serial interfaces I want to use. In that Linux machine I can only use screen to do so. My problem is that once i have one screen session open none of the screen key combinations work (detach, close...) as picocom is opened in a lower level thus waiting for key compilations. The problem with this situation is that I can't close firs the screen session forcing me to reboot the system every time I want to do something else.
I wonder if there is something I can do to avoid this situation.
serial-port serial-console
asked Feb 7 at 12:37
user3770060user3770060
1
add a comment |
I am connecting via serial terminal (picocom) to a Linux machine which at the same time has several serial interfaces I want to use. In that Linux machine I can only use screen to do so. My problem is that once i have one screen session open none of the screen key combinations work (detach, close...) as picocom is opened in a lower level thus waiting for key compilations. The problem with this situation is that I can't close firs the screen session forcing me to reboot the system every time I want to do something else.
I wonder if there is something I can do to avoid this situation.
serial-port serial-console
asked Feb 7 at 12:37
user3770060user3770060
1
1
By default, both picocom and screen use control-a as the special command character. If you start picocom with option--escape bfor example, then when you type control-a it should get passed through to the screen program. You will obviously have to use control-b for your picocom commands.
– meuh
Feb 7 at 13:36
Worked flawlessly :)
– user3770060
Feb 7 at 16:29
add a comment |
I am connecting via serial terminal (picocom) to a Linux machine which at the same time has several serial interfaces I want to use. In that Linux machine I can only use screen to do so. My problem is that once i have one screen session open none of the screen key combinations work (detach, close...) as picocom is opened in a lower level thus waiting for key compilations. The problem with this situation is that I can't close firs the screen session forcing me to reboot the system every time I want to do something else.
I wonder if there is something I can do to avoid this situation.
serial-port serial-console
asked Feb 7 at 12:37
user3770060user3770060
1
I am connecting via serial terminal (picocom) to a Linux machine which at the same time has several serial interfaces I want to use. In that Linux machine I can only use screen to do so. My problem is that once i have one screen session open none of the screen key combinations work (detach, close...) as picocom is opened in a lower level thus waiting for key compilations. The problem with this situation is that I can't close firs the screen session forcing me to reboot the system every time I want to do something else.
I wonder if there is something I can do to avoid this situation.
serial-port serial-console
serial-port serial-console
asked Feb 7 at 12:37
user3770060user3770060
1
asked Feb 7 at 12:37
user3770060user3770060
1
asked Feb 7 at 12:37
user3770060user3770060
1
asked Feb 7 at 12:37
user3770060user3770060
1
asked Feb 7 at 12:37
user3770060user3770060
1
1
1
By default, both picocom and screen use control-a as the special command character. If you start picocom with option--escape bfor example, then when you type control-a it should get passed through to the screen program. You will obviously have to use control-b for your picocom commands.
– meuh
Feb 7 at 13:36
Worked flawlessly :)
– user3770060
Feb 7 at 16:29
add a comment |
1
By default, both picocom and screen use control-a as the special command character. If you start picocom with option--escape bfor example, then when you type control-a it should get passed through to the screen program. You will obviously have to use control-b for your picocom commands.
– meuh
Feb 7 at 13:36
Worked flawlessly :)
– user3770060
Feb 7 at 16:29
1
1
By default, both picocom and screen use control-a as the special command character. If you start picocom with option
--escape b for example, then when you type control-a it should get passed through to the screen program. You will obviously have to use control-b for your picocom commands.– meuh
Feb 7 at 13:36
By default, both picocom and screen use control-a as the special command character. If you start picocom with option
--escape b for example, then when you type control-a it should get passed through to the screen program. You will obviously have to use control-b for your picocom commands.– meuh
Feb 7 at 13:36
Worked flawlessly :)
– user3770060
Feb 7 at 16:29
Worked flawlessly :)
– user3770060
Feb 7 at 16:29
add a comment |
0
active
oldest
votes
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%2f499270%2fchained-serial-connections-to-linux-machines-with-picocom-and-screen-issues%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f499270%2fchained-serial-connections-to-linux-machines-with-picocom-and-screen-issues%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
1
By default, both picocom and screen use control-a as the special command character. If you start picocom with option
--escape bfor example, then when you type control-a it should get passed through to the screen program. You will obviously have to use control-b for your picocom commands.– meuh
Feb 7 at 13:36
Worked flawlessly :)
– user3770060
Feb 7 at 16:29