Displaying 14 results from an estimated 14 matches for "math_emulation".
2007 Apr 18
4
[RFC, PATCH 2/24] i386 Vmi config
...6 +348,7 @@ config TOSHIBA
config I8K
tristate "Dell laptop support"
+ depends on !X86_VMI
---help---
This adds a driver to safely access the System Management Mode
of the CPU on the Dell Inspiron 8000. The System Management Mode
@@ -569,6 +596,7 @@ config HIGHPTE
config MATH_EMULATION
bool "Math emulation"
+ depends on !X86_VMI
---help---
Linux can emulate a math coprocessor (used for floating point
operations) if you don't have one. 486DX and Pentium processors have
@@ -760,7 +788,7 @@ source kernel/power/Kconfig
source "drivers/acpi/Kconfig"...
2007 Apr 18
4
[RFC, PATCH 2/24] i386 Vmi config
...6 +348,7 @@ config TOSHIBA
config I8K
tristate "Dell laptop support"
+ depends on !X86_VMI
---help---
This adds a driver to safely access the System Management Mode
of the CPU on the Dell Inspiron 8000. The System Management Mode
@@ -569,6 +596,7 @@ config HIGHPTE
config MATH_EMULATION
bool "Math emulation"
+ depends on !X86_VMI
---help---
Linux can emulate a math coprocessor (used for floating point
operations) if you don't have one. 486DX and Pentium processors have
@@ -760,7 +788,7 @@ source kernel/power/Kconfig
source "drivers/acpi/Kconfig"...
2008 Jun 07
1
using /dev/hda system to build initrd for /dev/sda system
I think I have booting issues for my custom kernel on centos 4. the sda
system cannot find the disk.
I used a qemu image to build a centos 4 MATH_EMULATION kernel.
This system has /dev/hda.
The system I am putting the vmlinuz and initrd files on is a /dev/sda
system.
I dont think the initrd image is getting built correctly.
Does this make sense?
What might I look at changing to ensure my initrd is made correctly.
Jerry
2003 Jun 04
1
Broken -STABLE kernel build?
Is anyone else seeing this:
perl @/kern/makeops.pl -h @/opencrypto/crypto_if.m
rm -f .depend
mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/../include -I/usr/obj/usr/local/src-STABLE/src/i386/usr/include /usr/local/src-STABLE/src/sys/modules/hifn/../../dev/hifn/hifn7751.c
/usr/local/src-STABLE/src/sys/modules/hifn/../../dev/hifn/hifn7751.c:47: opt_hifn.h: No such file or
2003 Jul 17
1
device troubles after stable update
After updating my kernel from a 4.7-stable to 4.8-stable update, my SB PCI128 is no longer recognized by the pcm driver.
Here is my dmesg:
FreeBSD 4.8-STABLE #0: Thu Jul 17 14:13:52 CDT 2003
root@hautlos.stout.osu-res.okstate.edu:/usr/obj/usr/src/sys/GENERIC
Timecounter "i8254" frequency 1193182 Hz
CPU: AMD Athlon(tm) Processor (800.03-MHz 686-class CPU)
Origin =
2003 Sep 11
5
FreeBSD 4.9-PRE+ nvidia
Hello all.
I have the same problem as described by Dmitry a day ago in a topic similar.
I am able to use x11 with base driver "nv" but when I load "nvidia" driver,
startx
simply crash my machine and reboot after 5 seconds. I have a similar log
file as reported by Dmitry even using startx+logverbose option. XF86Config
file is similar,except it is not the same nvidia video
2003 Aug 01
0
gdb coredumps
Hi,
After kernel panic I couldn't get gdb work properly.
msi$ uname -sr
FreeBSD 4.7-RELEASE
msi$ gdb -k /usr/src/sys/compile/MSINW/kernel.debug vmcore.0
GNU gdb 4.18 (FreeBSD)
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public
License, and you are welcome to change it and/or distribute copies of it under
certain conditions.
Type "show
2003 Jul 27
2
SMP Problems with 4.8-RELEASE
Hello,
I have the following hardware configuration.
Tyan 2466N motherboard, 1.03 BIOS, 2 Athlon-MP 1800+ CPUs, 512MB registered
ECC DRAM, Onboard 3Com NIC (xl type)
Radeon 8500 AGP video card
Adaptec 3210S SCSI RAID controller
Comtrol RocketPort 8 port PCI serial card
I have started to experience some odd system lockups in the past couple
months, and it seems to be getting worse. I particular,
2003 Oct 01
0
AC-97 problem between RELENG_4_8 and RELENG_4
Sorry if this is a known problem...
I've been tracking RELENG_4 on my Toshiba laptop for a while now; a
couple of months ago (not sure when) my sound stopped working. More
specifically, when it gets to the pcm probe, the boot hangs. I
dual-boot with WinXP and figured that somehow XP had hosed the
hardware, so I wrote it off.
Today, I made world with RELENG_4_8, and voila, my sound's
2003 Apr 07
1
kmem_malloc crash with 4.8
Hi. I've recently borrowed a SuperMicro 6013P-8 from a vendor
for the purposes of testing it to see if FreeBSD and these machines will
make a good replacements for our current flock of 11 Netra T1s running
solaris. Things are going very well with the tests, with the glaring
exception of the following crash:
While doing some significant disk operations: du, deleting a different
part of the
2003 Apr 10
2
Crash dump in umount
Hello.
I'm having a 4.7Rp9 server which is since months quite unstable, so I've compiled a debug kernel and got a crash dump.
I'm a programmer and I know a little how to use gdb, I'm not so expert about FreeBSD kernel insides however, so I can't
get much from it. Any kind of help is appreciated.
This is the crash message:
IdlePTD at phsyical address 0x0032f000
initial pcb
2007 Apr 18
33
[RFC PATCH 00/33] Xen i386 paravirtualization support
Unlike full virtualization in which the virtual machine provides
the same platform interface as running natively on the hardware,
paravirtualization requires modification to the guest operating system
to work with the platform interface provided by the hypervisor.
Xen was designed with performance in mind. Calls to the hypervisor
are minimized, batched if necessary, and non-critical codepaths
2007 Apr 18
43
[RFC PATCH 00/35] Xen i386 paravirtualization support
Unlike full virtualization in which the virtual machine provides
the same platform interface as running natively on the hardware,
paravirtualization requires modification to the guest operating system
to work with the platform interface provided by the hypervisor.
Xen was designed with performance in mind. Calls to the hypervisor
are minimized, batched if necessary, and non-critical codepaths
2007 Apr 18
43
[RFC PATCH 00/35] Xen i386 paravirtualization support
Unlike full virtualization in which the virtual machine provides
the same platform interface as running natively on the hardware,
paravirtualization requires modification to the guest operating system
to work with the platform interface provided by the hypervisor.
Xen was designed with performance in mind. Calls to the hypervisor
are minimized, batched if necessary, and non-critical codepaths