Networking Forums

Networking Forums > Computer Networking > Linux Networking > Re: Network fails with (almost) no error messages on LFS, but works on Debian

Reply
Thread Tools Display Modes

Re: Network fails with (almost) no error messages on LFS, but works on Debian

 
 
Bobby Martin
Guest
Posts: n/a

 
      07-03-2003, 09:10 PM
The answer is... noapic! Pass this in as a parameter in your
lilo.conf (or at boot time) and your problems will go away, I believe.

I'm now going to put a bunch of keywords in here so people googling
can find this information...

I bought a new Soyo kt400 lite motherboard and my ethernet went away.
Modules loaded just fine, ifconfig on eth0 seems to do what it's
supposed to, route seemed fine, but almost all packets fail to be
received by the on-board nic. Strangely, this also seemed to happen
on any other nic that I put into the mobo.

The only symptoms I could find (other than not being able to access
the network were some funny messages in my syslog:
eth0: transmit timed out: status 1003, PHY status 782d

Sometimes the nic would pick up packets sent to the broadcast address
(e.g. 192.168.1.255) but most of those were dropped, too.

I'm pretty sure the whole problem is the motherboard.

So, if you have a soyo kt400, soyo kt333, or any other soyo
motherboard and you are using Linux, I recommend trying noapic as a
lilo.conf parameter to fix your network card nightmares.
 
Reply With Quote
 
 
 
 
Lucius Chiaraviglio
Guest
Posts: n/a

 
      07-20-2003, 05:47 AM
(E-Mail Removed) (Bobby Martin) wrote:
>The answer is... noapic! Pass this in as a parameter in your
>lilo.conf (or at boot time) and your problems will go away, I believe.


My solution seems related to yours, as I posted in a new thread: I
found out that if I turned off CONFIG_X86_UP_IOAPIC in my kernel .config and
recompiled the kernel, the ethernet problem went away (although I haven't
tried a transfer at above 10 Mbps yet). Only problem this caused is the
occasional "spurious 8259A interrupt: IRQ7" error (nothing is even plugged
into the parallel port), which I just live with. According to one of the
kernel maintainers, the conflict between CONFIG_X86_UP_IOAPIC and VT6102
Rhine II ethernet cards on motherboards with Via chip sets is a known bug.

--
Lucius Chiaraviglio
Approximate E-mail address: (E-Mail Removed)
To get the exact address: ^^^ ^replace this with 'r'
|||
replace this with single digit meaning the same thing
(Spambots of Doom, take that!).
 
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

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


Similar Threads
Thread Thread Starter Forum Replies Last Post
debian Etch transparent squid proxy error messages Olaf Petzold Linux Networking 9 10-11-2006 10:22 PM
network event ID error messages exploreman Windows Networking 1 04-06-2005 08:17 AM
Setting up Network/Error Messages Andy M Moore Wireless Internet 1 12-29-2003 09:07 AM
rpc.statd fails on diskless Debian 3.0 install Oliver Hookins Linux Networking 9 09-09-2003 11:50 AM
debian potato, ups powerware and soft lansafe this not works !!! Marcin Miedziejko Linux Networking 0 07-31-2003 01:21 PM



1 2 3 4 5 6 7 8 9 10 11