Confirmed SATA Installs

[SmyTTor]

I would like to see if anyone has been able to do a FC2 install on an Athlon64 motherboard using SATA exclusively.

Has anyone been able to get an install through on an Abit KV8-MAX3 or ASUS K8V Deluxe, on either of the onboard SATA chipsets?

I can pretty much validate that the Foxconn 755a01 is NOT a viable board for any install, though I did get FC2 to install on the Silicon Image 3112 chipset (the SiS964 chipset is a no go). The reason that this motherboard should be avoided is the extremely poor USB implementation (how can you mess up USB?) that runs about %50 CPU usage when a single USB device is in use (around %60 in Windows XP) and with multiple USB devices working, like a KB, mouse, printer, and digital camera, the overall strain is so bad there is missed keystrokes, cursor positioning is lost, and print spooling or image copying fails. There is also abnormally high CPU usage on any HD access. When I was working on a logo and the mouse would lose position during a stroke I had to undo and restart the whole line over. In WinXP there were abundant quirks and crashes (more than usual). I shut down the system in disgust and switched back to my Athlon 2800 system and am considering the two motherboards above, or any that have a supported SATA chipset in FC2 and a verified install.

[mhec]

Subject says it all, I'll let you know the results.

[Bana]

Chaintech ZNF3-150 works fine with a silicon image 3114 SATA raid chip. Sound even works (after many weeks of waiting).

[SmyTTor]

Should have an Asus K8V SE Deluxe Monday, Tuesday by latest. I'm going to try an installs off both the SATA chipsets and let everyone know how it goes.



I installed Fedora 2 on one for my friend and everything seemed to go well, though I had to leave shortly after. The install was on a Hitchachi Deskstar SATA drive on the promise chipset. Graphics card was a Geforce FX 5950 and was not having any issues after install of os or the updated NVidia drivers. It detected the PCI Netgear NIC but apparently not the onboard Marvell gigabit, which I thought was supposed to be the 3com chip, but I guess they changed it from the original K8V Deluxe.

[lauterm]

Chaintech VNF3-250 also works. I'm not sure what SATA chip it is, but FC2 is installed on my SATA drive. I've had no problems with this board , except it doesn't have Gb Ethernet. However, it was a good bit cheaper than any of the NForce3-150 series mobos that I saw.

[mhec]

first off, this was a server install so don't ask me about sound or AGP graphics (although I did do a graphical install)

The only issue I had was with the whopping selection of SATA and PATA controllers on the board. Took me an hour of messing with diffrent combinations of my 3 hard drives (2 PATA, 1 SATA) + CD-ROM till I found one that worked.

1. The promise PATA raid controller is not recognized by FC2 (even if you tell it to act as a plain IDE controller via the BIOS.). Perhaps this is intentional?

2. The Via SATA controller is is recognized but does not use libata (perhaps it is only well supported on later kernels), so I avoided it.

3. The promise SATA controller is recognized by FC2 and it uses libata (i.e /dev/sdx Vs. /dev/hdx).

4. The Via PATA controller works as expected as well.

I choose to use 3 and 4 above in a Raid5 + LVM setup. Worked fine.

The only other issue I had was with the Marvell Gigabit NIC. Although it was recognized and worked (more or less), it spewed out errors in the syslog. Apparantly this board has faulty firmware for the NIC. Luckily, the driver can correct the bug via software. A patch to do just that made it into 2.6.7-rc2, which is in the latest kernel rpm available here:

http://people.redhat.com/arjanv/2.6/RPMS.kernel/

Using the new kernel has solved the problem for me.

Hope this helps.

[Zubir]

while i can use my SATA drives with the K8T NEO under FC2, it won't recognize my RAID 0. the raid controller is the VIA VT8237. it also takes an intolerably long time to boot, especially compared to FC1, which wasn't quick to start with on my old Nforce 2 board.

[Dok]

Just installed on a Tyan Tiger K8W. This board has the Silicon Image Sil3114 SATA controller that can do RAID 0 and 1. Installing to the SATA drives works fine. Installing to a RAID 0 or 1 array (created in the Silicon Image bios) doesn't work. FC2 still sees the two drives as separate.

This isn't a problem for me, I set up a software RAID 1 in FC2 that does the same thing.

Brad

[SmyTTor]

Ok, so here's my update.

SATA install using VIA RAID was a no go. Not only did it not recognize raid 0 or 1, but I could not even do an install to a single drive on the VIA chipset- it kept locking up.

SATA install using the Promise chipset does not work in RAID 0 or 1 either. It sees the drives individually. So I did WinXP on the first drive and FC2 on the second drive and the installs went through without error. I am now in my first log-in and nautilus failed right off; the updater locked up. I installed FC2 on another athlon 64 machine (the install only takes 16 minutes total time, how awesome is that?) that I had here and the exact same problem occurred.

From what I can see, SB Audigy works fine, GF FX5600 and monitor working great, both network cards (compaq server NIC and the fairly new Marvell onboard NIC) were installed and pulled addresses from both an internal LAN and an Internet router.

Being still relatively new to modern Linux (excluding the past few months, my last install was Slackware about '93) I'm going to have to take a little while to get familiar setting everything up and tracking down what's not playing nice. I can say that the 32bit version of WinXP is not playing nice at all with various NICS; It seems mainly driver issues at this point.

[Slinwagh]

I have managed an install on my Asus k8V SE.

I can install on any sinlge SATA disk, any controller, any channel.

As for RAID configs I only see two single disks in RAID 0 config (Fastrack) and no disks at all RAID 0 (Via)

Is there a fix/patch available?

[kingcrowbar]

Motherboard: MSI K8T Neo-FIS2R
HardDisk: Samsung 160GB SP1614C SATA

Harddisk connected to 1st SATA channel of the Via controller, DVD connected to Primary-Master IDE of the Via controller. Promise controller disabled in bios.

HardDisk appears as /dev/hde

Installed FC2-x86_64 from harddisk using loadlin from DOS to boot the vmlinuz/initrd.img which i extracted from the 1st cd image. Only tweak i had to make was to check if dma was enabled because it wasn't enabled for me during and after installation of FC2-i386. Pressing ctrl-alt-F2 and running hdparm -d1 /dev/hde around the timezone selection part fixed it for me. Everything install took about 25mins, rebooted and came here :)
Now i just need to make the hdparm -d1 stay over reboots

hth

[bazzoon]

ASUS k8v
athlon 64 3200+

I had the usual CD install for FC2. It went just fine with no problem. I installed the system on a hard drive connected to the via sata on the mother board.

Well, it is worth mentioning that the install failed for the FC2Test3. The sata drive was not recognized then. The problem was apparently solved in the final FC2 released.

[Zubir]

Motherboard: MSI K8T Neo-FIS2R
HardDisk: Samsung 160GB SP1614C SATA

Harddisk connected to 1st SATA channel of the Via controller, DVD connected to Primary-Master IDE of the Via controller. Promise controller disabled in bios.

HardDisk appears as /dev/hde

Installed FC2-x86_64 from harddisk using loadlin from DOS to boot the vmlinuz/initrd.img which i extracted from the 1st cd image. Only tweak i had to make was to check if dma was enabled because it wasn't enabled for me during and after installation of FC2-i386. Pressing ctrl-alt-F2 and running hdparm -d1 /dev/hde around the timezone selection part fixed it for me. Everything install took about 25mins, rebooted and came here :)
Now i just need to make the hdparm -d1 stay over reboots.

hth

As root, type "emacs /etc/rc.d/rc.local," then add the following line:

hdparm -d1 -c3 -a64 -X66 -k1 /dev/hde

Click "Save current buffer," and the change will stay after reboots.

[laBa]

Hi, I'm a noob with linux. I tried installing FC2-x86_64 from DVD on my KV8-MAX3 MB on the onchip VIA SATA controler, but it hangs during post installation config & it took hours to reach that!

I succeeded in installing mandrake-10_i586 worked fine on the same VIA controler. My silicon image 1134 controler is disabled.

You guys think it's a hardware problem?


thank you

I managed to install, after enabling both SATA controlers. I had my Silimage 1134 controler disabled.
every thing is ok now, but takes forever to boot :\ is that normal? like 5-10min to boot?

[ckasprzak]

I had to email Albatron about fixing the "K8 errata #93" error and I'm running a beta bios on here that fixed that, but for some reason when the kernel is trying to detect the drive on the SATA control it loses the interupt.

[Julio]

It works fine and easy on my Asus K8V SE Deluxe.

[wzzrd]

Had a little trouble installing on my MSI K8T NEO (had to do a network install, because the CD's I burned where fscked), but in the end it's all fine. Running FC2 @ 64bits right now, as a matter of facts :)

[ssenesac]

Ok, so here's my update.

SATA install using VIA RAID was a no go. Not only did it not recognize raid 0 or 1, but I could not even do an install to a single drive on the VIA chipset- it kept locking up.

SATA install using the Promise chipset does not work in RAID 0 or 1 either. It sees the drives individually. So I did WinXP on the first drive and FC2 on the second drive and the installs went through without error. I am now in my first log-in and nautilus failed right off; the updater locked up. I installed FC2 on another athlon 64 machine (the install only takes 16 minutes total time, how awesome is that?) that I had here and the exact same problem occurred.

From what I can see, SB Audigy works fine, GF FX5600 and monitor working great, both network cards (compaq server NIC and the fairly new Marvell onboard NIC) were installed and pulled addresses from both an internal LAN and an Internet router.

Being still relatively new to modern Linux (excluding the past few months, my last install was Slackware about '93) I'm going to have to take a little while to get familiar setting everything up and tracking down what's not playing nice. I can say that the 32bit version of WinXP is not playing nice at all with various NICS; It seems mainly driver issues at this point.

There's a reason why the RAID does not work in Linux. The RAID controllers on this motherboard and on most consumer SATA motherboards for that matter are not <B>hardware</B> RAID. The striping or mirroring is handled using a software driver as overhead to your system processor(s). On a true <B>hardware</B> RAID controller, the controller chip handles this. Since the software drivers are windows based, only a windows installation will recognize the RAID configuration. To your linux system the array is not seen and the data on the drives appears to be jibberish. There is no way to use the built-in software RAID functionality in Linux. If you wish to software RAID the drives in Linux you have to use the <B>md</B> module and setup a <B>raidtab</B> file describing the layout of your software array. However, if you do this, the array will not be recognized by Windows. So, you may RAID in Linux or you may RAID in Windows, but you may not RAID in both :mad: This totally blows, but such is life.

[mbirkis]

Installing on KV8MAX3 worked great for me... i used Silicon controller...

[linuxdude3]

I don't use SATA exclusively however, but boot using IDE (where all the system resides) and have a single SATA 300G as my data/video drive.

My motherboard Albatron K8T800 Pro II uses a VIA SATA driver chip, which I have set to "use like IDE" in my BIOS - no RAID enabled in BIOS. I cannot recall my BIOS revision at the moment.

Note that the sata-via driver gets "lost" after boot and therefore you cannot see your drive. So I added install sata-via in the modprobe.conf file and had to add a mount command in the local rcinit file. I cannot recall the exact entries off the top of my head but I can post the details if anyone wants.

My kernel is a built-from-source 2.6.8.1-521 with my own selection of modules and the K8 option (Athlon64), but no code changes.

[booh]

Hey all,

I installed FC2 last week on my new Abit KV8Pro (VIA SATA chip), using only SATA (except DVD which was on PATA of course).

I only have one HD, so I didn't even think about trying RAID.

The installation went off without a hitch :) , but there are problems using the via-velocity gigabit ethernet (but that's a whole other story...)

booh.

[clearer]

First time I installed it wouldn't boot. Have had no problems related to booting after this, however.

For people with sound problems - check your volume. I thought my soundcard wasn't supported in 64-bit version, but by accident, I turned up my speakers really loud and I heard some very faint sounds. Turned out that the sound is almost completly off. :)

EDIT: I noticed that some people have been having problems with SATA disk as RAID devices. I would like to add that, although I also have a VIA SATA RAID controller onboard, I have had no problems related to this. I can even switch between SATA RAID and regular IDE functions after installation without problems.

[Dog-One]

Installed fine on a MSI K8N-Neo. When I updated to kernel 2.6.8 she died. Come to find out that the nForce3 SATA has been relocated to the sata_nv module. I rebuilt a new initrd, modified my fstab and everything works fine again with the exception that smartd/smartctl can't see my SATA drives since they appear as SCSI drives now.

HTH

[longsiyin]

Hey all,

I installed FC2 last week on my new Abit KV8Pro (VIA SATA chip), using only SATA (except DVD which was on PATA of course).

I only have one HD, so I didn't even think about trying RAID.

The installation went off without a hitch :) , but there are problems using the via-velocity gigabit ethernet (but that's a whole other story...)

booh.

Is there any methods connecting to internet via the gigabit ethernet? :confused:

[madhippy]

Anyone recently tried an install onto SIS964 SATA controller?

[zshay]

FC2 install went perfect. I am having troubles wiht FC3 Test 2. I don't think it is localized to this release, but to the kernel '2.6.8-1.521'. I am not sure that the driver is included for this kernel. It is unable to find the harddrives on installation (and at boot time "VFS: kernel panic.....")

thanks

zshay

[JLF_65]

I just installed FC3t2 on my MSI Master2-FAR. That mobo has dual Opterons (only using one at the moment), the K8T800 chipset, with the VT8237 South Bridge / VT6420 SATA chipset. I put two Hitachi 80G 7200RPM 8M cache SATA drives on it.

FC2 completely bombs with this system with SATA. It has the bug were VP_IDE tries to use the SATA drives at the same time VIA8237SATA is using them. Lost interrupts, yada yada yada...

FC3t2 works like a charm on it. My drives are formatted like this:
RAID1 / 512M
RAID0 /var 8G
RAID0 /usr 16G
swap on both drives so FC uses it like RAID0 (2G total)
RAID0 /home 130G (all the rest of the space)

I based the sizes on the non-home partitions on twice what those directories had in them under FC2 plus a little extra. I figure that should be pretty safe. I put EVERYTHING into home anyway.

[madhippy]

knoppix 3.7 with 2.6 kernel recognises the SIS964 and partitions it - I'm going to retry Fedora later today.

[Dog-One]

I found this link (http://linux.yyz.us/sata/sata-status.html) and had to post it. Lots of good info on the state of SATA and Linux.

Also, there appears to be a bug in the sata_nv module version 0.02 found in the 2.6.8-1.521 kernel for FC2 users. You know if you have the problem when your syslog file grows to consume your entire filesystem. A patch is here (http://readlist.com/lists/vger.kernel.org/linux-kernel/7/36662.html) for those with strong hearts. :)

[TheBlueCow]

On a fresh install, Fedora won't recognize my poor Seagate SATA. I have a K8N Neo mainboard...I don't even know what driver to select from the list, it still won't recognize the drive when I tried ones I thought would be right. Any help?

[Dog-One]

The K8N Neo (which is the same as mine) found my drives as regular IDE drives when I first installed FC2. When I updated my kernel to 2.6.8, that's when I had to load sata_nv (nForce chipset) module. If you're using FC3 Test, I believe you'll start out with the same problem that I had when I updated.

Can you confirm that your BIOS sees the Seagate drive?

What version of Fedora are you trying to install?

[septus]

Hi "SmyTTor",
By know you may have had enough replies. Anyhow, Fedora core 2 installed without a glitch on my AMD 64 bit 3000+ system, with a Gigabyte K8N Pro mobo, exclusively using two SATA Hitachi 80 gig HHD:s. Interestingly, Xandros (still using the 2.4 kernel) and WinXP failed to install, but WinMe had no problem. One initial problem with Fedora was that the bootloader installation did not "see" the Win system), but changing the default bootup to "other", i.e. Win Me solved that problem.
Cheers
"septus" (aka Eric)

[smf321]

Last posting failed - so I'm trying again...

To get FC2 to install on an MSI K8T master mobo (dual opteron) with vt8237 SATA I had to pass "linux pci=noacpi", install still failed when I selected all packages (skipped straight to postinstall as the rpm installation was supposed to happen). A minimal install worked however and I'm adding the extra packages as required.

On another mobo - Gigabyte mobo (AMD64) I had to pass "linux norpobe".

Installation on a Promise SATA controller (PDC20378) and 3ware 7000-series ATA-RAID (4 SATA disc - RAID configuration), both worked fine. Although I needed to do a BIOS upgrade on one machine that was giving machine check exceptions.

[Bloemkoolvreter]

Could I ask how to begin an install on a SATA drive ? I have no idea how i can get FC 3 test 3 to recognize my SATA drives, it's probably just some kernel parameter i have to pass along ?

I'm trying to install on a nForce 3 platform : MSI K8N Neo2 Platinum, which also has raid capabilities (that I don't use)

[weapon]

to fix the lost interupt put acpi=off as a kernel argument

Dave

[cybrjackle]

A8V Deluxe, as many have mentioned, no SATA raid ;(

So I got 2 160 sata drives for no reason now, except to hold a lot of data.

[ahbrown41]

The SN85G4LV2 with the newest bios works great. It has the nForce3 chipset and the Silicon Image SATA controller. I have a single SATA drive.

[delt0r]

i just installed on a single SATA HDD last nite (1am --yea the wife loves the new machine;)..

Specs:
Gigabyte GA-K8NS Pro motherboard, Socket 754 , nForce....

Fedora Core 3 64 bit from a burnt dvd iso image. Segate 120g dirve ... Obscure DVD-ROM dual layer burner, and a very old TNT2 video card.

The nFroce SATA would always time out , but if i pluged it into the other SATA chipset (sil something--its at home), and zero problems. The 7 gig install was just a little over 10 mins. --I got it to work with default bios settings.

[murtle]

Athlon 64 3000+ 210*10 CL 2.5-3-3-8
1GB DDR400 noname
Biostar K8VHA Pro 1.1 (bios 1128bf)
Samsung SP0812C 80 GB SATA
Onboard VIA VT 8237 SATA Controller.

[rudi]

Just finished a fresh install of FC3 64 on a Tyan Tiger K8W
(S2875) with two Opterons. Installation on SATA was not a
problem but could not get RAID on the boot partition working
during install. (I was previously using software mirror RAID
on my boot partition).

rudi

[jo42]

FC3 was a no go for me. FC2 with kernel* in exclude in yum.conf was what I needed to keep it running.

Some more details here: http://www.fedoraforum.org/forum/showpost.php?p=143242&postcount=7

[yoonix]

I got FC3 x86_64 running no hassles with an K8N-E Deluxe.

I have 6x200GB SATA Seagate 7200s, all in one big RAID-5 (albeit a software raid.)

FC3 detects everything just fine, no hassles whatsoever.

[Dog-One]

Sweet! One TB of redundant storage. :)

You ought to be able to keep a few files on that machine aay?

[ccl2003]

please help me. i have a similar problem with my a64 3000+, msi k8n neo2 platinum, seagate 80gb sata hdd. after completing installation of fc3 the error message says: "kernel panic....attempted to run init". what is the meaning of this? i was able to run fc3 on an ide hdd before with the same mobo and proc but the shift to sata has been giving me problems. please help me i really need to run fc3 on my home system. thanks a lot.

[cybrjackle]

please help me. i have a similar problem with my a64 3000+, msi k8n neo2 platinum, seagate 80gb sata hdd. after completing installation of fc3 the error message says: "kernel panic....attempted to run init". what is the meaning of this? i was able to run fc3 on an ide hdd before with the same mobo and proc but the shift to sata has been giving me problems. please help me i really need to run fc3 on my home system. thanks a lot.

I have the same mobo running 2 160GB SATA's so it should work ;)

Have you tried to pass noapic to the boot?

As Grub boots up, hit esc to see the kernel, "e" i think for edit go into the line and add noapic to the end of it.

I don't remember the exact combonation of "e"'s and "b's", but once you hit ESC you will see the options in the bottom of grub.

[mlreta]

Guys,

My experience: No problems at all! I installed FC3 from DVD ISO image flawlessly on my machine. Config as follows:

MSI K8N Neo Platinum (nVidia nForce3-250 chipset, integrated SATA, GigaEther, 7.1 AC97 audio, 8x USB 2.0, Firewire)
AMD Athlon64 3000+
Hitachi 160GB SATA 7200RPM
nVidia GeForce 2MX
512MB DDR400 RAM

It installed almost automatically, rebooted with no problems, and is running fine! (and *FAST*!!!!).

Hope this helps.

Mariano
Tortuguitas, Argentina

[boo]

also got a k8n neo2 platinum nf3 board, 3200+
had some troubles when installing fc3 with 2 sata hdds plugged in, couldnt set up swap (illigeal argument error - afaik this error is caused by giving swapon the wrong partition as parameter, dunno whats wrong here), unplugged the second disk, works fine now.

[ruiner_]

I also got it working on my nforce 3 250 gb board. After install I would get a kernel panic on boot, but updating the kernel from rescue mode fixed this.

[vanstrien]

I have a K8T NEO2 - Firewall motherboard and a Western Digital 250G SATA drive. I had some serious woes with the box as shipped by Monarch Computer. The bios settings were fine for booting the DVD, but after install I could boot. Switching to the BIOS optimized settings worked though.

I've got a bunch of normal IDE drives as data drives also on this computer. This means the boot partition is actually hd3,0, even though the boot drive is /dev/sda0.

Now that I've got the bios sorted out the motherboard works like a champ.

[owen]

The only issue I had was with the whopping selection of SATA and PATA controllers on the board. Took me an hour of messing with diffrent combinations of my 3 hard drives (2 PATA, 1 SATA) + CD-ROM till I found one that worked.

All SATA/PATA controllers worked fine for me with FC2 and all SATA controllers
are acting as libata (sd) disks.

However, there is an issue with the Yukon in that ASUS has buggy Vital
Device Property information in the EEPROM and they seem to be unwilling
to fix this.

Worse yet, complaints have apparently been met with "We don't support
open source software." EVEN when the problem was duplicated on Windows.
Newer kernels (2.6.10+) have a patch that explains the problem in your
SYSLOG and works around it, but, prior to that, I had a lot of mysterious
system instability. I've sent a nastygram to ASUS about their attitude, but,
I'd like to encourage everyone here to do the same.

Search for ASUS Yukon VDP and you can find a few articles on the subject
at this point.

I have always liked ASUS, but, with an attitude liek this, I'll start giving my
dollars to more open-source friendly manufacturers.

[Daemon]

I didnt have any problems also with FC3 and MSI K8N New Platinum (nForce3 250GB) + 2x Maxtor's SATA 250GB (16MB). Everything installed perfectly without any glitches :)

[grevedan]

knoppix 3.7 with 2.6 kernel recognises the SIS964 and partitions it - I'm going to retry Fedora later today.

madhippy, can you provide output from lspci?

[legumes]

worked like it should with asus a8v deluxe wi-fi (via k8t800 chipset with via vt8237 sata controller w/1 hd attached).

[Airric]

Owen- Asus posted a dos-executable patch for the VPD errors with the K8V at:

http://www.asus.com/support/download/selectftp.aspx?l1_id=1&l2_id=20&l3_id=1&m_id=3&f_name=vpd_patch.zip~zaqwedc

It worked on my system, and it's not even the K8V! I have a Shuttle SN95G5 XPC with the Marvell Yukon chip.

[stodge]

I didnt have any problems also with FC3 and MSI K8N New Platinum (nForce3 250GB) + 2x Maxtor's SATA 250GB (16MB). Everything installed perfectly without any glitches :)


What ae your SATA drives plugged into? Mine is in SATA4, and Core 3 won't see it.

[dmarinescu]

i can confirm positive results on exclusive sata for k8n-e deluxe (32/64bit) and a7n8x deluxe (32bit) - __but__ for fc3 // why do you need exclusive sata with fc2? /* note that i didn't do more than confirming positive results with fc3 */

regards,
daniel

[dmarinescu]

yes, because you (probably) got only one sata hdd, on sata0

did you hear from anybody who installed the asus driver at install time (i am talking about installing on an exclusive hardware supported raid10, sata2-sata5)

ps
if you don't have the k8n-e (deluxe) skip my comment...

regards,
daniel

[neph04]

MSI K8T NEO2 PRO with VIA onboard sata goes with FC3_64
PROMISE dont run
(sata is auto recognized while booting)

[dmarinescu]

An of course, you have 4 sata hard drives, spreading over the 2 distinct raid controllers, configured in RAID5, right? And also, you installed the 64bit DVD ISO with "install everything"... Well, if you did, that means you've been lucky! Because it happens that if you put 2 sata HDDs (sata0 and sata1) on the first controller and another 2 (sata2 and sata3) on the second controller you will get python errors from anaconda (just before partitioning) if your partitioning scheme looks like:

sda:
/root (1G)
/soft_raid (fill...)

sdb, sdc, sdd:
/swap (1G)
/soft_raid (fill...)

then all 4 soft_raids in md0 (mounted as /) and mbr on sda!

and you would also be amazed to find out that anaconda doesn't sata0 as sda, but as sdc (contrary to the bios settings) and in order to be able to install the whole thing you should go like:

sdc:
/root (1G)
/soft_raid (fill...)

sda, sdb, sdd:
/swap (1G)
/soft_raid (fill...)

but even then, grub will be mislead you rendering your system unbootable, because instead of root(hd0,0) you get root(hd2,0) - so anaconda and grub are not even in sync, not to say a word about bios versus anaconda... it took me awhile to figured this out... so, my advice is:

1. if you have k8n-e with 3 (or 4) sata hdds, do _not_ put them on the secondary raid controller, spread them 2 and 2 (over both controllers)
2. understand that unlike the bios (and grub), which thinks that sata0 and sata1 are on the first controller, they are actually on the second (kernel thinks backwards on this one).
3. don't forget to apply the grub patch (defaulted root(hd2,0) should actually be root(hd0,0)! -- because grub is in sync with common sense and the bios, while the kernel is not...)

ps.
it would be also useful if we test things before giving other generic (news-paper-writer level) advices...

my2c - regards,
daniel

[dmarinescu]

correction, the partioning schemes should have /boot instead of /root (my mistake, too many white nights, i guess... :-))

yours,
daniel

[sandy_mcclintoc]

The Tyan S8228 Twin Opteron board works OK.
I was hoping to use RAID-0 SATA but Fedora 3 just grabbed the two drives and configured them as one big volume. I suppose its a sort of RAID-0

[lprince83068]

Motherboard: MSI K8T Neo-FIS2R
HardDisk: Samsung 160GB SP1614C SATA

Succeeded in installing drive. Although a 160GB drive, during boot it only shows it as a 149GB as well as Win XP Pro SP2 shows it as a 149GB?

What is the problem? Any fixes?

Thanks!

[kmkale]

Just installed on a Tyan Tiger K8W. This board has the Silicon Image Sil3114 SATA controller that can do RAID 0 and 1. Installing to the SATA drives works fine. Installing to a RAID 0 or 1 array (created in the Silicon Image bios) doesn't work. FC2 still sees the two drives as separate.

This isn't a problem for me, I set up a software RAID 1 in FC2 that does the same thing.

Brad

How did you install FC to tyan k8w with sata drive as the boot device? Please guide me as I need to install this machine in my college lab most urgently.

[kmkale]

Just finished a fresh install of FC3 64 on a Tyan Tiger K8W
(S2875) with two Opterons. Installation on SATA was not a
problem but could not get RAID on the boot partition working
during install. (I was previously using software mirror RAID
on my boot partition).

rudi
Hello,
On the k8w did you install boot on sata drive? if yes could you please tell me how? I am unable to get FC3 to boot on the sata drive. Tried inserting the drivers s per instructions found on tyan site & everywhere else but no go.
Please guide me as i need to install this mchine pronto in my college lab.

[ashokpai]

i have been trying 15 hours a day, non stop for the last 8 days. i have tried, ubuntu, fc3 - amd 64 and x86 versions, in all combinations. just coudlnt get my machine working. (my specs are similar to most here - amd 3000+ newcastle, asus k8n, samsung 160gb sata, 40 gb seagate - ide drive, 512 mb ram, etc.). i was trying to install linux on ide/slave and get the grub/ lilo install on the winxp on sata/master. somehow it wouldnt write it on to the mbr on sata disk. i tried it every way - making it slave or master. different version of linux, lilo and grub, all of them drew a blank.
i read someplace that i have to use "noapic" in grub, i am not familiar with the usage, but i can read a bit and use it - or if suggested. in some other forums they suggested that the sata_nv was loaded as a seperate module and this made it not recognise the disk to write to the mbr (even though it could be written to or read - as in mounting drives, etc). the solution there was to include the sata_nv into the kernel and recompile the kernel. for a not-so-seasoned linux user like me this isnt a very happy job - recompiling kernel.
could someone help me here? thanx! help much appreciated.

[ashokpai]

Motherboard: MSI K8T Neo-FIS2R
HardDisk: Samsung 160GB SP1614C SATA

Succeeded in installing drive. Although a 160GB drive, during boot it only shows it as a 149GB as well as Win XP Pro SP2 shows it as a 149GB?

What is the problem? Any fixes?

Thanks!

i too have a samsung sata disk, you can use thier disk manager utility (samsung- www.samsung.com/Products/HardDiskDrive/utilities/ (http://www.samsung.com/Products/HardDiskDrive/utilities/) ). you can use it to partition or format your hard disk, and the maximum usable space (around 160 gb.) yu need to use that before yo install anything, uh, need a floppy too to boot from it and do the needful. thats a small utility.

[Flanker]

i too have a samsung sata disk, you can use thier disk manager utility (samsung- www.samsung.com/Products/HardDiskDrive/utilities/ (http://www.samsung.com/Products/HardDiskDrive/utilities/) ). you can use it to partition or format your hard disk, and the maximum usable space (around 160 gb.) yu need to use that before yo install anything, uh, need a floppy too to boot from it and do the needful. thats a small utility.

The hd-size that Samsung gives is the, well let´s say "marketing"-size. It is the size that the unformated disk has. The formated hd will have a smaller size. All other hd-vendors trying to fool us likewise.
But the main point is the way Linux/Unix creates partitions. Have a look at the man-page of mkfs.ext3 or mkfs.ext2. Check the " -m" option. By default Linux will reserve 5% of the filesystem-blocks for the superuser.
5% from 160 GB makes 9GB. Keep in mind the formated size of your hd and you will get 149 GB.

To avoid this, create your partitions by using the install disk or similar and use the mkfs.ext3 command with the "-m" option.

cu

[ashokpai]

The hd-size that Samsung gives is the, well let´s say "marketing"-size. It is the size that the unformated disk has. The formated hd will have a smaller size. All other hd-vendors trying to fool us likewise.
But the main point is the way Linux/Unix creates partitions. Have a look at the man-page of mkfs.ext3 or mkfs.ext2. Check the " -m" option. By default Linux will reserve 5% of the filesystem-blocks for the superuser.
5% from 160 GB makes 9GB. Keep in mind the formated size of your hd and you will get 149 GB.

To avoid this, create your partitions by using the install disk or similar and use the mkfs.ext3 command with the "-m" option.

cu

u r correct there. i hadnt seen the correct numbers, initially, when i had installed my winxp, it just showed me 130 gb or so. later, i had to get the disk manager to fix it. yeah, its the marketing numbers that usually fool us - there's plenty of debate online this regarding the "available" disk space, "total" disk space, "formatted" disk space. thanks for pointing it out. i did a bit of digging and am wiser now :)

[kmkale]

I got my Tyan k8w to work with the sata disk after a fashion by inserting the drivers during install by doing linux dd.
Also you may find the following usefull for installing the mbr. It workes for me on a 64bit amd bord from asus but did not work for this dual procesor tyan k8w board.
Here goes............................ you can ignore the raid stuff if you dont want to use it.

Overall approach - Here are the high-level steps to get the beast running smoothly:

1) Install FC3, creating bootable RAID and second RAID LVM group,
2) Partially complete GRUB install,
3) Complete RAID install,
4) Complete GRUB install,
5) Test, test, and more test

