gishu.pillai@bently.com wrote:
Nopes. 8139too is the one that RHL has assigned to the device. Still won't activate Gishu
dmesg: ip_tables: (C) 2000-2002 Netfilter core team 8139too Fast Ethernet driver 0.9.25 PCI: Found IRQ 3 for device 00:12.0 divert: allocating divert_blk for eth0 eth0: RealTek RTL8139 Fast Ethernet at 0xc68abf00, 00:08:a1:5f:b6:a2, IRQ 3 eth0: Identified 8139 chip type 'RTL-8139C'
Try the 8139cp driver. modprobe -r 8139too; modprobe 8139cp
eth0: Setting 100mbps full-duplex based on auto-negotiated partner ability 41e1.
Your network card is up and running as per the above line You have probably not asigned any ip address. post the output of ifconfig eth0. jtd
Here is the output for ifconfig.
eth0 Link encap:Ethernet HWaddr 00:08:A1:5F:B6:A2 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:5 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 b) TX bytes:1710 (1.6 Kb) Interrupt:3 Base address:0xbf00
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:84 errors:0 dropped:0 overruns:0 frame:0 TX packets:84 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:5642 (5.5 Kb) TX bytes:5642 (5.5 Kb)
I ran the Internet Configuration Wizard but to no avail. Do I need to manually turn on DHCP or something ? I noticed that after the Wizard ran, the m/c on startup shows a new error on the console stating unable to bind IP or something. + what is to be done if my modem is not even detected by Linux. The last time I checked, the thing was supported until RHL 7.1 Why was this model singled out like this ? The modem works peacefully under Win98 and XP
My current Setup is M/c 1 : winXP with a lan card M/c 2 : Win98 with a lan card and a dial up modem. RHL 8 on dual boot I eventually want to remove Win98 from m/c 2 provided that everything that used to work still does.
Regards, Gishu