What about

ls -l /usr/lib/modules/2.6.16-1.2111_1.rhfc4.cubbi_swsusp2smp

does the 'build' symlink go to 
/usr/src/kernels/2.6.16-1.2111_1.rhfc4.cubbi_swsusp2smp/

if you do a 'make clean' in the ivtv-0.6.2 directory, does it find the 
kernel sources and correctly clean the modules?
----- Original Message ----- 
From: "Mark Prinz" <[EMAIL PROTECTED]>
To: "User discussion about IVTV" <[email protected]>
Sent: Wednesday, May 31, 2006 10:31 AM
Subject: Re: [ivtv-users] Unknown Symbol Errors after FC3 -> FC4 
UpgradeandIVTV Fresh Install


> Hi Phil,
>
> Looks like I do not have a '/usr/src/linux' symlink. There are two
> directories under /usr/src/, 'kernels' and 'redhat'. Am I mising
> something here?
>
> Under /usr/src/kernels...
>
> [EMAIL PROTECTED] kernels]# ls -l
> total 12
> drwxr-xr-x  18 root root 4096 May 27 16:27
> 2.6.16-1.2111_1.rhfc4.cubbi_swsusp2-i686
> drwxr-xr-x  18 root root 4096 May 30 00:54
> 2.6.16-1.2111_1.rhfc4.cubbi_swsusp2-smp-i686
> lrwxrwxrwx   1 root root   44 May 27 16:44
> 2.6.16-1.2111_1.rhfc4.cubbi_swsusp2smp-i686 ->
> 2.6.16-1.2111_1.rhfc4.cubbi_swsusp2-smp-i686
> drwxr-xr-x  18 root root 4096 May 27 15:38 2.6.16-1.2111_FC4-i686
>
> uname -a: Linux localhost.localdomain
> 2.6.16-1.2111_1.rhfc4.cubbi_swsusp2smp #1 SMP Mon May 22 15:06:33 EDT
> 2006 i686 i686 i386 GNU/Linux
>
> lsmod:
> Module               Size  Used by
> tveeprom               17296  0
> osslinux             1766548  0
> parport_pc             30893  1
> lp                     16641  0
> parport                39689  2 parport_pc,lp
> autofs4                22981  2
> eeprom                 11089  0
> lm85                   33893  0
> hwmon_vid               6721  1 lm85
> hwmon                   7109  1 lm85
> i2c_isa                 8897  0
> sunrpc                149605  1
> xfs                   548133  1
> exportfs                9793  1 xfs
> dm_mod                 57813  0
> video                  19013  0
> button                 10449  0
> battery                13253  0
> ac                      8773  0
> nvidia               4533652  12
> ipv6                  269313  24
> uhci_hcd               35921  0
> ehci_hcd               36301  0
> v4l1_compat            17477  0
> videodev               11392  0
> i82875p_edac           10693  0
> edac_mc                18569  1 i82875p_edac
> hw_random               9817  0
> i2c_i801               12749  0
> i2c_core               25537  6 
> tveeprom,eeprom,lm85,i2c_isa,nvidia,i2c_i801
> e1000                 112429  0
> floppy                 67709  0
> ext3                  133705  3
> jbd                    60885  1 ext3
> ata_piix               14661  1
> libata                 75733  1 ata_piix
> sd_mod                 22081  2
> scsi_mod              136269  2 libata,sd_mod
>
>
> On 5/31/06, Phil Davidov <[EMAIL PROTECTED]> wrote:
>> Mark,
>>
>> Looks like you have multiple kernel source RPM's
>> installed.  Can you confirm which one the
>> '/usr/src/linux' sym-link points to?  Also, could you
>> attach the output of 'uname -a' and 'lsmod' for
>> reference.
>>
>> Phil
>>
>> --- Mark Prinz <[EMAIL PROTECTED]> wrote:
>>
>> > Phil,
>> >
>> > Thanks again for the reply. I think I have
>> > everything correct...
>> >
>> > [EMAIL PROTECTED] /]# rpm -qa|grep kernel
>> > kernel-devel-2.6.16-1.2111_FC4
>> > kernel-smp-2.6.11-1.1369_FC4
>> > kernel-smp-2.6.16-1.2111_1.rhfc4.cubbi_swsusp2
>> > kernel-2.6.16-1.2111_FC4
>> > kernel-smp-devel-2.6.16-1.2111_1.rhfc4.cubbi_swsusp2
>> > kernel-2.6.11-1.1369_FC4
>> > kernel-devel-2.6.16-1.2111_1.rhfc4.cubbi_swsusp2
>> > kernel-2.6.16-1.2111_1.rhfc4.cubbi_swsusp2
>> >
>> > Also...
>> >
>> > [EMAIL PROTECTED] /]# yum info kernel*
>> > Name   : kernel-smp-devel
>> > Arch   : i686
>> > Version: 2.6.16
>> > Release: 1.2111_1.rhfc4.cubbi_swsusp2
>> > Size   : 14 M
>> > Repo   : installed
>> > Summary: Development package for building kernel
>> > modules to match the
>> > SMP kernel.
>> >
>> >
>> >
>> > On 5/31/06, Phil Davidov <[EMAIL PROTECTED]> wrote:
>> > > Mark,
>> > >
>> > > I assume that since you selected/built your kernel
>> > > modules that you have the matching 2.6.16 kernel
>> > > sources (ie. kernel devel RPM) for the kernel you
>> > are
>> > > currently running
>> > > (2.6.16.1.2111_1.rhfc4.cubbi_swsusp2smp).  This is
>> > a
>> > > requirement for compiling ivtv drivers from source
>> > for
>> > > your current kernel.
>> > >
>> > > If this is not the case, you probably want to
>> > > download/install the matching kernel sources,
>> > rebuild
>> > > your ivtv drivers and give it another shot.
>> > >
>> > > BTW, I am running Gentoo with a 2.6.16 kernel w/
>> > ivtv
>> > > drivers 0.6.2 and a PVR150 without problems.  Just
>> > > built everything as recentley as yesterday.
>> > >
>> > > Phil
>> > >
>> > > --- Mark Prinz <[EMAIL PROTECTED]> wrote:
>> > >
>> > > > Simon,
>> > > >
>> > > > Yep...unless something didn't go correct:
>> > > >
>> > > > [EMAIL PROTECTED] /]# ls -1
>> > > >
>> > >
>> >
>> /usr/src/kernels/2.6.16-1.2111_1.rhfc4.cubbi_swsusp2-smp-i686/
>> > > > arch
>> > > > block
>> > > > crypto
>> > > > drivers
>> > > > fs
>> > > > include
>> > > > init
>> > > > ipc
>> > > > kernel
>> > > > lib
>> > > > Makefile
>> > > > Makefile.orig
>> > > > mm
>> > > > Module.symvers
>> > > > net
>> > > > scripts
>> > > > security
>> > > > sound
>> > > > usr
>> > > >
>> > > > On 5/31/06, Simon Baxter <[EMAIL PROTECTED]>
>> > > > wrote:
>> > > > > Did you update your kernel sources?
>> > > > >
>> > > > > > Phil,
>> > > > > >
>> > > > > > Sorry...that would have been helpful. I am
>> > using
>> > > > the 0.6.2.
>> > > > > >
>> > > > > > Thanks,
>> > > > > > Mark
>> > > > > >
>> > > > > > On 5/31/06, Phil Davidov
>> > <[EMAIL PROTECTED]>
>> > > > wrote:
>> > > > > >> Mark,
>> > > > > >>
>> > > > > >> Which version of the ivtv drivers are you
>> > > > using?  I
>> > > > > >> believe that kernel 2.6.16 requires the
>> > latest
>> > > > 0.6.x
>> > > > > >> ivtv drivers.
>> > > > > >>
>> > > > > >> Phil Davidov
>> > > > > >> [EMAIL PROTECTED]
>> > > > > >>
>> > > > > >> --- Mark Prinz <[EMAIL PROTECTED]> wrote:
>> > > > > >>
>> > > > > >> > I recently upgraded my mythtv box from
>> > FC3 to
>> > > > FC4.
>> > > > > >> > Ran into a number
>> > > > > >> > of issues, got through them, but am stuck
>> > > > with the
>> > > > > >> > IVTV stuff.
>> > > > > >> >
>> > > > > >> > After the upgrade and using yum to get
>> > the
>> > > > IVTV
>> > > > > >> > packages, I had no
>> > > > > >> > sound. After trying a bunch of things, I
>> > > > decided to
>> > > > > >> > try and wipe
>> > > > > >> > everything clean and compile from source.
>> > > > > >> >
>> > > > > >> > As mentioned, I am running FC4 with
>> > version
>> > > > 2.6.16
>> > > > > >> > of the kernel
>> > > > > >> > (2.6.16.1.2111_1.rhfc4.cubbi_swsusp2smp
>> > from
>> > > > > >> > atrpms.net)
>> > > > > >> >
>> > > > > >> > When I run modprobe, I get this in dmesg:
>> > > > > >> > ivtv: disagrees about version of symbol
>> > > > > >> > video_unregister_device
>> > > > > >> > ivtv: Unknown symbol
>> > video_unregister_device
>> > > > > >> > ivtv: disagrees about version of symbol
>> > > > > >> > video_device_alloc
>> > > > > >> > ivtv: Unknown symbol video_device_alloc
>> > > > > >> > ivtv: disagrees about version of symbol
>> > > > > >> > video_register_device
>> > > > > >> > ivtv: Unknown symbol
>> > video_register_device
>> > > > > >> > ivtv: disagrees about version of symbol
>> > > > > >> > video_device_release
>> > > > > >> > ivtv: Unknown symbol video_device_release
>> > > > > >> >
>> > > > > >> > Here are the steps I took on this fresh
>> > > > install
>> > > > > >> > (after a cold boot):
>> > > > > >> >
>> > > > > >> > I downloaded the latest firmware and
>> > placed
>> > > > the four
>> > > > > >> > files here:
>> > > > > >> > [EMAIL PROTECTED] firmware]# ls -l
>> > > > /lib/firmware/
>> > > > > >> > drwxr-xr-x  3 root   root     4096 May 30
>> > > > 17:45
>> > > > > >> > 060314 Amity2
>> > > > > >> > 2.0.43.24073.PreRelease
>> > > > > >> > -rw-r--r--  1 root   root   114688 Sep 22
>> > > > 2004
>> > > > > >> > BCM2033-FW.bin
>> > > > > >> > -rw-r--r--  1 root   root     3245 Sep 22
>> > > > 2004
>> > > > > >> > BCM2033-MD.hex
>> > > > > >> > -rw-r--r--  1 root   root      122 Sep 22
>> > > > 2004
>> > > > > >> > BCM-LEGAL.txt
>> > > > > >> > -rw-r--r--  1 mythtv mythtv 262144 May 26
>> > > > 04:35
>> > > > > >> > v4l-cx2341x-dec.fw
>> > > > > >> > -rw-r--r--  1 mythtv mythtv 376836 May 26
>> > > > 04:35
>> > > > > >> > v4l-cx2341x-enc.fw
>> > > > > >> > -rw-r--r--  1 mythtv mythtv 155648 May 26
>> > > > 04:52
>> > > > > >> > v4l-cx2341x-init.mpg
>> > > > > >> > -rw-r--r--  1 mythtv mythtv  16382 May 26
>> > > > 04:35
>> > > > > >> > v4l-cx25840.fw
>> > > > > >> >
>> > > > > >> > I confirmed the packages were correct:
>> > > > > >> > [EMAIL PROTECTED] firmware]# md5sum
>> > v4l-cx2*
>> > > > > >> > 305dba74bbe5905447add8883f3ecb68
>> > > > v4l-cx2341x-dec.fw
>> > > > > >> > 5f5fa240ada73c3565f5f7de4c7b5138
>> > > > v4l-cx2341x-enc.fw
>> > > > > >> > 0661f8b2693fe3123e6234557353eacc
>> > > > > >> > v4l-cx2341x-init.mpg
>> > > > > >> > 99836e41ccb28c7b373e87686f93712a
>> > > > v4l-cx25840.fw
>> > > > > >> >
>> > > > > >> > Even though my
>> > /etc/hotplug/firmware.agent
>> > > > file had:
>> > > > > >> > FIRMWARE_DIR=/lib/firmware, I also added
>> > > > symlinks
>> > > > > >> > here:
>> > > > > >> > [EMAIL PROTECTED] modules]# ls -l|grep
>> > v4l-cx2
>> > > > > >> > lrwxrwxrwx  1 root root   32 May 30 21:50
>> > > > > >> > v4l-cx2341x-dec.fw ->
>> > > > > >> > /lib/firmware/v4l-cx2341x-dec.fw
>> > > > > >> > lrwxrwxrwx  1 root root   32 May 30 21:50
>> > > > > >> > v4l-cx2341x-enc.fw ->
>> > > > > >> > /lib/firmware/v4l-cx2341x-enc.fw
>> > > > > >> > lrwxrwxrwx  1 root root   34 May 30 21:50
>> > > > > >> > v4l-cx2341x-init.mpg ->
>> > > > > >> > /lib/firmware/v4l-cx2341x-init.mpg
>> > > > > >> > lrwxrwxrwx  1 root root   28 May 30 21:50
>> > > > > >> > v4l-cx25840.fw ->
>> > > > > >> > /lib/firmware/v4l-cx25840.fw
>> > > > > >> >
>> > > > > >> > AND here:
>> > > > > >> > [EMAIL PROTECTED] firmware]# ls -l
>> > > > > >> > /usr/lib/hotplug/firmware/
>> > > > > >> > total 0
>> > > > > >> > lrwxrwxrwx  1 root root 32 May 30 21:49
>> > > > > >> > v4l-cx2341x-dec.fw ->
>> > > > > >> > /lib/firmware/v4l-cx2341x-dec.fw
>> > > > > >> > lrwxrwxrwx  1 root root 32 May 30 21:49
>> > > > > >> > v4l-cx2341x-enc.fw ->
>> > > > > >> > /lib/firmware/v4l-cx2341x-enc.fw
>> > > > > >> > lrwxrwxrwx  1 root root 34 May 30 21:49
>> > > > > >> > v4l-cx2341x-init.mpg ->
>> > > > > >> > /lib/firmware/v4l-cx2341x-init.mpg
>> > > > > >> > lrwxrwxrwx  1 root root 28 May 30 21:49
>> > > > > >> > v4l-cx25840.fw ->
>> > > > > >> > /lib/firmware/v4l-cx25840.fw
>> > > > > >> >
>> > > > > >> > I then followed the HOWTO, performed the
>> > > > install,
>> > > > > >> > followed the 'Choose
>> > > > > >> > the Correct Kernel Modules' instructions
>> > > > (i.e. A)
>> > > > > >> > IVTV CARD
>> > > > > >> > INSTALLATION ALONE).
>> > > > > >> >
>> > > > > >> > I confirmed there were no old modules by
>> > > > running:
>> > > > > >> > [EMAIL PROTECTED] firmware]# /sbin/rmmod
>> > ivtv
>> > > > cx25840
>> > > > > >> > tuner tveeprom
>> > > > > >> > msp3400 wm8775 tda9887 saa7115 saa7127
>> > > > > >> > ERROR: Module ivtv does not exist in
>> > > > /proc/modules
>> > > > > >> > ERROR: Module cx25840 does not exist in
>> > > > > >> > /proc/modules
>> > > > > >> > ERROR: Module tuner does not exist in
>> > > > /proc/modules
>> > > > > >> > ERROR: Module msp3400 does not exist in
>> > > > > >> > /proc/modules
>> > > > > >> > ERROR: Module wm8775 does not exist in
>> > > > /proc/modules
>> > > > > >> > ERROR: Module tda9887 does not exist in
>> > > > > >> > /proc/modules
>> > > > > >> > ERROR: Module saa7115 does not exist in
>> > > > > >> > /proc/modules
>> > > > > >> > ERROR: Module saa7127 does not exist in
>> > > > > >> > /proc/modules
>> > > > > >> >
>> > > > > >> > When I run modprobe, I get this in dmesg:
>> > > > > >> > ivtv: disagrees about version of symbol
>> > > > > >> > video_unregister_device
>> > > > > >> > ivtv: Unknown symbol
>> > video_unregister_device
>> > > > > >> > ivtv: disagrees about version of symbol
>> > > > > >> > video_device_alloc
>> > > > > >> > ivtv: Unknown symbol video_device_alloc
>> > > > > >> > ivtv: disagrees about version of symbol
>> > > > > >> > video_register_device
>> > > > > >> > ivtv: Unknown symbol
>> > video_register_device
>> > > > > >> > ivtv: disagrees about version of symbol
>> > > > > >> > video_device_release
>> > > > > >> > ivtv: Unknown symbol video_device_release
>> > > > > >> >
>> > > > > >> > I did a few cold boots on these, left it
>> > off
>> > > > for
>> > > > > >> > over a minute but
>> > > > > >> > still the same problem.
>> > > > > >> >
>> > > > > >> > I believe I have hit everything listed in
>> > the
>> > > > > >> > Troubleshooting page but
>> > > > > >> > alas, I am stuck.
>> > > > > >> >
>> > > > > >> > Any suggestions?
>> > > > > >> >
>> > > > > >> > Thanks.
>> > > > > >> >
>> > > > > >> >
>> > > > _______________________________________________
>> > > > > >> > ivtv-users mailing list
>> > > > > >> > [email protected]
>> > > > > >> >
>> > > >
>> > http://ivtvdriver.org/mailman/listinfo/ivtv-users
>> > > > > >> >
>> > > > > >>
>> > > > > >>
>> > > > > >>
>> > > >
>> > __________________________________________________
>> > > > > >> Do You Yahoo!?
>> > > > > >> Tired of spam?  Yahoo! Mail has the best
>> > spam
>> > > > protection around
>> > > > > >> http://mail.yahoo.com
>> > > > > >>
>> > > > > >>
>> > _______________________________________________
>> > > > > >> ivtv-users mailing list
>> > > > > >> [email protected]
>> > > > > >>
>> > > >
>> > http://ivtvdriver.org/mailman/listinfo/ivtv-users
>> > > > > >>
>> > > > > >
>> > > > > >
>> > _______________________________________________
>> > > > > > ivtv-users mailing list
>> > > > > > [email protected]
>> > > > > >
>> > > >
>> > http://ivtvdriver.org/mailman/listinfo/ivtv-users
>> > > > >
>> > > > >
>> > > > >
>> > > > >
>> > _______________________________________________
>> > > > > ivtv-users mailing list
>> > > > > [email protected]
>> > > > >
>> > http://ivtvdriver.org/mailman/listinfo/ivtv-users
>> > > > >
>> > > >
>> > > > _______________________________________________
>> > > > ivtv-users mailing list
>> > > > [email protected]
>> > > >
>> > http://ivtvdriver.org/mailman/listinfo/ivtv-users
>> > > >
>> > >
>> > >
>> > > __________________________________________________
>> > > Do You Yahoo!?
>> > > Tired of spam?  Yahoo! Mail has the best spam
>> > protection around
>> > > http://mail.yahoo.com
>> > >
>> > > _______________________________________________
>> > > ivtv-users mailing list
>> > > [email protected]
>> > > http://ivtvdriver.org/mailman/listinfo/ivtv-users
>> > >
>> >
>> > _______________________________________________
>> > ivtv-users mailing list
>> > [email protected]
>> > http://ivtvdriver.org/mailman/listinfo/ivtv-users
>> >
>>
>>
>> __________________________________________________
>> Do You Yahoo!?
>> Tired of spam?  Yahoo! Mail has the best spam protection around
>> http://mail.yahoo.com
>>
>> _______________________________________________
>> ivtv-users mailing list
>> [email protected]
>> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>>
>
> _______________________________________________
> ivtv-users mailing list
> [email protected]
> http://ivtvdriver.org/mailman/listinfo/ivtv-users 



_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Reply via email to