Dave (from the UK) wrote:
> I have written an ISO of Solaris 10 update 1 to a DVD and tried to boot
> it from a PC with a single Opteron on a Tyan S895 motherboard

Correction, the motherboard is the Tyan Thunder S2895, not the S895 I said. To
be more precise, it is Tyan Thunder K8WE (S2895) S2895UA2NFRF, which is the
version with the LSI 53C1030 Ultra 320 SCSI controller

http://www.tyan.com/products/html/thunderk8we.html

I *thought* that was on the HCL, but seems I was mistaken as I can't find it!
But someone does claimed to have run Solaris 10 on it.

http://hardware.mcse.ms/archive131-2005-12-264788.html


--
Dave K MCSE.

MCSE = Minefield Consultant and Solitaire Expert.

Please note my email address changes periodically to avoid spam.
It is always of the form: month-year@domain. Hitting reply will work
for a couple of months only. Later set it manually.

Dave (from the UK) wrote:
> I have written an ISO of Solaris 10 update 1 to a DVD and tried to boot
> it from a PC with a single Opteron on a Tyan S895 motherboard and HP DVD
> writer.
>
> When the DVD is loaded and the machine powered on, I see:
>
> Loading stage2 ....
>
Have you updated the BIOS?

-
Ian Collins.

Ian Collins wrote:
> Dave (from the UK) wrote:
>
>>I have written an ISO of Solaris 10 update 1 to a DVD and tried to boot
>>it from a PC with a single Opteron on a Tyan S895 motherboard and HP DVD
>>writer.
>>
>>When the DVD is loaded and the machine powered on, I see:
>>
>>Loading stage2 ....
>>
>
> Have you updated the BIOS?
>
> -
> Ian Collins.

Yes I get the same result with the 1.02 or the recent (March 06) 1.03 release of
the BIOS.

Can anyone confirm the md5 checksum of the DVD iso image?

I unzipped the 5 parts, concatenated them together, then get this as final checksum:

% /opt/sfw/bin/gmd5sum sol-10-u1-ga-x86-dvd.iso
8ba12021b10104504c0de86e16af4e78 sol-10-u1-ga-x86-dvd.iso

A google on that checksum returned no hits. I do wish Sun would publish the md5
checksums of large downloads, so one can verify them. In the case of a DVD iso
where there are multiple parts, publishing the md5 of the complete iso would be
useful too.


--
Dave K MCSE.

MCSE = Minefield Consultant and Solitaire Expert.

Please note my email address changes periodically to avoid spam.
It is always of the form: month-year@domain. Hitting reply will work
for a couple of months only. Later set it manually.

Dave (from the UK) wrote:
>>
>> Have you updated the BIOS?
>>
>> -
>> Ian Collins.
>
>
> Yes I get the same result with the 1.02 or the recent (March 06) 1.03
> release of the BIOS.
>
> Can anyone confirm the md5 checksum of the DVD iso image?
>
> I unzipped the 5 parts, concatenated them together, then get this as
> final checksum:
>
> % /opt/sfw/bin/gmd5sum sol-10-u1-ga-x86-dvd.iso
> 8ba12021b10104504c0de86e16af4e78 sol-10-u1-ga-x86-dvd.iso
>
Odd.

/opt/sfw/bin/gmd5sum sol-10-u1-ga-x86-dvd.iso
280b0fa85e1f193bc93e036fa6e7311a sol-10-u1-ga-x86-dvd.iso

The file size should be 3276472320

I know this one's good as I've installed from it.

Maybe you put the bits together in the wrong order?

> A google on that checksum returned no hits. I do wish Sun would publish
> the md5 checksums of large downloads, so one can verify them. In the
> case of a DVD iso where there are multiple parts, publishing the md5 of
> the complete iso would be useful too.
>
One of these days they'll listen and do this.

--
Ian Collins.

Ian Collins wrote:
> Dave (from the UK) wrote:
>
>>>Have you updated the BIOS?
>>>
>>>-
>>>Ian Collins.
>>
>>
>>Yes I get the same result with the 1.02 or the recent (March 06) 1.03
>>release of the BIOS.
>>
>>Can anyone confirm the md5 checksum of the DVD iso image?
>>
>>I unzipped the 5 parts, concatenated them together, then get this as
>>final checksum:
>>
>>% /opt/sfw/bin/gmd5sum sol-10-u1-ga-x86-dvd.iso
>>8ba12021b10104504c0de86e16af4e78 sol-10-u1-ga-x86-dvd.iso
>>
>
> Odd.
>
> /opt/sfw/bin/gmd5sum sol-10-u1-ga-x86-dvd.iso
> 280b0fa85e1f193bc93e036fa6e7311a sol-10-u1-ga-x86-dvd.iso
>
> The file size should be 3276472320
>
> I know this one's good as I've installed from it.

Oh ****. That probably explains it then. The annoying thing is I have now
deleted the constituent parts, since I was a bit short of disk space.

> Maybe you put the bits together in the wrong order?

Possibly. There were not all in one directory, so it is possible I did something
silly.


>> I do wish Sun would publish
>>the md5 checksums of large downloads, so one can verify them. In the
>>case of a DVD iso where there are multiple parts, publishing the md5 of
>>the complete iso would be useful too.
>>
>
> One of these days they'll listen and do this.
>

Yes, lets up so. Has anyone with a Sun contract ever submitted such a request
formally? I really can't see the logic of providing files which are several
hundred MB is size and need to be concatenated together to make multi-GB files,
with no way to determine if there is a problem.

I might as well try Open Solaris now, as I have the parts on the disk for that,
whereas for Solaris 10 update 1 needs me to download 4 of them again.

can anyone verify these as the OpenSolaris 3/06 (x86) checksums:

385804ADD2DAC0D2C5018D59BF3DB9AE sol-nv-b33-x86-dvd-iso-a.zip
AC14323925B7E1517D2B2D3208400ABD sol-nv-b33-x86-dvd-iso-b.zip
CC02A5711241606E42EFEFFDB804B80E sol-nv-b33-x86-dvd-iso-c.zip
5BEE30B1A1CA237222A36BB670845B95 sol-nv-b33-x86-dvd-iso-d.zip
63C459CB9E7F2C2E48194D9BF9EF1C76 sol-nv-b33-x86-dvd-iso-e.zip

or these sizes:

sparrow /downloads % ls -go sol-nv-b33-x86-dvd-iso-?.zip
-rw-r--r-- 1 456043390 Apr 9 05:44 sol-nv-b33-x86-dvd-iso-a.zip
-rw-r--r-- 1 455300716 Apr 9 12:46 sol-nv-b33-x86-dvd-iso-b.zip
-rw-r--r-- 1 456195246 Apr 9 12:46 sol-nv-b33-x86-dvd-iso-c.zip
-rw------- 1 455303316 Feb 10 22:30 sol-nv-b33-x86-dvd-iso-d.zip
-rw------- 1 452923592 Feb 10 22:38 sol-nv-b33-x86-dvd-iso-e.zip

--
Dave K MCSE.

MCSE = Minefield Consultant and Solitaire Expert.

Please note my email address changes periodically to avoid spam.
It is always of the form: month-year@domain. Hitting reply will work
for a couple of months only. Later set it manually.