I think your kernel module isn't loaded for your card.
Once those get loaded, the stuff in /dev gets created.
Look in /lib/modules/<kernel number>/misc for the kernel modules
Do a 'demod -a' first and then you can do a blanket modprobe like this:
modprobe \*
It'll pretty much load all your modules that it can. You can then do a
'dmesg' and see if it says anything about it finding your hardware.
If you know which module is it, you can just do 'modprobe <module
name>
without the .o or .ko.
On Wed, 2004-07-21 at 11:48, Edwig Knol wrote:> I installed the QuadBri card in my * server.
> I'm installing * on a RedHat 9 server
>
> I run the install.sh file. So far no problems.
>
> If I try to start /sbin/ztcfg -v -c /etc/zaptel.conf
>
> I will see the following error:
>
> Zaptel Configuration
> =====================>
> SPAN 1: CCS/ AMI Build-out: 399-533 feet (DSX-1)
> SPAN 2: CCS/ AMI Build-out: 399-533 feet (DSX-1)
> SPAN 3: CCS/ AMI Build-out: 399-533 feet (DSX-1)
> SPAN 4: CCS/ AMI Build-out: 399-533 feet (DSX-1)
>
> 12 channels configured.
>
> Notice: Configuration file is /etc/zaptel.conf
> line 18: Unable to open master device '/dev/zap/ctl'
>
> Does anybody know what I do wrong?
>
> To be complete These are the configuration files:
>
> [zaptel.conf]
> loadzone=nl
> defaultzone=nl
> # qozap span definitions
> # most of the values should be bogus because we are not really zaptel
> span=1,1,3,ccs,ami
> span=2,0,3,ccs,ami
> span=3,0,3,ccs,ami
> span=4,0,3,ccs,ami
>
> bchan=1,2
> dchan=3
> bchan=4,5
> dchan=6
> bchan=7,8
> dchan=9
> bchan=10,11
> dchan=12
>
> [zapatel.conf]
> [channels]
>
> ;
> ; ISDN quadBRI interfaces
> ;
>
> switchtype = euroisdn
> signalling = bri_cpe_ptmp
> pridialplan = local
> group = 1
> context=to-pstn
> channel => 1-2
>
> switchtype = euroisdn
> signalling = bri_cpe_ptmp
> pridialplan = local
> group = 2
> context=to-pstn
> channel => 4-5
>
> To me it looks all fine.
>