2003-09-13 07:25:18

by Reg Clemens

[permalink] [raw]
Subject: 2.6.0-test5: "No module aic7xxx found for kernel 2.6.0-test5, aborting."

When trying to build SCSI support into 2.6.0-test5,
I configure SCSI, but
whether I configure NO driver at all
or configure the aic7xxx driver
when I get to the
make install
I constantly get the error message
No module aic7xxx found for kernel 2.6.0-test5, aborting.

Surely SOMEONE has built this kernel with SCSI support,
so why is it giving me this trouble.

I can probably build w/o ANY SCSI support at all, but that wouldnt be
useful, so I havent tried...
--
Reg.Clemens
[email protected]



2003-09-15 17:00:28

by Randy.Dunlap

[permalink] [raw]
Subject: Re: 2.6.0-test5: "No module aic7xxx found for kernel 2.6.0-test5, aborting."

On Sat, 13 Sep 2003 01:25:14 -0600 [email protected] wrote:

| When trying to build SCSI support into 2.6.0-test5,
| I configure SCSI, but
| whether I configure NO driver at all
| or configure the aic7xxx driver
| when I get to the
| make install
| I constantly get the error message
| No module aic7xxx found for kernel 2.6.0-test5, aborting.
|
| Surely SOMEONE has built this kernel with SCSI support,
| so why is it giving me this trouble.
|
| I can probably build w/o ANY SCSI support at all, but that wouldnt be
| useful, so I havent tried...

I build and boot with aic7xxx built into vmlinux all the time.
However, I don't use 'make install' so I haven't seen this.
If noone else knows the answer to this problem, perhaps you could
debug install.sh or /sbin/installkernel (if those are being used).

--
~Randy

2003-09-15 17:30:39

by Reg Clemens

[permalink] [raw]
Subject: Re: 2.6.0-test5: "No module aic7xxx found for kernel 2.6.0-test5, aborting."

> On Sat, 13 Sep 2003 01:25:14 -0600 [email protected] wrote:
>
> | When trying to build SCSI support into 2.6.0-test5,
> | I configure SCSI, but
> | whether I configure NO driver at all
> | or configure the aic7xxx driver
> | when I get to the
> | make install
> | I constantly get the error message
> | No module aic7xxx found for kernel 2.6.0-test5, aborting.
> |
> | Surely SOMEONE has built this kernel with SCSI support,
> | so why is it giving me this trouble.
> |
> | I can probably build w/o ANY SCSI support at all, but that wouldnt be
> | useful, so I havent tried...
>
> I build and boot with aic7xxx built into vmlinux all the time.
> However, I don't use 'make install' so I haven't seen this.
> If noone else knows the answer to this problem, perhaps you could
> debug install.sh or /sbin/installkernel (if those are being used).
>

I hadn't even thought of that.
Ive been using 'make install', as a convenience, ever since it first appeared,
and just never thought about going back to doing things by hand/the good old
way. I will take a look at the script tho, and try to see what it is doing
wrong.
--
Reg.Clemens
[email protected]


2003-09-16 17:47:10

by John Cherry

[permalink] [raw]
Subject: Re: 2.6.0-test5: "No module aic7xxx found for kernel 2.6.0-test5, aborting."

Are you compiling with anything other than -j1? There is a race in the
parallel build of aic7xxx. A patch has been submitted, but is not in
-test5.

Try the attached patches and see if this helps you.

John

On Mon, 2003-09-15 at 09:53, Randy.Dunlap wrote:
> On Sat, 13 Sep 2003 01:25:14 -0600 [email protected] wrote:
>
> | When trying to build SCSI support into 2.6.0-test5,
> | I configure SCSI, but
> | whether I configure NO driver at all
> | or configure the aic7xxx driver
> | when I get to the
> | make install
> | I constantly get the error message
> | No module aic7xxx found for kernel 2.6.0-test5, aborting.
> |
> | Surely SOMEONE has built this kernel with SCSI support,
> | so why is it giving me this trouble.
> |
> | I can probably build w/o ANY SCSI support at all, but that wouldnt be
> | useful, so I havent tried...
>
> I build and boot with aic7xxx built into vmlinux all the time.
> However, I don't use 'make install' so I haven't seen this.
> If noone else knows the answer to this problem, perhaps you could
> debug install.sh or /sbin/installkernel (if those are being used).
>
> --
> ~Randy
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/


Attachments:
part1 (0.99 kB)
part2 (762.00 B)
Download all attachments

2003-09-17 05:45:37

by Reg Clemens

[permalink] [raw]
Subject: Re: 2.6.0-test5: "No module aic7xxx found for kernel 2.6.0-test5, aborting."

>
> --=-qKbn9YnrwluGdEN58xpj
> Content-Type: text/plain
> Content-Transfer-Encoding: 7bit
>
> Are you compiling with anything other than -j1? There is a race in the
> parallel build of aic7xxx. A patch has been submitted, but is not in
> -test5.
>
> Try the attached patches and see if this helps you.
>
> John
>
Well, yes, I was using either -j2 or -j4 (on a single processor machine).
[[ Somehow, the 2.6.0 compiles seem REALLY SLOW compared to the 2.4.x and
previous compiles ]].

But the patch didnt seem to solve the problem, I still see:

Root device is (3, 7)
Boot sector 512 bytes.
Setup is 2544 bytes.
System is 1826 kB
Kernel: arch/i386/boot/bzImage is ready
sh arch/i386/boot/install.sh 2.6.0-test5 arch/i386/boot/bzImage System.map ""
No module aic7xxx found for kernel 2.6.0-test5
mkinitrd failed
make[1]: *** [install] Error 1
make: *** [install] Error 2

when I type 'make install'. The 'make bzImage' itself went just fine.
This was after a 'make mrproper'.

As suggest (by someone else) I guess I can just do the install by hand,
but this dependence on aic7xxx is VERY strange.




--
Reg.Clemens
[email protected]


2003-09-18 13:49:34

by Jesper Juhl

[permalink] [raw]
Subject: Re: 2.6.0-test5: "No module aic7xxx found for kernel 2.6.0-test5, aborting."


While not directly related to fixing the problems building the aic7xxx
driver I thought you might find these patches I did recently of
interrest since they also deal with aic7xxx, or rather with its
documentation (I've submitted these to lkml before, but they seemed to get
lost in the sea of email - probably in part because they are very
trivial).

I was hoping that since you are already working on aic7xxx you might
consider merging these while you where at it. If submitting the patches in
this manner is inappropriate I appologize.


diff -u linux-2.6.0-test5-orig/drivers/scsi/aic7xxx/Kconfig.aic79xx linux-2.6.0-test5/drivers/scsi/aic7xxx/Kconfig.aic79xx
--- linux-2.6.0-test5-orig/drivers/scsi/aic7xxx/Kconfig.aic79xx 2003-09-08 21:50:03.000000000 +0200
+++ linux-2.6.0-test5/drivers/scsi/aic7xxx/Kconfig.aic79xx 2003-09-15 23:32:06.000000000 +0200
@@ -66,7 +66,7 @@
with read streaming enabled so it is disabled by default. Read
Streaming can be configured in much the same way as tagged
queueing
using the "rd_strm" command line option. See
- drivers/scsi/aic7xxx/README.aic79xx for details.
+ <file:Documentation/scsi/aic79xx.txt> for details.

config AIC79XX_DEBUG_ENABLE
bool "Compile in Debugging Code"


diff -u linux-2.6.0-test5-orig/drivers/scsi/aic7xxx/Kconfig.aic7xxx
linux-2.6.0-test5/drivers/scsi/aic7xxx/Kconfig.aic7xxx
--- linux-2.6.0-test5-orig/drivers/scsi/aic7xxx/Kconfig.aic7xxx 2003-09-08 21:50:01.000000000 +0200
+++ linux-2.6.0-test5/drivers/scsi/aic7xxx/Kconfig.aic7xxx 2003-09-15 22:00:34.000000000 +0200
@@ -36,7 +36,7 @@
on some devices. The upper bound is 253. 0 disables tagged
queueing.

Per device tag depth can be controlled via the kernel command line
- "tag_info" option. See drivers/scsi/aic7xxx/README.aic7xxx
+ "tag_info" option. See <file:Documentation/scsi/aic7xxx.txt>
for details.

config AIC7XXX_RESET_DELAY_MS


diff -u linux-2.6.0-test5-orig/Documentation/scsi/aic79xx.txt linux-2.6.0-test5/Documentation/scsi/aic79xx.txt
--- linux-2.6.0-test5-orig/Documentation/scsi/aic79xx.txt 2003-09-08 21:50:18.000000000 +0200
+++ linux-2.6.0-test5/Documentation/scsi/aic79xx.txt 2003-09-14 16:12:08.000000000 +0200
@@ -141,7 +141,7 @@
Option: global_tag_depth
Definition: Global tag depth for all targets on all busses.
This option sets the default tag depth which
- may be selectively overridden vi the tag_info
+ may be selectively overridden via the tag_info
option.
Possible Values: 1 - 253
Default Value: 32


diff -u linux-2.6.0-test5-orig/Documentation/scsi/aic7xxx.txt linux-2.6.0-test5/Documentation/scsi/aic7xxx.txt
--- linux-2.6.0-test5-orig/Documentation/scsi/aic7xxx.txt 2003-09-08 21:49:58.000000000 +0200
+++ linux-2.6.0-test5/Documentation/scsi/aic7xxx.txt 2003-09-14 16:11:45.000000000 +0200
@@ -225,7 +225,7 @@
Option: global_tag_depth:[value]
Definition: Global tag depth for all targets on all busses.
This option sets the default tag depth which
- may be selectively overridden vi the tag_info
+ may be selectively overridden via the tag_info
option.
Possible Values: 1 - 253
Default Value: 32



Kind regards,

Jesper Juhl <[email protected]>

2003-09-18 18:07:37

by Sam Ravnborg

[permalink] [raw]
Subject: Re: 2.6.0-test5: "No module aic7xxx found for kernel 2.6.0-test5, aborting."

On Thu, Sep 18, 2003 at 03:44:45PM +0200, Jesper Juhl wrote:
>
> While not directly related to fixing the problems building the aic7xxx
> driver I thought you might find these patches I did recently of
> interrest since they also deal with aic7xxx, or rather with its
> documentation (I've submitted these to lkml before, but they seemed to get
> lost in the sea of email - probably in part because they are very
> trivial).
>
> I was hoping that since you are already working on aic7xxx you might
> consider merging these while you where at it. If submitting the patches in
> this manner is inappropriate I appologize.

You should send aic7xxx stuf direct to the maintainer - Justin.
I have added him on this mail.

Sam

[Kept the patch so Justin can see it]

>
>
> diff -u linux-2.6.0-test5-orig/drivers/scsi/aic7xxx/Kconfig.aic79xx linux-2.6.0-test5/drivers/scsi/aic7xxx/Kconfig.aic79xx
> --- linux-2.6.0-test5-orig/drivers/scsi/aic7xxx/Kconfig.aic79xx 2003-09-08 21:50:03.000000000 +0200
> +++ linux-2.6.0-test5/drivers/scsi/aic7xxx/Kconfig.aic79xx 2003-09-15 23:32:06.000000000 +0200
> @@ -66,7 +66,7 @@
> with read streaming enabled so it is disabled by default. Read
> Streaming can be configured in much the same way as tagged
> queueing
> using the "rd_strm" command line option. See
> - drivers/scsi/aic7xxx/README.aic79xx for details.
> + <file:Documentation/scsi/aic79xx.txt> for details.
>
> config AIC79XX_DEBUG_ENABLE
> bool "Compile in Debugging Code"
>
>
> diff -u linux-2.6.0-test5-orig/drivers/scsi/aic7xxx/Kconfig.aic7xxx
> linux-2.6.0-test5/drivers/scsi/aic7xxx/Kconfig.aic7xxx
> --- linux-2.6.0-test5-orig/drivers/scsi/aic7xxx/Kconfig.aic7xxx 2003-09-08 21:50:01.000000000 +0200
> +++ linux-2.6.0-test5/drivers/scsi/aic7xxx/Kconfig.aic7xxx 2003-09-15 22:00:34.000000000 +0200
> @@ -36,7 +36,7 @@
> on some devices. The upper bound is 253. 0 disables tagged
> queueing.
>
> Per device tag depth can be controlled via the kernel command line
> - "tag_info" option. See drivers/scsi/aic7xxx/README.aic7xxx
> + "tag_info" option. See <file:Documentation/scsi/aic7xxx.txt>
> for details.
>
> config AIC7XXX_RESET_DELAY_MS
>
>
> diff -u linux-2.6.0-test5-orig/Documentation/scsi/aic79xx.txt linux-2.6.0-test5/Documentation/scsi/aic79xx.txt
> --- linux-2.6.0-test5-orig/Documentation/scsi/aic79xx.txt 2003-09-08 21:50:18.000000000 +0200
> +++ linux-2.6.0-test5/Documentation/scsi/aic79xx.txt 2003-09-14 16:12:08.000000000 +0200
> @@ -141,7 +141,7 @@
> Option: global_tag_depth
> Definition: Global tag depth for all targets on all busses.
> This option sets the default tag depth which
> - may be selectively overridden vi the tag_info
> + may be selectively overridden via the tag_info
> option.
> Possible Values: 1 - 253
> Default Value: 32
>
>
> diff -u linux-2.6.0-test5-orig/Documentation/scsi/aic7xxx.txt linux-2.6.0-test5/Documentation/scsi/aic7xxx.txt
> --- linux-2.6.0-test5-orig/Documentation/scsi/aic7xxx.txt 2003-09-08 21:49:58.000000000 +0200
> +++ linux-2.6.0-test5/Documentation/scsi/aic7xxx.txt 2003-09-14 16:11:45.000000000 +0200
> @@ -225,7 +225,7 @@
> Option: global_tag_depth:[value]
> Definition: Global tag depth for all targets on all busses.
> This option sets the default tag depth which
> - may be selectively overridden vi the tag_info
> + may be selectively overridden via the tag_info
> option.
> Possible Values: 1 - 253
> Default Value: 32
>
>
>
> Kind regards,
>
> Jesper Juhl <[email protected]>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/