From: Khalid Aziz <khalid_aziz@hp.com>
To: Pavel Roskin <proski@gnu.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: COM1 became ttyS01 in 2.4.19-pre7
Date: Thu, 18 Apr 2002 17:06:43 -0600 [thread overview]
Message-ID: <3CBF5183.B87E1238@hp.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0204181855430.21502-100000@marabou.research.att.com>
Look for a patch already posted to LKML on Tuesday under thread "Linux
2.4.19-pre7".
--
Khalid
Pavel Roskin wrote:
>
> Hello!
>
> The serial ports have changed their names after upgrading from 2.4.19-pre4
> to 2.4.19-pre7. What used to be /dev/ttyS0 is /dev/ttyS1 now.
>
> This is from the kernel log:
>
> Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ
> SERIAL_PCI enabled
> ttyS01 at 0x03f8 (irq = 4) is a 16550A
> ttyS02 at 0x02f8 (irq = 3) is a 16550A
>
> $ ls -l /dev/tts/
> total 0
> crw-rw-rw- 1 root root 4, 65 Apr 18 18:50 1
> crw-rw-rw- 1 root root 4, 66 Dec 31 1969 2
>
> I'm using AMD K7, SMP is disabled, serial ports are enabled, ACPI is
> disabled, APM is enabled, devfs is enabled and used, CONFIG_SERIAL_CONSOLE
> is enabled but not currently used. The motherboard is AOpen KT-133. The
> ports are set in BIOS to standard COM1 and COM2 settings.
>
> I'm ready to provide more information if needed.
>
> --
> Regards,
> Pavel Roskin
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
====================================================================
Khalid Aziz Linux Systems Operation R&D
(970)898-9214 Hewlett-Packard
khalid@fc.hp.com Fort Collins, CO
prev parent reply other threads:[~2002-04-18 23:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-18 23:04 COM1 became ttyS01 in 2.4.19-pre7 Pavel Roskin
2002-04-18 23:06 ` Khalid Aziz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3CBF5183.B87E1238@hp.com \
--to=khalid_aziz@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=proski@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox