freebsd-stable Digest, Vol 71, Issue 7
freebsd-sta...@freebsd.org
freebsd...@freebsd.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
or, via email, send a message with subject or body 'help' to
freebsd-sta...@freebsd.org
You can reach the person managing the list at
freebsd-st...@freebsd.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-stable digest..."
Today's Topics:
1. XFree86 i830M unresolved symbols (Ethan)
2. Re: XFree86 i830M unresolved symbols (Jorn Argelo)
3. How does CAM determine the order to number drives ? (Pete French)
4. Re: How does CAM determine the order to number drives ?
(Michael Grant)
5. Re: How does CAM determine the order to number drives ?
(Dmitry Morozovsky)
6. Re: How does CAM determine the order to number drives ?
(Matthew Seaman)
7. Re: Looking for ntp/PPS setup guide (M. Warner Losh)
8. Re: Looking for ntp/PPS setup guide (Kevin Oberman)
9. Unable to use a PS/2 keyboard after a boot without it.
(Jesper Wallin)
10. Re: Unable to use a PS/2 keyboard after a boot without it.
(Josh Tolbert)
11. Re: Unable to use a PS/2 keyboard after a boot without it.
(Julian C. Dunn)
12. Re: Unable to use a PS/2 keyboard after a boot without it.
(Jesper Wallin)
13. Re: Looking for ntp/PPS setup guide (Harlan Stenn)
14. Re: Looking for ntp/PPS setup guide (Garrett Wollman)
15. RE: Unable to use a PS/2 keyboard after a boot without it.
(Darren Pilgrim)
16. Re: Looking for ntp/PPS setup guide (Eric Brown)
17. Re: Looking for ntp/PPS setup guide (Kevin Oberman)
18. wizardwaves.com mailing list memberships reminder
(mailma...@wizardwaves.com)
19. Re: Unable to use a PS/2 keyboard after a boot without it.
(Chris Whitehouse)
----------------------------------------------------------------------
Message: 1
Date: Sat, 31 Jul 2004 12:07:12 -0400
From: Ethan <eab...@ns.is-useless.org>
Subject: XFree86 i830M unresolved symbols
To: freebsd...@freebsd.org
Message-ID: <200407311607...@mx1.FreeBSD.org>
Hello,
I have installed freebsd 4.10 on my Sony vaio pcg-r505el
And I was wondering if anyone has gotten this problem before? i used
xf86cfg in ncurses mode to create my /etc/X11/XF86Config file
XFree86 Version 4.2.1 / X Window System
(protocol Version 11, revision 0, vendor release 6600)
Release Date: 3 September 2002
If the server is older than 6-12 months, or if your card is
newer than the above date, look for a newer version before
reporting problems. (See http://www.XFree86.Org/)
Build Operating System: FreeBSD 5.0-CURRENT i386 [ELF]
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/XFree86.0.log", Time: Sat Jul 31 16:03:34 2004
(==) Using config file: "/etc/X11/XF86Config"
(WW) I810: No matching Device section for instance (BusID PCI:0:2:1) found
Symbol xf86InterpretEDID from module /usr/X11R6/lib/modules/libvbe.a is unresolved!
Fatal server error:
Caught signal 11. Server aborting
ANY hely would be wonderfull!!
Thanks,
--Ethan--
------------------------------
Message: 2
Date: Sat, 31 Jul 2004 20:16:05 +0200
From: Jorn Argelo <jo...@wcborstel.nl>
Subject: Re: XFree86 i830M unresolved symbols
To: freebsd...@freebsd.org
Cc: Ethan <eab...@ns.is-useless.org>
Message-ID: <20040731201...@wcborstel.nl>
Content-Type: Text/Plain; charset="iso-8859-1"
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Saturday 31 July 2004 18:07, Ethan wrote:
> Hello,
> I have installed freebsd 4.10 on my Sony vaio pcg-r505el
> And I was wondering if anyone has gotten this problem before? i used
> xf86cfg in ncurses mode to create my /etc/X11/XF86Config file
>
> XFree86 Version 4.2.1 / X Window System
> (protocol Version 11, revision 0, vendor release 6600)
> Release Date: 3 September 2002
> If the server is older than 6-12 months, or if your card is
> newer than the above date, look for a newer version before
> reporting problems. (See http://www.XFree86.Org/)
> Build Operating System: FreeBSD 5.0-CURRENT i386 [ELF]
> Module Loader present
> Markers: (--) probed, (**) from config file, (==) default setting,
> (++) from command line, (!!) notice, (II) informational,
> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> (==) Log file: "/var/log/XFree86.0.log", Time: Sat Jul 31 16:03:34 2004
> (==) Using config file: "/etc/X11/XF86Config"
> (WW) I810: No matching Device section for instance (BusID PCI:0:2:1) found
> Symbol xf86InterpretEDID from module /usr/X11R6/lib/modules/libvbe.a is
> unresolved!
>
> Fatal server error:
> Caught signal 11. Server aborting
>
My first guess is that you're not using the right driver for your video card.
Make sure you use the proper driver and try again.
Cheers,
Jorn
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFBC+Hqs2lBCry7iusRAmaVAJ4oZuq0YzHH809cEzf8xHeseij99wCeOj8C
Ni2bzLSaduRWHREZj1ZZ+Q8=
=JPAF
-----END PGP SIGNATURE-----
------------------------------
Message: 3
Date: Sat, 31 Jul 2004 20:25:58 +0100
From: Pete French <petef...@ticketswitch.com>
Subject: How does CAM determine the order to number drives ?
To: freebsd...@freebsd.org
Message-ID: <E1BqzUU-...@dilbert.firstcallgroup.co.uk>
Hi, I have a small server which boots from an
Adaptec 2940 controller under CAM, and serves drives
off a Compaq 4200 RAID controller.
I have spent the afternoon ttrying to upgrade the
RAID controller from a 4200 to a 5300. The 5300 uses
the CISS driver rather than the IDA driver, and this
lives under CAM too. Thus my RAID drives have changed
from being idad devices to being da devices.
Unfortunately the RAID controller gets scanned first
so I now have a da0 and a da1 where I didnt before, and my
root drive has moved to da2.
I can't persuade it to boot like this - it refuses to mount
the root from da2. The simplest solution, of course, would
be to somehow force the CAM system to scan the Adaptec
controller first, so that the root device is back in da0
where it belongs. But I cant find out if there is a way
of dojing this, or indeed how the system determines the order
at all.
Any suggestions ?
-pcf.
PS: System is 4.10-RELEASE, though I suspect this is irrelevent
------------------------------
Message: 4
Date: Sat, 31 Jul 2004 16:05:54 -0400
From: Michael Grant <mg-f...@grant.org>
Subject: Re: How does CAM determine the order to number drives ?
To: Pete French <petef...@ticketswitch.com>
Cc: freebsd...@freebsd.org
Message-ID: <20040731200...@grant.org>
Content-Type: text/plain; charset=us-ascii
Yes, I know this situation all to well. In my case, I ended up
physically plugging and unplugging drives until they ended up in the
right place.
I would sure love to see a way to fix a drive to an identifier. This
has to be the one thing that has wasted more of my time than anything
else in freebsd. For example, when I had a drive die on me a couple
months back, when the machine rebooted, the dead drive still in the
system, da2 became da1 and things just did not work well.
If someone knows of a way to tie physical drives to the nodes in /dev,
please let me know. I've heard that this auto drive numbering
is a bios "feature" which is impossible to get around.
Michael Grant
On Sat, Jul 31, 2004 at 08:25:58PM +0100, Pete French wrote:
> Hi, I have a small server which boots from an
> Adaptec 2940 controller under CAM, and serves drives
> off a Compaq 4200 RAID controller.
>
> I have spent the afternoon ttrying to upgrade the
> RAID controller from a 4200 to a 5300. The 5300 uses
> the CISS driver rather than the IDA driver, and this
> lives under CAM too. Thus my RAID drives have changed
> from being idad devices to being da devices.
>
> Unfortunately the RAID controller gets scanned first
> so I now have a da0 and a da1 where I didnt before, and my
> root drive has moved to da2.
>
> I can't persuade it to boot like this - it refuses to mount
> the root from da2. The simplest solution, of course, would
> be to somehow force the CAM system to scan the Adaptec
> controller first, so that the root device is back in da0
> where it belongs. But I cant find out if there is a way
> of dojing this, or indeed how the system determines the order
> at all.
>
> Any suggestions ?
>
> -pcf.
>
> PS: System is 4.10-RELEASE, though I suspect this is irrelevent
> _______________________________________________
> freebsd...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stabl...@freebsd.org"
------------------------------
Message: 5
Date: Sun, 1 Aug 2004 00:15:30 +0400 (MSD)
From: Dmitry Morozovsky <ma...@rinet.ru>
Subject: Re: How does CAM determine the order to number drives ?
To: Michael Grant <mg-f...@grant.org>
Cc: freebsd...@freebsd.org
Message-ID: <2004080100...@woozle.rinet.ru>
Content-Type: TEXT/PLAIN; charset=US-ASCII
On Sat, 31 Jul 2004, Michael Grant wrote:
MG> Yes, I know this situation all to well. In my case, I ended up
MG> physically plugging and unplugging drives until they ended up in the
MG> right place.
MG>
MG> I would sure love to see a way to fix a drive to an identifier. This
MG> has to be the one thing that has wasted more of my time than anything
MG> else in freebsd. For example, when I had a drive die on me a couple
MG> months back, when the machine rebooted, the dead drive still in the
MG> system, da2 became da1 and things just did not work well.
MG>
MG> If someone knows of a way to tie physical drives to the nodes in /dev,
MG> please let me know. I've heard that this auto drive numbering
MG> is a bios "feature" which is impossible to get around.
root_disk_unit="2"
in /boot/loader.conf ?
MG>
MG> Michael Grant
MG>
MG> On Sat, Jul 31, 2004 at 08:25:58PM +0100, Pete French wrote:
MG> > Hi, I have a small server which boots from an
MG> > Adaptec 2940 controller under CAM, and serves drives
MG> > off a Compaq 4200 RAID controller.
MG> >
MG> > I have spent the afternoon ttrying to upgrade the
MG> > RAID controller from a 4200 to a 5300. The 5300 uses
MG> > the CISS driver rather than the IDA driver, and this
MG> > lives under CAM too. Thus my RAID drives have changed
MG> > from being idad devices to being da devices.
MG> >
MG> > Unfortunately the RAID controller gets scanned first
MG> > so I now have a da0 and a da1 where I didnt before, and my
MG> > root drive has moved to da2.
MG> >
MG> > I can't persuade it to boot like this - it refuses to mount
MG> > the root from da2. The simplest solution, of course, would
MG> > be to somehow force the CAM system to scan the Adaptec
MG> > controller first, so that the root device is back in da0
MG> > where it belongs. But I cant find out if there is a way
MG> > of dojing this, or indeed how the system determines the order
MG> > at all.
MG> >
MG> > Any suggestions ?
MG> >
MG> > -pcf.
MG> >
MG> > PS: System is 4.10-RELEASE, though I suspect this is irrelevent
MG> > _______________________________________________
MG> > freebsd...@freebsd.org mailing list
MG> > http://lists.freebsd.org/mailman/listinfo/freebsd-stable
MG> > To unsubscribe, send any mail to "freebsd-stabl...@freebsd.org"
MG> _______________________________________________
MG> freebsd...@freebsd.org mailing list
MG> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
MG> To unsubscribe, send any mail to "freebsd-stabl...@freebsd.org"
MG>
Sincerely,
D.Marck [DM5020, MCK-RIPE, DM3-RIPN]
------------------------------------------------------------------------
*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru ***
------------------------------------------------------------------------
------------------------------
Message: 6
Date: Sat, 31 Jul 2004 21:30:18 +0100
From: Matthew Seaman <m.se...@infracaninophile.co.uk>
Subject: Re: How does CAM determine the order to number drives ?
To: Michael Grant <mg-f...@grant.org>
Cc: freebsd...@freebsd.org
Message-ID:
<20040731203...@happy-idiot-talk.infracaninophile.co.uk>
Content-Type: text/plain; charset="us-ascii"
On Sat, Jul 31, 2004 at 04:05:54PM -0400, Michael Grant wrote:
> On Sat, Jul 31, 2004 at 08:25:58PM +0100, Pete French wrote:
> > I have spent the afternoon ttrying to upgrade the
> > RAID controller from a 4200 to a 5300. The 5300 uses
> > the CISS driver rather than the IDA driver, and this
> > lives under CAM too. Thus my RAID drives have changed
> > from being idad devices to being da devices.
> >
> > Unfortunately the RAID controller gets scanned first
> > so I now have a da0 and a da1 where I didnt before, and my
> > root drive has moved to da2.
> I would sure love to see a way to fix a drive to an identifier. This
> has to be the one thing that has wasted more of my time than anything
> else in freebsd. For example, when I had a drive die on me a couple
> months back, when the machine rebooted, the dead drive still in the
> system, da2 became da1 and things just did not work well.
You can wire down particular devices to a given SCSI bus, target and
LUN. Thus in your (4.x) kernel config you can say:
device scbus0 at ahc0
device da0 at scbus0 target 0 unit 0
Which means that your Adaptec controller will be treated as the first
SCSI bus, and that the drive at target zero on that bus will be called
'da0'
Under 4.x you need to create a custom kernel to do that: refer to
/usr/src/sys/i386/conf/LINT for the syntax. Under 5.x you have a very
similar syntax using sysctl 'hints' -- see /usr/src/sys/conf/NOTES,
but the above example would be something like:
hint.scbus.0.at="ahc0"
hint.da.0.at="scbus0"
hint.da.0.target="0"
hint.da.0.unit="0"
which you should be able to set from the loader.
(Nb. Specifying the unit number is optional, and the value defaults to
zero if not given explicitly).
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks
Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614 Bucks., SL7 1TH UK
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20040731/ee7d45a0/attachment-0001.bin
------------------------------
Message: 7
Date: Sat, 31 Jul 2004 14:46:27 -0600 (MDT)
From: "M. Warner Losh" <i...@bsdimp.com>
Subject: Re: Looking for ntp/PPS setup guide
To: obe...@es.net
Cc: g...@itga.com.au
Message-ID: <20040731.14462...@bsdimp.com>
Content-Type: Text/Plain; charset=us-ascii
In message: <200407300002...@ptavv.es.net>
"Kevin Oberman" <obe...@es.net> writes:
: > From: Gregory Bond <g...@itga.com.au>
: > Date: Fri, 30 Jul 2004 09:38:32 +1000
: > Sender: owner-free...@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
:
: You need to rebuild you kernel with "options PPS_SYNC". You can run PPS
: without this and the man page even says it's more accurate that way, but
: my experience is that it is much more accurate with the kernel option.
: I use CDMA clocks and they my time is stable within 10 microseconds.
I've found that w/o PPS_SYNC, we get worse results than when we have
it enabled.Of course, most of my work with this is with a pps that is
from a HP5071A atomic clock :-)
: I did find that nptd 4.2 seemed to converge better than 4.1, so I built
: the ntp port instead of the standard one. I then just installed the ntpd
: from the port over the one in /usr/sbin. 4.2 is now the standard NTP in
: version 5 and I suspect it will be MFCed to STABLE soon.
:
: 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. :-(
Warner
------------------------------
Message: 8
Date: Sat, 31 Jul 2004 16:19:08 -0700
From: "Kevin Oberman" <obe...@es.net>
Subject: Re: Looking for ntp/PPS setup guide
To: "M. Warner Losh" <i...@bsdimp.com>
Cc: g...@itga.com.au
Message-ID: <200407312319...@ptavv.es.net>
> Date: Sat, 31 Jul 2004 14:46:27 -0600 (MDT)
> From: "M. Warner Losh" <i...@bsdimp.com>
>
> In message: <200407300002...@ptavv.es.net>
> "Kevin Oberman" <obe...@es.net> writes:
> : > From: Gregory Bond <g...@itga.com.au>
> : > Date: Fri, 30 Jul 2004 09:38:32 +1000
> : > Sender: owner-free...@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
> :
> : You need to rebuild you kernel with "options PPS_SYNC". You can run PPS
> : without this and the man page even says it's more accurate that way, but
> : my experience is that it is much more accurate with the kernel option.
> : I use CDMA clocks and they my time is stable within 10 microseconds.
>
> I've found that w/o PPS_SYNC, we get worse results than when we have
> it enabled.Of course, most of my work with this is with a pps that is
> from a HP5071A atomic clock :-)
Show off!
>From what I have seen, the non-kernel PPS software handles jitter more
gracefully than the kernel version. My CDMA clock has about 4
microseconds of jitter with a spec of <10 and I suspect that your
HP5071A is a bit better in that regard. Since the PPS_SYNC stuff seem to
work very well as long as there is no significant jitter in the source,
I'll agree that it's the way to go for something as accurate as your
clock. Whether it turns out to be a win for mine depends on long-term
data that I should have Monday. (I moved my test system from PPS_SYNC to
PLL sync yesterday.
remote refid st t when poll reach delay offset jitter
==============================================================================
+TRUETIME(1) .CDMA. 0 l 6 16 377 0.000 2.699 5.184
oPPS(1) .PPS. 0 l 16 16 377 0.000 0.001 0.004
+bnl-owamp.es.ne .PPS. 1 u 7 64 377 71.908 0.051 0.034
It is critical that maxpoll and minpoll be set to 4 if the kernel
PPS_SYNC is not used. When I failed to do that, I got very poor
long-term stability.
I am also unsure how NTP calculates error estimates when PPS is used. The
values I see are not believable. Way too big. They look more like the
error estimates for TrueTime clock that PPS disciplines.
> : I did find that nptd 4.2 seemed to converge better than 4.1, so I built
> : the ntp port instead of the standard one. I then just installed the ntpd
> : from the port over the one in /usr/sbin. 4.2 is now the standard NTP in
> : version 5 and I suspect it will be MFCed to STABLE soon.
> :
> : 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. :-(
The twiki can help and I really hope to put in some good FreeBSD
specific stuff into it when time permits, but I'll agree that the
documentation can be confusing, hard to follow, and sometimes simply
wrong. But some of my own documentation is at least confusing and hard
to follow, too. ;-)
--
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: obe...@es.net Phone: +1 510 486-8634
------------------------------
Message: 9
Date: Sun, 1 Aug 2004 01:51:38 +0200 (CEST)
From: "Jesper Wallin" <jes...@hackunite.net>
Subject: Unable to use a PS/2 keyboard after a boot without it.
To: freebsd...@freebsd.org
Message-ID:
<1698.213.112.193.78...@mail.hackunite.net>
Content-Type: text/plain;charset=iso-8859-1
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
------------------------------
Message: 10
Date: Sat, 31 Jul 2004 18:55:13 -0500
From: Josh Tolbert <he...@puresimplicity.net>
Subject: Re: Unable to use a PS/2 keyboard after a boot without it.
To: Jesper Wallin <jes...@hackunite.net>
Cc: freebsd...@freebsd.org
Message-ID: <20040731235...@just.puresimplicity.net>
Content-Type: text/plain; charset=us-ascii
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
--
Josh Tolbert
he...@puresimplicity.net || http://www.puresimplicity.net/~hemi/
If your sysadmin's not being fascist, you're paying him too much.
--Sam Greenfield
------------------------------
Message: 11
Date: Sat, 31 Jul 2004 20:40:31 -0400 (EDT)
From: "Julian C. Dunn" <lists+...@aquezada.com>
Subject: Re: Unable to use a PS/2 keyboard after a boot without it.
To: freebsd...@freebsd.org
Cc: jes...@hackunite.net
Message-ID:
<Pine.LNX.4.58.04...@jupiter.acf.aquezada.com>
Content-Type: TEXT/PLAIN; charset=US-ASCII
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 <jd...@aquezada.com> * <jul...@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 ]
------------------------------
Message: 12
Date: Sun, 1 Aug 2004 02:48:17 +0200 (CEST)
From: "Jesper Wallin" <jes...@hackunite.net>
Subject: Re: Unable to use a PS/2 keyboard after a boot without it.
To: "Julian C. Dunn" <lists+...@aquezada.com>
Cc: freebsd...@freebsd.org
Message-ID:
<1966.213.112.193.78...@mail.hackunite.net>
Content-Type: text/plain;charset=iso-8859-1
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 <jd...@aquezada.com> * <jul...@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 ]
>
------------------------------
Message: 13
Date: Sat, 31 Jul 2004 20:45:06 -0400
From: Harlan Stenn <Harlan...@pfcs.com>
Subject: Re: Looking for ntp/PPS setup guide
To: "M. Warner Losh" <i...@bsdimp.com>
Cc: g...@itga.com.au
Message-ID: <21956.10...@dog.pfcs.com>
Content-Type: text/plain; charset=US-ASCII
> : 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
------------------------------
Message: 14
Date: Sat, 31 Jul 2004 21:25:04 -0400 (EDT)
From: Garrett Wollman <wol...@khavrinen.lcs.mit.edu>
Subject: Re: Looking for ntp/PPS setup guide
To: obe...@es.net
Cc: FreeBSD...@FreeBSD.org
Message-ID: <200408010125....@khavrinen.lcs.mit.edu>
In article <200407312319...@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@).
(Actually, I stole it from him.) This is using the host-triggered
timestamp mode of this device rather than PPS.
-GAWollman
------------------------------
Message: 15
Date: Sat, 31 Jul 2004 19:03:02 -0700
From: "Darren Pilgrim" <d...@bitfreak.org>
Subject: RE: Unable to use a PS/2 keyboard after a boot without it.
To: "'Jesper Wallin'" <jes...@hackunite.net>, "'Julian C. Dunn'"
<lists+...@aquezada.com>
Cc: freebsd...@freebsd.org
Message-ID: <000001c4776b$ad8495d0$142a15ac@spud>
Content-Type: text/plain; charset="us-ascii"
> 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.
------------------------------
Message: 16
Date: Sat, 31 Jul 2004 23:21:22 -0400
From: Eric Brown <bro...@locust.cns.vt.edu>
Subject: Re: Looking for ntp/PPS setup guide
To: Kevin Oberman <obe...@es.net>
Cc: g...@itga.com.au
Message-ID: <20040801032...@locust.cns.vt.edu>
Content-Type: text/plain; charset=us-ascii
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" <i...@bsdimp.com>
> >
> > In message: <200407300002...@ptavv.es.net>
> > "Kevin Oberman" <obe...@es.net> writes:
> > : > From: Gregory Bond <g...@itga.com.au>
> > : > Date: Fri, 30 Jul 2004 09:38:32 +1000
> > : > Sender: owner-free...@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
> > :
> > : You need to rebuild you kernel with "options PPS_SYNC". You can run PPS
> > : without this and the man page even says it's more accurate that way, but
> > : my experience is that it is much more accurate with the kernel option.
> > : I use CDMA clocks and they my time is stable within 10 microseconds.
> >
> > I've found that w/o PPS_SYNC, we get worse results than when we have
> > it enabled.Of course, most of my work with this is with a pps that is
> > from a HP5071A atomic clock :-)
>
> Show off!
>
> >From what I have seen, the non-kernel PPS software handles jitter more
> gracefully than the kernel version. My CDMA clock has about 4
> microseconds of jitter with a spec of <10 and I suspect that your
> HP5071A is a bit better in that regard. Since the PPS_SYNC stuff seem to
> work very well as long as there is no significant jitter in the source,
> I'll agree that it's the way to go for something as accurate as your
> clock. Whether it turns out to be a win for mine depends on long-term
> data that I should have Monday. (I moved my test system from PPS_SYNC to
> PLL sync yesterday.
> remote refid st t when poll reach delay offset jitter
> ==============================================================================
> +TRUETIME(1) .CDMA. 0 l 6 16 377 0.000 2.699 5.184
> oPPS(1) .PPS. 0 l 16 16 377 0.000 0.001 0.004
> +bnl-owamp.es.ne .PPS. 1 u 7 64 377 71.908 0.051 0.034
>
> It is critical that maxpoll and minpoll be set to 4 if the kernel
> PPS_SYNC is not used. When I failed to do that, I got very poor
> long-term stability.
>
> I am also unsure how NTP calculates error estimates when PPS is used. The
> values I see are not believable. Way too big. They look more like the
> error estimates for TrueTime clock that PPS disciplines.
>
> > : I did find that nptd 4.2 seemed to converge better than 4.1, so I built
> > : the ntp port instead of the standard one. I then just installed the ntpd
> > : from the port over the one in /usr/sbin. 4.2 is now the standard NTP in
> > : version 5 and I suspect it will be MFCed to STABLE soon.
> > :
> > : 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. :-(
>
> The twiki can help and I really hope to put in some good FreeBSD
> specific stuff into it when time permits, but I'll agree that the
> documentation can be confusing, hard to follow, and sometimes simply
> wrong. But some of my own documentation is at least confusing and hard
> to follow, too. ;-)
> --
> R. Kevin Oberman, Network Engineer
> Energy Sciences Network (ESnet)
> Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
> E-mail: obe...@es.net Phone: +1 510 486-8634
I'm running PPS from a DATUM GPS receiver with LPN ovenized quartz.
Unfortunately I can't say the same about the crystal on the motherboard.
I have the system configured so that ntpd and not the kernel disciplines
the system clock via PPS. I understood this to be the preferred
method especially after reading PHK's papers.
Typical performance reported via ntpd's logging is <10 microseconds,
however I frequently see offset wander to around 25 microseconds. I see
a strong correlation with temperature, even in an environmentally
controlled machine room. I was even able to show a correlation to
outside temperature after one very cold morning in the spring.
I would love to be able to read motherboard temperature and use it as
a secondary statistic in the ntpd control loop. Unfortunatly I've
put the ntp server project down for a while so this tweek won't happen
for some time.
--Eric Brown
------------------------------
Message: 17
Date: Sat, 31 Jul 2004 21:38:04 -0700
From: "Kevin Oberman" <obe...@es.net>
Subject: Re: Looking for ntp/PPS setup guide
To: Garrett Wollman <wol...@khavrinen.lcs.mit.edu>
Cc: FreeBSD...@FreeBSD.org
Message-ID: <200408010438...@ptavv.es.net>
> Date: Sat, 31 Jul 2004 21:25:04 -0400 (EDT)
> From: Garrett Wollman <wol...@khavrinen.lcs.mit.edu>
>
> In article <200407312319...@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@).
> (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.
The problem is that polling mode and PPS don't work properly together,
so I have found that the TrueTime format provides the best results.
ctime=off
emul=truetime
ctime=on
I am still looking at the best choice for PPS setup...PPS_SYNC (flag3 1"
or software PPL "flag3 1". Both do very well. I suspect that the absolute
time is closest with PPS_SYNC but the stability is often better with PLL
discipline. If PLL proves the more stable, I will use a fudge of time1
to correct for the offset. (In my last message bnl-owamp was running
PPS_SYNC and the system I queries was running PLL. Note the 51
microsecond offset. I don't know yet if that's real or an artifact of
network delays.
--
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: obe...@es.net Phone: +1 510 486-8634
------------------------------
Message: 18
Date: Sun, 01 Aug 2004 05:03:05 -0400
From: mailma...@wizardwaves.com
Subject: wizardwaves.com mailing list memberships reminder
To: freebsd...@freebsd.org
Message-ID: <mailman.2573.10913...@vc6.sneni.com>
Content-Type: text/plain; charset="us-ascii"
This is a reminder, sent out once a month, about your wizardwaves.com
mailing list memberships. It includes your subscription info and how
to use it to change it or unsubscribe from a list.
You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.
In addition to the URL interfaces, you can also use email to make such
changes. For more info, send a message to the '-request' address of
the list (for example, mailman...@wizardwaves.com) containing
just the word 'help' in the message body, and an email message will be
sent to you with instructions.
If you have questions, problems, comments, etc, send them to
mailma...@wizardwaves.com. Thanks!
Passwords for freebsd...@freebsd.org:
List Password // URL
---- --------
C...@wizardwaves.com osotad
http://wizardwaves.com/mailman/options/ccw_wizardwaves.com/freebsd-stable%40freebsd.org
------------------------------
Message: 19
Date: Sun, 01 Aug 2004 11:22:30 +0100
From: Chris Whitehouse <ch...@childeric.freeserve.co.uk>
Subject: Re: Unable to use a PS/2 keyboard after a boot without it.
To: freebsd...@freebsd.org
Message-ID: <84DYSPJ64Z3W6142NJ73JDVT62WQWS.410cc466@Soltek>
Content-Type: text/plain; charset="iso-8859-1"
01/08/04 00:51:38, "Jesper Wallin" <jes...@hackunite.net> 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..
If the machines are within reach of each other a kvm (keyboard video mouse) switch works well. You can get a passive switch or a fancy electronic one. The electronic
one mimics the devices plugged in and allows booting a machine which is not selected. With the passive one you must select the machine you want to boot. I have a
passive one and switch between various operating systems and between AT and PS2 type motherboards.
At one place I used to work we booted machines with a keyboard plugged in but otherwise moved the few keyboards around between running machines according to
need.
Chris
------------------------------
_______________________________________________
freebsd...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stabl...@freebsd.org"
End of freebsd-stable Digest, Vol 71, Issue 7
*********************************************