-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
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 pc
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.
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 Po
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-sn
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 instal
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
vi
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-
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.
>
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/e
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 wor
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 sy
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 mo
[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
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.
>
< 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
--
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
> > i
* 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 t
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 cop
[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
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
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:
::
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 coul
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.
Th
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
< 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;
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 auth
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([
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
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 ma
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
re
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 dr
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 cdcontr
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):
>
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 fre
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
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
speciali
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 i
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 wi
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
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.o
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/libexe
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
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 wh
> <
>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
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 r
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
com
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
>
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
initializ
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:
>
>
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 simila
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 <[E
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:
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
> option
-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 call
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 discu
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 ;)
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 perio
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.
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
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!
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
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 th
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
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 feature
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
lack
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 mes
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 sho
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
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
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 RELEN
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 tel
> 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 hea
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
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
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
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 2
77 matches
Mail list logo
