Difference between revisions of "Troubleshooting in Build: Audio"

From FreekiWiki
Jump to navigation Jump to search
(New page: ==DESKTOP BUILD: AUDIO TROUBLESHOOTING== {|class="wikitable" style="text-align:center" font-size="90%" border=".05" cellpadding=".4" width=100% valign="top" |style="text-align:center" w...)
 
Line 2: Line 2:
  
 
{|class="wikitable" style="text-align:center" font-size="90%" border=".05" cellpadding=".4" width=100%  valign="top"  
 
{|class="wikitable" style="text-align:center" font-size="90%" border=".05" cellpadding=".4" width=100%  valign="top"  
|style="text-align:center" width="20%"|'''There is no sound on the "Basic Check" Checklist'''
+
|style="text-align:center" width="20%"|'''There is no sound on the "Sound Check" step of the "Basic Check" Checklist'''
|style="text-align:left" width="80%"|All too frequently, one will spend a whole bunch of time trying to configure a seemingly non-functional wireless only to realize later that there was a much simpler solution.  First, look for a button or switch or combination of keys to activate/deactivate the wireless.  For example, is there a button above the keyboard?  a switch on the side?  maybe Fn + F5 turns the wireless on and off? A wireless antenna icon on the laptop is also a good clue, especially if it is illuminated.
+
|style="text-align:left" width="80%"|You're going along just fine, doing the basic check, and suddenly, when it goes to
|- 
 
 
|style="text-align:center" width="20%"|'''For these wireless cards: Intel PRO/Wireless 2200BG and 2915ABG using the lpw2200 driver'''
 
|style="text-align:center" width="20%"|'''For these wireless cards: Intel PRO/Wireless 2200BG and 2915ABG using the lpw2200 driver'''
 
|style="text-align:left" width="80%"|The indicator light for the Wifi on/off switch does not come on.This confuses quite a few customers (who have turned off their Wifi but do not know how to verify that they have done so). The solution can be found at the following link [http://wiki.freegeek.org/index.php/Enabling_LEDs_on_Intel_Wireless_Cards With thanks to Levi for the fix.]
 
|style="text-align:left" width="80%"|The indicator light for the Wifi on/off switch does not come on.This confuses quite a few customers (who have turned off their Wifi but do not know how to verify that they have done so). The solution can be found at the following link [http://wiki.freegeek.org/index.php/Enabling_LEDs_on_Intel_Wireless_Cards With thanks to Levi for the fix.]
 
|-   
 
|-   
|style="text-align:center" width="20%"|'''BIOS Trickery'''
+
|style="text-align:center" width="20%"|''''''
|style="text-align:left" width="80%"|Check out the BIOS settings. Sometimes there is an option in BIOS to disable/enable a mini-PCI or Wireless device.  If so, make sure that you enable it.
+
|style="text-align:left" width="80%"|
 
|-
 
|-
|style="text-align:center" width="20%"|'''lspci Is Your Friend'''
+
|style="text-align:center" width="20%"|''''''
|style="text-align:left" width="80%" |The '''lspci''' command  is a utility for displaying information about all PCI buses in the system and all devices connected to them.  It will tell you about your wireless card, if there is one installed.  In particular, it will tell you whether your wireless card has a Broadcom chipset (which, if it does, you'll need to install some stuff - see below).  The following example is the output from running '''lspci''' and it demonstrates that the Wireless card has a Broadcom chipset (see the words "Broadcom" and "Wireless" in the same line?).
+
|style="text-align:left" width="80%" |

Revision as of 14:20, 22 February 2011

DESKTOP BUILD: AUDIO TROUBLESHOOTING

There is no sound on the "Sound Check" step of the "Basic Check" Checklist You're going along just fine, doing the basic check, and suddenly, when it goes to For these wireless cards: Intel PRO/Wireless 2200BG and 2915ABG using the lpw2200 driver The indicator light for the Wifi on/off switch does not come on.This confuses quite a few customers (who have turned off their Wifi but do not know how to verify that they have done so). The solution can be found at the following link With thanks to Levi for the fix.
'
'