asterisk users - Apr 2005 - USB Controller ztdummy

I am attempting my fist asterisk install.
I do not have any digum cards so use ztdummy. 
However according to the Asterisk install guide it says to look for one
of the 
following USB controller chips.
UHCI USB controller of OHCI USB Controller. 
 
However, when I run lsmod to determine which have neither show up.
Can I continue the install and if I do will I have timing issues?
 

This is the output of lsmod

[root@Ask-NY17S root]# lsmod
Module                  Size  Used by
ipv6                  184288  10 
parport_pc             19392  0 
lp                      8236  0 
parport                29640  2 parport_pc,lp
autofs4                10624  0 
sunrpc                101064  1 
e1000                  68492  0 
floppy                 47440  0 
sg                     27552  0 
microcode               4768  0 
binfmt_misc             7176  1 
dm_mod                 33184  0 
button                  4504  0 
battery                 6924  0 
asus_acpi               8472  0 
ac                      3340  0 
ext3                  102376  2 
jbd                    40216  1 ext3
ata_piix                5380  3 
libata                 29312  1 ata_piix,[permanent]
sd_mod                 16384  5 
scsi_mod               91344  3 sg,libata,sd_mod
[root@Ask-NY17S root]# 


Regards, 
Michael 


  

 
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20050415/a1cad06f/attachment.htm

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 15 April 2005 12:51 pm, Michael Di Martino wrote:
> I am attempting my fist asterisk install.
> I do not have any digum cards so use ztdummy.
> However according to the Asterisk install guide it says to look for one
> of the
> following USB controller chips.
> UHCI USB controller of OHCI USB Controller.
>
> However, when I run lsmod to determine which have neither show up.
> Can I continue the install and if I do will I have timing issues?
>
>
> This is the output of lsmod
cat /proc/pci | grep USB?

You should get a line similar to the following:

    USB Controller: ServerWorks OSB4/CSB5 OHCI USB Controller (rev 4).

Or if using /sbin/lspci -v:

00:0f.2 USB Controller: ServerWorks OSB4/CSB5 OHCI USB Controller (rev 04) 
(prog-if 10 [OHCI])
        Subsystem: ServerWorks OSB4/CSB5 OHCI USB Controller

Here, you'll see I'm running an OHCI USB root hub.  Which means if I am
going
to use the ztdummy driver, I must be using Kernel 2.6 or higher.

Or, here's another example using 'cat /proc/pci | grep USB':

    USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 1).

As you can see, /proc/pci doesn't detail which type of USB root hub it is,
but
'/sbin/lspci -v | grep USB' does:

00:04.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01) (prog-if 
00 [UHCI])

As you can see the second machine is using a UHCI root hub.  So, it will work 
with the ztdummy driver on both the 2.4 and the 2.6 kernels.

If, when you do one of approaches mentioned above, and you still don't show
a
USB device, make sure:
	a) you have a USB device
	b) it isn't disabled in your CMOS setup

If you do have a USB device, it is enabled, and it shows up using one of the 
above methods, you need to make sure USB support is configured as a module.  
If you're sure it's configured as a module, try one of the following:
	insmod uhci
	insmod usb-ohci
	insmod usb-uhci
	insmod ehci-hcd

If you try all of the four insmods above, and they all produce errors, your 
usb hardware probably isn't supported.

If one of them worked, then additionally modprobe the same module.

If you can then load the ztdummy driver:  insmod ztdummy ; modprobe ztdummy

Then, everything's working, and you can change your bootup configuration so 
that it automatically loads the USB drivers and the ztdummy driver.  (Make 
sure the ztdummy driver gets loaded after the USB driver(s).)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFCYDvFgYKvkeyp3F4RAmhLAJ0Yc+ZKeI6lTA7jYSrq09x0j6kg2wCfaRjt
TOCyFxwPoi3urPGLckaVEyw=tOSs
-----END PGP SIGNATURE-----