asterisk users - Jun 2011 - Dahdi_genconfig - "Empty configuration -- no spans"

Asterisk - 1.8.4.1
Dahdi-linux - 2.4.1.2
Dahdi-tools - 2.4.1
Kernel: 2.6.37.6
Kernel BKL: enabled

I am upgrading Asterisk on this box. It has an OpenVox A400P PCI analog 
card with 1 FXO and 1FXS module.

This server has been running just fine for two years with Asterisk 1.6.1.0

I've just upgraded all the OS and installed Asterisk 1.8.4.1. On trying 
to configure the A400P I get:

# modprobe dahdi

# modprobe wctdm

# dahdi_genconf
Empty configuration -- no spans
Empty configuration -- no spans

# dahdi_cfg -vvv
DAHDI Tools Version - 2.4.1

DAHDI Version: 2.4.1.2
Echo Canceller(s):
Configuration
=====================

Channel map:


0 channels to configure.

# dahdi_hardware
driver should be 'wctdm' but is actually 'netjet'
pci:0000:01:09.0     wctdm+       e159:0001 Wildcard TDM400P REV E/F



Where am I going wrong? Why is dahdi_genconf not seeing the card, when 
dahdi_hardware does see it? I've tried "modprobe netjet", but
makes no
difference.


Thanks for any suggestions,

Sebastian

On 01/06/11 16:11, Sebastian Arcus wrote:
> Asterisk - 1.8.4.1
> Dahdi-linux - 2.4.1.2
> Dahdi-tools - 2.4.1
> Kernel: 2.6.37.6
> Kernel BKL: enabled
>
> I am upgrading Asterisk on this box. It has an OpenVox A400P PCI analog
> card with 1 FXO and 1FXS module.
>
> This server has been running just fine for two years with Asterisk 1.6.1.0
>
> I've just upgraded all the OS and installed Asterisk 1.8.4.1. On trying
> to configure the A400P I get:
>
> # modprobe dahdi
>
> # modprobe wctdm
>
> # dahdi_genconf
> Empty configuration -- no spans
> Empty configuration -- no spans
>
> # dahdi_cfg -vvv
> DAHDI Tools Version - 2.4.1
>
> DAHDI Version: 2.4.1.2
> Echo Canceller(s):
> Configuration
> =====================>
>
> Channel map:
>
>
> 0 channels to configure.
>
> # dahdi_hardware
> driver should be 'wctdm' but is actually 'netjet'

Answering my own quesiton. The answer was staring me in the face right 
on the line above. Thank you Asterisk team for putting in really helpful 
messages in there (no, that was not sarcasm - that message really is 
helpful).

As the line reads (well, implies), blacklisting netjet in 
/etc/modprobe.d/blacklist.conf and restarting did the trick.

Sebastian

 > pci:0000:01:09.0 wctdm+ e159:0001 Wildcard TDM400P REV E/F
>
>
>
> Where am I going wrong? Why is dahdi_genconf not seeing the card, when
> dahdi_hardware does see it? I've tried "modprobe netjet", but
makes no
> difference.
>
>
> Thanks for any suggestions,
>
> Sebastian
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> New to Asterisk? Join us for a live introductory webinar every Thurs:
> http://www.asterisk.org/hello
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-users
>