RE: Rocketport driver in kernel 2.6.8...
This works too! Thanks!
I'm ignorant about module implementation because it seemed to be an
implementation "in flux", and it's hard enough for me to keep up with
changes as it is. Thus I ignored modules and just stuck with compiling into
the kernel. ...that way, I only had to learn one new thing per major kernel
revision (kernel compiling specifics, and not all the changes to module
specifics also). This kept all the core stuff as small as possible and in
one place.
Looks like development has focused on module implementation over kernel
built-ins this time around. I plan to learn "modules" when Debian officially
releases Sarge on 2.6.x kernels, unless compelled to do so before then (I
may be there now).
Thanks,
Rick
> -----Original Message-----
> From: Mark White [mailto:jmarkw@ec.rr.com]
> Sent: Friday, December 10, 2004 1:03 PM
> To: Debian Hams
> Subject: Re: Rocketport driver in kernel 2.6.8...
>
>
> On Fri, 12/10/2004, 12:25PM, Rick Bolen wrote:
> > I changed my definition of CONFIG_ROCKETPORT from (*) to (M) in
> menuconfig,
> > recompiled, created a /etc/rc2.d/S99rocket file with...
> >
> > #! /bin/sh
> > modprobe rocket
> >
> > ... and this worked! Thanks.
> >
> Why not just list 'rocket' in /etc/modules? It'll get loaded at every
> runlevel, of course, so if that's not a problem, it's faster than
> creating a boot script.
>
> Mark, KE4QKT
> >
> >
> > --
> > To UNSUBSCRIBE, email to debian-hams-REQUEST@lists.debian.org
> > with a subject of "unsubscribe". Trouble? Contact
> listmaster@lists.debian.org
> >
>
>
> --
> To UNSUBSCRIBE, email to debian-hams-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmaster@lists.debian.org
>
>
Reply to: