Re: Bug#283595: pure64 2GB HD install

2004-11-30 Thread Christian Perrier

 I had problems installing kernel 2.6 on Seagate ST380013AS SATA drive.
 I put old 2GB Seagate ATA HD in the box, retaining SATA drive but 
 setting BIOS to boot off old ATA drive.


Have you tried modprobe sata_sil in console 2 when you're notified
the no hard disk foundĀ ?

I'm not a specialist of these hardware stuff but this seems to be the
driver to use with your SATA controller, according to discover1-data.

You can do this undestructively so you can test again even on the
installed machine.





Re: Bug#283595: pure64 2GB HD install

2004-11-30 Thread Goswin von Brederlow
Christian Perrier [EMAIL PROTECTED] writes:

 I had problems installing kernel 2.6 on Seagate ST380013AS SATA drive.
 I put old 2GB Seagate ATA HD in the box, retaining SATA drive but 
 setting BIOS to boot off old ATA drive.


 Have you tried modprobe sata_sil in console 2 when you're notified
 the no hard disk foundĀ ?

 I'm not a specialist of these hardware stuff but this seems to be the
 driver to use with your SATA controller, according to discover1-data.

 You can do this undestructively so you can test again even on the
 installed machine.

At first I would thing that the discover1-data udeb on the install CD
is outdated but you (Norval) wrote the disk still doesn't show up
after several dist-upgrades.

You don't need to boot the install CD to test the sata_sil module, in
fact it is probably better to try it with the newer kernel you are now
running.

If manual loading of the module shows the disk (you need the scsi disk
module too) then check if you have the newest discover + data
installed and check why it doesn't load the module. Once discover is
fixed then trying a new install is worth it.


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.

MfG
Goswin