Re: Can't start up the FreeBSD install disk on dual Xeon Nocona rig (itworks on other systems)
Chandler May wrote: 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? Looks like you've found the right answer there. Unfortunately you've hit Catch22: in order to fix the boot problem, you need to patch the kernel. In order to patch the kernel, you need a running system. In order to get a running system you need to fix the boot problem... Probably your best bet is to pull the disk out of your i7520 box and attach it to some other machine where you can install FreeBSD on it. At the same time try applying the patch from PR i386/74829 and building a kernel with it applied. If you can extract the patch either from the PR (http://www.freebsd.org/cgi/query-pr.cgi?pr=74829) or the e-mail you quoted, then to apply it: # cd /usr/src # patch -p 2 patch.txt Note that extracting the patch may be harder than you expect, as mailing systems and cut'n'paste tend to wrap lines or convert tabs to spaces and other such damage. Then rebuild the GENERIC kernel and install it onto your new drive. Instruction for building a kernel are here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-building.html Don't let your Gentoo experience tempt you into trying to chroot yourself onto the new drive -- while that could certainly be made to work, it's not something that gets done very often so you'ld end up having to debug things as you went along. Just use sysinstall(8) to install on the appropriate disk while it's attached to a spare system, and then boot up your spare system from that drive to do the kernel builds. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 8 Dane Court Manor School Rd PGP: http://www.infracaninophile.co.uk/pgpkey Tilmanstone Tel: +44 1304 617253 Kent, CT14 0JL UK signature.asc Description: OpenPGP digital signature
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: Keyboard Controller (i8042) port 0x64, 0x60 irq 1 on acpi0 atkbd0: AT Keyboard 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)
-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: Keyboard Controller (i8042) port 0x64, 0x60 irq 1 on acpi0 atkbd0: AT Keyboard 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 smime.p7s Description: S/MIME cryptographic signature
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: Keyboard Controller (i8042) port 0x64, 0x60 irq 1 on acpi0 atkbd0: AT Keyboard 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]
