On 10/01/2014 10:46 AM, Helge Deller wrote:
> Hi Peter,
>
>>> Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
>>> serial8250: ttyS0 at I/O 0x3f8 (irq = 3, base_baud = 115200) is a 16550A
>>>
>>> The source code for this driver is in drivers/parisc/superio.c,
>>> see e.g. function superio_s
Hi Peter,
> > Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
> > serial8250: ttyS0 at I/O 0x3f8 (irq = 3, base_baud = 115200) is a 16550A
> >
> > The source code for this driver is in drivers/parisc/superio.c,
> > see e.g. function superio_serial_init().
> > Maybe something is missing in
On 09/24/2014 02:48 PM, Helge Deller wrote:
> Hi Peter,
>
> On 09/23/2014 11:08 PM, Peter Hurley wrote:
>> On 09/23/2014 04:11 PM, Helge Deller wrote:
>>> During the release cycle of v3.17 I've seen sometimes a broken serial
>>> console output
>>> on the parisc platform. Interestingly all kernel
Hi Peter,
On 09/23/2014 11:08 PM, Peter Hurley wrote:
On 09/23/2014 04:11 PM, Helge Deller wrote:
During the release cycle of v3.17 I've seen sometimes a broken serial console
output
on the parisc platform. Interestingly all kernel messages printed by the kernel
via printk() show
up correctly
Hi Helge,
On 09/23/2014 04:11 PM, Helge Deller wrote:
> During the release cycle of v3.17 I've seen sometimes a broken serial console
> output
> on the parisc platform. Interestingly all kernel messages printed by the
> kernel via printk() show
> up correctly, but output from userspace (e.g. by
When resuming from S3 suspend, serial console starts sending garbage
on the serial port.
Not continuously, it sends garbage only when in local console prints a
text.
It stops only when the (sending) machine is shut down, or if some
text is sent manually (i.e. with "cat txtfile > /dev/ttyS0").
Ful
Hi Waldemar,
On Tue, May 20, 2014 at 10:21 AM, Waldemar Brodkorb wrote:
> Geert Uytterhoeven wrote,
>> On Fri, May 16, 2014 at 3:49 PM, Waldemar Brodkorb wrote:
>> > I am trying to bootup my Mikrotik RB532 board with the latest
>> > kernel, but my serial console is disabled after boot:
>> > ..
>
Hi Geert,
Geert Uytterhoeven wrote,
> Hi Waldemar,
>
> On Fri, May 16, 2014 at 3:49 PM, Waldemar Brodkorb wrote:
> > I am trying to bootup my Mikrotik RB532 board with the latest
> > kernel, but my serial console is disabled after boot:
> > ..
> > Serial: 8250/16550 driver, 4 ports, IRQ sharing
Hi Waldemar,
On Fri, May 16, 2014 at 3:49 PM, Waldemar Brodkorb wrote:
> I am trying to bootup my Mikrotik RB532 board with the latest
> kernel, but my serial console is disabled after boot:
> ..
> Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
> serial8250: ttyS0 at MMIO 0x0 (irq = 104
"Valerio Vanni" ha scritto nel messaggio
news:lg9etc$9fl$1...@ger.gmane.org
When resuming from S3 suspend, serial console starts sending garbage
on the serial port.
Not continuously, it sends garbage only when in local console prints a
text.
It stops only when the (sending) machine is shut down,
>>>i was wondering how to make kernel messages appear on /dev/ttyS0
>>without a reboot, i.e. kernelparam "console=ttyS0"
>>
>>The solution is simple... the following piece of code is inside
>>opensuse-10.3/src/sysvinit-2.86-115.src.rpm#showconsole-1.08.tar.bz2#showconsole-1.08/blogd.c
>>
>>(voi
In article <[EMAIL PROTECTED]>,
Jan Engelhardt <[EMAIL PROTECTED]> wrote:
>
>On Jan 3 2008 13:43, [EMAIL PROTECTED] wrote:
>>
>>hi !
>>
>>i was wondering how to make kernel messages appear on /dev/ttyS0
>without a reboot, i.e. kernelparam "console=ttyS0"
>
>The solution is simple... the following
> This errno is so out of place.
yes, that was stupid.
anyway:
# strace ./mytiocons
--snipp--
open("/dev/ttyS0", O_RDWR) = 3
ioctl(0, TIOCCONS) = -1 EBUSY (Device or resource busy)
ioctl(3, TIOCCONS) = -1 EBUSY (Device or resource busy)
--sni
On Jan 3 2008 15:39, [EMAIL PROTECTED] wrote:
>fantastic, thanks!
>
>unfortunately..
>
>opensuse103:/home/roland/serialcons # ./mytioccons
>ioctl: Device or resource busy
>
>but i`m not deep enough into programming to understand this.
>
>int main(void)
>{
>int fd = open("/dev/ttyS0", O_RDWR);
; Gesendet: 03.01.08 14:28:45
> An: [EMAIL PROTECTED]
> CC: linux-kernel@vger.kernel.org
> Betreff: Re: serial console _after_ boot ? - was: Redirect kernel console
>
>
> On Jan 3 2008 13:43, [EMAIL PROTECTED] wrote:
> >
> >hi !
> >
> >i was wonde
On Jan 3 2008 13:43, [EMAIL PROTECTED] wrote:
>
>hi !
>
>i was wondering how to make kernel messages appear on /dev/ttyS0 without a
>reboot, i.e. kernelparam "console=ttyS0"
The solution is simple... the following piece of code is inside
opensuse-10.3/src/sysvinit-2.86-115.src.rpm#showconsole-1.
change the console to which
kernel messages are printed. However, is it possible to redirect to ttyS0
without a reboot?
Jan Engelhardt
---
>> Subject: Re: serial console _after_ boot ?
>> > Setterm outputs the correct escape sequences to stdout. You can
>> > c
Christoph> On Wed, 25 Apr 2007, John Stoffel wrote:
>> Ok, no idea then. It's working for me in 2.6.21-rc7 as long as I
>> don't have more than one console= entry in my kernel boot args.
Christoph> 2.6.21-rc7 is working fine here too. mm is the problem.
Ah ok. My issue must be something else
On Wed, 25 Apr 2007, John Stoffel wrote:
> Ok, no idea then. It's working for me in 2.6.21-rc7 as long as I
> don't have more than one console= entry in my kernel boot args.
2.6.21-rc7 is working fine here too. mm is the problem.
-
To unsubscribe from this list: send the line "unsubscribe linu
> "Christoph" == Christoph Lameter <[EMAIL PROTECTED]> writes:
Christoph> On Wed, 25 Apr 2007, John Stoffel wrote:
Christoph> I use a serial console on my x86_84 box. For a while now I
Christoph> can see all output but I cannot type any
Christoph> characters. /dev/console broke?
>>
>> I've so
On Wed, 25 Apr 2007, John Stoffel wrote:
> Christoph> I use a serial console on my x86_84 box. For a while now I
> Christoph> can see all output but I cannot type any
> Christoph> characters. /dev/console broke?
>
> I've sorta seen this problem too, but with gdm. If I have my kernel
> line setup
Christoph> On Tue, 24 Apr 2007, Andrew Morton wrote:
>> > Nothing special apart from
>> > the usual problem with serial not accepting characters that we had for
>> > awhile now.
>>
>> I wasn't aware of that one.
Christoph> I use a serial console on my x86_84 box. For a while now I
Christoph> c
On Wed, Feb 14, 2007 at 05:39:22PM -0700, [EMAIL PROTECTED] wrote:
> Well, this is the most bastardized sucker I've ever seen. . . I have had
> no end of trouble with it (couldn't even get a boot loader to work with
> it - had to write my own). And, as luck would have it, the serial port
> is no d
> > In a previous post I incorrectly stated that my serial port is a
> > TI16750, as this is what /proc/tty/... revealed to me. After
> > re-reading the product manual, I see that this is actually a 16550.
> > Since Linux is seeing this port as a 16750, could that explain why I'm
> > seeing missin
On Wed, 14 Feb 2007 16:11:14 -0700
[EMAIL PROTECTED] wrote:
> In a previous post I incorrectly stated that my serial port is a
> TI16750, as this is what /proc/tty/... revealed to me. After
> re-reading the product manual, I see that this is actually a 16550.
> Since Linux is seeing this port as
In a previous post I incorrectly stated that my serial port is a
TI16750, as this is what /proc/tty/... revealed to me. After
re-reading the product manual, I see that this is actually a 16550.
Since Linux is seeing this port as a 16750, could that explain why I'm
seeing missing characters in the
David Lang wrote:
On Mon, 12 Feb 2007, Andy Kennedy wrote:
For those of you who are on BusyBox's mailing list, you've already
seen this -- I was sent here for help.
Specs:
Linux: 2.6.18
Bootloader: SysLinux
Init: BusyBox (ver 1.4.0) init.
Kernel command line: console=ttyS0,115200,n,8,1
S
On Mon, 12 Feb 2007, Andy Kennedy wrote:
For those of you who are on BusyBox's mailing list, you've already seen this
-- I was sent here for help.
Specs:
Linux: 2.6.18
Bootloader: SysLinux
Init: BusyBox (ver 1.4.0) init.
Kernel command line: console=ttyS0,115200,n,8,1
System: VersaLogic 5
In article <[EMAIL PROTECTED]>,
Narayan Desai <[EMAIL PROTECTED]> wrote:
>> "Mike" == Miquel van Smoorenburg <[EMAIL PROTECTED]> writes:
>
>Mike> In article <[EMAIL PROTECTED]>,
>Mike> Narayan Desai <[EMAIL PROTECTED]> wrote:
>>> Hi. I have started having serial console problems in the last bu
> "Mike" == Miquel van Smoorenburg <[EMAIL PROTECTED]> writes:
Mike> In article <[EMAIL PROTECTED]>,
Mike> Narayan Desai <[EMAIL PROTECTED]> wrote:
>> Hi. I have started having serial console problems in the last bunch
>> of kernel releases. I have tried various 2.4.4 and 2.4.5 ac kernels
>>
In article <[EMAIL PROTECTED]>,
Narayan Desai <[EMAIL PROTECTED]> wrote:
>Hi. I have started having serial console problems in the last bunch of
>kernel releases. I have tried various 2.4.4 and 2.4.5 ac kernels (up
>to and including 2.4.5-ac4) and the problem has persisted. The problem
>is basical
This is not a real patch but it works fine for me:
--- drivers/char/serial.c.orig Thu May 3 09:29:00 2001
+++ drivers/char/serial.c Thu May 3 09:29:34 2001
@@ -1764,8 +1764,8 @@
/*
* !!! ignore all characters if CREAD is not set
*/
- if ((cflag & CREAD) ==
On 03 May 2001 02:15:03 -0600
[EMAIL PROTECTED] (Eric W. Biederman) wrote:
>
> I get the impression that something in 2.4.3 fixed CREAD handling, and we
> started noticing the buggy user space.
That's my impression too...
> > > I wish I knew where the breakage actually occured.
> >
> > Just
Fabrice Gautier <[EMAIL PROTECTED]> writes:
> On 02 May 2001 10:37:21 -0600
> [EMAIL PROTECTED] (Eric W. Biederman) wrote:
>
> > Fabrice Gautier <[EMAIL PROTECTED]> writes:
> > > So this this probably a sulogin/mingetty problem. They should set the
> > > CREAD flag in your tty c_cflag.
> > >
>
On 02 May 2001 10:37:21 -0600
[EMAIL PROTECTED] (Eric W. Biederman) wrote:
> Fabrice Gautier <[EMAIL PROTECTED]> writes:
> > So this this probably a sulogin/mingetty problem. They should set the
> > CREAD flag in your tty c_cflag.
> >
> > the patch for busybox repalced the line
> > tty.c_cf
Fabrice Gautier <[EMAIL PROTECTED]> writes:
> On Wed, 02 May 2001 11:54:11 +0200
> Reto Baettig <[EMAIL PROTECTED]> wrote:
>
> > Hi
> >
> > I just installed 2.4.4 on our alpha SMP boxes (ES40) and now I have
> > problems with the serial console:
>
> I get same kind of problem when upgrading fr
On Wed, 02 May 2001 11:54:11 +0200
Reto Baettig <[EMAIL PROTECTED]> wrote:
> Hi
>
> I just installed 2.4.4 on our alpha SMP boxes (ES40) and now I have
> problems with the serial console:
I get same kind of problem when upgrading from 2.4.2 to 2.4.3 and using
busybox as init/getty
The proble
Apparently "Green" <[EMAIL PROTECTED]> wrote:
> Hi all,
> I want to login to my MIPS box through serial port.
> I execute 'make menuconfig' and select the 'serial console'.
> But I can't see the login prompt in my window(I use netterm).
> May I ask how serial console work?
> Or I forget som
Hi,
Steve Hill wrote:
> I'm building boxes with the console set to /dev/ttyS0. However, I can't
> guarantee that there will always be a term plugged into the serial
> port. If there is no term on the port, eventually the buffer fills and
> any processes that write to the console (i.e. init) bl
Yes it could be a modem on the line, so my comment about DCD is wrong, a comms
program must be able to send AT commands to the modem when DCD is not asserted
before the call is setup. I was being confused by the login getty which we run
on the same serial port. This drops back to the login promp
In article <[EMAIL PROTECTED]>,
Rogier Wolff <[EMAIL PROTECTED]> wrote:
>Paul Jakma wrote:
>> perhaps linux-mips is just different? or i386 serial-console is
>> incorrect?
>
>No. serial console on i386 doesn't and should not block.
>We're constantly using serial consoles here, so I really think I
See, in an ideal world, that shouldn't be the case, at all.
Since we're NOT operating under the assumption that the serial console is
a modem, we should be - instead - operating under the assumption
that it is a 3-wire NULL connection. (thus, making NO assumptions about
the user's hardware..)
If
>>
>> /dev/console will go to serial, but afaik it doesn't block for lack of
>> a terminal. (has something to do with /dev/console being semantically
>> different to /dev/tty..., eg it doesn't block, not sure of the exact
>> details).
>Nope, /dev/console *does* block. ATM I've found a quick wo
Unless of course you really DO have RTS/CTS (Or DTR-->CTS) flow control
turned on - on your terminal, and the terminal shuts off RTS (or DTR) to
indicate its fifo level is too high.
That *IS* useful.
but the ability to hard-code it in a shut-off state is *MUCH* better.
Chad
> On Tue, 5 Dec 200
On Tue, 5 Dec 2000, PaulJakma wrote:
> > ATM I've found a quick workaround - I
> > use "stty -F /dev/console clocal -crtscts" to turn off the serial flow
> > control at the stawrt of /etc/rc.d/rc.sysinit - this seems to work quite
> > well... of course it doesn't stop some program turning flow co
On Tue, 5 Dec 2000, Steve Hill wrote:
> On Tue, 5 Dec 2000, PaulJakma wrote:
>
> > how? symlink to /dev/ttyS0, or with console=ttyS0 boot option?
>
> console=ttyS0
>
> Nope, /dev/console *does* block.
very weird.. the reason i replied to you, even though i have no direct
experience of serial con
> Nope, /dev/console *does* block. ATM I've found a quick workaround - I
> use "stty -F /dev/console clocal -crtscts" to turn off the serial flow
> control at the stawrt of /etc/rc.d/rc.sysinit - this seems to work quite
> well... of course it doesn't stop some program turning flow control back
>
On Tue, 5 Dec 2000, PaulJakma wrote:
> how? symlink to /dev/ttyS0, or with console=ttyS0 boot option?
console=ttyS0
> use /dev/console (char, 5,1) for all your programmes and boot the
> kernel with serial console support and .
>
> /dev/console will go to serial, but afaik it doesn't block for
On Tue, 5 Dec 2000, Steve Hill wrote:
>
> I'm building boxes with the console set to /dev/ttyS0.
how? symlink to /dev/ttyS0, or with console=ttyS0 boot option?
> However, I can't
> guarantee that there will always be a term plugged into the serial
> port. If there is no term on the port, event
In article <[EMAIL PROTECTED]>,
Steve Hill <[EMAIL PROTECTED]> wrote:
>I'm building boxes with the console set to /dev/ttyS0. However, I can't
>guarantee that there will always be a term plugged into the serial
>port. If there is no term on the port, eventually the buffer fills and
>any process
50 matches
Mail list logo
