Re: [Cooker] NFS install fails
On 31 Jul 2001, Guillaume Cottenceau wrote: > > 1- isa-pnp in the krenel (but it give some problems when isa-pnp was > >compiled in-kernel, jeff do you remind was what they? > > 2- do a insmod isa-pnp before _anything_ in stage1. > > 3- fix all the kernel isa drivers and remove their isa-pnp support > >(not an option IMHO). > > But, I don't get it: > > - 3c509 is not dependant on isa-pnp > - when isa-pnp is insmod'ed, it messes with 3c509 > > Why so? Hmmm, I have been bursting into cursing mode because of this issue too. Actually, kernel isa-pnp module will *OVERRIDE* isapnptools setting, and used some certain decided setting. If that setting don't fit the real jumper setting of card, then there's no easy way to fix it -- either change jumper and all other conflicting cards to suit the kernel setting, or go through some undocumented (or barely documented) setting under /proc. Abel
Re: [Cooker] NFS install fails
Juan Quintela <[EMAIL PROTECTED]> writes: [...] > pixel> - fix the kernel :-( > > nope, if you ask the kernel to install isa-pnp, you initialize the > isa-pnp space, you need to do that the first time that you need the > thing. Ohh, wait, we need to fix the kernel, 3c509 _should_ not work > until isa-pnp is loaded. Problem was, isa-pnp worked pretty bad in > the kernel, that means that _some_ cards put a simple implementation > (aka it works for me), that implementation now breaks that we have > real isa-pnp support. I think that we need: > 1- isa-pnp in the krenel (but it give some problems when isa-pnp was >compiled in-kernel, jeff do you remind was what they? > 2- do a insmod isa-pnp before _anything_ in stage1. > 3- fix all the kernel isa drivers and remove their isa-pnp support >(not an option IMHO). But, I don't get it: - 3c509 is not dependant on isa-pnp - when isa-pnp is insmod'ed, it messes with 3c509 Why so? -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
Re: [Cooker] NFS install fails
> "pixel" == Pixel <[EMAIL PROTECTED]> writes: pixel> Guillaume Cottenceau <[EMAIL PROTECTED]> writes: pixel> [...] >> - you load (during stage1) 3c509 isa netword card driver by hand >> - there is no dependency 3c509 -> isa-pnp >> - but when isa-pnp gets loaded by drakx (due to dep on serial.o), it >> reclaims the netword card, and make the interface collapse >> >> >> For the moment we may have two solutions: >> >> - disable isa-pnp for boot kernel >> - always insmod isa-pnp during stage1 (dirty!?) pixel> third solution: pixel> - fix the kernel :-( nope, if you ask the kernel to install isa-pnp, you initialize the isa-pnp space, you need to do that the first time that you need the thing. Ohh, wait, we need to fix the kernel, 3c509 _should_ not work until isa-pnp is loaded. Problem was, isa-pnp worked pretty bad in the kernel, that means that _some_ cards put a simple implementation (aka it works for me), that implementation now breaks that we have real isa-pnp support. I think that we need: 1- isa-pnp in the krenel (but it give some problems when isa-pnp was compiled in-kernel, jeff do you remind was what they? 2- do a insmod isa-pnp before _anything_ in stage1. 3- fix all the kernel isa drivers and remove their isa-pnp support (not an option IMHO). Later, Juan. -- In theory, practice and theory are the same, but in practice they are different -- Larry McVoy
Re: [Cooker] NFS install fails
Guillaume Cottenceau <[EMAIL PROTECTED]> writes: [...] > - you load (during stage1) 3c509 isa netword card driver by hand > - there is no dependency 3c509 -> isa-pnp > - but when isa-pnp gets loaded by drakx (due to dep on serial.o), it > reclaims the netword card, and make the interface collapse > > > For the moment we may have two solutions: > > - disable isa-pnp for boot kernel > - always insmod isa-pnp during stage1 (dirty!?) third solution: - fix the kernel :-(
Re: [Cooker] NFS install fails
"kk1" <[EMAIL PROTECTED]> writes: > I don't know if anything has been changed by anyone, but it still fails > with the July 30 build. No, it's not solved yet AFAIK. -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
Re: [Cooker] NFS install fails
Guillaume Cottenceau <[EMAIL PROTECTED]> writes: > "kk1" <[EMAIL PROTECTED]> writes: > > > I don't know if anything has been changed by anyone, but it still fails > > with the July 30 build. > > No, it's not solved yet AFAIK. The scenario seems to be (correct me if necessary): - you load (during stage1) 3c509 isa netword card driver by hand - there is no dependency 3c509 -> isa-pnp - but when isa-pnp gets loaded by drakx (due to dep on serial.o), it reclaims the netword card, and make the interface collapse For the moment we may have two solutions: - disable isa-pnp for boot kernel - always insmod isa-pnp during stage1 (dirty!?) -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
Re: [Cooker] NFS install fails
> "kk1" == kk1 <[EMAIL PROTECTED]> writes: kk1> Here are the console dumps. kk1> On F4 kk1> <4>eth0: setting Rx mode to 1 addresses. (sic) kk1> <4>nfs warning: mount version older than kernel kk1> <6>isapnp: scanning for PnP cards kk1> <4>eth0: infinite loop in interrupt, status kk1> <6>isapnp: Card '3Com 3C509B Etherlink III' kk1> <6>isapnp: 1 Plug & Play card detected total kk1> <5>nfs: server xx.xx.xx.xx is not respoonding kk1> etc... Let me guess, you network card is an isa-pnp one. kk1> On F3: kk1> *succeeded nfs kk1> *preparing nfs mount kk1> *found the Mandrake installation kk1> *stage 1: disconnecting life support systems kk1> *second stage install running (DrakX v1.523 built 07/19/2001) kk1> *running: /usr/bininsmod_ 2> /dev/tty5 -f /tmp/isa-pnp.o We need to load that in a different order, forwarded the mail to responsible. Thanks for the report. Later, Juan. -- In theory, practice and theory are the same, but in practice they are different -- Larry McVoy
Re: [Cooker] NFS install fails
"kk1" <[EMAIL PROTECTED]> writes: > -- > Original Message > From: "Guillaume Cottenceau"<[EMAIL PROTECTED]> > Subject: Re: [Cooker] NFS install fails > Date: 25 Jul 2001 13:14:13 +0200 > > >"kk1" <[EMAIL PROTECTED]> writes: > > > >> Here are the console dumps. > >> > >> On F4 > >> <4>eth0: setting Rx mode to 1 addresses. (sic) > >> <4>nfs warning: mount version older than kernel > >> <6>isapnp: scanning for PnP cards > >> <4>eth0: infinite loop in interrupt, status > >> <6>isapnp: Card '3Com 3C509B Etherlink III' > >> <6>isapnp: 1 Plug & Play card detected total > >> <5>nfs: server xx.xx.xx.xx is not respoonding > > > >Are you sure the server is still responding :-)) ? > > > Seriously, yes I am sure. > I am using a hub and I can see the light going off on the client side. > The server is still on and available. Well the kernel says that the server is not responding.. how do you interpret this? Some compatibility problems? The thing is that it begins to work (isapnp stuff, etc) before "not responding" which is strange... -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
Re: [Cooker] NFS install fails
-- Original Message From: "Guillaume Cottenceau"<[EMAIL PROTECTED]> Subject: Re: [Cooker] NFS install fails Date: 25 Jul 2001 13:14:13 +0200 >"kk1" <[EMAIL PROTECTED]> writes: > >> Here are the console dumps. >> >> On F4 >> <4>eth0: setting Rx mode to 1 addresses. (sic) >> <4>nfs warning: mount version older than kernel >> <6>isapnp: scanning for PnP cards >> <4>eth0: infinite loop in interrupt, status >> <6>isapnp: Card '3Com 3C509B Etherlink III' >> <6>isapnp: 1 Plug & Play card detected total >> <5>nfs: server xx.xx.xx.xx is not respoonding > >Are you sure the server is still responding :-)) ? > Seriously, yes I am sure. I am using a hub and I can see the light going off on the client side. The server is still on and available. =-= kk1 _ Free email with personality! Over 200 domains! http://www.MyOwnEmail.com
Re: [Cooker] NFS install fails
"kk1" <[EMAIL PROTECTED]> writes: > Here are the console dumps. > > On F4 > <4>eth0: setting Rx mode to 1 addresses. (sic) > <4>nfs warning: mount version older than kernel > <6>isapnp: scanning for PnP cards > <4>eth0: infinite loop in interrupt, status > <6>isapnp: Card '3Com 3C509B Etherlink III' > <6>isapnp: 1 Plug & Play card detected total > <5>nfs: server xx.xx.xx.xx is not respoonding Are you sure the server is still responding :-)) ? -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/