Final Gusty throws me in to BusyBox on all attempts to install

Bug #153991 reported by Vitaly on 2007-10-18
14
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Medium
Unassigned
Nominated for Hardy by nemesis
linux-source-2.6.22 (Ubuntu)
Undecided
Unassigned
Nominated for Hardy by nemesis

Bug Description

When I try to install Ubuntu 7.10 ( Gusty ) it drops the box in to busybox. Even when i try to check the cd for errors. I have ran the memory test and it passed. My hard ware specs are http://vbabiy.mine.nu:8080/Desktop_Hardware.html ,I have used this CD to install gusty on my laptop and it ran 100%.

Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in linux-source-2.6.22.

Vitaly (vbabiy86) wrote :

I am very sorry about this. I personal did not have any idea what package to link it to. Also if any hardware specs or files off my computer are need please let me know.

Thanks for the help,
Vitaly Babiy

Bob Smith (ubuntu-mensetmanus) wrote :

I also get dropped to BusyBox (initramfs) after doing network upgrade from 7.04 to 7.10. Before upgrading, the 7.10 live CD worked fine. Now, starting with 2.6.20-16 instead of 2.6.22-14 works ok. This is with ASUS Z62FM laptop, Core 2 Duo, and System76 drivers installed.

Sisko78 (cjaegle) wrote :

There seem to be several people in the ubuntu forums with that problem. I have a similar one (probably related):

I've build a custom 2.6.22 (standard gutsy kernel). First without initrd support, which worked with 2.6.20. But it didn't compile. So I enabled initrd support and removed the initramdisk line from the grub config, otherwise I have the above mentioned problem (busybox...).
Don't know if this helps.

platypuss72 (luke-platypuss) wrote :

i am also having the same problems with the busybox (iniframfs) fault either from live cd or i did a upgrade and still the same ...

but as the others i can boot using the 2.6.20.16 kernal no problems .....

i have tried the livecd on my laptop and the same ( i had this problem with tribe 4/5 versions too .. so just waited for the full release ) BUT when i livecd on my newer pc with a sata drive ALL ok ( the other computers are both ide )

BUT GOOD NEWS ...... i found a posting on the forums (sorry can't find again) but i did this .... and now works :-)

I've solved the problem editing /etc/initramfs-tools/modules, and adding this lines:

piix
ide_generic
ide_cd
ide_disk

# blacklist bad driver
blacklist ata_piix

# prevent unnecessary modules from being loaded (you don't need to do this)
blacklist ata_generic
blacklist libata
blacklist scsi_mod

after editing:

sudo update-initramfs -u

after reboot I have my hard disks with the old fashioned /dev/hd*, without bugs!!!

Credit for this fix goes to "Fabio Povoledo". He had it posted in a forum somewhere and I was days finding the solution. I saw a lot of people trying to fix boot issue.

Bob Smith (ubuntu-mensetmanus) wrote :

This also works for me - Thanks, platypuss72. It seems a lot slower than before, although I didn't reboot very often, and usually did other things instead of watching...

Vitaly (vbabiy86) wrote :

I got it also to work :). For me I just had to go in my bios and set load default values which would enable the floppy. Once I did that it worked fine.

I have tried with Ubuntu 7.10 Live and also with Kubuntu 7.10 Live

platypuss72 (luke-platypuss) wrote :

hey bob ...

i think the same that it seems a lot slower than feisty 7.04 ......

is it just me and bob ??????????

Bob Smith (ubuntu-mensetmanus) wrote :

Hey platypuss72,

I got some of the old zip back by getting rid of compiz and xgl.

platypuss72, I'd like to try your soluce... but I got the same problem on a fress install of Gutsy.
I have a Feisty install on another partition so I can modify /etc/initramfs-tools/modules for the Gutsy install...
but I can't submit : sudo update-initramfs -u for Gutsy because I can't even have a console.

I see some people use another kernel for Gutsy... probably because they have updated from Feisty.
In my case, is there a way to add another kernel in a fresh Gutsy install ?

Or am I sticked to Feisty until this bug will be solved ?
Or do I need to install Feisty and use the update way to get Gutsy ?

platypuss72 (luke-platypuss) wrote :

hey Eric ..

have got some good news for you ....

i have found yet more stuff to make it work .....

there are a few things i can add to the previous stuff ... if you do an update over fiesty then the boot menu still has the older kernal boot options .. so boot into the previous kernal and run the sudo update-initramfs -u ...

BUT even easrier than that you just edit the boot loader on boot ... this is what i have posted somewere else once i found it .....

and its took most of it to sort the problems out again ..
i installed ok then first boot got the busybox halt ..
so booted live cd again and added the fix to the intramfs module file .. BUT i ran the sudo update and it only updated the
live version .. tryed reboot and still nothing .. livecd and update then copy then file into the orginal file ... reboot and still faulty
so a bit more lookin in forums and found all_generic_ide that i add to the livecd F6 boot if i add it to /boot/grub/menu.lst, you will find a line like this: # kopt=root=/dev/sda1 ro

OR even easier than that ....

on the boot up screen you press "e" very quicklly ... then you can edit the menu.lst string from there ..

just find the line # kopt=root=/dev/sda1 ro and add the all_generic-ide to the end of the line before the --

next thing i have got to sort out is why gusty thinks my ide drives are scsi ??????

thats for another day ... anymore help on that give me a shout and i am willing to help as it took me about 4hrs to find and sort ..

cheeers luke

Hi platypuss72.

I formatted my whole hard drive and I was able to install Gutsy with the Gutsy LiveCD.
Probably thre was a problem when trying to reuse my /home partition...

It's a very strange bug... but now it's ok for me.

Thanks for your reply.

The Hardy Heron kernel was recently uploaded for testing. We'd really appreciate it if you could try testing with this newer kernel and verify if this issue still exists. Unfortunately, the Hardy Heron Alpha1 LiveCD was released with the older 2.6.22 kernel. You'll have to manually install the newer Hardy Heron kernel in order to test. This should not be the case for Alpha2 which is set to come out around Dec 20. However, here are the instructions to install if you choose to do so, otherwise just wait for Alpha2 to come out:

1) edit the file /etc/apt/sources.list and add the following line:

deb http://archive.ubuntu.com/ubuntu hardy main restricted

2) sudo apt-get update
3) sudo apt-get install linux-image-2.6.24-1-generic
4) reboot and select the new kernel from the grub menu

After you've tested, please feel free to revert back - ie boot into the old kernel, sudo apt-get remove linux-image-2.6.24-1-generic, and remove the line from /etc/apt/sources.list . Please update this report with your results. Thanks in advance!

Changed in linux:
status: New → Incomplete

I'm opened a new task against the actively developed kernel. However, I'm closing the report against linux-source-2.6.22 as it does not meet the criteria for a stable release update. You can learn more about the stable release update process at https://wiki.ubuntu.com/StableReleaseUpdates . Thanks!

Changed in linux-source-2.6.22:
status: New → Won't Fix
Id2ndR (id2ndr) wrote :

This bug has been resolved for me using linux 2.6.24 from hardy alpha 2 (available at http://packages.ubuntu.com/hardy/metapackages/linux-image-generic).

Otherwise: workaround from platypuss72 worked with linux 2.6.22 but the system was slower (and there was a big warning during boot process).

Hardware :
pci.product: 82801DB (ICH4) IDE Controller
pci.product_id: 9419 (0x24cb)
pci.vendor: Intel Corporation
pci.vendor_id: 32902 (0x8086)

Id2ndR, thanks for the update. I'm glad to hear things are working for you with the newer release. Vitaly, since you are the original bug reporter, can you also verify? You can download and try the new Hardy Heron Alpha2 release from http://cdimage.ubuntu.com/releases/hardy/alpha-2/ . You should be able to then test the new kernel via the LiveCD. General information regarding the release can also be found here: http://www.ubuntu.com/testing/hardy/alpha2 . Thanks!

Vitaly (vbabiy86) wrote :

I have been using Gusty and I got it to work fine, after i reset my bios. But I will also download this live cd and give it a spin and see what happens.

perhaps this is related Bug #156428 https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/156428
If it is this problem (with 2 seagate drives) the fix appears to be

static const struct drive_list_entry hpa_list[] = {
 { "ST340823A", "ALL" },
 { "ST320413A", "ALL" },
 { NULL, NULL }
};

I am working on a system with what seems like identical issues, so far feisty will install but gutsy will only upgrade from feisty, the addition of all_generic_ide to the end of the boot command in the menu.lst seems to work but
its still very slow. I think the problem is the seagate drives report a non existent sector. this causes a massive slow down in boot up times. I am going to try hardy alpha2 alternate and see if it works. It installs without issue problem with some updates but thats to be expected.

Vitaly (vbabiy86) wrote :

So I have downloaded the alpha 2 release of Ubuntu Hardy and if I don't reset my bois it drops to busy box with in the first 10 secs of booting. But If i do reset the bois then it boots perfectly.

Not sure what could cause this.

Is your BIOS up to date?

Vitaly (vbabiy86) wrote :

Yes my BIOS is update date, Sorry for taken so long to reply.

Changed in linux:
assignee: nobody → ubuntu-kernel-team
importance: Undecided → Medium
status: Incomplete → Triaged
nemesis (nemesis-bluesunset) wrote :

I also have this problem (as the first post) on my Pentium3 Server (Intel SDS2 Motherboard) with 8.04 Beta.
There are two 3ware SATA Raid-Controller (8002 and 9550SX) with two Samsung and four Seagate HDDs and one SCSI from Seagate on the Onboard-Controller.

stuckagain (disposable-thrale) wrote :

I had same BusyBox initram problem. This fixed it easily...
https://wiki.ubuntu.com/WubiGuide#head-9fe000fa2e31a632fdcf384438b2aee35076c623

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.

Thank you Leann,

i used the alternate Install-CD for hardy. I will try the LiveCD when i
have time for it. Another problem that i have generally with newer
Ubuntu releases is, that the PC shutsdown when i press Standby. There's
no suspend to ram or disk. Is there a guide avaible how to track down
this problem?

Greats,
Roland Brickl

Am Donnerstag, den 28.08.2008, 17:26 +0000 schrieb Leann Ogasawara:
> 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.
>
> ** Tags added: cft-2.6.27
>

Bob Smith (ubuntu-mensetmanus) wrote :

Alpha5 for Intrepid Ibex 8.10 live CD (desktop x86) works for me. Alpha 4 live CD worked too.

Thanks for testing and the update Bob. Vitaly, since you are the original bug reporter, care to confirm this is resolved for Intrepid? Thanks.

Changed in linux:
status: Triaged → Incomplete

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.

Stefan Bader (smb) wrote :

This bug report is being closed because we received no response to the previous inquiry for information. Please reopen if this is still an issue in the current Ubuntu release, Jaunty Jackalope 9.04 - http://www.ubuntu.com/getubuntu/download. If the issue remains in Jaunty, please test the latest upstream kernel build - https://wiki.ubuntu.com/KernelMainlineBuilds . To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

    * Set status to Won't Fix

Changed in linux (Ubuntu):
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers