| Summary: | No tty's are available in the installer - 4RC | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | claire robinson <eeeemail> |
| Component: | Installer | Assignee: | Thomas Backlund <tmb> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | dvgevers, ennael1, mageia, thierry.vignaud, tmb |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | 4RC | ||
| Source RPM: | kernel | CVE: | |
| Status comment: | |||
| Bug Depends on: | 12241 | ||
| Bug Blocks: | |||
|
Description
claire robinson
2014-01-08 18:51:04 CET
claire robinson
2014-01-08 18:51:22 CET
CC:
(none) =>
ennael1 side effect of using dracut in stage1? CC:
(none) =>
mageia Can you be a little clearer about what you mean? Do you just mean during stage1? Or when the installer proper kicks in. I've happily been using tty's 1, 2, 3, 4 etc. to debug and log things since dracut switch. I suspect perhaps it's a problem with the latest kernel as it also doesn't boot on my machine (bare metal) and we had a similar regression in VirtualBox with an older kernel where you could not switch to the TTYs. Thomas WDYT? CC:
(none) =>
tmb Noticed in stage 2 but didnt check stage 1 so it may be the same. Confirmed by dvg. Still don't think it's related to anything other than kernel. Is it only the latest ISOs you're noticing this? If it was working in previous iterations, it's the only thing that could affect it. It's hard to say Colin its not something we really check for. This is valid in the current build though, build 4. AFAIK we missed tty's only in the 4th round prerelease iso's ! CC:
(none) =>
dvgevers (In reply to Dick Gevers from comment #6) > AFAIK we missed tty's only in the 4th round prerelease iso's ! Yeah I definitely used them when looking into the unconfigured network issue for sure, so I suspect a kernel issue. Probably related to the big regression (bug #12241) CC:
(none) =>
thierry.vignaud Presumed fixed. Status:
NEW =>
RESOLVED Yes, fixed in latest isos so must have been the previous kernel issue. |