Network card configuration

[svar]

I am resetting up a linux system 2.4.18 (Suse 8). This used to work
before till I had a disk crash, so now I am setting it up again. I seem to have a problem with the network config
e.g. ping says connect: Network is unreachable

I configure the network card rtl8139, except this seems
to be a buggy one, so should be set according to the
Suse database to 8139too. So I did that, but the only interface set up is lo
ifconfig gives:
lo Link encap:Local Loopback
....

ifconfig eth0 up
eth0: unknown inyterface: No such device

any ideas what I am doing wrong?
thanks, svar

 

[danielhozac]

Have you used [tt]modprobe[/tt] to get the kernel to recognize the card (if it's an ISA card) or checked the [tt]dmesg[/tt] output if it's something else? //Daniel

 

[svar]

It does not seem to have the dependencies file (modprobe)
dmesg does not seem to report anything on network card
Now?
svar

linux:/home/svar # modprobe
modprobe: Can't open dependencies file /lib/modules/2.4.18-4GB/modules.dep (No such file or directory)
linux:/home/svar # dmesg
VFS: Disk change detected on device fd(2,0)
end_request: I/O error, dev 02:00 (floppy), sector 0
VFS: Disk change detected on device fd(2,0)
end_request: I/O error, dev 02:00 (floppy), sector 0
VFS: Disk change detected on device fd(2,0)
end_request: I/O error, dev 02:00 (floppy), sector 0
VFS: Disk change detected on device fd(2,0)
end_request: I/O error, dev 02:00 (floppy), sector 0
parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE]
imm: Version 2.05 (for Linux 2.4.0)
ppa: Version 2.07 (for Linux 2.4.x)
WARNING - no ppa compatible devices found.
As of 31/Aug/1998 Iomega started shipping parallel
port ZIP drives with a different interface which is
supported by the imm (ZIP Plus) driver. If the
cable is marked with "AutoDetect", this is what has
happened.
VFS: Disk change detected on device fd(2,0)
end_request: I/O error, dev 02:00 (floppy), sector 0
VFS: Disk change detected on device fd(2,0)
end_request: I/O error, dev 02:00 (floppy), sector 0
PCI: Found IRQ 10 for device 00:0b.0
scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.5
<Adaptec 29160N Ultra160 SCSI adapter>
aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs

blk: queue c6485818, I/O limit 4095Mb (mask 0xffffffff)
Vendor: SEAGATE Model: ST336705LW Rev: 5063
Type: Direct-Access ANSI SCSI revision: 03
blk: queue c6485a18, I/O limit 4095Mb (mask 0xffffffff)
(scsi0:A:0): 160.000MB/s transfers (80.000MHz DT, offset 63, 16bit)
Vendor: SEAGATE Model: ST336705LW Rev: 5063
Type: Direct-Access ANSI SCSI revision: 03
blk: queue c6efb018, I/O limit 4095Mb (mask 0xffffffff)
(scsi0:A:1): 160.000MB/s transfers (80.000MHz DT, offset 63, 16bit)
Vendor: SEAGATE Model: ST336705LW Rev: 5063
Type: Direct-Access ANSI SCSI revision: 03
blk: queue c6efb618, I/O limit 4095Mb (mask 0xffffffff)
(scsi0:A:2): 160.000MB/s transfers (80.000MHz DT, offset 63, 16bit)
scsi0:A:0:0: Tagged Queuing enabled. Depth 253
scsi0:A:1:0: Tagged Queuing enabled. Depth 253
scsi0:A:2:0: Tagged Queuing enabled. Depth 253
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Attached scsi disk sdb at scsi0, channel 0, id 1, lun 0
Attached scsi disk sdc at scsi0, channel 0, id 2, lun 0
SCSI device sda: 71687370 512-byte hdwr sectors (36704 MB)
Partition check:
sda: sda1 sda2 sda3 sda4 < sda5 sda6 >
SCSI device sdb: 71687370 512-byte hdwr sectors (36704 MB)
sdb: sdb1
SCSI device sdc: 71687370 512-byte hdwr sectors (36704 MB)
sdc: sdc1
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
Initializing USB Mass Storage driver...
usb.c: registered new driver usb-storage
USB Mass Storage support registered.
VFS: Disk change detected on device fd(2,0)
end_request: I/O error, dev 02:00 (floppy), sector 0
VFS: Disk change detected on device fd(2,0)
end_request: I/O error, dev 02:00 (floppy), sector 0
LVM version 1.0.3(19/02/2002) module loaded
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
JFS development version: $Name: v1_0_16 $
SGI XFS with ACLs, DMAPI, realtime, quota, no debug enabled
Journalled Block Device driver loaded
raid5: measuring checksumming speed
8regs : 1736.800 MB/sec
32regs : 1284.000 MB/sec
pIII_sse : 2023.200 MB/sec
pII_mmx : 2289.200 MB/sec
p5_mmx : 2388.400 MB/sec
raid5: using function: pIII_sse (2023.200 MB/sec)
md: raid0 personality registered as nr 2
md: raid1 personality registered as nr 3
md: raid5 personality registered as nr 4
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.17, 10 Jan 2002 on sd(8,5), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.17, 10 Jan 2002 on sd(8,6), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.17, 10 Jan 2002 on sd(8,17), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.17, 10 Jan 2002 on sd(8,33), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.17, 10 Jan 2002 on sd(8,17), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.17, 10 Jan 2002 on sd(8,5), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.17, 10 Jan 2002 on sd(8,6), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.17, 10 Jan 2002 on sd(8,33), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Adding Swap: 570296k swap-space (priority -1)
VFS: Mounted root (ext2 filesystem) readonly.
change_root: old root has d_count=21
Trying to unmount old root ... okay
Freeing unused kernel memory: 120k freed
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
Adding Swap: 570296k swap-space (priority 42)
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.17, 10 Jan 2002 on sd(8,17), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.17, 10 Jan 2002 on sd(8,5), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.17, 10 Jan 2002 on sd(8,6), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.17, 10 Jan 2002 on sd(8,33), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Disk change detected on device fd(2,0)
VFS: Disk change detected on device fd(2,0)
linux:/home/svar #

 

[svar]

Oops, I forgot:
linux:/home/svar # modprobe
modprobe: Can't open dependencies file /lib/modules/2.4.18-4GB/modules.dep (No such file or directory)

happened because for some reason Suse created the
directory /lib/modules/2.4.18-64GB-SMP
instead of 2.4.18-4GB

So I made a copy of the directory and renamed it /lib/modules/2.4.18-4GB
, ran modprobe andb got back the message that /etc/modules.conf is more recent(rightly so, because
I had to change the nework card specs to 8139too)
However, modprove \* still gets confused because
it sees a kernel module version mismatch
(modules were compiler for 2.4.18-64GB-SMP while this version is 2.4.18-4GB

Any ideas?
Thanks, svar

 

[svar]

Oops, I forgot:
linux:/home/svar # modprobe
modprobe: Can't open dependencies file /lib/modules/2.4.18-4GB/modules.dep (No such file or directory)

happened because for some reason Suse created the
directory /lib/modules/2.4.18-64GB-SMP
instead of 2.4.18-4GB

So I made a copy of the directory and renamed it /lib/modules/2.4.18-4GB
, ran modprobe andb got back the message that /etc/modules.conf is more recent(rightly so, because
I had to change the nework card specs to 8139too)
However, modprove \* still gets confused because
it sees a kernel module version mismatch
(modules were compiler for 2.4.18-64GB-SMP while this version is 2.4.18-4GB

Any ideas?
Thanks, svar