[Asterisk-Users] Meetme : Zaptel ztdummy errors

[Areski]

Hi again !

I don't know if the motherboard have usb port, the machine is a remote
computer ;( 

Actually, I can install usb-ohci but not usb-uhci...


cat /proc/interrupts
           CPU0
  0: 2241860601          XT-PIC  timer
  1:          4          XT-PIC  keyboard
  2:          0          XT-PIC  cascade
  8:        344          XT-PIC  rtc
  9:   17615194          XT-PIC  aic7xxx
 10: 3698029021          XT-PIC  eth0
 14:          0          XT-PIC  ide0
NMI:          0
ERR:          0


Concerning http://www.voip-info.org/tiki-index.php?page=Asterisk+timer
I already had a look on it and as it said : 
"If you don't have Digium hardware, there are two replacements:
- ztdummy
- ztrtc found on http://ns1.jnetdns.de/jn/relaunch/asterisk/
uses the real time clock in the PC instead. This will not work on SMP
systems (Multiprocessor), where the RTC clock is used for SMP support."

I tried to check this page but I cannot find anything relating to ztrtc!
"Downloads  + chan_capi (0.3.0) + zaprtc (0.0.1)  + hfcdummy (0.0.1)"

Anyone have done it before ? 

Thanks in advance,
Areski


On Mon, 2003-11-17 at 15:09, Andrew Thompson wrote:
> Does your motherboard have USB ports and it's just that it's not loaded the right driver?
> 
> Send us a:
> 
> cat /proc/interrupts
> 
> -----
> Andrew Thompson
> 
> ----- Original Message ----- 
> From: "Areski" <areski at e-group.org>
> To: "Asterisk-Users Mailing-list" <asterisk-users at lists.digium.com>
> Sent: Monday, November 17, 2003 8:09 AM
> Subject: [Asterisk-Users] Meetme : Zaptel ztdummy errors
> 
> 
> > Hello All !!! 
> > 
> > 
> > I trying to make meetme working! 
> > 
> > I don't have zaptel interface and I cannot install ztdummy cause I don't
> > have usb-uhci !!! 
> > 
> > Is there any way to get it working ???
> > 
> > 
> > Thanks in advance,
> > Areski
> > 
> > 
> > 
> > 
> > 
> > # modprobe ztdummy
> > /lib/modules/2.4.18-18.7.x/kernel/drivers/usb/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.18-18.7.x/kernel/drivers/usb/usb-uhci.o: insmod
> > /lib/modules/2.4.18-18.7.x/kernel/drivers/usb/usb-uhci.o failed
> > /lib/modules/2.4.18-18.7.x/kernel/drivers/usb/usb-uhci.o: insmod ztdummy
> > failed
> > 
> > # modinfo ztdummy
> > filename:    /lib/modules/2.4.18-18.7.x/kernel/misc/ztdummy.o
> > description: "Dummy Zaptel Driver"
> > author:      "Robert Pleh <robert.pleh at hermes.si>"
> > license:     "GPL"
> > parm:        debug int
> > parm:        monitor int
> > 
> > # modprobe usb-uhci
> > /lib/modules/2.4.18-18.7.x/kernel/drivers/usb/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.18-18.7.x/kernel/drivers/usb/usb-uhci.o: insmod
> > /lib/modules/2.4.18-18.7.x/kernel/drivers/usb/usb-uhci.o failed
> > /lib/modules/2.4.18-18.7.x/kernel/drivers/usb/usb-uhci.o: insmod
> > usb-uhci
> > failed
> > 
> > usb.c: registered new driver usbdevfs
> > usb.c: registered new driver hub
> > usb-uhci.c: $Revision: 1.275 $ time 20:47:35 Nov 13 2002
> > usb-uhci.c: High bandwidth mode enabled
> > usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
> > usb.c: deregistering driver usbdevfs
> > usb.c: deregistering driver hub
> > 
> > 
> > _______________________________________________
> > Asterisk-Users mailing list
> > Asterisk-Users at lists.digium.com
> > http://lists.digium.com/mailman/listinfo/asterisk-users
> >