On Sat, 25 Jun 2005 15:58, Mark Kirkwood wrote:
I have experienced this (since about 5.3) on a dual PIII Tyan S1834. In
my case perseverance seems to pay off - one in (approx) 10 boots will
work...
Hmm strange..
I tried it a few times on an ABit AV8, once on an Epox 8KRDA+ and a few times
on
On Sun, 19 Jun 2005, Robert Watson wrote:
there is a PR for it : kern/74319
This sounds very similar to a serial console related tty bug I was
experiencing on -STABLE a few months ago, and that is believed may have been
worked around in 5.4 tweaks before release. In particular, that there
On Fri, 2005-06-24 at 23:43 -0700, Leland wrote:
I have got to be doing someting wrong, it is right in front of me and I just
don't seel it.
Hope someone can help, thanks.
From a clean install of 4.11-RELEASE with All Distributions,
cvsup-without-gui was then installed from ports.
cvsup
Johny Mattsson wrote:
Basically, the problem seems to be related to using more than one
channel on the IDE controller.
This isn't a solution to my problem. I only have one hard drive.
It's 120GB Seagate. We seem to have different problems, btw.
I also don't think, my problem is ATA-related.
On Sat, 2005-06-25 at 11:22 +0200, Andreas Rudisch wrote:
On Fri, 2005-06-24 at 23:43 -0700, Leland wrote:
I have got to be doing someting wrong, it is right in front of me and I just
don't seel it.
Hope someone can help, thanks.
From a clean install of 4.11-RELEASE with All
Accidentally I set this variable to 0 and it causes a hard lock (FreeBSD
5.4-RELEASE-p2)
could someone check if this reproducible in their test machines so I can
open a pr?
/---/
Geom name: datos
State: COMPLETE
Components: 3
Flags: ROUND-ROBIN
GenID: 0
SyncID: 3
ID: 3217021940
Daniel O'Connor wrote:
Hmm strange..
I tried it a few times on an ABit AV8, once on an Epox 8KRDA+ and a few times
on an Epox nForce2 board (I can't remember exactly which model) and it has
never worked. They all have AWARD BIOSen (if it matters)
I wonder if it's a problem where a memory
On Sat, 25 Jun 2005 19:54, Mark Kirkwood wrote:
I wonder if it's a problem where a memory area is overwritten because
there is more info from the BIOS than expected (ie floppy, CDROM, RAID).
Sounds like a promising possibility (good pun too) - as removing the
:)
RAID card (in my case a
Warren,
Why are you building xfree86? FreeBSD 5.4 uses Xorg. It's
just about the same code just different licensing. I don't think the
FreeBSD
core is bothering to keep the xfree86 port working on FreeBSD 5.X
just FreeBSD 4.11
Ted
-Original Message-
From: [EMAIL PROTECTED]
On Fri, Jun 24, 2005 at 02:13:38AM +, Balgansuren.B wrote:
Hello,
I have driver disk for the Windows 98/Me/2000/XP of the Buffalo
WLI-PCI-G54 wireless NIC.
If possible I want to know ndiscvt command convert Windows driver
to FreeBSD driver module.
Cool, hey anybody write vxd2ko.exe.
On Sat, Jun 25, 2005 at 09:14:26AM -0700, Ted Mittelstaedt wrote:
Why are you building xfree86? FreeBSD 5.4 uses Xorg. It's
just about the same code just different licensing. I don't think the
FreeBSD core is bothering to keep the xfree86 port working on FreeBSD 5.X
just FreeBSD 4.11
I'm
I had a READ_DMA timeout situation which I'm pretty sure was
related to a drive problem.
I'm running 5.3-RELEASE-p5 on an older machine (333 MHz AMD
K6). The 20 GB hard drive in this system periodically, but
only occasionally, gave READ_DMA timeout errors. These errors
sometimes cited identical
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Mark Linimon
Sent: Saturday, June 25, 2005 11:25 AM
To: Ted Mittelstaedt
Cc: Daniel O'Connor; freebsd-stable@freebsd.org; Warren;
freebsd-questions@freebsd.org
Subject: Re: Portupgrade in Xfree86 pkg failed
On Sun, 26 Jun 2005 7:45 am, Ted Mittelstaedt wrote:
But the plain fact of the matter is that the Open Source community
isn't going to tolerate what xfree86 tried doing, and the users of
open source, which is you and I, are not served by splitting development
between 2 forks of X Windows. The
On Sat, Jun 25, 2005 at 02:45:45PM -0700, Ted Mittelstaedt wrote:
I'm sorry to step on the toes of the port maintainer but instead
of complaining about it you need to respond to the realitites.
In general I would rather do that than argue, yes.
make: don't know how to make /drm.h. Stop
***
-Original Message-
From: Mark Linimon [mailto:[EMAIL PROTECTED]
Sent: Saturday, June 25, 2005 3:51 PM
To: Ted Mittelstaedt
Cc: Mark Linimon; Daniel O'Connor; freebsd-stable@freebsd.org; Warren;
freebsd-questions@freebsd.org
Subject: Re: Portupgrade in Xfree86 pkg failed
On Sat, Jun 25,
Daniel O'Connor wrote:
I find even disconnecting the drives so no RAID is detected works - ie it's
not the presence of the card per se that is a problem.
Good test - I had not tried that.
In addition, I can confirm your observation that merely deleting the
array makes the loader work
Hi,
I am updating an old 4.x system to 5.4 here and it has a Promise FT100TX2 RAID
controller (in mirror).
The problem is that when I boot the CD the loader crashes (does a reg dump)
but only if the card is present and an array is defined. I can't record what
the dump is because it continually
I'm trying to install 5.4-RELEASE off of CDROM on an ASUS P5S800 motherboard
with a SATA drive in it. The SATA drive shows up as ad4 during the install
process, and the install goes just fine.
But the resulting system fails to boot. It goes through the boot sequence,
draws the cute 5.x booto
I have experienced this (since about 5.3) on a dual PIII Tyan S1834. In
my case perseverance seems to pay off - one in (approx) 10 boots will
work...
Mark
Daniel O'Connor wrote:
Hi,
I am updating an old 4.x system to 5.4 here and it has a Promise FT100TX2 RAID
controller (in mirror).
The
I have got to be doing someting wrong, it is right in front of me and I just
don't seel it.
Hope someone can help, thanks.
From a clean install of 4.11-RELEASE with All Distributions,
cvsup-without-gui was then installed from ports.
cvsup -g -L 2 cvs-supfile will produce
Hi all,
Today I've taken a fresh stab at the problem (I'm never at my best at
5am in the morning having worked through the night), and I have managed
to come up with what appears to amount to a successful workaround. It
would be good if my observations could be confirmed by someone else.
22 matches
Mail list logo
