Re: ATA timeout errors

[Jeroen Ruigrok/Asmodai]

-On [2315 00:00], Will Saxon ([EMAIL PROTECTED]) wrote:
>I will continue to use ata because my drives work (albeit in PIO mode
>apparently) and I don't play audio off the cdrom. Some people will
>probably hold off on upgrading to 4.0 because of this, and I don't know if
>anyone important cares about that but imho it kind of looks bad.

The 4.x tree will keep wd around until we either fix all the problems or
until 5.x becomes mainstream.

5.x has wd removed and people following the bleeding edge are required
to send in feedback and not expect it to be easy to use as it was the
past year. =)

-- 
Jeroen Ruigrok vd Werven/Asmodaiasmodai@[wxs.nl|bart.nl|freebsd.org]
Documentation nutter/C-rated Coder BSD: Technical excellence at its best  
The BSD Programmer's Documentation Project 
Any fool can make a rule.  And every fool will mind it...


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

top %s not correct

[Nathan Sheeley]

As of roughly Mon Mar  6 19:37:1 CST 2000 /usr/bin/top doesn't show the
correct (or any) percentage CPU usage. (example below.) A minor issue I
know, just wanted to point it out if its part of a larger issue.
  
Since upgrading to -current I've noticed:
  o sound now works with my es1371 sb128 pci card, where it didn't no
matter what I tried in 3.4 stable.
  o things that allocate? shared memory (Linux CivCTP, wine) now work 
when I use a SMP kernel (I have a Abit BP6 w/2 433 Celerons)
  o my machine locks up after about 20 hours of uptime.

Obviously the last one is quite annoying, but I haven't been able to
get any info yet on why the crashes happen (I have a dumpdev now, so
it refuses to crash ;)

Nate 

  last pid: 49105;  load averages:  2.06,  1.63,  1.28 
up 1+04:43:59  00:24:42
  30 processes:  3 running, 27 sleeping
  CPU states:  0.0% user,  0.0% nice,  0.0% system,  0.0% interrupt,  0.0% idle
  Mem: 51M Active, 7520K Inact, 18M Wired, 760K Cache, 10M Buf, 47M Free
  Swap: 256M Total, 1560K Used, 254M Free
  
PID USERNAME PRI NICE  SIZERES STATE  C   TIME   WCPUCPU COMMAND
  49045 nobody30   1 14676K 14340K RUN1   3:18  0.00%  0.00% setiathome
  49048 nobody30   1 14676K 14340K CPU0   0   3:12  0.00%  0.00% setiathome
  49070 nsheeley   2   0 49372K 42720K select 1   0:04  0.00%  0.00% XF86_SVGA
199 root  10   0   928K   160K nanslp 1   0:01  0.00%  0.00% cron
160 root   2   0   872K   252K select 1   0:01  0.00%  0.00% syslogd
  49076 nsheeley  10   0  3272K  1984K nanslp 1   0:01  0.00%  0.00% xearth




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: 5.0-current breaks building jpeg shared library

[Richard Wackerbarth]

On Tue, 14 Mar 2000, Vallo Kallaste wrote:

> Strange, I always thought the -current list is for general issues
> related to -current branch  ...

We really should have a new mailing list since we have an additional branch.
I'll again voice the opinion that the naming of the lists is sub-optimal.

IMHO, we should have FreeBSD3, FreeBSD4, FreeBSD5, etc. rather than stable
or current (which one?)

The easiest way I see to make the transition is call the the head branch -DEVEL
and leave -CURRENT for 4.x (for a while)

The mailing lists can be supported by mail aliases until people learn to use
new names.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: 5.0-current breaks building jpeg shared library

[Vallo Kallaste]

On Tue, Mar 14, 2000 at 01:31:39PM -0800, David O'Brien <[EMAIL PROTECTED]> wrote:

> > It's current thing also, no? 
> 
> Not in the least.  Specialized mailing lists exist to take the
> specialized traffic off the more general lists.
> 
> Plus, the fix to your problem is to fix the port.  The Ports team takes
> care of Ports.  None of the Kernel hackers here are going to make any
> ports commits.

Strange, I always thought the -current list is for general issues
related to -current branch and for true kernel hackers exist -hackers.
Okay, this isn't something worth discussing as I believe anybody running
-current is able to fix such things and posting to -current isn't really
necessary.

Thanks
-- 

Vallo Kallaste
[EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: problems using pccard 3c589c with 4.0-snap install

[Warner Losh]

In message <[EMAIL PROTECTED]> Robert 
Watson writes:
: As a followup email, I suppose I'm specifically asking if there's a way to
: make sysinstall allocate IRQ3 to the card, as that seems to be the
: differentiating factor in terms of hardware configuration allocated
: between 3.3-PAO and 4.0-snapshot.  I.e., rather than a sysinstall field
: saying, ``Which of these IRQs should I note use'', instead, ``Which should
: I use''.  Or the like.

Agreed.  Like I said before, I've not had time to bungee into the
sysinstall code and do this... 

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: problems using pccard 3c589c with 4.0-snap install

[Warner Losh]

In message <[EMAIL PROTECTED]> Robert 
Watson writes:
: Any pointers--especially ones that get the install of 4.0 working ``out of
: the box'' on this notebook would be much appreciated.

Make buildworld + make installworld from your 3.3 PAO system.  I've
not had the time/energy to make the install disks bulletproof on all
the laptops.  I'm seriously thinking of doing two things.  First,
removing the IRQ from the pcic (eg make it polling always for
installs).  Second, I'm wanting add smarter IRQ usage to pccardd
and/or the sysinstall program...

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Linksys Revisted..

[Jay Oliver]

Ok... how is it possible to identify different revisions?  As far as I can
tell, the cards are being reported to be identical, though they're almost
certainly not.  And since they both worked fine under 'pn', will it be
possible in the future to have support for the current non working revision
via dc?

- Original Message -
From: "Alex Zepeda" <[EMAIL PROTECTED]>
To: "Jay Oliver" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, March 14, 2000 10:29 PM
Subject: Re: Linksys Revisted..

> Different "revisions" of the Linksys NICs use different chips, so problems
> that afflict one "revision" quite possibly have nothing to do with the
> other card working.
>
> - alex
>
>



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: current.freebsd.org snapshots and broken X11

[Doug Barton]

On Tue, 14 Mar 2000, Jordan K. Hubbard wrote:

> I was actually talking about FreeBSD 4.0, not XFree86 4.0. :)

D'oh! 

-- 
"Welcome to the desert of the real." 

- Laurence Fishburne as Morpheus, "The Matrix"



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: current.freebsd.org snapshots and broken X11

[Jordan K. Hubbard]

I was actually talking about FreeBSD 4.0, not XFree86 4.0. :)

> On Tue, 14 Mar 2000, Jordan K. Hubbard wrote:
> 
> > I think I'm just going to go to the 3.4 bits; I don't have a definitive
> > XFree86 distribution for 4.0 and I don't think I'm going to get one in
> > time to make a difference.
> 
>   Not to mention that 4.0 has "issues" with some
> hardware/software/etc. I can't get xfce to run in it, for example.
> 
> Doug
> -- 
> "Welcome to the desert of the real." 
> 
> - Laurence Fishburne as Morpheus, "The Matrix"
> 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: current.freebsd.org snapshots and broken X11

[Doug Barton]

On Tue, 14 Mar 2000, Jordan K. Hubbard wrote:

> I think I'm just going to go to the 3.4 bits; I don't have a definitive
> XFree86 distribution for 4.0 and I don't think I'm going to get one in
> time to make a difference.

Not to mention that 4.0 has "issues" with some
hardware/software/etc. I can't get xfce to run in it, for example.

Doug
-- 
"Welcome to the desert of the real." 

- Laurence Fishburne as Morpheus, "The Matrix"



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Linksys Revisted..

[Alex Zepeda]

On Mon, 13 Mar 2000, Jay Oliver wrote:

> dc0:  port 0xde00-0xdeff mem
> 0xdfffbf00-0xdfffbff
> dc0: Ethernet address: 00:a0:cc:32:a6:31

Different "revisions" of the Linksys NICs use different chips, so problems
that afflict one "revision" quite possibly have nothing to do with the
other card working.

- alex



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Australian Time Servers

[Chris Knight]

Howdy,
According to http://www.eecis.udel.edu/~mills/ntp/clock1.htm,
ntp.syd.dms.csiro.au no longer offers ntp services.
ntp.tip.csiro.au or ntp.ml.csiro.au should be used instead. These are
listed at the above-mentioned location as open access servers.
Here's a diff for sysinstall. Could some-one please commit it. Thanks.

Regards,
Chris Knight
Systems Administrator
AIMS Independent Computer Professionals
Tel: +61 3 6334 6664  Fax: +61 3 6331 7032  Mob: +61 419 528 795
Web: http://www.aims.com.au



--- release/sysinstall/menus.c.orig Wed Mar 15 13:57:59 2000
+++ release/sysinstall/menus.c  Wed Mar 15 13:59:27 2000
@@ -1365,9 +1365,9 @@
"ntpdate_enable=NO,ntpdate_flags=none" },
   { "Other",   "Select a site not on this list",
dmenuVarsCheck, configNTP, NULL, NULL },
-  { "Australia",   "ntp.syd.dms.csiro.au (HP 5061 Cesium Beam)",
+  { "Australia",   "ntp.tip.csiro.au (HP 5061 Cesium Beam)",
dmenuVarsCheck, dmenuSetVariables, NULL, 
-   "ntpdate_enable=YES,ntpdate_flags=ntp.syd.dms.csiro.au" },
+   "ntpdate_enable=YES,ntpdate_flags=ntp.tip.csiro.au" },
   { " Canada", "tick.usask.ca (GOES clock)",
dmenuVarsCheck, dmenuSetVariables, NULL, 
"ntpdate_enable=YES,ntpdate_flags=tick.usask.ca" },

Re: 4.0R ?

[Peter Jeremy]

On 2000-Mar-15 13:39:55 +1100, Anatoly Vorobey <[EMAIL PROTECTED]> wrote:
>So is there a consensus on when 3.x-STABLE is going to be
>retired?

Current suggestions are that it will go to 3.6 or 3.7 before being
retired.  This will presumably depend on the rate at which 4.x
stabilizes and people move to it, as well as the number of problems
found with 3.x.

> Will there be new releases on the RELENG_3 branch, in fact?

Yes.  At least 2, probably 3.

