![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=258400 ------- Comment #7 from karl-heinz_tm@hotmail.de 2007-04-23 20:49 MST ------- With a lot more of experience on this machine with OS 10.2 now, I think it is really a machine (bios?) related problem. Whether it boots or not seems to be accidental and happens on all kernels I tried (10.2 original, 10.2 update, and 2.6.21 ... git6 (sorry don't have exact version as I can't be in linux now)). It also appears to be unrelated to the kernel parameters as - now after many many "test boots" - I couldn't find a reliable parameter set for booting any of the kernels, and I did actually occasionally succeed booting all of them *without any (acpi related) kernel parameter*. Strange that earlier I didn't seem to have the problems with 2.6.18.2 - making me believe that the issue was related to the kernel update - but that has changed now that I did a lot of more "booting tests". I guess it's appropriate to not bother any further. The machine is not a common one, I think - and OS 10.2 runs fine on my newer centrino machine :-). One strange thing - maybe that provides some insight that's useful to know in some respect: 2.6.18.x kernel always have their hangs at the places I described earlier. But 2.6.21...git6 produces another error message "unreliable clock source". Just to mention another piece of information - to those who know the evolution from older suse versions - releases before 10.0 didn't show this behaviour. In case it's still of interest after all this, I can still provide the output of dmidecode (just let me know if you want me to). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.