Ubuntu 7.10 beta wont install

Asked by oddvar

I replaced Ubuntu Dapper with clean install Feisty just for testing the new Gutsy beta.
The CD boot, but nothing (as I can see, except light blinking a while in my cd-rom ) happen after I press Enter for install. So what can be the problem? md5sum give correct number

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Wrwrwr
Solved:
Last query:
Last reply:
Revision history for this message
Kiwinote (kiwinote) said :
#1

Does the system freeze, or is it just that the graphics don't work? Some hardware specifications would also be handy. I presume that you have given it enough time.

Revision history for this message
oddvar (aha5262) said :
#2

The system does freeze, and nothing happen while I wait.
I have Pentium D processor and Nvidia gforce 7100, Flatron L1753S monitor
80GB harddisk, all 4 months old.

If I can compare Boot-time for Feisty CD and Gutsy then certainly something is wrong with the beta Gutsy CD.

Revision history for this message
exactt (giesbert) said :
#3

maybe try to remove some boot options (e.g. "splash" and "quiet" ) from the kernel options to see where the live cd hangs...

Revision history for this message
oddvar (aha5262) said :
#4

How do I do that?

Revision history for this message
oddvar (aha5262) said :
#5

And where to fix kernel options in the cd?

Revision history for this message
exactt (giesbert) said :
#6

there is an option (F6 or something) in the live cd boot menu to change boot parameters ...

Revision history for this message
Wrwrwr (wrwrwr) said :
#7

Try the safe mode first, you could also try the alternate cd if this one gives you problems (alternate has just text installer, so it's not so good if you just want to try).

To edit boot options instead of clicking "start and install", you press F6, then 'e' to edit boot options, then you select the kernel line (longest) and press 'e' again. Now you can remove "quite" & "splash", or try adding some things for example "noapic" or "irqpoll".

The same happens with feisty and gutsy cds, or it's just gutsy?

Revision history for this message
oddvar (aha5262) said :
#8

Thank you. The only cd hat wont boot and install is the Gutsy beta.
On the other hand Feisty boot and install well, but there I have big problems with what I think is my graphic card. Nvidia gforce 7100. And I am forced to use low-resolution and whats more important programs like supertu and Gyachi dont work at all.
I am back to Dapper at present time, and I give it a new try october the 18th.
If it still dont function, I must consider finding another distrubution that dont mess my HW.
Btw, none of the Ubuntu distributions I have used has been able to utilize CD-RW. There is a symbol CD-RW but it turns out it can only be written once, and from there only read access.

I was higly impressed with Ubuntu when this machine was brand new, (April this year) and I installed Ubuntu Feisty for the first time. But then after a while the Video-CDs I made was unusable. Rastersoft had a fix, but it didnt function here.
So after long time trying to fix Feisty, I am back to Dapper. And I cant understand why this "old" Ubuntu is giving me a much better result than the newer one. What is an update/upgrade from Ubuntu really? Dont they test what functioned well in the old version still can be used in the new?
I have been working as a computer system programmer/maintainer for 20 years, and these things are absolute basics for any serious computer program. My platform then was IBM mainframe and mostly Cobol.

Revision history for this message
Ergosys (ergosys) said :
#9

Some comments:

The live CD is pretty slow, you might give it a longer time to start than previous versions. Let it go as long as it sounds like something is happening or if the drive light blinks. I seem to remember wondering if it was working the first time I tried it, and eventually it started up.

Some new CD drives are in need of a firmware update to work properly. Check the website of the manufacturer for an update.

Revision history for this message
oddvar (aha5262) said :
#10

Thank you. But the Gutsy beta is not bootnig beyond the start-up screen.
I tried some options in the start-up script as mentioned above. It give me a boot: prompt and after pressing enter I get msg Invalid kernel. How is that possible from a cd that has correct md5sum?
And I have waited like 30min to give the live-cd time to start, but nothing

Revision history for this message
Ergosys (ergosys) said :
#11

You say that the CD has the correct md5sum. Is this because you ran md5sum on the .iso, or did you somehow run a md5sum on the CD itself?
Did you try the "verify CD" function of the live CD? It sounds like it got to the menu with that option, right?

Revision history for this message
oddvar (aha5262) said :
#12

I run md5sum from the cd-directory, /media/cdrom0 even I cant remember now how I did it. But the md5sum was correct. As far I can remember 'ff ' something.
I will give another try for checking the cd.

Revision history for this message
Edmond Thiebaud (thiebaude) said :
#13

why not upgrade from 7.04 to 7.10 like i did.everything works great.this is the best ubuntu version to date.

Revision history for this message
Igor Guerrero (igorgue) said :
#14

Can you try with the alternate cd?

Revision history for this message
oddvar (aha5262) said :
#15

I did erase the entire HD with gconf boot CD, installed Ubuntu Feisty and tried to install Gutsy from there. But same result. Right now I download that Gutsy beta again, and will md5sum the iso when its complete.
Anyhow I am sure this is what I already did, and the cd is for one reason or another unusable.
This download just to make sure i'm not

Revision history for this message
oddvar (aha5262) said :
#16

...making any mistakes or saying wrong info

Revision history for this message
Best Wrwrwr (wrwrwr) said :
#17

Somebody reported having to use the same burner to burn and boot, and getting "Invalid or corrupted kernel" otherwise. May be worth trying a different cd/dvd, or some other burn process.

This probably won't help if the kernel is invalid , but you can pass it a lot of other things, the next most likely to help would be "all_generic_ide". You can find an almost full list here: http://www.kernel.org/pub/linux/kernel/people/gregkh/lkn/lkn_pdf/ch09.pdf.

What was the problem with the update from feisty? Most people probably take that path; it's much faster than downloading / burning / installing also.

PS: About this testing you've mentioned, i guess you're just experiencing it. ;) If you want a fully working gutsy i would give it even some more time, so everything settles. Gutsy looks good with that desktop effects and all, so maybe it's worth waiting for.

Revision history for this message
Alan (mrintegrity) said :
#18

Please don't ask for gutsy support here, it is not released yet and as such will contain many bugs. If you find a bug (like you seem to have done), you are better to file it on the gutsy bug database.

Revision history for this message
oddvar (aha5262) said :
#19

Ok, here we go again... The md5sum from iso is ffe55d31659828a5bfbdb0ec2ee78eb0 and thats correct.

Revision history for this message
exactt (giesbert) said :
#20

please also check that the cd was burned correctly by using the according option from the live cd boot menu...

Revision history for this message
oddvar (aha5262) said :
#21

How to check the cd when I dont boot? I am waiting while upgrade my Feisty to Gutsy, and it seems it might take long time.

Revision history for this message
oddvar (aha5262) said :
#22

I am upgrading from Feisty to Gutsy now, and will try to make a new cd after the 18th Oct.