|
||||||
| Forums FAQ | Members List | Search | Today's Posts | Mark Forums Read |
| Laptop Questions about laptop hardware and laptop specific software (power management ) |
![]() |
|
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
Okay, firstly regarding the wireless.
Quote:
Regarding the sound: Quote:
I have adjusted the mixer settings in kmix and also the volume settings in YAST -> Hardware -> Sound. I also increased volume and toggled mute on/off using the laptop FN key combinations. I also have tried with PulseAudio enabled and disabled in YAST. No errors in either speaker test, but still no sound. Incidentally, sound works fine if I boot into Windows, so I know my hardware is functional. I still think the detection of the sound chip as Nvidia is odd, but could be explainable with one vendor using another's chipset. I think the most telling clue is the message I get on bootup. I got a better look at it this time. It reads: Quote:
I am pretty experienced in Windows administration, but as you can tell my Linux is nearly nil. I appreciate all the help you guys are providing. |
|
|||
|
> I am pretty experienced in Windows administration
unfortunately, most of that experience is not applicable on any version of Linux, Unix, AIX, BSD, etc etc etc.. and, in some cases will lead you down blind alleys and to traps.. these might provide some relief for the frustration that usually builds in the transition process Linux is not Windows http://tinyurl.com/8b9s6 One Guys RANT "Not easier" http://tinyurl.com/yg3y9ca -it *is* difficult at first, as you learn more it will smooth out and in the end you will save all that time installing virus protection, cleaning out the malware, rebooting to solve problems, reinstalling to regain speed and sanity, etc etc etc.. patience and study will pay off.. oh, and your experience WILL help, because it is obvious that you have already learned it is easier to read the documentation BEFORE you break it beyond any level of "back out" is impossible.. -welcome- -- palladium Have a lot of fun.. |
|
||||
|
Quote:
There is more detail on the chipset that we need to dig out. The script I asked you to run: /usr/sbin/alsa-info.shwill dig out that information, and it will post it to a private URL on the internet, which I need you to post the URL here. PLEASE read the more detailed instructions on my above post! Alternative, if no internet, one can run: /usr/sbin/alsa-info.sh --no-uploadwhich will put the output of the script in the file /tmp/alsa-info.txt which one can then copy and paste on a pastebin site such as pastebin - Type, paste, share. ... and post here the URL. Quote:
There are a more than a few threads here to get rid of the error message (it won't fix your sound), where users have posted solutions that worked for them:I think I've seen other "solutions" as well, but a quick search did not reveal it (I probably had the wrong search parameters). |
|
|||
|
On 11/04/2009 09:46 AM, mjung79 wrote:
> I did these two things, but eth1 still does not show up after reboot. I > no longer have to modprobe ieee80211_crypt_tkip, so I believe that part > worked. I do still have to insmod wl.ko for eth1 to appear though. Once > I do that, my wlan works perfectly and my eth0 (wired ethernet) worked > out of the box. Does 'modprobe wl' work? If not, then the 'make install' step failed. Perhaps Broadcom forgot the 'depmod -a' step. As long as 'modprobe wl' works, you should be able to add wl to the MODULES_LOADED_ON_BOOT. |
|
|||
|
Quote:
Quote:
|
|
||||
|
Quote:
Your mixer settings look fine, although you could move the Master volume up from 74% to 95% until we get sound established, and then back off the volume to a lower level to reduce distortion. Please provide the remainder of the information I asked for. ie output of: rpm -qa '*alsa*'That will help me in coming up with the best recommendation. |
|
|||||
|
Here you go, thank you again.
Quote:
Quote:
Quote:
Quote:
Quote:
|
|
||||
|
Quote:
Code:
!!ALSA Version !!------------ Driver version: 1.0.17 Library version: Utilities version: 1.0.18 The reason for that, I believe, is you have inappropriately installed alsa-driver-unstable-kmp-pae, which has prevented your alsa-drive-kmp-pae from functioning. Please remove only alsa-driver-unstable-kmp-pae, and then re-update your alsa versions. To do that, first go to YaST > Software > Software Repositgories and disable your CD/DVD as a respository. Then from a terminal, with your PC connected to the internet, with root permissions, by copying and pasting the following: Code:
zypper ar http://download.opensuse.org/repositories/multimedia:/libs/openSUSE_11.1/ multimedia Code:
zypper install alsa alsa-docs alsa-utils alsa-plugins alsa-tools alsa-plugins-pulse alsa-oss alsa-firmware libasound2 Code:
zypper rr multimedia Code:
zypper ar http://download.opensuse.org/repositories/multimedia:/audio:/KMP/openSUSE_11.1_Update/ multimedia Code:
zypper install alsa-driver-kmp-pae Code:
zypper rr multimedia The above assumes you managed to sort your Internet access. It also assumes you did not inappropriately leave a repository called "multimedia" in your repository list. |
|
|||
|
On 11/04/2009 10:56 AM, mjung79 wrote:
> >> Does 'modprobe wl' work? If not, then the 'make install' step failed. >> Perhaps Broadcom forgot the 'depmod -a' step. As long as 'modprobe wl' >> works, you should be able to add wl to the MODULES_LOADED_ON_BOOT. > > Nope, 'modprobe wl' yields, 'FATAL: Module wl not found.' This gets confusing with two separate threads running. In the future, please keep each problem in its own thread. After you issue the command 'sudo /sbin/depmod -a', does 'sudo /sbin/modprobe wl' then work? If not, please send me the output of sudo find /lib/modules -name wl.ko Thanks. |
![]() |
|
| Bookmarks |
| Tags |
| compaq presario cq50, drivers, sound, wireless |
| Thread Tools | |
| Display Modes | |
|
|