I have contacted ULi about the support and SATA drivers are available.

I posted the package online at:
kuhazor.idlegames.com/1573_Linux_K2.6.x_Integrated_Driver_1.31.zip

Here are the instructions included in the package (~2MB)

=========================================================

SCSI_Driver:

The open source ULi SATA Linux driver, developed for standard kernel, it can be compiled
and installed to all linux distribution based on standard kernel.
Not support the raid function in driver, user can use linux software raid module on it.

=====================================================================

SCSI_RAID_Driver:

Builded driver binary, support the raid 0,raid 1,raid 0+1 by itself; it support the
following linux distribution:

1. Redhat 9.0
2. SuSe 9.0(32 bit & 64 bit)
3. Fedora core 2(32 bit & 64 bit)
4. Fedora core 3(32 bit & 64 bit)
ULi RAID Linux Driver
For Fedora core 2/3-32/64bit
Version 1.00 [22/11/2004]

[INTRODUCTION]

1.1 Foreword

This procedure applies to ULi RAID 5281|5283|5289|5287 adapters.

1.2 Prepare a Driver Diskette

You will use a diskette to load the new Linux driver onto your PC.

1) Obtain a new, formatted diskette and label it "ULi RAID Driver Disk."
Insert it into your PC's floppy drive.

2) Extract the contents of the driver file you downloaded from the
ULi website onto your floppy disk. Use either WinZIP in Windows or
Unzip in Linux to extract the files.


[INSTALLATION]

2.1 To install the ULi RAID Linux Driver into an EXISTING SYSTEM:

1.) Boot linux system and login as root.

2.) Insert ULi RAID Driver Disk for install ULi RAID Driver by issuing
commands :
# mount /dev/fd0 /mnt/floppy
# cd /mnt/floppy
# sh install (Answer Yes/No when inquire setup configuration)

You can answer Yes to bind ULi RAID driver into linux booting.

# cd ..
# umount /dev/fd0
NOTE: Due to the Linux kernel misidentifying the ULi RAID card, all IDE
channels except onboard IDE are disabled. To enable the other IDE channels,
remove the line "ide2=0 ide3=0 ide4=0 ide5=0 ide6=0 ide7=0 ide8=0 ide9=0"
in /etc/lilo.conf.anaconda or /boot/grub/grub.conf.

3.) Reboot Fedora system.


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)

For everyone who is trying to install linux on ST20G5 Shuttle xPC SUSE 9.3 installs fairly easy. Here is how:

1) Disable software SATA raid from BIOS
2) Use linux software RAID instead.
3) SATA drivers are detected just fine and the installation will be a snap
4) Now when the computer reboot and the system will hang probing PCI devices
5) Go back to BIOS, disable integrated ATA controlled, sound, USB
6) Reboot, the system will now boot up
7) Restart again, then enable things back on
8) You are done.

If you are using the integrated audio, there is a driver for it, available from ULi. See my other posts for the link.

Awesom! Superfast system!

SUSE Rocks here!

The hang in the boot is caused by the onboard USB. So just disable that and you should be fine... Trying to get USB to work next week.

I can't find your post about getting the integrated audio to work.

Just download the package I posted... It has drivers for the sound on it.

Can you repost that package? The link for your dyndns service no longer works.

Either that, or indicate where you got it from?

Thanks ;-)

Trying really hard to get audio working on my SuSE 9.3 box, ST20G5

The file can be found at:

http://kuhazor.dnsalias.com/1573_Lin...river_1.31.zip

Let me know if you get the sound working or OpenGL on X200 working. My ST20 box is really a server, so I kind of gave up on these.

Wow! Thanks for the quick response. Talk about prompt service ;-)

I feel like I've got sound 99% there. I can get the snd-hda-intel module from the latest alsa loaded, but I don't get any output. I've heard that this might be fixable by recompiling the kernel without sound support, and then compiling alsa from the native source.

I'll post my results as soon as I'm finished

Hi,

Did you work out this USB problem eventually? I just bought an XPC Barebone, ST20G5 and have the same problem... just found this post, and I try to avoid solving the same bug twice. Thanks beforehand. All pointers to a possible solution will be appreciated.
Best regards

Thomas

Well, I don't think the first post is still accurate. I've succeeded in installing FC4 on my ST20G5 (equipped with a maxtor SATA driver), without disabling SATA, USB or the sound support in the BIOS; make sure you install the latest BIOS version first (at least v15, or even better use v16) and boot linux with "noapic nolapic acpi=off"...

To get the sound going the kernel must indeed be compiled without the sound drivers integrated. Both ULI and Realtek provide the required audio drivers; there are currently at ASLA v1.0.9x; these only gave me sound though until my first reboot... When logging in again snd_hda_codec crashed. Installing the latest ALSA version (v1.0.10rc2) might solve this.

Good luck,

Diederik

The links appear to be dead. Is there a mirror?

Thanks in advance.

-dan

This should contain the drivers you're looking for:

ftp://www.uli.com.tw/driver/Linux_K2...egrated132.zip

Regards,

Diederik

On my Shuttle ST20G5 I had to enable SATA RAID from BIOS to get my (Seagate Barracuda 7200.8 250GB) SATA hard disk work with Linux.

Hello,

you knew all the st20g5 runs, but suboptimal.
Kernel crash if not acpi=off noapic
No Sound support in kernel 2.6.14
sata_uli is buggy, detects only disc if raid mode is set in bios.
or if not set you need a second load of sata_uli module.
ATI fglrx don't creates a correct module on 2.6.14
--- fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel.
--- [fglrx] Maximum main memory to use for locked dma buffers: 1824 MBytes.
--- [fglrx:firegl_stub_register] *ERROR* Unable to the open some already present DRM kernel module!

May it could helps if all send a Bug-Report to shuttle, so shuttle can maybe force uli (ali) and
ati to update their driver. You knew all that a single bug-report ends in /dev/null.
But if a lot of people sends bug-reports to shuttle, it could wake up the people there.
May they take notice, that not only M$-Gamers are using their barbones.

I prepare a extensive bug-report at
--> http://global.shuttle.com/Support/Su..._Technical.asp

And hope that you will do it like me, and try to request as much shuttle user
as possible to get the attention of shuttle to linux-users.

greetings thomas

Hi Thomas,

Please remove the dash from your link, it's not working!

PS: I'm in!

Regards,

Diederik