Summary: | static-BIOS-codes was needed | ||
---|---|---|---|
Product: | Branch 4.0 | Reporter: | Ivan Zakharyaschev <imz> |
Component: | lilo | Assignee: | Nobody's working on this, feel free to take it <nobody> |
Status: | CLOSED WONTFIX | QA Contact: | Q.A. 4.0 <qa-4.0> |
Severity: | normal | ||
Priority: | P2 | CC: | mike, ruslandh, slazav |
Version: | 4.0 | ||
Hardware: | all | ||
OS: | Linux | ||
Bug Depends on: | |||
Bug Blocks: | 15605 |
Description
Ivan Zakharyaschev
2008-05-12 03:18:37 MSD
https://bugzilla.altlinux.org/show_bug.cgi?id=15605 describes such a case. (In reply to comment #0) > In general, this option should never be used, except as a bug workaround. > I encountered a configuration where the only way to install a working LILO was > by using this option. So, it was probably a bug in lilo, wasn't it? Probably in BIOS. (In reply to comment #2) > (In reply to comment #0) > > In general, this option should never be used, except as a bug workaround. > > I encountered a configuration where the only way to install a working LILO was > > by using this option. So, it was probably a bug in lilo, wasn't it? > Probably in BIOS. Ah, I see. :) So, I misunderstood the manpage. What to do with the bug? INVALID? (In reply to comment #2) > > In general, this option should never be used, except as a bug workaround. > Probably in BIOS. But, well, I haven't dealt much with IDE, so I don't know whether it's normal: this BIOS could only boot from /dev/hda and /dev/hdc. I considered it to be an acceptable restriction of the BIOS and not a bug. But then, if I want to boot the ALTLinux system installed on /dev/hdb, I need to install lilo to /dev/hda. But lilo doesn't want to install itself onto /dev/hda without this option (I think, it's important that the kernel is on /dev/hdb in this case). Isn't it a problem of lilo? В 4.0/branch исправления не будут вноситься уже технически (заглушена очередь на сборку), поэтому прошу ошибки, актуальные для sisyphus/p7/t7, перевесить на текущие ветки или сизиф. |