Hi,
I'm getting the following errors when doing a 'make buildkernel':
/mnt/usr/src/sys/modules/sound/driver/cmi/../../../../dev/sound/pci/cmi.
c: In function `cmi_init':
/mnt/usr/src/sys/modules/sound/driver/cmi/../../../../dev/sound/pci/cmi.
c:747: `CMPCI_REG_N4SPK3D' undeclared (first use in t
I have more to report since the original posting, which was..
On Sat, 7 Apr 2001, Jim Durham wrote:
> I am trying an Adaptec scsi controller (AIC6360) with
> 4.3RC2.
>
> It does not work correctly with the out of the box pccard.conf.
>
> However, more importantly, pulling the card has twice p
On Wed, Apr 04, 2001 at 09:32:39PM -0500, Brian D. Woodruff wrote:
> I quickly learned that RC is for Release Candidate, which would inticate to
> me that it's somewhere between CURRENT and RELEASE, but nowhere near STABLE!!
Huh? RC means it could easily be _the_ RELEASE. In FreeBSD RC is more
Hi
Make sure that you have x11/wrapper installed. You can build it from the
ports collection.
kt
Sean M Hollingsworth wrote:
>
> I'm running FreeBSD 4.3-RC and XFree86-4.0.3 from the ports collection. If
> I start X as root, everything is fine. If I start X as any other user, I
> get this e
On 7 Apr 2001, at 22:35, Sean M Hollingsworth wrote:
> I'm running FreeBSD 4.3-RC and XFree86-4.0.3 from the ports collection. If
> I start X as root, everything is fine. If I start X as any other user, I
> get this error message:
>
> Fatal server error:
> Cannot open log file "/var/log/XFree8
I'm running FreeBSD 4.3-RC and XFree86-4.0.3 from the ports collection. If
I start X as root, everything is fine. If I start X as any other user, I
get this error message:
Fatal server error:
Cannot open log file "/var/log/XFree86.0.log"
/var/log/XFree86.0.log has perms 0644. Are these the co
Mike Barton <[EMAIL PROTECTED]> types:
> Are there any issues with placing swap first on the hard drive? Unless you
> insist on filling the drive, it seems to me that this swap arrangement would
> result in less stack travel.
Not that I know of. In fact, I'm pretty sure that one of my systems
has
* Robert <[EMAIL PROTECTED]> [010407 20:52] wrote:
>
>
> I can say with some certainty that the sti driver in 4.3-RC doesn't work. It
> for the Stallion EasyIO-4/8 boards. It amy have worked under earlier
> versions of the ststem, but it soesn't work under this one.
> It _almost_ works. It can s
I can say with some certainty that the sti driver in 4.3-RC doesn't work. It
for the Stallion EasyIO-4/8 boards. It amy have worked under earlier
versions of the ststem, but it soesn't work under this one.
It _almost_ works. It can signal the modem, signalling DTR, but apart from
that there is n
Hi,
I have the same problem too. Let me guess, your disk is an IBM DTLA
(ATA100). I believe this is due to incompatibility between HPT366 and IBM's
ATA100 disks.
HPT claims that the latest BIOS solved this problem but it didn't work for
me. I'm now avoiding HPT's controllers like plague.
kt
Are there any issues with placing swap first on the hard drive? Unless you
insist on filling the drive, it seems to me that this swap arrangement would
result in less stack travel.
- Original Message -
From: "Mike Meyer" <[EMAIL PROTECTED]>
To: "The Babbler" <[EMAIL PROTECTED]>
Cc: "Raspu
Hi!
Im running 4.2-RELEASE on an Abit BP6 with a 20G IBM connected to the
onboard HPT366-UDMA66 controller. During heavy disk-io I get a
read-command timed out error message and now Id like to know if this is
due to a know driver bug in 4.2-R or maybe a hardware problem.
Please let me know if yo
12 matches
Mail list logo