Re: Installation problems with Suse 9.x

On 04/07/05 23:28, mel jones wrote:
> 
> I have the following problems with two different computers on Suse 9.1
> and 9.2. I have used both Comedi-0.7.69/Comedilib-0.7.22 and
> Comedi-0.7.70/Comedilib-0.7.22
> 
> For some reason,  the irq  includes are not handled correctly  by  the
> configure routine.
> if I add "INCLUDES = -I/usr/src/linux/include/asm-i386/mach-default" to
> the Makefiles, it compiles with no errors.

I'm not sure why that's necessary.  I don't have a copy of SuSE to hand
at the moment, but I have a 'live' DVD I could try.

> Comedilib compiles and installs fine.
> 
> My card is a National Instruments 6023E.
> 
> When I do "modprobe ni_pcimio" I get
>  - from  tail /var/log/messages:
> 
> Jul  1 08:23:24 r6d -- MARK --
> Jul  1 08:28:57 r6d kernel: comedi: no version for "struct_module"
> found: kernel tainted.
> Jul  1 08:28:57 r6d kernel: comedi: unsupported module, tainting kernel.
> Jul  1 08:28:57 r6d kernel: comedi: version 0.7.70 - David Schleef
> <ds_at_schleef.org>
> Jul  1 08:28:58 r6d kernel: 8255: unsupported module, tainting kernel.
> Jul  1 08:28:58 r6d kernel: mite: unsupported module, tainting kernel.
> Jul  1 08:28:58 r6d kernel: Available NI device IDs: 0x2a60
> Jul  1 08:28:58 r6d kernel: comedi_fc: unsupported module, tainting kernel.
> Jul  1 08:28:58 r6d kernel: ni_pcimio: unsupported module, tainting kernel.
> 
> comedi_config will associate ni_pcimio with /dev/comedi0.
> 
> Are these messages important or do they just indicate some 2.4 / 2.6
> variation? How do I fix them? 

Those messages are probably due to a missing 'Modules.symvers' file in
the top-level kernel sources directory.  For SuSE 9.x, you have to
install the 'kernel-ksyms' package for your kernel to get that file.
Try installing 'kernel-syms', then rebuild comedi with 'make clean',
'make', 'make install'.

> Also, How can I get the driver to load at boot time. I tried putting
> entries into /etc/modprobe.conf.local but nothing happens. I may not -
> read probably don't - know the correct syntax for the entry.

If SuSE does coldplugging of modules for PCI cards, they ought to be
loaded automatically, as the PCI IDs are listed in the module's
'MODULE_DEVICE_TABLE', the contents of which end up in the
'/lib/modules/`uname -r`/modules.pcimap' file.  (Maybe they're not being
loaded automatically because of the above errors.)

You'll still need to arrange for 'comedi_config' to run to associate the
'/dev/comedi*' entry for the device, maybe using a hotplug script, a
special modprobe.conf 'install' command, a 'udev' rule or an 'rc.local'
script.

-- 
-=( Ian Abbott _at_ MEV Ltd.    E-mail: <abbotti_at_mev.co.uk>        )=-
-=( Tel: +44 (0)161 477 1898   FAX: +44 (0)161 718 3587         )=-

Received on 2005-07-05Z09:07:17