checksum mismatch on hicolor-icon-theme-0.5
Hi, I've been unable to compile a very large number of programs because of a checksum mismatch on hicolor-icon-theme-0.5.tar.gz. Ports refuses to connect to any FTP or HTTP servers for the download, and will not recognize the file when I download it manually and put it in distfiles. Besides this specific port (not sure about what to call it, but port sounds right), Ports works fine. I've cvsup'd everything already to FreeBSD 5.3-CURRENT, but my initial install was 5.3-RELEASE (if that makes a difference). Is this a known bug, or could it just be a problem with my system? Chandler ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: checksum mismatch on hicolor-icon-theme-0.5
I had downloaded the latest version (hicolor-icon-themes-0.5.tar.gz), and it was even the exact same size as the file that Ports was requesting, so I didn't think that redownloading it would do any good. Well, out of desperation, I did (delete the current file and download a new one), and that fixed everything. I don't know why or how, but it did. Thanks for your help! Chandler On Thu, 23 Dec 2004 14:28:19 -0800, Kris Kennaway <[EMAIL PROTECTED]> wrote: > On Thu, Dec 23, 2004 at 12:20:26PM -0800, Chandler May wrote: > > Hi, > > > > I've been unable to compile a very large number of programs because of > > a checksum mismatch on hicolor-icon-theme-0.5.tar.gz. > > If you already have a local copy of this file, you may need to remove > it and re-fetch an updated copy. Use 'make distclean' from the port > directory to remove all distfiles for the port so you can re-fetch > them. > > > Ports refuses to > > connect to any FTP or HTTP servers for the download, > > Verify that your ports collection is complete and up-to-date. This > kind of problem is usually fixed very quickly. > > > and will not > > recognize the file when I download it manually and put it in > > distfiles. > > Are you sure you're putting it in the right directory? Compare > carefully to the error message. > > Kris > > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Can't start up the FreeBSD install disk on dual Xeon Nocona rig (it works on other systems)
Hi! I just recently switched to FreeBSD on my primary computer, an Intel Pentium 4 Prescott rig, and I'm loving it. I came from Gentoo Linux, and, if at all possible, I never want to go back. Just a few days ago I set up a dual Intel Xeon Nocona system on the Tyan i7520 (S5360) motherboard. Gentoo Linux installed flawlessly on it, but when I tried FreeBSD, the install disk stopped before it had even fully started. When I select "Verbose Logging" from the start-up menu, it stops immediately after these four lines come up: atkbdc0: port 0x64, 0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD return status:00aa I've let it run for hours, but it never gets beyond that point. I'm definitely new to FreeBSD, but I'm relatively familiar with computers in general, so the first line of that message tipped me off, and I decided to try to boot it with ACPI disabled. I did, but it still stopped. Here is the last line that was shown before it stopped: cpu0 on motherboard Does anyone know why this is happening and/or has a solution to solve it? Chandler ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Can't start up the FreeBSD install disk on dual Xeon Nocona rig (itworks on other systems)
Yes, it works fine in Gentoo Linux (with the same PS/2 keyboard I am trying to use to install FreeBSD). Chandler On Wed, 29 Dec 2004 08:57:21 +0530, Subhro <[EMAIL PROTECTED]> wrote: > > > > -Original Message- > > From: [EMAIL PROTECTED] [mailto:owner-freebsd- > > [EMAIL PROTECTED] On Behalf Of Chandler May > > Sent: Wednesday, December 29, 2004 8:28 > > To: freebsd-questions@freebsd.org > > Subject: Can't start up the FreeBSD install disk on dual Xeon Nocona rig > > (itworks on other systems) > > > > Hi! > > > > I just recently switched to FreeBSD on my primary computer, an Intel > > Pentium 4 Prescott rig, and I'm loving it. I came from Gentoo Linux, > > and, if at all possible, I never want to go back. > > > > Just a few days ago I set up a dual Intel Xeon Nocona system on the > > Tyan i7520 (S5360) motherboard. Gentoo Linux installed flawlessly on > > it, but when I tried FreeBSD, the install disk stopped before it had > > even fully started. When I select "Verbose Logging" from the start-up > > menu, it stops immediately after these four lines come up: > > > > atkbdc0: port 0x64, 0x60 irq 1 on acpi0 > > atkbd0: irq 1 on atkbdc0 > > kbdc: RESET_KBD return code:00fa > > kbdc: RESET_KBD return status:00aa > > > > I've let it run for hours, but it never gets beyond that point. I'm > > definitely new to FreeBSD, but I'm relatively familiar with computers > > in general, so the first line of that message tipped me off, and I > > decided to try to boot it with ACPI disabled. I did, but it still > > stopped. Here is the last line that was shown before it stopped: > > > > cpu0 on motherboard > > > > Does anyone know why this is happening and/or has a solution to solve it? > > > > Chandler > > ___ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to "freebsd-questions- > > [EMAIL PROTECTED]" > > Looks to me as if the keyboard controller is broken. Does this thing work or > worked recently in anything else? > > Regards > S. > > Indian Institute of Information Technology > Subhro Sankha Kar > Block AQ-13/1, Sector V > Salt Lake City > PIN 700091 > India > > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Can't start up the FreeBSD install disk on dual Xeon Nocona rig (itworks on other systems)
I found this fix on a mailing list archive using Google: http://lists.freebsd.org/pipermail/freebsd-i386/2004-December/001958.html But I have no idea how to apply it. Can anybody help out here? Chandler On Tue, 28 Dec 2004 22:11:01 -0600, Chandler May <[EMAIL PROTECTED]> wrote: > Yes, it works fine in Gentoo Linux (with the same PS/2 keyboard I am > trying to use to install FreeBSD). > > Chandler > > > On Wed, 29 Dec 2004 08:57:21 +0530, Subhro <[EMAIL PROTECTED]> wrote: > > > > > > > -Original Message- > > > From: [EMAIL PROTECTED] [mailto:owner-freebsd- > > > [EMAIL PROTECTED] On Behalf Of Chandler May > > > Sent: Wednesday, December 29, 2004 8:28 > > > To: freebsd-questions@freebsd.org > > > Subject: Can't start up the FreeBSD install disk on dual Xeon Nocona rig > > > (itworks on other systems) > > > > > > Hi! > > > > > > I just recently switched to FreeBSD on my primary computer, an Intel > > > Pentium 4 Prescott rig, and I'm loving it. I came from Gentoo Linux, > > > and, if at all possible, I never want to go back. > > > > > > Just a few days ago I set up a dual Intel Xeon Nocona system on the > > > Tyan i7520 (S5360) motherboard. Gentoo Linux installed flawlessly on > > > it, but when I tried FreeBSD, the install disk stopped before it had > > > even fully started. When I select "Verbose Logging" from the start-up > > > menu, it stops immediately after these four lines come up: > > > > > > atkbdc0: port 0x64, 0x60 irq 1 on acpi0 > > > atkbd0: irq 1 on atkbdc0 > > > kbdc: RESET_KBD return code:00fa > > > kbdc: RESET_KBD return status:00aa > > > > > > I've let it run for hours, but it never gets beyond that point. I'm > > > definitely new to FreeBSD, but I'm relatively familiar with computers > > > in general, so the first line of that message tipped me off, and I > > > decided to try to boot it with ACPI disabled. I did, but it still > > > stopped. Here is the last line that was shown before it stopped: > > > > > > cpu0 on motherboard > > > > > > Does anyone know why this is happening and/or has a solution to solve it? > > > > > > Chandler > > > ___ > > > freebsd-questions@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > > To unsubscribe, send any mail to "freebsd-questions- > > > [EMAIL PROTECTED]" > > > > Looks to me as if the keyboard controller is broken. Does this thing work or > > worked recently in anything else? > > > > Regards > > S. > > > > Indian Institute of Information Technology > > Subhro Sankha Kar > > Block AQ-13/1, Sector V > > Salt Lake City > > PIN 700091 > > India > > > > > > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ghostscript install error on 5.3-RELEASE
HI, I'm having trouble installing ghostscript-gnu on FreeBSD 5.3-RELEASE (in order to set up CUPS as a print server). It stops during compilation. make install distclean > gs_install_error only sent part of the output that I saw to the file "gs_install_error". Hopefully, the rest of it is not needed for troubleshooting. If it is needed, could somebody advise me as to how to capture all of the output in one file? It was complaining about implicit function declarations, among a few other warnings. Please help! I've had so much trouble with FreeBSD, I almost want to go back to Linux. Chandler ===> Building for ghostscript-gnu-7.07_11 >>> in pre-build ... >>> creating directories for compilation ... >>> building gimp-print library ... gmake all-recursive gmake[1]: Entering directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6' Making all in intl gmake[2]: Entering directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/intl' gmake[2]: Nothing to be done for `all'. gmake[2]: Leaving directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/intl' Making all in include gmake[2]: Entering directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/include' Making all in gimp-print gmake[3]: Entering directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/include/gimp-print' gmake[3]: Nothing to be done for `all'. gmake[3]: Leaving directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/include/gimp-print' gmake[3]: Entering directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/include' gmake[3]: Nothing to be done for `all-am'. gmake[3]: Leaving directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/include' gmake[2]: Leaving directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/include' Making all in lib gmake[2]: Entering directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/lib' gmake[2]: Nothing to be done for `all'. gmake[2]: Leaving directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/lib' Making all in man gmake[2]: Entering directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/man' gmake[2]: Nothing to be done for `all'. gmake[2]: Leaving directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/man' Making all in src gmake[2]: Entering directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/src' Making all in printdef gmake[3]: Entering directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/src/printdef' gmake[3]: Nothing to be done for `all'. gmake[3]: Leaving directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/src/printdef' Making all in main gmake[3]: Entering directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/src/main' gmake[3]: Nothing to be done for `all'. gmake[3]: Leaving directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/src/main' Making all in escputil gmake[3]: Entering directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/src/escputil' gmake[3]: Nothing to be done for `all'. gmake[3]: Leaving directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/src/escputil' Making all in gimp gmake[3]: Entering directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/src/gimp' gmake[3]: Nothing to be done for `all'. gmake[3]: Leaving directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/src/gimp' Making all in cups gmake[3]: Entering directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/src/cups' gmake[3]: Nothing to be done for `all'. gmake[3]: Leaving directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/src/cups' Making all in foomatic gmake[3]: Entering directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/src/foomatic' gmake[3]: Nothing to be done for `all'. gmake[3]: Leaving directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/src/foomatic' Making all in ghost gmake[3]: Entering directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/src/ghost' gmake[3]: Nothing to be done for `all'. gmake[3]: Leaving directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/src/ghost' Making all in testpattern gmake[3]: Entering directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/src/testpattern' gmake[3]: Nothing to be done for `all'. gmake[3]: Leaving directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/src/testpattern' gmake[3]: Entering directory `/usr/ports/print/ghostsc
Re: ghostscript install error on 5.3-RELEASE
On Sat, 08 Jan 2005 23:58:19 +0100, Matthias Buelow <[EMAIL PROTECTED]> wrote: > Chandler May wrote: > > > troubleshooting. If it is needed, could somebody advise me as to how > > to capture all of the output in one file? It was complaining about > > implicit function declarations, among a few other warnings. > > Try >& file on csh, or >file 2>&1 on sh (and compatibles). That will > also redirect stderr into the file (instead of just stdout). > > Thanks for the tip! Here is the entire output when I try to install ghostscript-gnu (on FreeBSD 5.3-RELEASE), including errors: ===> Building for ghostscript-gnu-7.07_11 >>> in pre-build ... >>> creating directories for compilation ... >>> building gimp-print library ... gmake all-recursive gmake[1]: Entering directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6' Making all in intl gmake[2]: Entering directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/intl' gmake[2]: Nothing to be done for `all'. gmake[2]: Leaving directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/intl' Making all in include gmake[2]: Entering directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/include' Making all in gimp-print gmake[3]: Entering directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/include/gimp-print' gmake[3]: Nothing to be done for `all'. gmake[3]: Leaving directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/include/gimp-print' gmake[3]: Entering directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/include' gmake[3]: Nothing to be done for `all-am'. gmake[3]: Leaving directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/include' gmake[2]: Leaving directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/include' Making all in lib gmake[2]: Entering directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/lib' gmake[2]: Nothing to be done for `all'. gmake[2]: Leaving directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/lib' Making all in man gmake[2]: Entering directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/man' gmake[2]: Nothing to be done for `all'. gmake[2]: Leaving directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/man' Making all in src gmake[2]: Entering directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/src' Making all in printdef gmake[3]: Entering directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/src/printdef' gmake[3]: Nothing to be done for `all'. gmake[3]: Leaving directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/src/printdef' Making all in main gmake[3]: Entering directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/src/main' gmake[3]: Nothing to be done for `all'. gmake[3]: Leaving directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/src/main' Making all in escputil gmake[3]: Entering directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/src/escputil' gmake[3]: Nothing to be done for `all'. gmake[3]: Leaving directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/src/escputil' Making all in gimp gmake[3]: Entering directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/src/gimp' gmake[3]: Nothing to be done for `all'. gmake[3]: Leaving directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/src/gimp' Making all in cups gmake[3]: Entering directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/src/cups' gmake[3]: Nothing to be done for `all'. gmake[3]: Leaving directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/src/cups' Making all in foomatic gmake[3]: Entering directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/src/foomatic' gmake[3]: Nothing to be done for `all'. gmake[3]: Leaving directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/src/foomatic' Making all in ghost gmake[3]: Entering directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/src/ghost' gmake[3]: Nothing to be done for `all'. gmake[3]: Leaving directory `/usr/ports/print/ghostscript-gnu/work/ghostscript-7.07/gimp-print-4.2.6/src/ghost' Making all in testpattern gmake[3]: Entering directory `/usr/ports/print/ghost
Re: ghostscript install error on 5.3-RELEASE
On Sun, 09 Jan 2005 01:30:30 +0100, Matthias Buelow <[EMAIL PROTECTED]> wrote: > Chandler May wrote: > > > ./src/gdevl256.c:114: error: `G320x200x256' undeclared (first use in > > have you added any additional drivers, like "vgalib" in the dialog when > building the port? if so, then I'd first try it with the default > settings, unless you have a good reason to enable a particular driver > (in which case I'd file a problem report, if it then fails). > I did happen to add the vgalib and lvga256 drivers... how would I go about deleting records of the current progress, to restart the installation? Chandler ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ghostscript install error on 5.3-RELEASE
On Sat, 8 Jan 2005 20:57:33 -0600, Chandler May <[EMAIL PROTECTED]> wrote: > On Sun, 09 Jan 2005 01:30:30 +0100, Matthias Buelow <[EMAIL PROTECTED]> wrote: > > Chandler May wrote: > > > > > ./src/gdevl256.c:114: error: `G320x200x256' undeclared (first use in > > > > have you added any additional drivers, like "vgalib" in the dialog when > > building the port? if so, then I'd first try it with the default > > settings, unless you have a good reason to enable a particular driver > > (in which case I'd file a problem report, if it then fails). > > > > I did happen to add the vgalib and lvga256 drivers... how would I go > about deleting records of the current progress, to restart the > installation? > > Chandler > Never mind, I just deleted work and the ghostscript folder from distfiles... the installation is working now. So far so good - it has gotten farther than before, I think. Chandler ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
