[linux-dvb] System fails to boot on adding second DVB-T PCI card

hermann pitton hermann-pitton at arcor.de
Sat Jan 12 16:58:33 CET 2008


Hi,

Am Donnerstag, den 10.01.2008, 13:47 +0000 schrieb John Pilkington:
> hermann pitton wrote:
> > Am Donnerstag, den 10.01.2008, 01:13 +0200 schrieb Axel Thimm:
> >   
> >> Hi,
> >>
> >> On Wed, Jan 09, 2008 at 11:42:19PM +0100, hermann pitton wrote:
> >>     
> >>>>> video_buf: exports duplicate symbol videobuf_mmap_mapper (owned by 
> >>>>> videobuf_core)
> >>>>> video_buf: exports duplicate symbol videobuf_mmap_mapper (owned by 
> >>>>> videobuf_core)
> >>>>>           
> >>> Guess this is the root of the problem. Axel's modules might fail to
> >>> eliminate it.
> >>>
> >>> Mauro has converted the old single videobuf.ko to different types to be
> >>> more flexible. Looks like you have an upgrade to the new types without
> >>> that the old videobuf.ko is removed from your /lib/modules.../media
> >>> stuff. Try to remove/delete it manually and "depmod -a".
> >>>       
> >> is there a way to somehow blacklist videobuf.ko w/o having to remove
> >> it? The reason is that packagewise this belongs to the kernel rpm
> >> which is managed by the upstream vendor (e.g. Red Hat, Fedora) and I
> >> wouldn't want to nuke it - it would return anyway with the next kernel
> >> update.
> >>
> >> Instead maybe some dummy alias or some remapping could be made to
> >> effectively remove it from module-utils' radar w/o actually removing
> >> the file? That would be much cleaner from a packaging POV.
> >>
> >> Thanks!
> >>     
> >
> > Hi Axel,
> >
> > here it is de facto gone, if not anymore in the next kernel release.
> >
> > What you do in between is up to you.
> >
> > If you like to stay in sync as close as possible, of course v4l-dvb
> > counts and not the delayed kernel stuff.
> >
> > Greetings,
> > Hermann
> >
> >
> >
> >
> >
> >
> >
> >
> >   
> I'm not sure what ideas people have about this after a spate of messages 
> yesterday.  The dmesg extracts that I posted were from a forced reboot 
> after an improper shutdown and might not be 'typical', so I just risked 
> a normal reboot from cold.  This did not hang and has delivered a system 
> that seems to be working properly, but during the udev phase and twice 
> afterwards it reported on-screen that the video-buf.ko module was 
> malformed.  This is not recorded in dmesg. 
> 
> I then did an auto shutdown/reboot sequence, again without hanging but 
> with the same malformed-module message.
> 
> dmesg does still include repeated complaints about the duplicate symbol, 
> as above, but there is no module videobuf.ko in the relevant directory.
> > $ cd /lib/modules/2.6.18-53.1.4.el5/updates/drivers/media/video/
> > $ ls -l videobuf*.ko
> > -rw-r--r-- 1 root root 23232 Dec 27 11:21 videobuf-core.ko
> > -rw-r--r-- 1 root root 18120 Dec 27 11:21 videobuf-dma-sg.ko
> > -rw-r--r-- 1 root root 11616 Dec 27 11:21 videobuf-dvb.ko
> > -rw-r--r-- 1 root root 11616 Dec 27 11:21 videobuf-vmalloc.ko
> and the 'malformed' module is not there
> > $ ls -l video-buf*.ko
> > ls: video-buf*.ko: No such file or directory

the old 2.6.18 video-buf.ko is not in Axel's /updates,
but in the original .../drivers/media/video.

Hope this helps.

Else we clean everything ...
(modprobe -v and "less modules.symbols |grep video-buf")

> 
> The two dvb cards are
> > saa7133[0]: subsystem: 1461:f01d, board: Avermedia Super 007 
> > [card=117,autodetected]
> 
> 
> Thanks to all for your interest.  I hope this helps.
> 
> John Pilkington

Cheers,
Hermann





More information about the linux-dvb mailing list