[asterisk-users] DAHDI on VMWARE

[Shaun Ruffell]

On 12/2/10 6:47 PM, Shaun Ruffell wrote:
> 
> On 12/2/10 4:53 PM, Danny Nicholas wrote:
>>> Could you update to the lastest version of DAHDI-linux and try:
>>> ]# modprobe wctdm24xxp debug=1
>>>
>>> and give me the dmesg output?
>>>
>>> I think the IO registers being in use is a side effect of a previous
>>> failed load.  I just committed 9503 [1] to bypass that check.
>>>
>>> [1] http://svn.asterisk.org/view/dahdi?view=revision&revision=9503
>>
>> [77861.878126] No iBFT detected.
>> [77901.847781] wctdm24xxp 0000:13:00.0: PCI INT A ->   GSI 16 (level, low) ->
>> IRQ 16
>> [77901.847796] wctdm24xxp 0000:13:00.0: IO Registers are in use by another
>> module.
>> [77901.847807] wctdm24xxp 0000:13:00.0: PCI INT A disabled
>> [77901.847816] wctdm24xxp: probe of 0000:13:00.0 failed with error -5
>>
> 
> Are you sure you installed the new drivers?  After the new drivers are
> loaded, what is the output of 'cat /sys/modules/dahdi/version' and 'cat
> /sys/modules/wctdm24xxp/parameters/debug' ?
> 
> After a quick scan, I didn't see a code path where -EIO (which is the
> -5) would be returned from __voicebus_init without another corresponding
> message in the kernel log.
> 

Actually I think I wasn't clear.  Instead of the "latest version of DAHDI-linux" I think I should have said "to the current trunk of dahdi-linux"  i.e.

]# svn co http://svn.asterisk.org/svn/dahdi/linux/trunk dahdi-linux-trunk
]# cd dahdi-linux-trunk
]# make install
]# /etc/init.d/dahdi stop
]# dmesg -c > /dev/null
]# modprobe wctdm24xxp debug=1
]# dmesg | tee output.txt

The results of output.txt is what I am interested in. 

Thanks, Shaun

-- 
Shaun Ruffell
Digium, Inc. | Linux Kernel Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at: www.digium.com & www.asterisk.org