LinuxQuestions.org
Visit the LQ Articles and Editorials section
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Debian
User Name
Password
Debian This forum is for the discussion of Debian Linux.

Notices

Reply
 
Search this Thread
Old 05-26-2004, 02:12 PM   #1
redsky
LQ Newbie
 
Registered: May 2004
Location: Portland, OR
Distribution: debian 'woody'
Posts: 23

Rep: Reputation: 15
Automatic Interface Configuration


Here's the problem. New woody install, upgraded to 2.4.26. Everything works fine, except I have to run ifconfig eth0 [ip address][netmask address] up followed by route add default gw [address] before I can get out onto my LAN and out onto the internet.

I want the NIC's drivers to load automatically, and not have to run those commands on every reboot.

/etc/modules has an entry for my driver (tulip), but supposedly the bf2.4 kernel natively supports RTL8139 network cards.

/etc/network/interfaces has an entry for auto eth0.

Anybody got any suggestions on how to get this card to be recognized and configured automatically at boot?
 
Old 05-26-2004, 02:52 PM   #2
XSnack
LQ Newbie
 
Registered: May 2004
Location: Hamburg- Germany
Distribution: Debian GNU/Linux
Posts: 4

Rep: Reputation: 0
in /etc/network/interfaces
should be something like :

auto lo eth0
iface eth0 inet static
address 192.168.1.1
netmask 255.255.255.0
gateway 192.168.1.3

man interfaces could help ;-)

HTH
 
Old 05-26-2004, 02:54 PM   #3
TigerOC
Senior Member
 
Registered: Jan 2003
Location: Devon, UK
Distribution: Debian Etc/kernel 2.6.18-4K7
Posts: 2,380

Rep: Reputation: 49
Do modconf from a consol, go down to network card drivers, install the relevant driver. Edit /etc/network/interfaces with the addresses and then do /etc/init.d/networking start. Because you changed kernels and therefore have new modules the driver is not loading.
 
Old 05-26-2004, 06:44 PM   #4
redsky
LQ Newbie
 
Registered: May 2004
Location: Portland, OR
Distribution: debian 'woody'
Posts: 23

Original Poster
Rep: Reputation: 15
That was very good information, but unfortunately it didn't work. When I went into modconf it does not list the driver module there. The driver gets loaded with ifconfig because the tulip driver is natively compiled into the bf2.4 kernel.

/etc/network/interfaces looks like this:

# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)

# The loopback interface
auto lo
iface lo inet loopback

# The first network card - this entry was created during the Debian installation
auto eth0
iface eth0 inet dhcp
address 192.168.1.3
netmask 255.0.0.0
gateway 192.168.1.1


But I think you are on the right track to solving my problem, and I suspect it is on account of the new kernel. Any more suggestions that you or anyone else may have are most welcome
 
Old 05-27-2004, 01:23 AM   #5
TigerOC
Senior Member
 
Registered: Jan 2003
Location: Devon, UK
Distribution: Debian Etc/kernel 2.6.18-4K7
Posts: 2,380

Rep: Reputation: 49
A couple of comments;
Have a look at you /var/log/syslog and find out what is happening with the netcard.

You are using dhcp and addresses should not be necessary in /etc/network/interfaces

Your netmask does not look right. I think it should be 255.255.255.0
 
Old 05-27-2004, 12:32 PM   #6
redsky
LQ Newbie
 
Registered: May 2004
Location: Portland, OR
Distribution: debian 'woody'
Posts: 23

Original Poster
Rep: Reputation: 15
You were right in your first post. I went down into /usr/src/[kernel source]/drivers/net/tulip and found tulip.o, which I then copied to /lib/modules/2.4.26/kernel/drivers/net. Then ran modconf again and got the error message that it "couldn't find the kernel version the module was compiled for," and "INstallation failed. Depmod: *** Unresolved symbols in /lib/modules/2.4.26/kernel/net/tulip.o"

So, for whatever reason, it doesn't like that tulip.o, even though it originated and was compiled totally within the installation and upgrade.

My suspicion is that I missed a necessary patch (2.4.18 maybe?). Or is it something else?
 
Old 05-27-2004, 02:40 PM   #7
TigerOC
Senior Member
 
Registered: Jan 2003
Location: Devon, UK
Distribution: Debian Etc/kernel 2.6.18-4K7
Posts: 2,380

Rep: Reputation: 49
Unresolved symbol means that it has detected that the tulip driver is from another kernel version. If you compiled the kernel then you'll have to repeat the compile and either include it in the kernel or tag it as a module.
 
Old 05-27-2004, 03:35 PM   #8
redsky
LQ Newbie
 
Registered: May 2004
Location: Portland, OR
Distribution: debian 'woody'
Posts: 23

Original Poster
Rep: Reputation: 15
Okay. I will recompile. See if that helps. But let me ask, if the tulip.o module isn't being loaded, and that's the driver for my NIC, why does the NIC operate if I run ifconfig and route add? The fact that it does operate suggests that the driver is already compiled into the kernel doesn't it?
 
  


Reply


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 Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Interested in automatic kernel configuration? APB_4 Linux - Software 10 07-01-2005 12:42 PM
Automatic script for shutting down interface RajaRC Linux - Networking 0 11-02-2004 11:23 PM
how to use automatic configuration script???? TAAN Linux - Networking 1 06-23-2004 12:28 PM
Automatic Re-configuration of X nethook Linux - Software 0 05-18-2004 08:18 AM
Automatic kernel configuration tool? MartinN Programming 6 12-26-2003 05:53 PM


All times are GMT -5. The time now is 06:14 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