Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I tried those command but could not activate eth0.I have FC4 installed on HP pavilion dv1000.
ifup eth0 gave the same error SIOCSIFFLAGS:Invalid argument
dhclient eth0 gave no errors but eth0 was not activated as I was not able to connect to the net.
FC4 should automatically bring up your ethernet connection. Are you sure that your adapter is properly detected by fedora. If you're using gnome go the hardware browser and check that its listed properly. If not, go from there.
I see there is one question I asked not answered...
Did you try Network Device Control ?
... Fedora likes you to use the NDC interface to manage network devices.
FC4 does not automatically bring the ethernet connection up... only if you were on a network when you first started. (At least - that's so with mine. I had to bring eth0 up in the ndc to get connected.)
Have you configured eth0 for your network?
Are you plugged in?
Thanx to everybody for responding.
I did use the Network configuration utility in Fedora, the one which u get on typing neat in the konsole. There again when I click on activate for eth0 I get the same error. SIOCSIFFLAGS:Invalid Argument.
One more thing, everytime I face a problem in Linux I have to boot windows and then google for the problem as I am not connected to the net on Linux. Is there any solution for this so that I dont restart everytime.
> FC4 should automatically bring up your ethernet connection.
Yes, during bootup it does try to bring up eth0 but the same error message appears there as well.
Bringing up eth0 [Failed]
everytime I face a problem in Linux I have to boot windows and then google for the problem as I am not connected to the net on Linux. Is there any solution for this so that I dont restart everytime.
This is only an issue where the problem prevents internet access (or booting into linux). Generally these things are unusual. Booting into another OS, which can access the internet, is the usual method. For this reason, many people keep several kernels on their system... i.e. when they are recompiling a kernel, they keep a working version on standby.
Linux Rescue CDs can be useful here, as can live distributions like knoppix. (Knoppix in particular because of it's legendary hardware recognition.)
And, of course, there is always keeping several ways of accessing the internet. Keep a modem handy as well as an ethernet nic - that way one or the other is bound to be going. (Though, usually, ethernet is more reliable.)
I did use the Network configuration utility in Fedora, the one which u get on typing neat in the konsole. There again when I click on activate for eth0 I get the same error.
Hmmm... you're using KDE?
I'm not sure what you mean by "typing neat" (typo?) but I get it from the main menue > system tools > network device control.
It is unusual for users to be able to activate eth0 from the NDC.
Anyway - ndc also ha a "configure" button? This takes you to the "network configuration" dialog - you get an option to start the service there too (worth a try but unlikely to work given past results).
In Network Configuration, you can check your hardware status to see what it can see.
You can also destroy the eth0 configuration - I am suggesting you do this, then use the internet configuration wizard (main > system tools > internet configuration wizard) to add a new ethernet connection.
This should probe for your card, detect it, and walk you through configuring it properly.
BTW: what is this card? (lspci) I take it this card works under <sigh> windows?
Hmmm... done some brainstormin with some more savvy folk than me.
I take it this card has not been used in linux before? And that this is a pretty new installation of FC4? Did you skip the network configuration in anaconda (when you installed)? (If got called localhost - then you probably skipped.)
You see, the serious money in on the driver being absent or wrong.
lsmod (to check drivers)
lspci (to tell us what card this is)
It may be a matter of just modprobe <driver>.
Some other things to check:
What does your /etc/sysconfig/network-scripts/ifcfg-eth0 say?
What is in /etc/sysconfig/networks?
If this is a pci card, try reseating it, or using it in another slot.
Q: Ethernet networking is not working. I get the error message:
"SIOCSIFFLAGS: Try again"
A: This usually indicates a hardware conflict with your ethernet controller. Run "ifconfig -a" and check the IRQ and I/O addresses used by the controller. Also, look at the contents of the files /proc/interrupts and /proc/pci to determine what IRQ and I/O addresses are in use on your system. Many ethernet and SCSI drivers cannot share interrupts under Linux. Your system most likely has an IRQ conflict.
To fix IRQ conflicts on PCI bus systems, you can often go into the motherboard BIOS setup and mark the conflicting IRQ as "Used by an ISA Device". This will force the motherboard to reassign the IRQ, often eliminating the conflict.
This looks a lot like your problem right here.
Follow the advice above.
At this point I'd need feedback before continuing.
Thanx a lot for your continued help. The last link does look like my problem and I think it might fix it. Currently I am in my office and I would try it out tonight.
Thanx once again for your help.
and I checked /proc/pci and somewhere it contained the same address. I am not sure if that is causing the problem.
Following was the piece in proc/pci with the same address:
Class 0200:PCI device 10ec:8136(rev16)
Master Capable Latency=64 Min Gnt=32 Max Lat=64
I/O at 0x3000[0x30ff]
I tried to make the changes you suggested in the BIOS settings but I could not find the option. In any case I dont think it woul be safe to make changes to BIOS settings without being sure abt what I am doing. isnt there any other way out.
I also installed fedora again. During installation it gives two options for setting the hostname:
-> automatically via DHCP
In my earlier installation I had selected automatically via DHCP. This time I changed it to Manually and provided the IP address, subnet mask....
I thought this would solve the problem but again I got the same error:SIOCSIFFLAGS:Invalid argument