On 6/29/05, Ant Daniel <[EMAIL PROTECTED]> wrote:
> On 6/22/05, Bryan Mayland <[EMAIL PROTECTED]> wrote:
> > Ant Daniel wrote:
> >
> > >On 6/19/05, Ant Daniel <[EMAIL PROTECTED]> wrote:
> > >
> > >
> > >>insmod: error inserting '/lib/ivtv.ko': -1 Unknown symbol in module
> > >>ERROR: /bin/insmod exited abnormaly!
> > >>insmod: error inserting '/lib/ivtv-fb.ko': -1 Unknown symbol in module
> > >>ERROR: /bin/insmod exited abnormaly!
> > >>
> > >>
> > >No one got any suggestions?
> > >
> > >I'm thinking now of removing the kernel and then reinstalling it,
> > >hopefully this will get me back to the pre initrd issues, then I can
> > >wind the process forwards again (ignoring the initrd step).
> > >
> > >
> >     I've never worked with initrd, but maybe I can help you narrow down
> > the unknown symbol.  Simply dump the imports of the ivtv-fb.ko.  Here's
> > mine:
> > [EMAIL PROTECTED]:~$ nm -u video/ivtv/driver/ivtv-fb.ko
> >          U add_wait_queue
> >          U autoremove_wake_function
> >          U copy_from_user
> >          U copy_to_user
> >          U default_wake_function
> >          U __down_failed
> >          U dump_stack
> >          U fb_alloc_cmap
> >          U finish_wait
> >          U free_pages
> >          U get_user_pages
> >          U get_zeroed_page
> >          U ivtv_api
> >          U ivtv_cards
> >          U ivtv_cards_active
> >          U ivtv_debug
> >          U ivtv_vapi
> >          U jiffies
> >          U kfree
> >          U __kmalloc
> >          U kmem_cache_alloc
> >          U local_bh_enable
> >          U malloc_sizes
> >          U mem_map
> >          U mtrr_add
> >          U mtrr_del
> >          U __page_cache_release
> >          U preempt_schedule
> >          U prepare_to_wait
> >          U printk
> >          U register_framebuffer
> >          U remove_wait_queue
> >          U rwsem_down_read_failed
> >          U rwsem_wake
> >          U schedule
> >          U schedule_timeout
> >          U unregister_framebuffer
> >          U __up_wakeup
> >          U __wake_up
> >
> > Then find which module exports that symbol and make sure it is in your
> > inirtd (and is there a modules.dep in there too?).  That help at all?
> >
> >
> > -------------------------------------------------------
> > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> > from IBM. Find simple to follow Roadmaps, straightforward articles,
> > informative Webcasts and more! Get everything you need to get up to
> > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> > _______________________________________________
> > ivtv-devel mailing list
> > ivtv-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/ivtv-devel
> >
> 
> After some more trial and error I have worked out the following:
> The initrd is ok, the reason the boot errors is a problem with the ivtv load.
> 
> When I removed the ivtv from modprobe.conf the system boots, but then
> when I run modprobe ivtv I get
> 
> Jun 28 19:00:22 olympus kernel: ivtv: Unknown symbol video_unregister_device
> Jun 28 19:00:22 olympus kernel: ivtv: Unknown symbol video_device_alloc
> Jun 28 19:00:22 olympus kernel: ivtv: Unknown symbol video_register_device
> Jun 28 19:00:22 olympus kernel: ivtv: Unknown symbol video_usercopy
> Jun 28 19:00:22 olympus kernel: ivtv: Unknown symbol video_device_release
> Jun 28 19:00:22 olympus kernel: ivtv: Unknown symbol video_unregister_device
> Jun 28 19:00:22 olympus kernel: ivtv: Unknown symbol video_device_alloc
> Jun 28 19:00:22 olympus kernel: ivtv: Unknown symbol video_register_device
> Jun 28 19:00:22 olympus kernel: ivtv: Unknown symbol video_usercopy
> Jun 28 19:00:22 olympus kernel: ivtv: Unknown symbol video_device_release
> 
> Jun 28 19:00:34 olympus kernel: ivtv_fb: Unknown symbol ivtv_cards_active
> Jun 28 19:00:34 olympus kernel: ivtv_fb: Unknown symbol ivtv_debug
> Jun 28 19:00:34 olympus kernel: ivtv_fb: Unknown symbol ivtv_vapi
> Jun 28 19:00:34 olympus kernel: ivtv_fb: Unknown symbol ivtv_cards
> Jun 28 19:00:34 olympus kernel: ivtv_fb: Unknown symbol ivtv_api
> Jun 28 19:00:34 olympus kernel: ivtv_fb: Unknown symbol ivtv_cards_active
> Jun 28 19:00:34 olympus kernel: ivtv_fb: Unknown symbol ivtv_debug
> Jun 28 19:00:34 olympus kernel: ivtv_fb: Unknown symbol ivtv_vapi
> Jun 28 19:00:34 olympus kernel: ivtv_fb: Unknown symbol ivtv_cards
> Jun 28 19:00:34 olympus kernel: ivtv_fb: Unknown symbol ivtv_api
> 
> I'm assuming the ivtv_fb is erroring becuase the ivtv.ko is not
> loading, I know the ivtv.ko errors are something to do with v4l, but I
> don't know what I've broken or where to look to fix it.
> 
> Ant.
> 

Ok I solved it, somehow my videodev.ko got lost.

I manged to restore it by extracting it from the working initrd.img
file, and copying it back.

Finally got an 0.3.6 n :)

Looking forwards to trying the xv stuff.

Ant.


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click
_______________________________________________
ivtv-devel mailing list
ivtv-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

Reply via email to