On Wed, Aug 23, 2000 at 11:02:46AM -0700, Rich Wales wrote:
> OK, I did a bit more research on this problem.
>
> The reason 4.1-RELEASE "ipfw" fails with a 4.1-STABLE kernel appears to
> be because struct ip_fw (in netinet/ip_fw.h) has had two new elements
> added in the middle (u_char fw_tcpopt,
OK, I did a bit more research on this problem.
The reason 4.1-RELEASE "ipfw" fails with a 4.1-STABLE kernel appears to
be because struct ip_fw (in netinet/ip_fw.h) has had two new elements
added in the middle (u_char fw_tcpopt, fw_tcpnopt). As a result, the
"setsockopt" calls in "ipfw" failed wi
I've exeprienced the same behavior with bad RAM in the system. Did you ever have this
box running rock solid before?
If not, consider replacing various part of your box to determine faulty hardware.
Also, did you compile custom kernel?
You can also try enabling kernel dumps to see where it scr
Hello,
Im running a 4.1-STABLE machine which is very recently cvs'uped. The
hardware is an Athlon running on a FIC motherboard. I am receiving random
reboots every like 3 days or so. Sometimes sooner sometimes later. Has
anyone ever experienced these problems or know what could be the r
On Wed, Aug 23, 2000 at 06:18:02PM +0200, Graham Wheeler wrote:
>
> Its definitely being loaded. If I put commands in to configure the PCI
> cards, they work. Its just the commands that I would use in kernelconfig
> to configure an ISA card are causing syntax errors. So either the format
> should
I'm attempting to build the plugger port, and it comes back with this
error:
make plugger.so CC=gcc XCFLAGS='-fpic -aout' LD=gcc XLDFLAGS='-shared -aout'
gcc -shared -aout -o plugger.so plugger.o common.o
ld: c++rt0.o: No such file or directory
*** Error code 1
I'm guessing c++rt0.o is from the
I know that but the documentation of the mothercard (Asus P3V4X
JumperFree) says:
"UDMA66/Support: Comes with an on board PCI bus Master Controller with 2
connectors that support 4 IDE devices on 2 channel. Support UDMA 66, UDMA
33 PIO mode 3 & 4 and bus master IDE DMA mode 2."
But freebsd does
On Wed, Aug 23, 2000 at 08:27:59AM -0700, Rich Wales wrote:
> Does this sound like expected behavior? I would have thought that
> a 4.1-STABLE kernel (and modules) would still be compatible with the
> 4.1-RELEASE userland binaries; is this not the case? Did I do some-
> thing obviously wrong her
David Scialom wrote:
>
> I have also the problem that my FreeBSD does not recognize my Matrox
> hard disk drive which is UDMA 66 and is connected to the first
[snip]
> atapci0: port 0xd800-0xd80f at device
> 4.1 on pci0
> ata0: at 0x1f0 irq 14 on atapci0
> ata1: at 0x170 irq 15 on atapc
I have also the problem that my FreeBSD does not recognize my Matrox
hard disk drive which is UDMA 66 and is connected to the first
controller with a 80 pin cable. FreeBSD use only the drive with the UDMA
33 mode ( see my dmesg output below).
It possible that the reason is that there is a second
obviously please ignore my previous message. How embarassing...
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
subscribe [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
fingers stated:
: Hi all
:
: Ok, I've unfortunately got an onboard sound card of sorts. According to
: the bios, it's a "legacy SoundBlaster". Now I've tried reading varios
: doc's, but most of them are outdated.
:
: /usr/src/sys/i386/isa/sound/sound.doc talks about:
:
: Instructions on using a
13 matches
Mail list logo
