It seems Andrew Gallatin wrote:
These are UDMA CRC errors, if you upgrade to the latest current, ata
knows to retry these, only if they persist, something is wrong.
However it could indicate cable problems, ie bad connectors or maybe
too long cables..
He said the disk was
It seems [EMAIL PROTECTED] wrote:
Will the backdown to PIO mode be permanent till the next reboot of the
machine, or will the driver be able to attempt to return to DMA mode after
a timeout period. I'm only seeing these errors under really heavy disk
activity (mutlitple nfs readers and
It seems Mike Smith wrote:
It seems Munehiro Matsuda wrote:
Hi all,
I am using -current as of December 9 (CTM:src-cur.4130.gz), and
got following weird ATA related messages while 'make -j4 buildworld'.
I never had this kind of message when using wd drivers.
ata0-master:
statclock_disable is set to 1 if you have the 0x20 flag set on your APM
device. This should probably no longer be the default.
Oops, try this patch instead, again, it's done wrong, but I couldn't
figure out why statclock_disable was getting a value, and I don't have
time to figure it out.
I'd like to have a review on the following patch:
http://www.freebsd.org/~guido/netstat.diff
It adds support to netstat to show listen queue lengths.
Manual page diffs are in the working.
-Guido
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of
Peter Jeremy wrote:
=== games/fortune/datfiles
PATH=$PATH:/usr/games:/usr/obj/3.0/cvs/src/games/fortune/datfiles/../strfile
strfile -Crs /3.0/cvs/src/games/fortune/datfiles/fortunes fortunes.dat
strfile: illegal option -- C
strfile [-iorsx] [-c char] sourcefile [datafile]
*** Error code 1
On Mon, 13 Dec 1999 10:42:36 +0100, Marcel Moolenaar wrote:
I think the easiest solution would be (instead of your patches of
course):
-STRICTTMPPATH= ${WORLDTMP}/bin:${WORLDTMP}/usr/bin
+STRICTTMPPATH= ${WORLDTMP}/bin:${WORLDTMP}/usr/bin:${WORLDTMP}/usr/games
Only if you preceded the
I've just committed a bunch of fixes and enhancements to the ATA driver,
so before submitting new bug reports, PLEASE upgrade to the newest
sources, thanks!
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
What is the big rush to 4.0-RELEASE ?
With all the new functionality and recent changes there are some things
that need to be bedded in (I'm thinking newpcm and ATA). Maybe I'm
saying this because my SB16 PnP has only just been fixed and my CD-ROM
drive doesn't work under the ATA driver (I'm
On Mon, 13 Dec 1999, Steve O'Hara-Smith wrote:
Tell a computer to WIN and ...
... You lose
Actually, I always thought there was something subliminal about typing
"WIN". Funny how they didn't choose "WIND". It's like, you're typing
"WIN", so you in
On Sun, Dec 12, 1999 at 10:37:01AM -0500, Donald J . Maddox wrote:
After rebuilding World and kernel last night, I find that the behavior of
'netstat -a' has changed... Only UNIX domain sockets are shown in the
Errr... may I complain ?
I got the same problem :(
current last night.
On 13-Dec-99 Matthew Thyer wrote:
Consider the 2.2 stream that went through many more releases (counting
2.2.1 - 2.2.8). Using that yardstick you'd expect 4.0 to stay in
development until 3.7 is released. I know 7 releases of the 2.2 stream
was considerred a few too many but surely we can
Hello!
I rebuild all ad* devices at /dev with new MAKEDEV from /usr/src/etc at
my -current, but still have following problem...
...
ata-pci0: Intel PIIX4 ATA controller at device 7.1 on pci0
ata-pci0: Busmastering DMA supported
ata0 at 0x01f0 irq 14 on ata-pci0
ata1 at 0x0170 irq 15 on
On Mon, 13 Dec 1999 10:42:36 +0100, Marcel Moolenaar wrote:
I think the easiest solution would be (instead of your patches of
course):
-STRICTTMPPATH= ${WORLDTMP}/bin:${WORLDTMP}/usr/bin
+STRICTTMPPATH= ${WORLDTMP}/bin:${WORLDTMP}/usr/bin:${WORLDTMP}/usr/games
Only if you
Ah, I see the problem. I have a fix - I'm about to apply it to
-current and ask jkh for permission to MFC.
I've attached the -stable patch for your viewing enjoyment
"JH" == Jon Hamilton [EMAIL PROTECTED] writes:
JH Running -current from this afternoon, I am having a strange
On Mon, 13 Dec 1999, Peter Wemm wrote:
I wonder if we should move fortune to usr.bin? It's hardly a game and I'm
way beyond tired of it being left out of standard paths...
(ie: "/bin:/usr/bin[:/usr/local/bin]")
I have no opinion about fortune, but I do think that md5 should be moved
from
Hi, it looks GREAT !
X clive@cartier ~ netstat -a -f inet -L
Current listen queue sizes (qlen/incqlen/maxqlen)
Listen Local Address
0/0/5 *.1029
0/0/5 *.1028
0/0/5 *.1027
0/0/5 *.1026
"Mike" == Mike Smith [EMAIL PROTECTED] writes:
Mike The "right" solution is and has always been to name your
Mike disks and mount them by name. Once devfs is a reality,
Mike we'll be able to do just this. Until then, the problem's
Mike not really as bad as you make it out to
Soren Schmidt writes:
It seems Andrew Gallatin wrote:
These are UDMA CRC errors, if you upgrade to the latest current, ata
knows to retry these, only if they persist, something is wrong.
However it could indicate cable problems, ie bad connectors or maybe
too long cables..
What I didn't like about CAM was that I lost my tape drive. Since I
had all my backups and archives on DAT, it felt like a bad thing.
Which reminds me -- can anyone spare a 2.1 CD? Please send me private
mail, if so: I foolishly neglected to convert to CD, and now I can't
find 2.1 on the web
On Mon, Dec 13, 1999 at 15:45:15 -0600, Anthony Kimball wrote:
What I didn't like about CAM was that I lost my tape drive. Since I
had all my backups and archives on DAT, it felt like a bad thing.
What do you mean you "lost" your tape drive? CAM has included a tape
driver almost from day
On Saturday, 11 December 1999 at 8:52:28 +0100, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Warner Losh writes:
In message [EMAIL PROTECTED] Poul-Henning Kamp writes:
: You overlook one simple thing here: If we want the ata driver tested,
: we need to make existing kernel configs
On Friday, 10 December 1999 at 19:01:49 +0100, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Nate Williams writes:
In a few days time the wd driver will be retired from FreeBSDs
i386 architecture.
Given that the ATA driver just went active a few minutes ago, I think a
period of
p
On Saturday, 11 December 1999 at 18:28:42 +0800, Peter Wemm wrote:
Dieter Rothacker wrote:
On Sat, 11 Dec 1999 14:21:25 +0800 (WST), Michael Kennett wrote:
Note that wd1 is not present. This caused a mild hickup when rebooting the
new kernel, since the new ata controller assigned the
On Friday, 10 December 1999 at 19:19:43 +0100, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Nate Williams writes:
And your point is? I'm a user, not a developer. If I wanted to be a
developer, I'd have written my own device driver. I want to *USE*
FreeBSD, not develop it.
Then
On Saturday, 11 December 1999 at 15:03:19 +1000, Stephen McKay wrote:
On Friday, 10th December 1999, Mike Smith wrote:
The same mentality that made the CAM cutover a "debacle" is making the
ata cutover a "debacle".
This "mentality" might be an unavoidable part of human nature. I found
my
On Saturday, 11 December 1999 at 12:39:15 +1000, Stephen McKay wrote:
But that shouldn't stop us from moving forward with the ata driver. I
think that a small slowing of the pace, and a bit more understanding toward
those with unusual hardware will help. And I support PHK's hard line
On Saturday, 11 December 1999 at 2:09:48 +0800, Peter Wemm wrote:
Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Nate Williams writes:
In a few days time the wd driver will be retired from FreeBSDs
i386 architecture.
Given that the ATA driver just went active a few minutes ago, I
On Saturday, 11 December 1999 at 0:55:15 +0100, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Kris Ken
naway writes:
No-one (as far as I can see) is objecting to making ata the default (which
it already is), and to kill wd in some number of weeks. Why can't you just
do that, and
On Friday, 10 December 1999 at 17:54:14 -0800, Mike Smith wrote:
If half as much energy was spent adding the missing bits of functionality
to the new systems as people have been spending complaining it then we'd be
there ages ago.
Not true. It doesn't take a disk expert to complain about a
On Friday, 10 December 1999 at 17:11:53 +0100, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Greg Lehey writes:
We're getting off track again: the real issue is that you shouldn't
completely replace old drivers with new, better written, less buggy
drivers which have significantly
On Friday, 10 December 1999 at 23:32:27 -0800, Mike Smith wrote:
[missing attribution to Greg Childers [EMAIL PROTECTED]]
Except that ATA currently does not work on my system. So I assume I'm not
the only one.
Actually, to quote from your original message:
According to technical product
On Friday, 10 December 1999 at 19:04:33 +0100, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Nate Williams writes:
What we need here is a commitment to these new initiatives, not a lot of
fence-sitting and clutching our knitting to our chests.
If all our users were developers I
On Saturday, 11 December 1999 at 0:02:47 +0800, Peter Wemm wrote:
Jeroen Ruigrok/Asmodai wrote:
-On [19991209 16:03], Greg Lehey ([EMAIL PROTECTED]) wrote:
On Wednesday, 8 December 1999 at 20:23:24 +0100, Brad Knowles wrote:
This is -CURRENT. It pains me to say it, but anyone trying to
On Friday, 10 December 1999 at 22:44:36 +0100, Soren Schmidt wrote:
It seems Nate Williams wrote:
If half as much energy was spent adding the missing bits of functionality
to the new systems as people have been spending complaining it then we'd be
there ages ago.
Not true. It doesn't take
On Sun, 12 Dec 1999, Peter Wemm wrote:
-if (drive-vp-v_type != VBLK) { /* only consider bl
ock devices */
+if (!vn_isdisk(drive-vp)) { /* only consider bl
Note: this fixes some recent problems (Hi Greg!) that I've been
having.
From: Soren Schmidt [EMAIL PROTECTED]
Date: Mon, 13 Dec 1999 08:33:43 +0100 (CET)
::It seems Munehiro Matsuda wrote:
:: Hi all,
::
:: I am using -current as of December 9 (CTM:src-cur.4130.gz), and
:: got following weird ATA related messages while 'make -j4 buildworld'.
:: I never had this kind
Greg Lehey wrote:
On Friday, 10 December 1999 at 23:32:27 -0800, Mike Smith wrote:
[missing attribution to Greg Childers [EMAIL PROTECTED]]
Except that ATA currently does not work on my system. So I assume I'm not
the only one.
Actually, to quote from your original message:
On 1999-Dec-12 05:54:12 +1100, Greg Lehey [EMAIL PROTECTED] wrote:
On Friday, 10 December 1999 at 19:01:49 +0100, Poul-Henning Kamp wrote:
The ata driver has been available for you and other to test for a long
time.
Oh. Somehow I missed this. Sure, I saw commits, but I can't recall a
"HEADS
Hi,
Garrett Wollman wrote on 11 May 1999:
[Netgear GigE PCI interface]
I'm buying one of these cards today ($319.99 from NECX) and will stick
it into a machine here on our new Gigabit backbone. I'm particularly
interested to test out the VLAN support, since my Secret Plan is to
have this
Andrew Gallatin writes:
Soren Schmidt writes:
I've fixed it here (I hope), and it will be in the next batch of fixes.
I hope to get through my mailbox today :)
Thanks. I'm running a kernel built with them now. If/when we see CRC
errors, I'll let you know what happens. We
Hi,
The latest 4.0-CURRENT boot floppies are not working
on old ISA boards with 16-bit data transfer only, and
the installation of FreeBSD becomes impossible:( . It
seems that in this case ATA_16BIT_ONLY is not enough -
may be flags to ata0 controller or auto-detection as
Soren promised will be
Anthony Kimball wrote in list.freebsd-current:
What I didn't like about CAM was that I lost my tape drive. Since I
had all my backups and archives on DAT, it felt like a bad thing.
I don't think that's related to CAM. At least my crappy
HP 1533A drive (DDS2) still works with CAM.
Which
This is now fixed in -stable (and -current).
"JH" == Jon Hamilton [EMAIL PROTECTED] writes:
JH Running -current from this afternoon, I am having a strange
JH symptom with ppp over a pty; ppp does not detect that the pty
JH does not support carrier, and will cycle once
On Mon, 13 Dec 1999, Kris Kennaway wrote:
On Mon, 13 Dec 1999, Peter Wemm wrote:
I wonder if we should move fortune to usr.bin? It's hardly a game and I'm
way beyond tired of it being left out of standard paths...
(ie: "/bin:/usr/bin[:/usr/local/bin]")
I have no opinion about
On Mon, 13 Dec 1999, Kris Kennaway wrote:
On Mon, 13 Dec 1999, Peter Wemm wrote:
I wonder if we should move fortune to usr.bin? It's hardly a game and I'm
way beyond tired of it being left out of standard paths...
(ie: "/bin:/usr/bin[:/usr/local/bin]")
I have no opinion
On Mon, 13 Dec 1999, Louis A. Mamakos wrote:
So how about /usr/sbin/chown - /sbin/chown so that MAKEDEV works with
just the root file system mounted?
As one who just got his ass bitten by this, I would vote yes.
--
- bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp -
-
Folks,
In looking through the sysinstall source, I noticed that the man
page states
that "This product is currently at the end of its life cycle and will
eventually
be replaced."
Is there any truth to this? Apparently this verbiage was introduced in
rev 1.20 because the previous text
At 07:40 AM 12/14/99 +0800, Peter Wemm wrote:
Greg Lehey wrote:
On Friday, 10 December 1999 at 23:32:27 -0800, Mike Smith wrote:
[missing attribution to Greg Childers [EMAIL PROTECTED]]
Except that ATA currently does not work on my system. So I assume I'm not
the only one.
3. Get pissed off with FreeBSD and go elsewhere.
don't worry I am sure that quite a few user have left already.
This kind of situation reminds of when I
accidently broke the gus max backwards compatibility.
An old friend of mine sent me a quiet note stating that
he switch OSes cause he
On Sun, Dec 12, 1999 at 11:08:24PM -0800, Mike Smith wrote:
You'll need to take this up with Soren; I suspect though that the simplest
answer for you is going to be to stick with 'wd' until you get yourself a
less-broken disk, or manage to analyse the problem in greater depth.
Ideally I
that "This product is currently at the end of its life cycle and will
eventually
be replaced."
The handy thing about "eventually" is that it can be a long time. :)
Amusingly, the man page author (Jordan?) says, "This utility is a
prototype which lasted approximately 3 years past its
Hello,
I have a QIC 40/80 clone floppy tape drive controller (running
3.3-stable) and wondering if anyone is working/thinking about porting the
ft driver to 3.X/4.X branch. I understand the driver was "removed"
in 2.2.8 due to incompatibility issues. I'd like to help out, thus give
In message [EMAIL PROTECTED] Richard Furda
writes:
: I have a QIC 40/80 clone floppy tape drive controller (running
: 3.3-stable) and wondering if anyone is working/thinking about porting the
: ft driver to 3.X/4.X branch. I understand the driver was "removed"
: in 2.2.8 due to incompatibility
55 matches
Mail list logo
