Re: b43legacy: My laptop has no button for rfkill but the driver sais it has...
On Thursday 25 December 2008, Ulf Dambacher wrote: >Hi > >Michael Buesch schrieb: >> On Wednesday 24 December 2008 18:16:20 Ulf Dambacher wrote: >>> And both drivers use exactly the same code to test for the rfkill button. >>> one sais on the other sees off. >> >> You must also honor the fact that you are running a completely different >> kernel. It's _not_ that just "one driver works, but the other doesn't". >> Something else in the kernel can be poking with the rfkill. Look at acpi >> and stuff like that. > >Yes, thats a point. I'll start with a 2.6.24.7 as this is a kernel with >both drivers and I'll config it equally but for the drivers. >I'll try with minimum options first and if that works, I'll start to >activate all that gimmicks that fiddle with bios, acpi, dmi, smb, wms, >i2c or dell laptops. > >Hopefully I find something working. If only this system would compile >faster ... Look up 'ccache'. It helps me build a new kernel in 2 to 4 minutes, depending on how much of it is really new. >merry xmas and bye >Ulf >___ >Bcm43xx-dev mailing list >Bcm43xx-dev@lists.berlios.de >https://lists.berlios.de/mailman/listinfo/bcm43xx-dev -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Do nothing unless you must, and when you must act -- hesitate. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43legacy: My laptop has no button for rfkill but the driver sais it has...
Hi Michael Buesch schrieb: > On Wednesday 24 December 2008 18:16:20 Ulf Dambacher wrote: >> And both drivers use exactly the same code to test for the rfkill button. >> one sais on the other sees off. > > You must also honor the fact that you are running a completely different > kernel. > It's _not_ that just "one driver works, but the other doesn't". > Something else in the kernel can be poking with the rfkill. Look at acpi and > stuff like that. > Yes, thats a point. I'll start with a 2.6.24.7 as this is a kernel with both drivers and I'll config it equally but for the drivers. I'll try with minimum options first and if that works, I'll start to activate all that gimmicks that fiddle with bios, acpi, dmi, smb, wms, i2c or dell laptops. Hopefully I find something working. If only this system would compile faster ... merry xmas and bye Ulf ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43legacy: My laptop has no button for rfkill but the driver sais it has...
On Wednesday 24 December 2008 18:16:20 Ulf Dambacher wrote: > And both drivers use exactly the same code to test for the rfkill button. one > sais on the other sees off. You must also honor the fact that you are running a completely different kernel. It's _not_ that just "one driver works, but the other doesn't". Something else in the kernel can be poking with the rfkill. Look at acpi and stuff like that. -- Greetings, Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43legacy: My laptop has no button for rfkill but the driver sais it has...
On Wed, Dec 24, 2008 at 12:16 PM, Ulf Dambacher wrote: > Hi together > > To get it right: > - i have no rfkill hardware button anywhere on the laptop. > - Yesterday I opened it and there are no unused pins or connectors on the > card or the motherboard. > - the computer does not run any m$ software wich could interfere here > - my dell bios (version A32) sais the card is enabled and activated and can > be switched by software > - if I boot a kernel 2.6.22 and i use the bcm43xx driver it is happily > transmitting wireless > - if i reboot to kernel 2.6.27.9 and use the b43legacy driver it warns me > that i have turned the device on by software but a hardware button still > turns it off > - i8k does not work > - dell-laptop does not work > - Until now, I did not find switch in wmi, acpi, > > Now the tricky part: > - if I hack the b43legacy driver to ignore the button settings IT IS ABLE TO > ASCCOCIATE WITH MY AP > - get that again: it transmits some message that my ap obviously can receive > and it obviously receives a reply that it is associated. > - no ip packets can be received, it claims to have send some pings though. > > If Michael Buesch sais the driver can not overwrite hardware rfkill, I thake > that for granted and conclude that my card must be on but something else > holds it from sending and/or receiving packets - rember, its associated with > the ap... > This would be in line with the fact that the bcm43xx driver is indeed working. > And both drivers use exactly the same code to test for the rfkill button. one > sais on the other sees off. > > Im just reading code and fiddling with all the dell options and wmi and smb > options to get any hooks on where to find my button > > merry xmas and bye > Ulf OK, just a few thoughts on this.. you obviously have some sort of issue that's preventing you from using the new b43legacy driver. Unfortunately, you've only tested the latest version of the driver and nothing prior. Before blaming b43legacy as the cause, you should first try to determine if the b43legacy driver ever worked on your system. Doing a git bisect of the kernel tree should help you determine the point at which it worked or didn't work and eventually find the commit that caused the issue. If git bisect reveals the b43legacy driver never worked on your system since it's inclusion into the kernel and the last version of bcm43xx did work then you can blame the b43legacy driver. Until then, like Michael, I am suspect to believe the b43legacy driver is the cause of your issue. Regards, David Ellingsworth ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43legacy: My laptop has no button for rfkill but the driver sais it has...
Hi together To get it right: - i have no rfkill hardware button anywhere on the laptop. - Yesterday I opened it and there are no unused pins or connectors on the card or the motherboard. - the computer does not run any m$ software wich could interfere here - my dell bios (version A32) sais the card is enabled and activated and can be switched by software - if I boot a kernel 2.6.22 and i use the bcm43xx driver it is happily transmitting wireless - if i reboot to kernel 2.6.27.9 and use the b43legacy driver it warns me that i have turned the device on by software but a hardware button still turns it off - i8k does not work - dell-laptop does not work - Until now, I did not find switch in wmi, acpi, Now the tricky part: - if I hack the b43legacy driver to ignore the button settings IT IS ABLE TO ASCCOCIATE WITH MY AP - get that again: it transmits some message that my ap obviously can receive and it obviously receives a reply that it is associated. - no ip packets can be received, it claims to have send some pings though. If Michael Buesch sais the driver can not overwrite hardware rfkill, I thake that for granted and conclude that my card must be on but something else holds it from sending and/or receiving packets - rember, its associated with the ap... This would be in line with the fact that the bcm43xx driver is indeed working. And both drivers use exactly the same code to test for the rfkill button. one sais on the other sees off. Im just reading code and fiddling with all the dell options and wmi and smb options to get any hooks on where to find my button merry xmas and bye Ulf Pt! Schon vom neuen WEB.DE MultiMessenger gehört? Der kann`s mit allen: http://www.produkte.web.de/messenger/?did=3123 ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43legacy: My laptop has no button for rfkill but the driver sais it has...
On Wednesday 24 December 2008 16:58:14 Gene Heskett wrote: > With all due respect Michael, if it has been disabled by the panel switch > such > as the one on my lappy, can it not be made to emit such an error message so > that we know we have to toggle that pushbutton? We emit a message that the radio is disabled. The b43 driver has exactly one read-only bit to determine whether the radio is on or off. It polls that bit every second and displays a message when it got toggled. That's all we can do from within the driver. _If_ you can switch it by software, which is theoretically possible of course, then _not_ through the broadcom wireless PCI device. It has to be done through another device. So you must load the driver for that device and switch the signal. > On my HP- dv5120us, there is > no tactile feel, or any other means to determine the state of this switch, an > apparently push-push switch. The LED is no help cuz you can and do turn it > on and off at will regardless of the state of the switch. Having to push the > button and reboot to see if that fixes it doesn't seem like a very productive > way to spend an evening. So I give up and plug in a cable, hundreds of times > faster to get a network connection, or if on the road, to borrow a little > dlink tranceiver from the motel. That after all, is the target condition we > are trying to achieve. I think you should send this to HP. I really can't do anything about it. All I have is one single read-only bit. -- Greetings, Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43legacy: My laptop has no button for rfkill but the driver sais it has...
On Wednesday 24 December 2008, Michael Buesch wrote: >On Wednesday 24 December 2008 11:16:36 Ulf Dambacher wrote: >> Matthew Garrett schrieb: >> > On Sat, Dec 20, 2008 at 06:08:17PM +0100, Ulf Dambacher wrote: >> >> Hi >> >> >> >> I hav a dell inspiron 5100 and it has no hardware button device to >> >> toggle rfkill. >> >> The broadcom bcm4301 card has this feature and the driver sees it and >> >> disables itself hard, wich can not be overwritten by software. >> > >> > The dell-laptop driver is worth a go - it provides support for >> > controlling the Dell-specific rfkill interface. It may (or may not) help >> > here. >> >> Hi Matthew >> >> I still don't think its a general problem, but a problem that b43legacy >> does miss something bcm43xx does to initialize my hardware to enable it. > >We cannot enable the radio from within the driver, if it's hardware > disabled. We cannot do this in b43legacy and we cannot do this in bcm43xx. > Fullstop. > With all due respect Michael, if it has been disabled by the panel switch such as the one on my lappy, can it not be made to emit such an error message so that we know we have to toggle that pushbutton? On my HP- dv5120us, there is no tactile feel, or any other means to determine the state of this switch, an apparently push-push switch. The LED is no help cuz you can and do turn it on and off at will regardless of the state of the switch. Having to push the button and reboot to see if that fixes it doesn't seem like a very productive way to spend an evening. So I give up and plug in a cable, hundreds of times faster to get a network connection, or if on the road, to borrow a little dlink tranceiver from the motel. That after all, is the target condition we are trying to achieve. >If it fails now and didn't fail earlier, it almost certainly is something >_else_ that disables the rf. >Please make sure _all_ dell related kernel modules are loaded >and all dell related kernel options are enabled (there are quite a few). >And try to use the dell-tool that was suggested earlier in the thread. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) the difference between theory and practice is just a lot of work - from #offtopic (the offtopic chat channel of #kernelnewbies) ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43legacy: My laptop has no button for rfkill but the driver sais it has...
On Wednesday 24 December 2008 11:16:36 Ulf Dambacher wrote: > Matthew Garrett schrieb: > > On Sat, Dec 20, 2008 at 06:08:17PM +0100, Ulf Dambacher wrote: > >> Hi > >> > >> I hav a dell inspiron 5100 and it has no hardware button device to > >> toggle rfkill. > >> The broadcom bcm4301 card has this feature and the driver sees it and > >> disables itself hard, wich can not be overwritten by software. > > > > The dell-laptop driver is worth a go - it provides support for > > controlling the Dell-specific rfkill interface. It may (or may not) help > > here. > > > > Hi Matthew > > I still don't think its a general problem, but a problem that b43legacy > does miss something bcm43xx does to initialize my hardware to enable it. We cannot enable the radio from within the driver, if it's hardware disabled. We cannot do this in b43legacy and we cannot do this in bcm43xx. Fullstop. If it fails now and didn't fail earlier, it almost certainly is something _else_ that disables the rf. Please make sure _all_ dell related kernel modules are loaded and all dell related kernel options are enabled (there are quite a few). And try to use the dell-tool that was suggested earlier in the thread. -- Greetings, Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43legacy: My laptop has no button for rfkill but the driver sais it has...
Matthew Garrett schrieb: > On Sat, Dec 20, 2008 at 06:08:17PM +0100, Ulf Dambacher wrote: >> Hi >> >> I hav a dell inspiron 5100 and it has no hardware button device to >> toggle rfkill. >> The broadcom bcm4301 card has this feature and the driver sees it and >> disables itself hard, wich can not be overwritten by software. > > The dell-laptop driver is worth a go - it provides support for > controlling the Dell-specific rfkill interface. It may (or may not) help > here. > Hi Matthew I still don't think its a general problem, but a problem that b43legacy does miss something bcm43xx does to initialize my hardware to enable it. Anyway, Larry Finger also pointed me to your patches. I searched them from lkml and applied them to a 2.6.27.9 kernel (with some hand-work) When loading the module dell-laptop I get: FATAL: Eroor inserting dell_laptop: No such device Kernel dmesg sais: dcbas dcbas: Dell Systems management base Driver (version 5.6.0-3.2) So my system is not listed in your device_table? Attached is the output of dmidecode. And yes, i tested i8k (forced load) too without success. merry xmas Ulf ---8<-- > # dmidecode 2.9 > SMBIOS 2.3 present. > 41 structures occupying 1507 bytes. > Table at 0x000F9660. > > Handle 0xDA00, DMI type 218, 53 bytes > OEM-specific Type > Header and Data: > DA 35 00 DA B2 00 0D 1F 0F 37 40 7D 00 00 00 00 > 00 7E 00 02 00 00 00 01 F0 01 F0 00 00 02 F0 02 > F0 00 00 03 F0 03 F0 00 00 04 F0 04 F0 00 00 FF > FF 00 00 00 00 > > Handle 0x, DMI type 0, 20 bytes > BIOS Information > Vendor: Dell Computer Corporation > Version: A32 > Release Date: 10/18/2004 > Address: 0xF > Runtime Size: 64 kB > ROM Size: 576 kB > Characteristics: > ISA is supported > PCI is supported > PC Card (PCMCIA) is supported > PNP is supported > APM is supported > BIOS is upgradeable > BIOS shadowing is allowed > Boot from CD is supported > Selectable boot is supported > 3.5"/720 KB floppy services are supported (int 13h) > Print screen service is supported (int 5h) > 8042 keyboard services are supported (int 9h) > Serial services are supported (int 14h) > Printer services are supported (int 17h) > CGA/mono video services are supported (int 10h) > ACPI is supported > USB legacy is supported > AGP is supported > Smart battery is supported > BIOS boot specification is supported > Function key-initiated network boot is supported > > Handle 0x0100, DMI type 1, 25 bytes > System Information > Manufacturer: Dell Computer Corporation > Product Name: Inspiron 5100 > Version: Not Specified > Serial Number: 2QTMP0J > UUID: 44454C4C-5100-1054-804D-B2C04F50304A > Wake-up Type: Power Switch > > Handle 0x0200, DMI type 2, 9 bytes > Base Board Information > Manufacturer: Dell Computer Corporation > Product Name: 09U806 > Version: > Serial Number: .2QTMP0J.CN1296133C4728. > > Handle 0x0300, DMI type 3, 13 bytes > Chassis Information > Manufacturer: Dell Computer Corporation > Type: Portable > Lock: Not Present > Version: Not Specified > Serial Number: 2QTMP0J > Asset Tag: Not Specified > Boot-up State: Safe > Power Supply State: Safe > Thermal State: Safe > Security Status: None > > Handle 0x0400, DMI type 4, 32 bytes > Processor Information > Socket Designation: Microprocessor > Type: Central Processor > Family: Pentium 4 > Manufacturer: Intel > ID: 27 0F 00 00 FF F9 EB BF > Signature: Type 0, Family 15, Model 2, Stepping 7 > Flags: > FPU (Floating-point unit on-chip) > VME (Virtual mode extension) > DE (Debugging extension) > PSE (Page size extension) > TSC (Time stamp counter) > MSR (Model specific registers) > PAE (Physical address extension) > MCE (Machine check exception) > CX8 (CMPXCHG8 instruction supported) > SEP (Fast system call) > MTRR (Memory type range registers) > PGE (Page global enable) > MCA (Machine check architecture) > CMOV (Conditional move instruction supported) > PAT (Page attribute table) > PSE-36 (36-bit page size extension) > CLFSH (CLFLUSH instruction supported) > DS (Debug store) > ACPI (ACPI supported) > MMX (MMX technology supported) > FXSR (Fast floati
Re: b43legacy: My laptop has no button for rfkill but the driver sais it has...
On Sat, Dec 20, 2008 at 06:08:17PM +0100, Ulf Dambacher wrote: > Hi > > I hav a dell inspiron 5100 and it has no hardware button device to > toggle rfkill. > The broadcom bcm4301 card has this feature and the driver sees it and > disables itself hard, wich can not be overwritten by software. The dell-laptop driver is worth a go - it provides support for controlling the Dell-specific rfkill interface. It may (or may not) help here. -- Matthew Garrett | mj...@srcf.ucam.org ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43legacy: My laptop has no button for rfkill but the driver sais it has...
Larry Finger wrote: > If your laptop does not have an RFKILL button, I have no idea where > the signal to kill the radio is coming from. It can be connected to just about any GPIO pin on any chip in the system. The super IO, embedded controller and chipset all have IOs to spare, some chips have a lot of them too. Two designers at the Taiwanese ODM may know which pin controls it. Reverse engineer it. //Peter ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43legacy: My laptop has no button for rfkill but the driver sais it has...
Larry Finger schrieb: > As your next post shows, merely ignoring the RFKILL setting may do no good. If > the hardware sees that the radio is turned off by the "button", then there is > nothing the driver can do. The firmware will disable the radio. Accordingly, > your hack does no good. Hi Larry With the old bcm43xx driver, everything works well without me ever fiddling with the bios (btw. it sais enabled and software controls the card) If I bood to the old 2.6.23 kernel i don't have any problems. If I bood to 2.6.27.9 nothing works anymore. So the problems are with the new driver version. And if I can associate with the ap using the (rfkill-hacked) 2.6.27.9-b43legacy driver this means that packets are indeed sent (or else my ap would not see my laptop) This is why I posted two different problems. bye Ulf ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43legacy: My laptop has no button for rfkill but the driver sais it has...
Ulf Dambacher wrote: > Hi > > I hav a dell inspiron 5100 and it has no hardware button device to > toggle rfkill. > The broadcom bcm4301 card has this feature and the driver sees it and > disables itself hard, wich can not be overwritten by software. > > I tested a little bit with a hacked version always returning on on > rfkill pollling and that worked (partly, see next post) As your next post shows, merely ignoring the RFKILL setting may do no good. If the hardware sees that the radio is turned off by the "button", then there is nothing the driver can do. The firmware will disable the radio. Accordingly, your hack does no good. If your laptop does not have an RFKILL button, I have no idea where the signal to kill the radio is coming from. The BIOS in some computers has a setting that lets Windows turn off the radio when the system hibernates. If you then boot Linux, the radio will be off. Check if you have an option to override that behavior in your system. There is a facility called the Windows Management Interface (WMI) that is used to control facilities like this. A rudimentary one for Dell laptops is floating around, but not yet in the mainline kernels. The author is Matthew Garrett . Perhaps he knows more about the coding for Dell machines. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
b43legacy: My laptop has no button for rfkill but the driver sais it has...
Hi
I hav a dell inspiron 5100 and it has no hardware button device to
toggle rfkill.
The broadcom bcm4301 card has this feature and the driver sees it and
disables itself hard, wich can not be overwritten by software.
I tested a little bit with a hacked version always returning on on
rfkill pollling and that worked (partly, see next post)
I propose a module parameter to ignore the rfkill button setting.
I think the polling routine should not be registered if the button is to
be ignoerd.
If I want to send a patch for that, what would be better way to
implement it:
- putting some extern declaration in one of the headers (bcm43legacy.h
or main.h?) and test this directly within b43legacy_rfkill_init
- put a new filed in the dev structure for disabling the rfkill button?
- use enum { disable,enable, ignore} radio_hw_enable
bye
Ulf
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: My Laptop
On Wed, Dec 12, 2007 at 11:12:58PM -0500, Matthew Saltzman wrote: > > On Wed, 2007-12-12 at 17:00 -0500, Stuart D. Gathman wrote: > > On Wed, 12 Dec 2007, Larry Finger wrote: > > > > > Stuart D. Gathman wrote: > > >> , but I got kernel exceptions, DMA exception, and eventually the > > >> system froze. I would say it is not ready for prime time. (I will be > > >> looking for where to helpfully report the exceptions for those trying to > > >> debug the thing. I suspect donations of relevant hardware are most > > >> useful.) No problems with the zd1211 driver and USB key. > > > > > > I'm sorry that you had troubles with the BCM94311MCG in your laptop, but > > > I > > > think most of your problems are fixed in driver b43 in any of the > > > 2.6.24-rcX > > > kernels. In any case, the place to report such problems is > > > [EMAIL PROTECTED] > > > > FC8 has 2.6.23. I suppose FC9 might do the trick. Or maybe they'll > > backport > > some fixes. > > Fedora generally releases kernel updates fairly quickly to track > upstream (though they have patches to port forward before they are > ready). There's no 2.6.24 in updates-testing yet, however. > kernel-2.6.23.9-85 is there. Are you looking for wireless patches? At this moment there are no wireless bits in wireless-2.6 that are not in the latest Fedora kernels in Koji. The last one I built is here: http://koji.fedoraproject.org/koji/buildinfo?buildID=27585 Hth! John -- John W. Linville [EMAIL PROTECTED] ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: My Laptop
Stuart D. Gathman wrote: > Broadcom wireless is only partially reverse engineered. I tried the > b43 driver in FC8 on the BCM94311MCG in my new laptop. It worked, with > WPA even, but I got kernel exceptions, DMA exception, and eventually the > system > froze. I would say it is not ready for prime time. (I will be looking for > where to helpfully report the exceptions for those trying to debug > the thing. I suspect donations of relevant hardware are most useful.) > No problems with the zd1211 driver and USB key. I'm sorry that you had troubles with the BCM94311MCG in your laptop, but I think most of your problems are fixed in driver b43 in any of the 2.6.24-rcX kernels. In any case, the place to report such problems is [EMAIL PROTECTED] I have both rev 1 and 2 of that PCIe card for my laptop, and I have no kernel or DMA exceptions, the system never freezes, and my throughput is higher with the b43 driver than with Windows using the Broadcom driver. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
