On Sunday 29 October 2006 02:09, Pollywog wrote:
> On Sunday 29 October 2006 02:01, Elimar Riesebieter wrote:
> > > I believe the errors are due to incorrect gcc versions used to compile
> > > the module and the kernel. I am using
> >
> > Hmm, you have to be root to insmod the drivers.
>
> Shouldn'
On Saturday 28 October 2006 22:01, Elimar Riesebieter wrote:
> On Sat, 28 Oct 2006 the mental interface of
>
> Kamaraju Kusumanchi told:
> > Hi all
> > How can I find the gcc version that was used to compile the kernel? I
> > am running debian testing (etch) with
> >
> > $uname -a
> > Linux kus
On Sunday 29 October 2006 02:01, Elimar Riesebieter wrote:
> > I believe the errors are due to incorrect gcc versions used to compile
> > the module and the kernel. I am using
>
> Hmm, you have to be root to insmod the drivers.
>
Shouldn't one use modprobe with current versions of Linux?
Of cours
On Sat, 28 Oct 2006 the mental interface of
Kamaraju Kusumanchi told:
> Hi all
> How can I find the gcc version that was used to compile the kernel? I am
> running debian testing (etch) with
>
> $uname -a
> Linux kusumanchi 2.6.17-2-686 #1 SMP Wed Sep 13 16:34:10 UTC 2006 i686
> GNU/Linux
Hi all
How can I find the gcc version that was used to compile the kernel? I am
running debian testing (etch) with
$uname -a
Linux kusumanchi 2.6.17-2-686 #1 SMP Wed Sep 13 16:34:10 UTC 2006 i686
GNU/Linux
Why I need this:
I am trying to install madwifi drivers to get the wireless work
5 matches
Mail list logo