| 1 |
Set something that will show on the modinfo command? |
| 2 |
|
| 3 |
I dont have e1000, but this a coda.ko example |
| 4 |
|
| 5 |
bunyip ~ # modinfo coda |
| 6 |
filename: /lib/modules/2.6.27-gentoo-r4/kernel/fs/coda/coda.ko |
| 7 |
version: 6.6 |
| 8 |
license: GPL |
| 9 |
alias: char-major-67-* |
| 10 |
description: Coda Distributed File System VFS interface |
| 11 |
author: Jan Harkes, Peter J. Braam |
| 12 |
srcversion: 88DB5609F61269AF835BA05 |
| 13 |
depends: |
| 14 |
vermagic: 2.6.27-gentoo-r4 preempt mod_unload modversions |
| 15 |
PENTIUMM |
| 16 |
bunyip ~ # |
| 17 |
|
| 18 |
Billk |
| 19 |
|
| 20 |
|
| 21 |
|
| 22 |
|
| 23 |
On Thu, 2009-03-05 at 23:17 -0300, Francisco Ares wrote: |
| 24 |
> Never made such thing, so just a guess: maybe a log entry on some |
| 25 |
> event, like link up - at that time, probably, the log engine is |
| 26 |
> already up and running. |
| 27 |
> |
| 28 |
> Francisco |
| 29 |
> |
| 30 |
> On Thu, Mar 5, 2009 at 8:16 PM, Ezra Taylor <ezra.taylor@×××××.com> wrote: |
| 31 |
> > Hello all: |
| 32 |
> > I made some changes to the e1000 kernel driver. I then |
| 33 |
> > recompiled the kernel without any issue. How can I tell if the change |
| 34 |
> > actually went through? Again, this driver has been statically built into |
| 35 |
> > the kernel. Is there a way to test that a change went through without have |
| 36 |
> > to setup a test environment? |
| 37 |
> > |
| 38 |
> > -- |
| 39 |
> > Ezra Taylor |
| 40 |
> > |
| 41 |
> |
| 42 |
> |
| 43 |
> |
Archives