Re: SATA Silicon Image 3114 support for A64 images ?
Hi Tudiatya,
The MSI K8N Neo2, if that's the board you have, should be
using the nforce3 chipset, which has an nforce3 sata raid
and a silicon image 3512 sata raid.
If that's correct, I'd try this:
1. Undo the overclocking to get the installation done
2. If the sata raid still isn't automatically detected, is it
possible to go into the shell and issue 'modprobe sata_sil'?
That is the module you need for the sii3512
3. I don't recall now, but it's possible that the sata_nv has
problems in 2.6.8. If that's the case, I would install Debian on
a sata_sil drive, and then upgrade the kernel
4. To use the nforce3 NIC, you'll need a more recent kernel in
any case -- I recommend vanilla 2.6.12-rc2 from kernel.org,
but kernel-source-2.6.11 is available from Debian and may
work fine. The NIC needs the forcedeth driver. Note that it
doesn't show up in lspci, but it works fine.
5. If you have a second Marvell Yukos NIC, it may still need
some firmware not included in Debian (not free); a working
driver is available in the vanilla kernel (sk98lin)
Running a live CD and getting a lspci, lsmod, and dmesg output is
always worth doing, even before asking for help!
Dave
Tudiatya wrote:
>Okay, I went from the installer to "Execute a shell", but in the shell,
>lspci was not recognized as a command, so this won't take me further. :( (I
>don't have Linux, WinXP only ! Would it help you if I let a Suse Live CD run
>and lspci from there?)
>
>What interesting is, that there's a module called "siimage" in the
>installer's list, but I think that's for another type of silicon image
>controller.
>
>Would it perhaps help, if the installer would include sata_sil in it's list
>of selectable modules ?
>
>One another thing: people talk about that in lots of SATA topics that we
>have to set the "compatibility mode" in the BIOS so the installer sees the
>HDD - then recompile kernel etc with sata_nv and finally BIOS back to
>normal. I don't understand this, why to install a linux that hard way, on
>the other hand this procedure was for the sata_nv but probably would also
>work for sata_sil.. but anyway, why ??? This stupid WinXP installs onto both
>controllers without any word ..
>
>I don't have spare PATA HDD to cheat the whole thing out and MSI boards
>doesn't have "compatibility mode" regarding SATA controllers either - so it
>means, my BIOS reports on the "Energy Star" pre-boot screen the following:
>
>Primary Master - None
>Primary Slave - CDROM (actually name differs)
>Secondary Master - None
>Secondary Slave - None
>Third Master - None
>Fourth Master - None
>Fifth Master - My SATA Seagate Barracuda 7200.7 (160G)
>Sixth Master - None
>
>That's it. Third & Fourth are sata_nv and of course unused because of the
>NOT-fixed 33MHz clock, Fifth & Sixth are sata_sil whici I use right now. If
>I disable Third & Fourth in the BIOS, Fifth and Sixth won't appear as Third
>and Fourth, for PATA IDE Secondary Master controller "Disable" it's the
>same.
>
>On my Abit IC7 Intel chipset I had that Compatibility mode where if a
>controller was disabled, higher numbered channels took it's number, but now
>that's not the way to handle it. But anyway, if linux does have sata_sil
>already, we just need to put it into the menu of the debian installer as a
>loadable module, or am I wrong ? :(
>
>Sry for being so long ...
>
>----- Original Message -----
>From: "Cameron Patrick" <cameron@patrick.wattle.id.au>
>To: <debian-amd64@lists.debian.org>
>Sent: Sunday, June 05, 2005 12:53 PM
>Subject: Re: SATA Silicon Image 3114 support for A64 images ?
>
>
>
>
Reply to: