Weird situation, looking for feedback.
Posted: 2019-11-04 08:44
The situation, have an old Dell 1545 laptop and the thing is still running great even if it's dated 10 or so years now. However encountered a really odd situation, when am booted into a 64bit install ( I have both Stretch 64bit with a custom rolled vanilla kernel) and now a Buster 64b with stock kernel and also went ahead and installed the same custom one onto it. When booted into these babies, I get some odd clicking sound. Repeats every couple secs. The hard drive is an ancient thing, 250gb Western Digital black, 7200 rpm affair.
Not really expecting it to live all that much longer anyway. Not 100% it's originating from the hdd either, though at a loss as to what else it could be. Here's the rub, when booted into 32bit-Stretch, nope ... no clicking. So this leaves me scratching my head, is it only when the thing is booted with the cpu in 64bit Op-mode ? Is it strictly later kernel's responsible and maybe should play around with some older one's on the Buster install ? Yep ... that's the plan, the 32b/Stretch has a custom rolled 4.13 version kernel on it, shrugs. At this point not really sure what else to dork with other than trying old version kernels. Just got done getting this 64bit Buster about where I want it from a minimal netinstall + standard system tools. The idea of having to bother repeating the process with a 32bit netinstall iso or trying to convert the sucker to 32bit via multiarch makes me want to swallow my tongue.
Has anyone seen this type of thing before or have any worthwhile insights/comments, thanks in advance. All of these are pretty much clones, all the same, config'ed and setup to my preferences and confuzzled by this situation.
PS, Also o course going to have to compare output of lsmod I guess. Weird though that Debian would drop any relevant modules/drivers 64bit or not for this old thing. Would think it'd be right up Debian stable's alley !!!
Not really expecting it to live all that much longer anyway. Not 100% it's originating from the hdd either, though at a loss as to what else it could be. Here's the rub, when booted into 32bit-Stretch, nope ... no clicking. So this leaves me scratching my head, is it only when the thing is booted with the cpu in 64bit Op-mode ? Is it strictly later kernel's responsible and maybe should play around with some older one's on the Buster install ? Yep ... that's the plan, the 32b/Stretch has a custom rolled 4.13 version kernel on it, shrugs. At this point not really sure what else to dork with other than trying old version kernels. Just got done getting this 64bit Buster about where I want it from a minimal netinstall + standard system tools. The idea of having to bother repeating the process with a 32bit netinstall iso or trying to convert the sucker to 32bit via multiarch makes me want to swallow my tongue.
Has anyone seen this type of thing before or have any worthwhile insights/comments, thanks in advance. All of these are pretty much clones, all the same, config'ed and setup to my preferences and confuzzled by this situation.
PS, Also o course going to have to compare output of lsmod I guess. Weird though that Debian would drop any relevant modules/drivers 64bit or not for this old thing. Would think it'd be right up Debian stable's alley !!!