Date: Sun, 26 Jul 2015 15:09:02 -0400 (EDT) From: Benjamin Kaduk <kaduk@MIT.EDU> To: HeTak <hetakcoder@gmail.com> Cc: freebsd-hackers <freebsd-hackers@freebsd.org> Subject: Re: Kernel Debug Howto Message-ID: <alpine.GSO.1.10.1507261507000.22210@multics.mit.edu> In-Reply-To: <CAGyHxXWi74-_HOw%2BhnJERBKo-5MdPNfp-NzrHmhUX4eqEhvEaw@mail.gmail.com> References: <CAGyHxXWFwU%2Ba-S62DJA==UagFFvFxwpiw0Zmht6O-ppS-ddx%2Bg@mail.gmail.com> <514DDE7F-CF61-461D-A9FF-232DC938BDF5@FreeBSD.org> <alpine.GSO.1.10.1507251552590.22210@multics.mit.edu> <CAGyHxXWi74-_HOw%2BhnJERBKo-5MdPNfp-NzrHmhUX4eqEhvEaw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 26 Jul 2015, HeTak wrote: > > To speed up the build stage, you can 'make -DKERNFAST kernel' if you ha= ve > > only made "normal" code changes. > > > =E2=80=8BI have seen this option before but I don't know what it means by= "normal" > code changes. would you please explain it to me? It is more easily explained in the things that it is not -- making changes to what the build dependencies are or how they are computed, adding new directories, and changing configuration options are all things that would make KERNFAST a bad idea. If you're just changing a couple of lines in a few source files, it should work great. -Ben From owner-freebsd-hackers@freebsd.org Sun Jul 26 18:29:46 2015 Return-Path: <owner-freebsd-hackers@freebsd.org> Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 351079AB9C0; Sun, 26 Jul 2015 18:29:46 +0000 (UTC) (envelope-from isoa@kapsi.fi) Received: from mail.kapsi.fi (mx1.kapsi.fi [IPv6:2001:1bc8:1004::1:25]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E55BD84E; Sun, 26 Jul 2015 18:29:45 +0000 (UTC) (envelope-from isoa@kapsi.fi) Received: from 91-159-11-54.elisa-laajakaista.fi ([91.159.11.54] helo=[192.168.255.112]) by mail.kapsi.fi with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <isoa@kapsi.fi>) id 1ZJQg7-0000Hz-51; Sun, 26 Jul 2015 21:29:39 +0300 Subject: Re: 10.1-RELEASE UEFI RAID0 ASUS M5A97 R2.0 AMD64 PhenomIIx6 To: CeDeROM <cederom@tlen.pl>, "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org>, freebsd-hardware@freebsd.org, freebsd-sysinstall@freebsd.org References: <CAFYkXjkCfgMjSkbJ8J8ByTaEthJai8P6Z+66UFCSWU9ph1XipQ@mail.gmail.com> From: Arto Pekkanen <isoa@kapsi.fi> X-Enigmail-Draft-Status: N1110 Message-ID: <55B5270E.5060306@kapsi.fi> Date: Sun, 26 Jul 2015 21:29:34 +0300 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 MIME-Version: 1.0 In-Reply-To: <CAFYkXjkCfgMjSkbJ8J8ByTaEthJai8P6Z+66UFCSWU9ph1XipQ@mail.gmail.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="Vpr0WEXnxjDNlCG3XDPM1u3641uFADKhG" X-SA-Exim-Connect-IP: 91.159.11.54 X-SA-Exim-Mail-From: isoa@kapsi.fi X-SA-Exim-Scanned: No (on mail.kapsi.fi); SAEximRunCond expanded to false X-Mailman-Approved-At: Sun, 26 Jul 2015 19:53:05 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD <freebsd-hackers.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-hackers>, <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers/>; List-Post: <mailto:freebsd-hackers@freebsd.org> List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sun, 26 Jul 2015 18:29:46 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --Vpr0WEXnxjDNlCG3XDPM1u3641uFADKhG Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 22.7.2015 10:57, CeDeROM wrote: > Hello there :-) >=20 > I have successfully installed and running FreeBSD 10.1-RELEASE AMD64 > on ASUS M5A97 R2.0 AMD64 PhenomIIx6 using RAID0 booting with UEFI. >=20 > UEFI and GPT seems replacement for BIOS+MBR in modern PC hardware. You > can forget about BIOS+MBR in case of UEFI which is tightly related to > hardware/firmware. >=20 > What is best about FreeBSD that I also could to the setup on older > ASUS M4A88TD/V EVO/USB3.0 which did NOT support UEFI at all. RAID0 was > possible to accomplish in 4TB size with no problem. GPT support was > already there in FreeBSD. I have installed MBR bootloader which then > switched to GPT support. This setup was not possible for Windows nor > Linux which were limited to see two 2TB devices, even on RAID. Hale to > the FreeBSD!! :-) Gratz :) Although, I think it would be possible with Linux but you would have to u= se a DIY distro like Gentoo that doesn't hide all the features behind a c= ascade of automagic system management UI-dialogs or scripts. That being s= aid, haven't done a customized Linux installation for years now, since Fr= eeBSD + documentation enable me to more easily create a customized FreeBS= D installation for spesific tasks. > However, FreeBSD Boot and Kernel seems to work somehow different on > UEFI. There is no loader menu, there is no OS prompt. There is problem > with Xorg-NVidia driver which hangs the boot process at loader (you > need to use kld_list in rc.conf instead), and then hangs the computer > somewhere on screen blank. All seems new but familiar :-) That must be because UEFI depends on kms.ko to get a framebuffer console.= In this case it would be the kms/VESA module. So probably there's some k= ind of race condition between the kms/VESA framebuffer and nVidia kmod. Have you already checked if there's any PR about this? If not, you could = make one. I am sure this could be fixed easily. > Also installing OS on UEFI is somewhat different. You need to create a > dedicated EFI partition where boot code is loaded (using dd as > presented on uefi wiki). BSDInstall creates such partition but its > only 512k in size, while boot1.efifat is 800k. I have created separate > partition that is 100M and it works fine as well. I think installed > could increase the boot partition size, and then dd the boot1.efifat > over there during install on UEFI platform..? Hmm, this is something you should definitely make a PR for, if you can. Y= our description makes it seem like the BSDInstall scripts are a bit behin= d the actual UEFI boot stack. > FreeBSD IS THE BEST!! THANK YOU!! :-) > Tomek >=20 Thank you for describing your use case. This is valuable information :) --Vpr0WEXnxjDNlCG3XDPM1u3641uFADKhG Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (MingW32) iF4EAREIAAYFAlW1JxIACgkQTBivhqtJa27TwQD8D8etc34KPc9Bw3/xjh4rjoRb LUSYIw5k2Ygz54JZs+sA/Aq2QEQG8ECfR8WkBPCAVHM6cFB4hsB4vJBWlAZ640kz =TeJ1 -----END PGP SIGNATURE----- --Vpr0WEXnxjDNlCG3XDPM1u3641uFADKhG--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.GSO.1.10.1507261507000.22210>