Bug#404724: linux-image-2.6.16-1-686: can't compile kernel modules, incompatible with gcc 4.1

2006-12-27 Thread Mark Whitis
Package: linux-image-2.6.16-1-686
Version: 2.6.16-12
Severity: grave
Justification: renders package unusable

The current versions of kernel and gcc in unstable conflict, though
not detected at package load time.   This means that it is not possible
to compile loadable kernel modules, which most end-users need to
do at some point (not to mention module developers).

I just did a dist-upgrade from stable to unstable in the last 24 hours.
After that there were serius screen update problems so I tried to install
the nvidia driver (direct from nvidia, the older version I had been using
before).   It reported that the version of gcc used to compile
the kernel (4.0) is not the same as the version of gcc on the system
(4.1) and that the kernel module loader would reject any modules built
with gcc 4.1 (and indeed the module was rejected).



Nvidia driver version: NVIDIA-Linux-x86-1.0-8762-pkg1.run
-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-1-686
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages linux-image-2.6.16-1-686 depends on:
ii  module-init-tools 3.3-pre3-1 tools for managing Linux kernel mo
ii  yaird [linux-initramfs-tool]  0.0.12-18  Yet Another mkInitRD

Versions of packages linux-image-2.6.16-1-686 recommends:
pn  libc6-i686none (no description available)

-- debconf information:
  linux-image-2.6.16-1-686/preinst/initrd-2.6.16-1-686:
  linux-image-2.6.16-1-686/postinst/old-system-map-link-2.6.16-1-686: true
  linux-image-2.6.16-1-686/preinst/already-running-this-2.6.16-1-686:
  linux-image-2.6.16-1-686/preinst/overwriting-modules-2.6.16-1-686: true
  linux-image-2.6.16-1-686/postinst/old-initrd-link-2.6.16-1-686: true
  linux-image-2.6.16-1-686/preinst/abort-overwrite-2.6.16-1-686:
  linux-image-2.6.16-1-686/preinst/elilo-initrd-2.6.16-1-686: true
  linux-image-2.6.16-1-686/prerm/would-invalidate-boot-loader-2.6.16-1-686: true
  linux-image-2.6.16-1-686/postinst/bootloader-error-2.6.16-1-686:
  linux-image-2.6.16-1-686/postinst/create-kimage-link-2.6.16-1-686: true
  linux-image-2.6.16-1-686/preinst/lilo-has-ramdisk:
  linux-image-2.6.16-1-686/prerm/removing-running-kernel-2.6.16-1-686: true
  linux-image-2.6.16-1-686/postinst/old-dir-initrd-link-2.6.16-1-686: true
  linux-image-2.6.16-1-686/postinst/depmod-error-initrd-2.6.16-1-686: false
  linux-image-2.6.16-1-686/preinst/lilo-initrd-2.6.16-1-686: true
  linux-image-2.6.16-1-686/postinst/kimage-is-a-directory:
  linux-image-2.6.16-1-686/preinst/bootloader-initrd-2.6.16-1-686: true
  linux-image-2.6.16-1-686/postinst/depmod-error-2.6.16-1-686: false
  linux-image-2.6.16-1-686/preinst/failed-to-move-modules-2.6.16-1-686:
  linux-image-2.6.16-1-686/preinst/abort-install-2.6.16-1-686:
  linux-image-2.6.16-1-686/postinst/bootloader-test-error-2.6.16-1-686:


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#404724: linux-image-2.6.16-1-686: can't compile kernel modules, incompatible with gcc 4.1

2006-12-27 Thread Martin Michlmayr
* Mark Whitis [EMAIL PROTECTED] [2006-12-27 15:59]:
 Package: linux-image-2.6.16-1-686
 Version: 2.6.16-12
 
 I just did a dist-upgrade from stable to unstable in the last 24 hours.

2.6.16-12 is not in unstable but 2.6.18-3, which is compiled with gcc
4.1.  I suggest you upgrade to that version.
-- 
Martin Michlmayr
http://www.cyrius.com/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#404724: linux-image-2.6.16-1-686: can't compile kernel modules, incompatible with gcc 4.1

2006-12-27 Thread Mark Whitis



2.6.16-12 is not in unstable but 2.6.18-3, which is compiled with gcc
4.1.  I suggest you upgrade to that version.


Thanks for the quick response.

Unfortunately, apt-get dist-upgrade doesn't know that 2.6.18-3 replaces 
2.6.16-1.   Since I managed to get things working by reverting to gcc 4.0
and upgrading to the newest nvidia driver (see Bug #282183), I might stay 
at 2.6.16 for the time being.



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]