DebianThis forum is for the discussion of Debian Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I am unable to use any text mode console because the following message keeps repeating, disrupting anything on the screen:
printk: 1 messages suppressed.
I suspect it is a kernel issue, since I've been unable to find printk in any Debian package. I use kernel 2.6.9 which I've compiled from the source at kernel.org, and the Debian unstable distribution. Thanks for any help.
to see if it's actually the kernel's fault
try apt-get install kernel-image-2.6.9 or something, and see if you have the same problem, if you don't, you can recompile the kernel into a debian package and install it that way.
if you _are_ using a debian compiled kernel already, then perhaps you have to review your config file.
i tried to compile last week and the compilating was eating A LOT of my disk space that I ran out of memory. but good luck to ya
It is a very strange problem, because I tried switching to my previously compiled kernel, a 2.6.7, and experienced the same problem. In /var/log/kern.log I notice that the message appears alternating with this one:
UDP: short packet: From 196.*.*.*:0 0/25 to 255.255.255.255:0
( numbers replaced with * for isp protection )
i was just sayin that maybe in your custom compile that some options that debian need to run is disabled, so that tryin a debian compiled kernel maybe solve the problem, and if printk appears even with the official debian kernel, then it's a software/config problem, imo
I am not sure how it happened, but all seems to be working fine now. From /var/log/kern.log it appears that it had gone on unnoticed ( or just printed as an error to that file until it started clogging up the screen just recently ). I don't know what could have triggered this; it could have been during the last upgrade when one of the packages, named libreadline-common appeared as 'obsolete' and so I purged it and replaced it with a new 'experimental' package, ( I have since purged that and all programs depending on it ) but the underlying cause would still remain a mystery even if that were the case, unless the problem was with libreadline-common to begin with. Anyway, what finally seemed to correct it was when I put it in hibernation last night; I got an error during the shut-down saying I needed to put 'resume' in lilo.conf instead of 'pmdsk' which it now has. Then this morning it didn't resume and reported 'hda was not cleanly unmounted', but the printk problem is now gone! So the unexpected problem now is with lilo.conf, and why it must now have another configuration instead of the one that appeared to be working fine previously. If I can't figure that one out I'll be posting again. Thanks for your help anyway.