Re: NTP nanokernel support (experimental)
On Sat, Mar 06, 1999 at 08:00:53PM +0100, Ollivier Robert wrote:
The two outputs I sent were with 4.0.90f. When I run 4.0.92c, ntpd is not
able to get any accurate data from the device whereas 4.0.90f does.
I get lots of these in /var/log/messages and it doesn't sync at all.
-=-=-
Mar 6 14:02:25 tara ntpd[7600]: parse: convert_rawdcf: INCOMPLETE DATA -
time code only has 3 bits
Mar 6 14:02:29 tara ntpd[7600]: parse: convert_rawdcf: INCOMPLETE DATA -
time code only has 2 bits
It's typical from bad parity setting on your serial port.
Try a stty on that port; I bet it will show that PARENB is set.
Unset it and things should go back to normal.
Maybe it is a problem with 4.0.92c...
Yes, it's a problem with most of the ntpd 4.0.9x series. There's
absolutely no reason why you should enable PARENB for a raw DCF77
driver; yet that's what ntpd's configure does, at least under
FreeBSD.
I sent a bug report to the ntpd team a while ago but haven't heard
from them.
--
Pierre Beyssacp...@fasterix.frmug.org p...@fasterix.freenix.org
{Free,Net,Open}BSD, Linux : il y a moins bien, mais c'est plus cher
Free domains: http://www.eu.org/ or mail dns-mana...@eu.org
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: UPDATE2: ATA/ATAPI driver new version available.
On Sat, 6 Mar 1999, Sren Schmidt wrote: It seems Steve Price wrote: [debug output omitted] I think I know what is failing now, I just have to find a fix for it.. -S?ren This seems to be happening to me too on my laptop. The kernel hangs in ata_command() waiting for an interrupt (ATA_WAIT_INTR) when it is trying to probe the slave device on my second ide controller. Specifically, it is the first ata_command() in ata_get_param() which hangs. The laptop in question has a single IDE driver attached to the first controller as a master and a DVD driver attached to the second as a master. The older working probe looked like this: ad0: IBM-DYLA-28100/YSAOA22H ATA-3 disk at ata0 as master ad0: 7815MB (16007040 sectors), 15880 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue acd0: TOSHIBA DVD-ROM SD-C2102/1329 CDROM drive at ata1 as master acd0: drive speed 3445KB/sec, 128KB cache acd0: supported read types: CD-R, CD-RW, CD-DA acd0: Audio: play, 16 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked The probe which hangs looks the same but stops at this point. -- Doug Rabson Mail: d...@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: NTP nanokernel support (experimental)
According to Pierre Beyssac: absolutely no reason why you should enable PARENB for a raw DCF77 driver; yet that's what ntpd's configure does, at least under FreeBSD. Yes, it seems to be that again. I thought I had fixed it in config.cache but it seems not. It is working now. remote refid st t when poll reach delay offset jitter == 127.127.1.0 127.127.1.0 10 - 12 6410.0000.000 0.000 *127.127.8.0 .DCFa. 0 - 11 6430.000 32.068 0.514 224.0.1.1 0.0.0.0 16 u- 6400.0000.000 4000.00 A few more peerstats for you Poul-Henning, now with both your diffs and 4.0.92c. 51244 65536.259 127.127.8.0 96c4 0.032788333 0.0 0.0 0.002593271 51244 65537.261 127.127.8.0 96c4 0.032699250 0.0 0.0 0.002148683 51244 65538.259 127.127.8.0 96c4 0.032702500 0.0 0.0 0.001667484 51244 65539.253 127.127.8.0 96c4 0.032702500 0.0 0.0 0.000871368 51244 65540.259 127.127.8.0 96c4 0.032678083 0.0 0.0 0.000525512 51244 65541.259 127.127.8.0 96c4 0.032167917 0.0 0.0 0.000432877 51244 65542.639 127.127.8.0 96c4 0.032068250 0.0 0.0 0.000513906 The following diff should fix the ignpar/parenb problem. --- configure.in.oldSun Mar 7 19:11:41 1999 +++ configure.inSun Mar 7 19:11:55 1999 @@ -1055,6 +1055,9 @@ i?86-*-linux*) ans=yes ;; + *-*-freebsd*) +ans=yes +;; mips-sgi-irix*) ans=yes ;; -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #70: Sat Feb 27 09:43:08 CET 1999 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: UPDATE2: ATA/ATAPI driver new version available.
It seems Doug Rabson wrote: This seems to be happening to me too on my laptop. The kernel hangs in ata_command() waiting for an interrupt (ATA_WAIT_INTR) when it is trying to probe the slave device on my second ide controller. Specifically, it is the first ata_command() in ata_get_param() which hangs. Are you sure it tries to probe the slave ?? Could please try to have it printout scp-devices in ata_probe ?? -Søren To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: NTP nanokernel support (experimental)
Ollivier, For performance monitoring with the nanokernel and PPS source, see the peerstats and grope for 127.0.0.1 with grep. When the daemon has handed off PPS to the kernel, the radio timecode is used only to mean the transmitter is still on the air. Dave To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: NTP nanokernel support (experimental)
In message 199903071351.aa20...@huey.udel.edu, Dave Mills writes: Ollivier, For performance monitoring with the nanokernel and PPS source, see the peerstats and grope for 127.0.0.1 with grep. When the daemon has handed off PPS to the kernel, the radio timecode is used only to mean the transmitter is still on the air. I don't think Ollivier is doing PPP/hardpps() yet, at least I have not given him the semi-magic code needed for it :-) I wouldn't recommend trying it either, he is bound to have a 1 msec jitter on the DCF77 waves at his place, and that is a lousy diet for hardpps(). Poul-Henning PS: I have updated my rover page, you can see the performance of my machine with the nanokernel-PLL patch, 4.92c and a UT+ Oncore on http://phk.freebsd.dk/rover.html (This isn't using hardpps() either!) -- Poul-Henning Kamp FreeBSD coreteam member p...@freebsd.org Real hackers run -current on their laptop. FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: UPDATE2: ATA/ATAPI driver new version available.
On Sun, 7 Mar 1999, Sren Schmidt wrote: It seems Doug Rabson wrote: This seems to be happening to me too on my laptop. The kernel hangs in ata_command() waiting for an interrupt (ATA_WAIT_INTR) when it is trying to probe the slave device on my second ide controller. Specifically, it is the first ata_command() in ata_get_param() which hangs. Are you sure it tries to probe the slave ?? Could please try to have it printout scp-devices in ata_probe ?? I'll do that later on today and report back. -- Doug Rabson Mail: d...@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: UPDATE2: ATA/ATAPI driver new version available.
On Sun, 7 Mar 1999, Sren Schmidt wrote: It seems Doug Rabson wrote: This seems to be happening to me too on my laptop. The kernel hangs in ata_command() waiting for an interrupt (ATA_WAIT_INTR) when it is trying to probe the slave device on my second ide controller. Specifically, it is the first ata_command() in ata_get_param() which hangs. Are you sure it tries to probe the slave ?? Could please try to have it printout scp-devices in ata_probe ?? Here is a log of an attempted boot with ATA_DEBUG defined. It looks like ata_probe() detected a slave where there isn't one. ata-pci0: Intel PIIX4 IDE controller rev 0x01 on pci0.5.1 ata: type=71118086 class=01018001 cmd=0285 ata0: iobase=0x01f0 altiobase=0x03f6 ata0: mask=03 status0=50 status1=00 ata0: mask=03 status0=50 status1=00 ata0: devices = 0x1 ata0 at 0x01f0 irq 14 on ata-pci0 ata1: iobase=0x0170 altiobase=0x0376 ata1: mask=03 status0=50 status1=00 ata1: mask=03 status0=00 status1=00 ata1: devices = 0xc ata1 at 0x0170 irq 15 on ata-pci0 ... ataintr: entered unit=0 ataintr: entered unit=0 ad0: IBM-DYLA-28100/YSAOA22H ATA-3 disk at ata0 as master ad0: 7815MB (16007040 sectors), 15880 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue ataintr: entered unit=1 ata_start: entered ataintr: entered unit=1 ataintr: entered unit=1 ata_start: entered acd0: TOSHIBA DVD-ROM SD-C2102/1329 CDROM drive at ata1 as master acd0: drive speed 3445KB/sec, 128KB cache acd0: supported read types: CD-R, CD-RW, CD-DA acd0: Audio: play, 16 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked -- Doug Rabson Mail: d...@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: NTP nanokernel support (experimental)
On Sun, Mar 07, 1999 at 08:09:50PM +0100, Poul-Henning Kamp wrote:
I don't think Ollivier is doing PPP/hardpps() yet, at least I have not
given him the semi-magic code needed for it :-)
I wouldn't recommend trying it either, he is bound to have a 1
msec jitter on the DCF77 waves at his place, and that is a lousy
diet for hardpps().
I agree; jitter with a low-cost DCF77 receiver is even more than
that (5 to 10 ms). I tend to believe it's partly due to how the AM
signal is demodulated and not that much from the location (Paris
is not that far from Frankfurt after all). Maybe a lower jitter
could be obtained by averaging 10 or 100 samples, I suppose that's
how high-quality receivers work. This might be done in the ntpd
driver.
--
Pierre Beyssacp...@fasterix.frmug.org p...@fasterix.freenix.org
{Free,Net,Open}BSD, Linux : il y a moins bien, mais c'est plus cher
Free domains: http://www.eu.org/ or mail dns-mana...@eu.org
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: UPDATE2: ATA/ATAPI driver new version available.
It seems Doug Rabson wrote: Are you sure it tries to probe the slave ?? Could please try to have it printout scp-devices in ata_probe ?? Here is a log of an attempted boot with ATA_DEBUG defined. It looks like ata_probe() detected a slave where there isn't one. ata1: devices = 0xc Hmm, if it says it found a slave ATAPI device, it found the ATAPI signature in the regs addressed as a slave... Sounds to me like icky hardware, sigh... I'll see what I can do... -Søren To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: UPDATE2: ATA/ATAPI driver new version available.
On Sun, 7 Mar 1999, Doug Rabson wrote: # Are you sure it tries to probe the slave ?? # Could please try to have it printout scp-devices in ata_probe ?? # # Here is a log of an attempted boot with ATA_DEBUG defined. It looks like # ata_probe() detected a slave where there isn't one. # # ata-pci0: Intel PIIX4 IDE controller rev 0x01 on pci0.5.1 # ata: type=71118086 class=01018001 cmd=0285 [...] # ata0: devices = 0x1 [...] # ata1: devices = 0xc [snip] For what it's worth I get the same two lines: ata0: devices = 0x1 ata1: devices = 0xc So it found the master (the HD) on the first controller, but it appears to find both a master and a slave on the second controller. The problem is that the DVD-ROM doesn't appear to repsond correctly to either of the attempts to determine which one it wants to be. Just for grins I changed the ata_probe to ignore all but the first controller and it is back to the ufs_dirbad panic. :( To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
zpx in latest snap (4.0-19990307-SNAP)
I get the following message from the zp0 driver on boot: zp0 XXX: driver didn't set ifq_maxlen lo0 XXX: driver didn't set ifq_maxlen I assume they should be setting it? :-) Robert N Watson rob...@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: 03 01 DD 8E 15 67 48 73 25 6D 10 FC EC 68 C1 1C Carnegie Mellon Universityhttp://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ Safeport Network Services http://www.safeport.com/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
UPDATE3: ATA/ATAPI driver new version available.
Third update to the new ATA/ATAPI driver: ZIP drives should now be working, I'm not sure about LS120 drives, reports on those most welcome! Fixed problems: Hang on probe on fantom devices. The probe now use a timeout to avoid hangs if no interrupt is received. There has also been more general code clenaups, and some reorgs. As usual USE AT YOUR OWN RISK!!, this is still pre alpha level code. But please tell me how it works for you! Enjoy! -Søren To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: UPDATE2: ATA/ATAPI driver new version available.
On Sun, 7 Mar 1999, Steve Price wrote: On Sun, 7 Mar 1999, Doug Rabson wrote: # Are you sure it tries to probe the slave ?? # Could please try to have it printout scp-devices in ata_probe ?? # # Here is a log of an attempted boot with ATA_DEBUG defined. It looks like # ata_probe() detected a slave where there isn't one. # # ata-pci0: Intel PIIX4 IDE controller rev 0x01 on pci0.5.1 # ata: type=71118086 class=01018001 cmd=0285 [...] # ata0: devices = 0x1 [...] # ata1: devices = 0xc [snip] For what it's worth I get the same two lines: ata0: devices = 0x1 ata1: devices = 0xc So it found the master (the HD) on the first controller, but it appears to find both a master and a slave on the second controller. The problem is that the DVD-ROM doesn't appear to repsond correctly to either of the attempts to determine which one it wants to be. Just for grins I changed the ata_probe to ignore all but the first controller and it is back to the ufs_dirbad panic. :( I never had the ufs_dirbad panic. With the 4 March driver, my system works very well and probes all the ATA devices. Very odd. -- Doug Rabson Mail: d...@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
2nd request for review for vlan changes
This is a second request for review for my proposed if_vlan updates. Since I tweaked a couple of different things, I placed a tarball with the sources at http://www.freebsd.org/~wpaul/VLAN/vlan.tar.gz (or, for those of you with freebsd.org accounts, ~wpaul/public_html/VLAN/vlan.tag.gz). This contains updated sources if_vlan.c, if_vlan_var.h and ifconfig. The changes are as follows: - If the IFF_LINK0 flag is set on a vlan pseudo-interface, it does not peform any header mangling to create the 802.1Q encapsulation, instead allowing the underlying parent driver to do it. (Again, this is mainly for the Tigon driver that I'm working on, which can do its own vlan tag insertion and extraction in firmware.) (I know I used LINK1 before; that's because I forgot that the flag values were zero-based and that LINK0 was really the first one. :) Note: vlan_start() will set rcvif on the outbound mbuf so that the parent driver can find the vlan interface where it originated and find the vlan tag. In order to avoid having the driver possibly follow an uninitialized rcvif pointer, vlan_start() will also set the M_PROTO1 flag in the mbuf to signal to the parent driver that the rcvif is valid. - Implemented vlan_input_tag(), for use with interfaces that know how to do vlan tag extraction and de-capsulation on their own. Works like vlan_input(), except it accepts a third argument, t, which is the extracted vlan tag; given the tag, it tracks down the appropriate vlan interface and sends it the frame. - Added support for multicast. The vlan pseudo interface adds entries to the parent's multicast filter using if_addmulti() and keeps a private list of those groups which it has added. If an update is done, the private list is removed with if_delmulti(), and the parent is programmed again (which again updates the private list). This is a little messy in principle, but the code is fairly simple. - Implemented vlan_unconfig(), the opposite of vlan_config(). When setting up a vlan/parent association with SIOCSETVLAN, the parent's ethernet address and other info are copied to the vlan pseudo interface. This should be removed when the association is broken. - Changed vlan_input()/vlan_input_tag() and vlan_start() to update ifp-if_ipackets and ifp-if_opackets respecively. - If the output queue of the parent interface is full in vlan_start(), increment ifp-if_oerrors, free the mbuf, and continue, instead of just falling through and trying to queue the mbuf even though we know the output queue is full. - Modified ifconfig(8) to allow setting the vlan tag and parent interface of a vlan interface, and to display the interface settings. Three new commands have been added: vlan, vlandev and -vlandev. To set up a vlan interface, you can do this: # ifconfig vlan0 vlan 12345 vlandev foo0 To break the association, you can do this: # ifconfig vlan0 -vlandev foo0 You have to set vlan and vlandev at the same time, since that's how the SIOCSETVLAN ioctl works. Also updated the ifconfig.8 man page. - Fixed a bug in ifconfig. The setifflags() function does a SIOCGIFFLAGS on the ifreq structure that gets passed to it, however this clobbers part of it (namely sa_family) because everything after ifr_name is just one big union. This causes later portions of ifconfig that check the sa_family value to get confused. In my case, the effect was that when I did 'ifconfig vlan0 link0,' ifconfig printed out a line of appletalk status information because sa_family had gotten mangled to 16 (AF_APPLETALK). I still need to write a vlan(4) man page. -Bill -- = -Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu Work: wp...@ctr.columbia.edu | Center for Telecommunications Research Home: wp...@skynet.ctr.columbia.edu | Columbia University, New York City = It is not I who am crazy; it is I who am mad! - Ren Hoek, Space Madness = To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: 2nd request for review for vlan changes
What is vlan? Tnks, Amancio To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: UPDATE3: ATA/ATAPI driver new version available.
On Sun, 7 Mar 1999, S?ren Schmidt wrote: Third update to the new ATA/ATAPI driver: ZIP drives should now be working, I'm not sure about LS120 drives, reports on those most welcome! It doesn't lock up like before, but on my LS-120 wdc1: unit 0 (atapi): LS-120 COSM 02 UHD Floppy/0271C09T, removable, iordy it seems to have corrupt reads. In addition, much of the time the ATA code now will not boot my system, failing at atapi_transfer: bad command phase. Fixed problems: Hang on probe on fantom devices. The probe now use a timeout to avoid hangs if no interrupt is received. There has also been more general code clenaups, and some reorgs. As usual USE AT YOUR OWN RISK!!, this is still pre alpha level code. But please tell me how it works for you! Enjoy! -S?ren To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: UPDATE2: ATA/ATAPI driver new version available.
On Sun, 7 Mar 1999, Doug Rabson wrote: # Just for grins I changed the ata_probe to ignore all but the first # controller and it is back to the ufs_dirbad panic. :( # # I never had the ufs_dirbad panic. With the 4 March driver, my system # works very well and probes all the ATA devices. Very odd. Yep, this one has me baffled. The disklabels are there. Well at least 'disklabel slice_name' shows something besides gibberish. This may sound stupid but if they are required and indeed not there why would the old driver not barf at the same spot? If I had to fathom a guess I'd say it had to do with using incorrect drive geometry. Got any ideas on where I might start looking to fix this one? # -- # Doug Rabson Mail: d...@nlsystems.com # Nonlinear Systems Ltd.Phone: +44 181 442 9037 # # # To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: UPDATE2: ATA/ATAPI driver new version available.
Re: UPDATE2: ATA/ATAPI driver new version available.
On Sun, 7 Mar 1999, Mike Smith wrote: # # From the context I've seen, the 'ufs_dirbad' panic is almost certainly # due to corrupted disk input. I definitely can't rule that out as a possibility, but it does make it difficult to explain how the old driver works on this machine. I'm typing this message from the machine in question. Among other things it is building in the neighborhood of twenty ports, recompiling the JDK for the fifteen millionth time :/, CVSup'ing, running a bunch of rxvt's, and generally working its rump off without even the slightest hint of corrupted or flaky disk. All that aside I'm willing to look closer into the possibility of this being the problem. How does one go about obtaining a copy of the raw disklabels? And once I have them how do I verify them for correctness? Thanks. # -- # \\ Sometimes you're ahead, \\ Mike Smith # \\ sometimes you're behind. \\ m...@smith.net.au # \\ The race is long, and in the \\ msm...@freebsd.org # \\ end it's only with yourself. \\ msm...@cdrom.com # # # To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: UPDATE2: ATA/ATAPI driver new version available.
On Sun, 7 Mar 1999, Mike Smith wrote: # # From the context I've seen, the 'ufs_dirbad' panic is almost certainly # due to corrupted disk input. I definitely can't rule that out as a possibility, but it does make it difficult to explain how the old driver works on this machine. The way I read it, the old driver works fine, but the new driver is reading the wrong disk sectors or failing to transfer them correctly. You might want to try instrumenting the panic and see if you can work out what is actually being read. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ m...@smith.net.au \\ The race is long, and in the \\ msm...@freebsd.org \\ end it's only with yourself. \\ msm...@cdrom.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: UPDATE2: ATA/ATAPI driver new version available.
It seems Steve Price wrote: On Sun, 7 Mar 1999, Mike Smith wrote: # # From the context I've seen, the 'ufs_dirbad' panic is almost certainly # due to corrupted disk input. I definitely can't rule that out as a possibility, but it does make it difficult to explain how the old driver works on this machine. I'm typing this message from the machine in question. Among other things it is building in the neighborhood of twenty ports, recompiling the JDK for the fifteen millionth time :/, CVSup'ing, running a bunch of rxvt's, and generally working its rump off without even the slightest hint of corrupted or flaky disk. All that aside I'm willing to look closer into the possibility of this being the problem. How does one go about obtaining a copy of the raw disklabels? And once I have them how do I verify them for correctness? Hmm, the only thing I can come up with is that either your disk doesn't support multible sectors, or fails to do 32bit transfers. There is an if 0 around the 32/16 bit transfers try reversing it, and then try to comment out the lines that does the multisector setup. -Søren To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: UPDATE3: ATA/ATAPI driver new version available.
It seems Brian Feldman wrote: Third update to the new ATA/ATAPI driver: ZIP drives should now be working, I'm not sure about LS120 drives, reports on those most welcome! It doesn't lock up like before, but on my LS-120 wdc1: unit 0 (atapi): LS-120 COSM 02 UHD Floppy/0271C09T, removable, iordy it seems to have corrupt reads. In addition, much of the time the ATA code now will not boot my system, failing at atapi_transfer: bad command phase. Hmm, you could try to increase the timeout at line 230 in atapi-all.c, se if that helps. -Søren To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
