[Asterisk-Users] Problem with MeetMe

Daniel Salama dsalama at user.net
Thu May 12 07:35:56 MST 2005


What I have discovered is that my motherboard only supports usb-ohci  
and not usb-uhci. Reading on the wiki, it says that ztdummy requires  
usb-uhci.

To make things worse, I slapped in a TDM22B just to get timer  
support, only to discover that the machine kept crashing because of a  
hardware conflict with my RAID controller. Really weird!

Anyway, my only three other options are:
1) Compile kernel 2.6, which I'd hate to do
2) Replace either the motherboard or the RAID controller, which is  
worse than option 1
3) Setup a separate machine where I can install the TDM22B and  
dedicate it just for MeetMe and may be a couple of other things. I  
may give this a shot. I still need to figure out how to do this, so  
if you guys can provide any sample configs I'd appreciate it.

Any other suggestions you guys may have?

Thanks,
Daniel

On May 12, 2005, at 10:08 AM, Chris wrote:

> It sounds like you don't have USB support compiled in the kernel.
>
>
> Chris
>
> ----- Original Message -----
> From: "Daniel Salama" <dsalama at user.net>
> To: "Asterisk Users Mailing List - Non-Commercial Discussion"  
> <asterisk-users at lists.digium.com>
> Sent: Wednesday, May 11, 2005 11:55 PM
> Subject: Re: [Asterisk-Users] Problem with MeetMe
>
>
>
>> Chris/BJ,
>>
>> I am running REL3 with kernel 2.4.21-27.0.4.ELsmp. I enabled USB
>> devices in the BIOS. Here are the problems I'm seeing:
>>
>> root at asterisk0: ~ > modprobe zaptel
>> root at asterisk0: ~ > modprobe ztdummy
>> /lib/modules/2.4.21-27.0.4.ELsmp/kernel/drivers/usb/host/usb-uhci.o:
>> init_module: No such device
>> Hint: insmod errors can be caused by incorrect module parameters,
>> including invalid IO or IRQ parameters.
>>        You may find more information in syslog or the output from  
>> dmesg
>> /lib/modules/2.4.21-27.0.4.ELsmp/kernel/drivers/usb/host/usb-uhci.o:
>> insmod /lib/modules/2.4.21-27.0.4.ELsmp/kernel/drivers/usb/host/usb-
>> uhci.o failed
>> /lib/modules/2.4.21-27.0.4.ELsmp/kernel/drivers/usb/host/usb-uhci.o:
>> insmod ztdummy failed
>>
>> root at server0: ~ > lsmod
>> Module                  Size  Used by    Not tainted
>> zaptel                183104   0  (unused)
>> soundcore               7044   0  (autoclean)
>> iptable_filter          2412   0  (autoclean) (unused)
>> ip_tables              16544   1  [iptable_filter]
>> e1000                  77884   2
>> floppy                 57552   0  (autoclean)
>> sg                     37388   0  (autoclean)
>> usbcore                81152   1
>> ext3                   89992   2
>> jbd                    55156   2  [ext3]
>> 3w-9xxx               570016   3
>> sd_mod                 13936   6
>> scsi_mod              115240   2  [sg 3w-9xxx sd_mod]
>>
>> root at server0: ~ > modprobe -r zaptel
>> root at server0: ~ > modprobe usb-uhci
>> /lib/modules/2.4.21-27.0.4.ELsmp/kernel/drivers/usb/host/usb-uhci.o:
>> init_module: No such device
>> Hint: insmod errors can be caused by incorrect module parameters,
>> including invalid IO or IRQ parameters.
>>        You may find more information in syslog or the output from  
>> dmesg
>> /lib/modules/2.4.21-27.0.4.ELsmp/kernel/drivers/usb/host/usb-uhci.o:
>> insmod /lib/modules/2.4.21-27.0.4.ELsmp/kernel/drivers/usb/host/usb-
>> uhci.o failed
>> /lib/modules/2.4.21-27.0.4.ELsmp/kernel/drivers/usb/host/usb-uhci.o:
>> insmod usb-uhci failed
>>
>> root at server0: ~ > modprobe usb-ohci
>> root at server0: ~ > modprobe zaptel
>> root at server0: ~ > modprobe ztdummy
>> /lib/modules/2.4.21-27.0.4.ELsmp/kernel/drivers/usb/host/usb-uhci.o:
>> init_module: No such device
>> Hint: insmod errors can be caused by incorrect module parameters,
>> including invalid IO or IRQ parameters.
>>        You may find more information in syslog or the output from  
>> dmesg
>> /lib/modules/2.4.21-27.0.4.ELsmp/kernel/drivers/usb/host/usb-uhci.o:
>> insmod /lib/modules/2.4.21-27.0.4.ELsmp/kernel/drivers/usb/host/usb-
>> uhci.o failed
>> /lib/modules/2.4.21-27.0.4.ELsmp/kernel/drivers/usb/host/usb-uhci.o:
>> insmod ztdummy failed
>>
>> root at server0: ~ > lsmod
>> Module                  Size  Used by    Not tainted
>> zaptel                183104   0  (unused)
>> usb-ohci               23176   0  (unused)
>> soundcore               7044   0  (autoclean)
>> iptable_filter          2412   0  (autoclean) (unused)
>> ip_tables              16544   1  [iptable_filter]
>> e1000                  77884   2
>> floppy                 57552   0  (autoclean)
>> sg                     37388   0  (autoclean)
>> usbcore                81152   1  [usb-ohci]
>> ext3                   89992   2
>> jbd                    55156   2  [ext3]
>> 3w-9xxx               570016   3
>> sd_mod                 13936   6
>> scsi_mod              115240   2  [sg 3w-9xxx sd_mod]
>>
>> It still won't load ztdummy. I can't get usb-uhci to work. I read on
>> the wiki that ztdummy requires uhci. What's the difference between
>> ohci and uhci?
>>
>> Thanks,
>> Daniel
>>
>> On May 11, 2005, at 9:16 PM, Chris wrote:
>>
>>
>>>     I forgot because I haven't moved to a 2.6 kernel.
>>>
>>>
>>> Chris
>>>
>>>
>>> ----- Original Message -----
>>> From: "BJ Weschke" <bweschke at gmail.com>
>>> To: "Asterisk Users Mailing List - Non-Commercial Discussion"
>>> <asterisk-users at lists.digium.com>
>>> Sent: Wednesday, May 11, 2005 6:56 PM
>>> Subject: Re: [Asterisk-Users] Problem with MeetMe
>>>
>>>
>>>
>>>
>>>> Only if you're on a 2.4 kernel. A 2.6 kernel doesn't require USB  
>>>> for
>>>> it's timing source.
>>>>
>>>> On 5/11/05, Chris <listmail at odisok.net> wrote:
>>>>
>>>>
>>>>>     Edit the Makefile for the zaptel drivers.   You will see two
>>>>> commented lines that say ztdummy.  Uncomment them and rebuild.
>>>>> Once you install the rebuild, do a modprobe ztdummy and you
>>>>> should be good to go.   BTW, you do need an active USB for
>>>>> ztdummy to load.
>>>>>
>>>>>
>>>>> Chris
>>>>>
>>>>> ----- Original Message -----
>>>>> From: "Daniel Salama" <dsalama at user.net>
>>>>> To: "Asterisk Users Mailing List - Non-Commercial Discussion"
>>>>> <asterisk-users at lists.digium.com>
>>>>> Sent: Wednesday, May 11, 2005 3:28 PM
>>>>> Subject: Re: [Asterisk-Users] Problem with MeetMe
>>>>>
>>>>>
>>>>>
>>>>>> I don't have any of those modules loaded. I don't have any digium
>>>>>> cards so wcfxo and wcfxs won't load. When I do make clean; make
>>>>>> install in /usr/src/zaptel, it doesn't build ztdummy. If I  
>>>>>> manually
>>>>>> build ztdummy by running make zdummy.o and then try to insmod, it
>>>>>> fails with a bunch of unresolved symbols. I think it may have  
>>>>>> to do
>>>>>> with the fact that I don't have uhci support.
>>>>>>
>>>>>> I tried building zaprtc but when I do make load, it fails. dmesg
>>>>>> shows rtc: I/O port 112 is not free.
>>>>>>
>>>>>> Any other ideas?
>>>>>>
>>>>>> Thanks,
>>>>>> Daniel
>>>>>>
>>>>>> On May 11, 2005, at 3:41 PM, Chris wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>>     No timing?    Do you have the wcfxo, wcfxs, or ztdummy  
>>>>>>> loaded?
>>>>>>>
>>>>>>> ----- Original Message -----
>>>>>>> From: "Daniel Salama" <dsalama at user.net>
>>>>>>> To: "Asterisk Users Mailing List - Non-Commercial Discussion"
>>>>>>> <asterisk-users at lists.digium.com>
>>>>>>> Sent: Wednesday, May 11, 2005 1:09 PM
>>>>>>> Subject: [Asterisk-Users] Problem with MeetMe
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> I'm trying to configure some meet me rooms in asterisk 1.0.2
>>>>>>>> and I'm
>>>>>>>> getting the following problem:
>>>>>>>>
>>>>>>>>      -- Executing MeetMe("SIP/3210-38a9", "0224|qM") in new  
>>>>>>>> stack
>>>>>>>>    == Parsing '/etc/asterisk/meetme.conf': Found
>>>>>>>> May 11 14:05:46 WARNING[20050]: chan_zap.c:757 zt_open:  
>>>>>>>> Unable to
>>>>>>>> open '/dev/zap/pseudo': No such device or address
>>>>>>>> May 11 14:05:46 ERROR[20050]: chan_zap.c:6687 chandup: Unable
>>>>>>>> to dup
>>>>>>>> channel: No such device or address
>>>>>>>> May 11 14:05:46 WARNING[20050]: app_meetme.c:227 build_conf:
>>>>>>>> Unable
>>>>>>>> to open pseudo channel - trying device
>>>>>>>> May 11 14:05:46 WARNING[20050]: app_meetme.c:230 build_conf:
>>>>>>>> Unable
>>>>>>>> to open pseudo device
>>>>>>>>      -- Playing 'conf-invalid' (language 'en')
>>>>>>>>
>>>>>>>> I have the following in meetme.conf
>>>>>>>> [rooms]
>>>>>>>> conf => 0224
>>>>>>>>
>>>>>>>> What could be happening? I don't have any digium cards on the
>>>>>>>> machine. lsmod shows:
>>>>>>>> Module                  Size  Used by    Not tainted
>>>>>>>> zaptel                182080   0
>>>>>>>>
>>>>>>>> The other modules are not related to zaptel or asterisk.
>>>>>>>>
>>>>>>>> ls -l /dev/zap/ps* shows:
>>>>>>>> crw-r--r--    1 root     root     196, 255 May 11 10:07 /dev/ 
>>>>>>>> zap/
>>>>>>>> pseudo
>>>>>>>>
>>>>>>>> Any ideas?
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Daniel
>>>>>>>>
>>>>>>>>
>> _______________________________________________
>> Asterisk-Users mailing list
>> Asterisk-Users at lists.digium.com
>> http://lists.digium.com/mailman/listinfo/asterisk-users
>> To UNSUBSCRIBE or update options visit:
>>    http://lists.digium.com/mailman/listinfo/asterisk-users
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users




More information about the asterisk-users mailing list