Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 04 Feb 2009 18:01:46 +0100
From:      Martin Schweizer <office@pc-service.ch>
To:        Jerry McAllister <jerrymc@msu.edu>
Cc:        Tim Judd <tajudd@gmail.com>, freebsd-questions@freebsd.org
Subject:   Re: Using Serial Port Other Than sio0 for the Console
Message-ID:  <4989C9FA.5090803@pc-service.ch>
In-Reply-To: <20090204164310.GD31264@gizmo.acns.msu.edu>
References:  <20090130172843.GB89911@saturn.pcs.ms> <ade45ae90901311109x3cc9454j58027bfd6571b4cd@mail.gmail.com> <20090201160311.GD54916@saturn.pcs.ms> <20090204074546.GA88685@saturn.pcs.ms> <20090204164310.GD31264@gizmo.acns.msu.edu>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
Hello Jerry


Jerry McAllister schrieb:
> On Wed, Feb 04, 2009 at 08:45:46AM +0100, Martin Schweizer wrote:
> 
>> Hello Tim 
>>
>> I did what in the handbook under article 26.6.5.2. is described but not shure 
>> how I can write a new boot block to the disk. Here is what I think is correct:
>>
>> Output from df and bsdlabel mfid0s1:
>> # df -h
>> Filesystem       Size    Used   Avail Capacity  Mounted on
>> /dev/mfid0s1a    989M    378M    532M    42%    /
>> devfs            1.0K    1.0K      0B   100%    /dev
>> /dev/mfid0s1d    989M     16K    910M     0%    /tmp
>> /dev/mfid0s1f    388G    2.6G    354G     1%    /usr
>> /dev/mfid0s1e    182G     43M    167G     0%    /var
>>
>> # /dev/mfid0s1:
>> 8 partitions:
>> #        size   offset    fstype   [fsize bsize bps/cpg]
>>   a:  2097152        0    4.2BSD     2048 16384 28528 
>>   b:  8388608  2097152      swap                    
>>   c: 1246081662        0    unused        0     0         # "raw" part, don't 
>> edit
>>   d:  2097152 10485760    4.2BSD     2048 16384 28528 
>>   e: 394264576 12582912    4.2BSD     2048 16384 28528 
>>   f: 839234174 406847488    4.2BSD     2048 16384 28528 
>>
>> My opinion is:
>> bsdlabel -B mfid0s1
> 
> What has this all got to do with the Subject?
>   Subject: Re: Using Serial Port Other Than sio0 for the Console
> 
> Please don't hijack threads.
> Start a new one if you have something to ask.

In the article 26.6.5.2. in the handbook you will find the answer. If 
you want to use another sio port (COM2 im my case) for serial 
communications you need to write the boot blocks new. I do not use 
bsdlabel often so I want to cross check that I'm on the right way.

Regards,


