Kai, I have attached a patch which I had used to overcome similar problem in kernel version 2.6.19 from GIT. This patch will not directly apply on the latest kernel, but you can manually do the modifications by going through the patch. Check whether this solves your problem.
Regards, Sudhakar -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kai Fischer Sent: Monday, June 16, 2008 8:57 PM To: [email protected] Subject: Re: Problem with serial console Hi, Unfortunately this did not fix the problem. I investigated it a little further by sending some text to /dev/console from my remote shell: cat /proc/interrupts | grep serial 40: 36 AINTC serial echo hello > /dev/console cat /proc/interrupts | grep serial 40: 36 AINTC serial Nothing happens on the console, which is pretty obvious, since no serial interrupt occured after the echo command. But pressing the enter key on the serial console somehow triggers the interrupt and "hello" finally shows up there. Another cat /proc/interrupts gives 40: 41 AINTC serial I am afraid that further investigation will mean to debug the kernel. Any other suggestions? Best regards, Kai > -----Ursprüngliche Nachricht----- > Von: Andrew Goeldner [mailto:[EMAIL PROTECTED] > Gesendet: Montag, 16. Juni 2008 12:25 > An: Kai Fischer > Cc: [email protected] > Betreff: Re: Problem with serial console > > I had a similar problem, to fix it I had to mknod a console. > This had to be done as part of the boot as I could not log on! > Apologies if my terminology is not quite right - I am new to > this, but here goes > > in /etc/inittab, I already had the lines > > ======================================= > # This line provides a nice out-of-box experience. For > regular use, you # should replace it with the proper getty > lines below. > con:2345:respawn:/sbin/getty console > ======================================= > > > I added the following lines in > /etc/rc.d/init.d/rcS > ==================== > mknod /dev/console c 4 64 > mknod /dev/ttySER c 4 64 > chmod 666 /dev/console > chmod 666 /dev/ttySER > ===================== > > This allowed the console to run, and afterwards I could > delete the lines added to rcS. You should be able to do this over ssh. > > I am not sure if this release has changed something about > device nodes - I am still having some problems with mounting > compact flash drives over the USB which (nearly) worked > before which I suspect is a similar issue. > > Hope this helps, > Andrew Goeldner. > > On Fri, 2008-06-13 at 17:25 +0200, Kai Fischer wrote: > > > Hi, > > I have a very strange problem with my serial console > since I updated > from git tag "2.6.25-davinci1" to the most current master tree: > > During the early boot process, when the kernel sends > messages to the > console, everything works fine. But then, after the > init process is > started, the boot messages appear only after pressing > the return key. It > is also impossible to login on the serial console > because of this > behaviour (but I can do remote logins). > > Switching back to an old kernel version > (2.6.25-davinci1) solves this > problem instantly without touching the root filesystem > (Debian lenny - > armel). > > I already searched the git log for any clues, but did > not find anything > suspect. But maybe someone else has an idea about this... > > Many thanks in advance! > > Best regards, > Kai > _______________________________________________ > Davinci-linux-open-source mailing list > [email protected] > > http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source > > _______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
8250.patch
Description: 8250.patch
_______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
