Big Problem! help please...

This is a discussion on Big Problem! help please... within the Linux Networking forums, part of the Linux Forums category; Hi all. I have installed fedora core-1 onto a free partition on a win98 machine. The installation went well ...


Go Back   Usenet Forums > Linux Forums > Linux Networking

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 06-08-2004
ZoombyWoof
 
Posts: n/a
Default Big Problem! help please...

Hi all. I have installed fedora core-1 onto a free partition on a win98
machine. The installation went well all the way, the network config were
no problem, but the machine cant communicate on the network. Under win98
the machine has no problem. I initially gave the fedora installation the
same ip-adress and nodename as the win98 installation, but changing that
didnt help.
I can ping localhost, no problem. I have compared all the config files
with another fedora installation I have on another machine, everything
looks fine, except that ifconfig shows errors on TX packets and overruns
and carrier are high. If I reboot to win98 the network works just fine,
but under fedora I get overruns & carrier errors on TX packets.

Any ideas ?

Thanx

/ZoombyWoof
Reply With Quote
  #2 (permalink)  
Old 06-08-2004
Cameron Kerr
 
Posts: n/a
Default Re: Big Problem! help please...

ZoombyWoof <zoombywoofremove@thishotmail.com> wrote:

> If I reboot to win98 the network works just fine, but under fedora I
> get overruns & carrier errors on TX packets.


What NIC are you using?

What kernel version are you using `uname -r'?

Please give the output of the `lspci' command.

--
Cameron Kerr
cameron.kerr@paradise.net.nz : http://nzgeeks.org/cameron/
Empowered by Perl!
Reply With Quote
  #3 (permalink)  
Old 06-09-2004
ZoombyWoof
 
Posts: n/a
Default Re: Big Problem! help please...

Cameron Kerr wrote:
> ZoombyWoof <zoombywoofremove@thishotmail.com> wrote:
>
>
>>If I reboot to win98 the network works just fine, but under fedora I
>>get overruns & carrier errors on TX packets.

>
>
> What NIC are you using?
>
> What kernel version are you using `uname -r'?
>
> Please give the output of the `lspci' command.
>

here comes some information from the box :

Linux Enid 2.6.5-1.358 #1 Sat May 8 09:04:50 EDT 2004 i686 athlon i386
GNU/Linux

#lspci >>
00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133]
(rev 03)
00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP]
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South]
(rev 40)
00:07.1 IDE interface: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:07.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 16)
00:07.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 16)
00:07.4 Bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40)
00:07.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686
AC97 Audio Controller (rev 50)
00:09.0 Ethernet controller: 3Com Corporation 3c905 100BaseTX [Boomerang]
01:00.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2
MX/MX 400] (rev b2)

#ifconfig >>
eth0 Link encap:Ethernet HWaddr 00:60:08:68:C3:92
inet addr:192.168.0.10 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::260:8ff:fe68:c392/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:45 dropped:0 overruns:47 carrier:47
collisions:0 txqueuelen:1000
RX bytes:4085 (3.9 Kb) TX bytes:0 (0.0 b)
Interrupt:11 Base address:0xec00

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:1824 errors:0 dropped:0 overruns:0 frame:0
TX packets:1824 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2776756 (2.6 Mb) TX bytes:2776756 (2.6 Mb)

#lsmod >>
Module Size Used by
nls_utf8 1536 1
nls_cp437 5376 1
vfat 10496 1
fat 33472 1 vfat
snd_mixer_oss 13824 2
snd_via82xx 19104 3
snd_pcm 68872 1 snd_via82xx
snd_timer 17156 1 snd_pcm
snd_ac97_codec 50436 1 snd_via82xx
snd_page_alloc 7940 2 snd_via82xx,snd_pcm
gameport 3328 1 snd_via82xx
snd_mpu401_uart 4864 1 snd_via82xx
snd_rawmidi 17184 1 snd_mpu401_uart
snd_seq_device 6152 1 snd_rawmidi
snd 38372 10
snd_mixer_oss,snd_via82xx,snd_pcm,snd_timer,snd_ac 97_codec,snd_mpu401_uart,snd_rawmidi,snd_seq_devic e
soundcore 6112 3 snd
parport_pc 19392 1
lp 8236 0
parport 29640 2 parport_pc,lp
autofs4 10624 0
sunrpc 101064 1
3c59x 30376 0
floppy 47440 1
sg 27552 0
scsi_mod 91344 1 sg
dm_mod 33184 0
uhci_hcd 23708 0
button 4504 0
battery 6924 0
asus_acpi 8472 0
ac 3340 0
ipv6 184288 8
ext3 102376 2
jbd 40216 1 ext3

# Extracts from /var/log/messages
Jun 9 11:39:35 Enid kernel: NETDEV WATCHDOG: eth0: transmit timed out
Jun 9 11:39:35 Enid kernel: eth0: transmit timed out, tx_status 00
status e000.
Jun 9 11:39:35 Enid kernel: diagnostics: net 0cc0 media 8802 dma
00000000 fifo 0000
Jun 9 11:39:35 Enid kernel: Flags; bus-master 1, dirty 1(1) current 17(1)
Jun 9 11:39:35 Enid kernel: Transmit list 00000000 vs. 1a7f82a0.
Jun 9 11:39:35 Enid kernel: 0: @1a7f8200 length 8000002a status 8000002a
Jun 9 11:39:35 Enid kernel: 1: @1a7f82a0 length 8000002a status 0000002a
Jun 9 11:39:35 Enid kernel: 2: @1a7f8340 length 8000002a status 0000002a
Jun 9 11:39:35 Enid kernel: 3: @1a7f83e0 length 8000002a status 0000002a
Jun 9 11:39:35 Enid kernel: 4: @1a7f8480 length 8000002a status 0000002a
Jun 9 11:39:35 Enid kernel: 5: @1a7f8520 length 8000002a status 0000002a
Jun 9 11:39:35 Enid kernel: 6: @1a7f85c0 length 8000002a status 0000002a
Jun 9 11:39:35 Enid kernel: 7: @1a7f8660 length 8000002a status 0000002a
Jun 9 11:39:35 Enid kernel: 8: @1a7f8700 length 8000002a status 0000002a
Jun 9 11:39:35 Enid kernel: 9: @1a7f87a0 length 8000002a status 0000002a
Jun 9 11:39:35 Enid kernel: 10: @1a7f8840 length 8000002a status
0000002a
Jun 9 11:39:35 Enid kernel: 11: @1a7f88e0 length 8000002a status
0000002a
Jun 9 11:39:35 Enid kernel: 12: @1a7f8980 length 8000002a status
0000002a
Jun 9 11:39:35 Enid kernel: 13: @1a7f8a20 length 8000002a status
0000002a
Jun 9 11:39:35 Enid kernel: 14: @1a7f8ac0 length 8000002a status
0000002a
Jun 9 11:39:35 Enid kernel: 15: @1a7f8b60 length 8000002a status
8000002a
Jun 9 11:39:35 Enid kernel: eth0: Transmit error, Tx status register 90.
Jun 9 11:39:35 Enid kernel: Flags; bus-master 1, dirty 1(1) current 17(1)
Jun 9 11:39:35 Enid kernel: Transmit list 187f8340 vs. 1a7f82a0.
Jun 9 11:39:35 Enid kernel: 0: @1a7f8200 length 8000002a status 8000002a
Jun 9 11:39:35 Enid kernel: 1: @1a7f82a0 length 8000002a status 0000002a
Jun 9 11:39:35 Enid kernel: 2: @1a7f8340 length 8000002a status 0000002a
Jun 9 11:39:35 Enid kernel: 3: @1a7f83e0 length 8000002a status 0000002a
Jun 9 11:39:35 Enid kernel: 4: @1a7f8480 length 8000002a status 0000002a
Jun 9 11:39:35 Enid kernel: 5: @1a7f8520 length 8000002a status 0000002a
Jun 9 11:39:35 Enid kernel: 6: @1a7f85c0 length 8000002a status 0000002a
Jun 9 11:39:35 Enid kernel: 7: @1a7f8660 length 8000002a status 0000002a
Jun 9 11:39:35 Enid kernel: 8: @1a7f8700 length 8000002a status 0000002a
Jun 9 11:39:35 Enid kernel: 9: @1a7f87a0 length 8000002a status 0000002a
Jun 9 11:39:35 Enid kernel: 10: @1a7f8840 length 8000002a status
0000002a
Jun 9 11:39:35 Enid kernel: 11: @1a7f88e0 length 8000002a status
0000002a
Jun 9 11:39:35 Enid kernel: 12: @1a7f8980 length 8000002a status
0000002a
Jun 9 11:39:35 Enid kernel: 13: @1a7f8a20 length 8000002a status
0000002a
Jun 9 11:39:35 Enid kernel: 14: @1a7f8ac0 length 8000002a status
0000002a
Jun 9 11:39:35 Enid kernel: 15: @1a7f8b60 length 8000002a status
8000002a