> 
>> Is that correct?
>>
>> Regards,
>>  
>>
>> Am Sun, Feb 01, 2009 at 05:03:12PM +0100 Martin Schweizer schrieb:
>>> Probably I find the problem. I did not read care enough the article 26.6.5.2. 
>>> I will try it asap (in the next few days). I will keep you updated.
>>>
>>> Am Sat, Jan 31, 2009 at 12:09:28PM -0700 Tim Judd schrieb:
>>>> On Fri, Jan 30, 2009 at 10:28 AM, Martin Schweizer <lists_freebsd@bluewin.ch
>>>>> wrote:
>>>>>
>>>>> I want to use sio1 for console access. I read chapter 26.6 in the handbook
>>>>> and did the following:
>>>>>
>>>>> /boot.config:
>>>>> -P
>>>>>
>>>>> /boot/device.hints:
>>>>> [snip]
>>>>> hint.sio.0.at="isa"
>>>>> hint.sio.0.port="0x3F8"
>>>>> ### hint.sio.0.flags="0x10"
>>>>> hint.sio.0.irq="4"
>>>>> hint.sio.1.at="isa"
>>>>> hint.sio.1.port="0x2F8"
>>>>> hint.sio.1.flags="0x10"
>>>>> hint.sio.1.irq="3"
>>>>> [snip]
>>>>>
>>>>> My custom kernel:
>>>>> [snip]
>>>>> device sio
>>>>> [snip]
>>>>>
>>>>> /var/run/dmesg.boot:
>>>>> [snip]
>>>>> sio0: configured irq 4 not in bitmap of probed irqs 0
>>>>> sio0: port may not be enabled
>>>>> sio0: configured irq 4 not in bitmap of probed irqs 0
>>>>> sio0: port may not be enabled
>>>>> sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 on acpi0
>>>>> sio0: type 16550A
>>>>> sio0: [FILTER]
>>>>> sio1: configured irq 3 not in bitmap of probed irqs 0
>>>>> sio1: port may not be enabled
>>>>> sio1: configured irq 3 not in bitmap of probed irqs 0
>>>>> sio1: port may not be enabled
>>>>> sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 flags 0x10 on
>>>>> acpi0
>>>>> sio1: type 16550A, console
>>>>> sio1: [FILTER]
>>>>> [snip]
>>>>>
>>>>> /etc/ttys:
>>>>> [snip]
>>>>> ttyd0   "/usr/libexec/getty std.9600"   vt100   on  secure
>>>>> ttyd1   "/usr/libexec/getty std.9600"   vt100   on  secure
>>>>> ttyd2   "/usr/libexec/getty std.9600"   vt100   on  secure
>>>>> ttyd3   "/usr/libexec/getty std.9600"   vt100   on  secure
>>>>> [snip]
>>>>>
>>>>> The baud rate etc. are correct as well (the standard settings).
>>>>>
>>>>> The problem is I get no connection. I'm sure that my terminal works correct
>>>>> because I can connect other FreeBSD sever over the serial cable but not the
>>>>> above.
>>>>> Any ideas?
>>>>>
>>>>> Kind regards,
>>>>>
>>>>> --
>>>>>
>>>>> Martin Schweizer
>>>>> <office@pc-service.ch>
>>>>>
>>>>> PC-Service M. Schweizer GmbH; Bannholzstrasse 6; CH-8608 Bubikon
>>>>> Tel. +41 55 243 30 00; Fax: +41 55 243 33 22; http://www.pc-service.ch;
>>>>> public key : http://www.pc-service.ch/pgp/public_key.asc;
>>>>> fingerprint: EC21 CA4D 5C78 BC2D 73B7  10F9 C1AE 1691 D30F D239;
>>>>>
>>>> Surprised nobody's really responded.
>>>>
>>>> Enabling serial logins on ttyd1 (COM2 in Microsoft terms) is on -- it's
>>>> defined in your ttys.  The guaranteed "enabling" is to restart, but I've
>>>> heard that sigHUP init will reread ttys and enable logins (but I hadn't got
>>>> that to work yet).
>>>>
>>>> Enabling serial as your console output (in terms of the boot process and
>>>> everything) should be, if available, enabled in /boot/loader.conf
>>>>
>>>> There doesn't seem to be a setting to enable COM2 as your console device,
>>>> the only options (by reading through /boot/defaults/loader.conf) is to
>>>> enable comconsole, which runs over COM1
>>>>
>>>> You would likely have to hack the bootloader files in source and reinstall
>>>> to get that kind of functionality.
>>>>
>>>>
>>>> Does this help?  let me know if you want more help.  I like enabling serial
>>>> console for the fact that you can get into out-of-bounds management this way
>>>> easily.
>>>>
>>>> --Tim
>>>> _______________________________________________
>>>> freebsd-questions@freebsd.org mailing list
>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>>>> To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
>>> -- 
>>>
>>> Martin Schweizer
>>> <office@pc-service.ch>
>>>
>>> PC-Service M. Schweizer GmbH; Bannholzstrasse 6; CH-8608 Bubikon
>>> Tel. +41 55 243 30 00; Fax: +41 55 243 33 22; http://www.pc-service.ch;
>>> public key : http://www.pc-service.ch/pgp/public_key.asc; 
>>> fingerprint: EC21 CA4D 5C78 BC2D 73B7  10F9 C1AE 1691 D30F D239;
>>>
>>> _______________________________________________
>>> freebsd-questions@freebsd.org mailing list
>>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>>> To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
>> -- 
>>
>> Martin Schweizer
>> <office@pc-service.ch>
>>
>> PC-Service M. Schweizer GmbH; Bannholzstrasse 6; CH-8608 Bubikon
>> Tel. +41 55 243 30 00; Fax: +41 55 243 33 22; http://www.pc-service.ch;
>> public key : http://www.pc-service.ch/pgp/public_key.asc; 
>> fingerprint: EC21 CA4D 5C78 BC2D 73B7  10F9 C1AE 1691 D30F D239;
>>
>> _______________________________________________
>> freebsd-questions@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>> To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"

-- 
Martin Schweizer

PC-Service M. Schweizer GmbH; Bannholzstrasse 6; Postfach 132;
CH-8608 Bubikon; Tel. +41 55 243 30 00; Fax: +41 55 243 33 22;
http://www.pc-service.ch



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?4989C9FA.5090803>