Hi,
Thanks for the tips. Most of the way there, one problem remains [see below].
Andy Smith wrote:
Also "hvc0" in /etc/securetty, but I think
the normal package
upgrade does that.
Yeah, this was there.
And finally make sure udev is installed, but I think
it is on Etch
so should remain there.
It was and still is.
Now the problem I'm having is with configuring the new kernel (this was
the only dpkg issue with the upgrade, not bad). Here's the output:
laney@cripps:~$ sudo dpkg --configure -a
Setting up linux-image-2.6.26-1-xen-686 (2.6.26-13) ...
update-initramfs: Generating /boot/initrd.img-2.6.26-1-xen-686
Searching for GRUB installation directory ... found: /boot/grub
warning: grub-probe can't find drive for /dev/sda1.
grub-probe: error: Cannot find a GRUB drive for /dev/sda1. Check your
device.map.
dpkg: error processing linux-image-2.6.26-1-xen-686 (--configure):
subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of linux-image-2.6-xen-686:
linux-image-2.6-xen-686 depends on linux-image-2.6.26-1-xen-686; however:
Package linux-image-2.6.26-1-xen-686 is not configured yet.
dpkg: error processing linux-image-2.6-xen-686 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-image-xen-686:
linux-image-xen-686 depends on linux-image-2.6.26-1-xen-686; however:
Package linux-image-2.6.26-1-xen-686 is not configured yet.
dpkg: error processing linux-image-xen-686 (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
linux-image-2.6.26-1-xen-686
linux-image-2.6-xen-686
linux-image-xen-686
I tried to create a device.map but it didn't change anything. This looks
a lot like [0], so I guess this is a genuine bug.
Any ideas? I guess I should still be fine with etch's kernel, but I'd
obviously like to have Lenny's one if possible.
Iain
[0]
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=511587