I may have a similar problem here, I'm using debian with kernel
2.8.18-4-686 and udev v105, Vstuff v0.20.8 with four channel VGSM I card
In my case the kstreamer devices are created correctly but nothing gets
created for vgsm_mex.
udevtest /sys/class/tty/vgsm_meo gives this output:
main: looking at device '/class/tty/vgsm_me0' from subsystem
'tty'
run_program: 'vgsm_helper vgsm_me0'
run_program: '/lib/udev/vgsm_helper' returned with status 0
udev_rules_get_name: rule applied, 'vgsm_me0' becomes ''
udev_device_event: device node creation supressed
main: run: 'socket:/org/kernel/udev/monitor'
main: run: 'socket:/org/freedesktop/hal/udev_event'
Using udevmonitor --env shows that whenever the vgsm_mex devices are
being added the environment does not have the required $PHYSDEVPATH or
$PHYSDEVBUS set:
udevmonitor prints the received event from the kernel [UEVENT]
and the event which udev sends out after rule processing [UDEV]
UEVENT[1179149870.196706] add@/module/vgsm
ACTION=add
DEVPATH=/module/vgsm
SUBSYSTEM=module
SEQNUM=1634
UEVENT[1179149870.196883] add@/class/tty/vgsm_me0
ACTION=add
DEVPATH=/class/tty/vgsm_me0
SUBSYSTEM=tty
SEQNUM=1635
MAJOR=253
MINOR=0
UEVENT[1179149870.196894] add@/class/tty/vgsm_me1
ACTION=add
DEVPATH=/class/tty/vgsm_me1
SUBSYSTEM=tty
SEQNUM=1636
MAJOR=253
MINOR=1
UEVENT[1179149870.196914] add@/class/tty/vgsm_me2
ACTION=add
DEVPATH=/class/tty/vgsm_me2
SUBSYSTEM=tty
SEQNUM=1637
MAJOR=253
MINOR=2
... and so on up to vgsm_me62
Dmseg shows the following (with the kobject_add error repeated for each
of the four channels in the vgsm card )
PCI: Enabling device 0000:03:0d.0 (0000 -> 0003)
ACPI: PCI Interrupt 0000:03:0d.0[A] -> GSI 20 (level, low) -> IRQ 50
vgsm-pci: vgsm card found at 0xfdcff000 mapped at e0370000
vgsm-pci: VGSM card initialized
Micro 0 firmware version 2.2
Micro 1 firmware version 2.2
kobject_add failed for vgsm_me0 with -EEXIST, don't try to register
things with the same name in the same directory.
[<c01b7e78>] kobject_add+0x147/0x16d
[<c021152d>] class_device_add+0x9d/0x3b3
[<c01b7c06>] kobject_get+0xf/0x13
[<c02118cc>] class_device_create+0x79/0x99
[<c01fa19f>] tty_register_device+0x9e/0xa9
[<c0121c24>] tasklet_action+0x55/0xaf
[<e03797bf>] vgsm_write_msg+0x83/0x97 [vgsm]
[<e03797bf>] vgsm_write_msg+0x83/0x97 [vgsm]
[<e037b3dd>] vgsm_send_msg+0x41/0x85 [vgsm]
[<e037aeaf>] vgsm_module_register+0x27/0x7b [vgsm]
[<e037a293>] vgsm_card_probe+0x512/0x687 [vgsm]
[<c0210b68>] __driver_attach+0x0/0x5d
[<e037907c>] vgsm_probe+0x5/0xf [vgsm]
[<c01c18a8>] pci_device_probe+0x36/0x57
[<c0210ac9>] driver_probe_device+0x42/0x8b
[<c0210ba0>] __driver_attach+0x38/0x5d
[<c02105ea>] bus_for_each_dev+0x33/0x55
[<c0210a33>] driver_attach+0x11/0x13
[<c0210b68>] __driver_attach+0x0/0x5d
[<c0210303>] bus_add_driver+0x64/0xfd
[<c01c19e4>] __pci_register_driver+0x47/0x63
[<e012e0cd>] vgsm_init+0xcd/0x119 [vgsm]
[<c01358c1>] sys_init_module+0x16c3/0x1846
[<e014ea8a>] journal_end+0xad/0xb2 [reiserfs]
[<c0102c11>] sysenter_past_esp+0x56/0x79
kobject_add failed for vgsm_me1 with -EEXIST, don't try to register
things with the same name in the same directory.
[<c01b7e78>] kobject_add+0x147/0x16d
[<c021152d>] class_device_add+0x9d/0x3b3
[<c01b7c06>] kobject_get+0xf/0x13
[<c02118cc>] class_device_create+0x79/0x99
[<c01fa19f>] tty_register_device+0x9e/0xa9
.
.
.
vgsm-pci: VoiSmart PCI GSM Wildcard Driver loaded
And trying to load the vgsm module in asterisk 1.2.17 gives:
Warning[13656]: loader.c:325 __load_resource:
/usr/lib/asterisk/modules/chan_vgsm.so: undefined
symbol:vgsm_module_failure
Warning[13656]: loader.c:554 load_modules: loading module chan_vgsm.so
failed!
Any ideas? Can I provide any further information to help here?
Cheers,
Robin.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of matteo
brancaleoni
Sent: 11 May 2007 08:40
To: [email protected]
Subject: Re: [Visdn-hackers] No devices in /dev/ks with udev 039
Hi,
On Tue, 2007-05-08 at 12:27 +0200, Marcello Golfieri wrote:
> I read that in case I have a udev version prior to 054 I need to use
> special rules to make it working. I found out (by looking at the udev
> docs directory - /usr/share/doc/udev-039 - otherwise I'd like to know
> how to alternatively discover udev version...) that this is my case,
039
> in my case.
udev 039 is ancient :)
You should use at least 050, as we do with Centos 4
(that's the same as rhel4).
This rpm :
http://www.matteobrancaleoni.net/OLDSTUFF/udev-050-7.99_1.vs.i386.rpm
is udev for centos4 but should work also on rhel4.
regards,
matteo
--
Matteo Brancaleoni
R&D Director
Tel :+39.02.70633354
Voip :sip:[EMAIL PROTECTED]
_______________________________________________
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
