|
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
|
Re: [PLUG] meeting followup: ndiswrapper working with 2.6 Kernel
|
Thanks! No, I did not know they were there. I had once spent a half hour on the broadcom site looking for drivers. I finally wrote them a mail asking where they had drivers (and I was only looking for the Windows drivers!). I got a generic reply saying I had to get my drivers from the vendor of my computer, which I was able to do. I had learned a while back that broadcom would not release source and did not support Linux regarding the wireless cards. I guess I was misinformed or the Linux community is making even more recent progress.
These errors look similar to the compile errors of ndiswrapper with the newer kernel. An extra parameter was added to some functions.
/home/edmondrod/Desktop/bc/src/wl/sys/wl_iw.c:951: error: too few arguments to function 'iwe_stream_add_point'
/home/edmondrod/Desktop/bc/src/wl/sys/wl_iw.c:959: warning: passing argument 1 of 'iwe_stream_add_event' from incompatible pointer type
/
I wonder if something could have been done to get around this problem, sort of like a C++ overloaded function, to make things backward compatible. Or what could be nice too would be some compiler directive that when the error occurs an intellibile one or two line statement would be printed explaining the change and very briefly what it is about. This surely will cause problems for many people.
I guess the kernel is still written in "C", so this could not be done. I actually don't remember how to print a message via the compiler, though I seem to recall in a limited way, one could do this.
I'm not complaining, just thinking out loud, I guess.
/home/edmondrod/Desktop/bc/src/wl/sys/wl_iw.c:951: error: too few arguments to function 'iwe_stream_add_point'
/home/edmondrod/Desktop/bc/src/wl/sys/wl_iw.c:959: warning: passing argument 1 of 'iwe_stream_add_event' from incompatible pointer type
/home/edmondrod/Desktop/bc/src/wl/sys/wl_iw.c:959: warning: passing argument 3 of 'iwe_stream_add_event' from incompatible pointer type
/home/edmondrod/Desktop/bc/src/wl/sys/wl_iw.c:959: warning: passing argument 4 of 'iwe_stream_add_event' makes pointer from integer without a cast
/home/edmondrod/Desktop/bc/src/wl/sys/wl_iw.c:959: error: too few arguments to function 'iwe_stream_add_event'
/home/edmondrod/Desktop/bc/src/wl/sys/wl_iw.c:967: warning: passing argument 1 of 'iwe_stream_add_event' from incompatible pointer type
/home/edmondrod/Desktop/bc/src/wl/sys/wl_iw.c:967: warning: passing argument 3 of 'iwe_stream_add_event' from incompatible pointer type
/home/edmondrod/Desktop/bc/src/wl/sys/wl_iw.c:967: warning: passing argument 4 of 'iwe_stream_add_event' makes pointer from integer without a cast
/
----- Original Message ----
> From: Brian Vagnoni <bvagnoni@v-system.net>
> To: edmond rodriguez <erodrig_97@yahoo.com>; Philadelphia Linux User's Group Discussion List <plug@lists.phillylinux.org>
> Sent: Saturday, December 27, 2008 12:02:13 AM
> Subject: Re: [PLUG] meeting followup: ndiswrapper working with 2.6 Kernel
>
> ----- Original Message -----
> From: edmond rodriguez
> [mailto:erodrig_97@yahoo.com]
>
> > ndiswrapper working on 2.6 kernel, though still many issues with
>
>
> ----- Original Message -----
>
> Aaaaa you know about these right.....?
>
> http://www.broadcom.com/support/802.11/linux_sta.php
>
> If it doesn't compile you should be able to find a patch at kernel.org if I'm
> not mistaken.
>
> I was able to get it working under a Opensuse RC Release and a patch from above
> mentioned web site.
>
> Good luck and sorry if you have already tried these.
>
> --------------------------------------------------
> Brian Vagnoni
> PGP Digital Fingerprint
> F076 6EEE 06E5 BEEF EBBD BD36 F29E 850D FC32 3955
> --------------------------------------------------
>
>
>
> To: Philadelphia Linux User's Group
> Discussion List [mailto:plug@lists.phillylinux.org]
> Sent: Fri, 26 Dec
> 2008 22:11:29 -0500
> Subject: [PLUG] meeting followup: ndiswrapper
> working with 2.6 Kernel
>
>
> > ndiswrapper working on 2.6 kernel, though still many issues with
> > wpa_supplicant (an entirely seperate issue):
> >
> > For anyone interested in ndiswrapper issues with the 2.6 kernel, here
> > are some things I worked on since the last meeting:
> >
> > I had talked at a meeting about some problem with ndiswrapper and the
> > 2.6 kernel. ndiswrapper compiled and loaded, but no "blue light" (on
> > my machine) and no other indications from typing commands that it was
> > working. I was able to resolve all the problems, though I may never
> > get the wpa_supplicant to work (with or without WICD).
> >
> > I had trouble getting ndiswrapper and my Windows braodcom 4318 drives
> > to work on my 2.6.24 kernel.
> >
> > Learning at the meeting that Slackware recently made a new release to
> > 12.2 and also seeing from this forum (
> >
> >
> http://www.linuxquestions.org/questions/slackware-14/ndiswrapper-bcmwl5-conflicts-with-ssb-640892/
> >
> > ) that there may be minor issues with the 2.6.24 kernel working with
> > ndiswrapper, I decided to upgrade regardless of if the forum was
> > correct or not.
> >
> > Now with 2.6.27 kernel, ndiswrapper would no longer compile!
> >
> > So I found another posting about fixes for the compile:
> >
> > http://lkml.indiana.edu/hypermail/linux/kernel/0811.3/00977.html
> >
> > I ran recursive diffs to check on changes, then compiled and installed
> > this fixed version.
> >
> > Still no "blue light" on my machine.
> >
> > Using the earlier forum above, I had to remove modules that were
> > loaded at boot time:
> >
> > rmmod b43
> > rmmod ssb
> >
> > I don't recall now if there were any issues with the order in which I
> > removed them.
> >
> > Staring over with my Windows drivers newly loaded by my fixed
> > ndiswrapper I could now "modprobe ndiswrapper", and finally, the blue
> > light that indicates my wireless card is enabled comes on.
> >
> > I could scan the networks and connect to anything that is not secured.
> >
> > Now I once had wpa_supplicant working on an older kernel for WPA TKIP,
> > but at this time, after much frustration, not working! I am trying to
> > get it to work with WPA2 (TKIP or AES), as the configuation on my
> > router indicates. I learned about WICD, and that did not help after
> > hours of tweaking it.
> >
> > But that issue is independent of ndiswrapper. If anyone knows of a
> > very robust wpa interface, please do let me know.
> >
> > So the good news is, ndiswrapper is running and it is working on the
> > 2.6 kernel.
> >
> >
> > Edmond
> >
> > ___________________________________________________________________________
> > Philadelphia Linux Users Group --
> > http://www.phillylinux.org
> > Announcements -
> > http://lists.phillylinux.org/mailman/listinfo/plug-announce
> > General Discussion --
> > http://lists.phillylinux.org/mailman/listinfo/plug
> >
> ___________________________________________________________________________
> Philadelphia Linux Users Group -- http://www.phillylinux.org
> Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
> General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
___________________________________________________________________________
Philadelphia Linux Users Group -- http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|