Long story, but I decided that I would dip my toes into Linux by installing it on an old Pentium 133. I tried Mandrake but couldn't get through the install because it would lock up my mouse so I couldn't finish the install, then I got RH7.1 to install, but I couldn't get the old ISA NE2k compatible nic to work, so then I tried it with a "Linux compatible" D-Link 530tx+ or whatever it is that no one can make work, but that fails on startup and even by following the steps on D-Links page and by trying several different methods described in this forum, I decided that I wasn't smart enough to make that work, so I was about to give up.
Then RH 7.2 came out, so I thought that might make the difference, so I installed that, but no luck on the d-Link NIC. Then I found one of my boxen had yet another NIC in it, which Windows recognizes as an AEF-360TX Family PCI Fast Ethernet Adapter. RH recognized it as soon as I installed it, and it sees it as "RTL8139, SMC EZ Card Fast Eth" on eth0. Unfortunately, I still can't make it work. Earlier tonight I was able to get it to ping itself, but no one else. But then after a reboot, it would only say network is unreachable when pinging itself.
I tried to follow the "install a NIC" NHF, but it isnt' newbieized enough for this n00B.
Thanks for any help that can be offered. I will be eternally grateful.
madfgurtbn
12-10-2001, 06:26 PM
I haven't had much time to work on this problem since I posted the question, but I've got a few minutes tonight so I'll start working it through here, and post what I find as I go.
I'm trying to work through this howto: http://www.ibiblio.org/mdw/HOWTO/Ethernet-HOWTO-1.html#ss1.3
[ 10 December 2001: Message edited by: madfgurtbn ]
madfgurtbn
12-10-2001, 06:53 PM
Ah, screw it. That howto isn't helping me.
I'm working now on the "How to install a NIC" NHF at http://www.linuxnewbie.org/nhf/intel/network/nicinstall.html
It says: "-AS ROOT: Install module with
insmod rtl8139
"no module buy that name found"
Then the NHF says,
"-List the modules that are installed with lsmod
if you didn't get any errors during the module install and it was listed, then the module should work."
But I did get an error "module not found", and I don't know what lsmod means. Her's my lsmod:
But I can't make that happen. I guess I'm going to have to go find out how to run netcfg.
If it gets annoying for me to post these things, just let me know and I'll stop. I promise.
EDIT: OK, here we go. Apparently Xterminal means within the GUI, I thought the terminal was the command line DOS window looking thingy. I got Network Configuration up in RH by clicking on RUN in the startup menu, and now we've got lots of info to work with... Unfortunately the tabs don't match up with the tabs described in the NHF.
So her's what my tabs say:
Hardware tab:
Description: RTL8139, SMC EZ Card Fast Eth
Type: Ethernet
Device: eth0
click on Edit, and it brings up a dialog with the following choices and settings:
Adapter: RTL8139, SMC EZ Card Fast Ethernet
Device: eth0
Resource
IRQ: 9
Mem:
Io:
IO1:
IO2:
DMA0:
DMA1:
I think I tried experimenting with that IRQ setting a couple of times, but I don't remember now what settings I tried.
Ooops, just got another error when I tried to click OK in that dialog: "Warning: the Ethernet card could not be initialized. Please verify your settings and try again."
I don't think I was getting that error before when I tried to change IRQs in this dialog.
I just tried all available IRQ's in that dialog to no avail, each one from unknown to 15 gives the same error (which you have to drag the box into view in order to acknowledge the OK button.)
[ 10 December 2001: Message edited by: madfgurtbn ]
Anyway, moving along the tabs in Network Configuration, we get to
Devices
Nickname: eth0
Type: Ethernet
Highlight eth0 and click edit brings up dialog "Ethernet evice"
Nickname eth0
"Activate device when computer starts" is checked
"Allow all users to enable and diable the device" unchecked
Wondering if Hostname shouldn't have something there. when I run a DOS type terminal window it shows root@mstechlab2. I thought that mstechlab2 WAS the hostname?
[ 10 December 2001: Message edited by: madfgurtbn ]
Continuing within the Ethernet Device dialog to the
Hardware Device tab:
"Enable Device Alieas support" is unchecked
"Hardware Device": eth0 (RTL8139, SMC EZ CArd Fast Ethernet)
"Alias": 0
"Use Hardware Address" is checked
"Hardware Address": 00:40:33:d2:ad:7f
(I think I got that by clicking the Probe for Address button last time I was monkeying around in these dialogs)
That ends that set of dialogs under the Devices tab of Network Configuration.
Also shows what I believe is the loopback IP (whatever that is)
IP: 127.0.0.1
Name: localhost.localdomain
Aliases: localhost
Finally moving on to the DNS tab of Network Configuration, we find
Hostname: mstechlab2
Domain: myemployer.xxx.xx.xx
primary DNS 207.177.xxx.xxx
Secondary DNS 207.177.xxx.xxx
teritary DNS: blank
DNS SEarch Path
Domain: blank
[ 10 December 2001: Message edited by: madfgurtbn ]
[ 10 December 2001: Message edited by: madfgurtbn ]
madfgurtbn
12-10-2001, 09:23 PM
So what next. The NHF goes on about pinging some other machines, but I think I need to figure out 2 things (which might be basically the same problem).
1. that rtl8139 not found when I tried insmod.
2. Cannot activate NIC. That might be because fo the rtl8139 thing.
But now I see that that there's one more thing in that NHF: "* Last thing that you should have to do, is tell your machine which module to use when it tries to start eth0. You will do that by adding the folowing line to your [b]/etc/conf.modules file.
alias eth0 rtl8139 "
But I can't find [b]/etc/conf.modules
I went into the file explorer by clicking on the desktop icon "root's home", and the address bar says Location: /etc
There are numerous subdirectories under /etc but no folders named conf.modules, and no files in the righthand pane called conf.modules
Apparently that [b] thing in [b]/etc/conf.modules means something.
I don't see a search tool int he file explorer. Will have to see if I can find one to search for conf.modules (That's a filename right?)
EDIT: I think what I'm really learning here is that my old box isn't going to handle RH7.2. It's just too slow. I fished around a little in the start menus for a search tool, but couldn't find anything, so i went to help. I'm typing this while waiting for the darn thing to load the Gnome users guide. It seems that it will never stop grinding while it renders the page in Galeon. Maybe I'd be better off to spend my time building a new box.
[ 10 December 2001: Message edited by: madfgurtbn ]
I found the Gnome search tool, but did't find the conf.modules file
The search tool built the following command:
find / '!'-type d -name 'conf.modules' -print0
It spent some time searching, but came up with ERROR that said
"find: /proc/1588/fd: No such file or directory
find: /proc/1589/fd: No such file or directory"
[ 10 December 2001: Message edited by: madfgurtbn ]
fancypiper
12-11-2001, 02:19 AM
madfgurtbn muttered (apparently to himself) "But I can't find /etc/conf.modules"
If you had your box running at 4 AM, it runs a process called "ubdatedb" which reads all the files on your mounted drives and builds a database of them. You can do a very fast search for things with the command (either in a virtual terminal or an x terminal) locate <something> and you get a list of everything that contains <something> in the path or filename.
If you turn your computer overnight, as root command updatedb and the database is built after the drives stop spinning.
My RedHat 7.2 does this a few minutes after bootup if it has gone past the cron job time. Yours may do this as well.
An earlier version of RedHat called that file /etc/modules.conf.
Maybe you can get started that way.
I am just starting to learn local networking myself, so I am interested in your experiences. Please continue.
DMR
12-11-2001, 05:19 PM
A long story indeed; I'll try to sort through it from the beginning:
ifconfig gives me this
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:48 errors:0 dropped:0 overruns:0 frame:0
TX Packets:48 errors:0 dropped:0 overruns:0 carrer:0
collisions:0 txqueuelen:0
RX bytes:3148 (3.0Kb) TX bytes:3148 (3.0 Kb)
No NIC up and running, just the loopback device (lo). Try "ifconfig -a", which will show stats for all interfaces, active or not. You should then see something for "eth0", your ethernet card. Also try using the "lspci" command and see if it outputs any information on your card.
!!Turn off Plug-N-Play support in your BIOS if you haven't done so already!! It can cause resource (IRQ, I/O address) conflicts with some cards. Type "cat /proc/interrupts" and "cat /proc/ioports" to view IRQ and I/O assignments. Look for conflicts.
it says: "-AS ROOT: Install module with
insmod rtl8139
"no module buy that name found"The full name of the module is "rtl8139.o", try that. Also- newer distros are starting to use the "8139too.o" module instead. ... I don't know what lsmod means. List modules; we can see from the output of lsmod that the 8139 module is indeed not there. Do lsmod again after trying insmod with the module names I just gave you. I think I tried experimenting with that IRQ setting a couple of times, but I don't remember now what settings I tried.
That doesn't really work with PCI cards anyway. If you have an IRQ conflict, try rearranging the slot order of your PCI cards. Wondering if Hostname shouldn't have something there. when I run a DOS type terminal window it shows root@mstechlab2. I thought that mstechlab2 WAS the hostname?This can depend on what you're connnecting to and how. For instance, if you're connecting to the Internet via a cable modem, your hostname will need to be that assigned you by your ISP. Continuing within the Ethernet Device dialog to the...The rest of that looks correct.
In terms of finding /etc/conf.modules, as fancypiper said, some distros call(ed) it /etc/modules.conf.
I hope some of this helps; repost if you have more questions.
:)
[ 11 December 2001: Message edited by: DMR ]
madfgurtbn
12-12-2001, 08:56 AM
Originally posted by fancypiper:
[QB]madfgurtbn muttered (apparently to himself) "But I can't find /etc/conf.modules"
LOL! Yeah, I was basicallymuttering to myself. Thanks to both of you for your help and suggestions. I'll work on it today, and post my results...
madfgurtbn
12-12-2001, 09:10 AM
"locate modules.conf" worked great.
Also easily found the file in the explorer and opened it with gedit to see the following:
alias parport_lowlevel parport_pc
alias eth0 8139too
options 8139too irq=9
The reason I was supposed to open the conf.modules file was to add teh line "alias eth0 8139", but it looks like it's already in there as "alias eth0 8139too" so I'm going to leave that one alone and move on.
ifconfig -a gives me the same thing I got with just ifconfig, which was local loopback.
Not sure why..
Trying lspci
The relevant line appears to be:
00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139 (rev 10)
Tried insmod rtl8139.o
"No such file or directory
Tried insmod 8139too.o
"No such file or directory"
Just for fun tried insmod rtl8139too.o
"No such file or directory"
[ 12 December 2001: Message edited by: madfgurtbn ]
lsmod shows the same as earlier:
Module Size Used by
ide-cd 26592 0 (autoclean)
cdrom 29504 0 (audoclean) [ide-cd]
soundcore 4208 0 (autoclean)
binfmt_misc 6064 1
autofs 11232 0 (autoclean) (unused)
ipchains 36000 0
ext3 61936 2
jbd 38976 2 [ext3]
So far, I see two main problems. ifconfig -a shows nothing about my card, and no 8139 module installed. I'm going to turn off the PNP support, as directed, but before I do that, here's the output of
So if I'm understanding cat /proc/ioports, there is an io range specified for my card, and that range is not conflicting with any other devices. I'm not sure if that range has been assigned to the card, though. I remember having to assign a range to some other cards.
I'll try turning off PNP in the bios now, but won't have time until later to do much more.
[ 12 December 2001: Message edited by: madfgurtbn ]
Switched PNP to manual in the BIOS:
Bios shows the following
irq3 assigned to: Legacy ISA
irq4 assigned to: Legacy ISa
irq5 assigned to PCI/ISA PnP
irq-7 assigned to Legacy ISA
irq-9 assigned to PCI/ISA PnP
IRQ-10 assigned to PCI/ISA PnP
irq-11 assigned to pci/isa pnp
irq-12 assigned to pci/isa pnp
irq-14 assigned to Legacy ISa
irq-15 assigned to Legacy ISA
DMA-0 assigned to PCI/ISA PnP
DMA-1 assigned to PCI/ISA PnP
DMA-2 assigned to PCI/ISA PnP
DMA-3 assigned to PCI/ISA PnP
DMA-4 assigned to PCI/ISA PnP
DMA-5 assigned to PCI/ISA PnP
DMA-6 assigned to PCI/ISA PnP
DMA-7 assigned to PCI/ISA PnP
Booting into RH7.2 ...
[ 12 December 2001: Message edited by: madfgurtbn ]
Whenit's booting up, it always spends 3 or 4 minutes at "starting sendmail", then continues as normal. Is that because the NIC isn't working or is that a separate issue?
[ 12 December 2001: Message edited by: madfgurtbn ]
[ 12 December 2001: Message edited by: madfgurtbn ]
madfgurtbn
12-14-2001, 07:57 PM
All right, I'm back at it again tonight.
I had a script kiddie here take a look at my setup, and he wasn't able to figure out my problem, but I'm not sure of what all he did.
I decided to delete the eth device from Network Configuration and try again from scratch.
I can see the device in cat /proc/ioports, but not in cat /proc/interrupts
Still not sure why that it doesn't show in interrupts.
It does show in lspci as:
00:09.0 Ethernet controller: Realtek Semiconductor jCo., Ltd. RTL-8139 (rev 10)
I got the bright idea of checking with the manufacuture's (Addtron) site for any info that might help, and it looks like I might be on the right track. I got the drivers on a floppy, and am following the instructions.
The instructions had me first mkdir /temp
Then copy the rtl8139.c driver and an application called trans to /temp.
trans is apparently supposed to compile and copy the drive to linux source code. But when I ran trans, it didn't go exactly as planned. THe output was:
Compiling...
/temp/trans: gcc: command not found
Done!
So does that mean that it worked or not?
madfgurtbn
12-14-2001, 08:04 PM
The NIC install readme goes on:
B. RedHat
------
1) You must create or modify /etc/rc.modules to insmod driver.
This file will run at boot time. add a line in rc.modules:
cd /etc/rc.d/rc.modules
vi rc.modules
insmod /your driver' path/rtl8139.o
chmod 755 /etc/rc.modules
ex: insmod /usr/src/linux/modules/rtl8139.o
Note: parameter can be added by adding options=... behind
the istrruction
ex: full duplex: :(bit 4 of 'options')
'insmod rtl8139.o options=16'
(run 'lsmod' to see if the module is inserted)
2) Use 'netconf' to configure you network environment.
3) Reboot your system.
++++++++++++++++++++
++++++++++++++++++++
Sure that sounds easy, but I'm having some trouble understanding it. it wants me to edit a file called /etc/rc.d/rc.modules but that file doesn't seem to exist..
here's what's in /etc/rc.d/
a number of folders: init.d, rc0.d, rc1.d, rc2.d, rc3.d, rc4.d, rc5.d, and rc6.d
Also, 3 files called rc, rc.local, and rc.sysinit
the other problem is where it says "insmod /YOURDRIVER'S PATH/rtl8139.o
I'm not sure what the path is to my drivers. It gives the example of /usr/src/linux/modules/rtl8139.o but I don't have a linux directory under /usr/src
Does it mean the path to where the driver is now? Which is the /temp directory I transferred the driver to from the a: drive?
[ 14 December 2001: Message edited by: madfgurtbn ]
DMR
12-14-2001, 09:32 PM
Originally posted by madfgurtbn:
<STRONG>
Compiling...
/temp/trans: gcc: command not found
Done!
So does that mean that it worked or not?</STRONG>Probably not. It sounds like the compiler (gcc) isn't installed on your system, or isn't where trans expects it to be. gcc needs to be installed in order for the compile to work. My bet is that you don't have a working rtl8139.o module in /temp.
Also, the lack of an assigned IRQ and the fact that ifconfig -a shows squat for eth0 is kind of a Bad Thing.
I'm at work right now, so I can't poke around in my Linux box for ideas, but I'll be home in a couple of hours. In the mean time, could you post the results of the following two finds (perform as root):
find / -name rtl8139.o
find / -name 8139too.o
madfgurtbn
12-15-2001, 02:34 PM
Thanks, DMR. You are a true hero for reading through all my meanderings to help out with this problem.
find / -name rtl8139.o
You have new mail in /var/spool/mail/root
So I looked in the /var/spool/mail directory and did find a mail file called root, but it doesn't look like it is related to my find / -name rtl8139.o command. The last entries are from 4:00 a.m., and appear to be from a cron job that cannot find some files it needs.
I ran the find / -name rtl8139.o again, and it grinded away on the hard drive for a while, and eventually just produced another command prompt, but no output.
Trying the 2nd find command now--
That one worked a little better:
[ 15 December 2001: Message edited by: madfgurtbn ]
madfgurtbn
12-18-2001, 05:54 PM
I'm back at it again for a while tonight. I'm thinking I need to figure out why my card isn't showing up in cat /proc/interrupts so I'm looking here for advice: http://www.scyld.com/expert/irq-conflict.html
When you encounter this error message you can run the ifconfig or dmesg programs and compare the requested IRQ with the contents of /proc/interrupts to determine the device conflicts. The IRQ a PCI device uses is also reported in /proc/pci or by using the lspci program
I tried cat /proc/pci, and it does show the card! I'm so relieved:
Bus 0, device 9, function 0:
Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139 (rev 16).
IRQ 11.
Master Capable. Latency=32. Min Gnt=32.Max Lat=64.
I/O at 0x6100 [0x61ff].
Non-prefetchabel 32 bit memory at 0xf1000000 [0xf10000ff].
Now if I'm reading that right, its on IRQ 11, and I think when before I delet4ed the device from Network Configuration, it was on IRQ 9.
cat /proc/pci also shows the the VGA controller on irq 9. Before I deleted the NIC from Network Configuration, it was showing on irq 9, IIRC. So maybe that's my problem.
madfgurtbn
12-18-2001, 06:01 PM
Well, now as I look under all these windows I have open, there's a dialog box open called "pci" which shows almost the same, but not quite the same, info as cat /proc/pci did.
Here's the relevant info on the ethernet contorller:
00:09.0 Ethernet controller: realtek Semiconductor Co., Ltd. RTL-8139)rev 10)
Subsystem: Addtron Technology Co, Inc.: Unknown device 1360
Flags: bus master, medium devsel, latency 32, IRQ 11
I/O ports at 6100 [size=256]
Memory at f1000000 (32-bit, non-prefetchable) [size =256]
Capabilities: [50] Power Management version 2
it also shows the VGA controller on IRQ 9
madfgurtbn
12-18-2001, 06:43 PM
On another front, I'm trying to get this gcc command to work, so I can insmod the right mod.
According to this: http://gcc.gnu.org/ml/gcc-help/1999-q3n/msg00299.html
There are three possible cuases of this problem:
1). gcc is not installed on this system
2). gc is not installed corectly on this system.
3) your PATH variable does not include the directory where gcc is located.
Try finding out where gcc is, then check permissions on the files and
directories, then check the PATH. ont of these should cure it.
But that doesn't help a newbie much.
DMR
12-18-2001, 10:08 PM
Does anything else use IRQ 11? It isn't always the end of the world if a couple of devices cluster on an IRQ, but I'm just curious. If you do have a conflict, you can try rearranging the slot order of the PCI cards to "reshuffle" IRQ assignments.
I suppose it is possible that your particular card won't work with the 8139too module, which is what you have on your system. If that's the case, we'll have to get you going with the compiler.
Use the find command again to look for gccfiind / -name gccIf this just churns for awhile and drops you back at a command prompt, then gcc isn't installed. You'll have to install the package, but I can't tell you exactly which RPM you need, as I don't use that version of Redhat.
If it does find the program, note the entire path. Type echo $PATH to view your current PATH variable. If gcc's directory is already included in the PATH, then something is probably misconfigured. If the directory is not in the PATH, add it. I think it goes like this:export PATH=$PATH:/path/to/gcc
Hope this gives you a little to chew on. I've got to sign off for now, but I'll be back in a few hours; let me know what happens.
madfgurtbn
12-19-2001, 10:48 AM
find / -name gcc returned nothing.
I'm going to have to figure out how to get gcc..
madfgurtbn
12-19-2001, 11:10 AM
Found redhat's instructions for installing rpm's from the install cd here:
Red Hat (http://www.redhat.com/docs/manuals/linux/RHL-7.2-Manual/getting-started-guide/installing-cd-rpms.html)
Unfortunately, that site says to goto http://docs.redhat.com/ to find out which rpm I need. But that site is unavailable right now.
I've tried some google and a few other sites, but no luck on finding the correct rpm to install. There are a couple hundred in that folder on the cdrom, it looks like. I tried a search for *gcc* in that folder, no luck.
[ 19 December 2001: Message edited by: madfgurtbn ]
eflashj
12-19-2001, 12:57 PM
Hi,
I didn't read the entire thread, so forgive me if I'm repeating or off topic now. I have the same NIC in my box. The driver I use is via-rhine. You should be able to choose that driver from netconf or linuxconf.
Hope that gets it up for you.
Ed
madfgurtbn
12-19-2001, 01:47 PM
Originally posted by eflashj:
<STRONG>Hi,
I didn't read the entire thread, so forgive me if I'm repeating or off topic now. I have the same NIC in my box. The driver I use is via-rhine. You should be able to choose that driver from netconf or linuxconf.
Hope that gets it up for you.
Ed</STRONG>
Thank you for your assistance, it is not OT or redundant at all.
I tried using the network configuration tool to install hardware device eth0. The only via device was "VIA VT86c100A Rhine-II PCI. but that came back as "unable to activate device".
I then went to the command line and tried insmod via-rhine and got the following response:
Using /lib/modules/2.4.7-10/kernel/drivers/net/via-rhine.o
/lib/modules/2.4.7-10/kernel/drivers/net/via-rhine.o: init_module: No such device
Hint: insnmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
It looks like they are calling the via-rhine drive "via-rhine.o", so I tried "insmod via-rhine.o", but that just returned "no such file or directory"
jlany
12-19-2001, 09:34 PM
Let's slow down a bit on this thread. On 12/15 after a suggestion from DMR you reported the following:
find / -name 8139.too.o
/lib/modules/2.4.7-f10/kernel/drivers/net/8139too.o
Then on 12/18 you reported this after doing a cat /proc/pci:
Bus 0, device 9, function 0:
Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139 (rev 16).
IRQ 11.
Master Capable. Latency=32. Min Gnt=32.Max Lat=64.
I/O at 0x6100 [0x61ff].
Non-prefetchabel 32 bit memory at 0xf1000000 [0xf10000ff].
This tells us that you have a NIC that is based on the Realtec RTL-8139 chip and that you have the 8139.too driver for this NIC configured as a module in the proper location. Just do a 'insmod 8139.too' and let us know what happens.
DMR
12-20-2001, 03:21 AM
jlany,
On further inspection, you might have something there. It's a small point, but previous posts said "I tried insmod 8139too.o", as opposed to "insmod 8139too" (no .o). IIRC, you don't have to specify the ".o" in the module name with insmod. It might not make a difference, but then again...
[ 20 December 2001: Message edited by: DMR ]
madfgurtbn
12-20-2001, 12:56 PM
Originally posted by DMR:
<STRONG>jlany,
On further inspection, you might have something there. It's a small point, but previous posts said "I tried insmod 8139too.o", as opposed to "insmod 8139too" (no .o). IIRC, you don't have to specify the ".o" in the module name with insmod. It might not make a difference, but then again...
[ 20 December 2001: Message edited by: DMR ]</STRONG>
HEY! Something happened and I think it was a good thing. I tried insmod 8139too and received the following response:
Using /lib/modules/2.4.7-10/kernel/drivers/net/8139too.o
I think that's the first time I"ve tried insmod and received anything other than No such file or directory. I'll investigate further and report back!
madfgurtbn
12-20-2001, 01:11 PM
Well, we're on the right track, but I'm still not done. That module worked, and I was able to add the NIC in Network Configuration, but so far unable to ping anything-- ping just gives the response "network is unreachable"
The nic shows up in ifconfig -a
It does not show up in cat /proc/interrupts, however.
It does show up in cat /proc/ioports
I'm going to try a few things and get back to this later.
madfgurtbn
12-20-2001, 01:34 PM
:confused:
Now after a reboot, it doesn't show up in ifconfig -a ???
:mad:
jlany
12-20-2001, 08:22 PM
Originally posted by madfgurtbn:
<STRONG> :confused:
Now after a reboot, it doesn't show up in ifconfig -a ???
:mad:</STRONG>
To get the module to load automatically at every boot, you now have to add a line to your 'etc/modules.conf' file like so : 'alias eth0 8139.too'. If you don't have this file, create it with your favorite editor. To 'ping' a url on the net,you need to add the nameserver addy's provided by your ISP to the 'etc/resolv.conf' file like so:
nameserver 151.202.0.84
nameserver 151.203.0.84
Again, if this file doesn't exist, create it.
DMR
12-20-2001, 10:15 PM
Hey, progress!
Follow jlany's instructions and see what happens. If you can't ping the outside world, you should at least be able to ping the card's IP at that point.
Also, if everything is 100% joy, you should also be able to see the card in the output of ifconfig, even without using the "-a" option.
/me crosses fingers...
madfgurtbn
12-21-2001, 01:10 PM
Originally posted by jlany:
<STRONG>To get the module to load automatically at every boot, you now have to add a line to your 'etc/modules.conf' file like so : 'alias eth0 8139.too'. </STRONG>
When I opened etc/modules.conf, I found the following:
alias parport_lowlevel parport_pc
options 8139too io=0x6100 irq=11
alias eth0 8139too
So it appears that the alias eth0 line is there, although the "8139too" is slightly diffeent than the "8139.too" in jlany's post. I won't try to change that yet, then.
ifconfig -a shows only the loopback, same with just ifconfig
I'm going to go back and do what I did yesterday to see if I can get it to show it's face in config -a again.
jlany
12-21-2001, 08:31 PM
Me bad! Typo for the 'etc/modules.conf' file. It should be as your's indicates, 'alias eth0 8139too'. However you also have a line in there 'options 8139too io=0x6100 irq=11'. For the time being, open your favorite editor and place a hash mark '#' before that line, save your changes and reboot. The hash will cause Linux to ignore that line.
Your /etc/resolv.conf file looks OK. Just double check and make sure the nameserver IP's are correct. Good luck.
DMR
12-21-2001, 11:18 PM
Originally posted by jlany:
<STRONG>Me bad! Typo for the 'etc/modules.conf' file. It should be as your's indicates, 'alias eth0 8139too'. However you also have a line in there 'options 8139too io=0x6100 irq=11'. For the time being, open your favorite editor and place a hash mark '#' before that line, save your changes and reboot. The hash will cause Linux to ignore that line.</STRONG>Right on both counts. It's 8139too, not 8139.too, and you should try commenting out the "options 8139too io=0x6100 irq=11" line. That works for ISA cards, but PCI beasties aren't assigned that way.
DMR
12-22-2001, 09:41 PM
Originally posted by madfgurtbn:
<STRONG>[CODE]ifconfig -a shows only the loopback, same with just ifconfig</STRONG>
Argh. It sounds like you still might have an IRQ conflict. Try turning off Plug-N-Play support in your BIOS. You can also try putting the NIC in another PCI slot. That will often force the 'puter to assign a different IRQ to the card.
madfgurtbn
01-17-2002, 04:36 PM
I just wanted to thank everyone who helped me out in this thread.
In case you are wondering, I have at least for now given up in trying to get RH going on that old box (although I would like to eventually use it as a terminal). I bought a $20 Linux book which had a good enough description of how to use fips to repartition without destroying the data already there that I got brave and tried it on one of the new Win boxes here, and it worked very well (except I wasn't smart enough to format the new partition without doing a complete install and now I don't have any swap partition, but I'll deal with that some other time) Anyway, I think now that I've had that experience, I am going to just bite the bullet and set my main box up for dual boot. I have been afraid to do it because I can't afford the time it would take to restore my Windows stuff if I caused a disaster.
Anyway, thanks again for all your help. Even though we didn't get it working, it was a terrific learning experience, and I hope sometime I can return the favor.
jlany
01-18-2002, 07:38 PM
Originally posted by madfgurtbn:
<STRONG>I just wanted to thank everyone who helped me out in this thread.
In case you are wondering, I have at least for now given up in trying to get RH going on that old box (although I would like to eventually use it as a terminal). I bought a $20 Linux book which had a good enough description of how to use fips to repartition without destroying the data a
lready there that I got brave and tried it on one of the new Win boxes here, and it worked very well (except I wasn't smart enough to format the new partition without doing a complete install and now I don't have any swap partition, but I'll deal with that some other time) Anyway, I think now that I've had that experience, I am going to just bite the bullet and set my main box up for dual boot. I have been afraid to do it because I can't afford the time it would take to restore my Windows stuff if I caused a disaster.
Anyway, thanks again for all your help. Even though we didn't get it working, it was a terrific learning experience, and I hope sometime I can return the favor.</STRONG>
Yep! I was wondering what became of you. For what it's worth, I woudn't attempt to dual-boot. I've read to many horror stories in my time just hanging out here at LNO. With my setup, I can run three different flavors of Linux or, God Forbid, Win 98 ( installed on a 540 Meg drive). The way I do it is I have IDE Mobile racks for each distro with it's own hard drive. I just pop in the rack with the distro I want to use at the moment, and away I go. IMHO it's the way to go without causing undo grief.The racks can be had for $10 to $15 each and I obtained mine using eBay. This is the way I've been doing it for the past four years.
Whatever way you get to use Linux, good luck to you and hope to see you back here at LNO, learning and contributing. Chaio!
madfgurtbn
02-06-2002, 08:25 PM
Originally posted by jlany:
<STRONG> For what it's worth, I woudn't attempt to dual-boot. I've read to many horror stories in my time just hanging out here at LNO. </STRONG>
I'm glad to report that I'm officially dual-booting as of today. It's probably a good thing I didn't happen to see this quote from you until after I got it all done; it certainly would have scared me off. :)
It took longer than I planned because I had a real hard time getting WinMe to backup, then defrag my drive, which was necessary before repartitioning. I wouldn't recommend a newbie attempting it their first time on a production box, but after practicing on another, I found Fips to be relatively simple and safe to use on my hard drive, so that backup that took me so long won't be necessary yet. The Redhat 7.2 install was as flawless on the first try.
I guess I'm officially on board the Linux train now.
jlany
02-09-2002, 11:59 AM
The post wasn't meant to 'scare you off' from attempting to 'dual-boot'. It was meant to make you aware that doing so is inherently more troublesome and prone to system instability to the Linux neophite. I've come to believe that it is probably one of the major reasons users get 'turned off' to Linux, because they can't get it to perform correctly. However, this is solely my opinion and I am aware that many users have had little or no difficulty setting up their systems that way.
That being said, I'm happy that you have successfully set it up and are now officially on board. :)
[ 09 February 2002: Message edited by: jlany ]
justlinux.com
Copyright Internet.com Inc. All Rights Reserved.