I reported earlier that I had this problem trying to install 7.04 Desktop on a
dual processor 32-bit xeon system.
I am able to install 7.10 on the same system with no troubles.
--
Installation Error: Can't Access tty.
https://bugs.launchpad.net/bugs/126335
You received this bug notification b
I get this error when I have two SATA's and 2 PATA HDD's plugged in.
Two SATAs work fine.
1 SATA and 1 PATA work fine.
Motherboard: Asus PK5-VM
A work around is to press CTRL-ALT-F1 when Ubuntu is booting. It only
seems to happen when the boot screen is showing, pressing Ctrl-Alt-F1
switches to a
I've just encountered this trying to install 7.04 Desktop on a dual processor
32-bit xeon system. Specifically
(initramfs) /bin/sh: can't access tty; job control turned off
I catted out Casper.log: I'll try to summarize here
/init: /init: 1: cannot open /dev/fd0: No Such device or address
Una
Sorry, we don't have enough information to proceed with this bug.
Closing.
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: Incomplete => Invalid
--
Installation Error: Can't Access tty.
https://bugs.launchpad.net/bugs/126335
You received this bug notification because you are a member
I have open bug #129612 about this particular message: can't access tty; job
control turned off.
As I say there, you should probaby, at the # prompt, type:
cat /var/log/casper.log
and see if there is some error message there, that could have stopped the
booting of the CD.
You will probably have t
Thank you for taking the time to report this bug and helping to make Ubuntu
better. The issue that you reported is one that would benefit from testing
with the live environment of the Desktop CD of the development release - Gutsy
Gibbon. It would help us greatly if you could test with it so we
The machine is a stock Dell OptiPlex GX110 w/ 512MB. Default BIOS
settings. The boot order in the bios was CDROM then HardDrive with
floppy boot disabled.Instead of going with Ubunta I opted to try the
stock Debian Etch release. The Debian Etch network install CDROM (for
i386) works like
This is well before the installer starts and thus cannot be a bug in
ubiquity. The kernel team will need to know more details about your
system in order to diagnose this further; 'lspci -vvnn' output would
help, although it may be a pain to transcribe if you can't get to the
network. Perhaps a digi
** Changed in: ubiquity (Ubuntu)
Sourcepackagename: None => ubiquity
--
Installation Error: Can't Access tty.
https://bugs.launchpad.net/bugs/126335
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubunt
Used the image file ubuntu-7.04-desktop-i386.iso downloaded directly
from your website.
--
Installation Error: Can't Access tty.
https://bugs.launchpad.net/bugs/126335
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
10 matches
Mail list logo
