Mailinglist Archive: opensuse (2773 mails)
|< Previous||Next >|
Re: [SLE] SCSI Problems
- From: sworley@xxxxxxxxxxxxxx (scott worley)
- Date: Mon, 20 Dec 1999 13:14:12 -0600
- Message-id: <00035c1ff4e87c25_mailit@xxxxxxxxxxxxxxxxxxxxxxxxxx>
On December 20, 1999 Paul wrote
>My first posting to this group.
>I done a fresh install of 6.3 and recomplied the kernel with scsi
>support using the advansys scsi card. After recompiling the kernel and
>doing a bzlilo, a reboot does not show the scsi devices as being found.
>scsi devices=0. I have recompilied the kernel 3 times and have gotten
>the same results each time. I followed the 6.3 manual in doing this.
>Any ideas out there what is wrong. Is this a bug in the 6.3 distro.
>To unsubscribe send e-mail to suse-linux-e-unsubscribe@xxxxxxxx
>For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
>Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Did you choose to compile the Advansys driver as a module? The default
installation of SuSE 6.3 for SCSI uses the initrd(ramdisk) method. The
specific SCSI card driver is stored in /boot/initrd. If you compiled the
driver as a module you must regenerate /boot/initrd. I use the aic7xxx
driver as a module and did the following:
1. cp /boot/initrd /boot/initrd.old save the original
2. make menuconfig choose SCSI support as non-module, specific driver as
module(advansys, adaptec, etc). Also, SuSE has a global variable at the
beginning of /etc/rc.config which contains the list of modules which should
be in /boot/initrd. This gets filled in during install when you choose the
SCSI module to load.
3. make dep clean bzImage
4. make modules
5. make modules_install
6. edit /etc/lilo.conf like this:
A. add entry for old kernel, vmlinuz.old
B. comment out global entry initrd=/boot/initrd
C. add entry initrd=/boot/initrd under new kernel image statement
D. add entry initrd=/boot/initrd.old under old kernel image statement
7. make bzlilo
8. cp /boot/vmlinuz /boot/vmlinuz.suse this step keeps the mk_initrd script
from complaining and allows it to finish properly. It wouldn't work otherwise
9. mk_initrd this will generate the new initrd for the new kernel
10. /sbin/lilo MUST do this again
Of course this wont apply if you compiled the driver directly into the kernel
instead of as a module.
Hope this helps
To unsubscribe send e-mail to suse-linux-e-unsubscribe@xxxxxxxx
For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
|< Previous||Next >|