[Bug 220857] Re: linuxtv.org mercurial repository wont build against hardy kernel due to "disagrees about version of symbol videobuf_*

2008-05-12 Thread ca111a
To: Tim Gardner, Sorry to bother you again, but could you please point me to a guide on how to build against LUM headers? Do I need to somehow combine them with the `uname -r` headers? Thanks! To: Michael Krufky The problem I posted was with the latest uvcvideo module built from the source a

[Bug 150129] Re: [Gutsy] ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave

2007-10-22 Thread ca111a
same here, no sound in vlc, but totem is ok. ~$ aplay -l List of PLAYBACK Hardware Devices card 0: nForce2 [NVidia nForce2], device 0: Intel ICH [NVidia nForce2] Subdevices: 0/1 Subdevice #0: subdevice #0 card 0: nForce2 [NVidia nForce2], device 2: Intel ICH - IEC958 [NVidia nForce2

[Bug 220857] Re: linuxtv.org mercurial repository wont build against hardy kernel due to "disagrees about version of symbol videobuf_*

2008-05-02 Thread ca111a
Similar problem with uvcvideo module: ~$sudo modprobe uvcvideo FATAL: Error inserting uvcvideo (/lib/modules/2.6.24-16-generic/kernel/ubuntu/media/usbvideo/uvcvideo.ko): Unknown symbol in module, or unknown parameter (see dmesg) ~$dmesg [ 5664.367259] uvcvideo: disagrees about version of symbol

[Bug 220857] Re: linuxtv.org mercurial repository wont build against hardy kernel due to "disagrees about version of symbol videobuf_*

2008-04-23 Thread ca111a
same issue here, Mythubuntu 8.04 beta, Pinnacle PCTV 800i card, was working with 2.6.24-12, dist-upgraded yesterday to 2.6.24-16-generic and now seeing: [ 340.574722] cx88xx: disagrees about version of symbol videobuf_dma_free [ 340.574727] cx88xx: Unknown symbol videobuf_dma_free ... -- linux

[Bug 220857] Re: linuxtv.org mercurial repository wont build against hardy kernel due to "disagrees about version of symbol videobuf_*

2008-04-25 Thread ca111a
Removed the installed modules, cleaned, installed linux-headers-lum-2.6.24-16-generic, set C_LIBRARY_PATH/CPLUS_LIBRARY_PATH, built, installed. Still the same issue. It seemed to be able to temporarily insert it when "make insmod" but still with some "error (-19)". Were gone again after reboot