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

Bug#712115: linux-source-3.2: Kernel from proposed-updates fails to build without removing [drivers/staging/rts5139/rts5139.ko] from configuration



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Package: linux-source-3.2
Version: 3.2.46-1
Severity: normal

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these lines ***

I had to remove this: drivers/staging/rts5139 from my kernel-configuration in order to be
able to build correctly, before that I saw this:
.
.
..
  CC [M]  drivers/video/via/accel.o
  CC [M]  drivers/video/via/via_utility.o
  CC [M]  drivers/video/via/vt1636.o
  CC [M]  drivers/video/via/global.o
  CC [M]  drivers/usb/serial/ti_usb_3410_5052.o
  CC [M]  drivers/video/via/tblDPASetting.o
  CC [M]  drivers/video/via/viamode.o
  CC [M]  drivers/video/via/via-core.o
  CC [M]  drivers/video/via/via-gpio.o
  CC [M]  drivers/video/via/via_modesetting.o
  CC [M]  drivers/video/via/via_clock.o
  CC [M]  drivers/usb/serial/visor.o
  CC [M]  drivers/usb/serial/whiteheat.o
  LD [M]  drivers/video/sis/sisfb.o
  CC [M]  drivers/usb/serial/vivopay-serial.o
  LD [M]  drivers/video/via/viafb.o
  CC [M]  drivers/usb/serial/zio.o
  LD [M]  drivers/usb/serial/usbserial.o
  Building modules, stage 2.
  MODPOST 2796 modules
ERROR: "__modver_version_show" [drivers/staging/rts5139/rts5139.ko] undefined!
make[2]: *** [__modpost] Error 1
make[1]: *** [modules] Error 2
make[1]: Leaving directory `/home/andreas/src/linux-source-3.2'
make: *** [debian/stamp/build/kernel] Error 2

See my attached k-configuration.
The second problem is, that the AMD-legacy blob failed to be rebuilt by dkms for the
newly built kernel-image, when setting it up. I have no idea, wether this is the fault of
the dkms-mechanism or if it is the blob's fault, but this used to work very well on
Squeeze, now there was no hint at all about dkms, only update-grub was done when setting
up the new kernel-package. So as it looks like now, I have to reinstall the blob manually
every time a new kernel-version is installed. This is quite bad, another regression,
that makes me want to buy new hardware.

- -- System Information:
Debian Release: 7.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.46cak (SMP w/3 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages linux-source-3.2 depends on:
ii  binutils  2.22-8
ii  bzip2     1.0.6-4

Versions of packages linux-source-3.2 recommends:
ii  gcc                   4:4.7.2-1
ii  libc6-dev [libc-dev]  2.13-38
ii  make                  3.81-8.2

Versions of packages linux-source-3.2 suggests:
pn  libncurses-dev | ncurses-dev  <none>
pn  libqt4-dev                    <none>
ii  pkg-config                    0.26-1

- -- no debconf information
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlG5YhAACgkQ5+rBHyUt5wvd9gCfTv/PhXbckX4tISN7OGpqZi1Y
RZEAnAjXJMlB+YT9qZ4Yt0UvXILlPrcP
=GKKx
-----END PGP SIGNATURE-----

Attachment: config-3.2.46cak.bz2
Description: application/bzip


Reply to: