LinuxQuestions.org
Help answer threads with 0 replies.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices


Reply
  Search this Thread
Old 05-17-2004, 06:26 PM   #1
winsnomore
Member
 
Registered: May 2004
Location: USA
Distribution: #1 PCLinuxOS -- for laughs -> Ubuntu, Suse, Mepis
Posts: 315

Rep: Reputation: 31
Unhappy Ethernet Failes to come up - Fedora


I have a bad problem on brining up ethernet on new Linux install.

I am using Fedora 2.24 on a Asus Motherboad (P4SGX-MX - Pentium 4)
The Motherboard has a built in Ethernet (SIS900) Interface.
It's a dual boot system and I have no problem using it with W2k.

Using Linux Ethernt Eth0 fails to come up.

It fails during the boot and when I tried
network restart
it comesup with Eth0 failed : "SIOCSIFFLAGS .. device or resources busy "


I have tried giving manual IP address .. but I guess it doesn't even go that far.
It does load sis900 module .. you can see it with lsmod

I have tried all suggestions made regarding similar sounding problems to no avail.

Please provide help .. I can't bring in full logs from the linux machine to this as networking is not working, but will try to provide all the debug's i can find.

thanks

Last edited by winsnomore; 05-17-2004 at 06:29 PM.
 
Old 05-18-2004, 06:28 AM   #2
ppuru
Senior Member
 
Registered: Mar 2003
Location: Beautiful BC
Distribution: RedHat & clones, Slackware, SuSE, OpenBSD
Posts: 1,791

Rep: Reputation: 50
What does

#dmesg|grep eth

have to say?
 
Old 05-18-2004, 06:58 AM   #3
winsnomore
Member
 
Registered: May 2004
Location: USA
Distribution: #1 PCLinuxOS -- for laughs -> Ubuntu, Suse, Mepis
Posts: 315

Original Poster
Rep: Reputation: 31
dmseg has the following on eth0:
------------------------
divert: allocating divert_block for eth0
eth0: found RealTek 8201 Phy Device for interface 1
eth0: using Realtek found at interface 1 as default
eth0: SIS 900 base add 0x8800 IRQ 0, 00 oe 3b 4c ef 90
divert: freeing divert_block for eth0

----
 
Old 05-18-2004, 07:04 AM   #4
ppuru
Senior Member
 
Registered: Mar 2003
Location: Beautiful BC
Distribution: RedHat & clones, Slackware, SuSE, OpenBSD
Posts: 1,791

Rep: Reputation: 50
Not sure if this will help ... As dmesg shows the card as Realtek,

unload sis9000 and try loading the 8139too driver
 
Old 05-18-2004, 07:15 AM   #5
winsnomore
Member
 
Registered: May 2004
Location: USA
Distribution: #1 PCLinuxOS -- for laughs -> Ubuntu, Suse, Mepis
Posts: 315

Original Poster
Rep: Reputation: 31
I am afraid that's not the case.

Dmesg says "Realtek PHY device" .. and it then sees SIS 900 with the
correct "port add and pulls the right MAC out of it")
So .. it does recognize SIS 900.

In system->network dialog box, one cans the SIS-900/7106 (I think) module.

One can see it's MAC and "no interrupt .. interrupt says unknown" .. but that's probably because it's an integrated device and uses a common interrupt handler in the bios.


I am quiet certain that the problem is somewhere in configuring the IP portion and binding it to the port/hardware.

I have tried:
putting "hostname entry"
putting "static IP addresses "
putting "DNS addresses" .. and all the combinations of the above.

I have deleted the hardware from the system->network dialog and reslected it .. (If I don't select the SIS-900 ... it fails).

So though the hardware is loaded, it always comes up Inactive. Trying to activate it results in the SIO**FLAGS busy message.

I have done rmmod/modprobe/ismod .. and they all take the module.
network "start/restart" always results int eh same errors ..
 
Old 05-18-2004, 11:20 PM   #6
ppuru
Senior Member
 
Registered: Mar 2003
Location: Beautiful BC
Distribution: RedHat & clones, Slackware, SuSE, OpenBSD
Posts: 1,791

Rep: Reputation: 50
Check these links ... they point to IRQ conflict.

http://www.linuxmafia.com/faq/VALinu...ags-error.html
http://list.nmlug.org/nmlug/2004-January/msg00097.html


Last edited by ppuru; 05-18-2004 at 11:49 PM.
 
  


Reply



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 Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
ipw2200 failes to compile at create_workqueue Avenger Linux - Wireless Networking 0 09-05-2005 02:39 PM
networksetup failes ulaoulao Linux - Networking 1 12-08-2004 12:55 AM
fedora core 2 failes booting up gSalsero Fedora 1 09-21-2004 10:43 AM
Fluxbox compilation failes objorkum Linux - General 5 03-18-2004 09:38 AM
Redhat8.0 startx failes cuboctahedron Linux - Newbie 5 11-10-2002 04:25 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 04:11 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration