headers
Kevin Oberman | 1 Aug 2004 01:19

Re: Looking for ntp/PPS setup guide

> Date: Sat, 31 Jul 2004 14:46:27 -0600 (MDT)
> From: "M. Warner Losh" <imp <at> bsdimp.com>
> 
> In message: <20040730000205.E834A5D09 <at> ptavv.es.net>
>             "Kevin Oberman" <oberman <at> es.net> writes:
> : > From: Gregory Bond <gnb <at> itga.com.au>
> : > Date: Fri, 30 Jul 2004 09:38:32 +1000
> : > Sender: owner-freebsd-stable <at> freebsd.org
> : > 
> : > 
> : > We've got a GPS receiver to make an NTP server, and it has PPS output.
> : > Is there a guide to how to set up PPS on recent (4.10-ish) FreeBSD
> : > boxes?  Or I can put it on a 5.x box if that is better. I've had a
> : > look in all the obvious places but the only references I can find are
> : > to old (load a line discipline or patch a kernel) solutions.
> : 
> : I'd suggest the documentation at www.ntp.org, but it has a few errors
> : and lacks a bit of FreeBSD specific bits.
> : 
> : First off, you will need to rebuild ntpd with the appropriate reference
> : clocks, pps and whatever type of GPS you have. The software is in
> : /usr/src/contrib/ntp/ntpd. You can look at the list of clock drivers and
> : pick the one you need. If you look at the driver source, you will see
> : that REFCLOCK and a driver specific variable need to be defined.
> : 
> : Go to /usr/src/usr.sbin/ntp/ntpd and rebuild ntpd with the clock driver:
> : make clean
> : make -DREFCLOCK -DCLOCK_yourclock
> : make install
> :
(Continue reading)

Permalink | Reply | 1 comment |
headers
Jesper Wallin | 1 Aug 2004 01:51

Unable to use a PS/2 keyboard after a boot without it.

Hello..

I run a few FreeBSD machines at home (both 4.10 and 5.2.1) and if I boot them up
*without* having the PS/2 keyboard connected, I can't connect it later on.. My servers
usually runs without screen and keyboard, power and network cable is the only thing
needed. :) But when I need to change something (like, take them down to
single-user-mode), then I need to reconnect the keyboard, reboot the machine and THEN I
can use the keyboard..

I use to run Linux before and it seems like Linux handle that pretty well, therefore I
doubt it's a BIOS settings or so.. Is it possible to make FreeBSD work the same way to
always assume there's keyboard connected so I can connect it whenever I need to without
(re)booting with it connected?

Regards,
Jesper Wallin
_______________________________________________
freebsd-stable <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"
Permalink | Reply | 7 comments |
headers
Josh Tolbert | 1 Aug 2004 01:55

Re: Unable to use a PS/2 keyboard after a boot without it.

On Sun, Aug 01, 2004 at 01:51:38AM +0200, Jesper Wallin wrote:
> Hello..
> 
> I run a few FreeBSD machines at home (both 4.10 and 5.2.1) and if I boot them up
> *without* having the PS/2 keyboard connected, I can't connect it later on.. My servers
> usually runs without screen and keyboard, power and network cable is the only thing
> needed. :) But when I need to change something (like, take them down to
> single-user-mode), then I need to reconnect the keyboard, reboot the machine and THEN I
> can use the keyboard..
> 
> I use to run Linux before and it seems like Linux handle that pretty well, therefore I
> doubt it's a BIOS settings or so.. Is it possible to make FreeBSD work the same way to
> always assume there's keyboard connected so I can connect it whenever I need to without
> (re)booting with it connected?
> 
> 
> Regards,
> Jesper Wallin

Understandable, considering PS/2 is not technically hot-swappable...Be careful
doing that, cause I've seen machines stop responding to PS/2 input after a
"bad" swap...I don't know if the on-board keyboard controller gets fried or
what, but swapping PS/2 peripherals is just something I don't do any more.

As far as why FreeBSD doesn't recognize PS/2 hardware after it's hot-plugged,
I can't help you there. You might consider looking at the flags for the
drivers that work with the keyboard.

Josh
--

--
(Continue reading)

Permalink | Reply | 3 comments |
headers
Julian C. Dunn | 1 Aug 2004 02:40
Favicon

Re: Unable to use a PS/2 keyboard after a boot without it.

