Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 23 Mar 2003 13:29:18 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 23 Mar 2003 13:29:18 -0500 Received: from mail1.mx.voyager.net ([216.93.66.200]:32004 "EHLO mail1.mx.voyager.net") by vger.kernel.org with ESMTP id ; Sun, 23 Mar 2003 13:29:16 -0500 Message-ID: <3E7DFFC5.FDA38126@megsinet.net> Date: Sun, 23 Mar 2003 12:41:09 -0600 From: "M.H.VanLeeuwen" X-Mailer: Mozilla 4.8 [en] (X11; U; Linux 2.5.65 i686) X-Accept-Language: en MIME-Version: 1.0 To: Michael Frank CC: linux-kernel@vger.kernel.org Subject: Re: ISAPNP BUG: 2.4.65 ne2000 driver w. isapnp not working References: <3E7DE01B.2B6985DF@megsinet.net> <200303240157.53373.mflt1@micrologica.com.hk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 4104 Lines: 111 Michael, Thanks for the info. Like I said in previous e-mail I've not tested modules nor do I use them unless absolutely necessary. The question is who is the maintainer of the NE2K ISAPNP interface? Is this an NE2k maintainer issue or an ISAPNP issue or a "you have the hdwr" you fix it thingy? I can hack on ne2k but don't want to spend time on it if someone else already is or has a better solution or possibly colliding with ISAPNP development again as did my last patches sent to Linus. Martin Michael Frank wrote: > > Martin, > > Thank you for your message and patch which I tested. Firstlye some more background info. > > I just started testing 2.5 on all kinds of hw. This is being done on RH beta 8.094 (phoebe) > > This machine is an old 586 w/o ACPI and bootet with acpi=off. I sent messages and dmesg to your email only. > > 1) 2.5.65 + acpi20030321, isapnp fails on the _first_ attempt and works on the second and further(rmmod ne and 8390) attempts. There is a kernel message during ifup which may give you a hint > > 1st attempt: > kernel: pnp: res: The PnP device '01:01.00' is already active. > kernel: ne.c: You must supply "io=0xNNN" value(s) for ISA cards. > ifup: ne device eth0 does not seem to be present, delaying initialization. > network: Bringing up interface eth0: failed > > 2nd (and further after rmmod) attempt: > kernel: ne.c:v1.10 9/23/94 Donald Becker (becker@scyld.com) > kernel: Last modified Nov 1, 2000 by Paul Gortmaker > kernel: NE*000 ethercard probe at 0x2a0: 00 00 ff ff 27 ef > kernel: eth0: NE2000 found at 0x2a0, using IRQ 15. > network: Bringing up interface eth0: succeeded > > 2) 2.5.65 + acpi20030321 + your patch, pnp does not work at all, but the module can be inserted with modprobe ne io=0x2a0 irq=15. It seems it does not talk to the ne code as Beckers msg missing? > > All attempts of ifup eth0 or service network start: > > ifup: Cannot find device "eth0" > network: Bringing up loopback interface: succeeded > kernel: ne.c: You must supply "io=0xNNN" value(s) for ISA cards. > ifup: ne device eth0 does not seem to be present, delaying initialization. > network: Bringing up interface eth0: failed > > modprobe ne io=0x2a0 irq=15: > > kernel: ne.c:v1.10 9/23/94 Donald Becker (becker@scyld.com) > kernel: Last modified Nov 1, 2000 by Paul Gortmaker > kernel: NE*000 ethercard probe at 0x2a0: 00 00 ff ff 27 ef > kernel: eth0: NE2000 found at 0x2a0, using IRQ 15. > > > for me not yet ... :-) > Michael > > On Monday 24 March 2003 00:26, you wrote: > > > Hello. > > > > > > Have some trouble with loading modules (see earlier > > > message). Tried to compile a driver in. > > > > > > dmesg: > > > ------- > > > isapnp: Scanning for PnP cards... > > > isapnp: Card Plug & Play Ethernet card > > > isapnp: 1 Plug and Play card detected total > > > ------ > > > > > > - no further references do isapnp in logs > > > > > > - Same card works (with pnp disabled (jumper) and driver > > > compiled as a module) by modprobing it with io=0x300 > > > > > > - Same card works with 2.4.21-pre5 driver as module both > > > with pnp and modual probing > > > > > > Regards > > > Michael > > > - > > > > Michael, > > > > NE2k ISAPNP broke around 2.5.64, again. There are 2 parts to > > the attached patch, one to move the NIC initialization earlier > > in the boot sequence and the second is a HACK to get ne2k to > > work when compiled into the kernel, I've never tried NE2k as a > > module... > > > > 1. The level of isapnp_init was moved to after apci. Since it > > is now after net_dev_init, ISA PNP NICs fail to initialized at > > boot. > > > > This fix allows ISA PNP NIC cards to work during > > net_dev_init, and still leaves isapnp_init after apci_init. > > > > 2. The second piece kills off a now ?unnecessary? probe. > > > > Works for me, > > Martin - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/