[gentoo-amd64] Is 2005 broken?

[gentoo-amd64] Is 2005 broken?

[Tim Ames]

I posted a message in here last week about digest verification failing and 
also in the forums and did not receive a reply.  What is happening is that 
after updating portage when I tried to emerge files and they would download 
and you could see them get larger than the amount that was written in the 
first lookup of the file.  The file would go past 100 percent and then 
sometime later it would stop and it would come up with a digest 
verification error.

So I managed to get the machine online with just a modem after a while and 
the same pattern happened.  So I started out completely from scratch and I 
just compiled 2005.0.  Everything worked out until I tried to emerge 
coldplug from a genkernel.  I got the digest verification error again.  I 
emerge sync ed again and now everthing I try to emerge gets the digest 
verification error.

I guess I'm going to have to give up and go to another distro.

I'm running an sk8v asus motherboard with an fx-51 chip.

Does any of this ring a bell with anyone?

tia

Tim



-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Is 2005 broken?

[Zac Medico]

Tim Ames wrote:
> I'm running it looks like linux-2.6.7-gentoo-r14
> I haven't been able to get online for quite a while now.  When I originally 
> compiled I was on satellite and had a network connection that enabled me to 
> download just about anything I wanted.  I didn't have ppp compiled in the 
> kernel and I kept trying to get wvdial emerged or ppp working in the 
> machine to use a serial modem for dialup as that is all I can afford right 
> now, and probably all I can get in the location I'm living in.
> The problems started trying to emerge wvdial, I downloaded manually off of 
> one of the mirrors and put the files in
> /usr/portage/distfiles and then tried to emerge them on the machine
> I started getting md5 errors trying to emerge the files that I had 
> downloaded and burned to a cd using windows xp.
> I kept trying, deleted the files, put the machine finally online using 
> another machine on dialup and setting internet connection sharing and got 
> the 64bit gentoo machine online that way.  I tried doing and emerge sync 
> several times and still kept coming up with
> this message.
> Digest verification Failed:
> /usr/portage/distfiles/any downloaded .tar.gz file here
> Reason:  failed on MD5 verification
> I kept looking through the forums tried all the suggestions, ie ... 
> changing mirrors, re downloading, rebuilding the digest
> then I downloaded the webrsync file and rewrote the whole portage tree.  I 
> still get the MD5 errors.
> When I go to emerge a file that is in /usr/portage/distfiles  I get this error
> gzip: stdin: not in gzip format
> tar: Child returned status 1
> tar: Error exit delayed from previous errors
> when I try to gunzip the file I get
> !!!ERROR: dev-libs/xplc-0.3.11 failed
> !!!Function unpack, Line 375, Exitcode 2
> !!!failure unpacking   ... yada yada
> I'm at the point where I'm ready to wipe everything out and start over again.
> Can this be fixed??
> thanks in advance
> Tim


> I posted a message in here last week about digest verification failing
> and also in the forums and did not receive a reply.  What is happening
> is that after updating portage when I tried to emerge files and they
> would download and you could see them get larger than the amount that
> was written in the first lookup of the file.  The file would go past 100
> percent and then sometime later it would stop and it would come up with
> a digest verification error.
> 
> So I managed to get the machine online with just a modem after a while
> and the same pattern happened.  So I started out completely from scratch
> and I just compiled 2005.0.  Everything worked out until I tried to
> emerge coldplug from a genkernel.  I got the digest verification error
> again.  I emerge sync ed again and now everthing I try to emerge gets
> the digest verification error.
> 
> I guess I'm going to have to give up and go to another distro.
> 
> I'm running an sk8v asus motherboard with an fx-51 chip.
> 
> Does any of this ring a bell with anyone?
> 
> tia
> 
> Tim
> 
> 

Errors with both md5 and gzip?  Can you use a separate computer to determine if the problem is with md5/gzip programs or corruption of the distfiles themselves?

Zac
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Is 2005 broken?

[Tim Ames]

At 11:44 PM 7/8/2005, you wrote:
>Errors with both md5 and gzip?  Can you use a separate computer to 
>determine if the problem is with md5/gzip programs or corruption of the 
>distfiles themselves?
>
>Zac


I was able to download the gzip from the mirror and put them in my 
/distfiles  dir  and for example I was able to do that to wvdial and emerge 
it on the system and get it working.  But I couldn't download anything from 
a mirror on the sk8v machine and emerge it on that machine.  I was able to 
start all over again move a stage 3 tarball over and run it, compile the 
kernel, but then the same problem started all over again after the first 
emerge sync.

still scratching my head

thanks

Tim

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Is 2005 broken?

[Joerg Gollnick]

Am Samstag 09 Juli 2005 08:54 schrieb Tim Ames:
> At 11:44 PM 7/8/2005, you wrote:
> >Errors with both md5 and gzip?  Can you use a separate computer to 
> >determine if the problem is with md5/gzip programs or corruption of the 
> >distfiles themselves?
> >
> >Zac
> 
> 
> I was able to download the gzip from the mirror and put them in my 
> /distfiles  dir  and for example I was able to do that to wvdial and emerge 
> it on the system and get it working.  But I couldn't download anything from 
> a mirror on the sk8v machine and emerge it on that machine.  I was able to 
> start all over again move a stage 3 tarball over and run it, compile the 
> kernel, but then the same problem started all over again after the first 
> emerge sync.
> 
> still scratching my head
> 
> thanks
> 
> Tim
> 
> -- 
> gentoo-amd64@gentoo.org mailing list
> 
> 
Hello,
please have a look on your FETCHCOMMAND / RESUMECOMMAND in /etc/make.conf. 

(emerge --info -v | grep COMMAND)

FETCHCOMMAND="/usr/bin/wget -t 5 --passive-ftp -P ${DISTDIR} ${URI}"
RESUMECOMMAND="/usr/bin/wget -c -t 5 --passive-ftp -P ${DISTDIR} ${URI}"

You should be really sure, thaht you have removed any old files from 
your /distfiles dir. I had also strange problems with a wrong RESUMECOMMAND 
and partilly download files.

To get an idea what is wrong, try to download a small packages.
Please make an emerge -f app-admin/perl-cleaner.
After that compare the 
digest  /usr/portage/app-admin/perl-cleaner/files/digest-perl-cleaner-1.01 
with thhe downloaded file.
cd /usr/portage/distfiles
md5sum perl-cleaner-1.01.tar.gz
a657d9e9264cd9f550bd2c55c1220785  perl-cleaner-1.01.tar.gz
ls -l perl-cleaner-1.01.tar.gz 
I hope this will clarify, if you have problem with downloading the file or 
with gzip/md5sum. 

Best regards Joerg

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Is 2005 broken?

[Tim Ames]

Thanks for the reply.  I updated the bios on the sk8v with the beta version 
that was posted on the asus website.

bad news got a cmos error.  Went through all the proper steps, called tech 
at asus and I fried the bios chip they
are sending me a new one, so next week I'll try this again.  But this was a 
fresh install, fresh fdisk and I did the first emerge sync and this happened.

tim

At 12:16 AM 7/9/2005, you wrote:
>Am Samstag 09 Juli 2005 08:54 schrieb Tim Ames:
> > At 11:44 PM 7/8/2005, you wrote:
> > >Errors with both md5 and gzip?  Can you use a separate computer to
> > >determine if the problem is with md5/gzip programs or corruption of the
> > >distfiles themselves?
> > >
> > >Zac
> >
> >
> > I was able to download the gzip from the mirror and put them in my
> > /distfiles  dir  and for example I was able to do that to wvdial and 
> emerge
> > it on the system and get it working.  But I couldn't download anything 
> from
> > a mirror on the sk8v machine and emerge it on that machine.  I was able to
> > start all over again move a stage 3 tarball over and run it, compile the
> > kernel, but then the same problem started all over again after the first
> > emerge sync.
> >
> > still scratching my head
> >
> > thanks
> >
> > Tim
> >
> > --
> > gentoo-amd64@gentoo.org mailing list
> >
> >
>Hello,
>please have a look on your FETCHCOMMAND / RESUMECOMMAND in /etc/make.conf.
>
>(emerge --info -v | grep COMMAND)
>
>FETCHCOMMAND="/usr/bin/wget -t 5 --passive-ftp -P ${DISTDIR} ${URI}"
>RESUMECOMMAND="/usr/bin/wget -c -t 5 --passive-ftp -P ${DISTDIR} ${URI}"
>
>You should be really sure, thaht you have removed any old files from
>your /distfiles dir. I had also strange problems with a wrong RESUMECOMMAND
>and partilly download files.
>
>To get an idea what is wrong, try to download a small packages.
>Please make an emerge -f app-admin/perl-cleaner.
>After that compare the
>digest  /usr/portage/app-admin/perl-cleaner/files/digest-perl-cleaner-1.01
>with thhe downloaded file.
>cd /usr/portage/distfiles
>md5sum perl-cleaner-1.01.tar.gz
>a657d9e9264cd9f550bd2c55c1220785  perl-cleaner-1.01.tar.gz
>ls -l perl-cleaner-1.01.tar.gz
>I hope this will clarify, if you have problem with downloading the file or
>with gzip/md5sum.
>
>Best regards Joerg
>
>--
>gentoo-amd64@gentoo.org mailing list

-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: Is 2005 broken?

[Duncan]

Tim Ames posted
<6.2.0.14.2.20050709130256.027253c8@smtp.bigsurdigital.org>, excerpted
below,  on Sat, 09 Jul 2005 13:05:25 -0700:

> Thanks for the reply.  I updated the bios on the sk8v with the beta version 
> that was posted on the asus website.
> 
> bad news got a cmos error.  Went through all the proper steps, called tech 
> at asus and I fried the bios chip they
> are sending me a new one, so next week I'll try this again.  But this was a 
> fresh install, fresh fdisk and I did the first emerge sync and this happened.

You've /gotta/ have something /seriously/ wrong with that thing!  MD5s
going crazy, a BIOS update failing (I've /never/ seen that happen unless
the power dies in the middle).  There's just too much weird stuff going on
for it to be anything but hardware!

Hopefully, it was the old BIOS, and an entirely new chip fixes it.  If
not, I'd consider switching boards or memory or CPU or SOMETHING!  If
that isn't possible, then yes, on that one, I'd say run a binary install
of /something/, because if it's that unstable, I can't believe you could
reliably compile stuff either, and if you can't do that, who's to say
/what/ you'll find yourself overwriting, so better go with precompiled
binaries.  Even then, you've no idea when it'll suddenly start overwriting
stuff on your disk, so be prepared to reinstall when needed, and keep
daily, even hourly, backups, to clean media each time so it can't
overwrite /that/ with crazy stuff!

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman in
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html


-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: Is 2005 broken?

[Nuitari]

>> Thanks for the reply.  I updated the bios on the sk8v with the beta version
>> that was posted on the asus website.
>>
>> bad news got a cmos error.  Went through all the proper steps, called tech
>> at asus and I fried the bios chip they
>> are sending me a new one, so next week I'll try this again.  But this was a
>> fresh install, fresh fdisk and I did the first emerge sync and this happened.
>
> You've /gotta/ have something /seriously/ wrong with that thing!  MD5s
> going crazy, a BIOS update failing (I've /never/ seen that happen unless
> the power dies in the middle).  There's just too much weird stuff going on
> for it to be anything but hardware!

I would also take a close look at the power supply as it can easily be the 
cause of way too many weird problems.
-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: Re: Is 2005 broken?

[Duncan]

Nuitari posted <Pine.LNX.4.63.0507091824190.15832@melchior.nuitari.net>,
excerpted below,  on Sat, 09 Jul 2005 18:25:19 -0400:

> I would also take a close look at the power supply as it can easily be the 
> cause of way too many weird problems.

Yes, tho I think I mentioned that in an earlier post.  He's got only a 450
watt, the one that came with his case, and those aren't always known to be
good to anything near the claimed rating, and often don't have UL or other
certification matching that claim up to anything even close to real
numbers.  If it's UL listed for 450 watts, he's likely OK, tho maybe
barely.  However, if it's not, the thing could be peaking at 250 watts or
less, 450 watt claim or no 450 watt claim, and that just won't cut it.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman in
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html


-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Is 2005 broken?

[Zac Medico]

Tim Ames wrote:
> At 11:44 PM 7/8/2005, you wrote:
> 
>> Errors with both md5 and gzip?  Can you use a separate computer to
>> determine if the problem is with md5/gzip programs or corruption of
>> the distfiles themselves?
>>
>> Zac
> 
> 
> 
> I was able to download the gzip from the mirror and put them in my
> /distfiles  dir  and for example I was able to do that to wvdial and
> emerge it on the system and get it working.  But I couldn't download
> anything from a mirror on the sk8v machine and emerge it on that
> machine.  I was able to start all over again move a stage 3 tarball over
> and run it, compile the kernel, but then the same problem started all
> over again after the first emerge sync.
> 
> still scratching my head
> 
> thanks
> 
> Tim
> 

When you are experiencing the problem, copy the problem tarball to another computer and check it out.  Do an md5sum and try to untar it.  This will tell you whether or not the tarball is corrupted so you can isolate the problem.

Zac
-- 
gentoo-amd64@gentoo.org mailing list