On Fri, 2003-04-04 at 09:11, Bob Phan wrote:
> Anyway, rants aside, the first thing that you want to do if you're using
> iptables is to go into your kernel config and under Loadable Module
> Support, make sure you *disable* set version information on all modules.
> I'm not sure why this is an issue, but there was some kernel thread way
> back in the day (you can probably find it through google) that this
> option breaks iptables sometimes.
> 
> Next, you want to re-emerge iptables after you recompile your kernel.
> Iptables uses some stuff in /usr/src/linux (oh yeah, make sure that
> symlink is pointing to your current kernel) so every time you modify
> something in your kernel reflecting areas it might touch (netfilter
> configs and whatnot) or you install a new kernel, you have to do this.
> 
> Let me know if you still have issues after trying this.


That worked great, thanks a lot Bob. Cudo's on the signature. :)

I have a new problem though(its not new ..but now that the last bug is
fixed this one is next on my list).

When I boot the box, it seems to boot absolutly fine, and right when it
is finished booting and it is just about to hand over control to X for
gdm to start up.. then tones and tones of modprobe errors for devices
that i havent configured in my kernel go scrolling down the screen.
I deleted /lib/modules/2.4.20-ck/* and remade my kernel and I still get
the same errors.

To make my kernel i do:
make deb clean bzImage modules modules_install,
then mount /boot and cp bzImage to boot, then run /sbin/lilo and reboot.

The errors look like this:
modprobe: cant locate module /dev/vttuner
modprobe: cant locate module /dev/gpmctl
modprobe: cant locate module /dev/apm_bios
modprobe: cant locate module scd* which is needed for /dev/scd* 
modprobe: cant locate module sg* which is needed for /dev/sg*

It just goes on like that for pages and pages.. but then xfree takes
control and gdm starts up, and I log in, and everything works just fine.
The weird thing is that lsmod tells me that all the modules that I
specified in /etc/modules.autoload were loaded properly.

Any ideas?










--
[EMAIL PROTECTED] mailing list

Reply via email to