And this thread really belongs in -stable, not -current.

Peter


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: [sound] PCI ESS support

[Darryl Okahata]

[EMAIL PROTECTED] (Munehiro Matsuda) wrote:

> No, I don't have real ESS docs. 

 Thanks, anyway.

> I have 1)the usual DSMaestro2E 3-02-98.pdf datasheet, 2)some small stuff
> I grabbed off ftp.esstech.com.tw (nolonger exists on the site?) and

 There are hidden files on ftp.esstech.com.tw.  Just go to:

ftp://ftp.esstech.com.tw/PCIAudio/Maestro2E/

"PCIAudio" is an hidden directory.

> 3)source code for Maestro 2E Board Test (BTM2E.EXE) program which I
> downloaded from ftp://ftp.alsa-project.org/pub/manuals/ess/maestro.tar.gz.  

 Thanks for the pointer.  I'll check it out.

--
Darryl Okahata
[EMAIL PROTECTED]

DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion, or policy of Agilent Technologies, or
of the little green men that have been following him all day.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: 4.0R ?

[Anatoly Vorobey]

On Tue, Mar 14, 2000 at 02:33:26PM -0800, David O'Brien wrote:
> On Mon, Mar 13, 2000 at 07:05:46PM +, Ben Smithurst wrote:
> > I saw the RELENG_4 tag in my cvsup log, but I don't think that's the
> > same as the 4.0 release tag is it?
> 
> You are right -- RELENG_4 is not the release tag.
> 
> > That would be RELENG_4_0_0_RELEASE surely.
> 
> Correct.

So is there a consensus on when 3.x-STABLE is going to be
retired? Will there be new releases on the RELENG_3 branch, in fact?


-- 
Anatoly Vorobey,
[EMAIL PROTECTED] http://pobox.com/~mellon/
"Angels can fly because they take themselves lightly" - G.K.Chesterton


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: suggestion: a g77 -> f77 link

[Garrett Wollman]

< said:

> *IF* I understand what you are trying to say, here is my answer:  if I
> were to start fresh with with bringing in the first C compiler into
> FreeBSD, it would not have a 'gcc' name to it -- only 'cc'.

Indeed, that was precisely how it used to be.  Then


revision 1.6
date: 1994/11/01 20:51:29;  author: jkh;  state: Exp;  lines: +3 -1
Add LINKS to get gcc back.


...we decided that too many things were made unhappy when gcc was not
available under its usual name.  Not because it was the Right Thing,
but because we're not in this to make life hard for developers and
users.  The parallel log entry for c++/Makefile bears that out:


revision 1.4
date: 1994/11/01 21:28:00;  author: jkh;  state: Exp;  lines: +2 -1
Link g++ -> c++, like I did with gcc -> cc.  This is evil, but it's
now at least orthogonal evil.


Note that the change to cc/Makefile undid a previous change:


revision 1.3
date: 1994/08/23 17:18:58;  author: paul;  state: Exp;  lines: +0 -6
Fixed up everything so that the version of gcc that we install from the
FreeBSD system sources installs itself as the standard cc and c++. I've
fixed c++ to call cc instead of gcc and removed all the symlinks
that get created to g** version of the binaries. This means that
you can install a second version of gcc that does use the g prefix
alongside the "system" version of gcc. The only conflict is libgcc
[...]


So at one time we followed the direction you wish.

-GAWollman

--
Garrett A. Wollman   | O Siem / We are all family / O Siem / We're all the same
[EMAIL PROTECTED]  | O Siem / The fires of freedom 
Opinions not those of| Dance in the burning flame
MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: suggestion: a g77 -> f77 link

[David O'Brien]

On Tue, Mar 14, 2000 at 05:40:48PM -0500, Garrett Wollman wrote:
> > NO.  I will not apply this link.  BSD has always had a "f77" command.  It
> > has not always had a "g77" command.  The G77 developers should have
> > installed a "f77" compatability link.  It is their fault this misspelling
> > is perpitrating forward.  All the world is not Gfoo.
> 
> s/77/cc/g;

Due to your typical verbosity, I am left to wonder what you are trying to
say.  

*IF* I understand what you are trying to say, here is my answer:  if I
were to start fresh with with bringing in the first C compiler into
FreeBSD, it would not have a 'gcc' name to it -- only 'cc'.  There is too
much conflicts with other GCC ports or people installing their own copy
of GCC.

-- 
-- David([EMAIL PROTECTED])


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: suggestion: a g77 -> f77 link

[Satoshi - Ports Wraith - Asami]

 * From: "David O'Brien" <[EMAIL PROTECTED]>

 * On Mon, Mar 13, 2000 at 05:00:17PM +0100, Jose M. Alcaide wrote:
 * > I found that the "configure" script, when instructed to use the
 * > GNU Fortran compiler, searchs for "g77". Unfortunately, this compiler
 * > is installed as /usr/bin/f77. 

I think this is a reasonable request.

 * NO.  I will not apply this link.  BSD has always had a "f77" command.  It
 * has not always had a "g77" command.  The G77 developers should have
 * installed a "f77" compatability link.  It is their fault this misspelling
 * is perpitrating forward.  All the world is not Gfoo.

Yes, but ours *is* a GNU Fortran77 compiler.  It is perfectly sane for
programs to look for "g77" if they want GNU Fortran77 (for whatever
reason).

===
>> f77 -v 2>&1 | head -1
g77 version 2.95.2 19991024 (release) (from FSF-g77 version 0.5.25 19991024 (release))
>> f77 --version
GNU Fortran 0.5.25 19991024 (release)
Copyright (C) 1997 Free Software Foundation, Inc.
For more version information on components of the GNU Fortran
compilation system, especially useful when reporting bugs,
type the command `g77 --verbose'.

GNU Fortran comes with NO WARRANTY, to the extent permitted by law.
You may redistribute copies of GNU Fortran
under the terms of the GNU General Public License.
For more information about these matters, see the file named COPYING
or type the command `info -f g77 Copying'.
===

Satoshi


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: [sound] PCI ESS support

[Munehiro Matsuda]

From: Darryl Okahata <[EMAIL PROTECTED]>
Date: Tue, 14 Mar 2000 16:38:54 PST
::
::> If you are tring to write a driver for it, I still have some docs around.
::> If you need them, let me know.
::
:: If you have anything more than the ESS datasheets (like real ESS
::docs), I'd like to get a copy.

No, I don't have real ESS docs. 
I have 1)the usual DSMaestro2E 3-02-98.pdf datasheet, 2)some small stuff
I grabbed off ftp.esstech.com.tw (nolonger exists on the site?) and
3)source code for Maestro 2E Board Test (BTM2E.EXE) program which I
downloaded from ftp://ftp.alsa-project.org/pub/manuals/ess/maestro.tar.gz.  

For legacy support, source code for BTM2E.EXE should get you going.
Be aware, FreeBSD doesn't support DDMA, you need to hack around that too.
I've got a small DDMA patch for 3-STABLE, which dosen't apply to -current,
though...

  Haro
=--
   _ _Munehiro (haro) Matsuda
 -|- /_\  |_|_|   Office of Business Planning & Development, Kubota Corp.
 /|\ |_|  |_|_|   1-3 Nihonbashi-Muromachi 3-Chome
  Chuo-ku Tokyo 103, Japan
  Tel: +81-3-3245-3318  Fax: +81-3-32454-3315
  Email: [EMAIL PROTECTED]



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: [sound] PCI ESS support

[Darryl Okahata]

[EMAIL PROTECTED] (Munehiro Matsuda) wrote:

> If you are tring to write a driver for it, I still have some docs around.
> If you need them, let me know.

 If you have anything more than the ESS datasheets (like real ESS
docs), I'd like to get a copy.

 Thanks,

--
Darryl Okahata
[EMAIL PROTECTED]

DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion, or policy of Agilent Technologies, or
of the little green men that have been following him all day.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: 4.0R ?

[Peter Jeremy]

At 19:05 03/13/2000 +, Ben Smithurst wrote:
>I saw the RELENG_4 tag in my cvsup log, but I don't think that's the
>same as the 4.0 release tag is it? That would be RELENG_4_0_0_RELEASE
>surely.

That's correct.  RELENG_4 is the 4.x-STABLE branch.  At some point,
Jordan will create a RELENG_4_0_0_RELEASE tag which will define
4.0-RELEASE.

Peter


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: [sound] PCI ESS support

[Munehiro Matsuda]

From: "Alan Clegg" <[EMAIL PROTECTED]>
Date: 13 Mar 2000 13:34:01 -
::
::Ok, being a newbie to FreeBSD, I'm trying to get my laptop (WinBook XL2)
::sound working under -CURRENT.  If someone could point me to the relavent
::docs, I'd be happy Here is what I'm finding:
::
::dmesg reports:
::
::chip2:  port 0xec00-0xecff irq 5 at 

Hello,

As far as I know, "Maestro 2E" is not supported in -current.

I once tried to write a driver under 3-stable, but failed. More worse,
I've lost my source code due to disk crash, last fall. Sigh.

If you are tring to write a driver for it, I still have some docs around.
If you need them, let me know.

  Haro
