cli output
 

here's the output of ifconfig -a and dmesg:

(connection up)

dellbox:~# ifconfig -a
eth0 Link encap:Ethernet
Mask:255.255.255.0
inet6 addr: fe80::280:adff:fe76:c586/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:60 errors:2498 dropped:0 overruns:0 frame:0
TX packets:250 errors:2 dropped:0 overruns:0 carrier:2
collisions:0 txqueuelen:1000
RX bytes:13781 (13.4 KiB) TX bytes:43772 (42.7 KiB)
Interrupt:18 Base address:0xe800

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:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:560 (560.0 B) TX bytes:560 (560.0 B)

(disconnected)

dellbox:~# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:80:ad:76:c5:86
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:60 errors:2551 dropped:0 overruns:0 frame:0
TX packets:261 errors:2 dropped:0 overruns:0 carrier:2
collisions:0 txqueuelen:1000
RX bytes:13781 (13.4 KiB) TX bytes:45338 (44.2 KiB)
Interrupt:18 Base address:0xe800

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:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:560 (560.0 B) TX bytes:560 (560.0 B)

dmesg output:

2.811415] tulip0: EEPROM default media type Autosense.
[ 2.811421] tulip0: Index #0 - Media MII (#11) described by a 21140 MII PHY (1) block.
[ 2.811426] tulip0: Index #1 - Media 10baseT (#0) described by a 21140 non-MII (0) block.
[ 2.811431] tulip0: Index #2 - Media 100baseTx (#3) described by a 21140 non-MII (0) block.
[ 2.811435] tulip0: Index #3 - Media 10baseT-FDX (#4) described by a 21140 non-MII (0) block.
[ 2.811440] tulip0: Index #4 - Media 100baseTx-FDX (#5) described by a 21140 non-MII (0) block.
[ 2.813891] tulip0: MII transceiver #1 config 3100 status 7809 advertising 01e1.
[ 2.822036] eth0: Davicom DM9102/DM9102A rev 49 at Port 0xe800, 00:80:ad:76:c5:86, IRQ 18.

[ 52.832764] eth0: Setting full-duplex based on MII#1 link partner capability of 45e1.

[ 77.660026] eth0: no IPv6 routers present
[ 165.634520] 0000:02:09.0: tulip_stop_rxtx() failed (CSR5 0xfc740000 CSR6 0x2042202)

route -n just outputs the column headers, no data. still looking into the inet and module info..

just noticed something, the cli prompt doesn't show the root user name and i actually have to log in as "root" when i shell out with ctrl - alt - F1, this can't be good. root terminal from the applications / accessories takes the root password. i've been avoiding logging in as the root user until i needed it. may have fat - fingered this on the install. the gnome desktop won't take "root", second user login works ok. i'll work on the two items above, learning can't hurt, but a re -install might clear up future issues. still may have to switch drivers. distro, btw, is debian lenny.

thanks
t_o_w

Hi,

You definitely have rx/tx errors. What module do you show as being used? Output for 'lsmod'?

farslayer suggested in post #15.

What was the result from those actions?

no response from OP.. must have got the network issue fixed somehow, and be off on holiday now.. :)

checking modules
 

[QUOTE=farslayer;3561581]Davicom Semiconductor.. sometimes mis-detected as tulip.

Might want to check what module it is using. if it's using the tulip module remove it and insert dmfe in it's place.

if that resolves the issue then blacklist the tulip module.QUOTE]

hi all,

i hope the quote shows up OK, if not it's part of the thread above. i didn't try the blacklisting yet, i'm a little rusty on shell commands and usually look them up before trying them. i'm not sure what the lsmod and dmesg lines are telling me, am i missing something? Here's the output:

dellbox:/home/gh# lsmod |grep tulip
tulip 44064 0

dellbox:/home/gh# lsmod |grep dmfe
dmfe 16568 0

dellbox:/home/gh# dmesg |grep eth
[ 2.813812] eth0: Davicom DM9102/DM9102A rev 49 at Port 0xe800, 00:80:ad:76:c5:86, IRQ 18.
[ 24.852774] eth0: Setting full-duplex based on MII#1 link partner capability of 45e1.
[ 36.096017] eth0: no IPv6 routers present
[ 54.228029] eth0: no IPv6 routers present

dellbox:/home/gh# dmesg |grep tulip
[ 2.803369] tulip0: EEPROM default media type Autosense.
[ 2.803376] tulip0: Index #0 - Media MII (#11) described by a 21140 MII PHY (1) block.
[ 2.803380] tulip0: Index #1 - Media 10baseT (#0) described by a 21140 non-MII (0) block.
[ 2.803385] tulip0: Index #2 - Media 100baseTx (#3) described by a 21140 non-MII (0) block.
[ 2.803389] tulip0: Index #3 - Media 10baseT-FDX (#4) described by a 21140 non-MII (0) block.
[ 2.803394] tulip0: Index #4 - Media 100baseTx-FDX (#5) described by a 21140 non-MII (0) block.
[ 2.805846] tulip0: MII transceiver #1 config 3100 status 7809 advertising 01e1.

dellbox:/home/gh# dmesg |grep Davicom
[ 2.813812] eth0: Davicom DM9102/DM9102A rev 49 at Port 0xe800, 00:80:ad:76:c5:86, IRQ 18

i'm confused at this point, it looks to me like neither module is in use. am i checking the module use correctly?

[ 165.634520] 0000:02:09.0: tulip_stop_rxtx() failed (CSR5 0xfc740000 CSR6 0x2042202)

and is this telling me that the tulip driver failed on boot?
thanks,
t_o_w

success
 

please excuse the delay. newbie nervousness and "windows reflex" makes me check things before doing them. thanks guys, the network connection came up as soon as i hit the enter key after "modprobe dmfe". I'll try the blacklisting next now that i know what to search for. but if u read the last post, why did it show tulip and dmfe as 0?

hopefully the last question for a while, do i need antivirus before doing any serious web surfing from linux or just homework on my file structure and file permissions? please point to a wikis & tutorials on interpreting lsmod and ifconfig results, and file structure i'm still new to these commands.

hmm, obviously i ned to bone up on quoting in this site also. it has been a few years since using open bsd.

t_o_w

Hi,

Your using GNU/Linux not M$. Worse case would be a script problem but you could always use NoScript with FF.

As for some very useful links, look at 'Slackware-Links'. More than just Slackware® links!

BTW, checkout Chkrootkit if your worried about root breaks or ClamAV if you serve M$.

Glad to hear that worked for you..

Just follow the directions for blacklisting that I posted the link to step by step.. it's pretty straight forward, but not very intuitive. Once the blacklisting is done your problem should be resolved so it will not re-appear after a reboot.

As for why the tulip module even tries to load for that card in the first place I don't know.. but apparently after it fails and the proper module loads, the proper module doesn't function properly. Look on the bright side, we found the issue and were able to come up with a resolution quickly :)

I won't argue with you about being cautions.. I've been doing computer work for years now and I check, double check, and then triple check before I do a lot of things, just to make sure I don't make a mistake. Better to be cautions than to cause yourself tons of grief with a careless command.

serve M$? no way. i use 'em until i can lose 'em, and then they're goin' away. i used to be locked out of any root file but no more, now it's my responsibility so it's homework, homework... ahh, you know the drill. and who's complaining? you did good.
this one's brought to you by debian lenny.

google this if you have to:

kam se ha me dah, y'all

t_o_w

Hi,

Administration does have responsibility! You should always have the habit of checking then checking again. I remember the rule; 'measure twice, cut once'. That simple rule will save you a load of work and pain with any task. Be it computers or construction. :)