On Fri, Oct 21, 2011 at 01:17:20AM +0300, Touko Korpela wrote: > On Thu, Oct 20, 2011 at 10:08:53PM +0100, Miguel Figueiredo wrote: > > Hi, > > > > There were several pre-dependency problems but in the end it seems the disk > > is > > filled up and prevents the kernel to be installed: > > > > Oct 20 10:01:02 in-target: dpkg: error processing > > /media/cdrom//pool/main/l/linux-2.6/linux-image-3.0.0-1- > > amd64_3.0.0-3_amd64.deb (--unpack): > > Oct 20 10:01:02 in-target: unable to install new version of > > `/lib/modules/3.0.0-1-amd64/kernel/drivers/scsi/advansys.ko': No space left > > on > > device > > Oct 20 10:01:02 in-target: configured to not write apport reports > > Oct 20 10:01:03 in-target: Examining /etc/kernel/postrm.d . > > Oct 20 10:01:03 in-target: run-parts: executing > > /etc/kernel/postrm.d/initramfs-tools 3.0.0-1-amd64 > > /boot/vmlinuz-3.0.0-1-amd64 > > Oct 20 10:01:03 in-target: Processing triggers for man-db ... > > Oct 20 10:01:04 in-target: Errors were encountered while processing: > > Oct 20 10:01:04 in-target: /media/cdrom//pool/main/l/linux-2.6/linux- > > image-3.0.0-1-amd64_3.0.0-3_amd64.deb > > Oct 20 10:01:04 in-target: E: Sub-process /usr/bin/dpkg returned an error > > code > > (1) > > Oct 20 10:01:04 base-installer: error: exiting on error base- > > installer/kernel/failed-install > > Target /boot was 290MB and root was 6GB . I'm quite sure that they didn't get > full > during base system install. Stable 3.0.x kernel releases have some btrfs > fixes, that aren't included in installer kernel (3.0.0-1 is quite old > release). Or maybe it's not btrfs related, but more testing is needed.
New install from same media completed fine when I used just ext4 filesystems. But it has bad screen corruption problem (I opened new bugreport for it). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org