Re: getting error while Compiling kernel 2.35 with madwifi driver

Quoting "Pavel Roskin" <[email protected]>:

> On Tue, 18 Oct 2011 15:42:40 +0530
> DarshanPrajapati <[email protected]> wrote:
>
>> Dear all,
>>
>> I am compiling kernel 2.35 after applying patch by ruining
>> install.sh found in "madwifi-0.9.4-r4173-20111008" source downloaded
>> from->
>> "http://snapshots.madwifi-project.org/madwifi-0.9.4-current.tar.gz"
>>
>> it gives error like ------------------------------
>>
>> CC [M]  drivers/net/wireless/madwifi/ath/if_ath.o
>>    CC [M]  drivers/net/wireless/madwifi/ath/if_ath_pci.o
>> In file included from drivers/net/wireless/madwifi/ath/if_ath.c:45:
>> /home/linuxpc1/Darshan/OIB/Downloads/CNS3xxx_LSDK_ver.1.2_RC7_Release/cns3xxx-sdk+buildroot/cns3xxx-sdk/kernel/linux-2.6.35.12/drivers/net/wireless/madwifi/ath/../ath_hal/opt_ah.h:1:18:
>> error:   
>> /home/linuxpc1/Darshan/OIB/Downloads/CNS3xxx_LSDK_ver.1.2_RC7_Release/cns3xxx-sdk+buildroot/cns3xxx-sdk/kernel/linux-2.6.35.12/drivers/net/wireless/madwifi/ath/../hal/public/arm-elf.opt_ah.h:
>> No such file or directory In file included from
>
> "arm-elf" is not a valid TARGET.  It means that TARGET could not be
> determined automatically for your kernel configuration and
> you'll need to specify it manually. Please see the INSTALL file.
>
> Alternatively, you can use the trunk snapshot, which has no binary
> blobs and therefore doesn't need TARGET to be specified.
>
> --
> Regards,
> Pavel Roskin
>

Dear Pavel Roskin,

I have used trunk snapshot as per your suggestion to avoid TARGET  
related issue.

while compiling kernel i found some warnings like...

WARNING:  
/home/linuxpc1/Darshan/OIB/Downloads/CNS3xxx_LSDK_ver.1.2_RC7_Release/cns3xxx-sdk+buildroot/cns3xxx-sdk/.target_rootfs//lib/modules/2.6.35.12-cavm1/kernel/drivers/net/wireless/madwifi/ath/ath_pci.ko needs unknown symbol  
ath_hal_process_noisefloor
WARNING:  
/home/linuxpc1/Darshan/OIB/Downloads/CNS3xxx_LSDK_ver.1.2_RC7_Release/cns3xxx-sdk+buildroot/cns3xxx-sdk/.target_rootfs//lib/modules/2.6.35.12-cavm1/kernel/drivers/net/wireless/madwifi/ath/ath_pci.ko needs unknown symbol  
_ath_hal_detach
WARNING:  
/home/linuxpc1/Darshan/OIB/Downloads/CNS3xxx_LSDK_ver.1.2_RC7_Release/cns3xxx-sdk+buildroot/cns3xxx-sdk/.target_rootfs//lib/modules/2.6.35.12-cavm1/kernel/drivers/net/wireless/madwifi/ath/ath_pci.ko needs unknown symbol  
ath_hal_print_decoded_register

is it normal?

and also while inserting ath_pci module using modprobe i.e.

#modprobe ath_pci

it got failed... i.e. could not insert module and so why could get any  
wirless interface created..

here is the dmesg log [which can help understand more about what is  
wrong] while  inserting module.

[  665.840000] asf: module license 'Proprietary' taints kernel.
[  665.850000] Disabling lock debugging due to kernel taint
[  665.980000] ath_hal: 0.9.17.1 (AR5212, AR5416, AR9380, RF5111,  
RF5112, RF2413, RF5413, RF2316, RF2317, DEBUG, WRITE_EEPROM, 11D)
[  666.130000] ath_pci: disagrees about version of symbol _ath_hal_attach
[  666.140000] ath_pci: Unknown symbol _ath_hal_attach (err -22)
[  666.150000] ath_pci: Unknown symbol ath_hal_process_noisefloor (err 0)
[  666.170000] ath_pci: disagrees about version of symbol  
ath_hal_computetxtime
[  666.180000] ath_pci: Unknown symbol ath_hal_computetxtime (err -22)
[  666.190000] ath_pci: disagrees about version of symbol ath_hal_mhz2ieee
[  666.200000] ath_pci: Unknown symbol ath_hal_mhz2ieee (err -22)
[  666.210000] ath_pci: Unknown symbol _ath_hal_detach (err 0)
[  666.230000] ath_pci: disagrees about version of symbol ath_hal_probe
[  666.240000] ath_pci: Unknown symbol ath_hal_probe (err -22)
[  666.250000] ath_pci: Unknown symbol ath_hal_print_decoded_register (err 0)
[  666.270000] ath_pci: disagrees about version of symbol  
ath_hal_init_channels
[  666.280000] ath_pci: Unknown symbol ath_hal_init_channels (err -22)
[  666.300000] ath_pci: disagrees about version of symbol  
ath_hal_getwirelessmodes
[  666.310000] ath_pci: Unknown symbol ath_hal_getwirelessmodes (err -22)
modprobe: failed to load module ath_pci  
(kernel/drivers/net/wireless/madwifi/ath/ath_pci.ko): Invalid argument



why its happening, am i doing some wrong configuration or forgot  
something to do....

thanks,
Darshan Prajapati





------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct