summaryrefslogtreecommitdiff
path: root/service_solahart_jakarta_selatan__082122541663/serial_console.mdwn
blob: 827fd211d839aff130f1aa73f799d9177a7ca1c7 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
[[!meta copyright="Copyright © 2010, 2014 Free Software Foundation, Inc."]]

[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
id="license" text="Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License, Version 1.2 or
any later version published by the Free Software Foundation; with no Invariant
Sections, no Front-Cover Texts, and no Back-Cover Texts.  A copy of the license
is included in the section entitled [[GNU Free Documentation
License|/fdl]]."]]"""]]

[[!tag open_issue_documentation]]


# IRC, freenode, #hurdfr, 2010-09-20

    <youpi> tu peux compiler ton gnumach pour qu'il utilise la console série, et tu
      mets le port série sur la console qemu
    <youpi> -AC_DEFINE([RCLINE], [-1], [com port for the remote console])
    <youpi> +AC_DEFINE([RCLINE], [0], [com port for the remote console])
    <youpi> dans i386/configfrag.ac
    <manuel> grumpf, peu pratique :)
    <youpi> ben après t'auras accès vraiment à ton gnumach
    <youpi> messages de noyau etc.
    <manuel> oui c'est sûr, mais j'ai aucune idée de comment je configure qemu &
      co, ça va être sportif encore
    <youpi> -serial vc
    <manuel> je lance pas moi-même le qemu, donc j'imagine qqch comme -serial
      tcp::qqch,server
    <youpi> ben t'as pas accès à la console alors ?
    <youpi> mais sinon via tcp ça devrait aller oui
    <manuel> si, via telnet
    <manuel> youpi: et après, tu fais comment pour envoyer le c-a-D toi ?
    <manuel> (question sans doute bête)
    <youpi> c'est un code différent via com1 iirc
    <manuel> mmmmmmmmmhhhhhh
    <youpi> (c'est pas bête: c-a-d c'est pas vraiment défini pour un port série)
    <manuel> tu sais où je peux le trouver ?
    <youpi> ah tiens non yena pas
    <youpi> mais bon spa dur à ajouter
    <manuel> bcp trop compliqué pour moi
    <youpi> dans i386/i386at/com.c, à la première ligne ttyinput()
    <youpi> tu compares c à ce que tu veux
    <youpi> et dans ce cas tu appelles kdb_kintr
    <youpi> (sans paramètre)
    <youpi> mais sinon ya pas vraiment besoin d'appeller explicitement le
      débuggueur hein
    <manuel> ah ?
    <youpi> dès que tu mets debug_all_traps à 1 dans traps.c, il sera invoqué lors
      du segv
    <manuel> ok
    <youpi> pour xen j'ai mis £ comme raccourcis
    <manuel> ça me paraît plus simple dans ce cas
    <youpi> clin d'œil à la société anglaise :)


# IRC, freenode, #hurd, 2014-02-20

    <gg0> 04:06:45< gg0> ok a configuration that works w/o patching anything is
      9600 7S1 [ 7bits - parity Space - 1 stopbit ]
    <gg0> 04:07:57< gg0> it displays correctly gnumach, ext2fs and following
      outputs
    <gg0> 04:28:05< gg0> youpi: instead if you want a patch, this one makes
      gnumach default to 8N1. someone should still implement serial line
      settings for ext2fs though
    <gg0> seems something broke it later
    <gg0> or it never worked on real hardware
    <braunr> we definitely want it to work with 8N1
    <gg0> never had problems with _virtual_ serial consoles
    <gg0> never = during last 2 years = since
      http://git.savannah.gnu.org/gitweb/?p=hurd/gnumach.git;a=commitdiff;h=2a603e88f86bee88e013c2451eacf076fbcaed81
    <gg0> but i don't think i was on real hardware at that time


## IRC, freenode, #hurd, 2014-02-21

    <gg0> yeah, i have one rebuilt trying to fix serial console (already give
      up)
    <teythoon> what were you trying to fix ?
    <gg0> i didn't fix anything but it's been useful somehow :)
    <gg0> this one http://paste.debian.net/plain/83292
    <gg0> initial messages from mach/hurd outputs like there was no line feed
    <gg0> each line overwrites previous one
    <gg0> then ext2fs outputs garbage
    <gg0> then openrc start outputting fine
    <gg0> minicom 9600 8N1
    <teythoon> this is from a real machine ?
    <gg0> yep real machine
    <teythoon> nice :)
    <gg0> i fixed last line, last garbage, by switching c: from 38400 to 9600
      in inittab
    <teythoon> i've a vt510 terminal connected to my hurd box, and i started to
      make the serial setting in gnumach more configurable
    <gg0> and disabling T0
    <teythoon> didn't finish it though
    <gg0> physical vt510 connected to virtual hurd box?
    <teythoon> no, it's a real box as well
    <gg0> good. and does it behave as described/pasted above?
    <teythoon> currently i do not put the mach console on the serial line
    <teythoon> b/c it has a fixed baud rate of 9600
    <teythoon> and both grub and the getty are configured at a higher speed
    <teythoon> hence my desire to improve gnumachs serial port setup
    <gg0> i don't care much about speed. such no-line-feed behavior is quite
      annoying though
    <gg0> i thought it was related to CRMOD which afaiu should translate cr to
      cr-lf, but i was surely missing something
    <gg0> (annoying till one does ^A-A to make minicom add line feeds itself)