[alpha4 and 5] I get a busybox on one of my computers

[Martijn van Vliet]

The desktop-cd does not boot properly, as it goes into a busybox.

My hardware:
AMD64 3200+
asus a8n sli-deluxe with nforce3 chipset
asus nvidia 6600gt 128MB ram
1GB OCZ

It is also good to note that gutsy and dapper do run fine on this pc, so it got to be something new.

[Dereck Wonnacott (dereck)]

Thank you for your time in reporting this issue. would you please clarify on what you mean however by the term 'busybox.'

[Martijn van Vliet (mvanvliet)]

Well, as i know it, the busybox is a very spartain terminal where you cannot do that much. Someone told me once that a busybox only happens when there is something seriously wrong with the computer, and seeing this does not happen with dapper nor gutsy, i thought i would be a good idea to report this.

PS.Current sidux (also debian based) also installs fine on the problem pc.

[Michael Nagel (nailor)]

thanks for reporting! but since this bug has been reported a while ago
and not been touched since i dare to ask if it still is a problem. if it
still is, please file it against a specific package so the relevant
people will have a look at it...

[Martijn van Vliet (mvanvliet)]

I am sorry, i do not know which package this would involve... i have not tested this lately, but i will try it out again with the new 8.10 release to see whether this issue seems to be fixed or not. So i will report back later.

[Michael Nagel (nailor)]

i was thinking about the final 8.04 release (and not the alpha/beta versions) :)

[Martijn van Vliet (mvanvliet)]

I tried it out and i still get the busybox...
Also, it seems like i have an nForce4 not an nForce3 chip.

[Leann Ogasawara (leannogasawara)]

Hi Martijn,

The upcoming Intrepid Ibex 8.10 Alphas were recently released. It would be helpful if you could test the latest Alpha release and verify if this is still an issue in the upcoming release - http://www.ubuntu.com/testing . You should be able to test your bug using the LiveCD. If the issue still exists, can you try booting with the 'quiet' and 'splash' options removed and see if there are any error messages output prior to dropping down to a busybox. Please let us know your results. 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.

[snirp (prinsroy)]

I can confirm the issue with my system. Both the installation and the cd-check drop into BusyBox.

System:
AMD 4850e
Gigabyte 780g

This system runs 8.04 and 7.10 just fine

[snirp (prinsroy)]

The bug arises at Kubuntu 8.10 alpha 5

[snirp (prinsroy)]

@ Leann Ogasawara
Tried the install without quiet and splash. Do not know how to reproduce the whole log, but the latest messages are repeatedly:
[21.580006] kjournald starting. Commit interval 5 seconds
[21.580006] EXT3-fs: mounted filesystem with unordered date mode

When trying >>>exit in the busybox it echos some error messages:
mounting ... on ... failed No such file.

When trying >>>exit again it produces:
(...) Kernel panic
and hangs.

[snirp (prinsroy)]

Tried memorytesting. It starts the memory test, but returns 100% failed on the individual test.

After about 30% done on the first test it hangs with the message:

" unexpected interrupt "

[snirp (prinsroy)]

Should have mentioned earlier: this bug did no longer arises since the beta stage. Did a clean install of beta1 (32 bit) and subsequently of the final realease (64 bit) without encountering it. Seems solved.