|
linux-image-2.6.33-2.dmz.7-liquorix-686 fails to install
Running Debian sid, upgrading to linux-image-2.6.33-2.dmz.7-liquorix-686 fails with the following error messages:
:: Quote :: Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-2.6.33-2.dmz.7-liquorix-686 Processing triggers for python-support ... Errors were encountered while processing: linux-image-2.6.33-2.dmz.7-liquorix-686 linux-image-2.6-liquorix-686 E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up linux-image-2.6.33-2.dmz.7-liquorix-686 (2.6.33-24) ... Running depmod. Running update-initramfs. update-initramfs: Generating /boot/initrd.img-2.6.33-2.dmz.7-liquorix-686 initrd.img(/boot/initrd.img-2.6.33-2.dmz.7-liquorix-686 ) points to /boot/initrd.img-2.6.33-2.dmz.7-liquorix-686 (/boot/initrd.img-2.6.33-2.dmz.7-liquorix-686) -- doing nothing at /var/lib/dpkg/info/linux-image-2.6.33-2.dmz.7-liquorix-686.postinst line 400. vmlinuz(/boot/vmlinuz-2.6.33-2.dmz.7-liquorix-686 ) points to /boot/vmlinuz-2.6.33-2.dmz.7-liquorix-686 (/boot/vmlinuz-2.6.33-2.dmz.7-liquorix-686) -- doing nothing at /var/lib/dpkg/info/linux-image-2.6.33-2.dmz.7-liquorix-686.postinst line 400. Running update-grub. Generating grub.cfg ... No path or device is specified. Try `/usr/sbin/grub-probe --help' for more information. No path or device is specified. Try `/usr/sbin/grub-probe --help' for more information. User postinst hook script [update-grub] exited with value 1 dpkg: error processing linux-image-2.6.33-2.dmz.7-liquorix-686 (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of linux-image-2.6-liquorix-686: linux-image-2.6-liquorix-686 depends on linux-image-2.6.33-2.dmz.7-liquorix-686 (= 2.6.33-24); however: Package linux-image-2.6.33-2.dmz.7-liquorix-686 is not configured yet. dpkg: error processing linux-image-2.6-liquorix-686 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-image-2.6.33-2.dmz.7-liquorix-686 linux-image-2.6-liquorix-686 Reading package lists... Done Building dependency tree Reading state information... Done Reading extended state information... Done Initializing package states... Done Writing extended state information... Done Reading task descriptions... Done Back to top |
|||||
|
your grub 2 is set up incorrectly. that's what the error says, so I assume that's what the error is.
Back to top |
|||||
|
Besides agreeing with techAdmin's observation, is there more from the log of installing this version of the package?
Back to top |
|||||
|
hi
yes I can see grub2 error but before that what about :: Code ::
update-initramfs: Generating /boot/initrd.img-2.6.33-2.dmz.7-liquorix-686 Processing triggers for python-support ... Errors were encountered while processing: linux-image-2.6.33-2.dmz.7-liquorix-686 linux-image-2.6-liquorix-686 E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: try apt-get -f install and did you have any apt errors before attempting to get damentz's kernel pls? Back to top |
|||||
|
I'll have a look at my /etc/default/grub and /etc/grub.d/ files. I changed some things like timeout, and whether a recovery line should be created, but noting else.
I'll try installing a kernel from the repos to see if it works. If it does then the problem would seem to be with the L-kernel, at least, so I would assume. If it does not I will try re-installing grub2. What other logs would you like me to check damentz? Back to top |
|||||
|
The problem is in the update-grub command, please do NOT engage in further actions which can only serve to make matters worse.
When apt gives an error, do NOT then start installing and guessing, the general outcome to that is making the situation worse. Solve the problem then continue. Run the command update-grub see what it says. If it pukes, then fix the cause. Back to top |
|||||
|
Problem was in /etc/grub.d/05_debian_theme
I'd changed background to true, from false. Somehow that caused the problem. Thx for assist, sorry for the false alarm damentz. Back to top |
|||||
|
hi
damn I was wrong again I am leaving the world of grub2. I have now installed Tinycore to hard drive and grub legacy. Boot times are faster than sidux......so far....much faster but I don't have everything loaded as yet. I am sooo embarrassed....slinks away Back to top |
|||||
|
I don't understand why grub2 has so many more problems with it than grub legacy had. Why edit multiple files in grub2 than just edit one file in grub legacy?
Perhaps people should be opening more bug reports for grub2 so they get fixed. if grub2 is supposed to be better than grub legacy, then it should be less of an aggravation to configure. Back to top |
|||||
|
Because grub2 was designed and implemented without any consideration for normal human end users, by someone or someones clearly too far lost in the technical side of things to be able to make decent usability decisions for the end user. So you end up with arcane configuration syntaxes, an updating method that is harder to use than grub 1 (hint, when you 'improve' software, it should be EASIER to use, not harder), and which is as of now still incomplete, for example, it's hard and may require config patches to use disk labels in grub 2.
Back to top |
|||||
|
All times are GMT - 8 Hours
|
|||||