similar to: problems with i2o on XEN kernel when using high memory support in kernel

A Pre-Alpha release of a new i2o OSM for FreeBSD is now available for testing. Check http://simon-shapiro.org/drivers.html for details. -- Sincerely Yours, Shimon@Simon-Shapiro.ORG 404.664.6401 Simon Shapiro Unwritten code has no bugs and executes at twice the speed of mouth This is the moderated mailing list freebsd-announce.

Hi, following system: Dell PE2650, 2 2.4ghz Xeon, 1gb ram, Dell Perc4DC Controller It has EL5 installed, but I wanted to change to Centos because of the missing workstation packages in the entry server repository. The system was redhat up2date until yesterday, so the latest kernel was missing. I changed redhat-release to centos-release packages and the new centos kernel was installed the via

I've just made (yet another) CentOS 4 installation. The install process seems to go fine, however the machine doesn't wan't to boot. The system in question has one of I2O Adaptec RAID controllers. I've configured LVM with one volume group and several volumes. If I boot into the rescue mode, all looks fine and dandy. Anaconda finds the installation, and I can access all

Hi I'm doing a network install of Dovecot 1.1.2. All is fine apart from a little annoying mistake I've found: I do this: > ./configure --prefix=/appli/tools_Linux/dovecot/1.1.2 --localstatedir=/var && make && make install however, since the --localstatedir is equal to a default value, it is still being constructed as "PREFIX/var" for some reason and in

Hi all, Imagine an NFS mounted read-only file system containing directories full of plain mboxes. Any recommendations on how to approach the access with dovecot? I believe all NFS recommended options apply, how about index/cache files though? Can I switch them off deliberately for good? Performance degradation is not an issue. Thanks, R. --

[PATCH] Clean up x86 control register and MSR macros This patch is based on Rusty's recent cleanup of the EFLAGS-related macros; it extends the same kind of cleanup to control registers and MSRs. It also unifies these between i386 and x86-64; at least with regards to MSRs, the two had definitely gotten out of sync. Signed-off-by: H. Peter Anvin <hpa@zytor.com> diff -urN

[PATCH] Clean up x86 control register and MSR macros This patch is based on Rusty's recent cleanup of the EFLAGS-related macros; it extends the same kind of cleanup to control registers and MSRs. It also unifies these between i386 and x86-64; at least with regards to MSRs, the two had definitely gotten out of sync. Signed-off-by: H. Peter Anvin <hpa@zytor.com> diff -urN

This patch is based on Rusty's recent cleanup of the EFLAGS-related macros; it extends the same kind of cleanup to control registers and MSRs. It also unifies these between i386 and x86-64; at least with regards to MSRs, the two had definitely gotten out of sync. Signed-off-by: H. Peter Anvin <hpa@zytor.com> diff -urN --exclude='o.*' --exclude '*~'

This patch is based on Rusty's recent cleanup of the EFLAGS-related macros; it extends the same kind of cleanup to control registers and MSRs. It also unifies these between i386 and x86-64; at least with regards to MSRs, the two had definitely gotten out of sync. Signed-off-by: H. Peter Anvin <hpa@zytor.com> diff -urN --exclude='o.*' --exclude '*~'

[Bug that was found by my previous patch] This patch allows things like modules, which don't have a direct __pa(EIP) mapping to do emulated instructions. Sure, the emulated instruction probably should be a paravirt_op, but this patch lets you at least boot a kernel that has modules needing emulated instructions. Signed-off-by: Steven Rostedt <rostedt@goodmis.org> Index:

[Bug that was found by my previous patch] This patch allows things like modules, which don't have a direct __pa(EIP) mapping to do emulated instructions. Sure, the emulated instruction probably should be a paravirt_op, but this patch lets you at least boot a kernel that has modules needing emulated instructions. Signed-off-by: Steven Rostedt <rostedt@goodmis.org> Index:

Paravirt-ops guests which move the fixmap also end up moving the syscall = VDSO. This fails if it is prelinked at a fixed address, which is why = COMPAT_VDSO is broken under CONFIG_VMI (and also under CONFIG_XEN). = Several options are available to try to address this. Jan had cooked up = a patch for Xen that used build magic to find the parts of the VDSO that = need relocation. I

Paravirt-ops guests which move the fixmap also end up moving the syscall = VDSO. This fails if it is prelinked at a fixed address, which is why = COMPAT_VDSO is broken under CONFIG_VMI (and also under CONFIG_XEN). = Several options are available to try to address this. Jan had cooked up = a patch for Xen that used build magic to find the parts of the VDSO that = need relocation. I

Hi, is there a driver disk available for the LSI 1064e SAS controller, operating in software raid mode? This Controler is installed on the Intel SR1500ALSAS for example, and named here Intel Embedded Software RAID II. I found drivers for RHEL4 and SUSE 10, but not for CentOS5? If I disable SAS Software-RAID in BIOS the system finds /dev/sda and /dev/sba and loads the mptsas drivers. But the

In my experience the mass market HBAs and RAID cards typically do support only 8 or 16 drives. For the internal variety in a standard rack-mount server you'll usually see either 2 or 4 iPass cables (each of which support 4 drives) connected to the backplane. The marketing material you've referenced has a white lie in it: supporting more than 16 drives on a single card is very likely only

Hi guys! Unfortunately there is no offtopic list but the subject is somehow related to centos as the OS is/will be centos :) So, under this thin cover i ask : Is it possible that for a SAS controler like LSI 3008 that in specs says that : "This high-performance I/O controller supports T-10 data protection model and optical support, PCIe hot plugging, and up to 1,000 connected devices"

This is taken from the work I did on lguest64. When killing a guest, we read the guest stack to do a nice back trace of the guest and send it via printk to the host. So instead of just getting an error message from the lguest launcher of: lguest: bad read address 537012178 len 1 I also get in my dmesg: called from [<c0405f30>] show_trace_log_lvl+0x1a/0x2f [<c04069aa>]

This is taken from the work I did on lguest64. When killing a guest, we read the guest stack to do a nice back trace of the guest and send it via printk to the host. So instead of just getting an error message from the lguest launcher of: lguest: bad read address 537012178 len 1 I also get in my dmesg: called from [<c0405f30>] show_trace_log_lvl+0x1a/0x2f [<c04069aa>]

Hello all, Sorry for the OT thing. I'm helping a friend setting up a new box. It's a Pentium 4 with 430Watt power supply. He wants to plugin his old harddrives and DVD into the new box. The total will be: 3 harddrives, 1 DVD drive, 1 CDRW drive. In the box there are also 2 big fans. Is 430Watt enough? Thank you for your sharing. -- Fajar Priyanto | Reg'd Linux User #327841 |

Hi all, Lguest is a simple hypervisor which runs Linux under Linux, without needing VT hardware. Two people asked if I had a version of lguest which worked on other-than-bleeding-edge-mm kernels, so I did a backport of the latest version to 2.6.21. http://lguest.ozlabs.org/lguest-2.6.21-254.patch.gz See Documentation/lguest/lguest.txt for how to run, drivers/lguest/README for the draft code