On Friday 04 May 2007 14:40, Robin D. Bussell wrote: > > Kobject_add failed for vgsm_me0 with -EEXIST, don't try to register > things with the same name in the same directory.
What version of code are you running? There has been some change regarding that so, please, check that you are running the latest software, preferably the bzr version or one of the snapshots. > 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. For the first attempt do not install 30-vgsm2.rules, the devices should be created in /dev, if not, the problem is not in udev. > 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? To move from older software you have to check that no older modules remain in /lib/modules/`uname -r`/ Some new parameter has been added to the configuration files, so, you should give a look to the samples (in samples/) and look if you need to adapt your configuration. Remove 30-visdn.rules and add 30-kstreamer.rules, those are quite important because they creare /dev/ks/userport_* devices. Then modprobe vgsm and see in dmesg if your card has been detected. > 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. Uhm... let's ignore 30-vgsm.rules for a while, they are very tricky to make work on different distributions, you will be able to use vGSM anyway. The rule is essentially needed if you want to persistently name the device files. How many cards do you have? > 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 . Okay, that's a good sign. vgsm_me62 makes me thing you have more than one card :) > Currently however loading asterisk (v1.2.17) gives me a error when > loading chan_vgsm.so: "undefined symbol: vgsm_module_failure" Oops... vgsm_module_failure is really missing and for some strange reason Asterisk 1.4 didn't complain about it. Please download the current bzr tree or tomorrow's snapshot to fix this. Bye, -- Daniele "Vihai" Orlandi Espia S.r.l. _______________________________________________ Visdn-hackers mailing list [email protected] https://mailman.uli.it/mailman/listinfo/visdn-hackers
