Install with modified kernel?

jekillen jekillen at
Thu Mar 29 00:12:40 UTC 2007

On Mar 27, 2007, at 8:53 PM, Garrett Cooper wrote:

> jekillen wrote:
>> On Mar 27, 2007, at 4:35 PM, youshi10 at 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:
>>> < 
>>> 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  
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  
board, It has PCIx slots, two of them. I also had to get another AMD64  
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  
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  
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  
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  
complaint. It is being built as a DSO for use with Apache, which means  
a file called is supposed to be created and placed in  
again, same thing, I went and got a tarball I had around of php 5.1.2  
tried that, Same thing; no and am talking
find / -name -print;
I have posted these problems. But the first time I mentioned on this  
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  
fact the last few posts about this (networking) have been ignored,  
  your response has been the first on this subject (networking problem).
Um... I take that back, I did get reference links to the patch and  
for the Nvidia interfaces. I was not planning on getting into kernel
modification, but necessity pressed me in that direction. I even
had a problem the first time. I had commented out a bunch or
wireless networking related stuff and the build failed. I did not
at first understand what all the errors were about but after picking
over them and recognizing numerous references to IEEE80211, I
deduced that that was the wireless stuff I had eliminated. It effected
the compilation of the USB stuff, where the errors occurred.  So I  
that I got all the stuff in place for the Nvidia interfaces. I have  
the situation as it stand.
Are you beginning to see why; "In The Trenches With Tech related
Mailing LIsts (and other tech related subjects)"?

More information about the freebsd-questions mailing list