Public bug reported:
Binary package hint: busybox-initramfs
I have had this problem since trying to install 8.10 (Ibex). 8.04(Hardy)
has worked fine for me, as far as drives are concerned. Basic low down
is this:
ASUS M2N-SLI board, AMD 64 with built in IDE and SATA controller.
2 IDE hard drives. 1 IDE CD drive. 1 SATA DVD drive.
When I use the live CD, or attempt an upgrade, etc.... to Ibex, i get:
((xx.xxx) = misc numbers)
(xx.xxx) ata 5: COMRESET failed (errno=-16)
(xx.xxx) ata 5: COMRESET failed (errno=-16)
(xx.xxx) ata 5: COMRESET failed (errno=-16)
(xx.xxx) ata 5: COMRESET failed (errno=-16)
ata 5: reset failed, giving up
initramfs
So after reading around, some people's 'patch' was to go to BIOS ans
enable RAID for SATA (even though I only have one SATA drive, and it's
an optical drive, not setup for RAID at all).
This always happens after some little blurb about Busybox. I tried
enabling the RAID option in BIOS for the SATA drive. No luck. For
fun(?), last night I tried enabling RAID for all SATA drives, even
though I have only one. Live CD finally booted up ok, got to the demo.
Today I booted the CD, and installed. Seemed to go ok, so first thing I
tried to enable Nvidia drivers. Machine tried to reboot, and before
shutting down/restarting fell back to evil death loop of initramfs, etc,
etc errors, blank screens, lockups, blank screens, etc, etc. login
prompts... Finally hard booted and reloaded Hardy.
At this point, the RAID enabling option seems to be a faulty patch at
best. It only worked for me after enabling several drives that didn't
exist, and even then the system was unstable. After reading a lot of
posts and pieces here and there, it looks to be an issue if you have
mixed IDE/SATA setups. But that is only a guess on my part. I am going
to keep Hardy until Ubuntu can prove that some fix has been made on
this, Ibex so far will not work on my machine. I'd like to think that
each version will get better, and perhaps it has in some respects, but
this is ridiculous, if you expect a new user to grab a disk and install
it, and then say 'well, you just have to go into BIOS and lie to your PC
that it has RAID drives..'. It really is a bit much for a lot of people
who just want to try something different or new. I don't know enough
about programming and configuration to fix it or add anything else right
now.
This happened initially when trying to upgrade to Ibex. Full clean install of
Ibex reacts the same. I would expect that Busybox would be able to figure out
my drive setup instead of getting lost in the mix. There are a lot of posts in
Ubuntu forums pertaining to this if you look around. It is driving some users
away, it has been extremely frustrating and time consuming for me, this is as
far as I've gotten with info since trying a month ago to get Ibex working off
and on...
So far Ibex is unusable for me, will stick with Hardy until I hear something
different.
Thanks.
S*
** Affects: busybox (Ubuntu)
Importance: Undecided
Status: New
--
initramfs, Busybox, startup errors
https://bugs.launchpad.net/bugs/305023
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
