Re: Install with modified kernel?
On Mar 27, 2007, at 8:53 PM, Garrett Cooper wrote: jekillen wrote: On Mar 27, 2007, at 4:35 PM, [EMAIL PROTECTED] wrote: On Tue, 27 Mar 2007, jekillen wrote: Hello: Is it possible to install FreeBSD ( in this case v6.2 GENERIC RELEASE) with a modified kernel? I am having some network problems with an installation on ASUS N2M32 WS pro (AMD64) mb. I want to try installing without fire wire emulation support, which means I have to modify the kernel to eliminate it. But if I install and then modify the Kernel, it will have made its mark. Please forgive me it this seems like a stupid question. It probably is but I just want to be certain. Thanks in advance. Jeff K Jeff, Of course you can! Please read this chapter in the handbook, which describes the process in great detail: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ kernelconfig.html. As for the network problems, what exactly are you experiencing? -Garrett Hehe.. fun... it appears that I probably got myself into a real mess with the hardware I just purchased (ATI card, Soundblaster X-Fi card, Asus motherboard full of nForce stuff :(..). Oh well, I've learned my lesson I suppose *sign*. You should probably tell what you told me to the questions@ list though. I'm not the only one in the freebsd community, ya know ;)? -Garrett There's more, as a matter of fact, I should write an FYI. It involves much more than just the interface problem. Here goes: I made the mistake of thinking I could use a 64 bit PCIx SCSI adapter in PCIe slots. Now I have one MSI motherboard, AMD64 socket 939 processor and 1Gb of DDR ram I can't use the SCSI card with. So I found this ASUS ($309+) board, It has PCIx slots, two of them. I also had to get another AMD64 processor for it with AM2 slot. I also had to get another Gb of DDR2 RAM. I started assembling the thing and had trouble with the cdrom (ata) drive. It turns out that this board is picky about what ata connector it is plugged into. It is not the one that is usually right next to the power connector (20 pin). it is one further down the board and faces not up from the board but toward the front of the case. It has 3 black SATA bus connectors and 6 orange SATA connectors. I thought the black connectors where for internal drives, It turns out that they are for external drives and I should have plugged in the SATA drive I am using to boot the system into one of the orange connectors. The SCSI stuff works fine; 15k rpm with backplane adapters from 80 pin to 68 pin, I have been through this obstacle coarse before so I was already prepared. Ok, Now it was time to discover the networking problem. First was that the onboard lan is not supported directly by FreeBSD. All I got in the way of interfaces to configure by sysinstall was fwe0 (firewire ethernet emulation). I went looking for inet cards that would work in PCIe slots. The motherboard only has on standard PCI slot and I have a video card installed in it. I find the Intel cards that are made to work in PCIe lane one slots. I go to install them and one of the lane one slots is blocked physically by a copper heat sink assembly on a nearby component. I cannot use that lane one slot. I ended up putting the two Intel cards in the PCIe lane 16 slots. Now I get the system installed and go to the Apache site and get a v1.3.37 tarball and to the php site and get a v5.2.1 tarball, I go get Openssl and mod_ssl and the php gd module and a binary distribution of MySQL (first one specifically for FreeBSD that I had seen). So configure, build and install went fine accept for a few dumb mistakes on my part with Apache, but I got it together. I got all the stuff built and installed to be used with php , mcrypt, gd with freetype and all that. It went well. Then I go to build and install php. Now the next problem: Php goes all the way through the configure, make and make install without complaint. It is being built as a DSO for use with Apache, which means that a file called libphp5.so is supposed to be created and placed in Apache's libexec dir. NO FILE BY THAT NAME SHOWED UP ANY WHERE. I tried it again, same thing, I went and got a tarball I had around of php 5.1.2 and tried that, Same thing; no llibphp5.so and am talking find / -name libphp5.so -print; nothing. I have posted these problems. But the first time I mentioned on this list that I had bypassed ports to install from source I was told that if I do that do not come to this list with problem. I can really understand that and I have had specific and impatient reason from bypassing ports. But, common now, why would php configure, make and install without errors and not produce a critical file for its operation.? As a matter of fact the last few posts about this (networking) have been ignored, Actually your response has been the first on this subject (networking problem). Um... I take that back, I did get
Re: Re: Install with modified kernel?
Hello again: It is only fair to post this addenda to the message thread with this subject: From various suggestions from list responses, UUASC and I seem to remember one from this list also, that the problem could be consecutive addresses on the same subnet is what is causing the problem. I was asked by message from UUASC (Unix Users Association Of Southern California) to try changing the address. So I change it to (just for the sake of difference) 172.1.1.1 with netmask of 225.225.225.0 and I WAS able to ping the inter face successfully. was nfe0 192.168.1.16 (could ping) nfe1 192.168.1.17 (could not ping) nfe1 changed to 172.1.1.1 (now returns ping request) so that does seem to make a difference. I do not know why. But it looks like I will be able to go ahead and assign it the public ip address and it should work. Thanks Jeff K ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Install with modified kernel?
On Tue, 27 Mar 2007, jekillen wrote: Hello: Is it possible to install FreeBSD ( in this case v6.2 GENERIC RELEASE) with a modified kernel? I am having some network problems with an installation on ASUS N2M32 WS pro (AMD64) mb. I want to try installing without fire wire emulation support, which means I have to modify the kernel to eliminate it. But if I install and then modify the Kernel, it will have made its mark. Please forgive me it this seems like a stupid question. It probably is but I just want to be certain. Thanks in advance. Jeff K Jeff, Of course you can! Please read this chapter in the handbook, which describes the process in great detail: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig.html. As for the network problems, what exactly are you experiencing? -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Install with modified kernel?
jekillen wrote: On Mar 27, 2007, at 4:35 PM, [EMAIL PROTECTED] wrote: On Tue, 27 Mar 2007, jekillen wrote: Hello: Is it possible to install FreeBSD ( in this case v6.2 GENERIC RELEASE) with a modified kernel? I am having some network problems with an installation on ASUS N2M32 WS pro (AMD64) mb. I want to try installing without fire wire emulation support, which means I have to modify the kernel to eliminate it. But if I install and then modify the Kernel, it will have made its mark. Please forgive me it this seems like a stupid question. It probably is but I just want to be certain. Thanks in advance. Jeff K Jeff, Of course you can! Please read this chapter in the handbook, which describes the process in great detail: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig.html. As for the network problems, what exactly are you experiencing? -Garrett Thanks for the response; it is encouraging: I originally thought that I could use the dual enet interfaces built into the motherboard, but found out that the Marvell interfaces are not supported in v6.2. I installed two Intel cards made to work in PCIe slots. I got them install and up and running according to ifconfig. I could ping em0 and not em1. 192.168.1.16 is assigned em0 and 192.168.1.17 is assigned em1. The fwe interface was listed by ifconfig between em0 and em1. I wanted to know how to get them to load in a different order to eliminate the possibility that fwe was inter fering somehow with em1. I ended up modifying the kernel to keep it from loading fwe at all. Still had the problem. I had gotten a reference from this list to driver and patch for Nvidia inet. I installed the patch and rebuilt the kernel and then installed the drivers. I left the Intel card installed and then had a total of four interfaces, nfe0 nfe1 em0 and em1. I could only ping one when they all were up and running according to ifconfig. I took the Intel cards out so I only had the two active interfaces, nfe0 and nfe1 I could still only ping one, nfe0. This is all from local host from the shell with ping -c 1 192.168.1.16 (em0 and/or nfe0) and ping -c 1 192.168.1.17 (em1 and/ or nfe1). The same thing happens when I ping from another machine. Here is why I think that fwe might have caused the problem: When I first installed the system. that is the only interface that was offered for configuration by sysinstall. I am thinking that it may have some how set only one route from the shell to lo to the kernel to the interface and back. And fiddling with the interfaces has not changed that. First I will just try to re install the system with the Intel interfaces installed because I know they have adequate support. But I would like to disable fwe completely when I do this. Once the system is installed I can take out the Intel interface cards and install the patch and driver for the Nvidia interfaces again. I am thinking of writing a series of books vaguely along the lines of the For Dummies series, only I will call it In the Trenches With (pc hardware, javascript, php, networking, Apache configuration, Spam filtering etc etc etc, oh, and tech related mailing listsno offense intended)--(I always was curious as to why some one would call a programming IDE 'Code Warrior' hence, In The Trenches With.. Jeff K Hehe.. fun... it appears that I probably got myself into a real mess with the hardware I just purchased (ATI card, Soundblaster X-Fi card, Asus motherboard full of nForce stuff :(..). Oh well, I've learned my lesson I suppose *sign*. You should probably tell what you told me to the questions@ list though. I'm not the only one in the freebsd community, ya know ;)? -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
