Bug#283595: SOLVED: Dual SATA controllers on GA-K8NS Pro
On Thu, 2004-12-02 at 06:36 +0100, Christian Perrier wrote:
> Hmmm, you should have kept the original bug number of your install
> report in copy. Doing so, and keeping your whole answer.
Sorry for breaking the thread, I am more used to forums than lists...
>
>
> Quoting Norval Watson (norv@longforest.com):
> > The Gigabyte GA-K8NS Pro motherboard has four points you can plug a SATA
> > drive cable.
> > They are SATA0_SB and SATA1_SB, both controlled by the onboard nVIDIA
> > nForce3 250 chipset. I tried one of these and had no luck with 2.6
> > kernel, sarge i386 or sid-amd64, detecting my Seagate ST380013AS SATA
> > drive.
> > Then there are SATA0_SII and SATA1_SII, both controlled by the built-in
> > Silicon Image Sil3512 chipset. I swapped the cable into SATA0_SII socket
> > and rebooted. Straight away the drive was detected:
> > scsi3 : sata_sil
> > Vendor: ATA Model: ST380013AS Rev: 3.18
> > Type: Direct-Access ANSI SCSI revision: 05
> > SCSI device sda: 156299375 512-byte hdwr sectors (80025 MB)
> > SCSI device sda: drive cache: write back
> > /dev/scsi/host2/bus0/target0/lun0: p1 p2 < p5 p6 p7 p8 p9 >
> > Attached scsi disk sda at scsi2, channel 0, id 0, lun 0
> >
> > I am able to mount the drive.
> >
> > > > Have you tried "modprobe sata_sil" in console 2 when you're notified
> > > > the no hard disk found ?
> > > >
> > Thanks Christian. Sata_sil module was loading, as was sata_nv, I also
> > saw something to do with nv_sata in dmesg..
> >
> > > One more thing. There is no need to reinstall your system again (apart
> > > from testing if it works). You can go into single user mode and copy
> > > (tar | tar or rsync or whatever you prefer) the old system to the new
> > > disk, change the bootloader config and mkinitrd config, run mkinitrd
> > > and (for lilo) reinstall the bootloader by chrooting to the new disk.
> > Thanks Goswin. Does 'single user mode' mean become root? I will have to look for a tutorial coz I am almost out of my depth here.
> > First up I will copy the boot disk (2GB ATA) to the new SATA disk. I am
> > using GRUB.
> > Thanks again,
>
>
> However, we still need to know whether the installer automatically
> detects your SATA drive with your new hardware layout. Can you at
> least try to boot again the installer CD and go up to the disk
> partitioning step?
>
> This is non destructive as the only need is knowing whether the
> installer detects a disk or not.
I just did a fresh install of sid-amd64-netinst.iso on the SATA disk and
it worked well.
I had to disconnect the ATA drive as the install wanted to put the MBR
on that drive even when I set it to write to the SATA drive. That was
the only glitch.
When the base-system was installed I reconnected the ATA drive and used
that as my apt repository. I had already used dpkg-scanpackages (from
dpkg-dev) to make Packages.gz in (old ATA)/var/cache/apt/archives.
My sources list:
pan64:~# more /etc/apt/sources.list
#deb file:///cdrom/ sarge main
deb file:/mnt/hda/var/cache/apt archives/
I ran aptitude dist-upgrade which updated the base system and installed
the new 2.6.9 kernel
Then I ran aptitude install x-window-system gdm gnome-desktop which
installed a working desktop. Then aptitude install mozilla-firefox
evolution gimp totem , and a few other packages I use.
A quick check shows that browser and mail prog work, I can play CDs and
DVDs.
Should I file a new install report on this successful install?
Thanks,
Norv
>
>
>
>
Reply to: