[opensuse] Installing an ISA ethernet card in 10.3
If anyone can refer me to info about this problem I shall apologise and look it up but I can't find anything in the archives or by Google. I am trying to install a non-PnP NE2000 clone in my opensuse 10.3 setup which I plan to use as a gateway/router for my home network. YaST2 occasionally seems to add the card (and by the way the 'Choose from a list" button referred to in the help info seems not to exist in the latest version) but the configuration I use gets applied to one of my other cards, and rarely persists past a second boot (the module, "ne" in this case, no longer gets loaded). I have tried to put the module in /etc/sysconfig/kernel, and the parameters in /etc/modprobe.conf, after much research. And written an "ifcfg-ethx" for my new card. This sort of works, though most of the parameters in the ifcfg-ethx file get rejected at boot, presumably because they are being parsed by the wrong programme. If anyone can tell me where else I need to put information about my card for it be properly integrated into the system, this would be very helpful. Another problem is that when the module is installed it does not seem to deliver a name for the device which then can then be displayed (like D-Link DE-220T) - I don't know whether this is relevant to yast not finding the card even when I load it on boot. Many thanks for any advice, -- Roger Hayter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Roger Hayter wrote:
If anyone can refer me to info about this problem I shall apologise and look it up but I can't find anything in the archives or by Google. I am trying to install a non-PnP NE2000 clone in my opensuse 10.3 setup which I plan to use as a gateway/router for my home network. YaST2 occasionally seems to add the card (and by the way the 'Choose from a list" button referred to in the help info seems not to exist in the latest version) but the configuration I use gets applied to one of my other cards, and rarely persists past a second boot (the module, "ne" in this case, no longer gets loaded).
I have tried to put the module in /etc/sysconfig/kernel, and the parameters in /etc/modprobe.conf, after much research. And written an "ifcfg-ethx" for my new card. This sort of works, though most of the parameters in the ifcfg-ethx file get rejected at boot, presumably because they are being parsed by the wrong programme.
If anyone can tell me where else I need to put information about my card for it be properly integrated into the system, this would be very helpful. Another problem is that when the module is installed it does not seem to deliver a name for the device which then can then be displayed (like D-Link DE-220T) - I don't know whether this is relevant to yast not finding the card even when I load it on boot.
Many thanks for any advice, For such a task, imho SuSE 10.3 is a little obese.
I'd recommend ipcop that works with my PI 166 with one PCI and one ISA NE-2000 board. Kind regards Eberhard -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
In message <fgmusu$26l$1@ger.gmane.org>, Eberhard Roloff <tuxebi@gmx.de> writes
Roger Hayter wrote: (Opensuse as router)
Many thanks for any advice,
For such a task, imho SuSE 10.3 is a little obese.
I'd recommend ipcop that works with my PI 166 with one PCI and one ISA NE-2000 board.
Kind regards Eberhard
I am sure you're right, but I wrote to this mailing list specifically regarding the opensuse implications. Last time I looked, ipcop didn't really do all I wanted, but I am sure there are better dedicated solutions - I just like to use one distribution for all my machines. -- Roger Hayter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Roger Hayter wrote:
In message <fgmusu$26l$1@ger.gmane.org>, Eberhard Roloff <tuxebi@gmx.de> writes
Roger Hayter wrote: (Opensuse as router)
Many thanks for any advice,
For such a task, imho SuSE 10.3 is a little obese.
I'd recommend ipcop that works with my PI 166 with one PCI and one ISA NE-2000 board.
Kind regards Eberhard
I am sure you're right, but I wrote to this mailing list specifically regarding the opensuse implications. Last time I looked, ipcop didn't really do all I wanted, but I am sure there are better dedicated solutions - I just like to use one distribution for all my machines.
Also, make sure you check your BIOS and see if you can set the ISA IRQ as a "Legacy IRQ" or something similar. I have had this issue using Abit boards. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
In message <472F3D3A.40905@suddenlinkmail.com>, David C. Rankin <drankinatty@suddenlinkmail.com> writes
Roger Hayter wrote:
In message <fgmusu$26l$1@ger.gmane.org>, Eberhard Roloff <tuxebi@gmx.de> writes
Roger Hayter wrote: (Opensuse as router)
Many thanks for any advice,
For such a task, imho SuSE 10.3 is a little obese.
I'd recommend ipcop that works with my PI 166 with one PCI and one ISA NE-2000 board.
Kind regards Eberhard
I am sure you're right, but I wrote to this mailing list specifically regarding the opensuse implications. Last time I looked, ipcop didn't really do all I wanted, but I am sure there are better dedicated solutions - I just like to use one distribution for all my machines.
Also, make sure you check your BIOS and see if you can set the ISA IRQ as a "Legacy IRQ" or something similar. I have had this issue using Abit boards.
Good point. I have reserved the IRQ in BIOS and the port address not used by anything else. These are set on the card by a utility program, but unlike a PnP card it doesn't broadcast it is there until the port is probed. I can load the driver, and, indeed, use the card fully: but yast2 does not fully recognise it even when it is loaded. For instance, unlike other cards yast2 cannot discern its MAC address. I am concerned that some part of the setup I want to do will fail because the card is not fully integrated into all the relevant lists. -- Roger Hayter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (3)
-
David C. Rankin -
Eberhard Roloff -
Roger Hayter