I cannot bring up ethernet devices.

Slackware 9.1. Cable modem. Ethernet card RealTek 8139.

After installing slack from CD's and rebooting the only interface that is up
is loopback. During the booting process both netcards are detected:
eth0: RealTek RTL8139 Fast ....
eth0: Identified 8139 chip type 'RTL-8139B'

eth1: RealTek RTL8139 Fast ....
eth1: Identified 8139 chip type 'RTL-8139C'
(The eth1 is not important at the moment because I had a switch attached to
that card.) Despite the fact that network cards are detected the setup
process did not probe sucessfully the network cards as there is no single
trace of rc.netdevice. So I have fond within the rc.modules appriopriate (I
think) line /sbin/modeprobe 8139too, uncommented and rebooted once again.
The module is being loaded but it does not chage anything. The eth0 is still
down. To clarify I am using DHCP in rc.inet1.conf. It is somehow strange to
me as the FreeBSD that is installed on the same computer has no difficulties
in configuring the network. Previously I have installed also RH9 and no
problem at all.

Am I doing something wrong (or not doing something).

Pips

Jan Pips wrote:
> that card.) Despite the fact that network cards are detected the setup
> process did not probe sucessfully the network cards as there is no single
> trace of rc.netdevice. So I have fond within the rc.modules appriopriate (I
> think) line /sbin/modeprobe 8139too, uncommented and rebooted once again.

may not have been necessary. hotplug may recognise the cards.

> The module is being loaded but it does not chage anything. The eth0 is still
> down. To clarify I am using DHCP in rc.inet1.conf.

dhcpcd is quite verbose in logging, so you should see what you get in your
log files. in my setup, dhcpcd log messages appear in /var/log/debug for
some reason. check where they appear on your system and see what they say.

--
Joost Kremers joostkremers@yahoo.com
Slackware doesn't have any quirks. Other distros have quirks. Slackware's
just pure Linux.

Mea culpa, mea culpa mea maxima culpa.

I have run once again netconfig and have founded (with a big suprise) that
last screen told me "You (stupid donkey) do not have TCP/IP installed".
Isn't it a default part of installation? I know that slack is known because
of its so to speak "sanity" but it really goes beyond what I have expected.
As I ma new to slack shall I understand its one of the packages - it is
somehow different from FreeBSD?

Pips

Jan Pips wrote:
> Mea culpa, mea culpa mea maxima culpa.
>
> I have run once again netconfig and have founded (with a big suprise) that
> last screen told me "You (stupid donkey) do not have TCP/IP installed".
> Isn't it a default part of installation?

nothing is a default part of installation. *you* decide what you want to
install. at best, certain packages are marked as 'required'. but you can
still choose not to install those, if you so wish.

the TCP/IP protocol is part of the kernel, and it's certainly compiled into
the stock kernels that come with slackware. all i can think of is there is
a tcpip package in the n series, which may or may not be what is
missing. it provides TCP/IP utilities.

--
Joost Kremers joostkremers@yahoo.com
Slackware doesn't have any quirks. Other distros have quirks. Slackware's
just pure Linux.

Joost Kremers wrote:
> Jan Pips wrote:
>
>>I have run once again netconfig and have founded (with a big suprise) that
>>last screen told me "You (stupid donkey) do not have TCP/IP installed".
>>Isn't it a default part of installation?
>
> nothing is a default part of installation. *you* decide what you want to
> install. at best, certain packages are marked as 'required'. but you can
> still choose not to install those, if you so wish.
>
> the TCP/IP protocol is part of the kernel, and it's certainly compiled into
> the stock kernels that come with slackware. all i can think of is there is
> a tcpip package in the n series, which may or may not be what is
> missing. it provides TCP/IP utilities.

The tcpip package includes "ifconfig" along with others.

--
Confucius: He who play in root, eventually kill tree.
Registered with The Linux Counter. http://counter.li.org/
Slackware 9.1.0 Kernel 2.4.23 SMP i686 (GCC) 3.3.2
Uptime: 5 days, 3:32, 2 users, load average: 0.03, 0.07, 0.02

Joost Kremers <joostkremers@yahoo.com> wrote:
> Jan Pips wrote:
> > Mea culpa, mea culpa mea maxima culpa.

> > I have run once again netconfig and have founded (with a big
> > suprise) that last screen told me "You (stupid donkey) do not
> > have TCP/IP installed". Isn't it a default part of
> > installation?

> nothing is a default part of installation.

This is false. The required packages are installed by default.

> *you* decide what you want to install.

Yes, you can override the defaults.

> at best, certain packages are marked as 'required'. but you can
> still choose not to install those, if you so wish.

> the TCP/IP protocol is part of the kernel, and it's certainly
> compiled into the stock kernels that come with slackware. all i
> can think of is there is a tcpip package in the n series, which
> may or may not be what is missing. it provides TCP/IP utilities.

The tcpip package is not required and, as such, is not installed by
default.

cordially, as always,

rm

OK. Problem solved.

In fact, assuming that protocols like TCP/IP and some utilc like dhcp client
are installed by default, I have uncheck those options when going through
packages for instalation. Going once again through the instalation and
marking appriopriate packages I had succesfully installed slack with network
enabled. I have to admit however, it suprised me a lot. AFAIK unix and linux
are mainly recognized as excellent net systems so lack of default TCP/IP
necessary tools as well as lack of dhcp client within default set is to me
rather strange. I have to admit also that the speed of slack suprised me
very positively. Having no precise benchmark I can see the X + KDE is
starting amazingly fast, much, much faster than RH it does not have also
irritating screen flickering as RH9.

Long live slack and bsd.

Pips

Jan Pips wrote:
> In fact, assuming that protocols like TCP/IP and some utilc like dhcp client
> are installed by default, I have uncheck those options when going through
> packages for instalation.

like i said, nothing is "default" in slackware, in the sense that you
cannot turn it off. you could even skip installing aaa_base.

but surely those packages you unselected were marked "REQUIRED"?

> Going once again through the instalation and
> marking appriopriate packages I had succesfully installed slack with network
> enabled. I have to admit however, it suprised me a lot. AFAIK unix and linux
> are mainly recognized as excellent net systems so lack of default TCP/IP
> necessary tools as well as lack of dhcp client within default set is to me
> rather strange.

IMO it's not strange that you can leave out a dhcp client. not everyone
needs it. as for basic TCP/IP tools, yeah, there won't be many sites
without them. but suppose someone wants to use an old computer as an mp3
player in their car? (some people do that, in fact.)

so basically, you can never predict every use that people may come up with,
so it's good that even packages that would seem essential can be skipped
when installing.

> Long live slack and bsd.

hear, hear!

--
Joost Kremers joostkremers@yahoo.com
Slackware doesn't have any quirks. Other distros have quirks. Slackware's
just pure Linux.