Comments on: Fight with Ubuntu Hardy for a complete night http://www.linuxmonk.org/2008/09/12/fight-with-ubuntu-hardy-for-a-complete-night/ A Journey Towards Infinity... Fri, 16 Jul 2010 19:33:04 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Mambru Angeleri http://www.linuxmonk.org/2008/09/12/fight-with-ubuntu-hardy-for-a-complete-night/comment-page-1/#comment-66 Mambru Angeleri Tue, 30 Dec 2008 16:48:46 +0000 http://linuxmonk.wordpress.com/?p=122#comment-66 At the end I solved the problem in my parents laptop. There is actually little reason to believe it is the same problem you had. The misleading point is that the two kinit messages that you write in your post about mounting the resume image were unrelated to the problem. I played with boot options for a while. I tryed booting with kernel parameters noquiet and verbose=on (I am not sure if they are redundant) to get some extra information. Then I looked at the file /var/log/messages carefully. At some point I found the line "Clocksource tsc unstable (delta = -337913076 ns)". So I used the boot parameter clocksource=acpi_pm and that was the magic solution. So my final solution was to add that parameter to the boot options in grub. As I said before, most likely your problem is different. I can still see those kinit messages during boot time if I press Alt-F1. It seems to be the normal behavior of Ubuntu. Usually we don't see those messages only because we are entertained with the pretty splash screen. At the end I solved the problem in my parents laptop. There is actually little reason to believe it is the same problem you had. The misleading point is that the two kinit messages that you write in your post about mounting the resume image were unrelated to the problem.

I played with boot options for a while. I tryed booting with kernel parameters noquiet and verbose=on (I am not sure if they are redundant) to get some extra information. Then I looked at the file /var/log/messages carefully. At some point I found the line “Clocksource tsc unstable (delta = -337913076 ns)”. So I used the boot parameter clocksource=acpi_pm and that was the magic solution. So my final solution was to add that parameter to the boot options in grub.

As I said before, most likely your problem is different. I can still see those kinit messages during boot time if I press Alt-F1. It seems to be the normal behavior of Ubuntu. Usually we don’t see those messages only because we are entertained with the pretty splash screen.

]]> By: Rosario http://www.linuxmonk.org/2008/09/12/fight-with-ubuntu-hardy-for-a-complete-night/comment-page-1/#comment-65 Rosario Sat, 27 Dec 2008 17:19:28 +0000 http://linuxmonk.wordpress.com/?p=122#comment-65 Yes, the problem for me also started after upgrading the kernel... I think, if u upgrade the kernel alone first and theu booting into the new kernel, upgrade the remaining applications. then there will be no prob i suppose. try Yes, the problem for me also started after upgrading the kernel… I think, if u upgrade the kernel alone first and theu booting into the new kernel, upgrade the remaining applications. then there will be no prob i suppose. try

]]> By: Mambru Angeleri http://www.linuxmonk.org/2008/09/12/fight-with-ubuntu-hardy-for-a-complete-night/comment-page-1/#comment-64 Mambru Angeleri Thu, 25 Dec 2008 18:16:18 +0000 http://linuxmonk.wordpress.com/?p=122#comment-64 I don't have a solution but I have the same problem. It happens in only one of my computers. The old laptop that I gave to my parents. It uses XUbuntu Hardy. The problem started after upgrading from kernel 4.6.22 to 4.6.24. Downgrading to the older kernel is the unhappy fix I could find. I don’t have a solution but I have the same problem. It happens in only one of my computers. The old laptop that I gave to my parents. It uses XUbuntu Hardy. The problem started after upgrading from kernel 4.6.22 to 4.6.24. Downgrading to the older kernel is the unhappy fix I could find.

]]>