** Changed in: yaboot-installer (Ubuntu)
Sourcepackagename: None = yaboot-installer
** Summary changed:
- Cant boot in single-user mode (recovery-mode) on Hardy Heron powerpc
+ Can't boot in single-user mode (recovery-mode) on Gutsy Gybbon and Hardy
Heron for PowerPC
** Summary changed:
-
The same problem in my iMac G3 with ubuntu-8.04-alternate-powerpc image.
I can not boot the system.
--
Cant boot in single-user mode (recovery-mode) on Hardy Heron powerpc
https://bugs.launchpad.net/bugs/203206
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Affects too to Xubuntu 8.04.
--
Cant boot in single-user mode (recovery-mode) on Hardy Heron powerpc
https://bugs.launchpad.net/bugs/203206
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
The problem seems to be fixed from me after the latest updates (kernel -
2.6.24-16-generic).
The console text is visible in single user-mode ncurses dialog also has
visible text.
--
Cant boot in single-user mode (recovery-mode) on Hardy Heron powerpc
https://bugs.launchpad.net/bugs/203206
Problem remains with new kernel 2.6.24-14-powerpc-smp
** Description changed:
1.) Hardy Heron powerpc latest build
- 2.) maybe yaboot or xserver or gdm (if this is started in single-user mode)
-
- 4.) When I type Linux single on yaboot stage 2 bootprompt, the system
- should boot in
This happens even on amd64 hardy build (upgraded from gutsy).
single-user mode boot results in a ncurses like display but with no text.
In normal-boot VTs only have blinking cursor without any text. The cursors are
positioned where it should be if there was text. I can login into console
type
can you do a normal (not single) boot?
if so, when you do CTRL+ALT+F1 can you see the log in prompt?
--
Cant boot in single-user mode (recovery-mode) on Hardy Heron powerpc
https://bugs.launchpad.net/bugs/203206
You received this bug notification because you are a member of Ubuntu
Bugs, which is
No I don't. The VT's seem to be dead. Only the setupcon-command will
solve the matter. But because of the different situation on single-user
mode, I can't even log in blindly to execute setupcon. (normally in
single-user mode you are still loggged in as root, when my memories are
right) Did
