Installation Error: Can't Access tty.

Bug #126335 reported by Ben
8
Affects Status Importance Assigned to Milestone
linux-source-2.6.22 (Ubuntu)
Invalid
Undecided
Brian Murray

Bug Description

When attempting run the "Start/ Install" menu option from the stock Ubunta Desktop install CDROM. The installation boot stop with the following message:

/bin/sh: can't access tty; job control turned off

Then you are dropped to a text based command prompt (initramfs). No indication as to what the real problem is. No indication as to what simple corrective actions should be taken. Yes, I looked around but all workarounds look like the same old "Linux Gymnastics". Macintrash and Windoze install work reasonably well: the Ubunta installer should too.

Revision history for this message
Ben (bdebiase) wrote :

Used the image file ubuntu-7.04-desktop-i386.iso downloaded directly from your website.

Revision history for this message
Colin Watson (cjwatson) wrote :

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 digital camera would help?

Revision history for this message
Ben (bdebiase) wrote :

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 a charm without any gymnastics.

Revision history for this message
Brian Murray (brian-murray) wrote :

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 can work on getting it fixed in the actively developed kernel. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.
Alternatively, the output of 'sudo lspci -vvn' from your Debian install may be helpful.

Changed in linux-source-2.6.22:
assignee: nobody → brian-murray
status: New → Incomplete
Revision history for this message
Paul Dufresne (paulduf) wrote :

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 to use pen and paper to rewrite most pertinent information.

Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

Sorry, we don't have enough information to proceed with this bug. Closing.

Changed in linux-source-2.6.22:
status: Incomplete → Invalid
Revision history for this message
mark suhovecky (suhovecky) wrote :

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
Unable to find a medium containing a live file system
mount: mounting /cdrom failed
chroot: cannot execute debconf-communicate: no such file or directory
(lots more no such files or directory errors)
couldn't umount /root/cdrom: invalid argument

I've not tried the server version yet.

Revision history for this message
David Freitas (jddcef) wrote :

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 terminal till Ubuntu is finished booting up and this error doesn't occur.

Revision history for this message
mark suhovecky (suhovecky) wrote :

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.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.