- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Fedora 13 serial console no login prompt problem
Operating System - Linux
1752402
Members
5782
Online
108788
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-20-2010 12:55 PM
тАО08-20-2010 12:55 PM
I have recently upgraded to Fedora 13.
The following worked perfectly for Fedora 12. But it does no longer work for Fedora 13.
I do not get a login prompt when connecting a terminal emulator via a serial cable.
----
You need to reboot after making the following modifications:
vi /etc/securetty
ttyS0
vi /etc/event.d/ttyS0
# ttyS0 - mgetty
#
# This service maintains a getty on ttyS0 from the point the system is
# started until it is shut down again.
start on stopped rc1
start on stopped rc2
start on stopped rc3
start on stopped rc4
start on stopped rc5
stop on shutdown
respawn
#exec /sbin/agetty -L ttyS0 57600 vt100
exec /sbin/mgetty -r -s 57600 ttyS0 vt100
The following worked perfectly for Fedora 12. But it does no longer work for Fedora 13.
I do not get a login prompt when connecting a terminal emulator via a serial cable.
----
You need to reboot after making the following modifications:
vi /etc/securetty
ttyS0
vi /etc/event.d/ttyS0
# ttyS0 - mgetty
#
# This service maintains a getty on ttyS0 from the point the system is
# started until it is shut down again.
start on stopped rc1
start on stopped rc2
start on stopped rc3
start on stopped rc4
start on stopped rc5
stop on shutdown
respawn
#exec /sbin/agetty -L ttyS0 57600 vt100
exec /sbin/mgetty -r -s 57600 ttyS0 vt100
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-21-2010 10:28 AM
тАО08-21-2010 10:28 AM
Solution
I got curious about event.d and found this:
http://www.linuxquestions.org/questions/fedora-35/in-fedora13-etc-event-d-now-etc-sysconfig-init-827150/
http://www.linuxquestions.org/questions/fedora-35/in-fedora13-etc-event-d-now-etc-sysconfig-init-827150/
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-22-2010 03:08 PM
тАО08-22-2010 03:08 PM
Re: Fedora 13 serial console no login prompt problem
I implemented the advice of Michael -- thanks!
vi /etc/init/serial-console-ttyS0.conf
start on stopped rc RUNLEVEL=[2345]
stop on starting runlevel [016]
respawn
exec /sbin/agetty -L ttyS0 57600 vt100
#exec /sbin/mgetty -r -s 57600 /dev/ttyS0 vt100
(need to reboot)
But I still got errors and the serial port did not work:
tail -f /var/log/messages
... kernel: ttyS0: LSR safety check engaged!
The following articles suggested me to use the boot option acpi=off (I tried pnpacpi=off but this did not work):
https://bugzilla.redhat.com/show_bug.cgi?id=260481
http://www.linuxforums.org/forum/redhat-fedora-linux-help/85411-dev-ttys0-nc6000-not-working.html
The boot option acpi=off workaround seems to work. But perhaps other hardware features will now be inaccessible?
Seems to be an old unresolved Fedora bug resulting in a hardware IRQ conflict with an (unexisting) IR port for the Compaq nc6000 laptop? (I found references since Fedora core 6).
Question: Why does the Fedora team change the serial console behaviour at each release? Until and including Fedora 11 /etc/inittab itself could launch the ttyS0 console. The problems started with Fedora 12, and Fedora 13 which both required a different setup (see above) because /etc/inittab since release 12 only contains the default run level.
FYI, the pre-Fedora 12 setup:
vi /etc/inittab
...
C0:12345:respawn:/sbin/agetty -L ttyS0 57600 vt100
telinit q
vi /etc/init/serial-console-ttyS0.conf
start on stopped rc RUNLEVEL=[2345]
stop on starting runlevel [016]
respawn
exec /sbin/agetty -L ttyS0 57600 vt100
#exec /sbin/mgetty -r -s 57600 /dev/ttyS0 vt100
(need to reboot)
But I still got errors and the serial port did not work:
tail -f /var/log/messages
... kernel: ttyS0: LSR safety check engaged!
The following articles suggested me to use the boot option acpi=off (I tried pnpacpi=off but this did not work):
https://bugzilla.redhat.com/show_bug.cgi?id=260481
http://www.linuxforums.org/forum/redhat-fedora-linux-help/85411-dev-ttys0-nc6000-not-working.html
The boot option acpi=off workaround seems to work. But perhaps other hardware features will now be inaccessible?
Seems to be an old unresolved Fedora bug resulting in a hardware IRQ conflict with an (unexisting) IR port for the Compaq nc6000 laptop? (I found references since Fedora core 6).
Question: Why does the Fedora team change the serial console behaviour at each release? Until and including Fedora 11 /etc/inittab itself could launch the ttyS0 console. The problems started with Fedora 12, and Fedora 13 which both required a different setup (see above) because /etc/inittab since release 12 only contains the default run level.
FYI, the pre-Fedora 12 setup:
vi /etc/inittab
...
C0:12345:respawn:/sbin/agetty -L ttyS0 57600 vt100
telinit q
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP