Re: New Problem; Network Card

As the member who tipped you off about the installer kernel being 
built for a PIII, I can tell you that this is not fixed in 1.2.
The installer kernel in the generic i386 BSP remains precompiled 
for PIII.

We also had some problems with certain network cards. It
seemed that no amount of fiddling with the settings would
cause it to actually compile the ne2000 driver.  After a
lot of digging in the scripts, this was finally traced to
the state of a kernel config variable called "CONFIG_NET_ISA" 
which was set to "n". Attempting to change it to "y" did not work,
as something reset it to "n' every time. The result is that 
certain drivers in an ISA architecture can never be built. 
More digging in the scripts finnaly traced the problem to
the file "rules.cml" in "q+esto/bsp/i386/generic/cmls/kernel-tree".
Towards the end, in a section commented with
"Declare these to suppress some 'unknown symbol' messages...",
change the line 
"derive NET_ISA from n"
to
"derive NET_ISA from y"

This will fix the problem for any new projects created from 
now on.  To fix it for an existing project, make the same change
in the file "rules.out" in the root directory of the project,
and remove the existing "config.kernel" in the same directory.
It will then get rebuilt correctly.

Now, all of the above applies to your project's kernel, but you
also have be sure that the new installer kernel that you build
also has the correct network driver,  Further, the new installer
kernel should have the driver built directly into the kernel
instead of as a module.  It is possible to do it as a module,
but it is a lot more complicated, involving modifying the
prebuilt installer's initial ramdisk (initrd).

Hope this helps.

@(^.^)@  Ed
  


> Aron Reid wrote:
> 
> Thanks to one of the members here, I found out that the install kernel
> is designed for the PIII/Cele board, so I tried it, and it worked
> fine, however as another member on this board had a problem where by
> the boot kernel would contain a Tulip and 3C95x.o file however that
> was all [This is during the Qplus Install Boot, where you press 1, the
> IP and then install.conf].  I am having the same issue, and when I
> look in the /net folder there is absolutely nothing.  Also I tried
> checking the rootfs.tar.gz file, and again, nothing, I tried copying
> it in, and it didn't show up in the shell.  I removed all files except
> for qplus.etherboot and still it booted, so by process of elimination
> the qplus.etherboot file contains the rootfs for the install kernel
> too I assume?
> 
> Anyhow, I have also put a "Y" on "Realtek 8139" the chipset that I am
> using, recompiled the system, and same thing.
> 
> Going to the FTP site for Qplus I noted version 1.2 (I am using 1.0)
> would upgrading fix this? Would It fix my original issue where by the
> install kernel is specifically designed for PIII/Cele regardless of
> what I set in the Qplus builder? (I have it set to MMX, P1, PIII
> anything and yet my Socket 7 P1MMX reboots when loading the kernel)
> 
> Thank You Again All;
> Aron R.


-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504