Hi, all!
I want to change current RHEL 4.0 ES into CentOS 4.2 on Sun X4100 server.
The server has SAS SCSI based two 2.5" hard disks.
I could only install RHEL 4.0 Update 1 because the server is equipped with
RHEL 4.0 Update 1's device driver only.
I've included below the boot process messages concerned with SCSI
controller.
If it's possible for me to install CentOS 4.0 on my X4100, I am ready to
switch to it.
TIA
Sungsoo Kim
-------------------
SCSI subsystem initialized
Fusion MPT base driver 3.02.18
Copyright (c) 1999-2005 LSI Logic Corporation
ACPI: PCI interrupt 0000:02:03.0[A] -> GSI 28 (level, low) -> IRQ 209
mptbase: Initiating ioc0 bringup
ioc0: SAS1064: Capabilities={Initiator}
Fusion MPT SCSI Host driver 3.02.18
scsi0 : ioc0: LSISAS1064, FwRev=01040000h, Ports=1, MaxQ=203, IRQ=209
Vendor: FUJITSU Model: MAV2073RCSUN72G Rev: 0301
Type: Direct-Access ANSI SCSI revision: 04
SCSI device sda: 143374738 512-byte hdwr sectors (73408 MB)
SCSI device sda: drive cache: write through
sda: sda1 sda2 sda3
Attached scsi disk sda at scsi0, channel 0, id 2, lun 0
Vendor: FUJITSU Model: MAV2073RCSUN72G Rev: 0301
Type: Direct-Access ANSI SCSI revision: 04
SCSI device sdb: 143374738 512-byte hdwr sectors (73408 MB)
SCSI device sdb: drive cache: write through
sdb: sdb1
Attached scsi disk sdb at scsi0, channel 0, id 3, lun 0
There's a howto for switching from Whitebox, I'd imagine that ES to CentOS would be similar: http://centos.org/modules/smartfaq/faq.php?faqid=19 I took the above FAQ and made a working script you're free to play with: http://chico.benjamindsmith.com/wbel2centos4.sh Good luck. On Friday 06 January 2006 19:47, Sungsoo Kim wrote:> Hi, all! > > I want to change current RHEL 4.0 ES into CentOS 4.2 on Sun X4100 server. > The server has SAS SCSI based two 2.5" hard disks. > I could only install RHEL 4.0 Update 1 because the server is equipped with > RHEL 4.0 Update 1's device driver only. > > I've included below the boot process messages concerned with SCSIcontroller.> If it's possible for me to install CentOS 4.0 on my X4100, I am ready to > switch to it. > > TIA > > > Sungsoo Kim > > > ------------------- > > SCSI subsystem initialized > Fusion MPT base driver 3.02.18 > Copyright (c) 1999-2005 LSI Logic Corporation > ACPI: PCI interrupt 0000:02:03.0[A] -> GSI 28 (level, low) -> IRQ 209 > mptbase: Initiating ioc0 bringup > ioc0: SAS1064: Capabilities={Initiator} > Fusion MPT SCSI Host driver 3.02.18 > scsi0 : ioc0: LSISAS1064, FwRev=01040000h, Ports=1, MaxQ=203, IRQ=209 > Vendor: FUJITSU Model: MAV2073RCSUN72G Rev: 0301 > Type: Direct-Access ANSI SCSI revision: 04 > SCSI device sda: 143374738 512-byte hdwr sectors (73408 MB) > SCSI device sda: drive cache: write through > sda: sda1 sda2 sda3 > Attached scsi disk sda at scsi0, channel 0, id 2, lun 0 > Vendor: FUJITSU Model: MAV2073RCSUN72G Rev: 0301 > Type: Direct-Access ANSI SCSI revision: 04 > SCSI device sdb: 143374738 512-byte hdwr sectors (73408 MB) > SCSI device sdb: drive cache: write through > sdb: sdb1 > Attached scsi disk sdb at scsi0, channel 0, id 3, lun 0 >-- "The best way to predict the future is to invent it." - XEROX PARC slogan, circa 1978
On Sat, 2006-01-07 at 12:47 +0900, Sungsoo Kim wrote:> Hi, all! > > I want to change current RHEL 4.0 ES into CentOS 4.2 on Sun X4100 server. > The server has SAS SCSI based two 2.5" hard disks. > I could only install RHEL 4.0 Update 1 because the server is equipped with > RHEL 4.0 Update 1's device driver only. >This means that you installed a driver when you installed the OS ... do you still have the RHEL kernel what shipped with update 1 .. or have you upgraded the kernel since then. Have you done any other updates (besides the kernel) since update 1? What is the output of this command: uname -a> I've included below the boot process messages concerned with SCSI controller. > If it's possible for me to install CentOS 4.0 on my X4100, I am ready to > switch to it. > > TIA > > > Sungsoo Kim > > > ------------------- > > SCSI subsystem initialized > Fusion MPT base driver 3.02.18 > Copyright (c) 1999-2005 LSI Logic Corporation > ACPI: PCI interrupt 0000:02:03.0[A] -> GSI 28 (level, low) -> IRQ 209 > mptbase: Initiating ioc0 bringup > ioc0: SAS1064: Capabilities={Initiator} > Fusion MPT SCSI Host driver 3.02.18 > scsi0 : ioc0: LSISAS1064, FwRev=01040000h, Ports=1, MaxQ=203, IRQ=209 > Vendor: FUJITSU Model: MAV2073RCSUN72G Rev: 0301 > Type: Direct-Access ANSI SCSI revision: 04 > SCSI device sda: 143374738 512-byte hdwr sectors (73408 MB) > SCSI device sda: drive cache: write through > sda: sda1 sda2 sda3 > Attached scsi disk sda at scsi0, channel 0, id 2, lun 0 > Vendor: FUJITSU Model: MAV2073RCSUN72G Rev: 0301 > Type: Direct-Access ANSI SCSI revision: 04 > SCSI device sdb: 143374738 512-byte hdwr sectors (73408 MB) > SCSI device sdb: drive cache: write through > sdb: sdb1 > Attached scsi disk sdb at scsi0, channel 0, id 3, lun 0 > _______________________________________________More important than anything else is figuring out what kernel you need to use. There is a forzen CentOS-4.1 tree at http://vault.centos.org that has all the 4.1 kernels. (In CentOS ... 4.0 is the original release, 4.1 is update 1, 4.2 is update 2, etc.) After the kernel issues are defined, a plan for doing a switch can be put together. Is there a driver source so that you can build a new driver for new kernels (if required)? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://lists.centos.org/pipermail/centos/attachments/20060107/52b38db0/attachment.sig>
Dear Hughes,
Thank you for your reply!
As you metioned I installed device driver when I installed
RHEL 4.0 U1 by typing "linux dd" and inserting device driver CD
according to X4100's installation manual.
I just intalled RHES 4.0 U1, not updated anything.
So the running kernel version is kernel-smp-2.6.9-11.EL as shown below.
[root at atlas ~]# uname -a
Linux atlas 2.6.9-11.ELsmp #1 SMP Fri May 20 18:25:30 EDT 2005 x86_64 x86_64
x86_64 GNU/Linux
Thanks a lot!
Sungsoo Kim
----- Original Message -----
From: "Johnny Hughes" <mailing-lists at hughesjr.com>
To: "CentOS ML" <centos at centos.org>
Sent: Saturday, January 07, 2006 7:30 PM
Subject: Re: [CentOS] Can I install CentOS 4.2 on Sun X4100?
On Sat, 2006-01-07 at 12:47 +0900, Sungsoo Kim wrote:> Hi, all!
>
> I want to change current RHEL 4.0 ES into CentOS 4.2 on Sun X4100 server.
> The server has SAS SCSI based two 2.5" hard disks.
> I could only install RHEL 4.0 Update 1 because the server is equipped with
> RHEL 4.0 Update 1's device driver only.
>
This means that you installed a driver when you installed the OS ... do
you still have the RHEL kernel what shipped with update 1 .. or have you
upgraded the kernel since then.
Have you done any other updates (besides the kernel) since update 1?
What is the output of this command:
uname -a
> I've included below the boot process messages concerned with SCSI
controller.
> If it's possible for me to install CentOS 4.0 on my X4100, I am ready
to
> switch to it.
>
> TIA
>
>
> Sungsoo Kim
>
>
> -------------------
>
> SCSI subsystem initialized
> Fusion MPT base driver 3.02.18
> Copyright (c) 1999-2005 LSI Logic Corporation
> ACPI: PCI interrupt 0000:02:03.0[A] -> GSI 28 (level, low) -> IRQ 209
> mptbase: Initiating ioc0 bringup
> ioc0: SAS1064: Capabilities={Initiator}
> Fusion MPT SCSI Host driver 3.02.18
> scsi0 : ioc0: LSISAS1064, FwRev=01040000h, Ports=1, MaxQ=203, IRQ=209
> Vendor: FUJITSU Model: MAV2073RCSUN72G Rev: 0301
> Type: Direct-Access ANSI SCSI revision: 04
> SCSI device sda: 143374738 512-byte hdwr sectors (73408 MB)
> SCSI device sda: drive cache: write through
> sda: sda1 sda2 sda3
> Attached scsi disk sda at scsi0, channel 0, id 2, lun 0
> Vendor: FUJITSU Model: MAV2073RCSUN72G Rev: 0301
> Type: Direct-Access ANSI SCSI revision: 04
> SCSI device sdb: 143374738 512-byte hdwr sectors (73408 MB)
> SCSI device sdb: drive cache: write through
> sdb: sdb1
> Attached scsi disk sdb at scsi0, channel 0, id 3, lun 0
> _______________________________________________
More important than anything else is figuring out what kernel you need
to use. There is a forzen CentOS-4.1 tree at http://vault.centos.org
that has all the 4.1 kernels.
(In CentOS ... 4.0 is the original release, 4.1 is update 1, 4.2 is
update 2, etc.)
After the kernel issues are defined, a plan for doing a switch can be
put together. Is there a driver source so that you can build a new
driver for new kernels (if required)?