You some other kernel option off that all the things that are hidden depend on.

The kernel help for your wireless, which you can't see in make menuconfig shows

Code:

Intel PRO/Wireless 3945ABG/BG Network Connection (iwl3945) (IWL3945)

CONFIG_IWL3945:

Select to build the driver supporting the:

Intel PRO/Wireless 3945ABG/BG Network Connection

This driver uses the kernel's mac80211 subsystem.

In order to use this driver, you will need a microcode (uCode)
image for it. You can obtain the microcode from:

<http://intellinuxwireless.org/>.

The microcode is typically installed in /lib/firmware. You can
look in the hotplug script /etc/hotplug/firmware.agent to
determine which directory FIRMWARE_DIR is set to when the script
runs.

If you want to compile the driver as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
say M here and read <file:Documentation/kbuild/modules.txt>. The
module will be called iwl3945.

Look at the Depends on: line. Unless those options are either =y or =m the configuration option you need will be hidden.
I'm using make xconfig here to see this, which you can set to show all options, even hidden ones.

Its perfectly possible that one or more of the options you need is hidden because of something it depends on being set to =n ... and so on._________________Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

I completely forgot about you. I've been hitting my Gentoo-FreeBSD setup fairly hard for the last few days, so I took a bit of time off on a Sunday. My most humble apologies.

I did actually run your .config through my mill, and you were on target more than you were off. Where you were off, though, it was pretty scary. Such is life. My first kernel came with slackware, and I was scared to touch it in any way.

As for your /etc/fstab, that's pretty minimalist. I'm used to something more along these lines:

1) Move your .config file out of your kernel source directory.
2) Issue the command make mrproper. This is a destructive step. It returns the source to pristine condition. Unmoved .config files will be deleted!
3) Copy my .config into your source directory.
4) Issue the command make && make modules_install.
5) Install the kernel as you normally would, and reboot.
6) Once it boots, please post /var/log/dmesg so I can see how things loaded.

But yes, definitely do that in your own thread so that if you need anything else, we can go right to you. Don't forget to post the URL for that thread here.

Everyone else,

As wonky as this machine was once I did actually get back to it, I'm amazed I got anything accomplished at all. I did though. I've just uploaded .configs for 2.6.32-hardened-r146, 3.2.37-hardened, and 3.7.3-hardened in both x86 and x86_64 flavors. Enjoy!

I would do that, except that the FreeBSD kernel is so much easier to work with, it's not really worth the effort. Those who wish a custom kernel have been working with it enough that it's not a challenge. The documentation is also really good, so while it doesn't mention every little thing you should know about working with the FreeBSD kernel, it gives more than enough clues that someone given to be a geek could use to successfully configure and install their own kernel.

How long I stay with the idea of doing a Gentoo/FreeBSD hybrid depends on how long it takes to get some serious bugs removed. For now, I have X, but I'm limited to fvwm and xterm because pango refuses to finish compiling. No pango means no gtk+. No gtk+ means no Xfce4, and that is just unacceptable. I judge an operating system by how long it takes me to get a functional GUI. Gentoo takes a while, but it's worth it. FreeBSD, in its natural state takes about the same amount of time. The hybrid falls flat on its face, and while it did offer up a GUI rather quickly, the functionality of it is debatable. Without X-based file managers, what's the point of a GUI? At this point, I can only use mc (midnight commander). That's just not an acceptable situation.

Frankly, I enjoy working inside the Linux community more than what I've seen with FreeBSD. I'll still play with FreeBSD, but as long as I continue to oxygenate my blood naturally, I'll continue to be a Gentoo Linux fixture.

The hardened sources folks are always good for new source, and they don't disappoint tonight. I've just uploaded .configs for 2.6.32-hardened-r147, 3.2.37-hardened-r1, 3.7.4-gentoo, and 3.7.4-hardened in both x86 and x86_64 flavors. Enjoy!

The groundhog might think that spring is coming early, but the seeds are already here. I've just uploaded .configs for 2.6.32-hardened-r148, 3.2.37-hardened-r2, and 3.7.5-hardened in both x86 and x86_64 flavors. Enjoy!

The vanilla-sources folks were busy. I just uploaded .configs for 3.0.62, 3.4.29, and 3.7.6 in both x86 and x86_64 flavors. It was another case of getting the seeds done before the source hits portage. I love it when that happens. Enjoy!

Ah, the wonder of Gentoo and distributed computing. While this machine was moving up in FreeBSD world, hopefully not to die so soon thereafter, I was able to create seeds with a machine I got from Audiodef for helping him sort out some weirdness on his server. I still needed my main machine to distribute the files to the mirrors, as this is the machine with the right ssh key. Old laptops never die, okay, they eventually do, but that old P-4 celeron runs pretty good.

I've just uploaded .configs for 3.2.38 in both x86 and x86_64 flavors. Enjoy!

It's that time of evening. Dinner is done, so are the dishes, and portage dropped some fresh source! I've just uploaded .configs for 2.6.32-hardened-r150, 3.2.38-hardened-r1, and 3.7.8-hardened in both x86 and x86_64 flavors. Enjoy!_________________This space left intentionally blank, except for these ASCII symbols.