No Sound on Gateway Laptop
Hmmm .....
Alsa pet install notes:
1. Please note your kernel version.
2. Do not install from a fat32/ntfs partition. Download/copy to /tmp or any ext2 partition before installing.
3. A quick way to test would be using pfix=ram if you have enough ram.
AD1981B is AC97 audio hardware. Those HDA model options is irrelevant.
I asked our friend google to do a quick check for AD1981B and found:
- http://www.thinkwiki.org/wiki/AD1981B
- http://ubuntuforums.org/showthread.php?t=693088
- https://answers.launchpad.net/ubuntu/+question/75286
which indicates that on certain cases of AD1981B, the headphone jack sense may need to be switched off to enable speaker audio. Open alsamixer and toggle the headphone jack sense if any.
Other from the above, I have absolutely no idea how to fix this in alsa.
Rgds
Alsa pet install notes:
1. Please note your kernel version.
2. Do not install from a fat32/ntfs partition. Download/copy to /tmp or any ext2 partition before installing.
3. A quick way to test would be using pfix=ram if you have enough ram.
AD1981B is AC97 audio hardware. Those HDA model options is irrelevant.
I asked our friend google to do a quick check for AD1981B and found:
- http://www.thinkwiki.org/wiki/AD1981B
- http://ubuntuforums.org/showthread.php?t=693088
- https://answers.launchpad.net/ubuntu/+question/75286
which indicates that on certain cases of AD1981B, the headphone jack sense may need to be switched off to enable speaker audio. Open alsamixer and toggle the headphone jack sense if any.
Other from the above, I have absolutely no idea how to fix this in alsa.
Rgds
Turk Nailik,
To settle my curiosity, open a [rxvt] session by clicking on your desktop Console icon. Type: and hit Enter. (That last character of code is a small-case L, by the way.)
My buddy's Model 7305 Gateway laptop returns the following:
Does your machine show the same thing?
-Roy
To settle my curiosity, open a [rxvt] session by clicking on your desktop Console icon. Type:
Code: Select all
aplay -l
My buddy's Model 7305 Gateway laptop returns the following:
Code: Select all
# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: I82801DBICH4 [Intel 82801DB-ICH4], device 0: Intel ICH [Intel 82801DB-ICH4]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: I82801DBICH4 [Intel 82801DB-ICH4], device 4: Intel ICH - IEC958 [Intel 82801DB-ICH4 - IEC958]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: Modem [Intel 82801DB-ICH4 Modem], device 0: Intel ICH - Modem [Intel 82801DB-ICH4 Modem - Modem]
Subdevices: 0/1
Subdevice #0: subdevice #0
#
-Roy
No sound on Gateway laptop
I also have a Gateway .Puppy 4.2 live cd.NO sound.I did all the things that were suggested.I stumbled upon this solution ,why it works I don't know,maybe someone else does.When powering up wait for the Gateway screen,press F2 to enter Bios setup.You don't have to do anything just press F10 and exit saving changes.Puppy will boot up and you should have sound. I tried this afew times and everything works woof woof on delete,cd audio,and video sound.Thanks for all the info!
Ricky,
You might be on to something! When I was helping my buddy out with a frugal install of Puppy on his Gateway, I did open his laptop's BIOS to change his boot order, save, and exit. Hmmm...
I have learned a bit while trying to help these guys with their Gateway laptops, and will try to summarize it from memory here:
These particular Gateway laptops are using AC97 sound that **should** be picked up by Puppy's defaults.
Running the Sound Wizard -- or even selecting the Sound Wizard without actually using it -- broke the sound on my buddy's Gateway. I strongly recommend you do this only when running as a Live CD (no save file) to see what hardware is detected before any installation begins.
The last part of Turk Nailik's modprobe.conf file looks like this:
165 alias snd-card-0 snd-intel8x0m
166 alias sound-slot-0 snd-intel8x0m
My buddy's modprobe.conf file did not have the m's until after I had selected the sound wizard and broken his sound. Then his modprobe.conf file looked exactly like Turk Nailik's and the machine was silent.
Turk Nailik wrote:
Patriot's .pet does fix the sound issue on my Dell Mini-9, without requiring me to manually modify my own modprobe.conf file, but I did not use it on my buddy's Gateway, so that remains unconfirmed in this particular case with these Gateways. I will say that I do not believe that running Patriot's .pet has any real downside to it; I doubt it will break anything and know it will fix some sound issues, as it did on my Dell machine.
And yes, Ricky, it may be that opening and saving the BIOS might set or reset something important -- although I am much too new to understand what or why. Both of us opened and saved our BIOS files and both of these machines have sound. Thank you very much for pointing that out!
My buddy has since re-claimed his Gateway laptop, so I have nothing further to test with.
-Roy
You might be on to something! When I was helping my buddy out with a frugal install of Puppy on his Gateway, I did open his laptop's BIOS to change his boot order, save, and exit. Hmmm...
I have learned a bit while trying to help these guys with their Gateway laptops, and will try to summarize it from memory here:
These particular Gateway laptops are using AC97 sound that **should** be picked up by Puppy's defaults.
Code: Select all
INTEL 18X0 8086:24C5 (REV3)
The last part of Turk Nailik's modprobe.conf file looks like this:
165 alias snd-card-0 snd-intel8x0m
166 alias sound-slot-0 snd-intel8x0m
My buddy's modprobe.conf file did not have the m's until after I had selected the sound wizard and broken his sound. Then his modprobe.conf file looked exactly like Turk Nailik's and the machine was silent.
Turk Nailik wrote:
I **think** this is showing what Puppy **believes** you have for your sound chipset(s) / sound modem / whatever (don't know the correct terminology). Since Turk Nailik had run his sound wizard, thus modifying his modprobe.conf file and breaking any chance of sound, was Puppy showing the actual chipset in his machine or a different (incorrectly set by the Sound Wizard) one?Also, your sgmixer is labeled "Conexant id 30" while mine is called "Analog Devices AD 1981B"
Patriot's .pet does fix the sound issue on my Dell Mini-9, without requiring me to manually modify my own modprobe.conf file, but I did not use it on my buddy's Gateway, so that remains unconfirmed in this particular case with these Gateways. I will say that I do not believe that running Patriot's .pet has any real downside to it; I doubt it will break anything and know it will fix some sound issues, as it did on my Dell machine.
And yes, Ricky, it may be that opening and saving the BIOS might set or reset something important -- although I am much too new to understand what or why. Both of us opened and saved our BIOS files and both of these machines have sound. Thank you very much for pointing that out!
My buddy has since re-claimed his Gateway laptop, so I have nothing further to test with.
-Roy
I have been trying to get sound working on the new wife's Gateway 7326GZ with similar Intel hardware and having the same problems.
I might have a few more bits of info to try and track down the problem.
Sound worked longer ago using 4.0.3 (found old cd, booted and sound works)
No sound under 4.3 full (or Tuxx's 4.31.1)
BUT I do get sound using 4.3 small!!!
It seems it may have some thing to do not just with the sound but also the modem which seems to use the same hardware.
In full it loads the hfs modem module, but small loads intel8x0m (same in 4.0.3)
I tried blacklisting all the hfs modules, still no sound.
Added intel8x0m. No sound.
Added other modules that were different between 4.0.3 and 4.3 : slamr and slusb. No sound.
Checked modem. Still showed ttyhfs0. Erased, rebooted and re-probed and found ttysl0?? Modem seems to work, but no Sound.
For grins I re-ran ALSA config. I hear the speakers click when module installs, but no sound.
Took out the slamr and slub modules I added earlier, and ran ALSA config again, same result.
Does anything here make sense??
What is different between 4.0.3 and 4.3?? The "zdrv" file? Why does having extra drivers cause the wrong one(s) to load? Are the extra drivers broken?
Is it something else all together? I have came to the limit of my knowledge, can anyone give a hand?
Side note - may be important - Sound worked in and earlier version of Fedora (F8?) but is also broken in F10 and F11 as well. Is there a common problem here? ALSA broken?
I might dig up my old F8 disks and give it a spin as well to see what is different and report back.
I'll never get her to drop M$ if I can't crack this. And 4.3 (and 4.31.1) are so slick!!
Lyle
I might have a few more bits of info to try and track down the problem.
Sound worked longer ago using 4.0.3 (found old cd, booted and sound works)
No sound under 4.3 full (or Tuxx's 4.31.1)
BUT I do get sound using 4.3 small!!!
It seems it may have some thing to do not just with the sound but also the modem which seems to use the same hardware.
In full it loads the hfs modem module, but small loads intel8x0m (same in 4.0.3)
I tried blacklisting all the hfs modules, still no sound.
Added intel8x0m. No sound.
Added other modules that were different between 4.0.3 and 4.3 : slamr and slusb. No sound.
Checked modem. Still showed ttyhfs0. Erased, rebooted and re-probed and found ttysl0?? Modem seems to work, but no Sound.
For grins I re-ran ALSA config. I hear the speakers click when module installs, but no sound.
Took out the slamr and slub modules I added earlier, and ran ALSA config again, same result.
Does anything here make sense??
What is different between 4.0.3 and 4.3?? The "zdrv" file? Why does having extra drivers cause the wrong one(s) to load? Are the extra drivers broken?
Is it something else all together? I have came to the limit of my knowledge, can anyone give a hand?
Side note - may be important - Sound worked in and earlier version of Fedora (F8?) but is also broken in F10 and F11 as well. Is there a common problem here? ALSA broken?
I might dig up my old F8 disks and give it a spin as well to see what is different and report back.
I'll never get her to drop M$ if I can't crack this. And 4.3 (and 4.31.1) are so slick!!
Lyle
That report is KEY. Anyone care to put a, ahem ... bug in Barry's ear about this?lwill wrote: No sound under 4.3 full (or Tuxx's 4.31.1)
BUT I do get sound using 4.3 small!!!
[size=84][i]hangout:[/i] ##b0rked on irc.freenode.net
[i]diversion:[/i] [url]http://alienjeff.net[/url] - visit The Fringe
[i]quote:[/i] "The foundation of authority is based upon the consent of the people." - Thomas Hooker[/size]
[i]diversion:[/i] [url]http://alienjeff.net[/url] - visit The Fringe
[i]quote:[/i] "The foundation of authority is based upon the consent of the people." - Thomas Hooker[/size]
Got it to work!!
Not sure which change it was that did it so I made a fresh install and tried to retrace my steps.
Here is what I did:
Fresh install. (Ttuuxxx's 3.31.1 frugal) Create save file. Reboot.
Black listed all hfs* modules.
Ran connection wizard. chose modem, Probe, then erase.(Since ttySHFS0 was still selected)
Reboot.
SOUND WORKS!!!!
I did not run ALSA config.
BUT cannot find a modem. This doesn't bother me too much since I never use it, but would be nice if it worked in an emergency.
Apparently the reason sound worked in small was because the hfs modem modules were not included, so they were not installed. The sound card seems to need snd_intel9x0m loaded and it conflicts with some of the hfs modules and will not load. (I found this error when I tried modprobe -v snd_intel8x0)
Now, I am sure there is a better / more permanent way doing this (give preference to one module over another??) but I am not familiar enough with how all of the drivers interact to find a better way on my own.
Maybe some one could suggest a better solution to Barry for the next release??
Any one with similar hardware / sound problem want to verify this?
Lyle
Not sure which change it was that did it so I made a fresh install and tried to retrace my steps.
Here is what I did:
Fresh install. (Ttuuxxx's 3.31.1 frugal) Create save file. Reboot.
Black listed all hfs* modules.
Ran connection wizard. chose modem, Probe, then erase.(Since ttySHFS0 was still selected)
Reboot.
SOUND WORKS!!!!
I did not run ALSA config.
BUT cannot find a modem. This doesn't bother me too much since I never use it, but would be nice if it worked in an emergency.
Apparently the reason sound worked in small was because the hfs modem modules were not included, so they were not installed. The sound card seems to need snd_intel9x0m loaded and it conflicts with some of the hfs modules and will not load. (I found this error when I tried modprobe -v snd_intel8x0)
Now, I am sure there is a better / more permanent way doing this (give preference to one module over another??) but I am not familiar enough with how all of the drivers interact to find a better way on my own.
Maybe some one could suggest a better solution to Barry for the next release??
Any one with similar hardware / sound problem want to verify this?
Lyle
Thanks to all of you in this thread for your perseverance on this complex issue. As instigator of the Conexant modem support, I feel a responsibility to join in. Your information gives me a lot to work with.
I would like to take this up in the 4.3 Bugs thread, since the problems may be aggravated by the 4.3 addition of those drivers, as well as the patching of the ALSA driver to accommodate Conexant HDA modems.
I am concerned that there is an apparent conflict in Puppy's choice of modem drivers. But I see only the ID of the sound card here and need to know the ID of the modem. That ID triggers the driver selection. It could be that the same ID is accociated with both the Intel and HSF drivers. Could someone post (in 4.3 Bugs) what PupScan (in 4.3, with the zp430305.sfs file included) shows for the PCI interfaces for sound and modems? Also please note which sound and modem drivers are actually loaded (lsmod) in the various cases.
I am also interested in attempting to automate handling of situations requiring special "model =" updates to modprobe.conf. But that appears to be of lower priority, if I understand the conclusions you all have come to. Thank you for any further help you can provide to work this out for everyone.
Richard
I would like to take this up in the 4.3 Bugs thread, since the problems may be aggravated by the 4.3 addition of those drivers, as well as the patching of the ALSA driver to accommodate Conexant HDA modems.
I am concerned that there is an apparent conflict in Puppy's choice of modem drivers. But I see only the ID of the sound card here and need to know the ID of the modem. That ID triggers the driver selection. It could be that the same ID is accociated with both the Intel and HSF drivers. Could someone post (in 4.3 Bugs) what PupScan (in 4.3, with the zp430305.sfs file included) shows for the PCI interfaces for sound and modems? Also please note which sound and modem drivers are actually loaded (lsmod) in the various cases.
I am also interested in attempting to automate handling of situations requiring special "model =" updates to modprobe.conf. But that appears to be of lower priority, if I understand the conclusions you all have come to. Thank you for any further help you can provide to work this out for everyone.
Richard
I have found a better / proper fix!
Please check the 4.30 bug thread for a fix from rerwin for the modem conflicts.
http://www.murga-linux.com/puppy/viewto ... &start=225
Then try this in terminal:
If sound works then add this to your /etc/init.d/alsa just after the line
set "Audigy Analog/Digital Output Jack" off
For me sound and modem worked and even get modem sounds when dialing!
Good Luck!
Lyle
Please check the 4.30 bug thread for a fix from rerwin for the modem conflicts.
http://www.murga-linux.com/puppy/viewto ... &start=225
Then try this in terminal:
Code: Select all
amixer set 'Eternal Amplifier' off
set "Audigy Analog/Digital Output Jack" off
Code: Select all
set "External Amplifier" off
Good Luck!
Lyle
lwill,
You imply that the MODDULESCONFIG edit is needed. I am not currently submitting that technique for 4.3.1, so am curious whether it is really necessary. Will your ALSA fix alone solve the problem?
My take from your experience with that mod (reported via PM to me) is that intel8x0m got loaded first and the HSF modules (mysteriously) came later. Although I can't explain why the HSFs were loaded, since we were overriding their use, the result suggests there is a requirement for the modules to load in that sequence. There may be a better way to do that. What happens without that mod? And (with the mod) does it still work after a reboot? Since HSF disables intel8x0m, that might prevent its loading after the first time.
To help me understand this more, could you post the lsmod output from the successful Fedora run, as well as that from the good puppy run? I remain concerned about getting this HSF-and-sound thing right. Thanks.
Richard
You imply that the MODDULESCONFIG edit is needed. I am not currently submitting that technique for 4.3.1, so am curious whether it is really necessary. Will your ALSA fix alone solve the problem?
My take from your experience with that mod (reported via PM to me) is that intel8x0m got loaded first and the HSF modules (mysteriously) came later. Although I can't explain why the HSFs were loaded, since we were overriding their use, the result suggests there is a requirement for the modules to load in that sequence. There may be a better way to do that. What happens without that mod? And (with the mod) does it still work after a reboot? Since HSF disables intel8x0m, that might prevent its loading after the first time.
To help me understand this more, could you post the lsmod output from the successful Fedora run, as well as that from the good puppy run? I remain concerned about getting this HSF-and-sound thing right. Thanks.
Richard
Sorry, due to my excitement and the late hour, I was not as thorough or clear as I should have been.
I have tried to find the least common denominator.
Booted from CD pfix=ram. Modem worked, no sound.
Opened terminal and ran:
amixer set 'Eternal Amplifier' off
Sound and modem both work. That was all that was needed.
Included lsmod from this point and from my F11 install (both work)
So I would conclude the sound problem is with the sound setting, BUT that setting is affected by which modem is installed, which lead me down a false path.
Therefore your driver is OK, but why does it effect the sound setting?
Should that amixer setting be included as the default? Or will it mess up other cards?
Also, I never got the modem working using the snd_intel8x0m.
I hope that clears things up a bit.
Lyle
I have tried to find the least common denominator.
Booted from CD pfix=ram. Modem worked, no sound.
Opened terminal and ran:
amixer set 'Eternal Amplifier' off
Sound and modem both work. That was all that was needed.
Included lsmod from this point and from my F11 install (both work)
So I would conclude the sound problem is with the sound setting, BUT that setting is affected by which modem is installed, which lead me down a false path.
Therefore your driver is OK, but why does it effect the sound setting?
Should that amixer setting be included as the default? Or will it mess up other cards?
Also, I never got the modem working using the snd_intel8x0m.
I hope that clears things up a bit.
Lyle
- Attachments
-
- lsmodf11andworking430.tar.gz
- lsmod from working puppy and F11
- (1.84 KiB) Downloaded 320 times