Koozali.org: home of the SME Server

Obsolete Releases => SME Server 7.x => Topic started by: dswillia on March 09, 2006, 10:56:23 PM

Title: Sata Raid Controller ULI M5287
Post by: dswillia on March 09, 2006, 10:56:23 PM
Ok, new asus MB with integrated ULI m5287 Sata Controller.  Installing pre4 I get the no HD's found.  I go through the process to install drivers from the floppy and it loads into the "device" list.  But when I select it from the list, I get the message that no hardware was added.  When reading the readme.txt with the driver it specifies the following:

"2.2 To install the ULi RAID Linux Driver into a NEW SYSTEM

  1.) Start the Fedora Installation with CD-ROM booting.

  2.) At the first installation screen, a prompt
      labeled "boot:" will appear at the bottom of the screen.

  3.) Please append parameters (see Note 1 below) at the "boot:" prompt,
      then press the Enter key.

  4.) At the "driver disks" dialog box, press "YES" .

  5.) Next ,if "Driver Disk Source " dialog box appears,select "fd0" and press "OK".
 
  6.) At the Insert Driver disk" dialog box,insert your raid driver disk into floppy drive and press "OK" to continue;

  7.) If the system shows "Error" dialog box, press "Manually choose" and scroll down at "Select Device Driver to Load"
      dialog box to select ULi 5281 Raid Controller (ALiRaid),then press "OK".   
 

  8.) Enable "Configure advanced boot loader options" box at Boot Loader
      Configuration menu, and type kernel parameters (see NOTE 2 below)
      in the General kernel parameters field.

  9.) Continue with the installation as normal.

  10.) If the installer occur warning message about "The partition table on device /dev/sd(x)
   is of an unexpected type loop for your architecture....." or "the partition table on device sd(x) is unable to read
   ...",just click "YES" bottom to continue the install.
  11.) Complete the installation as directed by the install.

WARNING(only for fc2-64bit): After the install begins,fresh install into hd on 5281 card may pause at certain package because of the fc2-64 system 's ext3's bug;
   you must  repeat the install several times to solve the problem.

[NOTE]

   Linux Kernels 2.6.x misidentiy ULi ATA-RAID controllers as simple
IDE controllers. This results in the built-in Linux IDE driver trying to
handle the controller and can prevent the proper ULi RAID driver
from loading.
   Follow the installation instructions AND the parameter commands referred
to below section. This status we called "IDE issue".

M5281/M5283:  
   1.) "linux ide0=0x1f0,0x3f6,14 ide1=0x170,0x376,15 ide2=0 ide3=0 ide4=0
        ide5=0 ide6=0 ide7=0 ide8=0 ide9=0 dd "

   2.) "ide0=0x1f0,0x3f6,14 ide1=0x170,0x376,15 ide2=0 ide3=0 ide4=0 ide5=0
        ide6=0 ide7=0 ide8=0 ide9=0 noirqdebug"
        ("noirqdebug" parameter is for fedora 2 only)

M5287/M5289:
   1.) "linux dd"

   2.) "noirqdebug"
       ("noirqdebug" parameter is for fedora 2 only)"

Any help would be appreciated.

Regards,
Title: Sata Raid Controller ULI M5287
Post by: dsemuk on March 10, 2006, 12:08:21 AM
You need to be looking for RHEL / CentOS support for your controller.

Possibly the CentOS forums will give you some pointers as to what you need to get your controller working with that OS and you can use the same info to get running on SME7.

As you know SME7 is based on Centos4.2, which inturn is based on RHEL.

Dave
Title: Re: Sata Raid Controller ULI M5287
Post by: CharlieBrady on March 10, 2006, 12:19:02 AM
Quote from: "dswillia"
Ok, new asus MB with integrated ULI m5287 Sata Controller.  Installing pre4 I get the no HD's found.


The Bug Tracker, "SME Server 7.0" is the central repository of all 7.0 problem reports. Please add your report there. Thanks.
Title: Sata Raid Controller ULI M5287
Post by: dswillia on March 10, 2006, 04:20:23 AM
Sorry, I did a cut and paste on the wrong part of the readme.  I do have rh9 drivers, 32bit, but it says I need to pass the above variable "linux dd".  Would I do that by selecting the addtional info button and putting it there?  And Charlie, I will open a bug, as soon as I ensure I am not messing it up