Kernel Module - Raid

Kernel Module - Raid

[Paul VanGundy]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

All,

Hello. I don't know if this is the right place to post this issue but it
does deal with RAID so I thought I would try.

I successfully built a new kernel and am able to boot from it.
However, I need to incorporate a specific RAID driver (adpahci.ko) so we
can use the on-board RAID. The reason I am needing this is because we
have it working with one kernel (the one it was compiled on) but we
can't just copy the adpahci.ko and incorporate it into another kernel
because the kernel complains. I have the adpahci.ko and am unable to get
it to compile against any other kernel because I don't have the original
kernel module (adpahci.c I assume is what I need). Is there any way I
can view the adpahci.ko and copy the contents to make a adpahci.c? Is it
possible to get the kernel object to compile with another kernel only
using the adpahci.ko? Am I making sense?  :)  Thanks in advance.

/paul
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHL3rtul+dQkHY548RAtIDAJoDZWME/Hku9QCESFW/yo/YG3WE5wCfeHPb
fzs7FpKbhSr8PUbl2xrCfGA=
=Lcdq
-----END PGP SIGNATURE-----

Re: Kernel Module - Raid

[David Greaves]

Paul VanGundy wrote:
> All,
> 
> Hello. I don't know if this is the right place to post this issue but it
> does deal with RAID so I thought I would try.
It deals primarily with linux *software* raid.
But stick with it - you may end up doing that...

What hardware/distro etc are you using?
Is this an expensive (hundreds of £) card? Or an onboard/motherboard chipset?

Once you answer this then it may be worth suggesting using sw-raid (in which
case we can help out) or pointing you elsewhere...

> I successfully built a new kernel and am able to boot from it.
> However, I need to incorporate a specific RAID driver (adpahci.ko) so we
> can use the on-board RAID.
I think this is the adaptec proprietary code - in which case you may need a very
specific kernel to run it. You may find others on here who can help but you'll
probably need an Adaptec forum/list.

> I have the adpahci.ko and am unable to get
> it to compile against any other kernel because I don't have the original
> kernel module (adpahci.c I assume is what I need). Is there any way I
> can view the adpahci.ko and copy the contents to make a adpahci.c?
No

> Is it
> possible to get the kernel object to compile with another kernel only
> using the adpahci.ko?
No

> Am I making sense?  :)
Yes

That's one of the big reasons proprietary drivers suck on linux.

David

-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Kernel Module - Raid

[Paul VanGundy]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thanks for the prompt replay David. Below are the answers to your questions:

>> Hello. I don't know if this is the right place to post this issue but it
>> does deal with RAID so I thought I would try.
> It deals primarily with linux *software* raid.
> But stick with it - you may end up doing that...
> 
> What hardware/distro etc are you using?
> Is this an expensive (hundreds of £) card? Or an onboard/motherboard chipset?
The distro is Suse 10.1. It is an onboard chipset.
> 
> Once you answer this then it may be worth suggesting using sw-raid (in which
> case we can help out) or pointing you elsewhere...
> 
>> I successfully built a new kernel and am able to boot from it.
>> However, I need to incorporate a specific RAID driver (adpahci.ko) so we
>> can use the on-board RAID.
> I think this is the adaptec proprietary code - in which case you may need a very
> specific kernel to run it. You may find others on here who can help but you'll
> probably need an Adaptec forum/list.
Oi. This is a pain... ;)
> 
>> I have the adpahci.ko and am unable to get
>> it to compile against any other kernel because I don't have the original
>> kernel module (adpahci.c I assume is what I need). Is there any way I
>> can view the adpahci.ko and copy the contents to make a adpahci.c?
> No
That sucks. :)
> 
>> Is it
>> possible to get the kernel object to compile with another kernel only
>> using the adpahci.ko?
> No
> 
>> Am I making sense?  :)
> Yes
Good, because sometimes I don't make sense to myself. :)
> 
> That's one of the big reasons proprietary drivers suck on linux.
> 
Ok. So this chipset has the ability to use an Intel based RAID. Would
that be better?

Thanks again.

/paul
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHL4QOul+dQkHY548RAgF7AJ49tcLXtEp9DgZugK1ozhBNyP0tOgCeNygd
HVtJmjZR8qYm7+7lCwH7gLI=
=EQwg
-----END PGP SIGNATURE-----
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Kernel Module - Raid

[David Greaves]

Paul VanGundy wrote:
> Thanks for the prompt replay David. Below are the answers to your questions:
> 
>> What hardware/distro etc are you using?
>> Is this an expensive (hundreds of £) card? Or an onboard/motherboard chipset?
> The distro is Suse 10.1.
As a bit of trivia, Neil (who wrote and maintains linux RAID) works for Suse.

> It is an onboard chipset.
In which case it's not likely to be hardware RAID.
See: http://linux-ata.org/faq-sata-raid.html

>> Once you answer this then it may be worth suggesting using sw-raid (in which
>> case we can help out) or pointing you elsewhere...
You should probably configure the BIOS to use


>> That's one of the big reasons proprietary drivers suck on linux.
> 
> Ok. So this chipset has the ability to use an Intel based RAID. Would
> that be better?
mmm, see the link above...

In almost any case where you are considering 'onboard' raid, linux software raid
(using md and mdadm) is a better choice.

Start here: http://linux-raid.osdl.org/index.php/Main_Page
(feel free to correct it or ask here for clarification)

Also essential reading is the mdadm man page.

David

-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Kernel Module - Raid

[Paul VanGundy]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

All,

So I was able to get the Adaptec kernel module uncompiled (YES! :)). I
followed the instructions and now when I run 'make menuconfig' I see
that I can make the ADPAHCI a module of the kernel under Device Drivers
- -> SCSI (I belive) -> Low-level -> ADPAHCI. Everything to this point is
nice and happy.....However, when I start to compile the kernel I get the
following error once it gets to drivers/scsi/adphaci:

- ----------------------------------------------------------------
CC [M]  drivers/scsi/adpahci/hr.o
In file included from drivers/scsi/adpahci/hr.c:35:
drivers/scsi/adpahci/hr.h:50:26: error: linux/config.h: No such file or
directory
In file included from drivers/scsi/adpahci/cdacsmi.h:47,
                 from drivers/scsi/adpahci/hr.h:96,
                 from drivers/scsi/adpahci/hr.c:35:
drivers/scsi/adpahci/osmcda.h:228: warning: function declaration isn’t a
prototype
drivers/scsi/adpahci/osmcda.h:232: warning: function declaration isn’t a
prototype
In file included from drivers/scsi/adpahci/sysdef.h:186,
                 from drivers/scsi/adpahci/cdacsmi.h:60,
                 from drivers/scsi/adpahci/hr.h:96,
                 from drivers/scsi/adpahci/hr.c:35:
drivers/scsi/adpahci/cdadef.h:301: warning: useless storage class
specifier in empty declaration
drivers/scsi/adpahci/cdadef.h:314: warning: useless storage class
specifier in empty declaration
drivers/scsi/adpahci/cdadef.h:325: warning: useless storage class
specifier in empty declaration
drivers/scsi/adpahci/cdadef.h:338: warning: useless storage class
specifier in empty declaration
In file included from drivers/scsi/adpahci/cdacsmi.h:60,
                 from drivers/scsi/adpahci/hr.h:96,
                 from drivers/scsi/adpahci/hr.c:35:
drivers/scsi/adpahci/sysdef.h:469:1: warning: "/*" within comment
drivers/scsi/adpahci/sysdef.h:489:1: warning: "/*" within comment
In file included from drivers/scsi/adpahci/chim.h:45,
                 from drivers/scsi/adpahci/sysdef.h:523,
                 from drivers/scsi/adpahci/cdacsmi.h:60,
                 from drivers/scsi/adpahci/hr.h:96,
                 from drivers/scsi/adpahci/hr.c:35:
drivers/scsi/adpahci/chimosm.h:99:5: warning: "SAS_DOWNSHIFT_SUPPORT" is
not defined
drivers/scsi/adpahci/chimosm.h:142:7: warning:
"SAS_PROGRAMABLE_ALIGN_RATE" is not defined
In file included from drivers/scsi/adpahci/chim.h:49,
                 from drivers/scsi/adpahci/sysdef.h:523,
                 from drivers/scsi/adpahci/cdacsmi.h:60,
                 from drivers/scsi/adpahci/hr.h:96,
                 from drivers/scsi/adpahci/hr.c:35:
drivers/scsi/adpahci/chimdef.h:2602:5: warning:
"SATA_MESSAGE_SIGNALED_INTERRUPTS_SUPPORT" is not defined
drivers/scsi/adpahci/chimdef.h:2629:5: warning: "SAS_SAVE_RESTORE_STATE"
is not defined
drivers/scsi/adpahci/chimdef.h:2754:5: warning: "SAS_OSM_DEBUG_MODE" is
not defined
In file included from drivers/scsi/adpahci/raidtype.h:56,
                 from drivers/scsi/adpahci/sysdef.h:561,
                 from drivers/scsi/adpahci/cdacsmi.h:60,
                 from drivers/scsi/adpahci/hr.h:96,
                 from drivers/scsi/adpahci/hr.c:35:
drivers/scsi/adpahci/sysdef.h:469:1: warning: "/*" within comment
drivers/scsi/adpahci/sysdef.h:489:1: warning: "/*" within comment
In file included from drivers/scsi/adpahci/sysdef.h:574,
                 from drivers/scsi/adpahci/cdacsmi.h:60,
                 from drivers/scsi/adpahci/hr.h:96,
                 from drivers/scsi/adpahci/hr.c:35:
drivers/scsi/adpahci/sysdev.h:232:5: warning: "PROFILER" is not defined
In file included from drivers/scsi/adpahci/sysdef.h:577,
                 from drivers/scsi/adpahci/cdacsmi.h:60,
                 from drivers/scsi/adpahci/hr.h:96,
                 from drivers/scsi/adpahci/hr.c:35:
drivers/scsi/adpahci/osifprot.h:509: warning: function declaration isn’t
a prototype
drivers/scsi/adpahci/osifprot.h:512: warning: function declaration isn’t
a prototype
drivers/scsi/adpahci/osifprot.h:531: warning: parameter names (without
types) in function declaration
drivers/scsi/adpahci/osifprot.h:540: warning: function declaration isn’t
a prototype
drivers/scsi/adpahci/osifprot.h:552: warning: function declaration isn’t
a prototype
drivers/scsi/adpahci/osifprot.h:571: warning: function declaration isn’t
a prototype
drivers/scsi/adpahci/osifprot.h:573: warning: function declaration isn’t
a prototype
In file included from drivers/scsi/adpahci/sysdef.h:578,
                 from drivers/scsi/adpahci/cdacsmi.h:60,
                 from drivers/scsi/adpahci/hr.h:96,
                 from drivers/scsi/adpahci/hr.c:35:
drivers/scsi/adpahci/coreprot.h:274: warning: function declaration isn’t
a prototype
drivers/scsi/adpahci/coreprot.h:281: warning: function declaration isn’t
a prototype
drivers/scsi/adpahci/coreprot.h:487: warning: function declaration isn’t
a prototype
drivers/scsi/adpahci/coreprot.h:555: warning: function declaration isn’t
a prototype
drivers/scsi/adpahci/coreprot.h:741: warning: function declaration isn’t
a prototype
In file included from drivers/scsi/adpahci/cdacsmi.h:60,
                 from drivers/scsi/adpahci/hr.h:96,
                 from drivers/scsi/adpahci/hr.c:35:
drivers/scsi/adpahci/sysdef.h:604: warning: useless storage class
specifier in empty declaration
In file included from drivers/scsi/adpahci/cdacsmi.h:60,
                 from drivers/scsi/adpahci/hr.h:96,
                 from drivers/scsi/adpahci/hr.c:35:
drivers/scsi/adpahci/sysdef.h:613:1: warning: "ABORT_TASK" redefined
In file included from drivers/scsi/adpahci/hr.h:71,
                 from drivers/scsi/adpahci/hr.c:35:
include/scsi/scsi.h:277:1: warning: this is the location of the previous
definition
In file included from drivers/scsi/adpahci/cdacsmi.h:66,
                 from drivers/scsi/adpahci/hr.h:96,
                 from drivers/scsi/adpahci/hr.c:35:
drivers/scsi/adpahci/csmisasa.h:117:7: warning: "_WIN32" is not defined
In file included from drivers/scsi/adpahci/cdacsmi.h:66,
                 from drivers/scsi/adpahci/hr.h:96,
                 from drivers/scsi/adpahci/hr.c:35:
drivers/scsi/adpahci/csmisasa.h:184: warning: ignoring #pragma
CSMI_SAS_BEGIN_PACK
drivers/scsi/adpahci/csmisasa.h:257: warning: ignoring #pragma
CSMI_SAS_END_PACK
In file included from drivers/scsi/adpahci/hr.c:35:
drivers/scsi/adpahci/hr.h:134:5: warning: "HR_DEBUG" is not defined
drivers/scsi/adpahci/hr.h:392:1: warning: "roundup" redefined
In file included from include/linux/cache.h:4,
                 from include/asm/pda.h:7,
                 from include/asm/thread_info.h:14,
                 from include/linux/thread_info.h:21,
                 from include/linux/preempt.h:9,
                 from include/linux/spinlock.h:49,
                 from include/linux/vmalloc.h:4,
                 from include/asm/io.h:105,
                 from drivers/scsi/adpahci/hr.h:40,
                 from drivers/scsi/adpahci/hr.c:35:
include/linux/kernel.h:43:1: warning: this is the location of the
previous definition
drivers/scsi/adpahci/hr.c:1024:43: error: macro "INIT_WORK" passed 3
arguments, but takes just 2
drivers/scsi/adpahci/hr.c: In function ‘hr_setup_dev_dpc_task’:
drivers/scsi/adpahci/hr.c:1024: error: ‘INIT_WORK’ undeclared (first use
in this function)
drivers/scsi/adpahci/hr.c:1024: error: (Each undeclared identifier is
reported only once
drivers/scsi/adpahci/hr.c:1024: error: for each function it appears in.)
drivers/scsi/adpahci/hr.c: In function ‘hr_pci_init’:
drivers/scsi/adpahci/hr.c:1186: error: implicit declaration of function
‘pci_module_init’
drivers/scsi/adpahci/hr.c: In function ‘hr_register_host’:
drivers/scsi/adpahci/hr.c:1560: error: implicit declaration of function
‘scsi_assign_lock’
drivers/scsi/adpahci/hr.c: In function ‘hr_ioctl’:
drivers/scsi/adpahci/hr.c:2444: warning: ignoring return value of
‘copy_to_user’, declared with attribute warn_unused_result
drivers/scsi/adpahci/hr.c:2540: warning: ignoring return value of
‘copy_to_user’, declared with attribute warn_unused_result
drivers/scsi/adpahci/hr.c:2838:5: warning: "_NOTYET_" is not defined
drivers/scsi/adpahci/hr.c: At top level:
drivers/scsi/adpahci/hr.c:2966: warning: initialization from
incompatible pointer type
drivers/scsi/adpahci/hr.c: In function ‘hr_pci_dev_probe’:
drivers/scsi/adpahci/hr.c:3129: warning: ‘deprecated_irq_flag’ is
deprecated (declared at include/linux/interrupt.h:64)
drivers/scsi/adpahci/hr.c:3129: warning: passing argument 2 of
‘request_irq’ from incompatible pointer type
drivers/scsi/adpahci/hr.c: In function ‘hr_watchdog_thread’:
drivers/scsi/adpahci/hr.c:3704: error: ‘PF_FREEZE’ undeclared (first use
in this function)
drivers/scsi/adpahci/hr.c: In function ‘hr_ehandler_thread’:
drivers/scsi/adpahci/hr.c:4830: error: ‘PF_FREEZE’ undeclared (first use
in this function)
gmake[5]: *** [drivers/scsi/adpahci/hr.o] Error 1
gmake[4]: *** [drivers/scsi/adpahci] Error 2
gmake[3]: *** [drivers/scsi] Error 2
make[2]: *** [drivers] Error 2
error: Bad exit status from /var/tmp/rpm-tmp.66191 (%build)
- ----------------------------------------------------------------

Sorry for the long output, but that is the entire error so I included
the whole thing.

I guess the thing I am looking for is to ask if anyone else on this list
has successfully compiled Adaptec modules into the kernel before. I am
also wondering why there are so many errors and undeclared functions. I
did follow the instructions that came with the module and have even
tried over and over again. Thanks.

/paul

Paul VanGundy wrote:
> Thanks for the prompt replay David. Below are the answers to your questions:
> 
>>> Hello. I don't know if this is the right place to post this issue but it
>>> does deal with RAID so I thought I would try.
>> It deals primarily with linux *software* raid.
>> But stick with it - you may end up doing that...
> 
>> What hardware/distro etc are you using?
>> Is this an expensive (hundreds of £) card? Or an onboard/motherboard chipset?
> The distro is Suse 10.1. It is an onboard chipset.
>> Once you answer this then it may be worth suggesting using sw-raid (in which
>> case we can help out) or pointing you elsewhere...
> 
>>> I successfully built a new kernel and am able to boot from it.
>>> However, I need to incorporate a specific RAID driver (adpahci.ko) so we
>>> can use the on-board RAID.
>> I think this is the adaptec proprietary code - in which case you may need a very
>> specific kernel to run it. You may find others on here who can help but you'll
>> probably need an Adaptec forum/list.
> Oi. This is a pain... ;)
>>> I have the adpahci.ko and am unable to get
>>> it to compile against any other kernel because I don't have the original
>>> kernel module (adpahci.c I assume is what I need). Is there any way I
>>> can view the adpahci.ko and copy the contents to make a adpahci.c?
>> No
> That sucks. :)
>>> Is it
>>> possible to get the kernel object to compile with another kernel only
>>> using the adpahci.ko?
>> No
> 
>>> Am I making sense?  :)
>> Yes
> Good, because sometimes I don't make sense to myself. :)
>> That's one of the big reasons proprietary drivers suck on linux.
> 
> Ok. So this chipset has the ability to use an Intel based RAID. Would
> that be better?
> 
> Thanks again.
> 
> /paul
- -
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHMe0Wul+dQkHY548RApPuAJwMDgD9QsTd95KstkBQ9lwYGoMIvQCeNo1+
zod3Ps0tRbgAqaF4ChvWBMc=
=KtCC
-----END PGP SIGNATURE-----
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html