From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lee Revell Subject: Re: Print for tracing bugs Date: Tue, 24 Jan 2006 16:26:32 -0500 Message-ID: <1138137993.2771.133.camel@mindpipe> References: <200601231442.52366.gineera@aspect135.co.uk> <1138034480.1354.30.camel@mindpipe> <200601242129.25181.gineera@aspect135.co.uk> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <200601242129.25181.gineera@aspect135.co.uk> Sender: alsa-devel-admin@lists.sourceforge.net Errors-To: alsa-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Alan Horstmann Cc: Takashi Iwai , alsa-devel@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org On Tue, 2006-01-24 at 21:29 +0000, Alan Horstmann wrote: > On Monday 23 January 2006 16:41, you wrote: > > Yes just add printk()'s to the driver code. > > > Thanks. I can get these to print to var/log/messsages, but how do I get them > to come immediately to a konsole? No idea, that's a KDE issue. Most GUI terminals don't print out the kernel messages. Try a text console. Lee ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642