Re: [cobalt-developers] Replacing eepro100 with e100, need some .h source files

[Timothy Stonis <timothy.stonis@xxxxxxx>]

 That means there's no Makefile in the directory, which means the kernel
source isn't on the machine. I don't remember if the RaQ 4r's shipped with
kernel source or not. You'll have to hunt around on the FTP fit for the
kernel. Make sure you're in the right directory (usr/src/linux).

_Tim

On 12/4/01 2:15 PM, "William L. Thomson Jr." <wlt@xxxxxxxxxxxxxxxxxxxx>
wrote:

> I posted the message below a little while back. I received assistance
> from the group at thet time, but no reponse to the question below.
> 
> 
> Tim,
> Sorry for doing this step by step, but when I run those commands I get,
> make: *** No rule to make target.
> 
> So do I need a particular make file or something I am missing here?
> 
> Thanks for your assistance
> 
> Timothy Stonis wrote:
> 
>>  This will only generate files under /usr/src/linux, and should
> generate the
>> header file you need. Nothing else on your machine will be affected.
>> 
>> 
>> _Tim
>> 
>> On 11/9/01 5:14 PM, "William L. Thomson Jr." <wlt@xxxxxxxxxxxxxxxxxxxx>
>> wrote:
>> 
>> 
>>> Tim,
>>> Now I have that cleared up, what is the desired outcome? Will it create
>>> the .h file, and or files?
>>> 
>>> Sorry to be over cautious, its a new clean machine, I would like to keep
>>> that we.  It will be replaced with a XTR when ever they are released so
>>> I am hoping to get by without having to clean up or re-install the OS on
>>> this one, until it's time.
>>> 
>>> Thanks. :)
>>> 
>>> Timothy Stonis wrote:
>>> 
>>> 
>>>> You can do it either way. I semicolon in bash just means run one
> command
>>>> and then run the next one after it. So at the shell prompt, type:
>>>> 
>>>>  make oldconfig; make dep
>>>> 
>>>> 
>>>> 
>>>> On 11/9/01 3:58 PM, "William L. Thomson Jr." <wlt@xxxxxxxxxxxxxxxxxxxx>
>>>> wrote:
>>>> 
>>>> 
>>>> 
>>>>> Tim,
>>>>> Thanks but for clarity the commands or
>>>>> make oldconfig
>>>>> make dep" in /usr/src/linux
>>>>> or is it all on one line?
>>>>> 
>>>>> Or are you telling me to run
>>>>> make oldconfig
>>>>> and then
>>>>> make dep
>>>>> 
>>>>> in /usr/src/linux ?
>>>>> 
>>>>> 
>>>>> Just want to be sure before we start through commands around.
>>>>> 
>>>>> Timothy Stonis wrote:
>>>>> 
>>>>> 
>>>>> 
>>>>>> modversions.h is automatically generated. Try running a "make
> oldconfig;
>>>>>> make dep" in /usr/src/linux.
>>>>>> 
>>>>>> On 11/9/01 2:10 PM, "William L. Thomson Jr."
> <wlt@xxxxxxxxxxxxxxxxxxxx>
>>>>>> wrote:
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>>> I recently came across Intel's Advances Networking Services which
> allows
>>>>>>> you to group together two or more intel nic's to a single IP address.
>>>>>>> 
>>>>>>> I would like to be able to do this with a RaQ4r. Currently the
> RaQ uses
>>>>>>> the eepro100 module for the nic's. I need to compile and replace
> it with
>>>>>>> e100, which is compatible with IANS, eepro100 is not.
>>>>>>> 
>>>>>>> When I attempt to compile I am alerted that the following file is
>>>>>>> missing. I am not sure as to were I could obtain a copy of the
> file for
>>>>>>> the Cobalt, since I am assuming it may have been modified to fit the
>>>>>>> equipment when the kernel and such was compiled.
>>>>>>> 
>>>>>>> So I need to get a hold of the following, and after I may need others
>>>>>>> 
>>>>>>> /usr/src/linux-2.2.16C28_III/include/linux/module.h:19:
>>>>>>> linux/modversions.h: No such file or directory
>>>>>>> 
>>>>>>> When I attempt to compile IANS I get the following, which I assume is
>>>>>>> the same file.
>>>>>>> 
>>>>>>> cpp: /usr/src/linux/include/linux/modversions.h: No such file or
> directory
>>>>>>> 
>>>>>>> Although I hae been able to get around this error with IANS only.
> When
>>>>>>> compiling you can use a flag that compiles with modeversions
>>>>>>> disabled/enabled. No such flag for e100.
>>>>>>> 
>>>>>>> Bottom line I want to combine both ethernet interfaces to a
> single IP so
>>>>>>> I can group the ports on my switch.
>>>>>>> 
>>>>>>> Any suggestions?
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>> _______________________________________________
>>>>>> cobalt-developers mailing list
>>>>>> cobalt-developers@xxxxxxxxxxxxxxx
>>>>>> http://list.cobalt.com/mailman/listinfo/cobalt-developers
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>> _______________________________________________
>>>> cobalt-developers mailing list
>>>> cobalt-developers@xxxxxxxxxxxxxxx
>>>> http://list.cobalt.com/mailman/listinfo/cobalt-developers
>>>> 
>>>> 
>>>> 
>>>> 
>> 
>> _______________________________________________
>> cobalt-developers mailing list
>> cobalt-developers@xxxxxxxxxxxxxxx
>> http://list.cobalt.com/mailman/listinfo/cobalt-developers
>> 
>> 
>> 
>