Lost my network card 3

[skiflyer]

Run Debian... upgraded my kernel from source from 2.2 something to 2.4.22

Everything when great, was able to finally compile in my nvidia drivers and get X going on my laptop... still no sound, but that's not so important to me right now.

What is important to me, is how my eth0 disappeared. I'm a bit baffled and don't really know where to go to re-enable it. This is my ifconfig eth0 from my old boot...

eth0      Link encap:Ethernet  HWaddr 00:XX:XX:XX:XX:XX  
          inet addr:192.168.1.118  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:61 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          RX bytes:4384 (4.2 KiB)  TX bytes:342 (342.0 b)
          Interrupt:10 Base address:0x3000

With some numbers omitted... ifconfig now doesn't even show an eth0 entry. My specific error is something along the lines of device does not exist.

Thanks,
Rob

 

[danielhozac]

Did you remember to select the driver for your network card?

//Daniel

 

[skiflyer]

Chance are I didn't, but this is my problem, where do I go to select the driver for my network card? I thought I looked under the network menu but didn't see it.

I'll look again, but if it's not there, could you help me find it? I was using the command line configuration util, but am up for the graphical one if that's someone elses expertise.

-Rob

 

[thedaver]

I think danielhozac was referencing using Deb's apt-get to get the loadable module for YOUR NIC for the specific kernel. When you upgraded the kernel, the old module was unlinked.

With the module installed, you'd perhaps issue "insmod nic_driver_name" or "depmod -a"

Without a driver, you aren't going to have any impact by altering NIC config files.

Surfinbox.com Business Internet Services - National Dialup, DSL, T-1 and more.

http://www.surfinbox.com/business/

 

[skiflyer]

Oh, I thought he was referring to the kernel config... but if the thing was running before, and for that matter still runs if I choose the LinuxOLD from my boot menu, doesn't that mean the old module is still there, and I just need to reassociate it with the new kernel?

-Rob

 

[skiflyer]

Ok, so I found the network card under network devices, instead of networking... mutter... anyway, I have an eth0, don't think I have it right... but I'm at work behind so many firewalls and proxies and whatnot that I'll just have to wait until I get home to see what I did...

So I'll be back in 7 or 8 hours with an update... thanks for the help so far

-Rob

 

[skiflyer]

Ok, so now I'm so baffled, I found out it's not my work hookup, cause my old kernel still works fine... I must've just configured the new card incorrectly. Though I didn't really configure it, I just chose it...

Ok, so now here's my dmesg output... I have no idea how I got this to happen...

eth0: RealTek RTL8139 Fast Ethernet at 0xD080b800, More nums, IRQ 9
eth0: Identified 8139 chip type 'TL-8139B'

(That is in fact my card)
But then latter it gets funky
eth0: Setting 100mbps half-duplex based on auto-negotiated partner ability 40a1.

What the heck is that, and where's my IP Address... if I type ifconfig I don't have an inet addr for eth0... I'm wanting to run DHCP, but not sure if I'm running something else... ugh.

-Rob

 

[thedaver]

please paste file /etc/network/interfaces here.
please paste command 'ifconfig -a' here.
please paste command 'lsmod' here.
please paste command 'uname -a' here.


Surfinbox.com Business Internet Services - National Dialup, DSL, T-1 and more.

http://www.surfinbox.com/business/

 

[skiflyer]

Please forgive any small typos, I can't actually cut'n paste with my current setup...

/etc/network/interfaces
---------------------------
# /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
---------------------------

ifconfig -a (eth0 portion only, lo portion appears fine

eth0  Link encap: Ethernet HWaddr XX:XX:XX:XX:XX:XX
  UP BROADCAST RUNNING MULTICAST MTU:1500  Metric:1
  RX packets:664 errors:0 dropped:0 overruns: 0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:100
  RX bytes:89868 (87.7 KiB)  TX bytes:0 (0.0 b)
  Interrupt:9 Base address:0xb800

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

lsmod
-----------------------
Module   Size  Used by   Tained: P
NVdriver   945504    11  (autoclean)

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

uname -a
---------------------------
Linux debianlaptop 2.4.22 #1 SMP Mon Oct 27 08:29:26 CST 2003 i6896 unknown
----------------------------

Thanks so much for helping me out here.

-Rob

 

[danielhozac]

It's been a while since I used Debian, but in a

ps aux

do you see a dhclient or dhcpcd process running?

//Daniel

 

[skiflyer]

No, I do not... in my working 2.2 kernel I do have...

/sbin/dhclient-2.2.x -q eth0

though... so I'm guessing that's a problem?

 

[flugh]

I haven't used dhclient on my debian box. I use 'pump' like this:

pump -i eth0 -h comcast.net

I have booted the box 3 times this year, so it's been a while and may not be exactly right (not 100% sure about the -i eth0).

----
JBR

 

[skiflyer]

I'm just not sure that my DHCP connection is the whole thing, that cryptic
Setting 100mbps half-duplex based on auto-negotiated partner ability 40a1.

Is kinda making me wonder....

When I go home and access my apt sources again perhaps I'll give pump a try...

-Rob

 

[danielhozac]

That is just the network card's driver telling you that it's using 100 Mbps, half-duplex mode since that is the best thing the other end of the cable supports. Nothing to worry about.

//Daniel

 

[skiflyer]

So it's just the lack of a dhcp client then?

Is there a way to find out what the 2.2 kernel was doing and just mimicking it?

-Rob

 

[skiflyer]

Hey, everybody... here I am posting from my 2.4 kernel... odd, I downloaded and ran etherconf... and nothing worked, so I went ahead and ran pump which it had downloaded as part of etherconf... and tada, I got an IP... so now I have an easy question to help me wrap this up... how do I get it to run pump all by itself on boot?

 

[skiflyer]

Sorry for all the posts, but I'm going nuts, now my
apt-get install apache

won't work, I get a lousy

[Mon Oct 27 22:15:59 2003] [alert] apache: Could not determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
failed

When I try to start it... is this related to my earlier problem? Did I find a bad solution to get me online which is causing this to break?

Tearing my hair out!

-Rob

 

[skiflyer]

I'm getting obnoxious aren't I? Anyway, scratch that last post, I just went ahead and said forget apt, built it myself... and it's running now

Thanks for all the help people, I appreciate it so much.

-Rob

 

[flugh]

Needed to go into /etc/apache/httpd.conf and look for the ServerName line. Change it to 'localhost' or whatever your hostname is (needs to be in /etc/hosts too).

----
JBR