can't access tty; job control turned off

Bug #150324 reported by Justin Helgerson
4
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

Pentium 4 3GHz, nVidia 8600 GTS 256MB DDR3, 1GB RAM.

Ubuntu Gutsy 7.10 Beta

While trying to boot into the Live CD I receive this error: http://webpages.charter.net/muznic/IMG_0019.JPG

I have seen reports of this issue with Feisty and Edgy, but I didn't manage to find any dealing with Gutsy. It looks like I may have a reproduction of the issue.

Revision history for this message
Gaspard Leon (gaspard.leon) wrote :

Hi, I get one similar to this (dropped to busybox), but without the last more detailed line (COMRESET failed).

note that I get it 9 times out of 10, not 10 out of 10...

adding all_generic_ide to the boot parameters worked for me...

Also check your BIOS and try to disable/enable AHCI for your SATA controller and try again... see if results are different

Gaspard

Revision history for this message
Justin Helgerson (ek0nomik) wrote :

I tried booting with the all_generic_ide and it didn't change anything.

I never tried changing my BIOS settings, but they are currently set at RAID / AHCI.

I managed to install Ubuntu Gutsy Beta with the Alternate CD, but the problem still isn't solved.

Revision history for this message
Gaspard Leon (gaspard.leon) wrote :

Not sure if this will be fixed... the release is so close.. it might be a show-stopper for me, I'm thinking of waiting till 8.04 and just throwing windows xp on the box until then...

Revision history for this message
Gaspard Leon (gaspard.leon) wrote :

seems to be working so far (cross fingers) with my fresh copy of 7.10 installed.

cheers,

Gaspard

Revision history for this message
Gaspard Leon (gaspard.leon) wrote :

Justin:
have you tried the latest release CD?

Revision history for this message
Michael Nagel (nailor) wrote :

is this still an issue with hardy? could you please link the reports for feisty/edgy?

Revision history for this message
Pedro Villavicencio (pedro) wrote : Closing the report

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

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.