I have looked at other threads relating to this issue and have tried their suggestions there, but to no avail :-(

I have a fresh installation of Official Mandrake 10.0. I had some problems installing from the disks I downloaded (they complained about missing packages, as I recall) but it did complete and I have a system up and running (more or less.)

I am trying to configure the NIC with a static IP address. I can ping myself, but not my Linksys router.

On top of it all, I can't get my floppy up (I think this is a HW issue) so I have to copy command results by hand into my posts!

The Mandrake box is 192.168.1.2
The Router is 192.168.1.1

/etc/resolve.con has the following:
search thompco.com
nameserver 192.168.1.2
nameserver 192.168.1.1

ifconfig returns the following:
eth0: Link encap:Ethernet HWaddr 00:50:2C:A4:E9:C3
inet addr: 192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe89::250:2cff:fea4:e9c3/64 Scope:Link
UP BROADCAST RUNNING MUYLTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:436 overruns:0 frame:0
TX packets:0 errors:3 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:ll Base address:0xdc00

lo Link encap:Local loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:80 errors:0 dropped:0 overruns:0 frame:0
TX packets:80 errors:0 dropped:0 overruns:0 frame:0
collisions:0 txqueuelen:0
RX bytes:5540 (5.4 Kb) TX bytes:5540 (5.4 Kb)


route returns:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0



lsmod returns a lot of stuff, but no reference to the nic. Sorry - I had to type all of this in, so when I got to this, I threw up my hands! Is there something specific to for in lsmod?

Another clue (perhaps) is that if I change the address type to DHCP, and I watch my router/DHCP server as the Mandrake box restarts the ethernet, I can see the MAC address momentarily appear in the list of clients - so I think the NIC hardware is working properly. To test this, I tried a known NIC card that worked with a previous version of Mandrake and I get similar results.
thanks for your help,
jor

The first thing I would do is get a better installation in place.

I've found that simply assuming everything is fine when an error is reported during installation, is asking for trouble. You may be missing a key item and not know it, except that something does not work as it should... hmmm.


Your posted status output from ifconfig indicates that the driver is properly loaded.

Note the error counts and the RX and TX values.

RX packets:0 errors:0 dropped:436 overruns:0 frame:0
TX packets:0 errors:3 dropped:0 overruns:0 carrier:0

Why were 436 packets received but dropped? With ZERO actual received packets!

Even on an unconfigured NIC you get UDP packets being received and reported above.

SOMETHING should have been properly received by the card unless either 1) the cable is unplugged or of the wrong type 2) the card has been initialized for the WRONG media type, 3) you have a filtering rule installed (too high a security?) which drops all packets.

E.G. in the prior case your card is coming up as 100baseT full duplex when your network only supports half duplex or 10BaseT.

You may need to specify the media type manually and kick out IPV6 while you are at it until you get everything running.

Check out these threads.

http://www.linuxquestions.org/quest...threadid=223704

http://www.linuxquestions.org/quest...threadid=240418

It is likely that the problem is with the media type given the output of ifconfig -IF- you have no other filtering installed, such as iptables, shorewall, etc. swallowing all the packets.

If you were not careful in selecting which packages you selected at install time or upped the security too high you may have inadvertently prohibited all packets.

Thanks for your comments.

I agree that the broken installation could be plaguing me. I have tried several times with a minimal installation just to get the h/w recognized. This is frusterating me.
I have tried burning the ISOs at a much slower speed and this does not help.
I used md5sum to verify the iso's and they are fine.

I went with standard security for all installation attempts.
I have previousl looked at these threads and tried implementing their suggestions - to no avail.

Have you:

1) Run an MD5 sum against the burned CD's themselves to verify their contents?

2) Run a verify of the CD on the system you burned it on.

3) Run a verify of the CD on the system you intend to install Mandrake on.

4) Check the jumpers and configuration of the reader.

5) Set the CD drive and everything on the same chain to utilize PIO instead of DMA

I've seen instances where noise was causing bad reads from otherwise known good CD's and DVDs.

This is why it may be essential to first test the configuration you will be installing Linux on, especially with the results you are reporting.

They are unusual.

Finally you could have an odd case where you have a "broken" or brain dead CD/DVD reader. There are a few out there. You may want to try another one if possible.

Mandrake should install fairly smoothly and quickly otherwise.

Thanks for your help - the CD's are now OK
I broke down and bought some higher quality CD's and was able to burn at 16x and install with no errors/warnings!!!

I am still having problems with my USB printer and ethernet connection, however. Here is the output from the commands suggested earlier (this time via my new floppy drive!)

ifconfig returns:
eth0 Link encap:Ethernet HWaddr 00:50:2C:A4:E9:C3
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::250:2cff:fea4:e9c3/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:118 overruns:0 frame:0
TX packets:0 errors:11 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:11 Base address:0xdc00

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:181 errors:0 dropped:0 overruns:0 frame:0
TX packets:181 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:14350 (14.0 Kb) TX bytes:14350 (14.0 Kb)



lsmod returns:
Module Size Used by
nls_iso8859-1 3904 1
nls_cp850 4736 1
vfat 13760 1
fat 45120 1 vfat
parport_pc 32832 1
lp 12200 0
parport 38952 2 parport_pc,lp
snd-seq-oss 31232 0
snd-seq-midi-event 7552 1 snd-seq-oss
snd-seq 51024 4 snd-seq-oss,snd-seq-midi-event
snd-pcm-oss 51812 0
snd-mixer-oss 17952 2 snd-pcm-oss
snd-via82xx 24128 1
snd-pcm 93156 2 snd-pcm-oss,snd-via82xx
snd-timer 24484 2 snd-seq,snd-pcm
snd-ac97-codec 58148 1 snd-via82xx
gameport 4480 1 snd-via82xx
snd-page-alloc 11972 2 snd-via82xx,snd-pcm
snd-mpu401-uart 7072 1 snd-via82xx
snd-rawmidi 23616 1 snd-mpu401-uart
snd-seq-device 8008 3 snd-seq-oss,snd-seq,snd-rawmidi
snd 52484 12 snd-seq-oss,snd-seq-midi-event,snd-seq,snd-pcm-oss,snd-mixer-oss,snd-via82xx,snd-pcm,snd-timer,snd-ac97-codec,snd-mpu401-uart,snd-rawmidi,snd-seq-device
soundcore 9248 2 snd
af_packet 20520 0
hid 53312 0
ide-floppy 18752 0
ide-tape 34864 0
ide-cd 40548 0
cdrom 37184 1 ide-cd
floppy 59444 1
via-rhine 20520 0
mii 4992 1 via-rhine
md5 3872 1
ipv6 232352 6
supermount 37876 1
via-agp 7360 1
agpgart 31016 1 via-agp
usblp 12288 0
ehci-hcd 24196 0
uhci-hcd 29104 0
usbcore 99132 6 hid,usblp,ehci-hcd,uhci-hcd
rtc 11576 0
ext3 111048 12
jbd 54680 1 ext3


resolve.conf contains:
search thompco.com
nameserver 192.168.1.2
nameserver 192.168.1.1

# ppp temp entry

route returns:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0




I set up the IP as a fixed address (192.168.1.2) with a mask of 255.255.255.0 on eth0. The hardware was successfully discovered on installation.

Boy I am so happy I didn't give up on the disk burning... I don't think I'll ever buy cheap CD-R's again!!! I have installed a bunch of packages and have had no (0, none) CD errors. On the other hand, my ethernet and USB are still shot dead :-(

Your report of resolve.conf indicates your Domain Name Server addresses are located on your router and your computer:

resolve.conf contains:
search thompco.com
nameserver 192.168.1.2 <- Your Computer's IP address
nameserver 192.168.1.1 <- Your router's IP address

The Domain Name Server service is usually provided by your ISP, and as such is not located on your LAN [unless of course you have a computer which is your gateway, router and which provides Domain Name Services for your LAN, but if you have a Linksys router to connect your computer(s) to the internet, such a device does not provide DNS services, any you must use the DNS service IP addresses provided by your ISP.

In a terminal window try the command:

$ping yahoo.com

If that does not work, try the command:

$ping 216.109.112.135

This is the Ip address for yahoo.com. If this works, you need to change the DNS service IP addresses for your Internet connection.

HTH,

Thanks for your help,

Unfortunately I cannot even ping my router (192.168.1.1.)
Once I get to the point I can ping local 192.168.1.x IP addresses, I'll worry about DNS!
I have the same computer as a DNS because I want it to provide DNS service for the local machines on my 192.168.1.x network.
I am pretty sure that the router provdes DNS (I can't remember right now) - if not, I can add Road Runner's DNS servers.

It's great that you solved the CD issue, although 16x is rather "fast" for burns.

If you are having problems that seem related to media you should start at 1X and move up until you get read errors. Then you will have found the max for the suspect media.

Anyway, first as root

service iptables stop

To turn off any packet filtering that may have been installed.

And try to ping your router again...

If that still does not work follow the two threads I posted before.

Disable IPV6 (just in case).

Then try the changing the XbaseT media type as indicated on the one thread.

After doing so you may need to issue a

service network restart

before you can ping the router.

Thanks for your help, I'll try your suggestions tonight...
I have not tried 1) or 2) yet .

BTW, how do you turn off packet filtering? I have turned off all firewalls (I think) via MCC. Is this sufficient?

Re: Packet Filtering

It depends upon what you selected at install time.

iptables often gets installed so it can be to blame, as can shorewall or other programs.

Most of these run as services so if they are installed you'll have an entry in /etc/init.d/

running the

service XXX stop

as root will turn them off temporarily while running

chkconfig --del XXX

will turn them off completely until you re-enable them with

chkconfig --add XXX