[asterisk-users] zaptel compilation problems with linux 2.6.19

Tzafrir Cohen tzafrir.cohen at xorcom.com
Sat Dec 2 02:51:37 MST 2006


Hi

On Fri, Dec 01, 2006 at 01:43:20AM -0500, Matthew Rubenstein wrote:
> On Thu, 2006-11-30 at 17:56 -0700,
> asterisk-users-request at lists.digium.com wrote:
> > Message: 18
> > Date: Fri, 1 Dec 2006 00:56:10 +0200
> > From: Tzafrir Cohen <tzafrir.cohen at xorcom.com>
> > Subject: Re: [asterisk-users] zaptel compilation problems with linux
> >         2.6.19
> > To: asterisk-users at lists.digium.com
> > Message-ID: <20061130225610.GJ10512 at xorcom.com>
> > Content-Type: text/plain; charset=us-ascii
> > 
> > On Thu, Nov 30, 2006 at 02:44:03PM -0500, Matthew Rubenstein wrote:
> > >       I'm having problems installing ztdummy on my
> > > CentOS-2.6.16-rc6/Asterisk-1.2.11 datacenter server (no ZAP HW, SIP
> > only
> > > to PSTN). I unpacked the kernel sources and headers in a directory,
> > made
> > > (but not re/installed) the kernel, unpacked the zaptel-1.2.11
> > tarball,
> > > then went thru the make sequence. It seemed to proceed OK (without
> > > errors, just some warnings), but didn't seem to result in a loadable
> > > ztdummy kernel module. Complete (failed) install session transcript
> > is
> > > attached to this message; details appended:
> > > 
> > >
> > -------------------------------------------------------------------------
> > > # cd <path-to-zaptel-1.2.11-source>
> > > # export KSRC=<path-to-kernel-source-root-dir>
> > > # make clean
> > > # make config
> > > [... series of shell script conditionals apparently executed OK ...]
> > > # make linux26
> > > [... series of CC/LD reports, some warnings, no errors ...]
> > > # make install
> > > [... series of INSTALL messages, same warnings from (make linux26),
> > no
> > > errors ...] 
> > > # modprobe ztdummy
> > > FATAL: Module ztdummy not found.
> > > FATAL: Error running install command for ztdummy
> > > # modprobe zaptel
> > > FATAL: Module zaptel not found.
> > >
> > -------------------------------------------------------------------------
> > > 
> > > (make linux26) generated some warnings about various usb_*_dev
> > symbols
> > > undefined in [xpp,wcusb]/*.ko, but no actual errors. (make install)
> > 
> > Those are harmless, IIRC. I'll try to recall their source.
> 
> 	I suspected as such. But I don't think the server has full USB/UHCI
> support running, or fully installed:
> 
> -------------------------------------------------------------------------
> # lsmod
> Module                  Size  Used by
> binfmt_misc            12168  1 
> dm_mod                 59512  0 
> thermal                13864  0 
> processor              25284  1 thermal
> fan                     4772  0 
> floppy                 63172  0 
> generic                 4836  0 [permanent]
> ide_generic             1504  0 [permanent]
> # modprobe usb_uhci
> FATAL: Module uhci_hcd not found.
> # modprobe uhci
> FATAL: Module uhci_hcd not found.
> -------------------------------------------------------------------------
> 
> 
> > > repeated those warnings. (modprobe ztdummy) finished with
> > 
> > Was depmod run?
> 
> 	No, but trying it now (after the transcripted session) didn't seem to
> help:
> -------------------------------------------------------------------------
> # depmod
> # modprobe ztdummy
> FATAL: Module ztdummy not found.
> FATAL: Error running install command for ztdummy
> -------------------------------------------------------------------------
> 
> 
> > uname -r
> 
> # uname -r
> 2.6.16-rc6-060427a

so depmod, modprobe and such will look under /lib/modules/2.6.16-rc6-060427a ,
but the modules were installed elsewhere:

> 
> 
> > ls -l /lib/modules/2.6*/misc/*.ko
> 
> # ls -l /lib/modules/2.6*/misc/*.ko
> -rw-r--r--  1 root root 198617 Nov 30 09:24 /lib/modules/2.6.16-rc6/misc/pciradio.ko
> -rw-r--r--  1 root root 195365 Nov 30 09:24 /lib/modules/2.6.16-rc6/misc/tor2.ko
> -rw-r--r--  1 root root 122139 Nov 30 09:24 /lib/modules/2.6.16-rc6/misc/torisa.ko
> -rw-r--r--  1 root root 114623 Nov 30 09:24 /lib/modules/2.6.16-rc6/misc/wcfxo.ko
> -rw-r--r--  1 root root 164626 Nov 30 09:24 /lib/modules/2.6.16-rc6/misc/wct1xxp.ko
> -rw-r--r--  1 root root 340812 Nov 30 09:24 /lib/modules/2.6.16-rc6/misc/wctdm24xxp.ko
> -rw-r--r--  1 root root 215930 Nov 30 09:24 /lib/modules/2.6.16-rc6/misc/wctdm.ko
> -rw-r--r--  1 root root 204323 Nov 30 09:24 /lib/modules/2.6.16-rc6/misc/wcte11xp.ko
> -rw-r--r--  1 root root 155909 Nov 30 09:24 /lib/modules/2.6.16-rc6/misc/wcusb.ko
> -rw-r--r--  1 root root 343208 Nov 30 09:24 /lib/modules/2.6.16-rc6/misc/zaptel.ko
> -rw-r--r--  1 root root 106184 Nov 30 09:24 /lib/modules/2.6.16-rc6/misc/ztd-eth.ko
> -rw-r--r--  1 root root  92153 Nov 30 09:24 /lib/modules/2.6.16-rc6/misc/ztd-loc.ko
> -rw-r--r--  1 root root  72401 Nov 30 09:24 /lib/modules/2.6.16-rc6/misc/ztdummy.ko
> -rw-r--r--  1 root root  98511 Nov 30 09:24 /lib/modules/2.6.16-rc6/misc/ztdynamic.ko

One way to "fix" this is to move the modules, or pass the kernel
vesiosion explicitly to make with KVERS . However this raises the
question: does the kernel source tree you used to build the module
matches the running kernel version.

Is it a kernel you have built? Is there a link 
/lib/modules/2.6.16-060427a/build ?

> 
> 
> > -------------------------------------------------------------------------
> > > Building /etc/modprobe.d/zaptel...
> > > ***
> > > *** WARNING:
> > > *** If you had custom settings in /etc/modprobe.d/zaptel,
> > > *** they have been moved to /etc/modprobe.d/zaptel.bak.
> > 
> > CentOS? /etc/modprobe.d ? What version is it, exactly?
> 
> 	I'm  not sure which CentOS version - how can I tell?

Where is that kernel from? Have you built it?Doesn't look like a CentOS
kernel.

-- 
               Tzafrir Cohen       
icq#16849755                    jabber:tzafrir at jabber.org
+972-50-7952406           mailto:tzafrir.cohen at xorcom.com       
http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir


More information about the asterisk-users mailing list