|
Bugzilla – Full Text Bug Listing |
| Summary: | serial options in menu.lst are wrong ordered by yast2-bootloader | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.4 | Reporter: | Stefan Seyfried <seife> |
| Component: | YaST2 | Assignee: | Josef Reidinger <jreidinger> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | duwe |
| Version: | Factory | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Third Party Developer/Partner | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Stefan Seyfried
2010-10-29 09:10:10 UTC
Reassigning to yast2-bootloader maintainer. Stefan - Now there is no forcing of parameters order. If 'serial' must be before 'terminal' and it always work I can force it ( and prepare to other users whose complain about it :). So does it work in each situation if I force it? ( otherwise I must add special detection if I am in KVM managed quest, which is not easy ). torsten - what is difference in order of these two grub commands? I don't see anything about this topic in grub manual. "serial" sets it up, "terminal" selects it. You'll have a hard time pressing [Return] on the uninitialised serial line ;) Some broken BIOSes (surprise!) do not make an entry for the "unit 0", a --port=0x3f8 statement helps there, FYI. fixed in svn. Will be released on wednesday. |