|
OpenBSD General Other questions regarding OpenBSD which do not fit in any of the categories below. |
|
Thread Tools | Display Modes |
|
|
||||
Wireless networking xor battery monitor
I recently installed a 4.5-beta snapshot on my trusty HP Omnibook, and found that everything (including Atheros wireless with WPA) worked nicely except for the battery monitor. Then BSDfan666 chimed in with a tip for disabling apm in favour of acpi. I followed his advice and was pleased to note that klaptop (the battery monitor in KDE) began working!
However, that pleasure was short-lived when I later noticed that my wireless network interface, ath0, no longer existed. Wondering whether the lack of ath0 was related to the lack of apm, I rebooted with apm left on. And sure enough, ath0 was back. I then rebooted with apm disabled once more, and sure enough, ath0 had gone AWOL. This is quite a dilemma. It seems I am forced to choose between wireless networking and a functioning battery monitor. If truth be told, I'm reluctant to do without either feature. Advice and suggestions welcome! |
|
|||
I would highly suggest filing an official report such that the developers are aware of this scenario especially given the off chance that it might be fixed by the release date. Information on sending a PR can be found at the following:
http://openbsd.org/report.html Providing too much information is significantly better than not enough. |
|
||||
This is not the first time we have seen this problem. But, since you have elected not to post your two dmesgs, it will be up to you to determine if you're having the same problem.
In the prior case, the cause was hardware bus enumeration when ACPI was used. See post #27 in http://daemonforums.org/showthread.php?t=2846 If this doesn't match your particular problem, post more information. |
|
||||
Quote:
What could cause bus enumeration to fail, anyway? Is the BIOS in charge of that, or the OS kernel? I have run many other OSes on this laptop without running into ACPI/CardBus conflicts, so I suspect a bug in the OpenBSD kernel rather than the BIOS. Next time I'm in front of the laptop, I'll post the dmesgs. |
|
||||
I'm not sure who to blame. Here's my interpretation:
ACPI is a standard. My understanding, is that either the BIOS makers (and, I suppose, underlying hardware manufacturers) either treat the standard as a "suggestion", or the standard is so loosely defined as to defy any functional interoperability based upon it.For OpenBSD's kernel, users may disable individual ACPI related kernel components, or, disable ACPI entirely. There are, in addition, diagnostic tools, such as acpidump(8), the output which can be used as part of a problem report one sends to misc@ or in an official bug report. |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
gdm/ new monitor issue | jimbus | FreeBSD General | 3 | 4th August 2009 07:39 PM |
Network analyzer/monitor suggestion? | Bruco | FreeBSD Ports and Packages | 2 | 29th January 2009 06:42 PM |
wlan -> monitor mode | ccc | FreeBSD Security | 2 | 4th November 2008 09:19 PM |
What is best way to monitor for bad sectors? | PeterSteele | FreeBSD General | 9 | 16th August 2008 02:41 AM |