UbuntuThis 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.
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.
Are you installing from the same CD? Did you check the MDsum?
I burned 3 cd's, they did not function and then I used the MDSum to check if I had a good one.
With the next Cd with a good MDsum I had no problem. On the other hand I remember a problem with a new system where the burner didn't function correctly, the problem was over when I replaced the burner.
-- The md5sum program is included with your distro, so youprobably dont need to download or install it.
-- Download the iso and the .md5 files (for this example "VL4.0.iso" and "md5sum-vl4.0.md5")
-- Open a console and go to the directory where those files are located
-- There, type "md5sum -c md5sum-vl4.0.md5" (without quotes)
-- That command will check the fingerprint of your VL4.iso file against the fingerprint stored in md5sum-vl4.0.md5, if they match perfectly you will get a "file is OK" message, and you can be confident that the file was correctly downloaded. If the md5 values do not match then there is no point in burning that file because it is damaged.
-- If you have a slow computer, the program may take as much as a few minutes to run.
B) If the .iso file passed the mdsum integrity check , then you should try to burn the file at a different speed or use a different brand of media.
This can also help
These disable power managment, Notebooks often require them
linux noacpi
linux noapm
linux pci=noacpi
linux acpi=off
linux apm=off
C) There is an error message in the file : /var/log/mesages
See what is in it ........
ok i ran the live version, mounted my winxp drive (where i keep a copy of the iso), and did the md5sum thing you mentioned from the root terminal. i waited a while, then it returned to the prompt root@ubuntu:/home/ubuntu #
so i presume that means it is ok? in which case I'm back to square one
Originally posted by debnewb ok i ran the live version, mounted my winxp drive (where i keep a copy of the iso), and did the md5sum thing you mentioned from the root terminal. i waited a while, then it returned to the prompt root@ubuntu:/home/ubuntu #
so i presume that means it is ok? in which case I'm back to square one
It doesn't work that way.
If it said nothing than it is not ok, it should give you a number in return!.
Most linux versions can read XP but..........
3.1 Integrity check in Windows:
Download and unzip the GUI tool md5summer (http://www.md5summer.org/). Make sure you are using version 1.2.0.5 or above. The first time you run it, it asks permission to associate the extension .md5 with itself. If you agree, you just need to double-click on a .md5 file to check the integrity of the original file (as long as they are both in the same folder). Otherwise, you have to manually browse to the .md5 file within the md5summer interface, then click on the ?Verify sums? button and select the .md5 file. If you get an OK for the VL .iso image file, you can proceed to burn it as a cdrom image.
In this way you can do the MDsum check from windows. In linux it should give the same number as is stored on the site where you got the iso file from.
If on the site there is a number: ADFGH7658HL34RE
The check should give the same output, if not the iso is not verified.
CloudBuilder
Last edited by CloudBuilder; 08-23-2005 at 12:34 PM.
...
insmod /lib/modules/2.6.10-5-386/kernel/drivers/scsi/sr_mod.ko
file descriptor 3 left open
file descriptor 4 left open
file descriptor 5 left open
file descriptor 6 left open
no matching physical volumes found
file descriptor 3 left open
file descriptor 4 left open
file descriptor 5 left open
file descriptor 6 left open
no volume groups found
reading all physical volumes. this may take a while...
tar: ./var/share/man/man3/Locale: :gettext.3pm.gz: Invalid arguement
_
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.