Solved: Re: DVB: Unable to find symbol m88ds3103_attach() [Kernel 5.18.13]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello Skari,
hello list members,

the solution is, that CONFIG_TRIM_UNUSED_KSYMS *must not* be enabled.
The error occurs if it is, and vanishes, if it is not (e.g. module
loading works).

I tried to whitelist "m88ds3103_attach", however, the build dies[1] if I
do this (many other builds to find this out suceeded). 

I'm now on 6.0.2.

So either CONFIG_TRIM_UNUSED_KSYMS is broken (the help referes to 
possible issues with external modules, not internal) or cx23885 needs
to depend on this option to be off (possibly as workaround).

Please tell me, what else you need to fix the kernel. Is reporting
here sufficient or should I do this elsewhere?

Thanks

        Helge

For reference, below the last mail:

On Tue, Jul 26, 2022 at 10:40:16PM +0300, Sakari Ailus wrote:
> On Sat, Jul 23, 2022 at 05:57:07PM +0200, Helge Kreutzmann wrote:
> > I want to operate a Hauppauge WinTV-HR-5524 HD [1]. Despite numerous
> > attempts / searches /trials, I'm unable to get the sattelite part
> > operating, I always get (during boot):
> > 
> > Jul 23 08:37:19 twentytwo kernel: [    6.632755] DVB: Unable to find symbol m88ds3103_attach()
> > 
> > The full related boot log is below [2], I can provide more additional 
> > lines as necessary of course.
> > 
> > I listed the (related) loaded modules below [3], again I can provide
> > the full list of course.
> > 
> > Based on grep'ing through the kernel sources[4], I also modprobed …
> > but this did not improve the satellite detection[5].
> > 
> > According to the vendor satellite should work.
> > 
> > I can provide more details (also tried applications, ..) as needed.
> > 
> > Thanks for any pointer to get the satellite tuner working!
> 
> Looking at the problem, I guess this looks like something that shouldn't
> generally happen.
> 
> Have you tried removing cx23885 module and loading it again? It would seem
> lake in lsmod listing the module is there but somehow the symbol isn't
> found. I can't immediately think what else could cause this, than not being
> able to load the needed module when the symbol is looked up.

[1] with the following:
  CC [M]  drivers/iio/industrialio-triggered-event.o
  LD [M]  drivers/iio/industrialio.o
  GEN     .version
  CHK     include/generated/compile.h
  LD      vmlinux.o
  MODPOST vmlinux.symvers
  MODINFO modules.builtin.modinfo
  GEN     modules.builtin
  CC      .vmlinux.export.o
BTF: .tmp_vmlinux.btf: pahole (pahole) is not available
Failed to generate BTF for vmlinux
Try to disable CONFIG_DEBUG_INFO_BTF
make[3]: *** [Makefile:1169: vmlinux] Fehler 1
make[2]: *** [debian/rules:7: build-arch] Fehler 2
dpkg-buildpackage: Fehler: Unterprozess debian/rules binary lieferte Exitstatus 2
make[1]: *** [scripts/Makefile.package:83: bindeb-pkg] Fehler 2
make: *** [Makefile:1558: bindeb-pkg] Fehler 2
Version string is: twentytwo.03


-- 
      Dr. Helge Kreutzmann                     debian@xxxxxxxxxxxxx
           Dipl.-Phys.                   http://www.helgefjell.de/debian.php
        64bit GNU powered                     gpg signed mail preferred
           Help keep free software "libre": http://www.ffii.de/

Attachment: signature.asc
Description: PGP signature


[Index of Archives]     [Linux Input]     [Video for Linux]     [Gstreamer Embedded]     [Mplayer Users]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux