LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - General
User Name
Password
Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.

Notices

Reply
 
Search this Thread
Old 09-02-2007, 02:29 AM   #1
CJ Chitwood
Member
 
Registered: Dec 2006
Location: Jacksonville, FL
Distribution: Mint. Regrettably.
Posts: 127

Rep: Reputation: 16
Modules: Disagreements and unknown symbols


Okay.

I've had it.

I've spent an entire day trying to figure this one out. I've recently had to reinstall my Debian system. No big deal, just the O/S, all my irreplaceable data was safe and sound on another partition. However, I was running kernel 2.6.19.1. So I was going to try recompiling that kernel, but I figured that I might as well get the latest if I'm going to configure one from scratch.

So I got 2.6.22.5, and configured and compiled. Found some errors, reconfigured, recompiled. Did this loop about 7 times.

In the middle, I tried going back to the "old" kernel, 2.6.19.1. Same or similar problems.

Mostly, they revolve around modprobing, and the error "disagrees about version of symbol" and the other error "unknown symbol", ultimately resulting in
Code:
modprobe: WARNING: Error inserting <insert module here>: Unknown symbol in module, or unknown parameter (see dmesg)
My compile goes like this:
Code:
# cd /usr/local/src/linux-2.6.22.5
# make menuconfig
# make clean bzImage modules modules_install
# cp arch/i386/boot/bzImage /boot/bzImage-2.6.22.5-K7.x #(x = compile number)
# cp System.map /boot/System.map-2.6.22.5-K7.x
# vim /boot/grub/menu.lst  #edit to suit
(I make clean since I've compiled multiple times and want a fresh start each time. Is this correct to do?)

At the end of the make modules_install, I see it runs depmod -a. I then do the requisite copies and edits. In the past, I hadn't needed to make a symlink to System.map from the System.map-version.number, at least I didn't think I did. Is that actually necessary, or is it something some anal-retentive individual decided to start doing? Reason I ask is that I might decide to boot an older (or newer!) kernel and not want to have to redo that symlink every time. Regardless, to try to fix my problem, I even symlinked System.map this time.




Yet the error persists.

In my final config-and-compile, I configured EVERYTHING that would let me in NetFilter to be compiled into the kernel (e.g. not as modules). The only three that wouldn't were two related to h.323 which I don't use and one related to IPV6 which I don't use. Yet it still gripes.

I ignored this issue for a few days, since I was on the net and everything (mostly) was working, but I'm wondering if it's not why several little things (like, oh, having MENU SUPPORT in XFCE) aren't working. Probably unrelated, but I'm trying to pull this system up from nearly scratch so that nothing gets installed unless I actually do use and/or need it, so maybe some package isn't installed?

I believe this issue is why my Firestarter firewall can't create the mangle and nat matches in iptables, and thusly why when I start Firestarter, even with it properly "configured", I still get no packets in. It griped when it loaded certain modules, and others it could not find, but with everything in the kernel now, it should be fine. Still, when I run /etc/firestarter/firestarter.sh start, it says many times over "iptables: No chain/target/match by that name" speaking of the nat and mangle match names (found out which ones by editing the script outputs). I figured it just couldn't load certain netfilter modules, but then would that be the case with them compiled into the kernel?


It's nearly 3:30 a.m. here and I can't think any more tonight. Ask me for info and I'll post it, but PLEASE help me.

Compiling the latest unstable Firestarter from source is my very last resort. I'm not sure if that's even going to help. Please don't mention it first thing unless you know there is no other option for me.

Many, many thanks in advance!

CJ
 
Old 09-02-2007, 11:46 AM   #2
osor
HCL Maintainer
 
Registered: Jan 2006
Distribution: (H)LFS, Gentoo
Posts: 2,450

Rep: Reputation: 70
I am going to address only the issues you have with kernel compilation. First, when you get a modprobe error, what is the output of dmesg? Second, what compiler are you using? Third, are you using an initial ramdisk (perhaps unknowingly)? Sometimes, one inadvertently uses an initrd from an old installation, but with a new kernel. Also, can we see your grub.conf or menu.lst. Another thing: did your previous iptables have some custom modules patched into the kernel ( la patch-o-matic-ng)? What version of iptables are you using btw?

Finally, regarding this statement:
Quote:
Originally Posted by CJ Chitwood View Post
(I make clean since I've compiled multiple times and want a fresh start each time. Is this correct to do?)
I think it would be better to make clean prior to make menuconfig if at all (although I dont think this is the source of your problems).
 
Old 09-02-2007, 06:41 PM   #3
CJ Chitwood
Member
 
Registered: Dec 2006
Location: Jacksonville, FL
Distribution: Mint. Regrettably.
Posts: 127

Original Poster
Rep: Reputation: 16
Requested information provided...

Quote:
Originally Posted by osor View Post
I am going to address only the issues you have with kernel compilation. First, when you get a modprobe error, what is the output of dmesg? Second, what compiler are you using? Third, are you using an initial ramdisk (perhaps unknowingly)? Sometimes, one inadvertently uses an initrd from an old installation, but with a new kernel. Also, can we see your grub.conf or menu.lst. Another thing: did your previous iptables have some custom modules patched into the kernel ( la patch-o-matic-ng)? What version of iptables are you using btw?

Finally, regarding this statement:
I think it would be better to “make clean” prior to “make menuconfig” if at all (although I don’t think this is the source of your problems).

[Serenity][pts/0]
[cj][~]$ su
Password:

YOU ARE ROOT!
[Serenity][pts/0]
[root][/home/cj]# modprobe -l | grep conn
/lib/modules/2.6.22.5/kernel/net/netfilter/nf_conntrack_h323.ko
/lib/modules/2.6.22.5/kernel/net/ipv6/netfilter/nf_conntrack_ipv6.ko

YOU ARE ROOT!
[Serenity][pts/0]
[root][/home/cj]# modprobe nf_conntrack_h323
WARNING: Error inserting ipv6 (/lib/modules/2.6.22.5/kernel/net/ipv6/ipv6.ko): Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting nf_conntrack_h323 (/lib/modules/2.6.22.5/kernel/net/netfilter/nf_conntrack_h323.ko): Unknown symbol in module, or unknown parameter (see dmesg)

YOU ARE ROOT!
[Serenity][pts/0]
[root][/home/cj]# uname -a
Linux Serenity 2.6.22.5 #6 Mon Aug 27 20:16:35 EDT 2007 i686 GNU/Linux

YOU ARE ROOT!
[Serenity][pts/0]
[root][/home/cj]# gcc --version
gcc (GCC) 3.3.5 (Debian 1:3.3.5-13)
Copyright (C) 2003 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.


YOU ARE ROOT!
[Serenity][pts/0]
[root][/home/cj]#


The last 20 or so lines from `dmesg` are as follows:

ipv6: Unknown symbol xfrm_state_register_afinfo
ipv6: disagrees about version of symbol release_sock
ipv6: Unknown symbol release_sock
ipv6: disagrees about version of symbol secpath_dup
ipv6: Unknown symbol secpath_dup
nf_conntrack_h323: disagrees about version of symbol skb_copy_bits
nf_conntrack_h323: Unknown symbol skb_copy_bits
nf_conntrack_h323: Unknown symbol nf_conntrack_expect_alloc
nf_conntrack_h323: Unknown symbol nf_conntrack_expect_init
nf_conntrack_h323: Unknown symbol ip6_route_output
nf_conntrack_h323: Unknown symbol nf_conntrack_expect_put
nf_conntrack_h323: Unknown symbol nf_conntrack_expect_related
nf_conntrack_h323: Unknown symbol nf_conntrack_unexpect_related
nf_conntrack_h323: Unknown symbol nf_conntrack_helper_unregister
nf_conntrack_h323: Unknown symbol __nf_ct_refresh_acct
nf_conntrack_h323: disagrees about version of symbol ip_route_output_key
nf_conntrack_h323: Unknown symbol ip_route_output_key
nf_conntrack_h323: Unknown symbol nf_conntrack_helper_register
nf_conntrack_h323: Unknown symbol __nf_conntrack_expect_find
nf_conntrack_h323: Unknown symbol nf_ct_remove_expectations


Essentially, before this, it's just several dozen lines (all the way back in the scrollbuffer) of ipv6: disagrees and ipv6: unknown symbol errors. Now mind you, I've gone back and configured all the NetFilter items to be built-in to the kernel where I could. The H.323 and IPV6 items were the ones that would not build-in.

An excerpt from my current .config:


#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_UNIX=y
CONFIG_XFRM=y
CONFIG_XFRM_USER=y
# CONFIG_XFRM_SUB_POLICY is not set
# CONFIG_XFRM_MIGRATE is not set
CONFIG_NET_KEY=y
# CONFIG_NET_KEY_MIGRATE is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
CONFIG_IP_FIB_HASH=y
# CONFIG_IP_PNP is not set
CONFIG_NET_IPIP=m
CONFIG_NET_IPGRE=m
CONFIG_NET_IPGRE_BROADCAST=y
CONFIG_IP_MROUTE=y
CONFIG_IP_PIMSM_V1=y
CONFIG_IP_PIMSM_V2=y
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
CONFIG_INET_AH=y
CONFIG_INET_ESP=y
CONFIG_INET_IPCOMP=y
CONFIG_INET_XFRM_TUNNEL=y
CONFIG_INET_TUNNEL=y
CONFIG_INET_XFRM_MODE_TRANSPORT=y
CONFIG_INET_XFRM_MODE_TUNNEL=y
CONFIG_INET_XFRM_MODE_BEET=y
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_CUBIC=y
CONFIG_DEFAULT_TCP_CONG="cubic"
# CONFIG_TCP_MD5SIG is not set
# CONFIG_IP_VS is not set
CONFIG_IPV6=m
CONFIG_IPV6_PRIVACY=y
# CONFIG_IPV6_ROUTER_PREF is not set
# CONFIG_IPV6_OPTIMISTIC_DAD is not set
CONFIG_INET6_AH=m
CONFIG_INET6_ESP=m
CONFIG_INET6_IPCOMP=m
# CONFIG_IPV6_MIP6 is not set
CONFIG_INET6_XFRM_TUNNEL=m
CONFIG_INET6_TUNNEL=m
CONFIG_INET6_XFRM_MODE_TRANSPORT=m
CONFIG_INET6_XFRM_MODE_TUNNEL=m
CONFIG_INET6_XFRM_MODE_BEET=m
CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION=m
CONFIG_IPV6_SIT=m
CONFIG_IPV6_TUNNEL=m
CONFIG_IPV6_MULTIPLE_TABLES=y
# CONFIG_IPV6_SUBTREES is not set
CONFIG_NETWORK_SECMARK=y
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set

#
# Core Netfilter Configuration
#
CONFIG_NETFILTER_NETLINK=y
CONFIG_NETFILTER_NETLINK_QUEUE=y
CONFIG_NETFILTER_NETLINK_LOG=y
CONFIG_NF_CONNTRACK_ENABLED=y
CONFIG_NF_CONNTRACK=y
CONFIG_NF_CT_ACCT=y
CONFIG_NF_CONNTRACK_MARK=y
CONFIG_NF_CONNTRACK_SECMARK=y
CONFIG_NF_CONNTRACK_EVENTS=y
CONFIG_NF_CT_PROTO_GRE=y
CONFIG_NF_CT_PROTO_SCTP=y
CONFIG_NF_CONNTRACK_AMANDA=y
CONFIG_NF_CONNTRACK_FTP=y
CONFIG_NF_CONNTRACK_H323=m
CONFIG_NF_CONNTRACK_IRC=y
CONFIG_NF_CONNTRACK_NETBIOS_NS=y
CONFIG_NF_CONNTRACK_PPTP=y
CONFIG_NF_CONNTRACK_SANE=y
CONFIG_NF_CONNTRACK_SIP=y
CONFIG_NF_CONNTRACK_TFTP=y
CONFIG_NF_CT_NETLINK=y
CONFIG_NETFILTER_XTABLES=y
CONFIG_NETFILTER_XT_TARGET_CLASSIFY=y
CONFIG_NETFILTER_XT_TARGET_CONNMARK=y
CONFIG_NETFILTER_XT_TARGET_DSCP=y
CONFIG_NETFILTER_XT_TARGET_MARK=y
CONFIG_NETFILTER_XT_TARGET_NFQUEUE=y
CONFIG_NETFILTER_XT_TARGET_NFLOG=y
CONFIG_NETFILTER_XT_TARGET_NOTRACK=y
CONFIG_NETFILTER_XT_TARGET_SECMARK=y
CONFIG_NETFILTER_XT_TARGET_CONNSECMARK=y
CONFIG_NETFILTER_XT_TARGET_TCPMSS=m
CONFIG_NETFILTER_XT_MATCH_COMMENT=y
CONFIG_NETFILTER_XT_MATCH_CONNBYTES=y
CONFIG_NETFILTER_XT_MATCH_CONNMARK=y
CONFIG_NETFILTER_XT_MATCH_CONNTRACK=y
CONFIG_NETFILTER_XT_MATCH_DCCP=y
CONFIG_NETFILTER_XT_MATCH_DSCP=y
CONFIG_NETFILTER_XT_MATCH_ESP=y
CONFIG_NETFILTER_XT_MATCH_HELPER=y
CONFIG_NETFILTER_XT_MATCH_LENGTH=y
CONFIG_NETFILTER_XT_MATCH_LIMIT=y
CONFIG_NETFILTER_XT_MATCH_MAC=y
CONFIG_NETFILTER_XT_MATCH_MARK=y
CONFIG_NETFILTER_XT_MATCH_POLICY=y
CONFIG_NETFILTER_XT_MATCH_MULTIPORT=y
CONFIG_NETFILTER_XT_MATCH_PKTTYPE=y
CONFIG_NETFILTER_XT_MATCH_QUOTA=y
CONFIG_NETFILTER_XT_MATCH_REALM=y
CONFIG_NETFILTER_XT_MATCH_SCTP=y
CONFIG_NETFILTER_XT_MATCH_STATE=y
CONFIG_NETFILTER_XT_MATCH_STATISTIC=y
CONFIG_NETFILTER_XT_MATCH_STRING=y
CONFIG_NETFILTER_XT_MATCH_TCPMSS=y
CONFIG_NETFILTER_XT_MATCH_HASHLIMIT=m

#
# IP: Netfilter Configuration
#
CONFIG_NF_CONNTRACK_IPV4=y
CONFIG_NF_CONNTRACK_PROC_COMPAT=y
CONFIG_IP_NF_QUEUE=y
CONFIG_IP_NF_IPTABLES=y
CONFIG_IP_NF_MATCH_IPRANGE=y
CONFIG_IP_NF_MATCH_TOS=y
CONFIG_IP_NF_MATCH_RECENT=y
CONFIG_IP_NF_MATCH_ECN=y
CONFIG_IP_NF_MATCH_AH=y
CONFIG_IP_NF_MATCH_TTL=y
CONFIG_IP_NF_MATCH_OWNER=y
CONFIG_IP_NF_MATCH_ADDRTYPE=y
CONFIG_IP_NF_FILTER=y
CONFIG_IP_NF_TARGET_REJECT=y
CONFIG_IP_NF_TARGET_LOG=y
CONFIG_IP_NF_TARGET_ULOG=y
CONFIG_NF_NAT=y
CONFIG_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=y
CONFIG_IP_NF_TARGET_REDIRECT=y
CONFIG_IP_NF_TARGET_NETMAP=y
CONFIG_IP_NF_TARGET_SAME=y
CONFIG_NF_NAT_SNMP_BASIC=y
CONFIG_NF_NAT_PROTO_GRE=y
CONFIG_NF_NAT_FTP=y
CONFIG_NF_NAT_IRC=y
CONFIG_NF_NAT_TFTP=y
CONFIG_NF_NAT_AMANDA=y
CONFIG_NF_NAT_PPTP=y
CONFIG_NF_NAT_H323=m
CONFIG_NF_NAT_SIP=y
CONFIG_IP_NF_MANGLE=y
CONFIG_IP_NF_TARGET_TOS=y
CONFIG_IP_NF_TARGET_ECN=y
CONFIG_IP_NF_TARGET_TTL=y
CONFIG_IP_NF_TARGET_CLUSTERIP=y
CONFIG_IP_NF_RAW=y
CONFIG_IP_NF_ARPTABLES=y
CONFIG_IP_NF_ARPFILTER=y
CONFIG_IP_NF_ARP_MANGLE=y

#
# IPv6: Netfilter Configuration (EXPERIMENTAL)
#
CONFIG_NF_CONNTRACK_IPV6=m
CONFIG_IP6_NF_QUEUE=m
CONFIG_IP6_NF_IPTABLES=m
CONFIG_IP6_NF_MATCH_RT=m
CONFIG_IP6_NF_MATCH_OPTS=m
CONFIG_IP6_NF_MATCH_FRAG=m
CONFIG_IP6_NF_MATCH_HL=m
CONFIG_IP6_NF_MATCH_OWNER=m
CONFIG_IP6_NF_MATCH_IPV6HEADER=m
CONFIG_IP6_NF_MATCH_AH=m
CONFIG_IP6_NF_MATCH_MH=m
CONFIG_IP6_NF_MATCH_EUI64=m
CONFIG_IP6_NF_FILTER=m
CONFIG_IP6_NF_TARGET_LOG=m
CONFIG_IP6_NF_TARGET_REJECT=m
CONFIG_IP6_NF_MANGLE=m
CONFIG_IP6_NF_TARGET_HL=m
CONFIG_IP6_NF_RAW=m
CONFIG_IP_DCCP=m
CONFIG_INET_DCCP_DIAG=m
CONFIG_IP_DCCP_ACKVEC=y




I deliberately selected to disable initrd and ramdisk support because when I first started compiling my own kernels it took me forever to find a site that had the howto on building the initrd file. After that, it got to the point where every time I did a kernel build (because it really wasn't that often) I'd have to go find a HOWTO again, and often, I didn't have network support in whatever the kernel-du-jour was because I was always either on my laptop (with an axnet_cs wifi card) or on my new desktop (with an atheros wifi card), neither of which had kernel support at that time (I think the axnet might now, but I know the atheros doesn't). I'm not incredibly worried about speed, and other than that, I'm not sure what the benefit of an initrd is.

AFAIK, there is no "previous" iptables. This is a fresh install, with iptables apt-gotten from the web. Now, admittedly, there is the chance there was an iptables installed from first setup, but there should not have been anything special about it. I did find ipchains installed, and I removed it, seeing as it was a kernel 2.2 thing, but it didn't help any.

/boot/grub/menu.lst:

# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
default 0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 5

# Pretty colours
color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specifiv kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
# kopt=root=/dev/hda6 ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,6)

## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery mode) single
# altoptions=(recovery mode) single

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all

## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true

## ## End Default Options ##

#title Debian GNU/Linux, kernel 2.6.19.1.old
#root (hd0,6)
#kernel /vmlinuz-2.6.19.1.old root=/dev/hda6 ro
#savedefault
#boot

#title Debian GNU/Linux, kernel 2.6.19.1.old (recovery mode)
#root (hd0,6)
#kernel /vmlinuz-2.6.19.1.old root=/dev/hda6 ro single
#savedefault
#boot

#title Debian GNU/Linux, kernel 2.6.19.1
#root (hd0,6)
#kernel /vmlinuz-2.6.19.1 root=/dev/hda6 ro
#savedefault
#boot

#title Debian GNU/Linux, kernel 2.6.19.1 (recovery mode)
#root (hd0,6)
#kernel /vmlinuz-2.6.19.1 root=/dev/hda6 ro single
#savedefault
#boot

title Debian GNU/Linux, kernel memtest86+
root (hd0,6)
kernel /memtest86+.bin
boot

### END DEBIAN AUTOMAGIC KERNELS LIST

title Vanilla Kernel 2.6.22.5-K7.8
root (hd0,6)
kernel /bzImage-2.6.22.5-K7.6 root=/dev/hda6 ro idebus=66 dma=1 vga=a
savedefault
boot

title Vanilla Kernel 2.6.22.5-K7.8 Single-User
root (hd0,6)
kernel /bzImage-2.6.22.5-K7.7 root=/dev/hda6 ro idebus=66 dma=1 single vga=a
boot

title Vanilla Kernel 2.6.22.5-K7.6
root (hd0,6)
kernel /bzImage-2.6.22.5-K7.6 root=/dev/hda6 ro idebus=66 dma=1
boot

title Vanilla Kernel 2.6.22.5-K7.6 Single-User
root (hd0,6)
kernel /bzImage-2.6.22.5-K7.6 root=/dev/hda6 ro idebus=66 dma=1 vga=ask single
boot


# This is a divider, added to separate the menu items below from the Debian
# ones.
title Other operating systems:
root


# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/hda1
title Microsoft Windows XP Professional
root (hd0,0)
savedefault
makeactive
chainloader +1


As you can see there, I've commented out old kernels, and appropriately they do not show up in the boot-time menu. There also are no initrd entries in the file. I realize my "vga=a" line is invalid, but I correct it at boot time. It does force it to ask me for a mode though, which is why I haven't changed it yet. Doesn't affect the problem.

I'm not sure if I have a grub.conf; where would I find it? I don't see one in /boot or /etc, and `locate grub.conf` brings nothing, as is the same with `man grub.conf`.


Thank you for your time and help with this. It's much appreciated. I've been using Linux in one form or another since Mandrake 8.1 around 2001, and yet it continues to throw me these curveballs (I have to admit, it's part of why I like it).


Thanks again,

CJ
 
Old 09-02-2007, 06:45 PM   #4
CJ Chitwood
Member
 
Registered: Dec 2006
Location: Jacksonville, FL
Distribution: Mint. Regrettably.
Posts: 127

Original Poster
Rep: Reputation: 16
Hhhmmmmmm.... I feel like an idiot. Let me correct my menu.lst to boot the newest compilation of the kernel. I know I had corrected that, but it must have been one of the 7 or 8 times I got distracted by the other people in this house.

In one line, I titled the kernel as the .8 version, but I boot the .7. I'm about to fix that.
 
Old 09-02-2007, 06:59 PM   #5
CJ Chitwood
Member
 
Registered: Dec 2006
Location: Jacksonville, FL
Distribution: Mint. Regrettably.
Posts: 127

Original Poster
Rep: Reputation: 16
Sometimes you just need to talk it out with a friend.

I'm not sure what exactly I changed between my last compile and the one I quoted the .config from, but it worked. After booting my latest compiled kernel, I suddenly had errors modprobing my atheros (madwifi) drivers, which told me something was different. So I recompiled them from the madwifi source again, and now, I'm running firestarter, it's active, rules are defined, AND I'M STILL CONNECTED TO THE NET! And, connection tracking is working because it is showing me my open connections, as well as event logging, without showing errors in the console on which I opened it.





I finally feel like the system is back the way it was, functionally. Now it's just a matter of reinstalling the old software set.


Thanks!

CJ

Last edited by CJ Chitwood; 09-02-2007 at 08:00 PM.
 
Old 09-02-2007, 08:37 PM   #6
osor
HCL Maintainer
 
Registered: Jan 2006
Distribution: (H)LFS, Gentoo
Posts: 2,450

Rep: Reputation: 70
Glad to see you sorted it out.
 
  


Reply

Tags
build, compile, depmod, firestarter, iptables, kernel, modules, netfilter, symbols


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
i2c: Unknown symbols and parameters hussar Slackware 2 06-22-2008 05:49 AM
ALSA modules error unknown symbols binarybob0001 Linux - General 2 11-25-2005 03:52 AM
Sound Card Problems: Unknown Symbols Ovalteen Linux - Hardware 5 03-17-2005 06:35 AM
Unknown symbols in i2c-dev Zoombie Linux - Hardware 0 06-28-2004 02:56 AM
Pegasus: Unknown symbols on 2.6.6 kernel lrt2003 Linux - Hardware 4 06-14-2004 08:47 AM


All times are GMT -5. The time now is 09:18 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration