cannot access tty error

[weardlan]

I'm booting kubuntu and ubuntu 6.10 rc on a sony vaio VGN-FS215M both fail at the same point, dropping to an initramfs prompt with a 'cannot access tty' error

casper.log shows first a failure in mount /cdrom /root/cdrom folowed by lot's of 'not found' erros (presumably as a result of the cdrom mount failure)

[William Grant (wgrant)]

boot is a completely unrelated package...

[weardlan (ad-r3dsystems)]

this still exists in 6.10 final

(may be related to Alan Cox PATA bug in <2.6.17)

[trollord (trollenlord)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Thanks in advance.

[weardlan (ad-r3dsystems)]

1) YES is is still a *BUG*
2) YES it still fails
3) YES it still fails on later version of Ubuntu
4) I would have thought that failure to boot the live CD on a reasonably new
   high profile laptop would engender a slightly faster response than something in
   excess of 300 days
5) Frankly, it was never an ISSUE for me. I simply used Gentoo instead.

Still it's your OS, if you don't care whether it works or not, that's your problem not mine, I simply tried to help by letting you know.

Additionally, the only other response was to point out that this was not a 'boot' issue. Well, as a technical person of some years experience, I can comprehend what the Chap meant who replied as such.

However, from my Grandad's point of view such pedantry is less than useful, as far as he is concerned, he 'just stuck the disk in'. The disk failed while BOOTING, with the detailed error.

I was and am still prepared to offer further help to diagnose the problem in finer detail (as noted in the bug report, I tried several iterations of 6.10).

Though to be fair I should point out that if the average time between responses is going to exceed ten months, then the laptop under discussion may well have been consigned to the scraphead.

Thankyou

Regards
Alan Drew

----- Original Message -----
From: "trollord" <email address hidden>
To: <email address hidden>
Sent: 22 August 2007 23:41:13 o'clock (GMT) Europe/London
Subject: [Bug 68173] Re: cannot access tty error

Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering is this still an issue
for you? Thanks in advance.

--
cannot access tty error
https://bugs.launchpad.net/bugs/68173
You received this bug notification because you are a direct subscriber
of the bug.

[trollord (trollenlord)]

I am terribly sorry that it has taken so long. Snatched from #106864, could you try this out and report what happens:

To Install Feisty:

   1. From the main live CD menu press the F6 key to customize the boot command. Add the option break=top to it and boot up your PC.
   2. When you get to the dreaded (initramfs) prompt, type "modprobe piix" or "modprobe all_generic_ide" (either one should produce results), and press enter.
   3. Type exit to resume the normal live CD boot.

The install process should go smoothly from here on. However, when you reboot your PC your are likely to run into the same problem. So do as above to be able to boot your PC into your brand new installation. The permanent fix is the following:

   1. Add piix or all_generic_ide to /etc/initramfs-tools/modules.
   2. Run the command sudo update-initramfs -u .

[trollord (trollenlord)]

In case that works and you get the machine booted up, could you please post the information described here: https://wiki.ubuntu.com/DebuggingHardwareDetection ? Thank you in advance.

[trollord (trollenlord)]

Similar to #106864, and couple others also were assigned to linux-source packages.

[Brian Murray (brian-murray)]

I am assigning this bug to the 'ubuntu-kernel-team' per their bug policy. For future reference you can learn more about their bug policy at https://wiki.ubuntu.com/KernelTeamBugPolicies .

[Launchpad Janitor (janitor)]

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Ralph Janke (txwikinger)]

Unfortunately this bug report is being closed because we received no response to the last inquiry for information. However, the Intrepid Ibex 8.10 Beta release was most recently announced - http://www.ubuntu.com/testing/intrepid/beta . If you are able to confirm this is still an issue with this most recent release please feel free to reopen this report. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks.

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

[Felipe Zepeda (zepeda-felipe)]

Excuse me guys, I'm having the truble while I try to install Ubuntu Feisty Fawn (Desktop Edition -DVDROM) 7.04 on Laptop, Compaq Presario C700, and having the tty error during the install, some of the solutions are related to fix it previous the installating, which I can't do, other are related to open the machine and disconnect the devices, which I can't to either, this is other solution:

f you are getting this error (and you have a SATA harddrive); this is the fix:

At the LiveCD initial boot screen:
o Select F6 for more options
o Add the following option to the beginning of the options list:
break=top
o Press enter to start booting
Ubuntu will start booting, but kick you out to a command prompt; at the prompt type these two commands:
modprobe piix
exit

You will now boot into the LiveCD normally.

If you choose to install from the LiveCD, you must make the following modifications (or else your installed system will not be able to boot, just like the LiveCD):
o Make note of the device id of the partitions that were used to install (such as /dev/hda1)
-- if you choose to install the '/boot' mount from a different partition make note of it as well (this would be done from the manual partition selection); just a side note -- if you do this, make sure the boot partition is at least 50MB or the install will error at grub setup
o When the install is complete do not reboot -- stay in the LiveCD
o Open a terminal (Applications->Accessories->Terminal)
o You must now mount the installed partitions by typing the following (assuming the install was to /dev/hda1; otherwise replace '/dev/hda1' with the install partition) commands:

mkdir target
sudo mount /dev/hda1 target

*if you also created a boot partition issue (replace /dev/hda2 with the boot partition) the command:
sudo mount /dev/hda2 target/boot

sudo chroot target

o You will now be in a 'chroot' command prompt for your new ubuntu system (be careful here, you are editing with root access!)
o You must edit the /etc/initramfs-tools/modules file; adding a line with the word: piix
-- you should do this with your favorite unix editor; or simply type the command:
echo piix >> /etc/initramfs-tools/modules
o After modifying the file you must update the system with the command
update-initramfs -u
o When complete, type 'exit' to exit the chroot env; you can now close the Terminal and reset your system.

Now when you boot you will be in your new shinny Ubuntu system!

This solution is completely beyond my - GNU/LINUX - knowledge, can't perform this.

So... what can I do? I just want to get Feisty installed on the laptop, but I can't figure it out how to, yet.

Thanks.