Ubuntu This forum is for the discussion of Ubuntu Linux. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
11-09-2008, 06:17 AM
|
#1
|
Member
Registered: Nov 2005
Location: Russia, republic of Bashkiria
Distribution: Slackware 12.1
Posts: 294
Rep:
|
Kubuntu Installation stops at "initramfs"
Hi guys. Decided to try K 8.10. Well, downloaded iso, burned it, rebooted. And what we see? A naked shell with (initramfs) and "help". What next? Maybe some options are needed for kernel to boot? Please give any ideas you have. Thanks.
|
|
|
11-10-2008, 01:52 AM
|
#2
|
Senior Member
Registered: Mar 2006
Posts: 1,896
Rep:
|
I'm can't advise about any boot options. But I would suggest you first check the md5sums to verify the files on your CD. I just checked an old Ubuntu CD I have and the option (presented when live CD boots) is called Check CD for Defects.
|
|
|
11-10-2008, 02:27 AM
|
#3
|
Senior Member
Registered: May 2008
Location: planet earth
Distribution: Debian
Posts: 1,732
Rep:
|
What were the last few lines written to screen before you were dumped into the shell?
There's a very good chance that all you have to do is boot with a correct parameter for "root=".
If you can mount your root partition(s) and post the contents of /etc/fstab and 'fdisk -l' we'll have a better idea of what you can do.
|
|
|
11-11-2008, 05:10 AM
|
#4
|
Member
Registered: Nov 2005
Location: Russia, republic of Bashkiria
Distribution: Slackware 12.1
Posts: 294
Original Poster
Rep:
|
There are no any "last few lines". All I get is BusyBox,(btw, what is the BusyBox?) and (initramfs).
Btw, on another machine the dvd I've burned is able to boot into Live mode with KDE4.
|
|
|
11-11-2008, 06:14 AM
|
#5
|
Senior Member
Registered: May 2008
Location: planet earth
Distribution: Debian
Posts: 1,732
Rep:
|
Can you post the output of:
fdisk -l
and also the value of the "root=" parameter in the bootloader configuration. With grub you can press a key to select what you want to boot and to display the boot parameters. I can't remember if you have to press 'e' (edit) to see the boot parameters.
'busybox' is a program which can do the job of many system programs (ls, cd, mount, cat, more, vi ...)
The 'initramfs' is a compressed 'cpio' (that's the name of the tool) archive of a basic root filesystem which can be used to get the system up and running. Once the scripts in the 'initramfs' image have done their job (which includes finding the right drivers to be able to access your essential hardware such as the disks), the final root filesystem (which has *all* your software and so on) is mounted and the real 'init' program is run - at that point all the appropriate system startup scripts in /etc/init.d are run.
For a few years now, if the boot process got far enough to run the scripts in the initramfs image but could not load the final root filesystem, the Debian start scripts dumped you into the initramfs filesystem with busybox as your main tool. Often (but not always) you can fix up the system with those limited tools available.
|
|
|
11-11-2008, 12:04 PM
|
#6
|
Member
Registered: Nov 2005
Location: Russia, republic of Bashkiria
Distribution: Slackware 12.1
Posts: 294
Original Poster
Rep:
|
Ok, tried noapic and nolapic options for boot. Installed Kubuntu then. Didn't like KDE4, too buggy and slow.
|
|
|
11-14-2008, 04:36 AM
|
#7
|
Member
Registered: Nov 2005
Location: Russia, republic of Bashkiria
Distribution: Slackware 12.1
Posts: 294
Original Poster
Rep:
|
Installed now ubuntu 8.10. All is fine except fglrx driver. I'm getting black screen after installation? What the cure is?
|
|
|
All times are GMT -5. The time now is 03:24 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|