Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: #1 PCLinuxOS -- for laughs -> Ubuntu, Suse, Mepis
Posts: 315
Rep:
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.
Distribution: #1 PCLinuxOS -- for laughs -> Ubuntu, Suse, Mepis
Posts: 315
Original Poster
Rep:
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
Distribution: #1 PCLinuxOS -- for laughs -> Ubuntu, Suse, Mepis
Posts: 315
Original Poster
Rep:
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 ..
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.