> > Message: 1 > Date: Fri, 06 Jul 2007 12:53:42 -0500 > From: Larry Finger <[EMAIL PROTECTED]> > Subject: Re: bcm4312 on again, off again > To: Brennan Ashton <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED], [email protected] > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Brennan Ashton wrote: > >> On 7/4/07, Robert Easter <[EMAIL PROTECTED]> wrote: >> >>> It took a BS programmer over five hours, ... >>> > > What does BS mean in this context? > A B.S. Computer Science degree.. In other words somebody certified smart, as in in much better shape for this than Yours Truly. > > Several of us try very hard to make this forum helpful, and not chew out the > OP, but it is very hard > to diagnose a problem when crucial information is missing. Suppose I asked > for help in diagnosing my > Ford truck and I didn't tell you that it is a diesel, and I didn't even say > whether it started, or > not. And that is the reason I hope to find help from folks that have the chops to make this stuff work. Coding details are difficult enough, I imagine, for people that use them every day, what with the various languages, shells, routines,... I can't justify the time right now just to learn bash. For all I know I'd feed that diesel with gasoline and blow us all up! > For the record, diagnosis of problems require the kernel version (uname -r), > any patches that > have been applied, the results from the command 'dmesg | grep bcm43xx', > information about encryption > on the access point, and any additional software being used to connect > (NetworkManager, etc.). As > stated below, I make a note of it, thank you. > if you want to use ndiswrapper, go elsewhere. We have done a lot of work to > avoid that!! > See? For all I knew the two worked together, either the wrapper or the cutter, and until last week I didn't know that it was either/or. With your mate's help, I have put in a few hours trying to make the system run with the cutter, and Joe tried to make it work as well, before going with the wrapper approach. > >> As for the ability to connect sometimes and not others, it is >> something called i need to use the new kernel. Or use rmmod bcm43xx a >> lot. If you are using a distros kernel, it is very likely that it >> wont work, so i direct your attention toward www.kernel.org. At the >> time that my system was exhibiting that behavior, i applied this patch >> and it went away >> https://lists.berlios.de/pipermail/bcm43xx-dev/2007-February/003819.html >> . With the newer kernels, it should not be a problem. I still have >> problems when i am to far away from my AP, but in a reasonable range, >> it is very functional. >> Yes, that's basically what Joe did: downloaded a fresh kernel and compiled / built it to work with the driver, and still needed the wrapper. I don't know why, or for that matter how, when, where, or who. >> a uname -a would be helpful >> lspci | grep Broadcom >> dmesg | grep bcm43xx >> >> Also that tidbit about the light was completely useless, it is >> hardware not software (the filament in your ceiling light does not >> effect whether or not the wall switch opens and closes) >> When the wireless stopped working the light on the switch at the near edge of the notebook stopped working also. I tried several times but could not start the wireless channel in Network Manager. Then I saw the light working again, opened N.M., and was able to start the service. Maybe in this case that light is on a power detector and there was an open switch at or ahead of the ct/diode/transistor... >> If wont use the bcm43xx driver you are not going to find what people >> say here very useful. >> >> So what it looks like then is that until I have learned enough linux-ese to be able to access the technical pages, understand the difference (??) between a native driver and a bcm43xx driver, and why there's a notice in the F7 installation startup that there is no Broadcom support available when in fact there is (or is there) and know off-hand the meanings of the several hundred commands, conditions, and switches in bash, sh, ssh,... I should just go back to Windows? Surely there's a third option somewhere! >> Well that is my best guess at what you were trying to say. >> Larry, what I'm saying is that I am real grateful you guys run lists like this. I am busy enough at my end dealing with the technical language of my own line of work, trying to discern between ousia and hypostasis, nous and logos, form-, text-, and historical-critical arguments to take the few hundred hours it would take to start to get a short handle on the tech-speak of working out what it will take to make this notebook cooperate. Either I get a smart person's help when needed, or I'm back to pencils and paper, and I scribble even worse than I type.
Thanks. Robert For the record, [EMAIL PROTECTED] ~]# uname -a Linux localhost.localdomain 2.6.21-1.3228.fc7 #1 SMP Thu Jun 28 16:42:25 CDT 2007 i686 i686 i386 GNU/Linux [EMAIL PROTECTED] ~]# lspci | grep Broadcom 0a:03.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02) [EMAIL PROTECTED] ~]# dmesg | grep bcm43xx [EMAIL PROTECTED] ~]# _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
