Sangoma A101 not detected **Resolved**

Nope. The only thing I updated with yum is the gcc-c++ per instructions from the Sangoma wiki.

Thanks, yeah, I checked that out, and the strange thing is that there is no 'hotplug' script under /etc/init.d/

[root@asterisk1 ~]# cd /etc/init.d
[root@asterisk1 init.d]# ls
acpid dund killall nfslock saslauthd
anacron ez-ipupdate kudzu nscd sendmail
apmd functions lm_sensors ntpd single
asterisk gpm mdmonitor pand smartd
atd haldaemon mdmpd pcmcia sshd
auditd halt messagebus portmap syslog
autofs hidd microcode_ctl psacct vsftpd
bluetooth httpd mysqld rawdevices wanrouter
cpuspeed ipmi netdump readahead xinetd
crond iptables netfs readahead_early xplhub
cups ircd netplugd rhnsd ypbind
dhcpd irda network rpcgssd yum
dhcrelay irqbalance NetworkManager rpcidmapd
diskdump isdn nfs rpcsvcgssd

I've already tried making the modifications in the link you sent me then rebooting, and still no luck. If you know a way to disable hotplug altogether, I'd love to give that a try, I can't seem to figure it out. I even tried removing the RPM, but there are dependency issues with that...

Well, thanks for the reply, unfortunately that still didn't work. Is this what you have for your /etc/hotplug/net.agent config?

I made that change, added the start script and re-built wanpipe using ./Setup install --protocol=TDM and still get the same error with wanrouter hwprobe. If I run wancfg it does not detect the card, and won't let me generate a wanpipe1 config...

[root@asterisk1 ~]# cat /etc/hotplug/net.agent
#!/bin/sh
#
# Network hotplug policy agent for Linux 2.4 kernels
#
# Kernel NET hotplug params include:
#
# ACTION=%s [register or unregister]
# INTERFACE=%s
#
# HISTORY:
#
# 25-Feb-2001 Special case ppp and similar (redhat)
# 23-Jan-2001 Log invocation of "ifup" if debugging
# 04-Jan-2001 Initial version of "new" hotplug agent.
#
# $Id: net.agent,v 1.20 2004/04/01 08:13:57 kroah Exp $
#

cd /etc/hotplug
. /etc/sysconfig/network-scripts/network-functions
. ./hotplug.functions
# DEBUG=yes export DEBUG

if [ "$INTERFACE" = "" ]; then
mesg Bad NET invocation: \$INTERFACE is not set
exit 1
fi

case $ACTION in
add|register)
# Red Hat specific hack...
if [ -f /etc/redhat-release ]; then
# Don't do anything if the network is stopped
if [ ! -f /var/lock/subsys/network ]; then
exit 0
fi
fi

case $INTERFACE in
# interfaces that are registered after being "up" (?)
ppp*|ippp*|isdn*|plip*|lo*|irda*|dummy*|ipsec*|tun*|tap*|w*)
debug_mesg assuming $INTERFACE is already up
exit 0
;;
# interfaces that are registered then brought up
*)
# NOTE: network configuration relies on administered state,
# we can't do much here without distro-specific knowledge
# such as whether/how to invoke DHCP, set up bridging, etc.

# Run ifrename as needed - Jean II
# Remap interface names based on MAC address. This workaround
# the dreaded configuration problem "all my cards are 'eth0'"...
# This needs to be done before ifup otherwise ifup will get
# confused by the name changed and because iface need to be
# down to change its name.
if [ -x /sbin/ifrename ] && [ -r /etc/iftab ]; then
debug_mesg invoke ifrename for $INTERFACE
NEWNAME=`/sbin/ifrename -i $INTERFACE`
if [ -n "$NEWNAME" ]; then
debug_mesg iface $INTERFACE is remapped to $NEWNAME
INTERFACE=$NEWNAME
fi;
fi

# RedHat and similar
export IN_HOTPLUG=1
if [ -x /sbin/ifup ]; then
addr=`get_hwaddr ${INTERFACE}`
if [ -n "$addr" ]; then
nconfig=`get_config_by_hwaddr ${addr}`
[ -n "$nconfig" ] && INTERFACE=$nconfig
fi
debug_mesg invoke ifup $INTERFACE
exec /sbin/ifup $INTERFACE

# Gentoo
elif [ -f /etc/gentoo-release ]; then
script=/etc/init.d/net.$INTERFACE
if [ -x "$script" ]; then
debug_mesg invoke "$script" --quiet start
exec "$script" --quiet start
fi
else
mesg "how do I bring interfaces up on this distro?"
fi
;;
esac
mesg $1 $ACTION event not handled
;;

remove|unregister)
case $INTERFACE in
# interfaces that are unregistered after being "down" (?)
ppp*|ippp*|isdn*|plip*|lo*|irda*|dummy*|ipsec*|tun*|tap*|w*)
debug_mesg assuming $INTERFACE is already down
exit 0
;;
*)
# right now it looks like only Gentoo wants to care about
# unregistering network devices...
if [ -f /etc/gentoo-release ]; then
script=/etc/init.d/net.$INTERFACE
if [ -x "$script" ]; then
debug_mesg invoke "$script" --quiet stop
exec "$script" --quiet stop
fi
fi
;;
esac
mesg $1 $ACTION event not handled
;;

*)
debug_mesg NET $ACTION event for $INTERFACE not supported
exit 1 ;;

esac

Yes, I do get the error on startup, but not the one you listed after installing the driver.

Well, thanks so much for your advice. I've contacted Sangoma support, and they replied saying that the lspci output looks wrong. So, maybe it's a hardware problem.... The sangoma card is showing up as a VGA adaptor on my system, and it should be showing up as a network adaptor... I wonder if it's the riser card mucking things up....

I couldn't use any of the Sangoma cards with my Riser cards. I ended up buying a different rackmount case that didn't use the riser card. I lost a U of space though in the rack.

That's frustrating. Rack cases aren't cheap, either. Did you try any other riser cards first? Did you have similar errors to what I'm getting? Coming up as a VGA controller?