networking broken under my custom kernel, works under default kernel.

[coalbeeu]

I'm using debian (woody), and connect to a small home lan with a linksys card that uses the tulip driver, through a linksys cable/dsl router. I also have cable internet access through this router.

Evrything works great, and was set up pretty much automagically by the lovely debian install program. The problem arises when I try to compile my own (2.4.9) kernel. Everything compiles and boots ok, and the tulip driver is loaded but I have no network access, and can't even ping my router, under the new kernel. :confused:

Ifconfig shows eth0 as up, but lists no ip address or interface type (ie "Link encap: ethernet")for this adapter. Soo... I call ifconfig with these parameters and, bingo, The rest of the info (broadcast add., mask, mtu, etc.) shows up automatically. I can now ping my router, (yay) but still can't access the internet :mad: .

If I apt-get install kernel-image-2.4.9-k6, or any other one for that matter, and set that up, networking works fine as well, but I really do need to compile my own, for various reasons.

I'm sure I'm missing something simple, But I'm at a loss.

[bdg1983]

I also use tulip and these are some of my settings.

Forgot to say that this is also for 2.4.9

#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_NETLINK=y
# CONFIG_RTNETLINK is not set
CONFIG_NETLINK_DEV=y
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
# CONFIG_FILTER is not set
CONFIG_UNIX=y
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_INET_ECN is not set
CONFIG_SYN_COOKIES=y


#
# Network device support
#
CONFIG_NETDEVICES=y

#
# ARCnet devices
#
# CONFIG_ARCNET is not set
CONFIG_DUMMY=m
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_ETHERTAP is not set

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
# CONFIG_ARM_AM79C961A is not set
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_LANCE is not set
# CONFIG_NET_VENDOR_SMC is not set
# CONFIG_NET_VENDOR_RACAL is not set
# CONFIG_AT1700 is not set
# CONFIG_DEPCA is not set
# CONFIG_HP100 is not set
# CONFIG_NET_ISA is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_AC3200 is not set
# CONFIG_APRICOT is not set
# CONFIG_CS89x0 is not set
CONFIG_TULIP=m
# CONFIG_TULIP_MWI is not set
# CONFIG_TULIP_MMIO is not set
# CONFIG_DE4X5 is not set
# CONFIG_DGRS is not set
# CONFIG_DM9102 is not set
# CONFIG_EEPRO100 is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_8139TOO is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set
# CONFIG_WINBOND_840 is not set
# CONFIG_NET_POCKET is not set

[ 24 August 2001: Message edited by: mdwatts the 3rd ]

[coalbeeu]

Originally posted by mdwatts the 3rd:
<STRONG>I also use tulip and these are some of my settings.

--SNIP--

[ 24 August 2001: Message edited by: mdwatts the 3rd ]</STRONG>


What config file is that from? Keep in mind that I am still a relative newbie to linux. I use lonuxconf to set most of my config files.
:o

Yea, I know: linuxconf=baaad. But it makes things soo easy.

[ 24 August 2001: Message edited by: coalbeeu ]

[bdg1983]

The .config of my own 2.4.9 kernel.

Whenever you compile the kernel, a .config file is created with all the builtin support and modules you have selected. The example is from mine.

I would suggest you try to compile the 2.4.9 kernel again and select what I have noted.

It's always advisable to read the help available for each option.

[coalbeeu]

Possable clue:

The boot messages, from my "messed-up networking" kernel (2.4-xfs), for my ethernet card/driver contain a suspicious entry. This entry doesn't appear when I boot my "good kernels" (2.2.18, 2.4.9-k6).
Here are the relavent lines:

---------------------------------------

Linux tulip driver version 0.9.15-pre6 (july 2 2001)

pci: found irq 11 for device 00:0c.0

00:0c.0: pci cache line size set incorrectly (32 bytes) by bios/fw, correcting to 64

eth0: lite-on pnic-11 rev 37 at 0x8400, 00:A0:CC:E6:09:AE, irq 11

-----------------------------------------

(keep in mind that this is from notes. It may not be exact.)
The "cache line size" error is the suspicious line I was refering to. I'm not sure what it means or how to fix it, or if it even needs to be fixed.

--EDIT--
mdwatts: I'll take a look at my file, then, and see if that helps.
Oh, and thanks for the help, by the way. I appreciate it.

[ 24 August 2001: Message edited by: coalbeeu ]

[ 24 August 2001: Message edited by: coalbeeu ]

[bdg1983]

Glad to try and help.

Does the tulip module show up with 'lsmod'? Can you ping anything at all? i.e. ping localhost

[coalbeeu]

I can ping localhost, my router, and any other computer on my lan. Can ping nothing outside of it. Actually, I can ping nothing at all uppon booting, I first have to feed ifconfig my ip address, then my lan becomes accessable to me. Ifconfig originally shows eth0 up and running, but no ip specific info (ip address, netmask, etc) untill I call it with my ip addy.
Again, this only happens with my compiled kernels (have tried 4.4-xfs and 2.4.9). The stock kernel and the kernel images installed via apt-get work fine. :confused:

I re-compiled my kernel with networking options as you posted above, but it works no better. Was mostly the same as my own anyway.