Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

when/how are linux/modules/*.ver built? (p.s.)

You have somewhat lost me here.  First, if you are using Debian, then you
should install the "kernel-package" package and issue the "make-kpkg"
command after running the usual "make menuconfig" (or "make "config" or
"make xconfig" if you prefer).  You will need a Debianized kernel-source
tree, which can be obtained from installing any "kernel-source-*" package.

Second, there is no "Debian 2.1.12," as the nomenclature for a Debian
distribution would be something like "2.1r6" which is the current "stable"
version.  If you are running what is commonly termed Debian "Slink" then
this is 2.1; if you are running what is commonly termed Debian "Potato"
then this is 2.2 (which is currently in late beta).

Third, does your ".config" file have "CONFIG_MODVERSIONS" defined or not?

Fourth, why are you messing with the innards of the tulip driver?  If you
are unable to get it to work, did you try the de4x5 and old_tulip drivers?

-- Mike

On 2000-06-01 at 07:32 -0400, John G. Norman wrote:

> P.S. The message below refers to Debian 2.1.12.
> Hi. I'm recompiling the tulip.c network card driver, which wants to include 
> modversions.h, which in turn wants to include linux/modules/*.ver. But 
> they're not there. When/how are these .ver files built?

Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at (Subject line is ignored).

BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!

Boston Linux & Unix /