LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 12-08-2010, 11:59 AM   #46
T3slider
Senior Member
 
Registered: Jul 2007
Distribution: Slackware64-14.1
Posts: 2,367

Rep: Reputation: 841Reputation: 841Reputation: 841Reputation: 841Reputation: 841Reputation: 841Reputation: 841

Quote:
Originally Posted by onebuck View Post
Hi,
If you are going the 'netdevice' method then you must initialize this, since Slackware doesn't use the '/etc/rc.d/rc.netdevice' methods any longer. You could execute 'netdevice' from '/etc/rc.d/rc.local'. But to do it right we need to find out why it's not being setup through the scheduler(kernel).
From /etc/rc.d/rc.S:
Code:
# Priority is given first to a script named "rc.modules.local", then
# to "rc.modules-$FULL_KERNEL_VERSION", and finally to the plain "rc.modules".
# Note that if /etc/rc.d/rc.modules.local is found, then that will be the ONLY
# rc.modules script the machine will run, so make sure it has everything in
# it that you need.
if [ -x /etc/rc.d/rc.modules.local -a -r /proc/modules ]; then
  echo "Running /etc/rc.d/rc.modules.local:"
  /bin/sh /etc/rc.d/rc.modules.local
elif [ -x /etc/rc.d/rc.modules-$(uname -r) -a -r /proc/modules ]; then
  echo "Running /etc/rc.d/rc.modules-$(uname -r):"
  . /etc/rc.d/rc.modules-$(uname -r)
elif [ -x /etc/rc.d/rc.modules -a -r /proc/modules -a -L /etc/rc.d/rc.modules ]; then
  echo "Running /etc/rc.d/rc.modules -> $(readlink /etc/rc.d/rc.modules):"
  . /etc/rc.d/rc.modules
elif [ -x /etc/rc.d/rc.modules -a -r /proc/modules ]; then
  echo "Running /etc/rc.d/rc.modules:"
  . /etc/rc.d/rc.modules
fi
From /etc/rc.d/rc.modules-2.6.33.4:
Code:
# First, if setup probing found a network card, there may be an 'rc.netdevice'
# file that we should run to load the network module:
if [ -x /etc/rc.d/rc.netdevice ]; then
  . /etc/rc.d/rc.netdevice
fi
In Slackware 13.1 (64-bit in my case). With a properly setup Slackware rc.netdevice can be an appropriate place to put network device commands since it should be run before rc.M (ie before rc.inet1 is run). If you do this from rc.local it defeats the purpose of the rc.netdevice file altogether.
 
Old 12-08-2010, 01:07 PM   #47
onebuck
Moderator
 
Registered: Jan 2005
Location: Summer Midwest USA, Central Illinois, Winter Central Florida
Distribution: SlackwareŽ
Posts: 13,610
Blog Entries: 34

Rep: Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793
Hi,

Quote:
Originally Posted by T3slider View Post
From /etc/rc.d/rc.S:
Code:
# Priority is given first to a script named "rc.modules.local", then
# to "rc.modules-$FULL_KERNEL_VERSION", and finally to the plain "rc.modules".
# Note that if /etc/rc.d/rc.modules.local is found, then that will be the ONLY
# rc.modules script the machine will run, so make sure it has everything in
# it that you need.
if [ -x /etc/rc.d/rc.modules.local -a -r /proc/modules ]; then
  echo "Running /etc/rc.d/rc.modules.local:"
  /bin/sh /etc/rc.d/rc.modules.local
elif [ -x /etc/rc.d/rc.modules-$(uname -r) -a -r /proc/modules ]; then
  echo "Running /etc/rc.d/rc.modules-$(uname -r):"
  . /etc/rc.d/rc.modules-$(uname -r)
elif [ -x /etc/rc.d/rc.modules -a -r /proc/modules -a -L /etc/rc.d/rc.modules ]; then
  echo "Running /etc/rc.d/rc.modules -> $(readlink /etc/rc.d/rc.modules):"
  . /etc/rc.d/rc.modules
elif [ -x /etc/rc.d/rc.modules -a -r /proc/modules ]; then
  echo "Running /etc/rc.d/rc.modules:"
  . /etc/rc.d/rc.modules
fi
From /etc/rc.d/rc.modules-2.6.33.4:
Code:
# First, if setup probing found a network card, there may be an 'rc.netdevice'
# file that we should run to load the network module:
if [ -x /etc/rc.d/rc.netdevice ]; then
  . /etc/rc.d/rc.netdevice
fi
In Slackware 13.1 (64-bit in my case). With a properly setup Slackware rc.netdevice can be an appropriate place to put network device commands since it should be run before rc.M (ie before rc.inet1 is run). If you do this from rc.local it defeats the purpose of the rc.netdevice file altogether.
Your right, I completely forgot about that and made different assumptions relative to original install methods.

Thanks for the correction and clarification. I should take a look at the init scripts to refresh my memory. It's been awhile.

I still believe the recognition for the OP's device is the problem.

I'm still curious about the OP's problem.
 
Old 12-08-2010, 01:44 PM   #48
EldonCool
Member
 
Registered: Dec 2010
Location: Nevada
Distribution: Slackware
Posts: 240

Original Poster
Rep: Reputation: 2
I just rebooted and started to apply the last fixes,
as described by onebuck but I put those fixes on hold
for awhile because before applying them I tried:

~#ping 192.168.0.1
worked

~#ping 208.69.32.130
worked on google using address

~#ping google.com
worked.

I wonder why it now works without doing any of
the previous setup stuff like static IP etc.
Maybe ping google.com did not work because
it required a reboot, before the /etc/resolv.conf
file was read again, who knows?

Anyway I am about to put that machine into X
windows and see if a browser works. I am
betting it does. here goes.

I did it and firefox came up on the home page.
I guess the next thing is to go and save all
these files we been looking at, so I can
compare them if the thing decides to have
the wheels fall off again.

One thing I noticed different during boot up,
one of my last messages to come up said that
tg3 and eth0 broadcom were loaded. That is why
I decided to try the pings without even doing
any further trouble shooting.

Looking at the file rc.inet1.conf I see that
eth0 is set to use DHCP="yes" and it has no
IPADDRESS[0] set to blank.
no default gateway IP address set.
I assume that means this thing is really using
DHCP.

Would that be a correct assumption?

I have saved all the files on my home directory
with an extension name of .fix so that I can
compare if trouble arises again.

Shortly I will make sure I have notes on all
this new learned material, and give a recap
of what I learned here. I have been using
linux for a very long time, actually going
back to about slackware version 2 or so.
This has to be longer than 10 years. Back then
you could not even get on the internet. Maybe
the internet did not even exist, but my first
few machines did not even have X windows.
I can remember compiling the kernel back then.
When CDROM first came out they were not standard
and each worked differently. I remember I had
to go in and modify CDROM drivers and recompile
the kernel in order to get a CDROM to work.
Things have come a long way.

After I used Slackware back then I tried RedHat
and did not particularly like it. After a few
versions with Slackware I changed to SUSE. I went
with that system for a number of versions and
eventually got fed up with it, as it was trying
to work like Windows, that is, some program was
doing all the set up for you, and theorettically
you did not have to know anything. Good theory,
but in practise, it never works out, as just
demonstrated by this last problem you have been
working on with me. So I switched back to Slackware
a few versions ago and quit doing SUSE.

As I said, I will try to do a recap, review of this
thread, telling what all I have learned. Hopefully
this box will keep working for awhile now, if not,
I guess I will have to learn a little more.

Thanks again for the help, and as the guy said,
"if it were easy everyone would run a marathon".
 
Old 12-08-2010, 03:57 PM   #49
onebuck
Moderator
 
Registered: Jan 2005
Location: Summer Midwest USA, Central Illinois, Winter Central Florida
Distribution: SlackwareŽ
Posts: 13,610
Blog Entries: 34

Rep: Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793
Hi,

I am glad to here things are good to go!


What I like to is have a written system log for each machine. That way I can track & back track whenever necessary. Hard copy is great for that. I don't even erase but strike through and overwrite or reference else where. Just a habit that has been carried on for years. The only thing is that fire or physical lose will prevent the use of a well maintain system log with good notes. Somewhat like a system diary. My backups have saved me more than once.


I even have secondary backup for each systems configuration files(grandfathered else where). Useful!