DETAILS:
--------

1) INSTALL FC3, CREATING BOOTABLE RAID AND SECOND RAID LVM GROUP. Keys to success: both drive pairs must be partitioned exactly the same, with the appropriate partitions matched into RAID1 arrays. On the primary bootable array, I reserved 100MB for use with md0 (on both drives), 2GB for swap (both drives), and allocated the remaining space as md1. On the second drive pair, I allocated all the space to md2. I then mapped /boot to md0, and joined md1 and md2 into a LVM volume group, and mapped / to the new volume group.

At completion of the install, I tried a reboot, and the machine froze at GRUB.

2) PARTIALLY COMPLETE GRUB INSTALL - keys to success: boot from your CD using "linux rescue" option to get a command prompt. Change root to the newly created system (>> chroot /mnt/sysimage), and run grub. Below are the commands I used (you would substitute for your first SATA hard disk - mine was /dev/sda)

grub
> device (hd0) /dev/sda
> root (hd0,0)
> setup (hd0)

These commands make the first hard disk of your RAID array bootable. However, the second can't be made bootable until RAID is up and running properly. See step 3.

3) COMPLETE RAID INSTALL - Keys to success: boot the new hard disk, and check to see that your RAID arrays are working properly, using > cat /proc/mdstat.

[root@jigsaw ~]# cat /proc/mdstat

Personalities : [raid1]
md1 : active raid1 sdb2[1] sda2[0]
33945280 blocks [2/2] [UU]

md2 : active raid1 sdc1[0] sdd1[1]
156288256 blocks [2/2] [UU]

md0 : active raid1 sdb1[0] sda1[1]
104320 blocks [2/2] [UU]

This shows a properly working array. Note md0 - both partitions are listed. My first time through, I found that I was missing the other half of my RAID pair. SO - I needed to add them "hot" and rebuild the RAID. Here is the trick:

>> mdadm /dev/md0 --add /dev/sdb1

This will "hot add" /dev/sdb1 back into /dev/mdO and rebuild the RAID pair. For larger drives, this syncing make take a while. You can check the status with "cat /proc/mdstat"

4) COMPLETE THE GRUB INSTALL - Keys to success: once the /boot partition is properly synced (see step 3), then you can tell GRUB to boot from either disk. Let's repeat step two, activating the MBR for the first partition on each drive of the RAID array on /boot.

grub
> device (hd0) /dev/sda
> root (hd0,0)
> setup (hd0)
> device (hd1) /dev/sdb
> root (hd1,0)
> setup (hd1)

If you try this without completing the RAID install, you'll get "ERROR 15: file not found". Why? the /boot partition isn't properly mirrored across the disks.

5) TEST, TEST, and TEST - Keys to success: patience. a) power down, b) unplug a drive, c) power up and watch the bios, d) ensure you get a boot, e) check to see if all data is accessible, f) power down, g) replug the drive, h) power up and watch the bios, i) rebuild the array using "mdadm /dev/mdx --add /dev/sdyy"

[wdtj]

Not exactly Fedora related, but worth a menton here.

Well, after trying to get my MSI K8T800 with the VT8237 chip to talk SATA to two new Western Digital WD800JD disks, I found there is a compatibility issue with the WD800JD drives. Seems they want to talk SATA2 and the VT8237 get's confused. It only does SATA150.

I ended sending the WD800JD to WDC and they sent me 2 new WD1200 sata drives that did work.

Now, if only I could get hardware RAID to work with FC4T1.

[pza]

Gigabyte K8NS 939 Ultra has 4 SATA channels. 2 are with some silicon chip, and to nvidia ones (which are hot pluggable). The FC3 installation only works with the 2 nvidia channels, however using the latest FC3 kernel update, you can access all 4 channels.

FC4 (Test 1) installation works with all 4 channels.

[JLF_65]

Not exactly Fedora related, but worth a menton here.

Well, after trying to get my MSI K8T800 with the VT8237 chip to talk SATA to two new Western Digital WD800JD disks, I found there is a compatibility issue with the WD800JD drives. Seems they want to talk SATA2 and the VT8237 get's confused. It only does SATA150.

I ended sending the WD800JD to WDC and they sent me 2 new WD1200 sata drives that did work.

Now, if only I could get hardware RAID to work with FC4T1.

The K8T800 doesn't do hardware RAID. It's software RAID only. It has drivers for Windows built into the BIOS, and a driver disk for Windows, but these are just software RAID targetted at Windows. If you don't need Windows compatibility, don't even try to use these. Just stick to standard linux software RAID and you'll be fine. The linux RAID driver from VIA for Windows compatibility is really old and buggy. I don't recall seeing any reports of people using it successfully.

I have two 80G Hitachi SATA drives running under linux software RAID in FC3 on my MSI K8T800 mobo. One thing, as noted above, booting off RAID is a royal pain. I suggest you not bother. Just make the boot partition non-RAID and the rest of the partitions RAID.

[wdtj]

Thank you, I know the VT8237 will not do hardware raid. The problem I had was the the drives were never visible to the BIOS, so I couldn't even define a hardware RAID.

I called WDC support. They acknowledged that there is a compatiblity issue. They shipped me two new 120Gb Sata drives that work great.

Just wanted others to know about the problem so it doesn't cause them a months worth of headaches like it did me.

[Ridgerunner]

I got my Tyan k8w to work with the sata disk after a fashion by inserting the drivers during install by doing linux dd.
Also you may find the following usefull for installing the mbr. It workes for me on a 64bit amd bord from asus but did not work for this dual procesor tyan k8w board.
Here goes............................ you can ignore the raid stuff if you dont want to use it.

Overall approach - Here are the high-level steps to get the beast running smoothly:

1) Install FC3, creating bootable RAID and second RAID LVM group,
2) Partially complete GRUB install,
3) Complete RAID install,
4) Complete GRUB install,
5) Test, test, and more test

DETAILS:
--------

1) INSTALL FC3, CREATING BOOTABLE RAID AND SECOND RAID LVM GROUP. Keys to success: both drive pairs must be partitioned exactly the same, with the appropriate partitions matched into RAID1 arrays. On the primary bootable array, I reserved 100MB for use with md0 (on both drives), 2GB for swap (both drives), and allocated the remaining space as md1. On the second drive pair, I allocated all the space to md2. I then mapped /boot to md0, and joined md1 and md2 into a LVM volume group, and mapped / to the new volume group.

At completion of the install, I tried a reboot, and the machine froze at GRUB.

2) PARTIALLY COMPLETE GRUB INSTALL - keys to success: boot from your CD using "linux rescue" option to get a command prompt. Change root to the newly created system (>> chroot /mnt/sysimage), and run grub. Below are the commands I used (you would substitute for your first SATA hard disk - mine was /dev/sda)

grub
> device (hd0) /dev/sda
> root (hd0,0)
> setup (hd0)

These commands make the first hard disk of your RAID array bootable. However, the second can't be made bootable until RAID is up and running properly. See step 3.

3) COMPLETE RAID INSTALL - Keys to success: boot the new hard disk, and check to see that your RAID arrays are working properly, using > cat /proc/mdstat.

[root@jigsaw ~]# cat /proc/mdstat

Personalities : [raid1]
md1 : active raid1 sdb2[1] sda2[0]
33945280 blocks [2/2] [UU]

md2 : active raid1 sdc1[0] sdd1[1]
156288256 blocks [2/2] [UU]

md0 : active raid1 sdb1[0] sda1[1]
104320 blocks [2/2] [UU]

This shows a properly working array. Note md0 - both partitions are listed. My first time through, I found that I was missing the other half of my RAID pair. SO - I needed to add them "hot" and rebuild the RAID. Here is the trick:

>> mdadm /dev/md0 --add /dev/sdb1

This will "hot add" /dev/sdb1 back into /dev/mdO and rebuild the RAID pair. For larger drives, this syncing make take a while. You can check the status with "cat /proc/mdstat"

4) COMPLETE THE GRUB INSTALL - Keys to success: once the /boot partition is properly synced (see step 3), then you can tell GRUB to boot from either disk. Let's repeat step two, activating the MBR for the first partition on each drive of the RAID array on /boot.

grub
> device (hd0) /dev/sda
> root (hd0,0)
> setup (hd0)
> device (hd1) /dev/sdb
> root (hd1,0)
> setup (hd1)

If you try this without completing the RAID install, you'll get "ERROR 15: file not found". Why? the /boot partition isn't properly mirrored across the disks.

5) TEST, TEST, and TEST - Keys to success: patience. a) power down, b) unplug a drive, c) power up and watch the bios, d) ensure you get a boot, e) check to see if all data is accessible, f) power down, g) replug the drive, h) power up and watch the bios, i) rebuild the array using "mdadm /dev/mdx --add /dev/sdyy"

Did you have 4 hard drives for this install??

Ken

[kmkale]

Did you have 4 hard drives for this install??

Ken

YES. Had 4 drives 2 SATA & 2 IDE. Had trouble inserting mbr on SATA. I found this post somewhere on the net while trying to solve this problem. Found it VERY usefull so gave it here verbatim. My many thanks to the original poster.

[Ridgerunner]

kmkale

I think I have my raid working using your install. How ever when I used "mdadm /dev/md0 --add /dev/sdb1"
it told me: "mdadm: hot add failed for /dev/sdb1: Invalid argument"

when I use : "cat /proc/mdstat"
I get:
Personalities : [raid1]
md1 : active raid1 sdb2[1] sda2[0]
1052160 blocks [2/2] [UU]

md2 : active raid1 sdb3[1] sda3[0]
76943232 blocks [2/2] [UU]

md0 : active raid1 sdb1[1] sda1[0]
152512 blocks [2/2] [UU]

unused devices: <none>

so I think every thing is working.

Do you agree?
Ken

[kmkale]

Yes. Just shut down, pull the plug on one of the reid drives restart & check if the data is there on the other drive. Write some data to it, shut down, reconect the unplugged drive, restart & let it resync. Then pull off the other drive & check the file you created if its present & correct.

[subgenius]

Motherboard: Asus A8N-E
RAID card: Areca 1220
Drives: 7 WD Raptor 10000rpm 74GB drives
LUNs: 1 RAID 0 (2 of the drives), 1 RAID 5 (4 drives), 1 hotspare (configured via Areca BIOS)

only major snafu was enabling CONFIG_SCSI_MULTI_LUN=y in kernel options.

[Knudson]

I can say OK for:

MSI K8T800 socket 754 with FC3 and 1 seagate barracuda 7200.7 120GB sata + 1 maxtor 120GB sata

MSI K8N Neo2 Plat socket 939 with FC4 and 1 maxtor 250GB sata

[judung]

M/B: DFI NFII Ultra B w/SiI3114 onboard
Following step 1 for FC4, I skip to step 4 directly and everything's going pretty smoothly.

BTW, /boot can only reside on RAID1 (/dev/md0). The rest (/) is put on /dev/md1 (RAID0).

I got my Tyan k8w to work with the sata disk after a fashion by inserting the drivers during install by doing linux dd.
Also you may find the following usefull for installing the mbr. It workes for me on a 64bit amd bord from asus but did not work for this dual procesor tyan k8w board.
Here goes............................ you can ignore the raid stuff if you dont want to use it.

Overall approach - Here are the high-level steps to get the beast running smoothly:

1) Install FC3, creating bootable RAID and second RAID LVM group,
2) Partially complete GRUB install,
3) Complete RAID install,
4) Complete GRUB install,
5) Test, test, and more test

DETAILS:
--------

1) INSTALL FC3, CREATING BOOTABLE RAID AND SECOND RAID LVM GROUP. Keys to success: both drive pairs must be partitioned exactly the same, with the appropriate partitions matched into RAID1 arrays. On the primary bootable array, I reserved 100MB for use with md0 (on both drives), 2GB for swap (both drives), and allocated the remaining space as md1. On the second drive pair, I allocated all the space to md2. I then mapped /boot to md0, and joined md1 and md2 into a LVM volume group, and mapped / to the new volume group.

......

At completion of the install, I tried a reboot, and the machine froze at GRUB.

4) COMPLETE THE GRUB INSTALL - Keys to success: once the /boot partition is properly synced (see step 3), then you can tell GRUB to boot from either disk. Let's repeat step two, activating the MBR for the first partition on each drive of the RAID array on /boot.

grub
> device (hd0) /dev/sda
> root (hd0,0)
> setup (hd0)
> device (hd1) /dev/sdb
> root (hd1,0)
> setup (hd1)

If you try this without completing the RAID install, you'll get "ERROR 15: file not found". Why? the /boot partition isn't properly mirrored across the disks.

5) TEST, TEST, and TEST - Keys to success: patience. a) power down, b) unplug a drive, c) power up and watch the bios, d) ensure you get a boot, e) check to see if all data is accessible, f) power down, g) replug the drive, h) power up and watch the bios, i) rebuild the array using "mdadm /dev/mdx --add /dev/sdyy"

[RocketRay]

I was able to do it, but I had to remove my SATA controller card and just use the motherboard's. When I reconnected the card I couldn't boot, even though the BIOS said it would boot the first drive on the motherboard's controller. Fortunately I don't have anything important on that drive so I'm not missing it (yet).

[sej7278]

so it seems that the Silicon Image 3114 chipset and some VIA chipset are the only ones that work - and everyone seems to be using Athlon, not P4.

[cybrjackle]

so it seems that the Silicon Image 3114 chipset and some VIA chipset are the only ones that work - and everyone seems to be using Athlon, not P4.

How did you come to that? There are a lot that work.

[sidster]

Hi everyone
This is my first post but i've been browsing this and numerous other forums for weeks.
My setup is
GA-K8NF9 (Nforce4-4x chipset)
AMD64 3000+
1gb Corsair Ram
Seagate 80gb SATA
NVidia 6600 128mb GPU

I simply can't get FC4 to run. So maybe the trend has something to do with chipsets rather than manufacturers. I get all the way through the install but run into a kernel panic on the first boot.
Based on the info that rushes past during boot it looks as if the proccess halts when trying to mount the SATA drive. My conclusion is that my hardware is so rare that there is no built in support and/or configuration settings for it in FC4.

Can this be true? Because it appears as if that's what this particular forum thread is about: SATA/AMD hardware compatibilty with fedora.

Looking forward to learning as much as I can about Linux.

:-)

[Flanker]

I ran into the same error after my second attempt to install FC4.
The solution for me was to delete all new created partitions with fdisk using a live-cd (knoppix). Maybe you don´t have to do that, but my partitontable was wrong after the fist installaton attempt.
Next thing was to boot again from FC4 DVD and use the text-install of Fedora ("linux text").
The installation worked and after the first boot all, i had to do was to install the previously downloaded NVIDIA-driver.
Maybe this will work for you to.

bye

[sidster]

Thanks I think I'll try that. Formating was my last resort cause I've got XP on a separate partition. It looks like that is the very thing stoping me from running FC4. Figures...Thanks Bill. I'll probably have to get FC4 set up smoothly first and add the windoze partition later.

[cr_nandu]

I know the thread is about FC2, but I used FC4 final X86_64 and it detected my SATA which none of the other distributions was able to detect. I mean none because I tried from Debian, Ubuntu, Kanoppix, Kanotix, Mepis, Libranet, Litrix, Slynux, Mandriva and what not. FC4 wins the bet. All I read about my HDD is also a black listed one in various forums, but FC4 showed me how to do the stuff. My HDD is: Seagate Baracuda with Silicon Image 3112A controller (the worst case scenario one). At the time of install itself FC4 loaded sata_sil and straightaway recognised my HDD. I had to use the option ide=nodma and I don't know as whether that was the cause of detecting my HDD, but it did help. My motherboard is Optronix K200G-MLF (I think it is basically based on ASUS with ATI X200 Chipset (another worst case scenario)). Thanks to FC4 team for making this happening for me.

[richmlpdx]

I have installed FC4 x86_64 on the following:
MSI RS480M2
Athlon 64 3000+
2GB Ram
3 80GB Seagate SATA drives.

I had to use "linux noapic acpi=off" and set the BIOS to use SATA RAID rather than SATA Controller. If the BIOS is set to SATA controller, the install will fail.

[fpoole]

Confirmed:

FC4 x86_64
MSI K8N Neo4 Platinum
AMD Athon64 3200+
Seagate ST3160023AS Barracuda 7200.7 (SATA)
nVidia SATA Drivers (sata_nv)

Struggling with:
Plextor PX-7xxSA installation

[sirbrett]

Confirmed:

FC4 x86_64
EPoX EP-8KDA3I
nForce3 250Gb
Athlon 64 3000+
Seagate ST3120827AS 7200.7
sata_nv driver

[toracat]

motherboard: DFI K8M800-MLVF (VIA VT8237 chipset)
single SATA drive: Seagate 250GB

I have been trying to install FC without success. If I use an IDE drive, there is no problem. However I want to use the SATA drive. The installtion process goes through without a hitch. But the system does not boot and gets stuck after grub stage1_5. I tried reinstalling by booting from the rescue CD and issuing root hd(0,0) etc, etc at the grub prompt. No dice. :(

The only successful installation I got was FC3 with lilo (but NOT with grub). :) But I want to get FC4 and grub working.

Did anyone reading the forum succeed in installing FC4 on this particular motherboard? :confused:

Akemi

[PaulJavaJedi]

Works:
Gigabyte GA-K8N-Ultra
Nforce 4 controller
2x Western Digital WD1600JD (160GB SATA, 8MB Cache)
(not using Sil controller)
FC4+updates to 8/8/2005

Notes:
- Not using the Sil chip (provides additional 4x SATA on MB) but seems to have configured in kernel ok during install.
- 2x Western Digital WDJD1600JD attached to nForce4 controller - NOT using RAID function of controller.
- With defaults, Install was OK but on reboot would not boot, seems Grub never loaded
- Changed BIOS setting for onboard RAID (nForce4) to off
- BIOS then sees disks as standard stand alone & Grub loads correctly (there was much rejocing)
- Using software RAID accross disks.

Misc Notes:
- Had one instance of instability (Athlon64 3200, 1GB Crucial mem in 2x512 DDR config), disabled acpi with noacpi on Grub kernal options and has not re-occured.

[Picomp314]

Works:
Soltek SL-K8TPro-939
Promise controller
Maxtor 200GB sata
FC4 x86_64

Had to disable the default VIA sata controller from the BIOS, because system would freeze at "Verifying DMI Pool Data". Rebooted with promise only, and FC4 installed like a breeze without any kernel flags. I can't wait to start using the best 64bit linux around!

[juha_t_k]

Mobo asus a8V with additional SIL3112 pci sata controller
4xMaxtor 250G SATA disks

sda
/boot RAID1
LVM RAID5
sdb
/boot RAID1
LVM RAID5
sdc
/boot RAID1
LVM RAID5
sdd
/boot RAID1
LVM RAID5

LVM
swap
/

So boot is mirrored (RAID1) over all 4 disks and root directory and swap is on RAID5, do not know was this sensible. Of course if sda is killed then I cannot boot because MBR is missing from others, but installing MBR is quite easy. Any good ideas how to make this better?

Had terrible problems to get it working with all 4 disks, independently what disk setup used (RAID0,1,5 or LVM) then I marked that one option on installation where you have advanced setting for boot/disk druid. From there I moved the disks to the same order as in BIOS. Now it works perfectly.

[Seve]

Hi:
Has anyone installed FC on a SATA2 Seagate by any chance?

I would like to pick a couple up for my new box as they have NCQ as well.

Thanks

Seve

[Demz]

have you searches www.linuxforums.org i think it is? or www.linuxQuestions.org

[Seve]

have you searches www.linuxforums.org i think it is? or www.linuxQuestions.org

Hi:
Thanks for the suggestions. From what I gleaned from the searching is that as long as Linux recogonizes the SATA Controller it should be okay.....I guess I will find out.

Seve

[Demz]

Hi:
Thanks for the suggestions. From what I gleaned from the searching is that as long as Linux recogonizes the SATA Controller it should be okay.....I guess I will find out.

Seve
it should be aslong as the kernel picks it up during install, im not sure if the kernel supports or would support SATA2 HDD's yet but you may wanna look

[blkstorm]

This is my first posting in fedoraforum.org.

(Please be aware that I'm Korean and not good with English writing)

My team needed a powerful linux machine to make linux kernel and device driver for embedded system so that I ordered AMD Athlon 64 Manchester 3800+.

CPU : AMD Athlon 64-X2 Manchetser 3800+
RAM : 1GB (512MB x2)
M/B : ASUS A8N-SLI Premium
HDD : Western Digital 160GB SATA (2EA)
VGA : ATI Radeon X300
OS : Fedora Core 4 x86_64

It took 5 days for me to see grub message.

1) First of all, FC4 is not supporting SiI3114 properly. I've downloaded drivers for FC/Redhat from siliconimage.com, but failed.

2) In BIOS Setup mode(CMOS Setup), disable Sil3114 chipset in Onboard chip configuration, and enable NV.

3) Boot with FC4 Disc #1.

4) In boot prompt, type,

boot : linux noapic nolapic [Enter]

(I spend three days finding this)

If "noapic nolapic" is omitted, the system hangs showing message "Disable IRQ #5" while loading sata_nv drive. I think IRQ number might vary depending on M/B.

(It seems that there's IRQ problem in RAID Controller and apic with FC4.)

5) Continue installation

6) Before rebooting, disable NV Chipset in BIOS Setup mode(CMOS Setup).

If this chipset is enabled, the system never boots up. (spend almost two days finding this). At last, no chipset driver caring SATA is enabled in BIOS Setup.

Any further question would be welcomed.

Thanks.

[Seve]

Hi:
Has anyone installed FC on a SATA2 Seagate by any chance?

I would like to pick a couple up for my new box as they have NCQ as well.

Thanks

Seve
Hi: Just to update; I can confirm a successful FC4 32bitSMP install on an ASUS AN32SLI using a SATA 2 Seagate harddrive. It went very smoothly on the NVIDIA controller [BIOS configured as JBOD] This board also has a Silicon Image chip on it as well [Raid or JBOD]. FC4 did not see this and I could not find any driver that would work during the install. So just a head's up.
The box is dual booted to XPPro also on the Nvidia Controller, X24400, 2Gig of Ram, 2 7800GTX Top cards [SLI], 4 SATA2 Drives, 1 ATA133, DVD, floppy,24 " Dell, Firewire and an X-fi Creative Sound Card [which is awesome, however it does not work under Linux at this point AFAIK. The on-board sound is recognized by FC4 and works so-so to okay. I still have to install the Nvidia Drivers, however I expect they should work?
The new drivers from Nvidia worked like a charm and even configured my xorg.conf for me. The VidCards are running in SLI mode

Seve

[Sam Weldon]

ASUS K8V Deluxe Have FC4 installed

[hotdog]

I had a pretty much problem free 64 bit SMP install on a brand new Asus A8N-VM CSM based system (this motherboard uses the NVIDIA 6150/430 chipset). The installer didn't see my SATA hard disk at first, but all I had to do was tell it to load the sata_nv module and it installed just fine.

Two things I did before install may have given me less trouble than I might have otherwise had though, I updated the BIOS to the latest version (NVIDIA linux forums and the ASUS forums have revealed lots of bugs in the BIOS for this motherboard, especially the first release) and used the Fedora Core '4.2' unofficial respin from http://fedora.isphuset.no/ so that the installer would be able to use a more up to date version of sata_nv than the stock install does.

[mick_s3]

I had a pretty much problem free 64 bit SMP install on a brand new Asus A8N-VM CSM based system (this motherboard uses the NVIDIA 6150/430 chipset). The installer didn't see my SATA hard disk at first, but all I had to do was tell it to load the sata_nv module and it installed just fine.

Two things I did before install may have given me less trouble than I might have otherwise had though, I updated the BIOS to the latest version (NVIDIA linux forums and the ASUS forums have revealed lots of bugs in the BIOS for this motherboard, especially the first release) and used the Fedora Core '4.2' unofficial respin from http://fedora.isphuset.no/ so that the installer would be able to use a more up to date version of sata_nv than the stock install does.


I am trying to install 4 on a system with the same MB. Thanks for the tip on loading sata_nv, that at least allowed the install to proceed past the "you have no disks please check your hardware for errors" message, however once the install completes and I attempt to boot from the HD I get "disk read error press c+a+d to restart"

Any help would be greatly appreciated.

[hotdog]

Hmmmmmm, not sure what you problem is here, if sata_nv worked well enough to install onto the disk then it ought to be able to read it on reboot. At what point does the error message appear? During POST, loading GRUB, booting linux?

Did you make sure the motherboard BIOS was up to date before installing? I'd strongly recommend you use the latest BIOS, the original version was terrible.

