Welcome to the most active Linux Forum on the web.
Go Back > Forums > Linux Forums > Linux - Distributions > Fedora
User Name
Fedora This forum is for the discussion of the Fedora Project.


  Search this Thread
Old 01-17-2008, 07:31 AM   #16
Registered: Jun 2003
Location: UK
Distribution: Fedora 8, Centos 5.1
Posts: 480

Rep: Reputation: 30

Your installation DVD is probably broken. It may be due to dye seperation or maybe the original iso was bad to start with.

I take it you ran sha1sum against the iso and compared to the official checksum file that came with it?

Boot the dvd and run the media check stuff and see if all the checksums match now, it may be that they no longer do, in which case get some better discs next time.
Old 01-17-2008, 10:55 PM   #17
Registered: Dec 2007
Location: phobos, mars
Distribution: 64-bit linux mint 18.1
Posts: 221

Original Poster
Rep: Reputation: 15
good DVDs, probably

Originally Posted by v00d00101 View Post
Your installation DVD is probably broken. It may be due to dye seperation or maybe the original iso was bad to start with.

I take it you ran sha1sum against the iso and compared to the official checksum file that came with it?

Boot the dvd and run the media check stuff and see if all the checksums match now, it may be that they no longer do, in which case get some better discs next time.
Here are a few more specifics. I downloaded 32-bit and 64-bit DVD ISOs
for fedora 8 from two different sites (i remember one was georia tech).
I have two 100% identical computers (that I assembled from parts), one
with 64-bit XP and one was my old fedora Linux system. I burned DVDs
fairly often with both systems and they alway are readable on both.

I burned 8 DVDs from the ISOs - 2 copies of both of the 32-bit ISO images,
and 2 copies of both of the 64-bit ISO images (total = 8 DVD copies).
All the DVDs passed a sha1sum check.

I plugged *one* of the two SATAII drives in my Linux system into the
appropriate connector on my motherboard, and installed 64-bit fedora 8.
In fact, I installed it about 8 times. The first 4 times I let it run the test
of the DVD, the next 3 times I skipped it, and the last time I let it run.
It never found a problem. However, both 64-bit fedora 8 DVDs have been
exhibiting every problem I have described in my messages on this forum.

Then I unplugged the 64-bit fedora 8 drive, and plugged in the other
SATAII drive (difference: western digital 250GB versus hitachi 250GB).
Then I installed 32-bit fedora 8 from the second pair of DVDs, about
10 times now. Again, most times I let it test-read the DVD, but again,
the installer never encounters any problems with the DVD. I have the
exact same problems installing 32-bit fedora 8 as with the 64-bit version.

1: At least I know the workaround for the first problem. If I leave my
PCI serial port card in the computer, the installation process crashes.
Literally crashes (though it does print a "fatal error" dialog just before).
This is easy - I have removed the card from the system. Incidentally,
this is not a bad card, and not an incompatible card, because twice
when the installation is done (on both 64-bit and 32-bit fedora 8),
I configured ttyS2 and ttyS3 in minicom and it communicates just fine
with itself (it has two serial ports) and with its sister card on 64-bit XP.

2: If I select lots of packages, the installer *always* takes "forever"
to prepare the installation (downloading tons of information and files
from somewhere on the internet), then spends a couple minutes
"preparing xxx-something-xxx", then croaks and displays a dialog that
proclaims "file conflict" --- with one button that says "reboot".

Very nice. No escape, no partial install, just total disaster.
If I select nothing extra, or am careful and selective in my choices
of packages to install (and skip many things I actually do want),
then sometimes the installation completes without failure.

NOTE: It does *not* appear to be related to the raw number of
packages I choose to install. I have the distinct impression that
a couple of my successful installs have far more packages in them
than other install attempts that failed. Therefore, if I had to guess,
I would say some specific contradiction exists - which (it would seem)
the releasers presumably would have caught if they ran a test that
installed *every* available package.

3: Then finally the problem with upgrading, which appears to be
some problem with not mounting DVDs (while CDs automount okay).
On an attempt to "add/remove" software --- or accept its offer to
install the 284~875 [?security?] updates (depending on how many
packages I managed to install) - it asks me to insert "CD #1" (of the
installation CDs I think, even though the installations are on DVDs).

Note: For the first time, I just encountered my first installation that
*does* automount the DVD in the above situation! I suspect the
reason has something to do with what packages were in this install.
In other words, previous *successful* installs were all missing many
packages that I wanted to install, but didn't for fear of crashing the
installation process (via the "file conflict" error). Perhaps this time
I selected some package that makes DVD automount work. However,
I cannot imagine in my wildest dreams why anyone making a general
purpose release would omit packages necessary to automount DVDs!!!

I have yet to try to install all the other packages that I want/need.
Who knows what happens then.

If anyone "important" in/to fedora is reading this message, I very
much encourage you to encourage whoever fixes problems like this
to attempt to reproduce this behavior, and fix it. And if you can't
reproduce it, I am happy to help you/them find out why I have
these problems. I may be somewhat rusty on Linux right now, as
I have been working on a project on macroshaftware for awhile,
but I am not exactly a total dummy. I wrote a complete compiler,
debugger, software development environment with GuiDesigner on
Linux quite a while ago (still works) and 3D graphics engine, etc.
So if I have problems, semi-regular folks are gonna have problems.
Right now, I'm creating an embedded vision system with a multicore
MIPS64i SoC/CPU that will run Linux, and need to remote debug
(the development system now, and my system once built) from
the Linux-on-PC.

Thanks for help, ideas and comments.
Old 01-19-2008, 06:11 AM   #18
Registered: Dec 2007
Location: phobos, mars
Distribution: 64-bit linux mint 18.1
Posts: 221

Original Poster
Rep: Reputation: 15
vague and unreliable resolutions and conclusions

I have come to some provisional conclusions about my problems.
I submit these conclusions for any and all helpful comments, and
to forward on to whoever can fix the flaws in the distribution, IF
indeed my inferences are correct. Perhaps a big IF. You decide.

1: I do not know why, but any of the three PCI serial port cards
that I bought to remote debug with this Linux system cause the
installation process to crash. Every one, every time. I have no
idea why, but the cards are compatible with 32/64 fedora 8 Linux,
since all three can be configured once fedora 8 is installed, and
operate flawlessly under minicom (once I create the appropriate
minicom.ttyS2 and minicom.ttyS3 files in /etc via "minicom -s").

2: Once I found I could get fedora 8 to install all the packages
I want installed (given much effort and many attempts), I became
determined to *try* to figure out which package conflicts exist
that make the initial install process terminally fail and require a
reboot and total loss of all installation effort (30~60 minutes).
So I tried a successive-approximation-like attempt to zero in on
the "file conflict" that repeatedly terminated installation attempts.
I am *not-at-all* certain I found *the* "file conflict" that caused
most or all of my failed attempts, but I suspect I found one problem,
and it *might be* the crucial problem. I certainly do not know how
to interpret the following statement (of mine), but hopefully one of
you folks do. Here are the two "conflicts" I suspect nuked me:

"missing dependency: ruby needed for migemo"
"missing dependency: ruby needed for mfiler"

Okay, I don't know what migemo and mfiler are, and don't know
why I apparently selected those packages (or some packages
that require migemo/mfiler and therefore indirectly added them).
However, some of you hopefully can tell me what the above means,
and if this IS a/the source of the conflict/reboot problem, then we
should tell the masters of the fedora 8 distribution. What say you?

3: As you know, if you've been following this thread, another huge
obstacle to achieving a successful install was the apparent inability
of fedora 8 to mount my distribution DVD. This happened when
adding packages --- BOTH --- during the installation process
(when the problem caused total failure of the install process)
AND when executing "add/remove software" from the pulldown
menu on the desktop AFTER a successful (but limited) installation.

After mucking around many times, I believe I found the nature of
the phenomenon (to a moderate degree of certainty) --- namely:

A: If the DVD was already in the drive when the installer asked
for "install CD #1" (near the end of the install process, after we
have selected every package we want installed), then fedora 8
(?or the installer?) cannot automount the DVD. I removed and
reinserted the DVD dozens and dozens of times, hoping it might
"catch" one of the times --- but it never did - in this situation.
This happens during initial install AND "add/remove software"
after an installation is complete and Linux is up and running.

B: I found that --- if I was doing "add/remove software" and
I finally just "gave up" and canceled out of that portion of the
"add/remove software" process that tells me to insert "CD #1",
THEN I could insert the DVD --- and it would automount !!! :-o
Yup! It seems that IF it is waiting for the DVD to be inserted,
the DVD cannot be automounted! A self-negating-prophesy!
What the hell has the software done just prior to telling us to
insert "CD #1" - to lock up the DVD drive?

Though I didn't do this many times to be fully confident, I am
fairly sure that the DVD *would* automount if I inserted it into
the DVD drive *before* the installer asked for "CD #1" --- OR
after you give up and click the "cancel" or "i give up" button
on the installer.

Therefore, the above experiences convinces me the installer
is taking some action just before it displays the dialog that
says "insert CD #1". Is it "insisting on a CD" - and thereby
disabling the drive for DVDs? Or something else? Or what?
Any ideas?


I look forward to comments and suggestions, including who
should receive any/some/all of this information and inferences?


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
XP/Fedora8 File Sharing - can only be accessed via IP Gio Linux - Networking 1 01-10-2008 02:16 AM
connecting to Interner in fedora8 damon_hu90 Linux - Newbie 1 01-03-2008 12:59 AM
fedora8 update bearon50 Fedora 2 11-18-2007 03:49 PM
upgrade fedora7 to fedora8 seighalani Fedora 8 11-11-2007 04:14 PM
Software Sources Manager, how to add installation cd sources after deletion Lakota Mandriva 1 10-23-2003 01:39 AM > Forums > Linux Forums > Linux - Distributions > Fedora

All times are GMT -5. The time now is 05:50 AM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration