RE: RE Digital Venturis P166 thin clients problems PROGRESS!

I've compiled my working kernel monolithically, disabling modules...

But pxesconfig seems to expect modules to be available.  I know exactly what
hardware is in these machines, so modules seems a bit of a waste.  Is this
right?



-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Tim Bates
Sent: Thursday, 19 February 2004 4:37 p.m.
To: [email protected]
Subject: Re: RE [pxes-devel] Digital Venturis P166 thin clients problems
PROGRESS!


Whatever you do... Note how you fixed it NOW (somewhere near the box you
comile kernels on). In 2 weeks time you will have forgotten something like
that.

I'd personally make 2 kernels based on the one config, with only that one
change. Then set the IP's for the dodgy boxes to a certain range and make
that range grab the "fixed" kernel.

 Yes thank you Diego...  I've managed to prove that it's a compile-time
> option to the 8139too module.  I've brewed a kernel that boots on the 
> hardware bu turning on "Use PIO rather than MMIO"
>
> My question now is how to use this kernel without disrupting the other 
> machines.  Should I recompile the module?  Or should I compile a
monolithic
> kernel for these machines?  What other kernel options are required?





-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id56&alloc_id438&op=click