A bit more info: it looks like when vgsm_helper is being called the
$PHYSDEVBUS and $PHYSDEVPATH are empty. I'm not at all familiar with
udev so I don't know why.
If I remove the udev rules from /etc/udev/ruled.d then I get devices
named vgsm_me0 ... vgsm_me62 created in /dev which seem to work in that
I can use vgsmctl to power on and off modules 0..3 of my card using
/dev/vgsm_me0 ... /dev/vgsm_me3 .
Currently however loading asterisk (v1.2.17) gives me a error when
loading chan_vgsm.so: "undefined symbol: vgsm_module_failure"
Investigation continues, all help appreciated :-)
Cheers,
Robin.
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Robin D.
Bussell
Sent: 04 May 2007 13:41
To: [email protected]
Subject: [Visdn-hackers] trouble loading vstuff vgsm drivers
Hi folks,
When I try to load the vgsm module I get lines like this in the
log:
Kobject_add failed for vgsm_me0 with -EEXIST, don't try to register
things with the same name in the same directory.
Followed by a stack trace and the same gets repeated for each gsm
module.
The module appears in lsmod ok bur udev doesn't seem to be making the
devices, I get no messages regarding vgsm from udev in the log so I'm
guessing the driver isn't loading properly.
Any ideas what might be going on? I have recently been using the latest
visdn on the same system and think perhaps something is left over from
that installation. What steps should be taken when moving from visdn to
vstuff and back?
Cheers,
Robin.
P.S. this is on debian with kernel 2.6.18-4-686
_______________________________________________
Visdn-hackers mailing list
[email protected]
https://mailman.uli.it/mailman/listinfo/visdn-hackers
