🚀 go-pugleaf

You might want to try opening your file /etc/modules.conf, and adding the
following line:

alias eth0 rtl8139

Then reboot.

I can't promise that this will do the trick to get eth0 working. This line
will install the driver for the rtl8139 card (it appears that is the one
you have) and tell it to use eth0.

Also try running (as root)

/sbin/ifup eth0

Sometimes, network cards aren't configured to start on bootup. You would
have to edit /etc/sysconfig/network-scripts/ifcfg-eth0 to make it work.

Note: while file names are fairly standardized, the above are true for RedHat and
may not necessarily apply to your distribution.

As for the modem, that is often very tricky. Many modems will only work
under Windows in the first place. Some such modems now were made to work
under Linux, as well. Try searching Google for the term "linmodem".

On Wed, 18 Dec 2002 09:49:17 +0000, adsiz wrote:

> Folks,
> 
> I have recently purchased a PC with Thizlinux on it (very much like Redhat)
> . It came with  a NIC card as well as a PCI modem.    Unfortunately neither
> device is working
> since day one.  (I am now using an older PC running windows 98 to send this
> message Supposedly manufacturer tested this system but I am having hard time
> believing it. Support CDs and the book emphasizing WINDOWS implying that
> they really built this machine not for linux but windows. And I am not
> getting any significant support other then "bring it back to the store we
> will see what is wrong with it.)
> 
> I am a newbee in Lunix but I thought perhaps there is a set up problem that
> I can fix  instead of taking the PC to the shop I bought from (50 miles away
> from home). But I spent numerous hours with no success.
> 
> Here is the brief summary of the situation:
> 
> Both PCs are connected to the Linksys router which is the connected to the
> cable modem.
> Router lights shows both PC are connected OK.
> I have disabled ZoneAlarm that is on the old PC just in case.
> I have done LAN settings through ThizLinux's KDE interface.  with NO luck.
> 
> 
> dmesg:             shows that the LAN card (on board 8139)  is detected. But
> no mention of eth0.
> 
> /proc/ioports:   shows that the LAN card (on board 8139)  is detected. But
> no mention of eth0.
> 
> ifconfig:            only lists "lo". ie. there is no mention of "eth0".
> 
> route -n      : shows on only    127.0.0.0 , no other ip address.
> 
> /etc/sysconig/network-scripts/ifcfg-eth0 :   shows that Wan IP address of
> the router is picked up by the LAN card as IPADDR and BOOTPRO is "dhcp".  So
> it seems NIC is communicating with the router somehow.
> 
> Attempt to add eth0 with /sbin/ifcfg        replies with the message that
> the device does not exist.
> 
> What is it that needs to be done to make this device work?
> I'll appreciate your comments
> .
> Adsiz

1- lsmod to see if the 8139 module is loaded.  
2 - yes, go to 4. .  No?  run "modprobe 8139"  (if this doesn't work
try rtl8139 and/or 8139too)
3 - did it find the nic?  run lsmod again
4 - initialize eth0 with pump or dhcpcd to get IP from router
5 - check it with ifconfig again and you should see lo and eth0
6 - surf

On Wed, 18 Dec 2002 16:51:49 GMT, "Ingo Pakleppa"
<ingo-immigration@kkeane.com> wrote:

>alias eth0 rtl8139
>
>Then reboot.


reboot?   hehe.  you must be primarlily a Windows user.  

Rebooting is never required except for a few things such as updating
the new kernel

In alt.linux Ingo Pakleppa <ingo-immigration@kkeane.com> wrote:
> You might want to try opening your file /etc/modules.conf, and adding the
> following line:
> 
> alias eth0 rtl8139
> 
> Then reboot.
> 
> I can't promise that this will do the trick to get eth0 working. This line
> will install the driver for the rtl8139 card (it appears that is the one
> you have) and tell it to use eth0.

Nope, it tells the modprobe utility that "if someone asks to load a
module called 'eth0', load 'rtl8139' instead".  It just so happens that
if you try to configure an interface that doesn't exist, the kernel
module autoloader will try to load a module of that name, and try again.

You (or a script you run like if-up) type "ifconfig eth0 <ip>" to bring
up eth0.

ifconfig calls into the kernel to configure the eth0 interface.

The eth0 interface doesn't exist yet, so the kernel executes modprobe
and tells it to load the 'eth0' module.

modprobe knows that 'eth0' really means 'rtl8139', so it tries to load
that module.

The rtl8139 module loads successfully and registers eth* devices for all
the 8139 NICs it can find, including eth0.

Modprobe finishes, and the kernel tries again to configure eth0 - this
time, it works.

ifconfig finishes.

A similar story applies when you try to open a /dev/ device node when no
driver has registered the corresponding major/minor numbers, which is
how your soundcard module auto-loads when a program first tries to use
it.

	- Kevin.

On Wed, 18 Dec 2002 18:40:12 +0000, kerernn wrote:

> On Wed, 18 Dec 2002 16:51:49 GMT, "Ingo Pakleppa"
> <ingo-immigration@kkeane.com> wrote:
> 
>>alias eth0 rtl8139
>>
>>Then reboot.
> 
> 
> reboot?   hehe.  you must be primarlily a Windows user.
> 
> Rebooting is never required except for a few things such as updating the
> new kernel

Actually, you are right. I said to reboot because the original poster
described himself as a newbie.

modprobe -a, followed by ifup eth0 should do the same thing. It's just
more complicated to explain and easier to mess up and think the
modifications were incorrect when you really just made a mistake entering
the commands. Rebooting reduces the number of variables.

Incidentally, you can do almost everything (at least, comparable actions)
in Windows (the NT family, not the DOS-based family) without rebooting,
too. Windows merely tells you to reboot after installing to make it easier
and because of a maze of dependencies. For that matter, I had a client
once who insisted that my installation program reboot when it had
completed - even though it was completely unnecessary. He actually logged
a bug "install program does not reboot".

Today, I would be happy to have a client in the first place ;-) I'm
looking for Linux work. But that's kind of off-topic.

Thanks Kerernn.
  I was able to do steps 1,2, and 3 you suggested.
  Could not make 4 work but "ifcfg eth0 add 192.168.1.9" did the trick in
bringing iup eth0.
192.168.1.9 is the adress router was supposed to give to this linuz machine
(and 192.168.1.8 to win98 machine).

I still could not surf the net but had to some tweeking (Thizlinux settings
from the GUI, LAN Browsing preferences as well as Thinzlinux config) and was
finally able to reach internet.

Then I boothed to see if I could repeat the process.  ( I got some error
during shutdown, which I did not record).

When booted I could NOT get back to the internet.   eth0 was up and running
but I cannot accees internet (http addresses) and I cannot even ping to the
other (windows) machine anymore. But I can ping the router as well as
linuxmachine itself. And these are the only 2 ip adresses I can ping to.

Also  /etc/dhcpcd/hdcpcd-eth0.info file seems to imply that linux got the
domain name DNS names etc OK,  How else do I check DNS name issues.

I am lost.
I will try again later. If you (and others) have a suggestion please let me
know.

Thanks again.
Adsiz


"kerernn" <aer44dert@jj.com> wrote in message
news:3e00a73b.9574597@nntp.ktchnr.phub.net.cable.rogers.com...
>
> 1- lsmod to see if the 8139 module is loaded.
> 2 - yes, go to 4. .  No?  run "modprobe 8139"  (if this doesn't work
> try rtl8139 and/or 8139too)
> 3 - did it find the nic?  run lsmod again
> 4 - initialize eth0 with pump or dhcpcd to get IP from router
> 5 - check it with ifconfig again and you should see lo and eth0
> 6 - surf
>

Hi, this is the same person. different name.

getting that far is 99% of the battle.  You have it done now.

Run "netconfig" and choose dhcp and it should take care of the setup.

if that doesn't work, you need to find out how your router works.
does it need the linux system to specify a gateway and dns, for
example...