From: "Alex Risselada" <risselada-a@hetnet.nl> Date: Wed, 29 Nov 2000 19:35:10 +0100 Message-ID: <0bad45647181db0NET015S@hetnet.nl> Subject: Network card trouble Hello. Last weekend I bought a netwrork card for my brand new 486 Linux server. It was "NE2000 compatible and Software Configurable" First I tried to configure the card whith the shiped diskette, which let me to set base adress, an Interupt setting. Unfotunatly, this wasn't going to work. The next thing I tried was to boot a one disk linux distro (from Toms ;) But it only showed my already working NE2000 card at adress 300 IRQ5. Then I booted the good old Windows 95, and with a lot of hacking I managed te get my card in the Hardware list, without any errors ( at IRQ11 Adr 340) I thougt maybe the card would remember it's setting when I boot back to linux, but this was a big illusion... - Any thing I forgot? - Is there maybe a test tool to check if the card is functioning? - Is it possible to attacht my 2nd Network card to the 1st network card, which are in the same conputer, without any damage? Thanks in advance.. Alex Risselada
From: Cliff Sarginson <cliff@raggedclown.net> Date: Wed, 29 Nov 2000 21:34:20 +0100 Message-Id: <00112921342001.06399@buffy> Subject: Re: [SLE] Network card trouble On Wednesday 29 November 2000 19:35, Alex Risselada wrote:
Hello.
Last weekend I bought a netwrork card for my brand new 486 Linux server. It was "NE2000 compatible and Software Configurable" First I tried to configure the card whith the shiped diskette, which let me to set base adress, an Interupt setting. Unfotunatly, this wasn't going to work.
Ok. So you set the IRQ and IO address. How did you decide which values to use ? Most of the setup diskettes will run tests on whether the card hardware is in good shape for you. The
The next thing I tried was to boot a one disk linux distro (from Toms ;) But it only showed my already working NE2000 card at adress 300 IRQ5. Then I booted the good old Windows 95, and with a lot of hacking I managed te get my card in the Hardware list, without any errors ( at IRQ11 Adr 340) This is very confusing, what hacking ?
I
thougt maybe the card would remember it's setting when I boot back to linux, but this was a big illusion... - Any thing I forgot? - Is there maybe a test tool to check if the card is functioning? - Is it possible to attacht my 2nd Network card to the 1st network card, which are in the same conputer, without any damage? Attach.. meaning ?
Thanks in advance..
Alex Risselada
With an ISA NE2000 clone. - Disable any wired in IRQ/IO, this may be something like allowing "jumperless configuration" or something similar. Turn off any jazz about plug and play as well - Determine an IRQ/IO range your Linux system regards as free, the I/0 range shouldnt be a problem (there are thousands of them believe it or not) You can get this from /proc/interrupts and /proc/ioports (just cat them). - With the card setup program see what IRQ/IO possibilities it gives you and choose one that would seem acceptable to your linux system. -Set it ! -Use the card diagnostics to test it (the plug test will fail if the card aint connected, dont worry about that) -You will need to adjust rc.config or use yast1..whatever .. to pass the IRQ/IO paramaters to the card. Assuming you are using modules. If you are using NE2000 support in the kernel image you have to do something else .. repost if that is the case.. Hope this helps Cliff
At 21:34 29/11/00 +0100, Cliff Sarginson wrote:
With an ISA NE2000 clone.
Mine is a D-Link ISA network card DE-220PCT. I suppose it fulfills these requirements.
- Disable any wired in IRQ/IO, this may be something like allowing "jumperless configuration" or something similar. Turn off any jazz about plug and play as well
It's supposed to be a plug and play card but there is no jumper on it...
- Determine an IRQ/IO range your Linux system regards as free, the I/0 range shouldnt be a problem (there are thousands of them believe it or not) You can get this from /proc/interrupts and /proc/ioports (just cat them).
I will try this. Isn't the suggestion given by YaST correct?
- With the card setup program see what IRQ/IO possibilities it gives you and choose one that would seem acceptable to your linux system.
There is no such setup program for Linux in my case.
-Set it ! -Use the card diagnostics to test it (the plug test will fail if the card aint connected, dont worry about that) -You will need to adjust rc.config or use yast1..whatever .. to pass the IRQ/IO paramaters to the card. Assuming you are using modules. If you are using NE2000 support in the kernel image you have to do something else .. repost if that is the case..
Hope this helps Cliff
Maybe some more info will be useful. I thank you in advance. Patrick
Problem: borg:~ # hwclock --show Wed Apr 4 00:50:19 2001 -0.147254 seconds (Time is actually 7:50) After looking over the man pages for hwclock, I came across this piece of info: --utc --localtime ... If the adjtime file doesn't exist, the default is local time. ... . o O ( Why, what is the adjtime file for? ) borg:~ # locate adjtime /etc/adjtime /usr/share/man/man2/adjtimex.2.gz borg:~ # less /etc/adjtime -3.779150 986370144 0.000000 985204508 UTC borg:~ # rpm -qf /etc/adjtime file /etc/adjtime is not owned by any package borg:~ # mv /etc/adjtime /etc/adjtime.old borg:~ # hwclock --show Wed Apr 4 07:53:31 2001 -0.417313 seconds borg:~ # hwclock --hctosys borg:~ # date Wed Apr 4 07:54:07 PDT 2001 Now it works. So I'm wondering: Did the SuSE 7.1 upgrade leave behind /etc/adjtime that was screwing up stuff or what? -Garen
/etc/adjtime is a file with fudge factors that says how much your clock drifts. I find it easier since I have a 24x7 connection to just run netdate several times a day. adjtime is useful if you are connected most of the time and your hardware clock has a predictable drift. HTH, Jeffrey Quoting Garen Parham <nospam@garen.net>:
Problem:
borg:~ # hwclock --show Wed Apr 4 00:50:19 2001 -0.147254 seconds
(Time is actually 7:50)
After looking over the man pages for hwclock, I came across this piece of info:
... If the adjtime file doesn't exist, the default is local time. ...
. o O ( Why, what is the adjtime file for? )
borg:~ # locate adjtime /etc/adjtime /usr/share/man/man2/adjtimex.2.gz borg:~ # less /etc/adjtime -3.779150 986370144 0.000000 985204508 UTC borg:~ # rpm -qf /etc/adjtime file /etc/adjtime is not owned by any package borg:~ # mv /etc/adjtime /etc/adjtime.old borg:~ # hwclock --show Wed Apr 4 07:53:31 2001 -0.417313 seconds borg:~ # hwclock --hctosys borg:~ # date Wed Apr 4 07:54:07 PDT 2001
Now it works. So I'm wondering: Did the SuSE 7.1 upgrade leave behind /etc/adjtime that was screwing up stuff or what?
-Garen
-- I don't do Windows and I don't come to work before nine. -- Johnny Paycheck
Message-ID: <3A2571DE.CAD75F6B@halenet.com.au> Date: Thu, 30 Nov 2000 07:15:10 +1000 From: Don Hansford <donh@halenet.com.au> Subject: Re: [SLE] Network card trouble Alex Risselada wrote:
Hello.
Last weekend I bought a netwrork card for my brand new 486 Linux server. It was "NE2000 compatible and Software Configurable" First I tried to Then I booted the good old Windows 95, and with a lot of hacking I managed te get my card in the Hardware list, without any errors ( at IRQ11 Adr 340) I thougt maybe the card would remember it's setting when I boot back to linux, but this was a big illusion...
Those settings are internal to Windows, and do not affect the card in any way - only the way Win looks for it.
- Is there maybe a test tool to check if the card is functioning?
Most software configurable cards include the config and test software on the disk that comes with them
- Is it possible to attacht my 2nd Network card to the 1st network card, which are in the same conputer, without any damage?
Why would you want to do that? There is already a built-in loopback. -- This Email is 100% Virus Free! How do I know? Because no Microsoft products were used to generate it! Regards Don Hansford ECKYTECH COMPUTING/ SQIT Warwick <SuSE Linux 6.4> "We're tired, we're wired, and our breath smells bad -- -But at least our Operating System doesn't suck!"
participants (6)
-
cliff＠raggedclown.net -
donh＠halenet.com.au -
Garen Parham -
Jeffrey Taylor -
Patriiiiiiiiiick -
risselada-a＠hetnet.nl