Re: Verifing Genuine Install DVD

joev@pipeline.com adjusted his/her tin foil beanie and asbestos
underwear to write:

> How long should this take?

That can depend on lots of variables ( CPu speed, ram, dvd speed
etc... )

But really I suppose it is down to how fast the machine is, how fastthe dvd can be read and how long it takes to work out the md5`s.

How long is a piece of string ;-)

If it is taking an inordinate amount of time though it could be down
to
dirty media, DVD rom could be struggling to read the disk due to dirty

lens or slightly misaligned, DMA........

Why? how long /is/ it taking?

--
Mark
Novell Support Forums SysOp
Twixt hill and high water
N. Wales, UK.

baskitcaise wrote:

> How long is a piece of string ;-)

Twice the distance from the middle to one end
--
Bob Williams
-on his Linux box

Well I have a 3.0 processor with 1gb of ram on a 16x DVD. I don't
think
this is an issue. It still was not complete after 13 hours.

How do you rule out the disk vs the drive when evrything is brand new?


> That can depend on lots of variables ( CPu speed, ram, dvd speed
> etc... )
>
> But really I suppose it is down to how fast the machine is, how
fast
> the dvd can be read and how long it takes to work out the md5`s.
>
> How long is a piece of string ;-)
>
> If it is taking an inordinate amount of time though it could be down
to
> dirty media, DVD rom could be struggling to read the disk due to
dirty
> lens or slightly misaligned, DMA........
>
> Why? how long /is/ it taking?
>
> --
> Mark
> Novell Support Forums SysOp
> Twixt hill and high water
> N. Wales, UK.
>

joev@pipeline.com adjusted his/her tin foil beanie and asbestos
underwear to write:

> Well I have a 3.0 processor with 1gb of ram on a 16x DVD. I don't
> think this is an issue. It still was not complete after 13 hours.
>
> How do you rule out the disk vs the drive when evrything is brand
new?

One way would to get hold of a "live" CD like knoppix and see if thatcan boot and run so you can rule out the actual drive and also gauge
on
the actual performance of it.

However it should not take any longer than around 15-25 mins for the
default install, adding extra software after it is all configured andrunning.

Is the install process showing progress though or is it just stuck?

How long does it estimate it is going to take?

If it is some ridiculous time then I would be tempted to start afreshbut choose one of the other boot methods like "Safe mode" or "ACPI
disbaled" and see if that makes any difference.

Another thing ( very outside chance ) but have you got sauch a thing
as
"Cool&Quiet" turned on in the BIOS or CPU throttling?

When I first installed on this 64bit machine I was experiencing a slow

install and poor performance ( not anywhere as slow as you are ), it
was not till I realised that the machine had throttled back the CPU to

only 800 instead of 2250Mhz, I just went into the BIOS and set
everything to max performance and turned off anything related to power

save and such, this machine is on 24/7 @ 100%CPU so I do not need
anything like that except for shutdown temp just in case the fan falls

off.

HTH

--
Mark
Novell Support Forums SysOp
Twixt hill and high water
N. Wales, UK.

On Thu, 24 Mar 2005 18:12:05 GMT
joev@pipeline.com wrote:

> It still was not complete after 13 hours.
>
> How do you rule out the disk vs the drive when evrything is brand
new?

When you say 'verifying', do you mean checking md5sum, or something
similar? In that case, simply calculate an md5sum on another DVD,
preferrably a known good one, and compare the times.

If this is *not* what you mean, ignore this post! ;-)


--
Kevin Nathan (Arizona, USA)
Linux Potpourri and a.o.l.s. FAQ -- http://www.project54.com/linux/

Open standards. Open source. Open minds.
The command line is the front line.
Linux 2.6.8-24.11-default
8:34pm up 47 days 8:30, 11 users, load average: 0.10, 0.28, 0.30

> However it should not take any longer than around 15-25 mins for the

> default install, adding extra software after it is all configured
and
> running.
>
> Is the install process showing progress though or is it just stuck?>
> How long does it estimate it is going to take?

Well, my BIOS did have some CPU throttling that I turned it off.
Things did
run faster. The DVD did finish verifing without any errors.

I strated a fesh install with just the basic KDE install. At 7 hours,
the
slider bar was still sayiing three-quarters to install and 2 hours
remaining.

> If it is some ridiculous time then I would be tempted to start
afresh
> but choose one of the other boot methods like "Safe mode" or "ACPI
> disbaled" and see if that makes any difference.
>
What is the advantage or disadvantage of using these other modes? Thedocumentation really does not explain why it would be better or not.

joev@pipeline.com adjusted his/her tin foil beanie and asbestos
underwear to write:

>
>> However it should not take any longer than around 15-25 mins for
the
>> default install, adding extra software after it is all configured
and
>> running.
>>
>> Is the install process showing progress though or is it just stuck?

>>
>> How long does it estimate it is going to take?
>
> Well, my BIOS did have some CPU throttling that I turned it off.
> Things did run faster. The DVD did finish verifing without any
errors.
>
> I strated a fesh install with just the basic KDE install. At 7
hours,
> the slider bar was still sayiing three-quarters to install and 2
hours
> remaining.
>
>> If it is some ridiculous time then I would be tempted to start
afresh
>> but choose one of the other boot methods like "Safe mode" or "ACPI>> disbaled" and see if that makes any difference.
>>
> What is the advantage or disadvantage of using these other modes?
The
> documentation really does not explain why it would be better or not.


Some motherboard BIOSes are not standard or have implementations thatare broken and using different settings can get round the
shortcomings,
ACPI is one of the biggest bugbears and can really mess up the IRQ`s
and such.

7 hours is ridiculous, I have got 9.2 installed on an k6 II 450 and
that only took around 45 mins, even the doorstop 600 celeron here took

about the same time.

There definitely seems to be something not quite right with your
machine
somewhere.

Does it look like the DVD is struggling to read ( the light constantly

flashing instead of reading a bit then the light flashing while it
puts
it on the disk ) ?

While the install is going on press Ctrl+Alt+f10 ( or any of the
function keys, I am not sure if it is F10 during install ) you shouldsee the console with with messages scrolling up which shows the
progress of the install, if there are any IRQ timeouts or errors postthem back here, might be able to figure out what is causing the
slowdown.

HTH

--
Mark
Novell Support Forums SysOp
Twixt hill and high water
N. Wales, UK.

> While the install is going on press Ctrl+Alt+f10 ( or any of the
> function keys, I am not sure if it is F10 during install ) you
should
> see the console with with messages scrolling up which shows the
> progress of the install, if there are any IRQ timeouts or errors
post
> them back here, might be able to figure out what is causing the
> slowdown.

The only IRQ related looking errors I had during the intial console
(Ctrl+Alt+f1) are:

Disabling IRQ #11
hdb: hdb1
irq 11: nobody cared!

[<c010868c>] __report_bad_irq+0x1c/0x70

Watching the progress on the console (Ctrl+Alt+f3) I see lots of lines

refering to disabling IRQ #11 and some with
[<c010868c>] __report_bad_irq+0x1c/0x70.

Looks like the problem is my second HD with the LVM partition. I am
going
to take out my second drive, install and then add the drive back.