SlackwareThis Forum is for the discussion of Slackware Linux.
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 have recently installed Slackware 10.0. Everything went without a problem until I tried getting my network connection up and running. I am using a pretty basic setup: just a cable modem and router with DHCP through Comcast. To go ahead and rule out the physical connection, I know that works as I have windows 2000 installed on a seperate hd and I have a connection there. So, here's what I have configured thus far:
I have a Realtek 8139(a)-based nic.
During install, at netconfig, Slackware detected the card and assigned the module eepro100 (yeah, I thought it odd that it wasn't 8139too) to it.
I entered in the approriate information for DHCP and went ahead.
I checked modules.conf for the module and saw that it was uncommented as should be (the eepro100).
The resolv.conf file looks as such:
search nash01.tn.comcast.net ------>(my dns suffix)
I went into the rc.inet1.conf file and edited it for eth0 to have the approriate information (ipaddress, netmask, DHCP enabled, and default gateway). I didn't know what to put into the DHCP hostname entry so I left it blank, as I have never seen anything letting me know if or what my DHCP hostname is. I then restarted rc.inet1.
Still after this, nothing is happening.
So I manually start eth0 by typing:
ifconfig eth0 192.168.1.100 netmask 255.255.255.0 up
And after that if I do a ifconfig, eth0 is showing up now with the correct information there.
I can ping the ipaddress of 192.168.1.100 but not the gateway.
I'm sure I missed something in one of the conf files but I have scoured through forums searching for an answer to a similiar problem and I am at a loss. I had heard of typing dhcpcd eth0 but haven't had any luck using that either....don't know if I'm doing something wrong or what but I get a "stopped" message everytime I enter it, and then I have to exit the process. Everytime I come across someone with the exact same problem that is running Slackware I try the advice given, and still something is amiss. So I have to attribute it to user error as Slackware has been nothing but wonderful to me.
Any help to this Slack newbie is greatly appreciated. I'm pretty new to linux in general and decided to take on the daunting task of using Slackware as my Linux learning tool; talk about getting your feet wet. I've had many years of experience with Microsoft, but decided that I am too dependent on them. So there you go!
Thanks again all.
You leave Jack Burton alone!
Distribution: fluxbox-0.9.13 on Slackware 10.2 188.8.131.52 kernel
Have you checked dmesg for errors? really it sounds like it should be fine, maybe try
ifconfig eth0 down
ifconfig eth0 up
I dont know if that would reset the config files you modified or not, but im just tryin to see if you got the config files back to how they came with slack and brought the device up and dhcpcd if it would work, incase you missed something in the config files or setting up manually.
I tried everything that was suggested to no avail.
I checked out the dmesg and everything seemed to initialize fine and nothing was out of the ordinary.
I'm not too familiar with dhcpcd, so maybe I am missing something there, but when I type dhcpcd eth0 it just starts a new line as if it is waiting for some input. When I ctrl-c out of it is when I get the "stopped" message. Is there something I should enter there?
Also, I have noticed that eth0 doesn't start at boot up. I have to manually start it. I know I can set it up for boot, I just have to research which conf file to edit for it.
I changed my resolv.conf file to what shilo suggested and it didn't seem to make any change.
Kind of frustrating as it could be any number of things I'm missing.
Slack recognizes my card, will ping the card itself, and loads the module at boot. I am officially lost.
Looks like Im in the same boat as you guys... I have a 8139 based NIC and Its does not get an Ip at startup from my router for some reason. I found out this: On first attempt dhcpcd hangs. Ctrl-c and the command(dhcpcd eth1) again andi in a blink it recieves an IP.... Any Ideas?
Oh! Im runing properly uptated slack 9 on a machine with two nics First Is a 3Com NIC that gets loaded pefectly when incoming cable is attached to it...
Last edited by AlexiaDeath; 07-10-2004 at 11:51 AM.
It might be it, but 3com gets loaded perfectly every time. Im still aming to get it to load at startup...
EDIT: OKay.. ran a test... no difference. As long as one dhcpcd hasnt been aborted by ctrl-c it does not get an IP. But if one instance has been aborted it hapens in a blink...
Ill just give some more(in my mind) imortant inf about my system.
On installation only 3Com nic was detedted. At startup there apeared a conflict with two drivers both being atamted to load. 8139too and 8139cp. I tryed blacklisting them in turn. The too version works. Exept when getting an IP. I suspect its badly configured because it was not done during instalation but I have no clue what to fix or where. It apears as if there is not even attempt to get an IP for it during startup inspite the fact that
/etc/rc.d/rc.inet1.conf says to use dhcp.
Okay. Messed with the rc.inet1 and enabled DHCP from there. within the script. It works perfect if run again but on startup it tryes to get the ip BEFORE the drivers get loaded.... WTF! The script is run when the first NIC is loaded. any way of fixing this?
OKAY! Looks like I fixed it. Moved the adapters initzalization one step down in rc.M script right after hotplug call. That did the trick.
Last edited by AlexiaDeath; 07-10-2004 at 01:36 PM.