Also, were you installing from the stock Fedora Core 4 install media, or the updated unofficial respins? It's just possible that there's an incompatibility between the chipset SATA controller and the version of sata_nv in the the stock install media but not in the later respins.

[mick_s3]

Hmmmmmm, not sure what you problem is here, if sata_nv worked well enough to install onto the disk then it ought to be able to read it on reboot. At what point does the error message appear? During POST, loading GRUB, booting linux?

Did you make sure the motherboard BIOS was up to date before installing? I'd strongly recommend you use the latest BIOS, the original version was terrible.

Also, were you installing from the stock Fedora Core 4 install media, or the updated unofficial respins? It's just possible that there's an incompatibility between the chipset SATA controller and the version of sata_nv in the the stock install media but not in the later respins.
I finally got it to work, thanks for your reply.

I went back through the install and this time left the format hd options to default.
I guess I must have done something dumb there the first time... :)

Once I got the install up and running, I had to use the MB CD to build drivers for the onboad NIC and Sound.

The system has been up for a couple of weeks, the only issue I notice is sometimes the machine pauses while working in Gnome. I think I may need an update to the video driver. The machine is mostly used as a server/common storage area soI am not that concerned.

Thanks for taking the time to reply, I do appreciate that.

[hotdog]

Interesting that you're using the NVIDIA drivers for the NIC and sound.

The forcedeth driver in the standard kernel (at least recent versions of if) works without any problems with the NIC on this motherboard, my ethernet got detected and correctly configured during Fedora installation, no need for me to install any additional drivers. It's possible that this wouldn't work with the standard Fedora installation media though, and only with the more up to date kernel on the respins.

Sound is a slightly more awkward matter though. My machine is planned for use as a HTPC as well as general desktop so I wanted to use ALSA rather than NVIDIA's (rather retro) OSS only driver. ALSA hasn't quite caught up with the onboard sound yet, but it's being worked on (https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1678). For the time being a workaround patch gives me sound, but stereo only. I couldn't get the OSS driver downloaded from NVIDIA's website to work at all, I gather the Asus board uses a different sound chip than most of the NVIDIA 6130/430 chipsset based boards.

[mick_s3]

Interesting that you're using the NVIDIA drivers for the NIC and sound.

The forcedeth driver in the standard kernel (at least recent versions of if) works without any problems with the NIC on this motherboard, my ethernet got detected and correctly configured during Fedora installation, no need for me to install any additional drivers. It's possible that this wouldn't work with the standard Fedora installation media though, and only with the more up to date kernel on the respins.

Sound is a slightly more awkward matter though. My machine is planned for use as a HTPC as well as general desktop so I wanted to use ALSA rather than NVIDIA's (rather retro) OSS only driver. ALSA hasn't quite caught up with the onboard sound yet, but it's being worked on (https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1678). For the time being a workaround patch gives me sound, but stereo only. I couldn't get the OSS driver downloaded from NVIDIA's website to work at all, I gather the Asus board uses a different sound chip than most of the NVIDIA 6130/430 chipsset based boards.

That was the only way I could get the NIC to work, it did not auto-detect it for some reason.

I did up2date once I got the machine up and running, and had to do it twice. The first time I just downloaded the kernel update (with no source) and when I booted to the newer kernel the NIC did not work. I had to reboot to the old kernel, d/l the update with source, then rebuild the driver again for the new build.... hope I don't have to continue to do that every time I update :)

[perry753]

Here's my system with SATA running FC4 x86_64:
Asus K8N nForce 3 250GB for socket 754 AMD
nForce controller
Western Digital 250GB SATA drive and Hitachi 120GB IDE (RAID 0)

[holr]

I have fedora core 4 running on a sony vaio s570p. Its the only flavour of linux I have tried so far that works on this machine!

[txcrittr]

I tried repeatedly to get FC4 x86_64 installed on an ABIT KV8 MAX3 running an Athlon 64 3200+. I was not using a SATA drive and I never got it installed. Got an error message during "Performing post install processing" step. A bug report has been opened. I was able to get FC4 32 bit installed - first try - on the system. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=178516

[daviden]

Hi: Just to update; I can confirm a successful FC4 32bitSMP install on an ASUS AN32SLI using a SATA 2 Seagate harddrive. It went very smoothly on the NVIDIA controller [BIOS configured as JBOD] This board also has a Silicon Image chip on it as well [Raid or JBOD]. FC4 did not see this and I could not find any driver that would work during the install. So just a head's up.
The box is dual booted to XPPro also on the Nvidia Controller, X24400, 2Gig of Ram, 2 7800GTX Top cards [SLI], 4 SATA2 Drives, 1 ATA133, DVD, floppy,24 " Dell, Firewire and an X-fi Creative Sound Card [which is awesome, however it does not work under Linux at this point AFAIK. The on-board sound is recognized by FC4 and works so-so to okay. I still have to install the Nvidia Drivers, however I expect they should work?
The new drivers from Nvidia worked like a charm and even configured my xorg.conf for me. The VidCards are running in SLI mode

Seve
Hi
I am facing the same problems here too. I am trying to install a SATA II HD on FC4 but it only recognize the drive as SATA (I've checked the speed). My MoBo is ABIT NI8 SLI and it has 6 SATA II ports (4 by NV and 2 by Sil). In the BIOS, it only reads the IDE and 4 SATA II ports by NV and never the Sil 3132 SATA II ports.

How did you fix these problems last time?

Thanks

[Seve]

Hi
I am facing the same problems here too. I am trying to install a SATA II HD on FC4 but it only recognize the drive as SATA (I've checked the speed). My MoBo is ABIT NI8 SLI and it has 6 SATA II ports (4 by NV and 2 by Sil). In the BIOS, it only reads the IDE and 4 SATA II ports by NV and never the Sil 3132 SATA II ports.

How did you fix these problems last time?

ThanksHi:
With FC4 the Sil Controller was not recognized at all as you know during the install of FC4. Silcon Image has some driver support, located here http://www.siliconimage.com/support/supportsearchresults.aspx?pid=32&cid=3&ctid=2&osid=1&
I never bothered and left the installations on the NV controller.[Least effort principle]
The good news is that SATA 2 appears to be recognized correctly under the kernels released so far with FC5 Test 2 and as you can see (below). It looks like my SATA 2 drive connected to the Sil controller is seen correctly under FC5 as well......very interesting. I have not testetd / compared speeds, so I can't comment on that. FC5 is supposed to released in Mid March.

I am on FC5 x86_64 test2 at the moment but I think FC4 has released a 2.6.15 xxx kernel which may see the drives correctly. Although I have not gotten around to testing it.

kernel 2.6.15-1.1898_FC5 x86_64

dmesg | grep SATA



ata1: SATA max UDMA/133 cmd 0xDC00 ctl 0xD882 bmdma 0xD400 irq 225
ata2: SATA max UDMA/133 cmd 0xD800 ctl 0xD482 bmdma 0xD408 irq 225
ata1: SATA link up 3.0 Gbps (SStatus 123)
ata2: SATA link up 3.0 Gbps (SStatus 123)
ata3: SATA max UDMA/133 cmd 0xD080 ctl 0xD002 bmdma 0xC800 irq 233
ata4: SATA max UDMA/133 cmd 0xCC00 ctl 0xC882 bmdma 0xC808 irq 233
ata3: SATA link down (SStatus 0)
ata4: SATA link up 3.0 Gbps (SStatus 123)
ata5: SATA max UDMA/100 cmd 0xFFFFC20000030000 ctl 0x0 bmdma 0x0 irq 58
ata6: SATA max UDMA/100 cmd 0xFFFFC20000032000 ctl 0x0 bmdma 0x0 irq 58
ata5: SATA link down (SStatus 0)
ata6: SATA link up 3.0 Gbps (SStatus 123)

dmesg|grep -i sata

sata_nv 0000:00:10.0: version 0.8
ata1: SATA max UDMA/133 cmd 0xDC00 ctl 0xD882 bmdma 0xD400 irq 225
ata2: SATA max UDMA/133 cmd 0xD800 ctl 0xD482 bmdma 0xD408 irq 225
ata1: SATA link up 3.0 Gbps (SStatus 123)
nv_sata: Primary device added
nv_sata: Primary device removed
nv_sata: Secondary device added
nv_sata: Secondary device removed
scsi0 : sata_nv
ata2: SATA link up 3.0 Gbps (SStatus 123)
nv_sata: Primary device added
nv_sata: Primary device removed
nv_sata: Secondary device added
nv_sata: Secondary device removed
scsi1 : sata_nv
sda:<4>nv_sata: Primary device added
nv_sata: Primary device removed
nv_sata: Secondary device added
nv_sata: Secondary device removed
sda1 sda2 <<4>nv_sata: Primary device added
nv_sata: Primary device removed
nv_sata: Secondary device added
nv_sata: Secondary device removed
sda5<4>nv_sata: Primary device added
nv_sata: Primary device removed
nv_sata: Secondary device added
nv_sata: Secondary device removed
sdb:<4>nv_sata: Primary device added
nv_sata: Primary device removed
nv_sata: Secondary device added
nv_sata: Secondary device removed
ata3: SATA max UDMA/133 cmd 0xD080 ctl 0xD002 bmdma 0xC800 irq 233
ata4: SATA max UDMA/133 cmd 0xCC00 ctl 0xC882 bmdma 0xC808 irq 233
ata3: SATA link down (SStatus 0)
scsi2 : sata_nv
ata4: SATA link up 3.0 Gbps (SStatus 123)
nv_sata: Primary device added
nv_sata: Primary device removed
nv_sata: Secondary device added
nv_sata: Secondary device removed
scsi3 : sata_nv
sdc:<4>nv_sata: Primary device added
nv_sata: Primary device removed
nv_sata: Secondary device added
nv_sata: Secondary device removed
sata_sil24 0000:01:00.0: version 0.23
ata5: SATA max UDMA/100 cmd 0xFFFFC20000030000 ctl 0x0 bmdma 0x0 irq 58
ata6: SATA max UDMA/100 cmd 0xFFFFC20000032000 ctl 0x0 bmdma 0x0 irq 58
ata5: SATA link down (SStatus 0)
scsi4 : sata_sil24
ata6: SATA link up 3.0 Gbps (SStatus 123)
scsi5 : sata_sil24

fdisk -l

Disk /dev/hdc: 203.9 GB, 203928109056 bytes
255 heads, 63 sectors/track, 24792 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hdc1 * 1 12680 101852068+ c W95 FAT32 (LBA)

Disk /dev/sda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 2563 20587266 7 HPFS/NTFS
/dev/sda2 2564 14592 96622942+ f W95 Ext'd (LBA)
/dev/sda3 14593 14593 8032+ 8e Linux LVM
/dev/sda5 2564 9493 55665193+ 7 HPFS/NTFS
/dev/sda6 9494 14592 40957686 7 HPFS/NTFS

Disk /dev/sdb: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdb1 * 1 13 104391 83 Linux
/dev/sdb2 14 14593 117113850 8e Linux LVM

Disk /dev/sdc: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdc1 * 1 13 104391 83 Linux
/dev/sdc2 14 14593 117113850 8e Linux LVM

Disk /dev/sdd: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdd1 1 14593 117218241 7 HPFS/NTFS

Seve

[daviden]

Hi Seve...

I upgrade the kernel to 2.6.1-5 and it's working now. *me respect* :) The board succesfully works on SATA II HD..Thanks very much for your information.

Dave

[jruiseco]

I just finished my install. The system is an Asus A8N Premium Board with an AMD Athlon 64 X2 3800+ running 2G of generic DDR400 ram, an NVidia PCI-X 7800GT card from BFG (Overclocked). The drives are 2 SATA Western Digital Caviar WD 1600JS, an old CDRW, a brand new LG super multi USB 2166D DVD double layer all format drive (have to see whether these work fully, doubt it). The CPU operates well overclocked at up to 2.4GHz with the memory at 333MHz and 3338 timings. I didn't bother with the timings. It's a monster with more than 10GFlops and fast everything. So... I wanted RAID 0 to speed up the disk IO. I read earlier problems with the board and decided to go a different route:

Installed windoze XP 64 bit. Works ok, even played Doom 3 on it at full resolution and detail levels. Ultra fast response. I had to obviously update all the stuff including drivers and .net 2.0 is NOT going on this.

Installed FC4:
1) Researched and found the board only includes softraid stuff, so I said screw it. LVM striping here I come. Partition scheme is sda1- win XP 64 sdb1 - fat 32 /mnt/osshare sda2 is where grub is installed (/boot), Then I have the two physical LVM volumes of equal size set for striping, on the rest of the drives (about 200G). The only partitions I separated from the mamoth / partition were /home and /usr with 25G each.
2) Install went perfect, only thing I did was not activate SElinux because I couldn't be bothered with the extra security stuff. It's good that it exists, but it's not for me. Plus, it's too new to install on a development machine and more software means more problems.
3) I didnt' install kde. Nothing from kde. I hate gnome too, but twm is just too primitive. Blackbox or something similar will be going in unless I can get rid of all the gnome clutter and remap the mouse and keyboard to something more linux-like. Stupid registry, I can't belive they copied the worst winblows feature.
4) The system installed fine, but on first boot, it found a problem with the LAN drivers. " Memory corruption when..." whatever. Asus & NVidia boards said there was no fix yet for high PCI addresses corrupting memory due to a kernel feature/bug. I didn't believe them. So I turned off the LAN stuff in the BIOS and rebooted.
5)I downloaded the new FC4 kernel (2.6.15-1.1831_FC4-smp-x86_64) and all of its packages and installed them on the machine (/mnt/osshare comes in handy sometimes).
6) I also installed the latest NVidia MOBO and graphics card drivers. They had to build kernel modules, but no problem there.
7) Redid the whole grub dual boot thing (below).
8) Rebooted and activated the NVidia LAN port. Worked like a charm. I removed the X configuration files in /etc/X11/ and ran nvidia-xconfig (also downloaded from nvidia).
9) Rebooted, did a ctrl-alt - to get 1280x1024 and voila a supercomputer with linux on it and resolution matching my display. Beautiful!
10) I'm now running redhat up2date to get all the packages up to date.
11) Now for the hard part, getting our development & design environments working & installing more games like Quake 4. Oh, and getting the CDRW and LG super Multi DVD burner burning...

Oh and the dual boot stuff since I always forget it, sda2 is where grub-install puts the boot sector:

linux rescue (rescue disc)
chroot /mnt/sysimage
change grub.conf
grub-install
dd if=/dev/sda2 of=/tmp/bootsect.lnx bs=512 count=1
cp /tmp/bootsect.lnx /mnt/osshare/
reboot
Copy d:\bootsect.lnx c:\
change the boot.ini to include c:\bootsect.lnx as an option with a proper name and syntax
reboot
linux single
recompile nvidia drivers

Joaquin

[priyadarshanh]

I was able to install FC5 on my AMD Athlon 64 3500. I had to pass on the following kernel parameter "acpi=off".
Question: Will this reduce the functnality of my system?

My system used to hang up while booting when trying to start cpuspeed. I went into rescue mode and disabled the cpuspeed daemon. Now I am able to work with my system.
Question: Does any one have solution for making cpuspeed work?

I have trouble installing/upgrading software with the inbuilt pirut. I keep on getting the following error

failure: <some software .rpm> from <something>: [Errno 256] No more mirrors to try.


MY system configuration is as follows.
AMD Athlon 3500
ASUS A8N-VM-UAYGZ (Display adapter inbuilt PCI express)
SATA Hard Disk

Thanks in Advance for any help.

[kerneL26]

Hello!

Can somebody help me?
I have a problem installing FC5. When I try to instal FC5 : An error has occurred - No valid devices were found on which to create new file systems. Please check your hardware for the cause of this problem.

I have a Athlon64+ system with S-ATA HDD and no problem with instaling FC4. I think that FC5 does not recognise my S-ATA controler. I tried to install both release FC-5-x86_64-DVD and FC-5-i386 and I have the same problem. I dont now what to do can anyone help me?

[Seve]

Hello!

Can somebody help me?
I have a problem installing FC5. When I try to instal FC5 : An error has occurred - No valid devices were found on which to create new file systems. Please check your hardware for the cause of this problem.

I have a Athlon64+ system with S-ATA HDD and no problem with instaling FC4. I think that FC5 does not recognise my S-ATA controler. I tried to install both release FC-5-x86_64-DVD and FC-5-i386 and I have the same problem. I dont now what to do can anyone help me?
Hello:
What is the motherboard ?
What is the Sata controller?
And, are there any BIOS options related to the Sata Controller?

Seve

[kerneL26]

Hello:
What is the motherboard ?
What is the Sata controller?
And, are there any BIOS options related to the Sata Controller?

Seve

Hello! 10s for helping me.

My motherboard is ASUS K8N4-E

Silicon Image 3114 RAID Controller:
- 4 x Serial ATA
- Support RAID 0, RAID 1, RAID 10, RAID 5
(in BIOS I think is put it on default settings)

I have just one SATA1 HDD drive with NTFS and FAT and ext3 partition, and I already have insall on it Windows and FC4. :) I alredy test diferend wais to install FC5 as: ide=nodma; acpi=off; apm=off; nofb; resqued but with no favourable result. Is there any options to install FC5 or update my FC4 to FC5? :mad:

Have you any idea?

See you soon.

[Seve]

Hello! 10s for helping me.

My motherboard is ASUS K8N4-E

Silicon Image 3114 RAID Controller:
- 4 x Serial ATA
- Support RAID 0, RAID 1, RAID 10, RAID 5
(in BIOS I think is put it on default settings)

I have just one SATA1 HDD drive with NTFS and FAT and ext3 partition, and I already have insall on it Windows and FC4. :) I alredy test diferend wais to install FC5 as: ide=nodma; acpi=off; apm=off; nofb; resqued but with no favourable result. Is there any options to install FC5 or update my FC4 to FC5? :mad:

Have you any idea?
Is there a newer BIOS for your mother board?
Seve
See you soon.
Hello:
Is there a newer BIOS available for your mother board?
Seve

[kerneL26]

Tanke you for the advise.

I did update my BIOS and I made it . I exploring right now the new FC5 :).
I don't understand why my latest verion of BIOS not worked but it is all fine now. ;)

[Seve]

Tanke you for the advise.

I did update my BIOS and I made it . I exploring right now the new FC5 :).
I don't understand why my latest verion of BIOS not worked but it is all fine now. ;)
Great !!! :) You will like FC5

Seve

[sej7278]

i've had no problems installing centos4, fc4 and fc5 onto an abit ic7-max3's onboard sil-3114 controller with two wd2000js sata drives.

i've also got fc5 installed fine onto two wd2500ks sata-ii drives using a pci sil-3114a card.

just skip all of the bios raid crap and you should have no problems.

[Bandit]

FC5 installs on my system. Biostar K8M800-M7A SATA150 w/ WD Raptor HDD. I have ordered a second 74GB Raptor to run RAID0 to double my space and boost performance. I will let everyone know how it turns out this Wednesday when my goodies arive from newegg and tigerdirect.
BTW, my current system specs below...

Cheers,
Bandit

EDIT, I forgot some info...
I am running the 32bit version of FC5 at the momment. I will be using the 64bit version when I reinstall my system on the new RAID array..

[Eric Buist]

SATA support is not board-specific but chipset-specific. So when selecting a motherboard for a new computer, look at the specifications for the cipset it uses, especially the southbridge which contains the SATA controllers.
If you want to be nearly 100% sure that a SATA install will work on any present and future Linux distribution, choose a motherboard with AHCI support. Since AHCI is an open specification, the implementation has more chances to be bug-free and evolve faster to support NCQ.
Unfortunately, I did not find any AMD-compliant board, but all recent Intel boards support AHCI. I have installed FC4 and FC5 on my Asus P5LD2 without any SATA problem.
For AMD boards, there is no AHCI for the moment. The VIA VT8251 southbridge supports AHCI, but there are almost no AMD boards using it. The only board I found was an entry-level one with only 2 banks of DDR memory.
The sata_via driver seems to be more stable than sata_nv. To get sata_via used, you will need a VIA-based board with the VT8237 southbridge. However, there seems to have problems with the VT8237R southbridge.
I found a NVIDIA-based board with SATA working with FC4 recently. This is a nForce4 chipset because it supports PCI Express, but since it is a server, I cannot reboot it and check for the motherboard brand and model. nForce3 boards also seem to work with SATA; I have found several success reports about these boards.

[Eric Buist]

For non-AHCI board with non-working SATA, a solution might be to add a PCI(E) SATA controller card. This is rather expansive, this replicates ports already on the mb that should work fine, but at least, this saves you from putting a PATA hard drive in the machine, or falling back to MS Windows.

[Bandit]

@EricB.
My BIOSTAR K8M800-M7A uses the VIA 8237R southbridge. Everything works perfectly as its supposed to.
SATA RAID works perfectly also. Running RAID 0 (Stripping / Performance) right now with two WD Raptor hard drives.
From what I have read there seems to be more issues with the nvidia chipset boards, but those issues are limited to no good RAID support on those chipsets.

[b_martinez]

How do I add 2 Maxtor SATA hdd's to an existing raid array?
PROCESSOR:AMD 64 bit 3200+
MOBO:K8N NEO PLATINUM
IDE:2 x 160 GB Western Digital 160 GB hard drives
SATA:2 x Maxtor 200 GB hard drives
hda1 set-up as follows (from fdisk)

Disk /dev/hda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hda1 * 1 13 104391 83 Linux
/dev/hda2 14 3200 25599577+ fd Linux raid autodetect
/dev/hda3 3201 5750 20482875 fd Linux raid autodetect
/dev/hda4 5751 19457 110101477+ 5 Extended
/dev/hda5 5751 6387 5116671 fd Linux raid autodetect
/dev/hda6 6388 6518 1052226 fd Linux raid autodetect
/dev/hda7 6519 19457 103932486 fd Linux raid autodetect

hdb mirrors this, except that hdb1 is NOT set up as raid.
All raid partitions are set up as raid zero (0).
I want to set up the Maxtor drives exactly the same way, yet I want to mirror the existing drives. :)
To wit:
hda & hdb = raid 0 [striping]
sata1 &stas2 = raid zero (0)[striping]
hd* raid & sata raid = raid1 [mirroring][for redundancy] {did i spell that right?}
I do not want to re-install FC5. I want the short-cut,easy-to-do, trust-the-commandline way to do this, cuz i b lazy.
Thank You in advance, because I know you have the answer to my problem.
Bill
p.s. a bit of ego stroking never hurt. LOL

[jtilghman]

Just installed FC5 on a MSI K8M Neo-V with out any hicthes.

Sound, Network, X all work with NO PROBLEMS.

And I am using it as a MythTV system.

Its Sweet, :) I would buy one again if they were going to keep making them. Socket 754 AMD.

Thanks.

[Bloodflame]

i've been running Fedora Core 5 smoothly for a couple weeks now. Installed quickly and flawlessly. This is the first distro I've got successfully running on this hardware, but probably because the other ones I tried were a few months older than my system. heh, anyway my system specs are as follows:

DFI LanParty UT nF4 Ultra-D
AMD64 Athlon X2 4400+
1GB OCZ Gold VX PC4000
200GB Western Digital SATA-II
ATI Radeon X1800XL
17" widescreen LCD

I'm also dual-booting with Windows XP, but mostly just so I could play games. :P for the record, grub was easy to set up with FC5 and it works beautifully.

[FC5AMD64User]

Gosh, I thought this problem was solved with the latest Linux kernel in Fedora Core 5!

Firstly some system configs:

Hardware:
TYAN S2891 (K8SRE) mobo
2x Opteron 250 2.4 Ghz
2x 1G RAM (1G per CPU) - Total 2G
1x NVidia NProfessional 2200 MCP (Sata Controller)
4x SATA2 Western Digital WD800JD 80Gb -Total 300Gb
BIOS 2.01.2891 (Release Date: 09/28/05)

O/S install media:
Fedora Core 5 x86_64 DVD

Problem:
This is new Linux installation on 'straight-out-of-a-box' hardware. Bootup is fine. All system components recognised, especially the 4 SATA drives. I've tried various combinations of the follwoting options to get the Linux installation going, but all ended up with the same problem - the system hangs (black screen with cursor cross) after Anaconda starts installation:

BIOS settings:
BIOS Main: O/S Installed [Linux]/[Other]
NV Raid Configuration: [Disabled]
MTRR Mapping: [Discreet] - Onscreen help says that Linux O/S may need this setting - not sure what this does.
Enable ACPI: [No]
Interrupt Mode: [APIC]/[PIC]

I've also passed the following commands at boot time:
Boot: linux acpi=off nnoapic nolapic noprobe

The problem looks like an old one with the sata_nv driver causing a kernel panic. When I do not install the driver (using noprobe) Anaconda travels a little further but falls over when no hardrives are detected (as you would expect). This leads me to believe that the problem lies with the sata_nv driver and the kernel. I've researched this and I was under the impression that the kernel fix would have been included in Fedora Core 5.

I have seen some threads with successful workarounds but all with single Opteron - maybe the issue is with the SMP kernel version.

Any suggestions / help to get around this. Perhaps another Linux distro that works with the above setup?

Cheers.

[fmj]

Hi,

I've just installed FC5 during a system upgrade after a while on SuSE, and I had a couple of problems, but that could just be me ;)

On the first attempt, something crashed during setup, but then the second attempt went fine. I've now got a hardware RAID (striped over two Seagate Barracuda 200GB) on channels 1+2 of the nForce4 SLI Southbridge controller of an Asus A8N32-SLI Deluxe with an AMD64 4000+ San Diego and 2048 MB of Geil RAM.

I can't however, get my third drive up on channel 3 (SATA was on in the BIOS, but not RAID-enabled). Also, after updating itself to the latest version (2.6.17-1.2139_FC5), the kernel was unable to mount/find the logical volumes, resulting in a system crash. Reverting back to 2.6.16-1.2054_FC5 has resolved this. Any ideas?

Thanks

[FC5AMD64User]

Gosh, I thought this problem was solved with the latest Linux kernel in Fedora Core 5!

Firstly some system configs:

Hardware:
TYAN S2891 (K8SRE) mobo
2x Opteron 250 2.4 Ghz
2x 1G RAM (1G per CPU) - Total 2G
1x NVidia NProfessional 2200 MCP (Sata Controller)
4x SATA2 Western Digital WD800JD 80Gb -Total 300Gb
BIOS 2.01.2891 (Release Date: 09/28/05)

O/S install media:
Fedora Core 5 x86_64 DVD

Problem:
This is new Linux installation on 'straight-out-of-a-box' hardware. Bootup is fine. All system components recognised, especially the 4 SATA drives. I've tried various combinations of the follwoting options to get the Linux installation going, but all ended up with the same problem - the system hangs (black screen with cursor cross) after Anaconda starts installation:

BIOS settings:
BIOS Main: O/S Installed [Linux]/[Other]
NV Raid Configuration: [Disabled]
MTRR Mapping: [Discreet] - Onscreen help says that Linux O/S may need this setting - not sure what this does.
Enable ACPI: [No]
Interrupt Mode: [APIC]/[PIC]

I've also passed the following commands at boot time:
Boot: linux acpi=off nnoapic nolapic noprobe

The problem looks like an old one with the sata_nv driver causing a kernel panic. When I do not install the driver (using noprobe) Anaconda travels a little further but falls over when no hardrives are detected (as you would expect). This leads me to believe that the problem lies with the sata_nv driver and the kernel. I've researched this and I was under the impression that the kernel fix would have been included in Fedora Core 5.

I have seen some threads with successful workarounds but all with single Opteron - maybe the issue is with the SMP kernel version.

Any suggestions / help to get around this. Perhaps another Linux distro that works with the above setup?

Cheers.
Just thought I'ld close the loop for those that may have had the same experience. I finally got Linux to install without any problems using SuSe 10.0. I used Tyan Support's advice and used a commercial distribution that they support. After 3 weeks of solid searching and trying, it's a pity that I'm no closer to understanding what or why I had problems with FC 5.

Cheers.

[boknoy]

Did a fresh install of FC5 x86 using only the nvidia sata controller (silicon sata controller is disabled in bios and was never tested) using 4 harddisk in raid 0 config.
Everthing is working perfectly.

[wshawn]

MSI K8N SLI works fine. Only thing: I left a 40 GB IDE drive connected to use as a backup drive. The installer insisted on putting the boot loader on that drive. Going into the advance boot loader settings during install allowed me to select the proper boot order of the drives according to what I have in BIOS.

Ended up removing that install due to bad memory corrupting the file system.

Next time I installed I went into bios and disabled that controller on the motherboard, installed linux, set the boot order properly for the SATA II Seagates, and installed Linux on an 80 GB and 320GB SATAII combination set using my own partition scheme.

df -H shows:


[root@aragorn sysinfo]# df -H
Filesystem Size Used Avail Use% Mounted on
/dev/sda2 33G 655M 31G 3% /
/dev/hda1 41G 15G 24G 38% /backup
/dev/sda1 104M 16M 83M 17% /boot
/dev/mapper/VolGroup00-LogVol02 48G 5.1G 41G 12% /bootos
tmpfs 261M 0 261M 0% /dev/shm
/dev/mapper/VolGroup00-LogVol01 254G 520M 241G 1% /home
/dev/sda6 15G 175M 14G 2% /tmp
/dev/sda5 16G 3.4G 12G 24% /usr
/dev/sda3 16G 279M 15G 2% /var


The /bootos are my virtual machines for VMware Server

[jtang613]

FC5 on Asus M2NPV-VM with Nvidia NForce 430 SATA2 install confirmed:
00:0e.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev a1)

[billwww]

Asus A8V Deluxe
Western Digital Caviar 160GB in RAID 1 mode

FC5 install detected Promise RAID controller and loaded correct driver.
Problems with updates

[bazzoon]

Tyan s2865AG2NRF
Both sata (primary + sata I ) connections were detected (non-raid) were detected flowlessly.

[bruacucunalsucr]

Configuration:
Motherboard: ASUS A8M2N-LA (Bougth in a HP a1517.it)
SATA drives:
- WDC WD2000JS-60N Rev.10.0
- WDC WD2000JS-00M Rev.02.0
Software RAID

Everything went smooth installing Fedora Core 5 x86 64
:) :) :)

[jmorhus]

System specs in sig. FC5 and FC6 installed perfectly. Actually dual booting them right now.

[pescobar]

I have a Toshiba Core 2 Duo laptop and it has a SATA hard drive in it. I've never had a laptop with a SATA drive in it before.

I have it dual-booting FC 6 x86_64 and Windows XP and when I shut down with XP, I don't have any problems. But when I shut down with FC, there is a wierd "plonk" sound.

It is very similar to the sound when I force a shutdown by holding down the power button.

Anybody encounter something like this before?

[Eric Buist]

I have a similar behavior with my Dell Inspiron 6400, which has a SATA hard drive too.

[pescobar]

I have a similar behavior with my Dell Inspiron 6400, which has a SATA hard drive too.

Eric, I am very concerned about the sound that the drive makes on shutdown and so please do post here if you ever find a fix for it!

For now, I am not shutting down in FC6 and instead re-booting the machine, going into Windows and then shutting down from Windows. What a pain in the ass!

[binmasteh]

Hello All,

fc6 x86_64 OS
INTEL BOXDG965WHMKR
INTEL CORE 2 DUO E6400 2.13 GHZ EM64T 1066MHZ
1GB PC24200 533MHZ NON-ECC 240-PIN DDR2 DIMM x4
WD 80GB 800JD SATA 7200RPM 8MB x6
NEC AD7170A 18X BLACK DVD MULTI WRITER 18X DVD+R 8X DVD+RW 8X DVD+R DL 12X DVD-RAM
MITSUMI 1.44MB FLOPPY DRIVE
NORCO DS-600S 4U 3x5.25" 1x3.5" W/ 6 HOT-SWAPPABLE SLIM DRIVE BAY & 80mm CASE FAN x 4
EPOWER ZU-550W

*of note motherboard hardrive configuration needs to be set to ahci & all-generic-ide needs to be added to command line at boot time & later added to the kernel line in grub.conf.

will post particulars in a new thread, but this should start those struggling with the i965 chipset in the right direction. Intall is successfull but is a struggle.

[KennyKung]

Asus A8V + AMD 3000+
Promise RAID mode 1+0
WD 120GB+250GB
Fedora core 6 64bit
nvidia fx-5700

(it work fine with VIA Raid, but VIA Raid can't support my 250GB HD so i change to use Promise RAID)
i can't install it, it hangs after detected Promise RAID controller >.< (a totally blue screen with a movable mouse pointer)
what should i do?

[binmasteh]

why are you using a 120GB and a 250GB sized disks with a raid controller? I would not recomend using 2 different sized disks in any raid array. Are the disks sata or ide? what is your install media?

Is there a menu available for the controller during post? are the discs made initalized and made ready?

[KennyKung]

why are you using a 120GB and a 250GB sized disks with a raid controller? I would not recomend using 2 different sized disks in any raid array. Are the disks sata or ide? what is your install media?

Is there a menu available for the controller during post? are the discs made initalized and made ready?


Actually, this is my matherboard problem, i do not need and never think of using any raid. But if i use sata HD, i must choose a raid controller, Promise or VIA >.<

here is the detail of my MB:
http://www.asus.com/products.aspx?l1=3&l2=14&l3=67&model=236&modelmenu=2

[binmasteh]

KennyKung,

I'm not very familiar with your motherboard. But, I've glanced over quite of few forum posts where folks complain about promise controllers. I'm not an expert (thats why we visit these forums :-), but the best general idea I have is to pass the option "noprobe" at install time and manually install the latest promise drive from the manufacturer and not from the install media. Further if there is an option in the bios to set hdd types i'd choose ahci and not raid.
Hope it helps :-)

[tomman]

Installed FC6 (64-bit) on a Dell Inspiron 6400. Everything works fine, except that i CAN'T enable DMA for the DVD burner (a