On Thursday 20 March 2003 08:59, Arjan van de Ven wrote:
> easiest is to use the device driverdisk kit Doug has:
> http://people.redhat.com/dledford/
Been there tried that. Module doesn't get compiled w/ modversion.h for some
reason. Of corse, i've emailed dledford about it, have yet to get a
On Thu, 2003-03-20 at 17:15, Jesse Keating wrote:
> On Thursday 20 March 2003 08:03, Arjan van de Ven uttered:
> > that is not correct.
>
> Ok, so if thats not correct, could you help me in any way as to figure out why
> the method I use works for an installed kernel, but not the boot kernel? I'
On Thursday 20 March 2003 08:03, Arjan van de Ven uttered:
> that is not correct.
Ok, so if thats not correct, could you help me in any way as to figure out why
the method I use works for an installed kernel, but not the boot kernel? I'm
all ears. (;
--
Jesse Keating RHCE MCSE
http://geek.j2
On Thu, 2003-03-20 at 16:29, Jesse Keating wrote:
> I can build the module and load it into a running system w/out
> trouble. It's the boot kernel that is giving me trouble, and I'm thinking
> that it's because the -i386-BOOT config that came w/ the kernel differs from
> the actual kernel use
On Thursday 20 March 2003 04:53, George Magklaras uttered:
> Have you done a make modules and also a make modules_install ?
> If not it doesn't surprise me the least.
>
> If you do this and it makes the dependencies properly (you will know
> if you see the module under the /lib/modules/[kernel-ver
Have you done a make modules and also a make modules_install ?
If not it doesn't surprise me the least.
If you do this and it makes the dependencies properly (you will know
if you see the module under the /lib/modules/[kernel-version]
directory structure), it should work.
Regards,
GM
Jesse Keat
