To have the 4 card is the VGSM2 driver , and for that you need vstuff , not 
visdn. At least i coulnt make it work with visdn.
Just download vstuff
./configure
make
make install
depmod -a
ldconfig
copy the VGSM and VISDN rules to the udev rules directory (you need those to 
create the devices in "/dev/....")
reboot
and you should be all set

Carlos Galveias


----- Original Message ----- 
From: "Ibon Urretavizcaya" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Wednesday, July 18, 2007 12:19 PM
Subject: [Visdn-hackers] open failed: No such device


Hi,

I've problems to access the SIM modules. Installed software:

Ubuntu 7.04
kernel 2.6.20-16-server
Udev 105

the vGSM (4 SIM) card is detected, lspci:

02:06.0 Network controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN 
interface

I copy the configure file to:

/etc/vgsm/devices/pci-0000:02:06.0

And after compiling, I run "depmod -a", "ldconfig", "modprobe
ks_userport", "modprobe vgsm" and "lsmod | grep vgsm"

vgsm                   28172  0
ks_softswitch           4948  2 vgsm,ks_userport
kstreamer              39964  3 vgsm,ks_userport,ks_softswitch

dmesg:
[ 9094.788695] kstreamer: loading
[ 9094.791266] ks-userport: kstreamer userport module loading
[ 9099.343542] vgsm: VoiSmart vGSM-I card driver loaded

But, when I run "vgsmctl -d /dev/vgsm_me0 power on"
open failed: No such device

The only thing that I didn´t use of the install instructions is the
30-vgsm.rules and the helper, they don´t work for me. But without them
when I load de vgsm module I get:

/dev/vgsm_me0 to /dev/vgsm_me62

In asterisk CLI: show vgsm modules
averias0  : CLOSED  Error opening device: open(/dev/vgsm_me0): No such 
device
averias1  : CLOSED  Error opening device: open(/dev/vgsm_me1): No such 
device
averias2  : CLOSED  Error opening device: open(/dev/vgsm_me2): No such 
device
averias3  : CLOSED  Error opening device: open(/dev/vgsm_me3): No such 
device

The very strange thing is that a month ago the card worked fine, I was
configuring asterisk, doing some test, and after a reboot .... I get
the CLOSED error. Any idea? How can I check step by step?

This weekend I would try to change the card of pci slot, or even try
it in another cpu. I'm lost.

I thinking it could be a hardware error, I'm form Spain I buyed the
card in a Germany Online shop, and Voismart is from Italy... ¿where I
can send the card to verify it?, I buyed first of this year, so it is
in guarantee.

By the way, if my only asterisk hardware is your VGSM I card ¿I need
the zaptel software?

Thanks.
Ibon

PS: log when the modules works fine

dmesg
kernel:  kstreamer: loading
kernel:  ACPI: PCI Interrupt 0000:02:06.0[A] -> GSI 32 (level, low) -> IRQ 
22
kernel:  vgsm-pci: vgsm card found at 0xfe9df000 mapped at f8a3a000
kernel:  vgsm-pci: VGSM card initialized
kernel:  Micro 0 firmware version 2.2
kernel:  Micro 1 firmware version 2.2
kernel:  kobject_add failed for vgsm_me0 with -EEXIST, don't try to
register things with the same name in the same directory.
....
up error repeated for vgsm_me1, vgsm_me2 and vgsm_me3
...
kernel:   =======================
kernel:  vgsm-pci: VoiSmart PCI GSM Wildcard Driver loaded

*CLI> show vgsm modules
averias0  : READY REGISTERED_HOME   "MOVISTAR"
averias1  : READY REGISTERED_HOME   "MOVISTAR"
averias2  : READY NOT_REGISTERED
averias3  : READY REGISTERED_HOME   "MOVISTAR"

When all work I've:

Libpri 1.4.0
Zaptel 1.4.3
Asterisk 1.4.4
Vstuff 0.20.10

I've compiled this and a lot of combinations of software and I get the
same error:

Libpri 1.4.1
Zaptel 1.4.4
Asterisk 1.4.2, 1.4.5, 1.4.6, 1.4.7.1, 1.4.8
Vstuff 0.21.2

Even I tried the ubuntu packages of 1.2 tree (asterisk, zaptel,
libpri). In all combinations asterisk works and the vstuff software
compiles fine, but I get "No such device" allways.
_______________________________________________
Visdn-hackers mailing list
[email protected]
https://mailman.uli.it/mailman/listinfo/visdn-hackers 

_______________________________________________
Visdn-hackers mailing list
[email protected]
https://mailman.uli.it/mailman/listinfo/visdn-hackers

Reply via email to