Apologies for sounding paranoid, but I need to get back to work on my thesis, so I want to do this right, but am encountering problems, about which I'd appreciate advice:
squeezy wrote:add the wheezy main source to your sources.list file and upgrade the [kernel image and header packages], then disable wheezy. Don't upgrade anything else.
My problem is that, after updating my current {UP4, non-wheezy} setup, then doing
Code: Select all
me@it:~$ diff -wB /etc/apt/sources.list~ /etc/apt/sources.list
20c20
< #deb http://ftp.debian.org/debian/ testing main contrib non-free
---
> deb http://ftp.debian.org/debian/ testing main contrib non-free
me@it:~$ sudo aptitude update
...
> Current status: 1405 updates [+1405], 38825 new [+3229].
...
me@it:~$ sudo aptitude install linux-headers-3.2.0-3-amd64 linux-image-3.2.0-3-amd64
I got the response
Code: Select all
> The following NEW packages will be installed:
> linux-headers-3.2.0-3-amd64 linux-headers-3.2.0-3-common{a} linux-image-3.2.0-3-amd64
> 0 packages upgraded, 3 newly installed, 0 to remove and 1405 not upgraded.
...
> Setting up linux-image-3.2.0-3-amd64 (3.2.21-3) ...
> Running depmod.
> Examining /etc/kernel/postinst.d.
> run-parts: executing /etc/kernel/postinst.d/dkms 3.2.0-3-amd64 /boot/vmlinuz-3.2.0-3-amd64
> dkms.conf: Error! No 'BUILT_MODULE_NAME' directive specified for record #0.
> Error! Bad conf file.
> File:
> does not represent a valid dkms.conf file.
and again, later in same install:
Code: Select all
> Setting up linux-headers-3.2.0-3-common (3.2.21-3) ...
> Setting up linux-headers-3.2.0-3-amd64 (3.2.21-3) ...
> Examining /etc/kernel/header_postinst.d.
> run-parts: executing /etc/kernel/header_postinst.d/dkms 3.2.0-3-amd64
> dkms.conf: Error! No 'BUILT_MODULE_NAME' directive specified for record #0.
> Error! Bad conf file.
> File:
> does not represent a valid dkms.conf file.
My initial response was to do
Code: Select all
me@it:~$ sudo aptitude remove linux-headers-3.2.0-3-amd64 linux-headers-3.2.0-3-common linux-image-3.2.0-3-amd64
which ended with
Code: Select all
> The link /vmlinuz is a damaged link
> Removing symbolic link vmlinuz
> You may need to re-run your boot loader
> The link /initrd.img is a damaged link
> Removing symbolic link initrd.img
> You may need to re-run your boot loader
The symlink error is apparently a harmless legacy of
lilo: see
this serverfault question and
this debian-boot thread. (I hope it's harmless--I'll find out for sure on next reboot :-)
This thread recommends doing something like
Code: Select all
$ sudo aptitude remove live-initramfs
and also
Code: Select all
$ sudo aptitude remove nvidia-kernel-dkms nvidia-glx
$ sudo aptitude install nvidia-kernel-dkms nvidia-glx
But my error doesn't seem to involve live-initramfs, and I don't seem to have that anyway:
Code: Select all
me@it:~$ sudo aptitude search ~Dlive-initramfs | grep -e '^i' | wc -l
0
Similarly, my error doesn't seem to involve nvidia packages, and I don't seem to have them anyway:
Code: Select all
me@it:~$ sudo aptitude search ~Dnvidia | grep -e '^i' | wc -l
0
(However, after updating
inxi, I see
Code: Select all
me@it:~$ inxi -G
Graphics: Card: nVidia G98M [GeForce G 105M]
X.Org: 1.11.4 drivers: nouveau (unloaded: vesa,fbdev) Resolution: 1280x800@60.0hz
GLX Renderer: Gallium 0.4 on NV98 GLX Version: 2.1 Mesa 7.11.2
so perhaps I should have the nvidia packages?)
Anyway, assistance in resolving the dkms.conf error is appreciated!