On Wed, Dec 22, 1999 at 08:47:03PM +0100, Wilko Bulte wrote:
[...]
When I reboot the system from the /boot/loader
command line (with `reboot'), the system is
being resetted, the kernel loads and starts,
and when the FPU is being initialized the kernel
traps.
[...]
Works fine on my Asus
Sean-Paul Rees wrote in list.freebsd-stable:
Is there a MMX enabled setiathome for us with non-3DNow! enhanced
processors?
No, MMX is completely useless for this kind of stuff, because
MMX does not support floating point operations. Sorry.
However, I modified the FFT algorithm to optimize
Oliver Fromme wrote:
Sean-Paul Rees wrote in list.freebsd-stable:
Is there a MMX enabled setiathome for us with non-3DNow! enhanced
processors?
No, MMX is completely useless for this kind of stuff, because
MMX does not support floating point operations. Sorry.
However, I modified
On Wed, Dec 22, 1999 at 11:26:32PM +0100, Oliver Fromme wrote:
Wilko Bulte wrote in list.freebsd-stable:
On Mon, Dec 20, 1999 at 07:36:31PM +0100, Oliver Fromme wrote:
About 50%, that is, about 4.5 hours (instead of 9) on average
per work unit, on an Athlon-500. And I did only
On Wed, Dec 22, 1999 at 11:27:41PM +0100, Bjoern Fischer wrote:
On Wed, Dec 22, 1999 at 08:47:03PM +0100, Wilko Bulte wrote:
[...]
When I reboot the system from the /boot/loader
command line (with `reboot'), the system is
being resetted, the kernel loads and starts,
and when the FPU
I believe I've already replied to this; it does indeed appear to be a
BIOS bug. The 'reboot' loader command simply re-invokes the bootstrap
interrupt, it doesn't attempt a complete system restart. It seems that
some BIOSsen don't deal with this very well.
this may be a BIOS/Mainboard
On Tue, 21 Dec 1999, Mike Smith wrote:
The third update to the Mylex PCI:SCSI RAID controller driver for
FreeBSD-3.x-STABLE is now available at
http://www.freebsd.org/~msmith/RAID/mylex/mlx-stable-991221.tar.gz
According to the README:
Copy the files mlx.c, mlxvar.h,
On Tue, 21 Dec 1999, Ben WIlliams wrote:
Tuesday, December 21, 1999
So that's a "Yes you need [br]oot fixit"? (I actually tried it
with wd0s1a too and got the same effect.) I'll just take my disks next
time I go up to see the
Does FeeBSD/Alpha run reliably on an AXPpci33 with Quantum
Fireball (SCSI)?
Yes; we do test installs onto one (although I think it has a 2GB Empire
in it at the moment, the furball was too small).
--
\\ Give a man a fish, and you feed him for a day. \\ Mike Smith
\\ Tell him he should
Seems like /bin/test is broken after cvsup on Dec 16:
$ /bin/test 1 -ne 0 ]
[: ]: unexpected operator
--
Vlad Skvortsov, [EMAIL PROTECTED], [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the
On 1999-Dec-23 12:09:49 +1100, Vlad Skvortsov [EMAIL PROTECTED] wrote:
Seems like /bin/test is broken after cvsup on Dec 16:
$ /bin/test 1 -ne 0 ]
[: ]: unexpected operator
What behaviour were you expecting? That command should have been
expressed as either:
$
Can you please download the latest (4.0.98h, as I recall) NTP code from
either:
http://www.ntp.org
or
ftp://ftp.udel.edu/pub/ntp/testing/
run:
% configure
% make
# ntpd/ntpd (assuming ntpd is not currently running)
did all that, or the equivalent (ran it
Did ``boot -s'' and ran tunefs but got an error:
Enter full pathname of shell or RETURN for /bin/sh:
# pwd
/
# tunefs -n enable /usr
tunefs: soft updates set
tunefs: /dev/rda1s1e: reload: Invalid argument
What caused this? There's no reference in the manpage.
I've seen it on some IDE drives,
13 matches
Mail list logo
