Am Fr, den 30.01.2004 schrieb Mike
Westkamper um 01:23:
[ snip ]
> Greetings:
>
> After a few days away I am back trying to solve this problem.
>
> I modified the modules.conf to:
> ===============
> alias eth0 3c509
> alias scsi_host_adapter aic7xxx
> options aic7xxx 'aic7xxx=probe_eisa_vl.tag_info:{{}.{.10}}.seltime:1'
Do you really need this options line? I am not sure about which SCSI
adapter you use. If it is a normal PCI adapter, even embedded and not a
single slot card, these options certainly cause errors. It was just an
example from modinfo I posted you before. It is often helpful to ask
google for information by other users if you have problems with special
hardware. It is good to know the whole and exact product name to search
for.
> ===============
>
> Next I did a mkinitrd and logged the results:
> ===============
> Looking for deps of module scsi_mod
> Looking for deps of module sd_mod scsi_mod
> Looking for deps of module scsi_mod
> Looking for deps of module unknown
> Looking for deps of module aic7xxx scsi_mod
> Looking for deps of module scsi_mod
> Looking for deps of module ide-disk
> Looking for deps of module ext2
> Using modules: ./kernel/drivers/scsi/scsi_mod.o
> ./kernel/drivers/scsi/sd_mod.o ./kernel/drivers/scsi/aic7xxx/aic7xxx.o
> Using loopback device /dev/loop0
> /sbin/nash -> /tmp/initrd.iF2107/bin/nash
> /sbin/insmod.static -> /tmp/initrd.iF2107/bin/insmod
> `/lib/modules/2.4.22-1.2149.nptlcustom/./kernel/drivers/scsi/scsi_mod.o' ->
> `/tmp/initrd.iF2107/lib/scsi_mod.o'
> `/lib/modules/2.4.22-1.2149.nptlcustom/./kernel/drivers/scsi/sd_mod.o' ->
> `/tmp/initrd.iF2107/lib/sd_mod.o'
> `/lib/modules/2.4.22-1.2149.nptlcustom/./kernel/drivers/scsi/aic7xxx/aic7xxx
> .o' -> `/tmp/initrd.iF2107/lib/aic7xxx.o'
> Loading module scsi_mod
> Loading module sd_mod
> Loading module aic7xxx with options
> 'aic7xxx=probe_eisa_vl.tag_info:{{}.{.10}}.seltime:1'
> ===============
ramdisk did build properly
> Upon rebooting the machine, carefully choosing the correct kernel, the boot
> process proceeds normally until it produced the following error on the
> console:
> ===============
> /lib/aic7xxx.0
> insmod errors can be caused by incorrect IO or IRQ .....
> /bin/insmod exited abnormally
> ===============
Ok, the problem is a ressources conflict. Maybe the options line I
commented above is causing trouble.
> The error text may not be exactly correct as it was scrolling when I tried
> to catch it. I could not find the message in the boot sequence logged in
> /var/log/messages or dmesg or in boot.log A fdisk -l did not show the SCSI
> drives.
>
> Next, if I do an insmod aic7xxx the module loads and the drives appear.
After loading the module properly, can you do a "cat /proc/interrupts",
"cat /proc/pci" (if it's a PCI adapter) and "cat /proc/ioports" to see
which hardware resources the SCSI adapter uses?
> Help is really appreciated.
Alexander
--
Alexander Dalloz | Enger, Germany | GPG key 1024D/ED695653 1999-07-13
Fedora GNU/Linux Core 1 (Yarrow) on Athlon CPU kernel 2.4.22-1.2149.nptl
Sirendipity 11:58:58 up 20:46, 7 users, 0.19, 0.14, 0.09
[ ÎÎÏÎÎ Ï'ÎÏÏÎÎ - gnothi seauton ]
