>Question 1. Is there a chicken and egg problem here?
> How can a loaded kernel function without a builtin
> network driver? Surely it cannot successfully run
> insmod to load a remote network driver unless it has a
> network driver already?
> Should we expect to see tha kernel try to load a network
> module from the network?
No contradiction. The driver is loaded from ramdisk.
>Question 2. The Etherboot code we used is only a few days
> old. The network file is from the same origin as the
> kermel driver file but seems on inspection closer to
> the kernel 2.4.18 version than the kernel 2.4.9
> version.
> Is it likely that we need to graft the sis900.o module
> from the latest kermel onto the ltsp 2.4.9 kernel
> in order for the presumably newer chipset to work.
A friend of mine has this board. The latest kernel driver is needed.
>Question 3. The 630ET is a PCI device. Do we need to pass
> arguments to the kernel via the option-128 and option-129
> mechanism. If so does anyone know what is an appropriate
> arg list. (I have tried a few so far with no change in
> symptoms).
No, not for PCI devices.
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.openprojects.net