On Sat, 31 Jul 2004, Josh Tolbert wrote:

> As far as why FreeBSD doesn't recognize PS/2 hardware after it's hot-plugged,
> I can't help you there. You might consider looking at the flags for the
> drivers that work with the keyboard.

Delete "flags 0x01" from the line in your kernel config that references 
atkbd. According to LINT, "0x01" forces detection of the keyboard, so if 
you booted without it plugged in, the atkbd driver will never be loaded as 
a keyboard was not detected.

- Julian

[    Julian C. Dunn <jdunn <at> aquezada.com> * <julian <at> dreaming.org>      ]
[   WWW: www.aquezada.com/staff/julian/ * www.dreaming.org/~julian/   ]
[ PGP: 0xFDC205B9 - 91B3 7A9D 683C 7C16 715F 442C 6065 D533 FDC2 05B9 ]
[   "half a love is better than no love at all" - nerissa nields      ]
_______________________________________________
freebsd-stable <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"
Permalink | Reply | 2 comments |
headers
Jesper Wallin | 1 Aug 2004 02:48

Re: Unable to use a PS/2 keyboard after a boot without it.

Heya..

First of all, thanks for your reply.. but yet, I don't have any "flags 0x01" on the
atkbd line..

-snip-
# atkbdc0 controls both the keyboard and the PS/2 mouse
device          atkbdc          # AT keyboard controller
device          atkbd           # AT keyboard
#device         psm             # PS/2 mouse
-snip-

Regards,
Jesper Wallin

> On Sat, 31 Jul 2004, Josh Tolbert wrote:
>
>> As far as why FreeBSD doesn't recognize PS/2 hardware after it's hot-plugged,
>> I can't help you there. You might consider looking at the flags for the
>> drivers that work with the keyboard.
>
> Delete "flags 0x01" from the line in your kernel config that references
> atkbd. According to LINT, "0x01" forces detection of the keyboard, so if
> you booted without it plugged in, the atkbd driver will never be loaded as
> a keyboard was not detected.
>
> - Julian
>
> [    Julian C. Dunn <jdunn <at> aquezada.com> * <julian <at> dreaming.org>      ]
> [   WWW: www.aquezada.com/staff/julian/ * www.dreaming.org/~julian/   ]
(Continue reading)

Permalink | Reply | 1 comment |
headers
Harlan Stenn | 1 Aug 2004 02:45
X-Face

Re: Looking for ntp/PPS setup guide

> : Read the manual pages for pps and your GPS clock driver for how to set
> : up ntp.conf for that clock. You will need to set up kernel PPS there.
> 
> This can be the hardest part.  The documentation is a little less than
> stellar. :-(

Which is one reason why there is twiki.ntp.org .

H
_______________________________________________
freebsd-stable <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"
Permalink | Reply | 0 comments |
headers
Garrett Wollman | 1 Aug 2004 03:25
Picon

Re: Looking for ntp/PPS setup guide

In article <20040731231908.18F485D08 <at> ptavv.es.net> you write:

>From what I have seen, the non-kernel PPS software handles jitter more
>gracefully than the kernel version.

Which CDMA receiver do you have?  I'm using one from EndRun
Technologies which emulates a Trimble Palisade and it seems to perform
fairly well:

     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
*GPS_PALISADE(0) .CDMA.           0 l    1   32  377    0.000   -0.016   0.008
+NAVOBS1.MIT.EDU .PSC.            1 u   37   64  377    0.836    0.027   0.025
xtime-b.nist.gov .ACTS.           1 u   49   64  377   15.477   -6.898   9.374
+ntp2.usno.navy. .USNO.           1 u   10   64  337   40.016   -2.378  83.946
-gps.freebsd.dk  .GPS.            1 u   51   64  377  115.848    4.315   1.408

This receiver was recommended to me by Dave Andersen (dga <at> ).
(Actually, I stole it from him.)  This is using the host-triggered
timestamp mode of this device rather than PPS.

-GAWollman

_______________________________________________
freebsd-stable <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"
Permalink | Reply | 4 comments |
headers
Darren Pilgrim | 1 Aug 2004 04:03

RE: Unable to use a PS/2 keyboard after a boot without it.

> From: Jesper Wallin
> 
> Heya..
> 
> First of all, thanks for your reply.. but yet, I don't have 
> any "flags 0x01" on the atkbd line..

Which machine did you look at?

On the 4.10 machine, the "flags 0x01" will be on the device atkbd line in
your kernel config.  On the 5.2.1 machine, it will be in /boot/device.hints
as hint.atkbd.0.flags="0x1".

Check with your mainboard/BIOS manufacturer.  Some mainboards/BIOSes will
"turn off" the PS/2 ports if nothing is detected at boot.

_______________________________________________
freebsd-stable <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"
Permalink | Reply | 0 comments |
headers
Eric Brown | 1 Aug 2004 05:21
Picon

Re: Looking for ntp/PPS setup guide

On Sat, Jul 31, 2004 at 04:19:08PM -0700, Kevin Oberman wrote:
> > Date: Sat, 31 Jul 2004 14:46:27 -0600 (MDT)
> > From: "M. Warner Losh" <imp <at> bsdimp.com>
> > 
> > In message: <20040730000205.E834A5D09 <at> ptavv.es.net>
> >             "Kevin Oberman" <oberman <at> es.net> writes:
> > : > From: Gregory Bond <gnb <at> itga.com.au>
> > : > Date: Fri, 30 Jul 2004 09:38:32 +1000
> > : > Sender: owner-freebsd-stable <at> freebsd.org
> > : > 
> > : > 
> > : > We've got a GPS receiver to make an NTP server, and it has PPS output.
> > : > Is there a guide to how to set up PPS on recent (4.10-ish) FreeBSD
> > : > boxes?  Or I can put it on a 5.x box if that is better. I've had a
> > : > look in all the obvious places but the only references I can find are
> > : > to old (load a line discipline or patch a kernel) solutions.
> > : 
> > : I'd suggest the documentation at www.ntp.org, but it has a few errors
> > : and lacks a bit of FreeBSD specific bits.
> > : 
> > : First off, you will need to rebuild ntpd with the appropriate reference
> > : clocks, pps and whatever type of GPS you have. The software is in
> > : /usr/src/contrib/ntp/ntpd. You can look at the list of clock drivers and
> > : pick the one you need. If you look at the driver source, you will see
> > : that REFCLOCK and a driver specific variable need to be defined.
> > : 
> > : Go to /usr/src/usr.sbin/ntp/ntpd and rebuild ntpd with the clock driver:
> > : make clean
> > : make -DREFCLOCK -DCLOCK_yourclock
> > : make install
(Continue reading)

Permalink | Reply | 0 comments |
headers
Kevin Oberman | 1 Aug 2004 06:38

Re: Looking for ntp/PPS setup guide

> Date: Sat, 31 Jul 2004 21:25:04 -0400 (EDT)
> From: Garrett Wollman <wollman <at> khavrinen.lcs.mit.edu>
> 
> In article <20040731231908.18F485D08 <at> ptavv.es.net> you write:
> 
> >From what I have seen, the non-kernel PPS software handles jitter more
> >gracefully than the kernel version.
> 
> Which CDMA receiver do you have?  I'm using one from EndRun
> Technologies which emulates a Trimble Palisade and it seems to perform
> fairly well:
> 
>      remote           refid      st t when poll reach   delay   offset  jitter
> ==============================================================================
> *GPS_PALISADE(0) .CDMA.           0 l    1   32  377    0.000   -0.016   0.008
> +NAVOBS1.MIT.EDU .PSC.            1 u   37   64  377    0.836    0.027   0.025
> xtime-b.nist.gov .ACTS.           1 u   49   64  377   15.477   -6.898   9.374
> +ntp2.usno.navy. .USNO.           1 u   10   64  337   40.016   -2.378  83.946
> -gps.freebsd.dk  .GPS.            1 u   51   64  377  115.848    4.315   1.408
> 
> This receiver was recommended to me by Dave Andersen (dga <at> ).
> (Actually, I stole it from him.)  This is using the host-triggered
> timestamp mode of this device rather than PPS.

I am running the EndRun Proesis Ct. It can emulate many different clocks
and, if you don't have PPS, the Palisade is probably the best
choice. Unlike others which send out the time in ASCII every second, the
Palisade sends out the time in binary when polled. But this is not as
accurate as PPS which the unit also provides.
(Continue reading)

Permalink | Reply | 3 comments |

Gmane