=--
   _ _Munehiro (haro) Matsuda
 -|- /_\  |_|_|   Office of Business Planning & Development, Kubota Corp.
 /|\ |_|  |_|_|   1-3 Nihonbashi-Muromachi 3-Chome
  Chuo-ku Tokyo 103, Japan
  Tel: +81-3-3245-3318  Fax: +81-3-32454-3315
  Email: [EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: mouse question

[Brooks Davis]

On Tue, Mar 14, 2000 at 05:27:30PM -0500, Will Saxon wrote:
> Not certain what list this ought to go to, perhaps -questions so I
> apologize if this is not the right one.

-questions was the right place.  This has nothing do with current.
Redirecting to -questions.

> I was wondering if there could be a way to 'force' a type of ps/2 mouse. I
> have a logitech firstmouse+, with a wheel. It works fine if it is plugged
> directly into the back of this machine. However, I have it running through
> a KVM switch so that I can have one mouse for both of my machines. When
> in this configuration, the wheel action never works (although it works on
> the other machine, which runs windows), and the button action sometimes
> also doesn't work (this is rare). 
> 
> When plugged into the switch, I get this:
> 
> psm0: failed to get data.
> psm0:  irq 12 on atkbdc0
> psm0: model Generic PS/2 mouse, device ID 0
> 
> 
> When plugged directly into the machine the third line comes up with
> MouseMan+. 
> 
> I have tried to manipulate moused to account for the wheel by mapping the
> wheel events as extra buttons, and I have tried to do the same in
> XF86Config. Neither work.
> 
> Not terribly important, but it would be nice to know if there is something
> I can do about it.

Unless your switch supports wheel mice (in which case it would just
work) I believe you are SOL.  I tried a coupld of KVM solutions before
buying one from Black Box that explicitly supported wheel mice.  The
problem (I believe) is that KVMs must actuall emulate the mouse protocol
so they must know what your mouse thinks it is doing.  I'm pretty happy
with my switch, it's the Personal Serv Switch.  It's a bit more
expensive, but it actually works.  The only problem I've found is that
it occationaly looses sync with the mouse, but there is a keyboard
command to reset the mouse which generally fixes it.

-- Brooks

-- 
Any statement of the form "X is the one, true Y" is FALSE.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

ata + vinum problems

[Mathew Kanner]

Hi All, 
I wanted to document my difficuties with Vinum and multiple
disks on Promise controllers.  I believe that the problems lies with
multiple cards on the same interupt but what do I know  -- execpt that
the problem goes away when I disable most devices in the BIOS.
The motherboard is a abit BE6-II, I've enabled most BIOS
periphs such as serial ports, printer ports, usb, vga ints but not APM.  
I've included the script that causes the crash, a back-trace
and dmesg output right before the crash and the kernel config.  The
raid devices where made via the vinum simplified commands (which are
*very nice*).
It should be noted that I had to control the 'tar' part of the
script because it was stuck in a "nbufkv" and disk activity ceases.
The crash happened upto 10 seconds after I get a shell prompt back.
The "nbufkv" was the sure sign that something had gone wrong in my
previous 'uncontrolled' tests.

--Mat



#!/bin/sh -x

BLOCK_SIZE=`expr 32 \* 1024`
FRAG_SIZE=`expr 8 \* 1024`
ISIZE=`expr 6 \* ${FRAG_SIZE}`
#CYL=635
CYL=200
FAKE=""
DEV="/dev/vinum/raid5"
MOUNT="/mnt1"

newfs ${FAKE} -v -b ${BLOCK_SIZE} -f ${FRAG_SIZE} -i ${ISIZE} -c ${CYL} ${DEV}
tunefs -n enable ${DEV}
mount ${DEV} ${MOUNT}
tar cf - -C /usr/ ports | tar xf - -C ${MOUNT}


Copyright (c) 1992-2000 The FreeBSD Project.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
FreeBSD 5.0-CURRENT #4: Mon Mar 13 17:54:22 GMT 2000
[EMAIL PROTECTED]:/usr/src/sys/compile/KAZE
Timecounter "i8254"  frequency 1193182 Hz
CPU: Pentium III/Pentium III Xeon (551.25-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x673  Stepping = 3
  
Features=0x387f9ff
real memory  = 536870912 (524288K bytes)
avail memory = 516128768 (504032K bytes)
Preloaded elf kernel "kernel" at 0xc03e9000.
Pentium Pro MTRR support enabled
md0: Malloc disk
npx0:  on motherboard
npx0: INT 16 interface
pcib0:  on motherboard
pci0:  on pcib0
pcib1:  at device 1.0 on pci0
pci1:  on pcib1
pci1:  at 0.0 irq 10
isab0:  at device 7.0 on pci0
isa0:  on isab0
atapci0:  port 0xf000-0xf00f at device 7.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
pci0:  at 7.2 irq 9
chip1:  port 0x5000-0x500f at device 7.3 on 
pci0
xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0x9400-0x947f mem 0xe706-0xe706007f 
irq 9 at device 11.0 on pci0
xl0: Ethernet address: 00:50:da:d6:6a:d0
miibus0:  on xl0
xlphy0: <3Com internal media interface> on miibus0
xlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
xl0: supplying EUI64: 00:50:da:ff:fe:d6:6a:d0
atapci1:  port 
0xa800-0xa83f,0xa400-0xa403,0xa000-0xa007,0x9c00-0x9c03,0x9800-0x9807 mem 
0xe704-0xe705 irq 11 at device 13.0 on pci0
ata2: at 0x9800 on atapci1
ata3: at 0xa000 on atapci1
atapci2:  port 
0xbc00-0xbc3f,0xb800-0xb803,0xb400-0xb407,0xb000-0xb003,0xac00-0xac07 mem 
0xe702-0xe703 irq 5 at device 15.0 on pci0
ata4: at 0xac00 on atapci2
ata5: at 0xb400 on atapci2
atapci3:  port 
0xd000-0xd03f,0xcc00-0xcc03,0xc800-0xc807,0xc400-0xc403,0xc000-0xc007 mem 
0xe700-0xe701 irq 10 at device 17.0 on pci0
atapci4:  port 
0xdc00-0xdcff,0xd800-0xd803,0xd400-0xd407 irq 11 at device 19.0 on pci0
atapci5:  port 
0xe800-0xe8ff,0xe400-0xe403,0xe000-0xe007 irq 11 at device 19.1 on pci0
fdc0:  at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
atkbdc0:  at port 0x60-0x6f on isa0
atkbd0:  irq 1 on atkbdc0
kbd0 at atkbd0
psm0:  irq 12 on atkbdc0
psm0: model Generic PS/2 mouse, device ID 0
vga0:  at port 0x3c0-0x3df iomem 0xa-0xb on isa0
sc0:  on isa0
sc0: VGA <16 virtual consoles, flags=0x200>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
ppc0: cannot reserve I/O port range
ad0: 26063MB  [52953/16/63] at ata0-master using UDMA33
ad4: 26063MB  [52953/16/63] at ata2-master using UDMA66
ad6: 26063MB  [52953/16/63] at ata3-master using UDMA66
ad8: 26063MB  [52953/16/63] at ata4-master using UDMA66
ad10: 26063MB  [52953/16/63] at ata5-master using UDMA66
acd0: CD-RW  at ata1-master using PIO4
Mounting root from ufs:/dev/ad0s1a
vinum: loaded
vinum: reading configuration from /dev/ad10s1e
vinum: updating configuration from /dev/ad8s1e
vinum: updating configuration from /dev/ad4s1e
vinum: updating configuration from /dev/ad6s1e
xl0: starting DAD for fe80:0001::0250:daff:fed6:6ad0
xl0: DAD complete for fe80:0001::0250:daff:fed6:6ad0 - no duplicates found


#0  0xc017f008 in boot ()
#1  0xc017f38c in poweroff_wait ()
#2  0xc02ba2a9 in trap_fatal ()
#3  0xc02b9f81 in trap_pfault ()
#4  0xc02b9b77 in trap ()
#5  0xc025d8b4 in acquire_lock ()
#6  0xc026081a in initiate_write_filepage ()
#7  0xc02606e7 in softdep_disk_io_initiation ()
#8  0xc01b45b7 in spec_strategy ()
#9  0xc01b40ed in spec_vnoperate ()
#10 0xc026c4c9 in ufs_vnoperatesp

Re: Compaq SMART EISA and ida driver -> kernel panic

[Oliver Schonefeld]

Eines schoenen Tages schrieb Matthew N. Dodd:
> On Tue, 14 Mar 2000, Oliver Schonefeld wrote:
> > hmm ... the controller shows up with another io-adress, but now the driver
> > panics because of a time out :-(
> 
> Try this patch:
[snip]

again, no success. the driver counts down the timeout with the same result
as before.
stragne thing, after i applied you first patch (setting the other io-adress)
the machine would not reboot after the panic.
a "call boot()" would also hang the machine. i had to hard-reset that thing.

that's all i can observe right now. if you need more informations, please
let me know.

regards,
oliver
-- 

And remember: "To Infinity And Far Beyond ... Somehow?!"

email: [EMAIL PROTECTED]
   [EMAIL PROTECTED]

Hi! I'm a .signature virus! Copy me in your ~/.signature
to help me spread! <- Save this lifeform ;-)


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: suggestion: a g77 -> f77 link

[Garrett Wollman]

< said:

> NO.  I will not apply this link.  BSD has always had a "f77" command.  It
> has not always had a "g77" command.  The G77 developers should have
> installed a "f77" compatability link.  It is their fault this misspelling
> is perpitrating forward.  All the world is not Gfoo.

s/77/cc/g;

-GAWollman

--
Garrett A. Wollman   | O Siem / We are all family / O Siem / We're all the same
[EMAIL PROTECTED]  | O Siem / The fires of freedom 
Opinions not those of| Dance in the burning flame
MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: suggestion: a g77 -> f77 link

[David O'Brien]

On Mon, Mar 13, 2000 at 05:00:17PM +0100, Jose M. Alcaide wrote:
> I found that the "configure" script, when instructed to use the
> GNU Fortran compiler, searchs for "g77". Unfortunately, this compiler
> is installed as /usr/bin/f77. 

Fix Scilab-2.5's config script and send the patch to its author.
Alternately, send-pr an update to the math/Scilab port.

> The solution is simple: "ln f77 g77", but I think that the "g77" link
> should be standard, since it's coherent with the existence of the "cc"
> and "gcc" links.

NO.  I will not apply this link.  BSD has always had a "f77" command.  It
has not always had a "g77" command.  The G77 developers should have
installed a "f77" compatability link.  It is their fault this misspelling
is perpitrating forward.  All the world is not Gfoo.
 
-- 
-- David([EMAIL PROTECTED])


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: 4.0R ?

[David O'Brien]

On Mon, Mar 13, 2000 at 07:05:46PM +, Ben Smithurst wrote:
> I saw the RELENG_4 tag in my cvsup log, but I don't think that's the
> same as the 4.0 release tag is it?

You are right -- RELENG_4 is not the release tag.

> That would be RELENG_4_0_0_RELEASE surely.

Correct.
 
-- 
-- David([EMAIL PROTECTED])


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: 4.0R ?

[David O'Brien]

On Tue, Mar 14, 2000 at 08:20:40AM -0500, Tom Embt wrote:
> I believe RELENG_4 would refer to the 4.x-STABLE branch (??maybe??)

Yes.

-- 
-- David([EMAIL PROTECTED])


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

mouse question

[Will Saxon]

Hello,

Not certain what list this ought to go to, perhaps -questions so I
apologize if this is not the right one.

I was wondering if there could be a way to 'force' a type of ps/2 mouse. I
have a logitech firstmouse+, with a wheel. It works fine if it is plugged
directly into the back of this machine. However, I have it running through
a KVM switch so that I can have one mouse for both of my machines. When
in this configuration, the wheel action never works (although it works on
the other machine, which runs windows), and the button action sometimes
also doesn't work (this is rare). 

When plugged into the switch, I get this:

psm0: failed to get data.
psm0:  irq 12 on atkbdc0
psm0: model Generic PS/2 mouse, device ID 0


When plugged directly into the machine the third line comes up with
MouseMan+. 

I have tried to manipulate moused to account for the wheel by mapping the
wheel events as extra buttons, and I have tried to do the same in
XF86Config. Neither work.

Not terribly important, but it would be nice to know if there is something
I can do about it.

-Will



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Compaq SMART EISA and ida driver -> kernel panic

[Matthew N. Dodd]

On Tue, 14 Mar 2000, Oliver Schonefeld wrote:
> hmm ... the controller shows up with another io-adress, but now the driver
> panics because of a time out :-(

Try this patch:

Index: ida.c
===
RCS file: /cvs/src/sys/dev/ida/ida.c,v
retrieving revision 1.7
diff -u -r1.7 ida.c
--- ida.c   2000/03/08 16:16:30 1.7
+++ ida.c   2000/03/14 22:24:34
@@ -348,7 +348,7 @@
s = splbio();
STAILQ_INSERT_TAIL(&ida->qcb_queue, qcb, link.stqe);
ida_start(ida);
-   ida_wait(ida, qcb, 500);
+   ida_wait(ida, qcb, 20);
splx(s);
 
/* XXX should have status returned here? */

> 
> kernel msgs:
> ida0:  at 0x4000-0x40ff, 0x4c88-0x4c9e
> ida0: irq 15 (level) on eisa0 slot 4
> panic: ida_wait: timeout waiting for completion
> 
> kernel debugger:
> ida_wait(c0ca5d00,c0ca7000,1f4,c0ca5d00,0) at ida_wait+0x43
> ida_command(c0ca5d00,11,c029eeb4,9,0,1,c0ca5d00,0) at ida_command+0xf8
> ida_attach(c0ca5d00,c0ca4c80,c0ca4f00,0,c0ca5d00) at ida_attach+0x28
> ida_eisa_attach(c0ca4c80,c029ef08,c0156223,c0ca4c80,c0ca4c80) at
>   ida_eisa_attach+0x187
> DEVICE_ATTACH(c0ca4c80,c0ca4c80,c0ca2000,0,c029ef18) at DEVICE_ATTACH+0x2e
> 
> regards,
> oliver
> 

-- 
| Matthew N. Dodd  | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD  |
| [EMAIL PROTECTED] |   2 x '84 Volvo 245DL| ix86,sparc,pmax |
| http://www.jurai.net/~winter | This Space For Rent  | ISO8802.5 4ever |



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: ATA timeout errors

[Will Saxon]

Well, while this isn't a problem that causes panics or makes people unable
to use their machines, I think maybe the removal of the older wd driver
ought to be held off until the ata driver provides all the features wdc
does don't you think? I guess the philosophy here is that there shouldn't
be driver redundancy in a -RELEASE or something? 

I will continue to use ata because my drives work (albeit in PIO mode
apparently) and I don't play audio off the cdrom. Some people will
probably hold off on upgrading to 4.0 because of this, and I don't know if
anyone important cares about that but imho it kind of looks bad.

Just a thought. Again, my box works, just not as advertised :). Could very
well be user error, I just don't know.

-will

On Tue, 14 Mar 2000, Kris Kennaway wrote:

> On Tue, 14 Mar 2000, Patrik Sundberg wrote:
> 
> > I also get this when booting - think it started happening when I started
> > using the new ata-driver. For me it happens when the root is supposed to be
> > mounted (from dmesg):
> 
> > As you can see I am using a seagate disk and I am having the same problem.
> 
> I've always had this problem with the new ata drivers (on a Western
> Digital, though). Looks like it's just something we have to Deal With :-(
> Plus, my CDROM doesn't do audio any more.
> 
> Kris
> 
> 
> In God we Trust -- all others must submit an X.509 certificate.
> -- Charles Forsythe <[EMAIL PROTECTED]>
> 
> 




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: ATA timeout errors

[Kris Kennaway]

On Tue, 14 Mar 2000, Patrik Sundberg wrote:

> Tested my CDROM for audio just now - works fine (at least pressing the
> buttons on the unit, have no softwareplayer to test with so it might not
> work anyway - my cd is total crap and usually has all kinds of problems..)

The problem is with cdcontrol and the like, not the front-panel buttons
which bypass the software altogether.

Kris


In God we Trust -- all others must submit an X.509 certificate.
-- Charles Forsythe <[EMAIL PROTECTED]>



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: ATA timeout errors

[Patrik Sundberg]

On Tue, Mar 14, 2000 at 01:33:55PM -0800, Kris Kennaway wrote:
> On Tue, 14 Mar 2000, Patrik Sundberg wrote:
> 
> > I also get this when booting - think it started happening when I started
> > using the new ata-driver. For me it happens when the root is supposed to be
> > mounted (from dmesg):
> 
> > As you can see I am using a seagate disk and I am having the same problem.
> 
> I've always had this problem with the new ata drivers (on a Western
> Digital, though). Looks like it's just something we have to Deal With :-(
> Plus, my CDROM doesn't do audio any more.

Tested my CDROM for audio just now - works fine (at least pressing the
buttons on the unit, have no softwareplayer to test with so it might not
work anyway - my cd is total crap and usually has all kinds of problems..)

However, it seems this affects many people using different hardware. The
conclusion must be that the ATA drivers needs fixing - not being able to use
DMA-mode for disks etc just isn't acceptable, especially considering it
worked ok with the wd driver - or did that driver not even try the "better"
modes, just falling back to PIO default? I am not familiar with it so I
don't know. If it in fact worked before, the ata-guys(Sören, right?)
shouldn't have too hard a time getting it to function properly again.

Sören, comments?

-- 
Patrik Sundberg  -  email: [EMAIL PROTECTED] || [EMAIL PROTECTED]
---> telefon: 013-178 567  -  mobiltelefon: 070-760 22 40 <---


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: ATA timeout errors

[Eric Jacoboni]

Will Saxon <[EMAIL PROTECTED]> writes:

> ad0: READ command timeout - resetting
> ata0: resetting devices .. done
(...)
> I dont get any panics or anything, and after the reset to PIO everything
> seems to work fine. 

You're lucky ;-)

I have the same kind of messages, but it ends with a dead freeze of my box.

The messages are :

ad0: WRITE command timeout - resetting
ata0: resetting devices .. done

Sometimes i've also :

ad0: timeout waitin for DRQ
ad0: HARD WRITE ERROR blk#xx status=01 error=02

The relevant lines of booting messages are :

atapci0:  port 0xe800-0xe80f at device 7.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
(...)
ad0: 1222MB  [2484/16/63] at ata0-master using WDMA2
ad1: 2445MB  [4969/16/63] at ata0-slave using WDMA2
acd0: CDROM  at ata1-master using PIO4

This problem arises with the following kernel config :

device  ata
device  atadisk # ATA disk drives
device  atapicd # ATAPI CDROM drives
device  atapifd # ATAPI floppy drives

options ATA_STATIC_ID

If i use the old wdc driver, all is ok.

My box is using a Asustek P/I-P55T2P4 Motherboard, with a on-board PCI
Bus Master IDE controller. As written is the doc, this controller
supports PIO Modes 3 & 4 and Bus Master IDE DMA Mode 2.

If someone has a solution to get rid of wdc with such a config, he's
welcome... 

(I'm currently compiling a kernel with the "device ata0 at..." and
"device ata1 at..." lines
instead of "device ata", just to verify...)
-- 
-
Éric Jacoboni   « No sport, cigars! »  (W. Churchill)
-


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: ATA timeout errors

[Kris Kennaway]

On Tue, 14 Mar 2000, Patrik Sundberg wrote:

> I also get this when booting - think it started happening when I started
> using the new ata-driver. For me it happens when the root is supposed to be
> mounted (from dmesg):

> As you can see I am using a seagate disk and I am having the same problem.

I've always had this problem with the new ata drivers (on a Western
Digital, though). Looks like it's just something we have to Deal With :-(
Plus, my CDROM doesn't do audio any more.

Kris


In God we Trust -- all others must submit an X.509 certificate.
-- Charles Forsythe <[EMAIL PROTECTED]>



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: 5.0-current breaks building jpeg shared library

[David O'Brien]

On Tue, Mar 14, 2000 at 06:26:37PM +0200, Vallo Kallaste wrote:
> > This belongs in [EMAIL PROTECTED]  *NOT* the freebsd-current list!!!
> Yes, I did bounce the mail to freebsd-ports as well. 

> It's current thing also, no? 

Not in the least.  Specialized mailing lists exist to take the
specialized traffic off the more general lists.

Plus, the fix to your problem is to fix the port.  The Ports team takes
care of Ports.  None of the Kernel hackers here are going to make any
ports commits.

-- 
-- David([EMAIL PROTECTED])


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Compaq SMART EISA and ida driver -> kernel panic

[Oliver Schonefeld]

Eines schoenen Tages schrieb Matthew N. Dodd:
[snip]
> Doh!  Looks like Jonathan didn't merge the latest ida_eisa.c that I'd
> worked on when he fixed the driver to support multiple access methods and
> added EISA support.
> 
> Try this patch:
[snip]

hmm ... the controller shows up with another io-adress, but now the driver
panics because of a time out :-(

kernel msgs:
ida0:  at 0x4000-0x40ff, 0x4c88-0x4c9e
ida0: irq 15 (level) on eisa0 slot 4
panic: ida_wait: timeout waiting for completion

kernel debugger:
ida_wait(c0ca5d00,c0ca7000,1f4,c0ca5d00,0) at ida_wait+0x43
ida_command(c0ca5d00,11,c029eeb4,9,0,1,c0ca5d00,0) at ida_command+0xf8
ida_attach(c0ca5d00,c0ca4c80,c0ca4f00,0,c0ca5d00) at ida_attach+0x28
ida_eisa_attach(c0ca4c80,c029ef08,c0156223,c0ca4c80,c0ca4c80) at
  ida_eisa_attach+0x187
DEVICE_ATTACH(c0ca4c80,c0ca4c80,c0ca2000,0,c029ef18) at DEVICE_ATTACH+0x2e

regards,
oliver
-- 

And remember: "To Infinity And Far Beyond ... Somehow?!"

email: [EMAIL PROTECTED]
   [EMAIL PROTECTED]

Hi! I'm a .signature virus! Copy me in your ~/.signature
to help me spread! <- Save this lifeform ;-)


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: CMD640 and ATA drivers

[Thomas Veldhouse]

On Tue, 14 Mar 2000, Soren Schmidt wrote:

> It worked until the latest newbus changes, I'm looking at it, but havn't
> found anything obvious yet.
> But seriously you want to get another ATA interface, the CMD640 is
> _broken_ and no software can help that, you are playing russian
> roulette with your data. Get a promise, abit or siig controller
> and use that instead...

Yeap, that sounds like the best idea.  Right now it is just a gateway - so
there has been no really I/O on the drive.  I did have some corruption
awhile back while using SAMBA - but I did not attribute it to the CMD640
then.  I found an older ISA Promise for under $30, I think I will get
that.  This box is an old Pentium with a 166MMX Overdrive in it.  Old SiS
customized board too.

Tom Veldhouse
[EMAIL PROTECTED]




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: problems using pccard 3c589c with 4.0-snap install

[Robert Watson]

As a followup email, I suppose I'm specifically asking if there's a way to
make sysinstall allocate IRQ3 to the card, as that seems to be the
differentiating factor in terms of hardware configuration allocated
between 3.3-PAO and 4.0-snapshot.  I.e., rather than a sysinstall field
saying, ``Which of these IRQs should I note use'', instead, ``Which should
I use''.  Or the like.


On Tue, 14 Mar 2000, Robert Watson wrote:

> 
> Yesterday I spent a fair amount of time attempting to get a 4.0 snapshot
> to install on my notebook (Dell Latitude CPi), which until now has been
> happily running 3.3-PAO.  Sadly, it seems not to like my ethernet card. 
> When installing, sysinstall provides three IRQ exclude options before
> initializing pccard support--the first option causes ep0 not to be probed;
> the second two allow it to be probed, but not work correctly.  DHCP
> succeeds, but following that the DNS lookup hangs.  It appears that the
> IRQ is set wrong such that incoming packets are not being observed by the
> IP stack, but this is just speculation.  Tcpdump running on the box next
> to it shows that outgoing packets seem to be alright.  Sysinstall's debug
> screen indicates that IRQ5 is being assigned to the card--PAO was
> allocating IRQ 3 (and it worked :-).
> 
> Any pointers--especially ones that get the install of 4.0 working ``out of
> the box'' on this notebook would be much appreciated.
> 
>   Robert N M Watson 
> 
> [EMAIL PROTECTED]  http://www.watson.org/~robert/
> PGP key fingerprint: AF B5 5F FF A6 4A 79 37  ED 5F 55 E9 58 04 6A B1
> TIS Labs at Network Associates, Safeport Network Services
> 
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
> 


  Robert N M Watson 

[EMAIL PROTECTED]  http://www.watson.org/~robert/
PGP key fingerprint: AF B5 5F FF A6 4A 79 37  ED 5F 55 E9 58 04 6A B1
TIS Labs at Network Associates, Safeport Network Services



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: current.freebsd.org snapshots and broken X11

[Robert Watson]

Sounds good to me, as long as it runs :-).

BTW, ran into another nit from the 02/13 snapshot.  I installed the
X-kern-developer distribution, discovered X11 didn't work, so went back
into sysinstall to install X11 stuff.  I selected some combination of X11
components, and chose releng3.freebsd.org as the source -- sysinstall
coredumped.  A second attempt at the same resulted in sysinstall hanging.

This seems to be reproduceable -- what can I do to give you better
debugging information?

On Tue, 14 Mar 2000, Jordan K. Hubbard wrote:

> I think I'm just going to go to the 3.4 bits; I don't have a definitive
> XFree86 distribution for 4.0 and I don't think I'm going to get one in
> time to make a difference.
> 
> - Jordan
> 
> > 
> > It looks like the X11 associated with the snapshots on current.freebsd.org
> > is still broken:
> > 
> >   /usr/libexec/ld-elf.so.1: Share object "libXThrStub.so.6" not found
> > 
> > Installing -current boxes for testing and development would be a lot
> > easier if this worked. :-)  Especially leading up to releases when testing
> > changes in the install is useful :-)
> > 
> >   Robert N M Watson 
> > 
> > [EMAIL PROTECTED]  http://www.watson.org/~robert/
> > PGP key fingerprint: AF B5 5F FF A6 4A 79 37  ED 5F 55 E9 58 04 6A B1
> > TIS Labs at Network Associates, Safeport Network Services
> > 
> > 
> > 
> > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > with "unsubscribe freebsd-current" in the body of the message
> 
> 


  Robert N M Watson 

