Siduction Forum
Siduction Forum => Upgrade Warnings => Topic started by: hypper on 2014/04/22, 10:43:32
-
hi all,
after today's d-u, which went through without errors (although there were conflicts in some tex-packages) the system hangs on "Booting the Kernel." The kernel version is 3.14-1.towo-siduction-amd64. no errors are logged in kern.log, boot and messages.
using an older kernel 3.13-5.towo.2-siduction-amd64 the systems boots as usual.
any suggestions?
cheers,
mathias
-
I do not encounter anything like that (kde, 64-bit) and I have not heard anything the like so far. I would remove kernel and headers and install them anew.
greetz
devil
-
after purging and re-installing the kernel and headers the problem still occurs.
but now i found some logs in messages regarding os-prober.
i attached the last lines of messages after booting the new kernel => reset pc => booting the old kernel which works again.
-
I do not encounter anything like that (kde, 64-bit)
+1
-
I do not encounter anything like that (kde, 64-bit)
+1
It could be an aging hardware issue -- eventually kernel support for ancient bits of hardware gets dropped. So, could we please see the output of
inxi -v7
Another thought -- I think (but am not certain) that os-prober is called to write a grub menu entry for a new kernel -- suggesting (again) that the kernel installation is not completing correctly for some reason -- possibly a review of the grub menu file would reveal something -- compare the location information and partition UUID of the correctly booting kernel to the same items for the one that won't boot.
-
enclosed the output of inxi (without network addresses) and my grub.cfg.
i purged the kernel 3.14-1.towo-siduction-amd64 again and i encountered
"The link /vmlinuz.old is a damaged link"
...
"The link /initrd.img.old is a damaged link"
...
You may need to re-run your boot loader
i did a update-grub and re-install of the kernel without any errors but same behavior, no booting of the kernel. i also tried the kernel 3.14-0.towo.4-siduction-amd64, same problems.
maybe it is really something wrong with grub.
-
It looks like we do not need to worry about old hardware -- nice box! ;D
You have an unmounted partition. Was that partition unmounted when you installed siduction and the working kernel?
You might try
apt-get install --reinstall grub-pc
-
Hello hypper,
your grub.cfg doesn't contain the link "/vmlinuz.old".
Is a second Linux with another grub install involved?
greetings
musca
-
@dibl:
the unmounted partition is the windows 7 installation and was definitely unmounted when i installed the last 3 kernel, including the working one. i cannot recall what the siduction-installer did during first installation, probably all partitions were mounted after formatting them. after that i installed the win7.
i tried
apt-get install --reinstall grub-pc
but no working 3.14-1 kernel.
during installation of grub-pc i got:
Installing for i386-pc platform.
i guess its correct even though i have a 64bit machine.
@musca:
no other linux is involved. i just have a second partition called linux2 for a planned second installation. but so far not.
actually my previous post looks like
"The link /vmlinuz.old is a damaged link"
Removing symbolic link /vmlinuz.old
"The link /initrd.img.old is a damaged link"
Removing symbolic link /initrd.img.old
You may need to re-run your boot loader
so, no surprise that you cannot find those links in grub.cfg. sorry for the sloppiness.
-
Deleted post --- wrong information.
-
It must have something to do with those symbolic links, which appear under "/". Here is what I see -- I am booted in 3.14-1, and the previous kernel on this system was 3.14-0.towo.4.
.
.
.
lrwxrwxrwx 1 root root 40 Apr 15 06:52 vmlinuz -> boot/vmlinuz-3.14-1.towo-siduction-amd64
lrwxrwxrwx 1 root root 42 Apr 12 07:49 vmlinuz.old -> boot/vmlinuz-3.14-0.towo.4-siduction-amd64
.
.
.
You might take a look under "/" and see if your links make sense, after removing the 3.14-1 kernel and then again after reinstalling it.
-
after purging kernel 3.14-1 with
apt-get purge linux-image-3.14-1.towo-siduction-amd64 linux-headers-3.14-1.towo-siduction-amd64there are no symbolic links in "/" at all.
after re-install with
apt-get install linux-headers-siduction-amd64 linux-image-siduction-amd64
only
lrwxrwxrwx 1 root root 44 Apr 23 16:33 initrd.img -> /boot/initrd.img-3.14-1.towo-siduction-amd64
lrwxrwxrwx 1 root root 40 Apr 23 16:33 vmlinuz -> boot/vmlinuz-3.14-1.towo-siduction-amd64
are present. there are no *.old ones present even after an additional update-grub.
are those links needed at all? i mean in grub.cfg the full path /boot/vmlinuz-... is used.
but were does the "/" comes from in front of boot
lrwxrwxrwx 1 root root 44 Apr 23 16:33 initrd.img -> /boot/initrd.img-3.14-1.towo-siduction-amd64
is this correct, because there is no "/" pointing to boot/vmlinuz-...?
-
If these links are in the root directory then both are pointing to the same, right location.
-
with some understanding of very basic linux commands and grub concepts one can make some useful things with these links:
cp /etc/grub.d/40_custom /etc/grub.d/09_my_own_entry
after that one can place his prefered own things into this new file like this:
#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
menuentry 'My System - current kernel' {
load_video
insmod gzio
insmod part_gpt
insmod ext2
echo "current kernel with my static options:"
linux /vmlinuz root=/dev/sdc2 ro quiet ipv6.disable=1 nolapic_timer elevator=deadline
initrd /initrd.img
}
menuentry 'My System - old kernel' {
load_video
insmod gzio
insmod part_gpt
insmod ext2
echo "old kernel with my static options:"
linux /vmlinuz.old root=/dev/sdc2 ro quiet ipv6.disable=1 nolapic_timer elevator=deadline
initrd /initrd.img.old
}
if the kernel change, the first entry will work with the new kernel, the second with the now obsolated - and this will be in the future too with no need to change anything again. if the system don't work with the new kernel, just boot the old one.
if something fucked up this links, simply relink to te needed vmlinuz and initrd.
lrwxrwxrwx 1 root root 44 Apr 15 18:11 initrd.img -> /boot/initrd.img-3.14-1.towo-siduction-amd64
lrwxrwxrwx 1 root root 46 Apr 13 01:42 initrd.img.old -> /boot/initrd.img-3.14-0.towo.4-siduction-amd64
lrwxrwxrwx 1 root root 40 Apr 15 18:11 vmlinuz -> boot/vmlinuz-3.14-1.towo-siduction-amd64
lrwxrwxrwx 1 root root 42 Apr 13 01:42 vmlinuz.old -> boot/vmlinuz-3.14-0.towo.4-siduction-amd64
Normally apt-get should do that for you.
-
melmarker:
thanks for the introduction.
in the meanwhile i tested other kernels:
the last working kernel for me is 3.13-7.towo-siduction-amd64
it seems that the problems start with 3.14-0.towo.2-siduction-amd64
-
Please boot the kernel without quiet bootcheat.
-
towo:
also without quiet bootcheat no booting.
-
Without quiet you should get a more verbose output on your konsole.
Maybe we can see there, what's the problem on your pc.
-
do you need something special?
-
Maybe errors, failings before the stop?
I do not seat at your pc, so i cannot see, what's on your screen.
-
ah, i thought in the log-files.
at boot there are no additional messages on the screen. it hangs at "Booting the kernel." and a blinking cursor
-
i found something in the net, but i don't know if this can be the reason for the non-booting kernel in my case?
https://bugzilla.kernel.org/show_bug.cgi?id=74131
some users of arch-linux have similar problems and they could be fixed with an bios-update.
https://bugs.archlinux.org/task/39811
i am using a Gigabyte B85M-D3H mobo.
-
It seems, you affected by this bug.
If i find time at weekend, i will upload a patched kernel.
-
that would be great.
many thanks in advance.
-
I have uploaded a new kernel with the patch from the bugreport, please test.
-
Thanks a lot.
I can test it on monday at the earliest. Its my pc at work.
-
i installed the new (patched) kernel 3.14-1.towo.2-siduction-amd64 and it booted without any errors so far.
thanks towo and all the others who contributed to this topic and special problem.
i mark this topic as solved.