As to the '/etc/rc.d/rc.inet1.conf' question, if the DNS is properly setup then the gateway doesn't need defined within. That will depend on the server or local setup;

Quote:
excerpt from 'man resolv.conf';
DESCRIPTION
SYNOPSIS
/etc/resolv.conf

The resolver is a set of routines in the C library that provide access to the
Internet Domain Name System (DNS). The resolver configuration file contains
information that is read by the resolver routines the first time they are
invoked by a process. The file is designed to be human readable and contains
a list of keywords with values that provide various types of resolver infor-
mation.

On a normally configured system this file should not be necessary. The only

name server to be queried will be on the local machine; the domain name is
determined from the hostname and the domain search path is constructed from
the domain name.
The type of problem you had really bugs me. I'll trace that bugger until the answer is found. Just like intermittent problems, dislike this type even more. Trouble-shooting these types can be both fun and frustrating at other times.

Don't forget about the
PasteBin usage. Very beneficial! PasteBin is just one of many free online services.
 
Old 12-09-2010, 10:24 AM   #50
EldonCool
Member
 
Registered: Dec 2010
Location: Nevada
Distribution: Slackware
Posts: 240

Original Poster
Rep: Reputation: 2
Things I learned in this thread:

ifconfig - configures network, used mostly at boot time.
with no arguments it gives status of network can load or
unload drivers like this: ifconfig eth0 up, ifconfig eth0 down.

lspci - lists info about all PCI buses and all devices connected
to them

ath9k is the driver for most antheros ether net cards

lsmod - shows what kernel modules are currently loaded
by formating the file /proc/modules better to read.

modprobe - can add or remove modules in the kernel.
modprobe -r whatever (removes whatever)
modprobe whatever (adds whatever)

modinfo - shows information on a module, example -
modinfo tg3
shows this on my system:
filename: /lib/modules/2.6.24.5-smp/kernel/drivers/net/tg3.ko
version: 3.86
license: GPL
description: Broadcom Tigon3 ethernet driver
author: David S. Miller (davem@redhat.com) and Jeff Garzik
(jgarzik@pobox.com)

Slackware does not use the sysvinit-functions style; it's the BSD style;
every script fot initialization is under /etc/rc.d

dmesg - gives boot messages. example:
dmesg > file.1 (puts the messages into file.1 so you
can look through them with an editor)

On Slackware you can restart the network with:
/etc/rc.d/rc.inet1 restart

/etc/udev/rules.d/70-persistent-net.rules is a file
that is auto generated with info about network cards
installed, like ether net, wireless net.

A good site for slackware network info:
http://alien.slackbook.org/dokuwiki/...ckware:network


/etc/rc.d/rc.modules - loads modules into the kernel. Has
some good comments at the beginning about loading modules.

/etc/rc.d/rc.S - System initialization script

=============================
My problem seemed to be that the system was
configuring my ether net card as eth1 and
netconfig sets up eth0. It appeared that
the system did this by loading the wireless
net first, and this somehow made the ether
net come second and it got configured as
eth1. Also I believe it only loaded the
driver for the wireless card, not the regular
ether net.

Problem appeared to be fixed by making the
system configure my ether net as eth0,
by first unloading the eth1 that the system did,
and next load the driver for the ether net hardware
which had never been loaded. Next load the
ether net again, and this time it would load
as eth0 hopefully.

The commands to do this were:
Code:
rm tg3    (remove the ether net driver eth1)
modprobe broadcom   (load driver for physical ether net card)   
modprobe tg3        (load driver software for ether net)
These commands were put into file

/etc/rc.d/rc.netdevice

And this file was made executable, which made
it run during boot up.

Problem appeared to be solved.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

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
Network card problems in Slackware 12.1 Aled Evans Slackware - Installation 7 07-19-2008 10:29 AM
Problems setting up network with slackware 10 Cocheese1080 Linux - Newbie 1 04-01-2006 10:11 PM
Problems in Slackware w/ Network after Compiling Kernel 2.6.9 wasafiri Linux - Networking 6 12-08-2004 09:22 PM
Mouse and network problems on Slackware 10.0 with kernel 2.6.7 gyodai Slackware 2 08-13-2004 05:39 PM
Slackware 9 Network Problems wocdam Linux - Networking 6 06-12-2003 12:51 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 03:14 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