[EMAIL PROTECTED]  http://www.watson.org/~robert/
PGP key fingerprint: AF B5 5F FF A6 4A 79 37  ED 5F 55 E9 58 04 6A B1
TIS Labs at Network Associates, Safeport Network Services



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: current.freebsd.org snapshots and broken X11

[Jordan K. Hubbard]

I think I'm just going to go to the 3.4 bits; I don't have a definitive
XFree86 distribution for 4.0 and I don't think I'm going to get one in
time to make a difference.

- Jordan

> 
> It looks like the X11 associated with the snapshots on current.freebsd.org
> is still broken:
> 
>   /usr/libexec/ld-elf.so.1: Share object "libXThrStub.so.6" not found
> 
> Installing -current boxes for testing and development would be a lot
> easier if this worked. :-)  Especially leading up to releases when testing
> changes in the install is useful :-)
> 
>   Robert N M Watson 
> 
> [EMAIL PROTECTED]  http://www.watson.org/~robert/
> PGP key fingerprint: AF B5 5F FF A6 4A 79 37  ED 5F 55 E9 58 04 6A B1
> TIS Labs at Network Associates, Safeport Network Services
> 
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Compaq SMART EISA and ida driver -> kernel panic

[Matthew N. Dodd]

On Tue, 14 Mar 2000, Oliver Schonefeld wrote:
> there we go:
> qcb = 0xc0ca7000
> completed = 0x (so propably not initalized?!)
> qcb_done = 0x0

Doh!  Looks like Jonathan didn't merge the latest ida_eisa.c that I'd
worked on when he fixed the driver to support multiple access methods and
added EISA support.

Try this patch:

Index: ida_eisa.c
===
RCS file: /cvs/src/sys/dev/ida/ida_eisa.c,v
retrieving revision 1.1
diff -u -r1.1 ida_eisa.c
--- ida_eisa.c  2000/03/08 16:16:31 1.1
+++ ida_eisa.c  2000/03/14 19:34:23
@@ -247,6 +247,7 @@
return (ENXIO);
}
 
+   eisa_add_iospace(dev, io_base, 0x100, RESVADDR_NONE);
eisa_add_iospace(dev, (io_base + IDA_EISA_IOPORT_START),
 IDA_EISA_IOPORT_LEN, RESVADDR_NONE);
 

-- 
| Matthew N. Dodd  | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD  |
| [EMAIL PROTECTED] |   2 x '84 Volvo 245DL| ix86,sparc,pmax |
| http://www.jurai.net/~winter | This Space For Rent  | ISO8802.5 4ever |


Index: ida_eisa.c
===
RCS file: /cvs/src/sys/dev/ida/ida_eisa.c,v
retrieving revision 1.1
diff -u -r1.1 ida_eisa.c
--- ida_eisa.c  2000/03/08 16:16:31 1.1
+++ ida_eisa.c  2000/03/14 19:34:23
@@ -247,6 +247,7 @@
return (ENXIO);
}
 
+   eisa_add_iospace(dev, io_base, 0x100, RESVADDR_NONE);
eisa_add_iospace(dev, (io_base + IDA_EISA_IOPORT_START),
 IDA_EISA_IOPORT_LEN, RESVADDR_NONE);
 

current.freebsd.org snapshots and broken X11

[Robert Watson]

It looks like the X11 associated with the snapshots on current.freebsd.org
is still broken:

  /usr/libexec/ld-elf.so.1: Share object "libXThrStub.so.6" not found

Installing -current boxes for testing and development would be a lot
easier if this worked. :-)  Especially leading up to releases when testing
changes in the install is useful :-)

  Robert N M Watson 

[EMAIL PROTECTED]  http://www.watson.org/~robert/
PGP key fingerprint: AF B5 5F FF A6 4A 79 37  ED 5F 55 E9 58 04 6A B1
TIS Labs at Network Associates, Safeport Network Services



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: IPv6 setup...

[Brian Somers]

> < 
>said:
> 
> >   echo 24.113.25.85 | sed -e s/"\."/" "/g | awk '{$5 = $1*256 + $2; $6 = $3*256 + 
>$4; printf "2002:%x:%x:\n", $5, $6}'
> 
> Or, without only one extra process:
> 
> myaddr=24.113.25.85
> OIFS="$IFS"
> IFS=".$IFS"
> set $myaddr
> IFS="$OIFS"
> printf "2002:%x:%x:\n" $(($1 * 256 + $2)) $(($3 * 256 + $4))

Or if you wanna be really slick

myaddr=24.113.25.85
eval IFS=".$IFS" printf '2002:%02x%02x:%02x%02x:\\n' $myaddr

:*P

> -GAWollman
> 
> --
> Garrett A. Wollman   | O Siem / We are all family / O Siem / We're all the same
> [EMAIL PROTECTED]  | O Siem / The fires of freedom 
> Opinions not those of| Dance in the burning flame
> MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick

-- 
Brian <[EMAIL PROTECTED]>
     
Don't _EVER_ lose your sense of humour !




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: cs89x0 driver update (fwd)

[Warner Losh]

In message <[EMAIL PROTECTED]> Maxim 
Bolotin writes:
: We found that our driver doesn't work with PNP in 4.0 and
: use old, shared memory softc scheme. We rewrite it for the
: new scheme, now We can install it in dev/cs and remove
: isa_compat.c lines. I belive we have to commit it before
: 4.0 release.

I suspect that it is way too late to be included in 4.0, but can be
included in 4.0-stable once 4.0 is out the door.  Since Jkh has put
down the tags already and has started building I think that it can
just goin to -current and -stable at the same time.

Max, do you have commit privs?  If not, then I'll shepard this into
the tree.  My company uses an allinone computer with the CS8900A on it
and we need support for this chip.

Warner

[[ cc'd to current so committers there know it is being worked on ]]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Compaq SMART EISA and ida driver -> kernel panic

[Oliver Schonefeld]

Eines schoenen Tages schrieb Matthew N. Dodd:
[snip]
> Could you add
> 
> printf("0x%lx\n0x%lx0x%lx\n", qcb, completed, qcb_done);
> 
> to ida.c:ida_wait() after this line:
> 
> 454:qcb_done = idahwqcbptov(ida, completed & ~3);
> 
> And show us the output.
there we go:
qcb = 0xc0ca7000
completed = 0x (so propably not initalized?!)
qcb_done = 0x0

cheers,
oliver
-- 

And remember: "To Infinity And Far Beyond ... Somehow?!"

email: [EMAIL PROTECTED]
   [EMAIL PROTECTED]

Hi! I'm a .signature virus! Copy me in your ~/.signature
to help me spread! <- Save this lifeform ;-)


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: microuptime() still going backwards (long)

[Valentin S. Chopov]

Mike,

It was just a suggestion. I'm sure in my case  the
problem was in the buggy BIOS (this is a old 486
notebook:).

Val

--- Mike Smith <[EMAIL PROTECTED]> wrote:
> 
> This shouldn't have any effect at all; I think
> you're just waving 
> chickens here.  If you can work out what is actually
> happening here it'd 
> be quite useful though - PNPBIOS may result in some
> differences in 
> resource allocation which might be salient.
> 
> > Try w/o PNPBIOS option. I  had the similar
> problem,
> > and that fixed it.
> > 
> > Val
> > 
> > -
> > I followed the suggestions from people earlier
> today. 
> > That is to
> > say that I have upgraded my BIOS to 1012, disabled
> APM
> > in the BIOS,
> > and removed 'device apm' from the  kernel config,
> > however I still
> > receive lines like:
> > 
> > calcru: negative time of 20585525 usec for pid 477
> > (cvsup)
> > 
> > and also lines about microuptime() being negative
> (I
> > think these are
> > related :)
> > 
> > Below is a dmesg and my kernel config.
> > 
> > Cheers
> > 
> > 
> > __
> > Do You Yahoo!?
> > Talk to your friends online with Yahoo! Messenger.
> > http://im.yahoo.com
> > 
> > 
> > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > with "unsubscribe freebsd-current" in the body of
> the message
> > 
> 
> -- 
> \\ Give a man a fish, and you feed him for a day. \\
>  Mike Smith
> \\ Tell him he should learn how to fish himself,  \\
>  [EMAIL PROTECTED]
> \\ and he'll hate you for a lifetime. \\
>  [EMAIL PROTECTED]
> 
> 
> 
__
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

problems using pccard 3c589c with 4.0-snap install

[Robert Watson]

Yesterday I spent a fair amount of time attempting to get a 4.0 snapshot
to install on my notebook (Dell Latitude CPi), which until now has been
happily running 3.3-PAO.  Sadly, it seems not to like my ethernet card. 
When installing, sysinstall provides three IRQ exclude options before
initializing pccard support--the first option causes ep0 not to be probed;
the second two allow it to be probed, but not work correctly.  DHCP
succeeds, but following that the DNS lookup hangs.  It appears that the
IRQ is set wrong such that incoming packets are not being observed by the
IP stack, but this is just speculation.  Tcpdump running on the box next
to it shows that outgoing packets seem to be alright.  Sysinstall's debug
screen indicates that IRQ5 is being assigned to the card--PAO was
allocating IRQ 3 (and it worked :-).

Any pointers--especially ones that get the install of 4.0 working ``out of
the box'' on this notebook would be much appreciated.

  Robert N M Watson 

[EMAIL PROTECTED]  http://www.watson.org/~robert/
PGP key fingerprint: AF B5 5F FF A6 4A 79 37  ED 5F 55 E9 58 04 6A B1
TIS Labs at Network Associates, Safeport Network Services



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: ATA timeout errors

[Patrik Sundberg]

On Tue, Mar 14, 2000 at 12:17:15PM -0500, Will Saxon wrote:
> Hello,
> 
> I think this may have already been presented/answered but I am not
> certain. I have noticed recently that every so often I will get the
> following set of messages, generally right after the bootup sequence
> finishes:
> 
> ad0: READ command timeout - resetting
> ata0: resetting devices .. done
> ad0: READ command timeout - resetting
> ata0: resetting devices .. done
> ad0: READ command timeout - resetting
> ata0: resetting devices .. done
> ad0: READ command timeout - resetting
> ata0-master: WARNING: WAIT_READY active=ATA_ACTIVE_ATA
> ad0: trying fallback to PIO mode
> ata0: resetting devices .. done
> 
> This latest episode is on a 5.0-Current machine cvsupped yesterday, I got
> those messages while trying to log in after a reboot.

I also get this when booting - think it started happening when I started
using the new ata-driver. For me it happens when the root is supposed to be
mounted (from dmesg):


atapci0:  port 0xffa0-0xffaf at device 7.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0

ad0: 2015MB  [4095/16/63] at ata0-master using WDMA2
ad2: 814MB  [1654/16/63] at ata1-master using PIO3
acd0: CDROM  at ata0-slave using PIO3
Mounting root from ufs:/dev/ad0s1a
ad0: READ command timeout - resetting
ata0: resetting devices .. done
ad0: READ command timeout - resetting
ata0: resetting devices .. done
ad0: READ command timeout - resetting
ata0: resetting devices .. done
ad0: READ command timeout - resetting
ata0-master: WARNING: WAIT_READY active=ATA_ACTIVE_ATA
ad0: trying fallback to PIO mode
ata0: resetting devices .. done

and then everything proceeds as normal.

> I dont get any panics or anything, and after the reset to PIO everything
> seems to work fine. 

agree.
 
> ad0 is an IBM Deskstar 22GXP. I recall something about Deskstars resetting
> their heads every week as a possible explanation for a similar problem, is
> that what this is too?

As you can see I am using a seagate disk and I am having the same problem.

> I would of course prefer to be in DMA mode all the time rather than
> PIO. If there is something I can do to fix this I'm all ears.

There are probably many people out there affected by this so I really think
it ought to be fixed - preferably before -RELEASE.

-- 
Patrik Sundberg  -  email: [EMAIL PROTECTED] || [EMAIL PROTECTED]
---> telefon: 013-178 567  -  mobiltelefon: 070-760 22 40 <---


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: microuptime() still going backwards (long)

[Mike Smith]

This shouldn't have any effect at all; I think you're just waving 
chickens here.  If you can work out what is actually happening here it'd 
be quite useful though - PNPBIOS may result in some differences in 
resource allocation which might be salient.

> Try w/o PNPBIOS option. I  had the similar problem,
> and that fixed it.
> 
> Val
> 
> -
> I followed the suggestions from people earlier today. 
> That is to
> say that I have upgraded my BIOS to 1012, disabled APM
> in the BIOS,
> and removed 'device apm' from the  kernel config,
> however I still
> receive lines like:
> 
> calcru: negative time of 20585525 usec for pid 477
> (cvsup)
> 
> and also lines about microuptime() being negative (I
> think these are
> related :)
> 
> Below is a dmesg and my kernel config.
> 
> Cheers
> 
> 
> __
> Do You Yahoo!?
> Talk to your friends online with Yahoo! Messenger.
> http://im.yahoo.com
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
> 

-- 
\\ Give a man a fish, and you feed him for a day. \\  Mike Smith
\\ Tell him he should learn how to fish himself,  \\  [EMAIL PROTECTED]
\\ and he'll hate you for a lifetime. \\  [EMAIL PROTECTED]




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Also... /etc/periodic/daily/200.backup-passwd and MD5 (fwd)

[Visigoth]

Did anybody get a chance to look at this and decide that it wasn't
the case or was?  I was suprised because I didn't hear _anything_ and am
wondering if I was doing something wrong...

Resubmiting...
Dameion Stark






Date: Wed, 8 Mar 2000 15:34:58 -0600 (CST)
From: Visigoth <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: /etc/periodic/daily/200.backup-passwd and MD5


All flames welcome as a learning experience ;-)

I am currently running a -current on a group of machines where I
work.  I decided to use the MD5 libscrypt passwords, and noticed something
strange in the daily output e-mail.  When the MD5 passwords are used the
daily output e-mail fails to truncate the encrypted passwd from the
/etc/master.passwd file before e-mailing out the diffs.  This is the case
even on a machine which was built today.  I haven't seen any info on
-current about it so I thought I would bring it up.

I also wrote and attached small patch to take care of the issue in
the short term. all it does is change:

diff $bak/master.passwd.bak /etc/master.passwd |\
sed 's/^\([<>] [^:]*\):[^:]*:/\1:(password):/'
to:

diff $bak/master.passwd.bak /etc/master.passwd |\
sed 's/^\([^:]*\):[^:]*:/\1:(password):/'

My logic could be messed up, so if there are any issues that I
overlooked in the patch I would love to hear about them.  I thought it
might be a good thing to take care of quick before -RELEASE (yea!)

Thanks all...

Damieon Stark
[EMAIL PROTECTED]


*** /var/backups/200.backup-passwd  Mon Feb 21 09:19:00 2000
--- /etc/periodic/daily/200.backup-passwd   Mon Feb 21 09:19:28 2000
***
*** 16,22 
  if cmp -s $bak/master.passwd.bak /etc/master.passwd; then :; else
echo "$host passwd diffs:"
diff -u $bak/master.passwd.bak /etc/master.passwd |\
!   sed 's/^\([<>] [^:]*\):[^:]*:/\1:(password):/'
mv $bak/master.passwd.bak $bak/master.passwd.bak2
cp -p /etc/master.passwd $bak/master.passwd.bak
  fi
--- 16,22 
  if cmp -s $bak/master.passwd.bak /etc/master.passwd; then :; else
echo "$host passwd diffs:"
diff -u $bak/master.passwd.bak /etc/master.passwd |\
!   sed 's/^\([^:]*\):[^:]*:/\1:(password):/'
mv $bak/master.passwd.bak $bak/master.passwd.bak2
cp -p /etc/master.passwd $bak/master.passwd.bak
  fi

ATA timeout errors

[Will Saxon]

Hello,

I think this may have already been presented/answered but I am not
certain. I have noticed recently that every so often I will get the
following set of messages, generally right after the bootup sequence
finishes:

ad0: READ command timeout - resetting
ata0: resetting devices .. done
ad0: READ command timeout - resetting
ata0: resetting devices .. done
ad0: READ command timeout - resetting
ata0: resetting devices .. done
ad0: READ command timeout - resetting
ata0-master: WARNING: WAIT_READY active=ATA_ACTIVE_ATA
ad0: trying fallback to PIO mode
ata0: resetting devices .. done

This latest episode is on a 5.0-Current machine cvsupped yesterday, I got
those messages while trying to log in after a reboot.

I dont get any panics or anything, and after the reset to PIO everything
seems to work fine. 

ad0 is an IBM Deskstar 22GXP. I recall something about Deskstars resetting
their heads every week as a possible explanation for a similar problem, is
that what this is too?

I would of course prefer to be in DMA mode all the time rather than
PIO. If there is something I can do to fix this I'm all ears.

-Will



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: XFree86-4.0 error

[Ted Sikora]

Andrey Sverdlichenko wrote:
> 
> On Tue, 14 Mar 2000, Ted Sikora wrote:
> 
> > XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24
> 
> options SHMALL=1025
> options SHMMAX="(SHMMAXPGS*PAGE_SIZE+1)"
> options SHMMAXPGS=1025
> options SHMMIN=2
> options SHMMNI=256
> options SHMSEG=128
> 
> config, make, install.
> 

Thanks. Just added it and it's fixed...after removing wdc.h from 
../../sys/i386/isa/isa_compat.h 

--
Ted Sikora
Jtl Development Group 
[EMAIL PROTECTED]
http://powerusersbbs.com


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: isa_compat.h and new lack of wdc...

[Jeroen Ruigrok van der Werven]

-On [2314 17:50], Visigoth ([EMAIL PROTECTED]) wrote:
>
>The line in /sys/i386/isa/isa_compat.h which calls for the wdc
>code is still there and causing kernel build problems.  Minor issue
>considering all of the new changes related to that driver ;)

Aye, sorry.

Got called away to a meeting, grrr...

>I attached a patch that removes the line ( for convienience ) If I
>am wrong, go easy ;) just trying to be helpful...

Yeah, applied and it should fix what you reported.

Thanks,

-- 
Jeroen Ruigrok van der Werven  Network- and systemadministrator
<[EMAIL PROTECTED]>  VIA NET.WORKS The Netherlands
BSD: Technical excellence at its best  http://www.bart.nl
To err is human, to forgive divine...


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: MAX_UID ?

[Paul Richards]

Bruce Evans wrote:
> 
> On Sun, 12 Mar 2000, John Polstra wrote:
> 
> > Sheesh, criticism isn't enough?  Now it has to be constructive too? ;-)
> >
> > I guess it could go into  in the
> > "!defined(_ANSI_SOURCE)" section.  Bruce might have a better idea.

Trying to draw some closure on this discussion.

> 
> This is the same as putting it in  in the
> "!defined(_ANSI_SOURCE)" section.  Anyway, the names should be FOO_MAX,
> not MAX_FOO.
> 
> In C99, there are about 50 *_MAX and *_MIN values defined in 
> for Standard C types alone.
> 
> I would prefer standard maxof() and minof() interfaces that work on
> any arithmetic type.  These can almost be written in portable C, at
> least in C89 where types are restricted to char, signed char, ...,
> long double:
> 
> #define isfloat(type)   ((type)0.5 != 0)
> #define issigned(type)  ((type)-1 < 0)
> #define isschar(type)   (!isfloat(type) && issigned(type) && sizeof(type) == 1)
> #define isuchar(type)   (!isfloat(type) && !issigned(type) && sizeof(type) == 1)
> ...
> #define maxof(type) ((type)(isschar(type) ? SCHAR_MAX :
> isuchar(type) ? UCHAR_MAX ...))

Where do you think these macros should go then?

Having though about this some more, although the above macros are useful
and can be used in a lot of the places where bounds checking needs to be
done, there is still probably a need to define certain constants, such
as UID_MAX, because the range of valid values may not necessarily be the
same as the range of values supported by the type.

UID_MAX being a good example, since FreeBSD does not support 32-bit UIDs
at the moment even though the kernel does. Most applications are
limiting themselves to USHRT_MAX, those applications should be fixed to
use UID_MAX, even if we still limit UID_MAX == USHRT_MAX for backwards
compatibility.

So,  seems like the right place for constants like
UID_MAX. Any disagreements there?

I guess the above macros should really be machine specific if we're
going to be pedantic. Would  be an appropriate
location for them?

Paul.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

isa_compat.h and new lack of wdc...

[Visigoth]

The line in /sys/i386/isa/isa_compat.h which calls for the wdc
code is still there and causing kernel build problems.  Minor issue
considering all of the new changes related to that driver ;)

I attached a patch that removes the line ( for convienience ) If I
am wrong, go easy ;) just trying to be helpful...

Thanks

Damieon Stark



*** /sys/i386/isa/isa_compat.h.bak  Tue Mar 14 10:45:34 2000
--- /sys/i386/isa/isa_compat.h  Tue Mar 14 10:45:17 2000
***
*** 28,34 
  
  #include "vt.h"
  #include "adv.h"
- #include "wdc.h"
  #include "mse.h"
  #include "ar.h"
  #include "cs.h"
--- 28,33 

Re: CMD640 and ATA drivers

[Jim Bloom]

And I have three machines which I was trying to use for testing -current and my
firewall.  These machines all have either a CMD640 or an RZ100 controller on the
motherboard.  (They seemed to be popular with the early Pentium machines.) The
controllers seem reliable enough to use for extended periods as test machines. 
If it gets trashed because of a controller bug, I can simply reinstall and only
lose the install time. 

I upgraded my firewall to an old Adaptec SCSI controller, but I don't care about
data integrity on the other machines.  Unfortunately, none of them are usable at
the moment because of various bugs (panics on boot, not probing the hard drive,
etc.).

Jim Bloom
[EMAIL PROTECTED]

Soren Schmidt wrote:
> 
> It worked until the latest newbus changes, I'm looking at it, but havn't
> found anything obvious yet.
> But seriously you want to get another ATA interface, the CMD640 is
> _broken_ and no software can help that, you are playing russian
> roulette with your data. Get a promise, abit or siig controller
> and use that instead...


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: XFree86-4.0 error

[Kelly Yancey]

On Tue, 14 Mar 2000, Ted Sikora wrote:

> XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24
> Any ideas on a fix. Xfree86-4.0 is solid otherwise.
> 

  There was quite some discussion about this recent on either -hackers or
-current. You should be able to find it in the archives. However, as I
recall the answer was to increase SHMMAXPGS in your kernel config.

  Kelly

--
Kelly Yancey  -  [EMAIL PROTECTED]  -  Richmond, VA
Analyst / E-business Development, Bell Industries  http://www.bellind.com/
Maintainer, BSD Driver Database   http://www.posi.net/freebsd/drivers/
Coordinator, Team FreeBSDhttp://www.posi.net/freebsd/Team-FreeBSD/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: XFree86-4.0 error

[Andrey Sverdlichenko]

On Tue, 14 Mar 2000, Ted Sikora wrote:

> XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24

options SHMALL=1025
options SHMMAX="(SHMMAXPGS*PAGE_SIZE+1)"
options SHMMAXPGS=1025
options SHMMIN=2
options SHMMNI=256
options SHMSEG=128

config, make, install.




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: 5.0-current breaks building jpeg shared library

[Vallo Kallaste]

On Tue, Mar 14, 2000 at 08:19:24AM -0800, David O'Brien <[EMAIL PROTECTED]> wrote:

> On Tue, Mar 14, 2000 at 01:30:32PM +0200, Vallo Kallaste wrote:
> > Just did switchover to 5.0-current and noticed that building jpeg shared
> 
> This belongs in [EMAIL PROTECTED]  *NOT* the freebsd-current list!!!

Yes, I did bounce the mail to freebsd-ports as well. It's current thing
also, no? Before people start emailing to this list perhaps they saw the
message and can fix it.
Sorry.
-- 

Vallo Kallaste
[EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

XFree86-4.0 error

[Ted Sikora]

XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24
Any ideas on a fix. Xfree86-4.0 is solid otherwise.

--
Ted Sikora
Jtl Development Group 
[EMAIL PROTECTED]
http://powerusersbbs.com


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: 5.0-current breaks building jpeg shared library

[David O'Brien]

On Tue, Mar 14, 2000 at 01:30:32PM +0200, Vallo Kallaste wrote:
> Just did switchover to 5.0-current and noticed that building jpeg shared

This belongs in [EMAIL PROTECTED]  *NOT* the freebsd-current list!!!


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: CMD640 and ATA drivers

[Soren Schmidt]

It seems Thomas Veldhouse wrote:
> Are there any plans to support the buggy CMD640 interface in the future
> now that 4.0-RELEASE has come and gone?  I have a box that is running 3.4
> happily, and it has this interface.  I really would like the chance to use
> some of the 4.0 features, but I can not while support for this interface
> lacks.
> 
> Right now, the code does identify the controller and give a warning about
> a buggy interface.  It then proceeds to choke and die on the CD-ROM probe.
> I will gladly post more accurate details (I have already in the past) if
> such support will eventually be [re]added.

It worked until the latest newbus changes, I'm looking at it, but havn't
found anything obvious yet.
But seriously you want to get another ATA interface, the CMD640 is
_broken_ and no software can help that, you are playing russian
roulette with your data. Get a promise, abit or siig controller
and use that instead...


-Søren


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: CMD640 and ATA drivers

[Kelly Yancey]

On Tue, 14 Mar 2000, Thomas Veldhouse wrote:

> Are there any plans to support the buggy CMD640 interface in the future
> now that 4.0-RELEASE has come and gone?  I have a box that is running 3.4
> happily, and it has this interface.  I really would like the chance to use
> some of the 4.0 features, but I can not while support for this interface
> lacks.
> 

  The old wd driver is still present in 4.0, it just isn't the default. 
You can build a custom kernel with it rather than the new ata drivers and 
you are able to get all of the other benefits of 4.0 despite your buggy
CMD640 controller. But you'll have to hurry, some are looking to put wd
on the chopping block ;)

  Kelly

--
Kelly Yancey  -  [EMAIL PROTECTED]  -  Richmond, VA
Analyst / E-business Development, Bell Industries  http://www.bellind.com/
Maintainer, BSD Driver Database   http://www.posi.net/freebsd/drivers/
Coordinator, Team FreeBSDhttp://www.posi.net/freebsd/Team-FreeBSD/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

CMD640 and ATA drivers

[Thomas Veldhouse]

Are there any plans to support the buggy CMD640 interface in the future
now that 4.0-RELEASE has come and gone?  I have a box that is running 3.4
happily, and it has this interface.  I really would like the chance to use
some of the 4.0 features, but I can not while support for this interface
lacks.

Right now, the code does identify the controller and give a warning about
a buggy interface.  It then proceeds to choke and die on the CD-ROM probe.
I will gladly post more accurate details (I have already in the past) if
such support will eventually be [re]added.

Thanks,

Tom Veldhouse
[EMAIL PROTECTED]



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP! old wd driver going away

[Soren Schmidt]

It seems Bruce Evans wrote:
> On Tue, 14 Mar 2000, Jeroen Ruigrok van der Werven wrote:
> 
> > Yes...
> > 
> > That's right.
> > 
> > Use ata and related stuff instead.
> 
> No.

Yes.

-Søren


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP! old wd driver going away

[Matthew N. Dodd]

On Wed, 15 Mar 2000, Andy Farkas wrote:
> Fortunately, I can switch to using a SCSI disk on my DPT PM2022 EISA card,
> which is now supported - but only with 1 disk! (the driver does not work
> with a LUN != 0)

I think you mean 'ID != 0'.

'camcontrol rescan 0:n:0' will make the other devices show
up.  Really weird.  Don't blame me.

-- 
| Matthew N. Dodd  | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD  |
| [EMAIL PROTECTED] |   2 x '84 Volvo 245DL| ix86,sparc,pmax |
| http://www.jurai.net/~winter | This Space For Rent  | ISO8802.5 4ever |



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP! old wd driver going away

[Bruce Evans]

On Tue, 14 Mar 2000, Jeroen Ruigrok van der Werven wrote:

> Yes...
> 
> That's right.
> 
> Use ata and related stuff instead.

No.

Bruce



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP! old wd driver going away

[Andy Farkas]

Damn.  I'm gonna miss my faithful, old (circa 1993), worksation (dual P90,
Intel Neptune based PCI+EISA), with a crappy "TEKRAM DC-6X0X IDE cacheing
controller" in it.  Been using this thing since 3.0-current when SMP was
first introduced...(it was previously running OS/2 2.1 SMP)

Fortunately, I can switch to using a SCSI disk on my DPT PM2022 EISA card,
which is now supported - but only with 1 disk! (the driver does not work
with a LUN != 0)

> Yes...
> 
> That's right.
> 
> Use ata and related stuff instead.
> 
> -- 
> Jeroen Ruigrok van der Werven  Network- and systemadministrator
> <[EMAIL PROTECTED]>  VIA NET.WORKS The Netherlands
> BSD: Technical excellence at its best  http://www.bart.nl
> In my Dreams, I see you, I can tell you, how I feel...
> 

--
 
 :{ [EMAIL PROTECTED]
  
Andy Farkas
System Administrator
   Speednet Communications
 http://www.speednet.com.au/
  




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: 4.0R ?

[Tom Embt]

At 19:05 03/13/2000 +, Ben Smithurst wrote:
>Jim Bloom wrote:
>
>> The tag was laid down earlier today.  Here is what my current kernel
>> claims to be at the moment:
>
>I saw the RELENG_4 tag in my cvsup log, but I don't think that's the
>same as the 4.0 release tag is it? That would be RELENG_4_0_0_RELEASE
>surely.
>

I believe RELENG_4 would refer to the 4.x-STABLE branch (??maybe??), since
it is different from 5.0-CURRENT but still not ready for it's first release.

I'm no authority on the subject, though.



Tom Embt
[EMAIL PROTECTED]



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

HEADS UP! old wd driver going away

[Jeroen Ruigrok van der Werven]

Yes...

That's right.

Use ata and related stuff instead.

-- 
Jeroen Ruigrok van der Werven  Network- and systemadministrator
<[EMAIL PROTECTED]>  VIA NET.WORKS The Netherlands
BSD: Technical excellence at its best  http://www.bart.nl
In my Dreams, I see you, I can tell you, how I feel...


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: MAX_UID ?

[Peter Dufault]

> If this was comp.std.c, then I'd agree that such constructs may fail
> in some environments.  It's not so clear that we need to worry about
> this here (this being FreeBSD)...

No, system headers should be sticklers to the standard to remain
friendly to architectures BSD won't run on but the headers might
be useful for.

I can imagine non-byte addressable floating point DSPs with
sizeof(char) == sizeof(double).

I won't complain about the headers in a machine subdirectory.

--

Peter Dufault ([EMAIL PROTECTED])   Realtime development, Machine control,
HD Associates, Inc.   Fail-Safe systems, Agency approval


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

5.0-current breaks building jpeg shared library

[Vallo Kallaste]

Hello

Just did switchover to 5.0-current and noticed that building jpeg shared
library doesn't work. Lots of X apps depend on jpeg shared library. The
fix is very small, just edit patch-ac to include freebsd5* as well.
Just FYI.
-- 

Vallo Kallaste
[EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

PCI Audio - ESS Solo1

[Steve O'Hara-Smith]

Hi,

I know this little beasty isn't supported (yet) and I saw some comments
about it on the -multimedia archive. I am stuck with one and I would like to
make it work (at least as an SBPro emulation). I have enough docs on the card
to do that I think but I don't know what it takes to attach a PCI device to the
ISA SB code, do I just have to recognise it and put it into compatability mode
and then let the ISA probe find it or is there more to do than that ?

I am sure that making it work properly (with all features) is a lot more
work but I don't need that right now. Having basic audio working would be nice.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

cs89x0 driver update (fwd)

[Maxim Bolotin]

Hi,

We found that our driver doesn't work with PNP in 4.0 and
use old, shared memory softc scheme. We rewrite it for the
new scheme, now We can install it in dev/cs and remove
isa_compat.c lines. I belive we have to commit it before
4.0 release.

Regards,
Max. 

-
Rostov State University   Computer Center
Rostov-on-Don, +7 (8632) 285794 or 357476
Russia, RUNNet, MAB1-RIPE  [EMAIL PROTECTED]


/*
 * Copyright (c) 1997,1998 Maxim Bolotin and Oleg Sharoiko.
 * All rights reserved.
 *
 * Redistribution and use in source and binary forms, with or without
 * modification, are permitted provided that the following conditions
 * are met:
 * 1. Redistributions of source code must retain the above copyright
 *notice unmodified, this list of conditions, and the following
 *disclaimer.
 * 2. Redistributions in binary form must reproduce the above copyright
 *notice, this list of conditions and the following disclaimer in the
 *documentation and/or other materials provided with the distribution.
 *
 * THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
 * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
 * ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
 * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
 * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
 * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
 * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
 * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 * SUCH DAMAGE.
 *
 */

/*
 * $FreeBSD: src/sys/i386/isa/if_cs.c,v 1.14 1999/09/25 12:05:52 phk Exp $
 *
 * Device driver for Crystal Semiconductor CS8920 based ethernet
 *   adapters. By Maxim Bolotin and Oleg Sharoiko, 27-April-1997
 */

/*
#define  CS_DEBUG 
 */

#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 

#include 
#include 
#include 
#include 
#include 

#include 
#include 
#include 
#include 

#include 

#include 

#ifdef BRIDGE
#include 
#endif

#include 

#include 

#ifdef  CS_USE_64K_DMA
#define CS_DMA_BUFFER_SIZE 65536
#else
#define CS_DMA_BUFFER_SIZE 16384
#endif

/*
 * cs_softc: per line info and status
 */
struct cs_softc {

/* Ethernet common code */
struct arpcom arpcom;

/* Configuration words from EEPROM */
int auto_neg_cnf;   /* AutoNegotitation configuration */
int adapter_cnf;/* Adapter configuration */
int isa_config; /* ISA configuration */
int chip_type;  /* Type of chip */

struct ifmedia media;   /* Media information */

int port_rid;   /* resource id for port range */
int port_used;  /* nonzero if ports used */
struct resource* port_res;  /* resource for port range */
int mem_rid;/* resource id for memory range */
int mem_used;   /* nonzero if memory used */
struct resource* mem_res;   /* resource for memory range */
int irq_rid;/* resource id for irq */
struct resource* irq_res;   /* resource for irq */
void*   irq_handle; /* handle for irq handler */

int nic_addr;   /* Base IO address of card */
int send_cmd;
int line_ctl;   /* */
int send_underrun;
void*recv_ring;

unsigned char *buffer;
int buf_len;
};

static int  cs_recv_delay = 570;
SYSCTL_INT(_machdep, OID_AUTO, cs_recv_delay, CTLFLAG_RW, &cs_recv_delay, 0, "");

static int  cs_isa_probe__P((device_t dev));
static int  cs_isa_attach   __P((device_t dev));

static int  cs_cs89x0_probe __P((device_t dev));

driver_intr_t   csintr;

static int  cs_attach   __P((struct cs_softc *, int, int));

static void cs_init __P((void *));
static int  cs_ioctl__P((struct ifnet *, u_long, caddr_t));
static void cs_start__P((struct ifnet *));
static void cs_stop __P((struct cs_softc *));
static void cs_reset__P((struct cs_softc *));
static void cs_watchdog __P((struct ifnet *));

static int  cs_alloc_port(device_t dev, int rid, int size);
static int  cs_alloc_memory(device_t dev, int rid, int size);
static int  cs_alloc_irq(device_t dev, int rid, int flags);
static void cs_release_resources(device_t dev);

stat

Re: microuptime() still going backwards (long)

[Eric D. Futch]

I hate to say "me too" but I saw this for the first time today with cvsup 
crunching away. The motherboard is a Intel PR440FX (SMP).  I don't have
APM enabled at all.  I just thought it was ntp4 playing tricks :)

FreeBSD quake.nyct.net 4.0-CURRENT FreeBSD 4.0-CURRENT #3: Sat Mar 11
18:56:11 EST 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/QUAKE
i386

calcru: negative time of 993098931 usec for pid 98502 (cvsup)
calcru: negative time of 993098931 usec for pid 98502 (cvsup)

--
Eric Futch  New York Connect.Net, Ltd.
[EMAIL PROTECTED] Technical Support Staff
http://www.nyct.net (212) 293-2620
"Bringing New York The Internet Access It Deserves"



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message