How do you do? I’m fine! I've lost a few pounds already! It’s very easy
thanks to this drugs: http://resistances.org/net.php
--
Feisty boot fail "can't access tty" IDE SATA problem
https://bugs.launchpad.net/bugs/106864
You received this bug notification because you are a member of Ubuntu
Bugs,
Hello! I have very good news! I know how to help you to stop smoking!
http://praxeum.fr/net.php
--
Feisty boot fail "can't access tty" IDE SATA problem
https://bugs.launchpad.net/bugs/106864
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http://1marijuana.fimfowunsye.net
--
Feisty boot fail "can't access tty" IDE SATA problem
https://bugs.launchpad.net/bugs/106864
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
ht
http://www.lv4.life-health-co.com/b.php
--
Feisty boot fail "can't access tty" IDE SATA problem
https://bugs.launchpad.net/bugs/106864
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.
the Status column and change the status back to
"New". Thanks.
** Changed in: linux (Ubuntu)
Status: Incomplete => Won't Fix
--
long boot delay, similar to bug #106864
https://bugs.launchpad.net/bugs/108943
You received this bug notification because you are a member of Ubu
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.
** Tags added: cft-2.6.27
--
long boot delay, similar to bug #10
RONC55 :: thanks mate for your tips, it did work for me after changing
the boot options to "irqpoll"
--
Feisty boot fail "can't access tty" IDE SATA problem
https://bugs.launchpad.net/bugs/106864
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
I have been getting this problem while trying to boot Hardy off a Wubi
install process. I am using the 64-bit version.
I am currently running an Abit IB9 motherboard which has an IT8211 IDE
controller as well as a SATA controller. Previously I've encountered
this problem with Feisty and could not
I have this problem and "modprobe piix" didn't solve it.
--
Feisty boot fail "can't access tty" IDE SATA problem
https://bugs.launchpad.net/bugs/106864
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
I encountered the problem wit Feisty on a virtual machine.
Upgrading to Gutsy solved the problem (i.e. the modprode piix is not needed
anymore).
Hope that helps someone :)
--
Feisty boot fail "can't access tty" IDE SATA problem
https://bugs.launchpad.net/bugs/106864
You received this bug notific
Toni, thanks for testing the Hardy Alpha release. I'm glad to hear
things appear to be working with Hardy Alpha. Since jerry (the original
reporter) no longer has the hardware to verify this is resolved and no
one else has commented this still being an issue in Hardy I'm going to
mark this "Fix R
Ok, Edgy worked fine. And Feisty for a little while (but the LiveCD of
Feisty didn't boot, but a upgraded Egdy -> Feisty worked until some
update on Feisty). I was eventually successful booting Feisty's kernel
with the suggested "break=top; modprobe piix; exit" as most of people
here.
I updated Fe
Update
Since I have updated Ubuntu from its raw 7.10 status I am no longer able to get
Ctrl D to work. Since Windows XP works and there is no point continuing with
this exercise until somebody comes up with a fix. I cannot get a NVidia 8800gt
to work either so was using a 7600 for this exercis
Running on a abit IP35 with PATA dvd drive and Samsung hd501lj SATA hard
drive on SATA port 2 I need the workaround irqpoll for the live CD. I
loaded a new 7.10 32bit install with the alternate cd which partitioned
and populated ok but produces this issue on cold boot. Ctrl D allows
the system to
This problem is partially fixed for me:
- on my 64bit partition (fresh install of gutsy), this problem doesn't affect me
- on my 32bit partition (fresh install of feisty, upgraded to gutsy), I no
longer receive a "can't access tty" error, but the initramfs shell still
appears (hitting ctrl+D resu
I've run into this issue once again. Originally occured using a Feisty
LiveCD, this time I'm using a final-release Gutsy LiveCD. System specs
are same as before, and are as follows:
IBM eServer xSeries 232 (Type 8668-27X)
Dual P3 1.13GHz
1GB registered ECC-SDRAM
6 x 18.2GB IBM 10k u160 SCSI hard d
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team)
--
Feisty boot fail "can't access tty" IDE SATA problem
https://bugs.launchpad.net/bugs/106864
You received this bug notification because you are a member of Ubuntu
Bugs, which is th
Ok, this bug is realy fixed for me on two computers :
- An old one using intel 815 chipset, and now using ata_piix linux driver with
82801AA IDE Controller
- A new one using intel G35 chipset using pata_marvel linux driver (bug #134881)
I tested it with ubuntu livecd daily 20070921.1 on both.
--
Maybe the bug is now fixed. I can now access my IDE cdrom drive on
current installed version of gutsy and up-to-date (see bug #134881), so
I'll tried to download the latest daily cdimage and test it.
--
Feisty boot fail "can't access tty" IDE SATA problem
https://bugs.launchpad.net/bugs/106864
Yo
Undo of Henrik Nilsen Omma's change that was a mistake
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: Incomplete => Confirmed
--
Feisty boot fail "can't access tty" IDE SATA problem
https://bugs.launchpad.net/bugs/106864
You received this bug notification because you are a member of
Henrik Nilsen Onma, in my comment, comment #69,
(https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.20/+bug/106864/comments/69) I already reported reproducing it
on Gutsy/7.10 three months ago.
--
Feisty boot fail "can't access tty" IDE SATA problem
https://bugs.lau
** Also affects: linux-source-2.6.20 (Baltix)
Importance: Undecided
Status: New
--
Feisty boot fail "can't access tty" IDE SATA problem
https://bugs.launchpad.net/bugs/106864
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
I confirm this bug on Ubuntu Gutsy tribe 5.
It would be a share that lots of users can't use liveCd, as it was
already the case with feisty.
--
Feisty boot fail "can't access tty" IDE SATA problem
https://bugs.launchpad.net/bugs/106864
You received this bug notification because you are a member
Too late to fix this for Feisty.
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: Confirmed => Won't Fix
--
Feisty boot fail "can't access tty" IDE SATA problem
https://bugs.launchpad.net/bugs/106864
You received this bug notification because you are a member of Ubuntu
Bugs, which is t
Leaving open as a High importance Gutsy tasks, but it's incomplete as no
one has reported reproducing it on Gutsy yet.
** Changed in: linux-source-2.6.22 (Ubuntu)
Importance: Undecided => High
Status: New => Incomplete
--
Feisty boot fail "can't access tty" IDE SATA problem
https://bug
** Description changed:
Feisty 20070415 CD Live "can't access tty" will not boot.
Dapper's running great on same system, 1280x960 LCD, Intel 82845G
graphics so I didn't understand the "tty" failure.
Tried booting a bunch of times chasing around mulititude of boot options and
got doz
Me neither. The computer I had was replaced. (It was still pretty
snappy, but that's the policy.)
(My new ICH8-based system doesn't seem to have the problem, at least
not with Tribe 5.)
On 8/31/07, jerrylamos <[EMAIL PROTECTED]> wrote:
> I can't test this bug any more since my computer with th
I can't test this bug any more since my computer with the problem died
of an unrelated failure.
Cheers, Jerry Amos
--
Feisty boot fail "can't access tty" IDE SATA problem
https://bugs.launchpad.net/bugs/106864
You received this bug notification because you are a member of Ubuntu
Bugs, which is t
** Tags added: iso-testing
--
Feisty boot fail "can't access tty" IDE SATA problem
https://bugs.launchpad.net/bugs/106864
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
htt
** Attachment added: "lsmod"
http://launchpadlibrarian.net/8880206/lsmod.log
--
Feisty boot fail "can't access tty" IDE SATA problem
https://bugs.launchpad.net/bugs/106864
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubu
** Attachment added: "lshal"
http://launchpadlibrarian.net/8880197/lshal.log
--
Feisty boot fail "can't access tty" IDE SATA problem
https://bugs.launchpad.net/bugs/106864
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubu
** Attachment added: "lspci -vvnn"
http://launchpadlibrarian.net/8880189/lspci.log
--
Feisty boot fail "can't access tty" IDE SATA problem
https://bugs.launchpad.net/bugs/106864
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
-
** Attachment added: "syslog"
http://launchpadlibrarian.net/8880176/syslog
--
Feisty boot fail "can't access tty" IDE SATA problem
https://bugs.launchpad.net/bugs/106864
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubunt
** Attachment added: "dmesg"
http://launchpadlibrarian.net/8880163/dmesg
--
Feisty boot fail "can't access tty" IDE SATA problem
https://bugs.launchpad.net/bugs/106864
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-
.net/ubuntu/+source/linux-source-2.6.20/+bug/37382
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/64587
https://bugs.launchpad.net/linux/+bug/84603
https://bugs.launchpad.net/ubuntu/+bug/104581
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/106864
https://bugs.lau
** Also affects: linux-source-2.6.22 (Ubuntu)
Importance: Undecided
Status: New
--
Feisty boot fail "can't access tty" IDE SATA problem
https://bugs.launchpad.net/bugs/106864
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
This bug also occurs with Linux Mint 2.20. Ihave an old IBM Thinkpad
R30. I tried to install Linux Mint after many tries with all versions
of Fiesty Fawn and then bailed out to Linux Mint. Received the same
error message but I had removed the quiet splash and their installer
suggested using "irq
The problem "can't access tty". also occurs in the version Gutsy Tribe 3.
My the Hardware is: HD Sata Maxtor 80GB
Thanks.
--
Feisty boot fail "can't access tty" IDE SATA problem
https://bugs.launchpad.net/bugs/106864
You received this bug notification because you are a member of Ubuntu
Bugs, whi
On one of the myriad forums on "can't access tty" someone said they were
able to download and burn the alternate CD, and then install O.K. The
alternate doesn't run as a live CD, it is just for doing install and is
a lot more streamlined than the CD Live. If the Alternate is missing
some packages
Hi, I am also experiencing this bug on a friends computer. I have tried
the "break=top"-solution and also the piix-module solution - neither of
these two worked. I should also state that I didn't see any activity in
the floppy drive that was connected to the computer. Since it is my
friends compute
My interpretation, "can't access tty" is a catchall message that
something broke somewhere and Ubuntu isn't going to tell you what
failed. Example Gutsy winds up with the same message on the same
hardware, however the developer's fix break=top and modprobe piix don't
work because it fails before t
Is https://bugs.launchpad.net/ubuntu/+bug/120285 a duplicate of this
problem?
--
Feisty boot fail "can't access tty" IDE SATA problem
https://bugs.launchpad.net/bugs/106864
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu
> Can anyone point to any ongoing discussion of progress on this bug?
> I've googled around a bit but I'm not seeing anything. I wonder if
> anyone is even working on it...
>
>
I wonder the same thing but in general for bugs on lauchpad.
The trouble is that developers don't use this (launchpad
For what it's worth, I tried GG Tribe 1 just now, and I also am not able
to boot.
Can anyone point to any ongoing discussion of progress on this bug?
I've googled around a bit but I'm not seeing anything. I wonder if
anyone is even working on it...
--
Feisty boot fail "can't access tty" IDE SAT
t Tribe 1, so I tried to follow the
workaround posted by Ben Collins -
https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.20/+bug/106864/comments/13 - but it didn't work.
As soon as I start up my PC and see the Live CD menu, I hit F6, type
"break=top" (without the quotation
I had the same problen with Tribe 1, whith feisty a floppy disk take
care the problem but no lucky in Gutsy
--
Feisty boot fail "can't access tty" IDE SATA problem
https://bugs.launchpad.net/bugs/106864
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug c
I guess I don't have this bug. The CD-ROM is still accessible; it's
just "/dev/scd0" now.
--
Feisty boot fail "can't access tty" IDE SATA problem
https://bugs.launchpad.net/bugs/106864
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubunt
David:
I suspect your problem is different to this. See Bug #116996 .
--
Feisty boot fail "can't access tty" IDE SATA problem
https://bugs.launchpad.net/bugs/106864
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs ma
Gutsy Gibbon CD Live 20070606 "can't access tty" same CD & Hard disk on IDE1 as
originally reported error with Feisty at top of this post. Seems to make a lot
of accesses to fd0 floppy which go zipping by the screen.
break=top stops just after "can't access tty", modprobe piix gets "module piix
I'm not sure if this is related; but I can't access the CD-ROM drive on
an Ubuntu system after upgrading from Kubuntu/Breezy to Feisty. When I
try to do "mount /cdrom", I get the error-message
mount: /dev/hda is not a valid block device
The computer is a Dell system with an IDE CD-ROM and tw
I had some trouble with my Feisty installation, 'cause it didn't boot
the generic kernel. I have a Pentium D930, and I really didn't want to
use just one core, so i downgraded to dapper.
Once I installed Dapper (on 100GB unpartitioned disk space) i wanted to
upgrade to edgy. As far as i knew my ed
small 4GB SCSI HDD that we had
in there
we used that PC before to run a PBX Asterisk phone server ( if I say that right)
I am only an end user.
Victor
- Original Message
From: Mike Coleman <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Sent: Wednesday, May 23, 2007 10:18:30 PM
Subj
machs_fuel <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Sent: Wednesday, May 23, 2007 7:00:27 PM
Subject: [Bug 106864] Re: Feisty boot fail "can't access tty" IDE SATA problem
I'm having the same problem and have been watching this thread. I've
tryed a the piix solutions ment
ke Coleman <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Sent: Wednesday, May 23, 2007 4:04:10 PM
Subject: [Bug 106864] Re: Feisty boot fail "can't access tty" IDE SATA problem
> Ubuntu new with Feisty is trying to do more things in parallel to
speed up boot time.
If this parallel
I tried booting with *both* hard drives disconnected, to test whether
the (software) RAID filesystem present on them was causing my problems.
The first time I tried it (no break=top, no "modprobe piix"), it booted
up! Always skeptical, I tried it again, and it failed, just as before.
I did try the
Have a look at my post above. Of course, these modules will not work for
you. Start Ubuntu with an older kernel, and see the output of lsmod,
looking for something related to your VIA controler.
--
Feisty boot fail "can't access tty" IDE SATA problem
https://bugs.launchpad.net/bugs/106864
You rec
I'm having the same problem and have been watching this thread. I've
tryed a the piix solutions mentioned here to no avail. I'm going to try
vicarious1's solution step by step tonight just in case..
I was looking at Recalcitrante's lspci an noticed that he's got much
different hardware then I.
> Ubuntu new with Feisty is trying to do more things in parallel to
speed up boot time.
If this parallel system is active at the point when the error occurs,
this suggests another possible cause. Perhaps the startup dependencies
are incomplete and there is a race or something. (This might explai
Message
From: jerrylamos <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Sent: Wednesday, May 23, 2007 12:17:38 AM
Subject: [Bug 106864] Re: Feisty boot fail "can't access tty" IDE SATA problem
Let's see if we can get a little more information. When you type "exit&qu
hings back and forth from the different Linux's, or even Windoze.
A net effect I hit was a file system check failure on a drive that I had
removed from the system a while ago; pointers to it were still in
/boot/grub/menu.lst and /etc/fstab.
>From another post in bug 106864: "
Adding
I get the first prompt because of "break=top", do a "modprobe piix"
which causes a short barrage of IDE-related messages that look correct
to me, then an "exit". At that point there are several more pages of
messages, and then a new prompt. (Actually some messages appear after
the prompt--I'm ass
Let's see if we can get a little more information. When you type "exit"
you are likely at a command line? If so, what do the last few lines on
the screen say?
As far as configurations, the one that worked for me is to plug the CD
drive into IDE1 and the hard drives into IDE2. My best guess that
PROTECTED]
Sent: Tuesday, May 22, 2007 10:40:28 PM
Subject: [Bug 106864] Re: Feisty boot fail "can't access tty" IDE SATA problem
I have only one IDE hard drive and one CDRW drive. No SATA, No SCSI. I
swapped them on IDE controllers 0 and 1 but it made no difference - and
modprobe pi
AIL PROTECTED]>
To: [EMAIL PROTECTED]
Sent: Tuesday, May 22, 2007 10:11:34 PM
Subject: [Bug 106864] Re: Feisty boot fail..., but piix fix doesn't work for me
I have a system that generally runs Linux/Ubuntu fine, but the 7.04 live
CD fails, just as described here. I tried the 'modprobe
I have only one IDE hard drive and one CDRW drive. No SATA, No SCSI. I
swapped them on IDE controllers 0 and 1 but it made no difference - and
modprobe piix had no effect either way. I reverted to Edgy and all is
fine now.
--
Feisty boot fail "can't access tty" IDE SATA problem
https://bugs.la
I have a system that generally runs Linux/Ubuntu fine, but the 7.04 live
CD fails, just as described here. I tried the 'modprobe piix' fix, but
this didn't work for me.
The system has a SCSI as well as IDE interface, but there are no SCSI
drives attached. It has 2 IDE hard drives and an IDE CD-R
Thanks, but it really did seem the boot had stopped altogether at the
busybox prompt. I think I'll go back to Edgy until this one is fixed
properly. Nick
--
Feisty boot fail "can't access tty" IDE SATA problem
https://bugs.launchpad.net/bugs/106864
You received this bug notification because y
I had the same problem, downloaded the alternate CD and installed it
with that. Afterwards when Ubuntu started, I got ATA errors but waiting
a long period of time paid off since it did continue with booting. Then
I added the piix module in /etc/modules, I restarted and the problems
were gone. Maybe
Thanks so far, but unfortunately the workaround fails when I get the
(initramfs) prompt when booting from the new Feisty installation on the
hard disk: I type modprobe piix, and press enter, then when I type exit
to resume the boot I get the error 'can't access tty' again. Unable to
exit busybox
ehm? shouldn't this be break=top?
I assume you're talking about the graphical boot menu when you mean
bootgfx? Also the busybox menu, that is just the shell showing up after
the PC says "/bin/sh/:can't access tty job control turned off", with the
shell identifier (initramfs)?
--
Feisty boot fail
I have the same problem. Here is the ouput of lspci:
00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge
(rev 03)
00:01.0 PCI bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge
(rev 03)
00:03.0 CardBus bridge: Texas Instruments PCI1225 (rev 01)
00:03.1 Ca
ls/modules.
Thanks
Try this
Bug 106864 covers this. Here's a summary of the solution:
To Install Feisty:
1. From the main live CD menu press the F6 (? I don't really remember which
F key it is) key to customize the boot command. Add the option break=top to it
and boot up your PC.
The workaround mentioned in this thread (break=top + modprobe piix)
fixed the xfermode error problems described in bug #96826 for me on a
Dell OptiPlex GX100 system. The two problems seems to be connected.
--
Feisty boot fail "can't access tty" IDE SATA problem
https://bugs.launchpad.net/bugs/106
Please disregard my comment, just learned how inird.img is generated
during installation and is not part of any ubuntu package. Also closed
my bug.
--
Feisty boot fail "can't access tty" IDE SATA problem
https://bugs.launchpad.net/bugs/106864
You received this bug notification because you are a m
Could this be the source of the problem?
"The linux-image-2.6.20-15-generic package doesn't install a upgraded
initrd.img"
http://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/114541
--
Feisty boot fail "can't access tty" IDE SATA problem
https://bugs.launchpad.net/bugs/106864
You
Any news on this? It's been almost 3 weeks ago since feisty got released
and the problem still exists! There are no newer install cd's, and the
recommandation from Ben (piix) did not work for me. My pc has no SATA-
devices (not even a SATA-controller), and I'm not able to install and
work with feis
Is this not an upstream bug in udev?
http://forums.debian.net/viewtopic.php?t=4703
--
Feisty boot fail "can't access tty" IDE SATA problem
https://bugs.launchpad.net/bugs/106864
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
u
jerrylamos, you shouldn't have use you mail client because now our
addresses are on the internet and can be catch automatically.
Otherwise, I don't think the problem is fix if I had to load a module manually,
whereas it works with older version.
Kernel team have to fix it : that should load piix
USB keyboards can be enabled during boot up .. just enable USB Legacy
support in your BIOS
--
Feisty boot fail "can't access tty" IDE SATA problem
https://bugs.launchpad.net/bugs/106864
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu
Hi, any chance you could borrow a keyboard with another type of connection
just to get the problem fix put on?
Cheers, Jerry
-Original Message-
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sat, 28 Apr 2007 4:33 PM
Subject: [Bug 106864] Re: Feisty boot fail "can
I have the same problem too, but I wasn't able to boot with Ben's advice
because if I use break=top, I can't write anything on busybox. This
should be the case because I use an USB keyboard that is normaly
detected after tty access error.
--
Feisty boot fail "can't access tty" IDE SATA problem
ht
I had the same problem and I followed Ben's advice and now all works!
--
Feisty boot fail "can't access tty" IDE SATA problem
https://bugs.launchpad.net/bugs/106864
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs ma
check out this blog post about this error :
http://blog.shevin.info/2007/04/how-did-i-fix-cant-acess-tty-in-feisty.html
--
Feisty boot fail "can't access tty" IDE SATA problem
https://bugs.launchpad.net/bugs/106864
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Changed in: linux-source-2.6.20 (Ubuntu)
Importance: Undecided => Medium
Assignee: Brian Murray => Ubuntu Kernel Team
Status: Needs Info => Confirmed
--
long boot delay, similar to bug #106864
https://bugs.launchpad.net/bugs/108943
You received this bug notification be
ttachment added: "dmseg.log"
http://librarian.launchpad.net/7395083/dmesg.log
--
long boot delay, similar to bug #106864
https://bugs.launchpad.net/bugs/108943
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
The attachment above should read dmesg.log
Anyway, here is the other file.
** Attachment added: "lspci-vvnn.log"
http://librarian.launchpad.net/7395087/lspci-vvnn.log
--
long boot delay, similar to bug #106864
https://bugs.launchpad.net/bugs/108943
You received this bug notificati
rence, the full description of procedures for kernel-related bug
reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks
in advance!
** Changed in: linux-source-2.6.20 (Ubuntu)
Sourcepackagename: None => linux-source-2.6.20
Assignee: (unassigned) => Brian Murray
St
was
trying to boot from swap) so I checked the UUID's and they seem to point
to the right partition...
Then I found bug #106864, which is quite similar. I tried to do the following,
as Ben Collins recommended:
add "piix" to /etc/initramfs-tools/modules, and run "sudo update-init
This is the error message I get at first
** Attachment added: "Error messages"
http://librarian.launchpad.net/7386683/pic1.jpg
--
long boot delay, similar to bug #106864
https://bugs.launchpad.net/bugs/108943
You received this bug notification because you are a member of Ubuntu
B
I did another workaround and got everything working.
No slow boot with "waiting for root file system and no "can't access tty"
error.
I went in to Bios changed the IDE Configuration settings from AHCI to
Standard IDE.
--
Feisty boot fail "can't access tty" IDE SATA problem
https://bugs.launch
p.
Daniel
** Attachment added: "pic2.jpg"
http://librarian.launchpad.net/7386687/pic2.jpg
--
long boot delay, similar to bug #106864
https://bugs.launchpad.net/bugs/108943
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
I have followed Ben's advice, using modprobe piix, and got Feisty installed on
my parallels guest (in a mac mini). After rebooting to the installed system
(again using modprobe piix) I put piix into the initramfs modules file and ran
the update. On the next reboot I am still prompted by busybox
A bit further back you can read his work around. In any case here is the
comment with the work around: https://bugs.launchpad.net/ubuntu/+source
/linux-source-2.6.20/+bug/106864/comments/13
--
Feisty boot fail "can't access tty" IDE SATA problem
https://bugs.launchpad.net/
Tiemen Gysels can you tell me , what did u exactly? I didnt get what
colin said...
--
Feisty boot fail "can't access tty" IDE SATA problem
https://bugs.launchpad.net/bugs/106864
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
After an upgrade to Feisty, system takes forever to boot.
There were some 'ata2.01: failed to set xfermode (err_mask=0x4)' errors,
so i applied Ben Collins solution and everything went smooth.
** Attachment added: "lspci -vvnn output"
http://librarian.launchpad.net/7381388/output
--
Feisty b
I got the same "can't acess tty" error, with Feisty Beta and Kubuntu,
with this output:
[81.450108] ata2.00: port failed to respond (30 seconds, Status 0xd0)
[83.260473] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
[83.260520] ata2.00: (BDMA stat 0x65)
[83.260564] ata2.00: cmd
Hey Guys Update !
as I said I have two hard disk and a DVD-ROM and a CD-RW
I un-pluged the CD-RW and the windows Hard Disk .
and I installed the ubuntu fiesty sucessfully, but the problem is , now
when I plug the CD-RW or windows Hard Disk (which all my important
files are there) i get the same e
As I said I tried the workaround that Ben told us to try, and here is the
result 2 days later :
First errors :
[17179579.256000] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
[17179579.256000] hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Then I had to reboot the computer.
I really didnt get what Ben Collins said ...
can somebody tell me what to do to install ubuntu ?
--
Feisty boot fail "can't access tty" IDE SATA problem
https://bugs.launchpad.net/bugs/106864
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
By the way, there was nothing wrong with the way the CD was read on my
girlfriends computer. The alternate worked fine, although I did get
these ata2. errors but after waiting for a while I could install Feisty.
After installation applying the work around made the terrible delay and
the errors go a
1 - 100 of 122 matches
Mail list logo
