How to install KUBUNTU FEISTY and not to die in the intent...?

[Guest]

After more than 50 hours no longer encounter where to read about install Kubuntu.
Please. Is somebody able to help me?
Loaded Live CD with instruction 'linux noapic nolapic', runs well.
The installation process (Swap 8 GB, root 50 GB, home 50 GB) goes well.
Finished installation, leave CD and 'intro'
and when it restarts the PC inmediatly appears the options of GURB and quickly the machine is hung, leaving in the screen the following note:
'Kernel alive
kernel direct mapping tables up to 120000000 @ 8000-e000'

Equipment:
ASUS M2N32SLI-DELUXE WIRELESS EDITION
AMD ATHLON 64 DUAL X2 CORE 5200+ 2600 Mhz
DDR2 KINGSTON PC2 4200 1GB X 4 MODULATE = 4GB
ASUS EN7600GT SILENT/2DHT/256M chip nVIDIA GEFORCE 7600GT
Serial it TIES II (300 MB/s) Seagate ST3160811AS (Barracuda 7200.9)
HL-DT-ST DVDRAM GSA-H10N
NOT more devices.
It is not installed Windows of MS.

NOTICES: Fedora Core 6 x86_64, installs and it works well.
I will thank your suggestions.
lluís

[claydoh]

Re: How to install KUBUNTU FEISTY and not to die in the intent...?

You may want to try different options as specified here:
http://ubuntuforums.org/showthread.php?t=421876,
and here
https://answers.launchpad.net/ubuntu/+question/1808
though those items in the first link are for the livecd, you can edit this directly from the grub bootloader.

Hit the Esc key when the system starts to load, and when you see the boot loader screen, highlight the top menu entry, and type 'e' to edit the options for that line. edit the line to add 'noapic', (and nolapic , though I am unsure if this will help, but since it did work on the livecd it probably won't hurt)

Then type 'b' to boot using this edited setup.

If that works, you will have to edit your /boot/grub/menu.list file. If it doesn't, then try adding 'noapic' and remove 'splash' using the method above.


It may be a long shot, but have you checked the cd for errors, using that option in the boot menu of the livecd? you may want to check that the cd image is good by checking the md5sum, and if that is good, try burning your image at a much slower speed.