as of yesterday, every time I try to apt-get upgrade I get the following errors pertaining to firmware-linux-free and initramfs-tools:
crunchbang@crunchbang:~$ sudo apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 2 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue [Y/n]? y Setting up firmware-linux-free (3.2) ... update-initramfs: deferring update (trigger activated) ls: cannot access initrd.img-*: No such file or directory cp: cannot create regular file `/live/image/live/vmlinuz.new': No such file or directory dpkg: error processing firmware-linux-free (--configure): subprocess installed post-installation script returned error exit status 1 Setting up initramfs-tools (0.109) ... update-initramfs: deferring update (trigger activated) ls: cannot access initrd.img-*: No such file or directory cp: cannot create regular file `/live/image/live/vmlinuz.new': No such file or directory dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: firmware-linux-free initramfs-tools E: Sub-process /usr/bin/dpkg returned an error code (1)
The only change in the last days has been me uninstalling bluetooth (already disabled in rcconf) and some packages related to that and gigolo.
Not sure if it makes a difference, but I'm running Waldorf off a persistent USB with a persistence partition (as opposed to a max. 4GB persistence file).
Any help in figuring this out is greatly appreciated.
Last edited by atiroch (2013-02-24 21:15:22)
Last edited by sorcerer's_apprentice (2013-02-24 07:44:18)
Did you 'apt-get update' before 'apt-get upgrade'.
@fatmac Yes I did, update works fine.
@sorcerer's_apprentice I've actually rebooted and shut down a few times and it works. But what you're saying is entirely possible. However, from my limited understanding, all changes and updates go into my presistence partition, and the original live image doesn't get touched, so it might skip the broken kernel and fall back on the live one with some restrictions (I have no idea if that's possible or not, but it does boot up and everything installed so far works without a hitch).
I'll back up my config files a bit later and try smxi-scripts like you said. Worst case scenario I can boot into the live image, format my persistence partition and start from scratch. Thanks for the tip.
So I decided to just wipe the persistence partition and start fresh and it sort of, kind of works now. I still get errors related to initramfs-tools and firmware-linux-free but I can update, install and purge packages now, which is good enough. I'll try smxi in a few days when I don't need my laptop to be necessarily functional.
But as long as it works for now. Would be interesting to see if a new kernel will fix that.
Well, I decided I have too much time on my hands and tried smxi, but it won't work since my /home is on the persistence partition and grub is on the other one and I can't mount the live partition for some reason (says: Error when getting information for file '/live/rofs/filesystem.squashfs': No such file or directory). I guess if it ain't broke anymore, I won't bother that much to fix it. Thanks for the tip anyway.