Bug 16749
| Summary: | Secondary serial console doesn't allow you to pass kernel options | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Pekka Savola <pekkas> |
| Component: | lilo | Assignee: | Michael K. Johnson <johnsonm> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.1 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2002-06-04 05:17:15 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Pekka Savola
2000-08-22 20:44:22 UTC
hmmm ... I am unable to reproduce this problem (the inability to enter text mode at the lilo splash screen, and subsequently type in boot parameters): using rc2, I am able to install with an append="console=ttyS0,19200n8" line in my lilo.conf for the default linux boot label ... and upon reboot, I'm able to use ^X to enter text mode at the VGA splash screen, and am able to add boot parameters ... Please try using: append="console=ttyS0,19200n8 console=tty0" I think the problem occurs only when serial console is secondary. I use this to setup "backup" serial consoles (for systems that still do have VGA). this behavior is verified with the above append line, you can not enter lilo parameters over the serial line ... uh, why did you assign this to me? Does this still happen with current releases? Tested on RHL73: 1) whether primary or secondary console, if using message= in lilo.conf, you cannot pass any parameters (a "duplicate" of #24286) 2) you can pass parameters with secondary console is no message= is defined. Marking as duplicate even though this was a much earlier report. *** This bug has been marked as a duplicate of 24286 *** |