# More extracts from /var/log/messages

Jun 9 11:04:01 Enid kernel: PCI: PCI BIOS revision 2.10 entry at
0xfb250, last bus=1
Jun 9 11:04:01 Enid kernel: PCI: Using configuration type 1
Jun 9 11:04:01 Enid kernel: ACPI: PCI Root Bridge [PCI0] (00:00)
Jun 9 11:04:01 Enid kernel: PCI: Probing PCI hardware (bus 00)
Jun 9 11:04:01 Enid kernel: Disabling VIA memory write queue (PCI ID
0305, rev 03): [55] 89 & 1f -> 09
Jun 9 11:04:01 Enid kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4
5 6 7 *10 11 12 14 15)
Jun 9 11:04:01 Enid kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4
5 6 7 10 *11 12 14 15)
Jun 9 11:04:01 Enid kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4
*5 6 7 10 11 12 14 15)
Jun 9 11:04:01 Enid kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4
5 6 7 10 11 *12 14 15)
Jun 9 11:04:01 Enid kernel: ACPI: PCI Interrupt Link [LNKD] enabled at
IRQ 12
Jun 9 11:04:01 Enid kernel: ACPI: PCI Interrupt Link [LNKC] enabled at
IRQ 5
Jun 9 11:04:01 Enid kernel: ACPI: PCI Interrupt Link [LNKB] enabled at
IRQ 11
Jun 9 11:04:01 Enid kernel: ACPI: PCI Interrupt Link [LNKA] enabled at
IRQ 10
Jun 9 11:04:01 Enid kernel: PCI: Using ACPI for IRQ routing
Jun 9 11:04:01 Enid kernel: PCI: if you experience problems, try using
option 'pci=noacpi' or even 'acpi=off'
Jun 9 11:04:01 Enid kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jun 9 11:04:01 Enid kernel: VP_IDE: IDE controller at PCI slot 0000:00:07.1
Jun 9 11:04:04 Enid kernel: 0000:00:09.0: 3Com PCI 3c905 Boomerang
100baseTx at 0xec00. Vers LK1.1.19
Jun 9 11:04:04 Enid kernel: 0000:00:09.0: 3Com PCI 3c905 Boomerang
100baseTx at 0xec00. Vers LK1.1.19
Jun 9 11:04:07 Enid kernel: eth0: PCI bus error, bus status 00a00021

I have tried to enter options in modprobe.conf, setting full_duplex to
both 0 and 1, it didnt help.

Any help much appreciated. Thanx

/ZoombyWoof
Reply With Quote
  #4 (permalink)  
Old 06-09-2004
Ralf Herrmann
 
Posts: n/a
Default Re: Big Problem! help please...

Hi,

can't really tell what it would be, but seems to like a NIC module flaw.

> Linux Enid 2.6.5-1.358 #1 Sat May 8 09:04:50 EDT 2004 i686 athlon i386


Very new kernel i think. I don't know if they chaged a lot in the
3c59x - module, but if your NIC is fine with other OSs,
it's most likely the module or the entire kernel you are using.

Try to get a most recent (and additionally some older) src of the
3c59x module, compile it and try again.

You might want to try some other kernel as well
(most distros offer different kernels, i don't knoe fedora,
but in Debian/Knoppix you can chose between 2.4.xxxx and 2.6.xxxx)

Ok, just be sure your NIC/mobo is ok (i.e. no PCI fault),
try to boot your machine with e.g. Knoppix Live system
and see, if your NIC works fine.....

HTH

Ralf
Reply With Quote
  #5 (permalink)  
Old 06-09-2004
ZoombyWoof
 
Posts: n/a
Default Re: Big Problem...I gave up

ZoombyWoof wrote:
Thanx for the ideas and input guys. I gave up eventually and
replaced the card with another NIC and put it in another PCI slot as
well, and now the network works fine with Fedora, I havent booted Win98
yet :-)....

/ZoombyWoof
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are Off
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT +1. The time now is 09:37 AM.


Powered by vBulletin® Version 3.6.8
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.0.0